diff --git a/marked/Rel-11/23_series/23002/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-11/23_series/23002/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7967d2a62c3edf81f16c98c0aa4ac5679cb83732 --- /dev/null +++ b/marked/Rel-11/23_series/23002/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f57558cbc65054c22baf8e7ce9a44f95a1344f2c66267bbf0c035d5edfe36d4 +size 99771 diff --git a/marked/Rel-11/23_series/23002/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Rel-11/23_series/23002/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3886a61b30443704cb4acd47132e0b6f760487e8 --- /dev/null +++ b/marked/Rel-11/23_series/23002/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56c6f96a7a67483231f8a47e4bb1fd2831a311f718b511d180a66f4d55c6ac7c +size 131990 diff --git a/marked/Rel-11/23_series/23002/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/23_series/23002/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b227a42b795b9155ad490b9d6b63ad65a60c1356 --- /dev/null +++ b/marked/Rel-11/23_series/23002/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c029df4d695da6b0289d6002262a8524f389a5a45cfa2074578eb2e634a0e3b +size 49940 diff --git a/marked/Rel-11/23_series/23002/3263a25e110201638bda790456af2909_img.jpg b/marked/Rel-11/23_series/23002/3263a25e110201638bda790456af2909_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b647df3a716f97437a2477988ddcbbfec570a6e2 --- /dev/null +++ b/marked/Rel-11/23_series/23002/3263a25e110201638bda790456af2909_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8648b21c053345e24a98b2070f6fca2d90fa584684f664b2971ce5c68912377 +size 22743 diff --git a/marked/Rel-11/23_series/23002/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-11/23_series/23002/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3a8e0a19183117c999931cd2abbd9f5cef87632 --- /dev/null +++ b/marked/Rel-11/23_series/23002/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:982ba8eaacf4ceb2af7f549c21fa9b66fed2590f3ca312da443bf8844e153a19 +size 34559 diff --git a/marked/Rel-11/23_series/23002/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-11/23_series/23002/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65e345708ace1a5841ac4d4992c50e5941687989 --- /dev/null +++ b/marked/Rel-11/23_series/23002/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:faeee21ae165aedee7f0db4c234aa261ddc7c28bc50aa29c6124fc1dae5a719c +size 210781 diff --git a/marked/Rel-11/23_series/23002/3c04b14104f95eb8f7100f6d497d956e_img.jpg b/marked/Rel-11/23_series/23002/3c04b14104f95eb8f7100f6d497d956e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7da64c30f4bf178b10f3c78afed416e740834e1e --- /dev/null +++ b/marked/Rel-11/23_series/23002/3c04b14104f95eb8f7100f6d497d956e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b17baed37f226afd39eb59c70372f95c2c5c5bf685ce71aac159839695a8b46f +size 70994 diff --git a/marked/Rel-11/23_series/23002/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-11/23_series/23002/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..841125b25bc3af3096c48e9a699f8962a69b1267 --- /dev/null +++ b/marked/Rel-11/23_series/23002/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34bd9b95efa72c22d7b6f1537144c2415c73833b3e71ce4ccecbc210a5e74fbb +size 73837 diff --git a/marked/Rel-11/23_series/23002/508bc574df81fa8d3027a374f6d155fc_img.jpg b/marked/Rel-11/23_series/23002/508bc574df81fa8d3027a374f6d155fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0c92a1d660bc3a5ed5153dc6a62f687b7d90720 --- /dev/null +++ b/marked/Rel-11/23_series/23002/508bc574df81fa8d3027a374f6d155fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27c61ad582419431aaec8df295c8860217f6c6a52f16dcb16ee9a5271f240722 +size 34564 diff --git a/marked/Rel-11/23_series/23002/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/23_series/23002/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8cf149a9dba0e9b01573966ce5ae16ab05b99ab --- /dev/null +++ b/marked/Rel-11/23_series/23002/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95cfe3284b4e2a2da37ac3cde99b52bab52ef21e09c6d35a5f05b38d1c581ebc +size 73161 diff --git a/marked/Rel-11/23_series/23002/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-11/23_series/23002/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a88674ca685399613ba03252a9bb9484b08e8eb --- /dev/null +++ b/marked/Rel-11/23_series/23002/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4ab80d9f5e3d9a7c5d53c26d064be2c8509b19361f3f0b7ec8fb9a4feb3cfac +size 92633 diff --git a/marked/Rel-11/23_series/23002/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Rel-11/23_series/23002/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60a53bd9b55902df749026e9e0027730d9eec731 --- /dev/null +++ b/marked/Rel-11/23_series/23002/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4b49233f1c0b5a7d3957753e0a7c936ccb7c6ce501790ce7786c96cdb79328c +size 39975 diff --git a/marked/Rel-11/23_series/23002/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-11/23_series/23002/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a370698997ce019a1237cf589678fa157e088ed --- /dev/null +++ b/marked/Rel-11/23_series/23002/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6efd40b08079ebb597c9344e1e58001db740b43f261d215a795e833806cd4af +size 62129 diff --git a/marked/Rel-11/23_series/23002/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-11/23_series/23002/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ff158024a7d250da2d6534bd4ca5c80fc5ffc2c --- /dev/null +++ b/marked/Rel-11/23_series/23002/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ab784b5d7a59e179e6fa910e3844de78687f35d48f2dc285325d68522fede75 +size 71299 diff --git a/marked/Rel-11/23_series/23002/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/23_series/23002/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..669fea9116be42b40ef280dda6040cf5ca6faa68 --- /dev/null +++ b/marked/Rel-11/23_series/23002/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61e95b4c1aa69e941c0f76ddb43654aad08039a97cbd08cd367bc26152b7affb +size 38690 diff --git a/marked/Rel-11/23_series/23002/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Rel-11/23_series/23002/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63473832724b2943c2546158d7c36d8f74965912 --- /dev/null +++ b/marked/Rel-11/23_series/23002/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64f9098ca3b851202e0ff1173bea89bb12d229cb35367afa8e057f4985973d46 +size 46151 diff --git a/marked/Rel-11/23_series/23002/74d23510f27b21403a7be84820821863_img.jpg b/marked/Rel-11/23_series/23002/74d23510f27b21403a7be84820821863_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6df27b5b319b374a9183c92967daf336396a01fe --- /dev/null +++ b/marked/Rel-11/23_series/23002/74d23510f27b21403a7be84820821863_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3595ee335576335633f3153d654cf3cb1f5e4c95596b8c8a3cd209931c9646fa +size 43996 diff --git a/marked/Rel-11/23_series/23002/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg b/marked/Rel-11/23_series/23002/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41c8a79e968a503b0a0103ecb6403311cf0a1f3c --- /dev/null +++ b/marked/Rel-11/23_series/23002/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d119457ec6e373fd2294ea8f01d87b1799fd0cb90aa5dbee2a3e8056c1fedaf +size 106607 diff --git a/marked/Rel-11/23_series/23002/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-11/23_series/23002/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81af720c1a9cc6f52ee7cea5bc1d3fbabe4e2acf --- /dev/null +++ b/marked/Rel-11/23_series/23002/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c90d273fadb09bef170e31c438570a65b6421fa15479c48c7a6294bcb77854e4 +size 6374 diff --git a/marked/Rel-11/23_series/23002/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/Rel-11/23_series/23002/848073118eebfdbfdb9a60e3923fe0b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96a31d02615a02b5cc926995c12b894a6c4e1928 --- /dev/null +++ b/marked/Rel-11/23_series/23002/848073118eebfdbfdb9a60e3923fe0b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:132cf00814953290d1aeb88e93732175773f228fcb3334066a9ad46f5bfdcd6e +size 40044 diff --git a/marked/Rel-11/23_series/23002/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-11/23_series/23002/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac9d9189597700913599c7e9fcb3b378ccdfe75e --- /dev/null +++ b/marked/Rel-11/23_series/23002/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8233b055d3cfd20ef974b86387aa657bd6c5e66a49242bad20e077225dd3ed5a +size 29247 diff --git a/marked/Rel-11/23_series/23002/90df9788d66ecf65abf861caf76be5ca_img.jpg b/marked/Rel-11/23_series/23002/90df9788d66ecf65abf861caf76be5ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61535b41f4c6710c90773cd81e167f9a37dc76b0 --- /dev/null +++ b/marked/Rel-11/23_series/23002/90df9788d66ecf65abf861caf76be5ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c895d6f38063751a40b859d883ece139cf8f328456c37af9c4eda0a47fc9128 +size 14958 diff --git a/marked/Rel-11/23_series/23002/921458d4fc1b778c2450592ac9745b48_img.jpg b/marked/Rel-11/23_series/23002/921458d4fc1b778c2450592ac9745b48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9ae44d1dd0250f1cf00f4263c46051cdad5139a --- /dev/null +++ b/marked/Rel-11/23_series/23002/921458d4fc1b778c2450592ac9745b48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2eb5a1709b36be4b6935d8f5ad98f94efee2e79348db3445dc6bc5e83f72444e +size 41710 diff --git a/marked/Rel-11/23_series/23002/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-11/23_series/23002/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d399c657264a11418272998cb7be5609b7bf6492 --- /dev/null +++ b/marked/Rel-11/23_series/23002/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1500cc203e70f1bb6e4fbd7a9c014731a8d4daecb3bdf73f1b2a934232934c82 +size 82283 diff --git a/marked/Rel-11/23_series/23002/9e26cd5584f423e1b2155fb341db579f_img.jpg b/marked/Rel-11/23_series/23002/9e26cd5584f423e1b2155fb341db579f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac8db35ac5cb8573a2bb52bb743deca51953c5c1 --- /dev/null +++ b/marked/Rel-11/23_series/23002/9e26cd5584f423e1b2155fb341db579f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9455fd1216c8fff1ec1b828e2eceec6bcc51b67ea4c9a234d8ed611abed18e8 +size 44194 diff --git a/marked/Rel-11/23_series/23002/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/23_series/23002/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30f05256fd31d12c0aae0f5dbe2965ab2e49f40a --- /dev/null +++ b/marked/Rel-11/23_series/23002/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37c4c38845a481c2086e4e2cc6d075fd2e104b975b4506aa7f9a1b6c479b0c0b +size 161590 diff --git a/marked/Rel-11/23_series/23002/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-11/23_series/23002/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c66ba6b770d31f13de3032ff923176764cf04aca --- /dev/null +++ b/marked/Rel-11/23_series/23002/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e119cc2f8c8119569f031039661d17423956aed6e5a1b7eb852a548a32562c84 +size 138912 diff --git a/marked/Rel-11/23_series/23002/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/23_series/23002/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbdaed2c3084afccb02d40b904eb68c6944455d8 --- /dev/null +++ b/marked/Rel-11/23_series/23002/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:220f23237694c92f82d8cbbe06a83cde526d0c508f54592d26c1f06c6c145a85 +size 21013 diff --git a/marked/Rel-11/23_series/23002/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-11/23_series/23002/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0720d2ee37be9584751892f1a50ce21c327dd53d --- /dev/null +++ b/marked/Rel-11/23_series/23002/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f661b15e6b088935fb3cc5df976632bd516561102762ce2b6766bf87c7e07b5f +size 52621 diff --git a/marked/Rel-11/23_series/23002/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-11/23_series/23002/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58846cb584664f5fb5477900917875aec506791c --- /dev/null +++ b/marked/Rel-11/23_series/23002/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a9244eeed30dcdc6b980196140d1bc14e3871fecf152d5f63c4b163da6fa5cd +size 113624 diff --git a/marked/Rel-11/23_series/23002/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-11/23_series/23002/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20f52b777b55ca12747d15ab9f59baa970d4a088 --- /dev/null +++ b/marked/Rel-11/23_series/23002/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68135ebeb9f8b6127e751553738fc49c5d4f5292c47adcbb30a2ecce6c666860 +size 43295 diff --git a/marked/Rel-11/23_series/23002/c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg b/marked/Rel-11/23_series/23002/c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..102ba93a80a79ffec4250de0154a8feb1d47d520 --- /dev/null +++ b/marked/Rel-11/23_series/23002/c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:208f99cfb57260d2b890c88a5ee23787f07164d1c3392cbd8888ddcf78b8e5f3 +size 41600 diff --git a/marked/Rel-11/23_series/23002/d7948c38a18636aefecdd95388196460_img.jpg b/marked/Rel-11/23_series/23002/d7948c38a18636aefecdd95388196460_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b418e7ebde915e44e7ea5bc307f2c709cdc8c90 --- /dev/null +++ b/marked/Rel-11/23_series/23002/d7948c38a18636aefecdd95388196460_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9398a0e5500bf9efb2c9747857b6e854ae529586c567ef2c359a5c95e297b47 +size 36500 diff --git a/marked/Rel-11/23_series/23002/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-11/23_series/23002/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd90828a465087469c170f7ecc8dde34dccf0e0f --- /dev/null +++ b/marked/Rel-11/23_series/23002/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4027edf8f5c2d26ceb7032583dd51ade85246d15a10e91c3a5381bfb9264dfe +size 47203 diff --git a/marked/Rel-11/23_series/23002/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/Rel-11/23_series/23002/db5deafdae53dbc7d5972957f708c691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6325aef80fe4deb058265ef842462580a7a1ea53 --- /dev/null +++ b/marked/Rel-11/23_series/23002/db5deafdae53dbc7d5972957f708c691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:469265b0f3742085ca0ab9bf927e4bbf492e27764f061786aa5db163baaeecbe +size 16569 diff --git a/marked/Rel-11/23_series/23002/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-11/23_series/23002/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adb005fd15863f38302116c7f72c79b215757d38 --- /dev/null +++ b/marked/Rel-11/23_series/23002/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:446888bd6986d98eb90f6eb171c96fc26252c4bf14bfa406f90a8e5f8f4b7cdb +size 54397 diff --git a/marked/Rel-11/23_series/23002/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-11/23_series/23002/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69c93c541470f2b9be2825fb7bec1f12e556522f --- /dev/null +++ b/marked/Rel-11/23_series/23002/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68b7ef9c0cb3b8bd521b0f02e3d690a87b4807baecf4b227fa03273b18afb49b +size 42884 diff --git a/marked/Rel-11/23_series/23002/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-11/23_series/23002/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..789b7ce6dab5abb7886a3cfb3d0ba8832f596f74 --- /dev/null +++ b/marked/Rel-11/23_series/23002/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:495b1828e0b8182d3d62dea65a19aaf51e34827182342fb08c6968318824191e +size 80159 diff --git a/marked/Rel-11/23_series/23002/raw.md b/marked/Rel-11/23_series/23002/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9a6db64679b1c31c506208a2454f0270a5f4b4e6 --- /dev/null +++ b/marked/Rel-11/23_series/23002/raw.md @@ -0,0 +1,3726 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------|----| +| Foreword ..... | 11 | +| Introduction ..... | 11 | +| 1 Scope..... | 12 | +| 2 References..... | 12 | +| 3 Definitions and abbreviations ..... | 17 | +| 3.1 Public Land Mobile Network (PLMN) ..... | 18 | +| 3.2 Core Network (CN) and Access Network (AN) ..... | 18 | +| 3.3 Circuit Switched (CS) and Packet Switched (PS) Domains ..... | 18 | +| 3.3.1 CS Domain ..... | 18 | +| 3.3.2 PS Domain..... | 18 | +| 3.3a IP Multimedia subsystem (IMS) ..... | 18 | +| 3.4 Location register..... | 19 | +| 3.5 Cell..... | 19 | +| 3.6 Base Station Controller (BSC) area ..... | 19 | +| 3.7 Radio Network Controller (RNC) area ..... | 20 | +| 3.8 Location Area (LA) ..... | 20 | +| 3.9 Routing Area (RA)..... | 20 | +| 3.9a Tracking Area (TA)..... | 20 | +| 3.10 MSC area..... | 20 | +| 3.11 VLR area ..... | 20 | +| 3.12 SGSN area ..... | 20 | +| 3.13 Zones for Regional Subscription..... | 20 | +| 3.14 Service area ..... | 21 | +| 3.15 Group call area ..... | 21 | +| 3.15a MME Area..... | 21 | +| 3.16 Pool-area..... | 21 | +| 3.17 Serving GW Service Area..... | 21 | +| 4 The basic entities of the mobile system ..... | 21 | +| 4.1 The Core Network (CN) entities ..... | 22 | +| 4.1.1 Entities common to the PS and CS domains ..... | 22 | +| 4.1.1.1 The Home Subscriber Server (HSS)..... | 22 | +| 4.1.1.1.1 The Home Location Register (HLR)..... | 23 | +| 4.1.1.1.2 The Authentication Centre (AuC)..... | 23 | +| 4.1.1.1.3 HSS logical functions..... | 23 | +| 4.1.1.2 The Visitor Location Register (VLR)..... | 25 | +| 4.1.1.3 (void)..... | 26 | +| 4.1.1.4 The Equipment Identity Register (EIR)..... | 26 | +| 4.1.1.5 SMS Gateway MSC (SMS-GMSC) ..... | 26 | +| 4.1.1.6 SMS Interworking MSC (SMS-IWMSC)..... | 26 | +| 4.1.1.7 Subscription Locator Function (SLF) ..... | 26 | +| 4.1.2 Entities of the CS domain..... | 26 | +| 4.1.2.1 The Mobile-services Switching Centre (MSC) ..... | 26 | +| 4.1.2.1.1 MSC Server ..... | 27 | +| 4.1.2.1.2 Circuit Switched - Media Gateway Function (CS-MGW)..... | 27 | +| 4.1.2.2 The Gateway MSC (GMSC)..... | 28 | +| 4.1.2.2.1 Gateway MSC Server (GMSC Server) ..... | 28 | +| 4.1.2.3 The Interworking Function (IWF) ..... | 28 | +| 4.1.3 Entities of the GPRS PS domain ..... | 28 | +| 4.1.3.1 Serving GPRS Support Node (SGSN)..... | 29 | +| 4.1.3.2 Gateway GPRS Support Node (GGSN) ..... | 29 | +| 4.1.3.3 Void ..... | 29 | +| 4.1.4 Entities of the EPC PS Domain ..... | 30 | +| 4.1.4.1 MME..... | 30 | +| 4.1.4.2 Gateways..... | 31 | + +| | | | +|------------|------------------------------------------------------------------------------------------------------|----| +| 4.1.4.2.1. | Serving GW ..... | 31 | +| 4.1.4.2.2 | PDN GW ..... | 31 | +| 4.1.4.3 | SGSN ..... | 32 | +| 4.1.4.4 | Trusted and Untrusted Non-3GPP Access Network..... | 32 | +| 4.1.4.5 | ePDG..... | 32 | +| 4.1.4.6 | 3GPP AAA Server ..... | 33 | +| 4.1.4.7 | 3GPP AAA Proxy ..... | 33 | +| 4.1.4.8 | ANDSF ..... | 33 | +| 4.1.5 | Border Gateway (BG)] ..... | 33 | +| 4.2 | The Access Network (AN) entities ..... | 34 | +| 4.2.1 | The Base Station System (BSS) ..... | 34 | +| 4.2.1.1 | Base Station Controller (BSC)..... | 34 | +| 4.2.1.2 | Base Transceiver Station (BTS) ..... | 34 | +| 4.2.2 | The Radio Network System (RNS) ..... | 34 | +| 4.2.2.1 | Radio Network Controller (RNC)..... | 35 | +| 4.2.2.2 | Node B ..... | 35 | +| 4.2.3 | Access Network elements for E-UTRAN ..... | 35 | +| 4.2.3.1 | E-UTRAN Node B (eNB)..... | 35 | +| 4.2.3.2 | Evolved UTRAN ..... | 35 | +| 4.3 | The Mobile Station (MS) ..... | 35 | +| 4.4 | User Equipment (UE)..... | 35 | +| 4a | The specific entities of the 3GPP system..... | 35 | +| 4a.1 | The Group Call Register (GCR) entity ..... | 36 | +| 4a.2 | (void)..... | 36 | +| 4a.3 | The Location Services (LCS) entities ..... | 36 | +| 4a.3.1 | Location Services (LCS) entities in RAN ..... | 37 | +| 4a.3.2 | Gateway Mobile Location Centre (GMLC) ..... | 37 | +| 4a.3.3 | Location Measurement Unit (LMU) ..... | 37 | +| 4a.3.4 | Evolved Serving Mobile Location Centre (E-SMLC)..... | 38 | +| 4a.4 | CAMEL entities ..... | 38 | +| 4a.4.1 | GSM Service Control Function (gsmSCF)..... | 38 | +| 4a.4.2 | GSM Service Switching Function (gsmSSF) ..... | 38 | +| 4a.4.3 | GSM Specialised Resource Function (gsmSRF)..... | 39 | +| 4a.4.4 | GPRS Service Switching Function (gprsSSF) ..... | 39 | +| 4a.5 | CBS-specific entities..... | 39 | +| 4a.5.1 | Cell Broadcast Centre (CBC)..... | 39 | +| 4a.6 | Number Portability Specific entities ..... | 39 | +| 4a.6.1 | IN-based solution: Number Portability Database (NPDB) ..... | 39 | +| 4a.6.2 | Signalling Relay-based solution: Mobile Number Portability/Signalling Relay function (MNP-SRF) ..... | 39 | +| 4a.7 | IP Multimedia (IM) Core Network (CN) Subsystem entities ..... | 40 | +| 4a.7.1 | Call Session Control Function (CSCF) ..... | 40 | +| 4a.7.2 | Media Gateway Control Function (MGCF) ..... | 40 | +| 4a.7.3 | IP Multimedia Subsystem - Media Gateway Function (IMS-MGW) ..... | 40 | +| 4a.7.4 | Multimedia Resource Function Controller (MRFC) ..... | 40 | +| 4a.7.4a | Multimedia Resource Function Processor (MRFP) ..... | 40 | +| 4a.7.4b | Media Resource Broker (MRB) ..... | 41 | +| 4a.7.5 | Void ..... | 41 | +| 4a.7.6 | Breakout Gateway Control Function (BGCF)..... | 41 | +| 4a.7.7 | Application Server (AS) ..... | 41 | +| 4a.7.8 | Interconnection Border Control Function (IBCF) ..... | 42 | +| 4a.7.9 | Transition Gateway (TrGW) ..... | 42 | +| 4a.7.10 | Location Retrieval Function (LRF) ..... | 42 | +| 4a.7.11 | Service Centralization and Continuity Application Server (SCC AS) ..... | 42 | +| 4a.7.11a | Emergency Access Transfer Function (EATF) ..... | 42 | +| 4a.7.12 | Access Transfer Control Function (ATCF) ..... | 42 | +| 4a.7.13 | Access Transfer Gateway (ATGW) ..... | 43 | +| 4a.8 | Signalling Gateway Function (SGW) ..... | 43 | +| 4a.9 | Global Text Telephony Specific entities..... | 43 | +| 4a.10 | Security Gateway (SEG) ..... | 43 | +| 4a.11 | Application Function (AF) ..... | 43 | + +| | | | +|---------|-------------------------------------------------------------------------------------------------------------|----| +| 4a.12 | Void..... | 43 | +| 4a.13 | 3GPP/WLAN Interworking entities ..... | 44 | +| 4a.13.1 | WLAN UE..... | 44 | +| 4a.13.2 | 3GPP AAA Proxy..... | 44 | +| 4a.13.3 | 3GPP AAA Server..... | 44 | +| 4a.13.4 | WLAN Access Gateway (WAG) ..... | 44 | +| 4a.13.5 | Packet Data Gateway (PDG) ..... | 44 | +| 4a.13.6 | Home Agent (HA) ..... | 44 | +| 4a.14 | Multimedia Broadcast Multicast Service (MBMS) specific entities ..... | 44 | +| 4a.14.1 | General ..... | 44 | +| 4a.14.2 | Broadcast-Multicast Service Centre (BM-SC)..... | 44 | +| 4a.14.3 | MBMS-GW ..... | 44 | +| 4a.14.4 | Multi-cell/multicast Coordination Entity (MCE) ..... | 45 | +| 4a.15 | Void..... | 45 | +| 4a.16 | GUP Server ..... | 45 | +| 4a.17 | Policy and Charging Rules Function (PCRF) ..... | 45 | +| 4a.18 | Policy and Charging Enforcement Function (PCEF)..... | 45 | +| 4a.19 | Support of Short Message Service over generic 3GPP Internet Protocol access (SMSIP) specific entities ..... | 46 | +| 4a.19.1 | General ..... | 46 | +| 4a.19.2 | IP-Short-Message-Gateway (IP-SM-GW) ..... | 46 | +| 4a.20 | Subscription Profile Repository (SPR) ..... | 46 | +| 4a.21 | Service Data Flow Based Credit Control Function..... | 46 | +| 4a.22 | Offline Charging System (OFCS)..... | 46 | +| 4a.23 | Online Charging System (OCS)..... | 46 | +| 4a.24 | Bearer Binding and Event Reporting Function (BBERF)..... | 46 | +| 4a.25 | Home (e)NodeB entities..... | 46 | +| 4a.25.1 | Home NodeB Subsystem (HNS)..... | 46 | +| 4a.25.2 | Home eNodeB Subsystem (HeNS) ..... | 47 | +| 4a.25.3 | CSG List Server..... | 47 | +| 4a.25.4 | CSG Subscriber Server (CSS)..... | 47 | +| 4a.26 | Application Front Ends (AFE) ..... | 48 | +| 4a.27 | User Data Repository (UDR)..... | 48 | +| 4a.28 | Traffic Detection Function (TDF)..... | 48 | +| 4a.29 | Specific entities to facilitate communications with packet data networks and applications..... | 48 | +| 4a.29.1 | Machine Type Communication-InterWorking Function (MTC-IWF)..... | 48 | +| 4a.29.2 | Machine Type Communication- Authentication, Authorization and Accounting (MTC-AAA) ..... | 48 | +| 5 | Configuration of a Public Land Mobile Network ..... | 48 | +| 5.1 | Basic configuration ..... | 48 | +| 5.2 | Configuration of LCS entities ..... | 53 | +| 5.2.1 | Configuration of LCS entities for GERAN ..... | 53 | +| 5.2.2 | Configuration of LCS entities for UTRAN ..... | 54 | +| 5.2.3 | Configuration of LCS entities for E-UTRAN ..... | 54 | +| 5.3 | Configuration of CAMEL entities..... | 55 | +| 5.4 | Configuration of CBS entities ..... | 56 | +| 5.5 | Configuration of IM CN Subsystem entities..... | 56 | +| 5.5.1 | IM CN Subsystem functional entities..... | 56 | +| 5.5.2 | IM CN Subsystem Service layer ..... | 57 | +| 5.5.3 | Service Centralization and Continuity..... | 59 | +| 5.6 | Configuration of Signalling Gateway Function ..... | 60 | +| 5.7 | Configuration of 3GPP/WLAN Interworking..... | 60 | +| 5.8 | Configuration of Presence service..... | 61 | +| 5.9 | Configuration of MBMS entities..... | 61 | +| 5.10 | Configuration of Short Message Service over generic 3GPP Internet Protocol access (SMSIP) entities ..... | 63 | +| 5.11 | Configuration of Policy Control and Charging entities ..... | 63 | +| 5.12 | Configuration of CSFB(CS Fallback)..... | 66 | +| 5.13 | Configuration of Single Radio Voice Call Continuity (SRVCC)..... | 67 | +| 5.13.1 | E-UTRAN/UTRAN (HSPA) to UTRAN or GERAN SRVCC architecture ..... | 67 | +| 5.13.2 | UTRAN/GERAN to E-UTRAN or UTRAN (HSPA) SRVCC architecture ..... | 68 | +| 5.14 | Configuration of Security..... | 70 | +| 5.15 | Configuration of Lawful Intercept related entities ..... | 70 | + +| | | | +|----------|------------------------------------------------------------------------------------------------|----| +| 5.16 | Configuration of Charging related entities..... | 71 | +| 5.17 | Configuration of Home (e)NodeB entities ..... | 72 | +| 5.17.1 | Configuration of the Home NodeB Subsystem ..... | 72 | +| 5.17.2 | Configuration of the Home eNodeB Subsystem ..... | 73 | +| 5.18 | Configuration for facilitating communications with packet data networks and applications ..... | 74 | +| 6 | PLMN basic interfaces and reference points ..... | 74 | +| 6.1 | Interfaces between Mobile Station and the Fixed Infrastructure ..... | 74 | +| 6.1.1 | Interface between Mobile Station and Base Station System (Um-interface) ..... | 74 | +| 6.1.2 | Interface between User Equipment and Radio Network System (Uu-interface)..... | 75 | +| 6.1.3 | Interface between User Equipment and Evolved UTRAN (E-UTRAN Uu-interface) ..... | 75 | +| 6.2 | Interface between the Core Network and the Access Network..... | 75 | +| 6.2.1 | Interfaces between the CS domain and the Access Network ..... | 75 | +| 6.2.1.1 | Interface between the MSC and Base Station System (A-interface)..... | 75 | +| 6.2.1.2 | Interface between the MSC and Base Station System (Iu_CS interface) ..... | 75 | +| 6.2.1.3 | Interface between the MSC and RNS (Iu_CS interface) ..... | 75 | +| 6.2.2 | Interfaces between the PS domain and the Access Network..... | 75 | +| 6.2.2.1 | Interface between SGSN and BSS (Gb-interface)..... | 75 | +| 6.2.2.2 | Interface between SGSN and BSS (Iu_PS-interface)..... | 76 | +| 6.2.2.3 | Interface between SGSN and RNS (Iu_PS-interface) ..... | 76 | +| 6.2.3 | Interfaces between the Evolved Packet Core and the Access Network ..... | 76 | +| 6.2.3.1 | Interface between MME and E-UTRAN (S1-MME-interface)..... | 76 | +| 6.2.3.2 | Interface between S-GW and E-UTRAN (S1-U-interface)..... | 76 | +| 6.3 | Interfaces internal to the Access Network..... | 76 | +| 6.3.1 | Interface between BSC and BTS (Abis-interface) ..... | 76 | +| 6.3.2 | Interface between RNC and Node B (Iub-interface)..... | 76 | +| 6.3.3 | Interface between two RNCs (Iur-interface) ..... | 77 | +| 6.3.4 | Interface between two eNBs (X2-interface)..... | 77 | +| 6.3.5 | Interface between HNB and HNB-GW(luh-interface)..... | 77 | +| 6.4 | Interfaces internal to the Core Network ..... | 77 | +| 6.4.1 | Interfaces internal to the CS domain ..... | 77 | +| 6.4.1.1 | Interface between the MSC server and its associated VLR (B-interface) ..... | 77 | +| 6.4.1.2 | Interface between the HLR and the MSC server (C-interface) ..... | 77 | +| 6.4.1.3 | Interface between the HLR and the VLR (D-interface) ..... | 77 | +| 6.4.1.4 | Interface between MSC servers or MSC server and IP-SM-GW (E-interface)..... | 78 | +| 6.4.1.5 | Interface between MSC server and EIR (F-interface) ..... | 78 | +| 6.4.1.6 | Interface between VLRs (G-interface) ..... | 78 | +| 6.4.1.7 | Reference point (G)MSC server – CS-MGW (Mc Reference Point) ..... | 78 | +| 6.4.1.8 | Reference Point MSC Server – GMSC Server (Nc Reference Point) ..... | 78 | +| 6.4.1.9 | Reference Point CS-MGW – CS-MGW (Nb Reference Point)..... | 79 | +| 6.4.1.10 | Reference Point between the CSS and the VLR (Hv Reference Point)..... | 79 | +| 6.4.2 | Interfaces internal to the PS domain (GPRS) ..... | 79 | +| 6.4.2.1 | Interface between SGSN and HLR (Gr-interface)..... | 79 | +| 6.4.2.2 | Interface between SGSN and GGSN (Gn- and Gp-interface) ..... | 79 | +| 6.4.2.3 | Signalling Path between GGSN and HLR (Gc-interface) ..... | 79 | +| 6.4.2.4 | Interface between SGSN and EIR (Gf-interface) ..... | 79 | +| 6.4.2.5 | Reference Point between the CSS and the Gn/Gp SGSN (Ghv Reference Point) ..... | 80 | +| 6.4.3 | Interfaces used by CS and PS domains ..... | 80 | +| 6.4.3.1 | Interface between MSC/VLR and SGSN (Gs-interface) for GPRS ..... | 80 | +| 6.4.3.2 | Interface between HLR/HSS and AuC (H-Interface) ..... | 80 | +| 6.4.3.3 | Interface between SGSN/IP-SM-GW and SMS-GMSC/SMS-IWMSC (Gd-Interface) for GPRS ..... | 80 | +| 6.4.3.4 | Interface between MSC/VLR and MME (SGs-interface) for EPC ..... | 80 | +| 6.4.3.5 | Interface between 3GPP MSC Server and MME or SGSN (Sv-interface)..... | 80 | +| 6.4.4 | Interfaces internal & related to the Evolved Packet Core ..... | 80 | +| 6.4.4.1 | Interface between MME and HSS (S6a-interface) ..... | 80 | +| 6.4.4.2 | Interface between SGSN and HSS (S6d-interface) ..... | 81 | +| 6.4.4.3 | Interface between MME and S-GW (S11-interface) ..... | 81 | +| 6.4.4.4 | Interface between MME and MME (S10-interface)..... | 81 | +| 6.4.4.5 | Interface between S-GW and PDN GW (S5 and S8-interface) ..... | 81 | +| 6.4.4.6 | Interface between MME and EIR (S13-interface)..... | 81 | +| 6.4.4.7 | Interface between MME and SGSN (S3-interface) ..... | 81 | + +| | | | +|----------|---------------------------------------------------------------------------------------------------|----| +| 6.4.4.8 | Interface between S-GW and SGSN (S4-interface) ..... | 81 | +| 6.4.4.9 | Interface between S-GW and UTRAN (S12-interface)..... | 81 | +| 6.4.4.10 | Interface between Trusted non-3GPP IP Access and S-GW/PDN GW (S2a-interface) ..... | 82 | +| 6.4.4.11 | Interface between PDN GW/S-GW and ePDG (S2b-interface) ..... | 82 | +| 6.4.4.12 | Interface between PDN GW and UE (S2c-interface) ..... | 82 | +| 6.4.4.13 | Interface between PDN GW and 3GPP AAA Server/proxy (S6b-interface) ..... | 82 | +| 6.4.4.14 | Interface between Untrusted non-3GPP IP Access and 3GPP AAA Server/proxy (SWa-interface) ..... | 82 | +| 6.4.4.15 | Interface between Trusted non-3GPP IP Access and 3GPP AAA Server/proxy (STa-interface) ..... | 82 | +| 6.4.4.16 | Interface between 3GPP AAA Server and 3GPP AAA proxy (SWd-interface) ..... | 82 | +| 6.4.4.17 | Interface between ePDG and 3GPP AAA Server/proxy (SWm-interface) ..... | 82 | +| 6.4.4.18 | Interface between ePDG and Untrusted non-3GPP Access (SWn-interface)..... | 82 | +| 6.4.4.19 | Interface between ePDG and UE (SWu-interface) ..... | 83 | +| 6.4.4.20 | Interface between HSS and 3GPP AAA Server (SWx-interface) ..... | 83 | +| 6.4.4.21 | Interface between UE and ANDSF (S14-interface) ..... | 83 | +| 6.4.4.22 | Reference point between HRDP AN and MME (S101-reference point)..... | 83 | +| 6.4.4.23 | Reference point between 3GPP2 1xCS IWS and MME (S102-reference point) ..... | 83 | +| 6.4.4.24 | Interface between HSGW and S-GW (S103-interface)..... | 83 | +| 6.4.4.25 | Reference point between UE and CSG List Server (Uh reference point)..... | 83 | +| 6.4.4.26 | Reference Point between the CSS and the S4-SGSN (S7d Reference Point) ..... | 83 | +| 6.4.4.27 | Reference point between the CSS and the MME (S7a reference point)..... | 83 | +| 6.4.4.28 | Reference point between the MME and the SMS-GMSC/SMS-IWMSC/SMS Router (SGd reference point) ..... | 84 | +| 6.4.4.29 | Reference point between the HSS and the SMS-GMSC/SMS-IWMSC/SMS Router (S6c reference point)..... | 84 | +| 6a | PLMN specific interfaces..... | 84 | +| 6a.1 | GCR-specific interface..... | 84 | +| 6a.1.1 | Interface between the MSC and its associated GCR (I-interface)..... | 84 | +| 6a.2 | (void)..... | 84 | +| 6a.3 | LCS-specific interfaces ..... | 84 | +| 6a.3.1 | LCS interfaces using MAP ..... | 84 | +| 6a.3.2 | (void) ..... | 84 | +| 6a.3.3 | (void) ..... | 85 | +| 6a.3.4 | (void) ..... | 85 | +| 6a.3.5 | Interface between BSC and SMLC (Lb-interface)..... | 85 | +| 6a.3.6 | Interface between Peer SMLCs (Lp-interface)..... | 85 | +| 6a.3.7 | Interface between BTS and LMU (Um-interface)..... | 85 | +| 6a.3.8 | Interface between GMLC and External LCS Client (Le-interface) ..... | 85 | +| 6a.3.9 | Interface between RNS and Stand-Alone LMU, UE (Uu-interface)..... | 85 | +| 6a.3.10 | Interface between SRNC and SAS (Stand-Alone SMLC) (Iupc-interface) ..... | 85 | +| 6a.3.11 | Interface between GMLC and GMLC (Lr-interface) ..... | 85 | +| 6a.3.12 | Interface between GMLC and MME (SLg-interface) ..... | 85 | +| 6a.3.13 | Interface between MME and E-SMLC (SLs-interface) ..... | 86 | +| 6a.3.14 | Interface between GMLC and HSS (SLh-interface) ..... | 86 | +| 6a.4 | CAMEL-specific interfaces..... | 86 | +| 6a.4.1 | GMSC - gsmSSF interface ..... | 86 | +| 6a.4.2 | gsmSSF - gsmSCF interface ..... | 86 | +| 6a.4.3 | MSC - gsmSSF interface ..... | 86 | +| 6a.4.4 | gsmSCF - HLR interface ..... | 86 | +| 6a.4.5 | gsmSCF - gsmSRF interface..... | 86 | +| 6a.4.6 | MSC - gsmSCF interface..... | 86 | +| 6a.4.7 | SGSN - gprsSSF interface ..... | 86 | +| 6a.4.8 | gprsSSF - gsmSCF interface (Ge Reference Point)..... | 86 | +| 6a.5 | CBS-specific interfaces..... | 87 | +| 6a.5.1 | Interface between the CBC and RNS (Iu_BC Interface)..... | 87 | +| 6a.5.2 | Interface between the CBC and MME (SBc Interface)..... | 87 | +| 6a.5.3 | Interface between the CBC and BSC ..... | 87 | +| 6a.6 | Number portability specific interfaces ..... | 87 | +| 6a.6.1 | IN-based solution..... | 87 | +| 6a.6.1.1 | NPDB to MSC interface ..... | 87 | +| 6a.6.2 | Signalling Relay-based solution..... | 87 | + +| | | | +|----------|----------------------------------------------------------------------------------------|----| +| 6a.6.2.1 | GMSC to MNP-SRF interface ..... | 87 | +| 6a.6.2.2 | MNP-SRF to HLR interface ..... | 87 | +| 6a.7 | IM Subsystem Reference Points ..... | 88 | +| 6a.7.1 | Reference Point HSS – CSCF (Cx Reference Point) ..... | 88 | +| 6a.7.2 | Reference Point CSCF – UE (Gm Reference Point) ..... | 88 | +| 6a.7.3 | Reference Point MGCF – IMS-MGW (Mn Reference Point)..... | 88 | +| 6a.7.4 | Reference Point MGCF – CSCF (Mg Reference Point) ..... | 88 | +| 6a.7.5 | (void) ..... | 88 | +| 6a.7.5a | Reference Point AS-MRFC for media control (Cr Reference Point)..... | 88 | +| 6a.7.5b | Reference Point AS-MRFC for session control (Mr' Reference Point) ..... | 89 | +| 6a.7.6 | Reference Point CSCF - MRFC (Mr Reference Point) ..... | 89 | +| 6a.7.6a | Reference Point MRFC – MRFP (Mp Reference Point)..... | 89 | +| 6a.7.7 | Reference Point CSCF – CSCF (Mw Reference Point) ..... | 89 | +| 6a.7.8 | (void) ..... | 89 | +| 6a.7.8a | Reference Point CSCF – MRB (ISC Reference Point) ..... | 89 | +| 6a.7.9 | (void) ..... | 89 | +| 6a.7.9a | Reference Point AS – MRB (Rc Reference Point)..... | 89 | +| 6a.7.10 | Reference Point CSCF – BGCF (Mi reference point)..... | 90 | +| 6a.7.11 | Reference Point BGCF – MGCF (Mj reference point) ..... | 90 | +| 6a.7.12 | Reference Point BGCF/IBCF – BGCF (Mk reference point) ..... | 90 | +| 6a.7.13 | Reference Point CSCF- SLF (Dx Reference Point) ..... | 90 | +| 6a.7.14 | Reference Point to IPv6 network services (Mb reference point)..... | 90 | +| 6a.7.15 | Reference Point S-CSCF – AS (ISC Reference Point) ..... | 90 | +| 6a.7.15a | Reference Point E-CSCF - EATF (I4 Reference Point) ..... | 90 | +| 6a.7.15b | Reference Point I-CSCF - EATF (I5 Reference Point) ..... | 90 | +| 6a.7.16 | Reference Point HSS – SIP AS or OSA SCS (Sh Reference Point) ..... | 90 | +| 6a.7.17 | Reference Point HSS – CAMEL IM-SSF (Si Reference Point)..... | 91 | +| 6a.7.18 | Reference Point UE – AS (Ut Reference Point)..... | 91 | +| 6a.7.19 | Reference Point AS- SLF (Dh Reference Point) ..... | 91 | +| 6a.7.20 | Reference Point CSCF/BGCF - IBCF (Mx Reference Point) ..... | 91 | +| 6a.7.21 | Reference Point IBCF - TrGW (Ix Reference Point) ..... | 91 | +| 6a.7.22 | Reference Point I-CSCF – AS (Ma Reference Point) ..... | 91 | +| 6a.7.23 | Reference Point P-CSCF – IMS Access Gateway (Iq Reference Point) ..... | 91 | +| 6a.7.23a | Reference Point E-CSCF - LRF (MI Reference Point) ..... | 92 | +| 6a.7.24 | Reference Point IBCF - IBCF (Ici Reference Point)..... | 92 | +| 6a.7.25 | Reference Point TrGW - TrGW (Izi Reference Point)..... | 92 | +| 6a.7.26 | Void ..... | 92 | +| 6a.7.27 | Reference Point MSC Server - CSCF (I2 Reference Point)..... | 92 | +| 6a.7.28 | Reference Point MSC Server - TAS (I3 Reference Point) ..... | 92 | +| 6a.7.29 | Reference Point ICS UE – SCC AS (I1 Reference Point)..... | 92 | +| 6a.8 | Void ..... | 92 | +| 6a.9 | Reference Points for 3GPP/WLAN Interworking ..... | 92 | +| 6a.9.1 | Reference point 3GPP AAA Server - HLR (D'/Gr' Reference Point) ..... | 93 | +| 6a.9.2 | Reference point WLAN access network - 3GPP AAA Proxy/Server (Wa Reference Point) ..... | 93 | +| 6a.9.3 | Reference point 3GPP AAA Server – 3GPP AAA Proxy (Wd Reference Point)..... | 93 | +| 6a.9.4 | Reference point 3GPP AAA Server/Proxy - WAG (Wg Reference Point)..... | 93 | +| 6a.9.5 | Reference point PDG - packet data networks (Wi Reference Point) ..... | 93 | +| 6a.9.6 | Reference Point 3GPP AAA Server/Proxy - PDG (Wm Reference Point)..... | 93 | +| 6a.9.7 | Reference Point WAG - WLAN access network (Wn Reference Point) ..... | 93 | +| 6a.9.8 | Reference Point WAG - PDG (Wp Reference Point)..... | 93 | +| 6a.9.9 | Reference point WLAN UE - PDG (Wu Reference Point) ..... | 94 | +| 6a.9.10 | Reference point WLAN UE - WLAN access network (Ww Reference Point)..... | 94 | +| 6a.9.11 | Reference point 3GPP AAA Server - HSS (Wx Reference Point)..... | 94 | +| 6a.9.12 | Reference point 3GPP AAA Server - SLF (Dw reference point)..... | 94 | +| 6a.10 | MBMS specific reference points for GPRS ..... | 94 | +| 6a.10.1 | Reference point GGSN – BM-SC (Gmb Reference Point) ..... | 94 | +| 6a.10.2 | Reference point BM-SC – BM-SC (Mz Reference Point) ..... | 94 | +| 6a.10.3 | Reference point GGSN – RNS (or BSS Iu mode) (Gmc Reference Point)..... | 94 | +| 6a.11 | MBMS specific reference points for EPS ..... | 95 | +| 6a.11.1 | Reference point MBMS-GW – BM-SC (SGmb Reference Point)..... | 95 | +| 6a.11.2 | Reference point MBMS-GW – BM-SC (SGi-mb Reference Point) ..... | 95 | +| 6a.11.3 | Reference point MBMS-GW - MME (Sm Reference Point) ..... | 95 | + +| | | | +|-------------------------------|--------------------------------------------------------------------------------------------------------|------------| +| 6a.11.4 | Reference point MBMS-GW – SGSN (Sn Reference Point) ..... | 95 | +| 6a.11.5 | Reference point MBMS-GW – E-UTRAN/UTRAN (M1 Reference Point) ..... | 95 | +| 6a.11.6 | Reference point MME – MCE (M3 Reference Point)..... | 95 | +| 6a.11.7 | Reference point MCE - eNodeB (M2 Reference Point)..... | 95 | +| 6a.12 | Reference Points for 3GPP Generic User Profile (GUP)..... | 95 | +| 6a.12.1 | Reference Point GUP Server – Applications (Rg Reference Point)..... | 95 | +| 6a.12.2 | Reference Point GUP Server – HSS and Applications – HSS (Rp Reference Point) ..... | 96 | +| 6a.13 | Reference Points for Policy and Charging Control..... | 96 | +| 6a.13.1 | Reference Point PCEF - PCRF/H-PCRF/V-PCRF (Gx Reference Point) ..... | 96 | +| 6a.13.2 | Reference Point PCRF - Application Function (Rx Reference Point) ..... | 96 | +| 6a.13.3 | Reference Point SPR – PCRF (Sp Reference Point)..... | 96 | +| 6a.13.4 | Reference Point OCS – PCEF (Gy Reference Point) ..... | 96 | +| 6a.13.5 | Reference Point OFCS – PCEF (Gz Reference Point)..... | 96 | +| 6a.13.6 | Reference Point Trusted non-3GPP IP Access and PCRF/VPCRF (Gxa Reference Point) ..... | 96 | +| 6a.13.7 | Reference Point ePDG and PCRF/VPCRF (Gxb Reference Point) ..... | 96 | +| 6a.13.7a | Reference Point ePDG and PCRF/VPCRF (Gxb* Reference Point) ..... | 96 | +| 6a.13.8 | Reference point between S-GW and PCRF/VPCRF (Gxc-interface)..... | 97 | +| 6a.13.9 | Reference Point PCRF/VPCRF – BBERF (Gxx Reference Point)..... | 97 | +| 6a.13.10 | Reference Point HPCRF - VPCRF (S9- interface)..... | 97 | +| 6a.13.11 | Reference Point UDR – PCRF (Ud Reference Point)..... | 97 | +| 6a.13.12 | Reference Point TDF - PCRF/H-PCRF/V-PCRF (Sd Reference Point) ..... | 97 | +| 6a.13.13 | Reference Point OCS - PCRF/H-PCRF (Sy Reference Point)..... | 97 | +| 6a.13.14 | Reference Point HNB GW - PCRF/V-PCRF (S15 Reference Point)..... | 97 | +| 6a.13.15 | Reference Point BPCF - PCRF/v-PCRF (S9a Reference Point)..... | 97 | +| 6a.14 | SMSIP specific reference points ..... | 97 | +| 6a.14.1 | Reference point IP-SM-GW – HSS (J Reference Point)..... | 97 | +| 6a.15 | User Data Convergence specific reference points..... | 98 | +| 6a.15.1 | Reference point Application Front Ends - UDR (Ud Reference Point) ..... | 98 | +| 6a.16 | Specific reference points for facilitating communications with packet data networks and applications.. | 98 | +| 6a.16.1 | Reference point MTC-IWF - SCS (Tsp reference point) ..... | 98 | +| 6a.16.2 | Reference point MTC-IWF - HSS/HLR (S6m reference point)..... | 98 | +| 6a.16.3 | Reference point MTC-AAA - HSS/HLR (S6n reference point) ..... | 98 | +| 6a.16.4 | Reference point MTC-IWF - SMS-SC (T4 reference point)..... | 98 | +| 7 | Reference points between the PLMN and other networks..... | 98 | +| 7.1 | Reference point fixed networks - MSC..... | 99 | +| 7.2 | Reference point GGSN - packet data networks (Gi reference point)..... | 99 | +| 7.2a | Reference point PDN GW - packet data networks (SGi reference point)..... | 99 | +| 7.3 | Reference point GMLC - external LCS Client (Le reference point)..... | 99 | +| 7.4 | Reference Point CSCF/IBCF – Multimedia IP networks (Mm Reference Point)..... | 99 | +| 7.5 | (void)..... | 99 | +| 7.6 | Reference point PDG - packet data networks (Wi reference point)..... | 99 | +| 7.7 | Reference Point WAG – WLAN access network (Wn reference point)..... | 99 | +| 7.8 | Reference point MTC-IWF - SCS (Tsp reference point)..... | 99 | +| Annex A (informative): | Description for GLR-related entities and interfaces..... | 101 | +| A.1 | Normative references ..... | 101 | +| A.2 | Definitions related to Gateway Location Register (GLR) ..... | 101 | +| A.2.1 | Gateway Location Register (GLR) ..... | 101 | +| A.2.2 | Intermediate Mobile-services Switching Centre (IM- MSC)..... | 101 | +| A.2.3 | Intermediate GPRS Serving Node (IM-GSN)..... | 101 | +| A.3 | The entities of the mobile system ..... | 101 | +| A.3.1 | Gateway Location Register (GLR) ..... | 101 | +| A.3.2 | Intermediate Mobile-services Switching Centre (IM- MSC)..... | 102 | +| A.3.3 | Intermediate GPRS Serving Node (IM-GSN)..... | 102 | +| A.4 | Configuration of a Public Land Mobile Network ..... | 102 | +| A.4.1 | Basic configuration with GLR introduction..... | 102 | +| A.5 | PLMN interfaces ..... | 103 | +| A.5.1 | Interface between the HLR and the GLR (GLa-interface)..... | 103 | + +A.5.2 Interface between the VLR and the GLR (GLb-interface) .....103 +A.5.3 Interface between the SGSN and the GLR (GLc-interface) .....103 +A.5.4 Interface between the GLR and the IM\_MSC (GLd-interface) .....103 +A.5.5 Interface between the GLR and the IM\_GSN (GLe-interface).....103 +A.5.6 Interface between the SMS-GMSC and the GLR (GLf-interface) .....104 +A.5.7 Interface between the SMS-GMSC and the IM\_MSC (GLg-interface) .....104 +A.5.8 Interface between the MSC and the IM\_MSC (GLh-interface).....104 +A.5.9 Interface between the GMLC and the IM\_MSC (GLi-interface) .....104 +A.5.10 Interface between the GGSN and the IM\_GSN (GLj-interface).....104 +A.5.11 Interface between the SGSN and the IM\_GSN (GLk-interface) .....104 + +**Annex B (informative): Change history.....105** + +--- + +## Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +## Introduction + +This document presents the possible architectures of the 3GPP System covering both UTRAN and GERAN radio access technologies. In addition, this document also includes the Evolved Packet System providing support for E-UTRAN radio access technology in addition to UTRAN and GERAN radio access technologies. As well as providing support for E-UTRAN, UTRAN and GERAN radio access technologies, the Evolved Packet System also provides support for non-3GPP access technologies making it possible for these technologies to interwork with the 3GPP specified Evolved Packet Core network. The configuration of non-3GPP access networks using EPS is not within the scope of 3GPP specification. + +This document also presents the architecture for the IP Multimedia Subsystem common to 3GPP and other access systems such as Fixed Broadband and those specified by 3GPP2 and provide architecture for interworking and session continuity between IMS and Circuit Switched systems. + +Clause 3 of the document contains the definition of the PLMN entities. + +Clause 4 of the document contains the description of the basic entities of the PLMN, and clause 4a contains the description of the specific entities of the PLMN. + +Clause 5 of the document contains the configuration of the PLMN. + +Clauses 6, 6a and 7 of the document contain the PLMN's basic and specific interfaces and reference points and the PLMN's interfaces towards other networks. + +--- + +# 1 Scope + +This document offers an overview of the 3GPP PLMN and its architectures and configuration. The configuration and the functional entities of the PLMN and the interfaces between them are described on a general level in order to cope with possible implementations. These descriptions include interfaces between and within the core networks, the access networks, the user equipment, different service platforms, different domains and subsystems, and functional entities within domains and subsystems. + +This document covers different architectural aspects with varying level of detail. In general, other specifications shall be referred to for further details; these specifications enable the reader to acquire the full understanding of a system or service feature. + +Note that this document does not cover, or even list, all features of PLMNs. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] [void] +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.016: "International Mobile station Equipment Identities (IMEI)". +- [2a] 3GPP TS 22.060: "General Packet radio Service (GPRS); Service description; Stage 1". +- [2b] 3GPP TS 22.071: "Location Services (LCS); Service description; Stage 1". +- [2c] 3GPP TS 22.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description, Stage 1". +- [3] 3GPP TS 23.003: " Numbering, addressing and identification". +- [4] 3GPP TS 22.127: "Open Service Access (OSA)". +- [5] 3GPP TS 23.008: "Organization of subscriber data". +- [6] 3GPP TS 23.009: "Handover procedures". +- [7] 3GPP TS 23.012: "Location Management Procedures". +- [8] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [9] [void] +- [9a] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [10] [void] +- [10a] 3GPP TS 43.064: "Digital cellular telecommunication system (Phase 2+); General Packet Radio service (GPRS); Overall description of the GPRS radio interface; Stage 2". +- [10b] 3GPP TS 25.305: "Stage 2 Functional Specification of UE Positioning in UTRAN". + +- [10c] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3 - Stage 2". +- [10d] 3GPP TS 43.059: "Functional Stage 2 Description of Location Services in GERAN". +- [11] ITU-T Recommendation Q.1214 (05/1995): "Distributed Functional Plane for Intelligent Network CS-1". +- [11a] 3GPP TS 23.101: "General UMTS Architecture". +- [11b] 3GPP TS 23.110: "UMTS Access Stratum; Services and Functions". +- [12] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration". +- [13] 3GPP TS 48.001: "Base Station System - Mobile-services Switching Centre (BSS - MSC) interface; General aspects". +- [14] 3GPP TS 48.002: "Base Station System - Mobile-services Switching Centre (BSS - MSC) interface; Interface principles". +- [14a] 3GPP TS 25.410: "UTRAN Iu Interface: general aspects and principles". +- [15] 3GPP TS 48.004: "Base Station System - Mobile-services Switching Centre (BSS - MSC) interface Layer 1 specification". +- [16] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [17] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". +- [18] [void] +- [19] 3GPP TS 48.051: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; General aspects". +- [20] 3GPP TS 48.052: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Interface principles". +- [21] 3GPP TS 48.054: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 1 structure of physical circuits". +- [22] 3GPP TS 48.056: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 2 specification". +- [23] 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 3 specification". +- [24] 3GPP TS 48.060: "In-band control of remote transcoders and rate adaptors for full rate traffic channels". +- [25] 3GPP TS 48.061: "In-band control of remote transcoders and rate adaptors for half rate traffic channels". +- [26] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [27] 3GPP TS 22.228: "Service requirements for the IP Multimedia Core Network Subsystem". +- [28] 3GPP TS 23.207: "End-to-end Quality of Service (QoS) concept and architecture". +- [29] [void]. +- [30] [void]. + +- [31] 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)". +- [32] 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)". +- [33] 3GPP TS 29.011: "Signalling interworking for supplementary services". +- [34] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [35] 3GPP TS 41.103: "GSM Release 5 specifications". +- [36] 3GPP TS 43.051: "Technical Specification Group GSM/EDGE Radio Access Network; Overall description, Stage 2". +- [37] 3GPP TS 23.226: "Global Text Telephony (GTT); Stage 2". +- [38] 3GPP TS 26.226: "Cellular Text Telephone Modem; General Description". +- [39] 3GPP TS 23.016:"Subscriber data management; Stage 2". +- [40] 3GPP TS 23.066: "Support of Mobile Number Portability (MNP); Technical realization; Stage 2". +- [41] 3GPP TS 43.068: "Voice Group Call Service (VGCS); Stage 2". +- [42] 3GPP TS 43.069: "Voice Broadcast Service (VBS); Stage 2". +- [43] 3GPP TS 23.205: "Bearer independent circuit switched core network; Stage 2". +- [44] 3GPP TS 48.014: "Base Station System (BSS) – Serving GPRS Support Node (SGSN) interface; Gb interface Layer 1". +- [45] 3GPP TS 48.016: "Base Station System (BSS) – Serving GPRS Support Node (SGSN) interface; Network service". +- [46] 3GPP TS 48.018: "Base Station System (BSS) – Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [47] 3GPP TS 48.031: "Serving Mobile Location Centre – Serving Mobile Location Centre (SMLC – SMLC); SMLCPP specification". +- [48] 3GPP TS 29.016: "Serving GPRS Support Node (SGSN) – Visitor Location Register (VLR); Gs interface network service specification". +- [49] 3GPP TS 29.018: "Serving GPRS Support Node (SGSN) – Visitor Location Register (VLR); Gs interface Layer 3 specification". +- [50] 3GPP TS 49.031: "Network Location Services (LCS); Base Station System Application Part LCS extension (BSSAP-LE)". +- [51] 3GPP TS 29.060: "GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". +- [52] ITU-T Recommendation H.248: "Gateway Control Protocol". +- [53] ITU-T Recommendation E.164: "The International public telecommunication numbering plan". +- [54] ITU-T Recommendation H.323: "Packet-based multimedia communications systems". +- [55] 3GPP TS 44.071: "Mobile radio interface layer 3 Location Services (LCS) specification". +- [56] 3GPP TS 23.271: "Functional stage 2 description of LCS". +- [57] ITU-T Recommendation I.363-2 : "B-ISDN ATM Adaptation Layer (AAL) type 2 specification". +- [58] ITU-T Recommendation H.245: "Control protocol for multimedia communication". + +- [59] IETF RFC 768: "User Datagram Protocol". +- [60] IETF RFC 1889: "RTP: A Transport Protocol for Real-Time Applications". +- [61] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [62] OMA MLP TS: "Mobile Location Protocol", []. +- [63] 3GPP TS 29.198: "Open Service Access (OSA) Application Programming Interface (API)". +- [64] 3GPP TS 33.210: "3G Security; Network Domain Security; IP network layer security". +- [65] 3GPP TS 23.236: "Intra Domain Connection of RAN Nodes to Multiple CN Nodes". +- [66] 3GPP TS 25.453: "UTRAN Iupc interface Positioning Calculation Application Part (PCAP) signalling". +- [67] 3GPP TS 23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking". +- [68] 3GPP TS 23.141: "Presence Service; Architecture and functional description". +- [69] OMA RLP TS: "Roaming Location Protocol", []. +- [70] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description". +- [71] 3GPP TS 23.240: "3GPP Generic User Profile (GUP); Architecture (Stage 2)". +- [72] 3GPP TS 33.222: "Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS)". +- [73] 3GPP TS 23.203: "Policy Control and Charging Architecture (Stage 2)". +- [74] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions". +- [75] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access". +- [76] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [77] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses". +- [78] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [79] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description". +- [80] Open Mobile Alliance, OMA ERP SUPL V2.0: "Secure User Plane Location Enabler Release Package", (). +- [81] 3GPP TS 23.272: "Circuit Switched Fallback in Evolved Packet System; Stage 2". +- [82] 3GPP TS 29.118: "Mobility Management Entity (MME) – Visitors Location Register (VLR) SGs interface specification". +- [83] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2". +- [84] 3GPP TS 33.107: "3G security; Lawful interception architecture and functions". +- [85] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles". +- [86] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [87] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture". + +- [88] 3GPP TS 33.402: "3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses". +- [89] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [90] 3GPP TS 29.274: "General Packet Radio Service (GPRS); Evolved GPRS Tunnelling Protocol (eGTP) for EPS". +- [91] 3GPP TS 29.280: "Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC". +- [92] 3GPP TS 29.213: "PCC Signalling Flows and Mapping Tables". +- [93] 3GPP TS 29.275: "Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3". +- [94] 3GPP TS 24.304: "Mobility management based on Mobile IPv4; User Equipment (UE) - foreign agent interface; Stage 3". +- [95] 3GPP TS 24.303: "Mobility management based on Dual-Stack Mobile IPv6; Stage 3". +- [96] 3GPP TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces". +- [97] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks". +- [98] 3GPP TS 29.168: "Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage 3". +- [99] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [100] 3GPP TS 29.214: "Policy and Charging Control over Rx Interface". +- [101] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging". +- [102] IETF RFC 4006: "Diameter Credit-Control Application". +- [103] 3GPP TS 29.215: "Policy and Charging Control over S9 Interface". +- [104] 3GPP TS 29.061: "Interworking between PLMN supporting packet based services and PDN". +- [105] Void. +- [106] 3GPP2 A.S0008-C: "Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network". +- [107] 3GPP2 C.S0087 0: "E-UTRAN - HRPD and CDMA2000 1x Connectivity and Interworking: Air Interface Aspects". +- [108] 3GPP TS 32.296: "Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces". +- [109] 3GPP TS 32.295: "Telecommunication management; Charging management; Charging Data Record (CDR) transfer". +- [110] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services". +- [111] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity". +- [112] 3GPP TS 23.327: "Mobility between 3GPP-Wireless Local Area Network (WLAN) Interworking and 3GPP Systems". +- [113] 3GPP TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2". +- [114] 3GPP TS 25.467: "UTRAN architecture for 3G Home Node B (HNB); Stage 2". + +- [115] 3GPP TS 25.468: "UTRAN Iuh Interface RANAP User Adaption (RUA) signalling". +- [116] 3GPP TS 25.469: "UTRAN Iuh interface Home Node B (HNB) Application Part (HNBAP) signalling". +- [117] 3GPP TS 24.285: "Allowed Closed Subscriber Group (CSG) List; Management Object (MO)". +- [118] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application". +- [119] 3GPP TS 48.049: "Base Station Controller - Cell Broadcast Centre (BSC-CBC) Interface Specification; Cell Broadcast Service Protocol (CBSP)". +- [120] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows; Stage 2". +- [121] 3GPP TS 29.335: "User Data Convergence (UDC); User Data Repository Access Protocol over the Ud interface; Stage 3". +- [122] 3GPP TS 36.305: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN". +- [123] 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". +- [124] 3GPP TS 29.171: "Location Services (LCS); LCS Application Protocol (LCS-AP) between the Mobile Management Entity (MME) and Evolved Serving Mobile Location Centre (E-SMLC); SLs interface". +- [125] 3GPP TS 29.173: "Location Services (LCS); Diameter-based SLh interface for Control Plane LCS". +- [126] 3GPP TS 29.281: "GPRS Tunnelling Protocol User Plane (GTPv1-U)". +- [127] 3GPP TS 36.443: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M2 Application Protocol (M2AP)". +- [128] 3GPP TS 36.444: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M3 Application Protocol (M3AP)". +- [129] 3GPP TS 36.445: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M1 data transport". +- [130] 3GPP TS 22.220: "Service Requirements for Home NodeBs and Home eNodeBs". +- [131] 3GPP TS 29.219: "Policy and charging control: Spending limit reporting over Sy reference point". +- [132] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [133] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications". +- [134] 3GPP TS 29.337: "Diameter based T4 Interface for communications with packet data networks and applications". +- [135] 3GPP TS 29.338: "Diameter based protocols to support of SMS capable MMEs". +- [136] 3GPP TS 29.368: "Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS)". +- [137] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". + +--- + +## 3 Definitions and abbreviations + +In addition to the abbreviations given in the remainder of this clause others are listed in TR 21.905 [1a]. + +The definitions of the entities of the mobile system are given in the next clause. + +### 3.1 Public Land Mobile Network (PLMN) + +A Public Land Mobile Network (PLMN) is established and operated by an administration or Recognized Private Operating Agency (RPOA) for the specific purpose of providing land mobile telecommunications service services to the public. A PLMN may be regarded as an extension of networks (e.g. ISDN, corporate and public PDNs, etc.); it is a collection of MSCs areas in CS domain and SGSN or MME areas for EPC in PS domain within a common numbering plan (e.g. same National Destination Code) and a common routing plan. The MSCs are the functional interfaces between the fixed networks and a PLMN for call set-up in CS domain. The GGSN and the SGSN are the functional interfaces between the fixed networks and a PLMN for packet transmission in GPRS PS domain. In case of EPC PS Domain, the PDN GW, Serving-GW and the SGSN and the MME are the functional interfaces between the fixed networks and a PLMN for packet transmission. + +Functionally the PLMNs may be regarded as independent telecommunications entities even though different PLMNs may be interconnected through the ISDN/PSTN and PDNs for forwarding of calls or network information. A similar type of interconnection may exist for the interaction between the MSCs/SGSNs/MMEs of one PLMN. + +### 3.2 Core Network (CN) and Access Network (AN) + +The PLMN infrastructure is logically divided into a Core Network (CN) and an Access Network (AN) infrastructures, as defined in TS 23.101 [11a] and TS 23.110 [11b]. The CN is logically divided into a CS domain, a PS domain and an IM subsystem, as defined in next clause. The AN are GERAN (also called BSS for GSM), UTRAN (also called RNS), E-UTRAN, as defined in clause "The Access Network". + +### 3.3 Circuit Switched (CS) and Packet Switched (PS) Domains + +The CN is constituted of a Circuit Switched (CS) domain and a Packet Switched (PS) domain (which includes GPRS and EPC). These two domains differ by the way they support user traffic, as explained below. + +These two domains are overlapping, i.e. they contain some common entities. A PLMN can implement only one domain or both domains. + +#### 3.3.1 CS Domain + +The CS domain refers to the set of all the CN entities offering "CS type of connection" for user traffic as well as all the entities supporting the related signalling. A "CS type of connection" is a connection for which dedicated network resources are allocated at the connection establishment and released at the connection release. + +The entities specific to the CS domain are: MSC, GMSC, VLR. All the other CN entities defined in clause 4 "The basic entities of the mobile system" and not defined as PS domain specific entities (see following clause) are common to the CS and to the PS domains. In case of E-UTRAN access, there is no support for CS Domain. + +#### 3.3.2 PS Domain + +The PS domain refers to the set of all the CN entities offering "PS type of connection" for user traffic as well as all the entities supporting the related signalling. A "PS type of connection" transports the user information using autonomous concatenation of bits called packets: each packet can be routed independently from the previous one. + +The entities specific to the PS domain are the GPRS specific entities, i.e. SGSN and GGSN and EPS specific entities, i.e. PDN GW, S-GW, MME, SGSN. All the other CN entities defined in clause "4 The basic entities of the mobile system" and not defined as CS domain specific entities (see previous clause) are common to the CS and to the PS domains. + +### 3.3a IP Multimedia subsystem (IMS) + +The IM subsystem comprises all CN elements for provision of IP multimedia services comprising audio, video, text, chat, etc. and a combination of them delivered over the PS domain. The entities related to IMS are CSCF, MGCF, MRF, etc. as defined in the stage 2 of the IM subsystem TS 23.228 [34]. See TS 22.228 [27] for some service examples of IMS. + +### 3.4 Location register + +To enable communication to a mobile station the network must know where this mobile station is located. This information is stored in a function named location register. + +The location register is handled by the following entities. + +- The Home Location Register (HLR). + +The Home Location Register (HLR) is the location register to which a mobile subscriber is assigned for record purposes such as subscriber information. For EPS, the HLR functionality is provided via HSS. + +- The Visitor Location Register (VLR). + +The Visitor Location Register (VLR) is the location register for Circuit Switched (CS) services, other than the HLR, used by an MSC to retrieve information for, e.g. handling of calls to or from a roaming mobile station currently located in its area. + +- The Serving GPRS Support Node (SGSN). + +The location register function in the SGSN stores subscription information and location information for Packet Switched (PS) services for each subscriber registered in the SGSN. + +The SGSN is needed only in a PLMN which supports PS Domain with GERAN or UTRAN access. + +- The Gateway GPRS Support Node (GGSN). + +The location register function in the GGSN stores subscriber information and routing information (needed to tunnel packet data traffic destined for a GPRS MS to the SGSN where the MS is registered) for each subscriber for which the GGSN has at least one PDP context active. + +The GGSN is needed only in a PLMN which supports GPRS with GERAN or UTRAN access. + +- The Mobility Management Entity (MME). + +The location register function in the MME stores subscription information and location information for Packet Switched (PS) services for each subscriber registered in the MME for EPS. + +- The Packet Data Network Gateway (PDN GW). + +The location register function in the PDN GW stores subscriber information and routing information (needed to tunnel packet data traffic destined for an EPS UE to the Serving GW, where the UE is registered in the MME, in the SGSN or in the 3GPP AAA server in case of non-3GPP access) for each subscriber for which the PDN GW has at least one PDN connection active. + +### 3.5 Cell + +The cell is an area of radio coverage identified by a Base station identification as defined in TS 23.003 [3]. + +### 3.6 Base Station Controller (BSC) area + +The Base Station Controller (BSC) area is an area of radio coverage consisting of one or more cells controlled by one BSC. The boundaries of a BSC area and a location area are independent; a location area may span the boundary between BSC area and a BSC area may span the boundary between location areas. + +## 3.7 Radio Network Controller (RNC) area + +The Radio Network Controller (RNC) area is an area of radio coverage consisting of one or more cells controlled by one RNC. The boundaries of a RNC area and a location area are independent; a location area may span the boundary between RNC area and a RNC area may span the boundary between location areas. + +## 3.8 Location Area (LA) + +The Location Area (LA) is defined as an area in which a mobile station may move freely without updating the VLR. A location area includes one or several GERAN/UTRAN cells. + +## 3.9 Routing Area (RA) + +The Routing Area (RA) is defined as an area in which a mobile station, in certain operation modes, may move freely without updating the SGSN. A routing area includes one or several GERAN/UTRAN cells. A RA is always contained within a location area. + +## 3.9a Tracking Area (TA) + +A Tracking Area (TA) includes one or several E-UTRAN cells. The network allocates a list with one or more TAs to the UE . In certain operation modes, the UE may move freely in all TAs of the list without updating the MME. + +## 3.10 MSC area + +The MSC area is the part of the network covered by an MSC. An MSC area may consist of one or several location areas. An MSC area may also consist of one or several BSC areas. + +## 3.11 VLR area + +The VLR area is the part of the network controlled by a VLR. A VLR area may consist of one or several MSC areas. + +## 3.12 SGSN area + +The SGSN area is the part of the network served by an SGSN. An SGSN area may consist of one or several routing areas. An SGSN area may also consist of one or several BSC areas. There need not be a one to one relationship between SGSN area and MSC/VLR area. + +## 3.13 Zones for Regional Subscription + +A PLMN operator may define a number of regional subscription areas, each of which is a subset of the service area for an unrestricted mobile subscriber. A regional subscription area may be contained within the service area of a single PLMN, or may lie within the service areas of two or more PLMNs. Each regional subscription area consists of one or more zones; each zone is contained within the service area of a PLMN. + +The definition of a mobile subscriber's regional subscription area is stored within the HLR/HSS per National Destination Code(s) (NDC) of a PLMN and is transferred to the VLRs and/or SGSNs/MMEs of that PLMN. The VLR and/or SGSN/MME evaluates this information to extract the restricted or accessible MSC and/or SGSN/MME areas and location areas to which the mobile subscriber is allowed to roam. The VLR and/or SGSN/MME inform the HLR/HSS if an entire MSC and/or SGSN/MME area is restricted. + +Zones for Regional Subscription and their handling are defined in TS 23.003 [3], TS 23.008 [5] and TS 29.002 [26] and TS 29.272 [86] for EPC. + +## 3.14 Service area + +The service area is defined as an area in which a mobile subscriber can be reached by another (mobile or fixed) subscriber without the subscriber's knowledge of the actual location of the mobile station within the area. A service area may consist of several PLMNs. One service area may consist of one country, be a part of a country or include several countries. The location registration system associated with each service area must thus contain a list of all mobile stations located within that service area. + +## 3.15 Group call area + +The group call area is a predefined area composed of one or a number of cells to which a particular Voice Group Call Service (VGCS) or Voice Broadcast Service (VBS) call is distributed. The composition of a group call area is predefined in the network. The group call area may include cells of more than one MSC area and cells of more than one PLMN. + +## 3.15a MME Area + +The MME area is the part of the network served by an MME. An MME area consists of one or several Tracking Areas. All cells served by an eNodeB are included in an MME Area. There is no one to one relationship between an MME Area and an MSC/VLR area. Multiple MMEs may have the same MME Area as described in clause "Pool-area". MME Areas may overlap each other. + +## 3.16 Pool-area + +A pool area is an area where Intra Domain Connection of RAN Nodes to Multiple CN Nodes is applied. Within a pool-area an MS may roam without need to change the serving Core Network (CN) node. A pool-area is served by one or more CN nodes in parallel. + +## 3.17 Serving GW Service Area + +A Serving GW Service Area is the part of the network served by single Serving GW. Serving GW Service Areas consist of one or several complete Tracking Areas. All cells served by an eNodeB are included in an Serving GW Service Area .Serving GW Service Areas may overlap each other. There is no one to one relationship between an MME Area and a Serving GW Service Area. + +--- + +# 4 The basic entities of the mobile system + +To provide the mobile service as it is defined, it is necessary to introduce some specific functions. These functional entities can be implemented in different equipments or gathered. In any case, exchanges of data occur between these entities. + +Entities in the mobile system can be either implemented in a monolithic way where user data are stored within the entity itself (or in an external entity via non standard interfaces) or according to the User Data Convergence (UDC) concept (see TS 23.335 [120]) where the entity becomes a so-called user-dataless Application Front End (AFE). Application Front Ends access, via the Ud reference point, a User Data Repository (UDR), which stores the relevant user data managed by the applications. Unless explicitly stated otherwise, this document describes entities in its monolithic form, e.g. stating that user data are stored in the HSS. If however the UDC concept applies, user data are actually stored in the UDR and managed by one or several Application Front Ends, so that user data may be shared among the different Application Front Ends, allowing several AFEs of the same application type (e.g. HSS) to serve the same user at any given time. + +## 4.1 The Core Network (CN) entities + +### 4.1.1 Entities common to the PS and CS domains + +#### 4.1.1.1 The Home Subscriber Server (HSS) + +The HSS is the master database for a given user. It is the entity containing the subscription-related information to support the network entities actually handling calls/sessions. + +A Home Network may contain one or several HSSs: it depends on the number of mobile subscribers, on the capacity of the equipment and on the organisation of the network. + +As an example, the HSS provides support to the call control servers in order to complete the routing/roaming procedures by solving authentication, authorisation, naming/addressing resolution, location dependencies, etc. + +The HSS is responsible for holding the following user related information: + +- User Identification, Numbering and addressing information; +- User Security information: Network access control information for authentication and authorization; +- User Location information at inter-system level: the HSS supports the user registration, and stores inter-system location information, etc.; +- User profile information. + +The HSS also generates User Security information for mutual authentication, communication integrity check and ciphering. + +Based on this information, the HSS also is responsible to support the call control and session management entities of the different Domains and Subsystems (defined in section 3.3 and 3.3a) of the operator as shown in figure 0-a. + +![Figure 0-a: Example of a Generic HSS structure and basic interfaces. The diagram shows the HSS (Home Subscriber Server) at the top, containing 'Subscription information', 'Location information', and other data (indicated by dots). Below the HSS are several network entities connected via interfaces: AS (Application Server) via Sh; MSC Server via D; GMSC Server via C; SGSN via Gr/S6d; GGSN via Gc; CSCF via Cx; and MME via S6a.](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +``` + +graph TD + HSS((HSS)) --- Sh[Sh] --- AS[AS] + HSS --- D[D] --- MSCServer[MSC Server] + HSS --- C[C] --- GMSCServer[GMSC Server] + HSS --- GrS6d[Gr/S6d] --- SGSN[SGSN] + HSS --- Gc[Gc] --- GGSN[GGSN] + HSS --- Cx[Cx] --- CSCF[CSCF] + HSS --- S6a[S6a] --- MME[MME] + subgraph HSS + SI[Subscription information] + LI[Location information] + Dots[.....] + end + +``` + +Figure 0-a: Example of a Generic HSS structure and basic interfaces. The diagram shows the HSS (Home Subscriber Server) at the top, containing 'Subscription information', 'Location information', and other data (indicated by dots). Below the HSS are several network entities connected via interfaces: AS (Application Server) via Sh; MSC Server via D; GMSC Server via C; SGSN via Gr/S6d; GGSN via Gc; CSCF via Cx; and MME via S6a. + +**Figure 0-a: Example of a Generic HSS structure and basic interfaces** + +The HSS may integrate heterogeneous information, and enable enhanced features in the core network to be offered to the application & services domain, at the same time hiding the heterogeneity. + +The HSS consists of the following functionalities: + +- IP multimedia functionality to provide support to control functions of the IM subsystem such as the CSCF. It is needed to enable subscriber usage of the IM CN subsystem services. This IP multimedia functionality is independent of the access network used to access the IM CN subsystem. +- The subset of the HLR/AUC functionality required by the PS Domain (GPRS and EPC). +- The subset of the HLR/AUC functionality required by the CS Domain, if it is desired to enable subscriber access to the CS Domain or to support roaming to legacy GSM/UMTS CS Domain networks. + +The organisation of the subscriber data is outlined in TS 23.008 [5]. It also indicates which numbers, addresses and identifiers specified in TS 23.003 [3] are stored in HSS. + +#### 4.1.1.1.1 The Home Location Register (HLR) + +The HLR is shown in the Reference Architecture up to and including Rel-4. + +The HLR can be considered a subset of the HSS that holds the following functionality: + +- The functionality required to provide support to PS Domain entities such as the SGSN, MME and GGSN, through the Gr, S6a, S6d and Gc interfaces and the 3GPP AAA Server for EPS in case of non-3GPP access via SWx and for the I-WLAN through the D'/Gr' interface. It is needed to enable subscriber access to the PS Domain services. +- The functionality required to provide support to CS Domain entities such as the MSC/MSC server and GMSC/GMSC server, through the C and D interfaces. It is needed to enable subscriber access to the CS Domain services and to support roaming to legacy GSM/UMTS CS Domain networks. + +#### 4.1.1.1.2 The Authentication Centre (AuC) + +The AuC is shown in the Reference Architecture up to and including Rel-4. + +The AuC can be considered a subset of the HSS that holds the following functionality for the CS Domain and PS Domain: + +- The AuC is associated with an HLR and stores an identity key for each mobile subscriber registered with the associated HLR. This key is used to generate security data for each mobile subscriber: + - data which are used for mutual authentication of the International Mobile Subscriber Identity (IMSI) and the network; + - a key used to check the integrity of the communication over the radio path between the mobile station and the network; + - a key used to cipher communication over the radio path between the mobile station and the network. +- The AuC communicates only with its associated HLR over a non-standardised interface denoted the H-interface. The HLR requests the data needed for authentication and ciphering from the AuC via the H-interface, stores them and delivers them to the VLR and SGSN and MME which need them to perform the security functions for a mobile station. + +#### 4.1.1.1.3 HSS logical functions + +This section provides a high level and not exhaustive description of HSS functionality. + +![Diagram of HSS logical functions and network architecture. The HSS box contains Mobility Management, User security info. generation, User security support, Service Provisioning support, Call / Session establishment support, GUP Data Repository, Identification handling, Service authorization support, Access authorization, Application Services Support, and CAMEL Services Support. Below the HSS, the CS Domain includes GMSC, MSC/VLR, and gsmSCF. The PS Domain includes SGSN, MME, GGSN, and GPRS. The IM CN subsystem includes SIP Application Server, OSA SCS, IM-SSF, and CSCF. Interfaces shown include SWx, C, D, S6d, S6a, Gr, Gc, Rp, Sh, Si, and Cx. Other components include EPC, 3GPP AAA Server, Applications, and GUP Server.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +Diagram of HSS logical functions and network architecture. The HSS box contains Mobility Management, User security info. generation, User security support, Service Provisioning support, Call / Session establishment support, GUP Data Repository, Identification handling, Service authorization support, Access authorization, Application Services Support, and CAMEL Services Support. Below the HSS, the CS Domain includes GMSC, MSC/VLR, and gsmSCF. The PS Domain includes SGSN, MME, GGSN, and GPRS. The IM CN subsystem includes SIP Application Server, OSA SCS, IM-SSF, and CSCF. Interfaces shown include SWx, C, D, S6d, S6a, Gr, Gc, Rp, Sh, Si, and Cx. Other components include EPC, 3GPP AAA Server, Applications, and GUP Server. + +**Figure 0.b: HSS logical functions** + +- Mobility Management + +This function supports the user mobility through CS Domain, PS Domain and IM CN subsystem. + +- Call and/or session establishment support + +The HSS supports the call and/or session establishment procedures in CS Domain, PS Domain and IM CN subsystem. For terminating traffic, it provides information on which call and/or session control entity currently hosts the user. + +- User security information generation + +- The HSS generates user authentication, integrity and ciphering data for the CS and PS Domains and for the IM CN subsystem. User security support + +The HSS supports the authentication procedures to access CS Domain, PS Domain and IM CN subsystem services by storing the generated data for authentication, integrity and ciphering and by providing these data to the appropriate entity in the CN (i.e. MSC/VLR, SGSN, MME, 3GPP AAA Server or CSCF). + +- User identification handling + +The HSS provides the appropriate relations among all the identifiers uniquely determining the user in the system: CS Domain, PS Domain and IM CN subsystem (e.g. IMSI and MSISDNs for CS Domain; IMSI, MSISDNs and IP addresses for PS Domain, private identity and public identities for IM CN subsystem). + +- Access authorisation + +The HSS authorises the user for mobile access when requested by the MSC/VLR, SGSN, MME, 3GPP AAA Server or CSCF, by checking that the user is allowed to roam to that visited network. + +- Service authorisation support + +The HSS provides basic authorisation for MT call/session establishment and service invocation. Besides, the HSS updates the appropriate serving entities (i.e., MSC/VLR, SGSN, MME, 3GPP AAA Server, CSCF) with the relevant information related to the services to be provided to the user. + +- Service Provisioning Support + +- The HSS provides access to the service profile data for use within the CS Domain, PS Domain and/or IM CN subsystem. Application Services and CAMEL Services Support (for GERAN and UTRAN access). + +The HSS communicates with the SIP Application Server and the OSA-SCS to support Application Services in the IM CN subsystem. It communicates with the IM-SSF to support the CAMEL Services related to the IM CN subsystem. It communicates with the gsmSCF to support CAMEL Services in the CS Domain and GPRS PS Domain (for GERAN and UTRAN access). + +**Editor's Note: CAMEL support for GERAN/UTRAN via EPS (i.e. for S4 SGSN) is FFS.** + +- GUP Data Repository + +The HSS supports the storage of IM CN Subsystem user related data, and provides access to these data through the Rp reference point as described in TS 23.240 [71]. + +#### 4.1.1.2 The Visitor Location Register (VLR) + +A mobile station roaming in an MSC area or within a GERAN/UTRAN pool-area is controlled by a Visitor Location Register. When a Mobile Station (MS) enters a new location area it starts a registration procedure. An MSC in charge of that area notices this registration and transfers to a Visitor Location Register the identity of the location area where the MS is situated. If this MS is not yet registered in the VLR, the VLR and the HLR exchange information to allow the proper handling of CS calls involving the MS. + +A VLR may be in charge of one or several MSC areas. + +The VLR contains also the information needed to handle the calls set-up or received by the MSs registered in its data base (for some supplementary services the VLR may have to obtain additional information from the HLR). The following elements are included: + +- the International Mobile Subscriber Identity (IMSI); +- the Mobile Station International ISDN number (MSISDN); + +- the Mobile Station Roaming Number (MSRN), see TS 23.003 [3] for allocation principles; +- the Temporary Mobile Station Identity (TMSI), if applicable; +- the Local Mobile Station Identity (LMSI), if used; +- the location area where the mobile station has been registered; +- the identity of the SGSN where the MS has been registered. Only applicable to PLMNs supporting GPRS and which have a Gs interface between MSC/VLR and SGSN; +- the last known location and the initial location of the MS; +- the identity of the MME where the MS has been registered. Only applicable to PLMNs supporting EPC and CS Fallback and which have a SGs interface between MSC/VLR and MME. + +The VLR also contains supplementary service parameters attached to the mobile subscriber and received from the HLR. The organisation of the subscriber data is outlined in TS 23.008 [5]. + +#### 4.1.1.3 (void) + +#### 4.1.1.4 The Equipment Identity Register (EIR) + +The Equipment Identity Register (EIR) in the GSM system is the logical entity which is responsible for storing in the network the International Mobile Equipment Identities (IMEIs), used in the GERAN/UTRAN/E-UTRAN system. + +The equipment is classified as "white listed", "grey listed", "black listed" or it may be unknown as specified in TS 22.016 [2] and TS 29.002 [26]. + +This functional entity contains one or several databases which store(s) the IMEIs used in the system. + +The mobile equipment may be classified as "white listed", "grey listed" and "black listed" and therefore may be stored in three separate lists. + +An IMEI may also be unknown to the EIR. + +An EIR shall as a minimum contain a "white list" (Equipment classified as "white listed"). + +See also TS 22.016 [2] on IMEI. + +#### 4.1.1.5 SMS Gateway MSC (SMS-GMSC) + +The SMS Gateway MSC (SMS-GMSC) acts as an interface between a Short Message Service Centre and the PLMN, to allow short messages to be delivered to mobile stations from the Service Centre (SC). + +The choice of which MSCs can act as SMS Gateway MSCs is a network operator matter (e.g. all MSCs or some designated MSCs). + +#### 4.1.1.6 SMS Interworking MSC (SMS-IWMSC) + +The SMS Interworking MSC acts as an interface between the PLMN and a Short Message Service Centre (SC) to allow short messages to be submitted from Mobile Stations to the SC. + +The choice of which MSCs can act as SMS Interworking MSCs is a network operator matter (e.g. all MSCs or some designated MSCs). + +#### 4.1.1.7 Subscription Locator Function (SLF) + +The SLF: + +- Is queried by the I-CSCF during the Registration and Session Setup to get the name of the HSS containing the required subscriber specific data. Furthermore the SLF is also queried by the S-CSCF during the Registration. +- Is queried by the AS in conjunction with the Sh interface operation to get the name of the HSS containing the required subscriber specific data. + +- Is queried by the 3GPP AAA server to get the name of the HSS containing the required subscriber specific data. +- Is accessed via the Dx interface by the CSCF, via the Dh interface by the AS, and via the Dw interface by the 3GPP AAA Server. + +The SLF is not required in a single HSS environment. An example for a single HSS environment is a server farm architecture. Use of SLF is not required when AS are configured/managed to use pre-defined HSS. + +## 4.1.2 Entities of the CS domain + +### 4.1.2.1 The Mobile-services Switching Centre (MSC) + +The Mobile-services Switching Centre (MSC) constitutes the interface between the radio system and the fixed networks. The MSC performs all necessary functions in order to handle the circuit switched services to and from the mobile stations. + +In order to obtain radio coverage of a given geographical area, a number of BSS and/or RNS are normally required; i.e. each MSC would thus have to interface to one or more BSS(s) and/or RNS(s). In addition several MSCs may be required to cover a country. + +When Intra Domain Connection of RAN Nodes to Multiple CN Nodes is applied, all the MSCs serving a pool-area share the responsibility to serve the MSs located in the pool-area. All these MSCs interface to all the BSS(s) and/or RNS(s) forming the pool-area. + +The Mobile-services Switching Centre is an exchange, which performs all the switching and signalling functions for mobile stations located in a geographical area designated as the MSC area. When Intra Domain Connection of RAN Nodes to Multiple CN Nodes is applied, one or more MSCs serve a pool-area, but each individual MS is served by only one out of these MSCs, as described in TS 23.236 [65]. The main difference between a MSC and an exchange in a fixed network is that the MSC has to take into account the impact of the allocation of radio resources and the mobile nature of the subscribers and has to perform in addition, at least the following procedures: + +- procedures required for the location registration (see TS 23.012 [7]); +- procedures required for handover (see TS 23.009 [6]). + +NOTE: When this improves the readability (e.g. when dealing with inter-releases handover), the term 2G-MSC can be used to refer to an MSC Release 98 or prior, and the term 3G-MSC can be used to refer to an MSC Release 99 or later. + +When needed, the MSC can be implemented in two different entities: the MSC Server, handling only signalling, and the CS-MGW, handling user's data. A MSC Server and a CS-MGW make up the full functionality of a MSC. + +The CS fallback enabled MSC supports the following additional functions according to TS 23.272 [81]: + +- Maintaining SGs association towards MME for EPS/IMSI attached UE; +- Supporting SMS procedures according to CS Fallback. + +#### 4.1.2.1.1 MSC Server + +The MSC Server mainly comprises the call control (CC) and mobility control parts of a MSC. + +The MSC Server is responsible for the control of mobile originated and mobile terminated CC CS Domain calls. It terminates the user-network signalling and translates it into the relevant network – network signalling. The MSC Server also contains a VLR to hold the mobile subscriber's service data and CAMEL related data. + +The MSC Server controls the parts of the call state that pertain to connection control for media channels in a CS-MGW. + +An MSC Server which has been enhanced for SRVCC provides the following functions as needed for support of SRVCC according to TS 23.216 [83]: + +- Handling the Relocation Preparation procedure requested for the voice component from MME via Sv interface; +- Invoking the session transfer procedure from IMS to CS ; +- Coordinating the CS Handover and session transfer procedures; + +- Handling the MAP\_Update\_Location procedure without it being triggered from the UE. + +If a MSC Server is enhanced for IMS Centralized Services (as defined in TS 23.292 [110]), it is responsible for the CS to IMS interworking, and it terminates the user-network signalling received over the CS access (A/Iu and E interface) and translates it into SIP signalling in IMS and vice versa. + +#### 4.1.2.1.2 Circuit Switched - Media Gateway Function (CS-MGW) + +**NOTE:** In this document the term Media Gateway Function (MGW) is used when there is no need to differentiate between the CS domain entity and the IP Multimedia CN Subsystem entity. When referring specifically to the CS domain entity the term CS-MGW is used. When referring specifically to the IP Multimedia CN Subsystem entity, the term IMS-MGW is used. + +This component is PSTN/PLMN transport termination point for a defined network and interfaces UTRAN with the core network over Iu. + +A CS-MGW may terminate bearer channels from a switched circuit network and media streams from a packet network (e.g. RTP streams in an IP network). Over Iu, the CS-MGW may support media conversion, bearer control and payload processing (e.g. codec, echo canceller, conference bridge) for support of different Iu options for CS services (AAL2/ATM based as well as RTP/UDP/IP based). + +The CS-MGW: + +- Interacts with MGCF, MSC server and GMSC server for resource control. +- Owns and handles resources such as echo cancellers etc. +- May need to have Codecs. + +The CS-MGW will be provisioned with the necessary resources for supporting UMTS/GSM transport media. Further tailoring (i.e. packages) of the H.248 [52] may be required to support additional Codecs and framing protocols, etc. + +The CS-MGW bearer control and payload processing capabilities will also need to support mobile specific functions such as SRNS relocation/handover and anchoring. It is expected that current H.248 [52] standard mechanisms can be applied to enable this. + +#### 4.1.2.2 The Gateway MSC (GMSC) + +If a network delivering a call to the PLMN cannot interrogate the HLR, the call is routed to an MSC. This MSC will interrogate the appropriate HLR and then route the call to the MSC where the mobile station is located. The MSC which performs the routing function to the actual location of the MS is called the Gateway MSC (GMSC). + +The acceptance of an interrogation to an HLR is the decision of the operator. + +The choice of which MSCs can act as Gateway MSCs is for the operator to decide (i.e. all MSCs or some designated MSCs). + +If the call is a voice group/broadcast call, it is routed directly from the GMSC to the VBS/VGCS Anchor MSC, based on information (VBS/VGCS call reference) contained in the dialled number (see also TS 43.068 [41] and TS 43.069 [42]). + +**Editor's note:** There is a need to consider possibilities that call incoming to the PLMN may be routed to entities other than the GMSC, e.g., for networks that do not deploy CS domain. + +When needed, the GMSC can be implemented in two different entities: the GMSC Server, handling only signalling, as defined below, and the CS-MGW, defined above. A GMSC Server and a CS-MGW make up the full functionality of a GMSC. + +#### 4.1.2.2.1 Gateway MSC Server (GMSC Server) + +The GMSC server mainly comprises the call control and mobility control parts of a GMSC. + +#### 4.1.2.3 The Interworking Function (IWF) + +The Interworking Function (IWF) is a functional entity associated with the MSC. The IWF provides the functionality necessary to allow interworking between a PLMN and the fixed networks (ISDN, PSTN and PDNs). The functions of + +the IWF depend on the services and the type of fixed network. The IWF is required to convert the protocols used in the PLMN to those used in the appropriate fixed network. The IWF may have no functionality where the service implementation in the PLMN is directly compatible with that at the fixed network. The interworking functions are described in TS 29.007 [31]. + +### 4.1.3 Entities of the GPRS PS domain + +The UTRAN/GERAN PS-domain (or GPRS) Support Nodes (GSN) are the Gateway GSN (GGSN) and the Serving GSN (SGSN). They constitute the interface between the radio system and the fixed networks for packet switched services. The GSN performs all necessary functions in order to handle the packet transmission to and from the mobile stations. + +#### 4.1.3.1 Serving GPRS Support Node (SGSN) + +The location register function in the SGSN stores two types of subscriber data needed to handle originating and terminating packet data transfer: + +- subscription information: + - the IMSI; + - one or more temporary identities; + - zero or more PDP addresses. +- location information: + - depending on the operating mode of the MS, the cell or the routing area where the MS is registered; + - the VLR number of the associated VLR (if the Gs interface is implemented); + - the GGSN address of each GGSN for which an active PDP context exists. + +The SGSN provide support for Direct Tunnel functions as specified in TS 23.060 [9a]. + +The organisation of the subscriber data in the SGSN is defined in TS 23.008 [5] and TS 23.060 [9a]. + +The procedures for information transfer between the SGSN, the GGSN, the VLR and the HLR are defined in TS 23.016 [39] and TS 23.060 [9a]. + +NOTE: When this improves the readability (e.g. when dealing with inter-releases handover), the term 2G-SGSN can be used to refer to a SGSN Release 98 or prior, and the term 3G-SGSN can be used to refer to a SGSN Release 99 or later. + +The SGSN provides support for SRVCC functions as specified in TS 23.216 [83]. + +#### 4.1.3.2 Gateway GPRS Support Node (GGSN) + +The location register function in the GGSN stores subscriber data received from the HLR and the SGSN. There are two types of subscriber data needed to handle originating and terminating packet data transfer: + +- subscription information: + - the IMSI; + - zero or more PDP addresses. +- location information: + - the SGSN address for the SGSN where the MS is registered. + +The organisation of the subscriber data in the GGSN is defined in TS 23.008 [5] and TS 23.060 [9a]. + +The procedures for information transfer between the GGSN, the SGSN and the HLR are defined in TS 23.016 [39] and TS 23.060 [9a]. + +#### 4.1.3.3 Void + +### 4.1.4 Entities of the EPC PS Domain + +#### 4.1.4.1 MME + +MME is the control plane entity within EPS supporting functions as listed below. For detailed functional role of MME, see specifications TS 23.401 [76], TS 23.402 [77] and TS 36.300 [78]. + +Mobility Management, + +- NAS signalling and security; +- Inter CN node signalling for mobility between 3GPP access networks; +- Tracking Area list management; +- PDN GW and Serving GW selection; +- SGSN selection for handovers to 2G or 3G 3GPP access networks; +- Roaming ; +- Authentication; +- Bearer management functions including dedicated bearer establishment. +- Lawful Interception of signalling traffic. + +In order to support 3GPP2 access, MME supports: + +- HRPD access node selection and maintenance for handovers to HRPD; +- Transparent transfer of HRPD signalling messages and transfer of status information between E-UTRAN and HRPD access; + +The procedures for information transfer between the SGSN, the MME and the HSS are defined in TS 23.401 [76] and TS 23.060 [9a]. + +The CS fallback enabled MME supports the following additional functions according to TS 23.272 [81]: + +- Deriving a VLR number and LAI out of the TAI +- Maintaining of SGs association towards MSC/VLR for EPS/IMSI attached UE +- Initiating IMSI detach at EPS detach +- Initiating paging procedure towards eNodeB when MSC pages the UE for CS services +- Supporting SMS procedures for CS Fallback. +- Support CS Fallback interface and related functions for 1xRTT CDMA access. + +When the MME supports the interworking to 3GPP CS, the MME supports the following functions as specified in TS 23.216 [83]: + +- Performing the PS bearer splitting function by separating the voice PS bearer from the non-voice PS bearers. +- Handling the non-voice PS bearers handover with the target cell as according to Inter RAT handover procedure as defined in TS 23.401 [76]. +- Initiating the SRVCC handover procedure for handover of the voice component to the target cell. +- Coordinating PS handover and SRVCC handover procedures when both procedures are performed, +- support interworking and SRVCC related functions for 1xRTT CDMA access. + +#### 4.1.4.2 Gateways + +##### 4.1.4.2.1. Serving GW + +The Serving GW is the gateway which terminates the interface towards E-UTRAN. + +For each UE associated with the EPS, at a given point of time, there is a single Serving GW. For detailed S-GW functions, see TS 23.401 [76] and TS 23.402 [77]. + +Connectivity to a GGSN is not supported. + +The functions of the Serving GW include: + +- the local Mobility Anchor point for inter-eNodeB handover; +- Mobility anchoring for inter-3GPP mobility; +- ECM-IDLE mode downlink packet buffering and initiation of network triggered service request procedure; +- Lawful Interception; +- Packet routing and forwarding; +- Transport level packet marking in the uplink and the downlink; +Accounting on user and QCI granularity for inter-operator charging; +- A local non-3GPP anchor for the case of roaming when the non-3GPP IP accesses connected to the VPLMN; +- Event reporting (change of RAT, etc.) to the PCRF; +- Uplink and downlink bearer binding towards 3GPP accesses as defined in TS 23.203 [73]; +- Uplink bearer binding verification with packet dropping of "misbehaving UL traffic"; +- Mobile Access Gateway (MAG) functions if PMIP-based S5 or S8 is used; +- Support necessary functions in order for enabling GTP/PMIP chaining functions. + +##### 4.1.4.2.2 PDN GW + +The PDN GW is the gateway which terminates the SGi interface towards the PDN. + +If a UE is accessing multiple PDNs, there may be more than one PDN GW for that UE, however a mix of S5/S8 connectivity and Gn/Gp connectivity is not supported for that UE simultaneously. + +The PDN GW provides PDN connectivity to both GERAN/UTRAN only UEs and E-UTRAN capable UEs using any of E-UTRAN, GERAN or UTRAN. The PDN GW provides PDN connectivity to E-UTRAN capable UEs using E-UTRAN only over the S5/S8 interface. The PDN GW may also provide PDN connectivity to UEs using non-3GPP access networks with the procedures defined in TS 23.402 [77]. + +For detailed PDN GW functions, see TS 23.401 [76] and TS 23.402 [77]. + +PDN GW functions include: + +- Per-user based packet filtering (by e.g. deep packet inspection); +- Lawful Interception; +- UE IP address allocation; +- Transport level packet marking in the uplink and downlink, e.g. setting the DiffServ Code Point, based on the QCI of the associated EPS bearer; +- UL and DL service level charging, gating control, rate enforcement as defined in TS 23.203 [73]; +- UL and DL rate enforcement based on APN-AMBR; + +- DL rate enforcement based on the accumulated MBRs of the aggregate of SDFs with the same GBR QCI (e.g. by rate policing/shaping); +- DHCPv4 (server and client) and DHCPv6 (client and server) functions; + +Additionally the PDN GW includes the following functions for the GTP-based S5/S8/S2a/S2b: + +- UL and DL bearer binding as defined in TS 23.203 [73]; +- UL bearer binding verification; + +The PDN GW functions also includes user plane anchor for mobility between 3GPP access and non-3GPP access. It supports: + +- A LMA function for PMIPv6, if PMIP-based S5 or S8, or if PMIP based S2a or PMIP based S2b is used; +- A DSMIPv6 Home Agent, if S2c is used; +- Allocation of GRE key, which is used to encapsulate uplink traffic to the PDN GW on the PMIP-based S5/S8, or PMIP based S2a or PMIP based S2b interface; +- A MIPv4 Home Agent, if S2a with MIPv4 FA CoA mode is used. +- GPRS Tunnelling Protocol for the control plane and the user plane to provide PDN connectivity to UEs using non-3GPP accesses, if GTP based S2a or GTP based S2b is used. + +#### 4.1.4.3 SGSN + +In addition to the functions described for GPRS, for EPC SGSN functions include: + +- Inter EPC node signalling for mobility between 2G/3G and E-UTRAN 3GPP access networks; +- PDN and Serving GW selection: the selection of S GW/PDN GW by the SGSN is as specified for the MME; +- MME selection for handovers to E-UTRAN 3GPP access network. + +For details, see TS 23.401 [76] and TS 23.060 [9a]. + +#### 4.1.4.4 Trusted and Untrusted Non-3GPP Access Network + +Trusted and Untrusted Non-3GPP Access Networks are IP access networks that use access technology whose specification is out of the scope of 3GPP. + +Whether a Non-3GPP IP access network is Trusted or Untrusted is not a characteristic of the access network. + +In non-roaming scenario it is the HPLMN's operator decision if a Non-3GPP IP access network is used as Trusted or Untrusted Non-3GPP Access Network. + +In roaming scenario, the HSS/3GPP AAA Server in HPLMN makes the final decision of whether a Non-3GPP IP access network is used as Trusted or Untrusted non-3GPP Access Network. The HSS/3GPP AAA Server may take the VPLMN's policy and capability returned from the 3GPP AAA Proxy or roaming agreement into account. + +For details, see TS 23.402 [77]. + +#### 4.1.4.5 ePDG + +The functionality of ePDG includes the following: + +- Functionality defined for the PDG in TS 23.234 [67] for the allocation of a remote IP address as an IP address local to the ePDG which is used as CoA when S2c is used; +- Functionality for transportation of a remote IP address as an IP address specific to a PDN when S2b is used; +- Routing of packets from/to PDN GW (and from/to Serving GW if it is used as local anchor in VPLMN) to/from UE; if GTP based S2b is used, this includes routing of uplink packets based on the uplink packet filters in the TFTs assigned to the S2b bearers of the PDN connection; + +- Routing of downlink packets towards the SWu instance associated to the PDN connection; +- De-capsulation/Encapsulation of packets for IPSec and, if network based mobility (S2b) is used, for GTP or PMIP tunnels; +- Mobile Access Gateway (MAG) for PMIPv6 if PMIP based S2b is used; +- Tunnel authentication and authorization (termination of IKEv2 signalling and relay via AAA messages); +- Local mobility anchor within untrusted non-3GPP access networks using MOBIKE (if needed); +- Transport level packet marking in the uplink; +- Enforcement of QoS policies based on information received via AAA infrastructure; +- Lawful Interception. + +For details, see TS 23.402 [77]. + +#### 4.1.4.6 3GPP AAA Server + +The 3GPP AAA Server is located at the HPLMN and provides support for non-3GPP Access users with services like Authentication, Authorisation and location management services in order to get access to EPS. It also contains necessary user related information in order to grant access to non-3GPP access. It also coordinates the information needed to support mobility between 3GPP and non-3GPP accesses such as coordination of PDN GW information. It interacts with HSS to maintain consistent information for users supporting mobility and service continuity between 3GPP and non-3GPP access. For details, see TS 23.402 [77]. + +#### 4.1.4.7 3GPP AAA Proxy + +The 3GPP AAA Proxy provides support for roaming non-3GPP Access users in the VPLMN necessary the Authentication, Authorisation and location management services in order to get access to EPS. It may also provide roaming related information for support of chaining scenarios as described in TS 23.402 [77]. If an S-GW is needed for non-3GPP access in the visited network, the 3GPP AAA proxy selects an S-GW for the UE during initial attach or handover attach. + +#### 4.1.4.8 ANDSF + +The ANDSF (which is an optional element in the architecture) contains data management and control functionality necessary to provide network discovery and selection assistance data as per operators' policy. The ANDSF is able to initiate data transfer to the UE, based on network triggers, and respond to requests from the UE. It provides functions such as inter-system mobility policy, access network discovery information. + +The ANDSF in the subscriber's home operator network may interact with other databases such as the HSS user profile information residing in subscriber's home operator network. Details of such interaction with these databases are not described in this Release of the specifications. For details on ANDSF, see TS 23.402 [77]. + +NOTE: When the UE is roaming, how it discovers and interacts with the ANDSF is not specified in the specification of this release. + +### 4.1.5 Border Gateway (BG)] + +The Border Gateway (BG) is a gateway between a PLMN supporting GPRS/EPC and an external inter-PLMN backbone network used to interconnect with other PLMNs also supporting GPRS/EPC. The role of the BG is to provide the appropriate level of security to protect the PLMN and its subscribers. + +The BG is only needed in PLMNs supporting GPRS and EPC. + +## 4.2 The Access Network (AN) entities + +Three different types of access network are used by the CN: the AN include GERAN (also called BSS), UTRAN (also called RNS) and E-UTRAN. The MSC (resp. SGSN) can connect to one of the following Access Network type or to both of them: BSS, RNS. The MME connects to the E-UTRAN. + +The access technologies offered by the BSS are described in the 45-series of 3GPP specifications. The access technologies offered by the RNS (FDD, TDD) are described in the 25-series of 3GPP specifications. The access technologies offered by E-UTRAN (FDD, TDD) are described in the 36-series of 3GPP specifications. + +## 4.2.1 The Base Station System (BSS) + +The Base Station System (BSS) is the system of base station equipments (transceivers, controllers, etc.) which is viewed by the MSC through a single A and/or Iu-CS interface as being the entity responsible for communicating with Mobile Stations in a certain area. Similarly, in PLMNs supporting GPRS, the BSS is viewed by the SGSN through a single Gb or Iu-PS interface. When Intra Domain Connection of RAN Nodes to Multiple CN Nodes is applied, a BSS may connect to several MSCs by several A and/or Iu-CS interfaces, and a BSS may connect to several SGSNs by several Gb and/or Iu-PS interfaces. The functionality for the A interface is described in TS 48.002 [14] and for the Gb interface in TS 23.060 [9a]. The functionality for the Iu-CS interface is described in TS 25.410 [14a] and for the Iu-PS interface in TS 23.060 [9a]. + +The radio equipment of a BSS may support one or more cells. A BSS may consist of one or more base stations. Where an Abis-interface is implemented, the BSS consists of one Base Station Controller (BSC) and one or more Base Transceiver Station (BTS). The split of functions between BSS and CN for a Iu interface is described in the 25-series of UMTS Technical Specifications. + +The split of functions between BSS and CN for a A/Gb interface is described in the 48-series of GSM Technical Specifications. The split of functions between BSS and CN for a Iu interface is described in the 25-series of UMTS Technical Specifications. + +NOTE: The mobile station shall operate using only the following modes: + +- a** **A / Gb mode**, e.g. for pre-Release 4 terminals, or for Release 4 terminals when connected to a BSS with no Iu interface towards the Core Network. +- b** **Iu mode** (i.e. Iu-CS and Iu-PS ), e.g. for Release 4 terminals when connected to a BSS with Iu interfaces towards the Core Network. + +No other modes (e.g. A/Iu-PS or Iu-CS/Gb) shall be allowed. + +See also TS 43.051 [36]. + +### 4.2.1.1 Base Station Controller (BSC) + +A Base Station Controller (BSC) is a network component in the PLMN with the functions for control of one or more BTS. + +### 4.2.1.2 Base Transceiver Station (BTS) + +A Base Transceiver Station (BTS) is a network component which serves one cell. + +## 4.2.2 The Radio Network System (RNS) + +The Radio Network System (RNS) is the system of base station equipments (transceivers, controllers, etc.) which is viewed by the MSC through a single Iu-interface as being the entity responsible for communicating with Mobile Stations in a certain area. Similarly, in PLMNs supporting GPRS, the RNS is viewed by the SGSN through a single Iu-PS interface. When Intra Domain Connection of RAN Nodes to Multiple CN Nodes is applied, an RNS may connect to several MSCs by several Iu-CS interfaces, and an RNS may connect to several SGSNs by several Iu-PS interfaces. The functionality for the Iu-CS interface is described in TS 25.410 [14a] and for the Iu-PS interface in TS 23.060 [9a]. The radio equipment of a RNS may support one or more cells. A RNS may consist of one or more base stations. The RNS consists of one Radio Network Controller (RNC) and one or more Node B. + +The split of functions between RNS and CN is described in the 25-series of UMTS Technical Specifications. + +### 4.2.2.1 Radio Network Controller (RNC) + +A Radio Network Controller (RNC) is a network component in the PLMN with the functions for control of one or more Node B. + +#### 4.2.2.2 Node B + +A Node B is a logical network component which serves one or more UTRAN cells. + +### 4.2.3 Access Network elements for E-UTRAN + +#### 4.2.3.1 E-UTRAN Node B (eNB) + +An eNB is a logical network component which serves one or more E-UTRAN cells. + +#### 4.2.3.2 Evolved UTRAN + +The Evolved UTRAN (E-UTRAN) consists of eNBs, providing the E-UTRA user plane (PDCP/RLC/MAC/PHY) and control plane (RRC) protocol terminations towards the UE. The eNBs can be interconnected with each other by means of the X2 interface. The eNBs are connected by means of the S1 interface to the EPC (Evolved Packet Core), more specifically to the MME (Mobility Management Entity) by means of the S1-MME and to the Serving Gateway (S-GW) by means of the S1-U interface. The S1 interface supports a many-to-many relation between MMEs / Serving Gateways and eNBs. + +The split of functions between eNB and EPC is described in the specifications TS 23.401 [76], TS 36.300 [78] and TS 36.401 [79]. + +The architecture defined using E-UTRAN can be further described as follows: + +The E-UTRAN consists of set of eNBs connected to the EPC through the S1 interface. + +An eNB can support FDD mode, TDD mode or dual mode operation. + +## 4.3 The Mobile Station (MS) + +The mobile station consists of the physical equipment used by a PLMN subscriber; it comprises the Mobile Equipment (ME) and the Subscriber Identity Module (SIM), called UMTS Subscriber Identity Module (USIM) for Release 99 and following. The ME comprises the Mobile Termination (MT) which, depending on the application and services, may support various combinations of Terminal Adapter (TA) and Terminal Equipment (TE) functional groups. These functional groups are described in TS 24.002 [12]. + +## 4.4 User Equipment (UE) + +The User Equipment Allows a user access to network services. For the purpose of 3GPP specifications the interface between the UE and the network is the radio interface. A User Equipment can be subdivided into a number of domains, the domains being separated by reference points. Currently the User Equipment is subdivided into the UICC domain and the ME Domain. The ME Domain can further be subdivided into one or more Mobile Termination (MT) and Terminal Equipment (TE) components showing the connectivity between multiple functional groups. + +--- + +## 4a The specific entities of the 3GPP system + +The entities presented in this clause are dedicated to the provisioning of a given (set of) service(s). The fact that they are implemented or not in a given PLMN should have limited impact on all the other entities of the PLMN. + +All the specific entities defined so far are located in the Core Network. + +### 4a.1 The Group Call Register (GCR) entity + +The Group Call Register (GCR) is a register holding information about VGCS or VBS calls, the voice group or broadcast call attributes, respectively. + +Voice group or broadcast call attributes are defined for a specific voice group or broadcast call reference and include the data required to configure the conference bridge for a VGCS or VBS call and other call related attributes. + +The Group Call Register (GCR) shall hold for a related MSC area for each group ID and cell from which Voice Group Call Service (VGCS) or Voice Broadcast Service (VBS) calls can be established by mobile stations the voice group call + +reference or voice broadcast call reference to be used for a VGCS or VBS call to be established and an indication whether the originating MSC is the MSC responsible for that call. + +If the originating MSC is not responsible for that call, the GCR shall hold the routing information identifying the MSC responsible for that call. + +A GCR may be in charge of one or several MSC. Each MSC involved in a voice group or broadcast call requests its proper voice group or broadcast call attributes from its related GCR by use of the voice group or broadcast call reference. + +The contents of each list related to requests of the MSC responsible for a voice group or broadcast call is as follows: + +- a list of cells inside the MSC area of the requesting MSC into which the call is to be sent (part of the group call area); +- a list of other MSCs into which the call is to be sent; +- a list of identities of dispatchers to which a dedicated link is to be established; +- a list of identities of dispatchers which are allowed to initiate the voice group or broadcast call; +- a list of identities of dispatchers which are allowed to terminate the voice group or broadcast call; +- the length of time over which no activity is detected before the voice group call is automatically terminated; +- the default priority level related to the voice group or broadcast call if the eMLPP supplementary service applies; +- a flag indicating if acknowledgements are required for this voice group or broadcast call. + +The contents of each list related to requests of an MSC not responsible for a voice group or broadcast call is as follows: + +- a list of cells inside the MSC area of the requesting MSC into which the call is to be sent (part of the group call area). + +More information is provided in TS 43.068 [41] and TS 43.069 [42]. + +## 4a.2 (void) + +## 4a.3 The Location Services (LCS) entities + +This section describes the Location Services entities found in the Core Network and Radio Access Network that support positioning methods for the UE/MS. + +For further details on LCS in E-UTRAN, UMTS and GSM from system and core network point view, see TS 23.271 [56]. + +For further details on LCS in UTRAN, see TS 25.305 [10b]. + +For further details on LCS in GERAN, see TS 43.059 [10d]. + +For further details on user-plane LCS in E-UTRAN, see OMA SUPL [80]. For further details on control plane LCS for E-UTRAN see TS 36.305 [122]. + +### 4a.3.1 Location Services (LCS) entities in RAN + +The RAN (E-UTRAN, UTRAN and GERAN) supports one or more UE/MS positioning methods to calculate the geographical position of the UE/MS and responds to the UE/MS location request received from the CN. For UTRAN and GERAN, the RAN may broadcast LCS assistance data to UEs/MSs under its coverage. In case this assistance data is ciphered, the ciphering key is provided by the CN to the UE/MS. + +To support UE positioning methods, the RAN is made of several entities like: + +**BSC/SRNC:** the BSC for GERAN and SRNC for UTRAN receive authenticated location requests from the CN: + +- In UTRAN, the SRNC co-ordinates the positioning requests taking into account their priority and it selects the positioning method to fulfil the requested accuracy. It interfaces, when necessary, with the + +CRNC which mainly manages resources allocated to UE positioning operations and requests UE Positioning related measurements from its associated Node Bs and LMUs. + +- In GERAN, the BSC passes the location request to the SMLC. + +**SMLC:** + +- The Serving Mobile Location Centre (SMLC) function can be part of the RNC or be a SAS (Stand-Alone SMLC) for UTRAN. The SMLC function can be part of the BSC or be in a separate SMLC server for GERAN. +- In UTRAN, the SMLC function provides assistance data to the RNC and acts as a location calculation server if the location estimates are not to be calculated in the RNC. +- In GERAN, the SMLC function co-ordinates the positioning request, schedules resources required to perform positioning of a mobile, and calculates the final location estimate and accuracy. The SMLC may control a number of LMUs. + +**LMU:** The Location Measurement Unit (LMU) entity makes measurements for one or more positioning methods. + +**Node B:** Node B is a network element of UTRAN that may provide measurement results for position estimation and makes measurements of radio signals. + +**eNodeB:** The eNode B is a network element of E-UTRAN that may provide measurement results for position estimation and makes measurements of radio signals for a target UE and communicates these measurements to an E-SMLC. + +**CBC:** The Cell Broadcast Centre, in GERAN, the SMLC function may interface a CBC in order to broadcast assistance data using existing cell broadcast capabilities. + +For detail on Location services, entities and interfaces provided by E-UTRAN, see TS 36.305 [122]. + +For detail on Location services, entities and interfaces provided by UTRAN, see TS 25.305 [10b]. + +For detail on Location services, entities and interfaces provided by GERAN, see TS 43.059 [10d]. + +### 4a.3.2 Gateway Mobile Location Centre (GMLC) + +The Gateway Mobile Location Centre (GMLC) is the first node an external Location Application accesses in the GSM PLMN. The GMLC performs registration authorization and requests routing information from the HLR/HSS. There may be more than one GMLC in a PLMN. + +### 4a.3.3 Location Measurement Unit (LMU) + +An LMU makes radio measurements to support one or more positioning methods. + +Two types of LMU are defined: + +- Type A LMU: accessed over the normal GSM air interface; +- Type B LMU: accessed over the base station to controller interface (Abis in GSM and Iub in UMTS). + +A type A LMU is accessed exclusively over the GSM air interface (Um interface): there is no wired connection to any other network element. + +In GSM, a type A LMU has a serving BTS and BSC that provide signalling access to a controlling SMLC. With an NSS based SMLC, a type A LMU also has a serving MSC and VLR and a subscription profile in an HLR. A type A LMU always has a unique IMSI and supports all radio resource and mobility management functions of the GSM air interface that are necessary to support signalling using an SDCCH to the SMLC. A type A LMU supports those connection management functions necessary to support LCS signalling transactions with the SMLC and may support certain call control functions of to support signalling to an SMLC using a circuit switched data connection. + +In UTRAN, a type A LMU has signalling access to the SRNC. Type A LMU is not supported in UMTS release 1999. + +In GSM, a Type B LMU is accessed over the Abis interface from a BSC. The LMU may be either a standalone network element addressed using some pseudo-cell ID or connected to or integrated in a BTS. Signalling to a Type B LMU is by means of messages routed through the controlling BSC for a BSS based SMLC or messages routed through a controlling BSC and MSC for an NSS based SMLC. + +In UTRAN, a Type B LMU is accessed over the Iub interface from an RNC. The LMU may be either a standalone network element addressed using some pseudo-cell ID or connected to or integrated in a Node B. + +#### 4a.3.4 Evolved Serving Mobile Location Centre (E-SMLC) + +For E-UTRAN, the Evolved Serving Mobile Location Centre (E-SMLC) is a server in the core network. The E-SMLC manages the support of different location services for target UEs, including positioning of UEs and delivery of assistance data to UEs. The E-SMLC may interact with the serving eNodeB for a target UE in order to obtain position measurements for the UE, including uplink measurements made by the eNodeB and downlink measurements made by the UE that were provided to the eNodeB as part of other functions such as for support of handover. + +The E-SMLC may interact with a target UE in order to deliver assistance data if requested for a particular location service, to obtain a location estimate, or location related measurements, if that was requested. + +For positioning of a target UE, the E-SMLC decides on the position methods to be used, based on factors that may include the LCS Client type, the required QoS, UE positioning capabilities, and eNode B positioning capabilities. The E-SMLC then invokes these positioning methods in the UE and/or serving eNode B. The positioning methods may yield a location estimate for UE-based position methods and/or positioning measurements for UE-assisted and network-based position methods. The E-SMLC may combine all the received results and determine a single location estimate for the target UE (hybrid positioning). Additional information like accuracy of the location estimate and velocity may also be determined. + +#### 4a.4 CAMEL entities + +The entities of this clause support the CAMEL feature (Customised Applications for Mobile network Enhanced Logic). This feature provides the mechanisms to support services consistently independently of the serving network, as described in TS 22.078 [2c]. The following definitions are extracted from TS 23.078 [10c], which completely specifies CAMEL stage 2. + +##### 4a.4.1 GSM Service Control Function (gsmSCF) + +A functional entity that contains the CAMEL service logic to implement Operator Specific Service. It interfaces with the gsmSSF, the gsmSRF and the HLR. + +##### 4a.4.2 GSM Service Switching Function (gsmSSF) + +A functional entity that interfaces the MSC/GMSC to the gsmSCF. The concept of the gsmSSF is derived from the IN SSF, but uses different triggering mechanisms because of the nature of the mobile network. + +##### 4a.4.3 GSM Specialised Resource Function (gsmSRF) + +A functional entity which provides various specialized resources. It interfaces with the gsmSCF and with the MSC. This entity is defined in ITU-T Q.1214 [11] with variations defined in TS 23.078 [10c]. + +##### 4a.4.4 GPRS Service Switching Function (gprsSSF) + +A functional entity that interfaces the SGSN to the gsmSCF. The concept of the gprsSSF is derived from the IN SSF, but uses different triggering mechanisms because of the nature of the mobile network. + +#### 4a.5 CBS-specific entities + +The cell broadcast service (CBS) is a Teleservice which enables an Information Provider to submit short messages for broadcasting to a specified area within the PLMN. TS 23.041 [8] contains the technical realization of the service. + +### 4a.5.1 Cell Broadcast Centre (CBC) + +The CBC shall be responsible for the management of CBS messages and for determining the CBS delivery parameters of the BSS/RNS. The CBC may be connected to several BSCs/RNCs. The CBC is regarded to be integrated as a node into the core network. + +NOTE: Whether it should be possible that an RNC is connected to at least two CBCs at the same time (the "normal" one as in GSM and a second one for LCS) is for further study and depends on the solution taken for LCS. + +## 4a.6 Number Portability Specific entities + +Two different solutions are defined to support Number Portability. The first one is an IN based solution and is described in the next clause. The second one is a "Signalling Relay" based solution described in next but one clause. + +For details on MNP see TS 23.066 [40]. + +### 4a.6.1 IN-based solution: Number Portability Database (NPDB) + +The Number Portability Database (NPDB) is the central element of the IN based solution for Mobile Number Portability (MNP). MNP is the ability for a mobile subscriber to change the GSM subscription network within a portability cluster (e.g. a country) whilst retaining his/her original MSISDN or MSISDNs. + +The NPDB stores the table of correspondence between MSISDNs and Subscription networks. Upon request of the (gateway or visited) MSC, the NPDB retrieves from the MSISDN the Routing Number pointing out the Subscription network. + +### 4a.6.2 Signalling Relay-based solution: Mobile Number Portability/Signalling Relay function (MNP-SRF) + +The MNP-Signalling Relay Function (MNP-SRF) is the central element of the Signalling Relay based solution for Mobile Number Portability. + +The MNP-SRF obtains the routing information from a NP database to identify the subscription network associated with a particular national MSISDN. Upon request from gateway MSC, the MNP-SRF may perform one of the following actions: + +1. the MNP-SRF will reply back to the GMSC with the necessary routing information to route the call; +2. the message is relayed to the HLR; +3. the message is relayed to MNP-SRF in the subscription network. + +For non-call related signalling (e.g. delivery of SMS), only cases 2 and 3 are applicable. + +## 4a.7 IP Multimedia (IM) Core Network (CN) Subsystem entities + +### 4a.7.1 Call Session Control Function (CSCF) + +The CSCF can act as Proxy CSCF (P-CSCF), Serving CSCF (S-CSCF), Emergency CSCF (E-CSCF), or Interrogating CSCF (I-CSCF). The P-CSCF is the first contact point for the UE within the IM subsystem (IMS); the S-CSCF actually handles the session states in the network; the E-CSCF handles certain aspects of emergency sessions such as routing an emergency request to the correct emergency centre or PSAP; the I-CSCF is mainly the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. Further definitions of the P-, S- and I-CSCF are provided in TS 23.228 [34]. Further definitions of the E-CSCF is provided in TS 23.167 [74]. + +### 4a.7.2 Media Gateway Control Function (MGCF) + +The MGCF: + +- Controls the parts of the call state that pertain to connection control for media channels in an IMS-MGW. + +- Communicates with CSCF, BGCF, and circuit switched network entities. +- Determines the next hop depending on the routing number for incoming calls from legacy networks. +- Performs protocol conversion between ISUP/TCAP/SIP-I and the IM subsystem call control protocols. +- Out of band information received in MGCF may be forwarded to CSCF/IMS-MGW. + +#### 4a.7.3 IP Multimedia Subsystem - Media Gateway Function (IMS-MGW) + +Note: In this document the term Media Gateway Function (MGW) is used when there is no need to differentiate between the CS domain entity and the IP Multimedia CN Subsystem entity. When referring specifically to the CS domain entity, the term CS-MGW is used. When referring specifically to the IP Multimedia CN Subsystem entity, the term IMS-MGW is used. + +A IMS-MGW may terminate bearer channels from a switched circuit network and media streams from a packet network (e.g., RTP streams in an IP network). The IMS-MGW may support media conversion, bearer control and payload processing (e.g. codec, echo canceller, conference bridge), it: + +- Interacts with the MGCF for resource control. +- Owns and handles resources such as echo cancellers etc. +- May need to have Codecs. + +The IMS-MGW will be provisioned with the necessary resources for supporting UMTS/GSM transport media. Further tailoring (i.e. packages) of the H.248 [52] may be required to support additional Codecs and framing protocols, etc. + +#### 4a.7.4 Multimedia Resource Function Controller (MRFC) + +The MRFC: + +- Controls the media stream resources in the MRFP. +- Interprets information coming from an AS and S-CSCF (e.g. session identifier) and control MRFP accordingly. +- Generates CDRs . + +#### 4a.7.4a Multimedia Resource Function Processor (MRFP) + +The MRFP: + +- Controls bearers on the Mb reference point. +- Provides resources to be controlled by the MRFC. +- Mixes incoming media streams (e.g. for multiple parties). +- Sources media streams (for multimedia announcements). +- Processes media streams (e.g. audio transcoding, media analysis). +- Floor Control (i.e. manage access rights to shared resources in a conferencing environment). + +#### 4a.7.4b Media Resource Broker (MRB) + +The MRB supports the sharing of a pool of heterogeneous MRF resources by multiple heterogeneous applications. MRB assigns (and later releases) specific suitable MRF resources to calls as requested by the consuming applications, based on MRF attributes specified by the applications as well as other criteria. + +The MRB may take the following kinds of information into account when assigning MRF resources to an application: + +- the specific characteristics of the media resources required for the call or calls; +- the identity of the application; + +- rules for allocating MRF resources across different applications; +- per-application or per-subscriber SLA or QoS criteria; and +- capacity models of particular MRF resources. + +## 4a.7.5 Void + +## 4a.7.6 Breakout Gateway Control Function (BGCF) + +The Breakout Gateway control function (BGCF) determines the next hop for routing the SIP message. This determination may be based on information received in the signalling protocol, administrative information, and/or database access. For PSTN/CS Domain terminations, the BGCF determines the network in which PSTN/CS Domain breakout is to occur and - within the network where the breakout is to occur - selects the MGCF. + +Details are described in TS 23.228 [34]. + +## 4a.7.7 Application Server (AS) + +An Application Server (AS) i.e., SIP Application Server, OSA Application Server, or CAMEL IM-SSF, offers value added IM services and resides either in the user's home network or in a third party location. The third party could be a network or simply a stand-alone AS. + +NOTE 1: The OSA Application Server does not directly interact with the IMS network entities but through the OSA Service Capability Servers (OSA SCS-s). Further information on OSA is provided in TS 22.127 [4]. + +NOTE 2: A SIP Application Server specified within 3GPP that supports IMS reference points (e.g. ISC, Sh, Ut), in support of an application, is considered as part of the IM CN subsystem. Examples of such ASs are SCC AS and TAS. + +The AS (SIP Application Server and/or the OSA Service Capability Server and/or IM-SSF) can communicate with the HSS. The Sh and Si interfaces are used for this purpose. + +The Serving-CSCF to AS interface is used to provide services residing in an AS. Two cases were identified: + +- Serving-CSCF to an AS in Home Network. +- Serving-CSCF to an AS in a trusted External Network (e.g., Third Party or Visited). The S-CSCF does not provide authentication and security functionality for secure direct third party access to the IM Subsystem. The OSA framework provides a standardized way for third party access to the IM Subsystem. + +The Interrogating-CSCF to AS interface is used to forward SIP requests destined to a Public Service Identity hosted by the AS directly to that AS. + +The AS to MRFC interfaces are: + +- Mr' , used for session control; +- Cr, used for media control. + +The AS to MRB interface (Rc) is used by the AS to request that MRF resources with certain characteristics be assigned to a call. + +An Application Server may influence and impact the SIP session on behalf of the services supported by the operator's network. An AS may host and execute services. + +## 4a.7.8 Interconnection Border Control Function (IBCF) + +An IBCF provides application specific functions at the SIP/SDP protocol layer in order to perform interconnection between two operator domains. It enables communication between IPv6 and IPv4 SIP applications. network topology hiding, controlling transport plane functions, screening of SIP signalling information, selecting the appropriate signalling interconnect and generation of charging data records. Details are described in TS 23.228 [34]. + +#### 4a.7.9 Transition Gateway (TrGW) + +A TrGW is located within the media path and controlled by an IBCF. It provides functions like network address/port translation and IPv4/IPv6 protocol translation. Details are described in TS 23.228 [34]. + +#### 4a.7.10 Location Retrieval Function (LRF) + +The LRF retrieves location information for the UE including, where required, interim location information, initial location and updated location information. The LRF may interact with a Routing Determination Function (RDF) in order to obtain routing information. The LRF may interact with a GMLC or other types of location server functions in order to obtain location information. Further definitions of the LRF is provided in TS 23.167 [74]. + +#### 4a.7.11 Service Centralization and Continuity Application Server (SCC AS) + +The SCC AS is an IMS Application that can provide functionality required to enable IMS Centralized Services as defined in TS 23.292 [110], and can provide IMS-based mechanisms for enabling service continuity of multimedia sessions as defined in TS 23.237 [111]. + +#### 4a.7.11a Emergency Access Transfer Function (EATF) + +The EATF provides IMS-based mechanisms for enabling service continuity of IMS emergency sessions. It is a function in the serving (visited if roaming) IMS network, providing the procedures for IMS emergency session anchoring and PS to CS access transfer as defined in TS 23.237 [111]. + +#### 4a.7.12 Access Transfer Control Function (ATCF) + +The ATCF is a function in the serving (visited if roaming) IMS network. It enables SRVCC Session Transfer mechanisms in the serving network for a UE. The SCC AS can provide Session Transfer mechanisms in the serving network, if an ATCF is present in the SIP registration path of the UE, as defined in TS 23.237 [111]. + +#### 4a.7.13 Access Transfer Gateway (ATGW) + +The ATGW is a media function in the serving (visited if roaming) IMS network. It may anchor the media for enhanced SRVCC procedure as defined in TS 23.237 [111]. + +### 4a.8 Signalling Gateway Function (SGW) + +The SGW performs the signalling conversion (both ways) at transport level between the SS7 based transport of signalling used in pre-Rel-4 networks, and the IP based transport of signalling possibly used in post-R99 networks (i.e. between Sigtran SCTP/IP and SS7 MTP). The SGW does not interpret the application layer (e.g. MAP, CAP, BICC, ISUP) messages but may have to interpret the underlying SCCP or SCTP layer to ensure proper routing of the signalling. + +### 4a.9 Global Text Telephony Specific entities + +Interworking between cellular text modem (CTM) and text telephony standards (e.g. V.18) used in external networks can be supported by three methods: + +- Routing calls through a CTM Special resource function (CTM-SRF) in the core network. The CTM-SRF is linked in to the call path via CAMEL procedures. Depending on operator configuration the CTM-SRF may also be linked in to the call path for Emergency calls. +- A CTM / Text telephone converting function included along the speech call path selected by the network after an indication from the terminal that CTM is required. +- A CTM / Text telephone converting function included in all speech call paths. + +Further information of the support for text telephony is found in TS 23.226 [37]. + +For further details of CTM, see TS 26.226 [38]. + +## 4a.10 Security Gateway (SEG) + +The 3GPP system and its network domains shall be logically and physically divided into security domains in order to protect IP based control plane signalling. These security domains typically coincide with operator borders. + +The interface between different security domains is protected by Security Gateways (SEGs). The SEGs are responsible for enforcing the security policy of a IP security domain towards other SEGs in the destination IP security domain. All NDS/IP traffic shall pass through a SEG before entering or leaving a security domain. For further details of SEG, see TS 33.210 [64]. + +## 4a.11 Application Function (AF) + +The Application Function (AF) is an element offering applications that require the control of IP bearer resources or the control of flow based bearer charging. The AF is capable of communicating with the PCRF to transfer dynamic QoS-related service information and/or dynamic charging-related service information. + +One example of an AF is the P-CSCF of the IM CN subsystem. + +## 4a.12 Void + +## 4a.13 3GPP/WLAN Interworking entities + +### 4a.13.1 WLAN UE + +A WLAN UE is the User Equipment using a UICC card utilized by a 3GPP subscriber to access the WLAN network for 3GPP interworking purpose. + +### 4a.13.2 3GPP AAA Proxy + +The 3GPP AAA Proxy in case of I-WLAN access as specified in TS 23.234 [67] represents a AAA proxying and filtering function and resides in the visited 3GPP network. It is involved in access and service authentication and authorization procedures of a WLAN UE. + +### 4a.13.3 3GPP AAA Server + +The 3GPP AAA server resides in the 3GPP network and in case of I-WLAN access as specified in TS 23.234 [67] is responsible for access and service authentication and authorization of a WLAN UE. + +### 4a.13.4 WLAN Access Gateway (WAG) + +The WLAN access gateway is a gateway between WLAN and 3GPP network. In the roaming case it resides in the visited 3GPP network, otherwise in the home 3GPP network. It provides filtering, policing and charging functionality for the traffic between WLAN UE and 3GPP network. + +### 4a.13.5 Packet Data Gateway (PDG) + +The Packet Data Gateway provides access to PS based services for a WLAN UE. It resides either in the home (for access to home services) or in the visited 3GPP network (for access to local services). + +### 4a.13.6 Home Agent (HA) + +The HA provides control and mobility function for service continuity between 3GPP WLAN Interworking system and 3GPP Systems. The HA terminates the HGi reference point towards the PDN as defined in TS 23.327 [112]. + +## 4a.14 Multimedia Broadcast Multicast Service (MBMS) specific entities + +### 4a.14.1 General + +The Multimedia Broadcast Multicast Service (MBMS) is a point-to-multipoint service in which data is transmitted from a single source entity to multiple recipients. TS 23.246 [70] contains the technical realization of the service. + +### 4a.14.2 Broadcast-Multicast Service Centre (BM-SC) + +The Broadcast-Multicast Service Centre provides functions for MBMS user service provisioning and delivery. It may serve as an entry point for content provider MBMS transmissions, used to authorise and initiate MBMS Bearer Services within the PLMN and can be used to schedule and deliver MBMS transmissions. + +### 4a.14.3 MBMS-GW + +The MBMS-GW provides functions in the EPS for controlling MBMS session initiation/modification/termination by the MBMS User Service and for providing delivery of IP Multicast datagrams from the SGi-mb reference point to downstream nodes in the MBMS Service Area with a specified quality of service. + +### 4a.14.4 Multi-cell/multicast Coordination Entity (MCE) + +The MCE is a functional entity providing functions for admission control and allocation of radio resources by E-UTRAN and for MBMS session control. See TS 36.300 [78]. + +## 4a.15 Void + +## 4a.16 GUP Server + +The GUP Server is a functional entity providing a single point of access to the Generic User Profile data of a particular subscriber. The architecture does not specify or limit the physical location of the GUP Server enabling flexibility in the implementations. For further details of the GUP Server, see TS 23.240 [71]. + +## 4a.17 Policy and Charging Rules Function (PCRF) + +The Policy and Charging Rules Function (PCRF) acts as a policy decision point for policy and charging control of service data flows/applications and IP bearer resources. The PCRF selects and provides the applicable policy and charging control decision to the PCEF and, if applicable, application detection and control decision to the TDF or PCEF with application detection and control feature. When the Gxx interface applies, the PCRF maintains the correlation between the GW control session over Gxx interface and the IP-CAN session over Gx. The PCRF also acts as an information exchange relay between BBERF and PCEF to forward event triggers, which can't be transferred directly. + +When the Sd interface applies, the PCRF maintains the correlation between the IP-CAN session and the TDF session. Events subscribed by the TDF are reported by the PCRF. + +When S9a interface applies, the PCRF provides to the BPCF the UE/H(e)NB local IP address and UDP port number, the QoS rules and PCC rules over S9a interface. PCRF maintains the correlation between the GW control session over S9a interface and the IP-CAN session over Gx interface (if IP-CAN session over Gx interface is available). + +When S15 interface applies, the PCRF provides dynamic QoS control policies to the BPCF for the purpose of allocation of QoS resources in the Fixed Broadband Access Network for HNB CS traffic. + +PCRF is the policy and charging control element. PCRF functions are described in more detail in TS 23.203 [73]. + +In non-roaming scenario, there is only a single PCRF in the HPLMN associated with one UE's IP-CAN session. + +In a roaming scenario with local breakout of traffic and/or when a Gxx interface applies there are two PCRFs associated with one UE's IP-CAN session: + +- H-PCRF that resides within the H-PLMN; + +- V-PCRF that resides within the V-PLMN. + +A single logical PCRF entity may be deployed by means of multiple and separately addressable PCRFs in the PLMN. In this case, the PCRF discovery and selection is enabled by Diameter Routing Agency (DRA). + +## 4a.18 Policy and Charging Enforcement Function (PCEF) + +The Policy and Charging Enforcement Function (PCEF) acts as a policy enforcement point for policy and charging control of IP bearer resources. + +This functional entity is located at the Gateway (e.g. GGSN in the GPRS case) and in the PDN GW for EPS). + +The functionality of PCEF is described in TS 23.203 [73], TS 23.401 [76] and TS 23.402 [77]. + +## 4a.19 Support of Short Message Service over generic 3GPP Internet Protocol access (SMSIP) specific entities + +### 4a.19.1 General + +Support of Short Message Service over generic 3GPP Internet Protocol access (SMSIP) provide 3GPP SMS messaging services across any form of IP Connectivity Access Network. TS 23.204 [75] contains the technical realization of the service. + +### 4a.19.2 IP-Short-Message-Gateway (IP-SM-GW) + +The IP Short Message Gateway function is used for two functions: to deliver SMS messages over the IP network and to provide interworking between SMS users and Instant Messaging users. The interworking function translates between MAP and SIP signalling to convey messages and responses between the two systems. Both functions are described in TS 23.204 [75]. + +## 4a.20 Subscription Profile Repository (SPR) + +The SPR logical entity contains all subscriber/subscription related information needed for subscription-based policies and charging control by the PCRF. + +## 4a.21 Service Data Flow Based Credit Control Function + +The Service Data Flow Based Credit Control Function performs online credit control functions. It is a functional entity embedded in the Online Charging Function (OCF) within the Online Charging System (OCS) as specified in TS 32.296 [108]. + +## 4a.22 Offline Charging System (OFCS) + +The Offline Charging System is logically specified in TS 32.240 [85]. + +## 4a.23 Online Charging System (OCS) + +The Online Charging System is specified in TS 32.296 [108]. + +## 4a.24 Bearer Binding and Event Reporting Function (BBERF) + +The Bearer Binding and Event Reporting Function (BBERF) acts as a policy enforcement point for bearer binding, uplink bearer binding verification and event reporting to the PCRF when Gxx applies. + +This function entity is located at a GW (e.g. S-GW in the 3GPP access with PMIP based S5/S8 case, HSGW in the HRPD case, A-GW in the non- 3GPP access when PMIP or DSMIPv6 based mobility is used, ePDG with PMIP based S2b or Untrusted S2c case if Gxb\* applies). + +The BBERF in the ePDG supports only reporting of the UE's Local IP address and UDP port number to the PCRF. Bearer binding and bearer binding verification functions are not supported. + +## 4a.25 Home (e)NodeB entities + +### 4a.25.1 Home NodeB Subsystem (HNS) + +The Home NodeB Subsystem (HNS) consists of a Home NodeB (HNB), a Home NodeB Gateway (HNB-GW) and optionally a Local GW (L-GW). The Home NodeB Subsystem appears as an RNS to the core network and is connected by means of the Iu-CS interface to the MSC and by means of the Iu-PS interface to the SGSN. + +A Home NodeB is a Customer Premises Equipment (CPE) offering UTRAN coverage, further details can be found in TS 25.467 [114]. + +A Home NodeB Gateway is the gateway through which the Home NodeB accesses the core network, more details can be found in TS 25.467 [114]. + +A Local GW is a gateway towards the IP networks (e.g. residential/enterprise networks) associated with the Home NodeB, more details can be found in TS 23.060 [9a]. The Local GW is colocated with the Home NodeB. + +### 4a.25.2 Home eNodeB Subsystem (HeNS) + +The Home eNodeB Subsystem (HeNS) consists of a Home eNodeB (HeNB), optionally a Home eNodeB Gateway (HeNB-GW) and optionally a Local GW (L-GW). The Home eNodeB Subsystem is connected by means of the S1 interface to the EPC (Evolved Packet Core), more specifically to the MME (Mobility Management Entity) by means of the S1-MME interface and to the Serving Gateway (S-GW) by means of the S1-U interface. + +A Home eNodeB is a Customer-Premises Equipment (CPE) offering E-UTRAN coverage, further details can be found in TS 36.300 [78]. + +A Home eNodeB Gateway is an optional gateway through which the Home eNodeB accesses the core network, more details can be found in TS 36.300 [78]. + +A Local GW is a gateway towards the IP networks (e.g. residential/enterprise networks) associated with the Home eNodeB, more details can be found in TS 23.401 [76]. The Local GW is colocated with the Home eNodeB. + +### 4a.25.3 CSG List Server + +The CSG List Server provisions the Allowed CSG list and the Operator CSG list on the UE using the OTA procedures defined in TS 31.102 [118] or the OMA DM procedures defined in TS 24.285 [117]. + +The Allowed CSG list and the Operator CSG list are applicable to both UTRAN and E-UTRAN CSG cells for HNB and HeNB respectively. + +### 4a.25.4 CSG Subscriber Server (CSS) + +The CSS is the entity in the VPLMN storing and managing CSG subscription-related information for roaming UEs to enable VPLMN Autonomous CSG Roaming (see TS 22.220 [130]). + +The CSS is responsible for holding the following user related information: + +- User Identification; +- CSG membership granted to the subscriber during his stay in the VPLMN, i.e. list of CSG IDs and associated expiration dates; +- User Location information: the CSS stores the location information of the subscriber for subsequent update of the CSG subscription information at the MME, SGSN and VLR upon subscription change. + +The CSS consists of the following functionalities: + +- download of the CSG subscription information upon request from the serving MME, SGSN and VLR, through the S7a, S7d, Ghv and Hv interfaces, to enable roaming subscribers to access to the PS and CS Domain services via CSG cells; +- service provisioning, including updating the appropriate serving entities (i.e. MME, SGSN and VLR) with modifications of the the CSG membership granted to the subscriber. + +The organisation of the subscriber data is outlined in TS 23.008 [5]. It also indicates which numbers and identifiers specified in TS 23.003 [3] are stored in the CSS. + +## 4a.26 Application Front Ends (AFE) + +When the User Data Convergence (UDC) architecture is applied, certain functional entities keep the application logic, but do not locally store user data permanently. Examples of such functional entities are HLR/HSS/AuC and Application Servers. These data-less functional entities are known in the UDC architecture as Application Front Ends. The application that is handled by an AFE determines the type of AFE, e.g. HLR-FE or HSS-FE. The reference points between the Front Ends and the core and service layers are not affected by the UDC architecture. More information on Application Front Ends can be found in TS 23.335 [120]. + +## 4a.27 User Data Repository (UDR) + +The UDR is a functional entity that acts as a single logical repository storing user data. The user-related data traditionally stored in the HSS/HLR/AuC, Application Servers, etc., are now stored in the UDR. UDR facilitates the share and provisioning of user-related data. The UDR provides a unique reference point to Application Front Ends such as HSS/HLR/AuC/AS Front Ends. This reference point is named Ud. More information on the UDR can be found in TS 23.335 [120]. + +## 4a.28 Traffic Detection Function (TDF) + +The Traffic Detection Function (TDF) is a functional entity that performs application detection and control. + +The functional description of the TDF is in TS 23.203 [73]. + +## 4a.29 Specific entities to facilitate communications with packet data networks and applications + +### 4a.29.1 Machine Type Communication-InterWorking Function (MTC-IWF) + +The Machine Type Communication-InterWorking Function (MTC-IWF) is a functional entity that acts as an interface between the PLMN and a Services Capability Server (SCS) to provide specific MTC functionalities in the PLMN such as device triggering. + +The functional description of the MTC-IWF is in TS 23.682 [132]. + +### 4a.29.2 Machine Type Communication- Authentication, Authorization and Accounting (MTC-AAA) + +The Machine Type Communication-Authentication, Authorization and Accounting (MTC-AAA) is a functional entity that translates an IMSI to the external identifier(s) of the user. + +The functional description of the MTC-AAA is in TS 23.682 [132]. + +--- + +## 5 Configuration of a Public Land Mobile Network + +### 5.1 Basic configuration + +The basic configuration of a Public Land Mobile Network (PLMN) supporting GPRS and the interconnection to the PSTN/ISDN and PDN is presented in figure 1 and figure 1a. Whereas the basic configuration of a Public Land Mobile Network (PLMN) supporting PS Domain (both GPRS and EPC) and the interconnection to the PSTN/ISDN and PDN is presented in figure 1b. This configuration presents signalling and user traffic interfaces which can be found in a PLMN. Implementations may be different: some particular functions may be gathered in the same equipment and then some interfaces may become internal interfaces. + +In the basic configuration presented in figure 1, all the functions are considered implemented in different equipments. Therefore, all the interfaces within PLMN are external. Interfaces A and Abis are defined in the 48-series of Technical Specifications. Interfaces Iu, Iur and Iub are defined in the 25.4xx-series of Technical Specifications. Interfaces B, C, D, + +E, F and G need the support of the Mobile Application Part of the signalling system No. 7 to exchange the data necessary to provide the mobile service. No protocols for the H-interface and for the I-interface are standardized. All the GPRS-specific interfaces (G- series) are defined in the 23-series, 24-series and 29-series of Technical Specifications. Interfaces Mc, Nb, and Nc are defined in TS 23.205 [43] and in the 29-series of Technical Specifications. The specifications for E-UTRAN interfaces S1 and X2 are specified in TS 36.4xx and NAS protocol is specified in TS 24.301 [89] series of specifications. The interfaces S6a/d/S13 are specified in the specifications TS 29.272 [86]. The EPC specific S1/3/4/5/8/10/11/12/ series are specified in TS 29.274 [90] for GTP based protocols and for PMIP based S5/8 interfaces are specified in TS 29.275 [93]. + +From this configuration, all the possible 3GPP access PLMN organisations can be deduced. In the case when some functions are contained in the same equipment, the relevant interfaces become internal to that equipment. + +The configuration possibilities when using non-3GPP access technologies using EPS is not part of the scope of this specification. The architecture and details for non-3GPP access and mobility and interworking with non-3GPP access are described in TS 23.402 [77] and the interfaces and protocols are specified in 3GPP 24-series and 29-series of specifications.. + +![Figure 1: Basic Configuration of a PLMN supporting CS and PS services (using GPRS) and interfaces. The diagram shows the network architecture including PSTN, CS-MGW, GMSC server, PCRF, GGSN, HSS (HLR,AuC), EIR, VLR, MSC server, SGSN, BSS (BSC, BTS), RNS (RNC, Node B), and MS (ME, SIM/USIM). Interfaces are labeled with letters like PSTN, Rx, Gi, Gp, Mc, Nb, Ne, C, Gc, Gn, Gr, Gf, Gs, A, Gb, IuCS, IuPS, Iur, Abis, Iub, Um, and Uu. Bold lines represent user traffic interfaces, and dashed lines represent signalling interfaces.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +The diagram illustrates the basic configuration of a PLMN supporting CS and PS services using GPRS. It shows the interconnections between various network elements: + +- PSTN** (Packet Switched Network) connects to **CS-MGW** (Circuit Switched Media Gateway). +- CS-MGW** connects to **GMSC server** (Gateway MSC server) via **Mc** interface. +- GMSC server** connects to **PCRF** (PDN Gateway Control Function) via **Rx** interface. +- PCRF** connects to **GGSN** (PDN Gateway) via **Gx** interface. +- GGSN** connects to **HSS (HLR,AuC)** (Home Subscriber Server / Home Location Register, Authentication Center) via **Gn** interface. +- HSS (HLR,AuC)** connects to **EIR** (Equipment Identity Register) via **Gr** interface. +- EIR** connects to **SGSN** (Serving GPRS Support Node) via **Gf** interface. +- SGSN** connects to **HSS (HLR,AuC)** via **Gc** interface. +- SGSN** connects to **VLR** (Visitor Location Register) via **Gs** interface. +- VLR** connects to **MSC server** via **Nb** interface. +- MSC server** connects to **CS-MGW** via **Mc** interface. +- CS-MGW** connects to **BSS** (Base Station System) via **A** interface. +- BSS** contains **BSC** (Base Station Controller) and **BTS** (Base Transceiver Station). +- BSC** connects to **BTS** via **Abis** interface. +- BSC** connects to **SGSN** via **IuPS** interface. +- BSC** connects to **CS-MGW** via **IuCS** interface. +- RNS** (Radio Network Subsystem) contains **RNC** (Radio Network Controller) and **Node B** (cell). +- RNC** connects to **Node B** via **Iub** interface. +- RNC** connects to **SGSN** via **IuPS** interface. +- RNC** connects to **CS-MGW** via **IuCS** interface. +- RNC** connects to another **RNC** via **Iur** interface. +- MS** (Mobile Station) contains **ME** (Mobile Equipment) and **SIM** (Subscriber Identity Module) or **USIM** (Universal Subscriber Identity Module). +- ME** connects to **SIM** or **USIM** via **SIM-ME i/f** or **Cu** interface. +- ME** connects to **BTS** via **Um** interface. +- ME** connects to **Node B** via **Uu** interface. + +**Legend:** + +- Bold lines: interfaces supporting user traffic; +- Dashed lines: interfaces supporting signalling. + +**NOTE 1:** The figure shows direct interconnections between the entities. The actual links may be provided by an underlying network (e.g. SS7 or IP): this needs further studies. + +**NOTE 2:** When the MSC and the SGSN are integrated in a single physical entity, this entity is called UMTS MSC (UMSC). + +**NOTE 3:** A (G)MSC server and associated CS-MGW can be implemented as a single node: the (G)MSC. + +**NOTE 4:** The Gn interface (between two SGSNs) is also part of the reference architecture, but is not shown for layout purposes only. + +Figure 1: Basic Configuration of a PLMN supporting CS and PS services (using GPRS) and interfaces. The diagram shows the network architecture including PSTN, CS-MGW, GMSC server, PCRF, GGSN, HSS (HLR,AuC), EIR, VLR, MSC server, SGSN, BSS (BSC, BTS), RNS (RNC, Node B), and MS (ME, SIM/USIM). Interfaces are labeled with letters like PSTN, Rx, Gi, Gp, Mc, Nb, Ne, C, Gc, Gn, Gr, Gf, Gs, A, Gb, IuCS, IuPS, Iur, Abis, Iub, Um, and Uu. Bold lines represent user traffic interfaces, and dashed lines represent signalling interfaces. + +**Figure 1: Basic Configuration of a PLMN supporting CS and PS services (using GPRS) and interfaces** + +![Diagram showing the configuration for Short Message Service (SMS) with components: SMS-GMSC/SMS-IWMSC, MSC-Server, HSS (HLR), SGSN, and MME connected via interfaces E, S6c/C, Gd, and SGd.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` +graph TD; SMS[\"SMS-GMSC/ SMS-IWMSC\"] ---|E| MSC[\"MSC-Server\"]; SMS ---|S6c/C| HSS[\"HSS (HLR)\"]; SMS ---|Gd| SGSN[\"SGSN\"]; SMS ---|SGd| MME[\"MME\"]; +``` + +Diagram showing the configuration for Short Message Service (SMS) with components: SMS-GMSC/SMS-IWMSC, MSC-Server, HSS (HLR), SGSN, and MME connected via interfaces E, S6c/C, Gd, and SGd. + +**Figure 1a: Configuration for Short Message Service** + +![A complex network architecture diagram showing the interconnections between various 3GPP network elements. The diagram is divided into three main sections: Core Network (CN), Radio Access Network (RAN), and User Equipment (UE). The CN includes elements like CS-MGW, GMSC server, PCRF, GGSN, PDN-GW, S-GW, MME, HSS (HLR, AuC), EIR, and SGSN. The RAN includes BSS (BSC, BTS) and RNS (RNC, Node B). The UE includes ME, SIM, and USIM. Interfaces are labeled with letters (e.g., G, F, D, X, S) and standardized reference points (e.g., S1, S5, S8, X2). Blue lines represent EPS functions and reference points. The diagram also shows connections to external networks like PSTN and GPRS.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +The diagram illustrates the basic configuration of a 3GPP Access PLMN supporting CS and PS services. It shows the following components and interfaces: + +- Core Network (CN):** + - CS-MGW:** Connected to PSTN and MSC server. + - GMSC server:** Connected to PSTN and HSS. + - PCRF:** Connected to GGSN and HSS. + - GGSN:** Connected to PDN-GW and HSS. + - PDN-GW:** Connected to S-GW and external networks. + - S-GW:** Connected to PDN-GW, MME, and SGSN. + - MME:** Connected to S-GW, SGSN, and RAN. + - HSS (HLR, AuC):** Connected to GMSC server, PCRF, GGSN, and SGSN. + - EIR:** Connected to HSS and SGSN. + - SGSN:** Connected to S-GW, MME, and RAN. +- Radio Access Network (RAN):** + - BSS:** Contains BSC and BTS. BSC is connected to CS-MGW and SGSN. + - RNS:** Contains RNC and Node B. RNC is connected to SGSN and MME. +- User Equipment (UE):** + - ME:** Connected to SIM or USIM and eNB. + - SIM / USIM:** Connected to ME. + - eNB:** Part of E-UTRAN, connected to ME and other eNBs. +- Interfaces:** + - Blue lines:** Represent EPS functions and reference points (e.g., S1, S5, S8, X2). + - Other lines:** Represent CS and PS service interfaces (e.g., G, F, D, X, S). + +A complex network architecture diagram showing the interconnections between various 3GPP network elements. The diagram is divided into three main sections: Core Network (CN), Radio Access Network (RAN), and User Equipment (UE). The CN includes elements like CS-MGW, GMSC server, PCRF, GGSN, PDN-GW, S-GW, MME, HSS (HLR, AuC), EIR, and SGSN. The RAN includes BSS (BSC, BTS) and RNS (RNC, Node B). The UE includes ME, SIM, and USIM. Interfaces are labeled with letters (e.g., G, F, D, X, S) and standardized reference points (e.g., S1, S5, S8, X2). Blue lines represent EPS functions and reference points. The diagram also shows connections to external networks like PSTN and GPRS. + +NOTE: The interfaces in blue represent EPS functions and reference points. + +Figure 1b: Basic Configuration of a 3GPP Access PLMN supporting CS and PS services (using GPRS and EPS) and interfaces + +## 5.2 Configuration of LCS entities + +### 5.2.1 Configuration of LCS entities for GERAN + +The configuration of LCS entities for GERAN is presented in figure 2. In the figure, all the functions are considered implemented in different logical nodes. If two logical nodes are implemented in the same physical equipment, the relevant interfaces may become internal to that equipment. + +![Figure 2: Configuration of LCS entities for a GERAN PLMN. The diagram shows the internal structure of a GERAN (BSS, BTS, BSC, LMUs) and its external connections to a core network (MSCs, SGSNs, HSS, GMLC, SCS) and an external LCS client.](753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg) + +The diagram illustrates the configuration of LCS entities for a GERAN PLMN. On the left, the **GERAN** (GSM Edge Radio Access Network) is shown, containing a **BSS** (Base Station Subsystem) which includes a **BTS** (Base Transceiver Station) and a **BSC** (Base Station Controller). The **BTS** is connected to an **MS** (Mobile Station) via the **Um** interface. The **BTS** also contains a **Type B LMU** (Location Management Unit). The **BSC** is connected to the **BTS** via the **Abis** interface. The **BSC** also contains a **Type A LMU**. The **BSC** is connected to the **GERAN** via the **Lb** interface. The **GERAN** also contains a **SMLC** (Serving Mobile Location Center) and a **CBC** (CBC). The **SMLC** is connected to the **BSC** via the **Lp** interface. The **CBC** is connected to the **BSC** via the **CBC-BSC** interface. The **GERAN** is connected to the **core network** via the **Lu** interface. The **core network** includes a **3G MSC/MSC Server**, a **3G SGSN**, a **2G MSC**, and a **2G SGSN**. The **3G MSC/MSC Server** is connected to the **3G SGSN** via the **Lg** interface. The **3G SGSN** is connected to the **2G MSC** via the **Lg** interface. The **2G MSC** is connected to the **2G SGSN** via the **Lg** interface. The **2G SGSN** is connected to the **HSS** (Home Subscriber Server) via the **Lh** interface. The **HSS** is connected to the **GMLC** (Gateway Mobile Location Center) via the **Lr** interface. The **GMLC** is connected to the **OSA SCS** (OSA Service Capability Server) via the **Lc** interface. The **OSA SCS** is connected to the **External LCS Client** via the **Le** interface. The **OSA SCS** also has a **Proprietary** interface to the **gsmSCF** (gsmSCF). The **gsmSCF** is connected to the **External LCS Client** via the **OSA API** interface. The **External LCS Client** also has a **Proprietary** interface to the **GMLC**. + +**Note 1:** HSS includes both 2G-HLR and 3G-HLR functionality. + +**Note 2:** As one alternative the LCS client may get location information directly from GMLC, which may contain OSA Mobility SCS with support for the OSA user location interfaces. + +Figure 2: Configuration of LCS entities for a GERAN PLMN. The diagram shows the internal structure of a GERAN (BSS, BTS, BSC, LMUs) and its external connections to a core network (MSCs, SGSNs, HSS, GMLC, SCS) and an external LCS client. + +Figure 2: Configuration of LCS entities for a GERAN PLMN + +## 5.2.2 Configuration of LCS entities for UTRAN + +The basic configuration of UTRAN LCS is presented in figure 3. The SMLC functionality is integrated in SRNC or, in case a Stand-Alone SMLC entity (SAS) is present, split between SRNC and SMLC. + +![Figure 3: Configuration of LCS entities for a UTRAN PLMN. The diagram shows the internal structure of a UTRAN (RNC, RNS) and its external connections to a core network (3G MSC/ MSC server, 3G SGSN, GMLC, HSS) and external clients (gsmSCF, OSA SCS, External LCS client).](aeb2a26a07219661191294dba528067a_img.jpg) + +The diagram illustrates the configuration of LCS entities for a UTRAN PLMN. On the left, the **UTRAN** contains an **RNC** connected to an **RNS**. The **RNS** includes a **Stand-Alone SMLC (SAS)**, an **SRNC (SMLC functionality)**, and a **Node B** (containing an **Associated LMU** and **cell**). The **SRNC** is connected to the **RNC** via the **Iur** interface. The **SRNC** is also connected to the **Node B** via the **Iub** interface. The **SRNC** is connected to the **3G MSC/ MSC server** via the **Iu-cs** interface and to the **3G SGSN** via the **Iu-ps** interface. The **Node B** is connected to the **UE** and a **Stand-Alone LMU** via the **Uu** interface. The **SRNC** is also connected to the **Stand-Alone SMLC (SAS)** via the **Iu-pc** interface, which is marked with **\*Note 3**. The **3G MSC/ MSC server** is connected to the **GMLC** via the **Lg** interface. The **3G SGSN** is also connected to the **GMLC** via the **Lg** interface. The **GMLC** is connected to the **HSS** via the **Lh** interface, which is marked with **\*Note 1**. The **GMLC** is also connected to the **gsmSCF** via the **Lc** interface and to the **OSA SCS** via the **Lr** interface. The **gsmSCF** is connected to the **OSA SCS** via a **Proprietary** interface, which is marked with **\*Note 2**. The **OSA SCS** is connected to an **External LCS client** via the **Le** interface. The **External LCS client** is also connected to the **GMLC** via the **Lr** interface. + +**Note 1:** The HSS includes both 2G-HLR and 3G HLR functionality. + +**Note 2:** As one alternative the LCS client may get location information directly from GMLC, which may contain OSA Mobility SCS with support for the OSA user location interfaces. + +**Note 3:** The SMLC may be either a stand-alone network element (SAS) or an internal function of the RNC. + +Figure 3: Configuration of LCS entities for a UTRAN PLMN. The diagram shows the internal structure of a UTRAN (RNC, RNS) and its external connections to a core network (3G MSC/ MSC server, 3G SGSN, GMLC, HSS) and external clients (gsmSCF, OSA SCS, External LCS client). + +Figure 3: Configuration of LCS entities for a UTRAN PLMN + +## 5.2.3 Configuration of LCS entities for E-UTRAN + +The basic configuration of E-UTRAN LCS is presented in figure 3a. + +![Configuration of LCS entities for an E-UTRAN PLMN diagram](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +This diagram illustrates the configuration of LCS entities for an E-UTRAN PLMN. It shows a UE connected to an E-UTRAN via an LTE-Uu interface. The E-UTRAN is connected to an MME via an S1 interface. The MME is connected to an E-SMLC via an SLs interface and to a GMLC via an SLg interface. The GMLC is connected to an External LCS Client via an Le interface and to an HSS via an SLh interface. + +Configuration of LCS entities for an E-UTRAN PLMN diagram + +Figure 3a: Configuration of LCS entities for an E-UTRAN PLMN + +### 5.3 Configuration of CAMEL entities + +The following figure shows the interconnection of the CAMEL-specific entities with the rest of the network. Only the interfaces specifically involved in CAMEL provisioning are shown, i.e. all the GMSC, MSC, SGSN and HLR interfaces depicted in figure 1 are still supported by these entities even if not shown. CAMEL is not supported for E-UTRAN access. + +NOTE: Most CAMEL-specific interfaces have no particular name. They are designated by the name of the two entities they link together, e.g. "the gsmSSF-gsmSCF interface". + +![Configuration of CAMEL entities diagram](c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg) + +This diagram illustrates the configuration of CAMEL entities. At the top, a GMSC is connected to a gsmSSF. The gsmSSF is connected to a gsmSCF. The gsmSCF is connected to an HLR. The HLR is connected to a gprsSSF. The gprsSSF is connected to an SGSN. The gsmSCF is also connected to a gsmSRF. The gsmSRF is connected to an MSC. The MSC is connected to a VLR. The VLR is connected to a gsmSSF. The gsmSSF is connected to the MSC. The gsmSCF is connected to the HLR via a Ge interface. The HLR is connected to the gprsSSF via a D interface. The gprsSSF is connected to the SGSN via a Gr interface. The gsmSRF is connected to the MSC via a B interface. The gsmSSF is connected to the gsmSCF via a C interface. + +Configuration of CAMEL entities diagram + +Figure 4: configuration of CAMEL entities + +The bold lines are used for interfaces supporting user data only, the dashed lines are used for interfaces supporting signalling only. + +## 5.4 Configuration of CBS entities + +![Diagram showing the configuration of CBS entities for GERAN/UTRAN. A Core Network (CN) contains a CBC (Cell Broadcast Center). The CBC is connected via a dashed line (signalling) to a BSC (Base Station Controller) in a BSS (Base Station System) and via a solid line (user data) to an RNC (Radio Network Controller) in an RNS (Radio Network System). The BSC is connected to two BTS (Base Transceiver Station) units via dashed lines. The RNC is connected to two Node B units via dashed lines. One Node B is connected to a UE (User Equipment) via a solid line.](508bc574df81fa8d3027a374f6d155fc_img.jpg) + +Diagram showing the configuration of CBS entities for GERAN/UTRAN. A Core Network (CN) contains a CBC (Cell Broadcast Center). The CBC is connected via a dashed line (signalling) to a BSC (Base Station Controller) in a BSS (Base Station System) and via a solid line (user data) to an RNC (Radio Network Controller) in an RNS (Radio Network System). The BSC is connected to two BTS (Base Transceiver Station) units via dashed lines. The RNC is connected to two Node B units via dashed lines. One Node B is connected to a UE (User Equipment) via a solid line. + +Figure 5: Configuration of a PLMN supporting Cell Broadcast Service entities for GERAN/UTRAN + +![Diagram showing the Warning System Architecture for E-UTRAN Access. A UE (User Equipment) is connected to an E-UTRAN (Evolved UTRAN) via the E-UTRAN-Uu interface. The E-UTRAN is connected to an MME (Mobility Management Entity) via the S1-MME interface. The MME is connected to a CBC (Cell Broadcast Center) via the SBc interface. The CBC is connected to a CBE (Cell Broadcast Entity) via an interface that is out of scope of 3GPP specifications.](db5deafdae53dbc7d5972957f708c691_img.jpg) + +Diagram showing the Warning System Architecture for E-UTRAN Access. A UE (User Equipment) is connected to an E-UTRAN (Evolved UTRAN) via the E-UTRAN-Uu interface. The E-UTRAN is connected to an MME (Mobility Management Entity) via the S1-MME interface. The MME is connected to a CBC (Cell Broadcast Center) via the SBc interface. The CBC is connected to a CBE (Cell Broadcast Entity) via an interface that is out of scope of 3GPP specifications. + +Figure 4.2.3-1: Warning System Architecture for E-UTRAN Access + +NOTE: The CBE and the interface between CBE and CBC are out of scope of 3GPP specifications. + +## 5.5 Configuration of IM CN Subsystem entities + +### 5.5.1 IM CN Subsystem functional entities + +The configuration of IM CN Subsystem entities is presented in figure 6. In the figure, all the functions are considered implemented in different logical nodes. If two logical nodes are implemented in the same physical equipment, the relevant interfaces may become internal to that equipment. + +Only the interfaces specifically linked to the IM subsystem are shown, i.e. all the SGSN, GGSN and HSS interfaces depicted in figure 1 are still supported by these entities even if not shown. + +![Figure 6: Configuration of IM Subsystem entities. This is a complex architectural diagram showing the interconnections between various network elements. At the top, 'IP Multimedia Networks' are shown. Below them, the diagram is divided into three main vertical sections: 'CS Network' on the left, 'Legacy mobile signalling Networks' in the center, and 'LCS Client' on the right. The 'CS Network' section includes interfaces Mb, CS, and Mn. The 'Legacy mobile signalling Networks' section contains entities like BGCF, IMS-MGW, MRFP, MRFC, P-CSCF, IBCF, TrGW, and UE, connected by various interfaces such as Mk, Mg, Mj, Mi, Mw, Cx, Dx, ISC, Rc, I4, Ix, Iz, and Ut. The 'LCS Client' section includes LRF, E-CSCF, and BGCF, connected via interfaces Le, Mm, and MI. Solid lines represent user traffic interfaces, while dashed lines represent signalling interfaces.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +Figure 6: Configuration of IM Subsystem entities. This is a complex architectural diagram showing the interconnections between various network elements. At the top, 'IP Multimedia Networks' are shown. Below them, the diagram is divided into three main vertical sections: 'CS Network' on the left, 'Legacy mobile signalling Networks' in the center, and 'LCS Client' on the right. The 'CS Network' section includes interfaces Mb, CS, and Mn. The 'Legacy mobile signalling Networks' section contains entities like BGCF, IMS-MGW, MRFP, MRFC, P-CSCF, IBCF, TrGW, and UE, connected by various interfaces such as Mk, Mg, Mj, Mi, Mw, Cx, Dx, ISC, Rc, I4, Ix, Iz, and Ut. The 'LCS Client' section includes LRF, E-CSCF, and BGCF, connected via interfaces Le, Mm, and MI. Solid lines represent user traffic interfaces, while dashed lines represent signalling interfaces. + +**Legend:** + +**Bold lines:** interfaces supporting user traffic; + +**Dashed lines:** interfaces supporting only signalling. + +NOTE 1: The reference point CS (Circuit Switched) is not specified in this specification. + +NOTE 2: The reference point I5 is not shown in this figure. + +**Figure 6: Configuration of IM Subsystem entities** + +### 5.5.2 IM CN Subsystem Service layer + +The figure below depicts an overall view of the functional architecture for services. + +![Figure 6a: Functional architecture for the provision of service in the IMS. The diagram shows a SIP Application Server at the top containing 'LAS' and 'SCIM' components. It connects via an 'ISC' interface to an 'S-CSCF' block. The 'S-CSCF' is also connected to an 'HSS' via a 'Cx' interface, an 'IM-SSF' via an 'ISC' interface, and an 'OSA service capability server (SCS)' via an 'ISC' interface. The 'HSS' connects to the 'SIP Application Server' via an 'Sh' interface and to the 'IM-SSF' via 'Si' and 'MAP' interfaces. The 'IM-SSF' connects to a 'Camel Service Environment' via a 'CAP' interface. The 'OSA service capability server (SCS)' connects to an 'OSA application server' via an 'OSA API'. A large dashed box encloses the SIP Application Server, HSS, S-CSCF, and IM-SSF.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Figure 6a: Functional architecture for the provision of service in the IMS. The diagram shows a SIP Application Server at the top containing 'LAS' and 'SCIM' components. It connects via an 'ISC' interface to an 'S-CSCF' block. The 'S-CSCF' is also connected to an 'HSS' via a 'Cx' interface, an 'IM-SSF' via an 'ISC' interface, and an 'OSA service capability server (SCS)' via an 'ISC' interface. The 'HSS' connects to the 'SIP Application Server' via an 'Sh' interface and to the 'IM-SSF' via 'Si' and 'MAP' interfaces. The 'IM-SSF' connects to a 'Camel Service Environment' via a 'CAP' interface. The 'OSA service capability server (SCS)' connects to an 'OSA application server' via an 'OSA API'. A large dashed box encloses the SIP Application Server, HSS, S-CSCF, and IM-SSF. + +**Figure 6a: Functional architecture for the provision of service in the IMS** + +The purpose of the IM SSF is to host the CAMEL network features (i.e. trigger detection points, CAMEL Service Switching Finite State Machine, etc.) and to interwork with CAP. + +The IM SSF and the CAP interface support legacy services only. + +The application server may contain "service capability interaction manager" (SCIM) functionality and other application servers. The SCIM functionality is an application which performs the role of interaction management. The internal components are represented by the "dotted boxes" inside the SIP application server. The internal structure of the application server is outside the standards. The Sh interface shall have sufficient functionality to enable this scenario. + +The figure below depicts an overall view of the functional architecture for enabling the management of the user's service related information via the Ut interface. + +![Figure 6b: Functional architecture for the management of the user's service related information. The diagram shows a vertical stack of components: 'SIP Application Server' at the top, 'HSS' in the middle, and 'S-CSCF' at the bottom. A 'UE' block is to the left. The 'UE' connects to the 'SIP Application Server' via a 'Ut' interface. The 'SIP Application Server' connects to the 'HSS' via an 'Sh' interface and to the 'S-CSCF' via an 'ISC' interface. The 'HSS' connects to the 'S-CSCF' via a 'Cx' interface.](90df9788d66ecf65abf861caf76be5ca_img.jpg) + +Figure 6b: Functional architecture for the management of the user's service related information. The diagram shows a vertical stack of components: 'SIP Application Server' at the top, 'HSS' in the middle, and 'S-CSCF' at the bottom. A 'UE' block is to the left. The 'UE' connects to the 'SIP Application Server' via a 'Ut' interface. The 'SIP Application Server' connects to the 'HSS' via an 'Sh' interface and to the 'S-CSCF' via an 'ISC' interface. The 'HSS' connects to the 'S-CSCF' via a 'Cx' interface. + +**Figure 6b: Functional architecture for the management of the user's service related information** + +The figure below depicts an overall view of the functional architecture for routing SIP requests between I-CSCF and Application Server. + +![Figure 6c: Functional architecture for the routing of SIP requests between I-CSCF and AS](7ed5d5770331f31ade15439a21c31425_img.jpg) + +A vertical diagram showing two rectangular boxes connected by a single vertical line. The top box is labeled 'Application Server' and the bottom box is labeled 'I-CSCF'. The connection line has a small horizontal tick mark and is labeled 'Ma'. + +Figure 6c: Functional architecture for the routing of SIP requests between I-CSCF and AS + +**Figure 6c: Functional architecture for the routing of SIP requests between I-CSCF and AS** + +### 5.5.3 Service Centralization and Continuity + +Figure 6d depicts an overall view of the functional architecture for IMS services centralization and continuity. + +![Figure 6d: Functional architecture for IMS Service Centralization and Continuity](d7948c38a18636aefecdd95388196460_img.jpg) + +A complex functional architecture diagram. On the far left is a vertical box labeled 'UE'. To its right are three horizontal lines labeled 'I1', 'Gm', and 'A/lu'. 'I1' connects to a box labeled 'SCC AS'. 'Gm' connects to a box labeled 'CSCF'. 'A/lu' connects to a box labeled 'CS Access'. From 'CS Access', a line labeled 'A/lu' connects to a box labeled 'MSC Server'. Above 'MSC Server' is a box labeled 'TAS', connected by a line labeled 'I3'. To the right of 'MSC Server' is a box labeled 'CS-MGW', connected by a line labeled 'Mc'. Between 'SCC AS' and 'CSCF' is a line labeled 'ISC'. Between 'CSCF' and 'MSC Server' is a line labeled 'I2'. + +Figure 6d: Functional architecture for IMS Service Centralization and Continuity + +**Figure 6d: Functional architecture for IMS Service Centralization and Continuity** + +IMS Service Centralization, defined in TS 23.292 [110] provides communication services such that all services, and service control, are based on IMS mechanisms and enablers. It enables IMS services when using CS access as bearer for the media. + +IMS Service Continuity, defined in TS 23.237 [111] provides Session Transfer mechanisms to maintain service continuity in the event of access transfer for the case when such events are not hidden from the IMS session layer and thus service continuity could not otherwise be maintained. + +Figure 6e provides the reference architecture for SRVCC using the ATCF enhancements as defined in TS 23.237 [111]. The ATCF enhancements provide Session Transfer mechanisms in the serving network to maintain service continuity in the event of access transfer for SRVCC. + +![Figure 6e: IMS Service Centralization and Continuity Reference Architecture when using ATCF enhancements. The diagram shows a vertical stack of IMS components: SCC AS at the top, connected to I/S-CSCF via ISC. I/S-CSCF is connected to ATCF* via Mw/Mx. ATCF* is connected to ATGW* and to MSC Server via Mw/I2**. ATCF* is also connected to P-CSCF via Mw/Mx. On the left, UE is connected to P-CSCF via Gm, and UE is also connected to CS Access, which is connected to MSC Server.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +graph TD + SCCAS[SCC AS] -- ISC --> ISCSCF[I/S-CSCF] + ISCSCF -- Mw/Mx --> ATCF["ATCF*"] + ATCF -- Mw/I2** --> MSCServer[MSC Server] + ATCF -- " " --> ATGW["ATGW*"] + UE[UE] -- Gm --> PCSCF[P-CSCF] + PCSCF -- Mw/Mx --> ATCF + UE -- " " --> CSAccess[CS Access] + CSAccess -- " " --> MSCServer + +``` + +Figure 6e: IMS Service Centralization and Continuity Reference Architecture when using ATCF enhancements. The diagram shows a vertical stack of IMS components: SCC AS at the top, connected to I/S-CSCF via ISC. I/S-CSCF is connected to ATCF\* via Mw/Mx. ATCF\* is connected to ATGW\* and to MSC Server via Mw/I2\*\*. ATCF\* is also connected to P-CSCF via Mw/Mx. On the left, UE is connected to P-CSCF via Gm, and UE is also connected to CS Access, which is connected to MSC Server. + +\*: Location of functionality depends on deployment and collocation scenario + +\*\*: Reference point dependent on MSC Server capability. + +**Figure 6e: IMS Service Centralization and Continuity Reference Architecture when using ATCF enhancements** + +If neither the MSC Server is not enhanced for ICS, the interface between MSC Server and ATCF is Mw. + +If the MSC Server is enhanced for ICS, the interface between MSC Server and ATCF is I2. + +## 5.6 Configuration of Signalling Gateway Function + +The Signalling gateway function is used to interconnect different signalling networks i.e. SCTP/IP based signalling networks and SS7 signalling networks. The application layer (e.g. ISUP, BICC, MAP or CAP) is not affected. The signalling gateway function may be implemented as a stand alone entity or inside another entity. + +![Figure 7: Configuration of a signalling gateway function. The diagram shows a central SGW box connected to two cloud-like networks. On the left, an 'IP Signalling transport NW' is connected to the SGW via an 'SCTP/IP' interface. On the right, an 'SS7 Signalling transport NW' is connected to the SGW via an 'MTP' interface.](3263a25e110201638bda790456af2909_img.jpg) + +``` + +graph LR + IPNW((IP Signalling transport NW)) -- SCTP/IP --> SGW[SGW] + SGW -- MTP --> SS7NW((SS7 Signalling transport NW)) + +``` + +Figure 7: Configuration of a signalling gateway function. The diagram shows a central SGW box connected to two cloud-like networks. On the left, an 'IP Signalling transport NW' is connected to the SGW via an 'SCTP/IP' interface. On the right, an 'SS7 Signalling transport NW' is connected to the SGW via an 'MTP' interface. + +**Figure 7: Configuration of a signalling gateway function** + +NOTE: SS7 application transport and SCTP/IP adaption protocols are not shown. + +## 5.7 Configuration of 3GPP/WLAN Interworking + +The configuration of the 3GPP/WLAN interworking function is presented in figure 8. The figure shows all network entities and reference point for the roaming scenario when a WLAN UE accesses PS based services in the home network. PS based services in the visited network are accessed via a Packet Data Gateway in the visited 3GPP network. Reference point Ww between WLAN UE and WLAN is outside the scope of 3GPP and only shown for completeness. + +![Figure 8: Configuration of a 3GPP/WLAN interworking function. The diagram shows a WLAN UE connected to a WLAN Access Network, which is connected to an Intranet/Internet. The WLAN Access Network is also connected to a WAG (WLAN Access Gateway). The WAG is connected to a 3GPP Visited Network via the Wn reference point. Inside the 3GPP Visited Network, the WAG connects to a 3GPP AAA Proxy via the Wg reference point. The 3GPP AAA Proxy connects to a CGw/CCF via the Wf reference point. The 3GPP AAA Proxy also connects to a 3GPP AAA Server in the 3GPP Home Network via the Wd reference point. The 3GPP AAA Server connects to an HSS via the Wx reference point, to an HLR via the Dx/Gx reference point, to an OCS via the Wo reference point, and to a CGw/CCF via the Wf reference point. The WAG also connects to a Packet Data Gateway via the Wp reference point. The Packet Data Gateway connects to the 3GPP AAA Server via the Wm reference point and to the 3GPP Home Network via the Wi reference point. The WLAN UE also connects directly to the Packet Data Gateway via the Wu reference point.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +Figure 8: Configuration of a 3GPP/WLAN interworking function. The diagram shows a WLAN UE connected to a WLAN Access Network, which is connected to an Intranet/Internet. The WLAN Access Network is also connected to a WAG (WLAN Access Gateway). The WAG is connected to a 3GPP Visited Network via the Wn reference point. Inside the 3GPP Visited Network, the WAG connects to a 3GPP AAA Proxy via the Wg reference point. The 3GPP AAA Proxy connects to a CGw/CCF via the Wf reference point. The 3GPP AAA Proxy also connects to a 3GPP AAA Server in the 3GPP Home Network via the Wd reference point. The 3GPP AAA Server connects to an HSS via the Wx reference point, to an HLR via the Dx/Gx reference point, to an OCS via the Wo reference point, and to a CGw/CCF via the Wf reference point. The WAG also connects to a Packet Data Gateway via the Wp reference point. The Packet Data Gateway connects to the 3GPP AAA Server via the Wm reference point and to the 3GPP Home Network via the Wi reference point. The WLAN UE also connects directly to the Packet Data Gateway via the Wu reference point. + +Figure 8: Configuration of a 3GPP/WLAN interworking function + +### 5.8 Configuration of Presence service + +The reference architecture model, the reference points and the functional entities to support the Presence Service are described in TS 23.141 [68]. + +### 5.9 Configuration of MBMS entities + +The configuration of the MBMS entities for GPRS and EPS is represented in figures 9 and 9a respectively. MBMS for GPRS supports UTRAN and GERAN. MBMS for EPS supports E-UTRAN and UTRAN. + +![Figure 9: Configuration of MBMS entities for GPRS. This diagram shows the network architecture for GPRS. On the left, two User Equipment (UE) units are connected to UTRAN and GERAN respectively. Both radio access networks connect to an SGSN via 'lu' interfaces. The SGSN is connected to an HLR via a 'Gr' interface and to a GGSN TPF via 'Gn/Gp' and 'Gmc' interfaces. The GGSN TPF connects to a BM-SC via 'Gmb' and 'Gi' interfaces. The BM-SC is connected to a Content Provider / Multicast Broadcast Source and also to an 'Other PLMN' (represented by an oval) via 'Gi' and 'Mz' interfaces. A dashed vertical line on the right separates the PLMN from the PDN (e.g., Internet).](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +Figure 9: Configuration of MBMS entities for GPRS. This diagram shows the network architecture for GPRS. On the left, two User Equipment (UE) units are connected to UTRAN and GERAN respectively. Both radio access networks connect to an SGSN via 'lu' interfaces. The SGSN is connected to an HLR via a 'Gr' interface and to a GGSN TPF via 'Gn/Gp' and 'Gmc' interfaces. The GGSN TPF connects to a BM-SC via 'Gmb' and 'Gi' interfaces. The BM-SC is connected to a Content Provider / Multicast Broadcast Source and also to an 'Other PLMN' (represented by an oval) via 'Gi' and 'Mz' interfaces. A dashed vertical line on the right separates the PLMN from the PDN (e.g., Internet). + +Figure 9: Configuration of MBMS entities for GPRS + +![Figure 9a: Configuration of MBMS entities for Evolved Packet System. This diagram shows the network architecture for the Evolved Packet System (EPS). Two User Equipment (UE) units are connected to E-UTRAN and UTRAN respectively. The E-UTRAN connects to an MME via an 'E-UTRAN Uu' interface. The MME connects to an MBMS GW via 'M3' and 'Sm' interfaces. The UTRAN connects to an SGSN via a 'Uu' interface, which in turn connects to the MBMS GW via an 'lu' interface. The MBMS GW connects to a PDN Gateway via 'Sn' and 'SGmb' interfaces. The PDN Gateway connects to a BM-SC via an 'SGi' interface. The BM-SC is connected to a Content Provider via an 'SGi-mb' interface.](848073118eebfdbfdb9a60e3923fe0b3_img.jpg) + +Figure 9a: Configuration of MBMS entities for Evolved Packet System. This diagram shows the network architecture for the Evolved Packet System (EPS). Two User Equipment (UE) units are connected to E-UTRAN and UTRAN respectively. The E-UTRAN connects to an MME via an 'E-UTRAN Uu' interface. The MME connects to an MBMS GW via 'M3' and 'Sm' interfaces. The UTRAN connects to an SGSN via a 'Uu' interface, which in turn connects to the MBMS GW via an 'lu' interface. The MBMS GW connects to a PDN Gateway via 'Sn' and 'SGmb' interfaces. The PDN Gateway connects to a BM-SC via an 'SGi' interface. The BM-SC is connected to a Content Provider via an 'SGi-mb' interface. + +Figure 9a: Configuration of MBMS entities for Evolved Packet System + +NOTE: The MCE (Multi-cell/Multicast Coordination Entity) is not shown in the figure. See TS 36.300 [78]. + +## 5.10 Configuration of Short Message Service over generic 3GPP Internet Protocol access (SMSIP) entities + +The configuration of the Short Message Service over generic 3GPP Internet Protocol access (SMSIP) entities are represented in figure 10. + +![Figure 10: Configuration of SMSIP entities. This is a block diagram showing the architecture for SMSIP. At the top is the SME (Short Message Entity) connected to the SC (Service Center). The SC is connected to the SMS-GMSC/SMS-IWMSC. The SMS-GMSC/SMS-IWMSC is connected to the CGF/CDF (Charging Function/Charging Data Function) via an Rf interface, to the IP-SM-GW (IP Session Management Gateway) via an E / Gd interface, and to the HSS (Home Subscriber Server) via a C interface. The IP-SM-GW is connected to the OCS (Online Charging System) via an Ro interface, to the CSCF (CSCF) via an ISC interface, and to the HSS via Sh and J interfaces. The CSCF is connected to the UE (User Equipment) via a Gm interface. The HSS is also connected to the CSCF via a Cx interface.](68a5a1a1a761c652b4b4c56da7cf9914_img.jpg) + +``` + +graph TD + SME[SME] --> SC[SC] + SC --> SMSGMSC[SMS-GMSC/SMS-IWMSC] + SMSGMSC -- Rf --> CGFCDF[CGF/CDF] + SMSGMSC -- E / Gd --> IPSMGW[IP-SM-GW] + SMSGMSC -- C --> HSS[HSS] + IPSMGW -- Ro --> OCS[OCS] + IPSMGW -- ISC --> CSCF[CSCF] + IPSMGW -- Sh --> HSS + IPSMGW -- J --> HSS + CSCF -- Gm --> UE[UE] + HSS -- Cx --> CSCF + +``` + +Figure 10: Configuration of SMSIP entities. This is a block diagram showing the architecture for SMSIP. At the top is the SME (Short Message Entity) connected to the SC (Service Center). The SC is connected to the SMS-GMSC/SMS-IWMSC. The SMS-GMSC/SMS-IWMSC is connected to the CGF/CDF (Charging Function/Charging Data Function) via an Rf interface, to the IP-SM-GW (IP Session Management Gateway) via an E / Gd interface, and to the HSS (Home Subscriber Server) via a C interface. The IP-SM-GW is connected to the OCS (Online Charging System) via an Ro interface, to the CSCF (CSCF) via an ISC interface, and to the HSS via Sh and J interfaces. The CSCF is connected to the UE (User Equipment) via a Gm interface. The HSS is also connected to the CSCF via a Cx interface. + +Figure 10: Configuration of SMSIP entities + +## 5.11 Configuration of Policy Control and Charging entities + +The PCC functionality is comprised by the functions of the Policy and Charging Enforcement Function (PCEF), the Bearer Binding and Event Reporting Function (BBERF), the Policy and Charging Rules Function (PCRF), the Application Function (AF), the Online Charging System (OCS), the Offline Charging System (OFC), the Traffic Detection Function (TDF) and the Subscription Profile Repository (SPR) or the User Data Repository (UDR). Figures 5.11-1 through to 5.11-4 describe the non-roaming and roaming architecture for PCC. + +The PCC architecture extends the architecture of an IP-CAN, where the Policy and Charging Enforcement Function is a functional entity in the Gateway node implementing the IP access to the PDN. The allocation of the Bearer Binding and Event Reporting Function is specific to each IP-CAN type and specified in the TS 23.203 [73]. + +PCC function makes it possible to apply policy and charging control to any kind of 3GPP IP CAN and any non-3GPP accesses connected via EPC complying with TS 23.402 [77]. Applicability of PCC to other IP CAN is not restricted; however, it shall be possible for the PCC architecture to base decisions upon the type of IP CAN used (e.g. GPRS, I-WLAN, etc.). Support for policy control and charging when local breakout and roaming are applied as specified in TS 23.401 [76] and TS 23.402 [77] is supported. + +![Overall PCC logical architecture (non-roaming) when SPR is used](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +This diagram illustrates the overall PCC logical architecture when the Subscription Profile Repository (SPR) is used. A dashed line on the left delineates the 'Fixed Broadband Access NW'. Inside this network, the BPCF and HNB-GW are connected to the central Policy and Charging Rules Function (PCRF) via the S15 interface. The PCRF is connected to the SPR via the Sp interface, to the AF via the Rx interface, and to the Online Charging System (OCS) via the Sy interface. The PCRF also connects to the BBERF via the Gxx interface, to the TDF via the Sd interface, and to the PDN GW via the Gx interface. The PDN GW contains a PCEF, which is connected to the Offline Charging System (OFCS) via the Gy and Gz interfaces. The OCS is also connected to the OFCS. + +Overall PCC logical architecture (non-roaming) when SPR is used + +Figure 5.11-1: Overall PCC logical architecture (non-roaming) when SPR is used + +![Overall PCC logical architecture (non-roaming) when UDR is used](3c04b14104f95eb8f7100f6d497d956e_img.jpg) + +This diagram illustrates the overall PCC logical architecture when the User Data Repository (UDR) is used. Similar to the previous diagram, a dashed line on the left delineates the 'Fixed Broadband Access NW'. Inside this network, the BPCF and HNB-GW are connected to the central Policy and Charging Rules Function (PCRF) via the S15 interface. The PCRF is connected to the UDR via the Ud interface, to the AF via the Rx interface, and to the Online Charging System (OCS) via the Sy interface. The PCRF also connects to the BBERF via the Gxx interface, to the TDF via the Sd interface, and to the PDN GW via the Gx interface. The PDN GW contains a PCEF, which is connected to the Offline Charging System (OFCS) via the Gy and Gz interfaces. The OCS is also connected to the OFCS. + +Overall PCC logical architecture (non-roaming) when UDR is used + +Figure 5.11-2: Overall PCC logical architecture (non-roaming) when UDR is used + +![Overall PCC architecture diagram showing connections between SPR, AF, OCS, H-PCRF, V-PCRF, BPCF, HNB-GW, BBERF, TDF, PCEF, PDN GW, and OFCS with various interfaces like Sp, Rx, S9, S15, Gx, Gy, Gz, Sd, and S9a.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +The diagram illustrates the Overall PCC architecture for roaming with home routed access when SPR is used. It shows the following components and interfaces: + +- Subscription Profile Repository (SPR)**: Located in the HPLMN, it connects to the H-PCRF via the **Sp** interface. +- AF (Application Function)**: Connects to the H-PCRF via the **Rx** interface. +- Online Charging System (OCS)**: Connects to the H-PCRF via the **Sy** interface and to the PCEF via the **Gy** interface. +- Policy and Charging Rules Function (H-PCRF)**: The central element in the HPLMN, it connects to the SPR (Sp), AF (Rx), OCS (Sy), TDF (Sd), PCEF (Gx), and V-PCRF (S9). +- Policy and Charging Rules Function (V-PCRF)**: Located in the VPLMN, it connects to the H-PCRF (S9), BPCF (S9a), HNB-GW (S15), and BBERF (Gxx). +- BPCF (Bearing Control Function)**: Located in the Fixed Broadband Access Network, it connects to the V-PCRF via the **S9a** interface. +- HNB-GW (Home NodeB Gateway)**: Connects to the V-PCRF via the **S15** interface. +- BBRF (Bearer Binding and Resource Function)**: Connects to the HNB-GW via the **Gxx** interface. +- TDF (Traffic Detection Function)**: Connects to the H-PCRF via the **Sd** interface. +- PDN GW (PDN Gateway)**: Contains the **PCEF (PDN Connection and Enforcement Function)**. The PCEF connects to the H-PCRF (Gx), OCS (Gy), and OFCS (Gz). +- Offline Charging System (OFCS)**: Connects to the PCEF via the **Gz** interface. + +The diagram is divided into three main areas by dashed lines: **HPLMN** (Home PLMN), **VPLMN** (Visited PLMN), and **Fixed Broadband Access Network**. + +Overall PCC architecture diagram showing connections between SPR, AF, OCS, H-PCRF, V-PCRF, BPCF, HNB-GW, BBERF, TDF, PCEF, PDN GW, and OFCS with various interfaces like Sp, Rx, S9, S15, Gx, Gy, Gz, Sd, and S9a. + +Figure 5.11-3: Overall PCC architecture (roaming with home routed access) when SPR is used + +![Overall PCC architecture for roaming with PCEF in visited network (local breakout) when SPR is used. The diagram shows various network functions and their interfaces across different domains: VPLMN, HPLMN, and Fixed Broadband Access Network. Key components include AF, SPR, H-PCRF, V-PCRF, BPCF, HNB-GW, BBERF, TDF, PDN GW, PCEF, OCS, and OFCS. Interfaces are labeled with names like Sp, Rx, Sy, S9, S9a, S15, Gxx, Sd, Gx, Gy, and Gz.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +The diagram illustrates the overall PCC architecture for roaming with PCEF in a visited network (local breakout) when SPR is used. It is divided into three main domains: VPLMN (Visited Packet Core Network), HPLMN (Home Packet Core Network), and Fixed Broadband Access Network. The components and their interfaces are as follows: + +- HPLMN:** + - Subscription Profile Repository (SPR)** connects to **H-PCRF** via the **Sp** interface. + - AF** (Application Function) connects to **H-PCRF** via the **Rx** interface. +- VPLMN:** + - AF** connects to **V-PCRF** via the **Rx** interface. + - V-PCRF** connects to **H-PCRF** via the **S9** interface. + - V-PCRF** connects to **OCS** via the **Sy** interface. + - BPCF** (Bearing Control Function) connects to **V-PCRF** via the **S9a** interface. + - HNB-GW** (Home NodeB Gateway) connects to **V-PCRF** via the **S15** interface. + - HNB-GW** connects to **BBERF** via the **Gxx** interface. + - HNB-GW** connects to **TDF** via the **Sd** interface. + - HNB-GW** connects to **PDN GW** via the **Gx** interface. + - PDN GW** contains a **PCEF** (PDN Connection and Enforcement Function). + - PCEF** connects to **OCS** via the **Gy** interface. + - PCEF** connects to **OFCS** via the **Gz** interface. +- Fixed Broadband Access Network:** + - Contains **BPCF** which connects to **V-PCRF** via the **S9a** interface. + +Overall PCC architecture for roaming with PCEF in visited network (local breakout) when SPR is used. The diagram shows various network functions and their interfaces across different domains: VPLMN, HPLMN, and Fixed Broadband Access Network. Key components include AF, SPR, H-PCRF, V-PCRF, BPCF, HNB-GW, BBERF, TDF, PDN GW, PCEF, OCS, and OFCS. Interfaces are labeled with names like Sp, Rx, Sy, S9, S9a, S15, Gxx, Sd, Gx, Gy, and Gz. + +Figure 5.11-4: Overall PCC architecture for roaming with PCEF in visited network (local breakout) when SPR is used + +## 5.12 Configuration of CSFB(CS Fallback) + +The CS fallback in EPS enables the provisioning of voice and other CS-domain services (e.g. CS UDI video/ SMS/ LCS/ USSD) by reuse of CS infrastructure when the UE is served by E-UTRAN. This function is only available in case E-UTRAN coverage is overlapped by either GERAN coverage or UTRAN coverage. + +The configurations of the CSFB entities are represented in figure 5.12. + +![Figure 5.12: Configuration of CSFB. This diagram shows the network architecture for Circuit Switched Fallback (CSFB). A User Equipment (UE) is connected to an E-UTRAN via an E-UTRAN-Uu interface. The E-UTRAN is connected to an MME via an S1-MME interface. The MME is connected to an MSC/VLR via an SGs interface. The MSC/VLR is connected to both a UTRAN and a GERAN via Iu-CS and A interfaces, respectively. The UE also has direct connections to the UTRAN (Uu) and GERAN (Um) for fallback purposes.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +Figure 5.12: Configuration of CSFB. This diagram shows the network architecture for Circuit Switched Fallback (CSFB). A User Equipment (UE) is connected to an E-UTRAN via an E-UTRAN-Uu interface. The E-UTRAN is connected to an MME via an S1-MME interface. The MME is connected to an MSC/VLR via an SGs interface. The MSC/VLR is connected to both a UTRAN and a GERAN via Iu-CS and A interfaces, respectively. The UE also has direct connections to the UTRAN (Uu) and GERAN (Um) for fallback purposes. + +Figure 5.12: Configuration of CSFB + +NOTE: The MGW is not shown in the figure 5.12 since the CS fallback in EPS does not have any impacts to the User plane handling. + +## 5.13 Configuration of Single Radio Voice Call Continuity (SRVCC) + +### 5.13.1 E-UTRAN/UTRAN (HSPA) to UTRAN or GERAN SRVCC architecture + +Single Radio Voice Call Continuity (PS to CS) refers to continuity between IMS over PS access and CS calls that are anchored in IMS when the UE is capable of transmitting/receiving on only one of those access networks at a given time. PS to CS SRVCC is specified in TS 23.216 [83]. The following figures 5.13, 5.13a and 5.13b show the entities involved in PS to CS SRVCC. + +![Figure 5.13: SRVCC architecture for E-UTRAN to 3GPP UTRAN/GERAN. This diagram illustrates the SRVCC architecture. At the bottom, a UE is connected to an E-UTRAN via an E-UTRAN-Uu interface. The E-UTRAN is connected to an MME via an S1-MME interface and to a Serving/PDN GW via an S1-U interface. The MME is connected to an HSS via an S6a interface and to an MSC Server via an Sv interface. The Serving/PDN GW is connected to the 3GPP IMS via an SGi interface. The MSC Server is connected to a Target UTRAN/GERAN via an Iu-cs/A interface and to an SGSN via an Iu-ps/Gb interface. The SGSN is connected to the MME via an S3 interface. An arrow on the left indicates the flow of a call from the UE through the E-UTRAN, MME, and MSC Server to the Target UTRAN/GERAN.](921458d4fc1b778c2450592ac9745b48_img.jpg) + +Figure 5.13: SRVCC architecture for E-UTRAN to 3GPP UTRAN/GERAN. This diagram illustrates the SRVCC architecture. At the bottom, a UE is connected to an E-UTRAN via an E-UTRAN-Uu interface. The E-UTRAN is connected to an MME via an S1-MME interface and to a Serving/PDN GW via an S1-U interface. The MME is connected to an HSS via an S6a interface and to an MSC Server via an Sv interface. The Serving/PDN GW is connected to the 3GPP IMS via an SGi interface. The MSC Server is connected to a Target UTRAN/GERAN via an Iu-cs/A interface and to an SGSN via an Iu-ps/Gb interface. The SGSN is connected to the MME via an S3 interface. An arrow on the left indicates the flow of a call from the UE through the E-UTRAN, MME, and MSC Server to the Target UTRAN/GERAN. + +Figure 5.13: SRVCC architecture for E-UTRAN to 3GPP UTRAN/GERAN + +![Figure 5.13a: SRVCC architecture for UTRAN (HSPA) to 3GPP UTRAN/GERAN with Gn based SGSN. The diagram shows two User Equipment (UE) units. The top UE is connected to a Target UTRAN/GERAN via Um/Uu, which is then connected to an MSC Server via lu-cs/A. The bottom UE is connected to a UTRAN (HSPA) via Uu, which is connected to an SGSN via lu-ps. This SGSN is connected to another SGSN via Gn. The second SGSN is connected to an HSS via Gr and to a GGSN via Gn. The GGSN is connected to the 3GPP IMS via Gi. The MSC Server is connected to the 3GPP IMS via Sv. There is also a connection from the Target UTRAN/GERAN to the first SGSN via lu-ps/Gb.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +Figure 5.13a: SRVCC architecture for UTRAN (HSPA) to 3GPP UTRAN/GERAN with Gn based SGSN. The diagram shows two User Equipment (UE) units. The top UE is connected to a Target UTRAN/GERAN via Um/Uu, which is then connected to an MSC Server via lu-cs/A. The bottom UE is connected to a UTRAN (HSPA) via Uu, which is connected to an SGSN via lu-ps. This SGSN is connected to another SGSN via Gn. The second SGSN is connected to an HSS via Gr and to a GGSN via Gn. The GGSN is connected to the 3GPP IMS via Gi. The MSC Server is connected to the 3GPP IMS via Sv. There is also a connection from the Target UTRAN/GERAN to the first SGSN via lu-ps/Gb. + +**Figure 5.13a: SRVCC architecture for UTRAN (HSPA) to 3GPP UTRAN/GERAN with Gn based SGSN** + +![Figure 5.13b: PS to CS SRVCC architecture for UTRAN (HSPA) to 3GPP UTRAN/GERAN with S4 based SGSN. The diagram shows two User Equipment (UE) units. The top UE is connected to a Target UTRAN/GERAN via Um/Uu, which is then connected to an MSC Server via lu-cs/A. The bottom UE is connected to a UTRAN (HSPA) via Uu, which is connected to a Serving/PDN GW via S12. The Serving/PDN GW is connected to the 3GPP IMS via SGi and to an SGSN via S4. This SGSN is connected to another SGSN via S16. The second SGSN is connected to an HSS via Gr. The MSC Server is connected to the 3GPP IMS via Sv. There is also a connection from the Target UTRAN/GERAN to the first SGSN via lu-ps/Gb.](74d23510f27b21403a7be84820821863_img.jpg) + +Figure 5.13b: PS to CS SRVCC architecture for UTRAN (HSPA) to 3GPP UTRAN/GERAN with S4 based SGSN. The diagram shows two User Equipment (UE) units. The top UE is connected to a Target UTRAN/GERAN via Um/Uu, which is then connected to an MSC Server via lu-cs/A. The bottom UE is connected to a UTRAN (HSPA) via Uu, which is connected to a Serving/PDN GW via S12. The Serving/PDN GW is connected to the 3GPP IMS via SGi and to an SGSN via S4. This SGSN is connected to another SGSN via S16. The second SGSN is connected to an HSS via Gr. The MSC Server is connected to the 3GPP IMS via Sv. There is also a connection from the Target UTRAN/GERAN to the first SGSN via lu-ps/Gb. + +**Figure 5.13b: PS to CS SRVCC architecture for UTRAN (HSPA) to 3GPP UTRAN/GERAN with S4 based SGSN** + +NOTE 1: The above figures only show the necessary components related to MSC Server enhanced with SRVCC. + +NOTE 2: MSC Server shown in the above figures are enhanced for SRVCC. + +NOTE 3: This architecture also applies to roaming scenario (i.e., S8, S6a are not impacted due to SRVCC). + +NOTE 4: The MSC Server enhanced with SRVCC may not be the final target MSC which connects to the target cell. + +## 5.13.2 UTRAN/GERAN to E-UTRAN or UTRAN (HSPA) SRVCC architecture + +CS to PS Single Radio Voice Call Continuity refers to continuity between a CS call and IMS call over PS access that are anchored in IMS when the UE is capable of transmitting/receiving on only one of those access networks at a given time. CS to PS SRVCC is specified in TS 23.216 [83]. The following figures 5.13c, 5.13d and 5.13e show the entities involved in CS to PS SRVCC. + +![Figure 5.13c: CS to PS SRVCC architecture for UTRAN/GERAN to E-UTRAN. The diagram shows a UE connected to UTRAN/GERAN, which is connected to an MSC Server and an SGSN. The MSC Server is connected to an IMS and an MME. The MME is connected to an HSS and a Serving/PDN GW. The Serving/PDN GW is connected to the IMS. The diagram illustrates the bearer and signaling paths before and after a handover from UTRAN/GERAN to E-UTRAN. A legend indicates: solid line for bearer path before HO, dashed line for bearer path after HO, and dash-dot line for SIP signaling path after HO.](5801c19431e76330430e92a598cc7a16_img.jpg) + +Figure 5.13c: CS to PS SRVCC architecture for UTRAN/GERAN to E-UTRAN. The diagram shows a UE connected to UTRAN/GERAN, which is connected to an MSC Server and an SGSN. The MSC Server is connected to an IMS and an MME. The MME is connected to an HSS and a Serving/PDN GW. The Serving/PDN GW is connected to the IMS. The diagram illustrates the bearer and signaling paths before and after a handover from UTRAN/GERAN to E-UTRAN. A legend indicates: solid line for bearer path before HO, dashed line for bearer path after HO, and dash-dot line for SIP signaling path after HO. + +- NOTE 1: The above figure only shows the necessary components related to MSC Server enhanced for CS to PS SRVCC. +- NOTE 2: MSC Server shown in the figure is enhanced for CS to PS SRVCC. +- NOTE 3: This architecture also applies to roaming scenario (i.e. S8, S6a are not impacted due to CS to PS SRVCC). + +**Figure 5.13c: CS to PS SRVCC architecture for UTRAN/GERAN to E-UTRAN** + +![Figure 5.13d: CS to PS SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with Gn based SGSN. The diagram shows a UE connected to Target UTRAN/GERAN, which is connected to an MSC Server and an SGSN. The MSC Server is connected to an IMS. The Target UTRAN/GERAN is also connected to an SGSN via a Gn interface. This SGSN is connected to an HSS and a GGSN. The GGSN is connected to the IMS. The diagram illustrates the bearer and signaling paths before and after a handover from Target UTRAN/GERAN to UTRAN (HSPA).](9e26cd5584f423e1b2155fb341db579f_img.jpg) + +Figure 5.13d: CS to PS SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with Gn based SGSN. The diagram shows a UE connected to Target UTRAN/GERAN, which is connected to an MSC Server and an SGSN. The MSC Server is connected to an IMS. The Target UTRAN/GERAN is also connected to an SGSN via a Gn interface. This SGSN is connected to an HSS and a GGSN. The GGSN is connected to the IMS. The diagram illustrates the bearer and signaling paths before and after a handover from Target UTRAN/GERAN to UTRAN (HSPA). + +**Figure 5.13d: CS to PS SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with Gn based SGSN** + +![Figure 5.13e: CS to PS SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with S4 based SGSN. The diagram shows two User Equipment (UE) units. The top UE is connected to a Target UTRAN/GERAN via Um/Uu. The Target UTRAN/GERAN is connected to an MSC Server via lu-cs/A and to an SGSN via lu-ps/Gb. The MSC Server is connected to the IMS via a direct line, to an HSS via S6d, and to a Serving/PDN GW via Sv. The Target UTRAN/GERAN is also connected to the Serving/PDN GW via S16. The bottom UE is connected to a UTRAN (HSPA) via Uu. The UTRAN (HSPA) is connected to the Serving/PDN GW via S12. The Serving/PDN GW is connected to the IMS via SGi and to the HSS via S4. A large downward arrow is on the left side of the diagram.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +Figure 5.13e: CS to PS SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with S4 based SGSN. The diagram shows two User Equipment (UE) units. The top UE is connected to a Target UTRAN/GERAN via Um/Uu. The Target UTRAN/GERAN is connected to an MSC Server via lu-cs/A and to an SGSN via lu-ps/Gb. The MSC Server is connected to the IMS via a direct line, to an HSS via S6d, and to a Serving/PDN GW via Sv. The Target UTRAN/GERAN is also connected to the Serving/PDN GW via S16. The bottom UE is connected to a UTRAN (HSPA) via Uu. The UTRAN (HSPA) is connected to the Serving/PDN GW via S12. The Serving/PDN GW is connected to the IMS via SGi and to the HSS via S4. A large downward arrow is on the left side of the diagram. + +NOTE 1: The above figures only show the necessary components related to MSC Server enhanced with CS to PS SRVCC. + +NOTE 2: MSC Server shown in the above figures are enhanced for CS to PS SRVCC. + +NOTE 3: This architecture also applies to roaming scenario. + +**Figure 5.13e: CS to PS SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with S4 based SGSN** + +## 5.14 Configuration of Security + +The reference architecture model, the reference points and the functional entities to support and provide security related functions to the users, devices and network entities when in the UTRAN access as well as using IMS are described in TS 33.1xx series and TS 33.2xx series. + +The reference architecture model, the reference points and the functional entities to support security functions to the users, devices and network entities when in the EPC are described in TS 33.401 [87] for 3GPP access and in TS 33.402 [88] for non-3GPP accesses. + +## 5.15 Configuration of Lawful Intercept related entities + +The general configuration for Lawful Interception is shown in figure 5.15. The definition of the LI functional entities and interfaces is provided in TS 33.107 [84]. + +The reference configuration is only a logical representation of the entities involved in lawful interception and does not mandate separate physical entities. There is one Administration Function (ADMF) in the network. Every physical Intercepting Control Element (ICE) is linked by its own X1\_1-interface to the ADMF. Consequently, every single ICE performs interception (activation, deactivation, interrogation as well as invocation) independently from other ICEs. + +![Figure 5.15: General Lawful Interception Architecture diagram. On the left, a stack of three boxes represents the LEMF (Lawful Interception Management Function). To its right are three horizontal boxes representing HI1, HI2, and HI3 interfaces. HI1 contains 'Mediation Function' and 'ADMF'. HI2 contains 'Mediation Function' and 'Delivery Function 2'. HI3 contains 'Mediation Function' and 'Delivery Function 3'. On the far right is a box for 'Intercepting Control Element'. Arrows show data flow from X1_1, X1_2, X1_3, X2, and X3 points to the Intercepting Control Element.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +The diagram illustrates the General Lawful Interception Architecture. On the left, a stack of three boxes represents the LEMF (Lawful Interception Management Function). To its right are three horizontal boxes representing HI1, HI2, and HI3 interfaces. HI1 contains 'Mediation Function' and 'ADMF'. HI2 contains 'Mediation Function' and 'Delivery Function 2'. HI3 contains 'Mediation Function' and 'Delivery Function 3'. On the far right is a box for 'Intercepting Control Element'. Arrows show data flow from X1\_1, X1\_2, X1\_3, X2, and X3 points to the Intercepting Control Element. + +Figure 5.15: General Lawful Interception Architecture diagram. On the left, a stack of three boxes represents the LEMF (Lawful Interception Management Function). To its right are three horizontal boxes representing HI1, HI2, and HI3 interfaces. HI1 contains 'Mediation Function' and 'ADMF'. HI2 contains 'Mediation Function' and 'Delivery Function 2'. HI3 contains 'Mediation Function' and 'Delivery Function 3'. On the far right is a box for 'Intercepting Control Element'. Arrows show data flow from X1\_1, X1\_2, X1\_3, X2, and X3 points to the Intercepting Control Element. + +**Figure 5.15: General Lawful Interception Architecture** + +## 5.16 Configuration of Charging related entities + +The general configuration for common charging architecture for 3GPP defined entities is shown in figure 5.16 as defined in TS 32.240 [85]. This common charging architecture provides a logical view and the actual domain / service / subsystem specific charging architecture depends on the domain / service / subsystem in question. The physical mapping of the common logical architecture onto each domain, subsystem or service is described in the respective charging TS, i.e. the TSs 32.25x, 32.26x and 32.27x number range. + +3GPP networks provide functions that implement offline and/or online charging mechanisms on the bearer (e.g. EPC), subsystem (e.g. IMS) and service (e.g. MMS) levels. In order to support these charging mechanisms, the network performs real-time monitoring of resource usage on the above three levels in order to detect the relevant chargeable events. + +In offline charging, the resource usage is reported from the network to the Billing Domain after the resource usage has occurred. In online charging, a subscriber account, located in an Online Charging System, is queried prior to granting permission to use the requested network resource(s). + +Offline and online charging may be performed simultaneously and independently for the same chargeable event. + +![Figure 5.16: Logical ubiquitous charging architecture diagram. The diagram shows a central stack of network elements: CS-NE, Service-NE, SIP AS, MRFC, a group containing MGCF, BGCF, IBCF, P-CSCF, and I-CSCF, S-CSCF, IMS-GWF, WLAN, SGSN, S-GW, and P-GW (with PCEF). These are connected to a Billing Domain at the top, a CGF and CDF on the left, and an OCS on the right. Below the P-GW is a PCRF connected to an AF. Two dashed boxes labeled 'OFFLINE CHARGING' and 'ONLINE CHARGING' enclose different parts of the stack, with lines indicating data flow to the Billing Domain and OCS.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +Figure 5.16: Logical ubiquitous charging architecture diagram. The diagram shows a central stack of network elements: CS-NE, Service-NE, SIP AS, MRFC, a group containing MGCF, BGCF, IBCF, P-CSCF, and I-CSCF, S-CSCF, IMS-GWF, WLAN, SGSN, S-GW, and P-GW (with PCEF). These are connected to a Billing Domain at the top, a CGF and CDF on the left, and an OCS on the right. Below the P-GW is a PCRF connected to an AF. Two dashed boxes labeled 'OFFLINE CHARGING' and 'ONLINE CHARGING' enclose different parts of the stack, with lines indicating data flow to the Billing Domain and OCS. + +Figure 5.16: Logical ubiquitous charging architecture + +## 5.17 Configuration of Home (e)NodeB entities + +### 5.17.1 Configuration of the Home NodeB Subsystem + +The configuration of the Home NodeB Subsystem is presented in figure 5.17-1. In the figure, all the functions are considered implemented in different logical nodes. If two logical nodes are implemented in the same physical equipment, the relevant interfaces may become internal to that equipment. + +The Home NodeB Gateway may also be used only for the control plane of Iu-CS and/or Iu-PS interfaces. In this case, the user plane of Iu-CS and/or Iu-PS interfaces is directly between the Home NodeB and respectively the MSC/VLR and the SGSN/Serving GW/GGSN. + +In case Direct Tunnel is established, the user plane is directly between the Home NodeB Subsystem and the GGSN or Serving GW nodes. + +![Diagram of PLMN configuration supporting Home NodeB Subsystem.](5e9af8986a5845504f251d3079da8078_img.jpg) + +The diagram illustrates the network architecture for a PLMN supporting a Home NodeB Subsystem (HNS). + - A **UE** (User Equipment) connects to a **Home Node B** via the **Uu** interface. + - The **Home Node B** connects to a **Home Node B Gateway** via the **Iuh** interface. + - Both the Home Node B and the Home Node B Gateway are enclosed in a dashed box labeled **Home Node B Subsystem (HNS)**. + - A dashed line labeled **Uh(OMA DM/OTA)** connects the UE directly to the Home Network boundary. + - The Home Node B Gateway connects to an **MSC/VLR** via the **Iu-CS** interface and to an **SGSN** via the **Iu-PS** interface. + - The **MSC/VLR** and **SGSN** both connect to an **HSS (HLR, AuC)** via the **D** and **Gr/S6d** interfaces respectively. + - The **HSS (HLR, AuC)** and a **CSG list Server** are enclosed in a dashed box labeled **Located in the Home Network**. + - In a separate dashed box labeled **Located in the Visited Network**, there is a **CSS** node. + - The **MSC/VLR** and **SGSN** connect to the **CSS** via the **Ghv/S7d** interface. + - The **HSS** connects to the **CSS** via the **Hv** interface. + +Diagram of PLMN configuration supporting Home NodeB Subsystem. + +**Figure 5.17-1: Configuration of PLMN supporting Home NodeB Subsystem** + +### 5.17.2 Configuration of the Home eNodeB Subsystem + +The configuration of Home eNodeB Subsystem with a Home eNodeB Gateway present is shown in figure 5.17-2. In the figure, all the functions are considered implemented in different logical nodes. If two logical nodes are implemented in the same physical equipment, the relevant interfaces may become internal to that equipment. + +The presence of Home eNodeB Gateway in the configuration of Home eNodeB Subsystem is optional. + +The Home eNodeB Gateway may also be used only for the S1-MME interface. In this case, the S1-U interface is directly between the Home eNodeB and the S-GW. + +![Figure 5.17-2: Configuration of PLMN supporting Home eNodeB Subsystem. The diagram shows a UE connected to a Home eNode B via the LTE-Uu interface. The Home eNode B is part of a Home eNode B Subsystem (HeNS) which also includes an optional Home eNode B Gateway. The HeNS connects to an MME via the S1-MME interface and to an SGW via the S1-U interface. The MME is connected to an HSS (HLR, AuC) via the S6a interface and to the SGW via the S11 interface. The SGW is connected to a CSS via the S7a interface. The UE also has a connection to a UH (OMA DM/OTA) via a dashed line. The HSS is located in the Home Network and contains a CSG list Server. The CSS is located in the Visited Network.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +graph LR + UE[UE] -- LTE-Uu --> HeNS[Home eNode B Subsystem HeNS] + subgraph HeNS + direction TB + HeNS_ENB[Home eNode B] + HeNS_GW[Home eNode B Gateway optional] + end + HeNS_ENB -- S1-MME --> MME[MME] + HeNS_GW -- S1-U --> SGW[SGW] + MME -- S6a --> HSS[HSS HLR AuC] + MME -- S11 --> SGW + SGW -- S7a --> CSS[CSS] + UE -.-> UH[UH OMA DM OTA] + subgraph Home_Network [Located in the Home Network] + CSG[CSG list Server] + HSS + end + subgraph Visited_Network [Located in the Visited Network] + CSS + end + +``` + +Figure 5.17-2: Configuration of PLMN supporting Home eNodeB Subsystem. The diagram shows a UE connected to a Home eNode B via the LTE-Uu interface. The Home eNode B is part of a Home eNode B Subsystem (HeNS) which also includes an optional Home eNode B Gateway. The HeNS connects to an MME via the S1-MME interface and to an SGW via the S1-U interface. The MME is connected to an HSS (HLR, AuC) via the S6a interface and to the SGW via the S11 interface. The SGW is connected to a CSS via the S7a interface. The UE also has a connection to a UH (OMA DM/OTA) via a dashed line. The HSS is located in the Home Network and contains a CSG list Server. The CSS is located in the Visited Network. + +Figure 5.17-2: Configuration of PLMN supporting Home eNodeB Subsystem + +## 5.18 Configuration for facilitating communications with packet data networks and applications + +The reference architecture model, the reference points and the functional entities to facilitate communications with packet data networks and applications are described in TS 23.682 [132]. + +# 6 PLMN basic interfaces and reference points + +The implementation of the mobile service with international roaming implies the exchange of data between the equipment involved in the service. The same No.7 signalling network should be used to transfer these data and the call-related signalling information. + +*Editor's note: either the difference between interface and reference point should be clearly provided, or only one of the terms should be used.* + +## 6.1 Interfaces between Mobile Station and the Fixed Infrastructure + +### 6.1.1 Interface between Mobile Station and Base Station System (Um-interface) + +The interface between the MS and the BSS is specified in the 44- and 45-series of Technical Specifications. + +### 6.1.2 Interface between User Equipment and Radio Network System (Uu-interface) + +The interface between the UE and the RNS is specified in the 24- and 25-series of Technical Specifications. + +### 6.1.3 Interface between User Equipment and Evolved UTRAN (E-UTRAN Uu-interface) + +The interface between the UE and the E-UTRAN is specified in the 36-series of Technical Specifications. + +## 6.2 Interface between the Core Network and the Access Network + +### 6.2.1 Interfaces between the CS domain and the Access Network + +#### 6.2.1.1 Interface between the MSC and Base Station System (A-interface) + +The interface between the MSC and its BSS is specified in the 48-series of Technical Specifications. + +The BSS-MSC interface is used to carry information concerning: + +- BSS management; +- call handling; +- mobility management. + +#### 6.2.1.2 Interface between the MSC and Base Station System (Iu\_CS interface) + +The interface between the MSC and its BSS is specified in the 25.41x-series of Technical Specifications. + +The BSS-MSC interface is used to carry information concerning: + +- BSS management; +- call handling; +- mobility management; + +#### 6.2.1.3 Interface between the MSC and RNS (Iu\_CS interface) + +The interface between the MSC and its RNS is specified in the 25.41x-series of Technical Specifications. + +The RNS-MSC interface is used to carry information concerning: + +- RNS management; +- call handling; +- mobility management. + +### 6.2.2 Interfaces between the PS domain and the Access Network + +#### 6.2.2.1 Interface between SGSN and BSS (Gb-interface) + +The BSS-SGSN interface is used to carry information concerning: + +- packet data transmission; +- mobility management. + +The Gb interface is defined in TS 48.014 [44], TS 48.016 [45] and TS 48.018 [46]. + +#### 6.2.2.2 Interface between SGSN and BSS (Iu\_PS-interface) + +The BSS-SGSN interface is used to carry information concerning: + +- packet data transmission; +- mobility management. + +The Iu\_PS interface is defined in the 25.41x-series of 3GPP Technical Specifications. + +### 6.2.2.3 Interface between SGSN and RNS (Iu\_PS-interface) + +The RNS-SGSN interface is used to carry information concerning: + +- packet data transmission; +- mobility management. + +The Iu\_PS interface is defined in the 25.41x-series of Technical Specifications. + +## 6.2.3 Interfaces between the Evolved Packet Core and the Access Network + +### 6.2.3.1 Interface between MME and E-UTRAN (S1-MME-interface) + +Reference point for the control plane protocol between E-UTRAN and MME. This interface is defined in the TS 36.41x-series of Technical Specifications and in TS 24.301 [89]. + +### 6.2.3.2 Interface between S-GW and E-UTRAN (S1-U-interface) + +Reference point between E-UTRAN and S GW for the per bearer user plane tunnelling. This interface is defined in TS 29.281 [126]. + +## 6.3 Interfaces internal to the Access Network + +### 6.3.1 Interface between BSC and BTS (Abis-interface) + +When the BSS consists of a Base Station Controller (BSC) and one or more Base Transceiver Stations (BTS), this interface is used between the BSC and BTS to support the services offered to the GSM users and subscribers. + +The interface also allows control of the radio equipment and radio frequency allocation in the BTS. + +The interface is specified in the 48.5x-series of Technical Specifications. + +### 6.3.2 Interface between RNC and Node B (Iub-interface) + +When the RNS consists of a Radio Network Controller (RNC) and one or more Node B, this interface is used between the RNC and Node B to support the services offered to the UMTS users and subscribers. + +The interface also allows control of the radio equipment and radio frequency allocation in the Node B. + +The interface is specified in the 25.43x series of Technical Specifications. + +### 6.3.3 Interface between two RNCs (Iur-interface) + +This interface is defined in the 25.42x series of Technical Specifications. + +### 6.3.4 Interface between two eNBs (X2-interface) + +This is a logical interface between two eNBs. Whilst logically representing a point to point link between eNBs, the physical realization need not be a point to point link. This interface is defined in the TS 36.42x-series of Technical Specifications. + +### 6.3.5 Interface between HNB and HNB-GW (Iuh-interface) + +This interface is specified in the TS 25.467 [114], TS 25.468 [115] and TS 25.469 [116]. + +## 6.4 Interfaces internal to the Core Network + +### 6.4.1 Interfaces internal to the CS domain + +#### 6.4.1.1 Interface between the MSC server and its associated VLR (B-interface) + +The VLR is the location and management database for the mobile subscribers roaming in the area controlled by the associated MSC server(s). Whenever the MSC server needs data related to a given mobile station currently located in its area, it interrogates the VLR. When a mobile station initiates a location updating procedure with an MSC server, the MSC server informs its VLR which stores the relevant information. This procedure occurs whenever an MS roams to another location area. Also, when a subscriber activates a specific supplementary service or modifies some data attached to a service, the MSC server informs (via the VLR) the HLR which stores these modifications and updates the VLR if required. + +This interface is internal to the MSC server /VLR; signalling on it is not standardised. + +#### 6.4.1.2 Interface between the HLR and the MSC server (C-interface) + +The Gateway MSC server must interrogate the HLR of the required subscriber to obtain routing information for a call or a short message directed to that subscriber. + +Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (see TS 29.002 [26]). + +For CAMEL purposes, this interface is used as described in TS 23.078 [10c]. It is used e.g. at terminating calls to exchange routing information, subscriber status, location information, subscription information, etc. + +#### 6.4.1.3 Interface between the HLR and the VLR (D-interface) + +This interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to set up or to receive calls within the whole service area. To support this, the location registers have to exchange data. The VLR informs the HLR of the location of a mobile station managed by the latter and provides it (either at location updating or at call set-up) with the roaming number of that station. The HLR sends to the VLR all the data needed to support the service to the mobile subscriber. The HLR then instructs the previous VLR to cancel the location registration of this subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means. + +Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (see TS 29.002 [26]). + +For CAMEL purposes, this interface is used to send the CAMEL related subscriber data to the visited PLMN and for provision of MSRN. The interface is also used for the other purposes described in TS 23.078 [10c], e.g. to retrieve subscriber status and location information of the mobile subscriber or to indicate suppression of announcement for a CAMEL service. + +#### 6.4.1.4 Interface between MSC servers or MSC server and IP-SM-GW (E-interface) + +When a mobile station moves from one MSC area to another during a call, a handover procedure has to be performed in order to continue the communication. For that purpose the MSC servers have to exchange data to initiate and then to realise the operation. + +After the handover operation has been completed, the MSC servers will exchange information to transfer A- or Iu- interface signalling as defined in TS 23.009 [6]. + +When a short message is to be transferred between a Mobile Station and Short Message Service Centre (SC), in either direction, this interface is used to transfer the message between the MSC server serving the Mobile Station and the MSC server which acts as the interface to the SC, or between the IP-SM-GW serving the Mobile Station and the MSC server which acts as the interface to the SC. + +Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (see TS 29.002 [26]). + +#### 6.4.1.5 Interface between MSC server and EIR (F-interface) + +This interface is used between MSC server and EIR to exchange data, in order that the EIR can verify the status of the IMEI retrieved from the Mobile Station. + +Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (see TS 29.002 [26]). + +#### 6.4.1.6 Interface between VLRs (G-interface) + +When a mobile subscriber moves from a VLR area to another Location Registration procedure will happen. This procedure may include the retrieval of the IMSI and authentication parameters from the old VLR. + +Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (see TS 29.002 [26]). + +#### 6.4.1.7 Reference point (G)MSC server – CS-MGW (Mc Reference Point) + +The Mc reference point describes the interfaces between the MSC Server and CS-MGW, and between the GMSC Server and CS-MGW. It has the following properties: + +- full compliance with the H.248 [52] standard, baseline work of which is currently carried out in ITU-T Study Group 16, in conjunction with IETF MEGACO WG. +- flexible connection handling which allows support of different call models and different media processing purposes not restricted to H.323 [54] usage. +- open architecture where extensions/Packages definition work on the interface may be carried out. +- dynamic sharing of MGW physical node resources. A physical MGW can be partitioned into logically separate virtual MGWs/domains consisting of a set of statically allocated Terminations. +- dynamic sharing of transmission resources between the domains as the MGW controls bearers and manage resources according to the H.248 [52] protocols. + +The functionality across the Mc reference point will need to support mobile specific functions such as SRNS relocation/handover and anchoring. It is expected that current H.248/IETF Megaco [52] standard mechanisms can be applied to enable this. + +#### 6.4.1.8 Reference Point MSC Server – GMSC Server (Nc Reference Point) + +Over the Nc reference point, the Network-Network based call control is performed. Examples of this are ISUP or an evolution of ISUP for bearer independent call control (BICC). Different options for signalling transport on Nc shall be possible including IP. + +#### 6.4.1.9 Reference Point CS-MGW – CS-MGW (Nb Reference Point) + +Over the Nb reference point the bearer control and transport are performed. The transport may be RTP/UDP/IP [59], [60] or AAL2 (I.363-2) [57] for transport of user data. Different options for user data transport and bearer control shall be possible on Nb, for example: AAL2/Q.AAL2, STM/none, RTP/H.245 [58], IPBC. + +#### 6.4.1.10 Reference Point between the CSS and the VLR (Hv Reference Point) + +This reference point is used to transfer to the VLR the CSG subscription information stored in the VPLMN for roaming UEs. + +Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (TCAP) (see TS 29.002 [26]). + +### 6.4.2 Interfaces internal to the PS domain (GPRS) + +#### 6.4.2.1 Interface between SGSN and HLR (Gr-interface) + +This interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to transfer packet data within the whole + +service area. The SGSN informs the HLR of the location of a mobile station managed by the latter. The HLR sends to the SGSN all the data needed to support the service to the mobile subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means. + +Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (TCAP) (see TS 29.002 [26]). + +#### 6.4.2.2 Interface between SGSN and GGSN (Gn- and Gp-interface) + +These interfaces are used to support mobility between the SGSN and GGSN. The Gn interface is used when GGSN and SGSN are located inside one PLMN. The Gp-interface is used if GGSN and SGSN are located in different PLMNs. The Gn/Gp interface also includes a part which allows SGSNs to communicate subscriber and user data, when changing SGSN. + +Signalling on this interface uses the User Datagram Protocol, UDP/IP [59]. The Gn/Gp interface is defined in TS 29.060 [51]. + +#### 6.4.2.3 Signalling Path between GGSN and HLR (Gc-interface) + +This optional signalling path may be used by the GGSN to retrieve information about the location and supported services for the mobile subscriber, to be able to activate a packet data network address. + +There are two alternative ways to implement this signalling path: + +- if an SS7 interface is implemented in the GGSN, signalling between the GGSN and the HLR uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (TCAP) (see TS 29.002 [26]); +- if there is *no* SS7 interface in the GGSN, any GSN in the same PLMN and which has an SS7 interface installed can be used as a GTP to MAP protocol converter, thus forming a signalling path between the GGSN and the HLR. + +#### 6.4.2.4 Interface between SGSN and EIR (Gf-interface) + +This interface is used between SGSN and EIR to exchange data, in order that the EIR can verify the status of the IMEI retrieved from the Mobile Station. + +Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (TCAP) (see TS 29.002 [26]). + +#### 6.4.2.5 Reference Point between the CSS and the Gn/Gp SGSN (Ghv Reference Point) + +This reference point is used to transfer to the Gn/Gp SGSN the CSG subscription information stored in the VPLMN for roaming UEs. + +Signalling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities (TCAP) (see TS 29.002 [26]). + +### 6.4.3 Interfaces used by CS and PS domains + +#### 6.4.3.1 Interface between MSC/VLR and SGSN (Gs-interface) for GPRS + +The SGSN may send location information to the MSC/VLR via the optional Gs interface. The SGSN may receive paging requests from the MSC/VLR via the Gs interface. The MSC/VLR may indicate to an SGSN, via the Gs interface, that an MS is engaged in a service handled by the MSC. + +Signalling on this interface uses connectionless SCCP (without TCAP). SCCP Global Title (GT) is used for addressing. The Gs-interface is defined in TS 29.016 [48] and TS 29.018 [49]. + +#### 6.4.3.2 Interface between HLR/HSS and AuC (H-Interface) + +When an HLR/HSS receives a request for authentication and ciphering data for a Mobile Subscriber and it does not hold the requested data, the HLR/HSS requests the data from the AuC. The protocol used to transfer the data over this interface is not standardised. + +#### 6.4.3.3 Interface between SGSN/IP-SM-GW and SMS-GMSC/SMS-IWMSC (Gd-Interface) for GPRS + +This interface is used to transfer short messages between SGSN/IP-SM-GW and SMS-GMSC or SMS-IWMSC over GPRS. Signalling on this interface uses the Mobile Application Part (MAP) (see TS 29.002 [26]). + +#### 6.4.3.4 Interface between MSC/VLR and MME (SGs-interface) for EPC + +The SGs interface is the reference point between the MME and MSC/VLR which is used for the mobility management and paging procedures between EPS and CS domain, and it is based on the Gs interface procedures. + +The SGs interface is used to provide Fallback for Location Services (LCS) and Call Independent Supplementary Services (SS). + +The SGs interface is also used for the delivery of both mobile originating and mobile terminating SMS over EUTRAN in case SMSIP is not used. + +The signalling on this interface uses SCTP. The SGs interface is defined in TS 23.272 [81] and TS 29.118 [82]. + +#### 6.4.3.5 Interface between 3GPP MSC Server and MME or SGSN (Sv-interface) + +The Sv reference point provides SRVCC support for functions like sending Forward Relocation Message between MME or SGSN and 3GPP MSC Server. This interface is specified in TS 29.280 [91]. + +### 6.4.4 Interfaces internal & related to the Evolved Packet Core + +#### 6.4.4.1 Interface between MME and HSS (S6a-interface) + +This interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to transfer packet data within the whole service area. The MME informs the HSS of the location of a mobile station managed by the latter. The HSS sends to the MME all the data needed to support the service to the mobile subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means. + +Signalling on this interface uses Diameter S6a/S6d Application as specified in TS 29.272 [86]. + +#### 6.4.4.2 Interface between SGSN and HSS (S6d-interface) + +This interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to transfer packet data within the whole service area. The SGSN informs the HSS of the location of a mobile station managed by the latter. The HSS sends to the SGSN all the data needed to support the service to the mobile subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means. + +Signalling on this interface uses Diameter S6a/S6d Application as specified in TS 29.272 [86]. + +#### 6.4.4.3 Interface between MME and S-GW (S11-interface) + +This interface is used to support mobility and bearer management between the MME and S-GW. This interface is specified in TS 29.274 [90]. + +#### 6.4.4.4 Interface between MME and MME (S10-interface) + +This interface is used to support user information transfer and MME relocation support between the MMEs. This interface is specified in TS 29.274 [90]. + +#### **6.4.4.5 Interface between S-GW and PDN GW (S5 and S8-interface)** + +These interfaces are between S-GW and PDN GW, provides support for functions for packet data services towards end users during roaming and non-roaming cases (i.e. S8 is the inter PLMN variant of S5). These interfaces are specified in TS 29.274 [90] and TS 29.281 [126] for GTP and TS 29.275 [93] for PMIP. + +#### **6.4.4.6 Interface between MME and EIR (S13-interface)** + +This interface is used between MME and EIR to exchange data, in order that the EIR can verify the status of the IMEI retrieved from the Mobile Station. + +Signalling on this interface uses the Diameter S13 Application. in TS 29.272 [86]. + +#### **6.4.4.7 Interface between MME and SGSN (S3-interface)** + +This interface enables user and bearer information exchange for inter 3GPP access network mobility in idle and/or active state. This interface is specified in TS 29.274 [90]. + +#### **6.4.4.8 Interface between S-GW and SGSN (S4-interface)** + +This interface provides related control and mobility support between GPRS Core and the 3GPP Anchor function of Serving GW. In addition, if Direct Tunnel is not established, it provides the user plane tunnelling. This interface is specified in TS 29.274 [90] and TS 29.281 [126]. + +#### **6.4.4.9 Interface between S-GW and UTRAN (S12-interface)** + +Reference point between UTRAN and Serving GW for user plane tunnelling when Direct Tunnel is established. It is based on the Iu-u/Gn-u reference point using the GTP-U protocol as defined between SGSN and UTRAN or respectively between SGSN and GGSN. Usage of S12 is an operator configuration option. This interface is specified in TS 29.281 [126]. + +#### **6.4.4.10 Interface between Trusted non-3GPP IP Access and S-GW/PDN GW (S2a-interface)** + +It provides the user plane with related control and mobility support between trusted non 3GPP IP access and the Gateway. This interface is specified in TS 29.275 [93] and TS 24.304 [94] for PMIP and Client Mobile IPv4 FA mode respectively. When GTP is used in S2a, this interface is specified in TS 29.274 [90] for GTP control plane (GTP-C) and in TS 29.281 [126] for GTP user plane (GTP-U). + +#### **6.4.4.11 Interface between PDN GW/S-GW and ePDG (S2b-interface)** + +It provides the user plane with related control and mobility support between ePDG and the Gateway. This interface is specified in TS 29.274 [90] and TS 29.281 [126] for GTP and in TS 29.275 [93] for PMIP. + +#### **6.4.4.12 Interface between PDN GW and UE (S2c-interface)** + +It provides the user plane with related control and mobility support between UE and the Gateway. This reference point is implemented over trusted and/or untrusted non-3GPP Access and/or 3GPP access. This interface is specified in TS 24.303 [95]. + +#### **6.4.4.13 Interface between PDN GW and 3GPP AAA Server/proxy (S6b-interface)** + +It is the reference point between PDN GW and 3GPP AAA server/proxy for mobility related authentication and authorization. This reference point may also be used to retrieve and request storage of mobility parameters, such as the PDN GW Identity. This reference point may also be used to retrieve static QoS profile for a UE for non-3GPP access in case dynamic PCC is not supported. This interface is specified in TS 29.273 [96]. + +#### **6.4.4.14 Interface between Untrusted non-3GPP IP Access and 3GPP AAA Server/proxy (SWa-interface)** + +It enables support for the Untrusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and transports access authentication, authorization and charging-related information in a secure manner. This interface is specified in TS 29.273 [96]. + +#### **6.4.4.15 Interface between Trusted non-3GPP IP Access and 3GPP AAA Server/proxy (STa-interface)** + +It connects the Trusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and transports access authentication, authorization, mobility parameters and charging-related information in a secure manner. This interface is specified in TS 29.273 [96]. + +#### **6.4.4.16 Interface between 3GPP AAA Server and 3GPP AAA proxy (SWd-interface)** + +It connects the 3GPP AAA Proxy, possibly via intermediate networks, to the 3GPP AAA Server. This interface is specified in TS 29.273 [96]. + +#### **6.4.4.17 Interface between ePDG and 3GPP AAA Server/proxy (SWm-interface)** + +This reference point is located between 3GPP AAA Server/Proxy and ePDG and is used for AAA signalling (transport of mobility parameters, tunnel authentication and authorization data). This reference point also includes the MAG-AAA interface functionality and Mobile IPv6 NAS-AAA interface functionality. This interface is specified in TS 29.273 [96]. + +#### **6.4.4.18 Interface between ePDG and Untrusted non-3GPP Access (SWn-interface)** + +This is the reference point between the Untrusted Non-3GPP IP Access and the ePDG. Traffic on this interface for a UE-initiated tunnel has to be forced towards ePDG. This interface is specified in TS 29.273 [96]. + +#### **6.4.4.19 Interface between ePDG and UE (SWu-interface)** + +This is the reference point between the UE and the ePDG and supports handling of IPSec tunnels. The functionality of SWu includes UE-initiated tunnel establishment, user data packet transmission within the IPSec tunnel and tear down of the tunnel and support for fast update of IPSec tunnels during handover between two untrusted non-3GPP IP accesses. This interface is specified in TS 24.302 [97]. + +#### **6.4.4.20 Interface between HSS and 3GPP AAA Server (SWx-interface)** + +This reference point is located between 3GPP AAA Server and HSS and is used for transport of authentication data. This interface is specified in TS 29.273 [96]. + +#### **6.4.4.21 Interface between UE and ANDSF (S14-interface)** + +This reference point is between UE and ANDSF for direct queries via pull mechanism. It enables dynamic provision of information to the UE for Network discovery and selection procedures related to non-3GPP accesses. Push and/or combination of Pull-Push may be supported as well. This interface is specified in TS 24.302 [97]. + +#### **6.4.4.22 Reference point between HRDP AN and MME (S101-reference point)** + +The S101 interface supports procedures for Pre-Registration, Session Maintenance and Active handovers between E-UTRAN and HRPD networks. This is based on tunnelling over S101 signalling of one technology while the UE is in the other technology as specified in TS 23.402 [77]. The HRPD air interface messages tunnelled over S101 in E-UTRAN to HRPD mobility are defined in 3GPP2 C.S0087-0 [107]. + +#### **6.4.4.23 Reference point between 3GPP2 1xCS IWS and MME (S102-reference point)** + +The S102 reference point provides a tunnel between MME and 3GPP2 1xCS IWS to relay 3GPP2 1xCS signalling messages in order to support SRVCC as specified in TS 23.216 [83] and CS Fallback as specified in TS 23.272 [81]. 1x CS signalling messages are those messages that are defined for A2I interface as described in 3GPP2 A.S0008-C [106]. + +In case of CS Fallback to 1x CS network as specified in TS 23.272 [81], S102 Tunnel Redirection Procedure is used when the UE perform Tracking Area Update with MME change (as specified in TS 23.402 [77] in case of S101 tunnel redirection) while the UE is registered with the 1xRTT CS domain and the S102 session exists between the MME and the 1xCS IWS. + +#### 6.4.4.24 Interface between HSGW and S-GW (S103-interface) + +The S103 interface between the Serving GW and HRPD PDSN HSGW supports the forwarding of DL data during mobility from E-UTRAN to HRPD as specified in TS 23.402 [77]. Signalling procedures on the S101 interface are used to set up tunnels on the S103 interface. + +#### 6.4.4.25 Reference point between UE and CSG List Server (Uh reference point) + +This reference point is used to provision the Allowed CSG list and the Operator CSG list subscription information to the mobile station via OMA DM or OTA. This interface is specified in TS 24.285 [117] for OMA DM and in TS 31.102 [118] for OTA. + +#### 6.4.4.26 Reference Point between the CSS and the S4-SGSN (S7d Reference Point) + +This reference point is used to transfer to the S4-SGSN the CSG subscription information stored in the VPLMN for roaming UEs. + +Signalling on this interface uses Diameter S7d Application as specified in TS 29.272 [86]. + +#### 6.4.4.27 Reference point between the CSS and the MME (S7a reference point) + +This reference point is used to transfer to the MME the CSG subscription information stored in the VPLMN for roaming UEs. + +Signalling on this interface uses Diameter S7a Application as specified in TS 29.272 [86]. + +#### 6.4.4.28 Reference point between the MME and the SMS-GMSC/SMS-IWMSC/SMS Router (SGd reference point) + +This reference point is used to transfer short messages between the MME and SMS-GMSC, SMS-IWMSC or SMS Router. The details for this reference point are described in TS 23.040 [137] and TS 29.338 [135]. + +Signalling on this interface uses Diameter SGd Application as specified in TS 29.338 [135]. + +#### 6.4.4.29 Reference point between the HSS and the SMS-GMSC/SMS-IWMSC/SMS Router (S6c reference point) + +This reference point is used to interrogate the HSS of the required subscriber to obtain routing information for a short message directed to that subscriber. The details for this reference point are described in TS 23.040 [137] and TS 29.338 [135]. + +Signalling on this interface uses Diameter S6c Application as specified in TS 29.338 [135]. + +--- + +## 6a PLMN specific interfaces + +### 6a.1 GCR-specific interface + +#### 6a.1.1 Interface between the MSC and its associated GCR (I-interface) + +The GCR is the management data base for the voice group or broadcast calls in the area controlled by the associated MSC(s). Whenever the MSC needs data related to a requested voice group or broadcast call it interrogates the GCR to obtain the respective voice group or broadcast call attributes. The protocol used to transfer the data over this interface is not standardized. + +### 6a.2 (void) + +### 6a.3 LCS-specific interfaces + +#### 6a.3.1 LCS interfaces using MAP + +The following interfaces are based on MAP in LCS. + +- **Lh interface:** interface between GMLC and HLR. This interface is used by the GMLC to request the address of the visited MSC or SGSN for a particular target UE whose location has been requested (see TS 29.002 [26]). +- **Lg interface:** interface between GMLC - MSC and GMLC - SGSN. This interface is used by the GMLC to convey a location request to the MSC or SGSN currently serving a particular target UE whose location was requested. The interface is used by the MSC or SGSN to return location results to the GMLC (see TS 29.002 [26]). +- **Lc interface:** between GMLC and gsmSCF, CAMEL. This interface is used to get location information for CAMEL based services. (see TS 29.002 [26]). + +### 6a.3.2 (void) + +### 6a.3.3 (void) + +### 6a.3.4 (void) + +### 6a.3.5 Interface between BSC and SMLC (Lb-interface) + +In GERAN, a SMLC supports positioning via signalling on the Lb interface to the BSC serving the target MS. + +Signalling on this interface uses BSSAP-LE, which is specified in TS 49.031 [50] + +In UTRAN, the Lb interface is not standardized, the SMLC functionality is included in SRNC. + +### 6a.3.6 Interface between Peer SMLCs (Lp-interface) + +In GERAN, a SMLC may support the Lp interface to enable access to information and resources owned by another SMLC. + +Signalling on this interface uses BSSAPP-LE, which is defined in TS 49.031 [50], and SMLCPP, which is specified in TS 48.031 [47]. + +In UTRAN, the SMLC functionality is included in SRNC and the Iur interface shall include the Lp interface type of functionality. + +### 6a.3.7 Interface between BTS and LMU (Um-interface) + +The Um/Uu interface specific to LCS is defined in TS 44.071 [55]. + +### 6a.3.8 Interface between GMLC and External LCS Client (Le-interface) + +The Le interface is used by the external LCS client to retrieve location information from the LCS server. Signalling on this interface may use the OMA Mobile Location Protocol (MLP) [62] and Open Service Access Application Programming Interface (OSA-API), TS 29.198 [63]. + +### 6a.3.9 Interface between RNS and Stand-Alone LMU, UE (Uu-interface) + +The Uu interface is used to communicate among the UE Positioning entities associated with the SRNC, the UEs and the stand-alone LMU. The Uu interface may pass measurement requests and results to and from the UE or the stand-alone LMU. UE Positioning operations at the Uu interface are generally defined in the 24- and 25-series of 3GPP Technical Specifications. Furthermore, TS 25.305 [10b] describes how a stand-alone LMU may be distinguished from a normal UE. + +### 6a.3.10 Interface between SRNC and SAS (Stand-Alone SMLC) (Iupc-interface) + +The Iupc interface defined for LCS is specified in TS 25.453 [66]. + +### 6a.3.11 Interface between GMLC and GMLC (Lr-interface) + +The Lr interface is used by the GMLC to communicate with other GMLCs. Signalling on this interface may use the OMA Roaming Location Protocol (RLP) [69]. + +### 6a.3.12 Interface between GMLC and MME (SLg-interface) + +The SLg interface is used by the GMLC to communicate with MMEs. The SLg interface is defined in TS 29.172 [123]. + +### 6a.3.13 Interface between MME and E-SMLC (SLs-interface) + +The SLs interface is used to convey LCS messages between the MME and E-SMLC. It is also used for tunnelling positioning protocol messages between the E-SMLC and either E-UTRAN or UE which are transparent to the MME as described in TS 36.305 [122]. The SLs interface is defined in TS 29.171 [124]. + +### 6a.3.14 Interface between GMLC and HSS (SLh-interface) + +SLh interface between GMLC and HSS. This interface is used by the GMLC to request the address of the visited MME for a particular target UE whose location has been requested. The SLh interface is defined in TS 29.173 [125]. + +## 6a.4 CAMEL-specific interfaces + +The CAMEL-specific interfaces are detailed in TS 23.078 [10c]. These interfaces are. + +### 6a.4.1 GMSC - gsmSSF interface + +This is an internal interface. The interface is described in the specification to make it easier to understand the handling of Detection Points (arming/disarming of DPs, DP processing etc.). + +### 6a.4.2 gsmSSF - gsmSCF interface + +This interface is used by the gsmSCF to control a call in a certain gsmSSF and to request the gsmSSF to establish a connection with a gsmSRF. Relationships on this interface are opened as a result of the gsmSSF sending a request for instructions to the gsmSCF. + +### 6a.4.3 MSC - gsmSSF interface + +This is an internal interface. The interface is described in the specification to make it easier to understand the handling of DPs (arming/disarming of DPs, DP processing etc.). + +### 6a.4.4 gsmSCF - HLR interface + +This interface is used by the gsmSCF to request information from the HLR. As a network operator option the HLR may refuse to provide the information requested by the gsmSCF. + +This interface is also used for USSD operations, both for gsmSCF-initiated dialogues and MS-initiated dialogues (relayed via HLR). It is a network operator option whether to support or not USSD operations on this interface. + +### 6a.4.5 gsmSCF - gsmSRF interface + +This interface is used by the gsmSCF to instruct the gsmSRF to play tones/announcements to the users. + +### 6a.4.6 MSC - gsmSCF interface + +This interface is used by the MSC to send supplementary service invocation notifications to the gsmSCF. + +#### 6a.4.7 SGSN - gprsSSF interface + +This is an internal interface. The interface is described in the specification to make it easier to understand the handling of DPs (arming/disarming of DPs, DP processing etc.). + +#### 6a.4.8 gprsSSF - gsmSCF interface (Ge Reference Point) + +This interface is used by the gsmSCF to control a GPRS session or individual PDP Context in a certain gprsSSF. Relationships between the gprsSSF and the gsmSCF (GPRS dialogues) on this interface are opened as a result of the gprsSSF sending a request for instructions to the gsmSCF. This interface is also known as Ge reference point (see TS 23.060 [9a]). + +### 6a.5 CBS-specific interfaces + +#### 6a.5.1 Interface between the CBC and RNS (Iu\_BC Interface) + +The interface between the CBC and the RNS is specified in the 25.41x-series of Technical Specifications. + +The CBC-RNS interface is used to carry information concerning: + +- the CBS messages itself; and +- CBS delivery parameter. + +#### 6a.5.2 Interface between the CBC and MME (SBc Interface) + +Reference point between CBC and MME for warning message delivery and control functions. This interface is specified in TS 29.168 [98]. + +#### 6a.5.3 Interface between the CBC and BSC + +The interface between the CBC and the BSC is specified in TS 48.049 [119]. + +The CBC-BSC interface is used to carry information concerning: + +- the CBS message and the warning message itself; and +- CBS message and warning message delivery parameters. + +### 6a.6 Number portability specific interfaces + +#### 6a.6.1 IN-based solution + +##### 6a.6.1.1 NPDB to MSC interface + +Upon receiving an ISUP IAM, the (gateway or visited) MSC send a database query to the NPDB as a result of analysis of the received MSISDN. The MSISDN is included in the query to the NPDB. The NPDB determines whether the MSISDN is ported or not. If not, it responds back to the MSC to continue the normal call setup procedure for MT calls (optionally providing the Routing Number). If it is ported, the NPDB responds back to the MSC with a Routing Number pointing out the Subscription network. + +#### 6a.6.2 Signalling Relay-based solution + +##### 6a.6.2.1 GMSC to MNP-SRF interface + +Upon receiving an ISUP IAM, the gateway MSC sends a routing interrogation to the MNP-SRF, which in turn will perform one of the actions, described in clause 4a.7, depending on the portability status of the subscriber and the network configuration (see TS 23.066 [40]). + +### 6a.6.2.2 MNP-SRF to HLR interface + +When the MNP-SRF receives a routing interrogation from the GMSC or an interrogating network entity (non/call related signalling), and it determines that the subscriber is not ported or it has been ported from another network, the MNP-SRF relays the message to the HLR. + +## 6a.7 IM Subsystem Reference Points + +### 6a.7.1 Reference Point HSS – CSCF (Cx Reference Point) + +The Cx reference point supports information transfer between CSCF and HSS. + +The main procedures that require information transfer between CSCF and HSS are + +- 1) Procedures related to Serving CSCF assignment +- 2) Procedures related to routing information retrieval from HSS to CSCF +- 3) Procedures related to authorisation (e.g., checking of roaming agreement) +- 4) Procedures related to authentication: transfer of security parameters of the subscriber between HSS and CSCF +- 5) Procedures related to filter control: transfer of filter parameters of the subscriber from HSS to CSCF + +Further information on the Cx reference point is provided in TS 23.228 [34]. + +### 6a.7.2 Reference Point CSCF – UE (Gm Reference Point) + +The Gm reference point supports the communication between UE and IM CN subsystem, e.g. related to registration and session control. + +The protocol used for the Gm reference point is SIP (as defined by RFC 3261 [61], other relevant RFC's, and additional enhancements introduced to support 3GPP's needs). + +### 6a.7.3 Reference Point MGCF – IMS-MGW (Mn Reference Point) + +The Mn reference point describes the interfaces between the MGCF and IMS-MGW in the IMS. It has the following properties: + +- full compliance with the H.248 standard functions for IMS – PSTN/PLMN interworking.- flexible connection handling which allows support of different call models and different media processing purposes not restricted to H.323 [54] usage. +- open architecture where extensions/Packages definition work on the interface may be carried out. +- dynamic sharing of IMS-MGW physical node resources. A physical IMS-MGW can be partitioned into logically separate virtual MGWs/domains consisting of a set of statically allocated Terminations. +- dynamic sharing of transmission resources between the domains as the IMS- MGW controls bearers and manage resources according to the H.248 [52] protocols and functions for IMS. + +### 6a.7.4 Reference Point MGCF – CSCF (Mg Reference Point) + +The Mg reference point allows the MGCF to forward incoming session signalling (from the circuit switched network) to the CSCF for the purpose of interworking with circuit switched networks. + +The protocol used for the Mg reference point is SIP (as defined by RFC 3261 [61], other relevant RFC's, and additional enhancements introduced to support 3GPP's needs). + +### 6a.7.5 (void) + +### 6a.7.5a Reference Point AS-MRFC for media control (Cr Reference Point) + +The Cr reference point allows interaction between an Application Server and an MRFC for media control. + +The Cr reference point enables the MRFC to fetch and cache documents and resources from an Application Server and to return data to an Application Server. + +The Cr reference point enables media control protocol requests, responses and notifications to be sent between the MRFC and an Application Server. + +Further information on the Cr reference point is provided in TS 23.218 [113]. + +### 6a.7.5b Reference Point AS-MRFC for session control (Mr' Reference Point) + +The Mr' reference point allows interaction between an Application Server and an MRFC for session control without passing through an S-CSCF. + +Further information on the Mr' reference point is provided in TS 23.218 [113]. + +### 6a.7.6 Reference Point CSCF - MRFC (Mr Reference Point) + +The Mr reference point allows interaction between an S-CSCF and an MRFC. + +The protocol used for the Mr reference point is SIP (as defined by RFC 3261 [61], other relevant RFC's, and additional enhancements introduced to support 3GPP's needs). + +### 6a.7.6a Reference Point MRFC – MRFP (Mp Reference Point) + +The Mp reference point allows an MRFC to control media stream resources provided by an MRF. + +The Mp reference point has the following properties: + +- Full compliance with the H.248 [52] standard. +- Open architecture where extensions (packages) definition work on the interface may be carried out. + +### 6a.7.7 Reference Point CSCF – CSCF (Mw Reference Point) + +The Mw reference point allows the communication and forwarding of signalling messaging between CSCFs, e.g. during registration and session control. + +### 6a.7.8 (void) + +### 6a.7.8a Reference Point CSCF – MRB (ISC Reference Point) + +This interface is used with an MRB operating in In-Line mode and is described further in TS 23.218 [113]). The S-CSCF receives a session initiation request from an MRB that originated from an Application Server requesting MRF resources and whose destination is an MRF resource identified by the MRB. The S-CSCF routes the message to the identified MRFC. Subsequent messages in the same session dialog between the AS and MRFC traverse the MRB as well as the S-CSCF. + +### 6a.7.9 (void) + +### 6a.7.9a Reference Point AS – MRB (Rc Reference Point) + +The Rc reference point is used by the AS to request that media resources be assigned to a call when utilizing an MRB in both Query and In-Line modes (as described in TS 23.218 [113]). + +### 6a.7.10 Reference Point CSCF – BGCF (Mi reference point) + +This reference point allows the Serving CSCF to forward the session signalling to the Breakout Gateway Control Function for the purpose of interworking to the circuit switched networks. + +The Mi reference point is based on external specifications i.e. SIP [61]. + +### 6a.7.11 Reference Point BGCF – MGCF (Mj reference point) + +This reference point allows the Breakout Gateway Control Function to exchange session signalling message with the Media Gateway Control Function for the purpose of interworking to the circuit switched networks, or for transit scenarios. + +The Mj reference point is based on external specifications i.e. SIP [61]. + +### 6a.7.12 Reference Point BGCF/IBCF – BGCF (Mk reference point) + +This reference point allows the Breakout Gateway Control Function/IBCF to forward the session signalling to another Breakout Gateway Control Function. + +The Mk reference point is based on external specifications i.e. SIP [61]. + +### 6a.7.13 Reference Point CSCF- SLF (Dx Reference Point) + +This interface between CSCF and SLF is used to retrieve the address of the HSS which holds the subscription for a given user or information related to a service. + +This interface is not required in a single HSS environment. An example for a single HSS environment is a server farm architecture. + +Details are described in TS 23.228 [34], clause 5.8.1. + +### 6a.7.14 Reference Point to IPv6 network services (Mb reference point) + +Via the Mb reference point IPv6 network services are accessed. These IPv6 network services are used for user data transport. Note, that GPRS provides IPv6 network services to the UE, i.e. the GPRS Gi reference point and the IMS Mb reference point may be the same. + +### 6a.7.15 Reference Point S-CSCF – AS (ISC Reference Point) + +This interface between Serving CSCF and the Application Servers (i.e., SIP Application Server, OSA Service Capability Server, or CAMEL IM-SSF) is used to provide services for the IMS. + +Details are described in TS 23.228 [34], clause 4.2.4. + +### 6a.7.15a Reference Point E-CSCF - EATF (I4 Reference Point) + +This is the interface between the Emergency CSCF and the EATF in serving network (i.e. EATF as defined in TS 23.167 [74]), it is used to provide services for emergency sessions. + +### 6a.7.15b Reference Point I-CSCF - EATF (I5 Reference Point) + +This is the interface between the Interrogating CSCF and the EATF in serving network (i.e. EATF as defined in TS 23.167 [74]), it is used to provide services for emergency sessions. + +### 6a.7.16 Reference Point HSS – SIP AS or OSA SCS (Sh Reference Point) + +The Application Server (SIP Application Server and/or the OSA Service Capability Server) may communicate to the HSS. The Sh interface is used for this purpose. Details are described in TS 23.228 [34], clause 4.2.4. + +This reference point is also used to exchange signalling between IP-SM-GW and the HSS for SMSIP delivery. + +### 6a.7.17 Reference Point HSS – CAMEL IM-SSF (Si Reference Point) + +The CAMEL Application Server (IM-SSF) may communicate to the HSS. The Si interface is used for this purpose. Details are described in TS 23.228 [34], clause 4.2.4. + +### 6a.7.18 Reference Point UE – AS (Ut Reference Point) + +The Ut interface resides between the UE and the SIP Application Server. + +The Ut interface enables the user to manage information related to his services. Such as creation and assignment of Public Service Identities, management of authorization policies that are used e.g. by Presence service, conference policy management, etc. + +The AS may need to exhibit security related functions for the Ut interface, the details of these security functions are described in TS 33.222 [72]. + +For the protocol at the Ut reference point HTTP shall be supported. + +### 6a.7.19 Reference Point AS- SLF (Dh Reference Point) + +This interface between AS and SLF is used to retrieve the address of the HSS which holds the subscription for a given user. + +This interface is not required in a single HSS environment. An example for a single HSS environment is a server farm architecture. + +Details are described in TS 23.228 [34], clause 5.8.1. + +### 6a.7.20 Reference Point CSCF/BGCF - IBCF (Mx Reference Point) + +The Mx reference point allows the communication and forwarding of signalling messages between a CSCF/BGCF and an IBCF, e.g. during session establishment. + +### 6a.7.21 Reference Point IBCF - TrGW (Ix Reference Point) + +This interface is used by the IBCF to control the TrGW, e.g. to request network address translation binding. + +### 6a.7.22 Reference Point I-CSCF – AS (Ma Reference Point) + +This interface between Interrogating-CSCF and the Application Servers (i.e. SIP Application Server, OSA Service Capability Server, or CAMEL IM-SSF) is used to: + +- forward SIP requests destined to a Public Service Identity hosted by an Application Server directly to the Application Server. Details are described in TS 23.228 [34], clause 5.4.12; and +- initiate a request on behalf of a user or Public Service Identity, if the AS has no knowledge of the serving S-CSCF for that user or Public Service Identity. Details are described in TS 23.228 [34], clause 5.6.5.3. + +### 6a.7.23 Reference Point P-CSCF – IMS Access Gateway (Iq Reference Point) + +The Iq reference point is between the Proxy-CSCF and the IMS Access Gateway. It conveys the necessary information that is needed to allocate and release transport addresses. + +Details are described in TS 23.228 [34], Annex G. + +### 6a.7.23a Reference Point E-CSCF - LRF (MI Reference Point) + +The MI reference point allows the E-CSCF to request the LRF to validate the location information received from the UE, to determine or query the LRF for routing information to emergency centres. Location information may be received from LRF and/or reference key to allow the PSAP to retrieve location at a later stage. + +## 6a.7.24 Reference Point IBCF - IBCF (Ici Reference Point) + +The Ici reference point allows two IBCFs to communicate with each other in order to provide the communication and forwarding of signalling messaging between IM CN subsystem networks. + +## 6a.7.25 Reference Point TrGW - TrGW (Izi Reference Point) + +The Izi reference point allows two TrGWs to forward media streams between IM CN subsystem networks. + +## 6a.7.26 Void + +## 6a.7.27 Reference Point MSC Server - CSCF (I2 Reference Point) + +The I2 reference point is used to route session control signalling between the MSC Server and the IMS, as defined in TS 23.292 [110] and in TS 23.237 [111]. This can be a roaming and inter-operator reference point. + +I2 is used to support one or more of the following features: + +- An MSC Server enhanced for ICS, as defined in TS 23.292 [110]. +- An MSC Server enhanced for ICS and SRVCC, as defined in TS 23.292 [110], TS 23.216 [83] and TS 23.237 [111]. +- An MSC Server enhanced for ICS and SRVCC with the MSC Server assisted mid-call feature as defined in TS 23.237 [111]. +- An MSC Server enhanced for ICS and SRVCC with the SRVCC for call in alerting phase feature as defined in TS 23.237 [111]. + +## 6a.7.28 Reference Point MSC Server - TAS (I3 Reference Point) + +The I3 reference point is used between the MSC Server enhanced for ICS and the TAS to interwork CS signalling and communication service setting procedures, as defined in TS 23.292 [110]. + +## 6a.7.29 Reference Point ICS UE – SCC AS (I1 Reference Point) + +The I1 reference point is used between the ICS UE and the SCC AS for service control signalling over CS access, as defined in TS 23.292 [110]. + +## 6a.8 Void + +## 6a.9 Reference Points for 3GPP/WLAN Interworking + +NOTE: With the introduction of Evolved Packet Core System, the 3GPP AAA server and 3GPP AAA Proxy provide a set of different and additional functions as specified in the EPC specific section of this specification. + +### 6a.9.1 Reference point 3GPP AAA Server - HLR (D'/Gr' Reference Point) + +This is the reference point between the 3GPP AAA server and the HLR up to and including Rel-4 and the HSS in Rel-5. The functionality of this reference point is similar to that of the Wx reference point. For more information see TS 23.234 [67]. + +### 6a.9.2 Reference point WLAN access network - 3GPP AAA Proxy/Server (Wa Reference Point) + +This is the reference point between the WLAN access network and 3GPP AAA Proxy or Server. The AAA protocol on this reference point is used to transport authentication, authorization and charging data. + +### 6a.9.3 Reference point 3GPP AAA Server – 3GPP AAA Proxy (Wd Reference Point) + +This is the reference point between the 3GPP AAA Server and Proxy. the purpose of the protocols crossing this reference point is to transport authentication, authorization and related information. For more information see TS 23.234 [67]. + +### 6a.9.4 Reference point 3GPP AAA Server/Proxy - WAG (Wg Reference Point) + +This is the reference point between the 3GPP AAA server/proxy and WAG. It is used to provide information needed by the WAG to perform policy enforcement functions for authorised users and to transport per-tunnel based charging information from the WAG to the AAA Proxy in roaming scenarios. + +### 6a.9.5 Reference point PDG - packet data networks (Wi Reference Point) + +This is the reference point between the PDG and a packet data network. It may be an operator external public or private packet data network or an intra operator packet data network, e.g. for provision of IMS services. + +### 6a.9.6 Reference Point 3GPP AAA Server/Proxy - PDG (Wm Reference Point) + +This is the reference point between the 3GPP AAA server/proxy and PDG. The functionality of this reference point is to enable: + +- The 3GPP AAA Server/Proxy to retrieve tunnelling attributes and WLAN UE's IP configuration parameters from/via Packet Data Gateway +- Carrying messages for service authentication and authorization +- Carrying authentication data for the purpose of tunnel establishment, tunnel data authentication and encryption. + +For more information see TS 23.234 [67]. + +### 6a.9.7 Reference Point WAG - WLAN access network (Wn Reference Point) + +This is the reference point between the WAG and the WLAN access network. It is used to force traffic between a WLAN UE and PDG to go through the WAG. + +### 6a.9.8 Reference Point WAG - PDG (Wp Reference Point) + +This is the reference point between WAG and PDG. It is used to transport the Wu reference point protocol data packets. + +### 6a.9.9 Reference point WLAN UE - PDG (Wu Reference Point) + +This is the reference point between the 3GPP WLAN UE and PDG. The functionality of this reference point is to establish a tunnel between WLAN UE and PDG and to exchange data packets between WLAN UE and PDG. + +### 6a.9.10 Reference point WLAN UE - WLAN access network (Ww Reference Point) + +This is the reference point between the 3GPP WLAN UE and WLAN access network. The functionality of this reference point is specified by IEEE and outside the scope of 3GPP. + +### 6a.9.11 Reference point 3GPP AAA Server - HSS (Wx Reference Point) + +This is the reference point between the 3GPP AAA server and HSS. The functionality of this reference point is to enable: + +- Retrieval of authentication vectors + +- Retrieval of WLAN access-related subscriber information (profile) +- Registration of the 3GPP AAA Server of an authorised WLAN user in the HSS +- Indication of change of subscriber profile +- Retrieval of online charging / offline charging function addresses from HSS. +- Retrieval of service related information + +For more information see TS 23.234 [67]. + +## 6a.9.12 Reference point 3GPP AAA Server - SLF (Dw reference point) + +This reference point is between the 3GPP AAA Server and the SLF. The prime purpose of the protocol(s) crossing this reference point is to enable the 3GPP AAA Server to find the address of the HSS which holds the subscriber data for a given user identity in a configuration with multiple separately addressable HSSs. + +## 6a.10 MBMS specific reference points for GPRS + +### 6a.10.1 Reference point GGSN – BM-SC (Gmb Reference Point) + +This reference point is used to exchange signalling between GGSN and BM-SC. This represents the network side boundary of the MBMS Bearer Service from a control plane perspective. This includes user specific Gmb signalling and MBMS bearer service specific signalling. The details for this reference point are described in TS 23.246 [70] and TS 29.061 [104]. + +### 6a.10.2 Reference point BM-SC – BM-SC (Mz Reference Point) + +This reference point is the roaming variant of the Gmb reference point and is used to exchange signalling between a BM-SC in the VPLMN and a BM-SC in the HPLMN. The details for this reference point are described in TS 23.246 [70] and TS 29.061 [104]. + +### 6a.10.3 Reference point GGSN – RNS (or BSS Iu mode) (Gmc Reference Point) + +This reference point is used between GGSN and RNS (or BSS Iu mode) for MBMS data delivery using IP multicast. The details for this reference point are described in TS 23.246 [70] and TS 29.281 [126]. + +## 6a.11 MBMS specific reference points for EPS + +### 6a.11.1 Reference point MBMS-GW – BM-SC (SGmb Reference Point) + +This reference point is used to exchange signalling between MBMS-GW and BM-SC. This represents the network side boundary of the MBMS Bearer Service from a control plane perspective. This includes MBMS bearer service specific signalling. The details for this reference point are described in TS 23.246 [70] and TS 29.061 [104]. + +### 6a.11.2 Reference point MBMS-GW – BM-SC (SGi-mb Reference Point) + +This reference point is used between MBMS-GW and BM-SC for MBMS data delivery. The details for this reference point are described in TS 23.246 [70] and TS 29.061 [104]. + +### 6a.11.3 Reference point MBMS-GW - MME (Sm Reference Point) + +This reference point is used to exchange signalling between MBMS-GW and MME for MBMS Session Control. The details for this reference point are described in TS 23.246 [70] and TS 29.274 [90]. + +### 6a.11.4 Reference point MBMS-GW – SGSN (Sn Reference Point) + +This reference point is used to exchange signalling between MBMS-GW and S4-SGSN for MBMS Session Control and for MBMS data delivery in point-to-point mode. The details for this reference point are described in TS 23.246 [70] and TS 29.274 [90]. + +## 6a.11.5 Reference point MBMS-GW – E-UTRAN/UTRAN (M1 Reference Point) + +This reference point is used between MBMS-GW and E-UTRAN/UTRAN for MBMS data delivery using IP Multicast. The details for this reference point are described in TS 23.246 [70], TS 29.281 [126] and TS 36.445 [129]. + +## 6a.11.6 Reference point MME – MCE (M3 Reference Point) + +This reference point is used to exchange signalling between MME and MCE for MBMS Session Control. The details for this reference point are described in TS 23.246 [70], TS 36.300 [78] and TS 36.444 [128]. + +## 6a.11.7 Reference point MCE - eNodeB (M2 Reference Point) + +This reference point is used to exchange signalling between MCE and eNodeB for MBMS Session Control. The details for this reference point are described in TS 23.246 [70], TS 36.300 [78] and TS 36.443 [127]. + +## 6a.12 Reference Points for 3GPP Generic User Profile (GUP) + +### 6a.12.1 Reference Point GUP Server – Applications (Rg Reference Point) + +The Rg reference point resides between the GUP Server and the Applications. + +The Rg reference point allows applications to create, read, modify and delete any user profile data using the harmonized access interface. The GUP Server locates the data repositories responsible of the storage of the requested profile component(s). + +The details of the Rg reference point are described in TS 23.240 [71]. + +### 6a.12.2 Reference Point GUP Server – HSS and Applications – HSS (Rp Reference Point) + +The Rp reference point resides between the GUP Server and the HSS, and between the Applications and the HSS. + +The Rp reference point enables the GUP Server and the Applications to access GUP Data Repositories. The HSS is one of the GUP Data Repositories. It stores the IM CN Subsystem user related data. + +The details of the Rp reference point are described in TS 23.240 [71]. + +## 6a.13 Reference Points for Policy and Charging Control + +### 6a.13.1 Reference Point PCEF - PCRF/H-PCRF/V-PCRF (Gx Reference Point) + +This interface provides transfer of policy and charging rules from PCRF to Policy and Charging Enforcement Function Point (PCEF) in the GW (e.g. GGSN, PDN GW). This interface is specified in TS 29.212 [99]. + +### 6a.13.2 Reference Point PCRF - Application Function (Rx Reference Point) + +This interface allows for dynamic QoS and charging-related service information to be exchanged between the Policy and Charging Rules Function (PCRF) and the Application Function (AF). This information is used by the PCRF for the control of service data flows and IP bearer resources. For more information see TS 23.203 [73]. + +### 6a.13.3 Reference Point SPR – PCRF (Sp Reference Point) + +This interface allows for the PCRF to request subscription information from the SPR and the SPR to notify the PCRF when the subscription information has changed if the PCRF has requested such notifications. The details associated with the Sp reference point are not specified in this Release. + +### 6a.13.4 Reference Point OCS – PCEF (Gy Reference Point) + +This interface allows for the online charging based on the Diameter credit control application between the Online Charging System (OCS) and the PCEF. For more information see TS 32.251 [101] and RFC 4006 [102]. + +### 6a.13.5 Reference Point OFCS – PCEF (Gz Reference Point) + +This interface allows for the offline charging based on the charging record data transfer between the Offline Charging System (OFCS) and the PCEF. For more information see TS 32.295 [109]. + +### 6a.13.6 Reference Point Trusted non-3GPP IP Access and PCRF/VPCRF (Gxa Reference Point) + +This interface provides transfer of (QoS) policy information from PCRF to the Trusted Non-3GPP accesses. This interface is specified in TS 29.212 [99]. + +### 6a.13.7 Reference Point ePDG and PCRF/VPCRF (Gxb Reference Point) + +This interface is not specified within this release of the specification. + +### 6a.13.7a Reference Point ePDG and PCRF/VPCRF (Gxb\* Reference Point) + +The reference point transports access information from ePDG to PCRF/vPCRF for WLAN UEs such as the UE local IP address and the UDP port number. This interface is specified in TS 29.212 [99]. + +Gxb\* is only applicable to the interworking with Fixed Broadband Access network. + +### 6a.13.8 Reference point between S-GW and PCRF/VPCRF (Gxc-interface) + +This interface provides transfer of (QoS) policy information from PCRF to the Serving Gateway, Gxc is used only in the case of PMIP-based S5/S8. This interface is specified in TS 29.212 [99]. + +### 6a.13.9 Reference Point PCRF/VPCRF – BBERF (Gxx Reference Point) + +This interface allows for a PCRF to have a dynamic control over the Bearer Binding and Event Report Function (BBERF) behaviour. For more information see TS 23.402 [77] and TS 23.203 [73]. This interface is specified in TS 29.213 [92] + +### 6a.13.10 Reference Point HPCRF - VPCRF (S9- interface) + +This interface provides transfer of policy and charging rules (in case of local breakout of traffic) and/or (QoS) policy information (when Gxx interface applies) between the Home PCRF and the Visited PCRF in order to support PCC roaming related functions. This interface is specified in TS 29.215 [103]. + +### 6a.13.11 Reference Point UDR – PCRF (Ud Reference Point) + +This interface allows for the PCRF, acting as an UDC Application Frontend as defined in TS 23.335 [120], to request subscription information from the UDR and the UDR to notify the PCRF when the subscription information has changed if the PCRF has requested such notifications. For details regarding the Ud reference point see TS 23.335 [120] and TS 29.335 [121]. + +### 6a.13.12 Reference Point TDF - PCRF/H-PCRF/V-PCRF (Sd Reference Point) + +The Sd Reference Point enables a PCRF to have dynamic control over the application detection and control behaviour at a TDF. The Sd Reference Point is specified in TS 29.212 [99]. + +### 6a.13.13 Reference Point OCS - PCRF/H-PCRF (Sy Reference Point) + +The Sy Reference Point enables transfer of information relating to subscriber spending from OCS to PCRF. The Sy Reference Point is specified in TS 29.219 [131]. + +## 6a.13.14 Reference Point HNB GW - PCRF/V-PCRF (S15 Reference Point) + +This reference point supports the initiation, modification and termination of sessions between the HNB GW and PCRF to support CS sessions. It triggers the PCRF to request allocation of resources in the Fixed Broadband access network for HNB CS calls. This interface is specified in TS 29.212 [99]. + +S15 is only applicable to the interworking with Fixed Broadband Access network. + +## 6a.13.15 Reference Point BPCF - PCRF/v-PCRF (S9a Reference Point) + +This interface supports the transfer of (QoS) policy information from PCRF to BPCF of broadband access network. This interface is specified in TS 29.215 [103]. + +S9a is only applicable to the interworking with Fixed Broadband Access network. + +## 6a.14 SMSIP specific reference points + +### 6a.14.1 Reference point IP-SM-GW – HSS (J Reference Point) + +This reference point is used to exchange signalling between IP-SM-GW and the HSS for SMSIP delivery. The details for this reference point are described in TS 23.204 [75]. + +## 6a.15 User Data Convergence specific reference points + +### 6a.15.1 Reference point Application Front Ends - UDR (Ud Reference Point) + +This reference point is used to exchange user between Application Front Ends and the UDR. The details for this reference point are described in TS 23.335 [120] and TS 29.335 [121]. + +## 6a.16 Specific reference points for facilitating communications with packet data networks and applications + +### 6a.16.1 Reference point MTC-IWF - SCS (Tsp reference point) + +This reference point is used between the MTC-IWF and the Services Capability Server (SCS) to invoke specific functionalities in the PLMN such as device triggering. The details for this reference point are described in TS 23.682 [132] and TS 29.368 [136]. + +This interface is a PLMN internal interface if the SCS is controlled by the operator. + +Signalling on this interface uses Diameter Tsp Application as specified in TS 29.368 [136]. + +NOTE: See clause 7.8 when the SCS is not controlled by the operator. + +### 6a.16.2 Reference point MTC-IWF - HSS/HLR (S6m reference point) + +This reference point is used between the MTC-IWF and the HSS/HLR to authorize a certain SCS to request a specific service (e.g. device triggering), and to retrieve subscription information and routing information (i.e. serving SGSN/MME/MSC identities) from the HSS/HLR. + +The details for this reference point are described in TS 23.682 [132] and TS 29.336 [133]. + +Signalling on this interface uses Diameter S6m Application as specified in TS 29.336 [133]. + +### 6a.16.3 Reference point MTC-AAA - HSS/HLR (S6n reference point) + +This reference point is used between the MTC-AAA and the HSS/HLR to translate an IMSI to external identifier(s) of the user. + +The details for this reference point are described in TS 23.682 [132] and TS 29.336 [133]. + +Signalling on this interface uses Diameter S6n Application as specified in TS 29.336 [133]. + +#### 6a.16.4 Reference point MTC-IWF - SMS-SC (T4 reference point) + +This reference point is used between the MTC-IWF and the SMS-SC to transfer device trigger to the SMS-SC inside the HPLMN. + +The details for this reference point are described in TS 23.682 [132] and TS 29.337 [134]. + +Signalling on this interface uses Diameter T4 Application as specified in TS 29.337 [134]. + +--- + +### 7 Reference points between the PLMN and other networks + +The reference points between the PLMN and other networks, including dedicated networks, are described in the 49-series of Technical Specifications and in the 29-series of Technical Specifications. + +#### 7.1 Reference point fixed networks - MSC + +The MSC is based on a normal ISDN exchange. It has, for call control, the same reference points as the fixed network exchanges. The signalling reference point considered in the Technical Specifications is related to the signalling system No. 7 User Parts TUP and ISUP associated to the circuits used for incoming and outgoing calls. + +#### 7.2 Reference point GGSN - packet data networks (Gi reference point) + +This is the reference point between the GGSN and a packet data network. It may be an operator external public or private packet data network or an intra operator packet data network, e.g. for provision of IMS services. + +#### 7.2a Reference point PDN GW - packet data networks (SGi reference point) + +This is the reference point between the PDN GW and a packet data network. It may be an operator external public or private packet data network or an intra operator packet data network, e.g. for provision of IMS services. For more details see TS 29.061 [104]. + +#### 7.3 Reference point GMLC - external LCS Client (Le reference point) + +At this reference point external LCS Clients request services from the PLMN. + +#### 7.4 Reference Point CSCF/IBCF – Multimedia IP networks (Mm Reference Point) + +This is an IP interface between CSCF/IBCF and IP networks. This interface is used, for example, to receive a session request from another SIP server or terminal. + +#### 7.5 (void) + +#### 7.6 Reference point PDG - packet data networks (Wi reference point) + +This is the reference point between the PDG and a packet data network. It may be an operator external public or private packet data network or an intra operator packet data network, e.g. for provision of IMS services. + +## 7.7 Reference Point WAG – WLAN access network (Wn reference point) + +This is the reference point between the WAG and the WLAN access network. It is used to force traffic between a WLAN UE and PDG to go through the WAG. + +## 7.8 Reference point MTC-IWF - SCS (Tsp reference point) + +See clause 6a.16.1. + +This interface is an interface between the PLMN and other networks if the SCS is not controlled by the operator. + +--- + +## Annex A (informative): Description for GLR-related entities and interfaces + +This annex describes the GLR-related entities and the interfaces. This annex is an informative annex. The 'informative' means just that the GLR is an optional functional entity to optimize signalling traffic between PLMNs. Therefore, this annex is normative to a PLMN which introduce the GLR. + +The GLR is only applicable for GERAN and UTRAN access. The GLR is not applicable to the EPC. + +--- + +### A.1 Normative references + +[A1] 3GPP TS 23.119: "3rd Generation Partnership Project; Technical Specification Group Core Network; Gateway Location Register (GLR); Stage2". + +--- + +## A.2 Definitions related to Gateway Location Register (GLR) + +### A.2.1 Gateway Location Register (GLR) + +This entity handles location management of roaming subscriber in visited network without involving HLR. The location register function in the GLR stores subscription information and routing information for both CS services and PS services. This entity can be only located in a visited PLMN. + +### A.2.2 Intermediate Mobile-services Switching Centre (IM-MSC) + +This entity is used as serving MSC towards home network and relay some messages between home network and serving MSC. This entity can be only located in a visited PLMN. + +### A.2.3 Intermediate GPRS Serving Node (IM-GSN) + +This entity is used as serving GSN towards home network and relay some PDU notification messages between serving GSN and Gateway GSN. This entity can be only located in a visited PLMN. + +--- + +## A.3 The entities of the mobile system + +### A.3.1 Gateway Location Register (GLR) + +GLR is pseudo-HLR located in visited network. The roamer's information is stored in it and handles location management of it within the network. Presence of GLR is invisible from home network therefore interface between HLR and GLR is same as one of HLR and VLR. Also, the interface between the VLR and GLR is the same as the one between the VLR and the HLR. + +The GLR is a logical node and acts as a VLR for MAP signalling (e.g. PRN) from the HPLMN point of view. The GLR acts as a HLR for MAP signalling (e.g. Register SS) from the VPLMN point of view. + +The GLR also acts as an SGSN for MAP signalling only (e.g. ISD) from the HPLMN point of view. This is because MAP operations such as ISD must be terminated at the GLR for the purpose of subscriber data caching. + +The GLR shall terminate all TC dialogues and start new dialogues towards the HLR or the VLR. The GLR shall generate SCCP address of the HLR (i.e. E.214 MGT) from IMSI. + +### A.3.2 Intermediate Mobile-services Switching Centre (IM-MSC) + +The Intermediate MSC (IM-MSC) is the logical node, which represent MSCs in the visited network. Some service features use the MSC Number stored in the HLR directly to deliver message from a certain node in home network (e.g. + +SMS-GMSC) to serving MSC in visited network. In such case, the message is firstly distributed to representative MSC (i.e. IM- MSC) and it relays it to actual serving MSC interrogating routing information to GLR. + +- The Intermediate MSC (IM- MSC) is a logical node and represents the VMSC in the GLR equipped VPLMN. +- The IM- MSC acts as the VMSC for the HPLMN in the same way that the GLR acts as a VLR for HPLMN. The IM- MSC terminates MAP signalling from the HPLMN towards the VMSC and forwards the signal to the actual VMSC. +- The IM- MSC has an address interrogation function with which it is able to obtain the actual VMSC Number from the GLR. +- The IM- MSC is implemented in the same physical node as the one in which the GLR is implemented. +- The GLR alters the VMSC Number to the IM- MSC Number within an Update Location message. +- The IM- MSC Number is the E.164 Number assigned to the IM- MSC [53]. +- The interrogation function of the IM- MSC is similar to that in the SMS-GMSC. + +### A.3.3 Intermediate GPRS Serving Node (IM-GSN) + +The Intermediate GSN (IM-GSN) is a logical node and represents the SGSN for some GTP signalling termination in a GLR equipped VPLMN. + +The IM-GSN acts as an SGSN for ***only some GTP signalling messages*** (i.e. PDU\_Notification request/response, PDU\_Notification\_reject request/response) from the HPLMN point of view. The IM-GSN terminates these GTP signalling messages from the HPLMN towards SGSN and forwards the signal to the actual SGSN. The IM-GSN has an address interrogation function with which it is able to request the actual SGSN address from the GLR. + +Apart from the case described above (i.e. PDU\_Notification request/response, PDU\_Notification\_reject request/response), all other GTP signalling should be handled directly between the SGSN and the GGSN. + +NOTE: ***MAP signalling*** towards the SGSN is ***NOT*** terminated at the IM-GSN. Instead it is terminated at the GLR. + +--- + +## A.4 Configuration of a Public Land Mobile Network + +### A.4.1 Basic configuration with GLR introduction + +In the basic configuration with GLR introduction presented in figure A.1, all the functions related to GLR introduction are considered implemented in different equipments. Therefore, all the interfaces within PLMN are external. Interfaces GLa, GLb, GLc, GLd, GLf, GLg, GLh, and GLi need the support of the Mobile Application Part of the signalling system No. 7 to exchange the data necessary to provide the mobile service. No protocols for the GLe interface are standardized. GLj and GLk need the support of GPRS Tunnelling Protocol - Control to provide the packet domain services. + +![Diagram of a PLMN configuration with GLR and various interfaces (GLa through GLj).](a963ca41bde1669b18a4b783616f228b_img.jpg) + +The diagram illustrates the configuration of a PLMN and its interfaces with a GLR. At the top, SGSN and VLR/MSC are shown. Below them, IM-GSN and IM-MSC are connected to the GLR. At the bottom, a shaded oval labeled 'Other PLMN' contains GGSN, HLR, SMS-GMSC, and GMLC. Interfaces are labeled as follows: GLk (SGSN to IM-GSN), GLc (SGSN to GLR), GLb (VLR/MSC to GLR), GLh (VLR/MSC to IM-MSC), GLe (IM-GSN to GLR), GLd (IM-MSC to GLR), GLj (IM-GSN to GGSN), GLa (GLR to HLR), GLg (IM-MSC to SMS-GMSC), GLf (GLR to SMS-GMSC), and GLi (GMLC to GLR). A legend at the bottom indicates that dashed lines represent signalling interfaces and solid lines represent user traffic interfaces, which include Short Messages. + +Diagram of a PLMN configuration with GLR and various interfaces (GLa through GLj). + +Figure A.1: Configuration of a PLMN and interfaces with GLR + +## A.5 PLMN interfaces + +### A.5.1 Interface between the HLR and the GLR (GLa-interface) + +In circuit switched domain, this interface is the same as that between the VLR and the HLR (see TS 29.002 [26]). The HLR regards the GLR as the VLR via this interface. On the other hand, in packet switched domain, this interface is the same as that between the SGSN and the HLR (see TS 29.002 [26]). The HLR regards the GLR as the SGSN via this interface + +### A.5.2 Interface between the VLR and the GLR (GLb-interface) + +This interface is the same as those between the VLR and the HLR (see TS 29.002 [26]). The VLR regards the GLR as the HLR via this interface. + +### A.5.3 Interface between the SGSN and the GLR (GLc-interface) + +This interface is the same as those between the SGSN and the HLR (see TS 29.002 [26]). The SGSN regards the GLR as the HLR via this interface. + +### A.5.4 Interface between the GLR and the IM\_MSC (GLd-interface) + +In the network with the GLR, when the IM\_MSC receives a message, it interrogates the GLR for the routing information of the MSC. However, this interface is internal because GLR and IM-MSC are implemented in the same physical node and the protocol on this interface is not specified. + +### A.5.5 Interface between the GLR and the IM\_GSN (GLe-interface) + +In the network with the GLR when the IM\_GSN receiving a PDU notification from the GGSN, the IM\_GSN relays the notification to the SGSN by interrogating via the interface the routing information to the GLR. The interrogation uses the same operation on the interface between the SGSN and the HLR (see TS 29.002 [26]). + +### A.5.6 Interface between the SMS-GMSC and the GLR (GLf-interface) + +This interface is used to forward mobile-terminated short messages in the network with the GLR in case of SMS transfer over GPRS. Signalling on this interface uses the Mobile Application Part (MAP) (see TS 29.002 [26]). + +The SMS-GMSC regards the GLR as the SGSN via this interface. + +## **A.5.7 Interface between the SMS-GMSC and the IM\_MSC (GLg-interface)** + +This interface is used to forward short messages in the network with the GLR in case of SMS transfer over non-GPRS. Signalling on this interface uses the Mobile Application Part (MAP) (see TS 29.002 [26]). + +The SMS-GMSC regards the IM\_MSC as the MSC via this interface. + +## **A.5.8 Interface between the MSC and the IM\_MSC (GLh-interface)** + +This interface is used to forward short messages in the network with the GLR in case of SMS transfer over non-GPRS. Also this interface is used to exchange data needed by the MSC to perform subscriber authorization and allocate network resources. Signalling on this interface uses the Mobile Application Part (MAP) (see TS 29.002 [26]). + +## **A.5.9 Interface between the GMLC and the IM\_MSC (GLi-interface)** + +Also this interface is used to exchange data needed by the MSC to perform subscriber authorization and allocate network resources. Signalling on this interface uses the Mobile Application Part (MAP) (see TS 29.002 [26]). + +The GMLC regards the IM\_MSC as the MSC via this interface. + +## **A.5.10 Interface between the GGSN and the IM\_GSN (GLj-interface)** + +In the network with the GLR when receiving a PDP PDU from the external network the GGSN sends a notification to the IM\_GSN by the routing information from the HLR (see TS 29.060 [51]). The GGSN regards the IM\_GSN as the SGSN via this interface. + +## **A.5.11 Interface between the SGSN and the IM\_GSN (GLk-interface)** + +In the network with the GLR when receiving a PDP notification from the GGSN, the IM\_GSN relays the notification to the SGSN by the routing information from the GLR (see TS 29.060 [51]). The SGSN regards the IM\_GSN as the GGSN via this interface. + +## Annex B (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|------|-----|------------------------------------------------------------------------------------------------------|-----|-------------|--------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Cat | Old | New | +| 09/1999 | - | - | - | - | renumbering of the present document from 03.02 to 23.002 (23.002 v.3.0.0 identical to 03.02 v.7.0.0) | - | 03.02v7.0.0 | 23.002v3.0.0 | +| 09/2010 | SP-49 | SP-100555 | 0222 | 1 | Addition of GTP based S2b in the 3GPP network architecture | B | 9.4.0 | 10.0.0 | +| 09/2010 | SP-49 | SP-100557 | 0223 | - | Updates to IM Subsystem figure for E-CSCF and IBCF | F | 9.4.0 | 10.0.0 | +| 09/2010 | SP-49 | SP-100557 | 0225 | - | Architecture update of SRVCC architecture enhanced with ATCF | F | 9.4.0 | 10.0.0 | +| 09/2010 | SP-49 | SP-100557 | 0227 | 1 | Introducing Ud interface between UDR and PCRF | F | 9.4.0 | 10.0.0 | +| 12/2010 | SP-50 | SP-100674 | 0231 | - | Correction of MGCF definition to make it consistent with TS 29.235 | A | 10.0.0 | 10.1.0 | +| 01/2011 | - | - | - | - | Update of LTE logo to LTE-Advanced logo | - | 10.1.0 | 10.1.1 | +| 03/2011 | SP-51 | SP-110075 | 0228 | 2 | Correction on the reference of S2b interface | F | 10.1.1 | 10.2.0 | +| 03/2011 | SP-51 | SP-110070 | 0232 | - | Add LIPA_SIPTO in 23002 | B | 10.1.1 | 10.2.0 | +| 09/2011 | SP-53 | SP-110456 | 0238 | 2 | Correcting the definition of I2 | A | 10.2.0 | 10.3.0 | +| 09/2011 | SP-53 | SP-110460 | 0239 | 1 | MBMS support in EPS | F | 10.2.0 | 10.3.0 | +| 09/2011 | SP-53 | SP-110468 | 0240 | 2 | Introduction of the CSG Subscriber Server entity and interfaces | B | 10.3.0 | 11.0.0 | +| 12/2011 | SP-54 | SP-110737 | 0244 | - | Adding missing ACTF to IMS entities clause | A | 11.0.0 | 11.1.0 | +| 03/2012 | SP-55 | SP-120087 | 0242 | 2 | Clarification on GUP data repository's role as logical function in the HSS | F | 11.1.0 | 11.2.0 | +| 03/2012 | SP-55 | SP-120087 | 0245 | - | Editorial and reference corrections to 23.002 | F | 11.1.0 | 11.2.0 | +| 03/2012 | SP-55 | SP-120085 | 0246 | - | Clarifications for SaMOG in 23.002 | B | 11.1.0 | 11.2.0 | +| 06/2012 | SP-56 | SP-120244 | 0247 | 1 | Corrections related to SAPP introduction in the Network Architecture specification | F | 11.2.0 | 11.3.0 | +| 06/2012 | SP-56 | SP-120238 | 0248 | 1 | Corrections related to QoS_SSL introduction in the Network Architecture specification. | F | 11.2.0 | 11.3.0 | +| 06/2012 | SP-56 | SP-120248 | 0250 | 1 | Introduction of CS to PS SRVCC architecture | B | 11.2.0 | 11.3.0 | +| 06/2012 | SP-56 | SP-120241 | 0251 | 4 | BBAI update for architecture, entity and interface function | F | 11.2.0 | 11.3.0 | +| 09/2012 | SP-57 | SP-120482 | 0253 | 1 | SIMTC update for architecture, entities and interfaces | B | 11.3.0 | 11.4.0 | +| 09/2012 | SP-57 | SP-120627 | 0254 | 1 | Reference list correction to align with the corrected TS 29.212 title | F | 11.3.0 | 11.4.0 | +| 12/2012 | SP-58 | SP-120714 | 0255 | 1 | Clarifying that MSC Server assisted mid-call feature does not imply I2 interface | A | 11.4.0 | 11.5.0 | +| 12/2012 | SP-58 | SP-120726 | 0259 | 1 | Adding the missing ATGW to IMS entities description clause | A | 11.4.0 | 11.5.0 | +| 06/2013 | SP-60 | SP-130305 | 0261 | 2 | Clarification on the reference of SGd and S6c | F | 11.5.0 | 11.6.0 | +| 06/2013 | SP-60 | SP-130307 | 0265 | - | Correction of home routed access PCC architecture | F | 11.5.0 | 11.6.0 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23003/10d81b2cc455e3563e3e562a7f451124_img.jpg b/marked/Rel-11/23_series/23003/10d81b2cc455e3563e3e562a7f451124_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c96d404d625c7e05824610a60b65c0617035c91 --- /dev/null +++ b/marked/Rel-11/23_series/23003/10d81b2cc455e3563e3e562a7f451124_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68d3c7802b864b4b23cfb36085fae08b161fa8dd1795e815ad832fb6d4bc20a9 +size 18331 diff --git a/marked/Rel-11/23_series/23003/2bc39576969969ffe6d3f3d5264bba75_img.jpg b/marked/Rel-11/23_series/23003/2bc39576969969ffe6d3f3d5264bba75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df14fbe2705708982cebd1f690de6b04d4cbd4a5 --- /dev/null +++ b/marked/Rel-11/23_series/23003/2bc39576969969ffe6d3f3d5264bba75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:495f2500e1eeda29796ccc7edd74515bc07ed346c232cf5ba8ecc7c7e246468c +size 31649 diff --git a/marked/Rel-11/23_series/23003/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg b/marked/Rel-11/23_series/23003/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07753d81d6b9b0074d78b677e93927d04fc89301 --- /dev/null +++ b/marked/Rel-11/23_series/23003/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c01c137241a80115abe8f9cf4f968ff903aef7b98d282eb53ae80e82466b30d +size 19313 diff --git a/marked/Rel-11/23_series/23003/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/Rel-11/23_series/23003/409498e57b1f988b2b604d12cd997002_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c6fcb5152d1a455e9d3b310a8f54795868643ef --- /dev/null +++ b/marked/Rel-11/23_series/23003/409498e57b1f988b2b604d12cd997002_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5543902a1d0aad204b3d6e9518335c75c30697cc7e30bb2ecb93461831701537 +size 21387 diff --git a/marked/Rel-11/23_series/23003/678ac9faaa56bb929499cebeea83a110_img.jpg b/marked/Rel-11/23_series/23003/678ac9faaa56bb929499cebeea83a110_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91aeabc56494639250be38985f87d2aa5a76b701 --- /dev/null +++ b/marked/Rel-11/23_series/23003/678ac9faaa56bb929499cebeea83a110_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:047ea55caed80ea257ee44695e61747c3a0a26932fbfed9e9368e77cd5def5be +size 28235 diff --git a/marked/Rel-11/23_series/23003/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/marked/Rel-11/23_series/23003/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48b67ce4be78841cf88430b3588547b979fa2290 --- /dev/null +++ b/marked/Rel-11/23_series/23003/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f5cff3a33cfd4e3b39bbd67e44671f94f4931e4556f0e4eb46e423af8db4bc1 +size 14973 diff --git a/marked/Rel-11/23_series/23003/6f90e8489d3449ddab9b5773db240a16_img.jpg b/marked/Rel-11/23_series/23003/6f90e8489d3449ddab9b5773db240a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5322b510ccf0c45932d9fab3f45db01af2935d16 --- /dev/null +++ b/marked/Rel-11/23_series/23003/6f90e8489d3449ddab9b5773db240a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f916c85a305c3f161186c25f5cc54d5bf3fa06036a7db394738f3bf2d55d05b3 +size 14693 diff --git a/marked/Rel-11/23_series/23003/745261f385368efa3f2259c8681874e9_img.jpg b/marked/Rel-11/23_series/23003/745261f385368efa3f2259c8681874e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab15f02fe32063fb8274d18a189d1f71451254f1 --- /dev/null +++ b/marked/Rel-11/23_series/23003/745261f385368efa3f2259c8681874e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65f22bdc9b0ac076c132e3e9668d08999c8012cd62ad32e127f50ef705168ba3 +size 22478 diff --git a/marked/Rel-11/23_series/23003/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/23_series/23003/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81c5b785e324b820c4ccff93d4af4916c140c4bc --- /dev/null +++ b/marked/Rel-11/23_series/23003/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f3c62680de0f851f767ff2f6c2191d8a2097b3b203503e93193235bcda2f5b1 +size 18298 diff --git a/marked/Rel-11/23_series/23003/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/23_series/23003/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bb6f2dc2373363fc25dfb0834e7baf29ce2b8c9 --- /dev/null +++ b/marked/Rel-11/23_series/23003/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:983865b71e14a42eb9bc8346ac6f8cd0b91ff61067a6f4ae689284c391fa903b +size 29810 diff --git a/marked/Rel-11/23_series/23003/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg b/marked/Rel-11/23_series/23003/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84526678e5b4ef41a4f522a13ad6f0ce0978ef7d --- /dev/null +++ b/marked/Rel-11/23_series/23003/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff15fd557afcf39ec0d528ba0ad8f748199450e0faed2c5eaf52977d8b849602 +size 13390 diff --git a/marked/Rel-11/23_series/23003/836008eb3303ade9e269f93c04dc0a2e_img.jpg b/marked/Rel-11/23_series/23003/836008eb3303ade9e269f93c04dc0a2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3dbba0a60dffc7a48ebcedd95fcc4403760ff01d --- /dev/null +++ b/marked/Rel-11/23_series/23003/836008eb3303ade9e269f93c04dc0a2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:659810dadabf3de11d62bb5222b441b33c1ed93c62d716f7cd8562853b2e49ba +size 25215 diff --git a/marked/Rel-11/23_series/23003/8acc73a21038cd3ddc4c0ec148807f9d_img.jpg b/marked/Rel-11/23_series/23003/8acc73a21038cd3ddc4c0ec148807f9d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..924221577b093d91c5ce9d856c9cad2964113e5b --- /dev/null +++ b/marked/Rel-11/23_series/23003/8acc73a21038cd3ddc4c0ec148807f9d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7a2138c1252d9bf0b82b2b856059cb6a67bcb9d4f5c28230b5843ee835c6917 +size 16230 diff --git a/marked/Rel-11/23_series/23003/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-11/23_series/23003/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c121beff3f09586812804153fa4174378042d59e --- /dev/null +++ b/marked/Rel-11/23_series/23003/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc9ef156837547ad7ddf6a0438752a6efe97f3c07f2cc9d6b757edd97ed0d5bf +size 19746 diff --git a/marked/Rel-11/23_series/23003/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-11/23_series/23003/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebe0b1ab79cbfd7c09410ebf9d6f11a6a7dac696 --- /dev/null +++ b/marked/Rel-11/23_series/23003/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29a915905aaf74b1c66add61a35e43d93ea3d7b9c64ee7553cfaa13776e01a8e +size 9429 diff --git a/marked/Rel-11/23_series/23003/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Rel-11/23_series/23003/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c9783be47d0ea41f055b18dcd7b9145b3a32731 --- /dev/null +++ b/marked/Rel-11/23_series/23003/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:510441238e43182c2a156437289c5b4c415d5bec732adfba09d3681f2a6e8a69 +size 18538 diff --git a/marked/Rel-11/23_series/23003/a4bfa2343d75076b79f7e33d93915e00_img.jpg b/marked/Rel-11/23_series/23003/a4bfa2343d75076b79f7e33d93915e00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00304121490743582af0051e8061ea29151ebb2a --- /dev/null +++ b/marked/Rel-11/23_series/23003/a4bfa2343d75076b79f7e33d93915e00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9df92642993ee25c1970e03c89d9af2c5370e59e932eb2610b2c5caf8ca8b4a +size 17944 diff --git a/marked/Rel-11/23_series/23003/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/23_series/23003/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17309628bac22ec3269e18a01e9521f0e6a03b2e --- /dev/null +++ b/marked/Rel-11/23_series/23003/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2a24ba08c8a58d275f302aa5bac0cb759e49948a9a67b3436c89ea7d44e2a2a +size 19019 diff --git a/marked/Rel-11/23_series/23003/bf10cf36bba7b1d1f5ba30447da6905f_img.jpg b/marked/Rel-11/23_series/23003/bf10cf36bba7b1d1f5ba30447da6905f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..239cc632affd5f8edc92cf8e58792a140674982b --- /dev/null +++ b/marked/Rel-11/23_series/23003/bf10cf36bba7b1d1f5ba30447da6905f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6ac35131e1ca1bd857b576eaa86d064803fed117053da3efb31bf688f0f2a17 +size 14469 diff --git a/marked/Rel-11/23_series/23003/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Rel-11/23_series/23003/d3b5eac55166fc428a223bba5c46961b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70bb5c93ae8703562f338cd6468b10912cdac520 --- /dev/null +++ b/marked/Rel-11/23_series/23003/d3b5eac55166fc428a223bba5c46961b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81bca3161b8dea6811277e58e5259010ecb9b7cebacc1861b09908154953ff9b +size 21366 diff --git a/marked/Rel-11/23_series/23003/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/marked/Rel-11/23_series/23003/db5ab5d386827a5d5f5fad0f45612b90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8f055b02cdba5d492f2ee87bf279767d5fab5f0 --- /dev/null +++ b/marked/Rel-11/23_series/23003/db5ab5d386827a5d5f5fad0f45612b90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68911233f894333b4ea006eb2738f51133d76f919fcc47f4a496f6d719ddb49f +size 20137 diff --git a/marked/Rel-11/23_series/23003/f1fbb1287d999c7034742de35bdab836_img.jpg b/marked/Rel-11/23_series/23003/f1fbb1287d999c7034742de35bdab836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6a4bd2632a454746ad3422fc7c2ab959dac2ba8 --- /dev/null +++ b/marked/Rel-11/23_series/23003/f1fbb1287d999c7034742de35bdab836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:907cb6d9ce4032295d60b084ca8cd0016d2aa276b9e6be88914c4894857666f0 +size 26088 diff --git a/marked/Rel-11/23_series/23003/raw.md b/marked/Rel-11/23_series/23003/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a78faaff6e7ff7313845d8855b00639e1a39a5ed --- /dev/null +++ b/marked/Rel-11/23_series/23003/raw.md @@ -0,0 +1,3478 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 8 | +| 1 Scope..... | 9 | +| 1.1 References ..... | 9 | +| 1.1.1 Normative references..... | 9 | +| 1.1.2 Informative references ..... | 13 | +| 1.2 Abbreviations ..... | 13 | +| 1.3 General comments to references ..... | 13 | +| 1.4 Conventions on bit ordering..... | 13 | +| 2 Identification of mobile subscribers..... | 14 | +| 2.1 General ..... | 14 | +| 2.2 Composition of IMSI ..... | 14 | +| 2.3 Allocation principles ..... | 15 | +| 2.4 Structure of TMSI ..... | 15 | +| 2.5 Structure of LMSI ..... | 15 | +| 2.6 Structure of TLLI ..... | 15 | +| 2.7 Structure of P-TMSI Signature ..... | 16 | +| 2.8 Globally Unique Temporary UE Identity (GUTI) ..... | 17 | +| 2.8.1 Introduction ..... | 17 | +| 2.8.2 Mapping between Temporary and Area Identities for the EUTRAN and the UTRAN/GERAN based systems ..... | 17 | +| 2.8.2.0 Introduction..... | 17 | +| 2.8.2.1 Mapping from GUTI to RAI, P-TMSI and P-TMSI signature ..... | 18 | +| 2.8.2.1.1 Introduction ..... | 18 | +| 2.8.2.1.2 Mapping in the UE ..... | 18 | +| 2.8.2.1.3 Mapping in the old MME..... | 19 | +| 2.8.2.2 Mapping from RAI and P-TMSI to GUTI..... | 19 | +| 2.8.2.2.1 Introduction ..... | 19 | +| 2.8.2.2.2 Mapping in the UE ..... | 19 | +| 2.8.2.2.3 Mapping in the new MME ..... | 20 | +| 2.9 Structure of the S-Temporary Mobile Subscriber Identity (S-TMSI)..... | 20 | +| 3 Numbering plan for mobile stations..... | 20 | +| 3.1 General ..... | 20 | +| 3.2 Numbering plan requirements ..... | 20 | +| 3.3 Structure of MS international PSTN/ISDN number (MSISDN)..... | 21 | +| 3.4 Mobile Station Roaming Number (MSRN) for PSTN/ISDN routeing..... | 21 | +| 3.5 Structure of Mobile Station International Data Number ..... | 22 | +| 3.6 Handover Number ..... | 22 | +| 3.7 Structure of an IP v4 address..... | 22 | +| 3.8 Structure of an IP v6 address..... | 22 | +| 4 Identification of location areas and base stations..... | 22 | +| 4.1 Composition of the Location Area Identification (LAI) ..... | 22 | +| 4.2 Composition of the Routing Area Identification (RAI) ..... | 23 | +| 4.3 Base station identification ..... | 23 | +| 4.3.1 Cell Identity (CI) and Cell Global Identification (CGI) ..... | 23 | +| 4.3.2 Base Station Identify Code (BSIC) ..... | 24 | +| 4.4 Regional Subscription Zone Identity (RSZI) ..... | 24 | +| 4.5 Location Number..... | 25 | +| 4.6 Composition of the Service Area Identification (SAI)..... | 25 | +| 4.7 Closed Subscriber Group ..... | 25 | +| 4.8 HNB Name..... | 25 | +| 4.9 CSG Type..... | 26 | +| 4.10 HNB Unique Identity ..... | 26 | +| 5 Identification of MSCs, GSNs, location registers and CSSs ..... | 26 | +| 5.1 Identification for routeing purposes ..... | 26 | +| 5.2 Identification of HLR for HLR restoration application ..... | 27 | + +| | | | +|----------|------------------------------------------------------------------------------------------------|----| +| 6 | International Mobile Station Equipment Identity and Software Version Number ..... | 27 | +| 6.1 | General ..... | 27 | +| 6.2 | Composition of IMEI and IMEISV ..... | 27 | +| 6.2.1 | Composition of IMEI ..... | 27 | +| 6.2.2 | Composition of IMEISV ..... | 28 | +| 6.3 | Allocation principles ..... | 28 | +| 7 | Identification of Voice Group Call and Voice Broadcast Call Entities ..... | 28 | +| 7.1 | Group Identities ..... | 28 | +| 7.2 | Group Call Area Identification ..... | 29 | +| 7.3 | Voice Group Call and Voice Broadcast Call References ..... | 29 | +| 8 | SCCP subsystem numbers ..... | 29 | +| 8.1 | Globally standardized subsystem numbers used for GSM/UMTS ..... | 30 | +| 8.2 | National network subsystem numbers used for GSM/UMTS ..... | 30 | +| 9 | Definition of Access Point Name ..... | 30 | +| 9.0 | General ..... | 31 | +| 9.1 | Structure of APN ..... | 31 | +| 9.1.1 | Format of APN Network Identifier ..... | 31 | +| 9.1.2 | Format of APN Operator Identifier ..... | 31 | +| 9.2 | Definition of the Wild Card APN ..... | 32 | +| 9.2.1 | Coding of the Wild Card APN ..... | 32 | +| 9.3 | Definition of Emergency APN ..... | 32 | +| 10 | Identification of the Cordless Telephony System entities ..... | 33 | +| 10.1 | General description of CTS-MS and CTS-FP Identities ..... | 33 | +| 10.2 | CTS Mobile Subscriber Identities ..... | 33 | +| 10.2.1 | General ..... | 33 | +| | Composition of the CTSMISI ..... | 33 | +| 10.2.3 | Allocation principles ..... | 33 | +| 10.2.4 | CTSMISI hexadecimal representation ..... | 34 | +| 10.3 | Fixed Part Beacon Identity ..... | 34 | +| 10.3.1 | General ..... | 34 | +| 10.3.2 | Composition of the FPBI ..... | 34 | +| 10.3.2.1 | FPBI general structure ..... | 34 | +| 10.3.2.2 | FPBI class A ..... | 34 | +| 10.3.2.3 | FPBI class B ..... | 35 | +| 10.3.3 | Allocation principles ..... | 35 | +| 10.4 | International Fixed Part Equipment Identity ..... | 35 | +| 10.4.1 | General ..... | 35 | +| 10.4.2 | Composition of the IFPEI ..... | 36 | +| 10.4.3 | Allocation principles ..... | 36 | +| 10.5 | International Fixed Part Subscription Identity ..... | 36 | +| 10.5.1 | General ..... | 36 | +| 10.5.2 | Composition of the IFPSI ..... | 36 | +| 10.5.3 | Allocation principles ..... | 37 | +| 11 | Identification of Localised Service Area ..... | 37 | +| 12 | Identification of PLMN, RNC, Service Area, CN domain and Shared Network Area ..... | 37 | +| 12.1 | PLMN Identifier ..... | 38 | +| 12.2 | CN Domain Identifier ..... | 38 | +| 12.3 | CN Identifier ..... | 38 | +| 12.4 | RNC Identifier ..... | 38 | +| 12.5 | Service Area Identifier ..... | 38 | +| 12.6 | Shared Network Area Identifier ..... | 39 | +| 13 | Numbering, addressing and identification within the IP multimedia core network subsystem ..... | 39 | +| 13.1 | Introduction ..... | 39 | +| 13.2 | Home network domain name ..... | 39 | +| 13.3 | Private User Identity ..... | 40 | +| 13.4 | Public User Identity ..... | 40 | +| 13.4A | Wildcarded Public User Identity ..... | 41 | + +| | | | +|----------|------------------------------------------------------------------------------------------------------|----| +| 13.4B | Temporary Public User Identity ..... | 41 | +| 13.5 | Public Service Identity (PSI)..... | 41 | +| 13.5A | Private Service Identity ..... | 42 | +| 13.6 | Anonymous User Identity ..... | 42 | +| 13.7 | Unavailable User Identity..... | 42 | +| 13.8 | Instance-ID..... | 42 | +| 13.9 | XCAP Root URI..... | 43 | +| 13.9.1 | XCAP Root URI on Ut interface..... | 43 | +| 13.9.1.1 | General..... | 43 | +| 13.9.1.2 | Format of XCAP Root URI ..... | 43 | +| 14 | Numbering, addressing and identification for 3GPP System to WLAN Interworking ..... | 44 | +| 14.1 | Introduction ..... | 44 | +| 14.2 | Home network realm..... | 44 | +| 14.3 | Root NAI..... | 44 | +| 14.4 | Decorated NAI ..... | 45 | +| 14.4A | Fast Re-authentication NAI..... | 45 | +| 14.5 | Temporary identities ..... | 46 | +| 14.6 | Alternative NAI..... | 46 | +| 14.7 | W-APN..... | 46 | +| 14.7.1 | Format of W-APN Network Identifier ..... | 47 | +| 14.7.2 | Format of W-APN Operator Identifier ..... | 47 | +| 14.7.3 | Alternative Format of W-APN Operator Identifier ..... | 48 | +| 14.8 | Emergency Realm and Emergency NAI for Emergency Cases..... | 48 | +| 15 | Identification of Multimedia Broadcast/Multicast Service ..... | 49 | +| 15.1 | Introduction ..... | 49 | +| 15.2 | Structure of TMGI..... | 49 | +| 15.3 | Structure of MBMS SAI ..... | 50 | +| 15.4 | Home Network Realm..... | 50 | +| 16 | Numbering, addressing and identification within the GAA subsystem..... | 50 | +| 16.1 | Introduction ..... | 50 | +| 16.2 | BSF address..... | 51 | +| 17 | Numbering, addressing and identification within the Generic Access Network ..... | 51 | +| 17.1 | Introduction ..... | 51 | +| 17.2 | Network Access Identifiers ..... | 51 | +| 17.2.1 | Home network realm ..... | 51 | +| 17.2.2 | Full Authentication NAI..... | 52 | +| 17.2.3 | Fast Re-authentication NAI..... | 52 | +| 17.3 | Node Identifiers..... | 53 | +| 17.3.1 | Home network domain name..... | 53 | +| 17.3.2 | Provisioning GANC-SEGW identifier ..... | 53 | +| 17.3.3 | Provisioning GANC identifier ..... | 54 | +| 18 | Addressing and Identification for IMS Service Continuity and Single-Radio Voice Call Continuity..... | 54 | +| 18.1 | Introduction ..... | 54 | +| 18.2 | CS Domain Routeing Number (CSRN) ..... | 54 | +| 18.3 | IP Multimedia Routeing Number (IMRN)..... | 54 | +| 18.4 | Session Transfer Number (STN)..... | 55 | +| 18.5 | Session Transfer Identifier (STI)..... | 55 | +| 18.6 | Session Transfer Number for Single Radio Voice Call Continuity (STN-SR)..... | 55 | +| 18.7 | Correlation MSISDN..... | 55 | +| 18.8 | Transfer Identifier for CS to PS Single Radio Voice Call Continuity (STI-rSR) ..... | 55 | +| 18.9 | Additional MSISDN..... | 55 | +| 19 | Numbering, addressing and identification for the Evolved Packet Core (EPC)..... | 56 | +| 19.1 | Introduction ..... | 56 | +| 19.2 | Home Network Realm/Domain..... | 56 | +| 19.3 | 3GPP access to non-3GPP access interworking..... | 56 | +| 19.3.1 | Introduction ..... | 56 | +| 19.3.2 | Root NAI ..... | 57 | + +| | | | +|------------|---------------------------------------------------------------------------------|----| +| 19.3.3 | Decorated NAI..... | 57 | +| 19.3.4 | Fast Re-authentication NAI..... | 58 | +| 19.3.5 | Pseudonym Identities..... | 58 | +| 19.3.6 | Emergency NAI for Limited Service State..... | 59 | +| 19.4 | Identifiers for Domain Name System procedures ..... | 59 | +| 19.4.1 | Introduction ..... | 59 | +| 19.4.2 | Fully Qualified Domain Names (FQDNs) ..... | 60 | +| 19.4.2.1 | General..... | 60 | +| 19.4.2.2 | Access Point Name FQDN (APN-FQDN) ..... | 60 | +| 19.4.2.2.1 | Structure ..... | 60 | +| 19.4.2.2.2 | Void..... | 61 | +| 19.4.2.2.3 | Void..... | 61 | +| 19.4.2.2.4 | Void..... | 61 | +| 19.4.2.3 | Tracking Area Identity (TAI) ..... | 61 | +| 19.4.2.4 | Mobility Management Entity (MME)..... | 61 | +| 19.4.2.5 | Routing Area Identity (RAI) - EPC ..... | 62 | +| 19.4.2.6 | Serving GPRS Support Node (SGSN) within SGSN pool ..... | 62 | +| 19.4.2.7 | Target RNC-ID for U-TRAN ..... | 62 | +| 19.4.2.8 | DNS subdomain for operator usage in EPC ..... | 63 | +| 19.4.2.9 | ePDG Fully Qualified Domain Name..... | 63 | +| 19.4.2.10 | Global eNodeB-ID for eNodeB ..... | 63 | +| 19.4.3 | Service and Protocol service names for 3GPP ..... | 64 | +| 19.5 | Access Network Identity ..... | 64 | +| 19.6 | E-UTRAN Cell Identity (ECI) and E-UTRAN Cell Global Identification (ECGI)..... | 65 | +| 19.7 | Identifiers for communications with packet data networks and applications ..... | 65 | +| 19.7.1 | Introduction ..... | 65 | +| 19.7.2 | External Identifier..... | 65 | +| 20 | Addressing and Identification for IMS Centralized Services ..... | 66 | +| 20.1 | Introduction ..... | 66 | +| 20.2 | UE based solution..... | 66 | +| 20.3 | Network based solution..... | 66 | +| 20.3.1 | General ..... | 66 | +| 20.3.2 | Home network domain name..... | 66 | +| 20.3.3 | Private User Identity ..... | 67 | +| 20.3.4 | Public User Identity ..... | 67 | +| 20.3.5 | Conference Factory URI..... | 67 | +| 21 | Addressing and Identification for Dual Stack Mobile IPv6 (DSMIPv6)..... | 67 | +| 21.1 | Introduction ..... | 67 | +| 21.2 | Home Agent – Access Point Name (HA-APN) ..... | 67 | +| 21.2.1 | General ..... | 67 | +| 21.2.2 | Format of HA-APN Network Identifier ..... | 68 | +| 21.2.3 | Format of HA-APN Operator Identifier ..... | 68 | +| 22 | Addressing and identification for ANDSF ..... | 69 | +| 22.1 | Introduction ..... | 69 | +| 22.2 | ANDSF Server Name (ANDSF-SN)..... | 69 | +| 22.2.1 | General ..... | 69 | +| 22.2.2 | Format of ANDSF-SN..... | 69 | +| 23 | Numbering, addressing and identification for the Relay Node OAM System..... | 70 | +| 23.1 | Introduction ..... | 70 | +| 23.2 | OAM System Realm/Domain ..... | 70 | +| 23.3 | Identifiers for Domain Name System procedures ..... | 70 | +| 23.3.1 | Introduction ..... | 70 | +| 23.3.2 | Fully Qualified Domain Names (FQDNs) ..... | 70 | +| 23.3.2.1 | General..... | 70 | +| 23.3.2.2 | Relay Node Vendor-Specific OAM System..... | 71 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------|-----------| +| Annex A (informative): | Colour Codes ..... | 72 | +| A.1 | Utilization of the BSIC ..... | 72 | +| A.2 | Guidance for planning..... | 72 | +| A.3 | Example of PLMN Colour Codes (NCCs) for the European region ..... | 73 | +| Annex B (normative): | IMEI Check Digit computation ..... | 74 | +| B.1 | Representation of IMEI..... | 74 | +| B.2 | Computation of CD for an IMEI..... | 74 | +| B.3 | Example of computation ..... | 74 | +| Annex C (normative): | Naming convention..... | 76 | +| C.1 | Routing Area Identities ..... | 76 | +| C.2 | GPRS Support Nodes..... | 77 | +| C.3 | Target ID..... | 77 | +| Annex D (informative): | Applicability and use of the ".3gppnetwork.org" domain name..... | 78 | +| Annex E (normative): | Procedure for sub-domain allocation ..... | 79 | +| Annex F (informative): | Change history..... | 80 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document defines the principal purpose and use of International Mobile station Equipment Identities (IMEI) within the digital cellular telecommunications system and 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 principal purpose and use of International Mobile station Equipment Identities (IMEI) within the digital cellular telecommunications system and the 3GPP system. + +The present document defines: + +- a) an identification plan for mobile subscribers in the GSM system; +- b) principles of assigning telephone and ISDN numbers to MSs in the country of registration of the MS; +- c) principles of assigning Mobile Station (MS) roaming numbers to visiting MSs; +- d) an identification plan for location areas, routing areas, and base stations in the GSM system; +- e) an identification plan for MSCs, SGSNs, GGSNs, and location registers in the GSM system; +- f) principles of assigning international mobile equipment identities; +- g) principles of assigning zones for regional subscription; +- h) an identification plan for groups of subscribers to the Voice Group Call Service (VGCS) and to the Voice Broadcast Service (VBS); and identification plan for voice group calls and voice broadcast calls; an identification plan for group call areas; +- i) principles for assigning Packet Data Protocol (PDP) addresses to mobile stations; +- j) an identification plan for point-to-multipoint data transmission groups; +- k) an identification plan for CN domain, RNC and service area in the UTRAN system. +- l) an identification plan for mobile subscribers in the WLAN system. +- m) addressing and identification for IMS Service Continuity +- n) an identification plan together with principles of assignment and mapping of identities for the Evolved Packet System + +## 1.1 References + +### 1.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 TS 21.905: "Vocabulary for 3GPP Specifications ". +- [2] 3GPP TS 23.008: "Organization of subscriber data". +- [3] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2" +- [4] 3GPP TS 23.070: "Routeing of calls to/from Public Data Networks (PDN)". +- [5] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3". + +- [6] 3GPP TS 29.060: "GPRS Tunnelling protocol (GTP) across the Gn and Gp interface". +- [7] 3GPP TS 43.020: "Digital cellular telecommunications system (Phase 2+); Security related network functions". +- [8] void +- [9] 3GPP TS 51.011: " Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface". +- [10] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [11] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and mobile users". +- [12] ITU-T Recommendation E.213: "Telephone and ISDN numbering plan for land Mobile Stations in public land mobile networks (PLMN)". +- [13] ITU-T Recommendation X.121: "International numbering plan for public data networks". +- [14] IETF RFC 791: "Internet Protocol". +- [15] IETF RFC 2373: "IP Version 6 Addressing Architecture". +- [16] 3GPP TS 25.401: "UTRAN Overall Description". +- [17] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling". +- [18] IETF RFC 2181: "Clarifications to the DNS Specification". +- [19] IETF RFC 1035: "Domain Names - Implementation and Specification". +- [20] IETF RFC 1123: "Requirements for Internet Hosts -- Application and Support". +- [21] IETF RFC 2462: "IPv6 Stateless Address Autoconfiguration". +- [22] IETF RFC 3041: "Privacy Extensions for Stateless Address Autoconfiguration in IPv6". +- [23] 3GPP TS 23.236: "Intra Domain Connection of RAN Nodes to Multiple CN Nodes". +- [24] 3GPP TS 23.228: "IP Multimedia (IM) Subsystem – Stage 2" +- [25] Void +- [26] IETF RFC 3261: "SIP: Session Initiation Protocol" +- [27] 3GPP TS 31.102: "Characteristics of the USIM Application." +- [28] Void +- [29] 3GPP TS 44.118: "Radio Resource Control (RRC) Protocol, Iu Mode". +- [30] 3GPP TS 23.073: "Support of Localised Service Area (SoLSA); Stage 2" +- [31] 3GPP TS 29.002: "Mobile Application Part (MAP) specification" +- [32] 3GPP TS 22.016: "International Mobile Equipment Identities (IMEI)" +- [33] Void +- [34] Void +- [35] 3GPP TS 45.056: "CTS-FP Radio Sub-system" +- [36] 3GPP TS 42.009: "Security aspects" [currently not being raised to rel-5 – Pete H. looking into it] +- [37] 3GPP TS 25.423: "UTRAN Iur interface RNSAP signalling" +- [38] 3GPP TS 25.419: "UTRAN Iu-BC interface: Service Area Broadcast Protocol (SABP)" + +- [39] 3GPP TS 25.410: "UTRAN Iu Interface: General Aspects and Principles" +- [40] ISO/IEC 7812: "Identification cards - Numbering system and registration procedure for issuer identifiers" +- [41] Void +- [42] 3GPP TS 33.102 "3G security; Security architecture" +- [43] 3GPP TS 43.130: "Iur-g interface; Stage 2" +- [45] IETF RFC 3966: "The tel URI for Telephone Numbers" +- [46] 3GPP TS 44.068: "Group Call Control (GCC) protocol". +- [47] 3GPP TS 44.069: "Broadcast Call Control (BCC) Protocol ". +- [48] 3GPP TS 24.234: "3GPP System to WLAN Interworking; UE to Network protocols; Stage 3". +- [49] Void +- [50] IETF RFC 4187: "EAP AKA Authentication". +- [51] IETF RFC 4186: "EAP SIM Authentication". +- [52] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description" +- [53] IETF RFC 4282: "The Network Access Identifier". +- [54] IETF RFC 2279: "UTF-8, a transformation format of ISO 10646". +- [55] 3GPP TS 33.234: "Wireless Local Area Network (WLAN) interworking security". +- [56] Void +- [58] 3GPP TS 33.221 "Generic Authentication Architecture (GAA); Support for Subscriber Certificates". +- [60] IEEE 1003.1-2004, Part 1: Base Definitions +- [61] 3GPP TS 43.318: "Generic Access to the A/Gb interface; Stage 2" +- [62] 3GPP TS 44.318: "Generic Access (GA) to the A/Gb interface; Mobile GA interface layer 3 specification" +- [63] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks" +- [64] IETF RFC 2606: "Reserved Top Level DNS Names" +- [65] Void +- [66] 3GPP TS 51.011 Release 4: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface" +- [67] 3GPP2 X.S0013-004: "IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3" +- [68] 3GPP TS 23.402: "Architecture Enhancements for non-3GPP accesses" +- [69] 3GPP TS 33.402: "3GPP System Architecture Evolution: Security Aspects of non-3GPP accesses" +- [70] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services; Stage 2" +- [71] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity" +- [72] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access" + +- [73] 3GPP TS 29.303: "Domain Name System Procedures; Stage 3" +- [74] IETF RFC 3958: "Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)" +- [75] Void +- [76] 3GPP TS 23.237: "Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems" +- [77] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3" +- [78] 3GPP TS 23.273: "Evolved Packet System; 3GPP EPS AAA Interfaces" +- [79] IETF RFC 7254: "A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)" +- [80] IETF RFC 4122: "A Universally Unique Identifier (UUID) URN Namespace". +- [81] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [82] IETF RFC5448: "Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA) " +- [83] 3GPP TS 22.011: "Service accessibility". +- [84] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN) ; S1 Application Protocol (SIAP)". +- [85] Guidelines for use of a 48-bit Extended Unique Identifier (EUI-48™), + +- [86] GUIDELINES FOR 64-BIT GLOBAL IDENTIFIER (EUI-64) REGISTRATION AUTHORITY, + +- [87] The Broadband Forum TR-069: "CPE WAN Management Protocol v1.1", Issue 1 Amendment 2, December 2007 +- [88] 3GPP TS 29.274: "Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3". +- [89] 3GPP TS 33.401: "3GPP System Architecture Evolution: Security Architecture". +- [90] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [91] 3GPP TS 36.300: " Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [92] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC)". +- [93] 3GPP TS 31.103: "IP Multimedia Services Identity Module (ISIM) application". +- [94] IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)". +- [95] 3GPP TS 29.229: " Cx and Dx interfaces based on the Diameter protocol; Protocol details". +- [96] 3GPP TS 29.329: " Sh Interface based on the Diameter protocol; Protocol details". +- [97] 3GPP TS 29.165: "Inter-IMS Network to Network Interface (NNI); Stage 3". +- [98] 3GPP TS 23.682: "Architecture Enhancements to facilitate communications with Packet Data Networks and Applications". + +- [99] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol". +- [100] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) – Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol". +- [101] 3GPP TS 23.251: "Network Sharing; Architecture and functional description". + +### 1.1.2 Informative references + +- [44] "COMPLEMENT TO ITU-T RECOMMENDATION E.212 (11/98)", Annex to ITU Operational Bulletin No. 741 – 1.VI.200; This is published on the ITU-T website, whose home page is at +- [57] GSMA PRD IR.34 "Inter-PLMN Backbone Guidelines" +- [59] Void + +## 1.2 Abbreviations + +For the purposes of the present document, the abbreviations defined in 3GPP TS 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]. + +| | | +|------|---------------------------------------| +| EPS | Evolved Packet System | +| GUTI | Globally Unique Temporary UE Identity | +| ICS | IMS Centralized Services | +| MTC | Machine Type Communication | +| UUID | Universally Unique Identifier | + +## 1.3 General comments to references + +The identification plan for mobile subscribers defined below is that defined in ITU-T Recommendation E.212. + +The ISDN numbering plan for MSs and the allocation of mobile station roaming numbers is that defined in ITU-T Recommendation E.213. Only one of the principles for allocating ISDN numbers is proposed for PLMNs. Only the method for allocating MS roaming numbers contained in the main text of ITU-T Recommendation E.213 is recommended for use in PLMNs. If there is any difference between the present document and the ITU-T Recommendations, the former shall prevail. + +For terminology, see also ITU-T Recommendations E.164 and X.121. + +## 1.4 Conventions on bit ordering + +The following conventions hold for the coding of the different identities appearing in the present document and in other GSM Technical Specifications if not indicated otherwise: + +- the different parts of an identity are shown in the figures in order of significance; +- the most significant part of an identity is on the left part of the figure and the least significant on the right. + +When an identity appears in other Technical Specifications, the following conventions hold if not indicated otherwise: + +- digits are numbered by order of significance, with digit 1 being the most significant; +- bits are numbered by order of significance, with the lowest bit number corresponding to the least significant bit. + +# 2 Identification of mobile subscribers + +## 2.1 General + +A unique International Mobile Subscriber Identity (IMSI) shall be allocated to each mobile subscriber in the GSM/UMTS/EPS system. + +NOTE: This IMSI is the concept referred to by ITU-T as "International Mobile Station Identity". + +In order to support the subscriber identity confidentiality service the VLRs, SGSNs and MME may allocate Temporary Mobile Subscriber Identities (TMSI) to visiting mobile subscribers. The VLR, SGSN and MME must be capable of correlating an allocated TMSI with the IMSI of the MS to which it is allocated. + +An MS may be allocated three TMSIs, one for services provided through the MSC, one for services provided through the SGSN (P-TMSI for short) and one for the services provided via the MME (M-TMSI part GUTI for short). + +For addressing on resources used for GPRS, a Temporary Logical Link Identity (TLLI) is used. The TLLI to use is built by the MS either on the basis of the P-TMSI (local or foreign TLLI), or directly (random TLLI). + +In order to speed up the search for subscriber data in the VLR a supplementary Local Mobile Station Identity (LMSI) is defined. + +The LMSI may be allocated by the VLR at location updating and is sent to the HLR together with the IMSI. The HLR makes no use of it but includes it together with the IMSI in all messages sent to the VLR concerning that MS. + +## 2.2 Composition of IMSI + +IMSI is composed as shown in figure 1. + +![Diagram illustrating the structure of IMSI. The IMSI is shown as a sequence of three parts: MCC (Mobile Country Code), MNC (Mobile Network Code), and MSIN (Mobile Subscriber Identification Number). The MCC is 3 digits long. The MNC is 2 or 3 digits long. The MSIN is the remaining part of the IMSI. The total length of the IMSI is not more than 15 digits. The NMSI (National Mobile Subscriber Identity) is the combination of the MNC and the MSIN.](2bc39576969969ffe6d3f3d5264bba75_img.jpg) + +The diagram shows the structure of an IMSI. At the top, a double-headed arrow spans the entire length and is labeled "Not more than 15 digits". Below this, the IMSI is broken down into three components: MCC, MNC, and MSIN. The MCC is shown as a box labeled "MCC" with a double-headed arrow above it labeled "3 digits". The MNC is shown as a box labeled "MNC" with a double-headed arrow above it labeled "2 or 3". The MSIN is shown as a box labeled "MSIN". Below the MNC and MSIN boxes, a double-headed arrow spans both and is labeled "NMSI". At the bottom, a long double-headed arrow spans the entire length of the MCC, MNC, and MSIN boxes and is labeled "IMSI". + +Diagram illustrating the structure of IMSI. The IMSI is shown as a sequence of three parts: MCC (Mobile Country Code), MNC (Mobile Network Code), and MSIN (Mobile Subscriber Identification Number). The MCC is 3 digits long. The MNC is 2 or 3 digits long. The MSIN is the remaining part of the IMSI. The total length of the IMSI is not more than 15 digits. The NMSI (National Mobile Subscriber Identity) is the combination of the MNC and the MSIN. + +Figure 1: Structure of IMSI + +IMSI is composed of three parts: + +- 1) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the mobile subscriber; +- 2) Mobile Network Code (MNC) consisting of two or three digits for GSM/UMTS applications. The MNC identifies the home PLMN of the mobile subscriber. The length of the MNC (two or three digits) depends on the value of the MCC. A mixture of two and three digit MNC codes within a single MCC area is not recommended and is outside the scope of this specification. +- 3) Mobile Subscriber Identification Number (MSIN) identifying the mobile subscriber within a PLMN. + +The National Mobile Subscriber Identity (NMSI) consists of the Mobile Network Code and the Mobile Subscriber Identification Number. + +## 2.3 Allocation principles + +IMSI shall consist of decimal digits (0 through 9) only. + +The number of digits in IMSI shall not exceed 15. + +The allocation of Mobile Country Codes (MCCs) is administered by the ITU-T. The current allocation is given in the COMPLEMENT TO ITU-T RECOMMENDATION E.212 [44]. + +The allocation of National Mobile Subscriber Identity (NMSI) is the responsibility of each administration. + +If more than one PLMN exists in a country, the same Mobile Network Code should not be assigned to more than one PLMN. + +The allocation of IMSIs should be such that not more than the digits MCC + MNC of the IMSI have to be analysed in a foreign PLMN for information transfer. + +## 2.4 Structure of TMSI + +Since the TMSI has only local significance (i.e. within a VLR and the area controlled by a VLR, or within an SGSN and the area controlled by an SGSN, or within an MME and the area controlled by an MME), the structure and coding of it can be chosen by agreement between operator and manufacturer in order to meet local needs. + +The TMSI consists of 4 octets. It can be coded using a full hexadecimal representation. + +In order to avoid double allocation of TMSIs after a restart of an allocating node, some part of the TMSI may be related to the time when it was allocated or contain a bit field which is changed when the allocating node has recovered from the restart. + +In areas where both MSC-based services and SGSN-based services are provided, some discrimination is needed between the allocation of TMSIs for MSC-based services and the allocation of TMSIs for SGSN-based services. The discrimination shall be done on the 2 most significant bits, with values 00, 01, and 10 being used by the VLR, and 11 being used by the SGSN. + +If intra domain connection of RAN nodes to multiple CN nodes as described in 3GPP TS 23.236 [23] is applied in the MSC/VLR or SGSN, then the NRI shall be part of the TMSI. The NRI has a configurable length of 0 to 10 bits. A configurable length of 0 bits indicates that the NRI is not used and this feature is not applied in the MSC/VLR or SGSN. The NRI shall be coded in bits 23 to 14. An NRI shorter than 10 bits shall be encoded with the most significant bit of the NRI field in bit 23. + +The TMSI shall be allocated only in ciphered form. See also 3GPP TS 43.020 [7] and 3GPP TS 33.102 [42]. + +The network shall not allocate a TMSI with all 32 bits equal to 1 (this is because the TMSI must be stored in the SIM, and the SIM uses 4 octets with all bits equal to 1 to indicate that no valid TMSI is available). + +To allow for eventual modifications of the management of the TMSI code space management, MSs shall not check if an allocated TMSI belongs to the range allocated to the allocating node. MSs shall use an allocated TMSI according to the specifications, whatever its value. + +## 2.5 Structure of LMSI + +The LMSI consists of 4 octets and may be allocated by the VLR. The VLR shall not allocate the value zero. The value zero is reserved to indicate that an LMSI parameter sent from the HLR to the VLR shall not be interpreted. + +## 2.6 Structure of TLLI + +A TLLI is built by the MS or by the SGSN either on the basis of the P-TMSI (local or foreign TLLI), or directly (random or auxiliary TLLI), according to the following rules. + +The TLLI consists of 32 bits, numbered from 0 to 31 by order of significance, with bit 0 being the LSB. + +A local TLLI is built by an MS which has a valid P-TMSI as follows: + +bits 31 down to 30 are set to 1; and + +bits 29 down to 0 are set equal to bits 29 to 0 of the P-TMSI. + +A foreign TLLI is built by an MS which has a valid P-TMSI as follows: + +bit 31 is set to 1 and bit 30 is set to 0; and + +bits 29 down to 0 are set equal to bits 29 to 0 of the P-TMSI. + +A random TLLI is built by an MS as follows: + +bit 31 is set to 0; + +bits 30 down to 27 are set to 1; and + +bits 0 to 26 are chosen randomly. + +An auxiliary TLLI is built by the SGSN as follows: + +bit 31 is set to 0; + +bits 30 down to 28 are set to 1; + +bit 27 is set to 0; and + +bits 0 to 26 can be assigned independently. + +Other types of TLLI may be introduced in the future. + +Part of the TLLI codespace is re-used in GERAN to allow for the inclusion of the GERAN Radio Network Temporary Identifier in RLC/MAC messages. The G-RNTI is defined in 3GPP TS 44.118 [29]. + +The structure of the TLLI is summarised in table 1. + +**Table 1: TLLI structure** + +| 31 | 30 | 29 | 28 | 27 | 26 to 0 | Type of TLLI | +|----|----|----|----|----|---------|-----------------------------| +| 1 | 1 | T | T | T | T | Local TLLI | +| 1 | 0 | T | T | T | T | Foreign TLLI | +| 0 | 1 | 1 | 1 | 1 | R | Random TLLI | +| 0 | 1 | 1 | 1 | 0 | A | Auxiliary TLLI | +| 0 | 1 | 1 | 0 | X | X | Reserved | +| 0 | 1 | 0 | X | X | X | Reserved | +| 0 | 0 | 0 | 0 | G | G | Part of the assigned G-RNTI | +| 0 | 0 | 0 | 1 | R | R | Random G-RNTI | + +'T', 'R', 'A' and 'X' indicate bits which can take any value for the type of TLLI. More precisely, 'T' indicates bits derived from a P-TMSI, 'R' indicates bits chosen randomly, 'A' indicates bits chosen by the SGSN, 'G' indicates bits derived from the assigned G-RNTI and 'X' indicates bits in reserved ranges. + +## 2.7 Structure of P-TMSI Signature + +The P-TMSI Signature consists of 3 octets and may be allocated by the SGSN. + +The network shall not allocate a P-TMSI Signature with all 24 bits equal to 1 (this is because the P-TMSI Signature must be stored in the SIM, and the SIM uses 3 octets with all bits equal to 1 to indicate that no valid P-TMSI signature is available). + +## 2.8 Globally Unique Temporary UE Identity (GUTI) + +### 2.8.1 Introduction + +The purpose of the GUTI is to provide an unambiguous identification of the UE that does not reveal the UE or the user's permanent identity in the Evolved Packet System (EPS). It also allows the identification of the MME and network. It can be used by the network and the UE to establish the UE's identity during signalling between them in the EPS. See 3GPP TS 23.401 [72]. + +The GUTI has two main components: + +- one that uniquely identifies the MME which allocated the GUTI; and + +- one that uniquely identifies the UE within the MME that allocated the GUTI. + +Within the MME, the mobile shall be identified by the M-TMSI. + +The Globally Unique MME Identifier (GUMMEI) shall be constructed from the MCC, MNC and MME Identifier (MMEI). + +The MMEI shall be constructed from an MME Group ID (MMEGI) and an MME Code (MMEC). + +The GUTI shall be constructed from the GUMMEI and the M-TMSI. + +For paging purposes, the mobile is paged with the S-TMSI. The S-TMSI shall be constructed from the MMEC and the M-TMSI. + +The operator shall need to ensure that the MMEC is unique within the MME pool area and, if overlapping pool areas are in use, unique within the area of overlapping MME pools. + +NOTE: In some network sharing cases it is required that the MMEC and NRI values are coordinated between the sharing operators, as described in 3GPP TS 23.251 [101]. In order to achieve CS/PS coordination in shared GERAN/UTRAN networks, the MMEC included in the GUTI can be set to identify the CS operator serving the UE. + +The GUTI shall be used to support subscriber identity confidentiality, and, in the shortened S-TMSI form, to enable more efficient radio signalling procedures (e.g. paging and Service Request). + +The format and size of the GUTI is therefore the following: + +$\langle \text{GUTI} \rangle = \langle \text{GUMMEI} \rangle \langle \text{M-TMSI} \rangle$ , + +where $\langle \text{GUMMEI} \rangle = \langle \text{MCC} \rangle \langle \text{MNC} \rangle \langle \text{MME Identifier} \rangle$ + +and $\langle \text{MME Identifier} \rangle = \langle \text{MME Group ID} \rangle \langle \text{MME Code} \rangle$ + +MCC and MNC shall have the same field size as in earlier 3GPP systems. + +M-TMSI shall be of 32 bits length. + +MME Group ID shall be of 16 bits length. + +MME Code shall be of 8 bits length. + +### 2.8.2 Mapping between Temporary and Area Identities for the EUTRAN and the UTRAN/GERAN based systems + +#### 2.8.2.0 Introduction + +This section provides information on the mapping of the temporary and location area identities, e.g. for the construction of the Routeing Area Update Request message in GERAN/UTRAN or Tracking Area Update Request message in E-UTRAN. + +In GERAN and UTRAN: + +$\langle \text{RAI} \rangle = \langle \text{MCC} \rangle \langle \text{MNC} \rangle \langle \text{LAC} \rangle \langle \text{RAC} \rangle$ + +$\langle \text{P-TMSI/TLLI} \rangle$ includes the mapped NRI + +P-TMSI shall be of 32 bits length where the two topmost bits are reserved and always set to '11'. Hence, for a UE which may handover to GERAN/UTRAN (based on subscription and UE capabilities), the corresponding bits in the M-TMSI are set to '11' (see subclause 2.8.2.1.3). + +3GPP TS 23.236 [23] specifies that the NRI field is of variable length and shall be mapped into the P-TMSI starting at bit 23 and down to bit 14. The most significant bit of the NRI is located at bit 23 of the P-TMSI regardless of the configured length of the NRI. To support mobility between GERAN/UTRAN and E-UTRAN, the NRI length is limited to a maximum of 8 bits to be compatible for the mapping to MME Code within GUTI (see subclause 2.8.2.2). + +The P-TMSI and NRI are defined elsewhere in this specification. + +In the case of a combined MME-SGSN node, the NRI of the SGSN part and the MME code of the MME part, refer to the same combined node. RAN configuration allows NAS messages on GERAN/UTRAN and E-UTRAN to be routed to the same combined node. The same or different values of NRI and MME code may be used for a combined node. + +#### 2.8.2.1 Mapping from GUTI to RAI, P-TMSI and P-TMSI signature + +##### 2.8.2.1.1 Introduction + +This subclause addresses the case when a UE moves from an MME to an SGSN. The SGSN may be either an S4 SGSN or a Gn/Gp SGSN. + +##### 2.8.2.1.2 Mapping in the UE + +When a UE moves from an E-UTRAN to a GERAN/UTRAN, the UE needs to map the GUTI to an RAI, a P-TMSI and a P-TMSI Signature, for them to be sent to the SGSN. For GERAN, the TLLI is derived from the P-TMSI by the UE and is a foreign TLLI (see subclause 2.6). + +The mapping of the GUTI shall be done to the combination of RAI of GERAN / UTRAN and the P-TMSI: + +E-UTRAN maps to GERAN/UTRAN + +E-UTRAN maps to GERAN/UTRAN + +E-UTRAN maps to GERAN/UTRAN + +E-UTRAN maps to GERAN/UTRAN and is also copied into the 8 Most Significant Bits of the NRI field within the P-TMSI; + +E-UTRAN maps as follows: + +- 6 bits of the E-UTRAN starting at bit 29 and down to bit 24 are mapped into bit 29 and down to bit 24 of the GERAN/UTRAN ; +- 16 bits of the E-UTRAN starting at bit 15 and down to bit 0 are mapped into bit 15 and down to bit 0 of the GERAN/UTRAN ; +- and the remaining 8 bits of the E-UTRAN are mapped into the 8 Most Significant Bits of the field. + +The UE shall fill the remaining 2 octets of the according to subclauses 9.1.1, 9.4.1, 10.2.1, or 10.5.1 of 3GPP TS.33.401 [89], as appropriate, for RAU/Attach procedures. + +For UTRAN, the 10-bit long NRI bits are masked out from the P-TMSI and are also supplied by the UE to the RAN node as IDNNS (Intra Domain NAS Node Selector) (see 3GPP TS 23.236 [23]). However, the RAN configured NRI length should not exceed 8 bits. + +##### 2.8.2.1.3 Mapping in the old MME + +A new SGSN attempts to retrieve information regarding the UE, e.g. the IMSI, from the old MME. In order to find the UE context, the MME needs to map the RAI, P-TMSI (or TLLI) and the P-TMSI Signature (sent by the SGSN) to create the GUTI and compare it with the stored GUTI. + +The MME shall perform a reverse mapping to the mapping procedure specified in subclause 2.8.2.1.2 "Mapping in the UE" (see 3GPP TS 29.060 [6] and 3GPP TS 29.274 [88] for specifics of the messaging). For the reverse mapping, the E-UTRAN within the GUTI shall be set either to bits 23 to 16 of the GERAN/UTRAN (i.e., the NRI field) or to the GERAN/UTRAN . For GERAN TLLI, the old MME replaces the two topmost bits of TLLI, received from new SGSN via GTPv1, with '11' before mapping the TLLI to the GUTI used for looking up the "UE Context". + +#### 2.8.2.2 Mapping from RAI and P-TMSI to GUTI + +##### 2.8.2.2.1 Introduction + +This subclause addresses the case when a UE moves from an SGSN to an MME (i.e. during a TAU or an Attach to MME). The SGSN may be either an S4 SGSN or a Gn/Gp SGSN. + +##### 2.8.2.2.2 Mapping in the UE + +When the UE moves from the GERAN/UTRAN to the E-UTRAN, the UE needs to map the RAI and P-TMSI to a GUTI to be sent to the MME. The P-TMSI signature is sent intact to the MME. + +The mapping of P-TMSI (TLLI) and RAI in GERAN/UTRAN to GUTI in E-UTRAN shall be performed as follows: + +GERAN/UTRAN maps to E-UTRAN + +GERAN/UTRAN maps to E-UTRAN + +GERAN/UTRAN maps to E-UTRAN + +GERAN/UTRAN maps into bit 23 and down to bit 16 of the M-TMSI + +The 8 most significant bits of GERAN/UTRAN map to the MME code. + +GERAN/UTRAN maps as follows: + +- 6 bits of the GERAN/UTRAN starting at bit 29 and down to bit 24 are mapped into bit 29 and down to bit 24 of the E-UTRAN ; +- 16 bits of the GERAN/UTRAN starting at bit 15 and down to bit 0 are mapped into bit 15 and down to bit 0 of the E-UTRAN . + +The values of and shall be disjoint, so that they can be differentiated. + +The most significant bit of the shall be set to zero; and the most significant bit of shall be set to one. Based on this definition, the most significant bit of the can be used to distinguish the node type, i.e. whether it is an MME or SGSN. The UE copies the received old SGSN's into the when sending a message to an MME, regardless of the value of the most significant bit of the . + +In networks where this definition is not applied (e.g. in networks already configured with LAC with the most significant bit set to 1 before LTE deployment), the information in the TAU/RAU request indicating whether the provided GUTI/P-TMSI is "native" (i.e. no system change) or "mapped" (i.e. system change) can be used to distinguish the node type for UEs implemented according to this release of the specification (see 3GPP TS 24.301 [90] and 3GPP TS 24.008 [5]). Specific network implementations still satisfying 3GPP standard interfaces can be used for pre-Rel-10 UEs to distinguish the node type. + +NOTE 1: As an example, at NAS level, the MME/SGSN can retrieve the old SGSN/MME by using additional GUTI/additional RAI/P-TMSI with double DNS query to solve the first time the UE moves between E-UTRAN and GERAN/UTRAN. As another example, the MME/SGSN can retrieve the old SGSN/MME by using double DNS query. + +##### 2.8.2.2.3 Mapping in the new MME + +In order to retrieve the UE's information, e.g. the IMSI, from the old SGSN, the new MME extracts only the RAI and P-TMSI from the GUTI via the reverse mapping procedure to that specified in subclause 2.8.2.2.2. This is done in order to be able to include the mapped RAI and P-TMSI, along with the P-TMSI Signature received by the MME from the UE, in the corresponding message sent to the old SGSN (see 3GPP TS 29.060 [6] and 3GPP TS 29.274 [88] for specifics of the messaging). The old SGSN compares the received RAI, P-TMSI and P-TMSI Signature with the stored values for identifying the UE. + +## 2.9 Structure of the S-Temporary Mobile Subscriber Identity (S-TMSI) + +The S-TMSI is the shortened form of the GUTI to enable more efficient radio signalling procedures (e.g. paging and Service Request). For paging purposes, the mobile is paged with the S-TMSI. The S-TMSI shall be constructed from the MMEC and the M-TMSI: + + = + +See subclause 2.8 for these definitions and the mapping. + +# --- 3 Numbering plan for mobile stations + +## 3.1 General + +The structure of the following numbers is defined below: + +- the number used by a subscriber of a fixed (or mobile) network to call a mobile station of a PLMN; +- the network addresses used for packet data communication between a mobile station and a fixed (or mobile) station; +- mobile station roaming numbers. + +One or more numbers of the ISDN numbering plan shall be assigned to a mobile station to be used for all calls to that station, i.e. the assignment of at least one MSISDN to a mobile station is mandatory. As an exception, GPRS and EPS allow for operation whereby a MSISDN is not allocated as part of the subscription data (see 3GPP TS 23.060 [3] subclause 5.3.17 and 3GPP TS 23.401 [72]). + +NOTE: For card operated stations the ISDN number should be assigned to the holder of the card (personal number). + +## 3.2 Numbering plan requirements + +In principle, it should be possible for any subscriber of the ISDN or PSTN to call any MS in a PLMN. This implies that ISDN numbers for MSs should comply with the ISDN numbering plan in the home country of the MS. + +The ISDN numbers of MSs should be composed in such a way that standard ISDN/PSTN charging can be used for calls to MSs. + +It should be possible for each administration to develop its own independent numbering/addressing plan for MSs. + +The numbering/addressing plan should not limit the possibility for MSs to roam among PLMNs. + +It should be possible to change the IMSI without changing the ISDN number allocated to an MS and vice versa. + +In principle, it should be possible for any subscriber of the CSPDN/PSPDN to call any MS in a PLMN. This implies that it may be necessary for an MS to have a X.121 number. + +In principle, it should be possible for any fixed or mobile terminal to communicate with a mobile terminal using an IP v4 address or IP v6 address. + +## 3.3 Structure of MS international PSTN/ISDN number (MSISDN) + +MS international ISDN numbers are allocated from the ITU-T Recommendation E.164 numbering plan; see also ITU-T Recommendation E.213. The structure of the MS international ISDN number will then be as shown in figure 2. + +![Diagram illustrating the Number Structure of MSISDN. It shows three components: CC (Country Code), NDC (National Destination Code), and SN (Subscriber Number). The NDC and SN are grouped together as the 'National (significant) mobile number'. The CC, NDC, and SN together form the 'Mobile station international ISDN number'.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +The diagram shows the structure of an MSISDN. At the top, three boxes labeled 'CC', 'NDC', and 'SN' are shown. Below the 'NDC' and 'SN' boxes, a horizontal double-headed arrow spans both, labeled 'National (significant)' above and 'mobile number' below. Below the 'CC' box and the 'National (significant) mobile number' group, another horizontal double-headed arrow spans the entire width, labeled 'Mobile station international' above and 'ISDN number' below. + +Diagram illustrating the Number Structure of MSISDN. It shows three components: CC (Country Code), NDC (National Destination Code), and SN (Subscriber Number). The NDC and SN are grouped together as the 'National (significant) mobile number'. The CC, NDC, and SN together form the 'Mobile station international ISDN number'. + +**Figure 2: Number Structure of MSISDN** + +The number consists of: + +- Country Code (CC) of the country in which the MS is registered, followed by: +- National (significant) mobile number, which consists of: + - National Destination Code (NDC) and + - Subscriber Number (SN). + +For GSM/UMTS applications, a National Destination Code is allocated to each PLMN. In some countries more than one NDC may be required for each PLMN. + +The composition of the MS international ISDN number should be such that it can be used as a global title address in the Signalling Connection Control Part (SCCP) for routing messages to the home location register of the MS. The country code (CC) and the national destination code (NDC) will provide such routing information. If further routing information is required, it should be contained in the first few digits of the subscriber number (SN). + +A sub-address may be appended to an ISDN number for use in call setup and in supplementary service operations where an ISDN number is required (see ITU-T Recommendations E.164, clause 11.2 and X.213 annex A). The sub-address is transferred to the terminal equipment denoted by the ISDN number. + +The maximum length of a sub-address is 20 octets, including one octet to identify the coding scheme for the sub-address (see ITU-T Recommendation X.213, annex A). All coding schemes described in ITU-T Recommendation X.213, annex A are supported in GSM and UMTS. + +As an exception to the rules above, the MSISDN shall take the dummy MSISDN value composed of 15 digits set to 0 (encoded as an E.164 international number) when the MSISDN is not available in messages in which the presence of the MSISDN parameter is required for backward compatibility reason. See the relevant stage 3 specifications. + +## 3.4 Mobile Station Roaming Number (MSRN) for PSTN/ISDN routing + +The Mobile Station Roaming Number (MSRN) is used to route calls directed to an MS. On request from the Gateway MSC via the HLR it is temporarily allocated to an MS by the VLR with which the MS is registered; it addresses the Visited MSC collocated with the assigning VLR. More than one MSRN may be assigned simultaneously to an MS. + +The MSRN is passed by the HLR to the Gateway MSC to route calls to the MS. + +The Mobile Station Roaming Number for PSTN/ISDN routing shall have the same structure as international ISDN numbers in the area in which the roaming number is allocated, i.e.: + +- the country code of the country in which the visitor location register is located; +- the national destination code of the visited PLMN or numbering area; +- a subscriber number with the appropriate structure for that numbering area. + +The MSRN shall not be used for subscriber dialling. It should be noted that the MSRN can be identical to the MSISDN (clause 3.3) in certain circumstances. In order to discriminate between subscriber generated access to these numbers and + +re-routeing performed by the network, re-routeing or redirection indicators or other signalling means should be used, if available. + +## 3.5 Structure of Mobile Station International Data Number + +The structure of MS international data numbers should comply with the data numbering plan of ITU-T Recommendation X.121 as applied in the home country of the mobile subscriber. Implications for numbering interworking functions which may need to be provided by the PLMN (if the use of X.121 numbers is required) are indicated in 3GPP TS 23.070 [4]. + +## 3.6 Handover Number + +The handover number is used for establishment of a circuit between MSCs to be used for a call being handed over. The structure of the handover number is the same as the structure of the MSRN. The handover number may be reused in the same way as the MSRN. + +## 3.7 Structure of an IP v4 address + +One or more IP address domains may be allocated to each PLMN. The IP v4 address structure is defined in RFC 791 [14]. + +An IP v4 address may be allocated to an MS either permanently or temporarily during a connection with the network. + +## 3.8 Structure of an IP v6 address + +One or more IP address domains could be allocated to each PLMN. The IP v6 address structure is defined in RFC 2373 [15]. + +An IP v6 address may be allocated to an MS either permanently or temporarily during a connection with the network + +If the dynamic IPv6 stateless address autoconfiguration procedure is used, then each PDP context, or group of PDP contexts sharing the same IP address, is assigned a unique prefix as defined in 3GPP TS 23.060 [3]. + +As described in RFC 2462 [21] and RFC 3041 [22], the MS can change its interface identifier without the GPRS network being aware of the change. + +# --- 4 Identification of location areas and base stations + +## 4.1 Composition of the Location Area Identification (LAI) + +The Location Area Identification shall be composed as shown in figure 3: + +![Diagram showing the structure of Location Area Identification (LAI) composed of MCC, MNC, and LAC.](bf10cf36bba7b1d1f5ba30447da6905f_img.jpg) + +The diagram illustrates the structure of the Location Area Identification (LAI). It consists of three adjacent rectangular boxes labeled 'MCC', 'MNC', and 'LAC' from left to right. Below these boxes, a horizontal double-headed arrow spans the entire width, with the text 'Location Area Identification' centered beneath it. + +Diagram showing the structure of Location Area Identification (LAI) composed of MCC, MNC, and LAC. + +**Figure 3: Structure of Location Area Identification** + +The LAI is composed of the following elements: + +- Mobile Country Code (MCC) identifies the country in which the GSM PLMN is located. The value of the MCC is the same as the three digit MCC contained in international mobile subscriber identity (IMSI); +- Mobile Network Code (MNC) is a code identifying the GSM PLMN in that country. The MNC takes the same value as the two or three digit MNC contained in IMSI; +- Location Area Code (LAC) is a fixed length code (of 2 octets) identifying a location area within a PLMN. This part of the location area identification can be coded using a full hexadecimal representation except for the following reserved hexadecimal values: + +0000, and + +FFFE. + +These reserved values are used in some special cases when no valid LAI exists in the MS (see 3GPP TS 24.008 [5], 3GPP TS 31.102 [27] and 3GPP TS 51.011 [9]). + +A specific GSM PLMN code (MCC + MNC) may be broadcast for mobile stations which are not compatible with SoLSA and which do not understand the exclusive access indicator (see 3GPP TS 23.073 [30]). The reserved value of the escape PLMN code is MCC = 901 and MNC = 08. + +## 4.2 Composition of the Routing Area Identification (RAI) + +The Routing Area Identification shall be composed as shown in figure 4: + +![Figure 4: Structure of Routing Area Identification. A diagram showing a box containing two sub-boxes labeled 'LAI' and 'RAC'. Below these boxes, a double-headed arrow labeled 'Routeing Area Identification' spans the width of both sub-boxes.](6f31cdb576d2f15c35c3f266e5f59211_img.jpg) + +The diagram shows a large rectangular box containing two smaller rectangular boxes side-by-side. The left box is labeled 'LAI' and the right box is labeled 'RAC'. Below these two boxes, a horizontal double-headed arrow spans the width of both, with the text 'Routeing Area Identification' centered below it. + +Figure 4: Structure of Routing Area Identification. A diagram showing a box containing two sub-boxes labeled 'LAI' and 'RAC'. Below these boxes, a double-headed arrow labeled 'Routeing Area Identification' spans the width of both sub-boxes. + +**Figure 4: Structure of Routing Area Identification** + +The RAI is composed of the following elements: + +- A valid Location Area Identity (LAI) as defined in clause 4.1. Invalid LAI values are used in some special cases when no valid RAI exists in the mobile station (see 3GPP TS 24.008 [5], 3GPP TS 31.102 [27] and 3GPP TS 51.011 [9]). +- Routeing Area Code (RAC) which is a fixed length code (of 1 octet) identifying a routeing area within a location area. + +## 4.3 Base station identification + +### 4.3.1 Cell Identity (CI) and Cell Global Identification (CGI) + +The BSS and cell within the BSS are identified within a location area or routeing area by adding a Cell Identity (CI) to the location area or routeing area identification, as shown in figure 5. The CI is of fixed length with 2 octets and it can be coded using a full hexadecimal representation. + +The Cell Global Identification is the concatenation of the Location Area Identification and the Cell Identity. Cell Identity shall be unique within a location area. + +![Figure 5: Structure of Cell Global Identification. A diagram showing a box containing four sub-boxes labeled 'MCC', 'MNC', 'LAC', and 'CI'. Below the first three sub-boxes, a double-headed arrow labeled 'Location Area Identification' spans their width. Below all four sub-boxes, a longer double-headed arrow labeled 'Cell Global Identification (CGI)' spans their width.](836008eb3303ade9e269f93c04dc0a2e_img.jpg) + +The diagram shows a large rectangular box containing four smaller rectangular boxes in a row, labeled 'MCC', 'MNC', 'LAC', and 'CI' from left to right. Below the first three boxes ('MCC', 'MNC', 'LAC'), a horizontal double-headed arrow spans their width, with the text 'Location Area Identification' centered above it. Below all four boxes, a longer horizontal double-headed arrow spans their entire width, with the text 'Cell Global Identification (CGI)' centered above it. + +Figure 5: Structure of Cell Global Identification. A diagram showing a box containing four sub-boxes labeled 'MCC', 'MNC', 'LAC', and 'CI'. Below the first three sub-boxes, a double-headed arrow labeled 'Location Area Identification' spans their width. Below all four sub-boxes, a longer double-headed arrow labeled 'Cell Global Identification (CGI)' spans their width. + +**Figure 5: Structure of Cell Global Identification** + +### 4.3.2 Base Station Identify Code (BSIC) + +The base station identity code is a local colour code that allows an MS to distinguish between different neighbouring base stations. BSIC is a 6 bit code which is structured as shown in Figure 6. + +![Figure 6: Structure of BSIC. The diagram shows two boxes, NCC and BCC, each with '3 bits' written below it. Below the NCC box is the text 'PLMN colour code' and below the BCC box is 'BS colour code'. Double-headed arrows point from the '3 bits' text to the boxes above them.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Figure 6: Structure of BSIC. The diagram shows two boxes, NCC and BCC, each with '3 bits' written below it. Below the NCC box is the text 'PLMN colour code' and below the BCC box is 'BS colour code'. Double-headed arrows point from the '3 bits' text to the boxes above them. + +**Figure 6: Structure of BSIC** + +In the definition of the NCC, care should be taken to ensure that the same NCC is not used in adjacent PLMNs which may use the same BCCH carrier frequencies in neighbouring areas. Therefore, to prevent potential deadlocks, a definition of the NCC appears in annex A. This annex will be reviewed in a co-ordinated manner when a PLMN is created. + +In addition to the above, the GERAN networks should be configured so that: + +- in a cell shared between different PLMNs as per GERAN network sharing (see 3GPP TS 44.018 [99] and 3GPP TS 44.060 [100]), the NCC used in this cell is different from the NCC used in the neighbouring non-shared cells of these PLMNs; and that +- these PLMNs use different NCCs in non-shared cells neighbouring this shared cell. + +## 4.4 Regional Subscription Zone Identity (RSZI) + +A PLMN-specific regional subscription defines unambiguously for the entire PLMN the regions in which roaming is allowed. It consists of one or more regional subscription zones. The regional subscription zone is identified by a Regional Subscription Zone Identity (RSZI). A regional subscription zone identity is composed as shown in figure 7. + +![Figure 7: Structure of Regional Subscription Zone Identity (RSZI). The diagram shows a large box labeled 'RSZI' at the top. Below it, the box is divided into two main parts: the left part contains 'CC' and 'NDC', and the right part contains 'ZC'. Below the 'ZC' part is the text 'Zone Code, Two octets'. Double-headed arrows indicate the scope of the RSZI, CC, NDC, and ZC labels.](d3b5eac55166fc428a223bba5c46961b_img.jpg) + +Figure 7: Structure of Regional Subscription Zone Identity (RSZI). The diagram shows a large box labeled 'RSZI' at the top. Below it, the box is divided into two main parts: the left part contains 'CC' and 'NDC', and the right part contains 'ZC'. Below the 'ZC' part is the text 'Zone Code, Two octets'. Double-headed arrows indicate the scope of the RSZI, CC, NDC, and ZC labels. + +**Figure 7: Structure of Regional Subscription Zone Identity (RSZI)** + +The elements of the regional subscription zone identity are: + +- 1) the Country Code (CC) which identifies the country in which the PLMN is located; +- 2) the National Destination Code (NDC) which identifies the PLMN in that country; +- 3) the Zone Code (ZC) which identifies a regional subscription zone as a pattern of allowed and not allowed location areas uniquely within that PLMN. + +CC and NDC are those of an ITU-T E.164 VLR or SGSN number (see clause 5.1) of the PLMN; they are coded with a trailing filler, if required. ZC has fixed length of two octets and is coded in full hexadecimal representation. + +RSZIs, including the zone codes, are assigned by the VPLMN operator. The zone code is evaluated in the VLR or SGSN by information stored in the VLR or SGSN as a result of administrative action. If a zone code is received by a VLR or SGSN during updating by the HLR and this zone code is related to that VLR or SGSN, the VLR or SGSN shall be able to decide for all its MSC or SGSN areas and all its location areas whether they are allowed or not allowed. + +For details of assignment of RSZI and of ZC as subscriber data see 3GPP TS 23.008 [2]. + +For selection of RSZI at location updating by comparison with the leading digits of the VLR or SGSN number and for transfer of ZC from the HLR to VLR and SGSN see 3GPP TS 29.002 [31]. + +## 4.5 Location Number + +A location number is a number which defines a specific location within a PLMN. The location number is formatted according to ITU-T Recommendation E.164, as shown in figure 8. The Country Code (CC) and National Destination Code (NDC) fields of the location number are those which define the PLMN of which the location is part. + +![Figure 8: Location Number Structure diagram showing three boxes labeled CC, NDC, and LSP inside a larger rectangular frame.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +The diagram illustrates the structure of a location number. It consists of a large rectangular box containing three smaller, separate boxes arranged horizontally. These boxes are labeled 'CC' (Country Code), 'NDC' (National Destination Code), and 'LSP' (Locally Significant Part) from left to right. + +Figure 8: Location Number Structure diagram showing three boxes labeled CC, NDC, and LSP inside a larger rectangular frame. + +**Figure 8: Location Number Structure** + +The structure of the locally significant part (LSP) of the location number is a matter for agreement between the PLMN operator and the national numbering authority in the PLMN's country. It is desirable that the location number can be interpreted without the need for detailed knowledge of the internal structure of the PLMN; the LSP should therefore include the national destination code in the national numbering plan for the fixed network which defines the geographic area in which the location lies. + +The set of location numbers for a PLMN shall be chosen so that a location number can be distinguished from the MSISDN of a subscriber of the PLMN. This will allow the PLMN to trap attempts by users to dial a location number. + +## 4.6 Composition of the Service Area Identification (SAI) + +Void (see subclause 12.5). + +## 4.7 Closed Subscriber Group + +A Closed Subscriber Group consists of a single cell or a collection of cells within an E-UTRAN and UTRAN that are open to only a certain group of subscribers. + +Within a PLMN, a Closed Subscriber Group is identified by a Closed Subscriber Group Identity (CSG-ID). The CSG-ID shall be fix length 27 bit value. + +## 4.8 HNB Name + +HNB Name shall be a broadcast string in free text format that provides a human readable name for the Home NodeB or Home eNodeB CSG identity. + +HNB Name shall be coded in UTF-8 format with variable number of bytes per character. The maximum length of HNB Name shall be 48 bytes. + +See 3GPP TS 22.011 [83] for details. + +## 4.9 CSG Type + +CSG Type shall provide the type of a CSG identity in a human readable form. It shall reside in the UE only. See 3GPP TS 22.011 [83] for details. + +When the CSG Type has a text component, the CSG Type shall be coded in UTF-8 format with variable number of bytes per character . The maximum text length shall not exceed 12 characters in any language. + +## 4.10 HNB Unique Identity + +HNB Unique Identity uniquely identifies a Home NodeB or Home eNodeB. + +The HNB unique identity shall be defined as either a 48-bit or 64-bit extended unique identifier (EUI-48 or EUI-64) as defined in [45] (EUI-48) and [46] (EUI-64). + +For use in HNB certificates, the HNB Unique Identity shall be transformed into a FQDN in the form: + +- . + + is the first label which shall be the EUI-48 or EUI-64, represented as a string of 12 or 16 hexadecimal digits including any leading zeros. denotes the realm which may consist of 3 labels , e.g. hnb.femtocellvendor.com. + +# 5 Identification of MSCs, GSNs, location registers and CSSs + +## 5.1 Identification for routeing purposes + +MSCs, GSNs, location registers and CSSs are identified by international PSTN/ISDN numbers and/or Signalling Point Codes ("entity number", i.e., "HLR number", "VLR number", "MSC number", "SGSN number", "GGSN number" and "CSS number") in each PLMN. + +MMEs that support "SMS in MME" are identified by international PSTN/ISDN numbers for SM Routing via an IWF (i.e. "MME number for MT SMS"). + +Additionally SGSNs and GGSNs are identified by GSN Addresses. These are the SGSN Address and the GGSN Address. + +A GSN Address shall be composed as shown in figure 9. + +![Figure 9: Structure of GSN Address. The diagram shows a horizontal bar representing the GSN Address, divided into three fields: Address Type (2 bits), Address Length (6 bits), and Address (4 to 16 octets).](f1fbb1287d999c7034742de35bdab836_img.jpg) + +The diagram illustrates the structure of a GSN Address. It is a horizontal bar divided into three main components: **Address Type**, **Address Length**, and **Address**. Above the bar, a double-headed arrow labeled "GSN Address" spans the entire length. Below the bar, each component is shown in a box with its corresponding bit or octet length indicated by a double-headed arrow underneath: "Address Type" is 2 bits, "Address Length" is 6 bits, and "Address" is 4 to 16 octets. + +Figure 9: Structure of GSN Address. The diagram shows a horizontal bar representing the GSN Address, divided into three fields: Address Type (2 bits), Address Length (6 bits), and Address (4 to 16 octets). + +**Figure 9: Structure of GSN Address** + +The GSN Address is composed of the following elements: + +- 1) The Address Type, which is a fixed length code (of 2 bits) identifying the type of address that is used in the Address field. +- 2) The Address Length, which is a fixed length code (of 6 bits) identifying the length of the Address field. +- 3) The Address, which is a variable length field which contains either an IPv4 address or an IPv6 address. + +Address Type 0 and Address Length 4 are used when Address is an IPv4 address. + +Address Type 1 and Address Length 16 are used when Address is an IPv6 address. + +The IP v4 address structure is defined in RFC 791 [14]. + +The IP v6 address structure is defined in RFC 2373 [15]. + +## 5.2 Identification of HLR for HLR restoration application + +HLR may also be identified by one or several "HLR id(s)", consisting of the leading digits of the IMSI (MCC + MNC + leading digits of MSIN). + +# 6 International Mobile Station Equipment Identity and Software Version Number + +## 6.1 General + +The structure and allocation principles of the International Mobile station Equipment Identity and Software Version number (IMEISV) and the International Mobile station Equipment Identity (IMEI) are defined below. + +The Mobile Station Equipment is uniquely defined by the IMEI or the IMEISV. + +## 6.2 Composition of IMEI and IMEISV + +### 6.2.1 Composition of IMEI + +The International Mobile station Equipment Identity (IMEI) is composed as shown in figure 10. + +![Diagram showing the structure of IMEI, composed of TAC (8 digits), SNR (6 digits), and CD/SD (1 digit), totaling 15 digits.](db5ab5d386827a5d5f5fad0f45612b90_img.jpg) + +The diagram illustrates the structure of the IMEI (International Mobile Equipment Identity). It is a 15-digit number composed of three parts: TAC (Type Allocation Code) which is 8 digits long, SNR (Serial Number) which is 6 digits long, and CD/SD (Check Digit / Spare Digit) which is 1 digit long. The parts are shown in a horizontal sequence: TAC, SNR, and CD/SD. Above each part is a double-headed arrow indicating its length: 8 digits for TAC, 6 digits for SNR, and 1 digit for CD/SD. Below the entire sequence is a single long double-headed arrow labeled 'IMEI 15 digits'. + +Diagram showing the structure of IMEI, composed of TAC (8 digits), SNR (6 digits), and CD/SD (1 digit), totaling 15 digits. + +**Figure 10: Structure of IMEI** + +The IMEI is composed of the following elements (each element shall consist of decimal digits only): + +- Type Allocation Code (TAC). Its length is 8 digits; +- Serial Number (SNR) is an individual serial number uniquely identifying each equipment within the TAC. Its length is 6 digits; +- Check Digit (CD) / Spare Digit (SD): If this is the Check Digit see paragraph below; if this digit is Spare Digit it shall be set to zero, when transmitted by the MS. + +The IMEI (14 digits) is complemented by a Check Digit (CD). The Check Digit is not part of the digits transmitted when the IMEI is checked, as described below. The Check Digit is intended to avoid manual transmission errors, e.g. when customers register stolen MEs at the operator's customer care desk. The Check Digit is defined according to the Luhn formula, as defined in annex B. + +NOTE: The Check Digit is not applied to the Software Version Number. + +The security requirements of the IMEI are defined in 3GPP TS 22.016 [32]. + +### 6.2.2 Composition of IMEISV + +The International Mobile station Equipment Identity and Software Version Number (IMEISV) is composed as shown in figure 11. + +![Figure 11: Structure of IMEISV. The diagram shows a horizontal bar representing the 16-digit IMEISV, divided into three segments: TAC (8 digits), SNR (6 digits), and SVN (2 digits). Arrows above each segment indicate their respective lengths. A long arrow below the entire bar is labeled 'IMEISV 16 digits'.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +Figure 11: Structure of IMEISV. The diagram shows a horizontal bar representing the 16-digit IMEISV, divided into three segments: TAC (8 digits), SNR (6 digits), and SVN (2 digits). Arrows above each segment indicate their respective lengths. A long arrow below the entire bar is labeled 'IMEISV 16 digits'. + +**Figure 11: Structure of IMEISV** + +The IMEISV is composed of the following elements (each element shall consist of decimal digits only): + +- Type Allocation Code (TAC). Its length is 8 digits; +- Serial Number (SNR) is an individual serial number uniquely identifying each equipment within each TAC. Its length is 6 digits; +- Software Version Number (SVN) identifies the software version number of the mobile equipment. Its length is 2 digits. + +Regarding updates of the IMEISV: The security requirements of 3GPP TS 22.016 [32] apply only to the TAC and SNR, but not to the SVN part of the IMEISV. + +## 6.3 Allocation principles + +The Type Allocation Code (TAC) is issued by a central body. + +Manufacturers shall allocate individual serial numbers (SNR) in a sequential order. + +For a given ME, the combination of TAC and SNR used in the IMEI shall duplicate the combination of TAC and SNR used in the IMEISV. + +The Software Version Number is allocated by the manufacturer. SVN value 99 is reserved for future use. + +# 7 Identification of Voice Group Call and Voice Broadcast Call Entities + +## 7.1 Group Identities + +Logical groups of subscribers to the Voice Group Call Service or to the Voice Broadcast Service are identified by a Group Identity (Group ID). Group IDs for VGCS are unique within a PLMN. Likewise, Group IDs for VBS are unique within a PLMN. However, no uniqueness is required between the sets of Group IDs. These sets may be intersecting or even identical, at the option of the network operator. + +The Group ID is a number with a maximum value depending on the composition of the voice group call reference or voice broadcast call reference defined in section 7.3. + +For definition of Group ID on the radio interface, A interface and Abis interface, see 3GPP TS 44.068 [46] and 3GPP TS 44.069 [47]. + +For definition of Group ID coding on MAP protocol interfaces, see 3GPP TS 29.002 [31]. + +VGCS or VBS shall also be provided for roaming. If this applies, certain Group IDs shall be defined as supra-PLMN Group IDs which have to be co-ordinated between the network operators and which shall be known in the networks and in the SIM. + +The format of the Group ID is identical for VBS and VGCS. + +## 7.2 Group Call Area Identification + +Grouping of cells into specific group call areas occurs in support of both the Voice Group Call Service and the Voice Broadcast Service. These service areas are known by a "Group Call Area Identity" (Group Call Area Id). No restrictions are placed on what cells may be grouped into a given group call area. + +The Group Call Area ID is a number uniquely assigned to a group call area in one network and with a maximum value depending on the composition of the voice group call reference or voice broadcast reference defined under 7.3. + +The formats of the Group Call Area ID for VGCS and the Group Call Area ID for VBS are identical. + +## 7.3 Voice Group Call and Voice Broadcast Call References + +Specific instances of voice group calls (VGCS) and voice broadcast calls (VBS) within a given group call area are known by a "Voice Group Call Reference" or by a "Voice Broadcast Call Reference" respectively. + +Each voice group call or voice broadcast call in one network is uniquely identified by its Voice Group Call Reference or Voice Broadcast Call Reference. The Voice Group Call Reference or Voice Broadcast Call Reference is composed of the Group ID and the Group Call Area ID. The composition of the group call area ID and the group ID can be specific for each network operator. + +For definition of Group Call Reference (with leading zeros inserted as necessary) on the radio interface, A interface and Abis interface, see 3GPP TS 24.008 [5], 3GPP TS 44.068 [46] and 3GPP TS 44.069 [47]. + +For definition of Group Call Reference (also known as ASCII Call Reference, Voice Group Call Reference or Voice Broadcast Call Reference) coding on MAP protocol interfaces, see 3GPP TS 29.002 [31]. + +The format is given in figure 12. + +![Diagram illustrating the format of Voice Group Call Reference / Voice Broadcast Call Reference. It shows two boxes: 'Group Call Area ID' and 'Group ID'. Below these boxes, a double-headed arrow spans the width, labeled 'Voice Group Call Reference / Voice Broadcast Call Reference'.](745261f385368efa3f2259c8681874e9_img.jpg) + +The diagram shows a rectangular box containing two smaller boxes at the top. The left box is labeled "Group Call Area ID" and the right box is labeled "Group ID". Below these boxes, centered, is a double-headed horizontal arrow. Above the arrow, the text "Voice Group Call Reference / Voice Broadcast Call Reference" is written. The entire diagram is enclosed in a larger rectangular border. + +Diagram illustrating the format of Voice Group Call Reference / Voice Broadcast Call Reference. It shows two boxes: 'Group Call Area ID' and 'Group ID'. Below these boxes, a double-headed arrow spans the width, labeled 'Voice Group Call Reference / Voice Broadcast Call Reference'. + +**Figure 12: Voice Group Call Reference / Voice Broadcast Call Reference** + +# 8 SCCP subsystem numbers + +Subsystem numbers are used to identify applications within network entities which use SCCP signalling. In GSM and UMTS, subsystem numbers may be used between PLMNs, in which case they are taken from the globally standardized range (1 - 31) or the part of the national network range (129 - 150) reserved for GSM/UMTS use between PLMNs. For use within a PLMN, they are taken from the part of the national network range (32 - 128 & 151 - 254) not reserved for GSM/UMTS use between PLMNs. + +## 8.1 Globally standardized subsystem numbers used for GSM/UMTS + +The following globally standardised subsystem numbers have been allocated for use by GSM/UMTS: + +0000 0110HLR (MAP); + +0000 0111VLR (MAP); + +0000 1000MSC (MAP); + +0000 1001EIR (MAP); + +0000 1010 is allocated for evolution (possible Authentication Centre). + +## 8.2 National network subsystem numbers used for GSM/UMTS + +The following national network subsystem numbers have been allocated for use within GSM/UMTS networks: + +1111 1000CSS (MAP); + +1111 1001PCAP; + +1111 1010BSC (BSSAP-LE); + +1111 1011MSC (BSSAP-LE); + +1111 1100SMLC (BSSAP-LE); + +1111 1101BSS O&M (A interface); + +1111 1110BSSAP (A interface). + +The following national network subsystem numbers have been allocated for use within and between GSM/UMTS networks: + +1000 1110RANAP; + +1000 1111RNSAP; + +1001 0001GMLC (MAP); + +1001 0010CAP; + +1001 0011gsmSCF (MAP) or IM-SSF (MAP) or Presence Network Agent; + +1001 0100SIWF (MAP); + +1001 0101SGSN (MAP); + +1001 0110GGSN (MAP). + +# --- 9 Definition of Access Point Name + +In the GPRS backbone, an Access Point Name (APN) is a reference to a GGSN. To support inter-PLMN roaming, the internal GPRS DNS functionality is used to translate the APN into the IP address of the GGSN. + +## 9.0 General + +Access Point Name as used in the Domain Name System (DNS) Procedures defined in 3GPP TS 29.303 [73] is specified in subclause 19.4.2.2. + +## 9.1 Structure of APN + +The APN is composed of two parts as follows: + +- The APN Network Identifier; this defines to which external network the GGSN/PGW is connected and optionally a requested service by the MS. This part of the APN is mandatory. +- The APN Operator Identifier; this defines in which PLMN GPRS/EPS backbone the GGSN/PGW is located. This part of the APN is optional. + +NOTE 1: The APN Operator Identifier is mandatory on certain interfaces, see the relevant stage 3 specifications. + +The APN Operator Identifier is placed after the APN Network Identifier. An APN consisting of both the Network Identifier and Operator Identifier corresponds to a DNS name of a GGSN/PGW; the APN has, after encoding as defined in the paragraph below, a maximum length of 100 octets. + +The encoding of the APN shall follow the Name Syntax defined in RFC 2181 [18], RFC 1035 [19] and RFC 1123 [20]. The APN consists of one or more labels. Each label is coded as a one octet length field followed by that number of octets coded as 8 bit ASCII characters. Following RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. The APN is not terminated by a length byte of zero. + +NOTE 2: A length byte of zero is added by the SGSN/MME at the end of the APN before interrogating a DNS server. + +For the purpose of presentation, an APN is usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). + +### 9.1.1 Format of APN Network Identifier + +The APN Network Identifier shall contain at least one label and shall have, after encoding as defined in subclause 9.1 above, a maximum length of 63 octets. An APN Network Identifier shall not start with any of the strings "rac", "lac", "sgsn" or "rnc", and it shall not end in ".gprs", i.e. the last label of the APN Network Identifier shall not be "gprs". Further, it shall not take the value "\*". + +In order to guarantee uniqueness of APN Network Identifiers within or between GPRS/EPS PLMN, an APN Network Identifier containing more than one label shall correspond to an Internet domain name. This name should only be allocated by the PLMN if that PLMN belongs to an organisation which has officially reserved this name in the Internet domain. Other types of APN Network Identifiers are not guaranteed to be unique within or between GPRS/EPS PLMNs. + +An APN Network Identifier may be used to access a service associated with a GGSN/PGW. This may be achieved by defining: + +- an APN which corresponds to a FQDN of a GGSN/PGW, and which is locally interpreted by the GGSN/PGW as a request for a specific service, or +- an APN Network Identifier consisting of 3 or more labels and starting with a Reserved Service Label, or an APN Network Identifier consisting of a Reserved Service Label alone, which indicates a GGSN/PGW by the nature of the requested service. Reserved Service Labels and the corresponding services they stand for shall be agreed between operators who have GPRS/EPS roaming agreements. + +### 9.1.2 Format of APN Operator Identifier + +The APN Operator Identifier is composed of three labels. The last label (or domain) shall be "gprs". The first and second labels together shall uniquely identify the GPRS/EPS PLMN. + +For each operator, there is a default APN Operator Identifier (i.e. domain name). This default APN Operator Identifier is derived from the IMSI as follows: + +"mnc.mcc.gprs" + +where: + +"mnc" and "mcc" serve as invariable identifiers for the following digits. + + and are derived from the components of the IMSI defined in subclause 2.2. + +This default APN Operator Identifier is used for home routed inter-PLMN roaming situations when attempting to translate an APN consisting only of a Network Identifier into the IP address of the GGSN/PGW in the HPLMN. The PLMN may provide DNS translations for other, more human-readable, APN Operator Identifiers in addition to the default Operator Identifier described above. + +Alternatively, in the roaming case if the GGSN/PGW from the VPLMN is to be selected, the APN Operator Identifier for the UE is constructed from the serving network PLMN ID. In this case, the APN-OI replacement field, if received, shall be ignored. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "mnc.mcc.gprs" format of the APN OI shall be: + +- = 3 digits +- = 3 digits +- If there are only 2 significant digits in the MNC, one "0" digit is inserted at the left side to fill the 3 digits coding of MNC in the APN OI. + +As an example, the APN OI for MCC 345 and MNC 12 will be coded in the DNS as "mnc012.mcc345.gprs". + +The APN-OI replacement is only used for selecting the GGSN/PGW from the HPLMN. The format of the domain name used in the APN-OI replacement field (as defined in 3GPP TS 23.060 [3] and 3GPP TS 23.401 [72]) is the same as the default APN-OI as defined above except that it may be preceded by one or more labels each separated by a dot. + +EXAMPLE 1: province1.mnc012.mcc345.gprs + +EXAMPLE 2: ggsn-cluster-A.provinceB.mnc012.mcc345.gprs + +The APN constructed using the APN-OI replacement field is only used for DNS translation. The APN when being sent to other network entities over GTP interfaces shall follow the rules as specified in 3GPP TS 23.060 [3] and 3GPP TS 23.401 [72]. + +## 9.2 Definition of the Wild Card APN + +The APN field in the HLR may contain a wild card APN if the HPLMN operator allows the subscriber to access any network of a given PDP Type. If an SGSN has received such a wild card APN, it may either choose the APN Network Identifier received from the Mobile Station or a default APN Network Identifier for addressing the GGSN when activating a PDP context. + +### 9.2.1 Coding of the Wild Card APN + +The wild card APN is coded as an APN with "\*" as its single label, (i.e. a length octet with value one, followed by the ASCII code for the asterisk). + +## 9.3 Definition of Emergency APN + +The Emergency APN (Em-APN) is an APN used to derive a PDN GW selected for IMS Emergency call support. The exact encoding of the Em-APN is the responsibility of each PLMN operator as it is only valid within a given PLMN. + +# --- 10 Identification of the Cordless Telephony System entities + +## 10.1 General description of CTS-MS and CTS-FP Identities + +Every CTS-FP broadcasts a local identity - the Fixed Part Beacon Identity (FPBI) - which contains an Access Rights Identity. Every CTS-MS has both an Access Rights Key and a CTS Mobile Subscriber Identity (CTSMSI). These operate as a pair. A CTS-MS is allowed to access any CTS-FP which broadcasts an FPBI which can be identified by any of the CTS-MS Access Rights Keys of that CTS-MS. The CTS-MS Access Rights Key contains the FPBI and the FPBI Length Indicator (FLI) indicating the relevant part of the FPBI used to control access. + +## 10.2 CTS Mobile Subscriber Identities + +### 10.2.1 General + +Each CTS-MS has one or more temporary identities which are used for paging and to request access. The structure and allocation principles of the CTS Mobile Subscriber Identities (CTSMSI) are defined below. + +#### Composition of the CTSMSI + +![](3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg) + +``` + + bit No 22 1 + +------------------------------------------+ + | | | | | | | | | | | | | | | | + +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ + Type|<-----------Significant Part---------->| + + <-------------- CTSMSI 22 bits -------------> + +``` + +**Figure 13: Structure of CTSMSI** + +The CTSMSI is composed of the following elements: + +- CTSMSI Type. Its length is 2 bits; +- Significant Part. Its length is 20 bits. + +The following CTSMSI Type values have been allocated for use by CTS: + +- 00 Default Individual CTSMSI; +- 01 Reserved; +- 10 Assigned Individual CTSMSI; +- 11 Assigned Connectionless Group CTSMSI. + +### 10.2.3 Allocation principles + +The default Individual CTSMSI contains the least significant portion of the IMSI. This is the default CTS-MS identity. + +Assigned CTSMSIs are allocated by the CTS-FP during enrolment, registration and other access procedures. Significant Part of the assigned CTSMSI shall be allocated in the range 00001-FFFFE. CTS-FP shall not allocate Significant Part equal to 00000 or to FFFFF and shall not allocate Assigned CTSMSI using Reserved Type value. Such assignments shall be ignored by the CTS-MS. + +Assigned CTSMSIs are allocated in ciphered mode. + +NOTE: The assigned individual CTSMSI should be updated whenever it is sent in clear text on the CTS radio interface during RR connection establishment. + +The value FFFFF from the set of Assigned Connectionless Group CTSMSI shall be considered in all CTS-MS as the value of the Connectionless Broadcast Identifier. + +### 10.2.4 CTSMSI hexadecimal representation + +The 22 bits of CTSMSI are padded with 2 leading zeroes to give a 6 digit hexadecimal value. + +EXAMPLE: binary CTSMSI value: 11 1001 0010 0000 1011 1100 +hexadecimal CTSMSI value: 39 20 BC. + +## 10.3 Fixed Part Beacon Identity + +### 10.3.1 General + +Each CTS-FP has one Fixed Part Beacon Identity known by the enrolled CTS-MSs. The FPBI is periodically broadcast on the BCH logical channel so that the CTS-MSs are able to recognise the identity of the CTS-FP. The FPBI contains an Access Rights Identity. + +Enrolled CTS-MSs shall store the FPBI to which their assigned CTSMSIs are related. + +Below the structure and allocation principles of the Fixed Part Beacon Identity (FPBI) are defined. + +### 10.3.2 Composition of the FPBI + +#### 10.3.2.1 FPBI general structure + +![](a4b963a07cc368283154762c4b156fe7_img.jpg) + +``` + +bit No 19 1 ++---------------------------------------------+ +| | | | | | | | | | | | | | | | | | | | | | | | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +Type| Significant Part | + + FPBI 19 bits +<---------------------------------------------> + +``` + +**Figure 14: General structure of FPBI** + +The FPBI is composed of the following elements: + +- FPBI Type. Its length is 2 bits; +- FPBI Significant Part. Its length is 17 bits. + +NOTE: The three LSBs bits of the FPBI form the 3-bit training sequence code (TSC). See 3GPP TS 45.056 [35]. + +The following FPBI Type values have been allocated for use by CTS: + +00 FPBI class A: residential and single-cell systems; + +01 FPBI class B: multi-cell PABXs. + +All other values are reserved and CTS-MSs shall treat these values as FPBI class A. + +#### 10.3.2.2 FPBI class A + +This class is intended to be used for small residential and private (PBX) single cell CTS-FP. + +![](6f90e8489d3449ddab9b5773db240a16_img.jpg) + +``` + +bit No 19 1 ++---------------------------------------------+ +| 0 0 | | | | | | | | | | | | | | | | | | | | | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +Type| FPN | + + FPBI 19 bits +<---------------------------------------------> + +``` + +**Figure 15: Structure of FPBI class A** + +The FPBI class A is composed of the following elements: + +- FPBI Class A Type. Its length is 2 bits and its value is 00; +- Fixed Part Number (FPN). Its length is 17 bits. The FPN contains the least significant bits of the Serial Number part of the IFPEI. + +The FPBI Length Indicator shall be set to 19 for a class A FPBI. + +#### 10.3.2.3 FPBI class B + +This class is reserved for more complex private installation such as multi-cell PABXs. + +![](8acc73a21038cd3ddc4c0ec148807f9d_img.jpg) + +``` + +bit No 19 1 ++---------------------------------------------+ +| 0 1 | | | | | | | | | | | | | | | | | | | | | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +Type| CNN + FPN + RPN | + + FPBI 19 bits +<---------------------------------------------> + +``` + +**Figure 16: Structure of FPBI class B** + +The FPBI class B is composed of the following elements: + +- FPBI Class B Type. Its length is 2 bits and its value is 01; +- CTS Network Number (CNN). Its length is defined by the manufacturer or the system installer; +- Fixed Part Number (FPN). Its length is defined by the manufacturer or the system installer; +- Radio Part Number (RPN) assigned by the CTS manufacturer or system installer. Its length is defined by the manufacturer or the system installer. + +NOTE: RPN is used to separate a maximum of $2^{\text{RPN length}}$ different cells from each other. This defines a cluster of cells supporting intercell handover. RPN length is submitted to a CTS-MS as a result of a successful attachment. + +The FPBI Length Indicator shall be set to $(2 + \text{CNN Length})$ for a class B FPBI. + +### 10.3.3 Allocation principles + +The FPBI shall be allocated during the CTS-FP initialisation procedure. Any change to the value of the FPBI of a given CTS-FP shall be considered as a CTS-FP re-initialisation; i.e. each enrolled CTS-MS needs to be enrolled again. + +FPBI are not required to be unique (i.e. several CTS-FP can have the same FPBI in different areas). Care should be taken to limit CTS-MS registration attempts to a fixed part with the same FPBI as another fixed part. + +## 10.4 International Fixed Part Equipment Identity + +### 10.4.1 General + +The structure and allocation principles of the International Fixed Part Equipment Identity (IFPEI) are defined below. + +### 10.4.2 Composition of the IFPEI + +![Diagram showing the structure of the IFPEI (International Fixed Part Equipment Identity). It is a 16-digit number composed of four parts: TAC (6 digits), FAC (2 digits), SNR (6 digits), and SVN (2 digits).](10d81b2cc455e3563e3e562a7f451124_img.jpg) + +``` + + 6 digits 2d 6 digits 2d + <----------><----><----------><----> + +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ + | | | | | | | | | | | | | | | | | + +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ + TAC FAC SNR SVN + + IFPEI 16 digits + <------------------------------------------> + +``` + +Diagram showing the structure of the IFPEI (International Fixed Part Equipment Identity). It is a 16-digit number composed of four parts: TAC (6 digits), FAC (2 digits), SNR (6 digits), and SVN (2 digits). + +Figure 17: Structure of IFPEI + +The IFPEI is composed of the following elements (each element shall consist of decimal digits only): + +- Type Approval Code (TAC). Its length is 6 decimal digits; +- Final Assembly Code (FAC). Its length is 2 decimal digits; +- Serial Number (SNR). Its length is 6 decimal digits; +- Software Version Number (SVN) identifies the software version number of the fixed part equipment. Its length is 2 digits. + +Regarding updates of the IFPEI: the TAC, FAC and SNR shall be physically protected against unauthorised change (see 3GPP TS 42.009 [36]); i.e. only the SVN part of the IFPEI can be modified. + +### 10.4.3 Allocation principles + +The Type Approval Code (TAC) is issued by a central body. + +The place of final assembly (FAC) is encoded by the manufacturer. + +Manufacturers shall allocate unique serial numbers (SNR) in a sequential order. + +The Software Version Number (SVN) is allocated by the manufacturer after authorisation by the type approval authority. SVN value 99 is reserved for future use. + +## 10.5 International Fixed Part Subscription Identity + +### 10.5.1 General + +The structure and allocation principles of the International Fixed Part Subscription Identity (IFPSI) are defined below. + +### 10.5.2 Composition of the IFPSI + +![Diagram showing the structure of IFPSI. It is divided into three parts: MCC (3 digits), CON (3 digits), and FPIN (up to 15 digits). The MCC and CON parts are grouped together as NFPSI. The entire sequence (MCC + CON + FPIN) is labeled as IFPSI.](409498e57b1f988b2b604d12cd997002_img.jpg) + +``` + + No more than 15 digits + <-----> + 3d 3d + <-----><-----><-----//-----> + +-----+-----+-----//-----+ + | | | | | | | | | | | | | | | | + +-----+-----+-----//-----+ + MCC CON FPIN + + NFPSI + <-----> + + IFPSI + <-----> + +``` + +Diagram showing the structure of IFPSI. It is divided into three parts: MCC (3 digits), CON (3 digits), and FPIN (up to 15 digits). The MCC and CON parts are grouped together as NFPSI. The entire sequence (MCC + CON + FPIN) is labeled as IFPSI. + +**Figure 18: Structure of IFPSI** + +The IFPSI is composed of the following elements (each element shall consist of decimal digits only): + +- Mobile Country Code (MCC) consisting of three digits. The MCC identifies the country of the CTS-FP subscriber (e.g. 208 for France); +- CTS Operator Number (CON). Its length is three digits; +- Fixed Part Identification Number (FPIN) identifying the CTS-FP subscriber. + +The National Fixed Part Subscriber Identity (NFPSI) consists of the CTS Operator Number and the Fixed Part Identification Number. + +### 10.5.3 Allocation principles + +IFPSI shall consist of decimal characters (0 to 9) only. + +The allocation of Mobile Country Codes (MCCs) is administered by the ITU-T. + +The allocation of CTS Operator Number (CON) and the structure of National Fixed Part Subscriber Identity (NFPSI) are the responsibility of each National Regulation Authority. + +CTS Operators shall allocate unique Fixed Part Identification Numbers. + +# 11 Identification of Localised Service Area + +Cells may be grouped into specific localised service areas. Each localised service area is identified by a localised service area identity (LSA ID). No restrictions are placed on what cells may be grouped into a given localised service area. + +The LSA ID can either be a PLMN significant number or a universal identity. This shall be known both in the networks and in the SIM. + +The LSA ID consists of 24 bits, numbered from 0 to 23, with bit 0 being the LSB. Bit 0 indicates whether the LSA is a PLMN significant number or a universal LSA. If the bit is set to 0 the LSA is a PLMN significant number; if it is set to 1 it is a universal LSA. + +The LSA ID shall be composed as shown in figure 19: + +![Figure 19: Structure of LSA ID. The diagram shows a rectangular box representing the LSA ID. Inside, there are two parts: MSB (Most Significant Bit) on the left, labeled '23 bits', and LSB (Least Significant Bit) on the right, labeled '1 bit'. Below the box, a double-headed arrow labeled 'LSA ID' spans the entire width.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +Figure 19: Structure of LSA ID. The diagram shows a rectangular box representing the LSA ID. Inside, there are two parts: MSB (Most Significant Bit) on the left, labeled '23 bits', and LSB (Least Significant Bit) on the right, labeled '1 bit'. Below the box, a double-headed arrow labeled 'LSA ID' spans the entire width. + +Figure 19: Structure of LSA ID + +# 12 Identification of PLMN, RNC, Service Area, CN domain and Shared Network Area + +The following clauses describe identifiers which are used by both the CN and the UTRAN across the Iu interface. For identifiers which are solely used within the UTRAN, see 3GPP TS 25.401 [16]. + +NOTE: in the following subclauses, the double vertical bar notation || indicates the concatenation operator. + +## 12.1 PLMN Identifier + +A Public Land Mobile Network is uniquely identified by its PLMN identifier. PLMN-Id consists of Mobile Country Code (MCC) and Mobile Network Code (MNC). + +- **PLMN-Id = MCC || MNC** + +The MCC and MNC are predefined within a UTRAN, and set in the RNC via O&M. + +## 12.2 CN Domain Identifier + +A CN Domain Edge Node is identified within the UTRAN by its CN Domain Identifier. The CN Domain identifier is used over UTRAN interfaces to identify a particular CN Domain Edge Node for relocation purposes. The CN Domain identifier for Circuit Switching (CS) consists of the PLMN-Id and the LAC, whereas for Packet Switching (PS) it consists of the PLMN-Id, the LAC, and the RAC of the first accessed cell in the target RNS. + +The two following CN Domain Identifiers are defined: + +- **CN CS Domain-Id = PLMN-Id || LAC** +- **CN PS Domain-Id = PLMN-Id || LAC || RAC** + +The LAC and RAC are defined by the operator, and set in the RNC via O&M. + +For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413 [17]. + +## 12.3 CN Identifier + +A CN node is uniquely identified within a PLMN by its CN Identifier (CN-Id). The CN-Id together with the PLMN identifier globally identifies the CN node. The CN-Id together with the PLMN-Id is used as the CN node identifier in RANAP signalling over the Iu interface. + +**Global CN-Id = PLMN-Id || CN-Id** + +The CN-Id is defined by the operator, and set in the nodes via O&M. + +For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413 [17]. + +## 12.4 RNC Identifier + +An RNC node is uniquely identified by its RNC Identifier (RNC-Id). The RNC-Id of an RNC is used in the UTRAN, in a GERAN which is operating in GERAN Iu mode and between them. A BSC which is part of a GERAN operating in Iu mode is uniquely identified by its RNC Identifier (RNC-Id). The RNC-Id of a BSC is used in a GERAN which is + +operating in GERAN Iu mode, in the UTRAN and between them. RNC-Id together with the PLMN identifier globally identifies the RNC. The RNC-Id on its own or the RNC-Id together with the PLMN-Id is used as the RNC identifier in the UTRAN Iub, Iur and Iu interfaces. The SRNC-Id is the RNC-Id of the SRNC. The C-RNC-Id is the RNC-Id of the controlling RNC. The D-RNC-Id is the RNC Id of the drift RNC. + +- **Global RNC-Id = PLMN-Id || RNC-Id** + +The RNC-Id is defined by the operator, and set in the RNC via O&M + +For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413 [17]. + +For the usage of this identifier on Iur-g, see 3GPP TS 43.130 [43]. + +## 12.5 Service Area Identifier + +The Service Area Identifier (SAI) is used to identify an area consisting of one or more cells belonging to the same Location Area. Such an area is called a Service Area and can be used for indicating the location of a UE to the CN. + +The Service Area Code (SAC) together with the PLMN-Id and the LAC constitute the Service Area Identifier. + +- **SAI = PLMN-Id || LAC || SAC** + +The SAC is defined by the operator, and set in the RNC via O&M. + +For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413 [17]. 3GPP TS 25.423 [37] and 3GPP TS 25.419 [38] define the use of this identifier in RNSAP and SABP signalling. + +A cell may belong to one or two Service Areas. If it belongs to two Service Areas, one is applicable in the Broadcast (BC) domain and the other is applicable in both the CS and PS domains. + +The Broadcast (BC) domain requires that its Service Areas each consist of only one cell. This does not limit the use of Service Areas for other domains. Refer to 3GPP TS 25.410 [39] for a definition of the BC domain. + +## 12.6 Shared Network Area Identifier + +The Shared Network Area Identifier (SNA-Id) is used to identify an area consisting of one or more Location Areas. Such an area is called a Shared Network Area and can be used to grant access rights to parts of a Shared Network to a UE in connected mode (see 3GPP TS 25.401 [39]). + +The Shared Network Area Identifier consists of the PLMN-Id followed by the Shared Network Area Code (SNAC). + +- **SNA-Id = PLMN-Id || SNAC** + +The SNAC is defined by the operator. + +For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413 [17]. + +# --- 13 Numbering, addressing and identification within the IP multimedia core network subsystem + +## 13.1 Introduction + +This clause describes the format of the parameters needed to access the IP multimedia core network subsystem. For further information on the use of the parameters see 3GPP TS 23.228 [24] and 3GPP TS 29.163 [63]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. For more information on the ".invalid" top level domain see IETF RFC 2606 [64]. + +## 13.2 Home network domain name + +The home network domain name shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19]. + +For 3GPP systems, if there is no ISIM application, the UE shall derive the home network domain name from the IMSI as described in the following steps: + +1. Take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning. +2. Use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain name. +3. Add the label "ims." to the beginning of the domain. + +An example of a home network domain name is: + +IMSI in use: 234150999999999; + +where: + +- MCC = 234; +- MNC = 15; and +- MSIN = 0999999999, + +which gives the home network domain name: ims.mnc015.mcc234.3gppnetwork.org. + +For 3GPP2 systems, if there is no IMC present, the UE shall derive the home network domain name as described in Annex C of 3GPP2 X.S0013-004 [67]. + +## 13.3 Private User Identity + +The private user identity shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. + +NOTE: It is possible for a representation of the IMSI to be contained within the NAI for the private identity. + +For 3GPP systems, if there is no ISIM application, the private user identity is not known. If the private user identity is not known, the private user identity shall be derived from the IMSI. + +The following steps show how to build the private user identity out of the IMSI: + +1. Use the whole string of digits as the username part of the private user identity; and +2. convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in subclause 13.2. + +The result will be a private user identity of the form "@ims.mnc.mcc.3gppnetwork.org". For example: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the private user identity then takes the form "234150999999999@ims.mnc015.mcc234.3gppnetwork.org". + +For 3GPP2 systems, if there is no IMC present, the UE shall derive the private user identity as described in Annex C of 3GPP2 X.S0013-004 [67]. + +## 13.4 Public User Identity + +A Public User Identity is any identity used by a user within the IMS subsystem for requesting communication to another user. + +The Public User Identity shall take the form of either a SIP URI (see IETF RFC 3261 [26]) or a Tel URI (see IETF RFC 3966 [45]). + +The 3GPP specifications describing the interfaces over which Public User Identities are transferred specify the allowed Public User Identity formats, in particular 3GPP TS 24.229 [81] for SIP signalling interfaces, 3GPP TS 29.229 [95] for Cx and Dx interfaces, 3GPP TS 29.329 [96] for Sh interface, 3GPP TS 29.165 [97] for II-NNI interface. + +In the case the user identity is a telephone number, it shall be represented either by a Tel URI or by a SIP URI that includes a "user=phone" URI parameter and a "userinfo" part that shall follow the same format as the Tel URI. + +According to 3GPP TS 24.229 [81], the UE can use either: + +- a global number as defined in IETF RFC 3966 [45] and following E.164 format, as defined by ITU-T Recommendation E.164 [10] or +- a local number, that shall include a “phone-context” parameter that identifies the scope of its validity, as per IETF RFC 3966 [45]. + +According to 3GPP TS 29.165 [97] a global number as defined in IETF RFC 3966 [45] shall be used in a tel-URI or in the user portion of a SIP URI with the user=phone parameter when conveyed via a non-roaming II-NNI except when agreement exists between the operators to also allow other kinds of numbers. + +According to 3GPP TS 29.229 [95] and 3GPP TS 29.329 [96] the canonical forms of SIP URI and Tel URI shall be used over the corresponding Diameter interfaces. + +The canonical form of a SIP URI for a Public User Identity shall take the form "sip:username@domain" as specified in IETF RFC 3261 [26], section 10.3. SIP URI comparisons shall be performed as defined in IETF RFC 3261 [26], section 19.1.4. + +The canonical form of a Tel URI for a Public User Identity shall take the form “tel:+” (max number of digits is 15), that represents an E.164 number and shall contain a global number without parameters and visual separators (see IETF RFC 3966[45], section 3). Tel URI comparisons shall be performed as defined in IETF RFC 3966[45], section 4. + +Public User Identities are stored in the HSS either as a distinct Public User Identity or as a Wildcarded Public User Identity. A distinct Public User Identity contains the Public User Identity that is used in routing and it is explicitly provisioned in the HSS. + +## 13.4A Wildcarded Public User Identity + +Public User Identities may be stored in the HSS as Wildcarded Public User Identities. A Wildcarded Public User Identity represents a collection of Public User Identities that share the same service profile and are included in the same implicit registration set. Wildcarded Public User Identities enable optimisation of the operation and maintenance of the nodes for the case in which a large amount of users are registered together and handled in the same way by the network. The format of a Wildcarded Public User Identity is the same as for the Wildcarded PSI described in subclause 13.5. + +## 13.4B Temporary Public User Identity + +For 3GPP systems, if there is no ISIM application to host the Public User Identity, a Temporary Public User Identity shall be derived, based on the IMSI. The Temporary Public User Identity shall be of the form as described in sub-clause 13.4 and shall consist of the string "sip:" appended with a username and domain portion equal to the IMSI derived Private User Identity, as described in sub-clause 13.2. An example using the same example IMSI from sub-clause 13.2 can be found below: + +EXAMPLE: "sip:234150999999999@ims.mnc015.mcc234.3gppnetwork.org". + +For 3GPP2 systems, if there is no IMC present, the UE shall derive the public user identity as described in Annex C of 3GPP2 X.S0013-004 [67]. + +## 13.5 Public Service Identity (PSI) + +The public service identity shall take the form of either a SIP URI (see IETF RFC 3261 [26]) or a Tel URI (see IETF RFC 3966 [45]). A public service identity identifies a service, or a specific resource created for a service on an application server. The domain part is pre-defined by the IMS operators and the IMS system provides the flexibility to dynamically create the user part of the PSIs. + +The PSIs are stored in the HSS either as a distinct PSI or as a wildcarded PSI. A distinct PSI contains the PSI that is used in routing, whilst a wildcarded PSI represents a collection of PSIs. Wildcarded PSIs enable optimisation of the operation and maintenance of the nodes. A wildcarded PSI consists of a delimited regular expression located either in the userinfo portion of the SIP URI or in the telephone-subscriber portion of the Tel URI. The regular expression in the wildcarded PSI shall take the form of Extended Regular Expressions (ERE) as defined in chapter 9 in IEEE 1003.1-2004 Part 1 [60]. The delimiter shall be the exclamation mark character ("!"). If more than two exclamation mark characters are present in the userinfo portion or telephone-subscriber portion of a wildcarded PSI then the outside pair + +of exclamation mark characters is regarded as the pair of delimiters (i.e. no exclamation mark characters are allowed to be present in the fixed parts of the userinfo portion or telephone-subscriber portion). + +When stored in the HSS, the wildcarded PSI shall include the delimiter character to indicate the extent of the part of the PSI that is wildcarded. It is used to separate the regular expression from the fixed part of the wildcarded PSI. + +Example: The following PSI could be stored in the HSS - "sip:chatlist!.\*!@example.com". + +When used on an interface, the exclamation mark characters within a PSI shall not be interpreted as delimiter.. + +Example: The following PSIs communicated in interface messages to the HSS will match to the wildcarded PSI of "sip:chatlist!.\*!@example.com" stored in the HSS: + +sip:chatlist1@example.com + +sip:chatlist2@example.com + +sip:chatlist42@example.com + +sip:chatlistAbC@example.com + +sip:chatlist!1@example.com + +Note that sip:chatlist1@example.com and sip:chatlist!1@example.com are regarded different specific PSIs, both matching the wildcarded PSI sip:chatlist!.\*!@example.com. + +When used by an application server to identify a specific resource (e.g. a chat session) over Inter Operator Network to Network Interface (II-NNI), the PSI should be a SIP URI without including a port number. + +NOTE: Based on local configuration policy, a PSI can be routed over Inter Operator Network to Network Interface (II-NNI). Details of this routing are operator specific and out of scope of this specification. + +## 13.5A Private Service Identity + +The Private Service Identity is applicable to a PSI user and is similar to a Private User Identity in the form of a Network Access Identifier (NAI), which is defined in IETF RFC 4282 [53]. The Private Service Identity is operator defined and although not operationally used for registration, authorisation and authentication in the same way as Private User Identity, it enables Public Service Identities to be associated to a Private Service Identity which is required for compatibility with the Cx procedures. + +## 13.6 Anonymous User Identity + +The Anonymous User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). A SIP URI for an Anonymous User Identity shall take the form "sip:user@domain". The user part shall be the string "anonymous" and the domain part shall be the string "anonymous.invalid". The full SIP URI for Anonymous User Identity is thus: + +"sip:anonymous@anonymous.invalid" + +For more information on the Anonymous User Identity and when it is used, see 3GPP TS 29.163 [63]. + +## 13.7 Unavailable User Identity + +The Unavailable User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). A SIP URI for an Unavailable User Identity shall take the form "sip:user@domain". The user part shall be the string "unavailable" and the domain part shall be the string "unknown.invalid". The full SIP URI for Unavailable User Identity is thus: + +"sip:unavailable@unknown.invalid" + +For more information on the Unavailable User Identity and when it is used, see 3GPP TS 29.163 [63]. + +## 13.8 Instance-ID + +An instance-id is a SIP Contact header parameter that uniquely identifies the SIP UA performing a registration. + +When an IMEI is available, the instance-id shall take the form of a IMEI URN (see RFC 7254 [79]). The format of the instance-id shall take the form "urn:gsma:imei:" where by the imeival shall contain the IMEI encoded as defined in RFC 7254 [79]. The optional and parameters shall not be included in the instance-id. An example of such an instance-id is as follows: + +EXAMPLE: urn:gsma:imei:90420156-025763-0 + +If no IMEI is available, the instance-id shall take the form of a string representation of a UUID as a URN as defined in IETF RFC 4122 [80]. An example of such an instance-id is as follows: + +EXAMPLE: urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 + +For more information on the instance-id and when it is used, see 3GPP TS 24.229 [81]. + +## 13.9 XCAP Root URI + +### 13.9.1 XCAP Root URI on Ut interface + +#### 13.9.1.1 General + +XCAP Root URI is an HTTP URI that represents the XCAP Root. Although a valid URI, the XCAP Root URI does not correspond to an actual resource. + +#### 13.9.1.2 Format of XCAP Root URI + +The XCAP Root URI, as defined in IETF RFC 4825 [94], is an HTTP URI that should have the following format: + +"http://xcap." + +in which "" identifies the domain hosting the XCAP server. + +NOTE 1: The XCAP Root URI does not contain a port portion or an abs path portion of a standard HTTP URI. + +If a preconfigured or provisioned XCAP Root URI is available then the UE shall use it. When a preconfigured or provisioned XCAP Root URI does not exist then the UE shall create the XCAP Root URI as follows: + +- The first label shall be "xcap". +- The next label(s) shall identify the home network as follows: + 1. When the UE has an ISIM, the domain name from the IMPI shall be used (see 3GPP TS 31.103 [93]) as follows: + - a. if the last two labels of the domain name from the IMPI are "3gppnetwork.org": + - i. the next labels shall be all labels of the domain name from the IMPI apart from the last two labels; and + - ii. the last three labels shall be "pub.3gppnetwork.org"; + - b. if the last two labels of the domain name from the IMPI are other than the "3gppnetwork.org": + - i. the next labels shall be all labels of the domain name from the IMPI; + 2. When the UE has a USIM and does not have ISIM, the home network shall be "ims.mnc.mcc.pub.3gppnetwork.org" where and shall be derived from the components of the IMSI defined in subclause 2.2. If there are only two significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the FQDN of XCAP Root URI. + +As an example for the case when the UE has ISIM, where the IMPI is "user@operator.com", the overall XCAP Root URI used by the UE would be: + +"http://xcap.operator.com". + +As an example for the case when the UE has ISIM, where the IMPI is "23415099999999@ims.mnc015.mcc234.3gppnetwork.org", the overall XCAP Root URI used by the UE would be: + +"xcap.ims.mnc015.mcc234.pub.3gppnetwork.org". + +As an example for the case when the UE has USIM and does not have ISIM, where the MCC is 345 and the MNC is 12, the overall XCAP Root URI created and used by the UE would be: + +"xcap.ims.mnc012.mcc345.pub.3gppnetwork.org" + +# --- 14 Numbering, addressing and identification for 3GPP System to WLAN Interworking + +## 14.1 Introduction + +This clause describes the format of the parameters needed to access the 3GPP system supporting the WLAN interworking. For further information on the use of the parameters see 3GPP TS 24.234 [48]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. + +## 14.2 Home network realm + +The home network realm shall be in the form of an Internet domain name, e.g. operator.com, as specified in RFC 1035 [19]. + +When attempting to authenticate within WLAN access, the WLAN UE shall derive the home network domain name from the IMSI as described in the following steps: + +1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27], 3GPP TS 51.011 [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; +2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain name; +3. add the label "wlan." to the beginning of the domain name. + +An example of a WLAN NAI realm is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 099999999 + +Which gives the home network domain name: wlan.mnc015.mcc234.3gppnetwork.org. + +NOTE: If it is not possible for the WLAN UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the WLAN UE determines the length of the MNC (2 or 3 digits). + +## 14.3 Root NAI + +The Root NAI shall take the form of a NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. + +The username part format of the Root NAI shall comply with IETF RFC 4187 [50] when EAP AKA authentication is used and with IETF RFC 4186 [51], when EAP SIM authentication is used. + +When the username part includes the IMSI, the Root NAI shall be built according to the following steps: + +1. Generate an identity conforming to NAI format from IMSI as defined in EAP SIM [51] and EAP AKA [50] as appropriate; + +2. Convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in subclause 14.2. + +The result will be a root NAI of the form: + +"0@wlan.mnc.mcc.3gppnetwork.org", for EAP AKA authentication and + "1@wlan.mnc.mcc.3gppnetwork.org", for EAP SIM authentication + +For example, for EAP AKA authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the root NAI then takes the form 0234150999999999@wlan.mnc015.mcc234.3gppnetwork.org. + +## 14.4 Decorated NAI + +The Decorated NAI shall take the form of a NAI and shall have the form 'homerealm!username@otherrealm' as specified in clause 2.7 of the IETF RFC 4282 [53]. + +The realm part of Decorated NAI consists of 'otherrealm', see the IETF draft 2486-bis RFC 4282 [53]. 'Homerealm' is the realm as specified in clause 14.2, using the HPLMN ID ('homeMCC' + 'homeMNC'). 'Otherrealm' is the realm built using the PLMN ID (visitedMCC + visited MNC) of the PLMN selected as a result of WLAN PLMN selection (see 3GPP TS 24.234 [48]). + +The username part format of the Root NAI shall comply with IETF RFC 4187 [50] when EAP AKA authentication is used and with IETF RFC 4186 [51], when EAP SIM authentication is used. + +When the username part of Decorated NAI includes the IMSI, it shall be built following the same steps specified for Root NAI in clause 14.3. + +The result will be a decorated NAI of the form: + +"wlan.mnc.mcc.3gppnetwork.org !0@wlan.mnc.mcc.3gppnetwork.org", for EAP AKA authentication and " + wlan.mnc.mcc.3gppnetwork.org !1@wlan.mnc.mcc.3gppnetwork.org ", for EAP SIM authentication + +For example, for EAP AKA authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15) and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71 then the Decorated NAI takes the form wlan.mnc015.mcc234.3gppnetwork.org!0234150999999999@wlan.mnc071.mcc610.3gppnetwork.org. + +NOTE: the 'otherrealm' specified in the present document is resolved by the WLAN AN. If the WLAN AN does not have access to the GRX, then the WLAN AN should resolve the realm by other means e.g. static look-up table, private local DNS server acting as an authoritative name server for that sub-domain. + +## 14.4A Fast Re-authentication NAI + +The Fast Re-authentication NAI in both EAP-SIM and EAP-AKA shall take the form of a NAI as specified in clause 2.1 of IETF RFC 4282 [53]. If the 3GPP AAA server does not return a complete NAI, the Fast Re-authentication NAI shall consist of the username part of the fast re-authentication identity as returned from the 3GPP AAA server and the same realm as used in the permanent user identity. If the 3GPP AAA server returns a complete NAI as the re-authentication identity, then this NAI shall be used. The username part of the fast re-authentication identity shall be decorated as described in 14.4 if the Selected PLMN is different from the HPLMN. + +NOTE: The permanent user identity is either the root or decorated NAI as defined in clauses 14.3 and 14.4. + +EXAMPLE 1: If the fast re-authentication identity returned by the 3GPP AAA Server is 458405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: 458405627015@wlan.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 2: If the fast re-authentication identity returned by the 3GPP AAA Server is "458405627015@aaa1.wlan.mnc015.mcc234.3gppnetwork.org" and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: 458405627015@aaa1.wlan.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 3: If the fast re-authentication identity returned by the 3GPP AAA Server is 458405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, + +the Fast Re-authentication NAI takes the form: + +wlan.mnc015.mcc234.3gppnetwork.org !458405627015@wlan.mnc071.mcc610.3gppnetwork.org + +## 14.5 Temporary identities + +The Temporary identities (Pseudonyms and re-authentication identities) shall take the form of a NAI username as specified in clause 2.1 of the IETF RFC 4282 [53]. + +Temporary identity shall be generated as specified in subclause 6.4.1 of 3GPP TS 33.234 [55]. This part of the temporary identity shall follow the UTF-8 transformation format specified in IETF RFC 2279 [54] except for the following reserved hexadecimal octet value: + +FF. + +When the temporary identity username is coded with FF, this reserved value is used to indicate the special case when no valid temporary identity exists in the WLAN UE (see 3GPP TS 24.234 [48]). The network shall not allocate a temporary identity with the whole username coded with the reserved hexadecimal value FF. + +For EAP-AKA authentication, the username portion of the pseudonym identity shall be prepended with the single digit "2" and the username portion of the fast re-authentication identity shall be prepended with the single digit "4" as specified in sub-clause 4.1.1.7 of IETF RFC 4187 [50]. + +For EAP-SIM authentication, the username portion of the pseudonym identity shall be prepended with the single digit "3" and the username portion of the fast re-authentication identity shall be prepended with the single digit "5" as specified in sub-clause 4.2.1.7 of IETF RFC 4186 [51]. + +## 14.6 Alternative NAI + +The Alternative NAI shall take the form of a NAI, i.e. 'any\_username@REALM' as specified of IETF RFC 4282 [53]. The Alternative NAI shall not be routable from any AAA server. + +The Alternative NAI shall contain a username part which is not derived from the IMSI. The username part shall not be a null string. + +The REALM part of the NAI shall be "unreachable.3gppnetwork.org". + +The result shall be an NAI in the form of: + +"@unreachable.3gppnetwork.org" + +## 14.7 W-APN + +The W-APN is composed of two parts as follows: + +- The W-APN Network Identifier; this defines to which external network the PDG is connected. +- The W-APN Operator Identifier; this defines in which PLMN the PDG serving the W-APN is located. + +The W-APN Operator Identifier is placed after the W-APN Network Identifier. The W-APN consisting of both the Network Identifier and Operator Identifier corresponds to a FQDN of a PDG; the W-APN has, after encoding as defined in the paragraph below, a maximum length of 100 octets. + +The encoding of the W-APN shall follow the Name Syntax defined in IETF RFC 2181 [18], IETF RFC 1035 [19] and IETF RFC 1123 [20]. The W-APN consists of one or more labels. Each label is coded as a one octet length field followed by that number of octets coded as 8 bit ASCII characters. Following IETF RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following IETF RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. The W-APN is not terminated by a length byte of zero. + +For the purpose of presentation, a W-APN is usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). + +The W-APN for the support of IMS Emergency calls shall take the form of a common, reserved Network Identifier described in subclause 14.7.1 together with the usual W-APN Operator Identifier as described in subclause 14.7.2. + +### 14.7.1 Format of W-APN Network Identifier + +The W-APN Network Identifier follows the format defined for APNs in subclause 9.1.1. In addition to what has been defined in subclause 9.1.1 the W-APN Network Identifier shall not contain "w-apn." and not end in ".3gppnetwork.org". + +A W-APN Network Identifier may be used to access a service associated with a PDG. This may be achieved by defining: + +- a W-APN which corresponds to a FQDN of a PDG, and which is locally interpreted by the PDG as a request for a specific service, or +- a W-APN Network Identifier consisting of 3 or more labels and starting with a Reserved Service Label, or a W-APN Network Identifier consisting of a Reserved Service Label alone, which indicates a PDG by the nature of the requested service. Reserved Service Labels and the corresponding services they stand for shall be agreed between operators who have WLAN roaming agreements. + +The W-APN Network Identifier for the support of IMS Emergency calls shall take the form of a common, reserved Network Identifier of the form "sos". + +As an example, the W-APN for MCC 345 and MNC 12 is coded in the DNS as: + +"sos.w-apn.mnc012.mcc345.pub.3gppnetwork.org". + +where "sos" is the W-APN Network Identifier and " mnc012.mcc345.pub.3gppnetwork.org " is the W-APN Operator Identifier. + +### 14.7.2 Format of W-APN Operator Identifier + +The W-APN Operator Identifier is composed of six labels. The last three labels shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label distinguishes the domain name as a W-APN. + +For each operator, there is a default W-APN Operator Identifier (i.e. domain name). This default W-APN Operator Identifier is derived from the IMSI as follows: + +"w-apn.mnc.mcc.pub.3gppnetwork.org" + +where: + +"mnc" and "mcc" serve as invariable identifiers for the following digits. + + and are derived from the components of the IMSI defined in subclause 2.2. + +Alternatively, the default W-APN Operator Identifier is derived using the MNC and MCC of the VPLMN. See 3GPP TS 24.234 [48] for more information. + +The default W-APN Operator Identifier is used in both non-roaming and roaming situations when attempting to translate a W-APN consisting only of a Network Identifier into the IP address of the PDG in the HPLMN. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "w-apn.mnc.mcc.pub.3gppnetwork.org" format of the W-APN OI shall be: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the W-APN OI. + +As an example, the W-APN OI for MCC 345 and MNC 12 is coded in the DNS as: + +"w-apn.mnc012.mcc345.pub.3gppnetwork.org". + +### 14.7.3 Alternative Format of W-APN Operator Identifier + +For situations when the PDG serving the W-APN is located in such network that is not part of the GRX (i.e. the Interoperator IP backbone), the default Operator Identifier described in sub-clause 14.7.2 is not available for use. This restriction originates from the “.3gppnetwork.org” domain, which is only available in GRX DNS for actual use. Thus an alternative format of W-APN Operator Identifier is required for this case. + +The Alternative W-APN Operator Identifiers shall be constructed as follows: + +"w-apn." + +where: + + corresponds to REALM names owned by the operator hosting the PDG serving the desired W-APN. + +REALM names are required to be unique, and are piggybacked on the administration of the Public Internet DNS namespace. REALM names may also belong to the operator of the VPLMN. + +As an example, the W-APN OI for the Operator REALM "notareal.com" is coded in the Public Internet DNS as: + +"w-apn.notareal.com". + +## 14.8 Emergency Realm and Emergency NAI for Emergency Cases + +The emergency realm shall be of the form of a home network realm as described in clause 14.2 prefixed with the label "sos." at the beginning of the domain name. + +An example of a WLAN emergency NAI realm is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999 + +Which gives the home network domain name: sos.wlan.mnc015.mcc234.3gppnetwork.org. + +The NAI for emergency cases shall be of the form as specified in subclauses 14.3 and 14.4, with the addition of the emergency realm as described above for PLMNs where the emergency realm is supported. + +When UE is using I-WLAN as the access network for IMS emergency calls and IMSI is not available, the Emergency NAI shall be an NAI compliant with IETF RFC 4282 [53] consisting of username and realm, either constructed with IMEI or MAC address, as specified in 3GPP TS 33.234 [55]. The exact format shall be: + +imei@sos.wlan.mnc.mcc.3gppnetwork.org + +or if IMEI is not available, + +mac@sos.wlan.mnc.mcc.3gppnetwork.org + +The realm part of the above NAI consists of the realm built using the PLMN ID (visitedMCC + visitedMNC) of the PLMN selected as a result of the network selection procedure, as specified in section 5.2.5.4 of the 3GPP TS 24.234 [48]. + +The MNC and MCC shall be with 3 digits coded. If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the realm of the NAI. + +For example, if the IMEI is 219551288888888, and the selected PLMN is with MCC 345 and MNC 12, the Emergency NAI then takes the form of [imei219551288888888@sos.wlan.mnc012.mcc345.3gppnetwork.org](mailto:imei219551288888888@sos.wlan.mnc012.mcc345.3gppnetwork.org). + +For example, if the MAC address is 44-45-53-54-00-AB, and the selected PLMN is with MCC 345 and MNC 12, the Emergency NAI then takes the form of [mac4445535400AB@sos.wlan.mnc012.mcc345.3gppnetwork.org](mailto:mac4445535400AB@sos.wlan.mnc012.mcc345.3gppnetwork.org), where the MAC address is represented in hexadecimal format without separators. + +# 15 Identification of Multimedia Broadcast/Multicast Service + +## 15.1 Introduction + +This clause describes the format of the parameters needed to access the Multimedia Broadcast/Multicast service. For further information on the use of the parameters see 3GPP TS 23.246 [52]. + +## 15.2 Structure of TMGI + +Temporary Mobile Group Identity (TMGI) is used within MBMS to uniquely identify Multicast and Broadcast bearer services. + +TMGI is composed as shown in figure 15.2.1. + +![Figure 15.2.1: Structure of TMGI. The diagram shows the TMGI as a concatenation of three parts: MBMS Service ID (6 digits), MCC (3 digits), and MNC (2 or 3 digits).](678ac9faaa56bb929499cebeea83a110_img.jpg) + +The diagram illustrates the structure of the Temporary Mobile Group Identity (TMGI). It is composed of three parts: MBMS Service ID, MCC, and MNC. The MBMS Service ID is 6 digits long, the MCC is 3 digits long, and the MNC is 2 or 3 digits long. The TMGI is the concatenation of these three parts. + +| | | | +|-----------------|----------|---------------| +| 6 digits | 3 digits | 2 or 3 digits | +| MBMS Service ID | MCC | MNC | +| TMGI | | | + +Figure 15.2.1: Structure of TMGI. The diagram shows the TMGI as a concatenation of three parts: MBMS Service ID (6 digits), MCC (3 digits), and MNC (2 or 3 digits). + +Figure 15.2.1: Structure of TMGI + +The TMGI is composed of three parts: + +- 1) MBMS Service ID consisting of three octets. MBMS Service ID consists of a 6-digit fixed-length hexadecimal number between 000000 and FFFFFFF. MBMS Service ID uniquely identifies an MBMS bearer service within a PLMN. +- 2) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the BM-SC; +- 3) Mobile Network Code (MNC) consisting of two or three digits (depending on the assignment to the PLMN by its national numbering authority). The MNC identifies the PLMN which the BM-SC belongs to. For more information on the use of the TMGI, see 3GPP TS 23.246 [52]. + +## 15.3 Structure of MBMS SAI + +The MBMS Service Area (MBMS SA) is defined in 3GPP TS 23.246 [52]. It comprises of one or more MBMS Service Area Identities (MBMS SAIs), in any case each MBMS SA shall not include more than 256 MBMS SAIs. An MBMS SAI shall identify a group of cells within a PLMN, that is independent of the associated Location/Routing/Service Area and the physical location of the cell(s). A cell shall be able to belong to one or more MBMS SAs, and therefore is addressable by one or more MBMS SAIs. + +The MBMS SAI shall be a decimal number between 0 and 65,535 (inclusive). The value 0 has a special meaning; it shall denote the whole PLMN as the MBMS Service Area and it shall indicate to a receiving RNC/BSS/MCE that all cells reachable by that RNC/BSS/MCE shall be part of the MBMS Service Area. + +With the exception of the specific MBMS Service Area Identity with value 0, the MBMS Service Area Identity shall be unique within a PLMN and shall be defined in such a way that all the corresponding cells are MBMS capable. + +## 15.4 Home Network Realm + +The home network realm shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19]. + +During the MBMS service activation in roaming scenario, the BM-SC in the visited network shall derive the home network domain name from the IMSI as described in the following steps: + +1. Take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27], 3GPP TS 51.011 [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; +2. Use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" realm name; +3. Add the label "mbms." to the beginning of the realm name. + +An example of a home realm used in the MBMS roaming case is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999 + +Which gives the home network realm: mbms.mnc015.mcc234.3gppnetwork.org. + +# --- 16 Numbering, addressing and identification within the GAA subsystem + +## 16.1 Introduction + +This clause describes the format of the parameters needed to access the GAA system. For further information on the use of the parameters see 3GPP TS 33.221 [58]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. + +## 16.2 BSF address + +The Bootstrapping Server Function (BSF) address is in the form of a Fully Qualified Domain Name as defined in IETF RFC 1035 [19]. + +For 3GPP systems, the UE shall discover the BSF address from the identity information related to the UICC application that is used during the bootstrapping procedure i.e. IMSI for USIM, or IMPI for ISIM, in the following way: + +- In the case where the USIM is used in bootstrapping, the BSF address shall be derived as follows: + 1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; + 2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.pub.3gppnetwork.org" domain name; + 3. add the label "bsf." to the beginning of the domain. + +Example 1: If IMSI in use is "234150999999999", where MCC=234, MNC=15, and MSIN=0999999999, the BSF address would be "bsf.mnc015.mcc234.pub.3gppnetwork.org". + +- In the case where ISIM is used in bootstrapping, the BSF address shall be derived as follows: + +1. extract the domain name from the IMPI; +2. if the last two labels of the domain name extracted from the IMPI are "3gppnetwork.org": + - a. the first label is "bsf"; + - b. the next labels are all labels of the domain name extracted from the IMPI apart from the last two labels; and + - c. the last three labels are "pub.3gppnetwork.org"; + +Example 2: If the IMPI in use is "234150999999999@ims.mnc015.mcc234.3gppnetwork.org", the BSF address would be "bsf.ims.mnc015.mcc234.pub.3gppnetwork.org". + +3. if the last two labels of the domain name extracted from the IMPI are other than the "3gppnetwork.org": + - a. add the label "bsf." to the beginning of the domain. + +Example 3: If the IMPI in use is "user@operator.com", the BSF address would be "bsf.operator.com". + +# --- 17 Numbering, addressing and identification within the Generic Access Network + +## 17.1 Introduction + +This clause describes the format of the parameters needed to access the Generic Access Network (GAN). For further information on the use of the parameters and GAN in general, see 3GPP TS 43.318 [61] and 3GPP TS 44.318 [62]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. + +## 17.2 Network Access Identifiers + +### 17.2.1 Home network realm + +The home network realm shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19]. + +The UE shall derive the home network realm from the IMSI as described in the following steps: + +1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27], 3GPP TS 51.011 [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; +2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" network realm; +3. add the label "gan." to the beginning of the network realm. + +An example of a home network realm is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999, + +Which gives the home network realm: gan.mnc015.mcc234.3gppnetwork.org. + +NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). + +### 17.2.2 Full Authentication NAI + +The Full Authentication NAI in both EAP-SIM and EAP-AKA shall take the form of an NAI as specified in clause 2.1 of IETF RFC 4282 [53]. The format of the Full Authentication NAI shall comply with IETF RFC 4187 [50] when EAP-AKA authentication is used and with IETF RFC 4186 [51], when EAP-SIM authentication is used. The realm used shall be a home network realm as defined in sub-clause 17.2.1. + +The result will therefore be an identity of the form: + +"0@gan.mnc.mcc.3gppnetwork.org", for EAP-AKA authentication and +"1@gan.mnc.mcc.3gppnetwork.org", for EAP-SIM authentication + +EXAMPLE 1: For EAP AKA authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Full Authentication NAI takes the form 0234150999999999@gan.mnc015.mcc234.3gppnetwork.org. + +EXAMPLE 2: For EAP SIM authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Full Authentication NAI takes the form 1234150999999999@gan.mnc015.mcc234.3gppnetwork.org. + +### 17.2.3 Fast Re-authentication NAI + +The Fast Re-authentication NAI in both EAP-SIM and EAP-AKA shall take the form of an NAI as specified in clause 2.1 of IETF RFC 4282 [53]. The UE shall use the re-authentication identity received during the previous EAP-SIM or EAP-AKA authentication procedure. If such an NAI contains a realm part then the UE should not modify it, otherwise it shall use a home network realm as defined in sub clause 17.2.1. + +The result will therefore be an identity of the form: + +"@" for both EAP-SIM and EAP-AKA authentication when a realm is present in the re-authentication identity received during the previous EAP-SIM or EAP-AKA authentication procedure and + +"@gan.mnc.mcc.3gppnetwork.org", for both EAP-SIM and EAP-AKA authentication when a realm is *not* present in the re-authentication identity received during the previous EAP-SIM or EAP-AKA authentication procedure. + +EXAMPLE 1: If the re-authentication identity is "12345" and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Fast Re-authentication NAI takes the form 12345@gan.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 2: If the re-authentication identity is "12345@aaa1.gan.mnc015.mcc234.3gppnetwork.org", the Fast Re-authentication NAI takes the form 12345@aaa1.gan.mnc015.mcc234.3gppnetwork.org + +## 17.3 Node Identifiers + +### 17.3.1 Home network domain name + +The home network domain name shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19]. + +The UE shall derive the home network domain name from the IMSI as described in the following steps: + +- take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27], 3GPP TS 51.011 [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; + +2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.pub.3gppnetwork.org" domain name; +3. add the label "gan." to the beginning of the domain name. + +An example of a home network domain name is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999, + +Which gives the home network domain name: gan.mnc015.mcc234.pub.3gppnetwork.org. + +NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). + +### 17.3.2 Provisioning GANC-SEGW identifier + +The Provisioning GANC-SEGW identifier shall take the form of a fully qualified domain name (FQDN) as specified in IETF RFC 1035 [19]. If the (U)SIM is not provisioned with the FQDN or IP address of the Provisioning GANC-SEGW, the UE derives an FQDN from the IMSI to identify the Provisioning GANC-SEGW. The UE shall derive such an FQDN as follows: + +1. create a domain name as specified in 17.3.1; +2. add the label "psegw." to the beginning of the domain name. + +An example of an FQDN for a Provisioning GANC-SEGW is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999, + +Which gives the FQDN: psegw.gan.mnc015.mcc234.pub.3gppnetwork.org. + +NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). + +### 17.3.3 Provisioning GANC identifier + +The Provisioning GANC identifier shall take the form of a fully qualified domain name (FQDN) as specified in IETF RFC 1035 [19]. If the (U)SIM is not provisioned with the FQDN or IP address of the Provisioning GANC, the UE derives an FQDN from the IMSI to identify the Provisioning GANC. The UE shall derive such an FQDN as follows: + +1. create a domain name as specified in 17.3.1; +2. add the label "pganc." to the beginning of the domain name. + +An example of an FQDN for a Provisioning GANC is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999, + +Which gives the FQDN: pganc.gan.mnc015.mcc234.pub.3gppnetwork.org. + +NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). + +# --- 18 Addressing and Identification for IMS Service Continuity and Single-Radio Voice Call Continuity + +## 18.1 Introduction + +This clause describes the format of the parameters needed for the support of IMS Service Continuity. For further information on the use of the parameters see 3GPP TS 23.237 [71] and also 3GPP TS 23.292 [70]. + +## 18.2 CS Domain Routeing Number (CSRN) + +A CS Domain Routeing Number (CSRN) is a number that is used to route a call from the IM CN subsystem to the user in the CS domain. The structure is as defined in sub-clause 3.4. + +## 18.3 IP Multimedia Routeing Number (IMRN) + +An IP Multimedia Routeing Number (IMRN) is a routable number that points to the IM CN subsystem. In a roaming scenario, the IMRN has the same structure as an international ISDN number (see sub-clause 3.4). The Tel URI format of the IMRN (see IETF RFC 3966 [45]) is treated as a PSI (see sub-clause 13.5) within the IM CN subsystem. + +## 18.4 Session Transfer Number (STN) + +A Session Transfer Number (STN) is a public telecommunication number, as defined by ITU-T Recommendation E.164 [10] and is used by the UE to request Session Transfer of the media path from PS to CS access. + +## 18.5 Session Transfer Identifier (STI) + +A Session Transfer Identifier (STI) is a SIP URI or SIP dialogue ID (see IETF RFC 3261 [26] for more information) and is used by the UE to request Session Transfer of a media path. + +## 18.6 Session Transfer Number for Single Radio Voice Call Continuity (STN-SR) + +The Session Transfer Number for Single Radio Voice Call Continuity (STN-SR) is a public telecommunication number, as defined by ITU-T Recommendation E.164 [10] and is used by the MSC Server to request session transfer of the media path from the PS domain to CS domain. + +### 18.7 Correlation MSISDN + +A Correlation MSISDN (C-MSISDN) is an MSISDN (see sub-clause 3.3) that is used for correlation of sessions at access transfer and to route a call from the IM CN subsystem to the same user in the CS domain. The C-MSISDN is equal to the MSISDN or the basic MSISDN if multnumbering option is used (see 3GPP TS 23.008 [2], section 2.1.3) of the CS access. Any MSISDN of a user that can be used for TS11 (telephony) in the CS domain which is not shared by more than one IMS Private Identity in an IMS CN subsystem, can serve as the user's C-MSISDN. + +The C-MSISDN is bound to the IMS Private User Identity and is uniquely assigned per IMSI and IMS Private User Identity. + +If A-MSISDN is available it shall be used as the C-MSISDN. For the definition of A-MSISDN refer to section 18.9. + +## 18.8 Transfer Identifier for CS to PS Single Radio Voice Call Continuity (STI-rSR) + +A Session Transfer Identifier for CS to PS Single Radio Voice Call Continuity (STI-rSR) is a SIP URI (see IETF RFC 3261 [26] for more information) and is used by the UE to request access transfer of a media path. + +## 18.9 Additional MSISDN + +An Additional MSISDN (A-MSISDN) is an MSISDN (see sub-clause 3.3) that is assigned to a user with PS subscription in addition to the already assigned MSISDN(s). + +The structure of an A-MSISDN should follow the structure of an MS international ISDN number as defined in section 3.3. + +The A-MSISDN shall be able to be used for TS11 (telephony) in the CS domain and shall be uniquely assigned per IMSI. + +--- + +# 19 Numbering, addressing and identification for the Evolved Packet Core (EPC) + +## 19.1 Introduction + +This clause describes the format of the parameters needed to access the Enhanced Packet Core (EPC). For further information on the use of the parameters see 3GPP TS 23.401 [72] and 3GPP TS 23.402 [68]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document + +## 19.2 Home Network Realm/Domain + +The home Network Realm/Domain shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19]. + +The Home Network Realm/Domain shall be in the form of "epc.mnc.mcc.3gppnetwork.org", where "" and "" fields correspond to the MNC and MCC of the operator's PLMN. Both the "" and "" fields are 3 digits long. If the MNC of the PLMN is 2 digits, then a zero shall be added at the beginning. + +For example, the Home Network Realm/Domain of an IMSI shall be derived as described in the following steps: + +1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; +2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain name; +3. add the label "epc" to the beginning of the domain name. + +An example of a Home Network Realm/Domain is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999; + +Which gives the Home Network Realm/Domain name: epc.mnc015.mcc234.3gppnetwork.org. + +NOTE: If it is not possible for a UE to identify whether a 2 or 3 digit MNC is used (e.g. USIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). + +## 19.3 3GPP access to non-3GPP access interworking + +### 19.3.1 Introduction + +This subclause describes the format of the UE identification needed to access the 3GPP EPC from both 3GPP and non-3GPP accesses. + +The NAI is generated respectively by: + +- the S-GW at the S5/S8 reference point; +- the non-3GPP access network or client at the S2a reference point; +- the ePDG at the S2b reference point; +- the DSMIPv6 client at the S2c reference point. + +The NAI shall be generated based on the IMSI or, when UE is performing emergency attach and IMSI is not available or not authenticated, on the IMEI (see subclause 19.3.6). + +For further information on the use of the parameters see 3GPP TS 24.234 [48]. + +### 19.3.2 Root NAI + +The Root NAI shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. + +The format of the username part of the Root NAI shall comply with IETF RFC 4187 [50] for use with EAP AKA authentication. For EAP-AKA', see IETF RFC 5448 [82], the Root NAI shall comply with IETF RFC 4187 [50] except that the username part of the Root NAI shall be prepended with the single digit "6". + +When the username part includes the IMSI, the Root NAI shall be built according to the following steps: + +1. Generate an identity conforming to NAI format from IMSI as defined in EAP AKA [50] as appropriate; +2. Convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in subclause 19.2. +3. Prefix domain name with the label "nai". + +The result will be a root NAI of the form: + +"0@nai.epc.mnc.mcc.3gppnetwork.org" for EAP AKA authentication + +"6@nai.epc.mnc.mcc.3gppnetwork.org" for EAP AKA' authentication + +For example, if the IMSI is 234150999999999 (MCC = 234, MNC = 15), the root NAI then takes the form as 023415099999999@nai.epc.mnc015.mcc234.3gppnetwork.org for EAP AKA authentication, and takes the form as [623415099999999@nai.epc.mnc015.mcc234.3gppnetwork.org](mailto:623415099999999@nai.epc.mnc015.mcc234.3gppnetwork.org) for EAP AKA' authentication. + +The NAI sent in the Mobile Node Identifier field in PMIPv6 shall not include the digit prepended in front of the IMSI that is described above. Consequently the Permanent User Identity assigned by the 3GPP AAA Server when Network Based Mobility is used shall not include this digit either. + +### 19.3.3 Decorated NAI + +The Decorated NAI shall take the form of a NAI and shall have the form 'homerealm!username@otherrealm' as specified in clause 2.7 of the IETF RFC 4282 [53]. + +The realm part of Decorated NAI consists of 'otherrealm', see the IETF RFC 4282 [53]. 'Homerealm' is the realm as specified in subclause 19.2, using the HPLMN ID ('homeMCC' + 'homeMNC'). 'Otherrealm' is the realm built using the PLMN ID (visitedMCC + visited MNC) of the PLMN selected as a result of the PLMN selection (see 3GPP TS 23.402 [68]). + +The username part format of the Root NAI shall comply with IETF RFC 4187 [50] for use with EAP AKA. For EAP AKA', see IETF RFC 5448 [82], the Root NAI shall comply with IETF RFC 4187 [50] except that the username part of the NAI shall be prepended with single digit "6". + +When the username part of Decorated NAI includes the IMSI, it shall be built following the same steps specified for Root NAI in subclause 19.3.2. + +The result will be a decorated NAI of the form: + +nai.epc.mnc.mcc.3gppnetwork.org !0@nai.epc.mnc.mcc.3gppnetwork.org for EAP AKA authentication + +or + +nai.epc.mnc.mcc.3gppnetwork.org !6@nai.epc.mnc.mcc.3gppnetwork.org for EAP AKA' authentication. + +For example, if the IMSI is 234150999999999 (MCC = 234, MNC = 15) and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, then the Decorated NAI takes the form either as +nai.epc.mnc015.mcc234.3gppnetwork.org!023415099999999@nai.epc.mnc071.mcc610.3gppnetwork.org for EAP AKA authentication or +nai.epc.mnc015.mcc234.3gppnetwork.org!623415099999999@nai.epc.mnc071.mcc610.3gppnetwork.org for EAP AKA' authentication. + +### 19.3.4 Fast Re-authentication NAI + +The Fast Re-authentication NAI shall take the form of a NAI as specified in clause 2.1 of IETF RFC 4282 [53]. If the 3GPP AAA server does not return a complete NAI, the Fast Re-authentication NAI shall consist of the username part of the fast re-authentication identity as returned from the 3GPP AAA server and the same realm as used in the permanent user identity. If the 3GPP AAA server returns a complete NAI as the re-authentication identity, then this NAI shall be used. The username part of the fast re-authentication identity shall be decorated as described in 19.3.3 if the Selected PLMN is different from the HPLMN. + +For EAP-AKA authentication, the username portion of the fast re-authentication identity shall be prepended with the single digit "4" as specified in sub-clause 4.1.1.7 of IETF RFC 4187 [50]. + +For EAP AKA', see IETF RFC 5448 [82], the Fast Re-authentication NAI shall comply with IETF RFC 4187 [50] except that the username part of the NAI shall be prepended with single digit "8". + +NOTE: The permanent user identity is either the Root NAI or Decorated NAI as defined in clauses 19.3.2 and 19.3.3, respectively. + +EXAMPLE 1: If the fast re-authentication identity returned by the 3GPP AAA Server is 358405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: +358405627015@nai.epc.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 2: If the fast re-authentication identity returned by the 3GPP AAA Server is "358405627015@aaa1.nai.epc.mnc015.mcc234.3gppnetwork.org" and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: +358405627015@aaa1.nai.epc.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 3: If the fast re-authentication identity returned by the 3GPP AAA Server is 358405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, the Fast Re-authentication NAI takes the form: +nai.epc.mnc015.mcc234.3gppnetwork.org !358405627015@nai.epc.mnc071.mcc610.3gppnetwork.org. + +### 19.3.5 Pseudonym Identities + +The pseudonym shall take the form of an NAI, as specified in sub-clause 2.1 of IETF RFC 4282 [53]. + +The pseudonym shall be generated as specified in sub-clause 6.4.1 of 3GPP TS 33.234 [55]. This part of the pseudonym shall follow the UTF-8 transformation format specified in IETF RFC 2279 [54] except for the following reserved hexadecimal octet value: + +FF + +When the pseudonym username is coded with FF, this reserved value is used to indicate the special case when no valid temporary identity exists in the UE (see 3GPP TS 24.234 [48] for more information). The network shall not allocate a temporary identity with the whole username coded with the reserved hexadecimal value FF. + +The username portion of the pseudonym identity shall be prepended with the single digit "2" as specified in sub-clause 4.1.1.7 of IETF RFC 4187 [50] for EAP-AKA. For EAP AKA', see IETF RFC 5448 [82], the pseudonym NAI shall comply with IETF RFC 4187 [50] except that the username part of the NAI shall be prepended with single digit "7". + +NOTE: The permanent user identity is either the Root NAI or Decorated NAI as defined in sub-clauses 19.3.2 and 19.3.3, respectively. + +EXAMPLE 1: For EAP AKA, if the pseudonym returned by the 3GPP AAA Server is 258405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the pseudonym NAI for the case when NAI decoration is not used takes the form: 258405627015@nai.epc.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 2: For EAP AKA', if the pseudonym returned by the 3GPP AAA Server is 758405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the pseudonym NAI for the case when NAI decoration is not used takes the form: 758405627015@nai.epc.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 3: For EAP AKA, if the pseudonym returned by the 3GPP AAA Server is 258405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, the pseudonym NAI takes the form: +nai.epc.mnc015.mcc234.3gppnetwork.org! +258405627015@nai.epc.mnc071.mcc610.3gppnetwork.org + +EXAMPLE 4: For EAP AKA', if the pseudonym returned by the 3GPP AAA Server is 758405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, the pseudonym NAI takes the form: +nai.epc.mnc015.mcc234.3gppnetwork.org! +758405627015@nai.epc.mnc071.mcc610.3gppnetwork.org + +### 19.3.6 Emergency NAI for Limited Service State + +This subclause describes the format of the UE identification needed to access the 3GPP EPC from both 3GPP and non-3GPP accesses, when UE is performing emergency attach and IMSI is not available or not authenticated. For more information, see sections 4.6.1 and 5.2 of 3GPP TS 23.402 [68]. + +The Emergency NAI for Limited Service State shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. The exact format shall be: + +imei@sos.invalid + +NOTE: The top level domain ".invalid" is a reserved top level domain, as specified in IETF RFC 2606 [64], and is used here due to the fact that this NAI never needs to be resolved for routing (as specified in 3GPP TS 23.402 [68]). + +or + +mac@sos.invalid + +For example, if the IMEI is 219551288888888, the Emergency NAI for Limited Service State then takes the form of [imei219551288888888@sos.invalid](#). + +For example, if the MAC address is 44-45-53-54-00-AB, the Emergency NAI for Limited Service State then takes the form of [mac4445535400AB@sos.invalid](#), where the MAC address is represented in hexadecimal format without separators. + +## 19.4 Identifiers for Domain Name System procedures + +### 19.4.1 Introduction + +This clause describes Domain Name System (DNS) related identifiers used by the procedures specified in 3GPP TS 29.303 [73]. + +The DNS identifiers for APNs for legacy systems (as defined in clause 9), RAIs (as defined in clause C.1), GSNs (as defined in clause C.2) and RNCs (as defined in clause C.3) in the present document use the top level domain ".gprs" and have a similar purpose and function as those described below. These clauses are still valid and DNS records based on these and the below types of identifiers are expected to coexist in an operator's network for the purpose of backwards compatibility and interworking with legacy networks. + +The APN as defined in clause 9 is used also in EPC to identify the access network to be used for a specific PDN connection or PDP Context. In addition, the APN Network Identifier (APN-NI) part of the APN as defined in subclause 9.1.1 of the present document may be used to access a service associated with a PDN-GW or GGSN. This is achieved by defining an APN which in addition to being usable to select a PDN-GW or GGSN is locally interpreted by the PDN-GW or GGSN as a request for a specific service. + +For DNS procedures defined in 3GPP TS 29.303 [73], an APN-FQDN derived from a given APN is used instead of the APN itself as defined in subclause 19.4.2.2. For all other purposes, including communication between EPC nodes and to the UE, the APN format defined in clause 9 is used. In order to support backwards compatibility with existing GPRS/PS roaming using the Gn/Gp interfaces, the APN as specified in clause 9 of the present document may also be used for the DNS procedures as defined in 3GPP TS 23.060 [3]. + +### 19.4.2 Fully Qualified Domain Names (FQDNs) + +#### 19.4.2.1 General + +The encoding of any identifier used as part of a Fully Qualified Domain Name (FQDN) shall follow the Name Syntax defined in IETF RFC 2181 [18], IETF RFC 1035 [19] and IETF RFC 1123 [20]. An FQDN consists of one or more labels. Each label is coded as a one octet length field followed by that number of octets coded as 8 bit ASCII characters. Following IETF RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following IETF RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. Identifiers are not terminated by a length byte of zero. + +NOTE: A length byte of zero is added by the querying entity at the end of the FQDN before interrogating a DNS server. + +For the purpose of presentation, identifiers are usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). + +#### 19.4.2.2 Access Point Name FQDN (APN-FQDN) + +##### 19.4.2.2.1 Structure + +The Access Point Name FQDN (APN-FQDN) is derived from an APN as follows. The APN consists of an APN Network Identifier (APN-NI) and an APN Operator Identifier (APN-OI), which are as defined in subclause 9.1.1 and 9.1.2 of the present document. + +If an APN is constructed using the default APN-OI, the APN-FQDN shall be obtained from the APN by inserting the labels "apn.epc." between the APN-NI and the default APN - OI, and by replacing the label ".gprs" at the end of the default APN-OI with the labels ".3gppnetwork.org". + +EXAMPLE1: For an APN of internet.mnc015.mcc234.gprs, the derived APN-FQDN is [internet.apn.epc.mnc015.mcc234.3gppnetwork.org](#) + +If an APN is constructed using the APN-OI Replacement field (as defined in 3GPP TS 23.060 [3] and 3GPP TS 23.401 [72]), the APN-FQDN shall be obtained from the APN by inserting the labels "apn.epc." between the label "mnc" and its preceding label, and by replacing the label ".gprs" at the end of the APN-OI Replacement field with the labels ".3gppnetwork.org". + +EXAMPLE 2: If an APN-OI Replacement field is province1.mnc015.mcc234.gprs and an APN-NI is internet, the derived APN-FQDN is internet.province1.apn.epc.mnc015.mcc234.3gppnetwork.org + +19.4.2.2.2 Void + +19.4.2.2.3 Void + +19.4.2.2.4 Void + +19.4.2.3 Tracking Area Identity (TAI) + +The Tracking Area Identity (TAI) consists of a Mobile Country Code (MCC), Mobile Network Code (MNC), and Tracking Area Code (TAC). It is composed as shown in figure 19.4.2.3.1. + +![Diagram showing the structure of the Tracking Area Identity (TAI). It consists of three boxes labeled MCC, MNC, and TAC. Below these boxes, a double-headed arrow labeled 'Tracking Area Identity' spans the width of the MCC and MNC boxes, indicating that the TAI is composed of these two elements.](7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg) + +Diagram showing the structure of the Tracking Area Identity (TAI). It consists of three boxes labeled MCC, MNC, and TAC. Below these boxes, a double-headed arrow labeled 'Tracking Area Identity' spans the width of the MCC and MNC boxes, indicating that the TAI is composed of these two elements. + +**Figure 19.4.2.3.1: Structure of the Tracking Area Identity (TAI)** + +The TAI is composed of the following elements: + +- Mobile Country Code (MCC) identifies the country in which the PLMN is located. The value of the MCC is the same as the three digit MCC contained in the IMSI; +- Mobile Network Code (MNC) is a code identifying the PLMN in that country. The value of the MNC is the same as the two or three digit MNC contained in the IMSI; +- Tracking Area Code (TAC) is a fixed length code (of 2 octets) identifying a Tracking Area within a PLMN. This part of the tracking area identification shall be coded using a full hexadecimal representation. The following are reserved hexadecimal values of the TAC: + - 0000, and + - FFFE. + +NOTE: The above reserved values are used in some special cases when no valid TAI exists in the MS (see 3GPP TS 24.301 [90] for more information). + +A subdomain name can be derived from the TAI. This shall be done by adding the label "tac" to the beginning of the Home Network Realm/Domain (see subclause 19.2) and encoding the TAC as a sub-domain. This is called the TAI FQDN.. + +The TAI FQDN shall be constructed as follows: + +tac-lb.tac-hb.tac.epc.mnc.mcc.3gppnetwork.org + +The TAC is a 16-bit integer. The is the hexadecimal string of the most significant byte in the TAC and the is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in or , "0" digit(s) shall be inserted at the left side to fill the 2 digit coding. + +#### 19.4.2.4 Mobility Management Entity (MME) + +A Mobility Management Entity (MME) within an operator's network is identified using a MME Group ID (MMEGI), and an MME Code (MMEC). + +A subdomain name shall be derived from the MNC and MCC by adding the label "mme" to the beginning of the Home Network Realm/Domain (see subclause 19.2). + +The MME node FQDN shall be constructed as: + +mme.mme.mme.epc.mnc.mcc.3gppnetwork.org + +Where and are the hexadecimal strings of the MMEC and MMEGI. + +An MME pool FQDN shall be constructed as: + +mme.mme.epc.mnc.mcc.3gppnetwork.org + +If there are less than 2 significant digits in , "0" digit(s) shall be inserted at the left side to fill the 2 digit coding. If there are less than 4 significant digits in , "0" digit(s) shall be inserted at the left side to fill the 4 digit coding. + +#### 19.4.2.5 Routing Area Identity (RAI) - EPC + +The Routing Area Identity (RAI) consists of a RAC, LAC, MNC and MCC. + +A subdomain name for use by core network nodes based on RAI shall be derived from the MNC and MCC by adding the label "rac" to the beginning of the Home Network Realm/Domain (see subclause 19.2). + +The RAI FQDN shall be constructed as: + +rac.lac.rac.epc.mnc.mcc.3gppnetwork.org + + and shall be Hex coded digits representing the LAC and RAC codes respectively. + +If there are less than 4 significant digits in or , one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. + +Note: Above subdomain is for release 8 core network nodes to allow DNS records other than A/AAAA records. The subdomain name in Annex C.2 are still used for existing A/AAAA records for pre-Release 8 nodes and are also still used for backward compatibility. + +#### 19.4.2.6 Serving GPRS Support Node (SGSN) within SGSN pool + +A specific SGSN within an operator's network is identified using the RAI FQDN (subclause 19.4.2.5) and the Network Resource Identifier (NRI) (see 3GPP TS 23.236 [23]). Such an identifier can be used by a target MME or SGSN node to connect to the source SGSN node. + +The SGSN FQDN shall be constructed as: + +nri-sgsn.rac.lac.rac.epc.mnc.mcc.3gppnetwork.org + + shall be Hex coded digits representing the NRI code of the SGSN. + +If there are less than 4 significant digits in , one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. Coding for other fields is the same as in Section 19.4.2.5. + +When a target MME constructs the FQDN of the source SGSN in the case of SGSN pooling, it should derive the NRI from the 8-bit MME Code received in the GUTI from the UE. However, if the length of the NRI, e.g., X, which is configured in the MME is less than 8 bits, then the MME should use only the most significant X bits of the MME Code as the NRI within the SGSN FQDN. + +Note: Above subdomain is for release 8 core network nodes to allow DNS records other than A/AAAA records. The subdomain name in Annex C.2 are still used for existing A/AAAA records for pre-Release 8 nodes and are also still used for backward compatibility. . + +### 19.4.2.7 Target RNC-ID for U-TRAN + +In the special case of a UTRAN target RNC a possible SGSN that can control that RNC can be identified by RNC-ID. This identifier can be used for SRNS relocation with a U-TRAN target RNC. + +A subdomain name for use by core network nodes based on RNC-ID shall be derived from the MNC and MCC by adding the label "rnc" to the beginning of the Home Network Realm/Domain (see subclause 19.2). + +The RNC FQDN shall be constructed as: + +`rnc.rnc.epc.mnc.mcc.3gppnetwork.org` + + shall be Hex coded digits representing the RNC-ID code of the RNC. + +If there are less than 4 significant digits in , one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. + +NOTE: Above subdomain is for release 8 core network nodes to allow DNS records other than A/AAAA records. The subdomain name in Annex C.3 are still used for existing A/AAAA records for pre-Release 8 nodes and are still used for backward compatibility. However, RNC-ID in Annex C.3 was originally intended for the case where only one SGSN controlled an RNC-ID and gave the SGSN IP address. The usage for the above RNC FQDN is potentially broader and can target an SGSN pool. + +### 19.4.2.8 DNS subdomain for operator usage in EPC + +The EPC nodes DNS subdomain (DNS zone) shall be derived from the MNC and MCC by adding the label "node" to the beginning of the Home Network Realm/Domain (see subclause 19.2) and shall be constructed as: + +`node.epc.mnc.mcc.3gppnetwork.org` + +This DNS subdomain is formally placed into the operator's control. 3GPP shall never take this DNS subdomain back or any zone cut/subdomain within it for any purpose. As a result the operator can safely provision any DNS records it chooses under this subdomain without concern about future 3GPP standards encroaching on the DNS names within this zone. + +### 19.4.2.9 ePDG Fully Qualified Domain Name + +The ePDG Fully Qualified Domain Name (ePDG FQDN) contains an Operator Identifier that shall uniquely identify the PLMN where the ePDG is located. The ePDG FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The third and fourth labels together shall uniquely identify the PLMN. The first two labels shall be "epdg.epc". The result of the ePDG FQDN will be: + +`"epdg.epc.mnc.mcc.pub.3gppnetwork.org"` + +In the roaming case, the UE may utilise the services of the VPLMN. In this case, the ePDG FQDN Operator Identifier shall be constructed as described above, but using the MNC and MCC of the VPLMN. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "epdg.epc.mnc.mcc.pub.3gppnetwork.org" format of the ePDG FQDN Operator Identifier shall be: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the ePDG FQDN. + +As an example, the ePDG FQDN Operator Identifier for MCC 345 and MNC 12 is coded in the DNS as: + +`"epdg.epc.mnc012.mcc345.pub.3gppnetwork.org"`. + +### 19.4.2.10 Global eNodeB-ID for eNodeB + +The Global eNodeB-ID is used to identify eNodeBs globally which is composed of the concatenation of MCC, MNC and the eNodeBID. The MCC and MNC are the same as included in the E-UTRAN Cell Global Identifier (ECGI) (see subclause 19.6). + +A subdomain name shall be derived from the MNC and MCC by adding the label "enb" to the beginning of the Home Network Realm/Domain (see subclause 19.2). + +The Global eNodeB-ID FQDN shall be constructed as: + +enb.enb.epc.mnc.mcc.3gppnetwork.org + +The shall be coded using a full hexadecimal representation. If there are less than 4 significant digits in , "0" digit(s) shall be inserted at the left side to fill the 4 digit coding. + +### 19.4.3 Service and Protocol service names for 3GPP + +A list of standardized "service-parms" names is required to identify a "service" as defined in section 6.5 of IETF RFC 3958 [74]. + +The following table defines the names to be used in the procedures specified in 3GPP TS 29.303 [73]: + +**Table 19.4.3.1: List of 'app-service' and 'app-protocol' names** + +| Description | IETF RFC 3958 section 6.5 'app-service' name | IETF RFC 3958 section 6.5 'app-protocol' name | +|----------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| PGW and interface types supported by the PGW | x-3gpp-pgw | x-s5-gtp , x-s5-pmip,
x-s8-gtp , x-s8-pmip,
x-s2a-pmip, x-s2a-mipv4, x-s2a-gtp,
x-s2b-pmip, x-s2b-gtp, x-s2c-dsmip,
x-gn, x-gp | +| SGW and interface types supported by the SGW | x-3gpp-sgw | x-s5-gtp , x-s5-pmip,
x-s8-gtp , x-s8-pmip,
x-s11, x-s12, x-s4,
x-s1-u, x-s2a-pmip, x-s2b-pmip | +| GGSN | x-3gpp-ggsn | x-gn, x-gp | +| SGSN | x-3gpp-sgsn | x-gn, x-gp, x-s4,x-s3, x-s16, x-sv | +| MME and interface types supported by the MME | x-3gpp-mme | x-s10, x-s11, x-s3, x-s6a, x-s1-mme,
x-gn, x-gp, x-sv | +| MSC Server | x-3gpp-msc | x-sv | + +NOTE 1: The formats follow the experimental format as specified in IETF RFC 3958 [74]. For example, to find the S8 PMIP interfaces on a PGW the Service Parameter of "3gpp-pgw:x-s8-pmip" would be used as input in the procedures defined in IETF RFC 3958 [74]. + +NOTE 2: Currently 'app-service' names identify 3GPP node type and 'app-protocol' identify 3GPP interfaces, which differs from more common usage of S-NAPTR where app-protocol is used for transport protocol. Type of nodes (i.e PGW, SGW, SGSN, MME, MSC Server etc) and interfaces (i.e. S11, S5, S8, Sv, etc.) follow the standard names from 3GPP TS 23.401 [72] ,3GPP TS 29.060 [6] and3GPP TS 23.216 [92] with prefix "x-" added. + +NOTE 3: x-gn denotes an intra-PLMN interface using GTPv1-C, x-gp denotes a inter-PLMN interface using GTPv1-C. + +NOTE 4: The app-service of x-3gpp-pgw with app-protocols x-gn or x-gp identifies the co-located GGSN function on a PGW. The app-service of x-3gpp-ggsn with app-protocols x-gn or x-gp identifies a GGSN function that is not co-located with a PGW. + +NOTE 5: The app-service of x-3gpp-msc with app-protocol x-sv identifies the MSC Sv interface service. + +## 19.5 Access Network Identity + +A trusted non-3GPP access network used by the UE to access EPS can be identified using the Access Network Identity. The Access Network Identity is used as an input parameter in the EPS security procedures as specified in 3GPP TS 33.402 [69]. The format and signalling of the parameter between the network and the UE is specified in 3GPP TS 24.302 [77] and the format and signalling of this parameter between access network and core network is specified in 3GPP TS 29.273 [78]. + +The encoding of the Access Network Identity shall be specified within 3GPP, but the Access Network Identity definition for each non-3GPP access network is under the responsibility of the corresponding standardisation organisation respectively. + +## 19.6 E-UTRAN Cell Identity (ECI) and E-UTRAN Cell Global Identification (ECGI) + +The E-UTRAN Cell Global Identification (ECGI) shall be composed of the concatenation of the PLMN Identifier (PLMN-Id) and the E-UTRAN Cell Identity (ECI) as shown in figure 19.6.1 and shall be globally unique: + +![Diagram showing the structure of E-UTRAN Cell Global Identification (ECGI). It consists of three boxes labeled MCC, MNC, and ECI. A double-headed arrow labeled 'E-UTRAN Cell Global Identification' spans across the MCC and MNC boxes, indicating that the ECGI is the concatenation of MCC and MNC.](a4bfa2343d75076b79f7e33d93915e00_img.jpg) + +The diagram illustrates the structure of the E-UTRAN Cell Global Identification (ECGI). It features three rectangular boxes arranged horizontally, labeled 'MCC', 'MNC', and 'ECI' from left to right. Below the 'MCC' and 'MNC' boxes, a horizontal double-headed arrow spans their combined width, with the text 'E-UTRAN Cell Global Identification' centered beneath it. This visualizes that the ECGI is the concatenation of the MCC and MNC components. + +Diagram showing the structure of E-UTRAN Cell Global Identification (ECGI). It consists of three boxes labeled MCC, MNC, and ECI. A double-headed arrow labeled 'E-UTRAN Cell Global Identification' spans across the MCC and MNC boxes, indicating that the ECGI is the concatenation of MCC and MNC. + +**Figure 19.6.1: Structure of E-UTRAN Cell Global Identification** + +The ECI shall be of fixed length of 28 bits and shall be coded using full hexadecimal representation. The exact coding of the ECI is the responsibility of each PLMN operator. + +For more details on ECI and ECGI, see 3GPP TS 36.413 [84]. + +## 19.7 Identifiers for communications with packet data networks and applications + +### 19.7.1 Introduction + +This subclause describes external identifiers used to facilitate communications with packet data networks and applications (e.g. Machine Type Communication (MTC) applications on the external network/MTC servers) as specified in 3GPP TS 23.682 [98]. + +### 19.7.2 External Identifier + +An External Identifier identifies a subscription associated to an IMSI. A subscription associated to an IMSI may have one or several External Identifier(s) that are stored in the HSS. + +The External Identifier is used at: + +- the Tsp reference point; +- the T4 reference point; +- the S6m reference point; +- the Gi/SGi reference point; + +The External Identifier shall have the form `username@realm` as specified in clause 2.1 of IETF RFC 4282 [53]. + +The username part format of the External Identifier shall contain a Local Identifier as specified in 3GPP TS 23.682 [98]. The realm part format of the External Identifier shall contain a Domain Identifier as specified in 3GPP TS 23.682 [98]. As specified in subclause 4 of IETF RFC 4282 [53], the Domain Identifier shall be a duly registered Internet domain name. The combination of Local Identifier and Domain Identifier makes the External Identifier globally unique. + +The result of the External Identifier form is: + +`"@"` + +An example of an External Identifier is: + +Local Identifier in use: "123456789"; + +Domain Identifier = "domain.com"; + +Which gives the External Identifier as: + +"123456789@domain.com" + +--- + +## 20 Addressing and Identification for IMS Centralized Services + +### 20.1 Introduction + +This clause describes the format of the parameters needed specifically for IMS Centralized Services (ICS). For further information on the use of ICS parameters, see 3GPP TS 23.292 [70]. + +### 20.2 UE based solution + +In this solution, the UE is provisioned with an ICS specific client that simply reuses IMS registration as defined in 3GPP TS 23.228 [24]. Therefore, ICS capable UE shall reuse the identities defined in clause 13. + +### 20.3 Network based solution + +#### 20.3.1 General + +In this solution the MSC Server enhanced for ICS performs a special IMS registration on behalf of the UE. Thus, the MSC Server enhanced for ICS shall use a Private User Identity and Temporary Public User Identity that are different to those defined in clause 13 (see 3GPP TS 23.292 [70], sub-clause 4.6.2 for more information). Furthermore, the MSC Server enhanced for ICS derives a Conference Factory URI that is known to the home IMS. These are defined in the following sub-clauses. + +#### 20.3.2 Home network domain name + +The home network domain name shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19]. + +The MSC Server enhanced for ICS shall derive the home network domain name from the subscriber's IMSI as described in the following steps: + +1. Take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning. +2. Use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain name. +3. Add the label "ics." to the beginning of the domain. + +An example of a home network domain name is: + +IMSI in use: 234150999999999; + +where: + +- MCC = 234; +- MNC = 15; and +- MSIN = 0999999999, + +which gives the home network domain name: ics.mnc015.mcc234.3gppnetwork.org + +### 20.3.3 Private User Identity + +The Private User Identity shall take the form of an NAI, and shall have the form "username@realm" as specified in clause 2.1 of IETF RFC 4282 [53]. + +The MSC Server enhanced for ICS shall derive the Private User Identity from the subscriber's IMSI as follows: + +1. Use the whole string of digits as the username part of the private user identity; and +2. convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in sub-clause 20.3.2. + +The result will be a Private User Identity of the form "@ics.mnc.mcc.3gppnetwork.org". For example if the IMSI is 234150999999999 (MCC = 234, MNC = 15), the private user identity then takes the form 234150999999999@ics.mnc015.mcc234.3gppnetwork.org + +### 20.3.4 Public User Identity + +The Public User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]), and shall have the form "sip:username@domain". + +The MSC Server enhanced for ICS shall derive the Public User Identity from the subscriber's IMSI. The Public User Identity shall consist of the string "sip:" appended with a username and domain portion equal to the IMSI derived Private User Identity described in sub-clause 20.3.3. An example using the same example IMSI from sub-clause 20.3.3 can be found below: + +EXAMPLE: "sip:234150999999999@ics.mnc015.mcc234.3gppnetwork.org". + +### 20.3.5 Conference Factory URI + +The Conference Factory URI shall take the form of a SIP URI (see IETF RFC 3261 [26]) with a host portion set to the home network domain name as described in subclause 20.3.2 prefixed with "conf-factory.". An example using the same example IMSI from sub-clause 20.3.2 can be found below: + +EXAMPLE: "sip:conf-factory.ics.mnc015.mcc234.3gppnetwork.org". + +The user portion of the SIP URI is optional and implementation specific. + +--- + +## 21 Addressing and Identification for Dual Stack Mobile IPv6 (DSMIPv6) + +### 21.1 Introduction + +This clause describes the format of the parameters needed by the UE to use Dual Stack Mobile IPv6 (DSMIPv6) as specified in 3GPP TS 23.327 [76] and 3GPP TS 23.402 [68]. + +### 21.2 Home Agent – Access Point Name (HA-APN) + +#### 21.2.1 General + +The HA-APN is composed of two parts as follows: + +- The HA-APN Network Identifier; this defines to which external network the HA is connected. +- The HA-APN Operator Identifier; this defines in which PLMN the HA serving the HA-APN is located. + +The HA-APN Operator Identifier is placed after the HA-APN Network Identifier. The HA-APN consisting of both the Network Identifier and Operator Identifier corresponds to a FQDN of a HA; the HA-APN has, after encoding as defined in the paragraph below, a maximum length of 100 octets. + +The encoding of the HA-APN shall follow the Name Syntax defined in IETF RFC 2181 [18], IETF RFC 1035 [19] and IETF RFC 1123 [20]. The HA-APN consists of one or more labels. Each label is coded as a one octet length field + +followed by that number of octets coded as 8 bit ASCII characters. Following IETF RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following IETF RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. The HA-APN is not terminated by a length byte of zero. + +For the purpose of presentation, a HA-APN is usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). + +## 21.2.2 Format of HA-APN Network Identifier + +The HA-APN Network Identifier follows the format defined for APNs in subclause 9.1.1. In addition to what has been defined in subclause 9.1.1 the HA-APN Network Identifier shall not contain "ha-apn." or "w-apn." and not end in ".3gppnetwork.org". + +A HA-APN Network Identifier may be used to access a service associated with a HA. This may be achieved by defining: + +- a HA-APN which corresponds to a FQDN of a HA, and which is locally interpreted by the HA as a request for a specific service, or +- a HA-APN Network Identifier consisting of 3 or more labels and starting with a Reserved Service Label, or a HA-APN Network Identifier consisting of a Reserved Service Label alone, which indicates a HA by the nature of the requested service. Reserved Service Labels and the corresponding services they stand for shall be agreed between operators who have roaming agreements. + +As an example, the HA-APN for MCC 345 and MNC 12 is coded in the DNS as: + +"internet.ha-apn.mnc012.mcc345.pub.3gppnetwork.org". + +where "internet" is the HA-APN Network Identifier and "mnc012.mcc345.pub.3gppnetwork.org" is the HA-APN Operator Identifier. + +## 21.2.3 Format of HA-APN Operator Identifier + +The HA-APN Operator Identifier is composed of six labels. The last three labels shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label distinguishes the domain name as a HA-APN. + +For each operator, there is a default HA-APN Operator Identifier (i.e. domain name). This default HA-APN Operator Identifier is derived from the IMSI as follows: + +"ha-apn.mnc.mcc.pub.3gppnetwork.org" + +where: + +"mnc" and "mcc" serve as invariable identifiers for the following digits. + + and are derived from the components of the IMSI defined in subclause 2.2. + +Alternatively, the default HA-APN Operator Identifier is derived using the MNC and MCC of the VPLMN. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "ha-apn.mnc.mcc.pub.3gppnetwork.org" format of the HA-APN OI shall be: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the HA-APN OI. + +As an example, the HA-APN OI for MCC 345 and MNC 12 is coded in the DNS as: + +"ha-apn.mnc012.mcc345.pub.3gppnetwork.org". + +--- + +## 22 Addressing and identification for ANDSF + +### 22.1 Introduction + +This clause describes the format of the parameters needed by the UE to use Access Network Discovery and Selection Function (ANDSF) as specified in 3GPP TS 23.402 [68]. + +### 22.2 ANDSF Server Name (ANDSF-SN) + +#### 22.2.1 General + +ANDSF Server Name (ANDSF-SN) is used by UE to discover ANDSF Server in the network. + +#### 22.2.2 Format of ANDSF-SN + +The ANDSF-SN is composed of six labels. The last three labels shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label shall be "andsf". + +The ANDSF-SN is derived from the IMSI or Visited PLMN Identity as follows: + +"andsf.mnc.mcc.pub.3gppnetwork.org" + +where: + +"mnc" and "mcc" serve as invariable identifiers for the following digits. + +- When contacting Visited ANDSF (V-ANDSF), the and shall be derived from the Visited PLMN Identity as defined in subclause 12.1. +- When contacting Home ANDSF (H-ANDSF), the and shall be derived from the components of the IMSI defined in subclause 2.2. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "andsf.mnc.mcc.pub.3gppnetwork.org" format of the ANDSF-SN shall be: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the ANDSF-SN. + +As an example, the ANDSF-SN OI for MCC 345 and MNC 12 is coded in the DNS as: + +"andsf.mnc012.mcc345.pub.3gppnetwork.org". + +--- + +## 23 Numbering, addressing and identification for the Relay Node OAM System + +### 23.1 Introduction + +This clause describes some information needed to access the Relay Node OAM system as specified in TS 36.300 [91]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. + +### 23.2 OAM System Realm/Domain + +The OAM system shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19]. + +The OAM System Realm/Domain shall be in the form of "oam.mnc.mcc.3gppnetwork.org", where "" and "" fields correspond to the MNC and MCC of the operator's PLMN. Both the "" and "" fields are 3 digits long. If the MNC of the PLMN is 2 digits, then a zero shall be added at the beginning. + +For example, the OAM System Realm/Domain of an IMSI shall be derived as described in the following steps: + +1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; +2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain name; +3. add the label "oam" to the beginning of the domain name. + +An example of an OAM System Realm/Domain is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999; + +Which gives the OAM System Realm/Domain name: oam.mnc015.mcc234.3gppnetwork.org. + +NOTE: If it is not possible for a Relay Node to identify whether a 2 or 3 digit MNC is used (e.g. USIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the Relay Node determines the length of the MNC (2 or 3 digits). + +## 23.3 Identifiers for Domain Name System procedures + +### 23.3.1 Introduction + +This clause describes Domain Name System (DNS) related identifiers used by the procedures specified in 3GPP TS 29.303 [73]. + +### 23.3.2 Fully Qualified Domain Names (FQDNs) + +#### 23.3.2.1 General + +See subclause 19.4.2.1. + +#### 23.3.2.2 Relay Node Vendor-Specific OAM System + +As part of the startup procedure, relay nodes (see 3GPP TS 36.300 [91], sub-clause 4.7) needs to discover its Operations and Maintenance (OAM) system. A relay node vendor-specific OAM system within an operator's network is identified using the relay node type allocation code from IMEI or IMEISV (IMEI-TAC), MNC and MCC from IMSI and in some cases also tracking area code information associated to the eNB serving the relay node. + +A subdomain name for use by EUTRAN OAM system nodes shall be derived from the MNC and MCC by adding the label "eutran" to the beginning of the OAM System Realm/Domain (see sub-clause 23.2). + +The vendor-specific relay node OAM system FQDN shall be constructed as following: + +- tac-lb.tac-hb.imei-tac.eutran-rn.oam.mnc.mcc.3gppnetwork.org + +The IMEI-TAC is 8 decimal digits (see sub-clause 6.2). + +NOTE: IMEI-TAC is used for the type allocation code from IMEI or IMEISV instead of TAC in this sub-clause in order to separate it from the tracking area code (TAC). + +The TAC is a 16 bit integer. is the hexadecimal string of the most significant byte in the TAC and is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in or , "0" digit(s) shall be inserted at the left side to fill the 2 digit coding. + +--- + +## Annex A (informative): Colour Codes + +### A.1 Utilization of the BSIC + +A BSIC is allocated to each cell. A BSIC can take one of 64 values. In each cell the BSIC is broadcast in each burst sent on the SCH, and is then known by all MSs which synchronise with this cell. The BSIC is used by the MS for several purposes, all aiming at avoiding ambiguity or interference which can arise when an MS in a given position can receive signals from two cells *using the same BCCH frequency*. + +Some of the uses of the BSIC relate to cases where the MS is attached to one of the cells. Other uses relate to cases where the MS is attached to a third cell, usually somewhere between the two cells in question. + +The first category of uses includes: + +- The three least significant bits of the BSIC indicate which of the 8 training sequences is used in the bursts sent on the downlink common channels of the cell. Different training sequences allow for a better transmission if there is interference. The group of the three least significant bits of the BSIC is called the BCC (Base station Colour Code). +- The BSIC is used to modify the bursts sent by the MSs on the access bursts. This aims to avoid one cell correctly decoding access bursts sent to another cell. + +The second category of uses includes: + +- When in connected mode, the MSs measure and report the level they receive on a number of frequencies, corresponding to the BCCH frequencies of neighbouring cells in the same network as the used cell. Along with the measurement result, the MS sends to the network the BSIC which it has received on that frequency. This enables the network to discriminate between several cells which happen to use the same BCCH frequency. Poor discrimination might result in faulty handovers. +- The content of the measurement report messages is limited to information for 6 neighbour cells. It is therefore useful to limit the reported cells to those to which handovers are accepted. For this purpose, each cell provides a list of the values of the three most significant bits of the BSICs which are allocated to the cells which are useful to consider for handovers (usually excluding cells in other PLMNs). This information enables the MS to discard information for cells with non-conformant BSICs and not to report them. The group of the three most significant bits of the BSIC is called the NCC (Network Colour Code). + +It should be noted that when in idle mode, the MS identifies a cell (for cell selection purposes) according to the cell identity broadcast on the BCCH and *not* by the BSIC. + +--- + +### A.2 Guidance for planning + +From these uses, the following planning rule can be derived: + +*If there exist places where MSs can receive signals from two cells, whether in the same PLMN or in different PLMNs, which use the same BCCH frequency, it is highly preferable that these two cells have different BSICs.* + +Where the coverage areas of two PLMNs overlap, the rule above is respected if: + +- 1) The PLMNs use different sets of BCCH frequencies (In particular, this is the case if no frequency is common to the two PLMNs. This usually holds for PLMNs in the same country), or +- 2) The PLMNs use different sets of NCCs, or +- 3) BSIC and BCCH frequency planning is co-ordinated. + +Recognizing that method 3) is more cumbersome than method 2), and that method 1) is too constraining, it is suggested that overlapping PLMNs which use a common part of the spectrum agree on different NCCs to be used in any overlapping areas. As an example, a preliminary NCC allocation for countries in the European region can be found in clause A.3 of this annex. + +This example can be used as a basis for bilateral agreements. However, the use of the NCCs allocated in clause A.3 is not compulsory. PLMN operators can agree on different BSIC allocation rules in border areas. The use of BSICs is not constrained in non-overlapping areas, or if ambiguities are resolved by using different sets of BCCH frequencies. + +If the PLMNs share one or more cells with other PLMNs, the planning rule above should be applied also when the BCCH frequency is different. The rule should be respected by using different sets of NCCs. In addition to that, the PLMN sharing one or more cells with other PLMNs should use different NCCs for shared and non-shared neighbouring cells. + +## A.3 Example of PLMN Colour Codes (NCCs) for the European region + +| | | | +|---------------|---|-------------------------| +| Austria | : | 0 | +| Belgium | : | 1 | +| Cyprus | : | 3 | +| Denmark | : | 1 | +| Finland | : | 0 | +| France | : | 0 | +| Germany | : | 3 | +| Greece | : | 0 | +| Iceland | : | 0 | +| Ireland | : | 3 | +| Italy | : | 2 | +| Liechtenstein | : | 2 | +| Luxembourg | : | 2 | +| Malta | : | 1 | +| Monaco | : | 3 (possibly 0(=France)) | +| Netherlands | : | 0 | +| Norway | : | 3 | +| Portugal | : | 3 | +| San Marino | : | 0 (possibly 2(= Italy)) | +| Spain | : | 1 | +| Sweden | : | 2 | +| Switzerland | : | 1 | +| Turkey | : | 2 | +| UK | : | 2 | +| Vatican | : | 1 (possibly 2(=Italy)) | +| Yugoslavia | : | 3 | + +This allows a second operator for each country by allocating the colour codes $n$ (in the table) and $n + 4$ . More than 2 colour codes per country may be used provided that in border areas only the values $n$ and/or $n+4$ are used. + +## Annex B (normative): IMEI Check Digit computation + +### B.1 Representation of IMEI + +The International Mobile station Equipment Identity and Software Version number (IMEISV), as defined in clause 6, is a 16 digit decimal number composed of three distinct elements: + +- an 8 digit Type Allocation Code (TAC); +- a 6 digit Serial Number (SNR); and +- a 2 digit Software Version Number (SVN). + +The IMEISV is formed by concatenating these three elements as illustrated below: + +| | | | +|-----|-----|-----| +| TAC | SNR | SVN | +|-----|-----|-----| + +**Figure A.1: Composition of the IMEISV** + +The IMEI is complemented by a check digit as defined in clause 3. The Luhn Check Digit (CD) is computed on the 14 most significant digits of the IMEISV, that is on the value obtained by ignoring the SVN digits. + +The method for computing the Luhn check is defined in Annex B of the International Standard "Identification cards - Numbering system and registration procedure for issuer identifiers" (ISO/IEC 7812 [3]). + +In order to specify precisely how the CD is computed for the IMEI, it is necessary to label the individual digits of the IMEISV, excluding the SVN. This is done as follows: + +The (14 most significant) digits of the IMEISV are labelled D14, D13 ... D1, where: + +- TAC = D14, D13 ... D7 (with D7 the least significant digit of TAC); +- SNR = D6, D5 ... D1 (with D1 the least significant digit of SNR). + +### B.2 Computation of CD for an IMEI + +Computation of CD from the IMEI proceeds as follows: + +- Step 1: Double the values of the odd labelled digits D1, D3, D5 ... D13 of the IMEI. +- Step 2: Add together the individual digits of all the seven numbers obtained in Step 1, and then add this sum to the sum of all the even labelled digits D2, D4, D6 ... D14 of the IMEI. +- Step 3: If the number obtained in Step 2 ends in 0, then set CD to be 0. If the number obtained in Step 2 does not end in 0, then set CD to be that number subtracted from the next higher number which does end in 0. + +### B.3 Example of computation + +**IMEI (14 most significant digits):** + +| TAC | | | | | | | | SNR | | | | | | +|-----|-----|-----|-----|-----|----|----|----|-----|----|----|----|----|----| +| D14 | D13 | D12 | D11 | D10 | D9 | D8 | D7 | D6 | D5 | D4 | D3 | D2 | D1 | +| 2 | 6 | 0 | 5 | 3 | 1 | 7 | 9 | 3 | 1 | 1 | 3 | 8 | 3 | + +**Step 1:** + +| | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 2 | 6 | 0 | 5 | 3 | 1 | 7 | 9 | 3 | 1 | 1 | 3 | 8 | 3 | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---| + +| | | | | | | | +|----|----|----|----|----|----|----| +| x2 | x2 | x2 | x2 | x2 | x2 | x2 | +| 12 | 10 | 2 | 18 | 2 | 6 | 6 | + +**Step 2:** + +$$2 + 1 + 2 + 0 + 1 + 0 + 3 + 2 + 7 + 1 + 8 + 3 + 2 + 1 + 6 + 8 + 6 = 53$$ + +**Step 3:** + +$$CD = 60 - 53 = 7$$ + +--- + +## Annex C (normative): Naming convention + +This normative annex defines a naming convention which will make it possible for DNS servers to translate logical names for GSNs and RAs to physical IP addresses. The use of logical names is optional, but if the option is used, it shall comply with the naming convention described in this annex. The fully qualified domain names used throughout this annex shall follow the format defined in IETF RFC 1035 [19]. + +--- + +### C.1 Routing Area Identities + +This subclause describes a possible way to support inter-PLMN roaming. + +When an MS roams between two SGSNs within the same PLMN, the new SGSN finds the address of the old SGSN from the identity of the old RA. Thus, each SGSN can determine the address of every other SGSN in the PLMN. + +When an MS roams from an SGSN in one PLMN to an SGSN in another PLMN, the new SGSN may be unable to determine the address of the old SGSN. Instead, the SGSN transforms the old RA information to a logical name of the form: + +*racAAAA.lacBBBB.mncYYY.mccZZZ.gprs* + +A and B shall be Hex coded digits; Y and Z shall be encoded as single digits (in the range 0-9). + +If there are less than 4 significant digits in AAAA or BBBB, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digit coding. + +As an example, the logical name for RAC 123A, LAC 234B, MCC 167 and MNC 92 will be coded in the DNS server as: + +*rac123A.lac234B.mnc092.mcc167.gprs.* + +The SGSN may then acquire the IP address of the old SGSN from a DNS server, using the logical address. Introducing the DNS concept in GPRS enables operators to use logical names instead of IP addresses when referring to nodes (e.g. GSNs), thus providing flexibility and transparency in addressing. Each PLMN should include at least one DNS server (which may optionally be connected via the DNS service provided by the GSM Association). Note that these DNS servers are GPRS internal entities, unknown outside the GPRS system. + +The above implies that at least MCC || MNC || LAC || RAC (= RAI) is sent as the RA parameter over the radio interface when an MS roams to another RA. + +If for any reason the new SGSN fails to obtain the address of the old SGSN, the new SGSN takes the same actions as when the corresponding event occurs within one PLMN. + +Another way to support seamless inter-PLMN roaming is to store the SGSN IP addresses in the HLR and request them when necessary. + +If Intra Domain Connection of RAN Nodes to Multiple CN Nodes (see 3GPP TS 23.236 [23]) is applied then the Network Resource Identifier (NRI) identifies uniquely a given SGSN node out of all the SGSNs serving the same pool area. + +If the new SGSN is not able to extract the NRI from the old P-TMSI, it shall retrieve the address of the default SGSN (see 3GPP TS 23.236 [23]) serving the old RA, using the logical name described earlier in this section. The default SGSN in the old RA relays the GTP signalling to the old SGSN identified by the NRI in the old P-TMSI unless the default SGSN itself is the old SGSN. + +If the new SGSN is able to extract the NRI from the old P-TMSI, then it shall attempt to derive the address of the old SGSN from the NRI and the old RAI. NRI-to-SGSN assignments may be either configured (by O&M) in the new SGSN, or retrieved from a DNS server. If a DNS server is used, it shall be queried using the following logical name, derived from the old RAI and NRI information: + +*nriCCCC.racDDDD.lacEEEE.mncYYY.mccZZZ.gprs* + +C, D and E shall be Hex coded digits, Y and Z shall be encoded as single digits (in the range 0-9). If there are less than 4 significant digits in CCCC, DDDD or EEEE, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digits coding. + +As an example, the logical name for NRI 3A, RAC 123A, LAC 234B, MCC 167 and MNC 92 will be coded in the DNS server as: + +*nri003A.rac123A.lac234B.mnc092.mcc167.gprs.* + +If for any reason the new SGSN fails to obtain the address of the old SGSN using this method, then as a fallback method it shall retrieve the address of the default SGSN serving the old RA. + +--- + +## C.2 GPRS Support Nodes + +This subclause defines a naming convention for GSNs. + +It shall be possible to refer to a GSN by a logical name which shall then be translated into a physical IP address. This clause proposes a GSN naming convention which would make it possible for an internal GPRS DNS server to make the translation. + +An example of how a logical name of an SGSN could appear is: + +*sgsnXXXX.mncYYY.mccZZZ.gprs* + +X, shall be Hex coded digits, Y and Z shall be encoded as single digits (in the range 0-9). + +If there are less than 4 significant digits in XXXX one or more "0" digit(s) is/are inserted at the left side to fill the 4 digits coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digit coding. + +As an example, the logical name for SGSN 1B34, MCC 167 and MNC 92 will be coded in the DNS server as: +*sgsn1B34.mnc092.mcc167.gprs* + +--- + +## C.3 Target ID + +This subclause describes a possible way to support SRNS relocation. + +In UMTS, when SRNS relocation is executed, a target ID which consists of MCC, MNC and RNC ID is used as routing information to route to the target RNC via the new SGSN. An old SGSN shall resolve a new SGSN IP address by a target ID to send the Forward Relocation Request message to the new SGSN. + +It shall be possible to refer to a target ID by a logical name which shall be translated into an SGSN IP address to take into account inter-PLMN handover. The old SGSN transforms the target ID information into a logical name of the form: + +*rncXXXX.mncYYY.mccZZZ.gprs* + +X shall be Hex coded digits; Y and Z shall be encoded as single digits (in the range 0-9). If there are less than 4 significant digits in XXXX, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digits coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digit coding. Then, for example, a DNS server is used to translate the logical name to an SGSN IP address. + +As an example, the logical name for RNC 1B34, MCC 167 and MNC 92 will be coded in the DNS server as: +*rnc1B34.mnc092.mcc167.gprs* + +--- + +## Annex D (informative): Applicability and use of the ".3gppnetwork.org" domain name + +There currently exists a private IP network between operators to provide connectivity for user transparent services that utilise protocols that rely on IP. This includes (but is not necessarily limited to) such services as GPRS/PS roaming, WLAN roaming, GPRS/PS inter-PLMN handover and inter-MMSC MM delivery. This inter-PLMN IP backbone network consists of indirect connections using brokers (known as GRXs – GPRS Roaming Exchanges) and direct + +inter-PLMN connections (e.g. private wire); it is however *not* connected to the Internet. More details can be found in GSMA PRD IR.34 [57]. + +Within this inter-PLMN IP backbone network, the domain name ".gprs" was originally conceived as the only domain name to be used to enable DNS servers to translate logical names for network nodes to IP addresses (and vice versa). However, after feedback from the Internet Engineering Task Force (IETF) it was identified that use of this domain name has the following drawbacks: + +1. Leakage of DNS requests for the ".gprs" top level domain into the public Internet is inevitable at sometime or other, especially as the number of services (and therefore number of nodes) using the inter-PLMN IP backbone increases. In the worst case scenario of faulty clients, the performance of the Internet's root DNS servers would be seriously degraded by having to process requests for a top level domain that does not exist. +2. It would be very difficult for network operators to detect if/when DNS requests for the ".gprs" domain were leaked to the public Internet (and therefore the security policies of the inter-PLMN IP backbone network were breached), because the Internet's root DNS servers would simply return an error message to the sender of the request only. + +To address the above, the IETF recommended using a domain name that is *routable* in the public domain but which requests to it are not actually *serviced* in the public domain. The domain name ".3gppnetwork.org" was chosen as the new top level domain name to be used (as far as possible) within the inter-PLMN IP backbone network. + +Originally, only the DNS servers connected to the inter-PLMN IP backbone network were populated with the correct information needed to service requests for *all* sub-domains of this domain. However, it was later identified that some new services needed their allocated sub-domain(s) to be resolvable by the UE and not just inter-PLMN IP network nodes. To address this, additional, higher-level sub-domains were created: + +- "pub.3gppnetwork.org", which is to be used for domain names that need to be resolvable by UEs (and possibly network nodes too) that are connected to a local area network that is connected to the Internet; and +- "ipxuni.3gppnetwork.org", which is to be used for domain names for UNI interfaces that need to be resolvable by UEs that are connected to a local area network that is not connected to the Internet (e.g. local area networks connected to the inter-PLMN IP network of the IPX). + +Therefore, DNS requests for the above domain names can be resolved, while requests for all other sub-domains of "3gppnetwork.org" can simply be configured to return the usual DNS error for unknown hosts (thereby avoiding potential extra, redundant load on the Internet's root DNS servers). + +The GSM Association is in charge of allocating new sub-domains of the ".3gppnetwork.org" domain name. The procedure for requesting new sub-domains can be found in Annex E. + +## Annex E (normative): Procedure for sub-domain allocation + +When a 3GPP member company identifies the need for a new sub-domain name of ".3gppnetwork.org", that 3GPP member company shall propose a CR to this specification at the earliest available meeting of the responsible working group for this TS. The CR shall propose a new sub-domain name. The new sub-domain proposed shall be formatted in one of the formats as described in the following table. + +| Sub-domain Format | Intended Usage | +|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| .mnc.mcc.3gppnetwork.org
(see notes 1 and 2) | Domain name that is to be resolvable by network nodes only. This format inherently adds protection to the identified node, in that attempted DNS resolutions instigated directly from end user equipment will fail indefinitely. | +| .mnc.mcc.pub.3gppnetwork.org
(see notes 1 and 2) | Domain name that is to be resolvable by UEs and/or network nodes. This format inherently adds global resolution capability, but at the expense of confidentiality of network topology. | +| .mnc.mcc.ipxuni.3gppnetwork.org
(see notes 1 and 2) | Domain name for UNI interface that is to be resolvable by UEs that are connected to an inter-PLMN IP network that has no connectivity to the Internet.
This format inherently adds resolution capability for UEs in closed IP networks e.g. IPX. | + +**Table E.1: Sub-domain formats for the "3gppnetwork.org" domain and their respective intended usage** + +NOTE 1: "" is a chosen label, conformant to DNS naming conventions (usually IETF RFC 1035 [19] and IETF RFC 1123 [20]) that clearly and succinctly describe the service and/or operation that is intended to use this sub-domain. + +NOTE 2: "" and "" are the MNC (padded to the left with a zero, if only a 2-digit MNC) and MCC of a PLMN. + +Care should be taken when choosing which format a domain name should use. Once a format has been chosen, the responsible working group shall then check the CR and either endorse it or reject it. If the CR is endorsed, then the responsible working group shall send an LS to the GSMA IREG describing the following key points: + +- the context +- the service +- intended use +- involved actors +- proposed new sub-domain name + +GSMA IREG will then verify the consistence of the proposal and its usage within the domain's structure and interworking rules (e.g. access to the GRX Root DNS servers). GSMA IREG will then endorse or reject the proposal and inform the responsible working group (in 3GPP). It is possible that GSMA IREG will also specify, changes to the newly proposed sub-domain name (e.g. due to requested sub-domain name already allocated). + +It should be noted that services already defined to use the ".gprs" domain name will continue to do so and shall not use the new domain name of ".3gppnetwork.org"; this is to avoid destabilising services that are already live. + +--- + +## Annex F (informative): Change history + +| Change history | | | | | | | +|----------------|-----------|---------|-------|---------|-------------|------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| Apr 1999 | GSM 03.03 | 7.0.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.003 | | | | 3.0.0 | Approved at CN#03 | +| CN#04 | 23.003 | 3.0.0 | 001 | R99 | 3.1.0 | Definition of escape PLMN code | +| CN#04 | 23.003 | 3.0.0 | 002r1 | R99 | 3.1.0 | SSN reallocation for CAP, gsmSCF, SIWF, GGSN, SGSN, | +| CN#04 | 23.003 | 3.0.0 | 003 | R99 | 3.1.0 | Correction of VGC/VBC reference | +| CN#04 | 23.003 | 3.0.0 | 004 | R99 | 3.1.0 | Harmonisation of the MNC-length; correction of CR A019r1 | +| CN#04 | 23.003 | 3.0.0 | 005 | R99 | 3.1.0 | Correction to the MNC length | +| CN#05 | 23.003 | 3.1.3 | 007r1 | R99 | 3.2.0 | ASCII coding of and in APN OI | +| CN#05 | 23.003 | 3.1.3 | 008 | R99 | 3.2.0 | New SSN allocation for RANAP and RNSAP | +| CN#06 | 23.003 | 3.2.1 | 011 | R99 | 3.3.0 | Support of VLR and HLR Data Restoration procedures with LCS | +| CN#07 | 23.003 | 3.3.0 | 014 | R99 | 3.4.0 | Necessity of the function of the calculation of an SGSN IP address from the target ID | +| CN#07 | 23.003 | 3.3.0 | 016 | R99 | 3.4.0 | Definition of Service Area Identification | +| CN#07 | 23.003 | 3.3.0 | 017r2 | R99 | 3.4.0 | Modification of clause 6.2 to enhance IMEI security | +| CN#07 | 23.003 | 3.3.0 | 018 | R99 | 3.4.0 | Coding of a deleted P-TMSI signature | +| CN#07 | 23.003 | 3.4.0 | 013r2 | R99 | 3.4.1 | Introduction of Reserved Service Labels in the APN | +| CN#08 | 23.003 | 3.4.1 | 019 | R99 | 3.5.0 | Missing UTRAN identifiers | +| CN#08 | 23.003 | 3.4.1 | 021r1 | R99 | 3.5.0 | Editorial Modification of clause 6.2.2. | +| CN#08 | 23.003 | 3.4.1 | 022 | R99 | 3.5.0 | IMEI Formats and Encoding | +| CN#09 | 23.003 | 3.5.0 | 023 | R99 | 3.6.0 | Alignment of 23.003 with text from 25.401 | +| CN#10 | 23.003 | 3.6.0 | 024 | R99 | 3.7.0 | Moving informative Annex A from 3G TS 29.060 and making it normative. | +| CN#11 | 23.003 | 3.7.0 | 025 | R99 | 3.8.0 | Clarification to Definition of Service Area Identifier | +| CN#11 | 23.003 | 3.7.0 | 026 | R99 | 3.8.0 | Forbidden APN network identifier labels | +| CN#11 | 23.003 | 3.8.0 | | Rel-4 | 4.0.0 | Updated from R99 to Rel-4 after CN#11 | +| CN#12 | 23.003 | 4.0.0 | 028r1 | Rel-4 | 4.1.0 | Remove reference to TS23.022 | +| CN#12 | 23.003 | 4.1.0 | 029r1 | Rel-5 | 5.0.0 | New Subsystem Number for the Position Calculation Application Part on the Iupc interface | +| CN#13 | 23.003 | 5.0.0 | 032 | Rel-5 | 5.1.0 | Clarification on APN labels that begin with a digit | +| CN#13 | 23.003 | 5.0.0 | | Rel-5 | 5.1.0 | Editorial clean up | +| CN#14 | 23.003 | 5.1.0 | 033 | Rel-5 | 5.2.0 | Rules for TMSI partitioning | +| CN#14 | 23.003 | 5.1.0 | 035 | Rel-5 | 5.2.0 | Introduction of Global CN-ID definition | +| CN#16 | 23.003 | 5.2.0 | 037r1 | Rel-5 | 5.3.0 | IuFlex support for determining old SGSN during handover/relocation | +| CN#16 | 23.003 | 5.2.0 | 038 | Rel-5 | 5.3.0 | Allocation of unique prefixes to IPv6 terminals | +| CN#16 | 23.003 | 5.2.0 | 041r2 | Rel-5 | 5.3.0 | Use of a temporary public user identity | +| CN#16 | 23.003 | 5.2.0 | 044 | Rel-5 | 5.3.0 | Restructuring the IMEI to combine the TAC and FAC | +| CN#16 | 23.003 | 5.2.0 | 045 | Rel-5 | 5.3.0 | Use of the TLLI codespace in GERAN Iu mode | +| CN#17 | 23.003 | 5.3.0 | 048r3 | Rel-5 | 5.4.0 | Clarification on the definition of DNS | +| CN#17 | 23.003 | 5.3.0 | 050r1 | Rel-5 | 5.4.0 | Support for Shared Network in connected mode: definition of SNA | +| CN#17 | 23.003 | 5.3.0 | 053r1 | Rel-5 | 5.4.0 | Restructuring the IMEI to combine the TAC and FAC in Annex B | +| CN#17 | 23.003 | 5.3.0 | 054 | Rel-5 | 5.4.0 | SCCP sub-system Number for IM-SSF | +| CN#18 | 23.003 | 5.4.0 | 055r1 | Rel-5 | 5.5.0 | Iur-g Introduction | +| CN#18 | 23.003 | 5.4.0 | 056r2 | Rel-5 | 5.5.0 | Editorial clean-up | +| CN#18 | 23.003 | 5.4.0 | 057 | Rel-5 | 5.5.0 | Correction of the private user identity's form | +| CN#18 | 23.003 | 5.4.0 | 058 | Rel-5 | 5.5.0 | Addition of a reference to the ITU-T RECOMMENDATION E.212 for Mobile Country Codes | +| CN#18 | 23.003 | 5.4.0 | 059 | Rel-5 | 5.5.0 | Correction to the form of public user identity | +| CN#18 | 23.003 | 5.4.0 | 062 | Rel-5 | 5.5.0 | Fix miss-interworking for LMSI handling (LMSI definition) | +| CN#18 | 23.003 | 5.5.0 | | Rel-5 | 5.5.1 | Corrupted figures 13 – 18 fixed | +| CN#20 | 23.003 | 5.5.1 | 065 | Rel-5 | 5.6.0 | Correction to Annex C.3 – Target ID | +| CN#21 | 23.003 | 5.6.0 | 072 | Rel-5 | 5.7.0 | Correction to definition of Group-ID, Group call area ID and Group Call Reference | +| CN#21 | 23.003 | 5.7.0 | 073r2 | Rel-6 | 6.0.0 | PSI definition | + +| Change history | | | | | | | +|----------------|--------|---------|------------------------------------------|---------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| CN#22 | 23.003 | 6.0.0 | 078 | Rel-6 | 6.1.0 | On the length of the APN NI | +| CN#23 | 23.003 | 6.1.0 | 081 | Rel-6 | 6.2.0 | Changes and corrections to DNS names | +| CN#23 | 23.003 | 6.1.0 | 083r2 | Rel-6 | 6.2.0 | Changes to enable the GSMA root DNS architecture using ".3gppnetwork.org" TLD | +| CN#23 | 23.003 | 6.1.0 | 085r1 | Rel-6 | 6.2.0 | WLAN access parameters moved from TS 24.234 to TS 23.003 | +| CN#23 | 23.003 | 6.1.0 | 087 | Rel-6 | 6.2.0 | Assignment of SSN for Presence Network Agent | +| CN#24 | 23.003 | 6.2.0 | 086r4 | Rel-6 | 6.3.0 | Clarification of the uses of SIP URIs for Public User ID | +| CN#24 | 23.003 | 6.2.0 | 088r1 | Rel-6 | 6.3.0 | Addition of TMGI | +| CN#25 | 23.003 | 6.3.0 | 089 | Rel-6 | 6.4.0 | Background of and procedures for the ".3gppnetwork.org" domain name | +| CN#25 | 23.003 | 6.3.0 | 090r2 | Rel-6 | 6.4.0 | Decorated NAI format | +| CN#25 | 23.003 | 6.3.0 | 091r1 | Rel-6 | 6.4.0 | Introduction of temporary identities | +| CN#26 | 23.003 | 6.4.0 | 092r2 | Rel-6 | 6.5.0 | 'otherrealm' format of Decorated NAI | +| CN#26 | 23.003 | 6.4.0 | 095r1 | Rel-6 | 6.5.0 | Clarification of NRI position within (P)-TMSI | +| CN#26 | 23.003 | 6.4.0 | 096r1 | Rel-6 | 6.5.0 | BSF address | +| CN#27 | 23.003 | 6.5.0 | 097 | Rel-6 | 6.6.0 | Clarification of the TMGI | +| CN#27 | 23.003 | 6.5.0 | 093r3 | Rel-6 | 6.6.0 | Definition of Alternative NAI | +| CT#28 | 23.003 | 6.6.0 | 0099r4 | Rel-6 | 6.7.0 | W-APN Definition | +| CT#28 | 23.003 | 6.6.0 | 0100r5 | Rel-6 | 6.7.0 | Correction to wildcards in PSI | +| | | 6.7.0 | | Rel-6 | 6.7.1 | 2005-07: Correct line break before clause 14 header | +| CT#29 | 23.003 | 6.7.1 | 0102r2 | Rel-6 | 6.8.0 | Corrections to "3gppnetwork.org" addressing | +| CT#29 | 23.003 | 6.7.1 | 0103 | Rel-6 | 6.8.0 | Addition of addressing for the Generic Access Network | +| CT#29 | 23.003 | 6.7.1 | 0104r1 | Rel-6 | 6.8.0 | PSI routing | +| CT#31 | 23.003 | 6.8.0 | 0106r1 | Rel-6 | 6.9.0 | IETF references update | +| CT#32 | 23.003 | 6.9.0 | 0107r1 | Rel-6 | 6.10.0 | Fast re-authentication identity clarification | +| CT#32 | 23.003 | 6.9.0 | 0109r1
0111r1 | Rel-6 | 6.10.0 | Case insensitive naming convention
Correction to the W-APN definition | +| CT#32 | 23.003 | 6.10.0 | 0112r1 | Rel-7 | 7.0.0 | Definition of Anonymous URI in IMS | +| CT#33 | 23.003 | 7.0.0 | 0117r1
0115r3 | Rel-7 | 7.1.0 | Re-authentication identity definition correction
Definition of MBMS SAI | +| CT#34 | 23.003 | 7.1.0 | 0118
0119r2
0120
0121
0122r2 | Rel-7 | 7.2.0 | Voice Call Continuity Identification and Addressing
Unavailable User Identity
Emergency Realm for I-WLAN network advertisement
Definition of emergency W-APN
Format of emergency public identity | +| CT#35 | 23.003 | 7.2.0 | 0128r2
0126r2
0129r2 | Rel-7 | 7.3.0 | Definition of Private Service identity
Definition of emergency APN for IMS em-calls
Clarification to TMGI definition | +| CT#36 | 23.003 | 7.3.0 | 0131r2 | Rel-7 | 7.4.0 | Correction of derivation of identifiers, by the UE, using the IMSI | +| CT#37 | 23.003 | 7.4.0 | 0134r1
0135r2
0136 | Rel-7 | 7.5.0 | Home realm construction for MBMS roaming
PSI clarification
Remove emergency APN | +| CT#38 | 23.003 | 7.5.0 | 0138 | Rel-7 | 7.6.0 | Correction to text describing W-APN format | +| CT#39 | 23.003 | 7.6.0 | 0141r1 | Rel-7 | 7.7.0 | Structure of TMGI | +| CT#39 | 23.003 | 7.7.0 | 0140 | Rel-8 | 8.0.0 | Wildcarded Public User Identities format | +| CT#40 | 23.003 | 8.0.0 | 0142r2
0144
0146r2
0143r2 | Rel-8 | 8.1.0 | IMS public and private identity derivation in 3GPP2
Minor corrections to the IMS section
NAI for 3GPP access to Non-3GPP Access Interworking
Addition of IMS Centralized Services related identities | +| CT#41 | 23.003 | 8.1.0 | 0150
0152r3
0153r1 | Rel-8 | 8.2.0 | Emergency Public User Identity Removal
Introduction of IMC in support of common IMS
Introduction of STN-SR | + +| Change history | | | | | | | +|-----------------------|-------------|----------------|-----------|----------------------|--------------------|---------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | <Phase> | New Version | Subject/Comment | +| | | | 0154r1 | | | Addition and correction of DNS related identifiers for EPC | +| | | | 0155r1 | | | Definition of Globally Unique Temporary UE Identity | +| | | | 0156 | | | Reference correction | +| | | | 0158r1 | | | Addition of Conference Factory URI for IMS Centralized Services | +| | | | 0159r1 | | | Naming for HA discovery HA-APN | +| | | | 0160r2 | | | Definition and format of access network identifier | +| CT#42 | 23.003 | 8.2.0 | 0161 | | 8.3.0 | SGSN related FQDNs | +| | | | 0162 | | | New "nodes" subdomain for EPC | +| | | | 0165 | | | Clarify the mapping between M-TMSI and P-TMSI | +| | | | 0166 | | | Revising the GUTI Definition | +| | | | 0163r4 | | | Closed Subscriber Group | +| | | | 0167r1 | | | Adding the S-TMSI Definition | +| | | | 0168r1 | | | Definition of instance Id | +| | | | 0169 | | | STN-SR in SGSN | +| CT#43 | 23.003 | 8.3.0 | 0170 | Rel-8 | 8.4.0 | Correction to NAI format | +| | | | 0172 | | | Missing service identifiers for DNS procedures | +| | | | 0174 | | | Correction of the GUTI format | +| | | | 0176r1 | | | Correction of the GUTI P-TMSI mapping | +| | | | 0177 | | | Corrections to Service Continuity addressing | +| | | | 0178r1 | | | Support of EAP-AKA' | +| | | | 0179r2 | | | Naming for ANDSF discovery | +| | | | 0180r1 | | | ePDG naming | +| | | | 0181r2 | | | Clarification about canonical form of IMS Public User Identity when format is TEL URL | +| | | | 0182 | | | Temporary Identity Tag Values for Fast Re-authentication Ids | +| | | | 0187r2 | | | DNS-APN-OI | +| CT#44 | 23.003 | 8.4.0 | 0189r1 | Rel-8 | 8.5.0 | HNB Name Definition | +| | | | 0190r1 | | | Clarification on TAI FQDN | +| | | | 0191 | | | Service Parameters for S2c | +| | | | 0193r2 | | | Reference update for draft-montemurro-gsma-imei-urn | +| CT#45 | 23.003 | 8.5.0 | 0194r1 | Rel-8 | 8.6.0 | Public User Identity definition in TS 23.003 | +| | | | 0197r1 | | | Inclusion of CSG Type | +| CT#45 | 23.003 | 8.6.0 | 0199r1 | Rel-9 | 9.0.0 | IMEI Based NAI definitions for emergency services | +| CT#46 | 23.003 | 9.0.0 | 0200r1 | Rel-9 | 9.1.0 | IMEI based NAI | +| | | | 0205r4 | | | IMEI Based NAI | +| | | | 0210r1 | | | Reintroducing Emergency APN definition for IMS based Emergency Call | +| | | | 0212r1 | | | Clarification for the format of ANDSF-SN in roaming scenario | +| | | | 0215 | | | Tracking Area Code | +| | | | 0217 | | | E-UTRAN Cell Global Identification definition | +| CT#47 | 23.003 | 9.1.0 | 0213r4 | Rel-9 | 9.2.0 | Defining H(e)NB identity | +| | | | 0219r2 | | | Exclude prepended digit from the NAI in PMIPv6 | +| | | | 0221r2 | | | APN-FQDN construction | +| | | | 0223 | | | Corrections to APN structure | +| | | | 0225r1 | | | Correction on Home Network Realm/Domain | +| | | | 0227 | | | Corrections to IMS Public Identity | +| CT#48 | 23.003 | 9.2.0 | 0229r1 | Rel-9 | 9.3.0 | Removal of the redundancy reference to 23.401 | +| | | | 0232r1 | | | IMEI and IMEISV | +| | | | 0235r1 | | | Remove ambiguities and improved definition of HNB Unique Identity | +| | | | 0237r2 | | | Essential corrections to GUTI mapping | +| CT#49 | 23.003 | 9.3.0 | 0242r1 | Rel-9 | 9.4.0 | PSI use for services hosted in an AS | +| | | | 0246r3 | | | Essential corrections to GUTI mapping | +| | | | 0247r2 | | | Use of NRI | +| | | | 0256 | | | Format of the Unavailable User Identity | + +| Change history | | | | | | | +|-----------------------|-------------|----------------|-----------|----------------------|--------------------|----------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | <Phase> | New Version | Subject/Comment | +| | | | 0257 | | | Clarification of UE behaviour with regards to LAC format | +| CT#50 | 23.003 | 9.4.0 | 0252r2 | Rel-9 | 9.5.0 | Correction of C-MSISDN definition | +| | | | 0265 | | | Updating IMEI URN draft reference | +| | | | 0268r1 | | | Determination of type of source node during TAU/RAU | +| CT#50 | 23.003 | 9.5.0 | 0258r3 | Rel-10 | 10.0.0 | eNodeB-ID FQDN for DNS procedures | +| | | | 0269r1 | | | Determination of type of source node during TAU/RAU | +| | | | 0259 | | | Service Parameter on PGW selection for GTP based S2b | +| CT#51 | 23.003 | 10.0.0 | 0274r3 | Rel-10 | 10.1.0 | Relay Node OAM system identification | +| | | | 0279r3 | | | Correction of C-MSISDN definition | +| | | | 0277r1 | | | Determination of type of source node during TAU/RAU | +| | | | 0285 | | | Correction to a reference of an outdated IETF draft to an RFC | +| | | | 0280r2 | | | Correction to the reserved values for Tracking Area Code (TAC) | +| | | | 0286 | | | DNS Service Support For Sv | +| | | | 0289 | | | Clarification of decoding of NRI | +| CT#52 | 23.003 | 10.1.0 | 0290 | Rel-10 | 10.2.0 | Closed Subscriber Group clarification | +| | | | 0293r2 | | | UE moving from E-UTRAN to GERAN | +| | | | 0294r2 | | | XCAP Addressing | +| | | | 0296r1 | | | APN Network Identifier | +| | | | 0299 | | | Updating IMEI URN draft reference | +| CT#53 | 23.003 | 10.2.0 | 0307 | Rel-10 | 10.3.0 | Updating IMEI URN draft reference | +| | | | 0282r4 | | | Format of Public User Identities and SIP/TEL URI | +| | | | 0303r3 | | | Emergency NAI for UICC-less Terminal | +| CT#54 | 23.003 | 10.3.0 | 0316r1 | Rel-10 | 10.4.0 | Definition of Distinct Public User Identity | +| | | | 0309r1 | | | Emergency NAI for UICC-less Terminal | +| CT#54 | 23.003 | 10.4.0 | 0308r2 | Rel-11 | 11.0.0 | APN Operator Identifier for local breakout | +| | | | 0312r2 | | | Definition of STI-rSR | +| CT#55 | 23.003 | 11.0.0 | 0334 | Rel-11 | 11.1.0 | BSF address correction | +| | | | 0322r2 | | | Correction to domain name for XCAP Root URI | +| | | | 0325 | | | Updating IMEI URN draft reference | +| | | | 0317r2 | | | Clarification of GUTI mapping | +| | | | 0318 | | | Service Parameter on PGW selection for GTP based S2a | +| CT#56 | 23.003 | 11.1.0 | 0320r6 | Rel-11 | 11.2.0 | MTC External Identifier | +| | | | 0337r1 | | | New Service Parameters for CS to PS SRVCC | +| | | | 0319r5 | | | Definition of A-MSISDN | +| | | | 0335r2 | | | MME Number for SMS in MME | +| | | | 0311r7 | | | SSN Reallocation for CSS and its Number Definition | +| CT#57 | 23.003 | 11.2.0 | 0338r1 | Rel-11 | 11.3.0 | External Identifier definition | +| | | | 0339r1 | | | PS only subscription w/o MSISDN | +| | | | 0340r1 | | | NCC allocation in a shared network | +| | | | 0342r1 | | | MSB in the GUTI and P-TMSI mapping | +| | | | 0345r2 | | | Clarification to MME FQDN | +| CT#58 | 23.003 | 11.3.0 | 0347 | Rel-11 | 11.4.0 | Clarification on the use of APN Operator Identifier | +| | | | 0348r1 | | | PS only subscription without MSISDN | +| | | | 0352r1 | | | Updating IMEI URN draft reference | +| CT#59 | 23.003 | 11.4.0 | 0346r5 | Rel-11 | 11.5.0 | MME FQDN Clarification | +| CT#61 | 23.003 | 11.5.0 | 0358 | Rel-11 | 11.6.0 | Updating IMEI URN draft reference | +| | | | 0361r1 | | | MBMS SAI Definition Correction for LTE Access | +| | | | 0363r2 | | | NRI and MMEC coordination | +| CT#62 | 23.003 | 11.6.0 | 0369 | Rel-11 | 11.7.0 | Updating IMEI URN draft reference | +| CT#63 | 23.003 | 11.7.0 | 0378 | Rel-11 | 11.8.0 | Updating IMEI URN draft reference | +| CT#65 | 23.003 | 11.8.0 | 0390 | Rel-11 | 11.9.0 | Updating IMEI URN draft reference to RFC 7254 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23014/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23014/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..272564609753f73a9780a03c7817030bb85c3240 --- /dev/null +++ b/marked/Rel-11/23_series/23014/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6138a7f2f4e3f21f889c24b42c39418783003e9c428dff4eb3f39102b92d602e +size 103983 diff --git a/marked/Rel-11/23_series/23014/c9d8a18a6137ad054b841d7a614afb48_img.jpg b/marked/Rel-11/23_series/23014/c9d8a18a6137ad054b841d7a614afb48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..967bb05a7a33d12f625e912564c7974cedd5f7c3 --- /dev/null +++ b/marked/Rel-11/23_series/23014/c9d8a18a6137ad054b841d7a614afb48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4ffa30bd6daf2160da37856ce1f3d549f5676ff4236f70d63024a34adc6d7b2 +size 53683 diff --git a/marked/Rel-11/23_series/23014/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-11/23_series/23014/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93d70f369f14c83aa8ea592b70b9fe40d8150186 --- /dev/null +++ b/marked/Rel-11/23_series/23014/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4e83121467ba9cd8bac32192e80b3961cd76a1fb7a91f117f0752c8e3b03ef0 +size 53622 diff --git a/marked/Rel-11/23_series/23014/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-11/23_series/23014/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dfb2bef7e90130a0231a9d0fff01f385194e707 --- /dev/null +++ b/marked/Rel-11/23_series/23014/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a2b85abe8f31f8d6be2b75854469aa53924b0846e273bf7069a37b0eb21faaf +size 148278 diff --git a/marked/Rel-11/23_series/23014/raw.md b/marked/Rel-11/23_series/23014/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..697b23cb1506d13bd2c4db3ad4eafca63ba4d223 --- /dev/null +++ b/marked/Rel-11/23_series/23014/raw.md @@ -0,0 +1,351 @@ + + + + + + +# --- Contents + +| | | +|--------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Abbreviations ..... | 5 | +| 4 Requirement..... | 5 | +| 5 Cause of DTMF generation..... | 6 | +| 6 Support of DTMF across the air interface ..... | 6 | +| 6.1 General ..... | 6 | +| 6.2 Specific..... | 6 | +| 6.3 Tone durations..... | 7 | +| 7 Effect of Handover..... | 10 | +| 7.1 Internal Handover..... | 10 | +| 7.2 External Handover..... | 11 | +| Annex A (informative): Change history..... | 12 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document defines Dual Tone Multi Frequency (DTMF) signalling 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 this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the specification; + +# --- 1 Scope + +The present document describes how Dual Tone Multi Frequency (DTMF) signals are supported in the 3GPP system. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] Void. +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 45.002: "Multiplexing and Multiple Access on the Radio Path". +- [3] ETSI ES 201 235-1, v1.1.1: "Specification of Dual Tone Multi-Frequency (DTMF); Transmitters and Receivers; Part 1: General". +- [4] ETSI ES 201 235-2, v1.2.1: "Specification of Dual Tone Multi-Frequency (DTMF); Transmitters and Receivers; Part 2: Transmitters". +- [5] ETSI ES 201 235-3, v1.2.1: "Specification of Dual Tone Multi-Frequency (DTMF); Transmitters and Receivers; Part 3: Receivers". +- [6] ITU-T Recommendation H.245: "Control protocol for multimedia communication" + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations used in the present document are listed in 3GPP TR 21.905 [1a]. + +# --- 4 Requirement + +Dual Tone Multi Frequency (DTMF) is an inband one out of four plus one out of four signalling system, primarily used from terminal instruments in telecommunication networks. The international recommendations which apply are ETSI ES 201 235 [3, 4, 5] as detailed in subclauses 6.2 and 6.3. For PCS 1900 for North America the Standards which apply are operator specific. + +In the 3GPP system the MSC must support DTMF in the mobile to land direction. + +The support of this facility in the land to mobile direction is for further study. + +The use of DTMF is only permitted: + +- when the speech teleservice is being used or during the speech phase of alternate speech/data and alternate speech/facsimile teleservices; the DTMF is transmitted across the radio interface as specified in subclause 6 of this specification; and +- during a multimedia call; the DTMF is transmitted across the radio interface using the H.245 UserInputIndication message (see ITU-T H.245 [6]). This is transparent for the MSC. + +The responsibility for checking this lies in the MS. + +# --- 5 Cause of DTMF generation + +A user may cause a DTMF tone to be generated by depression of a key in the Mobile Station (MS). Optionally (on a MS basis) manufacturers of mobile equipment may choose to allow DTMF to be controlled from a remote terminal. + +The man-machine interface questions associated with this facility are not discussed further in the present document. + +# --- 6 Support of DTMF across the air interface + +## 6.1 General + +A message based signalling system is used across the 3GPP system air interface. + +This requires that the relevant user action (e.g. a key depression) is interpreted by the MS as a requirement for a DTMF digit to be sent, this is converted by the MS into a message, the message is transmitted across the air interface, and is converted by the MSC into a DTMF tone which is applied towards the network, which should then respond with an acknowledgement. When the user completes the key depression, an message that the DTMF sending should cease is also passed to the MSC, which again will respond with an acknowledgement. + +## 6.2 Specific + +The messages to be sent across the air interface will use the frame stealing mode of transmission. + +The messages when sent across the air interface should contain the following information: + +- a) START DTMF: Containing the digit value (0-9,A,B,C,D,\*,#); +- b) START DTMF ACKNOWLEDGE: Containing the digit value (0-9,A,B,C,D,\*,#) corresponding to the DTMF tone that the network applies towards the remote user; +- c) STOP DTMF: No further info; +- d) STOP DTMF ACKNOWLEDGE: No further info. + +Only a single digit will be passed in each START DTMF and START DTMF ACKNOWLEDGE message. + +The messages will be passed transparently through the base station and interpreted at the MSC. + +On receipt of a START DTMF message, the MSC will connect the correct dual-tone to line. This tone will remain connected until either the call is cleared or a STOP DTMF message is received. + +As an operator option, the tone may be ceased after a pre-determined time whether or not a STOP DTMF message has been received. + +The tones that are to be generated by the MSC are specified as follows: + +- Frequencies are defined in ETSI ES 201 235-1 [3] (for PCS 1900 for North America this is operator specific); +- Tone sending levels are defined in ETSI ES 201 235-2 [4] (for PCS 1900 for North America this is operator specific); +- Durations as specified below. + +## 6.3 Tone durations + +The network shall ensure that the minimum length of tone and the minimum gap between two subsequent tones according to ETSI ES 201 235-2 [4] is achieved. For PCS 1900 for North America this is operator specific. + +NOTE 1: In ETSI ES 201 235-2 [4] the minimum duration of a DTMF tone is 65 ms. + +NOTE 2: In ETSI ES 201 235-2 [4] the minimum gap between DTMF tones is 65 ms. + +There is no defined maximum length to the tone, which will normally cease when a STOP DTMF message is received from the MS. However, the operator may choose to put a pre-defined time limit on the duration of tones sent to line as mentioned in clause 6.2. + +Figures 1 to 3 show an overview of how the DTMF should operate. + +![Sequence diagram of a single DTMF transmission between MMI, MS, BSS, and MSC. The diagram shows the flow of START DTMF and STOP DTMF messages, and the corresponding tone generation in the MSC over time.](c9d8a18a6137ad054b841d7a614afb48_img.jpg) + +The diagram illustrates the interaction for a single DTMF transmission. It features four lifelines: MMI, MS, BSS, and MSC. + +1. **Key X depressed**: An arrow from MMI to MS. + +2. **START DTMF (X)**: An arrow from MS to BSS. + +3. **START DTMF (X)**: An arrow from BSS to MSC. + +4. **Tone X ON**: A vertical line on the MSC lifeline, starting at time **Ta**. + +5. **START DTMF ACKNOWLEDGE (X)**: An arrow from MSC to BSS. + +6. **START DTMF ACKNOWLEDGE (X)**: An arrow from BSS to MS. + +7. **ACKNOWLEDGE**: An arrow from MS to MMI. + +8. **Key X Released**: An arrow from MMI to MS. + +9. **STOP DTMF**: An arrow from MS to BSS. + +10. **STOP DTMF**: An arrow from BSS to MSC. + +11. **Tone OFF**: A vertical line on the MSC lifeline, starting at time **Tp**. + +12. **STOP DTMF ACKNOWLEDGE**: An arrow from MSC to BSS. + +13. **STOP DTMF ACKNOWLEDGE**: An arrow from BSS to MS. + +14. **ACKNOWLEDGE**: An arrow from MS to MMI. + +A shaded area on the MSC lifeline between **Ta** and **Tp** represents the duration of 'Tone X ON'. + +Sequence diagram of a single DTMF transmission between MMI, MS, BSS, and MSC. The diagram shows the flow of START DTMF and STOP DTMF messages, and the corresponding tone generation in the MSC over time. + +Ta Association time for DTMF Generator in MSC, implementation dependent but low. + +Tp Pre-determined maximum tone length, operator option. + +T1 Minimum length of tone. + +NOTE: If the Network operator implements the time limit option (see subclause 6.2), then the tone ends if the timer expires before the 'Stop DTMF' is received. + +**Figure 1: Single DTMF Transmission** + +![Sequence diagram for Single DTMF Transmission, Short Key Press showing interactions between MMI, MS, BSS, and MSC.](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` + +sequenceDiagram + participant MMI + participant MS + participant BSS + participant MSC + + Note over MMI: key X depressed + MMI->>MS: + MS->>BSS: START DTMF (X) + BSS->>MSC: START DTMF (X) + Note over MSC: Ta + Note right of MSC: Tone X ON + Note over MMI: key X released + MMI->>MS: + MSC->>BSS: START DTMF ACKNOWLEDGE (X) + BSS->>MS: START DTMF ACKNOWLEDGE (X) + MS->>MMI: ACKNOWLEDGE + Note right of MSC: / / / Tp / / / + MS->>BSS: STOP DTMF + BSS->>MSC: STOP DTMF + Note right of MSC: Tone OFF + MSC->>BSS: STOP DTMF ACKNOWLEDGE + BSS->>MS: STOP DTMF ACKNOWLEDGE + MS->>MMI: ACKNOWLEDGE + +``` + +Sequence diagram for Single DTMF Transmission, Short Key Press showing interactions between MMI, MS, BSS, and MSC. + +Ta Association time for DTMF Generator in MSC, implementation dependent but low. +Tp Pre-determined maximum tone length, operator option. +T1 Minimum length of tone. + +**Figure 2: Single DTMF Transmission, Short Key Press** + +![Sequence diagram showing two single DTMF transmissions between MMI, MS, BSS, and MSC. The diagram illustrates the message flow for DTMF digits X and Y, including key depression/release, START DTMF, STOP DTMF, and ACKNOWLEDGE messages, as well as the resulting tones (Tone X ON, Tone Y ON) and timing parameters (Ta, Tp).](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant MMI + participant MS + participant BSS + participant MSC + + Note right of MSC: Ta + MMI->>MS: key X depressed + MS->>BSS: START DTMF (X) + BSS->>MSC: START DTMF (X) + Note right of MSC: Ta + MMI->>MS: key X released + MMI->>MS: key Y depressed + MMI->>MS: key Y released + BSS->>MSC: START DTMF ACKNOWLEDGE (X) + MSC->>MS: Tone X ON + Note right of MSC: Tp + Note right of MSC: Tone OFF + MS->>BSS: STOP DTMF + BSS->>MSC: STOP DTMF + BSS->>MSC: STOP DTMF ACKNOWLEDGE + MS->>BSS: STOP DTMF ACKNOWLEDGE + MS->>MMI: ACKNOWLEDGE + Note right of MSC: Ta + MS->>BSS: START DTMF (Y) + BSS->>MSC: START DTMF (Y) + BSS->>MSC: START DTMF ACKNOWLEDGE (Y) + MSC->>MS: Tone Y ON + Note right of MSC: Tp + Note right of MSC: Tone OFF + MS->>BSS: STOP DTMF + BSS->>MSC: STOP DTMF + BSS->>MSC: STOP DTMF ACKNOWLEDGE + MS->>BSS: STOP DTMF ACKNOWLEDGE + MS->>MMI: ACKNOWLEDGE + +``` + +Sequence diagram showing two single DTMF transmissions between MMI, MS, BSS, and MSC. The diagram illustrates the message flow for DTMF digits X and Y, including key depression/release, START DTMF, STOP DTMF, and ACKNOWLEDGE messages, as well as the resulting tones (Tone X ON, Tone Y ON) and timing parameters (Ta, Tp). + +Ta Association time for DTMF Generation in MSC, implementation dependant but low. + Tp Pre-determined maximum tone length, operator option. + T2 Minimum gap between tones. + +**Figure 3: Two Single DTMF Transmission** + +![Sequence diagram showing two single DTMF transmissions with a short gap between key presses. The diagram involves four entities: MMI, MS, BSS, and MSC. The first transmission consists of key X depressed, key X released, key Y depressed, and key Y released. The second transmission consists of key Y depressed and key Y released. The diagram shows the flow of START DTMF, STOP DTMF, and ACKNOWLEDGE messages between the entities, and the internal processing of tones T1 and T2 within the MSC.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +sequenceDiagram + participant MMI + participant MS + participant BSS + participant MSC + + Note left of MMI: key X depressed + MMI->>MS: START DTMF (X) + Note left of MMI: key X released + MS->>BSS: START DTMF (X) + BSS->>MSC: START DTMF (X) + Note right of MSC: Tone X ON Start T1 + Note left of MMI: key Y depressed + Note left of MMI: key Y released + MS->>BSS: START DTMF ACKNOWLEDGE (X) + BSS->>MS: START DTMF ACKNOWLEDGE (X) + MS->>MMI: ACKNOWLEDGE + Note right of MSC: T1 still running, buffer STOP DTMF message. + Note right of MSC: T1 expires, process buffered message. Tone X OFF Start T2 + MS->>BSS: STOP DTMF + BSS->>MSC: STOP DTMF + Note right of MSC: T2 still running, buffer START DTMF (Y) message + Note left of MMI: key Y depressed + Note left of MMI: key Y released + MS->>BSS: STOP DTMF ACKNOWLEDGE + BSS->>MS: STOP DTMF ACKNOWLEDGE + MS->>MMI: ACKNOWLEDGE + Note right of MSC: T2 expires, process buffered message. Tone Y ON Start T1 + Note right of MSC: T1 still running, buffer STOP DTMF message. + Note right of MSC: T1 expires, process buffered message. Tone OFF + MS->>BSS: START DTMF ACKNOWLEDGE (Y) + BSS->>MS: START DTMF ACKNOWLEDGE (Y) + MS->>MMI: ACKNOWLEDGE + MS->>BSS: STOP DTMF + BSS->>MSC: STOP DTMF + MS->>BSS: STOP DTMF ACKNOWLEDGE + BSS->>MS: STOP DTMF ACKNOWLEDGE + MS->>MMI: ACKNOWLEDGE + +``` + +Sequence diagram showing two single DTMF transmissions with a short gap between key presses. The diagram involves four entities: MMI, MS, BSS, and MSC. The first transmission consists of key X depressed, key X released, key Y depressed, and key Y released. The second transmission consists of key Y depressed and key Y released. The diagram shows the flow of START DTMF, STOP DTMF, and ACKNOWLEDGE messages between the entities, and the internal processing of tones T1 and T2 within the MSC. + +T1 Minimum length of tones +T2 Minimum gap between tones. + +Figure 4: Two Single DTMF Transmissions, Short Gap Between Key Presses + +# 7 Effect of Handover + +## 7.1 Internal Handover + +There is unlikely to be any impact on DTMF due to internal handover. + +## 7.2 External Handover + +Depending on the exact moment when handover occurs, there may be a slight possibility of cutting short a DTMF tone. + +For protocol reasons, in the case of an MSC receiving a STOP DTMF message when no tone is being sent, it should respond with an acknowledgement as usual. + +No other impact is seen due to external handover. + +# Annex A (informative): Change history + +| Change history | | | | | | | +|--------------------|-------------------------------------------------------------------|---------|-------|---------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| Apr 1999 | 3GPP TS 03.14 | 7.0.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.014 | | | | 3.0.0 | Approved at CN#03 | +| CN#06 | 23.014 | 3.0.0 | 001r1 | R99 | 3.1.0 | Clarification of DTMF procedure | +| CN#11 | 23.014 | 3.1.0 | | Rel-4 | 4.0.0 | TSG CN#11 decided to issue this specification as Release 4 on 03-2001 | +| NP-16 | 23.014 | 4.0.0 | | Rel-5 | 5.0.0 | TSG CN#16 decided to issue this specification as part of release 5 on June 2002.
ETSI/MCC updated this version with references and editorials. | +| NP-17
NP-020365 | 23.014
N1-021655 (wrongly used N1-021654 inside the CR itself) | 5.0.0 | 006 | Rel-5 | 5.1.0 | Dual Tone Multi-Frequency signalling : Support in the whole 3GPP system, and editorial modifications.

Cat A CR | +| NP-26 | 23.014 | 5.1.0 | 007 | Rel-6 | 6.0.0 | Introduction of new references for DTMF | +| | | 6.0.0 | | | 7.0.0 | Upgraded to Rel-7 (MCC) | +| CP-42 | 23.014 | 7.0.0 | 008r1 | Rel-8 | 8.0.0 | DTMF transmission during multimedia call | +| CP-46 | | 8.0.0 | | Rel-9 | 9.0.0 | Upgraded to Rel-9 (MCC) | +| CP-51 | | 9.0.0 | | Rel-10 | 10.0.0 | Upgraded to Rel-10 (MCC) | +| CP-57 | | 10.0.0 | | Rel-11 | 11.0.0 | Upgraded to Rel-11 (MCC) | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23032/0a90113d6c8989e8b3c89c5cf9f926d7_img.jpg b/marked/Rel-11/23_series/23032/0a90113d6c8989e8b3c89c5cf9f926d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd4241ee49bd327809567f1cfdba4ec38086c16a --- /dev/null +++ b/marked/Rel-11/23_series/23032/0a90113d6c8989e8b3c89c5cf9f926d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb2d52cb03e6c7ab54c66c3502e1e0649089365c45ec5e81143d57a54f02a81c +size 21626 diff --git a/marked/Rel-11/23_series/23032/303fadfb9def251d1575d6221199b158_img.jpg b/marked/Rel-11/23_series/23032/303fadfb9def251d1575d6221199b158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa57edc6acfe091f1a2de092dd2e38c4fecc1ba1 --- /dev/null +++ b/marked/Rel-11/23_series/23032/303fadfb9def251d1575d6221199b158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:397b419ee3abf317d61574d64cca391c680366677b8d6355497bc5fe0a443aac +size 42715 diff --git a/marked/Rel-11/23_series/23032/61ce9760bffbecba8f5e63310be1ebec_img.jpg b/marked/Rel-11/23_series/23032/61ce9760bffbecba8f5e63310be1ebec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5b889bc26c75bdf8a37603a522378b01c930558 --- /dev/null +++ b/marked/Rel-11/23_series/23032/61ce9760bffbecba8f5e63310be1ebec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11389a2943647ad08ccf1250852f5966066a373340ff850d59601ae2cfe8dead +size 21477 diff --git a/marked/Rel-11/23_series/23032/671360bcdb148eb5e8007b64fe1cb424_img.jpg b/marked/Rel-11/23_series/23032/671360bcdb148eb5e8007b64fe1cb424_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86ea1aab8f0a99294d5509fe00d969f2dee53b4c --- /dev/null +++ b/marked/Rel-11/23_series/23032/671360bcdb148eb5e8007b64fe1cb424_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6a0a631e7ec7f07eaea07d55da58f2ec22a1a3af1b7ff8ee936e26154a211f5 +size 28372 diff --git a/marked/Rel-11/23_series/23032/6786ba12e3eceb3cf496108a02a37f09_img.jpg b/marked/Rel-11/23_series/23032/6786ba12e3eceb3cf496108a02a37f09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5885071d079168ad5ee4360b755feccbec4a2e2 --- /dev/null +++ b/marked/Rel-11/23_series/23032/6786ba12e3eceb3cf496108a02a37f09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e70c39eb654e8d4a5e2c6265b0a322e3556731d7c114c9cee05892432453a00 +size 15813 diff --git a/marked/Rel-11/23_series/23032/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Rel-11/23_series/23032/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b8d36596eb5f3178c5b299d8becd3c17830a9bf --- /dev/null +++ b/marked/Rel-11/23_series/23032/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4273b461d86bc3e2bd329e136f5a8d6865ba1bd97af68f0ea8fe8df50689f9e6 +size 45616 diff --git a/marked/Rel-11/23_series/23032/89986656b45c3b6896256f1a22f7c186_img.jpg b/marked/Rel-11/23_series/23032/89986656b45c3b6896256f1a22f7c186_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b111bb008534e213a0d37587809bd2fea0627d80 --- /dev/null +++ b/marked/Rel-11/23_series/23032/89986656b45c3b6896256f1a22f7c186_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f64c964ecd0982f4affd8071696e154590fc3949ff148963943ca8927299d7e +size 6967 diff --git a/marked/Rel-11/23_series/23032/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-11/23_series/23032/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11ab170e1aab1b19b6bf23970d464a595b72de46 --- /dev/null +++ b/marked/Rel-11/23_series/23032/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:566a68ca12468ccd97360df523d73043c039237879cc44d294651ac5026d10ff +size 28450 diff --git a/marked/Rel-11/23_series/23032/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg b/marked/Rel-11/23_series/23032/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71d9558d44c9bddf9be5f1dae3fea1d6746f62a5 --- /dev/null +++ b/marked/Rel-11/23_series/23032/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:780fb1bd784d61e808692a323e3f4e43250420ef71e3219b72e147024566526b +size 21554 diff --git a/marked/Rel-11/23_series/23032/a86610f7a0e579fec9f34dea52fa088b_img.jpg b/marked/Rel-11/23_series/23032/a86610f7a0e579fec9f34dea52fa088b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cdbd0379b8cbb0d97e9b8be26e2e06a98745a43 --- /dev/null +++ b/marked/Rel-11/23_series/23032/a86610f7a0e579fec9f34dea52fa088b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ed5f04bec33fb4dd280154d9af2b126cfa418433e9c9ff9fbd04bfa4c521855 +size 17957 diff --git a/marked/Rel-11/23_series/23032/b25cc68846b070bbe56a949b011ba91c_img.jpg b/marked/Rel-11/23_series/23032/b25cc68846b070bbe56a949b011ba91c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee2073917ea1a73131ac19395b043bd418ce46bd --- /dev/null +++ b/marked/Rel-11/23_series/23032/b25cc68846b070bbe56a949b011ba91c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45f01fe307b950cc9e99298faf1f812a41ef9ac127ddb9e0a207b0c1c44742e2 +size 15812 diff --git a/marked/Rel-11/23_series/23032/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/Rel-11/23_series/23032/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4aeab50a5798d6c80f0642d1e41f3a4d0de647d5 --- /dev/null +++ b/marked/Rel-11/23_series/23032/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3b6632e62332b9f64effce54a11cbbdcf87ad5b3b833b088433bdc74ee5aa57 +size 35746 diff --git a/marked/Rel-11/23_series/23032/d29cfbf30a471dc06a78be27f86bd1cf_img.jpg b/marked/Rel-11/23_series/23032/d29cfbf30a471dc06a78be27f86bd1cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad94727af5abd3fe9ee45e77a9461e8ba336aa0c --- /dev/null +++ b/marked/Rel-11/23_series/23032/d29cfbf30a471dc06a78be27f86bd1cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00a2a78a819d96cd62c1019ca65048601bddd99825399992a88e77722dc7ef89 +size 16821 diff --git a/marked/Rel-11/23_series/23032/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/23_series/23032/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaa6af97edf199ef7bcfbce04edfc1e565143f0d --- /dev/null +++ b/marked/Rel-11/23_series/23032/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:407d96385cfcb2d4ba5560a0a5dce1dd4e7f4bb01537b3de4936c892b9b5e8e4 +size 17050 diff --git a/marked/Rel-11/23_series/23032/efca2dce0095c9dc2a68e9af6b2bfd40_img.jpg b/marked/Rel-11/23_series/23032/efca2dce0095c9dc2a68e9af6b2bfd40_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9dacf6fe2dfd2f11570f36e7b583588f5eb57e9 --- /dev/null +++ b/marked/Rel-11/23_series/23032/efca2dce0095c9dc2a68e9af6b2bfd40_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed97dc494333c55966498020b97fb34ba0951ef4dfbfdfd9f34372d662d3a8c9 +size 47587 diff --git a/marked/Rel-11/23_series/23032/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Rel-11/23_series/23032/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd5d94056ff12f38123053d3e8067176c0c637b4 --- /dev/null +++ b/marked/Rel-11/23_series/23032/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a96941dc08c0d102de72b236b9bcb27d2f9046cb7a5af1ef6097ab13b1d5d3d4 +size 18420 diff --git a/marked/Rel-11/23_series/23032/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg b/marked/Rel-11/23_series/23032/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e4406faca3a42d73d9c905eaab1e04f398cbc47 --- /dev/null +++ b/marked/Rel-11/23_series/23032/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d20d9dcc8b84d53da839af4eca8bd6c414d4847dc8b2f23629efaec11b14df7d +size 14182 diff --git a/marked/Rel-11/23_series/23032/raw.md b/marked/Rel-11/23_series/23032/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..48763f4e4d61ce26d7a8df7870442e09796bd778 --- /dev/null +++ b/marked/Rel-11/23_series/23032/raw.md @@ -0,0 +1,889 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Reference system ..... | 7 | +| 5 Shapes ..... | 7 | +| 5.1 Ellipsoid Point..... | 7 | +| 5.2 Ellipsoid point with uncertainty circle ..... | 8 | +| 5.3 Ellipsoid point with uncertainty ellipse..... | 8 | +| 5.4 Polygon..... | 9 | +| 5.5 Ellipsoid Point with Altitude..... | 10 | +| 5.6 Ellipsoid point with altitude and uncertainty ellipsoid..... | 10 | +| 5.7 Ellipsoid Arc ..... | 11 | +| 6 Coding..... | 11 | +| 6.1 Point ..... | 11 | +| 6.2 Uncertainty..... | 12 | +| 6.3 Altitude..... | 12 | +| 6.4 Uncertainty Altitude..... | 13 | +| 6.5 Confidence ..... | 13 | +| 6.6 Radius..... | 13 | +| 6.7 Angle..... | 13 | +| 7 General message format and information elements coding..... | 14 | +| 7.1 Overview ..... | 14 | +| 7.2 Type of Shape..... | 14 | +| 7.3 Shape description ..... | 15 | +| 7.3.1 Ellipsoid Point ..... | 15 | +| 7.3.2 Ellipsoid Point with uncertainty Circle ..... | 16 | +| 7.3.3 Ellipsoid Point with uncertainty Ellipse..... | 17 | +| 7.3.4 Polygon..... | 18 | +| 7.3.5 Ellipsoid Point with Altitude ..... | 19 | +| 7.3.6 Ellipsoid Point with altitude and uncertainty ellipsoid..... | 20 | +| 7.3.7 Ellipsoid Arc..... | 21 | +| 8 Description of Velocity ..... | 21 | +| 8.1 Horizontal Velocity ..... | 21 | +| 8.2 Horizontal and Vertical Velocity ..... | 22 | +| 8.3 Horizontal Velocity with Uncertainty..... | 22 | +| 8.4 Horizontal and Vertical Velocity with Uncertainty ..... | 22 | +| 8.5 Coding Principles..... | 22 | +| 8.6 Coding of Velocity Type..... | 23 | +| 8.7 Coding of Horizontal Speed..... | 23 | +| 8.8 Coding of Bearing ..... | 23 | +| 8.9 Coding of Vertical Speed..... | 23 | +| 8.10 Coding of Vertical Speed Direction..... | 24 | +| 8.11 Coding of Uncertainty Speed..... | 24 | +| 8.12 Coding of Horizontal Velocity..... | 24 | +| 8.13 Coding of Horizontal with Vertical Velocity..... | 24 | +| 8.14 Coding of Horizontal Velocity with Uncertainty ..... | 25 | +| 8.15 Coding of Horizontal with Vertical Velocity and Uncertainty ..... | 25 | + +**Annex A (informative):**   **Element description in compact notation.....27** + +Annex B (informative):   Change history.....29 + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document defines an intermediate universal Geographical Area Description 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 an intermediate universal Geographical Area Description which subscriber applications, GSM or UMTS services can use and the network can convert into an equivalent radio coverage map. + +For GSM or UMTS services which involve the use of an "area", it can be assumed that in the majority of cases the Service Requester will be forbidden access to data on the radio coverage map of a particular PLMN and that the Service Requester will not have direct access to network entities (e.g. BSC/BTS or RNC/Node B). + +The interpretation by the PLMN operator of the geographical area in terms of cells actually used, cells that are partly within the given area and all other technical and quality of service aspects are out of the scope of the present document. + +This specification also provides a description of velocity that may be associated with a universal Geographical Area Description when both are applied to a common entity at a common time. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3 General aspects". +- [3] Military Standard WGS84 Metric MIL-STD-2401 (11 January 1994): "Military Standard Department of Defence World Geodetic System (WGS)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following definitions apply. + +**Service Requester:** Entity, which uses the Geographical Area Description in any protocol to inform the network about a defined area. + +**Target:** Entity whose precise geographic position is to be described. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in GSM 01.04 [1] and the following apply. + +| | | +|-----|-------------------------------| +| GAD | Geographical Area Description | +| GPS | Global Positioning System | +| WGS | World Geodetic System | + +# --- 4 Reference system + +The reference system chosen for the coding of locations is the World Geodetic System 1984, (WGS 84), which is also used by the Global Positioning System, (GPS). The origin of the WGS 84 co-ordinate system is the geometric centre of the WGS 84 ellipsoid. The ellipsoid is constructed by the rotation of an ellipse around the minor axis which is oriented in the North-South direction. The rotation axis is the polar axis of the ellipsoid, and the plane orthogonal to it and including the centre of symmetry is the equatorial plane. + +The relevant dimensions are as follows: + +Major Axis (a) = 6378137 m + +Minor Axis (b) = 6356752,314 m + +First eccentricity of the ellipsoid + +Co-ordinates are then expressed in terms of longitude and latitude relevant to this ellipsoid. The range of longitude is -180° to +180°, and the range of latitude is -90° to +90°. 0° longitude corresponds to the Greenwich Meridian, and positive angles are to the East, while negative angles are to the West. 0° latitude corresponds to the equator, and positive angles are to the North, while negative angles are to the South. Altitudes are defined as the distance between the ellipsoid and the point, along a line orthogonal to the ellipsoid. + +# --- 5 Shapes + +The intention is to incorporate a number of different shapes, that can be chosen according to need. + +- Ellipsoid Point; +- Ellipsoid point with uncertainty circle; +- Ellipsoid point with uncertainty ellipse; +- Polygon; +- Ellipsoid point with altitude; +- Ellipsoid point with altitude and uncertainty ellipsoid; +- Ellipsoid Arc. + +Each shape is discussed individually. + +## 5.1 Ellipsoid Point + +The description of an ellipsoid point is that of a point on the surface of the ellipsoid, and consists of a latitude and a longitude. In practice, such a description can be used to refer to a point on Earth's surface, or close to Earth's surface, with the same longitude and latitude. No provision is made in this version of the standard to give the height of a point. + +Figure 1 illustrates a point on the surface of the ellipsoid and its co-ordinates. + +The latitude is the angle between the equatorial plane and the perpendicular to the plane tangent to the ellipsoid surface at the point. Positive latitudes correspond to the North hemisphere. The longitude is the angle between the half-plane determined by the Greenwich meridian and the half-plane defined by the point and the polar axis, measured Eastward. + +![Figure 1: A 3D diagram of a sphere representing the Earth. It shows a central point from which three axes originate. One axis goes to the north pole, one to the equator on the prime meridian, and one to the equator at a specific longitude. An arc on the surface from the equator up to a point is labeled 'Latitude'. An arc along the equator from the prime meridian to the point's longitude is labeled 'Longitude'.](efca2dce0095c9dc2a68e9af6b2bfd40_img.jpg) + +Figure 1: A 3D diagram of a sphere representing the Earth. It shows a central point from which three axes originate. One axis goes to the north pole, one to the equator on the prime meridian, and one to the equator at a specific longitude. An arc on the surface from the equator up to a point is labeled 'Latitude'. An arc along the equator from the prime meridian to the point's longitude is labeled 'Longitude'. + +**Figure 1: Description of a Point as two co-ordinates** + +## 5.2 Ellipsoid point with uncertainty circle + +The "ellipsoid point with uncertainty circle" is characterised by the co-ordinates of an ellipsoid point (the origin) and a distance $r$ . It describes formally the set of points on the ellipsoid which are at a distance from the origin less than or equal to $r$ , the distance being the geodesic distance over the ellipsoid, i.e., the minimum length of a path staying on the ellipsoid and joining the two points, as shown in figure 2. + +As for the ellipsoid point, this can be used to indicate points on the Earth surface, or near the Earth surface, of same latitude and longitude. + +The typical use of this shape is to indicate a point when its position is known only with a limited accuracy. + +![Figure 2: A 2D diagram of a circle. A crosshair marks the center point. A horizontal arrow points from the center to the right edge of the circle, labeled with the variable 'r' above it, indicating the radius of uncertainty.](89986656b45c3b6896256f1a22f7c186_img.jpg) + +Figure 2: A 2D diagram of a circle. A crosshair marks the center point. A horizontal arrow points from the center to the right edge of the circle, labeled with the variable 'r' above it, indicating the radius of uncertainty. + +**Figure 2: Description of an uncertainty Circle** + +## 5.3 Ellipsoid point with uncertainty ellipse + +The "ellipsoid point with uncertainty ellipse" is characterised by the co-ordinates of an ellipsoid point (the origin), distances $r1$ and $r2$ and an angle of orientation $A$ . It describes formally the set of points on the ellipsoid which fall within or on the boundary of an ellipse with semi-major axis of length $r1$ oriented at angle $A$ (0 to 180°) measure clockwise from north and semi-minor axis of length $r2$ , the distances being the geodesic distance over the ellipsoid, i.e., the minimum length of a path staying on the ellipsoid and joining the two points, as shown in figure 2a. + +As for the ellipsoid point, this can be used to indicate points on the Earth's surface, or near the Earth's surface, of same latitude and longitude. The confidence level with which the position of a target entity is included within this set of points is also included with this shape. + +The typical use of this shape is to indicate a point when its position is known only with a limited accuracy, but the geometrical contributions to uncertainty can be quantified. + +![Figure 2a: Description of an uncertainty Ellipse. The diagram shows an ellipse centered at the origin of a coordinate system. A vertical arrow points upwards from the origin, labeled 'North'. A line segment from the origin to the top-right edge of the ellipse is labeled 'semi-major axis, r1'. A line segment from the origin to the bottom-right edge of the ellipse is labeled 'semi-minor axis, r2'. An arc between the North arrow and the semi-major axis is labeled 'angle, A'.](a86610f7a0e579fec9f34dea52fa088b_img.jpg) + +Figure 2a: Description of an uncertainty Ellipse. The diagram shows an ellipse centered at the origin of a coordinate system. A vertical arrow points upwards from the origin, labeled 'North'. A line segment from the origin to the top-right edge of the ellipse is labeled 'semi-major axis, r1'. A line segment from the origin to the bottom-right edge of the ellipse is labeled 'semi-minor axis, r2'. An arc between the North arrow and the semi-major axis is labeled 'angle, A'. + +**Figure 2a: Description of an uncertainty Ellipse** + +## 5.4 Polygon + +A polygon is an arbitrary shape described by an ordered series of points (in the example pictured in the drawing, A to E). The minimum number of points allowed is 3, and the maximum number of points allowed is 15. The points shall be connected in the order that they are given. A connecting line is defined as the line over the ellipsoid joining the two points and of minimum distance (geodesic). The last point is connected to the first. The list of points shall respect a number of conditions: + +- a connecting line shall not cross another connecting line; +- two successive points must not be diametrically opposed on the ellipsoid. + +The described area is situated to the right of the lines with the downward direction being toward the Earth's centre and the forward direction being from a point to the next. + +NOTE: This definition does not permit connecting lines greater than roughly 20 000 km. If such a need arises, the polygon can be described by adding an intermediate point. + +Computation of geodesic lines is not simple. Approximations leading to a maximum distance between the computed line and the geodesic line of less than 3 metres are acceptable. + +![Figure 3: Description of a Polygon. The diagram shows a polygon with five vertices labeled A, B, C, D, and E. The vertices are connected in the order A-B-C-D-E-A. Vertex A is at the bottom left, B is above it, C is at the top right, D is below C, and E is between A and C. Each vertex is marked with an 'X'.](6786ba12e3eceb3cf496108a02a37f09_img.jpg) + +Figure 3: Description of a Polygon. The diagram shows a polygon with five vertices labeled A, B, C, D, and E. The vertices are connected in the order A-B-C-D-E-A. Vertex A is at the bottom left, B is above it, C is at the top right, D is below C, and E is between A and C. Each vertex is marked with an 'X'. + +**Figure 3: Description of a Polygon** + +## 5.5 Ellipsoid Point with Altitude + +The description of an ellipsoid point with altitude is that of a point at a specified distance above or below a point on the earth's surface. This is defined by an ellipsoid point with the given longitude and latitude and the altitude above or below the ellipsoid point. Figure 3a illustrates the altitude aspect of this description. + +![Figure 3a: Description of an Ellipsoid Point with Altitude. A diagram showing a circle representing the Earth's surface. A horizontal line extends from the center to the right. A point on this line is labeled 'Point with positive altitude'. Another point on the circle's circumference is labeled 'Point with negative altitude'. Arrows indicate the vertical distance (altitude) from the horizontal line to each point.](61ce9760bffbecba8f5e63310be1ebec_img.jpg) + +Figure 3a: Description of an Ellipsoid Point with Altitude. A diagram showing a circle representing the Earth's surface. A horizontal line extends from the center to the right. A point on this line is labeled 'Point with positive altitude'. Another point on the circle's circumference is labeled 'Point with negative altitude'. Arrows indicate the vertical distance (altitude) from the horizontal line to each point. + +**Figure 3a: Description of an Ellipsoid Point with Altitude** + +## 5.6 Ellipsoid point with altitude and uncertainty ellipsoid + +The "ellipsoid point with altitude and uncertainty ellipsoid" is characterised by the co-ordinates of an ellipsoid point with altitude, distances $r_1$ (the "semi-major uncertainty"), $r_2$ (the "semi-minor uncertainty") and $r_3$ (the "vertical uncertainty") and an angle of orientation $A$ (the "angle of the major axis"). It describes formally the set of points which fall within or on the surface of a general (three dimensional) ellipsoid centred on an ellipsoid point with altitude whose real semi-major, semi-mean and semi-minor axis are some permutation of $r_1$ , $r_2$ , $r_3$ with $r_1 \geq r_2$ . The $r_3$ axis is aligned vertically, while the $r_1$ axis, which is the semi-major axis of the ellipse in a horizontal plane that bisects the ellipsoid, is oriented at an angle $A$ (0 to 180 degrees) measured clockwise from north, as illustrated in Figure 3b. + +![Figure 3b: Description of an Ellipsoid Point with Altitude and Uncertainty Ellipsoid. A diagram showing a three-dimensional ellipsoid. A vertical axis is labeled 'vertical'. The semi-major axis is labeled 'r1', the semi-minor axis is labeled 'r2', and the vertical axis is labeled 'r3'. An angle 'A' is shown between the vertical axis and the semi-major axis. A point on the ellipsoid is labeled 'ellipsoid point with altitude'. A North arrow 'N' is also shown.](0a90113d6c8989e8b3c89c5cf9f926d7_img.jpg) + +Figure 3b: Description of an Ellipsoid Point with Altitude and Uncertainty Ellipsoid. A diagram showing a three-dimensional ellipsoid. A vertical axis is labeled 'vertical'. The semi-major axis is labeled 'r1', the semi-minor axis is labeled 'r2', and the vertical axis is labeled 'r3'. An angle 'A' is shown between the vertical axis and the semi-major axis. A point on the ellipsoid is labeled 'ellipsoid point with altitude'. A North arrow 'N' is also shown. + +**Figure 3b: Description of an Ellipsoid Point with Altitude and Uncertainty Ellipsoid** + +The typical use of this shape is to indicate a point when its horizontal position and altitude are known only with a limited accuracy, but the geometrical contributions to uncertainty can be quantified. The confidence level with which the position of a target entity is included within the shape is also included. + +## 5.7 Ellipsoid Arc + +An ellipsoid arc is a shape characterised by the co-ordinates of an ellipsoid point $o$ (the origin), inner radius $r_1$ , uncertainty radius $r_2$ , both radii being geodesic distances over the surface of the ellipsoid, the offset angle ( $\theta$ ) between the first defining radius of the ellipsoid arc and North, and the included angle ( $\beta$ ) being the angle between the first and second defining radii. The offset angle is within the range of $0^\circ$ to $359,999...^\circ$ while the included angle is within the range from $0,000...1^\circ$ to $360^\circ$ . This is to be able to describe a full circle, $0^\circ$ to $360^\circ$ . + +This shape-definition can also be used to describe a sector (inner radius equal to zero), a circle (included angle equal to 360°) and other circular shaped areas. The confidence level with which the position of a target entity is included within the shape is also included. + +![Figure 3c: Description of an Ellipsoid Arc. The diagram shows a blue arc segment of an ellipsoid. A vertical arrow points upwards from a central point labeled 'Point (o)' to the word 'North'. A line segment labeled 'r1' extends from 'Point (o)' to the inner edge of the arc. Another line segment labeled 'r2' extends from 'Point (o)' to the outer edge of the arc. The angle between the vertical 'North' line and the 'r1' line is labeled 'θ'. The angle between the 'r1' and 'r2' lines is labeled 'β'.](d29cfbf30a471dc06a78be27f86bd1cf_img.jpg) + +Figure 3c: Description of an Ellipsoid Arc. The diagram shows a blue arc segment of an ellipsoid. A vertical arrow points upwards from a central point labeled 'Point (o)' to the word 'North'. A line segment labeled 'r1' extends from 'Point (o)' to the inner edge of the arc. Another line segment labeled 'r2' extends from 'Point (o)' to the outer edge of the arc. The angle between the vertical 'North' line and the 'r1' line is labeled 'θ'. The angle between the 'r1' and 'r2' lines is labeled 'β'. + +**Figure 3c: Description of an Ellipsoid Arc** + +# 6 Coding + +## 6.1 Point + +The co-ordinates of an ellipsoid point are coded with an uncertainty of less than 3 metres. + +The latitude is coded with 24 bits: 1 bit of sign and a number between 0 and $2^{23}-1$ coded in binary on 23 bits. The relation between the coded number N and the range of (absolute) latitudes X it encodes is the following (X in degrees): + +$$N \leq \frac{2^{23}}{90} X < N + 1$$ + +except for $N=2^{23}-1$ , for which the range is extended to include $N+1$ . + +The longitude, expressed in the range $-180^\circ$ , $+180^\circ$ , is coded as a number between $-2^{23}$ and $2^{23}-1$ , coded in 2's complement binary on 24 bits. The relation between the coded number N and the range of longitude X it encodes is the following (X in degrees): + +$$N \leq \frac{2^{24}}{360} X < N + 1$$ + +## 6.2 Uncertainty + +A method of describing the uncertainty for latitude and longitude has been sought which is both flexible (can cover wide differences in range) and efficient. The proposed solution makes use of a variation on the Binomial expansion. The uncertainty $r$ , expressed in metres, is mapped to a number K, with the following formula: + +$$r = C((1 + x)^K - 1)$$ + +with $C = 10$ and $x = 0,1$ . With $0 \leq K \leq 127$ , a suitably useful range between 0 and 1800 kilometres is achieved for the uncertainty, while still being able to code down to values as small as 1 metre. The uncertainty can then be coded on 7 bits, as the binary encoding of K. + +**Table 1: Example values for the uncertainty Function** + +| Value of K | Value of uncertainty | +|-------------------|-----------------------------| +| 0 | 0 m | +| 1 | 1 m | +| 2 | 2,1 m | +| - | - | +| 20 | 57,3 m | +| - | - | +| 40 | 443 m | +| - | - | +| 60 | 3 km | +| - | - | +| 80 | 20 km | +| - | - | +| 100 | 138 km | +| - | - | +| 120 | 927 km | +| - | - | +| 127 | 1800 km | + +## 6.3 Altitude + +Altitude is encoded in increments of 1 meter using a 15 bit binary coded number N. The relation between the number N and the range of altitudes *a* (in metres) it encodes is described by the following equation: + +$$N \leq a < N + 1$$ + +except for $N=2^{15}-1$ for which the range is extended to include all greater values of *a*. + +The direction of altitude is encoded by a single bit with bit value 0 representing height above the WGS84 ellipsoid surface and bit value 1 representing depth below the WGS84 ellipsoid surface. + +## 6.4 Uncertainty Altitude + +The uncertainty in altitude, *h*, expressed in metres is mapped from the binary number K, with the following formula: + +$$h = C((1+x)^K - 1)$$ + +with $C = 45$ and $x = 0,025$ . With $0 \leq K \leq 127$ , a suitably useful range between 0 and 990 meters is achieved for the uncertainty altitude. The uncertainty can then be coded on 7 bits, as the binary encoding of K. + +**Table 2: Example values for the uncertainty altitude Function** + +| Value of K | Value of uncertainty altitude | +|------------|-------------------------------| +| 0 | 0 m | +| 1 | 1,13 m | +| 2 | 2,28 m | +| - | - | +| 20 | 28,7 m | +| - | - | +| 40 | 75,8 m | +| - | - | +| 60 | 153,0 m | +| - | - | +| 80 | 279,4 m | +| - | - | +| 100 | 486,6 m | +| - | - | +| 120 | 826,1 m | +| - | - | +| 127 | 990,5 m | + +## 6.5 Confidence + +The confidence by which the position of a target entity is known to be within the shape description, (expressed as a percentage) is directly mapped from the 7 bit binary number K, except for K=0 which is used to indicate 'no information', and $100 < K \leq 128$ which should not be used but may be interpreted as "no information" if received. + +## 6.6 Radius + +Inner radius is encoded in increments of 5 meters using a 16 bit binary coded number N. The relation between the number N and the range of radius $r$ (in metres) it encodes is described by the following equation: + +$$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$ . This provides a true maximum radius of 327,675 meters. + +The uncertainty radius is encoded as for the uncertainty latitude and longitude. + +## 6.7 Angle + +Offset and Included angle are encoded in increments of $2^\circ$ using an 8 bit binary coded number N in the range 0 to 179. The relation between the number N and the range offset ( $ao$ ) and included ( $ai$ ) of angles (in degrees) it encodes is described by the following equations: + +Offset angle ( $ao$ ) + +$2 N \leq ao < 2 (N+1)$ Accepted values for $ao$ are within the range from 0 to 359,9...9 degrees. + +Included angle ( $ai$ ) + +$2 N < ai \leq 2 (N+1)$ Accepted values for $ai$ are within the range from 0,0...1 to 360 degrees. + +# --- 7 General message format and information elements coding + +This clause describes a coding method for geographical area descriptions. A geographical area description is coded as a finite bit string. In the figures, the bit string is described by octets from top downward, and in the octet from left to right. Number encoding strings start with the most significant bit. + +## 7.1 Overview + +A bit string encoding a geographical description shall consist of the following parts: + +- Type of Shape; +- Shape Description. + +Such a bit string is usually part of an information element. The structure of the information element (e.g., element identifier, length) depends on the protocol in which the message containing the description is defined, and is specified in the protocol specification. + +This organisation is illustrated in the example shown in figure 4. + +![Figure 4: Example diagram showing the structure of a bit string. It is a table with 8 columns (bits 8 to 1) and 3 rows. The first row (Octet 1) contains 'Type of shape' in bits 8-5 and is empty in bits 4-1. The second row (Octet 2) contains 'Shape description' across all bits 8-1. Subsequent rows are labeled 'Etc...'.](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +| | | | | | | | | | +|-------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Type of shape | | | | | | | | Octet 1 | +| Shape description | | | | | | | | Octet 2 | +| | | | | | | | | Etc... | + +Figure 4: Example diagram showing the structure of a bit string. It is a table with 8 columns (bits 8 to 1) and 3 rows. The first row (Octet 1) contains 'Type of shape' in bits 8-5 and is empty in bits 4-1. The second row (Octet 2) contains 'Shape description' across all bits 8-1. Subsequent rows are labeled 'Etc...'. + +Figure 4: Example + +## 7.2 Type of Shape + +The Type of Shape information field identifies the type which is being coded in the Shape Description. The Type of Shape is coded as shown in table 2a. + +Table 2a: Coding of Type of Shape + +| Bits | | +|--------------|---------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | Ellipsoid Point | +| 0 0 0 1 | Ellipsoid point with uncertainty Circle | +| 0 0 1 1 | Ellipsoid point with uncertainty Ellipse | +| 0 1 0 1 | Polygon | +| 1 0 0 0 | Ellipsoid point with altitude | +| 1 0 0 1 | Ellipsoid point with altitude and uncertainty Ellipsoid | +| 1 0 1 0 | Ellipsoid Arc | +| other values | reserved for future use | + +## 7.3 Shape description + +The shape description consist of different elements. + +### 7.3.1 Ellipsoid Point + +The coding of a point is described in figure 5. + +![Diagram of the shape description of a point showing 8 octets. Octet 1 contains bits 8-5 as '0' and bits 4-1 as 'spare'. Octet 2 starts with 'S' (Sign of latitude) in bit 8. Octets 3-4 contain 'Degrees of latitude'. Octets 5-6 contain 'Degrees of longitude'. Octet 7 is empty.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +|----------------------|---|---|---|-------|---|---|---|---------|---------| +| 0 | 0 | 0 | 0 | spare | | | | Octet 1 | | +| S | | | | | | | | | Octet 2 | +| Degrees of latitude | | | | | | | | Octet 3 | | +| | | | | | | | | Octet 4 | | +| | | | | | | | | Octet 5 | | +| Degrees of longitude | | | | | | | | Octet 6 | | +| | | | | | | | | Octet 7 | | + +Diagram of the shape description of a point showing 8 octets. Octet 1 contains bits 8-5 as '0' and bits 4-1 as 'spare'. Octet 2 starts with 'S' (Sign of latitude) in bit 8. Octets 3-4 contain 'Degrees of latitude'. Octets 5-6 contain 'Degrees of longitude'. Octet 7 is empty. + +Figure 5: Shape description of a point + +S: Sign of latitude + +Bit value 0 North + +Bit value 1 South + +Degrees of latitude + +Bit 1 of octet 4 is the low order bit + +Degrees of longitude + +Bit 1 of octet 7 is the low order bit + +### 7.3.2 Ellipsoid Point with uncertainty Circle + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | +|-------|------------------|----------------------|---|-------|---|---|---|---------|--|--|--|--|--|--|--|--|--|--| +| 0 | 0 | 0 | 1 | spare | | | | Octet 1 | | | | | | | | | | | +| S | | | | | | | | Octet 2 | | | | | | | | | | | +| | | Degrees of latitude | | | | | | Octet 3 | | | | | | | | | | | +| | | | | | | | | Octet 4 | | | | | | | | | | | +| | | | | | | | | Octet 5 | | | | | | | | | | | +| | | Degrees of longitude | | | | | | Octet 6 | | | | | | | | | | | +| | | | | | | | | Octet 7 | | | | | | | | | | | +| 0 | Uncertainty code | | | | | | | Octet 8 | | | | | | | | | | | +| spare | | | | | | | | | | | | | | | | | | | + +Figure 6: Shape description of an ellipsoid point with uncertainty circle + +### 7.3.3 Ellipsoid Point with uncertainty Ellipse + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | +|---------------------------|------------------------|---|---|-------|---|---|---|----------|--|--|--|--|--|--|--|--|--|--|--| +| 0 | 0 | 1 | 1 | spare | | | | Octet 1 | | | | | | | | | | | | +| S | | | | | | | | Octet 2 | | | | | | | | | | | | +| Degrees of latitude | | | | | | | | Octet 3 | | | | | | | | | | | | +| | | | | | | | | Octet 4 | | | | | | | | | | | | +| | | | | | | | | Octet 5 | | | | | | | | | | | | +| Degrees of longitude | | | | | | | | Octet 6 | | | | | | | | | | | | +| | | | | | | | | Octet 7 | | | | | | | | | | | | +| 0
spare | Uncertainty semi-major | | | | | | | Octet 8 | | | | | | | | | | | | +| 0
spare | Uncertainty semi-minor | | | | | | | Octet 9 | | | | | | | | | | | | +| Orientation of major axis | | | | | | | | Octet 10 | | | | | | | | | | | | +| 0
spare | Confidence | | | | | | | Octet 11 | | | | | | | | | | | | + +**Figure 6a: Shape description of an ellipsoid point with uncertainty ellipse** + +Orientation of major axis + +angle in degrees between the major axis and north + +(0 = north, 90 = east, values of 180 and above are not used) + +### 7.3.4 Polygon + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------|---|---|---|------------------|---|---|---|------------| +| 0 | 1 | 0 | 1 | Number of points | | | | Octet 1 | +| S1 | | | | | | | | Octet 2 | +| Degrees of latitude of point 1 | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | +| Degrees of longitude of point 1 | | | | | | | | Octet 5 | +| | | | | | | | | Octet 6 | +| | | | | | | | | Octet 7 | +| | | | | | | | | | +| Sn | | | | | | | | Octet 6n-4 | +| Degrees of latitude of point n | | | | | | | | Octet 6n-3 | +| | | | | | | | | Octet 6n-2 | +| Degrees of longitude of point n | | | | | | | | Octet 6n-1 | +| | | | | | | | | Octet 6n | +| | | | | | | | | Octet 6n+1 | + +**Figure 7: Shape description of a polygon** + +The number of points field encodes in binary on 4 bits the number $n$ of points in the description, and ranges from 3 to 15. + +### 7.3.5 Ellipsoid Point with Altitude + +The coding of an ellipsoid point with altitude is described in figure 8. + +![Diagram showing the bit structure for an ellipsoid point with altitude. It includes a header row with bits 8-1, followed by Octet 1 (bits 1-4: 1000, bits 5-8: spare), Octet 2 (bit 8: S, bits 7-1: Degrees of latitude), Octet 3 (Degrees of latitude), Octet 4 (Degrees of latitude), Octet 5 (Degrees of longitude), Octet 6 (Degrees of longitude), Octet 7 (Degrees of longitude), Octet 8 (bit 8: D, bits 7-1: Altitude), and Octet 9 (Altitude).](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +|----------------------|---------------------|---|---|-------|---|---|---|---------|---------| +| 1 | 0 | 0 | 0 | spare | | | | Octet 1 | | +| S | Degrees of latitude | | | | | | | | Octet 2 | +| Degrees of latitude | | | | | | | | | Octet 3 | +| Degrees of latitude | | | | | | | | | Octet 4 | +| Degrees of longitude | | | | | | | | | Octet 5 | +| Degrees of longitude | | | | | | | | | Octet 6 | +| Degrees of longitude | | | | | | | | | Octet 7 | +| D | Altitude | | | | | | | | Octet 8 | +| Altitude | | | | | | | | | Octet 9 | + +Diagram showing the bit structure for an ellipsoid point with altitude. It includes a header row with bits 8-1, followed by Octet 1 (bits 1-4: 1000, bits 5-8: spare), Octet 2 (bit 8: S, bits 7-1: Degrees of latitude), Octet 3 (Degrees of latitude), Octet 4 (Degrees of latitude), Octet 5 (Degrees of longitude), Octet 6 (Degrees of longitude), Octet 7 (Degrees of longitude), Octet 8 (bit 8: D, bits 7-1: Altitude), and Octet 9 (Altitude). + +**Figure 8: Shape description of an ellipsoid point with altitude** + +D: Direction of Altitude + +Bit value 0 Altitude expresses height + +Bit value 1 Altitude expresses depth + +Altitude + +Bit 1 of octet 9 is the low order bit + +### 7.3.6 Ellipsoid Point with altitude and uncertainty ellipsoid + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | +|------------|------------------------|---------------------------|---|-------|---|---|---|----------|--|--|--|--|--|--|--|--|--|--| +| 1 | 0 | 0 | 1 | spare | | | | Octet 1 | | | | | | | | | | | +| S | | | | | | | | Octet 2 | | | | | | | | | | | +| | | Degrees of latitude | | | | | | Octet 3 | | | | | | | | | | | +| | | | | | | | | Octet 4 | | | | | | | | | | | +| | | | | | | | | Octet 5 | | | | | | | | | | | +| | | Degrees of longitude | | | | | | Octet 6 | | | | | | | | | | | +| | | | | | | | | Octet 7 | | | | | | | | | | | +| D | | | | | | | | Octet 8 | | | | | | | | | | | +| | | Altitude | | | | | | Octet 9 | | | | | | | | | | | +| 0
spare | Uncertainty semi-major | | | | | | | Octet 10 | | | | | | | | | | | +| 0
spare | Uncertainty semi-minor | | | | | | | Octet 11 | | | | | | | | | | | +| | | Orientation of major axis | | | | | | Octet 12 | | | | | | | | | | | +| 0
spare | Uncertainty Altitude | | | | | | | Octet 13 | | | | | | | | | | | +| 0
spare | Confidence | | | | | | | Octet 14 | | | | | | | | | | | + +Figure 9: Shape description of an ellipsoid point with altitude and uncertainty ellipsoid + +### 7.3.7 Ellipsoid Arc + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +|---|--------------------|----------------------|---|-------|---|---|---|----------|----------| +| 1 | 0 | 1 | 0 | Spare | | | | Octet 1 | | +| S | | | | | | | | | Octet 2 | +| | | Degrees of latitude | | | | | | Octet 3 | | +| | | | | | | | | Octet 4 | | +| | | | | | | | | Octet 5 | | +| | | Degrees of longitude | | | | | | Octet 6 | | +| | | | | | | | | Octet 7 | | +| | | Inner radius | | | | | | Octet 8 | | +| | | | | | | | | Octet 9 | | +| 0 | Uncertainty radius | | | | | | | | Octet 10 | +| | | Offset angle | | | | | | Octet 11 | | +| | | Included angle | | | | | | Octet 12 | | +| 0 | Confidence | | | | | | | | Octet 13 | +| | | | | | | | | | | + +**Figure 10: Shape description of an Ellipsoid arc** + +Inner radius + +Bit 8 of octet 8 is the high order bit. + +Bit 1 of octet 9 is the low order bit. + +# 8 Description of Velocity + +A description of velocity is applicable to any target entity on or close to the surface of the WGS84 ellipsoid. + +## 8.1 Horizontal Velocity + +Horizontal velocity is characterised by the horizontal speed and bearing. The horizontal speed gives the magnitude of the horizontal component of the velocity of a target entity. The bearing provides the direction of the horizontal component of velocity taken clockwise from North. + +![Figure 11: Description of Horizontal Velocity with Uncertainty. A diagram showing a vector in a horizontal plane. A vertical arrow points up, labeled 'North'. A vector arrow points diagonally up and to the right. The angle between the North arrow and the vector is labeled 'Bearing'. The length of the vector is labeled 'Magnitude'. The entire diagram is enclosed in a box labeled 'Horizontal Plane' at the bottom.](b25cc68846b070bbe56a949b011ba91c_img.jpg) + +Figure 11: Description of Horizontal Velocity with Uncertainty. A diagram showing a vector in a horizontal plane. A vertical arrow points up, labeled 'North'. A vector arrow points diagonally up and to the right. The angle between the North arrow and the vector is labeled 'Bearing'. The length of the vector is labeled 'Magnitude'. The entire diagram is enclosed in a box labeled 'Horizontal Plane' at the bottom. + +Figure 11: Description of Horizontal Velocity with Uncertainty + +## 8.2 Horizontal and Vertical Velocity + +Horizontal and vertical velocity is characterised by horizontal speed, bearing, vertical speed and direction. The horizontal speed and bearing characterise the horizontal component of velocity. The vertical speed and direction provides the component of velocity of a target entity in a vertical direction. + +## 8.3 Horizontal Velocity with Uncertainty + +Horizontal velocity with uncertainty is characterised by a horizontal speed and bearing, giving a horizontal velocity vector $\underline{V}$ and an uncertainty speed $s$ . It describes the set of velocity vectors $\underline{v}$ related to the given velocity $\underline{V}$ as follows: + +![Figure 12: Description of Horizontal Velocity with Uncertainty. A 2D coordinate system with horizontal axis v_x and vertical axis v_v. A vector V points from the origin into the first quadrant. A vector v also points from the origin into the first quadrant, slightly below V. A dashed circle of radius s is centered at the tip of vector V. The vector v ends within this circle. The distance between the tips of V and v is labeled s.](fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg) + +$$|\underline{v} - \underline{V}| \leq s$$ + +Figure 12: Description of Horizontal Velocity with Uncertainty. A 2D coordinate system with horizontal axis v\_x and vertical axis v\_v. A vector V points from the origin into the first quadrant. A vector v also points from the origin into the first quadrant, slightly below V. A dashed circle of radius s is centered at the tip of vector V. The vector v ends within this circle. The distance between the tips of V and v is labeled s. + +Figure 12: Description of Horizontal Velocity with Uncertainty + +## 8.4 Horizontal and Vertical Velocity with Uncertainty + +Horizontal and vertical velocity with uncertainty is characterised by a horizontal speed and bearing, giving a horizontal velocity vector $\underline{V}_{x,y}$ , a vertical speed and direction giving a vertical velocity component $V_z$ and uncertainty speeds $s_1$ and $s_2$ . It describes the set of velocity vectors $\underline{v}$ with horizontal and vertical components $\underline{v}_{x,y}$ and $v_z$ that are related to the given velocity components $\underline{V}_{x,y}$ and $V_z$ as follows: + +$$|\underline{v}_{x,y} - \underline{V}_{x,y}| \leq s_1$$ + +$$|v_z - V_z| \leq s_2$$ + +## 8.5 Coding Principles + +Velocity is encoded as shown in Figure 13. The velocity type in bits 8-5 of octet 1 defines the type of velocity information in succeeding bits. + +![Figure 13: General Coding of Velocity. A diagram showing the structure of velocity data. At the top, bits 8, 7, 6, 5, 4, 3, 2, and 1 are listed. Below them is a table with two rows. The first row has a cell labeled 'Velocity Type' spanning bits 8, 7, 6, and 5. The second row has a cell labeled 'Velocity Information' spanning bits 4, 3, 2, and 1. To the right of the table, the labels 'Octet 1', 'Octet 2', and 'Etc...' are present, corresponding to the rows.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 13: General Coding of Velocity. A diagram showing the structure of velocity data. At the top, bits 8, 7, 6, 5, 4, 3, 2, and 1 are listed. Below them is a table with two rows. The first row has a cell labeled 'Velocity Type' spanning bits 8, 7, 6, and 5. The second row has a cell labeled 'Velocity Information' spanning bits 4, 3, 2, and 1. To the right of the table, the labels 'Octet 1', 'Octet 2', and 'Etc...' are present, corresponding to the rows. + +Figure 13: General Coding of Velocity + +## 8.6 Coding of Velocity Type + +Table 3 shows the coding of the velocity type. + +Table 3: Coding of Velocity Type + +| Bits | | | +|--------------|---|-----------------------------------------------------| +| 4 | 3 | 2 1 | +| 0 | 0 | 0 0 Horizontal Velocity | +| 0 | 0 | 0 1 Horizontal with Vertical Velocity | +| 0 | 1 | 0 Horizontal Velocity with Uncertainty | +| 0 | 1 | 1 Horizontal with Vertical Velocity and Uncertainty | +| other values | | reserved for future use | + +## 8.7 Coding of Horizontal Speed + +Horizontal speed is encoded in increments of 1 kilometre per hour using a 16 bit binary coded number N. The relation between the number N and the horizontal speed $h$ (in kilometres per hour) it encodes is described by the following equations: + +$$N \leq h < N + 0.5 \quad (N = 0)$$ + +$$N - 0.5 \leq h < N + 0.5 \quad (0 < N < 2^{16}-1)$$ + +$$N - 0.5 \leq h \quad (N = 2^{16}-1)$$ + +## 8.8 Coding of Bearing + +Bearing is encoded in increments of 1 degree measured clockwise from North using a 9 bit binary coded number N. The relation between the number N and the bearing $b$ (in degrees) it encodes is described by the following equation: + +$$N \leq b < N+1$$ + +except for $360 \leq N < 511$ which are not used. + +## 8.9 Coding of Vertical Speed + +Vertical speed is encoded in increments of 1 kilometre per hour using 8 bits giving a number N between 0 and $2^8-1$ . The relation between the number N and the vertical speed $v$ (in kilometres per hour) it encodes is described by the following equations: + +$$N \leq v < N + 0.5 \quad (N = 0)$$ + +$$N - 0.5 \leq v < N + 0.5 \quad (0 < N < 2^8-1)$$ + +$$N - 0.5 \leq v$$ + +$$(N = 2^8-1)$$ + +## 8.10 Coding of Vertical Speed Direction + +Vertical speed direction is encoded using 1 bit: a bit value of 0 indicates upward speed; a bit value of 1 indicates downward speed. + +## 8.11 Coding of Uncertainty Speed + +Uncertainty speed is encoded in increments of 1 kilometre 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. + +## 8.12 Coding of Horizontal Velocity + +The coding of horizontal velocity is described in figure 14. + +![](a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------|---|---|---|-------|---|---|---|---------| +| 0 | 0 | 0 | 0 | spare | | | | Octet 1 | +| Bearing | | | | | | | | Octet 2 | +| Horizontal Speed | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | + +**Figure 14: Coding of Horizontal Velocity** + +Bearing + +Bit 1 of octet 1 is the high order bit; bit 1 of octet 2 is the low order bit + +Horizontal Speed + +Bit 1 of octet 4 is the low order bit + +## 8.13 Coding of Horizontal with Vertical Velocity + +The coding of horizontal with vertical velocity is described in figure 15. + +![](671360bcdb148eb5e8007b64fe1cb424_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------|---|---|---|-------|---|---|---|---------| +| 0 | 0 | 0 | 1 | spare | | D | | Octet 1 | +| Bearing | | | | | | | | Octet 2 | +| Horizontal Speed | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | +| Vertical Speed | | | | | | | | Octet 5 | + +**Figure 15: Coding of Horizontal with Vertical Velocity** + +D: Direction of Vertical Speed + +Bit value 0 Upward + +Bit value 1 Downward + +## 8.14 Coding of Horizontal Velocity with Uncertainty + +The coding of horizontal velocity with uncertainty is described in figure 16. + +![](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------|---|---|---|-------|---|---|---|---------| +| 0 | 0 | 1 | 0 | spare | | | | Octet 1 | +| Bearing | | | | | | | | Octet 2 | +| Horizontal Speed | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | +| Uncertainty Speed | | | | | | | | Octet 5 | + +Figure 16: Coding of Horizontal Velocity with Uncertainty + +## 8.15 Coding of Horizontal with Vertical Velocity and Uncertainty + +The coding of horizontal with vertical velocity and uncertainty is described in figure 17. + +![](303fadfb9def251d1575d6221199b158_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|---|---|---|-------|---|---|---|---------| +| 0 | 0 | 1 | 0 | spare | | D | | Octet 1 | +| Bearing | | | | | | | | Octet 2 | +| Horizontal Speed | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | +| Vertical Speed | | | | | | | | Octet 5 | +| Horizontal Uncertainty Speed | | | | | | | | Octet 6 | +| Vertical Uncertainty Speed | | | | | | | | Octet 7 | + +Figure 17: Coding of Horizontal with Vertical Velocity and Uncertainty + +# Annex A (informative): Element description in compact notation + +The notation is the one described in GSM 04.07 [2]. + +``` + + ::= + | + | + | + | + | + | + ; + + ::= + 0000 (4) + ; + + ::= + + ; + + ::= + 0001 (4) + + ; + + ::= + 0011 (4) + + + + + ; + + ::= + 0101 + (val(Number of points)) ; + + ::= + 0011 | 0100 | 0101 | 0110 | 0111 | 1000 | 1001 | 1010 | + 1011 | 1100 | 1101 | 1110 | 1111 ; + + ::= + 1000 (4) + + ; + + ::= + + + ::= + 1001 (4) + + + + + + +``` + +``` + + ; + + ::= +<1010> spare(4) + + + ; + + + + ; + + ::= + | + | + | + ; + + : ::= +0000 (3) + +; + + : ::= +0001 (2) + + + +; + + : ::= +0010 (3) + + +; + + : ::= +0011 (2) + + + + + +; +``` + +# --- Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|--------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2004-12 | SP-26 | | | | Created version 6.0.0 | 5.0.0 | 6.0.0 | +| 2007-06 | SP-36 | - | - | - | Update to Rel-7 version (MCC) | 6.0.0 | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | Update to Rel-8 version (MCC) | 7.0.0 | 8.0.0 | +| 2009-12 | SP-46 | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | +| 2011-03 | SP-51 | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23034/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/marked/Rel-11/23_series/23034/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28c7e0221c577b7ce08d482fd376331771d5b777 --- /dev/null +++ b/marked/Rel-11/23_series/23034/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0ce4c94a808ee29f38fb38ba1bd88d874fbe1caebdc259180551235fe9439e3 +size 25811 diff --git a/marked/Rel-11/23_series/23034/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Rel-11/23_series/23034/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b27dd2a56efb8256bcde1f36794545bdd0545131 --- /dev/null +++ b/marked/Rel-11/23_series/23034/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6af4e49d81a80b539f2fdd236d611e67bc17bd8267d3f140165fd90a2d096326 +size 68139 diff --git a/marked/Rel-11/23_series/23034/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/23_series/23034/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffd76078a203c4fa378b90c8c0cc78c31ec25812 --- /dev/null +++ b/marked/Rel-11/23_series/23034/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4a950f9db0e9e1678a02fef6f8a5f5fd624ecb55a3c968ec3726c6578597a27 +size 37297 diff --git a/marked/Rel-11/23_series/23034/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-11/23_series/23034/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b4d0e90d9d6dccd5f6f77a146d18ce572166097 --- /dev/null +++ b/marked/Rel-11/23_series/23034/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc5b765ef6ff17430751cf96634c2380b085f610b8b7bb82544b9271cdb561e6 +size 97816 diff --git a/marked/Rel-11/23_series/23034/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/23_series/23034/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..051fce6d8711e3c4166ae1aa843a81b442b4a14e --- /dev/null +++ b/marked/Rel-11/23_series/23034/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49d0c2232a93f949496fadcb1f89d516913fbb0155136d7f974ab6aac0e9449b +size 118322 diff --git a/marked/Rel-11/23_series/23034/5dfc130b129ace4df375839020a5700d_img.jpg b/marked/Rel-11/23_series/23034/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..546624f3d79dae111bc3b22981e2caa18511e3b7 --- /dev/null +++ b/marked/Rel-11/23_series/23034/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e6ff02cb488a72f7c2e5d0d085219c8b0eda96b9259cb0106becfbdea7a037f +size 62665 diff --git a/marked/Rel-11/23_series/23034/78d5774278a3f4a614f8c0ae485ce8d9_img.jpg b/marked/Rel-11/23_series/23034/78d5774278a3f4a614f8c0ae485ce8d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c304e359c5f849dcbfa5be26430a9dd3e7f51cb7 --- /dev/null +++ b/marked/Rel-11/23_series/23034/78d5774278a3f4a614f8c0ae485ce8d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecefb568fb8f54e7e76519bd965268397407e9ca9d0b799ae63132412914ccda +size 29568 diff --git a/marked/Rel-11/23_series/23034/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/23_series/23034/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be1190d9a6956a491304d80de49037a85a03be05 --- /dev/null +++ b/marked/Rel-11/23_series/23034/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddb47f6332a29c18a4dbb3cb1b95169b5695707abeb2d699799a8692392476d9 +size 88572 diff --git a/marked/Rel-11/23_series/23034/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/23_series/23034/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34362ba8f13819b85849b9db549c8d6dcc7d091c --- /dev/null +++ b/marked/Rel-11/23_series/23034/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c5bbe1e0d03873c131c74b0f2491e65e739cdf9cb1994c08329428a55b9fbc3 +size 88434 diff --git a/marked/Rel-11/23_series/23034/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Rel-11/23_series/23034/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..620f8f3ac349f8605c66fd46caad8e8f265249e2 --- /dev/null +++ b/marked/Rel-11/23_series/23034/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f8d6484e0c5873c47f00e933d0f6c1a1db3080a949ea45ae2482363bc48d44e +size 93858 diff --git a/marked/Rel-11/23_series/23034/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-11/23_series/23034/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbcf170786cb27cb62259c55b00a09e8d69cbdb2 --- /dev/null +++ b/marked/Rel-11/23_series/23034/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca2ac6ca2cea305f8acd6f53e4855d8c540a9d43126859d3d7d88fe6ba61bfc4 +size 100949 diff --git a/marked/Rel-11/23_series/23034/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-11/23_series/23034/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f3d3e4ac1d3777dcdab9b09e853f315f670ce2c --- /dev/null +++ b/marked/Rel-11/23_series/23034/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7293910ddfd486365986a8d54a65cbd0b2ae141a24dac4a4508b923feeca52a0 +size 88231 diff --git a/marked/Rel-11/23_series/23034/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/23_series/23034/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c321d908da4caab1c0fb21a3398a2597ab6495f4 --- /dev/null +++ b/marked/Rel-11/23_series/23034/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:636cccea2111ef84b60f367d3987932994933588d19ef23ab39edc5a1f1b3b68 +size 69714 diff --git a/marked/Rel-11/23_series/23034/e2c1c672349c10dccb2563eff6d8260e_img.jpg b/marked/Rel-11/23_series/23034/e2c1c672349c10dccb2563eff6d8260e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad27d22b9a7904c08dc64c10606f87f1488e4d73 --- /dev/null +++ b/marked/Rel-11/23_series/23034/e2c1c672349c10dccb2563eff6d8260e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ef8b799662544402bd2419d5936eee343df4a1e6b9d1d712bcbfc8aba640b29 +size 31082 diff --git a/marked/Rel-11/23_series/23034/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/23_series/23034/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a4e749ac6839208fcbf25134f7d63b9d156b485 --- /dev/null +++ b/marked/Rel-11/23_series/23034/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bfc3dcb5525fad7b47f048a24e355c5ce2d08f84f0d76553d60c90ad8e4dc48 +size 56483 diff --git a/marked/Rel-11/23_series/23034/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Rel-11/23_series/23034/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f741aa94ad1b0cb76f8b93d1bf831cc66c629c53 --- /dev/null +++ b/marked/Rel-11/23_series/23034/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46e119e970721e31c9044f599428e6ec4ef6299a898b56d2ffa4604896ede2c4 +size 83430 diff --git a/marked/Rel-11/23_series/23034/fbfa653853daf5541118a9ddecb92284_img.jpg b/marked/Rel-11/23_series/23034/fbfa653853daf5541118a9ddecb92284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c18b6bbafb027d2b0cc90bf0cb66f360fb528dc5 --- /dev/null +++ b/marked/Rel-11/23_series/23034/fbfa653853daf5541118a9ddecb92284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b31c7155bfe4ab9d181db40d740d1f77db79165b163ef311bf417a867abee22 +size 110775 diff --git a/marked/Rel-11/23_series/23034/raw.md b/marked/Rel-11/23_series/23034/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5c713219917a1d615d15703c3c339aad7eb13301 --- /dev/null +++ b/marked/Rel-11/23_series/23034/raw.md @@ -0,0 +1,1009 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions..... | 6 | +| 4 Main concepts ..... | 7 | +| 4.1 HSCSD service aspects..... | 8 | +| 4.2 HSCSD service aspects in UTRAN Iu mode..... | 9 | +| 4.2.1 UTRAN Iu mode to GERAN Iu mode or A/Gb mode handover ..... | 9 | +| 5 HSCSD architecture and transmission..... | 9 | +| 5.1 Air interface..... | 9 | +| 5.2 Functions and information flows..... | 10 | +| 5.2.1 Call establishment procedures..... | 10 | +| 5.2.1.1 Mobile originated call establishment (A/Gb mode) ..... | 10 | +| 5.2.1.1a Mobile originated call establishment (GERAN Iu mode) ..... | 12 | +| 5.2.1.2 Mobile terminated call establishment (A/Gb mode)..... | 13 | +| 5.2.1.2a Mobile terminated call establishment (GERAN Iu mode) ..... | 14 | +| 5.2.2 Handover procedures..... | 16 | +| 5.2.2.1 Intra BSC handover (A/Gb mode) ..... | 16 | +| 5.2.2.1a Intra BSC handover (GERAN Iu mode)..... | 16 | +| 5.2.2.2 Inter BSC, intra-MSC handover (A/Gb mode)..... | 18 | +| 5.2.2.2a Inter BSC, intra-MSC handover (GERAN Iu mode)..... | 19 | +| 5.2.2.3 Inter MSC handover..... | 20 | +| 5.2.3 Resource upgrading, downgrading and configuration change (A/Gb mode)..... | 20 | +| 5.2.3a Resource upgrading, downgrading and configuration change (GERAN Iu mode)..... | 22 | +| 5.2.4 User initiated service level up- and downgrading (A/Gb mode)..... | 23 | +| 5.2.4a User initiated service level up- and downgrading (GERAN Iu mode)..... | 24 | +| 5.2.5 Link adaptation for ECSD ..... | 25 | +| 5.2.6 Start of ciphering ..... | 25 | +| 5.3 Transparent data transmission..... | 25 | +| 5.3.1 Numbering of data substreams ..... | 25 | +| 5.3.2 Padding ..... | 25 | +| 5.4 Non-Transparent data transmission..... | 25 | +| 5.4.1 HSCSD RLP ..... | 25 | +| 5.5 Interworking ..... | 26 | +| 5.6 Subscription aspects and storage of subscriber data ..... | 26 | +| 6 Charging..... | 26 | +| 6.1 General principles ..... | 26 | +| 6.2 Call forwardings..... | 26 | +| 6.3 AoC and toll ticketing ..... | 26 | +| Annex A (informative): Change history..... | 27 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the Stage 2 description of High Speed Circuit Switched Data (HSCSD) 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 contains the stage 2 service description for a High Speed Circuit Switched Data (HSCSD) on GSM/GERAN in A/Gb mode and Iu mode. HSCSD utilizes the multislot mechanism, i.e. using multiple traffic channels (/bearers) for the communication. + +Additionally, the present document specifies some HSCSD related requirements for multi system mobile stations operating in UTRAN Iu mode. In UTRAN Iu mode one bearer can provide all needed data rates, and the multislot mechanism is therefore not needed. However, for inter-system handover to GERAN, certain information has to be provided by the mobile station during the service negotiation. The UTRAN Iu mode aspects concerning HSCSD are described exclusively in clause 4.2. + +In analogy with ITU-T Recommendation I.130 [6] (refer to annex A) and with reference of ITU-T Recommendation Q.65 [7] VI.1 (Stage 2 of the method for characterization of services supported by an ISDN), the second stage of the HSCSD is defined as follows. + +Stage 2 identifies the functional capabilities and information flows needed to support the service as described in 3GPP TS 22.034 [9]. Furthermore, it identifies various possible physical locations for the functional capabilities. The output of Stage 2, which is signalling system independent, is used as an input to Stage 3, the design of signalling system and switching Recommendations. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void. +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [3] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols - Stage 3". +- [4] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". +- [5] 3GPP TS 24.022: "Radio Link Protocol (RLP) for data and telematic services on the Mobile Station - Base Station System (MS - BSS) interface and the Base Station System - Mobile-services Switching Centre (BSS - MSC)". +- [6] ITU-T Recommendation I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN". +- [7] ITU-T Recommendation Q.65: "The unified functional methodology for the characterization of services and network capabilities". +- [8] ITU-T Recommendation I.460: "Multiplexing, rate adaptation and support of existing interfaces". +- [9] 3GPP TS 22.034: "High Speed Circuit Switched Data (HSCSD); Stage 1". +- [10] 3GPP TS 43.020: "Security related network functions". + +- [11] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) Interface". +- [12] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [13] 3GPP TS 27.002: "Terminal Adaptation Functions (TAF) for services using Asynchronous bearer capabilities". +- [14] 3GPP TS 27.003: "Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities". +- [15] 3GPP TS 45.008: "Radio Subsystem Link Control". +- [16] 3GPP TS 23.008: "Organisation of subscriber data". +- [17] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [18] 3GPP TS 43.051: "GSM/EDGE Radio Access Network; Overall description - Stage 2". +- [19] 3GPP TS 25.413: "UTRAN Iu interface RANAP Signalling". +- [20] 3GPP TS 25.415: "UTRAN Iu interface user plane protocols". +- [21] 3GPP TS 44.118: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) Protocol, Iu Mode". +- [22] 3GPP TS 29.415: "Core Network Nb Interface User Plane Protocols". +- [23] 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)". +- [24] 3GPP TS 33.102: "3G Security; Security Architecture". + +# --- 3 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**A/Gb mode:** mode of operation of the MS when connected to the Core Network via GERAN and the A and/or Gb interfaces. + +**GERAN:** GSM/EDGE radio access network + +**HSCSD:** High Speed Circuit Switched Data + +**HSCSD configuration:** multislot configuration consisting of one or several full rate traffic channels for data transmission + +**HSCSD channel:** full rate traffic channel belonging to a HSCSD configuration + +**Iu mode:** mode of operation of the MS when connected to the Core Network via GERAN or UTRAN and the Iu interface. When preceded by the word GERAN or UTRAN, it means access over the Iu interface using the respective radio access network. + +**main channel:** only channel in a HSCSD configuration carrying an FACCH + +**symmetric configuration:** configuration consisting of bi-directional channels + +**asymmetric configuration:** configuration consisting of bi-directional channels and at least one uni-directional channel + +**UTRAN:** UMTS radio access network + +For further abbreviations see 3GPP TR 21.905 [1a]. + +# 4 Main concepts + +The air interface user rate in the original GSM data transmission is limited to 9,6 kbps with the 12 kbps air interface rate. The HSCSD described in the present document Stage 2 description allows higher air interface user rates to be used for transparent and non-transparent data services. + +NOTE: In the present document the term "air interface user rate" corresponds to the transfer rate in radio interface for user data and "air interface rate" includes additional data related to transmission protocols. + +HSCSD is a feature enabling the co-allocation of multiple full rate traffic channels (TCH/F) into a HSCSD configuration. The aim of HSCSD is to provide a mixture of services with different air interface user rates by a single physical layer structure. Further improvements in data rates are achieved through enhancement of the radio interface (modulation and coding schemes), which allows higher bit rates per one GSM time slot. The available capacity of a HSCSD configuration is several times the capacity of a TCH/F, leading to a significant enhancement in the air interface data transfer rate. + +Figure 1 represents the network architecture to support HSCSD in A/Gb mode based on the concept of multiple independent channels in one HSCSD configuration. Figure 1a represents the network architecture to support HSCSD in GERAN Iu mode. + +NOTE: 3GPP TS 43.051 [18] does not specify the GERAN internal interface between BSC and BTS. + +In case when enhanced modulation is used the number of time slots in the radio interface may not correspond to the number of data streams in the network side, for example a 28,8 kbps service may be offered through one air interface time slot, but it requires two 14,4 (16 kbps) Abis channels. Another example is bit transparent 56 kbps to 64 kbps service where two air interface time slots of 32 kbps are multiplexed onto one 64 kbps data stream on the network side. + +![Figure 1: Network architecture for supporting HSCSD in A/Gb mode. The diagram shows a sequence of network elements: MS (Mobile Station) containing a TAF (Terminal Adaptation Function), BTS (Base Transceiver Station), BSC (Base Station Controller), and MSC (Mobile Switching Center) containing an IWF (Interworking Function). The interfaces are labeled: Air I/F between MS and BTS, Abis I/F between BTS and BSC, and A I/F between BSC and MSC. Arrows indicate 'n full-rate or n time slots per TDMA' at the Air I/F and '1 circuit' at the A I/F.](e2c1c672349c10dccb2563eff6d8260e_img.jpg) + +Figure 1: Network architecture for supporting HSCSD in A/Gb mode. The diagram shows a sequence of network elements: MS (Mobile Station) containing a TAF (Terminal Adaptation Function), BTS (Base Transceiver Station), BSC (Base Station Controller), and MSC (Mobile Switching Center) containing an IWF (Interworking Function). The interfaces are labeled: Air I/F between MS and BTS, Abis I/F between BTS and BSC, and A I/F between BSC and MSC. Arrows indicate 'n full-rate or n time slots per TDMA' at the Air I/F and '1 circuit' at the A I/F. + +**Figure 1: Network architecture for supporting HSCSD in A/Gb mode** + +![Figure 1a: Network architecture for supporting HSCSD in GERAN Iu mode. This diagram is identical to Figure 1 except that the interface between the BSC and MSC is labeled 'Iu I/F' instead of 'A I/F'.](78d5774278a3f4a614f8c0ae485ce8d9_img.jpg) + +Figure 1a: Network architecture for supporting HSCSD in GERAN Iu mode. This diagram is identical to Figure 1 except that the interface between the BSC and MSC is labeled 'Iu I/F' instead of 'A I/F'. + +**Figure 1a: Network architecture for supporting HSCSD in GERAN Iu mode** + +A new functionality is introduced at the network and MS to provide the functions of combining and splitting the data into separate data streams which will then be transferred via n channels at the radio interface, where $n = 1, 2, 3, \dots, 8$ . Once split, the data streams shall be carried by the n full rate traffic channels, called HSCSD channels, as if they were independent of each other, for the purpose of data relay and radio interface L1 error control, until to the point in the network where they are combined. However, logically the n full rate traffic channels at the radio interface belong to the + +same HSCSD configuration, and therefore they shall be controlled as one radio link by the network for the purpose of cellular operations, e.g. handover. This requires a new functionality in BSS. + +The different user data substreams carried on the radio channels (one substream being the data flow over a single TCH) shall be mapped over the A interface or GERAN Iu interface, and vice versa, following the rules defined in 3GPP TS 24.008 [3] and 3GPP TS 48.020 [12]. + +In A/Gb mode, the use of resources on the A and E interfaces is restricted to one 64 kbps circuit by multiplexing the data streams into one A interface circuit (see ITU-T Recommendation I.460 [8]). + +In GERAN Iu mode, the user plane at the Iu interface shall comply to the Iu UP protocol (3GPP TS 25.415 [20]). For transparent calls the Iu user plane is operated in transparent mode, version 1, for non-transparent calls it is operated in support mode for predefined SDU sizes, version 2. + +After an inter-MSC SRNS relocation the user plane between the anchor MSC or MGW and the target MSC or MGW shall comply to the Nb UP protocol (3GPP TS 29.415 [22]), if the anchor MSC or MGW and the target MSC or MGW are connected via an ATM interface or IP interface. The NbUP shall be configured in support mode, the data is transported in a 64 kbit/s bit stream (for details see 3GPP TS 29.007 [23]). + +If both MSCs are connected via a TDM interface the use of resources on the E interface is restricted to one 64 kbps circuit (see 3GPP TS 29.007 [23]). + +## 4.1 HSCSD service aspects + +At call setup a user indicates a maximum number of TCH/F, acceptable channel codings (including extensions to acceptable channel codings for ECSD channel codings), possible other modem type, and fixed network user rate values. For non-transparent HSCSD connection, in addition, wanted air interface user rate is indicated and the network resource needs, if user wishes to make use of the user initiated modification of the maximum number of TCH/F and/or wanted air interface user rate (user initiated service level up- and downgrading described in subclauses 5.2.4 and 5.2.4a) during the call. In case the indicated acceptable channel coding(s) implies that enhanced modulation is possible, the user may indicate a preference for channel coding asymmetry, i.e. downlink biased channel coding asymmetry, uplink biased channel coding asymmetry or channel coding symmetry. Together these parameters describe the HSCSD characteristics and network uses them to allocate an appropriate HSCSD connection. + +For both transparent and non-transparent HSCSD connections the call can be established with any number of TCH/F from one up to the maximum number of TCH/F, i.e. the minimum channel requirement is always one TCH/F. + +If the wanted air interface user rate requirement cannot be met using a symmetric configuration, an asymmetric configuration can be chosen. The network shall in this case give priority to fulfilling the air interface user rate requirement in downlink direction. + +For non-transparent HSCSD connection the network can use dynamic allocation of resources, i.e. TCH/F, as long as the configuration is not in contradiction with the limiting values defined by the MS and the mobile equipment is capable of handling the allocated channel configuration. For transparent HSCSD connection the dynamic resource allocation is applicable, if the air interface user rate is kept constant. The change of channel configuration within the limits of minimum and maximum channel requirements is done with resource upgrading and resource downgrading procedures (described in subclauses 5.2.3 and 5.2.3a) during the call. + +The MS may request a service level up- or downgrading during the call, if so negotiated in the beginning of the call. In the user initiated modification procedure, the user can modify the channel coding asymmetry preference when enhanced modulation is indicated. This modification of channel requirements and/or wanted air interface user rate and/or channel coding asymmetry preference is applicable to non-transparent HSCSD connections only. + +## 4.2 HSCSD service aspects in UTRAN Iu mode + +The multislot mechanism is not needed in UTRAN Iu mode, as one bearer can provide all needed data rates. In UTRAN Iu mode, consequently the parameters required for setup of a multislot call are not needed in a call setup, and the MSC shall ignore the parameters. + +The parameters which are specific to multislot are (all contained in the Bearer Capability Information Element): + +- Maximum number of traffic channels. +- Acceptable Channel coding(s). + +- UIMI, User initiated modification indication. +- Acceptable Channel Codings extended. + +### 4.2.1 UTRAN Iu mode to GERAN Iu mode or A/Gb mode handover + +In case of handover from UTRAN Iu mode to GERAN Iu mode or A/Gb mode the multislot parameters are required in the middle of an ongoing call. A multi system mobile station supporting UTRAN Iu mode and at least one GERAN mode shall therefore always include the multislot parameters in the setup, also in UTRAN Iu mode. + +# 5 HSCSD architecture and transmission + +## 5.1 Air interface + +The HSCSD configuration is a multislot configuration using the TCH/F data channel mapping described in 3GPP TS 45.002 [2]. + +Two types of HSCSD configurations exist, symmetric configuration and asymmetric configuration. For both types of configurations the channels may be allocated on either consecutive or non-consecutive time slots taking into account the restrictions defined by the classmark. + +An example of the HSCSD operation with two consecutive time slots is shown in figure 2. + +![Figure 2: Double slot operation in the air interface. The diagram shows three horizontal timelines for MS RX, MS TX, and Monitor. MS RX has slots 0 and 1 shaded. MS TX has slots 5, 6, 7, 0, 1, 2, 3, 4, 5, 6, 7. Lines connect MS RX slots 0 and 1 to MS TX slots 0 and 1. The Monitor timeline has a single shaded slot at position 4.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg) + +Figure 2: Double slot operation in the air interface. The diagram shows three horizontal timelines for MS RX, MS TX, and Monitor. MS RX has slots 0 and 1 shaded. MS TX has slots 5, 6, 7, 0, 1, 2, 3, 4, 5, 6, 7. Lines connect MS RX slots 0 and 1 to MS TX slots 0 and 1. The Monitor timeline has a single shaded slot at position 4. + +**Figure 2: Double slot operation in the air interface** + +A symmetric HSCSD configuration consists of a bi-directional FACCH and co-allocated bi-directional TCH/F and SACCH channels. An asymmetric HSCSD configuration consists of a bi-direction FACCH and co-allocated uni-directional or bi-directional TCH/F and SACCH channels. A bi-directional channel is a channel on which the data is transferred in both uplink and downlink directions. On uni-directional channels for HSCSD the data is transferred in downlink direction, only. + +In both symmetric and asymmetric HSCSD configurations one bi-directional channel, the main channel, carries a FACCH used for all the signalling not carried on the SACCH(s). + +For HSCSD configuration all SACCHs are synchronized so that idle frames for each time slot coincide. + +The classification of mobile stations used for HSCSD shall be based on Multislot classes, described in detail in 3GPP TS 45.002 [2]. Further classification shall be based on the Mobile Station Classmark depending on the supported modulations. + +The same frequency hopping sequence and training sequence is used for all the channels in the HSCSD configuration. + +The same channel coding is used for all the channels in the HSCSD configuration, though in the enhanced modulation mode, for non-transparent services, it is possible to have one channel coding used in the downlink and another channel coding used in the uplink. Different channel codings for up- and downlink could be applied in three cases, see 3GPP TS 22.034 [9]: + +- If the mobile station only supports enhanced modulation in the downlink direction. +- If the mobile station supports enhanced modulation in both directions, but the user indicates preference for uplink or downlink biased channel coding asymmetry. +- If the mobile station supports enhanced modulation in both directions, and the user indicates preference for channel coding symmetry, but the link conditions justifies different channel coding in uplink or downlink. + +For Mobile Stations supporting 8-PSK modulation additional channel codings shall apply. The change between different TCH/F channel codings can be provided in A/Gb mode with the RR Channel Mode Modify or the + +Configuration Change procedure, and in GERAN Iu mode with the Radio Bearer Reconfiguration procedure. It shall be possible to change between channel codings of different modulation schemes. + +In symmetric HSCSD configuration individual signal level and quality reporting for each HSCSD channel is applied. + +For an asymmetric HSCSD configuration individual signal level and quality reporting is used for those channels, which have uplink SACCH associated with them. The quality measurements reported on the main channel are based on the worst quality measured among the main and the uni-directional downlink time slots used. + +In both symmetric and asymmetric HSCSD configuration the neighbouring cell measurement reports are copied on every uplink channel used. See 3GPP TS 45.008 [15] for more detail on signal level and quality reporting. + +In A/Gb mode, separate ciphering keys are used for each HSCSD channels. The ciphering keys used on different channels are derived from the Kc. See 3GPP TS 43.020 [10] for more details. In GERAN Iu mode, the same ciphering architecture is used as in UTRAN Iu mode. See 3GPP TS 43.051 [18] and 3GPP TS 33.102 [24] for more details. + +## 5.2 Functions and information flows + +The procedures discussed in this clause follow the procedures described in detail in 3GPP TS 48.008 [4], 3GPP TS 23.413 [19], 3GPP TS 23.415 [20], and 3GPP TS 24.008 [3]. Modifications are referred with text in brackets and conditional procedures with dashed line. Normal signalling or signalling presented earlier in the document is drawn with ovals. + +NOTE: 3GPP TS 43.051 [18] does not specify the GERAN internal interface between BSC and BTS. For the information flows in this document it is assumed that the protocols and procedures on this interface follow the conventions for the Abis interface, however, this is only an implementation option. + +### 5.2.1 Call establishment procedures + +#### 5.2.1.1 Mobile originated call establishment (A/Gb mode) + +Figure 3 depicts the procedures for a successful HSCSD call establishment in mobile originated case in A/Gb mode. + +The Multislot class is sent from MS to network using the early classmark sending. + +At the call setup the mobile station sends a set of parameters describing the HSCSD characteristics to the network. These parameters and their presence in the Setup message in transparent (T) and non-transparent (NT) calls are as follows: + +- | | | +|--------------------------------------------------------|-----------| +| - Other Modem Type, OMT | (T/NT); | +| - Fixed Network User Rate, FNUR | (T/NT); | +| - Acceptable Channel Codings, ACC (including ACC ext.) | (T/NT); | +| - maximum number of traffic channels, Max TCH/F | (T/NT); | +| - User Initiated Modification Indication, UIMI | (NT); | +| - wanted Air Interface User Rate, AIUR | (NT), and | +| - channel coding ASYMmetry indication, ASYM | (NT). | + +In reply the network responds in Call Proceeding with the Other Modem Type, OMT, Fixed Network User Rate, FNUR, and User Initiated Modification Indication, UIMI (NT only), parameters it is prepared to give to the mobile station. + +![Sequence diagram for Mobile originated call establishment (A/Gb mode) showing interactions between MS, BTS, BSC, and MSC.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + participant MSC + + Note over MS, BTS, BSC, MSC: Normal signalling + Note over BTS, BSC: Classmark change, CLM3 +( MS Multislot Class, Modulation capability) + Note over MS, BTS, BSC, MSC: Normal signalling + Note over BTS, BSC: SetUp +( OMT, FNUR, ACC, Max TCH/F, UIMI(NT only), AIUR(NT only), ASYM(NT only) ) + Note over MS, BTS, BSC, MSC: Call Proceeding +( OMT, FNUR, UIMI(NT only) ) + Note over BSC, MSC: Assignment Request +( Max TCH/F allowed, Allowed radio interface data rates, +Wanted total radio interface data rate(NT) / Requested +air interface user rate (T), Configuration evolution indication, +ASYM(NT only) ) + Note over BSC: Resource allocation + Note over BTS, BSC: Physical context interrogation + Note over BTS, BSC: Channel activation +( Bi-directional / Uni-directional Bm Multislot configuration) + Note over BTS, BSC: Channel activation ack + Note over MS, BTS, BSC, MSC: n times [ + Note over MS, BTS, BSC: Assignment command +( Description of multislot configuration ) + Note over MS, BTS, BSC, MSC: Signalling link establishment + Note over MS, BTS, BSC, MSC: Assignment complete + Note over BSC, MSC: Assignment complete +( Channel mode, n TCH/F ) + Note over MSC: Seize IW resources + ] + Note over MS, BTS, BSC, MSC: Normal signalling + + Note right of MS: n = number of time slots allocated + +``` + +The sequence diagram illustrates the mobile originated call establishment process in A/Gb mode. It involves four main participants: MS (Mobile Station), BTS (Base Transceiver Station), BSC (Base Station Controller), and MSC (Mobile Switching Center). The process begins with 'Normal signalling' between MS and BTS. The MS sends a 'Classmark change, CLM3' message to the BTS, which includes 'MS Multislot Class' and 'Modulation capability'. The BTS then sends 'Normal signalling' back to the MS. Next, the MS sends a 'SetUp' message to the BTS, which includes parameters like 'OMT', 'FNUR', 'ACC', 'Max TCH/F', 'UIMI(NT only)', 'AIUR(NT only)', and 'ASYM(NT only)'. The BTS responds with 'Call Proceeding', which includes 'OMT', 'FNUR', and 'UIMI(NT only)'. The BSC then sends an 'Assignment Request' to the MSC, detailing 'Max TCH/F allowed', 'Allowed radio interface data rates', 'Wanted total radio interface data rate(NT) / Requested air interface user rate (T)', 'Configuration evolution indication', and 'ASYM(NT only)'. The BSC performs 'Resource allocation' and sends a 'Physical context interrogation' to the BTS. The BTS then sends 'Channel activation' to the MS, specifying 'Bi-directional / Uni-directional Bm Multislot configuration'. The MS responds with 'Channel activation ack'. This is followed by a loop labeled 'n times' (where n is the number of time slots allocated). Inside the loop, the BTS sends an 'Assignment command' to the MS, describing the 'multislot configuration'. The MS and BTS establish a 'Signalling link establishment'. The BTS sends an 'Assignment complete' message to the MS. The BSC also sends an 'Assignment complete' message to the MSC, specifying 'Channel mode' and 'n TCH/F'. The MSC then 'Seize IW resources'. Finally, 'Normal signalling' occurs between the MS and BTS. + +Sequence diagram for Mobile originated call establishment (A/Gb mode) showing interactions between MS, BTS, BSC, and MSC. + +**Figure 3: Mobile originated call establishment (A/Gb mode)** + +The MSC requests the BSC to allocate the channel configuration using parameters derived from the HSCSD related parameters agreed in the setup phase. Based on these parameters and operator preferences the BSC then allocates a suitable number of channels and a suitable channel coding for the connection. + +The following rule for the channel allocation apply: + +- The BSS shall try to reach but not exceed, with one exception, the wanted AIUR. The exception is the case when the chosen configuration can reach the wanted AIUR with lower number of TCH/F, e.g. in case AIUR=14,4 kbit/s, max number of TCH/F=3, ACC=TCH/F4.8 and TCH/F9.6, the network shall choose 2 x 9,6 over 3 x 4,8 if the TCH/F9.6 is available in the cell. +- A separate channel activation is applied for each of the HSCSD channels before the selected channel configuration with information of the channel coding is forwarded to the mobile station. When the preference for downlink or uplink biased channel coding asymmetry is indicated by the user, and an asymmetric channel coding connection is set up based on this indication, the BSC shall always assign a TCH/F14.4 channel on the unbiased link of the connection. +- At assignment completion, the BSS informs the MSC of the chosen HSCSD configuration and the MSC may seize the IW resources accordingly. + +##### 5.2.1.1a Mobile originated call establishment (GERAN Iu mode) + +Figure 3a depicts the procedures for a successful HSCSD call establishment in mobile originated case in GERAN Iu mode. + +The MS GERAN Iu mode radio access capabilities, including the multislot capabilities of the MS, are sent from the MS to the network during the establishment of the RRC connection. + +The BSC includes the GERAN classmark in the RANAP Initial UE message to inform the MSC about the BSS capabilities of the serving cell: + +- Acceptable Channel Codings, ACC (including ACC ext.); and +- maximum number of traffic channels, Max TCH/F. + +The parameters in the Setup message and their presence requirements for transparent (T) and non-transparent (NT) calls are the same as for A/Gb mode, however, for non-transparent calls in GERAN Iu mode the channel coding asymmetry indication will be ignored. When negotiating the parameters for a transparent call, the MSC shall take the GERAN classmark into account. + +![Sequence diagram for Mobile originated call establishment (GERAN Iu mode) showing interactions between MS, BTS, BSC, and MSC.](fbfa653853daf5541118a9ddecb92284_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + participant MSC + + Note left of MS: RRC connection establishment with transfer of MS radio access capabilities + MS->>BSC: Initial Direct Transfer (CM Service Request) + BSC->>MSC: Initial UE (CM Service Request, GERAN Classmark) + Note over MS, MSC: Normal signalling + Note over BSC, MSC: SetUp (OMT, FNUR, ACC, Max TCH/F, UIMI(NT only), AIUR(NT only), ASYM(NT only)) + Note over MS, BSC: Call Proceeding (OMT, FNUR, UIMI(NT only)) + Note over BSC, MSC: RAB Assignment Request (RAB subflow combinations (NT only), GERAN BSC Container: Max TCH/F allowed, Allowed radio interface data rates) + Note right of BSC: Resource allocation + Note over BSC, MSC: Setup of radio access bearer + Note over BTS, BSC: Physical context interrogation + Note over BTS, BSC: Channel activation + Note left of MS: n times + Note over MS, BSC: Setup of radio bearer + Note over BSC, MSC: RAB Assignment Response (accepting all RAB subflow combinations (NT only)) + Note over BSC, MSC: Iu UP initialisation (NT only) + Note right of MSC: Seize IW resources + Note over MS, MSC: Normal signalling + +``` + +The sequence diagram illustrates the call establishment process. It begins with RRC connection establishment between the MS and BTS, followed by an Initial Direct Transfer (CM Service Request) from the MS to the BSC. The BSC then sends an Initial UE message to the MSC. Normal signalling follows, leading to a SetUp message from the MSC to the BSC. The BSC responds with Call Proceeding to the MS. The MSC then sends a RAB Assignment Request to the BSC, which includes parameters like RAB subflow combinations and the GERAN BSC Container. The BSC performs resource allocation and sets up the radio access bearer. It also sends physical context interrogation and channel activation messages to the BTS. This process repeats 'n times' (where n is the number of time slots allocated). The BSC then sends a RAB Assignment Response to the MSC, accepting all RAB subflow combinations. Finally, the BSC performs Iu UP initialisation (NT only), and the MSC seizes IW resources. The process concludes with normal signalling between the MS and MSC. + +n = number of time slots allocated + +Sequence diagram for Mobile originated call establishment (GERAN Iu mode) showing interactions between MS, BTS, BSC, and MSC. + +**Figure 3a: Mobile originated call establishment (GERAN Iu mode)** + +The MSC requests the BSC to allocate a radio access bearer by sending a RANAP RAB Assignment Request message. The RAB parameters in this message are set according to the parameters negotiated between MS and MSC and the GERAN classmark of the serving cell. For non-transparent calls the RAB parameters contain the description of all RAB + +subflow combinations allowable for the maximum bit rate at the Iu interface, and thus for the maximum possible AIUR that can be allocated by the BSC for this call. + +Additionally, the MSC includes a GERAN BSC container, indicating the Max TCH/F allowed and the Allowed radio interface data rates. In this version, the MSC shall indicate only one radio interface data rate as allowed. + +Based on these parameters and operator preferences the BSC then allocates a suitable number of channels for the allowed channel coding. + +After the successful setup of the radio access bearer, for non-transparent calls the BSC initiates the Iu user plane protocol. In the Iu UP initialisation message the first RAB subflow combination proposed in the list of RAB subflow combinations indicates the RAB subflow combination and thus the AIUR to be used by the IW function when starting the communication phase (see 3GPP TS 25.415 [20]). The BSC shall use the same RAB subflow combination in uplink direction. + +#### 5.2.1.2 Mobile terminated call establishment (A/Gb mode) + +Figure 4 depicts the procedures for a successful HSCSD call establishment in mobile terminated case in A/Gb mode. + +At the call setup the network sends the Other Modem Type, OMT, Fixed Network User Rate, FNUR, and User Initiated Modification Indication, UIMI (NT only), parameters to the mobile station. + +In reply the mobile station responds to the network with the set of parameters describing the HSCSD characteristics. These parameters and their presence in the Call Confirmed message in transparent (T) and non-transparent (NT) calls are as follows: + +- wanted Other Modem Type, OMT (T/NT); +- wanted Fixed Network User Rate, FNUR (T/NT); +- Acceptable Channel Codings, ACC (including ACC ext.) (T/NT); +- maximum number of traffic channels, Max TCH/F (T/NT); +- User Initiated Modification Indication, UIMI (NT); +- wanted Air Interface User Rate, AIUR (NT), and +- channel coding ASYMmetry indication, ASYM (NT). + +![Sequence diagram for Mobile terminated call establishment (A/Gb mode) showing interactions between MS, BTS, BSC, and MSC. The diagram shows signaling flows including Classmark change, SetUp, and Call Confirmed with specific parameters.](5dfc130b129ace4df375839020a5700d_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + participant MSC + + Note over MS, MSC: Normal signalling + MSC->>MS: Classmark change, CLM3 + Note over MS, MSC: ( Multislot class, Modulation capability ) + Note over MS, MSC: Normal signalling + MSC->>MS: SetUp + Note over MS, MSC: ( OMT, FNUR, UIMI(NT only) ) + MS->>MSC: Call Confirmed + Note over MS, MSC: ( OMT, FNUR, ACC, Max TCH/F, UIMI(NT only) , AIUR(NT only), ASYM(NT only) ) + Note over MS, MSC: Signalling as in mobile originated case + +``` + +Sequence diagram for Mobile terminated call establishment (A/Gb mode) showing interactions between MS, BTS, BSC, and MSC. The diagram shows signaling flows including Classmark change, SetUp, and Call Confirmed with specific parameters. + +**Figure 4: Mobile terminated call establishment (A/Gb mode)** + +The MSC requests the BSC to allocate the channel configuration using parameters derived from the HSCSD related parameters agreed in the setup phase. Based on these parameters and operator preferences the BSC then allocates a suitable number of channels and a suitable channel coding for the connection. + +The same channel allocation rules as in mobile originated case apply. + +The same channel activation rules as in mobile originated case apply. + +At assignment completion, the BSS informs the MSC of the chosen HSCSD configuration and the MSC may seize the IW resources accordingly. + +##### 5.2.1.2a Mobile terminated call establishment (GERAN Iu mode) + +Figure 4a depicts the procedures for a successful HSCSD call establishment in mobile terminated case in GERAN Iu mode. + +![Sequence diagram of mobile terminated call establishment (GERAN Iu mode)](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +``` +sequenceDiagram + participant MS + participant BTS + participant BSC + participant MSC + + Note right of MSC: Normal signalling (paging) + MS->>BSC: RRC connection establishment with transfer of MS radio access capabilities + BSC->>MSC: Initial Direct Transfer (Paging Response) + Note right of MSC: Initial UE (Paging Response, GERAN Classmark) + Note right of MSC: Normal signalling + MSC->>BSC: SetUp (OMT, FNUR, UIMI(NT only)) + BSC->>MSC: Call Confirmed (OMT, FNUR, ACC, Max TCH/F, UIMI(NT only), AIUR(NT only), ASYM(NT only)) + Note right of MSC: Signalling like in mobile originated case +``` + +The diagram illustrates the sequence of messages for a mobile terminated call establishment in GERAN Iu mode. It involves four main entities: MS (Mobile Station), BTS (Base Transceiver Station), BSC (Base Station Controller), and MSC (Mobile Switching Center). The process begins with 'Normal signalling (paging)' from the MSC. The MS then sends an 'RRC connection establishment with transfer of MS radio access capabilities' to the BSC. The BSC responds with an 'Initial Direct Transfer (Paging Response)' to the MSC, which in turn sends an 'Initial UE (Paging Response, GERAN Classmark)' back to the BSC. This is followed by 'Normal signalling' from the MSC. The MSC then sends a 'SetUp' message to the BSC, containing parameters like OMT, FNUR, and UIMI(NT only). The BSC responds with a 'Call Confirmed' message, containing parameters like OMT, FNUR, ACC, Max TCH/F, UIMI(NT only), AIUR(NT only), and ASYM(NT only). Finally, the diagram indicates 'Signalling like in mobile originated case'. + +Sequence diagram of mobile terminated call establishment (GERAN Iu mode) + +**Figure 4a: Mobile terminated call establishment (GERAN Iu mode)** + +For the Setup message and the Call Confirmed message the same rules apply as in A/Gb mode. + +The signalling for the setup of the radio bearer and the radio access bearer, and the initialisation of the Iu user plane (NT only) is as in the mobile originated case. + +### 5.2.2 Handover procedures + +#### 5.2.2.1 Intra BSC handover (A/Gb mode) + +Figure 5 depicts the procedures for a successful HSCSD intra BSC handover in A/Gb mode. + +![Sequence diagram for Intra BSC handover (A/Gb mode) showing interactions between MS, BTS old, BTS new, BSC, and MSC.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS old + participant BTS new + participant BSC + participant MSC + + MS->>BTS old: Measurement report + BTS old->>BSC: Measurement result + + Note right of BSC: HO decision + Note right of BSC: Resource allocation + + rect rgb(255, 255, 255) + Note left of BTS new: n times + BSC->>BTS new: Channel activation + Note over BSC, BTS new: ( Bi-directional / Uni-directional Bm Multislot configuration) + BTS new->>BSC: Channel activation ack + end + + BSC->>MS: Handover command + Note over MS, BSC: ( Description of multislot configuration ) + + Note over MS, BSC: Handover access and signalling link establishment + + MS->>BTS new: Handover complete + BTS new->>BSC: Handover complete + BSC->>MSC: Handover performed + Note over BSC, MSC: ( Channel mode, n TCH/F ) + + rect rgb(255, 255, 255) + Note over BTS old, BSC: m times RF channel release procedure + end + + Note right of MSC: Adjust IW resources + +``` + +$n$ = number of time slots in the new cell + $m$ = number of time slots in the old cell + +Sequence diagram for Intra BSC handover (A/Gb mode) showing interactions between MS, BTS old, BTS new, BSC, and MSC. + +**Figure 5: Intra BSC handover (A/Gb mode)** + +For a non-transparent call, the HSCSD configuration may be modified during an intra BSS handover within the maximum number of TCH/F and channel codings acceptable for the user and allowed by the network. + +The same allocation and activation rules as in call establishment apply. + +At handover completion, the BSC signals to the MSC the new HSCSD configuration and the MSC may adjust the IW resources accordingly. + +#### 5.2.2.1a Intra BSC handover (GERAN Iu mode) + +Figure 5a depicts the procedures for a successful HSCSD intra BSC handover in GERAN Iu mode. + +For a non-transparent call in GERAN Iu mode, the HSCSD configuration may be modified during an intra BSS handover within the maximum number of TCH/F acceptable for the user and allowed by the network. The outcome of the handover shall be reported to the MSC by means of an Iu UP rate control procedure (see 3GPP TS 25.415 [20]). The BSC shall set the maximum rate permitted downlink over the Iu interface according to the new HSCSD configuration. + +i.e. according to the AIUR to be used by the IW function when the communication is resumed after the handover. The BSC shall use the same RAB subflow combination in uplink direction. + +For a transparent call in GERAN Iu mode, the AIUR remains unchanged during the handover. Since the payload format at the Iu interface only depends on the AIUR, the IW resources do not need to be readjusted. + +![Sequence diagram for Intra BSC handover (GERAN Iu mode)](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` +sequenceDiagram + participant MS + participant BTS_old as BTS old + participant BTS_new as BTS new + participant BSC + participant MSC + + Note over MS, BSC: Normal signalling (measurement reporting) + Note right of BSC: HO decision + Note right of BSC: Resource allocation + Note right of BTS_new: n times Channel activation + BSC->>MS: Handover command ( Description of multislot configuration ) + Note over MS, BSC: Handover access and signalling link establishment + MS->>BTS_new: Handover complete + BTS_new->>BSC: Handover complete + Note right of BSC: Iu UP rate control (NT only) + Note right of MSC: Adjust IW resources + Note right of BTS_old: m times RF channel release procedure +``` + +The sequence diagram illustrates the interaction for an Intra BSC handover in GERAN Iu mode. It involves five lifelines: MS, BTS old, BTS new, BSC, and MSC. The process begins with 'Normal signalling (measurement reporting)' from the MS. The BSC performs an 'HO decision' and 'Resource allocation'. The BSC then sends 'Channel activation' messages to the BTS new 'n times'. A 'Handover command ( Description of multislot configuration )' is sent from the BSC to the MS. This is followed by 'Handover access and signalling link establishment'. The MS sends a 'Handover complete' message to the BTS new, which in turn sends a 'Handover complete' message to the BSC. The BSC performs 'Iu UP rate control (NT only)', and the MSC 'Adjust IW resources'. Finally, the BTS old performs 'RF channel release procedure' 'm times'. + +n = number of time slots in the new cell +m = number of time slots in the old cell + +Sequence diagram for Intra BSC handover (GERAN Iu mode) + +Figure 5a: Intra BSC handover (GERAN Iu mode) + +#### 5.2.2.2 Inter BSC, intra-MSC handover (A/Gb mode) + +Figure 6 depicts the procedures for a successful HSCSD inter BSC handover in A/Gb mode. + +![Sequence diagram for Inter BSC, intra-MSC handover (A/Gb mode).](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS old + participant BSC old + participant MSC + participant BSC new + participant BTS new + + Note right of BSC old: HO decision + MS->>BTS old: Measurement report + BTS old->>BSC old: Measurement result + BSC old->>MSC: Handover required + MSC->>BSC new: Handover request + + Note right of BSC new: ( Max TCH/F allowed, Allowed radio interface data rates, +Wanted total radio interface data rate(NT) / Requested air interface user rate (T), +Configuration evolution indication ) + BSC new->>BSC new: Resource allocation + BSC new->>BTS new: Channel activation + + Note right of BTS new: n times ( Bi-directional / Uni-directional Bm Multislot configuration ) + BTS new->>BSC new: Channel activation ack + BSC new->>MSC: Handover request ack + + Note right of MSC: ( Channel mode, n TCH/F ) + MSC->>BSC old: Handover command + + Note right of BSC old: ( Description of multislot configuration ) + Note over MS, BTS new: Handover access and signalling link establishment + BSC new->>BTS new: Handover complete + BTS new->>MSC: Handover complete + Note right of MSC: Adjust IW resources + MSC->>BSC old: Clear command + Note right of BTS old: m times RF channel release procedure + BSC old->>MSC: Clear complete + +``` + +The sequence diagram illustrates the interaction between the MS, BTS old, BSC old, MSC, BSC new, and BTS new for an inter BSC, intra-MSC handover in A/Gb mode. The process begins with the MS sending a measurement report to the BTS old, which then sends a measurement result to the BSC old. The BSC old makes an HO decision and sends a handover required message to the MSC. The MSC sends a handover request to the BSC new, including parameters such as Max TCH/F allowed, Allowed radio interface data rates, Wanted total radio interface data rate(NT) / Requested air interface user rate (T), and Configuration evolution indication. The BSC new performs resource allocation and sends a channel activation message to the BTS new. The BTS new performs n times Bi-directional / Uni-directional Bm Multislot configuration and sends a channel activation ack to the BSC new. The BSC new sends a handover request ack to the MSC, including Channel mode and n TCH/F. The MSC sends a handover command to the BSC old, including a description of multislot configuration. A handover access and signalling link establishment phase occurs. The BSC new sends a handover complete message to the BTS new, which then sends a handover complete message to the MSC. The MSC adjusts IW resources and sends a clear command to the BSC old. The BTS old performs m times RF channel release procedure and sends a clear complete message to the MSC. + +Sequence diagram for Inter BSC, intra-MSC handover (A/Gb mode). + +n = number of time slots in the new cell + +m = number of time slots in the old cell + +**Figure 6: Inter BSC intra MSC handover (A/Gb mode)** + +In inter BSS handover the MSC requests the new BSS to allocate a channel configuration using parameters derived from the HSCSD related parameters agreed earlier during the call. Based on these parameters and operator preferences the BSC then allocates a suitable number of TCH/F and a suitable channel coding for the connection. + +For a non-transparent call, the HSCSD configuration may be modified during an intra BSS handover within the maximum number of TCH/F and channel codings acceptable for the user and allowed by the network. + +The same channel allocation and activation rules as in call establishment apply. + +The BSC informs the MSC of the chosen HSCSD configuration and at handover completion the MSC may adjust the IW resources accordingly. + +##### 5.2.2.2a Inter BSC, intra-MSC handover (GERAN Iu mode) + +Figure 6a depicts the procedures for a successful HSCSD inter BSC handover in GERAN Iu mode. + +![Sequence diagram for Inter BSC, intra-MSC handover (GERAN Iu mode).](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS old + participant BSC old + participant MSC + participant BSC new + participant BTS new + + Note left of BSC old: Normal signalling (measurement reporting) + BSC old->>MSC: Relocation required (GERAN Classmark) + MSC->>BSC new: Relocation request (RAB subflow combinations (NT only), GERAN BSC Container: Max TCH/F allowed, Allowed radio interface data rates) + BSC new->>MSC: Resource allocation + Note right of MSC: Setup of radio access bearer + Note right of BSC new: Channel activation + Note right of MSC: n times + MSC->>BSC old: Relocation request ack (Iu UP initialisation (NT only)) + MSC->>BSC old: Relocation command + BSC old->>MS: Handover command (Description of multislot configuration) + Note right of MS: Handover access and signalling link establishment + BSC new->>MSC: Handover complete + MSC->>BSC old: Relocation complete + Note right of MSC: Adjust IW resources + MSC->>BSC old: Iu Release command + Note right of BTS old: m times RF channel release procedure + BSC old->>MSC: Iu Release complete + +``` + +$n$ = number of time slots in the new cell + $m$ = number of time slots in the old cell + +Sequence diagram for Inter BSC, intra-MSC handover (GERAN Iu mode). + +**Figure 6a: Inter BSC intra MSC handover (GERAN Iu mode)** + +The serving BSC includes the GERAN classmark of the target cell in the RANAP Relocation Required message. The MSC takes this information into account when it selects the RAB parameters for the RANAP Relocation Request message. + +For a non-transparent call in GERAN Iu mode, the HSCSD configuration may be modified during an inter BSC handover within the maximum number of TCH/F acceptable for the user and allowed by the network. After the successful setup of the radio access bearer towards the new BSC, for non-transparent calls the new BSC initiates the Iu user plane protocol. In the Iu UP initialisation message the first RAB subflow combination proposed in the list of RAB subflow combinations indicates the RAB subflow combination and thus the AIUR to be used by the IW function when the communication is resumed after the handover (see 3GPP TS 25.415 [20]). The new BSC shall use the same RAB subflow combination in uplink direction. + +For a transparent call in GERAN Iu mode, the AIUR remains unchanged during the handover. Since the payload format at the Iu interface only depends on the AIUR, the IW resources do not need to be readjusted. + +#### 5.2.2.3 Inter MSC handover + +In inter MSC handover the requested channel configuration is forwarded to a BSS within the new MSC using MAP protocol between MSCs. Procedures similar to those in inter BSS handover case can be applied in order to establish the HSCSD connection in a new cell. + +In GERAN Iu mode, the GERAN classmark of the target cell is forwarded to the anchor MSC and to the target MSC using MAP protocol between MSCs. + +### 5.2.3 Resource upgrading, downgrading and configuration change (A/Gb mode) + +Resource upgrading means allocating more channels to the HSCSD configuration. Similarly, in resource downgrading channels are released. + +Both of these procedures are initiated by the network and they are used in non-transparent calls to alter the channel resources between one TCH/F and the maximum number of TCH/F allowed. For transparent connection the alteration of resources is also applicable required that the AIUR for the connection remains constant. + +Figure 7 depicts the procedures for a successful resource upgrading and downgrading for an ongoing HSCSD call in A/Gb mode, in case the position of the main TCH/F remains unchanged. + +A separate channel activation for the new HSCSD channels is carried out and the earlier activated HSCSD channels may be modified, before RR Configuration change procedure is used for forwarding the new channel configuration to the mobile station. Similarly, the Configuration change procedure can be used in both transparent and non-transparent calls for reordering the channels in a call without changing the number of TCH/Fs allocated. + +At resource modification completion, the BSC signals to the MSC the new HSCSD configuration and the MSC may adjusts the IW resources accordingly. + +![Sequence diagram for Figure 7: Resource upgrading and downgrading in A/Gb mode, the position of the main channel unchanged. The diagram shows interactions between MS, BTS, BSC, and MSC. The BSC performs internal 'Resource change decision' and 'Resource allocation'. It then sends 'Channel activation / Mode modify' to the BTS, which responds with 'Channel activation ack / Mode modify ack'. This exchange is repeated (A + M) times for 'Bi-directional / Uni-directional Bm Multislot configuration'. Next, the BSC sends a 'Configuration change command' to the MS, which responds with 'Configuration change ack'. The BSC then signals 'Handover Performed' to the MSC with '( Channel mode, n TCH/F )'. Finally, the BSC sends 'RF channel release' to the BTS, which responds with 'RF channel release ack'. This exchange is repeated R times. The MSC then performs 'Adjust IW resources'.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + participant MSC + + Note right of BSC: Resource change decision + Note right of BSC: Resource allocation + BSC->>BTS: Channel activation / Mode modify + Note left of BTS: ( A + M ) times + Note left of BTS: ( Bi-directional / Uni-directional Bm Multislot configuration ) + BTS->>BSC: Channel activation ack / Mode modify ack + BSC->>MS: Configuration change command + Note left of MS: ( Description of multislot configuration ) + MS->>BSC: Configuration change ack + BSC->>MSC: Handover Performed + Note right of MSC: ( Channel mode, n TCH/F ) + Note right of MSC: Adjust IW resources + BSC->>BTS: RF channel release + Note left of BTS: R times + BTS->>BSC: RF channel release ack + +``` + +A = number of time slots added to the connection + R = number of time slots released from the connection + M = number of time slots modified + n = number of time slots after upgrading/downgrading + +Sequence diagram for Figure 7: Resource upgrading and downgrading in A/Gb mode, the position of the main channel unchanged. The diagram shows interactions between MS, BTS, BSC, and MSC. The BSC performs internal 'Resource change decision' and 'Resource allocation'. It then sends 'Channel activation / Mode modify' to the BTS, which responds with 'Channel activation ack / Mode modify ack'. This exchange is repeated (A + M) times for 'Bi-directional / Uni-directional Bm Multislot configuration'. Next, the BSC sends a 'Configuration change command' to the MS, which responds with 'Configuration change ack'. The BSC then signals 'Handover Performed' to the MSC with '( Channel mode, n TCH/F )'. Finally, the BSC sends 'RF channel release' to the BTS, which responds with 'RF channel release ack'. This exchange is repeated R times. The MSC then performs 'Adjust IW resources'. + +**Figure 7: Resource upgrading and downgrading in A/Gb mode, the position of the main channel unchanged** + +Figure 8 depicts the procedures for a successful resource upgrading and downgrading for an ongoing HSCSD call in A/Gb mode in case the position of the main channel is changed. + +A separate channel activation for the new HSCSD channels, is carried out and the earlier activated HSCSD channels may be modified or, in case of the new main channel, reactivated, before RR Assignment procedure is used for forwarding the new channel configuration to the mobile station. Similarly, the Assignment procedure can be used in both transparent and non-transparent calls for reordering the channels in a call without changing the number of TCH/Fs allocated. + +At resource modification completion, the BSC signals to the MSC the new HSCSD configuration and the MSC may adjust the IW resources accordingly. + +![Sequence diagram for Figure 8: Resource upgrading and downgrading in A/Gb mode, the position of the main channel changed. The diagram shows interactions between MS, BTS, BSC, and MSC. The process involves resource change decision, resource allocation, channel (re-)activation, assignment command, signalling link establishment, assignment complete, channel re-activation, RF channel release, and finally adjusting IW resources at the MSC.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + participant MSC + + Note right of BSC: Resource change decision + Note right of BSC: Resource allocation + BSC->>BTS: Channel (re-)activation / Mode modify +(Bi-directional / Uni-directional Bm Multislot configuration) + Note left of BTS: ( A + M - 1 ) times + BTS->>BSC: Channel (re-)activation ack / Mode modify ack + BSC->>MS: Assignment command +( Description of multislot configuration ) + Note over MS, BSC: Signalling link establishment + BSC->>MSC: Assignment complete +Handover Performed +( Channel mode, n TCH/F ) + Note right of MSC: Adjust IW resources + BSC->>BTS: Channel re-activation +( Bi-directional / Uni-directional Bm Multislot configuration) + Note right of BTS: Note ! + BTS->>BSC: Channel re-activation ack + Note left of BTS: R times + BTS->>BSC: RF channel release + BTS->>BSC: RF channel release ack + +``` + +Sequence diagram for Figure 8: Resource upgrading and downgrading in A/Gb mode, the position of the main channel changed. The diagram shows interactions between MS, BTS, BSC, and MSC. The process involves resource change decision, resource allocation, channel (re-)activation, assignment command, signalling link establishment, assignment complete, channel re-activation, RF channel release, and finally adjusting IW resources at the MSC. + +NOTE: Deactivates the old signalling link by modifying the old main channel. The old main can not be modified before a new main has been established. If the time slot for the old main is not used in the new HSCSD configuration, RF channel release is used instead. + +A = number of time slots added to the HSCSD connection + +R = number of time slots released from the HSCSD connection + +M = number of time slots modified or re-activated + +n = number of time slots after upgrading/downgrading + +**Figure 8: Resource upgrading and downgrading in A/Gb mode, the position of the main channel changed** + +#### 5.2.3a Resource upgrading, downgrading and configuration change (GERAN Iu mode) + +In GERAN Iu mode a Radio bearer reconfiguration procedure is used for forwarding the new channel configuration to the mobile station, regardless whether the position of the main channel is changed or not. + +Figure 8a depicts the procedures for a successful resource upgrading and downgrading for an ongoing HSCSD call in GERAN Iu mode, in case the position of the main TCH/F remains unchanged. + +![Sequence diagram for Figure 8a: Resource upgrading and downgrading in GERAN Iu mode. Lifelines: MS, BTS, BSC, MSC. The process involves Resource change decision, Resource allocation, Channel (re-)activation / Mode modify (A + M times), Radio bearer reconfiguration, Iu UP rate control (NT only), RF channel release (R times), and Adjust IW resources.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + participant MSC + + Note over BSC: Resource change decision + Note over BSC: Resource allocation + Note over BTS, BSC: Channel (re-)activation / Mode modify + Note left of BTS: (A + M) times + Note over MS, BSC: Radio bearer reconfiguration + Note over BSC, MSC: Iu UP rate control (NT only) + Note over BTS, BSC: RF channel release + Note left of BTS: R times + Note over MSC: Adjust IW resources + +``` + +**A** = number of time slots added to the HSCSD connection +**R** = number of time slots released from the HSCSD connection +**M** = number of time slots modified or re-activated +**n** = number of time slots after upgrading/downgrading + +Sequence diagram for Figure 8a: Resource upgrading and downgrading in GERAN Iu mode. Lifelines: MS, BTS, BSC, MSC. The process involves Resource change decision, Resource allocation, Channel (re-)activation / Mode modify (A + M times), Radio bearer reconfiguration, Iu UP rate control (NT only), RF channel release (R times), and Adjust IW resources. + +**Figure 8a: Resource upgrading and downgrading in GERAN Iu mode, the position of the main channel unchanged** + +The outcome of the procedure shall be reported to the MSC by means of an Iu UP rate control procedure (see 3GPP TS 25.415 [20]). The BSC shall set the maximum rate permitted downlink over the Iu interface according to the new HSCSD configuration, i.e. according to the AIUR to be used by the IW function when the communication is resumed after the handover. The BSC shall use the same RAB subflow combination in uplink direction. + +For a transparent call in GERAN Iu mode, the resource upgrading or downgrading is not applicable since the AIUR remains unchanged during the call, and the allowed radio interface data rate is set by the MSC. + +### 5.2.4 User initiated service level up- and downgrading (A/Gb mode) + +Figure 9 depicts the procedures for a successful user initiated service level up- and downgrading for on-going HSCSD call in A/Gb mode. + +During a HSCSD call the user may request, if so indicated in the call setup, the network to change the current maximum number of traffic channels and air interface user rate parameters and/or channel coding asymmetry preference. This is done by using the CC User initiated service level up- and downgrading procedure. + +If network allows the modification, the resulting new parameters are forwarded to BSC and the radio interface resources may be adjusted accordingly. The resource upgrading or downgrading is done separately from the change in HSCSD parameters. However, if a contradiction between the new parameters and the used air interface resources exists, the resource downgrading may be needed before the network acknowledges the new parameters. + +The user initiated service level up- and downgrading is applicable in non-transparent mode connections, only. + +![Sequence diagram for Figure 9: User initiated service level up- and downgrading in A/Gb mode. Lifelines: MS, BTS, BSC, MSC. The MS sends a Modify message to the MSC. The MSC sends an Assignment Request to the BSC. The BSC performs a possible resource up- or downgrading procedure and sends an Assignment complete message to the MSC. The MSC sends a Modify complete message to the MS.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + participant MSC + Note right of MSC: Possible resource up- or downgrading procedure + MS->>MSC: Modify +( OMT, FNUR, ACC, Max TCH/F, UIMI, AIUR(NT only), ASYM (NT only) ) + MSC->>BSC: Assignment Request +( Max TCH/F allowed, Allowed radio interface data rates, Wanted total radio interface data rate, ASYM(NT) ) + BSC-->>MSC: Assignment complete +( Channel mode, n TCH/F ) + MSC-->>MS: Modify complete + +``` + +Sequence diagram for Figure 9: User initiated service level up- and downgrading in A/Gb mode. Lifelines: MS, BTS, BSC, MSC. The MS sends a Modify message to the MSC. The MSC sends an Assignment Request to the BSC. The BSC performs a possible resource up- or downgrading procedure and sends an Assignment complete message to the MSC. The MSC sends a Modify complete message to the MS. + +n = number of time slots allocated + +Figure 9: User initiated service level up- and downgrading in A/Gb mode + +#### 5.2.4a User initiated service level up- and downgrading (GERAN Iu mode) + +Figure 9a depicts the procedures for a successful user initiated service level up- and downgrading for on-going HSCSD call in GERAN Iu mode. + +The user initiated service level up- and downgrading is applicable in non-transparent mode connections, only. + +![Sequence diagram for Figure 9a: User initiated service level up- and downgrading in GERAN Iu mode. Lifelines: MS, BTS, BSC, MSC. The MS sends a Modify message to the MSC. The MSC sends a RAB Assignment Request to the BSC. The BSC performs a modification of radio access bearer and a possible resource up- or downgrading procedure. The BSC sends a RAB Assignment Response to the MSC. The MSC performs Iu UP initialisation and sends a Modify complete message to the MS.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + participant MSC + Note right of BSC: Possible resource up- or downgrading procedure + MS->>MSC: Modify +( OMT, FNUR, ACC, Max TCH/F, UIMI, AIUR(NT only), ASYM (NT only) ) + MSC->>BSC: RAB Assignment Request +( RAB subflow combinations, GERAN BSC Container: Max TCH/F allowed, Allowed radio interface data rates ) + BSC-->>MSC: Modification of radio access bearer + BSC-->>MSC: RAB Assignment Response +( accepting all RAB subflow combinations ) + MSC-->>BSC: Iu UP initialisation + MSC-->>MS: Modify complete + +``` + +Sequence diagram for Figure 9a: User initiated service level up- and downgrading in GERAN Iu mode. Lifelines: MS, BTS, BSC, MSC. The MS sends a Modify message to the MSC. The MSC sends a RAB Assignment Request to the BSC. The BSC performs a modification of radio access bearer and a possible resource up- or downgrading procedure. The BSC sends a RAB Assignment Response to the MSC. The MSC performs Iu UP initialisation and sends a Modify complete message to the MS. + +n = number of time slots allocated + +Figure 9a: User initiated service level up- and downgrading in GERAN Iu mode + +### 5.2.5 Link adaptation for ECSD + +Link adaptation for ECSD particularly in high data rate call becomes essential in order to provide good enough service over large coverage areas. In A/Gb mode, signalling for link adaptation between channel coding schemes in 8-PSK modulation and between GMSK and 8-PSK coding schemes is done using existing signalling mechanisms, i.e. RR Channel Mode Modify procedure, intracell handover, etc. In performing link adaption between 8-PSK modulated channels, the normal Channel Mode (or the assignment or the intra-cell HO procedure) should be used and in case of link adaptation between 8-PSK modulated channels and GMSK modulated channels the assignment procedure or the intra-cell handover should be used. + +In GERAN Iu mode, the Radio bearer reconfiguration procedure is used for link adaptation. + +### 5.2.6 Start of ciphering + +In A/Gb mode, in order to start ciphering, the RR Encryption procedure is controlled by the main signalling link, only. The encryption information for secondary HSCSD channel is forwarded to the corresponding TCH/F in initial channel activation or later in the channel reactivation or Mode modify message. + +The change of ciphering modes for separate channels within the HSCSD connection might not be perfectly synchronized. + +In GERAN Iu mode, the Security mode control procedure is used to start ciphering (see 3GPP TS 44.118 [21]). + +## 5.3 Transparent data transmission + +### 5.3.1 Numbering of data substreams + +In transparent data transmission the V.110 data frames on the HSCSD channels carry data substream numbers to retain the order of transmission over GSM, between the split/combine functions. Between these functions a channel internal multiframing is also used in order to increase the tolerance against inter channel transmission delays. In A/Gb mode, depending on the location of the access point to external networks the split/combine functionality is located in the BSS or in the IWF on the network side, and at the mobile station. In GERAN Iu mode, the split/combine functionality on the network side is always located in the BSS. + +A detailed description of the numbering scheme is given in 3GPP TS 44.021 [11]. + +### 5.3.2 Padding + +HSCSD also supports user rates which are not multiples of rates provided by one TCH/F. + +If the selected user rate requires n TCH/F channels but is less than the total rate that can be achieved with these n TCH/F then in the first n-1 channels the data frames carry user data on all D bits. In the n th channel the unneeded D bits of the V.110 frames are padded with fill bits. + +## 5.4 Non-Transparent data transmission + +### 5.4.1 HSCSD RLP + +Non-transparent mode of HSCSD is realized by modifying the RLP and L2R functions to support multiple parallel TCH/Fs instead of only one TCH/F (figure 9a). In addition the RLP frame numbering is increased to accommodate the enlarged data transmission rate. + +The detailed specification of the RLP is given in 3GPP TS 24.022 [5], and L2R is defined in 3GPP TS 27.002 [13] and 3GPP TS 27.003 [14]. + +![Diagram of the HSCSD concept in non-transparent mode. It shows two main components: MS (Mobile Station) and IWF (Interworking Function). The MS contains an L2R block, an HSCSD RLP block, and multiple L1 entities. The IWF contains an HSCSD RLP block and an L2R block. The L1 entities in the MS are connected to the HSCSD RLP block, which is then connected to the L2R block. The L1 entities in the IWF are connected to the HSCSD RLP block, which is connected to the L2R block. There are zigzag lines between the L1 entities of the MS and the IWF, indicating a connection between them.](26d664119ad25250780f554633444e54_img.jpg) + +Diagram of the HSCSD concept in non-transparent mode. It shows two main components: MS (Mobile Station) and IWF (Interworking Function). The MS contains an L2R block, an HSCSD RLP block, and multiple L1 entities. The IWF contains an HSCSD RLP block and an L2R block. The L1 entities in the MS are connected to the HSCSD RLP block, which is then connected to the L2R block. The L1 entities in the IWF are connected to the HSCSD RLP block, which is connected to the L2R block. There are zigzag lines between the L1 entities of the MS and the IWF, indicating a connection between them. + +Figure 9a: The HSCSD concept in non-transparent mode + +## 5.5 Interworking + +Interworking of HSCSD will be arranged to all the services to which interworking is provided in the existing GSM-system; these services are PSTN, ISDN, CSPDN and PSPDN. + +## 5.6 Subscription aspects and storage of subscriber data + +The HSCSD uses general bearer services defined in 22 series specifications. No HSCSD related subscriber data is stored in HLR or VLR with the exception of the bearer capability allocation (see 3GPP TS 23.008 [16]). + +# 6 Charging + +## 6.1 General principles + +The A party is liable for the usage of all TCH/F in her PLMN. The B party may have to pay for one or more TCH/F in her PLMN. In case the originating or terminating subscriber is in the PSTN there is no additional charge for them. + +## 6.2 Call forwardings + +The A party is liable for the leg A-B. The B party who forwards the call to the forwarded-to subscriber (C party) is liable for the primary (basic) channel on the leg B-C. Forwarded-to (C party) is liable for the usage of one or more TCH/F in her PLMN. + +## 6.3 AoC and toll ticketing + +MSC will send the modified e-parameters to the MS, both in MO and in MT calls, every time the charging rate will change. This can happen when: + +- the coding on the air interface channel is changed; +- the number of TCH/F allocated is increased or decreased; + +during an existing HSCSD data call and when AoC supplementary service is activated. + +Appropriate information concerning these changes have to also be included in the charging record (toll ticket). + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|-----------|---------|-----|-----|--------|-------------|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | Rev | Rel. | New Version | Subject | Comment | +| Apr 1999 | GSM 03.34 | | | | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.034 | | | | | 3.0.0 | | Approved at CN#03 | +| CN#5 | 23.034 | 3.0.0 | 001 | 2 | R99 | 3.1.0 | CR to 23.034 due to asymmetry for ECSD | V3.1.1 was to correct the implementation of this CR | +| CN#7 | 23.034 | 3.1.1 | 003 | 2 | R99 | 3.2.0 | Modifications to Stage 2 service description due to EDGE | | +| CN#7 | 23.034 | 3.1.1 | 004 | 1 | R99 | 3.2.0 | Support of high speed data in UMTS/UTRAN | | +| NP-10 | 23.034 | 3.2.0 | 005 | | R99 | 3.3.0 | Terminology corrections | NP-000674 (N1-001321), 2000-12 | +| NP-11 | 23.034 | 3.3.0 | | | Rel-4 | 4.0.0 | | TSG CN#11 decided to issue this specification as part of release 4 on March 2001. | +| NP-16 | 23.034 | 4.0.0 | | | Rel-5 | 5.0.0 | | TSG CN#16 decided to issue this specification as part of release 5 on June 2002.
ETSI/MCC updated this version with references and editorials. | +| NP-18 | 23.034 | 5.0.0 | 007 | 3 | Rel-5 | 5.1.0 | Introduction of GERAN Iu-mode | NP-020570 (N1-022427), 2002-12 | +| NP-19 | 23.034 | 5.1.0 | 008 | | Rel-5 | 5.2.0 | Use of Nb UP protocol after inter-MSC handover | NP-030056 (N1-030091), 2003-03 | +| NP-26 | 23.034 | 5.2.0 | | | Rel-6 | 6.0.0 | Rel-6 published after CN#26 | | +| | | 6.0.0 | | | Rel-7 | 7.0.0 | Upgraded to Rel-7 by MCC | | +| | | 7.0.0 | | | Rel-8 | 8.0.0 | Upgraded to Rel-8 by MCC | | +| | | 8.0.0 | | | Rel-9 | 9.0.0 | Upgraded to Rel-9 by MCC | | +| | | 9.0.0 | | | Rel-10 | 10.0.0 | Upgraded to Rel-10 by MCC | | +| | | 10.0.0 | | | Rel-11 | 11.0.0 | Upgraded to Rel-11 by MCC | | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23035/raw.md b/marked/Rel-11/23_series/23035/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..683716f1ce4c56331a49ea243e365eabf8a73afe --- /dev/null +++ b/marked/Rel-11/23_series/23035/raw.md @@ -0,0 +1,225 @@ + + + + + + +# --- Contents + +| | | +|--------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 Information flows..... | 6 | +| 4.1 CAMEL implementation..... | 6 | +| 4.2 Non-CAMEL implementation..... | 6 | +| 5 Functional behaviour - CAMEL implementation ..... | 7 | +| 5.1 Subscriber settings..... | 7 | +| 5.2 DP Settings..... | 7 | +| 5.3 Call termination..... | 7 | +| 6 Functional behaviour - Non-CAMEL implementation..... | 7 | +| 6.1 Subscriber Settings ..... | 8 | +| 6.2 Periodic reporting mechanism..... | 8 | +| 6.2.1 IST Alert timer Settings..... | 8 | +| 6.2.2 Call termination ..... | 9 | +| 6.3 IST standalone mechanism..... | 9 | +| 6.4 Exception procedure..... | 9 | +| 7 Control of IST ..... | 10 | +| Annex A (Informative): Change History..... | 11 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +This Technical Specification specifies the stage 2 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN. + +Two implementations of IST are described: an implementation based on CAMEL, and an implementation based on a new MAP message. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.032: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Immediate Service Termination (IST), Service description - Stage 1". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Subscriber activities:** subscriber activities that must be terminated. These can be call related events (e.g. call set-up, call termination) or the invocation of call related and call independent supplementary services (e.g. Call Hold, Call Waiting, Call Transfer, Call Forwarding, Unstructured Supplementary Service Data (USSD)). + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following abbreviations apply: + +| | | +|-------|--------------------------------------------| +| IST | Immediate Service Termination | +| FDS | Fraud Detection System | +| FIGS | Fraud Information Gathering System | +| MO | Mobile Originated | +| MT | Mobile Terminated | +| O-CSI | Originating CAMEL Subscription Information | +| T-CSI | Terminating CAMEL Subscription Information | + +# --- 4 Information flows + +## 4.1 CAMEL implementation + +For the Customised Applications for Mobile network Enhanced Logic (CAMEL) implementation of Immediate Service Termination (IST) for a particular subscriber, an "IST" command (in reality, the CAMEL message "ReleaseCall") must be sent by the gsmSCF of the home PLMN to the gsmSSF controlling the call, for all the calls of the subscriber. + +Prior to the sending of the IST command, the Mobile Application Part (MAP) command "Cancel Location" should be sent to the VLR at which the subscriber is registered. This will ensure that the subscriber cannot re-commence service at that VLR after the IST command has been executed. See Annex A of TS 22.032 [2]. + +The compilation of the list of MSCs to which the IST command should be sent is outside the scope of this specification. However, if a PLMN operator wishes to implement IST using CAMEL, the list of MSCs to which the IST command should be sent for a subscriber is the list of MSCs with which the CAMEL server has a relationship for that subscriber. If this data is not available directly from the CAMEL server, it may be obtained using Fraud Information Gathering System (FIGS) or an Fraud Detection System (FDS) (if the HPLMN is using CAMEL for IST then it is likely that it will also be monitoring the subscriber's activities using FIGS level 2 or 3, which use CAMEL). + +## 4.2 Non-CAMEL implementation + +For each non-CAMEL-subscriber under IST control, the HLR shall request the MSCs during location update and routeing information retrieval to report for each remaining activity periodically at the frequency defined by the IST Alert timer value about the remaining activity for this subscriber in the node by sending an IST Alert Message to the HLR, as long as the activity is ongoing. The IST Alert timer value is set by HPLMN and communicated to VPLMN and IPLMN on subscriber basis. + +The HLR shall be able to request termination of ongoing call activities for a subscriber by returning a call termination indicator to the MSC in response to the IST Alert message initiated by this MSC. When this call termination indicator is received, the MSC shall terminate the call activities for that subscriber (the MSC shall terminate the call activity that triggered the IST Alert dialogue, and optionally other call activities in that MSC if the MSC is able to link the calls related to the subscriber). + +As an implementation option the HLR may for each non-CAMEL-subscriber under IST control maintain a list of MSCs which possibly have ongoing activities for the subscriber. The HLR may then send at any time (i.e. without waiting for the IST Alert message) an unsolicited IST Command message to these MSCs in order to request termination of all ongoing activities for the subscriber. The HLR should send unsolicited IST Command message only to those MSCs that are likely to be carrying a call that needs to be terminated. + +Before sending of any IST Command message for a subscriber, the HLR should send the MAP Cancel Location message to the VLR at which the subscriber is registered. This will ensure that the subscriber cannot re-commence service at the corresponding MSC after the IST Command message has been executed. See Annex A of TS 22.032 [2]. The MSC shall be prepared to receive an IST Command message before and/or after the subscriber record has been removed from the VLR. + +# --- 5 Functional behaviour - CAMEL implementation + +This clause describes the implementation of IST using CAMEL. CAMEL can be used to terminate all the mobile originated (MO), mobile terminated (MT) and forwarded (CF) calls of a subscriber, provided there is a control relationship between the CAMEL server (the gsmSCF) in the HPLMN and the MSC (visited MSC or GMSC) (the gsmSSF) controlling the call or forwarding leg. + +## 5.1 Subscriber settings + +The subscriber is marked as a CAMEL subscriber by setting Originating CAMEL Subscription Information (O-CSI) and Terminating CAMEL Subscription Information (T-CSI) in the subscriber data stored in the HLR of the HPLMN. The O-CSI is sent to the VPLMN when the subscriber first registers in the VPLMN; the T-CSI is sent to the GMSC in the response to a request for routeing information. If the subscriber is being monitored using FIGS, it will already be marked as a CAMEL subscriber. + +If the HPLMN wishes to mark a subscriber as a CAMEL subscriber when the subscriber is already registered in the VPLMN, it modifies the subscriber data in the VPLMN using the command *Insert Subscriber Data*. + +## 5.2 DP Settings + +A call cannot be terminated using CAMEL unless there is a control relationship between the gsmSCF and the gsmSSF controlling the call. To ensure that the IST command can be used at any point in the duration of a call, right up to the end of the call, there must be a control relationship until the end of the call. + +A "control relationship" exists where there is at least one armed DP in the gsmSSF. This can be achieved if the DP *O/T\_Disconnect* (which will trigger the sending of an *Event\_Report\_BCSM* to the gsmSCF) is set for the call. + +If the subscriber is being monitored using FIGS level 2 or 3, the subscriber will already be marked as a CAMEL subscriber and DP *O/T\_Disconnect* will already have been set. + +If the subscriber is not being monitored using FIGS levels 2 or 3 then *O/T\_Disconnect* is set with command *Request\_Report\_BCSM\_Event* sent to the gsmSSF by the gsmSCF after the gsmSCF has received notification of a call attempt via the *Initial\_DP* message received from the gsmSSF. + +*Initial\_DP* notifies the gsmSCF of call attempts. If the gsmSCF wishes to be notified of the success or failure of a call attempt, and so not be keeping a register of "calls" that may not have commenced, DP *O/T\_Answer* can be set to inform the gsmSCF when a call is answered by the calling party. + +If the **non**-reception of an *Event\_Report\_BCSM* indicating call answer is **not** sufficient indication to the HPLMN of the failure of a call attempt, DPs *O\_Route\_Select\_Failure*, *O/T\_Busy*, *O/T\_No\_Answer*, *O/T\_Abandon*, *O/T\_Not\_Reachable* can be set to inform the gsmSCF explicitly if the call attempt fails. If the various failure DPs are not armed, the gsmSCF can still deduce that the call attempt has failed because the gsmSSF will terminate the relationship when the call fails by sending message *Abort* to the gsmSCF. + +All these DPs can be set via the *Request\_Report\_BCSM\_Event* sent to the gsmSSF by the gsmSCF after receiving the *InitialDP* message. If all these DPs are set then the subscriber is in fact being monitored with the equivalent of FIGS level 2 monitoring. + +## 5.3 Call termination + +The HPLMN will be informed of the call attempts (MO, MT and CF) of the subscriber with message *InitialDP*. This message will give the address of the gsmSSF (=MSC) controlling the call. The call can be terminated by the gsmSSF at any time by sending message *ReleaseCall* to the controlling gsmSSF. The gsmSSF will then terminate the call. + +# --- 6 Functional behaviour - Non-CAMEL implementation + +This clause describes the implementation of IST using non-CAMEL implementation. This mechanism can be used to terminate all the originated (MO), terminated (MT) Deflected (CD), Transferred (ECT) and forwarded (CF) calls of a subscriber, provided that this IST mechanism is supported in the HLR and in the serving MSC/VLRs (visited MSC or GMSC controlling the call or forwarding leg). + +## 6.1 Subscriber Settings + +The subscriber is marked as a non-CAMEL IST subscriber by setting an IST Alert timer value in the subscriber data stored in the HLR. The IST Alert timer value is sent to the VLR in response to an Update Location request which indicates that the MSC/VLR supports IST; the IST Alert timer value is sent to the GMSC in the response to a request for routing information which indicates that the GMSC supports IST. + +The IST Alert timer value is in a range from 15 to 255 minutes with steps of 1 minute. For the subscribers not marked as IST non-CAMEL subscribers, the IST Alert timer value is not transmitted to the VLR or to the GMSC. The IST Alert timer value may be assigned on subscriber basis depending on the risk associated to the specific subscriber. As a network option the IST Alert timer value transmitted for a certain subscriber may be different for different entities (or PLMNs). + +If the HLR operator wishes to mark a subscriber as a non-CAMEL IST subscriber when the subscriber is already registered in a VLR, provided that the VLR supports IST, the HLR modifies the subscriber data in the VLR using the MAP Insert Subscriber Data message. Note that this does not affect already ongoing activities in the MSC. If the + +subscriber is under IST condition and the HLR operator decides to remove this condition, the HLR modifies the subscriber data in the VLR using the MAP Delete Subscriber Data message. Note that this does not affect the operation of any timer which is currently running. + +## 6.2 Periodic reporting mechanism + +### 6.2.1 IST Alert timer Settings + +The call termination shall be provided based on a "notification relationship". The HLR shall request to the MSCs during location update and routing information retrieval to report for each remaining activity periodically at the frequency defined by the IST Alert timer value about the remaining activity for that subscriber in the node by sending an IST Alert message to the HLR, as long as the activity is ongoing. + +The timer supervision starts in the MSC after initiation of any outgoing call activity [MO, CD, CF, ECT calls] for that subscriber. A separate timer supervision shall be initiated per each outgoing call activity for each subscriber. The notification IST Alert message is then transmitted to the HLR per call activity whenever the IST Alert timer running for that call expires. When the HLR receives an IST Alert message from an MSC, it can either return an empty result component, return a component including the subscribed IST Alert timer value, return an indication that the IST condition has been removed for the subscriber or return a call termination indicator. This returned call termination indicator is used by the MSC to terminate the outgoing call activities (either the call activity that initiated the IST Alert dialogue, or optionally to release all outgoing call activities) for that subscriber in the MSC. Release of all call activities using the returned call termination indicator is possible only if the MSC is able to link all call activities related to that subscriber. If the HLR has returned an indication that the IST condition has been removed from the subscriber, IST control for that call in the MSC is terminated. The IST Alert timer that monitors the activity that initiated the IST Alert is restarted when no call termination indicator has been received in the IST Alert dialogue and the IST Alert response received does not indicate termination of IST condition; the IST Alert timer value shall be the same as in the previous count, or the new value received in the IST Alert response if any. + +The timer supervision starts in the GMSC after reception of the response to a request for routing information. A separate timer supervision shall be initiated per each incoming call activity [MT, CF] for each subscriber. An IST Alert message is then transmitted to the HLR per call activity whenever the IST Alert timer running for that call expires. When the HLR receives an IST Alert message from a GMSC, it can either return an empty result component, return a component including the subscribed IST Alert timer value, return an indication that the IST condition has been withdrawn for the subscriber or return a call termination indicator. This returned call termination indicator is used by the GMSC to terminate the incoming call activities (either the call activity that initiated the IST Alert dialogue, or optionally to release all incoming call activities) for that subscriber in the GMSC. Release of all incoming call activities using the returned call termination indicator is possible only if the GMSC is able to link all call activities related to that subscriber. If the HLR has returned an indication that IST condition has been withdrawn from the subscriber, IST control for that call in the GMSC is terminated. The IST Alert timer that monitors the activity that initiated the IST Alert is restarted when no call termination indicator has been received in the IST Alert dialogue and the IST Alert response received does not indicate termination of IST condition; the timer value shall be the same as in the previous count, or the new value received in the IST Alert response if any. + +### 6.2.2 Call termination + +The VMSC (current or previous) will inform the HLR about each of the remaining outgoing call activities (MO, CD, ECT and CF) of the subscriber with a IST Alert message. This message contains the IMSI of that subscriber. Each of the originating, deflected, transferred or forwarded calls for a specific subscriber can be terminated in the MSC by returning a call termination indicator from the HLR to the controlling MSC in response to the IST Alert message. The MSC shall then terminate the call activity that initiated the alert, or it may also terminate all call activities for that subscriber if these activities are linked in the MSC. + +The GMSC will inform the HLR about each of the remaining incoming call activities (MT and CF) of the subscriber with a IST Alert message. This message contains the IMSI of that subscriber. Each of the terminating or forwarded calls for a specific subscriber can be terminated in the GMSC by returning a call termination indicator from the HLR to the controlling GMSC in response to the IST Alert message. The GMSC shall then terminate the call activity that initiated the alert, or it may also terminate all call activities for that subscriber if these activities are linked in the GMSC. + +## 6.3 IST standalone mechanism + +In addition to the periodic reporting mechanism, the IST standalone mechanism can optionally be supported in the HLR, the VMSC and the GMSC. This mechanism can be used to immediately terminate all outgoing subscriber + +activities in a VMSC and all incoming subscriber activities in the GMSC even when the subscriber is not under IST condition i.e. the MSC shall be able to terminate the call activities upon reception of the standalone IST command without having any previous IST subscriber settings defined. + +Provided that the MSC/VLR supports IST standalone mechanism, the HLR may request the immediate disconnection of the outgoing calls by sending a MAP Cancel Location message to the current VLR, and afterwards the IST Command message to the current VMSC without waiting for an IST Alert message. + +The HLR may also be able to request the immediate disconnection of outgoing call activities of a subscriber in previous VMSCs; for this purpose, the HLR may maintain a list of previous VMSCs with possibly remaining activities, to which the IST Command message may be sent without waiting for an IST Alert message. The mechanism used to maintain this list is out of the scope of this specification. The HLR may also be able to request the immediate disconnection of incoming call activities of a subscriber in any GMSC that may have requested routeing info from the HLR; for this purpose, the HLR may maintain a list of GMSCs with possibly remaining activities to which the IST Command message may be sent without waiting for an IST Alert message. The mechanism used to maintain this list is outside the scope of this specification. + +The standalone IST Command is used in the MSC to terminate immediately all outgoing call activities for a subscriber. This is only possible if the MSC is able to link all the call activities for the same subscriber using the IMSI as key. Then, when a standalone IST command is received including the IMSI of the subscriber, the MSC can terminate all the outgoing call activities for that subscriber. If the MSC does not support IST standalone mechanism, it shall return an error in response to the HLR. + +The standalone IST Command is used in the GMSC to terminate immediately all incoming call activities for a subscriber. This is only possible if the GMSC is able to link all the call activities for the same subscriber using the IMSI as key. Then, when a standalone IST Command is received including the IMSI of the subscriber, the GMSC can terminate all the incoming call activities for that subscriber. If the GMSC does not support IST standalone mechanism, it shall return an error in response to the HLR. + +## 6.4 Exception procedure + +The MSC/VLR shall inform the HLR about the support of IST function whenever a subscriber roams into that MSC/VLR area. Information about support of the IST standalone mechanism shall also be included. This information shall be included in the Update Location message sent to the HLR. The HLR can use the absence of any of these information to allow alternative actions in HLR in case of interworking with MSC/VLRs not supporting IST. + +The alternative actions when the MSC/VLR does not support the IST function can be, as an operator option: + +- Limit the service for the subscriber: +Activating temporarily an Operator Determined barring of Roaming, Incoming or outgoing calls. +- Allowing the service assuming associate risk of not having the IST mechanism available. + +The GMSC shall inform the HLR about the support of IST function whenever it requests routeing information to establish a call. Information about support of the IST standalone mechanism shall also be included. This information shall be included in the Send Routeing Information message sent to the HLR. The HLR can use the absence of any of these information to allow alternative actions in HLR in case of interworking with GMSCs not supporting IST. + +The alternative actions when the GMSC does not support the IST function can be, as an operator option: + +- Limit the service for the subscriber: +Activating temporarily an Operator Determined barring of incoming calls, deactivate temporarily the Call forwarding services invoked in the GMSC. +- Allowing the service assuming associate risk of not having the IST mechanism available. + +Error responses from HLR are also part of the exception procedures. Whenever the error "Unknown Subscriber" is received from the HLR in response to an IST Alert message, the receiving entity (MSC or GMSC) shall terminate the call that initiated the alert procedure. Also, if the receiving entity is able to link the activities for that subscriber (outgoing call activities in the MSC and incoming call activities in the GMSC), it shall terminate all of them if an "Unknown Subscriber" error is received in response to any IST Alert message. + +# --- 7 Control of IST + +Definition of the method used by a PLMN to decide which subscribers to use IST upon is outside the scope of this specification. However, it is likely that the decision will be made by some sort of FDS within the PLMN. The interface between the FDS and the PLMN node that sends the IST Command message to the VPLMN (the CAMEL server for a CAMEL implementation of IST) is outside the scope of this specification. + +# Annex A (Informative): Change History + +| Change history | | | | | | | | | +|--------------------------------------------------------|-------|-----------|-----|-----|-----|----------------------------------------------------------------------------------------------------------------------|------------------|-------------------| +| Date | TSG # | TSG Doc | CR | Rev | Cat | Subject/Comment | Old | New | +| 03-2001 | SP-11 | - | - | - | - | Upgrade to Release 4 (and 3GPP numbering) | 03.35
v 8.0.0 | 43.035
v 4.0.0 | +| 03-2002 | SP-15 | SP-020113 | 001 | | A | IST implementation for non-CAMEL subscribers | 4.0.0 | 4.1.0 | +| Status of TS 23.035 (Created from TS 43.035 Release 4) | | | | | | | | | +| 06-2002 | SP-16 | - | - | - | - | Decision to transfer IST to 3GPP system specification set.
References corrected to 3GPP specification references. | 43.035
4.1.0 | 23.035
4.0.0 | +| Status of TS 23.035 (Release 5) | | | | | | | | | +| 06-2002 | SP-16 | - | - | - | - | Upgrade to Release 5 | 4.0.0 | 5.0.0 | +| 09-2002 | SP-17 | SP-020509 | 003 | | A | Correction of use IST Command message and Call Termination Indication parameter | 5.0.0 | 5.1.0 | +| 12-2004 | SP-26 | - | - | - | - | Upgrade to Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | SP-36 | - | - | - | - | Upgrade to Release 7 | 6.0.0 | 7.0.0 | +| 12-2008 | SP-42 | - | - | - | - | Upgrade to Release 8 | 7.0.0 | 8.0.0 | +| 12-2009 | SP-46 | - | - | - | - | Upgrade to Release 9 | 8.0.0 | 9.0.0 | +| 2011-03 | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23040/01da0d212fb571933f10f96556157745_img.jpg b/marked/Rel-11/23_series/23040/01da0d212fb571933f10f96556157745_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3340375640e7a2b519ee397977b9addb80429d0 --- /dev/null +++ b/marked/Rel-11/23_series/23040/01da0d212fb571933f10f96556157745_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d30e81ee130fdb3ae1d6565aabb9e2c5aa2cc3fce545551c65a8bfbb70f2e7f1 +size 32736 diff --git a/marked/Rel-11/23_series/23040/07f537f57749b75157f742525e6a8dbc_img.jpg b/marked/Rel-11/23_series/23040/07f537f57749b75157f742525e6a8dbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67c212e4b7392bb0e5d0359d282c63a3f0bde39b --- /dev/null +++ b/marked/Rel-11/23_series/23040/07f537f57749b75157f742525e6a8dbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64a5fbf2417bb227f6659181327fd74b707c1f2f0c091e052e0999f8a765a05f +size 21184 diff --git a/marked/Rel-11/23_series/23040/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg b/marked/Rel-11/23_series/23040/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d69f739143ae814143486d4c7e55447fc2a42b53 --- /dev/null +++ b/marked/Rel-11/23_series/23040/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3403e266b6a799d40504319a990c6c0df8cc5702ade69603efb071c0fbe86239 +size 42846 diff --git a/marked/Rel-11/23_series/23040/10953d657a5f47fdc829a800419dd370_img.jpg b/marked/Rel-11/23_series/23040/10953d657a5f47fdc829a800419dd370_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03b1a55c7497f83a54c0f27c6bb2d75e55f139b8 --- /dev/null +++ b/marked/Rel-11/23_series/23040/10953d657a5f47fdc829a800419dd370_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:257af119c90bfb7cef69fb05694d54d63fe7ca0b4949bd6c6c933e8b1a7eb907 +size 8368 diff --git a/marked/Rel-11/23_series/23040/1517552d07f4a8b389be86af8aff6424_img.jpg b/marked/Rel-11/23_series/23040/1517552d07f4a8b389be86af8aff6424_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c938de3be35bdefa7bbb7c28eec21a334dace93 --- /dev/null +++ b/marked/Rel-11/23_series/23040/1517552d07f4a8b389be86af8aff6424_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0513d274cc897a5ff851799278eb28c01b18b184f0b46961f510217c8839d687 +size 1785 diff --git a/marked/Rel-11/23_series/23040/17b9d89b91e10c3efc38193baedee268_img.jpg b/marked/Rel-11/23_series/23040/17b9d89b91e10c3efc38193baedee268_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa39d51edad0806398d29f5a8b55a3332e2182a8 --- /dev/null +++ b/marked/Rel-11/23_series/23040/17b9d89b91e10c3efc38193baedee268_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e68811d10048e4472768642c6daf4a2829cb5ada04503ec32de4d4b46d8f79d +size 18811 diff --git a/marked/Rel-11/23_series/23040/184d3d9a856c77aae93652f4fe30f752_img.jpg b/marked/Rel-11/23_series/23040/184d3d9a856c77aae93652f4fe30f752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dab8d8f8919ccd37e0ca3414484e9afac3497738 --- /dev/null +++ b/marked/Rel-11/23_series/23040/184d3d9a856c77aae93652f4fe30f752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdfbcce73f36d6b2711531206137d98a005305e608463cfc0213e5bb71b146a5 +size 51846 diff --git a/marked/Rel-11/23_series/23040/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/23_series/23040/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bf37df5478dc0d2b88a195574720c4a18373c9b --- /dev/null +++ b/marked/Rel-11/23_series/23040/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:866e1de469d1d280bb80aa45670337d3f1c6a33359a7374a8aa4ef4b3a9b1d01 +size 113554 diff --git a/marked/Rel-11/23_series/23040/1b896a95bc9974ad01fac7ac6f541a96_img.jpg b/marked/Rel-11/23_series/23040/1b896a95bc9974ad01fac7ac6f541a96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..027faafff14a1d36ee646c437a8ba6a04aa826f4 --- /dev/null +++ b/marked/Rel-11/23_series/23040/1b896a95bc9974ad01fac7ac6f541a96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2215826263bd406900353ef92f399cc6e03a79dac87c62d1be31a07f66c3c63 +size 18280 diff --git a/marked/Rel-11/23_series/23040/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg b/marked/Rel-11/23_series/23040/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0ef5ac29047a610561ad9654db6bedf9010b0dd --- /dev/null +++ b/marked/Rel-11/23_series/23040/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20d6c96d131adf6cb59c0ad35cb8d916fcb0d425decbfd4a281a159a2736bb5c +size 65752 diff --git a/marked/Rel-11/23_series/23040/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/marked/Rel-11/23_series/23040/1c953f32bd34345dfd68fddf8a3736d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a699305dd84f27134a63cb426c203516388e461 --- /dev/null +++ b/marked/Rel-11/23_series/23040/1c953f32bd34345dfd68fddf8a3736d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48117beb3519fec6be6d9588cc5a3fa19ba3ea051a0b0097c2580255539a6c2e +size 40408 diff --git a/marked/Rel-11/23_series/23040/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/marked/Rel-11/23_series/23040/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cc7f8473a2809c3f0e8519f11119aea079bf69b --- /dev/null +++ b/marked/Rel-11/23_series/23040/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:479d13f2e9a0a4de7b82f3c669ac659ac5ab471eac89ca8bb4296bebe1ed76ef +size 41441 diff --git a/marked/Rel-11/23_series/23040/24029b85683e6c5b14e96022cd9b6ff6_img.jpg b/marked/Rel-11/23_series/23040/24029b85683e6c5b14e96022cd9b6ff6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2362ac20373d591a27e4e69cd85aa1c39c466618 --- /dev/null +++ b/marked/Rel-11/23_series/23040/24029b85683e6c5b14e96022cd9b6ff6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:944f57a1c2f99bde70d5e46a5e5851c36dc2fd9d6111bd214fee6e8e84c1ad54 +size 58390 diff --git a/marked/Rel-11/23_series/23040/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23040/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff0f8abfadada727d98a5f93cd506a51393b6c17 --- /dev/null +++ b/marked/Rel-11/23_series/23040/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5250f1eefdaed82c440ca598305f02430df58cdb907ac1ee982368aa953ee7fe +size 93033 diff --git a/marked/Rel-11/23_series/23040/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Rel-11/23_series/23040/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a221243b79e1d458bb39f99db79128758bf61bd --- /dev/null +++ b/marked/Rel-11/23_series/23040/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c2114e92e95df1b11f6aedc4e669f024076783bc5de9dc0dffd6818dc6ce90a +size 66711 diff --git a/marked/Rel-11/23_series/23040/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/23_series/23040/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f9ba9c74b2e2e8af0c55015d3aa36ad4bbfa1fa --- /dev/null +++ b/marked/Rel-11/23_series/23040/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc7b992b2eb2749fb8a89c4bdc2febffdd802a415bd535ffed501d6c455d22db +size 5531 diff --git a/marked/Rel-11/23_series/23040/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-11/23_series/23040/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fcff84f9a13880fab5d75a661947a148237353b --- /dev/null +++ b/marked/Rel-11/23_series/23040/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f4a0295f41788019fd0ced3466acafd6da61e5beccfeee50b530c7d0da524da +size 47104 diff --git a/marked/Rel-11/23_series/23040/373e2ccc5c19a052a1b8cb6de3eebc94_img.jpg b/marked/Rel-11/23_series/23040/373e2ccc5c19a052a1b8cb6de3eebc94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..862f7927096a74bd89362d9ca8a747ac983a2914 --- /dev/null +++ b/marked/Rel-11/23_series/23040/373e2ccc5c19a052a1b8cb6de3eebc94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7594b7e97ad51491744e58cb8a414a228921e9aaa15bce35f91cded0539eac4c +size 1679 diff --git a/marked/Rel-11/23_series/23040/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-11/23_series/23040/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98deb4d710d0e271157962422d1da468a9a2a44d --- /dev/null +++ b/marked/Rel-11/23_series/23040/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d2167ded1cbc27c07ab727657563cec1cb58f85909947aae76728ab089b26e8 +size 84663 diff --git a/marked/Rel-11/23_series/23040/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-11/23_series/23040/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8735f14980da35f4cda233fce81f42ace3b019d5 --- /dev/null +++ b/marked/Rel-11/23_series/23040/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6d32393d72b9ab6b1172b07c0fa42058db67ee94f0792964b9736e88bec8915 +size 37650 diff --git a/marked/Rel-11/23_series/23040/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/Rel-11/23_series/23040/409498e57b1f988b2b604d12cd997002_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..986618364aac7a83a41e2d8136b0837f3fbbd0f0 --- /dev/null +++ b/marked/Rel-11/23_series/23040/409498e57b1f988b2b604d12cd997002_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb4a127677e6ba59345a300f0e39e837b61a34530956c767de812e74736aa0b0 +size 3234 diff --git a/marked/Rel-11/23_series/23040/4540c7355b250cb891be0b54b0ba25c7_img.jpg b/marked/Rel-11/23_series/23040/4540c7355b250cb891be0b54b0ba25c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..beea35e178fc4689339f6f1f120778ac7169ecff --- /dev/null +++ b/marked/Rel-11/23_series/23040/4540c7355b250cb891be0b54b0ba25c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e102797dd0c36233bdb0183a976a3a33d5aeac9a6d4ae3c0e96642008324d6d1 +size 19092 diff --git a/marked/Rel-11/23_series/23040/475caf31ae90b878f12d651b689cc9d1_img.jpg b/marked/Rel-11/23_series/23040/475caf31ae90b878f12d651b689cc9d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29ad8cb3c5c5ca0103f024ff8374c3e5c768fc9b --- /dev/null +++ b/marked/Rel-11/23_series/23040/475caf31ae90b878f12d651b689cc9d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:167386bb81bb4c9d190e6ae6708b81c1372596a7e7d8a4cd44cf149dfcd9506b +size 4996 diff --git a/marked/Rel-11/23_series/23040/4792a2ccd62226861fadc22117edb7b1_img.jpg b/marked/Rel-11/23_series/23040/4792a2ccd62226861fadc22117edb7b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8d95629ef9835d8976d35d67d89d3ef7240c616 --- /dev/null +++ b/marked/Rel-11/23_series/23040/4792a2ccd62226861fadc22117edb7b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ad3032ad8253f7f41af65815e648666ad1bf3f7316feaf2fe4e53498f4880ea +size 112926 diff --git a/marked/Rel-11/23_series/23040/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-11/23_series/23040/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cf18df725653979d9e2230369c6ef58cf04b272 --- /dev/null +++ b/marked/Rel-11/23_series/23040/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65118aa05a165d5ff1bd080b58116133e5929bfc7bed5e8a10883d25d377cbbe +size 51671 diff --git a/marked/Rel-11/23_series/23040/4d5d6207a6d444ae745057ebc3ddcd86_img.jpg b/marked/Rel-11/23_series/23040/4d5d6207a6d444ae745057ebc3ddcd86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f0c659611f148d6eb24d6314ae1a09ced31cd9f --- /dev/null +++ b/marked/Rel-11/23_series/23040/4d5d6207a6d444ae745057ebc3ddcd86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e65e87decb37fc107acf578a4e0129c5ce8ac7d9aaf14dcc6b07cdd2ebffa468 +size 48904 diff --git a/marked/Rel-11/23_series/23040/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/Rel-11/23_series/23040/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..524d7deef1575662cb6258cf6e49658304919f2f --- /dev/null +++ b/marked/Rel-11/23_series/23040/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03b118cc1a91cc8791483c07a671803ceb726f512957b9abc7aadcae91eaacbc +size 50184 diff --git a/marked/Rel-11/23_series/23040/58bbc570572758132ea39938e4f03b5b_img.jpg b/marked/Rel-11/23_series/23040/58bbc570572758132ea39938e4f03b5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09d783bc91d707dda4ab945678a72af33a8c180a --- /dev/null +++ b/marked/Rel-11/23_series/23040/58bbc570572758132ea39938e4f03b5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a39c133bc30d0c67761626c35668ed96b0ae536375e5b75a206741d826b0f006 +size 33732 diff --git a/marked/Rel-11/23_series/23040/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/23_series/23040/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..642a0d48b5a65b24d1426041f61b217eaed56ed2 --- /dev/null +++ b/marked/Rel-11/23_series/23040/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a4560cd20954ec76a4649a58c487f10cc4100edb256aa87c5770c9dabc17498 +size 116135 diff --git a/marked/Rel-11/23_series/23040/5f9ca30b158bcba2f401ed8da6e72c00_img.jpg b/marked/Rel-11/23_series/23040/5f9ca30b158bcba2f401ed8da6e72c00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81aaa0d4496698aaabdb9a75a3807c1a3793a350 --- /dev/null +++ b/marked/Rel-11/23_series/23040/5f9ca30b158bcba2f401ed8da6e72c00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e87cd7f84e530452cfde34ccbc127fb57a67bdde9f5b6aa6588f8e479a6f930a +size 6185 diff --git a/marked/Rel-11/23_series/23040/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg b/marked/Rel-11/23_series/23040/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3019c803cb89f035dede10fc3fc4af0ecdb1502b --- /dev/null +++ b/marked/Rel-11/23_series/23040/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87b918be1cb30dd763c1e6e270f7e888121b69737b4ccd960e337a9107590205 +size 82359 diff --git a/marked/Rel-11/23_series/23040/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Rel-11/23_series/23040/69edc2887e907309499ac95b47ab6905_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adede1f12684cb9c06551f6d2af7b6ae4a901ae8 --- /dev/null +++ b/marked/Rel-11/23_series/23040/69edc2887e907309499ac95b47ab6905_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c090b3677d8831eb720c88f16aa086ec8b7daf0af4e8b602235c60ce6088a81b +size 117648 diff --git a/marked/Rel-11/23_series/23040/762a17cd79880dbca172bcbbe9375223_img.jpg b/marked/Rel-11/23_series/23040/762a17cd79880dbca172bcbbe9375223_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..555f6fd84f460fbe63e0533e9609de14c41005c6 --- /dev/null +++ b/marked/Rel-11/23_series/23040/762a17cd79880dbca172bcbbe9375223_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3cf8246e86dfd03035a3d776e03be8b624b4aa8bc93da270bced082e7426a50 +size 34255 diff --git a/marked/Rel-11/23_series/23040/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg b/marked/Rel-11/23_series/23040/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87a53b235e0b647e215771ba8337ed8c1f7ae074 --- /dev/null +++ b/marked/Rel-11/23_series/23040/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5b241fa7da661390f656b127cf6be8fa73072737c9a6b949e2a996f295e1678 +size 80224 diff --git a/marked/Rel-11/23_series/23040/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23040/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2906fd40f4cd5fa5d22762ac69f7463e9d81ba6f --- /dev/null +++ b/marked/Rel-11/23_series/23040/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c751904d934a85b5186aa6172bfd5edf2743d5d6baafc45a8d40d7c7ddc892e +size 70790 diff --git a/marked/Rel-11/23_series/23040/820515db47ded68f5e0b625f4ec7d2c1_img.jpg b/marked/Rel-11/23_series/23040/820515db47ded68f5e0b625f4ec7d2c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3f6c03369b005c83b54753e16e57396c285d44d --- /dev/null +++ b/marked/Rel-11/23_series/23040/820515db47ded68f5e0b625f4ec7d2c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee7cea5cd09dbbcfcbfa529835febf012f7feee9568027b7e7fa77170718b130 +size 46059 diff --git a/marked/Rel-11/23_series/23040/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/23_series/23040/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b9677d474d352b4f6b2f8780c774f9c820b1a8c --- /dev/null +++ b/marked/Rel-11/23_series/23040/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95308a3cfa3192db2952b97d54c195d6534eea9974d98fcba15d6f5fe5663678 +size 100406 diff --git a/marked/Rel-11/23_series/23040/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg b/marked/Rel-11/23_series/23040/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6224b1857aa325639a50b62668e8e84734a9785 --- /dev/null +++ b/marked/Rel-11/23_series/23040/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ac411bc0b1c0de39037c982ba7b4b8c9cd49bb657ee940b34425ab46c4ca164 +size 49984 diff --git a/marked/Rel-11/23_series/23040/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Rel-11/23_series/23040/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6b0f47e826a21de31d8d7ec346900bd37ab41a3 --- /dev/null +++ b/marked/Rel-11/23_series/23040/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29b21d8988f17187c3cfc50b7f61f73464bbba20fe6cd1b04bfa5f1536ba1596 +size 98264 diff --git a/marked/Rel-11/23_series/23040/895d588a848d9963890c938763de9ecf_img.jpg b/marked/Rel-11/23_series/23040/895d588a848d9963890c938763de9ecf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..720a410eaacc429305bda170afaef65d647877db --- /dev/null +++ b/marked/Rel-11/23_series/23040/895d588a848d9963890c938763de9ecf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f935bbed24e4c32d353ca5544456bd044b691b91203c4ed258c05bdde4e5d5ee +size 20192 diff --git a/marked/Rel-11/23_series/23040/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-11/23_series/23040/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eea3336d545f96c99c1a901e77dc446ab8833a3a --- /dev/null +++ b/marked/Rel-11/23_series/23040/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50da77bd289835780242c6213af554ddddab1d3b983cafd061234c1ca91814c0 +size 68907 diff --git a/marked/Rel-11/23_series/23040/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/Rel-11/23_series/23040/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d5a684f45c3aa3315142cbc8e3bacca14bdba2c --- /dev/null +++ b/marked/Rel-11/23_series/23040/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b7bc0ec085582d44c477bc4b2dacf14897d3ac047d8a166053d21c0d83d83a1 +size 24380 diff --git a/marked/Rel-11/23_series/23040/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-11/23_series/23040/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77c08c72f7ac5627c45b1b94029d241699016d57 --- /dev/null +++ b/marked/Rel-11/23_series/23040/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bc6c1080742d2b338afec0f88e8bf448e15efd468f4095f80c2d8a2325adbda +size 105174 diff --git a/marked/Rel-11/23_series/23040/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-11/23_series/23040/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..275649fc46eafb6f9972a7bf5279727d287c6499 --- /dev/null +++ b/marked/Rel-11/23_series/23040/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cd64ea7b322a2068dc6abcc0a614bc14d2d707e1136b319ff7ff7c2128a30bd +size 67432 diff --git a/marked/Rel-11/23_series/23040/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/23_series/23040/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f7367b9cba495b2cb6fb801c45e6d6c33248a27 --- /dev/null +++ b/marked/Rel-11/23_series/23040/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:695270fc53717b5b3e8d1e5d7506f17ba3eac6558c94c262c4f44d08c49ec3ca +size 90857 diff --git a/marked/Rel-11/23_series/23040/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/23_series/23040/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb76f71ff770e5638126bd4dd4c009841456e934 --- /dev/null +++ b/marked/Rel-11/23_series/23040/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e12f8c9445cfd20491d5abab02301c1ab3cef06ca565c1d64b22a030c45bebe +size 53949 diff --git a/marked/Rel-11/23_series/23040/a6a8016b231533e7f34b550f4676afc6_img.jpg b/marked/Rel-11/23_series/23040/a6a8016b231533e7f34b550f4676afc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d20bd6d47a913beadfe06b2c06ff8ba6361dd85 --- /dev/null +++ b/marked/Rel-11/23_series/23040/a6a8016b231533e7f34b550f4676afc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f18fc378e8b4fa3f4902203908abf8480e73736dd9f49da1e0963b2795852d00 +size 34532 diff --git a/marked/Rel-11/23_series/23040/a78db21022e0687c18d97ed547dd7ecb_img.jpg b/marked/Rel-11/23_series/23040/a78db21022e0687c18d97ed547dd7ecb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cda81fc1576d78aab54e9eab256c0233798ba8e6 --- /dev/null +++ b/marked/Rel-11/23_series/23040/a78db21022e0687c18d97ed547dd7ecb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9862711b662446672cffd02e83d3af7e02224d31cfee892f839c27d5251a636f +size 11166 diff --git a/marked/Rel-11/23_series/23040/a798c1bd0503d58906cf07d55f80ab83_img.jpg b/marked/Rel-11/23_series/23040/a798c1bd0503d58906cf07d55f80ab83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d42c940599dececd23e6c95824bcfda3dc78848e --- /dev/null +++ b/marked/Rel-11/23_series/23040/a798c1bd0503d58906cf07d55f80ab83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0767e4dd59878b609bc9b765ff3699dc1c4f24ec62e0de54187a0cb5f188c1b4 +size 47568 diff --git a/marked/Rel-11/23_series/23040/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-11/23_series/23040/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9db0927dd8247b1d722490b68c60f873dad764b0 --- /dev/null +++ b/marked/Rel-11/23_series/23040/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e735a61bd56caab8131c437bb438de64373c2806f644c5904f2201e74f5c4b2 +size 10600 diff --git a/marked/Rel-11/23_series/23040/aa81b9b80bd1e3d723922b3a033564a2_img.jpg b/marked/Rel-11/23_series/23040/aa81b9b80bd1e3d723922b3a033564a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..053d69e272b03540d2cf13ca08b6fbdc7e97978c --- /dev/null +++ b/marked/Rel-11/23_series/23040/aa81b9b80bd1e3d723922b3a033564a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed694105426b834353662739fe4e92d60dacdb992e42d13b1c8a46f69853f282 +size 130764 diff --git a/marked/Rel-11/23_series/23040/ae375ead8aa673286b534e079e9a8533_img.jpg b/marked/Rel-11/23_series/23040/ae375ead8aa673286b534e079e9a8533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dba4e739cb2da4338efdf6dc86f0d3e825e97cd --- /dev/null +++ b/marked/Rel-11/23_series/23040/ae375ead8aa673286b534e079e9a8533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6dbe2ca5eb23d85bfed3f56cfce6d1cd98ef4cad7b63ca29f3c6fe664c24409 +size 37598 diff --git a/marked/Rel-11/23_series/23040/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23040/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c070d2f5d1ff3e3226664272b95164bffc175be5 --- /dev/null +++ b/marked/Rel-11/23_series/23040/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2191ca8860223a1ccec4d8554c9f102bbb0f91fedda0d7d2ecd1f07b517eb8b0 +size 93063 diff --git a/marked/Rel-11/23_series/23040/b43872c7a81f62572f3be03b77d8655f_img.jpg b/marked/Rel-11/23_series/23040/b43872c7a81f62572f3be03b77d8655f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d208a99e242f780b7eb07c8282006fa4d321f84 --- /dev/null +++ b/marked/Rel-11/23_series/23040/b43872c7a81f62572f3be03b77d8655f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dcd75d364f5352f30d2b872370e70de3f5ee855c2a3426d8a4250e14bfd2b2a +size 54402 diff --git a/marked/Rel-11/23_series/23040/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/23_series/23040/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83a1bca8397b6e7492f078fa7beaba9cb5eb13e1 --- /dev/null +++ b/marked/Rel-11/23_series/23040/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e356fd734518b82acc5bb7c3636b52cc2d572afbe7b22ad47d0d82ecee5c5f7 +size 21897 diff --git a/marked/Rel-11/23_series/23040/b737358d3f26d530ace7882e75a05a47_img.jpg b/marked/Rel-11/23_series/23040/b737358d3f26d530ace7882e75a05a47_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..462301559b7537313a9d5b8f1feaed24a70d1b75 --- /dev/null +++ b/marked/Rel-11/23_series/23040/b737358d3f26d530ace7882e75a05a47_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:029503a72595cc3fae165e877132861d6d12dc5030ab7730870d180ceca11a19 +size 6952 diff --git a/marked/Rel-11/23_series/23040/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-11/23_series/23040/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a367bc2a8a94780941c777b179d6aee7d8db67de --- /dev/null +++ b/marked/Rel-11/23_series/23040/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fe789b89e3b2d664ba8d4351dff69bba19fc1432524d09050990a1659c78538 +size 73187 diff --git a/marked/Rel-11/23_series/23040/bc4b03830125f24f55b78ce2a3558887_img.jpg b/marked/Rel-11/23_series/23040/bc4b03830125f24f55b78ce2a3558887_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7dc8c3a7dee77291c41500c2e3b7e344d38cfd94 --- /dev/null +++ b/marked/Rel-11/23_series/23040/bc4b03830125f24f55b78ce2a3558887_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1070ea888c47586058f6c9e69ffd3cecb59ce7cd79d1058d12cc6b45714f4779 +size 6724 diff --git a/marked/Rel-11/23_series/23040/bd8e3fb102fd14e1edbc62f149241842_img.jpg b/marked/Rel-11/23_series/23040/bd8e3fb102fd14e1edbc62f149241842_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c348d8199ef0c5b69493574d41a4e1695e34aea8 --- /dev/null +++ b/marked/Rel-11/23_series/23040/bd8e3fb102fd14e1edbc62f149241842_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11b348deff3a0651b46854b3b47e521af475d89a081cd2c9a8b23cac8ae3bb62 +size 8635 diff --git a/marked/Rel-11/23_series/23040/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-11/23_series/23040/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4eb26bc2aa83982d586683d13d53a42d8f9911c --- /dev/null +++ b/marked/Rel-11/23_series/23040/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82ba7ed8021663108f517d763d144fca05f265d2386279e5e1e5659ff19067b8 +size 73000 diff --git a/marked/Rel-11/23_series/23040/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-11/23_series/23040/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26821e3b18a4ae65c219f87b9503a3b7b2cb4813 --- /dev/null +++ b/marked/Rel-11/23_series/23040/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09752817cae572a09485d0a4cd8310ade88b5eea48c5b6e1d6f13f01b677ef72 +size 84186 diff --git a/marked/Rel-11/23_series/23040/d3ca266c298aeb34b019960c6c36f187_img.jpg b/marked/Rel-11/23_series/23040/d3ca266c298aeb34b019960c6c36f187_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31108bd6cf24247edf3d1409b0c16947fa4f5fe6 --- /dev/null +++ b/marked/Rel-11/23_series/23040/d3ca266c298aeb34b019960c6c36f187_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee85837a24e026db9240782d3ce32b75cb77d7f121b60d1273b0bbff8d056ecd +size 120694 diff --git a/marked/Rel-11/23_series/23040/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-11/23_series/23040/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a40b3c26a265e64c634647d94dab097240af9fd5 --- /dev/null +++ b/marked/Rel-11/23_series/23040/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38bbfce9a0e8d9a955385a2f6deada2f22ce97b0fa290fa5807dd3acdf57b657 +size 34785 diff --git a/marked/Rel-11/23_series/23040/dcf83796ccf494110638fbd4677b931d_img.jpg b/marked/Rel-11/23_series/23040/dcf83796ccf494110638fbd4677b931d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b08a67318da60fbdc4aaec887a716f58adb8bf3 --- /dev/null +++ b/marked/Rel-11/23_series/23040/dcf83796ccf494110638fbd4677b931d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1242692ac7b61f229cb6dea74d8ab41c86d21aceaf595788d5cddd7aba6325b4 +size 72520 diff --git a/marked/Rel-11/23_series/23040/df935fc9efbd024af4ba77e46bb0bb19_img.jpg b/marked/Rel-11/23_series/23040/df935fc9efbd024af4ba77e46bb0bb19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bca172f9f96d2fb076eb9f3ac1542b6f90af0b0b --- /dev/null +++ b/marked/Rel-11/23_series/23040/df935fc9efbd024af4ba77e46bb0bb19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b15d4725cd6f3ad43bf49ee0ccbaa0bcf9fc9a1a1cfb341015601ad40dacf46c +size 52535 diff --git a/marked/Rel-11/23_series/23040/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/23_series/23040/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..937c375b91f129b9b7b7f58404d3570f3a0f64c6 --- /dev/null +++ b/marked/Rel-11/23_series/23040/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bbc978a61097b22b9a3ed3b4fd9774d87c220722e011506b562216d0c134cdb +size 28256 diff --git a/marked/Rel-11/23_series/23040/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-11/23_series/23040/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..819845289ec8b2d07ac851d91d83ee92fd095c72 --- /dev/null +++ b/marked/Rel-11/23_series/23040/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be04a182302984a6f0cf70fd55a1259b193fc8c1819329132f9fc4d059e0b9fc +size 133565 diff --git a/marked/Rel-11/23_series/23040/f89631cc38aa971e8d15cbffe28f1183_img.jpg b/marked/Rel-11/23_series/23040/f89631cc38aa971e8d15cbffe28f1183_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7537b1960a6f33db3e19e7e71e4f05ed795bae8 --- /dev/null +++ b/marked/Rel-11/23_series/23040/f89631cc38aa971e8d15cbffe28f1183_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:882f79b44b2120ce9af68caae08cf9fd366bbba1e77c5d03b18553fa2bee447a +size 35353 diff --git a/marked/Rel-11/23_series/23040/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23040/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb5b765f54a3b69c0d78dd31c78e7093bd18bd8d --- /dev/null +++ b/marked/Rel-11/23_series/23040/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1381c01643a18e17fd9e1003cb6461063a4f40079ce4cb261d593d4640bdb83 +size 105655 diff --git a/marked/Rel-11/23_series/23040/raw.md b/marked/Rel-11/23_series/23040/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4d50d3abe8a068f7532219c839b1fc8e883c02e0 --- /dev/null +++ b/marked/Rel-11/23_series/23040/raw.md @@ -0,0 +1,8157 @@ +# Contents + +| | | +|-----------------------------------------------------------------------------------------|----| +| Foreword..... | 9 | +| Introduction..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 2.1 Definitions and abbreviations..... | 12 | +| 2.1.1 Definitions..... | 12 | +| 2.1.2 Abbreviations..... | 15 | +| 3 Services and service elements..... | 15 | +| 3.1 Basic services..... | 15 | +| 3.2 Short Message Service elements..... | 17 | +| 3.2.0 Introduction..... | 17 | +| 3.2.1 Validity-Period..... | 17 | +| 3.2.2 Service-Centre-Time-Stamp..... | 17 | +| 3.2.3 Protocol-Identifier..... | 17 | +| 3.2.4 More-Messages-to-Send..... | 17 | +| 3.2.5 Delivery of Priority and non-Priority Messages..... | 17 | +| 3.2.6 Messages-Waiting..... | 18 | +| 3.2.7 Alert-SC..... | 21 | +| 3.2.7a MT Correlation ID..... | 21 | +| 3.2.8 Options concerning MNRG, MNRF, UNRI, MNRR-MSC, MNRR-SGSN, UNRR, MCEF and MWD..... | 22 | +| 3.2.9 Status report capabilities..... | 23 | +| 3.2.10 Reply Path..... | 24 | +| 3.3 Unsuccessful short message TPDU transfer SC -> MS..... | 24 | +| 3.3.1 Errors occurring during transfer of TPDU to MS..... | 24 | +| 3.3.2 Errors occurring after TPDU arrives at MS..... | 24 | +| 3.4 Unsuccessful short message TPDU transfer MS -> SC..... | 26 | +| 3.4.1 Errors occurring during transfer of TPDU to SC..... | 26 | +| 3.4.2 Errors occurring after TPDU arrives at SC..... | 26 | +| 3.5 Use of Supplementary Services in combination with the Short Message Service..... | 26 | +| 3.6 Applicability of Operator Determined Barring to the Short Message Service..... | 27 | +| 3.7 Multiple short message transfer..... | 27 | +| 3.8 SMS and Internet Electronic Mail interworking..... | 27 | +| 3.8.1 Basic Format..... | 27 | +| 3.8.2 Optional Fields..... | 28 | +| 3.8.2.1 Subject..... | 28 | +| 3.8.2.2 Real Name..... | 28 | +| 3.8.2.3 Optional Control Flag..... | 28 | +| 3.8.3 Text concatenation..... | 29 | +| 3.8.4 Alternative characters for Internet email addresses in MO SMS..... | 29 | +| 3.9 SMS COMPRESSION..... | 29 | +| 3.10 Enhanced Messaging Service..... | 30 | +| 3.10.1 Text formatting..... | 30 | +| 3.10.2 Pictures..... | 31 | +| 3.10.3 Animations..... | 31 | +| 3.10.4 Sound..... | 31 | +| 3.10.5 vCard and vCalendar..... | 31 | +| 3.10.6 WVG (Wireless Vector Graphics) Object..... | 31 | +| 3.10.6.1 Overview of WVG Graphical Primitives..... | 32 | +| 4 Network architecture..... | 32 | +| 4.1 Basic network structure..... | 32 | +| 4.2 Transfer on reference point 3..... | 33 | +| 5 Service Centre and PLMN interconnection..... | 34 | +| 5.1 Service centre connection..... | 34 | +| 5.2 Routing requirements..... | 34 | + +| | | | +|------------|-------------------------------------------------------------|----| +| 5.2.1 | Mobile terminated short message..... | 34 | +| 5.2.2 | Mobile originated short message..... | 34 | +| 6 | Service Centre functionality..... | 35 | +| 6.1 | Service Centre capabilities..... | 35 | +| 6.2 | SC functional requirements..... | 35 | +| 6.2.1 | Subaddressing support..... | 35 | +| 6.2.2 | Support for trigger SMS filtering for Tsms submissions..... | 36 | +| 6.3 | SC EMS Extended Object Data Request Command Feature..... | 36 | +| 7 | MS functionality..... | 36 | +| 7.1 | MS capabilities..... | 36 | +| 7.2 | MS configuration..... | 36 | +| 8 | Node functionality..... | 37 | +| 8.1 | Node functionality related to SM MT..... | 37 | +| 8.1.1 | Functionality of the SMS-GMSC..... | 37 | +| 8.1.2 | Functionality of the MSC..... | 39 | +| 8.1.3 | Functionality of the SGSN..... | 39 | +| 8.1.4 | Functionality of the SMS Router..... | 40 | +| 8.1.5 | Functionality of the IP-SM-GW..... | 42 | +| 8.2 | Node functionality related to SM MO..... | 42 | +| 8.2.1 | Functionality of the MSC..... | 42 | +| 8.2.2 | Functionality of the SMS-IWMSC..... | 42 | +| 8.2.3 | Functionality of the SGSN..... | 43 | +| 8.2.4 | Functionality of the IP-SM-GW..... | 43 | +| 8.3 | SMS-IWMSC functionality related to alerting..... | 44 | +| 9 | Protocols and protocol architecture..... | 44 | +| 9.1 | Protocol element features..... | 44 | +| 9.1.1 | Octet and Bit transmission order..... | 44 | +| 9.1.2 | Numeric and alphanumeric representation..... | 44 | +| 9.1.2.1 | Integer representation..... | 45 | +| 9.1.2.2 | Octet representation..... | 45 | +| 9.1.2.3 | Semi-octet representation..... | 46 | +| 9.1.2.4 | Alphanumeric representation..... | 46 | +| 9.1.2.5 | Address fields..... | 46 | +| 9.2 | Service provided by the SM-TL..... | 48 | +| 9.2.1 | General..... | 48 | +| 9.2.2 | PDU Type repertoire at SM-TL..... | 48 | +| 9.2.2.1 | SMS-DELIVER type..... | 49 | +| 9.2.2.1a | SMS-DELIVER-REPORT type..... | 51 | +| 9.2.2.2 | SMS-SUBMIT type..... | 53 | +| 9.2.2.2a | SMS-SUBMIT-REPORT type..... | 55 | +| 9.2.2.3 | SMS-STATUS-REPORT type..... | 57 | +| 9.2.2.4 | SMS-COMMAND type..... | 59 | +| 9.2.3 | Definition of the TPDU parameters..... | 60 | +| 9.2.3.1 | TP-Message-Type-Indicator (TP-MTI)..... | 60 | +| 9.2.3.2 | TP-More-Messages-to-Send (TP-MMS)..... | 60 | +| 9.2.3.3 | TP-Validity-Period-Format (TP-VPF)..... | 61 | +| 9.2.3.4 | TP-Status-Report-Indication (TP-SRI)..... | 61 | +| 9.2.3.5 | TP-Status-Report-Request (TP-SRR)..... | 61 | +| 9.2.3.6 | TP-Message-Reference (TP-MR)..... | 61 | +| 9.2.3.7 | TP-Originating-Address (TP-OA)..... | 62 | +| 9.2.3.8 | TP-Destination-Address (TP-DA)..... | 62 | +| 9.2.3.9 | TP-Protocol-Identifier (TP-PID)..... | 62 | +| 9.2.3.10 | TP-Data-Coding-Scheme (TP-DCS)..... | 64 | +| 9.2.3.11 | TP-Service-Centre-Time-Stamp (TP-SCTS)..... | 64 | +| 9.2.3.12 | TP-Validity-Period (TP-VP)..... | 65 | +| 9.2.3.12.1 | TP-VP (Relative format)..... | 65 | +| 9.2.3.12.2 | TP-VP (Absolute format)..... | 65 | +| 9.2.3.12.3 | TP-VP (Enhanced format)..... | 65 | +| 9.2.3.13 | TP-Discharge-Time (TP-DT)..... | 66 | + +| | | | +|--------------------|----------------------------------------------------------------------|-----| +| 9.2.3.14 | TP-Recipient-Address (TP-RA)..... | 66 | +| 9.2.3.15 | TP-Status (TP-ST)..... | 66 | +| 9.2.3.16 | TP-User-Data-Length (TP-UDL)..... | 67 | +| 9.2.3.17 | TP-Reply-Path (TP-RP)..... | 68 | +| 9.2.3.18 | TP-Message-Number (TP-MN)..... | 68 | +| 9.2.3.19 | TP-Command-Type (TP-CT)..... | 68 | +| 9.2.3.20 | TP-Command-Data-Length (TP-CDL)..... | 68 | +| 9.2.3.21 | TP-Command-Data (TP-CD)..... | 69 | +| 9.2.3.22 | TP-Failure-Cause (TP-FCS)..... | 69 | +| 9.2.3.23 | TP-User-Data-Header-Indicator (TP-UDHI)..... | 70 | +| 9.2.3.24 | TP-User Data (TP-UD)..... | 70 | +| 9.2.3.24.1 | Concatenated Short Messages..... | 74 | +| 9.2.3.24.2 | Special SMS Message Indication..... | 75 | +| 9.2.3.24.3 | Application Port Addressing 8 bit address..... | 77 | +| 9.2.3.24.4 | Application Port Addressing 16 bit address..... | 77 | +| 9.2.3.24.5 | SMSC Control Parameters..... | 78 | +| 9.2.3.24.6 | UDH Source Indicator..... | 79 | +| 9.2.3.24.7 | (U)SIM Toolkit Security Headers..... | 79 | +| 9.2.3.24.8 | Concatenated short messages, 16-bit reference number..... | 79 | +| 9.2.3.24.9 | Wireless Control Message Protocol..... | 80 | +| 9.2.3.24.10 | Enhanced Messaging Service..... | 81 | +| 9.2.3.24.10.1 | EMS Coding..... | 81 | +| 9.2.3.24.10.1.1 | Text Formatting..... | 81 | +| 9.2.3.24.10.1.2 | Predefined Sound..... | 83 | +| 9.2.3.24.10.1.3 | User Defined Sound..... | 83 | +| 9.2.3.24.10.1.4 | Predefined Animation..... | 83 | +| 9.2.3.24.10.1.5 | Large Animation..... | 83 | +| 9.2.3.24.10.1.6 | Small Animation..... | 83 | +| 9.2.3.24.10.1.7 | Large Picture..... | 84 | +| 9.2.3.24.10.1.8 | Small Picture..... | 84 | +| 9.2.3.24.10.1.9 | Variable Picture..... | 84 | +| 9.2.3.24.10.1.10 | User Prompt Indicator..... | 84 | +| 9.2.3.24.10.1.11 | Standard WVG Object..... | 85 | +| 9.2.3.24.10.1.12 | Character Size WVG Object..... | 85 | +| 9.2.3.24.10.1.13 | Extended Object..... | 86 | +| 9.2.3.24.10.1.14 | Reused Extended Object..... | 88 | +| 9.2.3.24.10.1.15 | Compression Control..... | 88 | +| 9.2.3.24.10.1.15.1 | LZSS Implementation for EMS extended object compression..... | 90 | +| 9.2.3.24.10.1.15.2 | Data Compression..... | 92 | +| 9.2.3.24.10.1.15.3 | Data De-compression..... | 92 | +| 9.2.3.24.10.1.15.4 | Test Vectors..... | 93 | +| 9.2.3.24.10.1.16 | Object Distribution Indicator..... | 93 | +| 9.2.3.24.10.1.17 | Reply Address Element..... | 93 | +| 9.2.3.24.10.1.18 | Extended Object Data Request Command..... | 94 | +| 9.2.3.24.10.2.1 | Example of Basic text formatting and predefined EMS coding..... | 94 | +| 9.2.3.24.10.2.2 | Example of User defined Objects EMS coding..... | 95 | +| 9.2.3.24.10.2.3 | Concatenation of SMS messages..... | 95 | +| 9.2.3.24.10.3 | EMS Formats..... | 96 | +| 9.2.3.24.10.3.1 | Sounds..... | 96 | +| 9.2.3.24.10.3.2 | Pictures..... | 96 | +| 9.2.3.24.10.3.3 | Animation..... | 97 | +| 9.2.3.24.11 | IETF RFC 5322 E-Mail Header..... | 97 | +| 9.2.3.24.12 | Hyperlink format element..... | 99 | +| 9.2.3.24.13 | Enhanced Voice Mail Information..... | 100 | +| 9.2.3.24.13.1 | Enhanced Voice Mail Notification..... | 100 | +| 9.2.3.24.13.2 | Enhanced Voice Mail Delete Confirmation..... | 103 | +| 9.2.3.24.14 | Identification of a directory number within the User Data Field..... | 105 | +| 9.2.3.24.15 | National Language Single Shift..... | 105 | +| 9.2.3.24.16 | National Language Locking Shift..... | 106 | +| 9.2.3.25 | TP-Reject-Duplicates (TP-RD)..... | 106 | +| 9.2.3.26 | TP-Status-Report-Qualifier (TP-SRQ)..... | 106 | + +| | | | +|-------------------------------|--------------------------------------------------------------|------------| +| 9.2.3.27 | TP-Parameter-Indicator (TP-PI)..... | 106 | +| 9.2.3.28 | TP-Loop-Prevention (TP-LP)..... | 107 | +| 9.3 | Service provided by the SM-RL..... | 108 | +| 9.3.1 | General..... | 108 | +| 9.3.2 | Protocol element repertoire at SM-RL..... | 108 | +| 9.3.2.1 | RP-MO-DATA..... | 108 | +| 9.3.2.2 | RP-MT-DATA..... | 109 | +| 9.3.2.3 | RP-ACK..... | 109 | +| 9.3.2.4 | RP-ERROR..... | 109 | +| 9.3.2.5 | RP-ALERT-SC..... | 110 | +| 9.3.2.6 | RP-SM-MEMORY-AVAILABLE..... | 110 | +| 10 | Fundamental procedures within SMS..... | 110 | +| 10.1 | Short message mobile terminated..... | 111 | +| 10.2 | Short message mobile originated..... | 125 | +| 10.3 | Alert transfer..... | 133 | +| 11 | Mapping of error causes between RP layers..... | 136 | +| 11.1 | Mobile Terminated short message transfer..... | 136 | +| 11.2 | Memory available notification..... | 137 | +| 11.3 | Mobile Originated short message transfer..... | 137 | +| Annex A (informative): | Protocol stacks for interconnecting SCs and MSCs..... | 139 | +| Annex B (informative): | Information now contained in 3GPP TS 23.038 [9]..... | 140 | +| Annex C (informative): | Short message information flow..... | 141 | +| Annex D (informative): | Mobile Station reply procedures..... | 158 | +| D.1 | Introduction..... | 158 | +| D.2 | The scope of applicability..... | 158 | +| D.3 | Terminology..... | 158 | +| D.4 | The reply path requesting procedure..... | 158 | +| D.5 | The reception of an original MT SM..... | 159 | +| D.6 | The submission of the reply MO SM..... | 159 | +| D.7 | Usage of SCs for replying..... | 159 | +| D.8 | Replying possibilities for Phase 1 mobile stations..... | 160 | +| D.9 | The resulting service for originating SMEs..... | 160 | +| Annex E (normative): | Extended Object Format Type..... | 161 | +| E.1 | Predefined Sound..... | 161 | +| E.2 | iMelody..... | 161 | +| E.3 | Black and white bitmap..... | 161 | +| E.4 | 2-bit greyscale bitmap..... | 161 | +| E.5 | 6-bit colour bitmap..... | 162 | +| E.6 | Predefined animation..... | 162 | +| E.7 | Black and white bitmap animation..... | 162 | +| E.8 | 2-bit greyscale bitmap animation..... | 163 | +| E.9 | 6-bit colour bitmap animation..... | 163 | +| E.10 | vCard..... | 164 | + +| | | | +|--------------------------------|----------------------------------------------------------------------------|------------| +| E.11 | vCalendar..... | 164 | +| E.12 | Data Format Delivery Request..... | 164 | +| E.13 | Standard WVG Object..... | 164 | +| E.14 | Polyphonic melody..... | 165 | +| Annex F (informative) : | Compression methods for EMS..... | 166 | +| F.1 | LZSS compression..... | 166 | +| F.1.1 | Introduction..... | 166 | +| F.1.2 | LZSS Basic Algorithm..... | 166 | +| F.1.3 | Informative Example..... | 167 | +| Annex G (normative): | WVG (Wireless Vector Graphics) data format..... | 169 | +| G.1 | Introduction..... | 169 | +| G.1.1 | Standard and Character Size WVG elements..... | 169 | +| G.1.2 | Compression methods..... | 169 | +| G.1.3 | Coordinate Systems..... | 170 | +| G.1.3.1 | Compact Coordinate System..... | 170 | +| G.1.3.2 | Flat Coordinate System..... | 172 | +| G.1.3.3 | Coordinate values..... | 172 | +| G.1.4 | Color schemes..... | 172 | +| G.1.5 | Rendering model..... | 173 | +| G.2 | Graphical elements..... | 173 | +| G.2.1 | Line elements..... | 173 | +| G.2.1.1 | Polyline..... | 173 | +| G.2.1.2 | Circular Polyline..... | 173 | +| G.2.1.3 | Bezier Polyline..... | 174 | +| G.2.1.4 | Auto-closure of a line..... | 174 | +| G.2.2 | Polygon elements..... | 174 | +| G.2.3 | Simple shape elements..... | 174 | +| G.2.3.1 | Ellipse..... | 174 | +| G.2.3.2 | Rectangle..... | 174 | +| G.2.4 | Special shape elements..... | 175 | +| G.2.5 | Text element..... | 175 | +| G.2.6 | Group elements..... | 176 | +| G.2.7 | Reuse element..... | 176 | +| G.2.8 | Animation elements..... | 176 | +| G.2.8.1 | Simple animation elements..... | 176 | +| G.2.8.2 | Standard Animation Element..... | 178 | +| G.2.9 | Frame Element..... | 178 | +| G.2.10 | Local Element..... | 178 | +| G.2.11 | Extended Element..... | 178 | +| G.3 | Element attributes..... | 179 | +| G.4 | Element Transform..... | 179 | +| G.5 | Character Size WVG Element..... | 179 | +| G.6 | Data Format BNF..... | 180 | +| G.7 | Web Safe Color Palette..... | 197 | +| Annex H (informative): | Development Guidelines for Creation of Polyphony Using SP-MIDI..... | 199 | +| H.1 | Running status..... | 199 | +| H.2 | File type considerations..... | 199 | +| H.3 | File size reduction..... | 199 | +| H.4 | Restrictions..... | 200 | + +**Annex I (normative):**       **SMS in MME..... 201** + +I.1   General.....201 + +I.2   Registration of MME for SMS.....203 + +I.2.1   Void..... 204 + +I.2.2   Void..... 204 + +Annex J (informative):       Change history.....204 + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +The Short Message Service (SMS) provides a means of sending messages of limited size to and from GSM/UMTS/EPS mobiles. The provision of SMS makes use of a Service Centre, which acts as a store and forward centre for short messages. Thus a GSM/UMTS/EPS PLMN needs to support the transfer of short messages between Service Centres and mobiles. + +Mobile originated messages shall be transported from an MS to a Service Centre. These may be destined for other mobile users, or for subscribers on a fixed network. Mobile terminated messages shall be transported from a Service Centre to an MS. These may be input to the Service Centre by other mobile users (via a mobile originated short message) or by a variety of other sources, e.g. speech, telex, or facsimile. + +# 1 Scope + +The present document describes the Short Message Service (SMS) for GSM/UMTS networks. It defines: + +- the services and service elements; +- the network architecture; +- the Service Centre functionality; +- the SMS Router functionality; +- the MSC functionality (with regard to the SMS); +- the SGSN functionality (with regard to the SMS); +- the MME functionality (with regard to the SMS); +- the routing requirements; +- the protocols and protocol layering; + +for the Mobile Originated and Mobile Terminated Short Message Service Teleservices, as specified in 3GPP TS 22.003 [2] and 3GPP TS 22.105 [32]. + +The use of radio resources for the transfer of short messages between the MS and the MSC or the SGSN or the MME is described in 3GPP TS 24.011 [13]. + +The present document also describes the Short Message Service (SMS) for EPS networks supported via "SMS in MME" (see 3GPP TS 23.272 [45], annex C). + +The network aspects of Short Message Service provision are outside the scope of the present document (i.e. the provision of network connectivity between the PLMN subsystems). There is no technical restriction within the present document for the transfer of short messages between different PLMNs. Any such restriction is likely to be subject to commercial arrangements and PLMN operators must make their own provision for interworking or for preventing interworking with other PLMNs as they see fit. + +The required and assumed network service offered to the higher layers is defined in the present document. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void +- [2] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)". +- [3] 3GPP TS 22.004: "General on supplementary services". +- [4] 3GPP TS 22.041: "Operator Determined Barring (ODB)". +- [5] 3GPP TS 23.002: "Network architecture". +- [6] 3GPP TS 23.008: "Organization of subscriber data". + +- [7] 3GPP TS 23.011: "Technical realization of supplementary services". +- [8] 3GPP TS 23.015: "Technical realization of Operator Determined Barring (ODB)". +- [9] 3GPP TS 23.038: "Alphabets and language-specific information". +- [10] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [11] Void +- [12] 3GPP TS 44.008: "Mobile radio interface layer 3 specification". +- [13] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". +- [14] 3GPP TS 27.005: "Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)". +- [15] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [16] 3GPP TS 51.011 Release 4 (version 4.x.x): "Specification of the Subscriber Identity Module - Mobile Equipment (SIM- ME) interface". +- [17] CCITT Recommendation E.164 (Blue Book): "The international public telecommunication numbering plan". +- [18] CCITT Recommendation E.163 (Blue Book): "Numbering plan for the international telephone service". +- [19] CCITT Recommendation Q.771: "Specifications of Signalling System No.7; Functional description of transaction capabilities". +- [20] CCITT Recommendation T.100 (Blue Book): "International information exchange for interactive videotex". +- [21] CCITT Recommendation T.101 (Blue Book): "International interworking for videotex services". +- [22] CCITT Recommendation X.121 (Blue Book): "International numbering plan for public data networks". +- [23] CCITT Recommendation X.400 (Blue Book): "Message handling services: Message handling system and service overview". +- [24] ISO/IEC10646: "Universal Multiple-Octet Coded Character Set (USC); UCS2, 16 bit coding". +- [25] 3GPP TS 22.022: "Personalisation of Mobile Equipment (ME); Mobile functionality specification". +- [26] 3GPP TS 23.042: "Compression Algorithm for Text Messaging Services". +- [27] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [28] 3GPP TS 31.115: "Secured packet structure for (U)SIM toolkit application". +- [29] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [30] 3GPP TS 31.102: "Characteristics of the USIM application". +- [31] 3GPP TS 31.101: "UICC – Terminal interface; Physical and logical characteristics". +- [32] 3GPP TS 22.105: "Services and Service Capabilities". +- [33] Infrared Data Association. Specifications for Ir Mobile Communications (IrMC). iMelody. +- [34] IETF RFC 5322 (October 2008): "Internet Message Format". +- [35] Void + +- [36] "vCard - The Electronic Business Card", version 2.1, The Internet Mail Consortium (IMC), September 18, 1996, [URL: http://www.imc.org/pdi/vcard-21.doc](http://www.imc.org/pdi/vcard-21.doc)". +- [37] "vCalendar - the Electronic Calendaring and Scheduling Format", version 1.0, The Internet Mail Consortium (IMC), September 18, 1996, [URL: http://www.imc.org/pdi/vcal-10.doc](http://www.imc.org/pdi/vcal-10.doc) +- [38] Scalable Polyphony MIDI Specification, MIDI Manufacturers Association (2002); +- [39] Scalable Polyphony MIDI Device 5-to-24 Note Profile for 3GPP, MIDI Manufacturers Association (2002); +- [40] The Complete MIDI 1.0 Detailed Specification, Incorporating all Recommended Practices, MIDI Manufacturers Association, Document version 96.1, 1996; +- [41] 3GPP TS 23.097: Multiple Subscriber Profile (MSP) (Phase 2) - Stage 2 +- [42] 3GPP TS 23.204: "Support of SMS over generic 3GPP IP access; Stage 2". +- [43] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol". +- [44] IETF RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging". +- [45] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2". +- [46] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [47] 3GPP TS 29.118: "Mobility Management Entity (MME) – Visitor Location Register (VLR) SGs interface specification". +- [48] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [49] Void. +- [50] 3GPP TS 29.338: "Diameter based protocols to support of SMS capable MMEs". + +## 2.1 Definitions and abbreviations + +### 2.1.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +NOTE 1: The term "mobile station" (MS) in the present document is synonymous with the term "user equipment" (UE) in UMTS terminology as defined in 3GPP TR 21.905 [29]. + +**active MS:** switched-on mobile station with a SIM/UICC see 3GPP TS 31.101 [31] module attached + +**alert-SC:** service element provided by a GSM/UMTS PLMN to inform an SC which has previously initiated unsuccessful short message delivery attempt(s) to a specific MS, that the MS is now recognized by the PLMN to have recovered operation + +**status report:** SC informing the originating MS of the outcome of a short message submitted to an SME + +**Gateway MSC For Short Message Service (SMS-GMSC):** function of an MSC capable of receiving a short message from an SC, interrogating an HLR for routing information and SMS info, and delivering the short message to the VMSC or the SGSN of the recipient MS + +**Interworking MSC For Short Message Service (SMS-IWMSC):** function of an MSC capable of receiving a short message from within the PLMN and submitting it to the recipient SC + +**IP-Short-Message-Gateway (IP-SM-GW):** function responsible for protocol interworking between the IP-based UE and the SC + +**Loop Prevention (LP):** information element that allows SMS applications to inhibit forwarding or automatic message generation that could cause infinite looping. + +**Messages-Waiting (MW):** service element that makes a PLMN store information (Messages-Waiting-Indication), listing those SCs that have made unsuccessful short message delivery attempts to MSs in that PLMN + +**Messages-Waiting-Indication (MWI):** data to be stored in the HLR and VLR with which an MS is associated, indicating that there is one or more messages waiting in a set of SCs to be delivered to the MS (due to unsuccessful delivery attempt(s)) + +**Messages-Waiting-Data (MWD):** part of the MWI to be stored in the HLR. MWD consists of an address list of the SCs which have messages waiting to be delivered to the MS + +**Mobile Management Entity (MME):** exchange which performs packet switching functions for mobile stations located in a geographical area designated as the MME area. + +**Mobile-services Switching Centre (MSC):** exchange which performs switching functions for mobile stations located in a geographical area designated as the MSC area + +**Mobile-Station-Memory-Capacity-Exceeded-Flag (MCEF):** part of the MWI to be stored in the HLR + +NOTE 2: MCEF is a Boolean parameter indicating if the address list of MWD contains one or more entries because an attempt to deliver a short message to an MS has failed with a cause of MS Memory Capacity Exceeded + +**Mobile-Station-Not-Reachable-Flag (MNRF):** part of the MWI to be stored in the VLR, the MME, and the HLR. The MME supports all the requirements specified in the present document for the VLR with regard to the MNRF. + +NOTE 3: MNRF is a Boolean parameter indicating if the address list of MWD contains one or more entries because an attempt to deliver a short message to an MS has failed with a cause of Absent Subscriber. + +**Mobile-station-Not-Reachable-for-GPRS (MNRG):** part of the MWI to be stored in the SGSN and the HLR + +NOTE 4: MNRG is a Boolean parameter indicating if the address list of MWD contains one or more entries because an attempt to deliver a short message to an MS has failed with a cause of Absent Subscriber. + +**Mobile-Station-Not-Reachable-via-the- MSC-Reason (MNRR- MSC):** part of the MWI in the HLR which stores the reason for an MS being absent when an attempt to deliver a short message to an MS fails at the MSC with a cause of Absent Subscriber + +**Mobile-Station-Not-Reachable-via-the-SGSN-Reason (MNRR-SGSN):** part of the MWI in the HLR which stores the reason for an MS being absent when an attempt to deliver a short message to an MS fails at the SGSN with a cause of Absent Subscriber + +**More-Messages-To-Send (MMS):** information element offering an MS receiving a short message from an SC the information whether there are still more messages waiting to be sent from that SC to the MS + +NOTE 5: The TP-MMS element (conveyed in the Transfer layer) is copied into the RP-MMS element (conveyed in the Relay layer). It is possible with Phase 2 and later versions of MAP (3GPP TS 29.002 [15]) for the RP-MMS element to keep an SM transaction open between the SMS-GMSC and the MS in the case where there are more-messages-to-send. Earlier versions of MAP support the transport of the TP-MMS element. + +**priority:** service element enabling the SC or SME to request a short message delivery attempt to an MS irrespective of whether or not the MS has been identified as temporarily absent + +**protocol-identifier:** information element by which the originator of a short message (either an SC or an MS) may refer to a higher layer protocol + +**receiving MS:** the mobile station to which an MT SM is destined. + +**reply path procedure:** mechanism which allows an SME to request that an SC should be permitted to handle a reply sent in response to a message previously sent from that SME to another SME + +NOTE 6: This may happen even though the SC may be unknown to the SME which received the initial message. + +**report:** response from either the network or the recipient upon a short message being sent from either an SC or an MS + +NOTE 7: A report may be a delivery report, which confirms the delivery of the short message to the recipient, or it may be a failure report, which informs the originator that the short message was never delivered and the reason why. + +- When issued by the Service Centre, the delivery report confirms the reception of the Short Message by the SC, and not the delivery of the Short Message to the SME. +- When issued by the Mobile Station, the delivery report confirms the reception of the Short Message by the Mobile Station, and not the delivery of the Short Message to the user. + +**replace short message type:** range of values in the Protocol Identifier which allows an indication to be sent with a short message (MT or MO) that the short message is of a particular type allowing the receiving MS or the SC to replace an existing message of the same type held in the SC, the ME or on the SIM/UICC, provided it comes: + +- in MT cases: from the same SC and originating address; +- in MO cases: from the same MS. + +**sending MS:** the mobile station from which an MO SM is sourced. + +**Service Centre (SC):** function responsible for the relaying and store-and-forwarding of a short message between an SME and an MS + +NOTE 8: The SC is not a part of the GSM/UMTS PLMN, however MSC and SC may be integrated. + +**Serving GPRS Support Node (SGSN):** exchange which performs packet switching functions for mobile stations located in a geographical area designated as the SGSN area + +**short message:** information that may be conveyed by means of the Short Message Service + +NOTE 9: As described in the present document. + +**Short Message Entity (SME):** entity which may send or receive Short Messages + +NOTE 10: The SME may be located in a fixed network, an MS, or an SC. + +**SMS-STATUS-REPORT:** short message transfer protocol data unit informing the receiving MS of the status of a mobile originated short message previously submitted by the MS, i.e. whether the SC was able to forward the message or not, or whether the message was stored in the SC for later delivery + +**SMS-COMMAND:** short message transfer protocol data unit which enables an MS to invoke an operation at the SC + +NOTE 11: An MS may then, for example, delete a short message, cancel a TP-Status-Report-Request, enquire about the status of a short message or request another function to be performed by the SC. + +NOTE 12: The type of operation is indicated by the TP-Command-Type and the particular SM to operate on is indicated by the TP-Message-Number and the TP-Destination-Address. Receipt of an SMS-COMMAND is confirmed by an RP-ACK or RP-ERROR. In the case of certain SMS-COMMANDs, an SMS-STATUS-REPORT may be sent, where the outcome of the SMS-COMMAND is passed in its TP-Status field. + +**SMS-DELIVER:** short message transfer protocol data unit containing user data (the short message), being sent from an SC to an MS + +**SMS-SUBMIT:** short message transfer protocol data unit containing user data (the short message), being sent from an MS to an SC + +**Service-Centre-Time-Stamp (SCTS):** information element offering the recipient of a short message the information of when the message arrived at the SM-TL entity of the SC + +NOTE 13: The time of arrival comprises the year, month, day, hour, minute, second and time zone. + +**UE-Not-Reachable-for-IP (UNRI):** part of the MWI to be stored in the IP-SM-GW and the HSS/HLR + +NOTE 14: UNRI is a Boolean parameter indicating if the address list of MWD contains one or more entries because an attempt to deliver a short message to an UE has failed with a cause of Absent Subscriber. + +**UE-Not-Reachable-Reason (UNRR):** part of the MWI in the HSS/HLR which stores the reason for an UE being absent when an attempt to deliver a short message to an UE fails at the IP-SM-GW. + +**Validity-Period (VP):** information element enabling the originator MS to indicate the time period during which the originator considers the short message to be valid. + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.038 [9] apply: + +**National Language Identifier** + +**National Language Locking Shift Table** + +**National Language Single Shift Table** + +### 2.1.2 Abbreviations + +For the purposes of the present document, the abbreviations defined in 3GPP TR 21.905 [29] and the following apply: + +| | | +|-------|---------------------------------------| +| SM MO | Short Message Mobile Originated | +| SM MT | Short Message Mobile Terminated | +| SM-AL | Short Message Application Layer | +| SM-LL | Short Message Lower Layers | +| SM-RL | Short Message Relay Layer | +| SM-RP | Short Message Relay Layer Protocol | +| SM-RS | Short Message Relay Service | +| SM-TL | Short Message Transfer Layer | +| SM-TP | Short Message Transfer Layer Protocol | +| SM-TS | Short Message Transfer Service | +| SSN | Sub-System Number | +| TPDU | Transfer protocol data unit | + +# --- 3 Services and service elements + +The SMS provides a means to transfer short messages between a GSM/UMTS MS and an SME via an SC. The SC serves as an interworking and relaying function of the message transfer between the MS and the SME. + +The present document describes only the short message services between the MS and SC. It may, however, refer to possible higher layer applications. + +## 3.1 Basic services + +The Short Message Service comprise two basic services: + +SM MT (Short Message Mobile Terminated); + +SM MO (Short Message Mobile Originated). + +SM MT denotes the capability of the GSM/UMTS system to transfer a short message submitted from the SC to one MS, and to provide information about the delivery of the short message either by a delivery report or a failure report with a specific mechanism for later delivery; see figure 1. + +SM MO denotes the capability of the GSM/UMTS system to transfer a short message submitted by the MS to one SME via an SC, and to provide information about the delivery of the short message either by a delivery report or a failure report. The message shall include the address of that SME to which the SC shall eventually attempt to relay the short message; see figure 2. + +The text messages to be transferred by means of the SM MT or SM MO contain up to 140 octets. + +![Sequence diagram for Short Message Service mobile terminated. A Service Center (SC) box on the left sends a 'Short message delivery' message (arrow) to a Mobile Station (MS) box on the right. The MS box responds with a 'Report' message (arrow) back to the SC box.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant SC + participant MS + Note over SC,MS: Short message delivery + SC->>MS: Short message delivery + MS-->>SC: Report + +``` + +Sequence diagram for Short Message Service mobile terminated. A Service Center (SC) box on the left sends a 'Short message delivery' message (arrow) to a Mobile Station (MS) box on the right. The MS box responds with a 'Report' message (arrow) back to the SC box. + +**Figure 1: The Short Message Service mobile terminated** + +![Sequence diagram for Short Message Service mobile originated. A Mobile Station (MS) box on the right sends a 'Short message submission' message (arrow) to a Service Center (SC) box on the left. The SC box responds with a 'Report' message (arrow) back to the MS box.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` + +sequenceDiagram + participant SC + participant MS + Note over SC,MS: Short message submission + MS->>SC: Short message submission + SC-->>MS: Report + +``` + +Sequence diagram for Short Message Service mobile originated. A Mobile Station (MS) box on the right sends a 'Short message submission' message (arrow) to a Service Center (SC) box on the left. The SC box responds with a 'Report' message (arrow) back to the MS box. + +**Figure 2: The Short Message Service mobile originated** + +An active MS shall be able to receive a short message TPDU (SMS-DELIVER) at any time, independently of whether or not there is a speech or data call in progress. A report shall always be returned to the SC; either confirming that the MS has received the short message, or informing the SC that it was impossible to deliver the short message TPDU to the MS, including the reason why. + +An active MS shall be able to submit a short message TPDU (SMS-SUBMIT) at any time, independently of whether or not there is a speech or data call in progress. A report shall always be returned to the MS; either confirming that the SC has received the short message TPDU, or informing the MS that it was impossible to deliver the short message TPDU to the SC, including the reason why. + +NOTE: When the transmission or reception of a short message coincide with a change of state in the MS, i.e. from busy to idle or from idle to busy, or during a handover, the short message transfer may be aborted. + +It is also possible for two short messages to be received in sequence having the same originating address and identification, i.e. message reference number (MO) or SC Timestamp (MT). Such a situation may be due to errors at the RP or CP layers (e.g. during inter MSC handover) where it may be a duplicated message or otherwise it may be a valid new message. + +The receiving entity should therefore make provision to check other parameters contained in the short message to decide whether the second short message is to be discarded. + +## 3.2 Short Message Service elements + +### 3.2.0 Introduction + +The SMS comprises 8 elements particular to the submission and reception of messages: + +- Validity-Period; +- Service-Centre-Time-Stamp; +- Protocol-Identifier; +- More-Messages-to-Send; +- Priority; +- Messages-Waiting; +- Alert-SC. +- MT Correlation ID. + +### 3.2.1 Validity-Period + +The Validity-Period is the information element which gives an MS submitting an SMS-SUBMIT to the SC the possibility to include a specific time period value in the short message (TP-Validity-Period field, see clause 9). The TP-Validity-Period parameter value indicates the time period for which the short message is valid, i.e. for how long the SC shall guarantee its existence in the SC memory before delivery to the recipient has been carried out. + +### 3.2.2 Service-Centre-Time-Stamp + +The Service-Centre-Time-Stamp is the information element by which the SC informs the recipient MS about the time of arrival of the short message at the SM-TL entity of the SC. The time value is included in every SMS-DELIVER (TP-Service-Centre-Time-Stamp field, see clause 9) being delivered to the MS. + +### 3.2.3 Protocol-Identifier + +The Protocol-Identifier is the information element by which the SM-TL either refers to the higher layer protocol being used, or indicates interworking with a certain type of telematic device. + +The Protocol-Identifier information element makes use of a particular field in the message types SMS-SUBMIT, SMS-SUBMIT-REPORT for RP-ACK, SMS-DELIVER, SMS-DELIVER-REPORT for RP-ACK, SMS\_STATUS\_REPORT and SMS-COMMAND TP-Protocol-Identifier (TP-PID). + +### 3.2.4 More-Messages-to-Send + +The More-Messages-to-Send is the information element by which the SC informs the MS that there is one or more messages waiting in that SC to be delivered to the MS. The More-Messages-to-Send information element makes use of a Boolean parameter in the message SMS-DELIVER, TP-More-Messages-to-Send (TP-MMS). + +### 3.2.5 Delivery of Priority and non-Priority Messages + +Priority is the information element provided by an SC or SME to indicate to the PLMN whether or not a message is a priority message. + +Delivery of a non-priority message shall not be attempted if the MS has been identified as temporarily absent (see clause 3.2.6). + +Delivery of a non-priority message shall be attempted if the MS has not been identified as temporarily absent irrespective of whether the MS has been identified as having no free memory capacity (see clause 3.2.6). + +Delivery of a priority message shall be attempted irrespective of whether or not the MS has been identified as temporarily absent, or having no free memory capacity. + +### 3.2.6 Messages-Waiting + +The Messages-Waiting is the service element that enables the PLMN to provide the HLR, SGSN and VLR with which the recipient MS is associated with the information that there is a message in the originating SC waiting to be delivered to the MS. The service element is only used in case of previous unsuccessful delivery attempt(s) due to temporarily absent mobile or MS memory capacity exceeded. This information, denoted the Messages-Waiting-Indication (MWI), consists of Messages-Waiting-Data (MWD), the Mobile-station-Not-Reachable-for-GPRS (MNRG), the UE-Not-Reachable-for-IP (UNRI), the Mobile-Station-Not-Reachable-Flag (MNRF), the Mobile-Not-Reachable-via-the- MSC-Reason (MNRR-MSC), the Mobile-Not-Reachable-via-the-SGSN-Reason (MNRR-SGSN), the UE Not Reachable-Reason (UNRR) and the Mobile-Station-Memory-Capacity-Exceeded-Flag (MCEF) located in the HLR; the Mobile-station-Not Reachable-for-GPRS (MNRG) located in the SGSN, and the Mobile-Station-Not-Reachable-Flag (MNRF) located in the VLR. Figure 3 shows an example. + +![Figure 3: Example of how information on one MS can be put in relation to SC(s) in order to fulfil the requirement of Alert-SC mechanism. The diagram shows the structure of the Messages-Waiting-Data (MWD) and related flags in the HSS/HLR, VLR, SGSN, and IP-SM-GW.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +The diagram illustrates the organization of information for the Alert-SC mechanism across different network elements: + +- HSS/HLR:** Contains a box labeled **MWD:** which includes a list of elements: **MSIsdn-Alert**, **SC address1**, **SC address2**, an ellipsis (**...**), and **SC addressn**. Below this list are several flags: **MNRF**, **MCEF**, **MNRG**, **UNRI**, **MNRR-MSC**, **MNRR-SGSN**, and **UNRR**. +- VLR:** Contains a box with the flag **MNRF**. +- SGSN:** Contains a box with the flag **MNRG**. +- IP-SM-GW:** Contains a box with the flag **UNRI**. + +Figure 3: Example of how information on one MS can be put in relation to SC(s) in order to fulfil the requirement of Alert-SC mechanism. The diagram shows the structure of the Messages-Waiting-Data (MWD) and related flags in the HSS/HLR, VLR, SGSN, and IP-SM-GW. + +**Figure 3: Example of how information on one MS can be put in relation to SC(s) in order to fulfil the requirement of Alert-SC mechanism** + +The MWD shall contain a list of addresses (SC-Addr) of SCs which have made previous unsuccessful delivery attempts of a message (see clause 5). In order to be able to send alert messages to every SC which has made unsuccessful delivery attempts to an MS, the HLR shall store the MSIsdn-Alert or IMSI-Alert (see clause 3.2.7) together with references to the SC addresses. The requirements placed upon the HLR are specified in GSM TS 03.08 [6]. The description of how the HLR is provided with SC and MS address information is given in 3GPP TS 29.002 [15]. + +The Mobile-Station-Memory-Capacity-Exceeded-Flag (MCEF) within the HLR is a Boolean parameter with the value TRUE an attempt to deliver a short message to an MS has failed with a cause of MS Memory Capacity Exceeded, and with the value FALSE otherwise. + +The Mobile-station-Not Reachable-for-GPRS (MNRG) within the HLR and the SGSN is a Boolean parameter with the value TRUE when an attempt to deliver a short message to an MS has failed with a cause of Absent Subscriber, and with the value FALSE otherwise (except as described in note 1 below). + +The Mobile-Station-Not-Reachable-Flag (MNRF) within the HLR and the VLR is a Boolean parameter with the value TRUE when the list MWD contains one or more list elements because an attempt to deliver a short message to an MS has failed with a cause of Absent Subscriber, and with the value FALSE otherwise. + +The UE-Not-Reachable-for-IP (UNRI) within the HLR/HSS and IP-SM-GW is a Boolean parameter with the value TRUE when the list MWD contains one or more list elements because an attempt to deliver a short message to an UE has failed with a cause of Absent Subscriber, and with the value FALSE otherwise. + +The Mobile-Station-Not-Reachable-via-the- MSC-Reason (MNRR- MSC) within the HLR stores the reason for the MS being absent when an attempt to deliver a short message to an MS fails at the MSC with the cause Absent Subscriber. The HLR updates the MNRR- MSC with the reason for absence when an absent subscriber diagnostic information is received from the SMS-GMSC and the MNRF is set. The HLR clears the MNRR- MSC when the MNRF is cleared. If the MNRF is set due to a failure at the MSC with cause Absent Subscriber and information pertaining to the absence of the MS is not available from the SMS-GMSC, the MNRR- MSC shall remain in a cleared state. The MNRR- MSC shall either be in a cleared state or contain one of the following reasons: + +- No Paging Response via the MSC; +- IMSI Detached. + +The Mobile-Station-Not-Reachable-via-the-SGSN-Reason (MNRR-SGSN) within the HLR stores the reason for the MS being absent when an attempt to deliver a short message to an MS fails at the SGSN with the cause Absent Subscriber. The HLR updates the MNRR-SGSN with the reason for absence when an absent subscriber diagnostic information is received from the GMSC and the MNRG is set. The HLR clears the MNRR-SGSN when the MNRG is cleared. If the MNRG is set due to a failure at the SGSN with cause Absent Subscriber and information pertaining to the absence of the MS is not available from the GMSC, the MNRR-SGSN shall remain in a cleared state. The MNRR-SGSN shall either be in a cleared state or contain one of the following reasons: + +- No Paging Response via the SGSN; +- GPRS Detached. + +NOTE 1: The MNRG can also be set in the HLR and in the SGSN after an unsuccessful attempt to invoke the network requested PDP-Context Activation procedure. In this case, no SC address is stored in MWD list (see 3GPP TS 23.060 [27]). + +NOTE 2: When a short message delivery attempt fails at the HLR due to Roaming being Restricted, the MS being deregistered in HLR or the MS being Purged the absent subscriber diagnostic reason is returned to the SC, however the reason is not stored in the MNRR- MSC or MNRR-SGSN. + +The UE-Station-Not-Reachable-Reason (UNRR) within the HSS/HLR stores the reason for the UE being absent when an attempt to deliver a short message to an UE fails at the IP-SM-GW with the cause Absent Subscriber. The HSS/HLR updates the UNRR with the reason for absence when an absent subscriber diagnostic information is received from the IP-SM-GW and the UNRI is set. The HSS/HLR clears the UNRR when the UNRI is cleared. If the UNRI is set due to a failure at the IP-SM-GW with cause Absent Subscriber, the UNRR shall remain in a cleared state. The UNRR shall either be in a cleared state or contain one of the following reasons: + +- No Response via the IP-SM-GW; +- UE deregistered. + +The MWD, MCEF, MNRR- MSC, MNRR-SGSN, MNRG, MNRF, UNRI and UNRR are updated in the following way: + +- 1a) When a mobile terminated short message delivery fails at the MSC due to the MS being temporarily absent (i.e. either IMSI DETACH flag is set or there is no response from the MS to a paging request via the MSC), the SC address is inserted into the MWD list (if it is not already present), the MNRF is set (if it is not already set) and the MNRR- MSC is updated (if the information is available), as described in clause 10. +- 1b) When a mobile terminated short message delivery fails at the SGSN due to the MS being temporarily absent (i.e. either GPRS DETACH flag is set or there is no response from the MS to a paging request via the SGSN), the SC address is inserted into the MWD list (if it is not already present), the MNRG is set (if it is not already set) and the MNRR-SGSN is updated (if the information is available), as described in clause 10. +- 1c) When a mobile terminated short message delivery fails at the MSC due to the MS memory capacity being exceeded, the SC address is inserted into the MWD list (if it is not already present), the MCEF is set (if it is not already set), the MNRF is cleared and the MNRR- MSC is cleared. +- 1d) When a mobile terminated short message delivery fails at the SGSN due to the MS memory capacity being exceeded, the SC address is inserted into the MWD list (if it is not already present), the MCEF is set (if it is not already set), the MNRG is cleared and the MNRR-SGSN is cleared. + +- 1e) When a mobile terminated short message delivery fails due to the UE memory capacity via the IP-SM-GW being exceeded, the SC address is inserted into the MWD list (if it is not already present), the MCEF is set (if it is not already set), the UNRI is cleared and the UNRR is cleared. +- 1f) If the MSISdn or IMSI used by the SC to address the recipient MS for alerting purposes is different from the MSISdn-Alert or IMSI-Alert of the MS (see clause 3.2.7), the HLR returns the MSISdn-Alert or IMSI-Alert to the SC within the failure report, see "1c Failure report" in figures 15 and 16. +- 2a) When either the HLR or VLR detects that the MS has recovered operation (e.g. has responded to a paging request over MSC), the HLR directly or on request of the VLR shall clear MNRF and MNRR-MSC. Then, if with a non empty MWD list and the MCEF clear, the HLR shall invoke operations to alert the SCs within the MWD (see clause 3.2.7 and clause 10). After each SC is alerted by the HLR, the address for that SC shall be deleted from the MWD. If the MCEF is set in the HLR, the HLR shall not invoke operations to alert the SCs within the MWD and data are not cleared from the MWD. +- 2b) When either the HLR or SGSN detects that the MS has recovered operation (e.g. has responded to a paging request via the SGSN), the HLR directly or on request of the SGSN shall clear MNRG and MNRR-SGSN. Then, if with a non empty MWD list and the MCEF clear, the HLR shall invoke operations to alert the SCs within the MWD (see clause 3.2.7 and clause 10). After each SC is alerted by the HLR, the address for that SC is deleted from the MWD. If the MCEF is set in the HLR, the HLR shall not invoke operations to alert the SCs within the MWD and data are not cleared from the MWD. +- 2c) When the IP-SM-GW informs the HLR/HSS that the UE is reachable for SMS over IP, either due to an IMS registration or due to the UE becoming available again, the HLR/HSS shall clear the UNRI and UNRR. Then, if with a non empty MWD list and the MCEF clear, the HLR/HSS shall invoke operations to alert the SCs within the MWD (see clause 3.2.7 and clause 10). After each SC is alerted by the HLR/HSS, the address for that SC is deleted from the MWD. If the MCEF is set in the HLR/HSS, the HLR/HSS shall not invoke operations to alert the SCs within the MWD and data are not cleared from the MWD. +- 2d) When the HLR receives (via the MSC and the VLR) a notification that the MS (with a non-empty MWD and the MCEF set in the HLR) has memory capacity available to receive one or more short messages, the HLR shall invoke operations to alert the SCs within the MWD (see clause 3.2.7 and clause 10). Once the Alert SC operations have been invoked, the MNRF is cleared in the VLR and the MCEF, MNRF and MNRR-MSC are cleared in the HLR. After each SC is alerted by the HLR, the address for that SC is deleted from the MWD. +- 2e) When the HLR receives (via the SGSN) a notification that the MS (with a non-empty MWD and the MCEF set in the HLR) has memory capacity available to receive one or more short messages, the HLR shall invoke operations to alert the SCs within the MWD (see clause 3.2.7 and clause 10). Once the Alert SC operations have been invoked, the MNRG is cleared in the SGSN and the MCEF, MNRG and MNRR-SGSN are cleared in the HLR. After each SC is alerted by the HLR, the address for that SC is deleted from the MWD. +- 2f) When the HLR/HSS receives (via the IP-SM-GW) a notification that the UE (with a non-empty MWD and the MCEF set in the HLR/HSS) has memory capacity available to receive one or more short messages, the HLR/HSS shall invoke operations to alert the SCs within the MWD (see clause 3.2.7 and clause 10). Once the Alert SC operations have been invoked, the UNRI and UNRR are cleared in the HLR/HSS. After each SC is alerted by the HLR/HSS, the address for that SC is deleted from the MWD. +- 2g) When the HLR receives from the SMS-GMSC a notification that a short message has been successfully delivered from an SC to an MS via the MSC for which the MCEF is set and the MWD are not empty, the HLR shall invoke operations to alert other SCs within the MWD (see clause 3.2.7 and clause 10). Once the Alert SC operations have been invoked, the MCEF, MNRF and MNRR-MSC are cleared in the HLR. After each SC is alerted by the HLR, the address for that SC is deleted from the MWD. The SC which successfully delivered the message is also deleted from the MWD, if present. +- 2h) When the HLR receives from the SMS-GMSC a notification that a short message has been successfully delivered from an SC to an MS via the SGSN for which the MCEF is set and the MWD are not empty, the HLR shall invoke operations to alert other SCs within the MWD (see clause 3.2.7 and clause 10). Once the Alert SC operations have been invoked, the MCEF, MNRG and MNRR-SGSN are cleared in the HLR. After each SC is alerted by the HLR, the address for that SC is deleted from the MWD. The SC which successfully delivered the message is also deleted from the MWD, if present. +- 2i) When the HLR receives (via the MSC and the VLR, or the SGSN) a notification that the MS has memory capacity available to receive one or more short messages but the MCEF is not set and the MWD are empty, the HLR acknowledges the notification but does not alert any service centre. + +NOTE 3: The HLR can be in a situation where the MWD list is empty but where either MNRF or MNRG (with the related MNRR-MSC or MNRR-SGSN) is still set. This enables the HLR to return the correct address (MSC or SGSN address) at the next Send Routing Information Request from the SMS-GMSC. + +NOTE 4: If the SMS delivery failed on first attempt via the MSC or the SGSN (see cases 1a for IMSI Detach and 1b for GPRS Detach), and is successful on the second attempt (see cases 2e and 2f), the SC address shall not be inserted into the MWD list + +### 3.2.7 Alert-SC + +The Alert-SC is the service element, which may be provided by some GSM/UMTS PLMNs, to inform the SC that an MS: + +- 1) to which a delivery attempt has failed because the MS is not reachable or because the MS memory capacity was exceeded; and +- 2) which is now recognized by the PLMN: + - a) to have resumed operation (e.g. to have responded to a paging request); or + - b) to have memory newly available (which implies that the mobile is reachable). + +is again ready to receive one or more short messages. The SC may - on reception of an Alert-SC - initiate the delivery attempt procedure for the queued messages destined for this MS. + +To each MS there may be allocated one or more MSISdns or External-Identifier(s). When the HLR is to alert an SC that an MS is again attainable it shall use a specific MSISdn or IMSI corresponding to the External-Identifier for this purpose; in the present document called MSISdn-Alert or IMSI-Alert. + +NOTE 5: Repeated delivery attempts from the SC may be of two types: + +- i) A repeated delivery attempt because the SC has been informed that the MS is active and available to receive short messages. +- ii) An autonomous repeated delivery attempt by the SC. +- The application of these two options is defined by the providers of the SC and the network. + +### 3.2.7a MT Correlation ID + +The MT Correlation ID is a service element used only when the HPLMN of the receiving MS is using an SMS Router or an IP-SM-GW. It is used to correlate a Forward SM operation to a previous Info Retrieval operation. + +Use of the MT Correlation ID enhances security. By analysing the Correlation ID received in a Forward Short message operation, it can be easily checked from where the associated Info Retrieval operation originated, thus resulting in detection of "fake" and "spoofed" SMs. + +The MT Correlation ID is used in place of the IMSI in the IMSI IE at the protocol layer. Hence, its structure is defined to be exactly the same as this element. + +NOTE: Using an MT Correlation ID in place of the real IMSI has the added benefit of enhancing subscriber privacy in that the full IMSI is not shared with the HPLMN of the sending MS. + +The MT Correlation ID shall be composed as shown in figure 3a below. + +![Figure 3a: Structure of the MT Correlation ID. The diagram shows a 15-digit MT-SMS Correlation ID composed of three parts: MCC (3 digits), MNC (3 digits), and Sender ID (9 digits).](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates the structure of the MT Correlation ID. It is a 15-digit number divided into three segments: + + +- MCC (Mobile Country Code):** 3 digits +- MNC (Mobile Network Code):** 3 digits +- Sender ID:** 9 digits + + The total length is 15 digits, labeled as "MT-SMS Correlation ID". + +Figure 3a: Structure of the MT Correlation ID. The diagram shows a 15-digit MT-SMS Correlation ID composed of three parts: MCC (3 digits), MNC (3 digits), and Sender ID (9 digits). + +**Figure 3a: Structure of the MT Correlation ID** + +The MT Correlation ID is composed of three parts: + +- 1) Mobile Country Code (MCC) of the HPLMN of the receiving MS. It consists of three decimal digits. +- 2) Mobile Network Code (MNC) of the HPLMN of the receiving MS. It consists of three decimal digits. If the MNC of the HPLMN of the receiving MS is 2 digits only in length, the first digit of the MSIN shall be appended to the right-hand side. +- 3) Sender ID. It consists of nine decimal digits and shall be unique for its lifetime. For security purposes, its value shall be a number allocated at random, rather than sequentially. + +An example of the MT Correlation ID is: + +Sender ID: 569123006 + +IMSI in use: 234151234567890 + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 1234567890, + +Which gives the MT Correlation ID: 234151569123006. + +### 3.2.8 Options concerning MNRG, MNRF, UNRI, MNRR-MSC, MNRR-SGSN, UNRR, MCEF and MWD + +Setting the Mobile-Station-Not-Reachable-Flag (MNRF) in the VLR is mandatory. Setting the Mobile-station-Not-Reachable-for-GPRS (MNRG) in the SGSN is mandatory. It is mandatory for the VLR or the SGSN to send the "MS Reachable" message (see clause 10) to the HLR when the MS has been detected as becoming active and then to clear MNRF in the VLR or the MNRG in SGSN. + +The Messages-Waiting-Data (MWD), the Mobile-Station-Not-Reachable-Flag (MNRF), the Mobile-station-Not-Reachable-for-GPRS (MNRG), the Mobile-Station-Not-Reachable-via-the-MSC-Reason (MNRR-MSC), the Mobile-Station-Not-Reachable-via-the-SGSN-Reason (MNRR-SGSN), and the Mobile-Station-Memory-Capacity-Exceeded-Flag (MCEF) within the HLR are optional, but if one is implemented all must be implemented (except MNRG and MNRR-SGSN if the HLR does not support GPRS). This is linked to the transmission of the "Alert SC" message. + +The following describes what happens when a delivery fails. + +Case 1: MWD, MNRF, MNRG, UNRI, MNRR-MSC, MNRR-SGSN, UNRR, and MCEF are implemented in the HLR. + +In the case of a delivery failure (to an MS) with cause Absent Subscriber, the SMS-GMSC requests the HLR to add, if needed, a new entry in the MWD with cause Absent Subscriber. This new entry contains the SC address. The HLR sets its copy of the MNRF, MNRG or both and updates the MNRR-MSC, MNRR-SGSN or both (if the information is available). The SC is notified of the failure, the reason for the MS being absent and also of the MWD setting in the HLR within the Report message (see clause 10). + +If a delivery through an IP-SM-GW fails (to an MS) with cause Mobile Station Memory Capacity Exceeded via the SGSN, IP-SM-GW, or the MSC, the IP-SM-GW requests the HSS to add, if needed, a new entry in the MWD with cause Mobile Station Memory Capacity Exceeded. This new entry contains the SC address. The HLR sets the MCEF and resets MNRF, MNRG, or UNRI. The SC is notified of the failure and also of the MWD setting in the HLR within the Report message (see clause 10). + +In the case of a delivery failure (to an MS) with cause Mobile Station Memory Capacity Exceeded via the SGSN or the MSC, the SMS-GMSC or SMS Router requests the HLR to add, if needed, a new entry in the MWD with cause Mobile Station Memory Capacity Exceeded. This new entry contains the SC address. The HLR sets the MCEF and resets MNRF or MNRG. The SC is notified of the failure and also of the MWD setting in the HLR within the Report message (see clause 10). + +If the HLR indicates that it is able to store the SC address, then the SC shall receive an Alert SC message when the MS becomes active. + +If the HLR indicates that it is unable to store the SC address (e.g. because MWD is full), then the only way to ensure delivery is for the SC to try to retransmit the message periodically. + +When the HLR receives the MS Reachable message, if the MCEF is clear it sends an Alert SC message to the concerned SC, updates MWD and clears MNRF (if the MS is reachable via the MSC) or MNRG (if the MS is reachable via the SGSN) or UNRI (if the MS is reachable via the IP-SM-GW). + +When the HLR receives the MS Memory Capacity Available message, it sends an Alert SC message to the concerned SC, updates MWD, clears the MCEF and clears MNRF (if the MS is reachable via the MSC), UNRI (if the UE is reachable via the IP-SM-GW) or MNRG (if the MS is reachable via the SGSN). + +Case 2: MWD, MNRF, MNRG, MNRR-MSC, MNRR-SGSN and MCEF are not implemented in the HLR. + +NOTE: HLRs supporting SMSIP and having implemented MWD, MNRF, MNRG, MNRR, MCEF shall also implement UNRI and UNRR + +In the case of a delivery failure, the SC is notified that the HLR is unable to store its address in the MWD. In case of a delivery failure (to a MS) with cause Absent Subscriber, the SC is notified of the reason for the MS being absent (if the information is available). The SC must retransmit the short message periodically in order to ensure delivery. + +The HLR discards the MS Reachable message received from the VLR or SGSN without any failure or error report. + +The HLR discards the MS Memory Capacity Available message received from the MS via the MSC and the VLR or SGSN without any failure or error report. + +### 3.2.9 Status report capabilities + +The SMS also offers to the SC the capabilities of informing the MS of the status of a previously sent mobile originated short message. The status of the message can be: + +- Successfully delivered to the SME; +- The SC was not able to forward the message to the SME. The reason can be an error of permanent or temporary nature. Permanent errors can be e.g. validity period expired, invalid SME address. Errors of temporary nature can be e.g. SC-SME connection being down, SME temporarily unavailable. + +This is achieved by the SC returning a status report TPDU (SMS-STATUS-REPORT) to the originating MS when the SC has concluded the status of the short message. The status report may be initiated by a status report request within the mobile originated short message. The status report TPDU is treated as an SMS-DELIVER TPDU by the SC when it comes to delivery procedures e.g. the alerting mechanism. + +The SC may also return to a non-MS SME the status of a mobile terminated short message. This is however outside the scope of the present document. + +The status report capabilities of the SMS are optional, i.e. the choice of whether to offer status report or not is left to the SC operator. + +For reasons of resilience and/or load sharing architecture of SMSC's by network operators, the SMSC address (the RP-OA) used by the SMSC to send the Status Report to the MS cannot be guaranteed to be the same SMSC address (RP-DA) used by the MS to submit the SM to which the Status Report refers. Where an MS wishes to implement a check that these addresses correlate, a means of disabling the correlation check shall be provided at the MS through MMI. + +### 3.2.10 Reply Path + +Reply Path specified in the present document provides a way of both requesting and indicating a service centre's commitment to deliver a reply from the replying MS to the originating SME. + +Annex D deals with MS procedures, which in general are outside the scope of GSM/UMTS specifications. However, for advanced use of the SMS, including both application level protocols and human responses, it is of vital importance to guarantee that a reply-supporting MS is able to reply on every SM, to every SME capable of receiving such reply short messages. + +## 3.3 Unsuccessful short message TPDU transfer SC -> MS + +Unsuccessful message transfer SC -> MS may be caused by a variety of different errors. The description of the occurrence of the different errors and how to handle and transfer the error indications is given in GSM 44.008 [12], 3GPP TS 24.011 [13] and 3GPP TS 29.002 [15]. + +The different error indications which the SMS-GMSC shall be capable of returning to the SC following an unsuccessful short message TPDU transfer SC -> MS, are given in table 1. In some cases, additional diagnostic information may be provided. + +### 3.3.1 Errors occurring during transfer of TPDU to MS + +These errors are generally due to barring or unsupported service in the PLMN or MS. An error indication is returned to the SC from the SMS-GMSC, but further diagnostic information from the MS shall not be available. + +### 3.3.2 Errors occurring after TPDU arrives at MS + +These errors may occur due to the MS not supporting optional short message service features, or in connection with a short message application. An error indication shall be returned to the SC from the SMS-GMSC. Additionally, a TPDU (SMS-DELIVER-REPORT) containing diagnostic information may be conveyed from the MS to the originating SC, transparently through the PLMN, by means defined in 3GPP TS 24.011 [13] and 3GPP TS 29.002 [15]. The sending of the diagnostic information is optional at the MS, but when it is sent, the PLMN shall convey the information to the SC, and the SC shall support reception of the information. + +**Table 1: Error indications related to mobile terminated short message transfer which may be transferred to the originating SC** + +| Error indication | S 1) | Meaning | +|-----------------------------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Unknown subscriber | P | The PLMN rejects the short message TPDU because there is not allocated an IMSI or a directory number for the mobile subscriber in the HLR (see 3GPP TS 29.002 [15]). | +| Teleservice not provisioned | P | The PLMN rejects the short message TPDU because the recipient MS has no SMS subscription (see 3GPP TS 29.002 [15]). | +| Call barred | T | The PLMN rejects the short message TPDU due to barring of the MS (see 3GPP TS 29.002 [15], description of the Barring supplementary service, 3GPP TS 22.004 [3] and 3GPP TS 23.011[7]), description of Call barred due to Unauthorised Message Originator, 3GPP TS 29.002 [15], and description of Operator Determined Barring, 3GPP TS 22.041 [4] and 3GPP TS 23.015 [8]). | +| Facility not supported | T | The VPLMN rejects the short message TPDU due to no provision of the SMS in the VPLMN (see 3GPP TS 29.002 [15]). | +| Absent subscriber | T | The PLMN rejects the short message TPDU because
  • - there was no paging response via the SGSN, MSC or both (see GSM 44.008 [12] & 3GPP TS 29.002 [15])
  • - the IMSI GPRS or both records are marked detached (see 3GPP TS 29.002 [15]);
  • - the MS is subject to roaming restrictions (see "Roaming not allowed", 3GPP TS 29.002 [15]);
  • - deregistered in the HLR. The HLR does not have an MSC, SGSN or both numbers stored for the target MS, (see 3GPP TS 29.002 [15]);
  • - Unidentified subscriber (see 3GPP TS 29.002 [15]);
  • - MS purged (see 3GPP TS 29.002 [15]) ;
  • - the MS is not registered in the HSS/HLR for IMS;
  • - there was no SIP response received by the IP-SM-GW.
(The reasons for absence are assigned integer values in table 1a. The appropriate integer value is sent with the absent subscriber error indication as defined in 3GPP TS 29.002 [15]) | +| MS busy for MT SMS | T | The PLMN rejects the short message TPDU because of congestion encountered at the visited MSC or the SGSN. Possible reasons include any of the following events in progress:
  • - short message delivery from another SC;
  • - IMSI or GPRS detach
  • - Location Update or Inter SGSN Routing Area Update;
  • - paging;
  • - emergency call;
  • - call setup.
| +| SMS lower layers capabilities not provisioned | T | The PLMN rejects the short message TPDU due to MS not being able to support the Short Message Service.
The short message transfer attempt is rejected either due to information contained in the class-mark, or the MSC not being able to establish connection at SAPI = 3 (see GSM 44.008 [12] and 3GPP TS 29.002 [15]). | +| Error in MS | T | The PLMN rejects the short message TPDU due to an error occurring within the MS at reception of a short message, e.g. protocol error. | +| Illegal Subscriber | P | The PLMN rejects the short message TPDU because the MS failed authentication. | +| Illegal Equipment | P | The PLMN rejects the short message TPDU because the IMEI of the MS was black-listed in the EIR. | +| System failure | T | The PLMN rejects the short message TPDU due to network or protocol failure others than those listed above (see 3GPP TS 29.002 [15]). | +| Memory Capacity Exceeded | T | The MS rejects the short message since it has no memory capacity available to store the message. | + +1) : Status (Permanent or Temporary) + +The relation between the two sets of error indications is given in the table 1. Each error is classified as either "Temporary" or "Permanent". This classification gives an indication of whether or not it is probable that the MS becomes attainable within a reasonable period, and so provides the recommended action to be taken by the SC, i.e. either to store the message for later transfer, or to discard it. + +**Table 1a: Assignment of values to reasons for absence +(values must be in the range of 0 to 255, see 3GPP TS 29.002 [15])** + +| Values | Reason for absence | +|----------------------------------------------------------------------------------------------------------------|----------------------------------------| +| 0 | - no paging response via the MSC | +| 1 | - IMSI detached | +| 2 | - roaming restriction | +| 3 | - deregistered in the HLR for non GPRS | +| 4 | - MS purged for non GPRS | +| 5 | - no paging response via the SGSN | +| 6 | - GPRS detached | +| 7 | - deregistered in the HLR for GPRS | +| 8 | - MS purged for GPRS | +| 9 | - Unidentified subscriber via the MSC | +| 10 | - Unidentified subscriber via the SGSN | +| 11 | - deregistered in the HSS/HLR for IMS | +| 12 | - no response via the IP-SM-GW | +| All 'non GPRS' reasons (except for roaming restriction) can be combined with all 'GPRS' reasons and vice-versa | | +| All other integer values are reserved. | | + +## 3.4 Unsuccessful short message TPDU transfer MS -> SC + +The error indications related to mobile originated short message transfer which may be transferred to the originating MS are given in 3GPP TS 24.011 [13]. In some cases, additional diagnostic information may be provided. + +### 3.4.1 Errors occurring during transfer of TPDU to SC + +These errors are generally due to barring or unsupported service in the PLMN. An error indication is returned to the MS from the MSC or the SGSN, but further diagnostic information from the SC shall not be available. + +### 3.4.2 Errors occurring after TPDU arrives at SC + +These errors may occur due to the SC not supporting optional short message service features, or in connection with a short message application. An error indication shall be returned to the MS from the MSC or from the SGSN. Additionally, a TPDU (SMS-SUBMIT-REPORT) containing diagnostic information may be conveyed from the SC to the originating MS, transparently through the PLMN, as defined in 3GPP TS 29.002 [15] and 3GPP TS 24.011 [13]. The sending of the diagnostic information is optional at the SC, but when it is sent, the PLMN shall convey the information to the MS, and the MS shall support reception of the information. + +NOTE: The SMS-SUBMIT-REPORT is part of the negative acknowledgement to the mobile originated short message, and is not part of the status report capabilities described in clause 3.2.9. + +## 3.5 Use of Supplementary Services in combination with the Short Message Service + +Only a sub-set of the Supplementary Services defined in 3GPP TS 22.004 [3] and 3GPP TS 23.011 [7] may be used in combination with the Short Message Service. This sub-set comprises the following Supplementary Services: + +All the 5 Barring services. + +## 3.6 Applicability of Operator Determined Barring to the Short Message Service + +The network feature Operator Determined Barring (see 3GPP TS 22.041 [4]) applies to the Short Message Service. + +If a short message fails due to operator determined barring then an appropriate error cause is returned to the originator. + +## 3.7 Multiple short message transfer + +To avoid the need for a mobile to be paged, authenticated etc. for each message waiting in the Service Centre, the SC may indicate to the SMS-GMSC that there are more messages to send. When this indication is given, MAP procedures are invoked such that this indication is passed to the VMSC, and the VMSC does not release the MS until all short messages waiting in the SC have been transferred. + +## 3.8 SMS and Internet Electronic Mail interworking + +The interworking between Internet electronic mail and SMS is offered in both directions which enables new and old mobiles to send/receive Internet electronic mails via SMS. The interworking is according to the following procedures: + +- An SMS message which is required to interwork with Internet email may have its TP-PID value set for Internet electronic mail; + +NOTE: There is an alternative mechanism described in subclause 9.2.3.24 providing full RFC 5322 [34] internet electronic mail interworking. + +- Either single or concatenated SMS can be used to transport the email; +- Concatenation may be achieved by the TPUDH mechanism, in which case the concatenation is carried out at a lower level to the formats specified in subclauses 3.8.1 and 3.8.2. Alternatively, concatenation may be achieved using the text-based means described below; +- Email cc fields are not supported; +- Where multiple fields are present, additional spaces may be inserted by the sender to improve presentation of the message. Spaces may not be inserted into the actual email address (e.g. user@domain1.domain2). + +### 3.8.1 Basic Format + +The basic format for transferring email in either direction consists of the following: + +MT SMS: + +- [] + +MO SMS: + +- [] +- where [] denote optional fields and <> delimit fields. + +The to-address or from address may take the form: + +- user@domain1.domain2 + +or + +- User Name + +In the latter case the angle brackets <> are part of the address and are actually transmitted. + +Depending on the nature of the gateway, the destination/origination address is either derived from the content of the SMS TP-OA or TP-DA field, or the TP-OA/TP-DA field contains a generic gateway address and the to/from address is added at the beginning as shown above. + +Multiple addresses may be identified in MO messages by separating each address by a comma like this: + +address1,address2,address3 + +It is optional for the receiving gateway to support this. If the receiving gateway does not support multiple messages then it shall reject the original message by returning an appropriate error in a text message. + +## 3.8.2 Optional Fields + +The following further optional fields are supported. An email <-> SMS gateway may insert additional spaces in the MT message for presentation to the user, and must accept additional spaces in the MO message from the user. + +### 3.8.2.1 Subject + +The subject is placed between the address and the message, delimited by round brackets () or preceded by ##, for example: + +- []( +) + +or + +- []### + +An MO message may contain either format. An MT message may contain either format. Developers must ensure that both forms are supported for full compatibility. + +### 3.8.2.2 Real Name + +The Real Name field contains the real name of the sender and is used only in MO messages. The SC or email gateway shall generate an email message according to standard email procedures containing Real Name (the angle brackets being part of the address and hence transmitted). If a subject is to be included with the Real Name then only the ## prefix is used. + +The syntax is: + +[]#[##]# + +### 3.8.2.3 Optional Control Flag + +An optional control flag may be added to the start of the message in MO messages only. This consists of a single character following a # symbol as follows: + +[##][] + +This may also be used in combination with the above fields. It is intended for use where a particular SC or email gateway specific function is required to be invoked. For example, the control flag #A# might add a particular (pre-stored) signature to the end of the message or #R# might change the from-address to a pre-stored value or #5# might add the text "Please phone me at the office". All of these functions are open for definition by Service Centre or email gateway operators. + +## 3.8.3 Text concatenation + +If the concatenation mechanism described in subclause 9.2.3.24.1 is not supported by the transmitting or receiving entity, the following textual concatenation mechanism may be used. The first message is ended with a + sign, and each subsequent message start and end with + signs until the final message which starts with a + sign but does not end with a + sign. + +- + +- ++ +- + + +Any header fields placed on the front of an MO or MT message are not added to the second and subsequent messages. + +This provides a simple mechanism which is completely backward compatible. There is no indication of the number of messages and should a message be lost by the system or arrive out of sequence then the original message cannot be reconstructed. Therefore, wherever possible the concatenation mechanism specified in subclause 9.2.3.24.1 should be used instead. + +### 3.8.4 Alternative characters for Internet email addresses in MO SMS. + +It is difficult or impossible to generate some characters on a mobile phone and so the following alternatives may be used: + +- @ may be replaced by \* +- \_ (underscore) may be replaced by \$ + +## 3.9 SMS COMPRESSION + +Short Messages may be compressed in accordance with the compression algorithm described in 3GPP TS 23.042 [26]. + +Compression and Decompression may take place between SME's or between an SME and the SC. + +The compression only applies to the TP-User-Data part of the TPDU and excludes any TP-User-Data-Header which may be present. The Compression Header (see 3GPP TS 23.042 [26]) must commence at the first octet of the TP-User-Data field immediately following any TP-User-Data-Header field which may be present. + +The TP-UDL value must be set in accordance with that value defined for the compressed TP-User-Data case in clause 9.2.3.16. + +The TP-DCS parameter indicates whether or not a short message is compressed. If the TP-DCS parameter indicates that the short message is compressed then the alphabet encoding values (bits 2 and 3 in 3GPP TS 23.038 [9]) must be ignored by the receiving entity. + +In the case where a short message after compression is greater than 140 octets (including the Compression Header and Footer (see 3GPP TS 23.042 [26]) and any TP-User-Data-Header which may be present) then the sending entity must concatenate the short message in the normal way as described in clause 9.2.3.24.1 if it wishes to continue to send the short message. Only the first segment of the concatenated short message must contain the Compression Header defined in 3GPP TS 23.042 [26]. All segments other than the final segment must be 140 octets in length. Only the final segment contains the Compression Footer (see 3GPP TS 23.042 [26]). + +For mobile terminated compressed messages, where the MMI or the Message Class indicated in the TP-DCS requires the message to be stored in the MS then the MS shall store the compressed message as received. In the case where the MS is capable of decompression then the MS may display the decompressed message. Such an MS may optionally store the message in decompressed form subject to the MS being configured to do this via MMI. However, prior to storing the message in decompressed form, the MS may have to create a concatenated SM and carry out component modification on the TP-UDL and TP-DCS values to indicate the correct length values and that the message is no longer compressed. Transfer of messages direct from the radio interface or those stored in the MS to a TE is according to the procedure defined in 3GPP TS 27.005 [14] and is independent of whether the message is compressed or uncompressed. + +For mobile originated compressed messages, an MS capable of compression may compress a short message generated within the MS itself prior to sending it to the radio interface. An MS capable of compression may optionally compress an uncompressed message received from a TE subject to the MS being configured to do this via MMI. In such a case the MS would have to carry out component modification on the TP-UDL and TP-DCS values to indicate the correct length values and that the message is compressed. A TE may send a message (compressed or uncompressed) to the MS using the procedures defined in 3GPP TS 27.005 [14]. The MS shall store the compressed message as received and/or transfer it directly to the radio interface. + +In addition for the compression method described above, it may be possible to compress certain Information Elements of the User Data Header of a TPDU. The compression method is defined in subclause 9.2.3.24.10.1.13. + +## 3.10 Enhanced Messaging Service + +The Enhanced Messaging Service (EMS) is based upon the standard SMS, but with formatting added to the text. The formatting may permit the message to contain animations, pictures, melodies, formatted text, and vCard and vCalendar + +objects. Objects may be mixed together into one message. This clause overviews the supported features. The coding mechanisms and formats are specified in subclause 9.2.3.24.10. + +The following sub clauses describe a number of features of EMS. The data formats in the features below shall be supported (ie the UE shall behave in a predictable manner when receiving such data) but the features are supported subject to the capabilities of the UE. However, it is highly recommended that all of these features are implemented otherwise interoperability problems at the application level may result. + +### 3.10.1 Text formatting + +The following text formatting features are supported: + +#### Alignment + +- Left +- Centre +- Right +- Default (Language dependent) + +#### Font size + +- Normal +- Large +- Small + +#### Style + +- Normal +- **Bold** +- *Italic* +- Underlined +- ~~Strikethrough~~ +- Text Colour +- Text Background Colour + +### 3.10.2 Pictures + +#### Basic Pictures + +It is possible to include either a small (16\*16 pixels), large (32\*32 pixels) or pictures of variable size. These pictures have neither animation nor grey scale; they are plain black and white. All pictures are user defined. + +#### Extended Pictures + +It is possible to include extended pictures. These pictures may be black and white, greyscale or colour bit maps. The picture size is a maximum of 255 x 255 pixels. These pictures may be transmitted in a compressed form. + +### 3.10.3 Animations + +#### Predefined + +There are number of predefined animations. These animations are not sent as animation over the air interface, only the identification of them. As soon as the position of the animation in the SM data is reached, the animation corresponding to the received number shall be displayed in a manner which is manufacturer specific. + +#### User Defined + +The user-defined animations consist of 4 pictures and there are two different sizes of these animations. The picture size of the small animations are 8\*8 pixels and the large 16\*16 pixels. These animations are sent over the air interface. + +### Extended Animations + +It is possible to include extended animations. These may be black and white, greyscale or colour bit maps. The maximum size of a single animated frame is 255 x 255 pixels. The repetition of these animations may be controlled by the originator. These animations may be transmitted in a compressed form. + +## 3.10.4 Sound + +### Predefined + +There are a number of predefined sounds. These sounds are not transferred over the air interface, only the identification of them. There are 10 different sounds that can be added in the message, and as soon as the sound mark is in focus (on the display), the sound will be played. + +### User Defined + +The sender can define own melodies according to the iMelody format [33]. These melodies are transferred in the SM and can take up to 128 bytes. + +### Extended Sounds + +Monophonic melodies may be transferred using the iMelody format [33]. These may be transmitted in a compressed form. + +## 3.10.5 vCard and vCalendar + +A message may contain vCard and vCalendar objects as specified in [36][37]. These may be transmitted in a compressed form. + +## 3.10.6 WVG (Wireless Vector Graphics) Object + +A message may contain one or more WVG objects. A WVG object is a vector graphics picture or animation and is scalable. Two subtypes of WVG objects are supported; Standard WVG object and Character Size WVG object. Actual display size of a Standard WVG object depends on display screen size and MMI implementation on terminals. A Character Size WVG object has a height that equals or is similar to the height of message text but with variable width. Character Size WVG object may be edited in the same way as standard text, e.g. insertion deletion and text wrapping. + +### 3.10.6.1 Overview of WVG Graphical Primitives + +The WVG element is used to describe vector graphics objects. The vector graphics format is used to allow the creation of small pictures which may include simple animation or the creation small handwritten sketches. WVG makes use of the following graphical primitives (full detail is listed in annex G.2) These primitives can be used to describe a compact drawing. + +List of Graphical Primitives: + +- Polylines (G2.1) + - Simple Line Polyline (G.2.1.1) + - Circular Polyline (G.2.1.2) + - Bezier lines (G.2.1.3) +- Polygons (G.2.2) + - Arbitrary Polygon (G.2.2) + - Regular Polygon (G.2.4) + - Star Shaped Polygon (G.2.4) + +- Regular Grid Element (G.2.4) +- Ellipses (G.2.3.1) +- Rectangles (G.2.3.2) +- Text Element (G.2.5) +- Grouping Element (G.2.6) +- Reuse Element (G.2.7) +- Animations Elements (G.2.8) +- Frame Element (G.2.9) +- Local Element (G.2.10) + +## 4 Network architecture + +### 4.1 Basic network structure + +The exchange of messages between an MS and an SME involves the entities shown in figure 4. + +The architecture for providing SMS over a generic IP CAN is described in 3GPP TS 23.204 [42] (see subclause 5). + +The basic network structure of the SMS is depicted in figure 5. + +![Figure 4: Entities involved in the provision of SM MT and SM MO. The diagram shows a sequence of entities: SME, SMS-SC, SMS-GMSC / SMS-IWMSC *, SMS Router ***, MSC/VLR or SGSN **, and MS. A vertical dashed line separates the first two entities (SME and SMS-SC) from the rest. Below the entities, a large double-headed arrow indicates the scope of the 3GPP/GSM specification set. The left part of the arrow, containing SME and SMS-SC, is labeled 'Outside the scope of the 3GPP/GSM specification set'. The right part of the arrow, containing the remaining four entities, is labeled 'Inside the scope of the 3GPP/GSM specification set'.](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +Figure 4: Entities involved in the provision of SM MT and SM MO. The diagram shows a sequence of entities: SME, SMS-SC, SMS-GMSC / SMS-IWMSC \*, SMS Router \*\*\*, MSC/VLR or SGSN \*\*, and MS. A vertical dashed line separates the first two entities (SME and SMS-SC) from the rest. Below the entities, a large double-headed arrow indicates the scope of the 3GPP/GSM specification set. The left part of the arrow, containing SME and SMS-SC, is labeled 'Outside the scope of the 3GPP/GSM specification set'. The right part of the arrow, containing the remaining four entities, is labeled 'Inside the scope of the 3GPP/GSM specification set'. + +\*) : SMS-GMSC when the short message is transferred from the SC to the MS, SMS-IWMSC when the short message is transferred from the MS to the SC. The SC may be integrated with the SMS-GMSC/SMS-IWMSC. + +\*\*) : SGSN is used in place of the MSC for SMS transfer over GPRS. + +\*\*\*) : The SMS Router is an optional functional entity, and is used only in the MT case. + +**Figure 4: Entities involved in the provision of SM MT and SM MO** + +The reference points of figure 5 support the short message transfer in the following way: + +- message transfer on reference point 1 is described in clause 5; +- the operations performed on reference points 2 and 4 are described in 3GPP TS 29.002 [15]; +- message transfer on reference point 3 is described in subclause 4.2; +- message transfer on reference point 5 is supported by the protocol described in 3GPP TS 24.011 [13]. +- the operations performed on reference points 6 are described in 3GPP TS 29.118 [47]. + +![Diagram of the main network structure serving as a basis for the short message transfer. It shows a mobile station (MS) on the left connected to an MSC. The MSC is connected to an SMS-GMSC/SMS-IWMSC. The SMS-GMSC/SMS-IWMSC is connected to an SMS Router (optional) and an SGSN. The SMS Router is connected to the MSC and the SGSN. The SGSN is connected to the MS. Reference points are indicated by double-headed arrows between the entities.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Diagram of the main network structure serving as a basis for the short message transfer. It shows a mobile station (MS) on the left connected to an MSC. The MSC is connected to an SMS-GMSC/SMS-IWMSC. The SMS-GMSC/SMS-IWMSC is connected to an SMS Router (optional) and an SGSN. The SMS Router is connected to the MSC and the SGSN. The SGSN is connected to the MS. Reference points are indicated by double-headed arrows between the entities. + +NOTE 1: Reference point 4 is not used for SMS transfer via the SGSN + +NOTE 2: The SMS Router is an optional entity that may be present in the MT case only. If it is not present, reference point 3 extends from the SMS-GMSC directly to the MSC/SGSN. + +NOTE 3: Reference point 6 is used for SMS transfer when SMS over SGs is used and the MME is used to tunnel SMS messages. + +**Figure 5: The main network structure serving as a basis for the short message transfer** + +## 4.2 Transfer on reference point 3 + +Reference point 3 is used to support communications between: + +- MSC <-> SMS-GMSC / SMS-IWMSC; +- SGSN <-> SMS-GMSC / SMS-IWMSC; +- SMS Router <-> SMS-GMSC; +- SMS Router <-> MSC; +- SMS Router <-> SGSN. + +If any of the above two end nodes are in the same PLMN, the definition of this reference point is left to the operators. For example, this reference point may use: + +- PSPDN; or +- CCITT SS no 7 (according to 3GPP TS 29.002 [15]). + +If any of the above two end nodes are in different PLMNs, this reference point shall use CCITT SS no 7 according to 3GPP TS 29.002 [15], unless otherwise bilaterally agreed. + +# 5 Service Centre and PLMN interconnection + +The present document deals with the SC only with regard to the interchange of messages between SC and MS. Only the requirements put upon the SC by the SMS functionality are specified in the present document. + +## 5.1 Service centre connection + +One SC may be connected to several PLMNs, and may be connected to several MSCs (SMS-GMSCs or SMS-IWMSCs) within one and the same PLMN. + +The SC is addressed from the mobile by an E.164 [17] number in the numbering plan of the PLMN to which the SC is connected. This E.164 [17] number shall uniquely identify the SC to that PLMN. + +There may be an intermediate network between the PLMN and the SC; in this case the PLMN must autonomously make a connection to the SC using the SC address in this intermediate network. + +No mandatory protocol between the SC and the MSC below the transfer layer is specified by GSM/UMTS; this is a matter for agreement between SC and PLMN operators. However, annex A provides an example protocol stack which could be used. + +## 5.2 Routing requirements + +### 5.2.1 Mobile terminated short message + +The SC sends the short message to the SMS-GMSC. The SMS-GMSC interrogates the HLR to retrieve routing information necessary to forward the short message, and then sends the message to the relevant MSC or SGSN, transiting other networks if necessary and transiting an SMS Router in the HPLMN of the receiving MS if this is deployed. The MSC or SGSN then sends the short message to the MS. + +### 5.2.2 Mobile originated short message + +The MS sends the short message to the MSC or the SGSN. The MS shall always address the required SC by an E.164 [17] address. The visited PLMN shall route the message to the appropriate SMS-IWMSC in the SC's PLMN, transiting other networks if necessary. + +As an operator option, the SMS-IWMSC may interrogate the HLR to retrieve the recipient's IMSI in order to check that an SMS Interworking agreement exists between the two networks. + +--- + +## 6 Service Centre functionality + +In the present document, only the SC functionality related to the short message service between the SC and the MS is specified. + +### 6.1 Service Centre capabilities + +The SC should be capable of: + +- submitting a short message to an MS, retaining the responsibility of the message until + - 1) the report has been received; or + - 2) the Validity-Period expires. +- receiving a report from the PLMN; +- receiving a short message from an MS; +- returning a report to the PLMN for a previously received short message. + +### 6.2 SC functional requirements + +The detailed functionality of the SC is outside the scope of the present document, and is for the SC operator to define. However, the following functional requirements are mandatory for all SCs in order to support the SM-TP (see clause 9) towards the PLMN: + +- 1) To identify each SMS-DELIVER sent to an MS in a unique way, a time stamp value is included in the field TP-Service-Centre-Time-Stamp, TP-SCTS, of the SMS-DELIVER. The time stamp gives the time when the message arrived at the SC with the accuracy of a second. If two or more messages to the same MS arrive at the SC within one second, the SC shall modify the time stamp of those messages in such a way that: + - a) all messages to the MS contain different time stamps; + - b) the modification of the time stamps is kept to a minimum. + +- 2) The SC is only allowed to have one outstanding SMS-DELIVER (i.e. a message for which a report has not been received) to a specific MS at a given time. +- 3) The SC shall be able to initiate overwriting of short messages previously received by the SC if requested by the same originating address (MS or any other source) by use of the same message type. + +## 6.2.1 Subaddressing support + +Support for subaddressing is an optional functional requirement for an SC. If it is supported, subaddressing information shall be conveyed from SME to SME according the following rules: + +- A SME may send a SM with '\*'s or '#'s included in the TP-DA field. The first '#' encountered in TP-DA indicates where the address for SC routing purposes is terminated. Additional '\*'s or '#'s can be present in the following digits, and all these digits including the first '#' are subaddress digits. +- When the SC receives a SM to convey with such a subaddress information, it should deliver the SM to the destination SME with the same subaddress digits copied in the TP-OA field. + +This subaddressing mechanism does not apply when the TON is alphanumeric + +Example: + +SME with number 987654321 sends a SM with TP-DA = 1234#56#789\* + +SME with number 1234 will receive the SM with TP-OA = 987654321#56#789\* + +## 6.2.2 Support for trigger SMS filtering for Tsms submissions + +Support for trigger SMS filtering for Tsms submissions is an optional functional requirement for an SC as specified in 3GPP TS 23.682 [48]. If it is supported, the SC uses the TP-Protocol-Identifier containing a Device Triggering Short Message code as an indication of trigger SMS and compare list of known SME against the SME in the RP-OA field of received short message to filter and block all short messages that do not originate from trusted SMEs. + +## 6.3 SC EMS Extended Object Data Request Command Feature + +An SME has the ability of determining which data formats within the Extended Object IE are supported by a specific terminal. The SC has the option of supporting this feature using an SMS-DELIVER PDU. This SMS-DELIVER PDU shall contain the EMS Data Format Delivery Request IE, and be marked for automatic deletion by the mobile station. + +--- + +## 7 MS functionality + +In the present document, only the MS functionality related to the short message service between the SC and the MS is specified. + +### 7.1 MS capabilities + +The MS, when equipped for SMS, should be capable of: + +- submitting a short message TPDU to an SC, retaining the responsibility of the message until: + - 1) the report arrives from the network; or + - 2) a timer expires. +- receiving a short message TPDU from an SC; +- returning a delivery report to the network for a previously received short message; +- receiving a report from the network; +- notifying the network when it has memory capacity available to receive one or more short messages when it has previously rejected a short message because its memory capacity was exceeded; + +- notifying the SC when a short message is intended to replace a short message the MS has previously submitted to the same destination address. + +It is recommended that an MS supporting both replying and automatic SC selection (as specified in clause D.2 of annex D) follows procedures specified in annex D when replying to MT short messages with MO short messages. + +It is recommended that an MS supporting a capability for requesting a reply path follows procedures specified in annex D. + +## 7.2 MS configuration + +The reference configuration is assumed as in figure 6, i.e. only the case where the terminal is integrated in the MS is considered. + +![Figure 6: Reference configuration of the MS which apply to the SMS. The diagram shows a box labeled 'MTO' connected to a line that ends in a small circle labeled 'Um'.](409498e57b1f988b2b604d12cd997002_img.jpg) + +``` + +graph LR + MTO[MTO] --- Um((Um)) + +``` + +Figure 6: Reference configuration of the MS which apply to the SMS. The diagram shows a box labeled 'MTO' connected to a line that ends in a small circle labeled 'Um'. + +**Figure 6: Reference configuration of the MS which apply to the SMS** + +NOTE: It is foreseen that a terminal interface may be offered, e.g. for higher layer protocols, memory capacity reasons or to be able to type in mobile originated messages. This terminal interface is regarded as an implementation option, although, where offered, it must be based upon an R- or S-reference point. 3GPP TS 27.005 [14] provides an example based on the R reference point. + +## 8 Node functionality + +The overall requirements to the MSC, SMS-GMSC, SMS-IWMSC, SGSN and SMS Router with respect to handling of the Short Message Service is to cater for the routing and necessary intermediate buffering of the short messages. + +### 8.1 Node functionality related to SM MT + +#### 8.1.1 Functionality of the SMS-GMSC + +When receiving a short message TPDU from the SC, the SMS-GMSC is responsible for the following operations: + +- reception of the short message TPDU; +- inspection of the parameters. + +NOTE 1: The SMS-GMSC may be identical to the MSC. + +if parameters are incorrect: + +- returning the appropriate error information to the SC in a failure report (see clauses 9 and 10); + +if errors are not found within parameters: + +- interrogating the HLR ("sendRoutingInfoForShortMsg", see clause 10); retrieving routing information or possible error information; + +if HLR is returning error information: + +- returning the appropriate error information to the SC in a failure report (see clauses 9 and 10); + +if no errors are indicated by the HLR: + +- transferring the short message TPDU to the MSC or SGSN using the routing information obtained from the HLR ("forwardShortMessage", see clause 10); + +NOTE 2: In case where two addresses (SGSN and MSC) are received from HLR, the SMS-GMSC may choose (operator dependant) via which nodes (SGSN or MSC) the SMS is first to be sent. The SMS delivery via the SGSN is normally more radio resource efficient than the SMS delivery via the MSC. + +if one address (SGSN or MSC) is received from HLR: + +- When receiving the report associated with the short message from the MSC or SGSN (positive or negative outcome of "forwardShortMessage", see clause 10), the SMS-GMSC is responsible for the following operations; + +if the report indicates successful delivery: + +- notifying the HLR of the successful delivery via the MSC or the SGSN, which shall cause the HLR to alert any service centres whose addresses are stored in the MWD for the MS; +- creating and sending the successful report to the SC; + +if the report is a failure report indicating "absent subscriber" via the MSC or the SGSN (see clause 3.3): + +- requesting the HLR to insert the address of the originating SC into the MWD (if implemented) with cause Absent Subscriber ("SM\_DeliveryReportStatus", see clauses 9 and 10); +- informing the HLR of the reason for the MS being absent via the MSC or the SGSN (if this information is available); +- establishing, where necessary, a link with the addressed SC (see clause 5); +- creating and sending the negative report to the SC which should include the reason for the MS being absent (if this information is available) so that the SC may adjust any retry algorithm appropriately (see clauses 9 and 10); + +if the report is a failure report indicating "MS memory capacity exceeded" via the MSC or the SGSN (see clause 3.3): + +- requesting the HLR to insert the address of the originating SC into the MWD (if implemented) with cause MS Memory Capacity Exceeded via the MSC or the SGSN ("SM\_DeliveryReportStatus", see clauses 9 and 10); +- establishing, where necessary, a link with the addressed SC (see clause 5); +- creating and sending the report to the SC (see clauses 9 and 10). + +if two addresses (SGSN and MSC) are received from HLR: + +- When receiving the first report associated with the short message from the MSC or SGSN (positive or negative outcome of "forwardShortMessage", see clause 10), the SMS-GMSC is responsible for the following operations: + +if the first report indicates successful delivery: + +- notifying the HLR of the successful delivery via the MSC or the SGSN, which shall cause the HLR to alert any service centres whose addresses are stored in the MWD for the MS; +- creating and sending the successful report to the SC; + +if the first report is a failure report indicating: + +- - Unidentified subscriber; +- - Facility not supported; +- - Absent subscriber with indication: GPRS or IMSI Detach; +- - System failure; +- - Unexpected data value; +- - Data missing; +- GPRS connection suspended (see 3GPP TS 29.002 [15]); +- SM Delivery Failure with indication: equipment Not SM Equipped; +- transferring the short message TPDU to the second path using the routing information obtained from HLR. + +if the second report indicates successful delivery: + +- notifying the HLR of the successful delivery of the second transfer via the MSC or SGSN, which shall cause the HLR to alert any service centres whose addresses are stored in the MWD for the MS; +- notifying the HLR of the unsuccessful delivery at first transfer only with cause "absent subscriber"; +- notifying the HLR of the reason for the MS being absent via the MSC or the SGSN (if this information is available); +- establishing, when necessary, a link with the addressed SC (see clause 5); +- creating and sending the successful report to the SC; + +if the second report is a failure report: + +- requesting the HLR to insert the address of the originating SC into the MWD (if implemented) only if at least one of the first or second report failed due to "MS Memory Capacity Exceeded" or "Absent Subscriber" ("SM\_DeliveryReportStatus", see clauses 9 and 10); +- notifying the HLR only with the causes "Absent Subscriber", "Memory Capacity Exceeded" via the MSC or the SGSN, or both; +- notifying the HLR of the reason for the MS being absent via the MSC, SGSN or both (if this information is available); +- establishing, where necessary, a link with the addressed SC (see clause 5); +- creating and sending the negative report to the SC with errors from first and second path (see clauses 9 and 10). + +## 8.1.2 Functionality of the MSC + +When receiving a short message TPDU from the SMS-GMSC ("forwardShortMessage", see clause 10), the MSC is responsible for the following operations: + +- reception of the short message TPDU; +- the receiving network may verify if the received SM-SC address (contained in RP-OA IE) and SCCP Calling Party Address are of the same PLMN; +- retrieving information from the VLR ("sendInfoFor-MT-SMS", see clause 10); location area address and, when appropriate, error information; + +if errors are indicated by the VLR: + +- returning the appropriate error information to the SMS-GMSC in a failure report (negative outcome of "forwardShortMessage" see clauses 10 and 11); + +if no errors are indicated by the VLR: + +- transferring the short message to the MS (see 3GPP TS 24.011 [13]). + +When receiving a confirmation that the message is received by the MS (see 3GPP TS 24.011 [13]): + +- relaying the delivery confirmation to the SMS-GMSC in a delivery report (positive outcome of "forwardShortMessage", see clauses 10 and 11). + +When receiving a failure report of the short message transfer to the MS (see 3GPP TS 24.011 [13]): + +- returning the appropriate error information to the SMS-GMSC in a failure report (negative outcome of "forwardShortMessage", see clause 10). + +When receiving a notification from the MS that it has memory available to receive one or more short messages (see 3GPP TS 24.011 [13]): + +- relaying the notification to the VLR ("mSMemoryCapacityAvailable", see clause 10); + +if errors are indicated by the VLR: + +- returning the appropriate error information to the MS in a failure report (negative outcome of "ReadyForSM", see clauses 10 and 11). + +When there is an ongoing MT-SMS transfer to the MS (see 3GPP TS 24.011 [13]), or other busy condition for MT-SMS, the MSC has the option to store the TPDU in a queue for a short time (which must be shorter than the supervision timer defined in 3GPP TS 29.002 [15]). The maximum time that a message may be queued is related to the permitted delay for the MSC to respond to the SMS-GMSC. When the MS becomes available for MT-SMS transfer, the stored TPDU are delivered to the MS on a first-in first-out basis. If a message is not successfully transferred to the MS within the permitted time, the MSC returns an appropriate error to the SMS-GMSC. + +NOTE: The reaction of MSC when the message verification failed is operator specific and not specified in 3GPP specifications. + +### 8.1.3 Functionality of the SGSN + +When receiving a short message TPDU from the SMS-GMSC ("forwardShortMessage", see clause 10), the SGSN is responsible for the following operations: + +- reception of the short message TPDU; +- the receiving network may verify if the received SM-SC address (contained in RP-OA IE) and SCCP Calling Party Address are of the same PLMN. + +if errors are detected by the SGSN: + +- returning the appropriate error information to the SMS-GMSC in a failure report (negative outcome of "forwardShortMessage" see clauses 10 and 11); + +if no errors are detected by the SGSN: + +- transferring the short message to the MS (see 3GPP TS 24.011 [13]). + +When receiving a confirmation that the message is received by the MS (see 3GPP TS 24.011 [13]): + +- relaying the delivery confirmation to the SMS-GMSC in a delivery report (positive outcome of "forwardShortMessage", see clauses 10 and 11). + +When receiving a failure report of the short message transfer to the MS (see 3GPP TS 24.011 [13]): + +- returning the appropriate error information to the SMS-GMSC in a failure report (negative outcome of "forwardShortMessage", see clause 10). + +When receiving a notification from the MS that it has memory available to receive one or more short messages (see 3GPP TS 24.011 [13]): + +if errors are detected by the SGSN: + +- returning the appropriate error information to the MS in a failure report (negative outcome of "ReadyForSM", see clauses 10 and 11). + +if no errors are detected by the SGSN: + +- notifying the HLR of memory available in the MS via the SGSN with "ReadyForSM" (see clauses 10 and 11). + +When the MS is becoming reachable again (see GSM 44.008 [12]): + +- notifying the HLR of MS being reachable via the SGSN (and via the MSC if any) with "ReadyForSM" (see clauses 10). + +When there is an ongoing MT-SMS transfer to the MS (see 3GPP TS 24.011 [13]), or other busy condition for MT-SMS, the SGSN has the option to store the TPDU in a queue for a short time (which must be shorter than the supervision timer defined in 3GPP TS 29.002 [15]). The maximum time that a message may be queued is related to the permitted delay for the SGSN to respond to the SMS-GMSC. When the MS becomes available for MT-SMS transfer, the stored TPDU are delivered to the MS on a first-in first-out basis. If a message is not successfully transferred to the MS within the permitted time, the SGSN returns an appropriate error to the SMS-GMSC. + +NOTE: The reaction of SGSN when the message verification failed is operator specific and not specified in 3GPP specifications. + +### 8.1.4 Functionality of the SMS Router + +When receiving a routing information retrieval ("sendRoutingInfoForShortMsg", see clause 10), the SMS Router is responsible for the following operations: + +- interrogating the HLR ("sendRoutingInfoForShortMsg", see clause 10); retrieving routing information or possible error information. This interrogation may be omitted if a parameter within the "sendRoutingInfoForShortMsg" explicitly indicates that delivery of a short message is not intended and only MCC+MNC are requested. + +if HLR is returning error information: + +- forwarding the returned error information transparently to the SMS-GMSC; + +if no errors are indicated by the HLR: + +- creating an MT Correlation ID; +- storing against the MT Correlation ID: the IMSI, the MSC address and/or the SGSN address. The address of the SMS-GMSC and the destination MSISDN may also be stored. Creating an MT Correlation ID and storing these data against the MT Correlation ID may be omitted if a parameter within the "sendRoutingInfoForShortMsg" explicitly indicates that delivery of a short message is not intended; +- forwarding the returned information to the SMS-GMSC populating the IMSI IE with the MT Correlation ID and either: + +- a) the MSC address and/or SGSN address with the address of the SMS Router; or + +NOTE 1: In this case if two addresses (SGSN and MSC) are received from HLR, the SMS-GMSC chooses (operator dependant) via which node (SGSN or MSC) the SM is first to be sent, not the SMS Router. + +- b) the address of the SMS Router. In this case the SMS Router delivers the SM as described in 3GPP TS 23.204 [42] for the IP-SM-GW. This option is mandatory when the SMS Router is deployed together with an IP-SM-GW. + +NOTE 2: In this case if two addresses (SGSN and MSC) are received from HLR, the SMS Router chooses via which node (SGSN or MSC) the SM is first to be sent, i.e. the SMS Router delivers the SM as an IP-SM-GW. + +If a parameter within the "sendRoutingInfoForShortMsg" explicitly indicates that delivery of a short message is not intended and that only IMSI or only MCC+MNC are requested, the IMSI IE may be populated with IMSI or MCC+MNC+dummy MSIN, respectively, and the MSC address and/or SGSN address with a dummy network node address. + +if HLR is returning an Inform-Service-Centre information: + +- forwarding the received information transparently to the SMS-GMSC. + +When receiving a short message TPDU from the SMS-GMSC ("forwardShortMessage", see clause 10), the SMS Router is responsible for the following operations: + +- receiving the short message TPDU; +- forwarding the trigger SMS to filtering infrastructure to filter and block all trigger SMS that does not originate from SMS-GMSC in the HPLMN; +- checking validity of the MT Correlation ID received in the IMSI field + +SMS Router can use the TP-Protocol-Identifier containing a Device Triggering Short Message code as an indication of trigger SMS and compare list of known SMS-GMSC against the SMS-GMSC in the RP-OA field of received short message to filter and block all short messages that do not originate from SMS-GMSC in the HPLMN. + +The MT Correlation ID shall be considered invalid if the MT Correlation ID is unknown. Optionally, the MT Correlation ID may also be considered invalid if the CC and NDC of the address of the SMS-GMSC from which the forwardShortMessage was received is different from the CC and NDC of the SMS-GMSC address stored above i.e. the forwardShortMessage has originated from a different network than that which issued the sendRoutingInfoForShortMsg. + +If the received MT Correlation ID is deemed invalid by the SMS Router: + +- returning the error "System failure" to the SMS-GMSC in a failure report (negative outcome of "forwardShortMessage" see clauses 10 and 11). + +If the received MT Correlation ID is deemed valid by the SMS Router: + +- transferring the short message TPDU to the MSC (if the called party SSN in the received message is for MSC) or to the SGSN (if the called party SSN in the received message is for SGSN) using the stored routing information and replacing the MT Correlation ID with the stored IMSI (obtained from the HLR, above); +- support for service execution, lawful interception, and number portability if required; +- forwarding the delivery confirmation or failure report from the MSC or SGSN (which may have originally come from the MS) transparently to the SMS-GMSC; and +- if the SMS Router finds that SMS delivery is to be performed towards serving MSC or SGSN in a different PLMN, the SMS Router may replace the SMS-SC address in RP OA with an address containing the PLMN ID of the PLMN in which the SMS-Router is located before the SMS router forwards the request to the serving MSC or SGSN. + +NOTE 3: This option can be used if the PLMN that deploys the SMS-router wants to ensure the delivery of a MT-SMS to a UE roaming in a different PLMN and this PLMN is known to deploy PLMN ID check on both RP-OA IE and SCCP Global Title. + +NOTE 4: When using this functionality, the PLMN deploying the SMS-Router must be aware that reply path functionality offered by the originating SMS-SC cannot be used. + +## 8.1.5 Functionality of the IP-SM-GW + +The IP-SM-GW is described in 3GPP TS 23.204 [42], it provides: + +- protocol interworking for delivery of short message between the IP-based UE and the SMSC; +- delivery of the SM to the MSC/SGSN if needed as described in 3GPP TS 23.204 [42]; and +- support for service execution, lawful interception, and number portability if required. + +## 8.2 Node functionality related to SM MO + +### 8.2.1 Functionality of the MSC + +When receiving a short message TPDU from the MS, the MSC is responsible for the following operations: + +- reception of the short message TPDU (see 3GPP TS 24.011 [13]); +- retrieving information from the VLR ("sendInfoForMO-SMS", see clause 10); the MSISDN of the MS and, when appropriate, error information. The retrieval of information from the VLR is followed by the VLR investigating the MNRF (to be used in the alerting procedure, see clause 10) + +if errors are indicated by the VLR: + +- returning the appropriate error information to the MS in a failure report (negative outcome of "sendInfoForMO-SMS" see clauses 10 and 11); + +if no errors are indicated by the VLR: + +- inspection of the RP-DA parameter; + +if parameters are incorrect: + +- returning the appropriate error information to the MS in a failure report (see 3GPP TS 24.011 [13]); + +if no parameter errors are found: + +NOTE: The SMS-IWMSC may be identical to the MSC. + +- transferring the short message TPDU to the SMS-IWMSC ("forwardShortMessage", see clause 10). + +When receiving the report of the short message from the SMS-IWMSC (positive or negative outcome of the "forwardShortMessage", see clause 10), the MSC is responsible for the following operations: + +- relaying the report to the MS (see 3GPP TS 24.011 [13]). + +## 8.2.2 Functionality of the SMS-IWMSC + +When receiving a short message TPDU from the MSC, IP-SM-GW or SGSN ("forwardShortMessage", see clause 10), the SMS-IWMSC is responsible for the following operations: + +- reception of the short message TPDU; +- optionally, interrogating the HLR ("sendRoutingInfoForShortMsg", see clause 10); retrieving the recipient's IMSI in order to check for the existence of an SMS Interworking agreement before establishing a link with the addressed SC; + +if HLR returns error information: + +- returning the appropriate error information to the MSC or SGSN in a failure report (negative outcome of "forwardShortMessage", see clause 10); + +if no errors are indicated by the HLR: + +- inspecting the IMSI parameter and ignoring the other routing information; + +if the received parameter is unacceptable to the SMS-IWMSC (due to lack of an SMS Interworking agreement): + +- returning SM Delivery Failure with indication: invalid SME-address to the MSC or SGSN; + +if the parameter is acceptable to the SMS-IWMSC (due to the existence of an SMS Interworking agreement) or the SMS-IWMSC didn't apply the optional HLR interrogation: + +- establishing, where necessary, a link with the addressed SC (see clause 5); +- transferring the short message TPDU to the SC (if the address is valid); + +if a report associated with the short message is received from the SC, the SMS-IWMSC is responsible for the following operations: + +- relaying of the report to the MSC or SGSN (positive or negative outcome of "forwardShortMessage", see clause 10); + +if a report associated with the short message is not received from the SC before a timer expires or if the SC address is invalid, the SMS-IWMSC is responsible for the following operations: + +- returning the appropriate error information to the MSC or SGSN in a failure report (negative outcome of "forwardShortMessage", see clause 10). + +The value of the timer is dependent on the protocol between the SC and the SMS-IWMSC. + +## 8.2.3 Functionality of the SGSN + +When receiving a short message TPDU from the MS, the SGSN is responsible for the following operations: + +- reception of the short message TPDU (see 3GPP TS 24.011 [13]); +- inspection of the RP-DA parameter; + +if parameters are incorrect: + +- returning the appropriate error information to the MS in a failure report (see 3GPP TS 24.011 [13]); + +if no parameter errors are found: + +- transferring the short message TPDU to the SMS-IWMSC ("forwardShortMessage", see clause 10). + +When receiving the report of the short message from the SMS-IWMSC (positive or negative outcome of the "forwardShortMessage", see clause 10), the SGSN is responsible for the following operations: + +- relaying the report to the MS (see 3GPP TS 24.011 [13]). + +## 8.2.4 Functionality of the IP-SM-GW + +Successful SM MO delivery procedure with IP-SM-GW is described in 3GPP TS 23.204 [42] (see subclause 6.3). + +## 8.3 SMS-IWMSC functionality related to alerting + +When receiving an alert from the HLR ("alertServiceCentre", see clause 10), the SMS-IWMSC is responsible for the following operations: + +- inspect the SC address; +- generate an RP-Alert-SC (see clause 9); +- transferring the RP-Alert-SC to the SC. + +NOTE: If the SC address is not valid, then no further action shall be taken. + +# 9 Protocols and protocol architecture + +The protocol layers of the SMS are structured as shown in figure 7. + +![Figure 7: Protocol layer overview for the Short Message Service. The diagram shows five functional entities: SMS-SC, SMS-GMSC / SMS-IWMSC, SMS Router, MSC/VLR or SGSN, and MS. Below these entities, four protocol layers are shown: SM-AL, SM-TL, SM-RL, and SM-LL. SM-AL and SM-TL layers have direct connections between the SMS-SC and the MS. SM-RL and SM-LL layers have connections between the SMS-SC and the MS, passing through the SMS-GMSC / SMS-IWMSC and the MSC/VLR or SGSN. The SMS Router is shown as an optional entity between the SMS-GMSC / SMS-IWMSC and the MSC/VLR or SGSN.](a798c1bd0503d58906cf07d55f80ab83_img.jpg) + +Figure 7: Protocol layer overview for the Short Message Service. The diagram shows five functional entities: SMS-SC, SMS-GMSC / SMS-IWMSC, SMS Router, MSC/VLR or SGSN, and MS. Below these entities, four protocol layers are shown: SM-AL, SM-TL, SM-RL, and SM-LL. SM-AL and SM-TL layers have direct connections between the SMS-SC and the MS. SM-RL and SM-LL layers have connections between the SMS-SC and the MS, passing through the SMS-GMSC / SMS-IWMSC and the MSC/VLR or SGSN. The SMS Router is shown as an optional entity between the SMS-GMSC / SMS-IWMSC and the MSC/VLR or SGSN. + +NOTE: The SMS Router is an optional functional entity, and is used only in the MT case. + +**Figure 7: Protocol layer overview for the Short Message Service** + +The present document specifies the protocol at the SM-TL, the service offered by the SM-TL at the MS and the SC, and the service offered by the SM-RL at the SC. + +Note that while normally SM-TL terminates at the SC in SM MO, the SMS-IWMSC may inspect TP-DA in SMS-SUBMIT for the purpose of checking the existence of an SMS interworking agreement (see clause 8.2.2). + +## 9.1 Protocol element features + +### 9.1.1 Octet and Bit transmission order + +The octets are transmitted according to their individual numbering; the octet with the lowest number being transmitted first. The bits within each octet are transmitted according to their individual numbering also; the bits with the lowest internal number being transmitted first. + +### 9.1.2 Numeric and alphanumeric representation + +For parameters within the TPDU, there are four ways of numeric representation: Integer representation, octet, semi-octet and alphanumeric representation. + +#### 9.1.2.1 Integer representation + +Wherever the bits from a number of octets, complete or in fractions, are to represent an integer, the interpretation shall be according to the following: + +- 1) Between octets: the octets with the lowest octet numbers shall contain the most significant bits, i.e. the byte order shall be big endian. +- 2) Within an octet: the bits with the highest bit numbers shall be the most significant. + +Below is given an example of octet and bit representation and transmission order of an integer represented field. + +Let the 2 rightmost bits of octet no 5, the complete octet no 6 and 7, and the 3 leftmost bits of octet no 8 represent an integer, as shown in figure 8. + +![Diagram showing the mapping of bits from octets 5, 6, 7, and 8 to a 21-bit integer. Part α) shows a table of octet numbers and bit positions. Part β) shows the sequence of bits in order of significance. Part γ) shows the transmission order with brackets and arrows indicating the mapping from β) to γ).](8e80de0cac529b2c3775d677c5203133_img.jpg) + +α) + +| | | | | | | | | | +|---------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Oct.no. | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| 5 | | | | | | | 5 b1 | 5 b0 | +| 6 | 6 b7 | 6 b6 | 6 b5 | 6 b4 | 6 b3 | 6 b2 | 6 b1 | 6 b0 | +| 7 | 7 b7 | 7 b6 | 7 b5 | 7 b4 | 7 b3 | 7 b2 | 7 b1 | 7 b0 | +| 8 | 8 b7 | 8 b6 | 8 b5 | | | | | | + +β) + +5b1 5b0 6b7 6b6 ..... 6b1 6b0 7b7 7b6 ..... 7b1 7b0 8b7 8b6 8b5 + +γ) + +5b0 5b1 5b2 5b3 5b4 5b5 5b6 5b7 6b0 6b1 6b2 6b3 6b4 6b5 6b6 6b7 > + +> 7b0 7b1 7b2 7b3 7b4 7b5 7b6 7b7 | 8b0 8b1 8b2 8b3 8b4 | 8b5 8b6 8b7 + +Diagram showing the mapping of bits from octets 5, 6, 7, and 8 to a 21-bit integer. Part α) shows a table of octet numbers and bit positions. Part β) shows the sequence of bits in order of significance. Part γ) shows the transmission order with brackets and arrows indicating the mapping from β) to γ). + +\*) : Bits not representing the integer. + +**Figure 8: 21 bits from the octets 5, 6, 7, and 8 in a short message α) shall represent an integer as shown in β), and shall be transmitted in an order as shown in γ)** + +### 9.1.2.2 Octet representation + +A field which is octet represented, shall always consist of a number of complete octets. Each octet within the field represents one decimal digit. The octets with the lowest octet numbers shall contain the most significant decimal digits. + +### 9.1.2.3 Semi-octet representation + +A field which is semi-octet represented, shall consist of a number of complete octets and - possibly - one half octet. Each half octet within the field represents one decimal digit. The octets with the lowest octet numbers shall contain the most significant decimal digits. Within one octet, the half octet containing the bits with bit numbers 0 to 3, shall represent the most significant digit. + +In the case where a semi-octet represented field comprises an odd number of digits, the bits with bit numbers 4 to 7 within the last octet are fill bits and shall always be set to "1111". + +If a mobile receives an address field containing non-integer information in the semi-octets other than "1111" (e.g. 1110) it shall display the semi-octet as the representation given in GSM 44.008 [12] under "called BCD number", viz 1010="\*", 1011="#", 1100="a", 1101="b", 1110="c". In the event of a discrepancy between the values quoted here and the values specified in GSM 44.008[12] then GSM 44.008 [12] shall take precedence. If a mobile receives "1111" in a position prior to the last semi-octet then processing shall commence with the next semi-octet and the intervening semi-octet shall be ignored. + +Within each semi octet, the bits with the highest bit numbers shall be the most significant. + +Below is given an example: + +Octet no: + +| | | | | | | | | | +|-----|---------|---|---|---|---------|--|--|--| +| n+1 | Digit 2 | | | | Digit 1 | | | | +| n+2 | Digit 4 | | | | Digit 3 | | | | +| n+3 | 1 | 1 | 1 | 1 | Digit 5 | | | | + +### 9.1.2.4 Alphanumeric representation + +A field which uses alphanumeric representation shall consist of a number of 7-bit characters represented as the default alphabet defined in 3GPP TS 23.038 [9]. + +### 9.1.2.5 Address fields + +Address fields used by SM-RL are specified in 3GPP TS 24.011 [13] and 3GPP TS 29.002 [15]. + +Each address field of the SM-TL consists of the following sub-fields: An Address-Length field of one octet, a Type-of-Address field of one octet, and one Address-Value field of variable length; as shown below: + +![Diagram of an address field structure. It shows a vertical stack of octets. The first octet is labeled '1' and corresponds to 'Address-Length'. The second octet is labeled '2' and corresponds to 'Type-of-Address'. Octets 3, 4, and 5 are grouped by a bracket on the right as 'Address-Value'. A dotted line indicates a variable number of octets. The last octet is labeled with the Greek letter mu (μ). A bracket on the left groups all octets from 1 to μ as 'Addr.'. Vertical ellipses are shown above and below the stack.](762a17cd79880dbca172bcbbe9375223_img.jpg) + +Diagram of an address field structure. It shows a vertical stack of octets. The first octet is labeled '1' and corresponds to 'Address-Length'. The second octet is labeled '2' and corresponds to 'Type-of-Address'. Octets 3, 4, and 5 are grouped by a bracket on the right as 'Address-Value'. A dotted line indicates a variable number of octets. The last octet is labeled with the Greek letter mu (μ). A bracket on the left groups all octets from 1 to μ as 'Addr.'. Vertical ellipses are shown above and below the stack. + +The Address-Length field is an integer representation of the number of useful semi-octets within the Address-Value field, i.e. excludes any semi octet containing only fill bits. + +The Type-of-Address field format is as follows: + +| | | | | | | | | +|---|----------------|--|--|-------------------------------|--|--|--| +| 1 | Type-of-number | | | Numbering-plan-identification | | | | +|---|----------------|--|--|-------------------------------|--|--|--| + +## Type-of-number: + +Bits 6 5 4 + +- 0 0 0 Unknown 1) +- 0 0 1 International number 2) +- 0 1 0 National number 3) +- 0 1 1 Network specific number 4) +- 1 0 0 Subscriber number 5) +- 1 0 1 Alphanumeric, (coded according to 3GPP TS 23.038 [9] GSM 7-bit default alphabet) +- 1 1 0 Abbreviated number +- 1 1 1 Reserved for extension + +The MS shall interpret reserved values as "Unknown" but shall store them exactly as received. + +The SC may reject messages with a type of number containing a reserved value or one which is not supported. + +Reserved values shall not be transmitted by an SC conforming to this version of the specification. + +- 1) "Unknown" is used when the user or network has no a priori information about the numbering plan. In this case, the Address-Value field is organized according to the network dialling plan, e.g. prefix or escape digits might be present. +- 2) The international format shall be accepted also when the message is destined to a recipient in the same country as the MSC or as the SGSN. +- 3) Prefix or escape digits shall not be included. +- 4) "Network specific number" is used to indicate administration/service number specific to the serving network, e.g. used to access an operator. +- 5) "Subscriber number" is used when a specific short number representation is stored in one or more SCs as part of a higher layer application. (Note that "Subscriber number" shall only be used in connection with the proper PID referring to this application). + +## Numbering-plan-identification + +Bits 3 2 1 0 + +- 0 0 0 0 Unknown + - 0 0 0 1 ISDN/telephone numbering plan (E.164 [17]/E.163[18]) + - 0 0 1 1 Data numbering plan (X.121) + - 0 1 0 0 Telex numbering plan + - 0 1 0 1 Service Centre Specific plan 1) + - 0 1 1 0 Service Centre Specific plan 1) + - 1 0 0 0 National numbering plan + - 1 0 0 1 Private numbering plan + - 1 0 1 0 ERMES numbering plan (ETSI DE/PS 3 01-3) + - 1 1 1 1 Reserved for extension +- All other values are reserved. + +- 1) "Service Centre specific number" is used to indicate a numbering plan specific to External Short Message Entities attached to the SMSC. + +For Type-of-number = 101 bits 3,2,1,0 are reserved and shall be transmitted as 0000. Note that for addressing any of the entities SC, MSC, SGSN or MS, Numbering-plan-identification = 0001 shall always be used. However, for addressing the SME, any specified Numbering-plan-identification value may be used. + +The MS shall interpret reserved values as "Unknown" but shall store them exactly as received. + +The SC may reject messages with a type of number containing a reserved value or one which is not supported. + +Reserved values shall not be transmitted by an SC conforming to this version of the specification. + +Within the Address-Value field, either a semi-octet or an alphanumeric1) representation applies. + +The maximum length of the full address field (Address-Length, Type-of-Address and Address-Value) is 12 octets. + +1) Applies only to addressing at the SM-TL. + +## 9.2 Service provided by the SM-TL + +### 9.2.1 General + +The Short Message Transfer Layer (SM-TL) provides a service to the Short Message Application Layer (SM-AL). This service enables the SM-AL to transfer short messages to its peer entity, receive short messages from its peer entity and receive reports about earlier requests for short messages to be transferred. + +In order to keep track of messages and reports about those messages, primitives between the SM-AL and SM-TL contain a Short Message Identifier (SMI), which is a reference number for the message associated with the primitive. This Short Message Identifier is mapped to and from the Short Message Identifier used between the SM-TL and the Short Message Relay Layer (SM-RL). The Short Message Identifier is not carried between entities and therefore a given message may have different SMIs at the MS and SC sides (see clause 9.3.1 below). + +The SM-TL communicates with its peer entity by the protocol described in the following clauses. + +### 9.2.2 PDU Type repertoire at SM-TL + +The SM-TL comprises the following six PDUs: + +- SMS-DELIVER, conveying a short message from the SC to the MS; +- SMS-DELIVER-REPORT, conveying; + - a) a failure cause (if necessary); + - b) information as part of a positive or negative acknowledgement to an SMS-DELIVER or SMS-STATUS-REPORT; +- SMS-SUBMIT, conveying a short message from the MS to the SC; +- SMS-SUBMIT-REPORT, conveying; + - a) a failure cause (if necessary); + - b) information as part of a positive or negative acknowledgement to an SMS-SUBMIT or SMS-COMMAND; +- SMS-STATUS-REPORT, conveying a status report from the SC to the MS; +- SMS-COMMAND, conveying a command from the MS to the SC. + +### 9.2.2.1 SMS-DELIVER type + +Basic elements of the SMS-DELIVER type: + +| Abbr. | Reference | P 1) | R 2) | Description | +|---------|-------------------------------|-----------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| TP-MTI | TP-Message-Type-Indicator | M | 2b | Parameter describing the message type. | +| TP-MMS | TP-More-Messages-to-Send | M | b | Parameter indicating whether or not there are more messages to send | +| TP-LP | TP-Loop-Prevention | O | b | Parameter indicating that SMS applications should inhibit forwarding or automatic message generation that could cause infinite looping. | +| TP-RP | TP-Reply-Path | M | b | Parameter indicating that Reply Path exists. | +| TP-UDHI | TP-User-Data-Header-Indicator | O | b | Parameter indicating that the TP-UD field contains a Header | +| TP-SRI | TP-Status-Report-Indication | O | b | Parameter indicating if the SME has requested a status report. | +| TP-OA | TP-Originating-Address | M | 2-12o | Address of the originating SME. | +| TP-PID | TP-Protocol-Identifier | M | o | Parameter identifying the above layer protocol, if any. | +| TP-DCS | TP-Data-Coding-Scheme | M | o | Parameter identifying the coding scheme within the TP-User-Data. | +| TP-SCTS | TP-Service-Centre-Time-Stamp | M | 7o | Parameter identifying time when the SC received the message. | +| TP-UDL | TP-User-Data-Length | M | l | Parameter indicating the length of the TP-User-Data field to follow. | +| TP-UD | TP-User-Data | O | 3) | | + +- 1) Provision; Mandatory (M) or Optional (O). +- 2) Representation; Integer (I), bit (b), 2 bits (2b), Octet (o), 7 octets (7o), 2-12 octets (2-12o). +- 3) Dependent on the TP-DCS. + +Layout of SMS-DELIVER: + +![Diagram showing the layout of SMS-DELIVER with bit positions 0-7 and various fields like TP-MTI, TP-OA, TP-PID, TP-DCS, TP-SCTS, TP-UDL, and TP-UD.](7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg) + +The diagram illustrates the structure of an SMS-DELIVER message. It consists of several fields, each represented by a grid of bits (0-7). The fields and their bit positions are as follows: + +- TP-MTI, TP-MMS, TP-LP, TP-SRI, TP-UDHI, TP-RP:** Bit 0 (1 bit). Bit 7 is used for TP-MTI, TP-MMS, TP-LP, TP-SRI, TP-UDHI, and TP-RP. +- Number of octets:** Bits 1-6 (6 bits). Bit 7 is used for TP-OA. +- TP-OA:** Bits 0-6 (7 bits). Bit 7 is used for TP-PID. +- TP-PID:** Bit 0 (1 bit). Bit 7 is used for TP-DCS. +- TP-DCS:** Bit 0 (1 bit). Bit 7 is used for TP-SCTS. +- TP-SCTS:** Bits 0-6 (7 bits). Bit 7 is used for TP-UDL. +- TP-UDL:** Bit 0 (1 bit). Bit 7 is used for TP-UD. +- TP-UD:** Bits 0-6 (7 bits). Bit 7 is used for the next field. + +The diagram shows the following structure: + +| Field | Bit no. | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-----------------------------------------------|------------------|---|---|---|---|---|---|---|---| +| TP-MTI, TP-MMS, TP-LP, TP-SRI, TP-UDHI, TP-RP | 1 | | | | | | | | | +| | Number of octets | | | | | | | | | +| TP-OA | 1 | | | | | | | | | +| | 2 | | | | | | | | | +| TP-PID | 2 to 12 | | | | | | | | | +| | 1 | | | | | | | | | +| TP-DCS | 1 | | | | | | | | | +| | 1 | | | | | | | | | +| TP-SCTS | 1 | | | | | | | | | +| | 1 | | | | | | | | | +| TP-UDL | 1 | | | | | | | | | +| | 1 | | | | | | | | | +| TP-UD | 1 | | | | | | | | | +| | 1 | | | | | | | | | + +Diagram showing the layout of SMS-DELIVER with bit positions 0-7 and various fields like TP-MTI, TP-OA, TP-PID, TP-DCS, TP-SCTS, TP-UDL, and TP-UD. + +NOTE: Any unused bits shall be set to zero by the sending entity and shall be ignored by the receiving entity. + +### 9.2.2.1a SMS-DELIVER-REPORT type + +An SMS-DELIVER-REPORT TPDU is carried as a RP-User-Data element within an RP-ERROR PDU and is part of the negative acknowledgement to an SMS-DELIVER or SMS-STATUS-REPORT. + +An SMS-DELIVER-REPORT TPDU is also carried as a RP-User-Data element within an RP-ACK PDU and is part of a positive acknowledgement to a SMS-DELIVER or SMS-STATUS REPORT. + +#### (i) SMS-DELIVER-REPORT for RP-ERROR + +Basic elements of the SMS-DELIVER-REPORT type: + +| Abbr. | Reference | p1) | p2) | Description | +|---------|--------------------------------|-----|-------|----------------------------------------------------------------------------------| +| TP-MTI | TP-Message-Type-Indicator | M | 2b | Parameter describing the message type | +| TP-UDHI | TP-User-Data-Header-Indication | O | b | Parameter indicating that the TP-UD field contains a Header | +| TP-FCS | TP-Failure-Cause | M | l | Parameter indicating the reason for SMS-DELIVER failure | +| TP-PI | TP-Parameter-Indicator | M | o | Parameter indicating the presence of any of the optional parameters which follow | +| TP-PID | TP-Protocol-Identifier | O | o | see clause 9.2.3.9 | +| TP-DCS | TP-Data-Coding-Scheme | O | o | see clause 9.2.3.10 | +| TP-UDL | TP-User-Data-Length | O | o | see clause 9.2.3.16 | +| TP-UD | TP-User-Data | O | 3) 4) | see clause 9.2.3.24 | + +- 1) Provision: Mandatory (M) or Optional (O). +- 2) Representation: Integer (I), bit (b), 2bits (2b), octet (o). +- 3) Dependent upon the TP-DCS. +- 4) The TP-User-Data field in the SMS-DELIVER-REPORT is only available for use by the MT. + +Layout of SMS-DELIVER-REPORT: + +![](ae375ead8aa673286b534e079e9a8533_img.jpg) + +Bit Number + +| Number of Octets | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +|------------------|---|---|---|---|---|---|---|---|-----------------| +| 1 | | | | | | | | | TP-MTI, TP-UDHI | +| 1 | | | | | | | | | TP-FCS | +| 1 | | | | | | | | | TP-PI | +| 0,1 | | | | | | | | | TP-PID | +| 0,1 | | | | | | | | | TP-DCS | +| 0,1 | | | | | | | | | TP-UDL | +| 0 to 158 | | | | | | | | | TP-UD | + +Bits 7 and 5 - 2 in octet 1 are presently unused and the sender shall set them to zero. If any of these bits is non-zero, the receiver shall not examine the other field and shall treat the TP-Failure-Cause as "Unspecified error cause". + +## (ii) SMS-DELIVER-REPORT for RP-ACK + +Basic elements of the SMS-DELIVER-REPORT type: + +| Abbr | Reference | p1) | p2) | Description | +|---------|--------------------------------|-----|-------|----------------------------------------------------------------------------------| +| TP-MTI | TP-Message Type Indicator | M | 2b | Parameter describing the message type | +| TP-UDHI | TP-User-Data-Header-Indication | O | b | Parameter indicating that the TP-UD field contains a Header | +| TP-PI | TP-Parameter-Indicator | M | o | Parameter indicating the presence of any of the optional parameters which follow | +| TP-PID | TP-Protocol-Identifier | O | o | see clause 9.2.3.9 | +| TP-DCS | TP-Data-Coding-Scheme | O | o | see clause 9.2.3.10 | +| TP-UDL | TP-User-Data-Length | O | o | see clause 9.2.3.16 | +| TP-UD | TP-User-Data | O | 3) 4) | see clause 9.2.3.24 | + +- 1) Provision: Mandatory (M) or Optional (O). +- 2) Representation: Integer (I), Bit (b), 2 bits (2b), octet (o). +- 3) Dependent upon the TP-DCS. +- 4) The TP-User-Data field in the SMS-DELIVER-REPORT is only available for use by the MT. + +Layout of SMS-DELIVER-REPORT: + +![](58bbc570572758132ea39938e4f03b5b_img.jpg) + +Bit Number + +| Number of Octets | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +|------------------|---|---|---|---|---|---|---|---|-----------------| +| 1 | | | | | | | | | TP-MTI, TP-UDHI | +| 1 | | | | | | | | | TP-PI | +| 0,1 | | | | | | | | | TP-PID | +| 0,1 | | | | | | | | | TP-DCS | +| 0,1 | | | | | | | | | TP-UDL | +| 0 to 159 | | | | | | | | | TP-UD | + +Bits 7 and 5 - 2 in octet 1 are presently unused in the SMS-DELIVER-REPORT and the sender shall set them to zero. If any of these bits is non-zero, the receiver shall ignore them. + +### 9.2.2.2 SMS-SUBMIT type + +Basic elements of the SMS-SUBMIT type: + +| Abbr. | Reference | p1) | p2) | Description | +|---------|-------------------------------|-----|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TP-MTI | TP-Message-Type-Indicator | M | 2b | Parameter describing the message type. | +| TP-RD | TP-Reject-Duplicates | M | b | Parameter indicating whether or not the SC shall accept an SMS-SUBMIT for an SM still held in the SC which has the same TP-MR and the same TP-DA as a previously submitted SM from the same OA | +| TP-VPF | TP-Validity-Period-Format | M | 2b | Parameter indicating whether or not the TP-VP field is present. | +| TP-RP | TP-Reply-Path | M | b | Parameter indicating the request for Reply Path. | +| TP-UDHI | TP-User-Data-Header-Indicator | O | b | Parameter indicating that the TP-UD field contains a Header. | +| TP-SRR | TP-Status-Report-Request | O | b | Parameter indicating if the MS is requesting a status report. | +| TP-MR | TP-Message-Reference | M | I | Parameter identifying the SMS-SUBMIT. | +| TP-DA | TP-Destination-Address | M | 2-12o | Address of the destination SME. | +| TP-PID | TP-Protocol-Identifier | M | o | Parameter identifying the above layer protocol, if any. | +| TP-DCS | TP-Data-Coding-Scheme | M | o | Parameter identifying the coding scheme within the TP-User-Data. | +| TP-VP | TP-Validity-Period | O | o/7o | Parameter identifying the time from where the message is no longer valid. | +| TP-UDL | TP-User-Data-Length | M | I | Parameter indicating the length of the TP-User-Data field to follow. | +| TP-UD | TP-User-Data | O | 3) | | + +- 1) Provision; Mandatory (M) or Optional (O). +- 2) Representation; Integer (I), bit (b), 2 bits (2b), Octet (o), 7 octets (7o), 2-12 octets (2-12o). +- 3) Dependent on the TP-DCS. + +Layout of SMS-SUBMIT: + +![Protocol header diagram showing fields like TP-MTI, TP-RD, TP-VPF, TP-SRR, TP-UDHI, TP-RP, TP-MR, TP-DA, TP-PID, TP-DCS, TP-VP, TP-UDL, and TP-UD with bit and octet counts.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +The diagram illustrates the structure of a protocol header, organized into several fields with their respective bit and octet counts. + +- Bit no:** 7 6 5 4 3 2 1 0 +- TP-MTI, TP-RD, TP-VPF, TP-SRR, TP-UDHI, TP-RP:** 1 bit +- TP-MR:** 1 bit +- Number of octets:** 2 to 12 (TP-DA) +- TP-PID:** 1 bit +- TP-DCS:** 1 bit +- TP-VP:** 0, 1 or 7 bits +- TP-UDL:** 1 bit +- TP-UD:** 0 to 140 octets + +Protocol header diagram showing fields like TP-MTI, TP-RD, TP-VPF, TP-SRR, TP-UDHI, TP-RP, TP-MR, TP-DA, TP-PID, TP-DCS, TP-VP, TP-UDL, and TP-UD with bit and octet counts. + +![Diagram showing a rectangular box with a horizontal line near the top and eight small vertical lines along the bottom edge, representing a data structure or field layout.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Diagram showing a rectangular box with a horizontal line near the top and eight small vertical lines along the bottom edge, representing a data structure or field layout. + +NOTE: Any unused bits shall be set to zero by the sending entity and shall be ignored by the receiving entity. + +### 9.2.2.2a SMS-SUBMIT-REPORT type + +An SMS-SUBMIT-REPORT TPDU is carried as a RP-User-Data element within an RP-ERROR PDU and is part of the negative acknowledgement to an SMS-SUBMIT or SMS-COMMAND. + +An SMS-SUBMIT-REPORT TPDU is also carried as a RP-User-Data element with an RP-ACK PDU and is part of a positive acknowledgement to a SMS-SUBMIT or SMS-COMMAND. + +#### (i) SMS-SUBMIT-REPORT for RP-ERROR + +Basic elements of the SMS-SUBMIT-REPORT type: + +| Abbr. | Reference | p1) | p2) | Description | +|---------|--------------------------------|-----|----------|-------------------------------------------------------------------------------------------| +| TP-MTI | TP-Message-Type-Indicator | M | 2b | Parameter describing the message type | +| TP-UDHI | TP-User-Data-Header-Indication | O | b | Parameter indicating that the TP-UD field contains a Header | +| TP-FCS | TP-Failure-Cause | M | l | Parameter indicating the reason for SMS-SUBMIT failure | +| TP-PI | TP-Parameter-Indicator | M | o | Parameter indicating the presence of any of the optional parameters which follow | +| TP-SCTS | TP-Service-Centre-Time-Stamp | M | 7o
5) | Parameter identifying the time when the SC received the SMS-SUBMIT
See clause 9.2.3.11 | +| TP-PID | TP-Protocol-Identifier | O | o | See clause 9.2.3.9 | +| TP-DCS | TP-Data-Coding-Scheme | O | o | see clause 9.2.3.10 | +| TP-UDL | TP-User-Data-Length | O | o | see clause 9.2.3.16 | +| TP-UD | TP-User-Data | O | 3) 4) | see clause 9.2.3.24 | + +- 1) Provision: Mandatory (M) or Optional (O). +- 2) Representation: Integer (I), bit (b), 2bits (2b), octet (o). +- 3) Dependent upon the TP-DCS. +- 4) The TP-User-Data field in the SMS-SUBMIT-REPORT is only available for use by the SC. +- 5) This same time value shall also be carried in the SMS-STATUS-REPORT relating to a particular SM. See clause 9.2.2.3. This shall allow the submitting SME to associate a particular SMS-SUBMIT with a subsequent SMS-STATUS-REPORT by correlating the TP-SCTS values. + +Layout of SMS-SUBMIT-REPORT: + +![](0a06de972d61ab9bb901bd74dd4ff51f_img.jpg) + +Bit Number + +| Number of Octets | Bit Number | | | | | | | | | +|------------------|------------|---|---|---|---|---|---|---|-----------------| +| | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| 1 | | | | | | | | | TP-MTI, TP-UDHI | +| 1 | | | | | | | | | TP-FCS | +| 1 | | | | | | | | | TP-PI | +| 7 | | | | | | | | | TP-SCTS | +| 0,1 | | | | | | | | | TP-PID | +| 0,1 | | | | | | | | | TP-DCS | +| 0,1 | | | | | | | | | TP-UDL | +| 0 to 151 | | | | | | | | | TP-UD | + +Bits 7 and 5 - 2 in octet 1 are presently unused and the sender shall set them to zero. If any of these bits is non-zero, the receiver shall not examine the other field and shall treat the TP-Failure-Cause as "Unspecified error cause". + +## (ii) SMS-SUBMIT-REPORT for RP-ACK + +Basic elements of the SMS-SUBMIT\_REPORT type: + +| Abbr | Reference | p1) | p2) | Description | +|---------|--------------------------------|-----|----------|-------------------------------------------------------------------------------------------| +| TP-MTI | TP-Message Type-Indicator | M | 2b | Parameter describing the message type | +| TP-UDHI | TP-User-Data-Header-Indication | O | b | Parameter indicating that the TP-UD field contains a Header | +| TP-PI | TP-Parameter-Indicator | M | o | Parameter indicating the presence of any of the optional parameters which follow | +| TP-SCTS | TP-Service-Centre-Time-Stamp | M | 7o
5) | Parameter identifying the time when the SC received the SMS-SUBMIT
See clause 9.2.3.11 | +| TP-PID | TP-Protocol-Identifier | O | o | See clause 9.2.3.9 | +| TP-DCS | TP-Data-Coding-Scheme | O | o | see clause 9.2.3.10 | +| TP-UDL | TP-User-Data-Length | O | o | see clause 9.2.3.16 | +| TP-UD | TP-User-Data | O | 3) 4) | see clause 9.2.3.24 | + +- 1) Provision: Mandatory (M) or Optional (O). +- 2) Representation: Integer (I), Bit (B), 2bits (2b), octet (o). +- 3) Dependent upon the TP-DCS. +- 4) The TP-User-Data field in the SMS-SUBMIT-REPORT is only available for use by the SC. +- 5) This same time value shall also be carried in the SMS-STATUS-REPORT relating to a particular SM. See clause 9.2.2.3. This shall allow the submitting SME to associate a particular SMS-SUBMIT with a subsequent SMS-STATUS-REPORT by correlating the TP-SCTS values. + +Layout of SMS-SUBMIT REPORT + +![](a78db21022e0687c18d97ed547dd7ecb_img.jpg) + +Bit Number + +| Number of Octets | Bit Number | | | | | | | | | +|------------------|------------|---|---|---|---|---|---|---|-------------| +| | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| 1 | | | | | | | | | TP-MTI, TP- | + +| | | | | | | | | | +|----------|--|--|--|--|--|--|--|---------| +| | | | | | | | | UDHI | +| 1 | | | | | | | | TP-PI | +| 7 | | | | | | | | TP-SCTS | +| 0,1 | | | | | | | | TP-PID | +| 0,1 | | | | | | | | TP-DCS | +| 0,1 | | | | | | | | TP-UDL | +| 0 to 152 | | | | | | | | TP-UD | + +Bits 7 and 5 - 2 in octet 1 are presently unused in the SMS-SUBMIT-REPORT and the sender shall set them to zero. If any of these bits is non-zero, the receiver shall ignore them. + +### 9.2.2.3 SMS-STATUS-REPORT type + +Basic elements of the SMS-STATUS-REPORT type: + +| Abbr. | Reference | P 1) | R 2) | Description | +|---------|------------------------------------|--------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| TP-MTI | TP-Message-Type-Indicator | M | 2b | Parameter describing the message type | +| TP-UDHI | TP-User-Data-Header-Indication | O | b | Parameter indicating that the TP-UD field contains a Header | +| TP-MMS | TP-More-Messages-to-Send | M | b | Parameter indicating whether or not there are more messages to send | +| TP-LP | TP-Loop-Prevention | O | b | Parameter indicating that SMS applications should inhibit forwarding or automatic message generation that could cause infinite looping. | +| TP-SRQ | TP-Status-Report-Qualifier | M | b | Parameter indicating whether the previously submitted TPDU was an SMS-SUBMIT or an SMS-COMMAND | +| TP-MR | TP-Message-Reference 3) | M | l | Parameter identifying the previously submitted SMS-SUBMIT or SMS-COMMAND | +| TP-RA | TP-Recipient-Address | M | 2-12o | Address of the recipient of the previously submitted mobile originated short message | +| TP-SCTS | TP-Service-Centre-Time-Stamp | M | 7o | Parameter identifying time when the SC received the previously sent SMS-SUBMIT | +| TP-DT | TP-Discharge-Time | M | 7o | Parameter identifying the time associated with a particular TP-ST outcome | +| TP-ST | TP-Status | M | o | Parameter identifying the status of the previously sent mobile originated short message | +| TP-PI | TP-Parameter-Indicator | O
4) | o | Parameter indicating the presence of any of the optional parameters which follow | +| TP-PID | TP-Protocol-Identifier | O | o | see clause 9.2.3.9. TP-PID of original SMS-SUBMIT | +| TP-DCS | TP-Data-Coding-Scheme | O | o | see clause 9.2.3.10 | +| TP-UDL | TP-User-Data-Length | O | o | see clause 9.2.3.16 | +| TP-UD | TP-User-Data | O | 5) | see clause 9.2.3.24 | + +- 1) Provision: Mandatory (M) or Optional (O). +- 2) Representation: Integer (I), bit (b), 2 bits (2b), Octet (o), 7 octets (7o), 2-12 octets (2-12o). +- 3) Where the SMS-STATUS-REPORT is the result of an SMS-COMMAND and the TP-Command-Type was an Enquiry, the TP-MR returned in the SMS-STATUS-REPORT shall be the TP-MN which was sent in the SMS-COMMAND (i.e. the TP-MR of the previously submitted SM to which the Enquiry refers). +- 4) Mandatory if any of the optional parameters following TP-PI is present, otherwise optional. +- 5) TP-UD contains information related to a SMS-DELIVER; can contain information transported in the TP-UD of SMS-DELIVER-REPORT, and information inserted by the SMSC. The length of the TP-UD field is limited and might not be long enough to fit information both from the original receiving terminal (as included into the SMS- + +DELIVER-REPORT) and information added by the SMSC. In these cases the former information has higher priority, and the latter shall be truncated. + +Layout of SMS-STATUS-REPORT: + +![](28085f681b9fff76a53c5b8b32338ee1_img.jpg) + +| Bit no. | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +|------------------|----------|---|---|---|---|---|---|---|----------------------------------------| +| Number of octets | 1 | | | | | | | | TP-MTI, TP-MMS, TP-LP, TP-SRQ, TP-UDHI | +| | 1 | | | | | | | | TP-MR | +| | 1 | | | | | | | | TP-RA | +| | 2 | | | | | | | | | +| | 2 to 12 | | | | | | | | TP-SCTS | +| | 7 | | | | | | | | | +| | 7 | | | | | | | | TP-DT | +| | 1 | | | | | | | | | +| | 1 | | | | | | | | TP-ST | +| | 1 | | | | | | | | TP-PI | +| | 1 | | | | | | | | TP-PID | +| | 1 | | | | | | | | TP-DCS | +| | 1 | | | | | | | | TP-UDL | +| | 1 | | | | | | | | TP-UD | +| | 0 to 143 | | | | | | | | | + +NOTE: Any unused bits shall be set to zero by the sending entity and shall be ignored by the receiving entity. + +The maximum guaranteed length of TP-UD is 131 octets. In order to achieve the maximum stated above (143 octets), the TP-RA field must have a length of 2 octets and TP-PID and TP-DCS must not be present. + +### 9.2.2.4 SMS-COMMAND type + +Basic elements of the SMS-COMMAND type: + +| Abbr. | Reference | P 1) | R 2) | Description | +|---------|--------------------------------|-----------------|-----------------|-----------------------------------------------------------------------------| +| TP-MTI | TP-Message-Type-Indicator | M | 2b | Parameter describing the type | +| TP-UDHI | TP-User-Data-Header-Indication | O | b | Parameter indicating that the TP-CD field contains a Header | +| TP-SRR | TP-Status-Report- Request | O | b | Parameter indicating if the SMS Command is requesting a status report. | +| TP-MR | TP-Message Reference | M | l | Parameter identifying the SMS-COMMAND | +| TP-PID | TP-Protocol- Identifier | M | o | Parameter identifying the above layer protocol, if any | +| TP-CT | TP-Command-Type | M | o | Parameter specifying which operation is to be performed on a SM | +| TP-MN | TP-Message-Number | M 3) | o | Parameter indicating which SM in the SC to operate on | +| TP-DA | TP-Destination-Address | M 4) | 2-12o | Parameter indicating the Destination Address to which the TP-Command refers | +| TP-CDL | TP-Command-Data-Length | M | o | Parameter indicating the length of the TP-CD field in octets | +| TP-CD | TP-Command-Data | O | o | Parameter containing user data | + +- 1) Provision: Mandatory (M) or Optional (O). +- 2) Representation: Integer (I), bit (b), 2bits (2b), octet (o). +- 3) For TP-Command-Types which are not for a specific SM this field shall be ignored when received. Its value is of no concern but the field must be present to maintain the structure. +- 4) For certain TP-Command-Types which operate on a specific SM (e.g. Enquire, Delete etc.) the full TP-DA must be specified. For TP-Command-Types which do not operate on a specific SM, the address length must be set to zero indicating that the Address-Value fields are not present. The Type-of-Address field must be present (see 9.1.2.5) and shall be set to zero and ignored. + +Layout of SMS-COMMAND: + +![](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) + +| Bit no. | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +|-----------|----------|---|---|---|---|---|---|---|----------------------------| +| Number | 1 | | | | | | | | TP-MTI, TP-SRR,
TP-UDHI | +| of octets | 1 | | | | | | | | TP-MR | +| | 1 | | | | | | | | TP-PID | +| | 1 | | | | | | | | TP-CT | +| | 1 | | | | | | | | TP-MN | +| | 2 to 12 | | | | | | | | TP-DA | +| ..... | | | | | | | | | | +| | 1 | | | | | | | | TP-CDL | +| ..... | | | | | | | | | | +| | 0 to 156 | | | | | | | | TP-CD | + +NOTE: The maximum guaranteed length of TP-CD is 146 octets. In order to achieve the maximum stated above (156 octets), the TP-DA field must have a length of 2 octets. + +## 9.2.3 Definition of the TPDU parameters + +### 9.2.3.1 TP-Message-Type-Indicator (TP-MTI) + +The TP-Message-Type-Indicator is a 2-bit field, located within bits no 0 and 1 of the first octet of all PDUs which can be given the following values: + +| bit1 | bit0 | Message type | +|------|------|------------------------------------------------| +| 0 | 0 | SMS-DELIVER (in the direction SC to MS) | +| 0 | 0 | SMS-DELIVER REPORT (in the direction MS to SC) | +| 1 | 0 | SMS-STATUS-REPORT (in the direction SC to MS) | +| 1 | 0 | SMS-COMMAND (in the direction MS to SC) | +| 0 | 1 | SMS-SUBMIT (in the direction MS to SC) | +| 0 | 1 | SMS-SUBMIT-REPORT (in the direction SC to MS) | +| 1 | 1 | Reserved | + +If an MS receives a TPDU with a "Reserved" value in the TP-MTI it shall process the message as if it were an "SMS-DELIVER" but store the message exactly as received. + +### 9.2.3.2 TP-More-Messages-to-Send (TP-MMS) + +The TP-More-Messages-to-Send is a 1-bit field, located within bit no 2 of the first octet of SMS-DELIVER and SMS-STATUS-REPORT, and to be given the following values: + +| | | | +|-----------|---|----------------------------------------------------| +| Bit no 2: | 0 | More messages are waiting for the MS in this SC | +| | 1 | No more messages are waiting for the MS in this SC | + +NOTE: In the case of SMS-STATUS-REPORT this parameter refers to messages waiting for the mobile to which the status report is sent. The term message in this context refers to SMS-messages or status reports. + +### 9.2.3.3 TP-Validity-Period-Format (TP-VPF) + +The TP-Validity-Period-Format is a 2-bit field, located within bit no 3 and 4 of the first octet of SMS-SUBMIT, and to be given the following values: + +| | bit4 | bit3 | | +|---|------|------|---------------------------------------| +| • | 0 | 0 | TP-VP field not present | +| | 1 | 0 | TP-VP field present - relative format | +| | 0 | 1 | TP-VP field present - enhanced format | +| | 1 | 1 | TP-VP field present - absolute format | + +Any unsupported value may be rejected by the SC by returning the "TP-VPF not supported" TP-FCS value in the SMS Submit Report for RP-Error. + +### 9.2.3.4 TP-Status-Report-Indication (TP-SRI) + +The TP-Status-Report-Indication is a 1-bit field, located within bit no. 5 of the first octet of SMS-DELIVER, and to be given the following values: + +| | | +|--------------|--------------------------------------------------| +| Bit no. 5: 0 | A status report shall not be returned to the SME | +| 1 | A status report shall be returned to the SME | + +### 9.2.3.5 TP-Status-Report-Request (TP-SRR) + +The TP-Status-Report-Request is a 1-bit field, located within bit no. 5 of the first octet of SMS-SUBMIT and SMS-COMMAND, and to be given the following values: + +| | | +|--------------|----------------------------------| +| Bit no. 5: 0 | A status report is not requested | +| 1 | A status report is requested | + +### 9.2.3.6 TP-Message-Reference (TP-MR) + +The TP-Message-Reference field gives an integer representation of a reference number of the SMS-SUBMIT or SMS-COMMAND submitted to the SC by the MS. The MS increments TP-Message-Reference by 1 for each SMS-SUBMIT or SMS-COMMAND being submitted. The value to be used for each SMS-SUBMIT is obtained by reading the Last-Used-TP-MR value from the SMS Status data field in the (U)SIM (see GSM TS 51.011 [16] and 3GPP TS 31.102 [30]) and incrementing this value by 1. After each SMS-SUBMIT has been submitted to the network, the Last-Used-TP-MR value in the (U)SIM is updated with the TP-MR that was used in the SMS-SUBMIT operation. The reference number may possess values in the range 0 to 255. The value in the TP-MR assigned by the MS is the same value which is received at the SC. + +In the case where no response or an RP-ERROR with an appropriate cause value (see 3GPP TS 24.011 [13]) is received in response to an SMS-SUBMIT, then the MS shall automatically repeat the SMS-SUBMIT but must use the same TP-MR value and set the TP-RD bit to 1 (see 9.2.3.25). The number of times the MS automatically repeats the SMS-SUBMIT shall be in the range 1 to 3 but the precise number is an implementation matter. The automatic repeat mechanism should be capable of being disabled through MMI. + +If all automatic attempts fail (or in the case of no automatic attempts the first attempt fails), the user shall be informed. The failed message shall be stored in the mobile in such a way that the user can request a retransmission using the same TP-MR value, without the need to re-enter any information. Such storage need only be provided for a single failed message, i.e. the one most recently attempted. + +The SC should discard an SMS-SUBMIT which has the TP-RD bit set to a 1 and which has the same TP-MR value as the previous SMS-SUBMIT received from the same originating address. In the case of a discarded SMS-SUBMIT, the SC should respond with an RP-ERROR, in which case the RP-ERROR shall include a SMS-SUBMIT-REPORT with TP-FCS indicating "SM Rejected – Duplicate SM". In some cases, for backward compatibility with earlier phases and versions of this specification, the SC may be configured to respond with an RP-ACK. + +The SMS-STATUS-REPORT also contains a TP-Message-Reference field. The value sent to the MS shall be the same as the TP-Message-Reference value generated by the MS in the earlier SMS-SUBMIT or SMS-COMMAND to which the status report relates. + +### 9.2.3.7 TP-Originating-Address (TP-OA) + +The TP-Originating-Address field is formatted according to the formatting rules of address fields. + +The first '#' encountered in TP-OA indicates where the address for SMSC routing purposes is terminated. Additional '\*'s or '#'s can be present in the following digits, and all these digits including the first '#' are subaddress digits. + +### 9.2.3.8 TP-Destination-Address (TP-DA) + +The TP-Destination-Address field is formatted according to the formatting rules of address fields. + +The first '#' encountered in TP-DA indicates where the address for SMSC routing purposes is terminated. Additional '\*'s or '#'s can be present in the following digits, and all these digits including the first '#' are subaddress digits. + +### 9.2.3.9 TP-Protocol-Identifier (TP-PID) + +The TP-Protocol-Identifier parameter serves the purposes indicated in clause 3.2.3. It consists of one octet, and the bits in the octet are used as follows: + +The MS shall interpret reserved, obsolete, or unsupported values as the value 00000000 but shall store them exactly as received. + +The SC may reject messages with a TP-Protocol-Identifier containing a reserved value or one which is not supported. + +| bits | usage | +|------|--------------------------------------| +| 7 6 | | +| 0 0 | Assigns bits 0..5 as defined below | +| 0 1 | Assigns bits 0..5 as defined below | +| 1 0 | reserved | +| 1 1 | Assigns bits 0-5 for SC specific use | + +In the case where bit 7 = 0 and bit 6 = 0, + +bit 5 indicates telematic interworking: + +value = 0 : no interworking, but SME-to-SME protocol + +value = 1 : telematic interworking + +In the case of telematic interworking, the following five bit patterns in bits 4..0 are used to indicate different types of telematic devices: + +| 4.. 0 | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------| +| 00000 | implicit - device type is specific to this SC, or can be concluded on the basis of the address | +| 00001 | telex (or teletex reduced to telex format) | +| 00010 | group 3 telefax | +| 00011 | group 4 telefax | +| 00100 | voice telephone (i.e. conversion to speech) | +| 00101 | ERMES (European Radio Messaging System) | +| 00110 | National Paging system (known to the SC) | +| 00111 | Videotex (T.100 [20] / T.101 [21]) | +| 01000 | teletex, carrier unspecified | +| 01001 | teletex, in PSPDN | +| 01010 | teletex, in CSPDN | +| 01011 | teletex, in analog PSTN | +| 01100 | teletex, in digital ISDN | +| 01101 | UCI (Universal Computer Interface, ETSI DE/PS 3 01-3) | +| 01110..01111 | (reserved, 2 combinations) | +| 10000 | a message handling facility (known to the SC) | +| 10001 | any public X.400-based message handling system | +| 10010 | Internet Electronic Mail | +| 10011..10111 | (reserved, 5 combinations) | +| 11000..11110 | values specific to each SC, usage based on mutual agreement between the SME and the SC (7 combinations available for each SC) | + +11111 A GSM/UMTS mobile station. The SC converts the SM from the received TP-Data-Coding-Scheme to any data coding scheme supported by that MS (e.g. the default). + +If bit 5 has value 1 in an SMS-SUBMIT PDU, it indicates that the SME is a telematic device of a type which is indicated in bits 4..0, and requests the SC to convert the SM into a form suited for that device type. If the destination network is ISDN, the SC must also select the proper service indicators for connecting to a device of that type. + +If bit 5 has value 1 in an SMS-DELIVER PDU, it indicates that the SME is a telematic device of a type which is indicated in bits 4..0. + +If bit 5 has value 0 in an SMS-DELIVER PDU, the value in bits 4..0 identifies the SM-AL protocol being used between the SME and the MS. + +Note that for the straightforward case of simple MS-to-SC short message transfer the Protocol Identifier is set to the value 0. + +In the case where bit 7 = 0, bit 6 = 1, bits 5..0 are used as defined below + +| | | +|----------------|-------------------------------------| +| 5 .. . 0 | | +| 000000 | Short Message Type 0 | +| 000001 | Replace Short Message Type 1 | +| 000010 | Replace Short Message Type 2 | +| 000011 | Replace Short Message Type 3 | +| 000100 | Replace Short Message Type 4 | +| 000101 | Replace Short Message Type 5 | +| 000110 | Replace Short Message Type 6 | +| 000111 | Replace Short Message Type 7 | +| 001000 | Device Triggering Short Message | +| 001001..011101 | Reserved | +| 011110 | Enhanced Message Service (Obsolete) | +| 011111 | Return Call Message | +| 100000..111011 | Reserved | +| 111100 | ANSI-136 R-DATA | +| 111101 | ME Data download | +| 111110 | ME De-personalization Short Message | +| 111111 | (U)SIM Data download | + +A short message type 0 indicates that the ME must acknowledge receipt of the short message but shall discard its contents. This means that + +- the MS shall be able to receive the type 0 short message irrespective of whether there is memory available in the (U)SIM or ME or not, +- the MS shall not indicate the receipt of the type 0 short message to the user, +- the short message shall neither be stored in the (U)SIM nor ME. + +The Replace Short Message feature is optional for the ME and the (U)SIM but if implemented it shall be performed as described here. + +For MT short messages, on receipt of a short message from the SC, the MS shall check to see if the associated Protocol Identifier contains a Replace Short Message Type code. + +If such a code is present, then the MS shall check the originating address and replace any existing stored message having the same Protocol Identifier code and originating address with the new short message and other parameter values. If there is no message to be replaced, the MS shall store the message in the normal way. The MS may also check the SC address as well as the Originating Address. However, in a network which has multiple SCs, it is possible for a Replace Message type for a SM to be sent via different SCs and so it is recommended that the SC address should not be checked by the MS unless the application specifically requires such a check. + +If a Replace Short Message Type code is not present then the MS shall store the message in the normal way. + +In MO short messages the SC reacts similarly but only the address of the originating MS or any other source is checked. + +The Device Triggering Short Message feature is optional for the MS, but if implemented it shall be performed as described here. + +For MT short messages, on receipt of a short message from the SC, the MS can check to see if the associated Protocol Identifier contains a Device Triggering Short Message code. + +If such a code is present, then the MS shall interpret the short message as a device triggering short message. The value contained in the Application Port Addressing information element identifies the application to receive the trigger. + +MO short messages with a Protocol Identifier containing a Device Triggering Short Message code are not supported and shall be discarded by the SC. + +A Return Call Message indicates to the MS to inform the user that a call (e.g. a telephone call) can be established to the address specified within the TP-OA. The RP-OA contains the address of the SC as usual. The message content (if present) gives displayable information (e.g. the number of waiting voice messages). The message is handled in the same way as all other messages of the Replace Short Message Types. + +The ME De-personalization Short Message is a ME-specific message which instructs the ME to de-personalities the ME (see 3GPP TS 22.022 [25]). The TP-DCS shall be set to Uncompressed, Default Alphabet, and Message Class 1 (ME-specific), which corresponds to a bit coding of 00010001. The TP-UD field contains de-personalization information coded according to 3GPP TS 22.022 [25]. This information shall not be displayed by an ME which supports the scheme. The acknowledgement to this message is a SMS-DELIVER-REPORT for RP-ACK in which the TP-User-Data shall be coded according to 3GPP TS 22.022 [25]. + +(U)SIM Data download is a facility whereby the ME must pass the short message in its entirety including all SMS elements contained in the SMS deliver to the (U)SIM using the mechanism described in GSM TS 51.011 [16] and 3GPP TS 31.102 [30]. The DCS shall be set to message class 2. The entire user data field is available for (U)SIM Data download. If the DCS is not set to message class 2 then the message shall be handled in the normal way by the ME. However it has to be noted that MEs based on releases of this specification earlier than REL-5 may allow only 8 bit message class 2 with bit coding 11110110 or 00010110 for (U)SIM Data download. + +ME Data download is a facility whereby the ME shall process the short message in its entirety including all SMS elements contained in the SMS deliver to the ME. The DCS should normally be set to message class 1. If the DCS is set to message class 1 and no application in the ME exists, which is able to process the short message, the ME may discard the short message. The entire user data field is available for ME data download. The TPDU parameters required for the SMS-DELIVER should be passed transparently by all involved SCs, so no TPDU parameter in the entire short message is modified, other than the changes required to convert an SMS-SUBMIT into an SMS-DELIVER. + +ANSI-136 R-DATA is a facility whereby the ME must pass the short message in its entirety, including all elements contained in the SMS DELIVER, to the (U)SIM using the mechanism described in GSM TS 11.14 [16] and 3GPP TS 31.102 [30]. The DCS shall be set to message class 2. If the DCS is not set to message class 2 then the message shall be handled in the normal way by the ME. However it has to be noted that MEs based on releases of this specification earlier than REL-5 may allow only 8 bit message class 2 with bit coding 11110110 or 00010110 for ANSI-136 R-DATA. + +### 9.2.3.10 TP-Data-Coding-Scheme (TP-DCS) + +The TP-Data-Coding-Scheme is defined in 3GPP TS 23.038 [9]. + +### 9.2.3.11 TP-Service-Centre-Time-Stamp (TP-SCTS) + +The TP-Service-Centre-Time-Stamp field is given in semi-octet representation, and represents the local time in the following way: + +| | Year: | Month: | Day: | Hour: | Minute: | Second: | Time Zone | +|--------------------------|-------|--------|------|-------|---------|---------|-----------| +| Digits:
(Semi-octets) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | + +The Time Zone indicates the difference, expressed in quarters of an hour, between the local time and GMT. In the first of the two semi-octets, the first bit (bit 3 of the seventh octet of the TP-Service-Centre-Time-Stamp field) represents the algebraic sign of this difference (0: positive, 1: negative). + +The Service-Centre-Time-Stamp, and any other times coded in this format that are defined in the present document, represent the time local to the sending entity. + +If the MS has knowledge of the local time zone, then any time received (e.g. Service-Centre-Time-Stamp) at the MS may be displayed in the local time rather than the time local to the sending entity. Messages shall be stored as received without change to any time contained therein. + +The Time Zone code enables the receiver to calculate the equivalent time in GMT from the other semi-octets in the Service-Centre-Time-Stamp, or indicate the time zone (GMT, GMT+1H etc.), or perform other similar calculations as required by the implementation. The value contained in the Time Zone field must take into account daylight saving time, such that when the sending entity changes from regular (winter) time to daylight saving (summer) time, there is a change to the value in the Time Zone field, for example in the UK the winter setting is 00000000 and the summer setting is 01000000. + +If the MS receives a non-integer value in the SCTS, it shall assume that the digit is set to 0 but shall store the entire field exactly as received. + +### 9.2.3.12 TP-Validity-Period (TP-VP) + +#### 9.2.3.12.1 TP-VP (Relative format) + +The TP-Validity-Period comprises 1 octet in integer representation, giving the length of the validity period, counted from when the SMS-SUBMIT is received by the SC. + +The representation of time is as follows: + +| TP-VP value | Validity period value | +|-------------|-------------------------------------------------------------------| +| 0 to 143 | (TP-VP + 1) x 5 minutes (i.e. 5 minutes intervals up to 12 hours) | +| 144 to 167 | 12 hours + ((TP-VP - 143) x 30 minutes) | +| 168 to 196 | (TP-VP - 166) x 1 day | +| 197 to 255 | (TP-VP - 192) x 1 week | + +#### 9.2.3.12.2 TP-VP (Absolute format) + +The TP-Validity Period comprises 7 octets in semi octet representation giving the absolute time of the validity period termination. + +The representation of time is identical to the representation of the TP-Service-Centre-Time-Stamp. + +#### 9.2.3.12.3 TP-VP (Enhanced format) + +The TP-Validity Period comprises 7 octets. The presence of all octets is mandatory although they may not all be used. The first octet indicates the way in which the following 6 octets are used. Any reserved/unused bits or octets must be set to zero. + +Octet 1 TP-VP functionality indicator + +bit 7 Extension bit + +Set to 1 if the TP-VP functionality indicator is to be extended to another octet. A setting of 0 indicates that there are no more TP-VP functionality indicator extension octets to follow. + +Any such extension octet shall immediately follow the previous TP-VP functionality indicator. + +bit 6 Single shot SM. + +Set to 1 if the SC is required to make up to one delivery attempt. The TP-Validity Period, where present, shall be applicable to the Single shot SM. + +bits 5, 4, 3 Reserved + +bits 2, 1, 0 Validity Period Format. + +## Value bits    2   1   0 + +| | | +|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 0 | No Validity Period specified | +| 0 0 1 | Validity Period is as specified for the relative case. The following octet contains the TP-VP value as described in 9.2.3.12.1 | +| 0 1 0 | Validity period is relative in integer representation and the following octet contains the TP-VP value in the range 0 to 255 representing 0 to 255 seconds. A TP-VP value of zero is undefined and reserved for future use. | +| 0 1 1 | Validity period is relative in semi-octet representation. The following 3 octets contain the relative time in Hours, Minutes and Seconds giving the length of the validity period counted from when the SMS-SUBMIT is received by the SC. The representation of time uses the same representation as the Hours, Minutes and Seconds in the TP-Service-Centre-Time-Stamp. | +| 1 0 0 | Reserved | +| 1 0 1 | Reserved | +| 1 1 0 | Reserved | +| 1 1 1 | Reserved | + +The SC shall reject any Unsupported/ Reserved values received by returning the 'TP-VP not supported' TP-FCS value in the Submit SM Report for RP-Error. + +### 9.2.3.13 TP-Discharge-Time (TP-DT) + +The TP-Discharge-Time field indicates the time at which a previously submitted SMS-SUBMIT was successfully delivered to or attempted to deliver to the recipient SME or disposed of by the SC. + +In the case of "transaction completed" the time shall be the time of the completion of the transaction. In the case of "SC still trying to transfer SM" the time shall be the time of the last transfer attempt. In the case of "permanent or temporary error - SC not making any more transfer attempts" the time shall be the time of either the last transfer attempt or the time at which the SC disposed of the SM according to the Status outcome in TP-ST. + +The TP-Discharge-Time is given in semi-octet representation in a format identical to the TP-SCTS. + +### 9.2.3.14 TP-Recipient-Address (TP-RA) + +The TP-Recipient-Address field indicates the address of the SME that was the destination of the previously submitted mobile originated short message being subject to the status report. The field is formatted according to the formatting rules of address fields. + +### 9.2.3.15 TP-Status (TP-ST) + +The TP-Status field indicates the status of a previously submitted SMS-SUBMIT and certain SMS COMMANDS for which a Status -Report has been requested. It consists of one octet and the bits in the octet are used as follows. + +The MS shall interpret any reserved values as "Service Rejected" (01100011) but shall store them exactly as received. + +| bits | value/usage | +|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7 | 0      Bits 0..6 as defined below: | +| 6...0 | Indicate whether the previously submitted short message was successfully forwarded to the SME, or whether an error condition has been encountered, as follows: | +| |
  • Short message transaction completed
  • 0000000                      Short message received by the SME
  • 0000001                      Short message forwarded by the SC to the SME but the SC is unable to confirm delivery
  • 0000010                      Short message replaced by the SC
  • 0000011..0001111      Reserved
  • 0010000..0011111      Values specific to each SC
  • Temporary error, SC still trying to transfer SM
| + +- 0100000 Congestion +0100001 SME busy +0100010 No response from SME +0100011 Service rejected +0100100 Quality of service not available +0100101 Error in SME +- 0100110..0101111 Reserved +0110000..0111111 Values specific to each SC +- Permanent error, SC is not making any more transfer attempts +- 1000000 Remote procedure error +1000001 Incompatible destination +1000010 Connection rejected by SME +1000011 Not obtainable +1000100 Quality of service not available +1000101 No interworking available +1000110 SM Validity Period Expired +1000111 SM Deleted by originating SME +1001000 SM Deleted by SC Administration +1001001 SM does not exist (The SM may have previously existed in the SC but the SC no longer has knowledge of it or the SM may never have previously existed in the SC) +1001010..1001111 Reserved +1010000..1011111 Values specific to each SC +- Temporary error, SC is not making any more transfer attempts +- 1100000 Congestion +1100001 SME busy +1100010 No response from SME +1100011 Service rejected +1100100 Quality of service not available +1100101 Error in SME +1100110..1101001 Reserved +1101010..1101111 Reserved +1110000..1111111 Values specific to each SC + +| bits | value/usage | | | +|------|-------------|-----------|----------| +| 7 | 1 | Bits 0..6 | reserved | + +### 9.2.3.16 TP-User-Data-Length (TP-UDL) + +If the TP-User-Data is coded using the GSM 7 bit default alphabet, the TP-User-Data-Length field gives an integer representation of the number of septets within the TP-User-Data field to follow. If the 7bit default-alphabet extension mechanism is used within the TP-User-Data (see 3GPP TS 23.038 [9]), the actual number of characters in the message shall be less than the number of septets. If a TP-User-Data-Header field is present, then the TP-User-Data-Length value is the sum of the number of septets in the TP-User-Data-Header field (including any padding) and the number of septets in the TP-User-Data field which follows. See figure 9.2.3.24 (a). If the TP-User-Data is coded using 8-bit data, the TP-User-Data-Length field gives an integer representation of the number of octets within the TP-User-Data field to follow. If a TP-User-Data-Header field is present, then the TP-User-Data-Length value is the sum of the number of octets in the TP-User-Data-Header field and the number of octets in the TP-User-Data field which follows. See figure 9.2.3.24 (b). + +If the TP-User-Data is coded using UCS2 [24] data, the TP-User-Data-Length field gives an integer representation of the number of octets within the TP-User-Data field to follow. If a TP-User-Data-Header field is present, then the TP-User-Data-Length value is the sum of the number of octets in the TP-User-Data-Header field and the number of octets in the TP-User-Data field which follows. See figure 9.2.3.24 (b). + +If the TP-User-Data is coded using compressed GSM 7 bit default alphabet or compressed 8 bit data or compressed UCS2 [24] data, the TP-User-Data-Length field gives an integer representation of the number of octets after compression within the TP-User-Data field to follow. If a TP-User-Data-Header field is present, then the TP-User-Data-Length value is the sum of the number of uncompressed octets in the TP-User-Data-Header field and the number of octets in the compressed TP-User-Data field which follows. See figure 9.2.3.24 (c). + +For other Data Coding Schemes, see 3GPP TS 23.038 [9]. If this field is zero, the TP-User-Data field shall not be present. + +### 9.2.3.17 TP-Reply-Path (TP-RP) + +The TP-Reply-Path is a 1-bit field, located within bit no 7 of the first octet of both SMS-DELIVER and SMS-SUBMIT, and to be given the following values: + +| | | | +|-----------|---|---------------------------------------------------------------| +| Bit no 7: | 0 | TP-Reply-Path parameter is not set in this SMS-SUBMIT/DELIVER | +| | 1 | TP-Reply-Path parameter is set in this SMS-SUBMIT/DELIVER | + +Please refer to annex D for details about the Reply procedures. + +### 9.2.3.18 TP-Message-Number (TP-MN) + +The TP-Message-Number is an 8-bit field allowing an MS to refer uniquely to an SM in the SC which that MS has previously submitted. The TP-MN value is the TP-MR value of a previously submitted SM. + +### 9.2.3.19 TP-Command-Type (TP-CT) + +The TP-Command-Type is an 8-bit field specifying the type of operation that the SC is to perform. It has the following values: + +| Value (bit 7 .. 0) | Command Description | Status Report Request Value | +|--------------------|-----------------------------------------------------------------------------|-----------------------------| +| 00000000 | Enquiry relating to previously submitted short message | 1 | +| 00000001 | Cancel Status Report Request relating to previously submitted short message | 0 | +| 00000010 | Delete previously submitted Short Message | 0 | +| 00000011 | Enable Status Report Request relating to previously submitted short message | 0 | +| 00000100..00011111 | Reserved | unspecified | +| 11100000..11111111 | Values specific for each SC | 1 or 0 | + +The SC shall return an RP-Error with an appropriate TP-Failure-Cause for any TP-Command value which is reserved, unsupported or invalid or the actioning of the command has failed. + +The SC shall return an RP-ACK if the actioning of the Command has succeeded. + +A successful Enquiry shall result in the SC sending a SMS-STATUS-REPORT for the SM to which the Enquiry refers. In the case where the SC has a number of SMs which have the same TP-MR, the same TP-DA and have come from the same originating address the SC shall send a SMS-STATUS-REPORT for each SM. + +In the case where a TP-Command is to Delete a previously submitted short message, the SC shall send a Status Report indicating that the SM has been deleted if the original Submit SM request requested a status Report. + +### 9.2.3.20 TP-Command-Data-Length (TP-CDL) + +The TP-Command-Data-Length field is used to indicate the number of octets contained within the TP-Command-Data field. If this field is set to zero, the TP-Command-Data field shall not be present. + +### 9.2.3.21 TP-Command-Data (TP-CD) + +The TP-Command-Data field contains data relating to the operation requested by the MS which is to be performed at the SC. The maximum length of this field is 157 octets. The usage and provision of the optional TP-Command-Data field shall be determined by the function selected by the TP-Command-Type field. + +### 9.2.3.22 TP-Failure-Cause (TP-FCS) + +The TP-Failure-Cause field is used to report the reason for failure to transfer or process a short message. It consists of a single octet used as follows: + +| TP-FCS
Value
(Hex) | Meaning | When used | | +|--------------------------|---------------------------------------------|-----------|----| +| | | MO | MT | +| 00 - 7F | Reserved | | | +| 80 - 8F | TP-PID errors | | | +| 80 | Telematic interworking not supported | X | | +| 81 | Short message Type 0 not supported | X | X | +| 82 | Cannot replace short message | X | X | +| 83 - 8E | Reserved | | | +| 8F | Unspecified TP-PID error | X | X | +| 90 - 9F | TP-DCS errors | | | +| 90 | Data coding scheme (alphabet) not supported | X | | +| 91 | Message class not supported | | X | +| 92 - 9E | Reserved | | | +| 9F | Unspecified TP-DCS error | X | X | +| A0 - AF | TP-Command Errors | | | +| A0 | Command cannot be actioned | X | | +| A1 | Command unsupported | X | | +| A2 - AE | Reserved | | | +| AF | Unspecified TP-Command error | X | | +| B0 | TPDU not supported | X | X | +| B1 - BF | Reserved | | | +| C0 | SC busy | X | | +| C1 | No SC subscription | X | | +| C2 | SC system failure | X | | +| C3 | Invalid SME address | X | | +| C4 | Destination SME barred | X | | +| C5 | SM Rejected-Duplicate SM | X | | +| C6 | TP-VPF not supported | X | | +| C7 | TP-VP not supported | X | | +| C8 - CF | Reserved | | | +| D0 | (U)SIM SMS storage full | | X | +| D1 | No SMS storage capability in (U)SIM | | X | +| D2 | Error in MS | | X | +| D3 | Memory Capacity Exceeded | | X | +| D4 | (U)SIM Application Toolkit Busy | | X | +| D5 | (U)SIM data download error | | X | +| D6 - DF | Reserved | | | +| E0 - FE | Values specific to an application | X | X | +| FF | Unspecified error cause | X | X | + +NOTE: Any reserved codes which are received should be treated as an unspecified error cause. + +MT and MO refer to the overall mobile terminated and mobile originated services; not the direction of transmission of TP-FCS. + +### 9.2.3.23 TP-User-Data-Header-Indicator (TP-UDHI) + +The TP-User-Data-Header-Indicator is a 1 bit field within bit 6 of the first octet of the following six PDUs: + +- SMS-SUBMIT, +- SMS-SUBMIT-REPORT, +- SMS-DELIVER, +- SMS-DELIVER-REPORT, +- SMS-STATUS-REPORT, +- SMS-COMMAND. + +TP-UDHI has the following values. + +- | | | | +|-----------|---|--------------------------------------------------------------------------------------| +| Bit no. 6 | 0 | The TP-UD field contains only the short message | +| | 1 | The beginning of the TP-UD field contains a Header in addition to the short message. | + +### 9.2.3.24 TP-User Data (TP-UD) + +The length of the TP-User-Data field is defined in the PDU's of the SM-TL (see clause 9.2.2). + +The TP-User-Data field may comprise just the short message itself or a Header in addition to the short message depending upon the setting of TP-UDHI. + +Where the TP-UDHI value is set to 0 the TP-User-Data field comprises the short message only, where the user data can be 7 bit (default alphabet) data, 8 bit data, or 16 bit (UCS2 [24]) data. + +Where the TP-UDHI value is set to 1 the first octets of the TP-User-Data field contains a Header in the following order starting at the first octet of the TP-User-Data field. + +Irrespective of whether any part of the User Data Header is ignored or discarded, the MS shall always store the entire TPDU exactly as received. + +| FIELD | LENGTH | +|------------------------------------|-----------------| +| Length of User Data Header | 1 octet | +| Information-Element-Identifier "A" | 1 octet | +| Length of Information-Element "A" | 1 octet | +| Information-Element "A" Data | 0 to "n" octets | +| Information-Element-Identifier "B" | 1 octet | +| Length of Information-Element "B" | 1 octet | +| Information-Element "B" Data | 0 to "n" octets | +| Information-Element-Identifier "X" | 1 octet | +| Length of Information-Element "X" | 1 octet | +| Information-Element "X" Data | 0 to "n" octets | + +The diagram below shows the layout of the TP-User-Data-Length and the TP-User-Data for uncompressed GSM 7 bit default alphabet data. The UDHL field is the first octet of the TP-User-Data content of the Short Message. + +![Diagram (a) showing the layout of TP-User-Data for 7-bit data. The message structure includes UDL, UDHL, and a series of Information Elements (IE1a, IEIDLa, IEDa, IE1b, ..., IEn, IEDLn, IEDn), followed by Fill bits and SM (7bit data). The UDHL field contains a 'Length Indicator' for the total number of octets of the Information Elements. Another 'Length Indicator' in the UDHL field indicates the total number of septets for the entire user data (IEs + Fill bits + SM). Brackets labeled 'Octets' point to the IE section, and a 'Septet Boundary' is marked between the Fill bits and the SM section.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +Diagram (a) showing the layout of TP-User-Data for 7-bit data. The message structure includes UDL, UDHL, and a series of Information Elements (IE1a, IEIDLa, IEDa, IE1b, ..., IEn, IEDLn, IEDn), followed by Fill bits and SM (7bit data). The UDHL field contains a 'Length Indicator' for the total number of octets of the Information Elements. Another 'Length Indicator' in the UDHL field indicates the total number of septets for the entire user data (IEs + Fill bits + SM). Brackets labeled 'Octets' point to the IE section, and a 'Septet Boundary' is marked between the Fill bits and the SM section. + +Figure 9.2.3.24 (a) + +The diagram below shows the layout of the TP-User-Data-Length and the TP-User-Data for uncompressed 8 bit data or uncompressed UCS2 data. The UDHL field is the first octet of the TP-User-Data content of the Short Message. + +![Diagram (b) showing the layout of TP-User-Data for 8-bit or UCS-2 data. The message structure includes UDL, UDHL, and a series of Information Elements (IE1a, IEIDLa, IEDa, IE1b, ..., IEn, IEDLn, IEDn), followed by SM (8 bit data or UCS-2 data). The UDHL field contains a 'Length Indicator' for the total number of octets of the Information Elements. Another 'Length Indicator' in the UDHL field indicates the total number of octets for the entire user data (IEs + SM). Brackets labeled 'Octets' point to the IE section, and an 'Octet Boundary' is marked between the IE section and the SM section.](4d5d6207a6d444ae745057ebc3ddcd86_img.jpg) + +Diagram (b) showing the layout of TP-User-Data for 8-bit or UCS-2 data. The message structure includes UDL, UDHL, and a series of Information Elements (IE1a, IEIDLa, IEDa, IE1b, ..., IEn, IEDLn, IEDn), followed by SM (8 bit data or UCS-2 data). The UDHL field contains a 'Length Indicator' for the total number of octets of the Information Elements. Another 'Length Indicator' in the UDHL field indicates the total number of octets for the entire user data (IEs + SM). Brackets labeled 'Octets' point to the IE section, and an 'Octet Boundary' is marked between the IE section and the SM section. + +Figure 9.2.3.24 (b) + +The diagram below shows the layout of the TP-User-Data-Length and the TP-User-Data for compressed GSM 7 bit default alphabet data, compressed 8 bit data or compressed UCS2 data. The UDHL field is the first octet of the TP-User-Data content of the Short Message. + +![Diagram of TP-User-Data structure showing fields UDL, UDHL, and a series of Information Elements (IEs) with their length indicators and data fields, followed by Compressed SM. Annotations show 'Octets' for IE data, 'Total number of Octets' for IE data and the entire TP-User-Data field, and 'Length Indicator' for the UDHL and UDL fields. An 'Octet Boundary' is marked at the start of the Compressed SM field.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +The diagram illustrates the structure of a TP-User-Data field. It consists of the following fields in sequence: UDL (User Data Length), UDHL (User Data Header Length), and a series of Information Elements (IEs). Each IE consists of an IE Identifier (IEI), an IE Data Length (IEDL), and IE Data (IED). The IEDL field is annotated with 'Octets'. The IEs are followed by 'Compressed SM (octets)'. The start of the Compressed SM field is marked as an 'Octet Boundary'. Two 'Total number of Octets' annotations are shown: one for the sum of all IE Data fields, and another for the total length of the TP-User-Data field (from the start of UDHL to the end of Compressed SM). The UDHL field is annotated with 'Length Indicator', and the UDL field is also annotated with 'Length Indicator'. + +Diagram of TP-User-Data structure showing fields UDL, UDHL, and a series of Information Elements (IEs) with their length indicators and data fields, followed by Compressed SM. Annotations show 'Octets' for IE data, 'Total number of Octets' for IE data and the entire TP-User-Data field, and 'Length Indicator' for the UDHL and UDL fields. An 'Octet Boundary' is marked at the start of the Compressed SM field. + +Figure 9.2.3.24 (c) + +The definition of the TP-User-Data-Length field which immediately precedes the "Length of User Data Header" is unchanged and shall therefore be the total length of the TP-User-Data field including the Header, if present. (see 9.2.3.16). + +The "Length-of-Information-Element" fields shall be the integer representation of the number of octets within its associated "Information-Element-Data" field which follows and shall not include itself in its count value. + +The "Length-of-User-Data-Header" field shall be the integer representation of the number of octets within the "User-Data-Header" information fields which follow and shall not include itself in its count or any fill bits which may be present (see text below). + +Information Elements may appear in any order and need not follow the order used in the present document. Information Elements are classified into 3 categories as described below. + +- SMS Control – identifies those IEs which have the capability of dictating SMS functionality. +- EMS Control – identifies those IEs which manage EMS Content IEs. +- EMS Content – identifies those IEs containing data of a unique media format. + +It is permissible for certain IEs to be repeated within a short message, or within a concatenated message. There is no restriction on the repeatability of IEs in the EMS Content classification. The repeatability of SMS Control and EMS Control IEs is determined on an individual basis. See the IE table below for the repeatability of each IE. + +In the event that IEs determined as not repeatable are duplicated, the last occurrence of the IE shall be used. In the event that two or more IEs occur which have mutually exclusive meanings (e.g. an 8bit port address and a 16bit port address), then the last occurring IE shall be used. + +If the length of the User Data Header is such that there are too few or too many octets in the final Information Element then the whole User Data Header shall be ignored. + +If any reserved values are received within the content of any Information Element then that part of the Information Element shall be ignored. + +The support of any Information Element Identifier is optional unless otherwise stated. + +The Information Element Identifier octet shall be coded as follows: + +| VALUE (hex) | MEANING | Classification | Repeatability | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|---------------| +| 00 | Concatenated short messages, 8-bit reference number | SMS Control | No | +| 01 | Special SMS Message Indication | SMS Control | Yes | +| 02 | Reserved | N/A | N/A | +| 03 | Value not used to avoid misinterpretation as character | N/A | N/A | +| 04 | Application port addressing scheme, 8 bit address | SMS Control | No | +| 05 | Application port addressing scheme, 16 bit address | SMS Control | No | +| 06 | SMSC Control Parameters | SMS Control | No | +| 07 | UDH Source Indicator | SMS Control | Yes | +| 08 | Concatenated short message, 16-bit reference number | SMS Control | No | +| 09 | Wireless Control Message Protocol | SMS Control | Note 3 | +| 0A | Text Formatting | EMS Control | Yes | +| 0B | Predefined Sound | EMS Content | Yes | +| 0C | User Defined Sound (iMelody max 128 bytes) | EMS Content | Yes | +| 0D | Predefined Animation | EMS Content | Yes | +| 0E | Large Animation (16*16 times 4 = 32*4 =128 bytes) | EMS Content | Yes | +| 0F | Small Animation (8*8 times 4 = 8*4 =32 bytes) | EMS Content | Yes | +| 10 | Large Picture (32*32 = 128 bytes) | EMS Content | Yes | +| 11 | Small Picture (16*16 = 32 bytes) | EMS Content | Yes | +| 12 | Variable Picture | EMS Content | Yes | +| 13 | User prompt indicator | EMS Control | Yes | +| 14 | Extended Object | EMS Content | Yes | +| 15 | Reused Extended Object | EMS Control | Yes | +| 16 | Compression Control | EMS Control | No | +| 17 | Object Distribution Indicator | EMS Control | Yes | +| 18 | Standard WVG object | EMS Content | Yes | +| 19 | Character Size WVG object | EMS Content | Yes | +| 1A | Extended Object Data Request Command | EMS Control | No | +| 1B-1F | Reserved for future EMS features (see subclause 3.10) | N/A | N/A | +| 20 | RFC 5322 E-Mail Header | SMS Control | No | +| 21 | Hyperlink format element | SMS Control | Yes | +| 22 | Reply Address Element | SMS Control | No | +| 23 | Enhanced Voice Mail Information | SMS Control | No | +| 24 | National Language Single Shift | SMS Control | No | +| 25 | National Language Locking Shift | SMS Control | No | +| 26 – 6F | Reserved for future use | N/A | N/A | +| 70 – 7F | (U)SIM Toolkit Security Headers | SMS Control | Note 1 | +| 80 – 9F | SME to SME specific use | SMS Control | Note 2 | +| A0 – BF | Reserved for future use | N/A | N/A | +| C0 – DF | SC specific use | SMS Control | Note 2 | +| E0 – FF | Reserved for future use | N/A | N/A | +| Note 1: | The functionality of these IEIs is defined in 3GPP TSG 31.115 [28], and therefore, the repeatability is not within the scope of this document and will not be determined here. | | | +| Note 2: | The functionality of these IEIs is used in a proprietary fashion by different SMSC vendors, and therefore, are not within the scope of this technical specification. | | | +| Note 3: | The functionality of these IEIs is defined by the WAP Forum and therefore the repeatability is not within the scope of this document and will not be determined here. | | | + +A receiving entity shall ignore (i.e. skip over and commence processing at the next information element) any information element where the IEI is Reserved or not supported. The receiving entity calculates the start of the next information element by looking at the length of the current information element and skipping that number of octets. + +The SM itself may be coded as 7, 8 or 16 bit data. + +If 7 bit data is used and the TP-UD-Header does not finish on a septet boundary then fill bits are inserted after the last Information Element Data octet up to the next septet boundary so that there is an integral number of septets for the entire TP-UD header. This is to ensure that the SM itself starts on a septet boundary so that an earlier Phase mobile shall be capable of displaying the SM itself although the TP-UD Header in the TP-UD field may not be understood. + +It is optional to make the first character of the SM itself a Carriage Return character encoded according to the default 7 bit alphabet so that earlier Phase mobiles, which do not understand the TP-UD-Header, shall over-write the displayed TP-UD-Header with the SM itself. + +If 16 bit (USC2) data is used then padding octets are not necessary. The SM itself shall start on an octet boundary. + +If 8 bit data is used then padding is not necessary. An earlier Phase mobile shall be able to display the SM itself although the TP-UD header may not be understood. + +It is also possible for mobiles not wishing to support the TP-UD header to check the value of the TP-UDHI bit in the SMS-Deliver PDU and the first octet of the TP-UD field and skip to the start of the SM and ignore the TP-UD header. + +#### 9.2.3.24.1 Concatenated Short Messages + +This facility allows short messages to be concatenated to form a longer message. + +In the case of uncompressed 8-bit data, the maximum length of the short message within the TP-UD field is 134 (140-6) octets. + +In the case of uncompressed GSM 7 bit default alphabet data, the maximum length of the short message within the TP-UD field is 153 (160-7) characters. A character represented by an escape-sequence shall not be split in the middle. + +In the case of 16 bit uncompressed USC2 data, the maximum length of the short message within the TP-UD field is 67 ((140-6)/2) characters. A UCS2 character shall not be split in the middle; if the length of the User Data Header is odd, the maximum length of the whole TP-UD field is 139 octets. + +In the case of compressed GSM 7 bit default alphabet data, 8 bit data or UCS2 the maximum length of the compressed short message within the TP-UD field is 134 (140-6) octets including the Compression Header and Compression Footer, both or either of which may be present (see clause 3.9). + +The maximum length of an uncompressed concatenated short message is 39015 (255\*153) default alphabet characters, 34170 (255\*134) octets or 17085 (255\*67) UCS2 characters. + +The maximum length of a compressed concatenated message is 34170 (255\*134) octets including the Compression Header and Compression Footer (see clause 3.9 and figure 9.2.3.24.1(a) below). + +![Diagram illustrating the concatenation of a compressed short message. The top part shows a single message structure with 'Compression Header', 'Compressed Data (CD)', and 'Compression Footer'. The bottom part shows the segmented structure: 'First segment' (TP-UDH, CH, CD), 'Intermediate segments' (TP-UDH, CD), and 'Final segment' (TP-UDH, CD, CF). Arrows indicate the mapping of the top-level fields to the segmented fields, with a 'Segmentation / De-segmentation' block in the center.](8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg) + +The diagram shows the relationship between a full compressed message and its segmented transmission. At the top, a single message is shown with three fields: 'Compression Header', 'Compressed Data (CD)', and 'Compression Footer'. Below this, the message is shown as it would be segmented for transmission. The 'First segment' contains 'TP-UDH', 'CH' (Compression Header), and 'CD' (Compressed Data). 'Intermediate segments' contain 'TP-UDH' and 'CD'. The 'Final segment' contains 'TP-UDH', 'CD', and 'CF' (Compression Footer). Arrows point from the top-level fields to their corresponding parts in the segments: 'Compression Header' to the 'CH' in the first segment, 'Compressed Data (CD)' to the 'CD' in all segments, and 'Compression Footer' to the 'CF' in the final segment. A central box labeled 'Segmentation / De-segmentation' indicates the process of breaking down and reassembling the data. + +Diagram illustrating the concatenation of a compressed short message. The top part shows a single message structure with 'Compression Header', 'Compressed Data (CD)', and 'Compression Footer'. The bottom part shows the segmented structure: 'First segment' (TP-UDH, CH, CD), 'Intermediate segments' (TP-UDH, CD), and 'Final segment' (TP-UDH, CD, CF). Arrows indicate the mapping of the top-level fields to the segmented fields, with a 'Segmentation / De-segmentation' block in the center. + +**Figure 9.2.3.24.1 (a): Concatenation of a Compressed short message** + +The Information-Element-Data field contains information set by the application in the SMS-SUBMIT so that the receiving entity is able to re-assemble the short messages in the correct order. Each concatenated short message contains a reference number which together with the originating address and Service Centre address allows the receiving entity to discriminate between concatenated short messages sent from different originating SMEs and/or SCs. In a network which has multiple SCs, it is possible for different segments of a concatenated SM to be sent via different SCs and so it is recommended that the SC address should not be checked by the MS unless the application specifically requires such a check. + +The TP elements in the SMS-SUBMIT PDU, apart from TP-MR, TP-SRR, TP-UDL and TP-UD, should remain unchanged for each SM which forms part of a concatenated SM, otherwise this may lead to irrational behaviour. TP-MR must be incremented for every segment of a concatenated message as defined in clause 9.2.3.6. A SC shall handle segments of a concatenated message like any other short message. The relation between segments of a concatenated message is made only at the originator, where the message is segmented, and at the recipient, where the message is reassembled. SMS-COMMANDs identify messages by TP-MR and therefore apply to only one segment of a concatenated message. It is up to the originating SME to issue SMS-COMMANDs for all the required segments of a concatenated message. + +The Information-Element-Data octets shall be coded as follows. + +- Octet 1      Concatenated short message reference number. + +This octet shall contain a modulo 256 counter indicating the reference number for a particular concatenated short message. This reference number shall remain constant for every short message which makes up a particular concatenated short message. + +- Octet 2      Maximum number of short messages in the concatenated short message. + +This octet shall contain a value in the range 0 to 255 indicating the total number of short messages within the concatenated short message. The value shall start at 1 and remain constant for every short message which makes up the concatenated short message. If the value is zero then the receiving entity shall ignore the whole Information Element. + +- Octet 3      Sequence number of the current short message. + +This octet shall contain a value in the range 0 to 255 indicating the sequence number of a particular short message within the concatenated short message. The value shall start at 1 and increment by one for every short message sent within the concatenated short message. If the value is zero or the value is greater than the value in octet 2 then the receiving entity shall ignore the whole Information Element. + +The IEI and associated IEI length and IEI data shall be present in every segment of the concatenated SM. + +#### 9.2.3.24.2      Special SMS Message Indication + +There are three levels of "Message Waiting" indication provided within the present document. The first level is to set the Protocol Identifier to "Return Call message", which indicates that a message is waiting and relies on the text of the message to supply the detail. The second level uses the Data Coding Scheme with or without Return Call Message (see 3GPP TS 23.038 [9]) to indicate the type of message waiting and whether there are some messages or no messages. The third level is described here, and provides the maximum detail level for analysis by the mobile, i.e. an indication of the number and type of messages waiting in systems connected to the PLMN. + +This information shall be stored by the ME in the Message Waiting Indication Status on the SIM (see 3GPP TS 51.011 [16]) or USIM (see 3GPP TS 31.102 [30]) when present or otherwise should be stored in the ME. In case there are multiple records of EFMWIS this information shall be stored within the record according to the profile if available – or otherwise within the first record. + +The number of messages shall be stored in Message Waiting Indication Status and an indicator should be shown if the number of messages is non-zero or removed if the number of messages is zero. The ME may also provide some MMI to indicate and access the actual number of messages waiting. Text may be included by the SMS Service Centre for backward compatibility with the earliest Phase mobiles and the Data Coding Scheme may also be used to convey this information in parallel for backward compatibility with "middle" Phase mobiles (which support the use of Data Coding Scheme for Message Waiting Indication but not the use of TP-UDH for Message Waiting Indication). + +The information-Element octets shall be coded as follows: + +- Octet 1      Message Indication type and Storage. + +- Bit 7 Indicates whether or not the message shall be stored. +- Bit 7 +- 0      Discard message after updating indication +- 1      Store message after updating indication +- In the event of a conflict between this setting and the setting of the Data Coding Scheme (see 3GPP TS 23.038 [9]) then the message shall be stored if either the DCS indicates this, or Octet 1 above indicates this. +- Bits 0 and 1 indicate the basic message indication type. +- 00              Voice Message Waiting +- 01              Fax Message Waiting + +| | | +|----|-----------------------------------------------------------------------------| +| 10 | Electronic Mail Message Waiting | +| 11 | Extended Message Type Waiting (equivalent to "other" in 3GPP TS 23.038 [9]) | + +- Bits 432 indicate the extended message indication type. +- - 000 No extended message indication type. + - 001 Video Message Waiting +- Other values of bits 432 where bits 0 and 1 are '11' are Reserved for future use in the present document. +- Values of bits 432 where bits 0 and 1 are '00', '01' or '10' are Reserved for future use in the present document. + +NOTE: Values using bits 432 where bits 0 and 1 are '11' should be exhausted before using the remaining codespace due to existing early implementations erroneously using parts of this codespace. + +- Bits 6 and 5 indicate the profile ID of the Multiple Subscriber Profile (see 3GPP TS 23.097 [41]). +- - 00 profile ID 1 + - 01 profile ID 2 + - 10 profile ID 3 + - 11 profile ID 4 +- Terminals should be capable of receiving any values in octet 1, including those marked as Reserved. Terminals may add the Message Count of all unknown Message Waiting Indication types received within the same TP-UDH and indicate this result to the user. + +Octet 2 Message Count. + +- This octet shall contain a value in the range 0 to 255 indicating the number of messages of the type specified in Octet 1 waiting. The value 255 shall be taken to mean 255 or greater. In the event of a conflict between this setting and the setting of the Data Coding Scheme (see 3GPP TS 23.038 [9]) then the Message Count in the TP-UDH shall override the indication in the TP-DCS. + +If more than one type of message is required to be indicated within one SMS message, then further octets must be used, as in the following example: + +- [00] TP-UDL [1E] (30 decimal septets) +- [01] Length of TP-UDH [08] +- [02] IEI = Special SMS Message Indication [01] +- [03] Length = 02 +- [04] Octet 1 = Voice Mail, do not store [00] +- [05] Octet 2 = 04 Messages +- [06] IEI = Special SMS Message Indication [01] +- [07] Length = 02 +- [08] Octet 1 = Fax Mail, Store [81] +- [09] Octet 2 = 02 Messages + ++ 5 Fill bits + ++ 19 seven-bit character message text + +The Total number of bits is 210. + +In the case where this IEI is to be used in a concatenated SM then the IEI, its associated IEI length and IEI data shall be contained in the first segment of the concatenated SM. The IEI, its associated IEI length and IEI data should also be contained in every subsequent segment of the concatenated SM although this is not mandatory. However, in the case where these elements are not contained in every subsequent segment of the concatenated SM and where an out of + +sequence segment delivery occurs or where the first segment is not delivered then processing difficulties may arise at the receiving entity which may result in the concatenated SM being totally or partially discarded. + +#### 9.2.3.24.3 Application Port Addressing 8 bit address + +This facility allows short messages to be routed to one of multiple applications, using a method similar to TCP/UDP ports in a TCP/IP network. An application entity is uniquely identified by the pair of TP-DA/TP-OA and the port address. The port addressing is transparent to the transport, and also useful in Status Reports. + +The total length of the IE is 2 octets: + +- octet 1      Destination port. + +This octet contains a number indicating the receiving port, i.e. application, in the receiving device. + +- octet 2      Originator port. + +This octet contains a number indicating the sending port, i.e. application, in the sending device. + +The port range is up to 255 using 8 bit addressing space. The Integer value of the port number is presented as in 3GPP TS 23.040 clause 9.1.2.1. + +| VALUE (port number) | MEANING | +|---------------------|------------------------------------------| +| 0 - 239 | Reserved | +| 240 - 255 | Available for allocation by applications | + +A receiving entity shall ignore (i.e. skip over and commence processing at the next information element) any information element where the value of the Information-Element-Data is Reserved or not supported. + +In the case where this IE is to be used in a concatenated SM then the IEI, its associated IEI length and IEI data shall be contained in the first segment of the concatenated SM. The IEI, its associated IEI length and IEI data shall also be contained in every subsequent segment of the concatenated SM. + +#### 9.2.3.24.4 Application Port Addressing 16 bit address + +This facility allows short messages to be routed to one of multiple applications, using a method similar to TCP/UDP ports in a TCP/IP network. An application entity is uniquely identified by the pair of TP-DA/TP-OA and the port address. The port addressing is transparent to the transport, and also useful in Status Reports. + +The total length of the IE is 4 octets: + +- octet 1,2      Destination port. + +These octets contain a number indicating the receiving port, i.e. application, in the receiving device. + +- octet 3,4      Originator port. + +These octets contain a number indicating the sending port, i.e. application, in the sending device. + +The port range is up to 65535 using 16 bit addressing space. The Integer value of the port number is presented as in 3GPP TS 23.040 clause 9.1.2.1. + +| VALUE (port number) | MEANING | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 - 15999 | UDP/TCP port numbers assigned by IANA without the need to refer to 3GPP. For the procedure, use and assignment of port numbers in this range – refer to the IANA database. ( http://www.IANA.com/ ). See Note 1. | +| 16000 - 16999 | Available for allocation by SMS applications without the need to refer to 3GPP or IANA. See Note 2. | +| 17000 - 49151 | UDP/TCP port numbers assigned by IANA. For the procedure, use and assignment of port numbers in this range – refer to the IANA database. ( http://www.IANA.com/ ). See Note 1. | +| 49152 – 65535 | Reserved for future allocation by 3GPP. For a port number in this range an application must be made to 3GPP. | + +NOTE 1: The value used for this field by a particular application is the same value that the application would use when using a UDP or a TCP transport. Therefore, applications that register a UDP or TCP port with the IANA need to use the same registered value for this field. UDP and TCP ports are registered separately. Therefore, it is necessary to check the application since the fact that a particular TCP port is registered (e.g., for HTTP) does not mean that its corresponding UDP port will be also registered for the same application. + +NOTE 2: There is a risk of port numbers in this range having conflicting applications. If it is desirable to avoid such a conflict then an application for a port number in the range 49152 – 65535 is to be made to 3GPP. + +A receiving entity shall ignore (i.e. skip over and commence processing at the next information element) any information element where the value of the Information-Element-Data is Reserved or not supported. + +In the case where this IE is to be used in a concatenated SM then the IEI, its associated IEI length and IEI data shall be contained in the first segment of the concatenated SM. The IEI, its associated IEI length and IEI data shall also be contained in every subsequent segment of the concatenated SM. + +#### 9.2.3.24.5 SMSC Control Parameters + +The facility enables the SMS protocol headers to be expanded using a flexible method. It may be used to control the SMSC, but is also passed transparently to the receiving mobile. The Information Element must be present in every short message affected by it, i.e. in every short message in a concatenated message. + +The Information Element data octets shall be coded as follows: + +- octet 1            Selective Status Report. + - This facility is used to control the creation of Status Reports, depending on the error code of the particular message. It is also used by the sending entity to request inclusion of the original UDH into the Status Report. In this case the original UDH must be separated from the rest of the UDH using the Source Indicator. The TP-SRR must be set in order for the Selective Status Report to be enabled. The bits are defined as follows: +- bit 0 + - 0 No Status Report for short message transaction completed + - 1 Status Report for short message transaction completed +- bit 1 + - 0 No Status Report for permanent error when SC is not making any more transfer attempts + - 1 Status Report for permanent error when SC is not making any more transfer attempts +- bit 2 + - 0 No Status Report for temporary error when SC is not making any more transfer attempts + - 1 Status Report for temporary error when SC is not making any more transfer attempts +- bit 3 + - 0 No Status Report for temporary error when SC is still trying to transfer SM + - 1 Status Report for temporary error when SC is still trying to transfer SM +- bits 4 and 5 + - reserved for future use. +- bit 6 + +- 0 No activation +- 1 A Status Report generated by this Short Message, due to a permanent error or last temporary error, cancels the SRR of the rest of the Short Messages in a concatenated message. This feature can only be used where a SC is aware of the segmentation of a concatenated SM and is therefore an implementation matter. +- bit 7 + - 0 Do not include original UDH into the Status Report + - 1 Include original UDH into the Status Report + +#### 9.2.3.24.6 UDH Source Indicator + +The facility is used to separate the UDH of the original message, a UDH created by the SMSC, and a UDH provided by the original receiving entity. The Source Indicator is placed in front of the content inserted by the source. The indicated content (one or more Information-Elements) ends at the next UDH-Source-Indicator, or at the end of the UDH. The Separator is intended to be used especially in Status Reports, but can also be used by the SMSC to add information into Short Message (for example Message waiting). The default content for a UDH in a SMS-DELIVERY is the headers inserted by the sending device, and the default content for a UDH in a SMS-STATUS-REPORT is the headers copied from the SMS-DELIVERY-REPORT. + +Values of octet: + +- 01 The following part of the UDH is created by the original sender (valid in case of Status Report) +- 02 The following part of the UDH is created by the original receiver (valid in case of Status Report) +- 03 The following part of the UDH is created by the SMSC (can occur in any message or report) + +In the case where this IEI is to be used in a concatenated SM then the IEI, its associated IEI length and IEI data shall be contained in the first segment of the concatenated SM. The IEI, its associated IEI length and IEI data should also be contained in every subsequent segment of the concatenated SM although this is not mandatory. However, in the case where these elements are not contained in every subsequent segment of the concatenated SM and where an out of sequence segment delivery occurs or where the first segment is not delivered then processing difficulties may arise at the receiving entity which may result in the concatenated SM being totally or partially discarded. + +#### 9.2.3.24.7 (U)SIM Toolkit Security Headers + +There are no IEI data values associated with these IEI values and so the associated Length of Information element field is present but set to zero. + +These IEI values implicitly define that a Security Header is always present at the start of the TP-User-Data field which immediately follows the TP-User-Data-Header. Details of the Security Header will be found in TS 31.115 [28]. + +In the case where a concatenated message contains a Security Header then the Security Header will only be present in the first segment of a concatenated message. + +In the case where SMS compression is applied to a TP-User-Data field which contains a Security Header then the SMS compression header (3GPP TS 23.042 [26]) shall immediately precede the Security Header. + +#### 9.2.3.24.8 Concatenated short messages, 16-bit reference number + +This facility is an enhanced variant of the Concatenated Short Message facility (see clause 9.2.3.24.1). The enhancement is a 16-bit reference number, instead of the short 8-bit reference number. The larger reference number reduces the probability that two different concatenated messages are mistakenly sent with identical reference numbers to a receiver. Except for the size of the reference number this facility is identical to the Concatenated Short Message facility (see clause 9.2.3.24.1). + +In the case of uncompressed 8-bit data, the maximum length of the short message within the TP-UD field is 133 (140-7) octets. + +In the case of uncompressed GSM 7 bit default alphabet data, the maximum length of the short message within the TP-UD field is 152 (160-8) characters. A character represented by an escape-sequence shall not be split in the middle. + +In the case of 16 bit uncompressed USC2 data, the maximum length of the short message within the TP-UD field is 66 $((140-7)/2)$ characters. A UCS2 character shall not be split in the middle; if the length of the User Data Header is odd, the maximum length of the whole TP-UD field is 139 octets. + +In the case of compressed GSM 7 bit default alphabet data, 8 bit data or UCS2 the maximum length of the compressed short message within the TP-UD field is 133 (140-7) octets including the Compression Header and Compression Footer, both or either of which may be present (see clause 3.9). + +The relation between compression and concatenation is the same as for Concatenated Short Messages (see clause 9.2.3.24.1). + +The Information-Element-Data field contains information set by the application in the SMS-SUBMIT so that the receiving entity is able to re-assemble the short messages in the correct order. Each concatenated short message contains a reference number which together with the originating address and Service Centre address allows the receiving entity to discriminate between concatenated short messages sent from different originating SMEs and/or SCs. In a network which has multiple SCs, it is possible for different segments of a concatenated SM to be sent via different SCs and so it is recommended that the SC address should not be checked by the MS unless the application specifically requires such a check. + +The TP elements in the SMS-SUBMIT PDU, apart from TP-MR, TP-UDL and TP-UD, should remain unchanged for each SM which forms part of a concatenated SM, otherwise this may lead to irrational behaviour. TP-MR must be incremented for every segment of a concatenated message as defined in clause 9.2.3.6. A SC shall handle segments of concatenated message like any other short message. The relation between segments of a concatenated message is made at the originator, where the message is segmented, and at the recipient, where the message is reassembled. SMS-COMMANDs identify messages by TP-MR and therefore apply to only one segment of a concatenated message. It is up to the originating SME to issue SMS-COMMANDs for all the required segments of a concatenated message. + +The Information-Element-Data octets shall be coded as follows: + +- Octet 1-2 Concatenated short messages, 16-bit reference number. + +This octet shall contain a modulo 65536 counter indicating the reference number for a particular enhanced concatenated short message. This reference number shall remain constant for every short message which makes up a particular enhanced concatenated short message. + +- Octet 3 Maximum number of short messages in the enhanced concatenated short message. + +This octet shall contain a value in the range 0 to 255 indicating the total number of short messages within the concatenated short message. The value shall start at 1 and remain constant for every short message which makes up the enhanced concatenated short message. If the value is zero then the receiving entity shall ignore the whole Information Element. + +- Octet 4 Sequence number of the current short message. + +This octet shall contain a value in the range 0 to 255 indicating the sequence number of a particular short message within the concatenated short message. The value shall start at 1 and increment by one for every short message sent within the concatenated short message. If the value is zero or the value is greater than the value in octet 3 then the receiving entity shall ignore the whole Information Element. + +The IEI and associated IEI length and IEI data shall be present in every segment of the concatenated SM. + +#### 9.2.3.24.9 Wireless Control Message Protocol + +The Wireless Control Message Protocol (WCMP) is part of the WAP suite of protocols; an open standard specified by the WAP Forum Ltd. + +The protocol specifies a set of messages that can be used by the receiver to notify the sender if an error occurs. This can be due to routing problems, no application listening at the destination port number, or due to insufficient buffer capacity. The error messages can be used by the sender to avoid retransmitting packets, that can not be properly handled at the receiver. WCMP can also be used for diagnostics and informational purposes. WCMP messages are usually generated by a datagram transport layer or a management entity. + +The Information-Element-Data octet(s) shall be coded as follows: + +- Octet 1-n Protocol Data Unit of WCMP. + +This octet(s) shall contain a WCMP protocol data unit. + +In the case where this IE is to be used in a concatenated SM then the IEI, its associated IEI length and IEI data shall be contained in the first segment of the concatenated SM. The IEI, its associated IEI length and IEI data shall also be contained in every subsequent segment of the concatenated SM. + +## 9.2.3.24.10 Enhanced Messaging Service + +### 9.2.3.24.10.1 EMS Coding + +Enhanced Messaging is based on standard mechanism in GSM SMS messaging. The first mechanism is called **user data header** (TP-UDH), which makes it possible to include binary data in a normal SM prior the text message itself (clause 9.2.3.24). The binary data is in the TP-UD field (message), which means that it steals a part of the 140 bytes. Each object within the SM shall be identified by a IE in the TP-UD Header. The IE will contain a **octet** (refer to clause 9.2.3.24.10.1) that identifies the absolute position of the object within and from the beginning of the SM data. In case of formatting text, an additional octet will give the number of characters for which the formatting applies. Next mechanism that is used is **concatenation**, see clause 9.2.3.24.1. This mechanism permits longer messages than 140 bytes, in fact 255 messages a 140 bytes each can be concatenated to one message up to about 38k bytes. + +EMS IEs of the same type may occur more than once in a single message or one segment of a concatenated SM. + +#### 9.2.3.24.10.1.1 Text Formatting + +The Information-Element-Data octet(s) shall be coded as follows: + +- Octet 1 Start position of the text formatting. Set to the number of characters after the formatting shall be applied from the beginning of the SM data. + - This octet shall be coded as an integer value in the range 0 (beginning of the SM data) to the maximum number of characters included in the SM data of one single SM or one segment of a concatenated SM. +- Octet 2 Text formatting length. Gives the number of formatted characters or sets a default text formatting. + - This octet shall be coded as an integer value in the range 1 to the maximum number of characters for which the formatting applies in one single SM or one segment of a concatenated SM. + - A text formatting length value of 0 indicates that the text format shall be used as a default text format for the current SM. The default text format shall be used for all text in a concatenated SM unless temporarily overridden by a text formatting IE with a non-zero text format length field. + - It shall be possible to re-define the default text formatting to be applied to all subsequent text in the current SM by sending a new Text Format IE with text format length zero. + - Conflicting overlapping text formatting instructions shall be resolved by applying the formatting instructions in their sequential order. +- Octet 3 formatting mode value coded as following: + +| Octet 3: | | | Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | Bit 0 | +|----------|-------|------------------------------|-------|-------|-------|-------|-------|-------|-------|-------| +| Bit 1 | Bit 0 | *Alignment | | | | | | | | | +| 0 | 0 | Left | | | | | | | | | +| 0 | 1 | Center | | | | | | | | | +| 1 | 0 | Right | | | | | | | | | +| 1 | 1 | Language dependent (default) | | | | | | | | | + +\*in case formatting text is inserted on the same line as previous non formatting text or with a different mode value, the alignment value shall be set to the same value as the previous formatted predefined object. + +Alignment may affect object placement. + +| Bit 3 | Bit 2 | Font Size | +|-------|-------|------------------| +| 0 | 0 | Normal (default) | + +| | | | +|-------|---|---------------------------------------| +| 0 | 1 | Large | +| 1 | 0 | Small | +| 1 | 1 | reserved | +| Bit 4 | | Style bold | +| 1 | | Bold on | +| 0 | | Bold off | +| Bit 5 | | Style Italic | +| 1 | | Italic on | +| 0 | | Italic off | +| Bit 6 | | Style Underlined | +| 1 | | Underlined on | +| 0 | | Underlined off | +| Bit 7 | | Style Strikethrough | +| 1 | | Strikethrough on | +| 0 | | Strikethrough off | + +If bit 4,5,6 and 7 are set to 0, it will mean normal style (default). + +Octet 4 Text Colour. + +This Octet may be omitted by setting the IED length accordingly. + +Bits 0..3 define the Text Foreground Colour + +Bits 4..7 define the Text Background Colour + +Each colour is defined in a semi octet according to the table below. The actual colours displayed may vary between ME's depending on the display device used. + +The colour values defined are simple primary and secondary colours plus four levels of grey. Bright colours have a higher intensity than dark colours. + +| Nibble Value
(msb...lsb) | Colour | +|-----------------------------|---------------| +| 0000 | Black | +| 0001 | Dark Grey | +| 0010 | Dark Red | +| 0011 | Dark Yellow | +| 0100 | Dark Green | +| 0101 | Dark Cyan | +| 0110 | Dark Blue | +| 0111 | Dark Magenta | +| 1000 | Grey | +| 1001 | White | +| 1010 | Bright Red | +| 1011 | Bright Yellow | +| 1100 | Bright Green | + +| | | +|------|----------------| +| 1101 | Bright Cyan | +| 1110 | Bright Blue | +| 1111 | Bright Magenta | + +#### 9.2.3.24.10.1.2 Predefined Sound + +The Information-Element-Data octet(s) shall be coded as follows. + +- Octet 1 position indicating in the SM data the instant after which the sound shall be played. It will be set to the number of characters from the beginning of the SM data after which the sound shall be played. + +This octet shall be coded as an integer value in the range 0 (beginning of the SM data) to the maximum number of characters included in the SM data of one single SM or one segment of a concatenated SM. + +- Octet 2 sound number. Shall be encoded as a integer value. + +#### 9.2.3.24.10.1.3 User Defined Sound + +The Information-Element-Data octet(s) shall be coded as follows. + +- Octet 1 position indicating in the SM data the instant the after which the sound shall be played (refer to clause 9.2.3.24.10.1.2). +- Octet 2-n Protocol Data Unit as described in clause 9.2.3.24.10.3.1. + +This octet(s) shall contain a User Defined Sound. + +#### 9.2.3.24.10.1.4 Predefined Animation + +The Information-Element-Data octet(s) shall be coded as follows: + +- Octet 1 position indicating in the SM data the instant the animation shall be displayed. Set to the number of characters from the beginning of the SM data after which the animation shall be displayed. + +This octet shall be coded as an integer value in the range 0 (beginning of the SM data) to the maximum number of characters included in the SM data of one single SM or one segment of a concatenated SM. + +- Octet 2 animation number. Shall be encoded as an integer value. + +#### 9.2.3.24.10.1.5 Large Animation + +The Information-Element-Data octet(s) shall be coded as follows: + +- Octet 1 position indicating the instant the animation shall be displayed in the SM data (refer clause 9.2.3.24.10.1.4). +- Octet 2-n Protocol Data Unit as described in clause 9.2.3.24.10.3.3. + +This octet(s) shall contain a Large Animation. + +#### 9.2.3.24.10.1.6 Small Animation + +The Information-Element-Data octet(s) shall be coded as follows: + +- Octet 1 position indicating the instant the animation shall be displayed in the SM data (refer clause 9.2.3.24.10.1.4). +- Octet 2-n Protocol Data Unit as described in clause 9.2.3.24.10.3.3. + +This octet(s) shall contain a Small Animation. + +#### 9.2.3.24.10.1.7 Large Picture + +The Information-Element-Data octet(s) shall be coded as follows: + +- Octet 1 position indicating in the SM data the instant the picture shall be displayed. Set to the number of characters from the beginning of the SM data after which the picture shall be displayed. This octet shall be coded as an integer value in the range 0 (beginning of the SM data) to the maximum number of characters included in the SM data of one single SM or one segment of a concatenated SM. +- Octet 2-n Protocol Data Unit as described in 9.2.3.24.10.3.2. + +This octet(s) shall contain a Large Picture. + +#### 9.2.3.24.10.1.8 Small Picture + +The Information-Element-Data octet(s) shall be coded as follows: + +- Octet 1 position indicating in the SM data the instant the picture shall be displayed in the SM data (refer clause 9.2.3.24.10.1.7). +- Octet 2-n Protocol Data Unit as described in clause 9.2.3.24.10.3.2. + +This octet(s) shall contain a Small Picture. + +#### 9.2.3.24.10.1.9 Variable Picture + +The Information-Element-Data octet(s) shall be coded as follows: + +- Octet 1 position indicating in the SM data the instant the picture shall be displayed in the SM data (refer clause 9.2.3.24.10.1.7). +- Octet 2 Horizontal dimension of the picture. + +This octet shall contain the horizontal number of 8 pixels i.e. this value shall be multiplied by 8 to get the whole number of horizontal pixels. + +- Octet 3 Vertical dimension of the picture. + +This octet shall contain the vertical number of pixels. + +- Octet 4-n Protocol Data Unit as described in clause 9.2.3.24.10.3.2. + +This octet(s) shall contain a Variable Picture line by line from top left to bottom right. + +The values of the horizontal and vertical dimensions must be chosen properly by the sending entity. If the calculated size of this IE exceeds the limits of a single SM or segment it shall be discarded by the receiving entity. + +#### Examples of EMS coding + +All IE values in the TP-UD are hexadecimal values. + +#### 9.2.3.24.10.1.10 User Prompt Indicator + +With the User Prompt Indicator a sending entity is able to indicate to the receiving entity, that the following object is intended to be handled at the time of reception, e.g. by means of user interaction. The object may be a picture, an animation, a User Defined Sound or a combination of these. + +For example the User Prompt Indicator may be used when sending an operators logo to the ME that should be displayed instead of the operators name in standby mode. + +When receiving the object the user shall be prompted to accept or discard the object. After this user interaction the SM may be discarded. + +The User Prompt Indicator IE shall immediately precede the corresponding object IE(s). + +If a User Prompt Indicator IE is not followed by a corresponding object IE it shall be discarded. + +The Information-Element-Data octet(s) shall be coded as follows: + +- Octet 1 Number of corresponding objects. + - This octet shall contain the number of corresponding objects as an integer value. + +Where Octet 1 indicates that the User Prompt Indicator refers to more than one object, the ME should check the validity of the objects referenced for stitching together. The objects should be considered for stitching if they are either Images (Small, Large, Variable Pictures) or User Defined Sounds, and all of the objects referenced by the User Prompt Indicator IE are of the same type. Animations, Text formatting and pre-defined sound IE's are not suitable for stitching. + +User defined sounds may be stitched by concatenating the data contained within each User Defined Sound IE into a single melody object, this may be achieved by ignoring the iMelody header and footer information of the second and subsequent User Defined Sound IE's referenced from the User Prompt Indicator. + +Images may be joined along their vertical edges, to form a single "wide" image, the resulting image will have a width equal to the sum of the widths of all the images defined in the User Prompt Indicator. + +#### 9.2.3.24.10.1.11 Standard WVQ Object + +The Standard WVQ object as defined by IEI 18 is structured as follows: + +Octet 1 position indicating in the SM data the instant the object shall be displayed in the SM data + +Octet 2..n Standard WVQ object bit stream + +The unused bits in the last octet will be filled with 0 + +The detailed data format and attributes of Standard WVQ object are defined in Annex G. + +The bit order is defined as follows: + +The octet with a smaller octet number stores the bits appearing in the front position in the bit stream; the most significant bit in an octet stores the first bit in position in a 8-bit segment in the bit stream. + +A Standard WVQ object may or may not have fixed size. In either case, display size should be determined by the terminal implementation. Recommended display size is a largest possible size on terminal screen while aspect ratio shall be maintained. + +#### 9.2.3.24.10.1.12 Character Size WVQ Object + +The Character Size WVQ object as defined by IEI 19 is structured as follows: + +Octet 1 position indicating in the SM data the instant the object shall be displayed in the SM data + +Octet 2..n Character Size WVQ bit stream + +The unused bits in the last octet will be filled with 0 + +The detailed data format and attributes of Character Size WVQ object are defined in Annex G. + +The bit order is defined as follows: + +The octet with a smaller octet number stores the bits appearing in the front position in the bit stream; the most significant bit in an octet stores the first bit in position in a 8-bit segment in the bit stream. + +A Character Size WVQ object is a small graphics similar to the size of a typed character. The display height for a Character Size WVQ object is decided by the terminal implementation. Recommended Character Size WVQ object height is to be similar to the message text font height. The width of a Character Size WVQ object is variable depending on the aspect ratio defined in the object. Character Size WVQ objects can appear more than one time in one message. + +Example: + +**Dad, I ♥ you!** + +In the above example, the “heart” is a Character Size WVQ object at the position in between the letter “I” and “y”. + +你好北京 + +In the above example, there are 4 Character Size WVQ objects, each representing a Chinese character. + +### 9.2.3.24.10.1.13 Extended Object + +The Extended Object allows an extended code range for format types. The Extended Object may extend across segment boundaries of a concatenated short message. Octets 1 through 7 of the first Extended Object IE shall be contained in a single segment. A single segment may include one or more Extended Object IEs. + +If multiple SMs are concatenated and at least one of them contains an Extended Object information element, then concatenation of the SMs shall be done using the 'Concatenated short messages, 16-bit reference number', versus the 'Concatenated short messages, 8-bit reference number' information element. The re-assembly of the Extended Object segments shall be done according to the sequence number of the associated Concatenation IE. + +One or more Extended Objects may be compressed using a compression algorithm as indicated in the Compression Control IE (see clause 9.2.3.24.10.1.13). + +An SME implementing the Extended Object IE shall be capable of interpreting an uncompressed concatenated message composed of at least **min\_co\_msg** short messages which have been received. According to current content provider requirements and handset manufacturer constraints, variable **min\_co\_msg** is set to 8. + +The first Extended Object IE of an Extended Object contains a reference number, length, control data, type and position. The subsequent Extended Object IEs shall only contain Extended Object data as illustrated in Figure 9.2.24.10.11. + +The IE length is variable. + +- Octet 1        Extended Object reference number. +A modulo 256 counter indicating the reference number for the Extended Object. Two different Extended Objects in a single concatenated message shall have different reference numbers. +- Octet 2..3    Extended Object length in number of octets (integer representation) as shown in Figure 9.2.3.24.10.1.11. +- Octet 4        Control data. +- Bit 0            Object distribution +- 0    Object may be forwarded +- 1    Object shall not be forwarded by SMS +- Bit 1            User Prompt Indicator +- 0    Object shall be handled normally +- 1    Object shall be handled as a User Prompt (see 9.2.3.24.10.1.10) +- Bit 2..7        reserved +- Any reserved values shall be set to 0. +- Octet 5        Extended Object Type. +This octet indicates the format of the Extended Object from the table below. +If the value is reserved or if the associated format is not supported then the receiving entity shall ignore the Extended Object. + +| Format Type | Format Description | +|-------------|---------------------------------------------------------| +| 0x00 | Predefined sound as defined in annex E. | +| 0x01 | iMelody as defined in annex E. | +| 0x02 | Black and white bitmap as defined in annex E. | +| 0x03 | 2-bit greyscale bitmap as defined in annex E. | +| 0x04 | 6-bit colour bitmap as defined in annex E. | +| 0x05 | Predefined animation as defined in annex E. | +| 0x06 | Black and white bitmap animation as defined in annex E. | +| 0x07 | 2-bit greyscale bitmap animation as defined in annex E. | +| 0x08 | 6-bit colour bitmap animation as defined in annex E. | +| 0x09 | vCard as defined in annex E. | +| 0x0A | vCalendar as defined in annex E. | +| 0x0B | Standard WVG object as defined in annex E | +| 0x0C | Polyphonic melody as defined in annex E. | +| 0x0D.. 0xFE | Reserved | +| 0xFF | Data Format Delivery Request as defined in annex E. | + +## Octet 6..7 Extended Object Position (integer representation). + +The Extended Object Position indicates the absolute character position within the message text after which the object shall be played or displayed. The absolute character position relates to the entire text within the concatenated message, the first character is numbered character 1. + +NOTE: Although this is an absolute value, for concatenated messages, it is suggested the positions used are those that lie within the text of short message segments that have the sequence number equal to or higher than the one that contains the Extended Object IE. + +If more than one Extended Object is located at the same position then they may be played or displayed in sequence or simultaneously. + +Octet 8..n Extended Object Data. + +This sequence of octets is structured as illustrated in the figure below and defined annex E. This figure illustrates the construction of a number of SMs containing a large Extended Object which crosses a SM boundary and is encoded into 2 SM TPDU. The figure illustrates only the User Data field of the SM (TPDUs). For a description of concatenation of SM refer to Figures 9.2.3.24 (a, b and c) + +![Diagram illustrating the construction of Extended Object Data across two SM TPDU. The top part shows the internal structure of the Extended Object Header Information (octets 1-7) and Extended Object Data (octet 8..n). The bottom part shows the mapping of these octets into two TPDU User Data (UDHL) fields. TPDU 1 contains the header and the start of the data, while TPDU 2 contains the continuation of the data. Arrows indicate the mapping of octet ranges from the top structure to the TPDU fields.](dcf83796ccf494110638fbd4677b931d_img.jpg) + +| Extended Object Header Information | | | | | Extended Object Data | | +|------------------------------------|-----------|-------------|--------------|-----------------|-------------------------|----------------------| +| Octet Number | 1 | 2,3 | 4 | 5 | 6,7 | 8.....n | +| | Reference | Data Length | Control Byte | Type Identifier | Positioning Information | Extended Object Data | + + + +| TPDU | UDHL | Concatenation Info | IEI
E.O.* | IEIDL | Extended Object Header | Extended Object Data | +|--------|------|--------------------|--------------|-------|------------------------|----------------------| +| TPDU 1 | | | | | | | + + + +| TPDU | UDHL | Concatenation Info | IEI
E.O.* | IEIDL | Continuation of Extended Object Data | +|--------|------|--------------------|--------------|-------|--------------------------------------| +| TPDU 2 | | | | | | + +\* E.O. means Extended Object + +Diagram illustrating the construction of Extended Object Data across two SM TPDU. The top part shows the internal structure of the Extended Object Header Information (octets 1-7) and Extended Object Data (octet 8..n). The bottom part shows the mapping of these octets into two TPDU User Data (UDHL) fields. TPDU 1 contains the header and the start of the data, while TPDU 2 contains the continuation of the data. Arrows indicate the mapping of octet ranges from the top structure to the TPDU fields. + +Figure 9.2.3.24.10.1.13 + +#### 9.2.3.24.10.1.14 Reused Extended Object + +This facility is used to reuse an Extended Object in a message which has already been defined in the same message. + +Octet 1 Reference number of the Extended Object to be reused. + +NOTE: The suggested reference numbers are those of Extended Objects that are contained in short messages that have the sequence number equal to or lower than the one that contains the Reused Extended Object IE. + +Octet 2..3 indicates in the concatenated message the absolute character position after which the object shall be played or displayed. + +NOTE: Although this is an absolute value, for concatenated messages, the suggested positions that lie within the text of short message segments that have the sequence number equal to or higher than the one that contains the Extended Object IE. + +#### 9.2.3.24.10.1.15 Compression Control + +This information element is used to indicate a compressed octet sequence. The compression control is only used in association with one or more Extended Objects and/or Reused Extended Objects. The compressed data may extend across sequential short messages within a concatenated short message as illustrated by Figure 9.2.24.10.1.15. The first Compression Control IE of a compressed data sequence contains one octet of Compression Information and a 2-octet length field. + +The SME shall support decompression if the Extended Object IE is implemented. An SME implementing the Extending Object IE shall be capable of decompressing a received stream for which the original uncompressed information fits into 1 to **min\_eo\_msg** messages. An SME may be capable of decompressing a received stream for which the original uncompressed information fits into more than **min\_eo\_msg** short messages. Variable **min\_eo\_msg** is defined in clause 9.2.3.24.10.1.11. + +The IE length is variable. + +Octet 1            Compression information. + +Bits 0..3 represent the compression algorithm and bits 4..7 represent compression algorithm specific parameters. + +Bit 0..3            Compression algorithm + +0000                LZSS Compression according to clause 9.2.3.24.10.1.15.1 + +Bit 4..7            Shall be set 0. + +0001..1111        reserved for future use; reserved bits shall be transmitted 0. + +Bit 4..7            reserved + +Octets 2..3        Length of the compressed data in octets (integer representation). + +The length indicates the length of the compressed data that may extend across several compression control IEs. + +Octets 4..n        Compressed data may contain one or more compressed Extended Objects. Figure 9.2.3.24.10.1.15 is an example and illustrates the assembly of a series of SM TPDU from a sequence of concatenated and compressed extended objects. Each Extended Object is preceded by its IEI (Extended Object or Reused Extended Object). A series of Extended Objects is then compressed into a single buffer and this is split into several SM TPDU as illustrated. + +![Diagram illustrating the LZSS implementation for EMS extended object compression. The process starts with an 'Extended Object Header' and 'Extended Object Data'. The header is a table with fields: Object n Reference, Object n data length, Object n control byte, Object n type identifier, Object n information, and Object n data. These are concatenated into a single byte stream containing IEI EO *, Extended Object 1, IEI EO *, Extended Object 2, IEI REO*, and Reused Extended Object 1. This stream is then compressed into a 'Compressed Data Stream'. An 'Extended Object Compression Information Header' is added, consisting of Compression Information, Compressed Data Length, and the Compressed Data Stream. This is further processed into a 'Compression Header' (Compression Information, Compressed Data Length) and 'Compressed Data'. Finally, individual EMS User-Data-Header fields are built from the compressed stream, resulting in two possible formats: one with UHDL, Concatenation information, IEI C.C., EIDL, Compression Header, and Compression Data; and another with U DHL, Concatenation Information, IEI CC, EIDL, and Continuation of Compression Data.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +Extended Object Header + +Extended Object Data + +| | | | | | | +|--------------------|----------------------|-----------------------|--------------------------|----------------------|---------------| +| Object n Reference | Object n data length | Object n control byte | Object n type identifier | Object n information | Object n data | +|--------------------|----------------------|-----------------------|--------------------------|----------------------|---------------| + +Concatenate Extended objects into single byte stream + +| | | | | | | +|----------|-------------------|----------|-------------------|----------|--------------------------| +| IEI EO * | Extended Object 1 | IEI EO * | Extended Object 2 | IEI REO* | Reused Extended Object 1 | +|----------|-------------------|----------|-------------------|----------|--------------------------| + +Compress + +Compressed Data Stream + +Add Extended Object Compression Information Header + +| | | | +|-------------------------|------------------------|------------------------| +| Compression Information | Compressed Data Length | Compressed Data Stream | +|-------------------------|------------------------|------------------------| + +Compression Header + +Compressed Data + +Build individual EMS User-Data-Header fields from the compressed extended object byte stream + +| | | | | | | +|------|---------------------------|----------|------|--------------------|------------------| +| UHDL | Concatenation information | IEI C.C. | EIDL | Compression Header | Compression Data | +|------|---------------------------|----------|------|--------------------|------------------| + +| | | | | | +|-------|---------------------------|--------|------|----------------------------------| +| U DHL | Concatenation Information | IEI CC | EIDL | Continuation of Compression Data | +|-------|---------------------------|--------|------|----------------------------------| + +Diagram illustrating the LZSS implementation for EMS extended object compression. The process starts with an 'Extended Object Header' and 'Extended Object Data'. The header is a table with fields: Object n Reference, Object n data length, Object n control byte, Object n type identifier, Object n information, and Object n data. These are concatenated into a single byte stream containing IEI EO \*, Extended Object 1, IEI EO \*, Extended Object 2, IEI REO\*, and Reused Extended Object 1. This stream is then compressed into a 'Compressed Data Stream'. An 'Extended Object Compression Information Header' is added, consisting of Compression Information, Compressed Data Length, and the Compressed Data Stream. This is further processed into a 'Compression Header' (Compression Information, Compressed Data Length) and 'Compressed Data'. Finally, individual EMS User-Data-Header fields are built from the compressed stream, resulting in two possible formats: one with UHDL, Concatenation information, IEI C.C., EIDL, Compression Header, and Compression Data; and another with U DHL, Concatenation Information, IEI CC, EIDL, and Continuation of Compression Data. + +\*E.O Means Extended Object. + +\*R.E.O means Reused Extended Object. + +C.C. means compression. + +Figure 9.2.3.24.10.1.15 + +#### 9.2.3.24.10.1.15.1 LZSS Implementation for EMS extended object compression + +LZSS compression uses two tokens to identify either literal strings (byte-sequences) or references to repeated sequences. These tokens (for EMS extended-object compression) are described in this clause of the document. A more general introduction to LZSS compression together with an informative example (based upon the tokens described below) is provided in Annex F (informative). + +The compressed data stream consists of any combination of literal data blocks and slice descriptor sequences. + +The format of the compressed data stream is illustrated as follows: - + +![](38d82ffe820e339811b396206f40a201_img.jpg) + +| Compressed data stream (initial section) ..... | | | | | | | | | | | | | | | | | +|------------------------------------------------|---|---|---|---|---|---|------------------|---|--------------------|---|---|------------------|---|------------------|--|--| +| 1 | 2 | 3 | 4 | 5 | . | . | . | . | . | . | . | . | . | | | | +| Literal data block | | | | | | | Slice descriptor | | Literal data block | | | Slice descriptor | | Slice descriptor | | | + +**Figure 9.2.3.24.10.1.15.1.a**      **LZSS compressed data format** + +This diagram represents the structure of a compressed byte stream using LZSS. The stream contains a mixture of literal octets from the input buffer and slice descriptors representing the re-occurrence of an octet sequence together with a length and index for the matching octet sequence. The initial octets of a compressed buffer will always be a sequence of literal octets. The structures of the literal data blocks and slice descriptors are given below. + +![](4540c7355b250cb891be0b54b0ba25c7_img.jpg) + +| Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | Bit 0 | +|-------|---------------------------------|-------|-------|-------|-------|-------|-------| +| 1 | Number literal bytes to follow. | | | | | | | + +**Figure 9.2.3.24.10.1.15.1.b**      **Literal block identifier** + +When literal octets are written into the compression buffer (for instance during the initial phases of compression) they are preceded by a literal block identifier. The most significant bit (bit 7) of this block shall be set 1. Bits 6-0 indicate the length of the literal block which follows (up to 127 octets). If no match can be found in an octet sequence of greater than 127 octets then 2 (or more) literal blocks shall be written sequentially. + +| Octet 1 | | | | | | | | Octet 2 | | | | | | | | +|---------|--------------|--------|--------|--------|--------|-------|-------|--------------|-------|-------|-------|-------|-------|-------|-------| +| Bit 15 | Bit 14 | Bit 13 | Bit 12 | Bit 11 | Bit 10 | Bit 9 | Bit 8 | Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | Bit 0 | +| 0 | Slice Length | | | | | | | Slice Offset | | | | | | | | + +Figure 9.2.3.24.10.1.15.1.c + +Slice Descriptor + +As can be seen from the above table, the slice descriptor sequence length is two octets, hence only repeating slices of data longer than two octets are extracted. The “slice length” is contained in the descriptor high octet and describes a data slice length of up to 63 octets. The “slice offset index” to the start of the slice is contained in the lower 9 bits and limits the window to 511 octets. The “slice offset index” gives the start position of the source slice measured backwards from the current writing position in the output decoded message data buffer, expressed as a positive number. + +### 9.2.3.24.10.1.15.2 Data Compression + +The compressed data output stream is constructed by repeating the following process until the end of the input data buffer is reached. + +The input data buffer is scanned, from the current reading position (minus 1) through to a position 511 bytes back from current reading position (the window) looking for the maximum (but limited to 63 octets) length matching data slice contained that matches the data starting at the current reading position (the look ahead buffer). + +If no matching data slice, longer than two octets, is found then the input data octet at the current reading position is written to a literal buffer. Both the current reading position in the input data buffer and the current writing position in the output data buffer are incremented by one. + +If a matching slice is found then a slice descriptor is written to the output data buffer at the current writing position in the output data buffer and the current writing position is incremented by two. The current reading position in the input data buffer is incremented by the length of the newly found matching data slice. + +If the next read octet results in a matching slice being found then the literal buffer is written out. The literal block header, containing a count of the number of literals in the block, is written out first. (If more than 127 literal octets exist in the literal buffer, then it is split into multiple blocks). + +The above sequence is repeated until the current reading position reaches the end of the input data buffer. + +When encoding (compressing), it is the input data buffer, up to the current reading position, that is used to search for already known matching data slices, as this represents, and is equal to, the reconstructed output data buffer of the decoder at the receiving end. + +### 9.2.3.24.10.1.15.3 Data De-compression + +The following sequence is repeated until the end of the input data buffer. + +The data octet at the current reading position in the input data buffer is tested for either 0 or 1 in bit 7. + +If the bit is set (bit 7 = 1), then the number of literal octets that follow is determined from the lower 7 bits of the header octet (this one). + +The literal octet block is written to the output data buffer at the current writing position and both the output data writing position and the input data reading position pointers are incremented by the block size. + +If the bit is clear (bit 7 = 0), then the “slice length” and “slice offset index” are extracted from the two octet slice descriptor. + +The data slice is copied from within the output data buffer to the end of the output data buffer, where the start of the source slice is at a position “slice offset index” back from the current output data writing position and the destination start position of the slice is the current output buffer writing position. The input data buffer reading position is incremented by two and the output data writing position is incremented by the “slice length”. + +#### 9.2.3.24.10.1.15.4 Test Vectors + +In order to assist implementers of the compression algorithm described in this specification, a suite of test vectors and 'help' information are available in electronic format. The test vectors are supplied with this specification. + +These test vectors provide checks for most of the commonly expected parameter value variants in this specification and may be updated as the need arises. + +In addition Annex F contains an introduction to LZ-type compression algorithms and also has a brief informative example. + +#### 9.2.3.24.10.1.16 Object Distribution Indicator + +This facility allows a level of control to be requested over the distribution of objects contained within selected information elements in short messages. + +If no Object Distribution Indicator is specified for an information element in which an object is received, then that object may be freely distributed. + +If a MS provides facilities to modify an object, then the Distribution Attributes (see below) shall be maintained; i.e. an object that is not allowed to be distributed cannot become so after modification. + +The use of the Object Distribution Indicator in conjunction with a TE is beyond the scope of the present document. + +Where the Object Distribution Indicator is applied to object IE's that are also addressed by an IE which affects or controls them in some other way (such as User Prompt Indicator IE (see clause 9.2.3.24.10.1.10)), then it shall precede all of the IE's including the other controlling IE's. + +Octet 1 Number of Information Elements. + +This octet specifies the number of information elements from 1-255 for which the Distribution Attributes in the next octet shall apply. The affected objects shall be contained in Information Elements immediately following this IE and may be contained in subsequent short message segments within a concatenated short message. + +If the Object Distribution Indicator is applied to the same object IE's as addressed by an IE which affects or controls them in some other way (such as the User Prompt Indicator IE), then value of this field shall reflect the total number of all the object IE's and all of the controlling IE's. + +If set to 0 the Distribution Attributes shall apply to all information elements until either the end of the message or another Object Distribution Indicator IE is received. + +Octet 2 Distribution Attributes. + +Bit 0 + +0 the associated object(s) may be forwarded + +1 the associated object(s) shall not be forwarded by SMS + +bit 1..7 + +reserved for future use. + +#### 9.2.3.24.10.1.17 Reply Address Element + +Only one alternate Reply Address Element can be integrated in a message. In the case the Reply Address Element is part of a Concatenated SM this IE shall occur in its first segment only. + +Octet 1..n Alternate Reply Address encoded as specified for address fields in clause 9.1.2.5 + +When this IE is received in a message, replies to this message should take place by default using the address specified in this IE instead of the regular message TP-OA. + +NOTE: Despite the fact that MMI aspects of the ME are out of the scope of the present document, it must be mentioned that this mechanism might open the door to potential abuse. It is desirable that the user is made aware in some way that the reply address of the incoming message is different from the originator's one, and that the user is presented with the original TP-OA address to identify the sender of the SM . + +#### 9.2.3.24.10.1.18 Extended Object Data Request Command + +There is no data element associated with this IE. The associated Information Element Length field is present but set to zero. + +Upon receiving this IE in an SMS-DELIVER PDU, if an MS supports this request and the corresponding response, it shall respond with an SMS-DELIVER-REPORT PDU containing a Data Format Delivery Request as defined in the Extended Object IE. This SMS-DELIVER PDU may be discarded. + +#### 9.2.3.24.10.2.1 Example of Basic text formatting and predefined EMS coding + +An example of the basic concept of coding is given as follows: + +TP-UDHI=1 + +SMS User Data Header: UDHL=05, IEI=0A, IEDL=03, IED1=0F, IED2=12, IED3=10 + +SMS User Data: This is a text with bold option on following with normal text. + +Should be displayed as: + +This is a text **with bold option on** following with normal text. + +It is also possible to add predefined sounds in the message. + +Example: + +TP-UDHI=1 + +SMS User Data Header: UDHL=08, IEI=0B, IEDL=02, IED1=09,, IEI=0B, IEDL=2, IED1=1C, + +SMS User Data: This is a message with two different sounds. + +The sound nr5 shall be played after the 9th received character ("a") and sound nr7 shall be played after the 28th received character ("e"). + +### 9.2.3.24.10.2.2 Example of User defined Objects EMS coding + +Example of a message including one small picture is coded as follows: + +TP UDHI=1 + +SMS User Data Header: UDHL=24, IEI=11, IEIDL=22, IED1=08, < (small picture 32bytes)> + +SMS User Data: Hello!One small picture in here + +Should be displayed as: + +![A rectangular box representing a mobile phone screen display. It contains the text 'Hello!' at the top and 'One small picture in here' at the bottom, separated by a blank space.](bc4b03830125f24f55b78ce2a3558887_img.jpg) + +A rectangular box representing a mobile phone screen display. It contains the text 'Hello!' at the top and 'One small picture in here' at the bottom, separated by a blank space. + +If the message starts with , then the "unreadable" data in an old terminal will be overwritten by the text, and the user will not see any strange characters. It is possible to insert the same picture several times in the same message. In that case, the TP-UD header shall contain as many IE as the number of occurrences contained in the SM or one segment of a concatenated message. Using defined elements will normally imply that more than one SM is required and therefore concatenation is required. + +### 9.2.3.24.10.2.3 Concatenation of SMS messages + +Concatenated messages are required in most cases required when using several types of EMS elements, since it is only possible to send one large picture/large animation/melody in one single SM. After including either of these elements, there are only 4 (or 9 if no concatenation is used) characters left to the text part, and this is usually too little. + +If one or more objects are embedded in one segment of a concatenated message, the IE octet indicating its/their position within the SM data cannot be set to a value that would refer to a position in the next segment(s) so that received segments should be processed before all of them have been received. It means that a formatting text that could not be conveyed in one segment shall be split in as many segments as necessary. In that case, the IE relating to the formatting shall be repeated in all the segments in which it will apply. + +Example of a message including 2 Large Pictures, 4 Small animations and 2 User defined Melodies together with some text. + +The EMS message: Hello All, This is a real Enhanced Message . I can send and receive really advanced EMS messages Isn't it impressive? /Lars + +This EMS message has to use concatenated messages and the SM will typically contain the following data: + +| SM | User Data Header | User Data | +|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| 1 | IEI=10 (Large Picture)
IED:=00 (beginning of the SM)
| [] | +| 2 | IEI=0C (User Defined Sound)
IED:=00 (beginning of the SM)
| Hello | +| 3 | IEI=0F (Small Animation)
IED:=24 (36 th position)

IEI=0F (Small Animation)
IED:=2F (47 th position)
| All, This is a real Enhanced Message. I can send and | +| 4 | IEI=0F (Small Animation)
IED:=07 (7 th position)

IEI=0F (Small Animation)
IED:=25 (37 th position)
| receive really advanced EMS messages. Isn't it impressive? /Lars. | +| 5 | IEI=0C (User Defined Sound)
IED:=00 (beginning of the SM)
| [] | +| 6 | IEI=10 (Large Picture)
IED:=00 (beginning of the SM)
| | + +### 9.2.3.24.10.3 EMS Formats + +#### 9.2.3.24.10.3.1 Sounds + +##### Predefined Sounds + +There are a number of fixed predefined sounds. Each sound nr corresponds to a specific sound according to the table below. The presentations of these sounds are manufacturer specific. + +| Sound nr | Description | +|----------|-------------| +| 0 | Chimes high | +| 1 | Chimes low | +| 2 | Ding | +| 3 | TaDa | +| 4 | Notify | +| 5 | Drum | +| 6 | Claps | +| 7 | FanFar | +| 8 | Chord high | +| 9 | Chord low | + +##### User defined sounds + +The user defined sounds are coded according to the iMelody format[33]. The maximum length of a sound is 128 bytes. + +#### 9.2.3.24.10.3.2 Pictures + +Pictures are coded from upper left to lower right and in each byte the most significant bit represent the pixel at the left. The pictures are plain black and white, no colours or grey scales are supported. The bitvalue "0" represents a white pixel and the bitvalue "1" represents a black pixel. + +Example 16\*16 picture + +| | | +|---------|---------| +| Byte 1 | Byte 2 | +| Byte 3 | Byte 4 | +| ... | ... | +| ... | ... | +| Byte 31 | Byte 32 | + +### 9.2.3.24.10.3.3 Animation + +#### Predefined + +There are a number of predefined animations. Each animation nr corresponds to a specific animation according to the table below. The way of displaying the animation is manufacturer specific. + +| Animation nr | Description | +|--------------|---------------------| +| 0 | I am ironic, flirty | +| 1 | I am glad | +| 2 | I am sceptic | +| 3 | I am sad | +| 4 | WOW! | +| 5 | I am crying | +| 6 | I am winking | +| 7 | I am laughing | +| 8 | I am indifferent | +| 9 | In love/Kissing | +| 10 | I am confused | +| 11 | Tongue hanging out | +| 12 | I am angry | +| 13 | Wearing glasses | +| 14 | Devil | + +#### User Defined + +Animations are coded as 4 sequential pictures, with the first picture sent first. + +### 9.2.3.24.11 IETF RFC 5322 E-Mail Header + +This information element is used to indicate the existence of an IETF RFC 5322 Internet electronic mail in the data part of the short message. Both, E-Mail Header and (optional) E-Mail Body shall be parts of the SM's data and shall be compliant with the syntax specified in IETF RFC 5322 [34]. The character set used for encoding of E-Mail Header and E-Mail body, however, shall be according to 3GPP TS 23.038 [9]. Encoding of E-Mail Header and E-Mail Body shall be done using the same character set. + +In compliance with IETF RFC 5322 [34] the E-Mail Header shall always be located at the very beginning of the SM's data part. It shall always be present in the "unfolded" format as it is specified in IETF RFC 5322 [34]. Not the character defined in IETF RFC 5322 [34] but the character according to 3GPP TS 23.038 [9] shall be used for the separation of different E-Mail Header fields. + +If an RFC 5322 E-Mail Body exists, it shall immediately follow the E-Mail Header in the SM's data part. + +NOTE 1: The null line defined in IETF RFC 5322 [34] for the separation of E-Mail Header and E-Mail Body may be discarded. + +NOTE 2: The sending of extended SMTP headers is allowed and the MS should not reject the message if there are header fields in the email header part that are not specified in IETF RFC 5322 [34]. + +In case of an IETF RFC 5322 [34] E-Mail Header exceeding the data part of a single SM, concatenation shall be used. In this case the E-Mail Header starts in the first segment of a concatenated SM and continues in one or several subsequent segments. The IETF RFC 5322 [34] E-Mail Body shall immediately follow the final fraction of the IETF RFC 5322 [34] E-Mail Header and may also be spread over several segments of the concatenated SM. + +In case where this IEI is to be used in a concatenated SM then the IEI, its associated IEDL, and IED fields shall be contained in the first segment of the concatenated SM and shall also be contained in every subsequent segment of the concatenated SM. + +The Information-Element-Data octet shall be coded as follows: + +Octet 1 IETF RFC 5322[34] E-Mail Header length indicator. + +This octet shall indicate the length of the IETF RFC 5322 [34] E-Mail Header that is located at the beginning of the data part of the SM. In case of an E-Mail Header exceeding the data part of a single SM, this octet shall indicate the length of that fraction of the IETF RFC 5322 [34] E-Mail Header that is located at the beginning of the data part of the current segment of the concatenated SM. + +If the user data is coded using the GSM 7 bit default alphabet, this IED octet shall give an integer representation of the number of septets within (that fraction of) the IETF RFC 5322 [34] E-Mail Header that is located at the beginning of the data part of the current (segment of the concatenated) SM. See figure 9.2.3.24.11 (a). + +If the user data is coded using 8-bit data, this IED octet shall give an integer representation of the number of octets within (that fraction of) the IETF RFC 5322 E-Mail Header that is located at the beginning of the data part of the current (segment of the concatenated) SM. See figure 9.2.3.24.11 (b). + +If the user data is coded using UCS2 [24] data, this IED octet shall give an integer representation of the number of UCS2 characters (consisting of 2 octets) within (that fraction of) the RFC 822 E-Mail Header that is located at the beginning of the data part of the current (segment of the concatenated) SM. See figure 9.2.3.24.11 (c). + +NOTE 3: If the user data is coded using compressed GSM 7 bit default alphabet or compressed 8 bit data or compressed UCS2 [24] data the RFC 822 E-Mail Header length indicator's value shall be based on the amount of uncompressed data, i.e. before compression is performed. + +The diagram below shows the layout of the IED for GSM 7 bit default alphabet data. + +![Diagram showing the layout of the IED for GSM 7 bit default alphabet data. It includes fields like UDL, UDHL, IEIa, IEIx, IEIDLx, IEDx, IEDn, Fill bits, RFC 822 Header, and RFC 822 Body. Annotations indicate 'Octet', 'SM (7bit data)', 'Number of Septets', 'Length Indicator', 'Total number of Octets', and 'Total number of Septets'.](b43872c7a81f62572f3be03b77d8655f_img.jpg) + +The diagram illustrates the structure of a concatenated Short Message (SM) for GSM 7-bit default alphabet data. The top row shows the fields: UDL, UDHL, IEIa, ..., IEIx = 20, IEIDLx = 01, IEDx, ..., IEDn, Fill bits, RFC 822 Header, and RFC 822 Body. Above the IEIDLx = 01 field, an arrow labeled 'Octet' points to it. Above the RFC 822 Header and RFC 822 Body, a bracket labeled 'SM (7bit data)' spans both. Below the fields, several annotations with arrows indicate specific lengths: 'Total number of Octets' spans from the start of IEIa to the start of Fill bits; 'Length Indicator' (for octets) is shown below that, spanning the same range; 'Total number of Septets' spans from the start of IEIa to the start of RFC 822 Body; 'Length Indicator' (for septets) is shown below that, spanning the same range; and 'Number of Septets' is indicated by a double-headed arrow within the RFC 822 Header field. + +Diagram showing the layout of the IED for GSM 7 bit default alphabet data. It includes fields like UDL, UDHL, IEIa, IEIx, IEIDLx, IEDx, IEDn, Fill bits, RFC 822 Header, and RFC 822 Body. Annotations indicate 'Octet', 'SM (7bit data)', 'Number of Septets', 'Length Indicator', 'Total number of Octets', and 'Total number of Septets'. + +Figure 9.2.3.24.11 (a) + +The diagram below shows the layout of the IED for 8 bit data. + +![Diagram of IED layout for 8-bit data showing fields UDL, UDHL, IEla, IEIx, IEIDLx, IEDx, IEDn, RFC 822 Header, and RFC 822 Body with length indicators and octet counts.](184d3d9a856c77aae93652f4fe30f752_img.jpg) + +The diagram illustrates the layout of the IED for 8-bit data. It consists of a sequence of octets: UDL, UDHL, IEla, ..., IEIx (value = 20), IEIDLx (value = 01), IEDx, ..., IEDn, followed by an RFC 822 Header and an RFC 822 Body. The RFC 822 Header and Body are collectively labeled as 'SM (8 bit data)'. Several length indicators and total counts are shown with arrows: + + +- An arrow labeled 'Octet' points to the IEIDLx field. +- A 'Length Indicator' arrow spans from the start of the IEla field to the start of the IEDn field. +- A 'Total number of Octets' arrow spans from the start of the IEla field to the start of the RFC 822 Header. +- Another 'Length Indicator' arrow spans from the start of the UDHL field to the start of the IEDn field. +- A 'Total number of Octets' arrow spans from the start of the UDHL field to the start of the RFC 822 Body. +- A final 'Length Indicator' arrow spans from the start of the UDL field to the start of the IEDn field. +- Inside the RFC 822 Header, a 'Number of Octets' arrow spans from its start to the start of the RFC 822 Body. +- Inside the RFC 822 Header, a 'Length Indicator' arrow spans from its start to the start of the RFC 822 Body. + +Diagram of IED layout for 8-bit data showing fields UDL, UDHL, IEla, IEIx, IEIDLx, IEDx, IEDn, RFC 822 Header, and RFC 822 Body with length indicators and octet counts. + +**Figure 9.2.3.24.11 (b)** + +The diagram below shows the layout of the IED for UCS2 data. + +![Diagram of IED layout for UCS2 data showing fields UDL, UDHL, IEla, IEIx, IEIDLx, IEDx, IEDn, RFC 822 Header, and RFC 822 Body with length indicators and octet counts.](df935fc9efbd024af4ba77e46bb0bb19_img.jpg) + +The diagram illustrates the layout of the IED for UCS2 data. It consists of a sequence of octets: UDL, UDHL, IEla, ..., IEIx (value = 20), IEIDLx (value = 01), IEDx, ..., IEDn, followed by an RFC 822 Header and an RFC 822 Body. The RFC 822 Header and Body are collectively labeled as 'SM (UCS2 characters)'. Several length indicators and total counts are shown with arrows: + + +- An arrow labeled 'Octet' points to the IEIDLx field. +- A 'Length Indicator' arrow spans from the start of the IEla field to the start of the IEDn field. +- A 'Total number of Octets' arrow spans from the start of the IEla field to the start of the RFC 822 Header. +- Another 'Length Indicator' arrow spans from the start of the UDHL field to the start of the IEDn field. +- A 'Total number of Octets' arrow spans from the start of the UDHL field to the start of the RFC 822 Body. +- A final 'Length Indicator' arrow spans from the start of the UDL field to the start of the IEDn field. +- Inside the RFC 822 Header, a 'Number of UCS2 characters' arrow spans from its start to the start of the RFC 822 Body. +- Inside the RFC 822 Header, a 'Length Indicator' arrow spans from its start to the start of the RFC 822 Body. + +Diagram of IED layout for UCS2 data showing fields UDL, UDHL, IEla, IEIx, IEIDLx, IEDx, IEDn, RFC 822 Header, and RFC 822 Body with length indicators and octet counts. + +**Figure 9.2.3.24.11 (c)** + +#### 9.2.3.24.12 Hyperlink format element + +A hyperlink format element shall be structured as follows: + +Octet 1 and 2 Absolute Element Position (integer representation). + +The Absolute Element Position indicates the absolute character position within the message text. The absolute character position relates to the entire text within the concatenated message, the first character is numbered character 1. + +Octet 3 Hyperlink Title length: an integer representation of the number of characters in the hyperlink title. + +Octet 4 URL length: an integer representation of the number of characters in the URL. + +A space character shall be inserted between the hyperlink title and the URL. The hyperlink title can be a mixture of text, animations and pictures. Elements (text, animations and pictures) for which the position is included in the range [Absolute hyperlink position...Absolute hyperlink position+hyperlink title length] are part of the hyperlink title. The string of text in the range [Absolute hyperlink position+hyperlink title length+1...Absolute hyperlink position+hyperlink title length+1+URL length] is to be interpreted as a URL. + +#### 9.2.3.24.13 Enhanced Voice Mail Information + +Enhanced Voice Mail Information allows a Voice Mail system to convey to a mobile subscriber, comprehensive information regarding individual voice mail messages and mailbox status. + +Enhanced Voice Mail Information has two types of Information Element Data + +- Enhanced Voice Mail Notification which conveys to the MS information regarding newly deposited Voice Mail messages and Voice Mailbox Status +- Enhanced Voice Mail Delete Confirmation which allows an MS to maintain Voice mailbox status information synchronisation between the MS and the Voice Mailbox in the event of Voice Mail Message deletion. + +The first 'bit' of the Enhanced Voice Mail Information Element Data is known as Enhanced Voice Mail PDU Type and discriminates between whether the Enhanced Voice Mail Information PDU is an Enhanced Voice Mail Notification or an Enhanced Voice Mail Delete Confirmation. + +##### 9.2.3.24.13.1 Enhanced Voice Mail Notification + +The Enhanced Voice Mail Notification Information Element Data has the following format where the parameters are in strict order following the IEDL. The Enhanced Voice Mail Notification IEI and its associated IEDL and IED shall be complete within a single UDHL. + +In the event of a contradiction between Enhanced Voice Mail Notification and either the DCS (23.038) [9] indicating Voicemail Message Waiting or the Special SMS Message Indication (9.2.3.24.2) indicating Voice Message Waiting or both then the Enhanced Voice Mail Notification specified here shall take precedence. + +| Parameter | Parameter Length | Mandatory/
Optional/Conditional | +|-----------------------------------------------|-----------------------------|------------------------------------| +| ENHANCED_VOICE_MAIL_PDU_TYPE | Bit 0 Octet 1 | M | +| RESERVED_FOR_FUTURE_USE | Bit 1 Octet 1 | M | +| MULTIPLE_SUBSCRIBER_PROFILE | Bits 2..3 Octet 1 | M | +| SM_STORAGE | Bit 4 Octet 1 | M | +| VM_MAILBOX_ALMOST_FULL | Bit 5 Octet 1 | M | +| VM_MAILBOX_FULL | Bit 6 Octet 1 | M | +| VM_MAILBOX_STATUS_EXTENSION_INDICATOR | Bit 7 Octet 1 | M | +| VM_MAILBOX_ACCESS_ADDRESS | Octets 2.. n+2 (NOTE 2) | M | +| NUMBER_OF_VOICE_MESSAGES | Bits 0..7 Octet n+3 | M | +| NUMBER_OF_VM_NOTIFICATIONS | Bits 0..4 Octet n+4 | M | +| RESERVED_FOR_FUTURE_USE | Bits 5..7 Octet n+4 | M | +| VM_MAILBOX_STATUS_EXTENSION_LENGTH | 1 Octet (NOTE 3) | C | +| VM_MAILBOX_STATUS_EXTENSION_DATA | 1 or more Octets (NOTE 3) | C | +| VM_MESSAGE_ID (NOTE 1) | Bits 0..15 Octets n+5..n+6 | M | +| VM_MESSAGE_LENGTH (NOTE 1) | Bits 0..7 Octet n+7 | M | +| VM_MESSAGE_RETENTION_DAYS (NOTE 1) | Bits 0..4 Octet n+8 | M | +| RESERVED_FOR_FUTURE_USE (NOTE 1) | Bit 5 Octet n+8 | M | +| VM_MESSAGE_PRIORITY_INDICATION (NOTE 1) | Bit 6 Octet n+8 | M | +| OCTET_VM_MESSAGE_EXTENSION_INDICATOR (NOTE 1) | Bit 7 Octet n+8 | M | +| VM_MESSAGE_CALLING_LINE_IDENTITY (NOTE 1) | Octets n+9.. n+9+m (NOTE 2) | M | +| VM_MESSAGE_EXTENSION_LENGTH (NOTE 1) | 1 Octet (NOTE 3) | C | +| VM_MESSAGE_EXTENSION_DATA (NOTE 1) | 1 or more Octets (NOTE 3) | C | + +NOTE 1: This sequence of parameters are repeated a number of times according to the number of Voice Mail notifications conveyed in this IE. + +NOTE 2: 'n' and 'm' denote the number of octets required for the VM\_MAILBOX\_ACCESS\_ADDRESS and the VM\_CALLING\_LINE\_IDENTITY as appropriate including the Address-Length, Type-of-address and Address-value (see 9.1.2.5). + +NOTE 3: The Conditional Octets are excluded from the Octet count in the table in this release because no extensions are defined in this release. + +| | | +|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ENHANCED_VOICE_MAIL_PDU_TYPE | This parameter shall be set to 0 to specify that the following Information Element Data Parameters is an Enhanced Voice Mail Notification. | +| RESERVED_FOR_FUTURE_USE | This parameter is set to 0 and is reserved for future use. | +| MULTIPLE_SUBSCRIBER_PROFILE | This parameter shall indicate the Multiple Subscriber Profile (see 3GPP TS 23.097 [41]):
00 profile ID 1
10 profile ID 2
01 profile ID 3
11 profile ID 4 | +| SM_STORAGE | This parameter shall be set to 0 to indicate that this SM shall be discarded after evaluating its contents; otherwise it shall be set to a 1 to indicate to the MS that this SM shall be stored in the ME or the USIM. | +| VM_MAILBOX_ALMOST_FULL | This parameter shall be set to 1 if the Voice Mailbox in the Voice Mail system is almost full; otherwise this field shall be set to 0. The point at which the voice mailbox is considered almost full is Voice Mail System specific. | +| VM_MAILBOX_FULL | This parameter shall be set to 1 if the Voice Mailbox in the Voice Mail system is full; otherwise this field shall be set to 0. | +| VM_MAILBOX_STATUS_EXTENSION_INDICATOR | In this release, this parameter shall be set to 0. This parameter shall be set to 1 to indicate that a VM_MAILBOX_STATUS_EXTENSION_LENGTH parameter is present in this PDU. | +| VM_MAILBOX_ACCESS_ADDRESS | This parameter shall contain the Voice Mailbox number. It shall be coded according to section 9.1.2.5. In case of contradiction between this parameter and the Mailbox Dialing Numbers stored on (U)SIM this parameter shall take precedence and the MS may try to update EF MBDN on (U)SIM. | +| NUMBER_OF_VOICE_MESSAGES | This octet shall contain a value in the range 0 to 255 indicating the current number of Voice Mail messages that are unread. The value 255 shall be taken to mean 255 or greater. The NUMBER_OF_VOICE_MESSAGES shall be stored on the (U)SIM in accordance with the procedure for storage of Message Waiting Indication Status described in Special SMS Message Indication (9.2.3.24.2). | +| NUMBER_OF_VM_NOTIFICATIONS | This parameter has a range 0 to 15. This parameter shall indicate the number of specific Voice Message notifications to follow within this IE. | +| RESERVED_FOR_FUTURE_USE | This parameter shall be set to 0 and is reserved for future use. | +| VM_MAILBOX_STATUS_EXTENSION_LENGTH | This parameter shall be set to the number of additional octets that immediately follow. This parameter has a value in the range 0 to 255. The presence of this parameter is conditional on the setting of VM_MAILBOX_STATUS_EXTENSION_INDICATOR in this PDU. | + +**VM\_MAILBOX\_STATUS\_EXTENSION\_DATA** This parameter comprises a number of additional octets allowing additional VM mailbox generic status parameters to be conveyed in this PDU. Additional octets are not defined in this release but may be defined later by 3GPP. This parameter is conditional on the presence of **VM\_MAILBOX\_EXTENSION\_LENGTH** + +**VM\_MESSAGE\_ID** This parameter shall be set to the message ID of the Voice Mail message in this specific Voice Message notification. This parameter is binary and has a range 0 to 65535, modulus 65536. It is the responsibility of the Voice Mail system to set this parameter to uniquely identify a Voice Mail message within the modulus. + +**VM\_MESSAGE\_LENGTH** This parameter shall be set to the length of the Voice Mail message in this notification in seconds. This parameter has a range 0 to 255. For voice mail messages that are longer than 255 seconds, this parameter shall be set to its maximum 255. + +**VM\_MESSAGE\_RETENTION\_DAYS** This parameter shall be set to the number of days after which the specific Voice Mail message in this notification is anticipated to be automatically deleted from the Voice Mail system timed from the GSM Timestamp (TP-SCTS 9.2.3.11) for this Enhanced Voice Mail Notification. This parameter has a range 0 to 31. For Voice Mail messages that have a longer retention time than 31 days, this parameter shall be set to its maximum 31. + +**NOTE:** The GSM Timestamp is the time that the SC received the SM from the Voice Mail system which is not necessarily the time that the voice message was deposited into the Voice Mail system. + +**RESERVED\_FOR\_FUTURE\_USE** This parameter is set to 0 and is reserved for future use. + +**VM\_MESSAGE\_PRIORITY\_INDICATION** This parameter shall be set to 1 to indicate that the specific Voice Mail message in this notification held in the Voice Mailbox is urgent; otherwise the parameter shall be set to 0. + +**VM\_MESSAGE\_EXTENSION\_INDICATOR** In this release, this parameter shall be set to 0. This parameter shall be set to a 1 to indicate that a **VM\_MESSAGE\_EXTENSION\_LENGTH** parameter is present in this PDU. + +**VM\_MESSAGE\_CALLING\_LINE\_IDENTITY** This parameter shall contain the address to be used by the mobile subscriber to contact the originator of the specific Voice Mail message in this notification. Where the CLI is not available then the coding of this parameter shall indicate that there is no address. i.e The length indicator in this parameter shall be set to 0. + +This parameter coding shall comply with the the SM-TL address format specified in 9.1.2.5 above. + +**VM\_MESSAGE\_EXTENSION\_LENGTH** This parameter shall be set to the number of additional octets that immediately follow. This parameter has a value in the range 0 to 255. The presence of this parameter is conditional on the setting of **VM\_MESSAGE\_EXTENSION\_INDICATOR** in this PDU. + +**VM\_MESSAGE\_EXTENSION\_DATA** This parameter comprises a number of additional octets allowing additional voicemail message specific parameters to be conveyed in this PDU. Additional octets are not defined in this release but may be + +defined later by 3GPP. This parameter is conditional on the presence of VM\_MESSAGE\_EXTENSION\_LENGTH. + +#### 9.2.3.24.13.2 Enhanced Voice Mail Delete Confirmation + +The Enhanced Voice Mail Delete Confirmation Information Element Data contains synchronization information. A Voice Mail system may send an Enhanced Voice Mail Delete Confirmation in order to indicate to the ME that certain voice mail messages that have been deleted and to indicate the updated status of the Voice Mailbox. + +The Enhanced Voice Mail Delete Confirmation Information Element Data has the following format where the parameters are in strict order following the IEDL. The Enhanced Voice Mail Delete Confirmation IEI and its associated IEDL and IED shall be complete within a single UDH. + +| Parameter | Parameter Length | Mandatory/
Conditional/Optional | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------| +| ENHANCED_VOICE_MAIL_PDU_TYPE | Bit 0 Octet 1 | M | +| RESERVED_FOR_FUTURE_USE | Bit 1 Octet 1 | M | +| MULTIPLE_SUBSCRIBER_PROFILE | Bits 3..2 Octet 1 | M | +| SM_STORAGE | Bit 4 Octet 1 | M | +| VM_MAILBOX_ALMOST_FULL | Bit 5 Octet 1 | M | +| VM_MAILBOX_FULL | Bit 6 Octet 1 | M | +| VM_MAILBOX_STATUS_EXTENSION_INDICATOR | Bit 7 Octet 1 | M | +| VM_MAILBOX_ACCESS_ADDRESS | Octets 2..n+2 (NOTE 2) | M | +| NUMBER_OF_VOICE_MESSAGES | Bits 0..7 Octet n+3 | M | +| NUMBER_OF_VM_DELETES | Bits 0..4 Octet n+4 | M | +| RESERVED_FOR_FUTURE_USE | Bits 5..7 Octet n+4 | M | +| VM_MAILBOX_STATUS_EXTENSION_LENGTH | 1 Octet (NOTE 3) | C | +| VM_MAILBOX_STATUS_EXTENSION_DATA | 1 or more Octets (NOTE 3) | C | +| VM_MESSAGE_ID (NOTE 1) | Octets n+5..n+6 | M | +| RESERVED_FOR_FUTURE_USE (NOTE 1) | Bits 0..6 Octet n+7 | M | +| VM_MESSAGE_EXTENSION_INDICATOR (NOTE 1) | Bit 7 Octet n+7 | M | +| VM_MESSAGE_EXTENSION_LENGTH (NOTE 1) | 1 Octet (NOTE 3) | C | +| VM_MESSAGE_EXTENSION_DATA (NOTE 1) | 1 or more Octets (NOTE 3) | C | +| NOTE 1: This sequence of parameters are repeated a number of times according to the number of Voice Mail Delete Confirmations conveyed in this IE. | | | +| NOTE 2: 'n' denotes the number of octets required for the VM_MAILBOX_ACCESS_ADDRESS including the Address-Length, Type-of-address and Address-value (see 9.1.2.5). | | | +| NOTE 3: The Conditional Octets are excluded from the Octet count in the table in this release because no extensions are defined in this release. | | | + +ENHANCED\_VOICE\_MAIL\_PDU\_TYPE This parameter shall be set to 1 to specify that the following Information Element Data is an Enhanced Voice Mail Delete Confirmation. + +RESERVED\_FOR\_FUTURE\_USE This parameter is set to 0 and is reserved for future use. + +| | | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MULTIPLE_SUBSCRIBER_PROFILE | See clause 9.2.3.24.13.1 | +| SM_STORAGE | See clause 9.2.3.24.13.1 | +| VM_MAILBOX_ALMOST_FULL | See clause 9.2.3.24.13.1 | +| VM_MAILBOX_FULL | See clause 9.2.3.24.13.1 | +| VM_MAILBOX_STATUS_EXTENSION_INDICATOR | In this release, this parameter shall be set to 0. This parameter shall be set to 1 to indicate that a VM_MAILBOX_STATUS_EXTENSION_LENGTH parameter is present in this PDU. | +| VM_MAILBOX_ACCESS_ADDRESS | See clause 9.2.3.24.13.1 | +| NUMBER_OF_VOICE_MESSAGES | See clause 9.2.3.24.13.1 | +| NUMBER_OF_VM_DELETES | This parameter has a range 0 to 63. This parameter shall indicate the number of VM_MESSAGE_ID's that follow in this IE | +| RESERVED_FOR_FUTURE_USE | This parameter is set to 0 and is reserved for future use. | +| VM_MAILBOX_STATUS_EXTENSION_LENGTH | This parameter shall be set to the number of additional octets that immediately follow. This parameter has a value in the range 0 to 255. The presence of this parameter is conditional on the setting of VM_MAILBOX_STATUS_EXTENSION_INDICATOR in this PDU. | +| VM_MAILBOX_STATUS_EXTENSION_DATA | This parameter comprises a number of additional octets allowing additional VM mailbox generic status parameters to be conveyed in the PDU. Additional octets are not defined in this release but may be defined later by 3GPP. This parameter is conditional on the presence of VM_MAILBOX_EXTENSION_LENGTH | +| VM_MESSAGE_ID | This parameter shall be set to the message ID of the specific voice mail message(s) whose deletion is being confirmed. The range of this parameter is defined in clause 9.2.3.24.13.1 and for a specific voice mail message the value of this parameter shall be identical to that used for the VM Notification. This parameter is repeated according to the number of voice mail message deletions being confirmed. | +| RESERVED_FOR_FUTURE_USE | This parameter is set to 0 and is reserved for future use. This parameter is repeated according to the number of voice mail message deletions being confirmed. | +| VM_MESSAGE_EXTENSION_INDICATOR | In this release, this parameter shall be set to 0. This parameter shall be set to a 1 to indicate that a VM_MESSAGE_EXTENSION_LENGTH parameter is present in this PDU. | +| VM_MESSAGE_EXTENSION_LENGTH | This parameter shall be set to the number of additional octets that immediately follow. This parameter has a value in the range 0 to 255. The presence of this parameter is conditional on the setting of VM_MESSAGE_EXTENSION_INDICATOR in this PDU | +| VM_MESSAGE_EXTENSION_DATA | This parameter comprises a number of additional octets allowing additional voicemail message specific parameters to be conveyed in this PDU. Additional octets are not defined in this release but may be defined later by 3GPP. This parameter is conditional on the presence of VM_MESSAGE_EXTENSION_LENGTH | + +##### 9.2.3.24.14 Identification of a directory number within the User Data Field + +A directory number may, as an optional feature, be identified within the User Data Field. + +This allows, for example, a receiving entity to automatically identify a string of digits in the User Data Field as being a telephone number in order to facilitate easy call back by user action. + +This shall be implemented by enclosing the directory number in inverted commas (character 0100010 from the 7 bit default alphabet in 3GPP TS 23.038 [9] or its equivalent in other character sets). + +Unspecified address formats or International address formats (using + symbol) may be used for the directory number. + +Spaces may be included with the directory number inside the inverted commas. E.g. “+1 234 567 8901” + +The User Data Field displayed to the recipient may contain more than one directory number, in which case it is for the user to select the one required. + +##### 9.2.3.24.15 National Language Single Shift + +This information element is used to indicate which National Language Single Shift Table is used instead of the GSM 7 bit default alphabet extension table specified in 3GPP TS 23.038 [9]. + +The total length of the IE is 1 octet: + +octet 1 National Language Identifier. + +The National Language Identifier values and Language tables are defined in 3GPP TS 23.038 [9]. + +A receiving entity shall ignore (i.e. skip over and commence processing at the next information element) this information element if the value of the National Language Identifier is not described in 3GPP TS 23.038 [9]. + +If this IE is duplicated within different segments of a concatenated message then a receiving entity shall process each segment individually. + +If this IE is not included within a segment of a concatenated message then the receiving entity shall use the GSM 7 bit default alphabet extension table for this segment. + +In the event that this IE is duplicated within one segment of a concatenated message or a single message then a receiving entity shall use the last occurrence of the IE. + +In the event that this IE is received within a single message or a segment of a concatenated message, in which the DCS has indicated UCS-2 encoding, then the receiving entity shall ignore this IE. + +##### 9.2.3.24.16 National Language Locking Shift + +This information element is used to indicate which National Language Locking Shift Table is used instead of the GSM 7 bit default alphabet specified in 3GPP TS 23.038 [9]. + +This IE is coded in the same way as the National Language Single Shift IE in subclause 9.2.3.24.15. + +A receiving entity shall ignore (i.e. skip over and commence processing at the next information element) this information element if the value of the National Language Identifier is not described in 3GPP TS 23.038 [9]. + +If this IE is duplicated within different segments of a concatenated message then a receiving entity shall process each segment individually. + +If this IE is not included within a segment of a concatenated message then the receiving entity shall use the GSM 7 bit default alphabet table for this segment. + +In the event that this IE is duplicated within one segment of a concatenated message or a single message then a receiving entity shall use the last occurrence of the IE. + +In the event that this IE is received within a single message or a segment of a concatenated message, in which the DCS has indicated UCS-2 encoding, then the receiving entity shall ignore this IE. + +#### 9.2.3.25 TP-Reject-Duplicates (TP-RD) + +The TP-Reject-Duplicates is a 1 bit field located within bit 2 of the first octet of SMS-SUBMIT and has the following values. + +- | | | | +|------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bit no. 2: | 0 | Instruct the SC to accept an SMS-SUBMIT for an SM still held in the SC which has the same TP-MR and the same TP-DA as a previously submitted SM from the same OA. | +| | 1 | Instruct the SC to reject an SMS-SUBMIT for an SM still held in the SC which has the same TP-MR and the same TP-DA as the previously submitted SM from the same OA. In this case the response returned by the SC is as specified in 9.2.3.6.. | + +#### 9.2.3.26 TP-Status-Report-Qualifier (TP-SRQ) + +The TP-Status-Report-Qualifier is a 1 bit field located within bit 5 of the first octet of SMS-STATUS-REPORT and has the following values + +- | | | | +|------------|---|------------------------------------------------------------------------| +| Bit no. 5: | 0 | The SMS-STATUS-REPORT is the result of a SMS-SUBMIT. | +| | 1 | The SMS-STATUS-REPORT is the result of an SMS-COMMAND e.g. an Enquiry. | + +#### 9.2.3.27 TP-Parameter-Indicator (TP-PI) + +The TP-Parameter-Indicator comprises a number of octets between 1 and n where each bit when set to a 1 indicates that a particular optional parameter is present in the fields which follow. The TP-PI is present as part of the RP-User-Data in the RP-ACK or the RP-ERROR as indicated in clauses 9.2.2.1a and 9.2.2.2a or the RP-DATA as indicated in clause 9.2.2.3. + +The structure of the TP-PI is as follows: + +Octet 1: + +| bit 7 | bit 6 | bit 5 | bit 4 | bit 3 | bit 2 | bit 1 | bit 0 | +|---------------|----------|----------|----------|----------|--------|--------|--------| +| Extension bit | Reserved | Reserved | Reserved | Reserved | TP-UDL | TP-DCS | TP-PID | + +The most significant bit in octet 1 and any other TP-PI octets which may be added later is reserved as an extension bit which when set to a 1 shall indicate that another TP-PI octet follows immediately afterwards. + +If the TP-UDL bit is set to zero then by definition neither the TP-UDL field or the TP-UD field can be present. If the TP-UDL bit is set to "1" but the TP-DCS bit is set to "0" then the receiving entity shall for TP-DCS assume a value of 0x00, i.e. the 7bit default alphabet. + +If a Reserved bit is set to "1" then the receiving entity shall ignore the setting. The setting of this bit shall mean that additional information will follow the TP-User-Data, so a receiving entity shall discard any octets following the TP-User-Data. + +#### 9.2.3.28 TP-Loop-Prevention (TP-LP) + +The TP-Loop-Prevention is a 1-bit field, located within bit no 3 of the first octet of the SMS-Deliver and SMS-Status-Report, and to be given the values in the table below. + +In the following description, a 'spawned' message refers to an application-generated message (e.g. an auto-reply or a copy to a second subscription) generated in response to a received SMS-Deliver or SMS-Status-Report. In order to prevent message loops, only a single off-net forwarding operation shall be permitted on any SMS-Deliver or SMS-Status-Report, and a spawned message shall not spawn a further message. To achieve this, spawned messages and forwarded messages (but not the original message) shall be marked using the TP-LP bit so that further spawning or further off-net forwarding of these messages is inhibited. + +A network entity (e.g. an SC) that generates or transports SMS-Deliver or SMS-Status-Report shall set this bit in the forwarded message when forwarding to a destination other than that specified in the received SMS-Deliver or SMS-Status-Report. + +A network entity (e.g. an SC) that implements SMS forwarding shall inhibit off-net forwarding of SMS-Deliver or SMS-Status-Report if this bit is already set in the SMS-Deliver or SMS-Status-Report received from another network. + +If an implementation does not prevent on-net message looping by other means, a network entity (e.g. an SC) that implements SMS forwarding may inhibit on-net forwarding of SMS-Deliver or SMS-Status-Report if this bit is already set in the received SMS-Deliver or SMS-Status-Report. + +A network entity (e.g. an SC) that spawns an additional message from a received SMS-Deliver or SMS-Status-Report shall set the TP-LP bit in the spawned message. + +A network entity (e.g. an SC) shall inhibit generation of a spawned message if this bit is already set in the received SMS-Deliver or SMS-Status-Report from which the spawned message would otherwise be generated. + +| TP-LP Value | Description | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | The message has not been forwarded and is not a spawned message (or the sending network entity (e.g. an SC) does not support the setting of this bit.) | +| 1 | The message has either been forwarded or is a spawned message. | + +## 9.3 Service provided by the SM-RL + +### 9.3.1 General + +The Short Message Relay Layer (SM-RL) provides a service to the Short Message Transfer Layer (SM-TL). This service enables the SM-TL to send Transfer Protocol Data Units (TPDUs) to its peer entity, receive TPDUs from its peer entity and receive reports about earlier requests for TPDUs to be transferred. + +In order to keep track of TPDUs and reports about those TPDUs, primitives between the SM-TL and SM-RL contain a Short Message Identifier (SMI), which is a reference number for the TPDU associated with the primitive. This Short Message Identifier is not carried via the SM-RL protocol of clause 9.3.2. It is carried via the relay layer service between the SC and GMSC. It is also carried by SM-RL of 3GPP TS 24.011 [13], between the visited MSC and MS. The parameter is not carried by MAP but is mapped to and from the TCAP dialogue Identifier (see CCITT Recommendation Q.771, "Blue Book" [19]) at the GMSC and the visited MSC (therefore the Message Identifier at the SC/GMSC interface is not the same as at the visited MSC/MS interface). + +The SM-RL communicates with its peer entity by the protocol described in the following clauses. + +### 9.3.2 Protocol element repertoire at SM-RL + +Different protocols are required between different pairs of SM-RL entities. Those are described in other GSM/UMTS specifications. This clause gives a survey of the different information elements which have to be conveyed between those entities. (Note that the notation of the protocol and information elements may vary between different GSM/UMTS specifications). + +The SM-RL comprises the following 6 protocol elements: + +| | | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| RP-MO-DATA | for transferring a TPDU from MS to SC | +| RP-MT-DATA | for transferring a TPDU from SC to MS | +| RP-ACK | for acknowledging an RP-MO-DATA, an RP-MT-DATA or an RP-SM-MEMORY-AVAILABLE | +| RP-ERROR | for informing of an unsuccessful RP-MO-DATA or an RP-MT-DATA transfer attempt | +| RP-ALERT-SC | for alerting the SC that the MS has recovered operation (information sent from the HLR to the SC) | +| RP-SM-MEMORY-AVAILABLE | for notifying the network that the MS has memory available to accept one or more short messages (information sent from the MS to the HLR) | + +#### 9.3.2.1 RP-MO-DATA + +Basic elements of the RP-MO-DATA type. + +| Abbr. | Reference | p1) | Description | +|-------|------------------------|-----|--------------------------------| +| RP-OA | RP-Originating-Address | ++- | Address of the originating MS. | +| RP-DA | RP-Destination-Address | -++ | Address of the destination SC. | +| RP-UD | RP-User-Data | +++ | Parameter containing the TPDU | + +- 1) Provision on the links SC<->MSC, MSC<->MSC or MSC<->SGSN, and MSC<->MS or SGSN<->MS indicated by "xxx", where x may be either "+" or "-", dependent on whether the parameter is mandatory or not on the respective link. + +#### 9.3.2.2 RP-MT-DATA + +Basic elements of the RP-MT-DATA type. + +| Abbr. | Reference | p1) | Description | +|---------|----------------------------|-----|------------------------------------------------------------------------------------------------------------------------------------------------| +| RP-PRI | RP-Priority-Request | +-- | Parameter indicating whether or not the short message transfer should be stopped if the originator SC address is already contained in the MWD. | +| RP-MMS | RP-More-Messages-To-Send | OO- | Parameter indicating that there are more messages waiting in the SC | +| RP-OA | RP-Originating-Address | +++ | Address of the originating SC. | +| RP-DA | RP-Destination-Address | ++- | Address of the destination MS. | +| RP-UD | RP-User-Data | +++ | Parameter containing the TPDU | +| RP-MTI | RP-Message Type Indicator | O-- | Parameter indicating if the TPDU is a SMS Deliver or a SMS Status Report 2) | +| RP-SMEA | RP-originating SME-Address | O-- | Address of the originating SME 2) | + +- 1) Provision on the links SC<->MSC, MSC<->MSC or MSC<->SGSN, and MSC<->MS or SGSN<->MS indicated by "xxx", where x may be "+", "-" or "O", dependent on whether the parameter is mandatory, not present or optional on the respective link. +- 2) These information elements may be included in the "Send Routing Information for SM" sent by the SMS-GMSC to the HLR. + +When transmitted, the RP-SMEA shall take the TP-OA value. + +When transmitted, the RP-MTI shall be given the following values: + +- | | | +|---|--------------------| +| 0 | SMS Deliver. | +| 1 | SMS Status Report. | + +This may be used by the HLR to distinguish the two cases in order not to apply any filtering mechanism based on the RP-SMEA value in case of a SMS-Status Report transmission. + +#### 9.3.2.3 RP-ACK + +The RP-ACK contains the RP-User-Data which is a parameter containing the TPDU (see subclauses 9.2.2.1a and 9.2.2.2a). + +#### 9.3.2.4 RP-ERROR + +Basic elements of the RP-ERROR type. + +| Abbr. | Reference | p1) | Description | +|-----------|----------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RP-MSI | RP-MW-Set-Indication | +-- | Parameter indicating whether or not the MWI has been up-dated. 2) | +| RP-CS | RP-Cause | +++ | Parameter identifying the error type. The RP-Cause parameter gives the reason why a short message transfer attempt fails. In practice three relay layer protocols are used - SC to GMSC/IWMSC (see Annex A), MAP (see 3GPP TS 29.002 [15]) and via the radio interface (see 3GPP TS 24.011 [13]) | +| RP-MSIsdn | RP-international--MS-ISDN-number | +-- | MSIsdn-Alert or IMSI-Alert of the MS, see clause 3.2.7 3) | +| RP-UD | RP-User-Data | OO O | Parameter containing a TPDU | + +- 1) Provision on the links SC<->MSC, MSC<->MSC or MSC<->SGSN, and MSC<->MS or SGSN<->MS indicated by "xxx", where x may be "+", "-" or "O" dependent on whether the parameter is mandatory, not present or optional on the respective link. +- 2) Only present when the RP-ERROR is transferred from the SMS-GMSC to the SC. +- 3) Only present when the RP-MT-DATA transfer attempt failed because the MS is not reachable or because the MS memory capacity was exceeded and the MSIsdn-Alert or IMSI-Alert is different from the MSIsdn or IMSI used by the SC to address the recipient MS. + +#### 9.3.2.5 RP-ALERT-SC + +Basic elements of the RP-ALERT-SC type: + +| Abbr. | Reference | p1) | Description | +|-----------|---------------------------------------------|-----|-------------------| +| RP-MSIsdn | RP-International-MS-ISDN-Number | O | MSIsdn of the MS. | +| RP-IMSI | RP-International-Mobile-Subscriber-Identity | O | IMSI of the MS | + +- 1) Provision; Optional (O). +- 2) It is mandatory to include either RP-MSIsdn or RP-IMSI. + +#### 9.3.2.6 RP-SM-MEMORY-AVAILABLE + +Basic elements of the RP-SM-MEMORY-AVAILABLE type: + +| Abbr. | Reference | p1) | Description | +|---------|---------------------------------------------|-----|-----------------| +| RP-IMSI | RP-International-Mobile-Subscriber-Identity | ++- | IMSI of the MS. | + +- 1) Provision on the links HLR<->VLR or HLR<->SGSN, VLR<->MSC and MSC<->MS or SGSN<->MS indicated by "xxx", where x may be either "+" or "-", dependent on whether the parameter is mandatory or not present on the respective link. + +# --- 10 Fundamental procedures within SMS + +The procedures for providing SMS over a generic IP CAN is described in 3GPP TS 23.204 [42] (see subclause 6). + +The SMS comprises 3 fundamental procedures: + +- 1) Short message mobile terminated. This procedure consists of all necessary operations to: + - a) transfer a short message or status report from the SC to the MS; + - b) return a report to the SC, containing the result of the message transfer attempt. +- 2) Short message mobile originated. This procedure consists of all necessary operations to: + +- a) transfer a short message from the MS to the SC; + - b) return a report to the MS, containing the result of the message transfer attempt. +- 3) Transfer of an Alert. This procedure consists of all necessary operations for an HLR or a VLR to initiate a transfer of an Alert to a specific SC, informing the SC that the MS has recovered operation. + +3GPP TS 29.002 [15] defines operations necessary for the provision of the Short Message Service. The operations defined in clause 10 describe the requirement that the Short Message Service puts upon the network functionality. If discrepancies exist in nomenclature, it is the 3GPP TS 29.002 [15] that shall be the reference. + +Annex C indicates the flow of primitives and parameters during the short message transfer between the SC and the MS. Both the Mobile terminated and the Mobile originated cases are covered. + +## 10.1 Short message mobile terminated + +The entities involved in this procedure are depicted in figure 14. + +![Figure 14: Interfaces involved in the Short message mobile terminated procedure. The diagram shows a sequence of network entities: SC, SMS-GMSC, SMS Router, SGSN, MSC, MS, HLR, and VLR. The SC is connected to the SMS-GMSC via an interface marked with an 'X'. The SMS-GMSC is connected to the SMS Router. The SMS Router is connected to both the SGSN and the MSC. The SGSN and MSC are both connected to the MS. The HLR is connected to the SMS-GMSC and the SMS Router. The VLR is connected to the MSC.](9791722d75115ddcc599b07d7bc35d73_img.jpg) + +``` + +graph LR + SC[SC] -- X --- SMS-GMSC[SMS-GMSC] + SMS-GMSC --- SMS-Router[SMS Router] + SMS-Router --- SGSN[SGSN] + SMS-Router --- MSC[MSC] + SGSN --- MS[MS] + MSC --- MS + HLR[HLR] --- SMS-GMSC + HLR --- SMS-Router + MSC --- VLR[VLR] + +``` + +Figure 14: Interfaces involved in the Short message mobile terminated procedure. The diagram shows a sequence of network entities: SC, SMS-GMSC, SMS Router, SGSN, MSC, MS, HLR, and VLR. The SC is connected to the SMS-GMSC via an interface marked with an 'X'. The SMS-GMSC is connected to the SMS Router. The SMS Router is connected to both the SGSN and the MSC. The SGSN and MSC are both connected to the MS. The HLR is connected to the SMS-GMSC and the SMS Router. The VLR is connected to the MSC. + +NOTE 1: The SMS Router is an optional entity. If it is not present, the two interfaces extending from the right side of the SMS-GMSC extend directly to the SGSN and MSC, respectively. + +NOTE 2: Since the short message mobile terminated procedure covers the functionality required at SM-RL for transferring TPDU from SC to MS, the procedure described covers both short message (SMS-DELIVER) and status report (SMS-STATUS-REPORT) transfer. The term "short message transfer" therefore, in this clause, covers both cases. + +**Figure 14: Interfaces involved in the Short message mobile terminated procedure. GSM TS 43.002 [5]. X is the interface between an MSC and an SC as defined in clause 5** + +In figure 15, sequence diagrams are shown for the following basic situations of short message mobile terminated transfer attempt: + +- Successful short message transfer via the MSC or the SGSN; +- Successful short message transfer via the SMS Router, and the MSC or SGSN; +- Short message transfer attempt failing due to error at the SMS-GMSC; +- Short message transfer attempt failing due to negative outcome of HLR information retrieval; +- Short message transfer attempt via the SMS Router failing due to negative outcome of HLR information retrieval; +- Short message transfer attempt failing due to error at the MSC or SGSN; +- Short message transfer attempt failing due to negative outcome of VLR information retrieval; +- Short message transfer attempt failing due to erroneous message transfer on the radio path; +- Short message transfer attempt failing over the first path (e.g. SGSN) and succeeding over the second path (e.g. MSC); +- Short message transfer attempt via the SMS Router failing over the first path (e.g. SGSN) and succeeding over the second path (e.g. MSC); + +- Short message transfer attempt failing over the first path (e.g. SGSN) and over the second path (e.g. MSC). + +References to the relevant specifications of the different operations are given in clause 4. + +![Sequence diagram showing successful short message transfer via MSC or SGSN. Lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, MS. The process involves message transfer, routing info exchange, forwarding, delivery reports, and final delivery to the MS.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +``` +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + Note right of SC: Error! No text of specified style in + + SC->>SMS-GMSC: 1a. Message transfer + SMS-GMSC->>HLR: 2. SendRoutingInfo - ForShortMsg + SMS-GMSC->>MSC or SGSN: 4a. ForwardShortMessage + MSC or SGSN->>VLR: 5. sendInfoFor- 1) MT-SMS + MSC or SGSN->>MS: 6. Message transfer + MSC or SGSN->>SMS-GMSC: 4b. Delivery report + SMS-GMSC->>HLR: 3. SM-Delivery ReportStatus + SMS-GMSC->>SC: 1b. Delivery report +``` + +Sequence diagram showing successful short message transfer via MSC or SGSN. Lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, MS. The process involves message transfer, routing info exchange, forwarding, delivery reports, and final delivery to the MS. + +- Image: Double arrow icon + + Operation invocation or message transfer. +- Image: Double arrow with return icon + + Successful operation invocation or message transfer including report. + +NOTE 1): This operation is not used by the SGSN. + +**Figure 15a): Successful short message transfer attempt via the MSC or the SGSN** + +Error! No + +9 + +Error! No text of specified style in + +![Sequence diagram for a successful short message transfer attempt via the SMS Router, and the MSC or SGSN. Lifelines: SC, SMS-GMSC, HLR, SMS Router, MSC or SGSN, VLR, MS. The sequence involves routing information exchange, message forwarding, and delivery reports.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant SMS Router + participant MSC or SGSN + participant VLR + participant MS + + Note right of SC: 1a. Message Transfer + SC->>SMS-GMSC: 1a. Message Transfer + Note right of SMS-GMSC: 2a. SendRoutingInfo ForShortMsg + SMS-GMSC->>HLR: 2a. SendRoutingInfo ForShortMsg + Note right of HLR: 2. SendRoutingInfo ForShortMsg + HLR->>SMS Router: 2. SendRoutingInfo ForShortMsg + Note right of SMS Router: 2b. SendRoutingInfo ForShortMsg + SMS Router->>HLR: 2b. SendRoutingInfo ForShortMsg + Note right of HLR: 4a. ForwardShortMsg + HLR->>SMS Router: 4a. ForwardShortMsg + Note right of SMS Router: 4a. ForwardShortMsg + SMS Router->>MSC or SGSN: 4a. ForwardShortMsg + Note right of MSC or SGSN: 5. SendInfoFor MT-SMS + MSC or SGSN->>VLR: 5. SendInfoFor MT-SMS + Note right of VLR: 6. Message Transfer + VLR->>MS: 6. Message Transfer + Note right of MS: 4b. Delivery Report + MS->>MSC or SGSN: 4b. Delivery Report + Note right of MSC or SGSN: 4b. Delivery Report + MSC or SGSN->>SMS Router: 4b. Delivery Report + Note right of SMS Router: 3. SM-Delivery ReportStatus + SMS Router->>HLR: 3. SM-Delivery ReportStatus + Note right of HLR: 1b. Delivery Report + HLR->>SMS-GMSC: 1b. Delivery Report + Note right of SMS-GMSC: 1b. Delivery Report + SMS-GMSC->>SC: 1b. Delivery Report + +``` + +→ Operation invocation or message transfer + ← Successful operation invocation or message transfer including a report + +Sequence diagram for a successful short message transfer attempt via the SMS Router, and the MSC or SGSN. Lifelines: SC, SMS-GMSC, HLR, SMS Router, MSC or SGSN, VLR, MS. The sequence involves routing information exchange, message forwarding, and delivery reports. + +NOTE 1: Operation 5 is not used by the SGSN. + +**Figure 15aa): Successful short message transfer attempt via the SMS Router, and the MSC or SGSN** + +![Sequence diagram for a short message transfer attempt failing due to error at the SMS-GMSC. Lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, MS. The sequence shows an initial message transfer from SC to SMS-GMSC followed by a failure report from SMS-GMSC back to SC.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + Note right of SC: 1a. Message transfer + SC->>SMS-GMSC: 1a. Message transfer + Note right of SMS-GMSC: 1c. Failure report + SMS-GMSC-->>SC: 1c. Failure report + +``` + +-.-> Error report + → Operation invocation or message transfer + +Sequence diagram for a short message transfer attempt failing due to error at the SMS-GMSC. Lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, MS. The sequence shows an initial message transfer from SC to SMS-GMSC followed by a failure report from SMS-GMSC back to SC. + +**Figure 15b): Short message transfer attempt failing due to error at the SMS-GMSC** + +![Sequence diagram for Figure 15c showing a failed short message transfer from SC to MS via SMS-GMSC and HLR. The HLR returns a negative response to the SMS-GMSC, which then sends a failure report back to the SC.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + Note right of SC: Error! No text of specified style in + SC->>SMS-GMSC: 1a. Message transfer + SMS-GMSC->>HLR: 2. sendRoutingInfo ForShortMsg + HLR-->>SMS-GMSC: 7. InformSC + SMS-GMSC-->>SC: 1c. Failure report + +``` + +Legend: + +- Operation invocation or message transfer. +- .-> Error report +- <--> Unsuccessful operation invocation or message transfer including report + +Sequence diagram for Figure 15c showing a failed short message transfer from SC to MS via SMS-GMSC and HLR. The HLR returns a negative response to the SMS-GMSC, which then sends a failure report back to the SC. + +**Figure 15c): Short message transfer attempt failing due to negative outcome of HLR information retrieval** + +![Sequence diagram for Figure 15ca showing a failed short message transfer from SC to MS via SMS-GMSC, HLR, and SMS Router. The HLR returns a negative response to the SMS-GMSC via the SMS Router, which then sends a delivery report back to the SC.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant SMS Router + participant MSC or SGSN + participant VLR + participant MS + + SC->>SMS-GMSC: 1a. Message Transfer + SMS-GMSC->>HLR: 2a. SendRoutingInfo ForShortMsg + HLR->>SMS Router: 2a. SendRoutingInfo ForShortMsg + SMS Router-->>HLR: 2. SendRoutingInfo ForShortMsg + HLR->>SMS Router: 7. InformSC + SMS Router-->>SMS-GMSC: 2b. SendRoutingInfo ForShortMsg + SMS Router->>SMS-GMSC: 7. InformSC + SMS-GMSC-->>SC: 1c. Delivery Report + +``` + +Legend: + +- Operation invocation or message transfer +- <--> Successful operation invocation or message transfer including report +Error Report +- .-> Operation invocation or message transfer +- <--> Unsuccessful operation invocation or message transfer including report + +Sequence diagram for Figure 15ca showing a failed short message transfer from SC to MS via SMS-GMSC, HLR, and SMS Router. The HLR returns a negative response to the SMS-GMSC via the SMS Router, which then sends a delivery report back to the SC. + +**Figure 15ca) Short message transfer attempt via the SMS Router failing due to negative outcome of HLR information retrieval** + +![Sequence diagram showing a failed SMS transfer from SC to MS via SMS-GMSC, HLR, and MSC or SGSN. The sequence involves message transfer, routing info request, forward short message, failure report, and delivery report status updates.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + SC->>SMS-GMSC: 1a. Message transfer + SMS-GMSC->>HLR: 2. SendRoutingInfo + HLR->>SMS-GMSC: ForShortMsg + SMS-GMSC->>MSC or SGSN: 4a. ForwardShortMessage + MSC or SGSN-->>SMS-GMSC: 4c. Failure report + SMS-GMSC->>HLR: 3a. SM-Delivery + HLR->>SMS-GMSC: ReportStatus + SMS-GMSC-->>SC: 1c. Failure report + +``` + +⟶ Operation invocation or message transfer. + +⟷ Successful operation invocation or message transfer including report. + +⋯⟶ Error report + +⋯⟷ Unsuccessful operation invocation or message transfer including report. (or with missing confirmation) + +Sequence diagram showing a failed SMS transfer from SC to MS via SMS-GMSC, HLR, and MSC or SGSN. The sequence involves message transfer, routing info request, forward short message, failure report, and delivery report status updates. + +NOTE: If an SMS Router is present, the message flow in 15aa is used, except that a 4c Failure Report message is transparently transferred to the SMS-GMSC from the MSC or SGSN by the SMS Router instead of a 4b Delivery Report. + +**Figure 15d): Short message transfer attempt failing due to error at the MSC or SGSN** + +![Sequence diagram showing a failed SMS transfer attempt due to VLR info retrieval failure. The flow goes from SC to SMS-GMSC, then routing info is checked with HLR. The message is forwarded to MSC, which fails to get info from VLR. A failure report is then propagated back to the SC via the SMS-GMSC, and the HLR is updated with the delivery status. Solid single arrow Solid double arrow Dashed single arrow Dashed double arrow](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC + participant VLR + participant MS + + SC->>SMS-GMSC: 1a. Message transfer + SMS-GMSC->>HLR: 2. SendRoutingInfo- + HLR->>SMS-GMSC: ForShortMsg + SMS-GMSC->>MSC: 4a. ForwardShortMessage + MSC-->>VLR: 5. sendInfoFor- + VLR-->>MSC: MT-SMS + MSC-->>SMS-GMSC: 4c. Failure report + SMS-GMSC->>HLR: 3a. SM-Delivery + HLR->>SMS-GMSC: ReportStatus + SMS-GMSC-->>SC: 1c. Failure report + +``` + +- Operation invocation or message transfer. +- Successful operation invocation or message transfer including report. +- Error report +- Unsuccessful operation invocation or message transfer including report. (or with missing confirmation) + +Sequence diagram showing a failed SMS transfer attempt due to VLR info retrieval failure. The flow goes from SC to SMS-GMSC, then routing info is checked with HLR. The message is forwarded to MSC, which fails to get info from VLR. A failure report is then propagated back to the SC via the SMS-GMSC, and the HLR is updated with the delivery status. Solid single arrow Solid double arrow Dashed single arrow Dashed double arrow + +NOTE: If an SMS Router is present, the message flow in 15aa is used, except that a 4c Failure Report message is transparently transferred to the SMS-GMSC from the MSC or SGSN by the SMS Router instead of a 4b Delivery Report. + +**Figure 15e): Short message transfer attempt failing due to negative outcome of VLR information retrieval** + +![Right arrow Double-headed arrow Dashed right arrow Dashed double-headed arrow](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Sequence diagram illustrating a short message transfer attempt failing due to erroneous message transfer on the radio path. + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + SC->>SMS-GMSC: 1a. Message transfer + SMS-GMSC->>HLR: 2. SendRoutingInfo + HLR-->>SMS-GMSC: - ForShortMsg + SMS-GMSC->>MSC or SGSN: 4a. ForwardShortMessage + MSC or SGSN->>VLR: 5. sendInfoFor1) + VLR-->>MSC or SGSN: MT-SMS + MSC or SGSN->>MS: 6. Message transfer + MSC or SGSN-->>SMS-GMSC: 4c. Failure report + SMS-GMSC->>HLR: 3. SM-Delivery + HLR-->>SMS-GMSC: ReportStatus + SMS-GMSC-->>SC: 1c. Failure report + +``` + +Legend: + +- Operation invocation or message transfer. +- Successful operation invocation or message transfer including report. +- Error report +- Unsuccessful operation invocation or message transfer including report. (or with missing confirmation) + +Right arrow Double-headed arrow Dashed right arrow Dashed double-headed arrow + +NOTE 1: This operation is not used by the SGSN. + +NOTE 2: If an SMS Router is present, the message flow in 15aa is used, except that a 4c Failure Report message is transparently transferred to the SMS-GMSC from the MSC or SGSN by the SMS Router instead of a 4b Delivery Report. + +**Figure 15f): Short message transfer attempt failing due to erroneous message transfer on the radio path** + +![Sequence diagram for short message transfer (Figure 15g) showing a failure over the first path (SGSN) and success over the second path (MSC).](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The sequence diagram illustrates the interaction between SC, SMS-GMSC, HLR, MSC or SGSN, VLR, and MS for short message transfer. The process involves an initial message transfer, routing information lookup, a failed attempt over the first path (SGSN), a successful attempt over the second path (MSC), and final delivery and reports. + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + Note left of SC: Operation invocation or message transfer. + SC->>SMS-GMSC: 1a. Message transfer + Note left of SMS-GMSC: Successful operation invocation or message transfer including report. + SMS-GMSC->>HLR: 2. SendRoutingInfo + Note left of HLR: Error report. + HLR-->>SMS-GMSC: 2. SendRoutingInfo - ForShortMsg + Note left of SMS-GMSC: Unsuccessful operation invocation or message transfer including report. (or with missing confirmation) + SMS-GMSC->>MSC or SGSN: 4a. ForwardShortMessage (e.g over SGSN) + Note left of MSC or SGSN: Error report. + MSC or SGSN-->>VLR: 5. sendInfoFor- MT-SMS + Note left of MSC or SGSN: Successful operation invocation or message transfer including report. + MSC or SGSN->>SMS-GMSC: 4c. Failure Report + Note left of SMS-GMSC: Error report. + SMS-GMSC->>MSC or SGSN: 4a. ForwardShortMessage (e.g over MSC) + Note left of MSC or SGSN: Successful operation invocation or message transfer including report. + MSC or SGSN-->>VLR: 5. sendInfoFor- MT-SMS + Note left of MSC or SGSN: Successful operation invocation or message transfer including report. + MSC or SGSN->>MS: 6. Message Transfer + Note left of MS: Successful operation invocation or message transfer including report. + MS->>MSC or SGSN: 4b. Delivery Report + Note left of MSC or SGSN: Successful operation invocation or message transfer including report. + MSC or SGSN->>SMS-GMSC: 3. SM-Delivery + Note left of SMS-GMSC: Successful operation invocation or message transfer including report. + SMS-GMSC->>HLR: ReportStatus + Note left of HLR: Successful operation invocation or message transfer including report. + SMS-GMSC->>SC: 1b. Delivery report + Note left of SC: Successful operation invocation or message transfer including report. + +``` + +Legend: + +- Operation invocation or message transfer. +- Successful operation invocation or message transfer including report. +- Error report +- Unsuccessful operation invocation or message transfer including report. (or with missing confirmation) + +Sequence diagram for short message transfer (Figure 15g) showing a failure over the first path (SGSN) and success over the second path (MSC). + +NOTE 1: This operation is not used by the SGSN. + +NOTE 2: Two addresses (SGSN and MSC) are received from HLR. + +NOTE 3: Both successful transfer over second path and unsuccessful transfer over first path (e.g. Absent subscriber) are sent to HLR. + +NOTE 4: The SMS transfer towards the second path is only triggered by the reception of some MAP errors on the first path as described in sub-clause 8.1.1. + +**Figure 15g): Short message transfer attempt failing over the first path (e.g. SGSN) and succeeding over the second path (e.g. MSC)** + +![Sequence diagram for Short message transfer attempt via the SMS Router failing over the first path (e.g. SGSN) and succeeding over the second path (e.g. MSC).](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant SMS Router + participant MSC or SGSN + participant VLR + participant MS + + Note right of SC: Error! No + Note right of HLR: 15 + Note right of MSC or SGSN: Error! No text of specified style in + + SC->>SMS-GMSC: 1a. Message Transfer + SMS-GMSC->>HLR: 2a. SendRoutingInfo ForShortMsg + HLR->>SMS Router: 2a. SendRoutingInfo ForShortMsg + HLR->>SMS Router: 2. SendRoutingInfo ForShortMsg + SMS Router->>SMS-GMSC: 2b. SendRoutingInfo ForShortMsg + SMS-GMSC->>SMS Router: 4a. ForwardShortMsg (e.g. via SGSN) + SMS Router->>MSC or SGSN: 4a. ForwardShortMsg (e.g. via SGSN) + MSC or SGSN->>VLR: 5. SendInfoFor MT-SMS + MSC or SGSN-->>SMS Router: 4c. Failure Report + SMS Router-->>SMS-GMSC: 4c. Failure Report + SMS-GMSC->>SMS Router: 4a. ForwardShortMsg (e.g. via MSC) (See NOTE 4) + SMS Router->>MSC or SGSN: 4a. ForwardShortMsg (e.g. via MSC) + MSC or SGSN->>VLR: 5. SendInfoFor MT-SMS + MSC or SGSN->>MS: 6. Message Transfer + MSC or SGSN->>SMS Router: 4b. Delivery Report + SMS Router->>SMS-GMSC: 4b. Delivery Report + SMS-GMSC->>HLR: 3. SM-Delivery ReportStatus + SMS-GMSC->>SC: 1b. Delivery Report + +``` + +Sequence diagram for Short message transfer attempt via the SMS Router failing over the first path (e.g. SGSN) and succeeding over the second path (e.g. MSC). + +→ Operation invocation or message transfer + +←→ Successful operation invocation or message transfer including report +Error Report + +-.-> Operation invocation or message transfer + +-.-← Unsuccessful operation invocation or message transfer including report + +NOTE 1: Operation 5 is not used by the SGSN. + +NOTE 2: In Operation 2b, two addresses are received from the SMS Router by the SMS-GMSC. Both contain the address of the SMS Router, however, each address identifies delivery to the MS via the MSC or via the SGSN. + +NOTE 3: In Operation 3, both successful transfer over second path and unsuccessful transfer over first path (e.g. Absent subscriber) are sent to the HLR. + +NOTE 4: The SMS transfer towards the second path is only triggered by the reception of some MAP errors on the first path as described in sub-clause 8.1.1. + +**Figure 15ga): Short message transfer attempt via the SMS Router failing over the first path (e.g. SGSN) and succeeding over the second path (e.g. MSC)** + +![Sequence diagram for Figure 15h: Short message transfer attempt failing over the first path (e.g. SGSN) and over the second path (e.g. MSC).](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The sequence diagram illustrates the interaction between six entities: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, and MS. The process begins with the SC sending a '1a. Message transfer' to the SMS-GMSC. The SMS-GMSC then sends a '2. SendRoutingInfo' to the HLR, which responds with 'ForShortMsg'. The SMS-GMSC attempts to forward the message via '4a. ForwardShortMessage (e.g over SGSN)' to the MSC or SGSN. The MSC or SGSN sends a '5. sendInfoFor-' (labeled 1) to the VLR, which results in an 'MT-SMS' to the MS. However, the MSC or SGSN also sends a '4c. Failure Report' back to the SMS-GMSC. The SMS-GMSC then attempts the second path with '4a. ForwardShortMessage (e.g over MSC)' to the MSC or SGSN. Again, the MSC or SGSN sends a '5. sendInfoFor-' (labeled 1) to the VLR for 'MT-SMS' to the MS, but also sends another '4c. Failure Report' to the SMS-GMSC. Finally, the MSC or SGSN sends a '6. Message Transfer' to the MS. The SMS-GMSC receives a '3. SM-Delivery' from the HLR and a 'ReportStatus' from the HLR. The SC receives a '1b. Failure report' from the SMS-GMSC. + +Legend: + +- Operation invocation or message transfer. +- ← Successful operation invocation or message transfer including report. +- Error report +- ← Unsuccessful operation invocation or message transfer including report. (or with missing confirmation) + +Sequence diagram for Figure 15h: Short message transfer attempt failing over the first path (e.g. SGSN) and over the second path (e.g. MSC). + +NOTE 1: This operation is not used by the SGSN. + +NOTE 2: Two addresses (SGSN and MSC) are received from HLR. + +NOTE 3: Unsuccessful transfer over the second path (e.g. MemoryCapacityExceeded) and over the first path (e.g. Absent subscriber) are sent to HLR. + +NOTE 4: The SMS transfer towards the second path is only triggered by the reception of some MAP errors on the first path as described in clause 8.1.1. + +NOTE 5: If an SMS Router is present, the message flow in 15ga is used, except that a 4c Failure Report message is transparently transferred to the SMS-GMSC from the MSC or SGSN by the SMS Router instead of a 4b Delivery Report. + +**Figure 15h): Short message transfer attempt failing over the first path (e.g. SGSN) and over the second path (e.g. MSC)** + +Operation 1: Message transfer SC -> SMS-GMSC. + +This operation is used to transfer a short message from an SC to an SMS-GMSC. + +The operation consists of: + +- the transfer of a message containing the TPDU from the SC to the SMS-GMSC (see "1a. Message transfer" in figure 15); and +- the return of either a "Failure report" (see 1c. in figure 15) or a "Delivery report" (see 1b. in figure 15). + +"Failure report" is returned to the SC when the SMS-GMSC has received indication from another entity (MSC, SGSN or HLR) the procedure was unsuccessful. The error indications which the SMS-GMSC may receive from the MSC, + +SGSN, HLR, VLR or MS enable the SMS-GMSC to return one of the error indications given in clause 3.3 back to the SC. + +Operation 2: sendRoutingInfoForShortMsg. + +The operation is an interrogation of the HLR by the SMS-GMSC or the SMS Router to retrieve information necessary to deliver the short message. + +The result may contain the MSC, SGSN, both MSC and SGSN addresses, or the address of the SMS Router. It shall also indicate which address belongs to the MSC and the SGSN, however, it shall not indicate if the address belongs to an SMS Router (as the SMS Router poses as either an MSC or an SGSN or both to the SMS-GMSC). + +Operation 3: SM-DeliveryReportStatus. + +The operation provides a means for the SMS-GMSC to request the HLR to add an SC address to the MWD, and is activated when the SMS-GMSC receives an absent subscriber indication from the MSC, SGSN or both, and/or when the SMS-GMSC receives a failure report for a short message transfer with cause MS Memory Capacity Exceeded via the MSC or SGSN. The Return Result optionally contains the MSIsdn-Alert or IMSI-Alert. + +This operation is also activated at successful delivery short message when the MNRF, MNRG or both are set in HLR. + +The operation consists of: + +- the transfer of a message, containing the MSISDN or IMSI of the MS to which the short message was addressed, the SC-address, the successful outcome and/or the causes (Absent Subscriber, MS memory capacity exceeded or both) for updating the MWD, from the SMS-GMSC to the HLR (see 3. in figure 15). + +Operation 4: forwardShortMessage. + +The operation provides a means for the SMS-GMSC to transfer a short message to the MSC or to the SGSN at which the MS is currently located, via an SMS Router if deployed by the HPLMN of the receiving MS. + +The operation works in tandem with the forwarding of the short message from the MSC or from the SGSN to the MS. Thus, the outcome of the operation comprises either success, i.e. that the message has been delivered to the MS; or a failure that may be caused by several reasons, e.g. failure in the transfer SMS-GMSC -> MSC or SMS-GMSC -> SGSN, MS being detached, or no paging response. + +It should be noted that the MNRG setting is implicitly carried out in the SGSN when the message transfer is denied due to GPRS DETACH. + +Operation 5: sendInfoForMT-SMS. + +The operation provides a means for the MSC to retrieve subscriber information from VLR for mobile terminated short message transfer. The operation may be associated with an authentication procedure, as shown in figure 16. Unsuccessful retrieval (e.g. absent subscriber) is indicated by a cause indication to the SMS-GMSC. + +An overall depiction of how operation 5 interacts with signalling on the radio path is given in figure 16. + +It should be noted that the MNRF setting is implicitly carried out when the message transfer is denied due to IMSI DETACH. + +NOTE: This operation is not used by the SGSN. + +Operation 6: Message transfer MSC -> MS. + +The operation is used to transfer a short message from the MSC to the MS. + +If the transfer is not successful, e.g. due to the MS losing radio coverage after having successfully authenticated, a failure report (RP-ERROR) is returned to the SMS-GMSC. In this case, MWD and MCEF in the HLR shall be updated only for the case where the transfer fails with cause MS Memory Capacity Exceeded. + +If the MS notifies the network that the MS has been unable to accept a short message because its memory capacity has been exceeded, then the ME shall set the memory capacity Exceeded Notification flag if present. + +Operation 7: InformSC. + +The operation is used to transfer the MSIsdn-Alert or IMSI-Alert from the HLR to the SMS-GMSC if the error Absent Subscriber or a positive result is given as an answer to the operation SendRoutingInfoForSM. + +![Sequence diagram showing the interaction between SC, SMS-GMSC, HLR, MSC or SGSN, VLR, and MS for mobile terminated short message transfer.](24029b85683e6c5b14e96022cd9b6ff6_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + Note right of SMS-GMSC: 4a. forwardShortMessage + SMS-GMSC->>MSC or SGSN: 4a. forwardShortMessage + Note right of MSC or SGSN: 5a. sendInfoFor- MT-SMS 2) + MSC or SGSN->>VLR: 5a. sendInfoFor- MT-SMS 2) + Note right of VLR: Page 1) + VLR->>MS: Page 1) + Note right of VLR: Authent. 1) + VLR->>MS: Authent. 1) + Note right of MSC or SGSN: 5b. sendInfoFor- MT-SMS (Ack) 2) + MSC or SGSN->>HLR: 5b. sendInfoFor- MT-SMS (Ack) 2) + Note right of MSC or SGSN: 6. Message transfer (correct) + MSC or SGSN->>MS: 6. Message transfer (correct) + Note right of MSC or SGSN: 4b. Delivery report + MSC or SGSN->>SMS-GMSC: 4b. Delivery report + +``` + +Sequence diagram showing the interaction between SC, SMS-GMSC, HLR, MSC or SGSN, VLR, and MS for mobile terminated short message transfer. + +-----> : Operation invocation or message transfer +<----- : Successful operation invocation or message transfer incl. report + +NOTE 1: Described in GSM 44.008 [12] and 3GPP TS 29.002 [15]. + +If the SGSN is used, Paging and Authentication are performed from SGSN. + +NOTE 2: This operation is not used by the SGSN. + +NOTE 3: If an SMS Router is present, the message 4a forwardShortMessage and 4b Delivery report are transparently transferred from/to the SMS-GMSC to/from the MSC or SGSN by the SMS Router. + +**Figure 16a): "Send information for MT SMS" procedure; error free case** + +![Sequence diagram for 'Send information for MT SMS' procedure showing an erroneous case with an absent subscriber. Lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, MS. The diagram shows message 4a (forwardShortMessage) from SMS-GMSC to MSC or SGSN, followed by 5a (sendInfoFor-MT-SMS) and 5c (Failure report) from MSC or SGSN to VLR. A failure report (4c) is then sent from MSC or SGSN back to SMS-GMSC, which finally sends 3a (SMDelivery) to HLR with a ReportStatus.](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + Note right of SMS-GMSC: 4a. forwardShortMessage + SMS-GMSC->>MSC or SGSN: 4a. forwardShortMessage + Note right of MSC or SGSN: 5a. sendInfoFor- MT-SMS 1) + MSC or SGSN->>VLR: 5a. sendInfoFor- MT-SMS 1) + Note right of MSC or SGSN: 5c. Failure report + MSC or SGSN-->>VLR: 5c. Failure report + Note right of MSC or SGSN: 4c. Failure report + MSC or SGSN-->>SMS-GMSC: 4c. Failure report + Note right of SMS-GMSC: 3a. SMDelivery + SMS-GMSC->>HLR: 3a. SMDelivery + Note right of SMS-GMSC: ReportStatus + SMS-GMSC-->>HLR: ReportStatus + +``` + +Sequence diagram for 'Send information for MT SMS' procedure showing an erroneous case with an absent subscriber. Lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, MS. The diagram shows message 4a (forwardShortMessage) from SMS-GMSC to MSC or SGSN, followed by 5a (sendInfoFor-MT-SMS) and 5c (Failure report) from MSC or SGSN to VLR. A failure report (4c) is then sent from MSC or SGSN back to SMS-GMSC, which finally sends 3a (SMDelivery) to HLR with a ReportStatus. + +----- : Operation invocation or message transfer + - - - -> : Error report + +NOTE 1: The GPRS DETACH information is in the SGSN. + This operation is not used by the SGSN. + +NOTE 2: If an SMS Router is present, the message 4a forwardShortMessage and 4c Failure report are transparently transferred from/to the SMS-GMSC to/from the MSC or SGSN by the SMS Router. + +**Figure 16b): "Send information for MT SMS" procedure; + erroneous case: absent subscriber (e.g. IMSI DETACH or GPRS DETACH)** + +![Sequence diagram for 'Send information for MT SMS' procedure showing an erroneous case where the subscriber is absent. Lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, MS. The sequence starts with 4a. forwardShortMessage from SMS-GMSC to MSC or SGSN. MSC or SGSN sends 5a. sendInfoFor-MT-SMS to VLR, which then sends a Page to MS. MSC or SGSN receives 5c. Paging failure from VLR and sends 4c. Failure report back to SMS-GMSC. Finally, SMS-GMSC sends 3a. SM-Delivery and ReportStatus to HLR.](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + Note left of SC: ----- : Operation invocation or message transfer + Note left of SC: - - - -> : Error report + + SMS-GMSC->>MSC or SGSN: 4a. forwardShortMessage + MSC or SGSN->>VLR: 5a. sendInfoFor-MT-SMS 2) + VLR->>MS: Page 1) + VLR-->>MSC or SGSN: 5c. Paging failure2) + MSC or SGSN-->>SMS-GMSC: 4c. Failure report + SMS-GMSC->>HLR: 3a. SM-Delivery + SMS-GMSC->>HLR: ReportStatus + +``` + +Sequence diagram for 'Send information for MT SMS' procedure showing an erroneous case where the subscriber is absent. Lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, MS. The sequence starts with 4a. forwardShortMessage from SMS-GMSC to MSC or SGSN. MSC or SGSN sends 5a. sendInfoFor-MT-SMS to VLR, which then sends a Page to MS. MSC or SGSN receives 5c. Paging failure from VLR and sends 4c. Failure report back to SMS-GMSC. Finally, SMS-GMSC sends 3a. SM-Delivery and ReportStatus to HLR. + +----- : Operation invocation or message transfer + - - - -> : Error report + +NOTE 1: Described in GSM 44.008 [12] and 3GPP TS 29.002 [15]. + If the SGSN is used, Paging is performed from SGSN. + +NOTE 2: This operation is not used by the SGSN. + +NOTE 3: If an SMS Router is present, the message 4a forwardShortMessage and 4c Failure report are transparently transferred from/to the SMS-GMSC to/from the MSC or SGSN by the SMS Router. + +**Figure 16c): "Send information for MT SMS" procedure; + erroneous case: Absent subscriber (e.g. no paging response)** + +![Sequence diagram for 'Send information for MT SMS' procedure with incorrect authentication. Lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, MS. The sequence shows a failure in authentication between the VLR and MS, leading to an authentication failure report back to the MSC/SGSN and then a failure report to the SMS-GMSC.](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC_SGSN as MSC or SGSN + participant VLR + participant MS + + Note left of SC: Error! No + Note right of MS: Error! No text of specified style in + + SMS-GMSC->>MSC_SGSN: 4a. forwardShortMessage + MSC_SGSN->>VLR: 5a. sendInfoFor-MT-SMS 2) + VLR->>MS: Page 1) + MS-->>VLR: Authent. 1) +(incorr. resp.) + VLR-->>MSC_SGSN: 5c. +auth. failure 2) + MSC_SGSN-->>SMS-GMSC: 4c. Failure report + +``` + +Legend: + +- > : Operation invocation or message transfer +- - -> : Error report +- <- - -> : Unsuccessful operation invocation or message transfer including error report (or with missing confirmation) + +NOTE 1: Described in GSM 44.008 [12] and 3GPP TS 29.002 [15]. +If the SGSN is used, Paging and Authentication are performed from SGSN. + +NOTE 2: This operation is not used by the SGSN. + +NOTE 3: If an SMS Router is present, the message 4a forwardShortMessage and 4c Failure report are transparently transferred from/to the SMS-GMSC to/from the MSC or SGSN by the SMS Router. + +Sequence diagram for 'Send information for MT SMS' procedure with incorrect authentication. Lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, MS. The sequence shows a failure in authentication between the VLR and MS, leading to an authentication failure report back to the MSC/SGSN and then a failure report to the SMS-GMSC. + +**Figure 16d): "Send information for MT SMS" procedure; incorrect authentication** + +## 10.2 Short message mobile originated + +The entities involved in this procedure is depicted in figure 17. + +![Diagram showing the interfaces involved in the Short message mobile originated procedure. SC is connected to SMS-IWMSC via interface X. SMS-IWMSC is connected to both SGSN and MSC. SGSN is connected to MS. MSC is connected to MS and VLR. VLR is connected to MS.](1b896a95bc9974ad01fac7ac6f541a96_img.jpg) + +``` + +graph LR + SC[SC] ---|X| SMS-IWMSC[SMS-IWMSC] + SMS-IWMSC --- SGSN[SGSN] + SMS-IWMSC --- MSC[MSC] + SGSN --- MS[MS] + MSC --- MS + MSC --- VLR[VLR] + VLR --- MS + +``` + +Diagram showing the interfaces involved in the Short message mobile originated procedure. SC is connected to SMS-IWMSC via interface X. SMS-IWMSC is connected to both SGSN and MSC. SGSN is connected to MS. MSC is connected to MS and VLR. VLR is connected to MS. + +**Figure 17: Interfaces involved in the Short message mobile originated procedure** + +GSM TS 43.002 [5]. X is the interface between an MSC or an SGSN and an SC as defined in clause 5. + +Note that since the short message mobile originated procedure covers the functionality required at SM-RL for transferring TPDU's from SC to MS, the procedure described covers both short message (SMS-SUBMIT) and command (SMS-COMMAND) transfer. The term "short message transfer" therefore in this clause, covers both cases. + +In figure 18, sequence diagrams for the following basic situations of short message mobile terminated transfer attempt: + +- Successful short message transfer; +- Short message transfer attempt failing due to error at the MSC or SGSN; +- Short message transfer attempt failing due to negative outcome of VLR information retrieval; +- Short message transfer attempt failing due to error at the SMS-IWMSC; +- Short message transfer attempt failing due to error at the SC; +- Short Message transfer attempt successful due to the existence of an SMS Interworking agreement; +- Short Message transfer attempt failing due to non-existence of an SMS Interworking agreement; +- Short Message transfer attempt failing due to negative outcome of HLR information retrieval. + +References to the relevant specifications of the different operations are given in clause 4. + +![Sequence diagram for a successful short message transfer attempt. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The sequence starts with an Access request from MS to VLR, followed by 7a. Message transfer from MSC or SGSN to MS. Then 8a. sendInfoFor-MO-SMS from MSC or SGSN to VLR. Next, 9. forwardShortMessage from MSC or SGSN to SMS-IWMSC. Then 10a. Message transfer from SMS-IWMSC to SC, followed by 10b. Delivery report from SC to SMS-IWMSC. Then 9b. Delivery report from SMS-IWMSC to MSC or SGSN, and finally 7b. Delivery report from MSC or SGSN to MS.](1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-IWMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + Note right of MS: Access request +<----->> MS +and possible authentication 1) + + Note right of MSC or SGSN: 7a. Message transfer + MSC or SGSN->>MS: 7a. Message transfer + + Note right of MSC or SGSN: 8a. sendInfoFor- +<----->> VLR +MO-SMS 2) + + Note right of MSC or SGSN: 9. forwardShortMessage + MSC or SGSN->>SMS-IWMSC: 9. forwardShortMessage + + Note left of SMS-IWMSC: 10a. Message +<----->> SC +transfer + + Note left of SMS-IWMSC: 10b. Delivery +<----->> SMS-IWMSC +report + + Note right of SMS-IWMSC: 9b. Delivery report + SMS-IWMSC->>MSC or SGSN: 9b. Delivery report + + Note right of MSC or SGSN: 7b. Delivery report + MSC or SGSN->>MS: 7b. Delivery report + +``` + +Sequence diagram for a successful short message transfer attempt. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The sequence starts with an Access request from MS to VLR, followed by 7a. Message transfer from MSC or SGSN to MS. Then 8a. sendInfoFor-MO-SMS from MSC or SGSN to VLR. Next, 9. forwardShortMessage from MSC or SGSN to SMS-IWMSC. Then 10a. Message transfer from SMS-IWMSC to SC, followed by 10b. Delivery report from SC to SMS-IWMSC. Then 9b. Delivery report from SMS-IWMSC to MSC or SGSN, and finally 7b. Delivery report from MSC or SGSN to MS. + +-----> : Operation invocation or message transfer + <-----> : Successful operation invocation or message transfer including report + +NOTE 1): Described in [12] and 3GPP TS 29.002 [15]. + +NOTE 2): This operation is not used by the SGSN. + +**Figure 18a): Successful short message transfer attempt** + +![Sequence diagram for Figure 18b showing a short message transfer attempt failing due to an error at the MSC or SGSN. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The sequence starts with an Access request from VLR to MS. Then, 7a. Message transfer from MSC or SGSN to MS. Finally, 7c. Failure report from MSC or SGSN to MS via a dashed line.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-IWMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + Note right of VLR: Access request +<-----> MS +and possible authentication 1) + Note right of MSC or SGSN: 7a. Message transfer + MSC or SGSN->>MS: + Note right of MSC or SGSN: 7c. Failure report + MSC or SGSN-->>MS: + +``` + +Sequence diagram for Figure 18b showing a short message transfer attempt failing due to an error at the MSC or SGSN. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The sequence starts with an Access request from VLR to MS. Then, 7a. Message transfer from MSC or SGSN to MS. Finally, 7c. Failure report from MSC or SGSN to MS via a dashed line. + +- : Operation invocation or message transfer +- <-----> : Successful operation invocation or message transfer including report +- > : Error report + +NOTE 1): Described in GSM 44.008 [12] and 3GPP TS 29.002 [15]. + +**Figure 18b): Short message transfer attempt failing due to error at the MSC or SGSN** + +![Sequence diagram for Figure 18c showing a short message transfer attempt failing due to negative outcome of VLR information retrieval. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The sequence starts with an Access request from VLR to MS. Then, 7a. Message transfer from MSC or SGSN to MS. Next, 8. sendInfoFor-MO-SMS from MSC or SGSN to VLR. Finally, 7c. Failure report from MSC or SGSN to MS via a dashed line.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-IWMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + Note right of VLR: Access request +<-----> MS +and possible authentication 1) + Note right of MSC or SGSN: 7a. Message transfer + MSC or SGSN->>MS: + Note right of MSC or SGSN: 8. sendInfoFor-MO-SMS 2) + MSC or SGSN-->>VLR: + Note right of MSC or SGSN: 7c. Failure report + MSC or SGSN-->>MS: + +``` + +Sequence diagram for Figure 18c showing a short message transfer attempt failing due to negative outcome of VLR information retrieval. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The sequence starts with an Access request from VLR to MS. Then, 7a. Message transfer from MSC or SGSN to MS. Next, 8. sendInfoFor-MO-SMS from MSC or SGSN to VLR. Finally, 7c. Failure report from MSC or SGSN to MS via a dashed line. + +- : Operation invocation or message transfer +- <-----> : Successful operation invocation or message transfer including report +- > : Error report +- <-----> : Unsuccessful operation invocation or message transfer incl. error report (or with missing confirmation) + +NOTE 1): Described in GSM 44.008 [12] and 3GPP TS 29.002 [15]. + +NOTE 2): This operation is not used by the SGSN. + +**Figure 18c): Short message transfer attempt failing due to negative outcome of VLR information retrieval** + +![Sequence diagram for short message transfer attempt failing due to error at the SMS-IWMSC. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The diagram shows an 'Access request' from MS to VLR, followed by '7a. Message transfer' from VLR to MSC or SGSN, then '8a. sendInfoFor MO-SMS' from MSC or SGSN to VLR. The MSC or SGSN then sends '9. forwardShortMessage' to SMS-IWMSC, which fails. A '9c. Failure report' is sent from SMS-IWMSC to MSC or SGSN, which then sends a '7c. Failure report' to MS.](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` +sequenceDiagram + participant MS + participant VLR + participant MSC_SGSN as MSC or SGSN + participant HLR + participant SMS_IWMSC as SMS-IWMSC + participant SC + + Note right of VLR: Access request +and possible authentication 1) + MS->>VLR: Access request + VLR->>MSC_SGSN: 7a. Message transfer + MSC_SGSN->>VLR: 8a. sendInfoFor MO-SMS 2) + MSC_SGSN->>SMS_IWMSC: 9. forwardShortMessage + Note left of SMS_IWMSC: Error at SMS-IWMSC + SMS_IWMSC-->>MSC_SGSN: 9c. Failure report + MSC_SGSN-->>MS: 7c. Failure report +``` + +Sequence diagram for short message transfer attempt failing due to error at the SMS-IWMSC. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The diagram shows an 'Access request' from MS to VLR, followed by '7a. Message transfer' from VLR to MSC or SGSN, then '8a. sendInfoFor MO-SMS' from MSC or SGSN to VLR. The MSC or SGSN then sends '9. forwardShortMessage' to SMS-IWMSC, which fails. A '9c. Failure report' is sent from SMS-IWMSC to MSC or SGSN, which then sends a '7c. Failure report' to MS. + +- : Operation invocation or message transfer +- <----- : Successful operation invocation or message transfer including report +- - - - - : Error report + +NOTE 1): Described in GSM 44.008 [12] and 3GPP TS 29.002 [15]. + +NOTE 2): This operation is not used by the SGSN. + +**Figure 18d): Short message transfer attempt failing due to error at the SMS-IWMSC** + +![Sequence diagram for short message transfer attempt failing due to error at the SC. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The diagram shows a failed message transfer from MS to SC, with error reports being generated at the SC and propagated back through the network elements.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS_IWMSC as SMS-IWMSC + participant HLR + participant MSC_SGSN as MSC or SGSN + participant VLR + participant MS + + Note right of VLR: Access request +and possible authentication 1) + MS->>VLR: Access request + VLR->>MSC_SGSN: 7a. Message transfer + MSC_SGSN->>VLR: 8a. sendInfoFor-MO-SMS 2) + MSC_SGSN->>SMS_IWMSC: 9. forwardShortMessage + SMS_IWMSC->>SC: 10a. Message transfer + SC-->>SMS_IWMSC: 10c. Failure report + SMS_IWMSC-->>MSC_SGSN: 9c. Failure report + MSC_SGSN-->>VLR: 7c. Failure report + +``` + +Legend: + +- \_\_\_\_\_\_\_\_ : Operation invocation or message transfer +- <------- : Successful operation invocation or message transfer including report +- - - - - : Error report + +Sequence diagram for short message transfer attempt failing due to error at the SC. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The diagram shows a failed message transfer from MS to SC, with error reports being generated at the SC and propagated back through the network elements. + +NOTE 1): Described in GSM 44.008 [12] and 3GPP TS 29.002 [15]. + +NOTE 2): This operation is not used by the SGSN. + +**Figure 18e): Short message transfer attempt failing due to error at the SC** + +![Sequence diagram for Short Message transfer. Lifelines: HLR-b (see note 3), SC, SMS-IWMSC, HLR-a, MSC or SGSN, VLR, MS-a. The diagram shows the interaction between these entities for a successful SMS transfer. Legend: Single arrow = Operation invocation or message transfer; Double arrow = Successful operation invocation or message transfer including report.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +sequenceDiagram + participant MS-a + participant VLR + participant MSC or SGSN + participant HLR-a + participant SMS-IWMSC + participant SC + participant HLR-b as HLR-b (see note 3) + + Note right of MS-a: Access request and possible authentication (see note 1) + MS-a->>VLR: + VLR->>MSC or SGSN: 7a Message transfer + MSC or SGSN->>VLR: 8a. SendInfoFor-MO-SMS (see note2) + MSC or SGSN->>HLR-a: 9. forwardShortMessage + HLR-a->>SC: 2. SendRoutingInfoFor-SM + SC->>SMS-IWMSC: 10a. Message transfer + SMS-IWMSC->>SC: 10b. Delivery report + SC->>HLR-a: 9b. Delivery report + HLR-a->>MSC or SGSN: 7b. Delivery report + +``` + +Legend: + +- : Operation invocation or message transfer +- ⇒ : Successful operation invocation or message transfer including report + +Sequence diagram for Short Message transfer. Lifelines: HLR-b (see note 3), SC, SMS-IWMSC, HLR-a, MSC or SGSN, VLR, MS-a. The diagram shows the interaction between these entities for a successful SMS transfer. Legend: Single arrow = Operation invocation or message transfer; Double arrow = Successful operation invocation or message transfer including report. + +NOTE 1: Described in 3GPP TS 44.008 [12] and 3GPP TS 29.002 [15]. + +NOTE 2: This operation is not used by the SGSN. + +NOTE 3: HLR that terminated user belongs to. + +After completing operation 2, SMS-IWMSC could check whether SMS interworking agreement exists or not based on IMSI. In this figure 18f case, there is an SMS interworking agreement between operators. + +**Figure 18f): Short Message transfer Successful due to the existence of an SMS Interworking agreement** + +![Sequence diagram for Short Message transfer attempt failing due to non-existence of an SMS Interworking agreement. Lifelines: HLR-b (see note 3), SC, SMS-IWMSC, HLR-a, MSC or SGSN, VLR, MS-a.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant HLR-b as HLR-b (see note 3) + participant SC + participant SMS-IWMSC + participant HLR-a + participant MSC_SGSN as MSC or SGSN + participant VLR + participant MS-a + + Note over VLR, MS-a: Access request and possible authentication (see note 1) + MS-a<->VLR: + Note over MSC_SGSN, MS-a: 7a. Message transfer request + MS-a->MSC_SGSN: + Note over MSC_SGSN, VLR: 8a. SendInfoFor-MO-SMS (see note 2) + MSC_SGSN<->VLR: + Note over SMS-IWMSC, MSC_SGSN: 9. forwardShortMessage + MSC_SGSN->SMS-IWMSC: + Note over HLR-b, SMS-IWMSC: 2a. SendRoutingInfoFor-SM + SMS-IWMSC<->HLR-b: + Note over SMS-IWMSC, MSC_SGSN: 9c. Failure report (see note 4) + SMS-IWMSC-->MSC_SGSN: + Note over MSC_SGSN, MS-a: 7c. Failure report (see note 4) + MSC_SGSN-->MS-a: + +``` + +→ : Operation invocation or message transfer + ↔ : Successful operation invocation or message transfer including report + --> : Error report + +Sequence diagram for Short Message transfer attempt failing due to non-existence of an SMS Interworking agreement. Lifelines: HLR-b (see note 3), SC, SMS-IWMSC, HLR-a, MSC or SGSN, VLR, MS-a. + +NOTE 1: Described in 3GPP TS 44.008 [12] and 3GPP TS 29.002 [15]. + +NOTE 2: This operation is not used by the SGSN. + +NOTE 3: HLR that terminated user belongs to. + +NOTE 4: The lack of an SMS interworking agreement can not be conveyed in the Failure Report as a specific indication. + +After completing operation 2, SMS-IWMSC could check whether SMS interworking agreement exists or not based on IMSI. In this figure 18g case, there is no SMS Interworking agreement between operators. + +**Figure 18g): Short Message transfer attempt failing due to non-existence of an SMS Interworking agreement** + +![Sequence diagram for Short Message transfer attempt failing due to negative outcome of HLR information retrieval. Lifelines: HLR-b (see note 3), SC, SMS-IWMSC, HLR-a, MSC or SGSN, VLR, MS-a. The diagram shows a failed attempt where the HLR-a returns an error report to the MSC/SGSN, which then propagates the failure back to the SMS-IWMSC and finally to the MS-a. Solid line with open arrowhead Solid line with double arrowhead Dashed line with open arrowhead](68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg) + +``` + +sequenceDiagram + participant MS-a + participant VLR + participant MSC or SGSN + participant HLR-a + participant SMS-IWMSC + participant SC + participant HLR-b as HLR-b (see note 3) + + Note right of MS-a: Access request and possible authentication (see note 1) + MS-a->>VLR: Access request + VLR->>MSC or SGSN: 7a. Message transfer request + MSC or SGSN->>VLR: 8a. SendInfoFor- + Note right of MSC or SGSN: MO-SMS (see note 2) + VLR->>HLR-a: 9. forwardShortMessage + HLR-a-->>MSC or SGSN: 9c. Failure report (see note 4) + MSC or SGSN-->>VLR: 7c. Failure report (see note 4) + VLR-->>MS-a: 7c. Failure report (see note 4) + MSC or SGSN->>HLR-b: 2. SendRoutingInfoFor-SM + HLR-b-->>SC: 7. InformSC + SC-->>SMS-IWMSC: 9c. Failure report (see note 4) + +``` + +Legend: + +- : Operation invocation or message transfer +- : Successful operation invocation or message transfer including report +- : Error report + +Sequence diagram for Short Message transfer attempt failing due to negative outcome of HLR information retrieval. Lifelines: HLR-b (see note 3), SC, SMS-IWMSC, HLR-a, MSC or SGSN, VLR, MS-a. The diagram shows a failed attempt where the HLR-a returns an error report to the MSC/SGSN, which then propagates the failure back to the SMS-IWMSC and finally to the MS-a. Solid line with open arrowhead Solid line with double arrowhead Dashed line with open arrowhead + +NOTE 1: Described in 3GPP TS 44.008 [12] and 3GPP TS 29.002 [15]. + +NOTE 2: This operation is not used by the SGSN. + +NOTE 3: HLR that terminated user belongs to. + +NOTE 4: The lack of an SMS interworking agreement can not be conveyed in the Failure Report as a specific indication. + +If SMS-IWMSC receives an informSC Message, then this message shall be ignored by the SMS-IWMSC. + +**Figure 18h: Short Message transfer attempt failing due to negative outcome of HLR information retrieval** + +If a failure report is indicated by the HLR after invocation of the "sendRoutingInfoForShortMsg" operation, the SMS-IWMSC shall return the appropriate error information to the MSC/SGSN with the error cause coded as follows: + + + +The procedure works in tandem with the forwarding of the short message from the SMS-IWMSC to the SC. Thus, the outcome of the operation comprises either success, i.e. that the message has been delivered to the SC; or a failure that may be caused by several reasons, e.g. failure in the transfer MSC --> SMS-IWMSC or SGSN --> SMS-IWMSC, SC does not comply. + +Operation 10: Message transfer SMS-IWMSC -> SC. + +The operation is used to transfer a short message from an SMS-IWMSC to an SC, and consists of: + +- the transfer of a message containing the TPDU from the SMS-IWMSC to the SC (see "10a. Message transfer" in figure 18); and +- the return of either a "Failure report" (see 10c. in figure 18) or a "Delivery report" (see 10b. in figure 18). + +"Failure report" is returned to the MS when the SMS-IWMSC has received indication from the network or the SC that the procedure was unsuccessful. + +## 10.3 Alert transfer + +The entities involved in this procedure are depicted in figure 19. + +![Diagram of interfaces involved in the Alert procedure. It shows a central SMS-IWMSC connected to an SC (via interface X), an HLR, and an MSC. The MSC is connected to an SGSN, a VLR, and an MS. The HLR is also connected to the VLR.](17b9d89b91e10c3efc38193baedee268_img.jpg) + +``` +graph LR + SC[SC] ---|X| SMS-IWMSC[SMS-IWMSC] + SMS-IWMSC --- HLR[HLR] + SMS-IWMSC --- MSC[MSC] + MSC --- SGSN[SGSN] + MSC --- VLR[VLR] + MSC --- MS[MS] + HLR --- VLR +``` + +Diagram of interfaces involved in the Alert procedure. It shows a central SMS-IWMSC connected to an SC (via interface X), an HLR, and an MSC. The MSC is connected to an SGSN, a VLR, and an MS. The HLR is also connected to the VLR. + +**Figure 19: Interfaces involved in the Alert procedure. X is the interface between an SC and an MSC as defined in clause 5** + +This procedure consists of the operations shown in figure 20. + +Three cases are distinguished: + +- the MS becomes reachable when the MNRF, MNRG or both are set but the MCEF is not set (figure 20a); +- the MS becomes reachable when the MNRF, MNRG or both, and the MCEF are set (figure 20b); +- the MS notifies the network that it has memory available to receive one or more short messages when the MCEF is set (figure 20c). + +The operations between MSC and VLR, between HLR and VLR or SGSN and between HLR and SMS-IWMSC are specified in 3GPP TS 29.002 [15]. The operation between MS and MSC or SGSN is specified in 3GPP TS 24.011 [13]. References to specifications of other operations are given in clause 4. + +![Sequence diagram showing the alert procedure. Message 11 (ReadyForSM) goes from VLR or SGSN to HLR. Message 12 (alertService-Centre) goes from HLR to SMS-IWMSC. Message 13 (Service-CentreAlert) goes from SMS-IWMSC to SC.](4792a2ccd62226861fadc22117edb7b1_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-IWMSC + participant HLR + participant MSC + participant VLR or SGSN + participant MS + + VLR or SGSN-->>HLR: 11. ReadyForSM (MS reachable) 1) + HLR-->>SMS-IWMSC: 12. alertService-Centre + SMS-IWMSC-->>SC: 13. Service-CentreAlert + +``` + +------- : Operation invocation or message transfer + +Sequence diagram showing the alert procedure. Message 11 (ReadyForSM) goes from VLR or SGSN to HLR. Message 12 (alertService-Centre) goes from HLR to SMS-IWMSC. Message 13 (Service-CentreAlert) goes from SMS-IWMSC to SC. + +NOTE 1): In case ReadyForSM is sent by the SGSN, the reason may be MS reachable via the SGSN, or MS reachable via the SGSN and the MSC (see 3GPP TS 23.060 [27]). + +**Figure 20a: The alert procedure when the MS becomes reachable, MNRF, MNRG or both are set and MCEF is not set** + +![Sequence diagram showing a partial alert procedure. Message 11 (ReadyForSM) goes from VLR or SGSN to HLR.](895d588a848d9963890c938763de9ecf_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-IWMSC + participant HLR + participant MSC + participant VLR or SGSN + participant MS + + VLR or SGSN-->>HLR: 11. ReadyForSM (MS reachable) 1) + +``` + +------- : Operation invocation or message transfer + +Sequence diagram showing a partial alert procedure. Message 11 (ReadyForSM) goes from VLR or SGSN to HLR. + +NOTE 1): In case ReadyForSM is sent by the SGSN, the reason may be MS reachable via the SGSN, or MS reachable via the SGSN and the MSC (see 3GPP TS 23.060 [27]). + +**Figure 20b: The alert procedure when the MS becomes reachable, MNRF, MNRG or both are set and MCEF is set** + +![Sequence diagram for Figure 20b showing the alert procedure when the MS becomes reachable. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The sequence starts with a message 'ReadyForSM' from MS to MSC or SGSN. Step 14: (smMemoryCapacityAvailable) 1) is shown from MSC or SGSN to HLR. Step 12: alertService-Centre is shown from HLR to SMS-IWMSC. Step 13: Service-Centrealert is shown from SMS-IWMSC to SC.](820515db47ded68f5e0b625f4ec7d2c1_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-IWMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + Note right of MSC or SGSN: ReadyForSM + MSC or SGSN->>HLR: 14. (smMemoryCapacityAvailable) 1) + HLR->>SMS-IWMSC: 12. alertService-Centre + SMS-IWMSC->>SC: 13. Service-Centrealert + +``` + +——→ : Operation invocation or message transfer + <—— : Successful operation invocation or message transfer including report + +Sequence diagram for Figure 20b showing the alert procedure when the MS becomes reachable. Lifelines: SC, SMS-IWMSC, HLR, MSC or SGSN, VLR, MS. The sequence starts with a message 'ReadyForSM' from MS to MSC or SGSN. Step 14: (smMemoryCapacityAvailable) 1) is shown from MSC or SGSN to HLR. Step 12: alertService-Centre is shown from HLR to SMS-IWMSC. Step 13: Service-Centrealert is shown from SMS-IWMSC to SC. + +NOTE 1): Described in 3GPP TS 24.011 [13] and 3GPP TS 29.002 [15]. + +**Figure 20c: The alert procedure when the MS notifies the network that it has memory available to receive one or more short messages and MCEF is set** + +Operation 11: ReadyForSM (MS reachable). + +The operation provides a means to transfer alert information from VLR or SGSN to HLR. + +The procedure is activated when the VLR or the SGSN detects that the MS is active, i.e. when the MS responds to a paging request. + +Operation 12: alertServiceCentre. + +The operation provides a means to transfer alert information from HLR to MSC. + +Operation 13: ServiceCentrealert. + +The operation provides a means to transfer alert information from an SMS-IWMSC to an SC. + +The operation consists of transfer of a message ("RP-ALERT-SC") from the SMS-IWMSC to the SC. + +Operation 14: ReadyForSM (smMemoryCapacityAvailable). + +The operation provides a means for the MS to notify the network that it has memory available to receive one or more short messages. + +The following applies if the memory capacity available notification flag is implemented in the (U)SIM. + +The operation consists of transfer of a message ("RP-SM-MEMORY-AVAILABLE") from the MS to the HLR, and the return of an acknowledgement to the MS. When the MS rejects a short message due to lack of available memory capacity the need to transfer notification shall be stored in the (U)SIM. After a attempt to transfer the RP-SM-Memory-Available message the following applies: + +If the MS receives a positive acknowledgement it shall unset the memory capacity exceeded notification flag in the (U)SIM and exit this procedure. + +If the MS receives a negative acknowledgement indicating a permanent failure condition (as specified in 3GPP TS 24.011 [13]) it shall unset the memory capacity exceeded notification flag in the (U)SIM and exit the procedure. + +If the MS receives a negative acknowledgement indicating a temporary failure condition (as specified in 3GPP TS 24.011 [13]) or receives no acknowledgement or an indication of failure by lower layers, it shall repeat the attempt to transfer the message in accordance with procedures defined in 3GPP TS 24.011 [13]. If these repeat procedures fail, the mobile shall unset the memory capacity exceeded notification flag in the (U)SIM and exit this procedure. + +If memory capacity has become available because memory is cleared, the value of the memory capacity exceeded notification flag is read. If the flag is set, the MS notifies the network that memory capacity is now available as described above. + +When the mobile is powered up or the SIM/UICC is inserted, the mobile shall check the memory capacity exceeded notification flag in the (U)SIM; if the flag is set and the MS has memory available to receive a short message the mobile shall attempt to notify the network that it has memory available, as described above. + +# 11 Mapping of error causes between RP layers + +This clause describes the interworking between the relay layers on the radio interface (i.e. between the servicing MSC/SGSN and the mobile station), and within the network (i.e. between servicing MSC/SGSN, VLR, HLR, or GMSC). + +## 11.1 Mobile Terminated short message transfer + +If errors are indicated by the VLR after invocation of the "sendInfoFor-MT-SMS" operation, the appropriate error information is returned to the SMS-GMSC in a failure report as specified in 3GPP TS 29.002 [15] (negative outcome of "forwardShortMessage" see clause 10). + +If errors are detected by the MSC or by the SGSN during the transfer on the radio interface, or by the IP-SM-GW, the error cause returned in the return error of the MAP procedure ForwardShortMessage shall be set as follows: + +| Failure at the MSC , SGSN or IP-SM-GW | Return error to be included in the MAP-proc | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| RP-ERROR message with error cause: | | +| 22 Memory capacity exceeded | SM_DeliveryFailure with cause "MemoryCapacityExceeded" 1) | +| Other error causes | SM_DeliveryFailure with cause "equipmentProtocolError" 1) | +| CP or lower layer error
(e.g. RR, layer 2 failure) 2) | SM_DeliveryFailure with cause "equipmentProtocolError" 1) | +| Mobile has no SM capability | SM_DeliveryFailure with cause "equipmentNotSM-Equipped" 1) 0) | +| TR1N timeout 2)
MNSMS-error-ind (No SAPI 3) | SM_DeliveryFailure with cause "equipmentProtocolError" 1) | +| SIP transaction timeout in IP-SM-GW | SM_DeliveryFailure with cause "absentSubscriber" 1) | +| SIP transport error (e.g. SIP failure response message) 3) | SM_DeliveryFailure with cause "equipmentProtocolError" 1) | +| 1) For definition of MAP error SM_DeliveryFailure and its parameter "cause" see 3GPP TS 29.002 [15]. | | +| 2) The error causes of the RP-ERROR message, the CP layer and timer TR1N are defined in 3GPP TS 24.011 [13]. | | +| 3) The failure response codes for the SIP MESSAGE request are defined in IETF RFC 3428 [44], and the failure response codes for SIP transaction timeout in IETF RFC 3261 [43]. | | + +## 11.2 Memory available notification + +If errors are indicated by the HLR (via the VLR, the IP-SM-GW, or the SGSN) after invocation of the "ReadyForSM" operation, the MSC, the IP-SM-GW, or the SGSN shall return the appropriate error information to the MS in a failure report (i.e. a RP-ERROR message) containing the following error cause: + +| Return error from ReadyForSM
(Alert Reason is "memory available") | Cause value in the RP-ERROR message | +|---------------------------------------------------------------------------------------------|---------------------------------------| +| DataMissing | 38 Network out of order | +| UnexpectedDataValue | 38 Network out of order | +| UnknownSubscriber | 30 Unknown Subscriber | +| FacilityNotSupported | 69 Requested facility not implemented | +| System Failure | 38 Network out of order | +| Local or lower layer failure
(e.g. reject condition, timer expired or transaction abort) | 38 Network out of order | + +NOTE: The coding and the use of the RP-ERROR message is specified in 3GPP TS 24.011 [13]. + +## 11.3 Mobile Originated short message transfer + +If errors are indicated by the VLR after invocation of the "sendInfoForMO-SMS" operation (see clause 10), the MSC shall return the appropriate error information to the MS in a failure report (i.e. a RP-ERROR message) containing the following error cause: + +| Return error from SendInfoForMO-SMS | Cause value in the RP-ERROR message | +|-------------------------------------|--------------------------------------| +| DataMissing | 38 Network out of order | +| UnexpectedDataValue | 38 Network out of order | +| TeleserviceNotProvisioned | 50 Requested facility not subscribed | +| CallBarred | | +| - barringServiceActive | 10 Call barred | +| - operatorBarring | 8 Operator determined barring | + +NOTE: The coding and the use of the RP-ERROR message is specified in 3GPP TS 24.011 [13]. The operation SendInfoForMO-SMS is not used by the SGSN. + +If errors are indicated by the SMS-IWMSC (negative outcome of the "forwardShortMessage"), the MSC, the IP-SM-GW, or the SGSN shall send a failure report (i.e. a RP-ERROR message) to the MS, with the error cause coded as follows: + +| Return error from ForwardShortMessage | Cause value in the RP-ERROR message | +|------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| System Failure | 38 Network out of order | +| FacilityNotSupported | 69 Requested facility not implemented | +| UnexpectedDataValue | 38 Network out of order | +| SM-DeliveryFailure
cause: unknownSC | 1 Unassigned number | +| SM-DeliveryFailure
cause: SC-Congestion | 42 Congestion | +| SM-DeliveryFailure
cause: invalidSME-Addr (NOTE 1) | 21 Short message transfer rejected | +| SM-DeliveryFailure
cause: subscriberNotSC-Subscriber | 28 Unidentified subscriber | +| Local or lower layer failure
(e.g. reject condition, timer expired or transaction abort) | 38 Network out of order | +| NOTE 1: This cause includes the case when the outcome of optional HLR interrogation is unacceptable (see clause 8.2.2) | | + +NOTE: The coding and the use of the RP-ERROR message is specified in 3GPP TS 24.011 [13]. + +# --- Annex A (informative): Protocol stacks for interconnecting SCs and MSCs + +No mandatory protocol between the Service Centre (SC) and the Mobile Switching Centre (MSC) below the transfer layer is specified by GSM/UMTS specifications; this is a matter of agreement between SC and PLMN operators. However, SC and PLMN operators can base these protocols on the following principles: + +- a) provide the service defined for SM-RL (see subclause 9.3); +- b) be based on widely accepted telecommunications protocols in the public domain; +- c) permit open interconnection. + +# --- Annex B (informative): Information now contained in 3GPP TS 23.038 [9] + +Annex B held information that is now contained in 3GPP TS 23.038 [9]. + +# --- Annex C (informative):Short message information flow + +The diagrams in this annex describe the flow of primitives and parameters during the short message transfer. These diagrams refer to specifications 3GPP TS 23.040, 3GPP TS 24.011 [13] and 3GPP TS 29.002 [15]. The parameters in dotted lines are optional. The abbreviations used in diagrams are listed below. The relevant specifications are given in parentheses. (\*) stands for a common GSM/UMTS abbreviations and (-) for a general abbreviation. + +| | | +|-----------|---------------------------------------------------------| +| CM | Call Management (*) | +| CS | CauSe (-) | +| DA | Destination Address (-) | +| DCS | Data Coding Scheme (3GPP TS 23.040) | +| DI | Dialogue Identifier TCAP | +| GMSCA | Gateway MSC Address | +| GPRS | General Packet Radio Services 3GPP TS 23.060 [27] | +| HLR | Home Location Register (*) | +| IMSI | International Mobile Subscriber Identity (*) | +| MAL | MSIsdn-Alert or IMSI-Alert (3GPP TS 23.040) | +| MMS | More Messages to Send (3GPP TS 23.040) | +| MR | Message Reference (3GPP TS 23.040) | +| MS | Mobile Station (*) | +| MSC | Mobile services Switching Centre (*) | +| MSCA | MSC Address | +| MSI | Mobile waiting Set Indication (3GPP TS 23.040) | +| MSIsdn | Mobile Station ISDN number (*) | +| MSM | More Short Messages (3GPP TS 29.002 [15]) | +| MSRN | Mobile Station Roaming Number (*) | +| MT | Message Type (3GPP TS 24.011[13]) | +| MTI | Message Type Indicator (3GPP TS 24.011[13]) | +| MWS | Message Waiting Set (3GPP TS 23.040) | +| OA | Originating Address (-) | +| OC | Operation Code (3GPP TS 29.002 [15]) | +| PCI | Protocol Control Information (-) | +| PDI | Protocol DIsriminator (*) | +| PRI | PRiority (3GPP TS 23.040) | +| RCT | ReCeption Time (3GPP TS 23.040) | +| REA | REcipient Address (3GPP TS 23.040) | +| RL | ReLay function (3GPP TS 24.011[13]) | +| RP | Reply Path (3GPP TS 23.040) | +| SC | Service Centre (3GPP TS 23.040) | +| SCA | Service Centre Address (3GPP TS 23.040) | +| SCTS | Service Centre Time Stamp (3GPP TS 23.040) | +| SGSN | Serving GPRS Support Node (3GPP TS 23.060 [27]) | +| SM | Short Message (3GPP TS 23.040) | +| SM-AL | Short Message Application Layer (3GPP TS 23.040) | +| SME | Short Message Entity (3GPP TS 23.040) | +| SMI | Short Message Identifier (3GPP TS 23.040) | +| SM-RL | Short Message Relay Layer (3GPP TS 23.040, 24.011[13]) | +| SMS-GMSC | Short Message Service Gateway MSC (3GPP TS 23.040) | +| SMS-IWMSC | Short Message Service Interworking MSC (3GPP TS 23.040) | +| SoR | Status of Report (3GPP TS 23.040) | +| SM-TL | Short Message Transfer Layer (3GPP TS 23.040) | +| SRI | Status Report Indication (3GPP TS 23.040) | +| SRR | Status Report Request (3GPP TS 23.040) | +| TCAP | Transaction Capabilities Application Part (-) | +| TID | Transaction Identifier (*) | +| UD | User Data (-) | +| UDL | User Data Length (3GPP TS 23.040) | +| VLR | Visitor Location Register (*) | +| VP | Validity Period (3GPP TS 23.040) | +| VPF | Validity Period Format (3GPP TS 23.040) | + +![Sequence diagram showing the mobile terminated short message process. It starts with a SERVICE CENTRE sending a TS-DELIVER.REQ (containing MSISDN, SME, SC) to the SMAL layer. SMAL constructs an SMS-DELIVER message (MTI, MMS, RP, SRI, OA, PID, DCS, SCTS, UDL, UD) and sends it to the SM TL layer. SM TL constructs an RS-MT-DATA.REQ (SMI, DA, OA, MMS, PRI, UD) and sends it to the SM RL layer. SM RL constructs an RP-MT-DATA message (SMI, PRI, DA, OA, MMS, UD) and sends it TO THE SMS-GMSC.](4792a2ccd62226861fadc22117edb7b1_img.jpg) + +The diagram illustrates the protocol stack for a mobile terminated short message. At the top, the **SERVICE CENTRE** initiates the process with a **TS-DELIVER.REQ** message. This message includes fields for **MSISDN**, **SME**, and **SC**. The **SMAL** (Short Message Application Layer) layer receives this and constructs an **SMS-DELIVER** message. This message contains the following fields: **MTI** (Message Type Indicator), **MMS** (Multi Media Service), **RP** (Relay Protocol), **SRI** (Short Reference Indicator), **OA** (Originating Address), **PID** (Protocol Identifier), **DCS** (Data Coding Scheme), **SCTS** (Short Communication Transfer Capability), **UDL** (User Data Length), and **UD** (User Data). The **SM TL** (Short Message Transport Layer) layer receives the SMS-DELIVER message and constructs an **RS-MT-DATA.REQ** message. This message contains the fields: **SMI** (Service Message Indicator), **DA** (Destination Address), **OA** (Originating Address), **MMS**, **PRI** (Priority Indicator), and **UD**. The **SM RL** (Short Message Relay Layer) layer receives the RS-MT-DATA.REQ message and constructs an **RP-MT-DATA** message. This message contains the fields: **SMI**, **PRI**, **DA**, **OA**, **MMS**, and **UD**. Finally, the **RP-MT-DATA** message is sent **TO THE SMS-GMSC**. + +Sequence diagram showing the mobile terminated short message process. It starts with a SERVICE CENTRE sending a TS-DELIVER.REQ (containing MSISDN, SME, SC) to the SMAL layer. SMAL constructs an SMS-DELIVER message (MTI, MMS, RP, SRI, OA, PID, DCS, SCTS, UDL, UD) and sends it to the SM TL layer. SM TL constructs an RS-MT-DATA.REQ (SMI, DA, OA, MMS, PRI, UD) and sends it to the SM RL layer. SM RL constructs an RP-MT-DATA message (SMI, PRI, DA, OA, MMS, UD) and sends it TO THE SMS-GMSC. + +NOTE: SMI is not carried via SM-RL of clause 9.3.5 but is carried via the relay service between the SC and GMSC (see clause 9.3.4.1). + +**Figure C.1: Mobile terminated short message** + +![Sequence diagram of mobile terminated short message flow between SC, SMS-GMSC, HLR, and MSC.](69edc2887e907309499ac95b47ab6905_img.jpg) + +The diagram illustrates the sequence of messages for a mobile terminated short message. It consists of the following components and steps: + +- Entities:** + - SC (Sender Component):** Initiates the message from the bottom left. + - SMS-GMSC (SMS Gateway Mobile Switching Center):** The central routing entity. + - HLR (Home Location Register):** Located at the top, providing routing information. + - MSC (Mobile Switching Center):** The final destination at the bottom right. +- Message Flow:** + - FROM SC:** An arrow points from the SC to the SMS-GMSC. The message structure is **RP-MT-DATA**, which contains sub-fields: **SMI**, **PRI**, **DA**, **OA**, **MMS**, and **UD**. Above this, the **MSISDN** and **SCA** are indicated. + - SEND ROUTING INFO FOR SHORT MESSAGE (3G TS 29.002):** The SMS-GMSC sends this message to the HLR. It includes a box with **DA**, **SMI**, and **DI**. The HLR responds with a **SHORT MESSAGE ROUTING INFORMATION MESSAGE (3G TS 29.002)**, containing **OC**, **PRI**, **MSISDN**, and **SCA**. + - FORWARD SHORT MESSAGE (3G TS 29.002):** The SMS-GMSC then forwards the message to the MSC via **TCAP**. The message structure includes **OC**, **DA**, **OA**, **UD**, and **MSM**. Below this, **GMSCA**, **DA**, **DI**, and **UD** are shown, with **MSCA** indicated. The **SCA** is also shown in this section. + - TO THE MSC:** A large arrow points from the TCAP section to the MSC at the bottom right. + +Sequence diagram of mobile terminated short message flow between SC, SMS-GMSC, HLR, and MSC. + +NOTE: A sequence of short messages shall have MMS set to 1 in each RP-MT-DATA except the last (last shall have MMS set to 0). Each RP-MT-DATA shall be carried via FORWARD SHORT MESSAGE via TCAP and shall be assigned the same Dialogue Identifier as previous RP-MT-DATAS in the sequence. + +**Figure C.2: Mobile terminated short message** + +![Sequence diagram for mobile terminated short message. It shows the flow of data from a GMSC through an MSC to an MS. The diagram includes layers for SME, RL, and TCAP. Key messages include SEND INFO FOR I/C CALL SET UP (3G TS 29.002), SMS-DELIVER, FORWARD SHORT MESSAGE (3G TS 29.002), SM-RL-DATA-REQUEST (3G TS 24.011), RP-DATA (3G TS 24.011), and MNSMS-EST-REQ (3G TS 24.011).](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +The diagram illustrates the protocol stack and message flow for a mobile terminated short message (MT-SMS). At the top, the **MSC** (Mobile Switching Center) contains the **SME** (Short Message Entity) with fields: MTI, MMS, RP, SRI, OA, PID, DCS, SCTS, UDL, and UD. The **RL** (Relay Layer) contains fields: DI, MR, OC, DA, OA, UD, and MSM. The **TCAP** (Transaction Capabilities Application Part) contains fields: GMSCA, DA, DI, and UD. The **MS** (Mobile Station) contains fields: MTI, MR, OA, UDL + UD, and SCA. + +Message flow: + +- FROM GMSC** to **MSC**: **SEND INFO FOR I/C CALL SET UP (3G TS 29.002)**. This message triggers the setup of a relay link (RL). +- Inside the **MSC**, the **SME** sends an **SMS-DELIVER** message to the **RL**. +- The **RL** sends a **FORWARD SHORT MESSAGE (3G TS 29.002)** message to the **TCAP**. +- The **TCAP** sends a **SM-RL-DATA-REQUEST (3G TS 24.011)** message to the **MSC**. +- The **MSC** sends a **RP-DATA (3G TS 24.011)** message to the **MS**. +- Finally, the **MSC** sends an **MNSMS-EST-REQ (3G TS 24.011)** message to the **MS**. + +Sequence diagram for mobile terminated short message. It shows the flow of data from a GMSC through an MSC to an MS. The diagram includes layers for SME, RL, and TCAP. Key messages include SEND INFO FOR I/C CALL SET UP (3G TS 29.002), SMS-DELIVER, FORWARD SHORT MESSAGE (3G TS 29.002), SM-RL-DATA-REQUEST (3G TS 24.011), RP-DATA (3G TS 24.011), and MNSMS-EST-REQ (3G TS 24.011). + +NOTE: MR is of local significance to the MSC/MS interface and is not the value supplied to the MSC. + +Figure C.3: Mobile terminated short message + +![Diagram of mobile terminated short message protocol stack. The diagram shows the flow of data from the MSC up through the CM, SM-RL, SM-TL, and SM-AL layers. Each layer has a corresponding protocol data unit (PDU) structure shown in boxes. Arrows indicate the mapping of fields between layers. At the top, the Mobile Station contains the SME and SC entities.](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +MOBILE STATION + +SM-AL + +SME SC + +SMI SRI OA SCA RP PID DCS MMS SCTS SM TS-DELIVER.IND + +MTI MMS RP SRI OA PID DCS SCTS UDL UD SMS-DELIVER + +SM-TL + +SMI OA UD SM-RL-DATA-IND (RS-MT-DATA.IND) (3G TS 24.011) + +MTI PRI MR OA UDL + UD RP-DATA (3G TS 24.011) + +SM-RL + +MNSMS-EST-IND (3G TS 24.011) + +CM + +FROM THE MSC + +Diagram of mobile terminated short message protocol stack. The diagram shows the flow of data from the MSC up through the CM, SM-RL, SM-TL, and SM-AL layers. Each layer has a corresponding protocol data unit (PDU) structure shown in boxes. Arrows indicate the mapping of fields between layers. At the top, the Mobile Station contains the SME and SC entities. + +Figure C.4: Mobile terminated short message + +![Protocol stack diagram for SMS MT case showing layers SM-AL, SM-TL, SM-RL, and CM. It details the encapsulation of RP-DATA into RP-ACK or RP-ERROR structures, which are then passed to the CM layer as CP-DATA for transmission to the MSC.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +The diagram illustrates the protocol stack for the MT (Mobile Terminated) case of SMS, showing the flow of data through four layers: SM-AL, SM-TL, SM-RL, and CM. + +- SM-AL (SMS Application Layer):** Contains the **MOBILE STATION** entity. +- SM-TL (SMS Transport Layer):** + - At the top, an **SMS-DELIVER-REPORT** is shown with fields **MTI** and **FCS**. + - Below it, **RP-DATA (3G TS 24.011)** is encapsulated into two structures: + - RP-ACK (3G TS 24.011)** containing **MTI** and **MR** fields. + - RP-ERROR (3G TS 24.011)** containing **MTI**, **MR**, **CS**, and **UD** fields. +- SM-RL (SMS Relaying Layer):** + - The **RP-ACK** and **RP-ERROR** structures are combined into a single block: **RP-ACK OR RP-ERROR**. + - This block is associated with **MNSMS-DATA-REQ (3G TS 24.011)**. +- CM (CM-RL Layer):** + - The **RP-ACK OR RP-ERROR** block is encapsulated into a structure with fields **PDI**, **TID**, **MT**, and **UD**. + - An arrow labeled **TO THE MSC** indicates transmission to the Mobile Switching Center. + - The final output is **CP-DATA (3G TS 24.011)**. + +Protocol stack diagram for SMS MT case showing layers SM-AL, SM-TL, SM-RL, and CM. It details the encapsulation of RP-DATA into RP-ACK or RP-ERROR structures, which are then passed to the CM layer as CP-DATA for transmission to the MSC. + +Figure C.5: Acknowledgement in the MT case + +![Sequence diagram showing the acknowledgement in the MT case across CM, SM-RL, and RL layers. It details the flow of CP-DATA, RP-ACK/ERROR, and SMRL-REPORT-IND messages between the MS and the MSC.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +The diagram illustrates the protocol interaction for an MT case across three layers: CM (Communication Management), SM-RL (SMS-RL), and RL (Relay Layer). + +- CM Layer:** + - A message box labeled **CP-DATA (3G TS 24.011)** contains sub-fields: **PDI**, **TID**, **MT**, and **UD**. + - This message is sent **FROM THE MS** (Mobile Station) to the SM-RL layer. +- SM-RL Layer:** + - The CM layer message is processed into an **RP-ACK OR RP-ERROR** message box. + - This box has two outgoing arrows: + - An arrow pointing left to an **RP-ACK (3G TS 24.011)** message box containing **MTI** and **MR**. + - An arrow pointing right to an **RP-ERROR (3G TS 24.011)** message box containing **MTI**, **MR**, **CS**, and **UD**. +- RL Layer:** + - The **RP-ACK** message is forwarded to a box containing **MTI** and **MR**. + - The **RP-ERROR** message is forwarded to a box containing **MTI**, **MR**, **CS**, and **UD**. + - Both RL layer boxes then point to a higher-level box containing **DI** and **UD**. + - From this **DI/UD** box, a message labeled **SMRL-REPORT-IND (3G TS 24.011)** is sent to the **MSC**. + - There is also a **TCAP** message flow indicated between the left **DI/UD** box and the **MSC**. + - A large arrow at the top points from the **MSC** **TO THE SMS-GMSC**. + +Sequence diagram showing the acknowledgement in the MT case across CM, SM-RL, and RL layers. It details the flow of CP-DATA, RP-ACK/ERROR, and SMRL-REPORT-IND messages between the MS and the MSC. + +NOTE: The cause carried via UD of TCAP is not the cause supplied via RP-ERROR but is the cause resulting from application of the mapping specified by table 8.5 of 24.011[13]. + +**Figure C.6: Acknowledgement in the MT case** + +![Sequence diagram showing the acknowledgement in the MT case. It illustrates the flow of messages between an SMS-GMSC, an MSC, and a Service Center (SC).](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the message flow for an acknowledgement in the MT case: + +- From MSC to SMS-GMSC:** A message is sent from the MSC to the SMS-GMSC. It contains a TCAP layer with DI (Destination Indicator) and UD (User Data). Above the TCAP layer is an SM-RL (SMS-Relay Layer) with SCA (Service Center Address), DA (Destination Address), SMI (SMSC Identifier), and DI (Destination Indicator). The message is labeled "FROM MSC". +- From SMS-GMSC to SC:** The SMS-GMSC sends a message to the SC. This message is labeled "RP-ACK" and contains an SMI (SMSC Identifier). A thick line represents the main message path to "TO THE SC". +- From SC to SMS-GMSC:** The SC sends a response message back to the SMS-GMSC. This message is labeled "RP-ERROR" and contains several fields: SMI, CS (Cause), MWS (Message Waiting Status), MAL (Message Acknowledgement Length), and UD (User Data). A thick line represents the main message path from "TO THE SC". +- From SMS-GMSC to MSC:** The SMS-GMSC sends a "RESULT" message back to the MSC. This message contains a "SET MESSAGE WAITING DATA (3G TS 29.002)" operation. The message is routed through a circular node (representing a switch or router) and then to the MSC. The message contains DI (Destination Indicator) and UD (User Data). + +Sequence diagram showing the acknowledgement in the MT case. It illustrates the flow of messages between an SMS-GMSC, an MSC, and a Service Center (SC). + +NOTE 1: The MAP operation "SetMessageWaitingData" is invoked only if a cause "Absent Subscriber" is carried in TCAP UD. + +NOTE 2: The cause delivered to the SC is not necessarily the cause carried via TCAP but is one of the set specified by table 03.40/1. + +Figure C.7: Acknowledgement in the MT case + +![Sequence diagram showing protocol layer mapping for acknowledgements in the MT case. It shows how parameters like SMI, SoR, MWS, CS, MAL, and UD are passed between RP, RS, and TS layers for both successful reports and error reports.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +SERVICE CENTRE + +The diagram illustrates the mapping of parameters between protocol layers for Mobile Terminated (MT) acknowledgements. A vertical dashed line separates the Service Centre side from the Mobile Station side. The layers shown are SM-RL (Relay Layer) and SM-TL (Transfer Layer). + +**Left side (Successful Acknowledgement):** + +- RP-ACK:** Contains the **SMI** parameter. +- RS-REPORT:** Receives the **SMI** parameter from RP-ACK. +- TS-REPORT:** Receives the **SMI** parameter and adds **SoR**. + +**Right side (Error and Delivery Reports):** + +- RP-ERROR:** Contains parameters **SMI**, **MWS**, **CS**, **MAL**, and **UD**. +- RS-ERROR:** Receives **SMI**, **MWS**, **CS**, **MAL**, and **UD** from RP-ERROR. +- SMS-DELIVER-REPORT:** Maps **MTI** and **FCS** from the RS-ERROR parameters. +- TS-REPORT:** Maps **SMI**, **SoR**, and **MWS** from the RS-ERROR parameters. + +The flow originates **FROM SMS-GMSC** at the bottom, indicated by heavy black arrows pointing into the RP layer. + +Sequence diagram showing protocol layer mapping for acknowledgements in the MT case. It shows how parameters like SMI, SoR, MWS, CS, MAL, and UD are passed between RP, RS, and TS layers for both successful reports and error reports. + +**Figure C.8: Acknowledgement in the MT case** + +![Diagram of mobile originated short message protocol stack showing layers SM-AL, SM-TL, SM-RL, and CM with various data fields like SMI, DA, RP, PID, DCS, VP, SM, MTI, VPF, MR, UDL, and UD.](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram illustrates the protocol stack for a mobile originated short message (SMS) within a **MOBILE STATION**. It shows the mapping of data across different layers: + +- SM-AL (SMS Application Layer):** Contains fields **SME** (SMI, SRI, DA, SCA, RP, PID, DCS, VP, SM) and **SC**. The message is labeled **TS-SUBMIT.REQ**. +- SM-TL (SMS Transport Layer):** Contains fields **SMI**, **DA**, and **UD**. The message is labeled **RS-MO-DATA.REQ (SM-RL-DATA-REQ) (3G TS 24.011)**. +- SM-RL (SMS Relay Layer):** Contains fields **MTI**, **MR**, **DA**, and **UDL + UD**. The message is labeled **RP-DATA (3G TS 24.011)**. +- CM (Connection Management):** Contains the field **RP-DATA**. The message is labeled **MNSMS-EST-REQ (3G TS 24.011)**. This layer connects **TO THE MSC**. + +Intermediate data structures include **SMS-SUBMIT** (MTI, VPF, RP, SRI, MR, DA, PID, DCS, VP, UDL, UD) and **RP-DATA** (MTI, MR, DA, UDL + UD). Arrows indicate the flow and mapping of data between these structures and the protocol layers. + +Diagram of mobile originated short message protocol stack showing layers SM-AL, SM-TL, SM-RL, and CM with various data fields like SMI, DA, RP, PID, DCS, VP, SM, MTI, VPF, MR, UDL, and UD. + +NOTE: The mapping of SMI to MR by the MS is a local matter. + +Figure C.9: Mobile originated short message + +Error! No + +11 + +Error! No text of specified style in + +![Sequence diagram of mobile originated short message (Figure C.10) showing interactions between MS, SCA, MSC, and VLR.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the signaling for a mobile originated short message. It shows the flow of information from the Mobile Station (MS) through the Service Center Address (SCA) to the Mobile Switching Center (MSC) and Visitor Location Register (VLR). + +**Sequence of Events:** + +- FROM THE MS:** A message is sent from the MS to the SCA. The SCA header consists of **MTI**, **MR**, **DA**, and **UDL + UD**. The payload is **MNSMS-EST-IND (RP-DATA) (3G TS 24.011)**. +- SCA to MSC:** The SCA forwards information to the MSC via a **SEND INFO FOR O/G CALL SET UP (3G TS 29.002)** message. This message includes a box with **OA**, **MR**, and **DI**, and an associated **MSISDN**. +- MSC to VLR:** The MSC sends a **COMPLETE CALL (3G TS 29.002)** message to the VLR. +- MSC to SCA (Forwarding):** The MSC also sends a **FORWARD SHORT MESSAGE (3G TS 29.002)** message back to the SCA. This message includes a box with **OC**, **DA**, **OA**, and **UD**, and an associated **MSISDN**. +- SCA to SMS-IWMSC:** Finally, the SCA forwards the message to the SMS-IWMSC via a **TCAP** message. The SCA header for this leg includes **OA**, **GMSCA**, **DI**, and **UD**, with an associated **MSCA**. + +**Protocol Layers:** + +- CM (Connection Management):** The layer between the MS and the SCA. +- SM-RL (SMS Relay Layer):** The layer between the SCA and the MSC/SMS-IWMSC. + +Sequence diagram of mobile originated short message (Figure C.10) showing interactions between MS, SCA, MSC, and VLR. + +Figure C.10: Mobile originated short message + +![Diagram showing the mapping of parameters between TCAP, Forward Short Message, and RP-DATA-MO protocols for a mobile originated short message. Arrows indicate the flow of data: DI from TCAP maps to DI in the top-left box; OA and UD from TCAP map to OA and UD in the Forward Short Message; MR, OA, and UD from the Forward Short Message map to the RP-DATA-MO structure.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +SMS-IWMSC + + + +| | | +|----|----| +| MR | DI | +|----|----| + +| | | | | +|----|-----|--------|----| +| OC | DA | OA | UD | +| | SCA | MSISDN | | + +FORWARD +SHORT MESSAGE +(3G TS 29.002) + +--- + +TC-BEGIN + +| | | | | +|----|--------|----|----| +| OA | IWMSCA | DI | UD | +|----|--------|----|----| + +TCAP + +| | | | +|----|----|----| +| MR | OA | UD | +|----|----|----| + +RP-DATA-MO + +SM-RL + +--- + +FROM THE MSC +**↑** + +TO THE SC +**→** + +Diagram showing the mapping of parameters between TCAP, Forward Short Message, and RP-DATA-MO protocols for a mobile originated short message. Arrows indicate the flow of data: DI from TCAP maps to DI in the top-left box; OA and UD from TCAP map to OA and UD in the Forward Short Message; MR, OA, and UD from the Forward Short Message map to the RP-DATA-MO structure. + +NOTE: MR is of local significance to the IWMSC/SC interface and is not the value supplied by the MS via the MS/MSC interface. + +**Figure C.11: Mobile originated short message** + +![Diagram of mobile originated short message layers: SM-AL, SM-TL, SM-RL. It shows the mapping of fields like SMI, SRI, DA, OA, PID, DCS, VP, SM, MTI, VPF, RP, MR, UDL, and UD between these layers and the SERVICE CENTRE.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +The diagram illustrates the protocol layers for a mobile originated short message, showing the mapping of fields between the Service Centre and the mobile station across three layers: SM-AL, SM-TL, and SM-RL. + +- SM-AL (Service Centre Layer):** Contains a box labeled "SERVICE CENTRE". Below it, the "TS-SUBMIT.IND" message structure is shown with fields: SMI, SRI, DA, OA, PID, DCS, VP, and SM. Above the DA, OA, and PID fields is the label "SME MSISDN". +- SM-TL (Transport Layer):** Contains the "SMS-SUBMIT" message structure with fields: MTI, VPF, RP, SRI, MR, DA, PID, DCS, VP, UDL, and UD. Arrows indicate mapping from TS-SUBMIT.IND fields to SMS-SUBMIT fields: SMI to MTI, SRI to SRI, DA to DA, OA to OA, PID to PID, DCS to DCS, VP to VP, and SM to UD. +- SM-RL (Relay Layer):** Contains two message structures. The "RS-MO-DATA.IND" structure has fields: SMI, OA, and UD. The "RP-MO-DATA" structure has fields: MR, OA, and UD. Arrows indicate mapping from SMS-SUBMIT fields to RS-MO-DATA.IND fields: MTI to SMI, VPF to OA, RP to MR, SRI to SMI, MR to OA, DA to OA, PID to OA, DCS to OA, VP to OA, UDL to UD, and UD to UD. A large arrow points from "FROM THE SMS-IWMSC" to the RP-MO-DATA structure. + +Diagram of mobile originated short message layers: SM-AL, SM-TL, SM-RL. It shows the mapping of fields like SMI, SRI, DA, OA, PID, DCS, VP, SM, MTI, VPF, RP, MR, UDL, and UD between these layers and the SERVICE CENTRE. + +Figure C.12: Mobile originated short message + +![Sequence diagram for SMS MO acknowledgement. Lifelines: SERVICE CENTRE, MR (on the left), and MR, CS, UD (on the right). The diagram shows the flow of messages between the MR and the SERVICE CENTRE, with a callout for SMS-SUBMIT-REPORT details.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates the interaction for an SMS MO acknowledgement. At the top center is a box labeled "SERVICE CENTRE". Below it, on the left, is a box labeled "MR". On the right, there is a group of three boxes labeled "MR", "CS", and "UD". Above the "UD" box is another group of two boxes labeled "MTI" and "FCS", with dotted lines connecting them to the "SMS-SUBMIT-REPORT" text. A horizontal line labeled "SM-RL" spans the width of the diagram. A vertical line descends from the "MR" box on the left. A vertical line descends from the "MR" box in the group on the right. A horizontal arrow points from the right vertical line to the right, labeled "TO THE SMS-IWMSC". The text "RP-ACK" is positioned above the left vertical line. The text "RP-ERROR" is positioned above the right vertical line. + +Sequence diagram for SMS MO acknowledgement. Lifelines: SERVICE CENTRE, MR (on the left), and MR, CS, UD (on the right). The diagram shows the flow of messages between the MR and the SERVICE CENTRE, with a callout for SMS-SUBMIT-REPORT details. + +Figure C.13: Acknowledgement in the MO case + +![Sequence diagram for SMS-IWMSC acknowledgement in the MO case. The diagram shows messages (RP-ACK, RP-ERROR, MR, CS, UD, DI, TCAP) being exchanged between 'FROM THE SC' and 'TO THE MSC' via an 'SMS-IWMSC' block. A top box contains MR and DI fields.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +SMS-IWMSC + +The diagram illustrates the acknowledgement process in the Mobile Originated (MO) case for SMS-IWMSC. + At the top left, a dashed box contains fields **MR** and **DI**. + Below, a horizontal line separates the upper logic from the transport layer. + The flow 'FROM THE SC' is represented by a thick black line on the left, and 'TO THE MSC' is on the right. + Vertical arrows connect the transport lines to protocol blocks: + - **RP-ACK** is associated with an **MR** block. + - **RP-ERROR** is associated with a combined **MR**, **CS**, and **UD** block. + - **TCAP** messages are associated with **DI** and **UD** blocks. + Lines connect these protocol blocks back to the **MR** and **DI** fields at the top, indicating mapping or reference. + +Sequence diagram for SMS-IWMSC acknowledgement in the MO case. The diagram shows messages (RP-ACK, RP-ERROR, MR, CS, UD, DI, TCAP) being exchanged between 'FROM THE SC' and 'TO THE MSC' via an 'SMS-IWMSC' block. A top box contains MR and DI fields. + +**Figure C.14: Acknowledgement in the MO case** + +![Sequence diagram for SMS MO acknowledgement. The diagram shows the interaction between an SMS-IWMSC and an MSC across three layers: SM-TL, SM-RL, and SM-CM. The process starts with data from the SMS-IWMSC, which is encapsulated in TCAP and sent to the MSC. The MSC then uses SM-RL to send an SM-RL-REPORT-REQ to the SM-TL layer. The SM-TL layer generates an RP-ACK or RP-ERROR. If it's an RP-ACK, it's sent back via SM-RL as an RP-ACK. If it's an RP-ERROR, it's sent via SM-RL as an RP-ERROR, which then triggers an MN SMS-DATA-REQ to the SM-TL layer. Finally, the SM-TL layer encapsulates the data in CP-DATA and sends it to the MS. Return paths for acknowledgements are shown at the top of the diagram.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram illustrates the acknowledgement process for a Mobile Originated (MO) SMS. It is divided into three horizontal layers: SM-TL (top), SM-RL (middle), and SM-CM (bottom). + +- Input:** Data arrives "FROM THE SMS-IWMSC" at the bottom. It is processed through a TCAP layer, resulting in a "DI" (Delivery Indicator) or "DI" and "UD" (User Data) message. +- SM-CM to SM-RL:** These messages are passed up to the SM-RL layer. +- SM-RL to SM-TL:** The SM-RL layer sends an "SM-RL-REPORT-REQ (3G TS 24.011)" message to the SM-TL layer. +- SM-TL Processing:** The SM-TL layer generates an "RP-ACK OR RP-ERROR" response. + - If it is an "RP-ACK (3G TS 24.011)", it contains an "MR" (Message Reference) and is sent back down through the SM-RL layer. + - If it is an "RP-ERROR (3G TS 24.011)", it contains "MR", "CS" (Coding Scheme), and "UD" (User Data). This triggers an "MN SMS-DATA-REQ (3G TS 24.011)" message from the SM-TL layer back to the SM-RL layer. +- SM-TL to SM-CM:** Both the RP-ACK and the MN SMS-DATA-REQ result in a "CP-DATA (3G TS 24.011)" message at the SM-TL layer, which contains "PDI", "TID", "MT", and "UD". This is then sent "TO THE MS" (Mobile Station) at the bottom. +- Return Paths:** At the top, two return paths are shown: one from the "RP-ACK OR RP-ERROR" box back to the "OA MR DI" box, and another from the "MR CS UD" box back to the "DI UD" box. + +Sequence diagram for SMS MO acknowledgement. The diagram shows the interaction between an SMS-IWMSC and an MSC across three layers: SM-TL, SM-RL, and SM-CM. The process starts with data from the SMS-IWMSC, which is encapsulated in TCAP and sent to the MSC. The MSC then uses SM-RL to send an SM-RL-REPORT-REQ to the SM-TL layer. The SM-TL layer generates an RP-ACK or RP-ERROR. If it's an RP-ACK, it's sent back via SM-RL as an RP-ACK. If it's an RP-ERROR, it's sent via SM-RL as an RP-ERROR, which then triggers an MN SMS-DATA-REQ to the SM-TL layer. Finally, the SM-TL layer encapsulates the data in CP-DATA and sends it to the MS. Return paths for acknowledgements are shown at the top of the diagram. + +Figure C.15: Acknowledgement in the MO case + +![Sequence diagram showing the protocol stack and message flow for acknowledgement in the MO case across SM-TL, SM-RL, and CM layers.](8307f6b04df072c9332f9987e034272c_img.jpg) + +The diagram illustrates the protocol stack and message flow for an acknowledgement in the Mobile Originated (MO) case within a Mobile Station. It is divided into three horizontal layers: SM-TL (top), SM-RL (middle), and CM (bottom). + +MOBILE STATION + +--- + +**SM-TL Layer** + +TS-REPORT.IND [SMI | SoR]          [SMI | SoR] TS-REPORT.IND + +[MTI | FCS] SMS-SUBMIT-REPORT + +--- + +**SM-RL Layer** + +SM-RL-REPORT-IND [SMI]          [SM | CS | UD] SM-RL-REPORT-IND + +RP-ACK [MTI | MR]          [MTI | MR | CS | UD] RP-ERROR + +RP-ACK OR RP-ERROR + +MNSMS-DATA-IND (3G TS 24.011) + +--- + +**CM Layer** + +CP-DATA (3G TS 24.011) + +FROM THE MSC + +*Description of flow:* A CP-DATA message arrives from the MSC at the CM layer. It is passed to the SM-RL layer as an MNSMS-DATA-IND. The SM-RL layer interprets this as either an RP-ACK or an RP-ERROR. + +- If **RP-ACK**: It contains MTI and MR fields. It triggers an SM-RL-REPORT-IND with an SMI field, which is then passed to the SM-TL layer as a TS-REPORT.IND containing SMI and SoR. + +- If **RP-ERROR**: It contains MTI, MR, CS, and UD fields. This triggers an SM-RL-REPORT-IND containing SM, CS, and UD fields. This is further mapped to an SMS-SUBMIT-REPORT (MTI, FCS) and finally a TS-REPORT.IND (SMI, SoR) at the SM-TL layer. + +Sequence diagram showing the protocol stack and message flow for acknowledgement in the MO case across SM-TL, SM-RL, and CM layers. + +**Figure C.16: Acknowledgement in the MO case** + +# --- Annex D (informative): Mobile Station reply procedures + +## D.1 Introduction + +The reply procedures specified in this annex should be followed by a mobile station when replying to a short message, i.e. when generating a MO SM in response to a received MT SM, addressed to the originator of that MT SM. The main purpose of this annex is to specify how the MS selects the service centre for delivering that MO SM: an arbitrary SME may only be reached by submitting the reply SM to a specific SC, known to be able of delivering to that SME. + +## --- D.2 The scope of applicability + +The reply procedures in clauses 5 and 6 of this annex should be followed by every MS which fulfils the following criteria: + +- 1) The MS automatically selects the value for the RP-Destination-Address parameter in RP-MO-DATA, or the MS has the SC address within the SM-RL entity. (That is to say: the human user is not obliged to manually key in the SC address for every MO short message). +- 2) The MS or an application within it supports some form of replying to a MT SM with a MO SM. (That is to say: in the process of generating the reply MO SM, any reference whatsoever, implicit or explicit, is made to the original MT SM). +- 3) The replying support of (2) is to be equally available towards every SME. + +When an SME submits an SM to an SC for delivery, it may request that the SC sets the TP-Reply-Path parameter in the SM to be delivered. If the submitting SME is an MS, the reply path requesting procedure; in clause 4 of this annex may be applied. However, an SC may support the reply procedures without supporting the reply path requesting procedure; in that case, the SC sets the TP-Reply-Path parameter on another basis, which must be the case if the SM originates from an SME which is not an MS. + +## --- D.3 Terminology + +An originating SME submits an original SM to an original SC, which delivers the original MT SM to a replying MS. The replying MS sends back a reply MO SM, a MO SM which is generated (automatically or by human operations) in response to the original MT SM, and which is addressed to the originating SME. + +If the originating SME is an MS, the original MT SM is submitted within an SMS-SUBMIT PDU; we say that reply path is requested if the TP-Reply-Path parameter is set in the SMS-SUBMIT PDU of the original MT SM. + +We say that reply path exists if the TP-Reply-Path parameter was set in the SMS-DELIVER PDU of the original MT SM; we say that reply path does not exist otherwise. + +The replying MS may have a default SC which is normally used for delivering all the MO short messages originated from the replying MS. Alternatively, a human user or automatic application may specify a selected SC for delivering a particular SM (thus the term selected SC refers to an SC address selected for one short message only). + +## --- D.4 The reply path requesting procedure + +The discussion in this clause applies to cases when the originating SME is a mobile station only. The reply procedures discussed in the clauses to follow this one are independent of the type of the originating SME. + +The reply path is requested by the originating SME (an MS) by setting the TP-Reply-Path parameter in the SMS SUBMIT PDU of the original SM. If the original SC supports reply path requesting for the originating SME (an MS), it shall take notice of the TP-Reply-Path parameter in the SMS-SUBMIT PDU and set the TP-Reply-Path parameter in the SMS-DELIVER PDU of the original MT SM towards the replying MS. Hence, reply path exists for the replying MS towards the originating SME (an MS). + +## --- D.5 The reception of an original MT SM + +When a replying MS receives an original MT SM, it then has: + +- 1) originating SME = TP-Originating-Address in the SMS-DELIVER PDU, +- 2) original SC = RP-Originating-Address in RPS-MT-DATA, and +- 3) reply path exists/reply path does not exist = TP-Reply-Path in SMS-DELIVER PDU (set/not set). + +## --- D.6 The submission of the reply MO SM + +According to clause 5, the replying MS knows if: + +- a) reply path exists; or +- b) reply path does not exist. + +We then specify that when submitting the reply MO SM, the replying MS should use parameters as follows: + +- 1) TP-Destination-Address in SMS-SUBMIT PDU = originating SME, +- 2a) If reply path exists: + +RP-Destination-Address in RP-MO-DATA = original SC, + +- 2b) If reply path does not exist: + +RP-Destination-Address in RS-MO-DATA = selected SC or default SC or original SC, + +- 3a) If reply path exists: + +after submitting one reply MO SM, the reply path does not exist any more. + +In case (2b), it is allowed to use the original SC or the default SC, but then there is no guarantee that the original/default SC shall deliver the reply MO SM. (The original SC may refuse to deliver, if the replying MS is not its subscriber; the default SC may be unable to deliver, if it has no access path to the originating SME.) + +Requirement (3a) states that the case (a), reply path exists, holds for one reply MO SM only (per original MT SM). + +## --- D.7 Usage of SCs for replying + +The specification in this annex supports the following way of replying. + +The original MT SM and the reply MO SM are delivered by the same SC, the original SC. This principle maximizes the probability that the SC can e.g. route the reply MO SM to the proper data network for reaching the originating SME; this principle is a must, if the originating SME is integrated within the original SC. + +If the original SC by any means whatsoever knows that it is both willing and able to deliver one (potential) reply MO SM, it may indicate this fact by setting the TP-Reply-Path parameter in the original MT SM. The original SC thus commits itself to delivering one reply MO SM; let us call this reply delivery commitment. + +One reason for the SC to make the reply delivery commitment may be the reply path requesting procedure specified in clause 4 on this annex. + +The reply path commitment is not valid forever, but the original SC may have e.g. a time limit for maintaining this commitment. + +## --- D.8 Replying possibilities for Phase 1 mobile stations + +The Phase 2 mobile stations should support the procedures in this annex (if they fulfil the criteria in clause 2 of it). Yet, Phase 1 mobile stations, too, may apply steps (1) and (2a) in clause 6 of this annex, i.e. reply via the original SC, + +automatically or manually (by choosing selected SC = original SC), despite the fact that the TP-Reply-Path parameter shall be ignored by them. The delivery of the reply MO SM cannot be guaranteed in this case, yet the possibility of delivery may be improved (especially if the originating SME is not an MS). + +## --- D.9 The resulting service for originating SMEs + +As the consequence of the replying procedures specified in this annex, all SMEs and applications within them may assume that replying from all mobile stations is always possible, provided that the mobile stations do support the proper replying mechanism itself (human response in context with the original MT SM, automatic replying by an application, application level protocols, etc.). + +# --- Annex E (normative): Extended Object Format Type + +## E.1 Predefined Sound + +The predefined sound as integrated in the Extended Object IE is structured as follows: + +Octet 8 Sound number as defined in table of subclause 9.2.3.24.10.3.1. + +--- + +## E.2 iMelody + +An iMelody object [33] can be integrated in an Extended Object IE with the following structure: + +Octet 8..n iMelody object coded according to the iMelody format [33]. + +--- + +## E.3 Black and white bitmap + +The user-defined black and white bitmap as integrated in the Extended Object IE is structured as follows: + +Octet 8 Horizontal dimension of picture. +This octet shall contain the horizontal number of pixels + +Octet 9 Vertical dimension of picture. +This octet shall contain the vertical number of pixels. + +Octet 10..n Picture data, pixel by pixel from top left to bottom right. The picture data is encoded as a continuous sequence of bits. There shall be no fill bits at the end of each row of data, Fill bits may only be used in the last octet of the picture data if needed. The fill bits in the last octet shall be ignored. Within each octet the MSB represents the leftmost pixel. + +The colour values are encoded as follows: + +| Bit Value | Colour | +|-----------|--------| +| 0 | White | +| 1 | Black | + +--- + +## E.4 2-bit greyscale bitmap + +The user-defined 2-bit greyscale bitmap as integrated in the Extended Object IE is structured as follows: + +Octet 8 Horizontal dimension of picture. +This octet shall contain the horizontal number of pixels + +Octet 9 Vertical dimension of picture. +This octet shall contain the vertical number of pixels. + +Octet 10..n Picture data, pixel by pixel from top left to bottom right. The picture data is encoded as a continuous sequence of bits. There shall be no fill bits at the end of each row of data, Fill bits may only be used in the last octet of the picture data. The fill bits in the last octet shall be ignored. The pair of bits at the MSB represents the leftmost pixel of the four defined in an octet. + +The colour values are encoded as follows: + +| Bit Value | Colour | +|-----------|------------| +| 00 | Black | +| 01 | Dark Grey | +| 10 | Light Grey | +| 11 | White | + +## E.5 6-bit colour bitmap + +The user-defined 6-bit colour bitmap as integrated in the Extended Object IE is structured as follows: + +Octet 8 Horizontal dimension of picture. +This octet shall contain the horizontal number of pixels + +Octet 9 Vertical dimension of picture. +This octet shall contain the vertical number of pixels. + +Octet 10..n. + +Picture data, pixel by pixel from top left to bottom right. The picture data is encoded as a continuous sequence of bits. There shall be no fill bits at the end of each row of data, Fill bits may only be used in the last octet of the picture data. The fill bits in the last octet shall be ignored. + +Each pixel colour is represented by 6-bits of data, giving a total of 64 colours. (2 bits of data define the levels of each red, green and blue). The overall pixel colour is a composite of the three RGB values. + +The first pair of bits of picture data define the level of red of the topmost, leftmost pixel, the next pair of bits the level of green for this pixel, and the third pair the level of blue for the pixel. The first bit of a pair defining a colour level is the MSB. This is illustrated below. + +| Octet 1 | | | | | | | | +|---------|---------|-----------|-----------|----------|----------|---------|---------| +| Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | Bit 0 | +| MSB Red | LSB Red | MSB Green | LSB Green | MSB Blue | LSB Blue | MSB Red | LSB Red | +| Pixel 1 | Pixel 1 | Pixel 1 | Pixel 1 | Pixel 1 | Pixel 1 | Pixel 2 | Pixel 2 | + + + +| Octet 2 | | | | | | | | +|-----------|-----------|----------|----------|---------|---------|-----------|-----------| +| Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | Bit 0 | +| MSB Green | LSB Green | MSB Blue | LSB Blue | MSB Red | LSB Red | MSB Green | LSB Green | +| Pixel 2 | Pixel 2 | Pixel 2 | Pixel 2 | Pixel 3 | Pixel 3 | Pixel 3 | Pixel 3 | + +## E.6 Predefined animation + +The predefined animation as integrated in the Extended Object IE is structured as follows: + +Octet 8 Animation number as defined in table of subclause 9.2.3.24.10.3.3. + +## E.7 Black and white bitmap animation + +The user-black and white animation is integrated in the Extended Object IE is structured as follows: + +Octet 8 Horizontal dimension of picture. +This octet shall contain the horizontal number of pixels. + +Octet 9 Vertical dimension of picture. +This octet shall contain the vertical number of pixels. + +Octet 10 The number of frames in the animation. + +Octet 11 Animation control byte. + +| Bits | Meaning | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------| +| 7 – 4 | Frame display. The value (in tenths of a second) that is requested between each frame: 0000 1 tenth (i.e. 0.1s) 1111 16 tenths (i.e. 1.6 s) | +| 3 – 0 | Repeat value. The requested number of repetitions of the animation: 0000 Unlimited repetition 0001 1 repetition 1111 15 repetitions | + +Octet 12..n Contains a series of bitstreams encoding 1 bit pixel depth bitmaps as defined in F.3. If a frame in the animation would require fill bits (as described in F.3) these shall be contained at the end of the frame such that the bitstream for the next frame begins on an octet boundary. + +## E.8 2-bit greyscale bitmap animation + +The user-black and white animation is integrated in the Extended Object IE is structured as follows: + +- Octet 8 Horizontal dimension of picture. +This octet shall contain the horizontal number of pixels. +- Octet 9 Vertical dimension of picture. +This octet shall contain the vertical number of pixels. +- Octet 10 The number of frames in the animation. +- Octet 11 Animation control byte. + +| Bits | Meaning | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------| +| 7 – 4 | Frame display. The value (in tenths of a second) that is requested between each frame: 0000 1 tenth (i.e. 0.1s) 1111 16 tenths (i.e. 1.6 s) | +| 3 – 0 | Repeat value. The requested number of repetitions of the animation: 0000 Unlimited repetition 0001 1 repetition 1111 15 repetitions | + +Octet 12..n Contains a series of bitstreams encoding 2 bit pixel depth bitmaps as defined in F.4. If a frame in the animation would require fill bits (as described in F.4) these shall be contained at the end of the frame such that the bitstream for the next frame begins on an octet boundary. + +## E.9 6-bit colour bitmap animation + +The user-black and white animation is integrated in the Extended Object IE is structured as follows: + +- Octet 8 Horizontal dimension of picture. +This octet shall contain the horizontal number of pixels. +- Octet 9 Vertical dimension of picture. +This octet shall contain the vertical number of pixels. +- Octet 10 The number of frames in the animation. +- Octet 11 Animation control byte. + +| Bits | Meaning | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------| +| 7 – 4 | Frame display. The value (in tenths of a second) that is requested between each frame: 0000 1 tenth (i.e. 0.1s) 1111 16 tenths (i.e. 1.6 s) | +| 3 – 0 | Repeat value. The requested number of repetitions of the animation: 0000 Unlimited repetition 0001 1 repetition 1111 15 repetitions | + +Octet 12..n Contains a series of bitstreams encoding 6 bit pixel depth bitmaps as defined in F.5. If a frame in the animation would require fill bits (as described in F.5) these shall be contained at the end of the frame such that the bitstream for the next frame begins on an octet boundary. + +## --- E.10 vCard + +A vCard object [36] can be integrated in a Extended Object IE with the following structure: + +Octet 8.n      vCard object as defined in [36]. The UTF-8 encoding is used instead of the default 7-bit ASCII. For certain vCard properties, other encoding can be used by setting the CHARSET property parameter to the appropriate character set. + +--- + +## E.11 vCalendar + +A vCalendar object [37] can be integrated in a Extended Object IE with the following structure: + +Octet 8..n vCalendar object as defined in [37]. The UTF-8 encoding is used instead of the default 7-bit ASCII. For certain vCalendar properties, other encoding can be used by setting the CHARSET property parameter to the appropriate character set. + +## --- E.12 Data Format Delivery Request + +This Data Format Delivery Request is an optional feature used by an SME to indicate which Extended Object data formats, listed in subclause 9.2.3.24.10.1.11, it is requesting for delivery. This Data Format Delivery Request may be included by an SME in a MO SM containing other EMS related data, or in a MO SM independently. Processing of this data format is optional in a MT short message. + +The information in this data format represents an extensible bit field with the first bit being mapped to the first Extended Object (EO) data format defined in the table in subclause 9.2.3.24.10.1.11. + +Octet 8 + +Bit 0: If set to 1 indicates support for EO data format 00 + +Bit 1: If set to 1 indicates support for EO data format 01 + +Bit 2: If set to 1 indicates support for EO data format 02 + +..... + +..... + +Octet n + +Bit 0: If set indicates support for EO data format $((n - 8) * 8)$ + +Bit 1: If set indicates support for EO data format $((n - 8) * 8) + 1$ + +Bit 2: If set indicates support for EO data format $((n - 8) * 8) + 2$ + +..... + +Any unused bits in the last octet shall be set to zero. + +## --- E.13 Standard WVG Object + +The Standard WVG object as defined by Format Type 0x0B in the Extended Object IE is as follows. + +Octet 8..n Standard WVG object bit stream + +The unused bits in the last octet will be filled with 0 + +The detailed data format and attributes of Standard WVG object are defined in Annex G. + +The bit order is defined as follows: + +The octet with a smaller octet number stores the bits appearing in the front position in the bit stream; the most significant bit in an octet stores the first bit in position in a 8-bit segment in the bit stream. + +A Standard WVG object may or may not have fixed size. In either case, display size should be determined by the terminal implementation. Recommended display size is a largest possible size on terminal screen while aspect ratio shall be maintained. + +## --- E.14 Polyphonic melody + +A Polyphonic melody can be integrated as an extended object in one or more short messages. Informative guidelines for the creation of polyphony content using SP-MIDI [38] are listed in Annex H. + +However, in order to guarantee the interoperability with legacy mobile devices which are not able to interpret specific SP-MIDI content, the following considerations shall be taken into account for content creation: + +- When content is not provided in SP-MIDI format the presence of the MIP table in polyphonic extended objects is not mandatory. Since a receiving SME supporting polyphonic extended objects may decide to ignore and skip the content of a MIP message by implementing its own note stealing or channel masking strategy when played. However, when SP-MIDI format data is present and the message is stored and subject to potential forwarding, the specific SP-MIDI content shall be kept as received by the SME. +- the additional rhythm channel as specified in subclause 3.2 in [38] might not be supported by the receiving SME. + +Octet 8..n                SMF as defined in [38], [40] + +# Annex F (informative) : Compression methods for EMS + +## F.1 LZSS compression + +### F.1.1 Introduction + +The LZSS compression algorithm is one of a number of compression algorithms generally referred to as “Dictionary Methods”. These algorithms rely upon the fact that (in general) an input data buffer will contain repeating “patterns” or matching sequences of bytes. + +The algorithms fall into 2 groups. Systems like LZ78 and LZW scan an input buffer and construct a “dictionary” of the most commonly occurring byte sequences or “phrases”. This dictionary is pre-pended with the compressed data and the compressed data comprises an array of indices into the dictionary. + +A second set is a modification of this in that the data dictionary is implicit in the uncompressed data buffer. All are based upon an algorithm developed and published in 1977 by Abraham Lempel and Jakob Ziv [LZ77](#). A refinement of this algorithm, which is the basis for practically all the later methods in this group, is the [LZSS](#) algorithm developed in 1982 by Storer and Szymanski. These methods try to find if the character sequence currently being compressed has already occurred earlier in the input data and then, instead of repeating it, output only a pointer to the earlier occurrence. This is illustrated in the following diagram: + +![Diagram showing arrows from the Input Stream to the Output Stream. The first six characters A, B, C, D, E, F map directly down. The second sequence of A, B, C, D, E in the input stream is represented by 'Ptr' in the output stream. An arrow from 'Ptr' loops back to the start of the output stream (A). The final 'G' maps directly down.](f89631cc38aa971e8d15cbffe28f1183_img.jpg) + +**Input Stream** + +| | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---| +| A | B | C | D | E | F | A | B | C | D | E | G | +|---|---|---|---|---|---|---|---|---|---|---|---| + + + + +| | | | | | | | | +|---|---|---|---|---|---|-----|---| +| A | B | C | D | E | F | Ptr | G | +|---|---|---|---|---|---|-----|---| + +**Output Stream** + +Diagram showing arrows from the Input Stream to the Output Stream. The first six characters A, B, C, D, E, F map directly down. The second sequence of A, B, C, D, E in the input stream is represented by 'Ptr' in the output stream. An arrow from 'Ptr' loops back to the start of the output stream (A). The final 'G' maps directly down. + +**Figure F.1 Illustration of “Implicit Dictionary” compression methods** + +### F.1.2 LZSS Basic Algorithm + +The algorithm searches the window (a buffer moving back from the current position in the input data). It searches for the longest match with the beginning of the look-ahead buffer (a buffer moving forward from the current position in the input data) and outputs a pointer to that match. This pointer indicates a position and length of that data match. It is referred to here as a “Slice Descriptor”. + +Since it is possible that not even a one-character match can be found, the output cannot contain just pointers. Accordingly at times it is necessary to write literal octets into the output buffer. A block of literal octets is preceded by a “Literal Block Identifier” which indicates the length of the literal octet sequence that follows. + +### F.1.3 Informative Example. + +The following is provided as an informative example using the input buffer shown below. + +| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | +|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| 0x01 | 0x02 | 0x03 | 0x01 | 0x02 | 0x03 | 0x04 | 0x01 | 0x02 | 0x03 | 0x01 | 0x02 | 0x03 | 0x01 | 0x02 | 0x03 | + +Figure F.2 Sample input buffer (16 octets long) + +#### **Step 1:** + +Starting position is byte 1 in the input buffer. For octets 1 to 3 there are no octet matches in the window for the look-ahead buffer. So write a literal octet sequence of 3 octets following a literal block header. + +| 1 | 2 | 3 | 4 | +|------|------|------|------| +| 0x83 | 0x01 | 0x02 | 0x03 | + +Figure F.3 Output buffer after initial literal block is written + +#### **Step 2:** + +Current position is octet 4. Examining the look-ahead buffer and the window a 3 octet match is found beginning 3 octets before (octet 1) and of 3 octets in length. A 2 octet slice descriptor is added to the output buffer. The current position moves to octet 7 of the input buffer. + +| 1 | 2 | 3 | 4 | 5 | 6 | +|------|------|------|------|------|------| +| 0x83 | 0x01 | 0x02 | 0x03 | 0x06 | 0x03 | + +Figure F.4 Output buffer after the first slice descriptor is written + +#### **Step 3:** + +Current position is octet 7 in the input buffer (0x04). There are no matches in the window for this value so a 2 octet literal sequence is written to the end of the output buffer. The current position moves to octet 8 of the input buffer. + +| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|------|------|------|------|------|------|------|------| +| 0x83 | 0x01 | 0x02 | 0x03 | 0x06 | 0x03 | 0x81 | 0x04 | + +Figure F.5 Second literal block is written into output buffer + +#### **Step 4:** + +Current position is octet 8 of the input buffer. Comparing the window with the look-ahead buffer reveals a octet match from the current position with octets 1 to 6 of the input buffer. That is a 6 octet sequence beginning 7 octets back from the current position.. A two-octet slice descriptor for this match is added to the output buffer. The current position moves to octet 14 of the input buffer (6 octets further on). + +| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | +|------|------|------|------|------|------|------|------|------|------| +| 0x83 | 0x01 | 0x02 | 0x03 | 0x06 | 0x03 | 0x81 | 0x04 | 0x0C | 0x07 | + +Figure F.6 Octet match slice descriptor is written into output buffer + +#### **Step 5:** + +Current position is octet 14 of the input buffer. Comparing the window with the look-ahead buffer reveals another 3 octet sequence match (0x01, 0x02, 0x03). This octet sequence occurs several times in the window within the 511 octets that the slice descriptor allows. Therefore several different (but valid) slice descriptors could be written (this would be implementation dependent). However in this example we will reference the initial 3 octets of the input buffer and write a slice descriptor indicating a 3 octet match beginning 13 octets behind the current position. + +| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | +|------|------|------|------|------|------|------|------|----------|----------|----------|----------| +| 0x83 | 0x01 | 0x02 | 0x03 | 0x06 | 0x03 | 0x81 | 0x04 | 0x0
C | 0x0
7 | 0x0
6 | 0x0
D | + +**Figure F.7 Octet match slice descriptor is written into output buffer: the final output buffer** + +# --- Annex G (normative): WVG (Wireless Vector Graphics) data format + +WVG (Wireless Vector Graphics) is a compact binary data format for vector graphics. WVG data is represented by a bit stream, composed of a header, codec parameters and graphical elements. The bit representation of the drawing and contained graphical elements is designed such that the bit stream can be optimized for smallest possible size. + +--- + +## G.1 Introduction + +### G.1.1 Standard and Character Size WVG elements + +A Standard WVG element is defined by the complete WVG specification. Using a set of the WVG specification with a set of default values, a simplified vector graphics can be used to represent a simple and small vector graphics or glyph. Character Size WVG elements can be included in normal text to represent a handwritten character or symbols that are not supported by character coding system and the font library. + +### G.1.2 Compression methods + +A combination of compression methods is used in the WVG to achieve the best compression ratio for simple vector graphics and animations. They include: + +- **switchable linear or non-linear coordination system:** when graphical elements in a drawing are not evenly distributed, the representation of coordinates can be optimized using a non-linear coordinate system (uneven coordinates) +- **bit packing:** variable number of bits to represent a number. The number of bits used in WVG can vary from 1 bit to 16 bits. +- **local envelope:** use a dedicated coordinate system to describe elements in a small area using relatively small coordinate numbers +- **variable resolution:** in coordinates, sizes, angles, scale and etc, different resolutions can be used for a graphical element to save the number of bits needed for representing a value. +- **palettes:** color and element ID can be mapped using a palette defined in the drawing header. This also saves the number of bits for representing a color value and an element ID. +- **default values:** many values can be omitted to use default values. E.g. when no color scheme is defined, the data describes a mono drawing +- **default animation timing:** in addition to standard time based animation, WVG uses a simplified animation model. In Simple Animation mode, no timing is needed for describing animations. Instead, a cycle is defined to describe the timing for these animations. + +### G.1.3 Coordinate Systems + +There are two coordinate systems used in WVG, namely Compact Coordinate System and Flat Coordinate System. + +#### G.1.3.1 Compact Coordinate System + +In compact coordinate system, a drawing area is defined as rectangle area called envelope. There are two types of envelopes, global envelope and local envelope. The global envelope is a base area in which the drawing is contained. There is only one global envelope. A local envelope is a square area completely or partially within the global envelope. There is no specific global envelope size specified in the data format. The physical display size is decided at rendering time. + +The aspect ratio and orientation are defined in the data header and should be maintained when the drawing is displayed. + +Aspect ratios include 1:1, 4:3, 16:9 up to 1024: 729 (height:width), in both portrait and landscape orientation. Aspect ratio for Characters Size WVG elements only has landscape orientation. + +![Diagram of a Compact Coordinate System grid showing Local and Global Envelopes.](a6a8016b231533e7f34b550f4676afc6_img.jpg) + +The diagram illustrates a 2D coordinate system with a grid. The origin is labeled $(0, 0)$ at the top-left corner. The bottom-right corner is labeled $(1, 1)$ . A dashed rectangle, labeled "Local Envelope", is nested within the grid, starting from an internal point $(0, 0)$ and ending at $(1, 1)$ . A dotted rectangle, labeled "Global Envelope", represents the outer boundary of the grid. Arrows indicate the positive directions of the x and y axes. + +Diagram of a Compact Coordinate System grid showing Local and Global Envelopes. + +In Compact Coordinate System, coordinates are restricted to certain positions which are the cross points of a grid. The grid is defined in the WVG data header, set by a group of parameters. The grid lines along with x axis or y axis may be unevenly distributed. + +The global grid can be described using a curve shown above. + +![Diagram of a curve on a grid with Peak and Valley parameters.](01da0d212fb571933f10f96556157745_img.jpg) + +The diagram shows a step-function curve on a grid. The horizontal axis is labeled "X Axis" and has a value of $1.0$ at the right end. The curve features a central high-value peak and two lower-value side valleys. The "Peak Position" is marked on the x-axis at the center of the peak, and the "Peak value" is indicated by a vertical double-headed arrow. The "Peak Width" is the horizontal span of the central high section. The "Valley Width" is the horizontal span of the lower side sections, and the "Valley value" is indicated by vertical double-headed arrows for the two valley regions. + +Diagram of a curve on a grid with Peak and Valley parameters. + +There are one peak and two valleys in the curve. The definition of the curve is: + +- peak position: the central position of a peak; +- peak value: a value equal or larger than $1,0$ ; +- peak width: a value less than $1,0$ . + +All valleys should have the same value. + +The total area enclosed by the curve and the x-axis from $0,0$ to $1,0$ is always equating to $1,0$ . + +The curve can be uniquely defined by peak position, peak value and peak width. Once the parameters are determined, other values such as valley value can be calculated. Once a curve is given, grid line positions can be calculated according to the following function: + +$$\int d(x)dx = \frac{k}{n-1}$$ + +Where $X_k$ is the position of the $k^{\text{th}}$ grid line, where $n$ is total number of grid lines. $d(x)$ is the curve function described in the present document. + +In standard WVG, the curve parameters are preset as follows. + +##### **Variable parameters:** + +- number of grid lines: 15, 31, 63 or 127; +- peak value: 1,0, 1,5, 2,0 and 2,5; +- peak position: 13 options from 0,0 (0/12), 0,083333 (1/12), 0,166667 (2/12) to 1,0 (12/12); +- peak width: 0,3, 0,4, 0,5 and 0,6. + +When a portion of a peak exceeds the global envelope only the part within the global envelope is valid. + +For Character Size WVG or glyph, the parameters are set as follows. + +##### **Predefined parameters:** + +- peak width: 0,4. + +##### **Variable parameters:** + +- number of grid lines: 7, 15, 31 or 63; +- peak value: 1,0 or 1,5; +- peak position: 0,3333 (1/3), 0,5, 0,6667 (2/3). + +When using relative coordinates in Compact Coordinate System (refer to clause G 1.3.3), some elements may be specified with specific resolution, which is independent of the global resolution. There are 8 predefined resolutions available for "re-definition resolution", there are 1/27, 1/38, 1/48, 1/64, 1/85, 1/128 and 1/160 of the length of the shorter global envelope edge. Re-definition of resolution only applies to elements in global scope. + +#### G.1.3.2 Flat Coordinate System + +The Flat Coordinate System is a 16 bit signed coordinate system with the top left coordinate of the screen being defined as $(x=0,y=0)$ and the bottom right coordinate being described as $(x=2^{15}, y=2^{15})$ . Note that this expresses the dynamic range of the coordinate system, however it does not mean that all drawings are of this size. + +![Diagram of a rectangle representing the Flat Coordinate System. The top-left corner is labeled (x=0,y=0) and the bottom-right corner is labeled (x=2^15,y=2^15).](b737358d3f26d530ace7882e75a05a47_img.jpg) + +Diagram of a rectangle representing the Flat Coordinate System. The top-left corner is labeled (x=0,y=0) and the bottom-right corner is labeled (x=2^15,y=2^15). + +#### G.1.3.3 Coordinate values + +Coordinate values may be represented using two methods: absolute coordinate and relative coordinate. + +**Absolute Coordinate:** an absolute coordinate is a pair of x and y coordinate number. In WVG Compact Coordinate System, absolute coordinate values are the coordinate grid line numbers and are always positive. + +**Relative Coordinate:** the relative coordinate is used only in lines and transform. If the start point is defined by an absolute coordinate, subsequent points can be described by relative coordinates, which are relative grid units from the previous point. A relative coordinate is signed, and it may be positive or negative. A relative coordinate may be used in + +both global and local coordinate systems. A relative coordinate may exceed the scope of the local envelope that defines the start point of the line. + +### G.1.4 Color schemes + +WVG supports the following color schemes. + +- Black and white (2 Colors): black and white color. +- 2-bit grayscales: four grayscales are defined as (0,0,0), (85,85,85), (170,170,170) and (255,255,255) in 24-bit RGB color format. +- 4 default colors. +- 6-bit RGB color: it is similar to 24-bit RGB color definition but uses only 2 bits to represent a single color, in which value 0, 1, 2 and 3 represent 8-bit color value 0, 85, 170 and 255 respectively. +- 6-bit RGB color using 2nd palette. +- 8-bit websafe color. +- 12-bit and 24-bit RGB color. + +There are 2 optional drawing pens in WVG, stroke pen and fill pen. Stroke pen and fill pen can be specified with one of the colors defined using the scheme. When the stroke pen is not defined, BLACK should be used for strokes. When the fill pen is not defined, no fill should be applied. + +### G.1.5 Rendering model + +WVG uses painter model. The elements appears in the later position in the WVG bit stream will overrides the overlapped portion of the elements which appear in the front in the bit stream. + +## --- G.2 Graphical elements + +WVG defines a set of graphical and animation elements. Among them, line, shape and text elements are the building blocks to form a drawing. These elements can be transformed, grouped and animated. There are also special elements that are auxiliary. + +### G.2.1 Line elements + +There are 3 types of lines: polyline, circular polyline and bezier polyline. A polyline can represent a dot when there is only a start point defined. + +A line element has its reference point at the starting point. A reference point of an element specifies the location of the element. + +#### G.2.1.1 Polyline + +Polyline is a set of straight lines connecting a sequence of points. When there is only one point, it is defined as a dot. + +#### G.2.1.2 Circular Polyline + +Circular Polyline is a line that contains at least one circular curve segment. The curve segment connects two adjacent points by a circular arc. The curve segment is determined by the two adjacent points and a curve offset (the perpendicular distance from the center of the line connecting the adjacent points to the circular arc). + +![Diagram illustrating a curve offset and center point. A curved line is shown with a straight line segment (the base line) connecting two points on the curve. A point on the base line is labeled 'Center point'. A double-headed arrow perpendicular to the base line indicates the 'Curve offset' distance from the base line to the curve.](07f537f57749b75157f742525e6a8dbc_img.jpg) + +Diagram illustrating a curve offset and center point. A curved line is shown with a straight line segment (the base line) connecting two points on the curve. A point on the base line is labeled 'Center point'. A double-headed arrow perpendicular to the base line indicates the 'Curve offset' distance from the base line to the curve. + +Curve offset values are within the range $-0,5$ to $0,5$ , inclusive. A value of $0,5$ or $-0,5$ identifies that the curve offset equals half of length of the connecting line. The value indicates that the curve is close to a half circle. A positive value indicates that the curve is at the left side of the base line viewed from the curve direction. A negative value indicates that the curve is at the right side of the base line viewed from the curve direction. + +#### G.2.1.3 Bezier Polyline + +A Bezier Polyline contains one or more off curve control points in between on curve points. Bezier curves can be filled to create curved shapes and are common in generalized font representations. + +All line elements have direction from the start point to the end point. + +Color fill may apply to a line. Refer to clause G.2.1.4. + +#### G.2.1.4 Auto-closure of a line + +When a line is specified with the fill attribute, the line is considered as a closed line, which connects the start point and the end point using a straight line. The enclosed area of a closed line can be used for color fill. + +The enclosed area is based on nonzero fill rule. Following are two examples in which the light color indicates the enclosed area. + +![Two diagrams illustrating the nonzero fill rule for closed lines. The left diagram shows a self-intersecting closed line with two overlapping regions shaded light gray. The right diagram shows a more complex self-intersecting closed line with multiple overlapping regions shaded light gray, demonstrating how the nonzero fill rule determines the enclosed area.](bd8e3fb102fd14e1edbc62f149241842_img.jpg) + +Two diagrams illustrating the nonzero fill rule for closed lines. The left diagram shows a self-intersecting closed line with two overlapping regions shaded light gray. The right diagram shows a more complex self-intersecting closed line with multiple overlapping regions shaded light gray, demonstrating how the nonzero fill rule determines the enclosed area. + +### G.2.2 Polygon elements + +Polygon elements are closed representations of polyline, circular polyline and Bezier polyline elements. Polygons may have separate line and fill colors or may not be filled at all. + +Polygon elements use the nonzero fill rule for enclosed areas and can be used for color fill. + +A polygon element has its reference point at the starting point. + +### G.2.3 Simple shape elements + +Simple Shapes are rectangles and ellipses. A simple shape is defined by width, height, center point, and angle of rotation. The angle parameter defines how much the shape should be rotated about its center from a horizontal axis drawn through its center. Note that angle units are specified in the main header. + +#### G.2.3.1 Ellipse + +Ellipses are defined by their major axis, minor axis, center and angle of rotation. Circles are considered a special case of ellipse in which the major and minor axis are the same length. + +#### G.2.3.2 Rectangle + +Rectangles are represented by their center, width, height, and rotation angle. Squares are considered special rectangles in which the width and height are identical. + +When the "round corner" indicator is set, the corner of the rectangle should be rounded. There is no specific radius of the round corner is defined. The recommended radius of the rounded corner should be 20% of the length of the shorter edge of the rectangle or the square. + +![A diagram of a rounded rectangle with a small circle inside its top-left corner, illustrating the 'round corner' indicator.](475caf31ae90b878f12d651b689cc9d1_img.jpg) + +A diagram of a rounded rectangle with a small circle inside its top-left corner, illustrating the 'round corner' indicator. + +A simple shape element has its reference point at its center. + +### G.2.4 Special shape elements + +There are 3 types of special shapes. These shapes are Regular Polygons, Stars, and Grids. Each shape has a reference point that determines its position for the purpose of transformations such as detailed in G2.8.1 and G.4. Shapes may have other parameters. These shapes include: + +- **Regular polygon:** a regular polygon has equal length of all its edges. In its original position, the bottom edge of the regular polygon should be aligned horizontally. A rotate angle can be optionally specified. Regular polygon parameters include the number of vertex, the diameter of the reference circle and angle of rotation. + +![A diagram of a regular pentagon with a dashed circle passing through its vertices, illustrating the reference circle.](5f9ca30b158bcba2f401ed8da6e72c00_img.jpg) + +A diagram of a regular pentagon with a dashed circle passing through its vertices, illustrating the reference circle. + +- **Star:** a star is defined by the number of corner vertex, the diameter of the reference circle, vertex angle and angle of rotation. In its original position, the bottom edge, which formed by two vertexes of the star, should be aligned horizontally. A rotate angle can be optionally specified. Vertex angles are predefined as 0, 36, 60, 90 degrees. + +![A diagram of a five-pointed star inside a dashed circle. An arrow labeled 'vertex' points to the top-most point of the star.](10953d657a5f47fdc829a800419dd370_img.jpg) + +A diagram of a five-pointed star inside a dashed circle. An arrow labeled 'vertex' points to the top-most point of the star. + +If the vertex angle is 0, a single line from center to vertex shall be drawn. + +- **Grid:** a grid is a number of evenly distributed perpendicular lines. Its parameters include height, width, angle and number of rows and columns (up to 16). + +A special shape element has its reference point at its center. + +### G.2.5 Text element + +WVG supports text display inside the drawing. However it supports only the default font. To avoid inconsistency on different terminals, it is recommended to use vector based font. Text can be placed in a drawing with position, font size and rotate angle. Like other elements, text has attributes of line style, line color, line width. It can also be animated. + +Control characters are ignored when the text is rendered except for the CR (Carriage Return). The CR indicates the text followed by should be displayed at the next line position. Multi-line text should be left aligned. There is no character spacing and line spacing defined. Recommended character spacing is 10% of the text height. Recommended line spacing is 20% of the text height. + +A text element has its reference point at top-left corner. + +### G.2.6 Group elements + +A set of elements can be grouped together. + +The Group element is used to mark the start and end of grouped elements. A group of elements starts with a Group element which has the end-group indicator off, followed by a list of elements in the group, and ends with an Group element which has the end-group indicator on. Groups can be nested. Implementation must support at least 2 levels of nested group. + +Group (start) + +Element 1 + +Element 2 + +..... + +Group (start) + +Element a + +Element b + +..... + +Group (end) + +Element n + +Element n+1 + +..... + +Group (end) + +### G.2.7 Reuse element + +Reuse element can be used to display an element or a group of elements with a transform and/or changed attributes and/or display an array. Whether a reuse element references a group or a basic element depends on the element type that the element\_index in the reuse element points to. When reuse array is specified, the referenced element or group of elements is duplicated in rows and columns. The reference point of a reused array is at the reference point of the top-left element in the array. + +### G.2.8 Animation elements + +There are two types of animation elements, Simple Animation Element and Standard Animation Element. In the data format, a simple animation element is followed by another element or a group element that the animation applies to. A standard animation element has pointer or index that points to another element or a group element. + +#### G.2.8.1 Simple animation elements + +Simple animation is defined for WVG. All animation timing is based on an "Animation Cycle". WVG animation is repetitive. After completion of playing one cycle, a subsequent cycle play commences immediately. + +There are two types of animation cycles defined, short cycle and long cycle. The time length of animation cycles are not defined. The time length of a long cycle should be twice the length of a short cycle. Recommended short cycle should collapse for 1 second and long cycle play for 2 seconds. + +There are two types of animations. + +**Visibility:** an element can be visible or invisible during a specific cycle segments. A short cycle is divided into 4 time segments equally and a long cycle is divided into 8 time segments equally. + +In the following example, a visibility for short cycle animation is defined. The element to be animated will blink following the pattern defined in the Visibility field below. Bit 1 indicates the element should be displayed during the time segment. Bit 0 indicates it should not be displayed during the time segment. + +| | | | | +|---|---|---|---| +| 0 | 1 | 0 | 1 | +|---|---|---|---| + +In the following example, a visibility for long cycle animation is defined. The element to be animated will blink following the pattern defined in the visibility field below. + +| | | | | | | | | +|---|---|---|---|---|---|---|---| +| 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | +|---|---|---|---|---|---|---|---| + +**Round Rotation:** an element can be rotated at clockwise or counter-clockwise directions. + +**Transform:** a start and an end transform can be applied to an element to describe the start and end position of a rotate, a scale, a translate animation or any combination of these action. When a transform element is omitted, it defaults to use the element's original position. An animation element must include at least one transform element. The animated element can also be a group to allow the animation action applied to a group of elements. + +In simple animation, a transform from start position to end position should be completed in one cycle. A bounced flag can be turned on to allow "bouncing" animation. A bounced transform transforms the element from start position to end position in one cycle. + +Transform in a short cycle: + +| | | +|--|--| +| | | +|--|--| + +start status + +end status + +Bounced Transform in a short cycle: + +| | | | +|--|--|--| +| | | | +|--|--|--| + +start +status + +end +status + +start +status + +Transform in a long cycle: + +| | | +|--|--| +| | | +|--|--| + +start status + +end status + +Bounced Transform in a long cycle: + +| | | | +|--|--|--| +| | | | +|--|--|--| + +start +status + +end +status + +start +status + +Visibility and transform animation can be applied to the same element. + +#### G.2.8.2 Standard Animation Element + +A Standard Animation Element contains animation information such as begin transform position, end transform position, begin color, end color, begin time, end time, etc. This allows one animation element to represent a series of related images, which results in significant compression of the data stream. The WVG player interpolates between the beginning state and end state to achieve animation. + +Animation elements are not allowed inside groups. Animation rotation ranges from 0 to 360 degrees in both clockwise and counter-clockwise directions. + +### G.2.9 Frame Element + +Frame Element is as a marker of the start of a new frame. All elements before a frame element belong to previous frame. The delay between two frames is defined as an infinite time interval. This means says that once a frame marker is reached, the elements that have been displayed on the screen at this time will stay on the screen until the user requests that the next frame should be displayed. The idea is that one can have multiple "pages" of graphics, such as a multi-page cartoon. The user can then study the first page and when finish can press a button (or trigger some other event) to see the next page of the cartoon. The mechanism of the user event is not defined and is left up to the application developer. + +Here are parameters of a frame element: + +- keep last frame contents (or not). Zero means not keeping last frame contents, otherwise all the contents of previous frame will be kept. +- fill in a new background color (or not). Zero means no new fill color is needed for this frame, otherwise a new background color will be used. +- new background color. + +A frame element cannot appear in an element group. Reuse and animation elements can not apply to a frame element. + +### G.2.10 Local Element + +This element defines the size and position of a local envelope. + +The local envelope is a square area whose top-left corner is defined as the origin for its x and y-axis. The number of grid lines are pre-defined to 7, 15, 31 and 63. The resolution is constant in a local grid which is pre-defined at 1/27, 1/32, 1/48, 1/64, 1/85, 1/128, and 1/160 of the local envelope width. Actual envelope size can be determined by number of grid lines and grid resolution. The position of the local envelope is determined by the local envelope origin that falls at a coordinate within the global envelope. + +A local element cannot appear in between another local start and local end element. + +### G.2.11 Extended Element + +The Extended Element is defined to create objects which are not part of the base parsing level of defined objects in the present document and as a future proof method of expansion as defined by 3GPP technical committees. The extended element is intended for resolving problems in the current release. It may also be possible to use the extended element for potential enhancements in future releases. If the decoder encounters an extended element and the extended element type is unrecognizable, it can gracefully skip this element by seeking past it in the bitstream, and continuing decoding at the next element in the bitstream. + +An extended element contains the size of the extended element, the extended element type, and a series of bytes representing the payload data. The size field represents the payload data size in bytes. Note that when reading the payload data, bit alignment should be assumed (not byte alignment). + +## --- G.3 Element attributes + +Each element has a number of attributes such as pen color, fill color and line width used for stroking. The following elements Line, polygon, shape and text elements have the listed attributes. + +- Line width: 3 levels (fine, medium, thick). Default is fine. +- Line style: 4 types (solid, dash, dot and reserved). Default is solid. +- Pen color and fill color. + +Line Width: + +There are 4 line width settings defined, namely "No Line", "Fine", "Medium" and "Thick". No specific width is defined for "Fine", "Medium" and "Thick". Recommended line widths are 1% or one pixel, 2% and 4% of the shorter dimension of the drawing. Line width for "Fine", "Medium" and "Thick" should be at least 1 pixel. E.g., in a 120 x 80 pixel screen, the line width may appear as 1 pixel, 2 pixels and 3 pixels. + +Line Type: + +Dash Line: a dash line should start with a solid segment of the line. The length of the solid segments is recommended to be 4 to 6 times of the line width. The space between two solid segments is recommended to be 3-4 times of the line width. + +![Three thick horizontal black line segments representing a dashed line pattern.](373e2ccc5c19a052a1b8cb6de3eebc94_img.jpg) + +Three thick horizontal black line segments representing a dashed line pattern. + +Dotted Line: a dotted line is a string of circular dot on the path of a line. It is recommended that the diameter of rounded dot is same as the line width. The space between two dots shall be between 1 to 2 dot diameters. + +![A sequence of five solid black circular dots representing a dotted line pattern.](1517552d07f4a8b389be86af8aff6424_img.jpg) + +A sequence of five solid black circular dots representing a dotted line pattern. + +Line Cap: + +Line cap is Circular. + +Line Joint: + +Line joint is Round for line joint. + +## G.4 Element Transform + +The Transform element is used to scale, rotate, or translate any single element or group of elements. Multiple transforms may be applied in succession to any element by standard matrix concatenation. The transform element may be included in Group, Reuse and Animation elements and applied to line, polygon, shape, text and group elements. The sequence of applying transform operations is scale->rotate->translate. + +## G.5 Character Size WVG Element + +The character size WVG, or glyph is a subset variation of WVG. Character Size WVG uses a compact coordinate system with a half resolution global grid (7, 15, 31 and 63 grid lines), default color (monochrome), line elements (polyline, circular polyline and Bezier polyline) and a simplified drawing header. + +## G.6 Data Format BNF + +The following notation is used in the present document for BNF syntax: + +| | | +|-----|----------------------------------------------------------------| +| < > | Enclose term names | +| | Separates alternatives (exclusive OR) | +| [] | Square brackets enclose optional items in syntax descriptions. | +| {} | { } Term enclosed is used zero or more times | +| () | ( ) Enclose groups of alternative terms | +| ... | From ... to | +| ; | Start with comments | +| 0 | Bit value 0 in bit stream | +| 1 | Bit value 1 in bit stream | +| ' ' | Terminator described by enclosed text | + +Notes for reading the BNF: + +NOTE 1: The bit value appearing at the left in the BNF indicates it is arranged in the front in the bit stream. + +NOTE 2: Notation 00...11 is equivalent to ( 00 | 01 | 10 | 11 ). + +NOTE 3: Notation ( 0 | 1 ) is used in the BNF in many occurrences for optionally omitting a value. In this example, it indicates either a specific value can be used, or it can be omitted when default value can be used. The bit value 0 or 1 indicates if is specified. + +NOTE 4: Signed integers use Two's Complement representation. + +### WVG (Wireless Vector Graphics) + + ::= ( 0 ) | ( 1 ) + + ::= + + ::= + +#### Common + + ::= 0 | 1 *; 0 for 7-bit GSM character set. 1 for 16-bit UCS-2* + + ::= 'unsigned 8-bit integer' *; number of GSM or UCS-2 characters +; GSM extension characters are counted as one character +; = 0 means null string* + + ::= 'unsigned 7 bit integer' *; 7-bit GSM character value +; Extension table are supported but the Another Extension; and the +; Page Break are not supported.* + | 'unsigned 16 bit integer' *; 16-bit UCS-2 value +; CR is supported but other control characters are not supported +; (ignored when processed).* + + := 0 | 1 *; 0 for false, 1 for true* + + := 0 | 1 *; 0 for false, 1 for true* + +#### Character Size WVG Header + + ::= ( 0 ( + ) ) *; standard header* + | ( 1 ( ) ) *; compact header. In this case, x and y grid are same, +; default peak value 1.0, default aspect ratio 1:1. +; Note: character size WVG always use compact coordinate mode* + + ::= *; true for at least one polyline element in the drawing* + *; true for at least one circular polyline element in the drawing* + *; true for at least one Bezier polyline element in the drawing* + + ::= 0 | 1 *; 0 for all points use absolute coordinates,* + +*; 1 for at least one point uses relative coordinate (offset mode)* + + ::= + + ::= + + ::= + + ::= + + ::= + + ::= 00...11 *; 00 for 3 bits (max value 7), 01 for 4 bits (max value 15)* + +*; 10 for 5 bits (max value 31), 11 for 6 bits (max value 63)* + + ::= 00...11 *; 00: peak value 1.0, no peak position required* + +*; 01: peak value 1.5, peak position 0.5* + +*; 10: peak value 1.5, peak position 0.3333* + +*; 11: peak value 1.5, peak position 0.6667* + +#### Character Size WVG Elements + + ::= { } + + ::= 'unsigned 7-bit integer' *; maximum 127 elements* + + ::= + +( | | ) + + ::= [ ] *; appear when = 1* + + ::= *; empty, when = 100, 010 or 100* + +0 | 1 *; when = 011, 110, 110 or 101* + +*; 0 for the first element with mask value 1 in the * + +*; 1 for the second element with mask value 1 in * + +00..11 *; 00 for polyline, 01 for circular polyline, 10 for Bezier polyline* + +*; (when = 111>)* + + ::= 0 | (1 ) *; 0 for use of absolute coordinate for * + +*; 1 for using relative coordinate (offset mode) for * + +#### Standard WVG Header + + ::= + + ::= 0 | ( 1 <time stamp> ) + +<version> ::= 0000...1111 + +<author string> ::= 0 | (1 <string length> <char> { <char> } ) + +<title string> ::= 0 | (1 <string length> <char> { <char> } ) + +<time stamp> ::= 0 | (1 <year> <month> <day> <hour> <minute> <second> ) + +<year> ::= 'signed\_13\_bit\_integer' + +<month> ::= 'unsigned\_4\_bit\_integer' ; range 1-12 + +<day> ::= 'unsigned\_5\_bit\_integer' ; range 1-31 + +<hour> ::= 'unsigned\_5\_bit\_integer' ; range 0-23 + +<minute> ::= 'unsigned\_6\_bit\_integer' ; range 0-59 + +<second> ::= 'unsigned\_6\_bit\_integer' ; range 0-59> + +#### Color + +<color configuration> ::= <color scheme> <default colors> + +<color scheme> ::= + +| | | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | ; <i>black and white</i> | +| 010 | ; 2-bit gray scale | +| 011 | ; 2-bit predefined color. 4 color value 00, 01, 10, 11 are<br>; mapped to RGB color (255,255,255), (255,0,0),<br>; (0,255,0) and (0,0,255) respectively | +| 100 | ; 6-bit RGB color | +| 101 | ; websafe color | +| 1100 <6-bit color palette> | ; 6-bit RGB color using 2nd color palette | +| 1101 <8-bit color palette> | ; websafe color using 2nd palette | +| 1110 | ; for 12 bits color mode | +| 1111 | ; for 24 bits color mode | + +<6-bit color palette> ::= 00000...11111 ; *A value equal to “number of color” - 1.* + +; + +*Maximum 32 color entries* + +{<6-bit RGB color>} ; *specify color value from 0 to “number of color”-1* + +<8-bit color palette> ::= 0000000...1111111 ; *A value equal to “number of color” - 1.* + +; *Maximum 128 color entries* + +{ <8-bit websafe color> } ; *specify color value from 0 to “number of color”-1* + +; *Note: the decoder will decide number of bits used by <indexed* + +; *RGB/websafe color> <indexed color> use 1 to 7 bits if <number of* + +; *color> is 2, 3...4, 5...8, 9...16, 17...32, 33...64, 65...128.* + +<draw color> ::= + +| | | +|--------------------------|------------------------------------| +| <b/w color> | ; <i>when color scheme is 00</i> | +| <grayscale> | ; <i>when color scheme is 010</i> | +| <2-bit predefined color> | ; <i>when color scheme is 011</i> | +| <6-bit RGB color> | ; <i>when color scheme is 100</i> | +| <8-bit websafe color> | ; <i>when color scheme is 101</i> | +| <indexed RGB color> | ; <i>when color scheme is 1100</i> | +| <indexed websafe color> | ; <i>when color scheme is 1101</i> | +| <12 bit RGB color> | ; <i>when color scheme is 1110</i> | +| <24 bit RGB color> | ; <i>when color scheme is 1111</i> | + +<b/w color> ::= 0 | ; white + +1 ; black + +<grayscale> ::= 00...11 ; 00 for 24-bit RGB color (0,0,0), 01 for 24-bit RGB color (85,85,85) + ; 10 for 24-bit RGB color (170,170,170), 11 for 24-bit RGB color (255,255,255) + +<2-bit predefined color> ::= 00...11 ; 00 for 24-bit RGB color (255,255,255), 01 for 24-bit RGB color (255,0,0) + ; 10 for 24-bit RGB color (0,255,0), 11 for 24-bit RGB color (0,0,255) + +<6-bit RGB color> ::= <2-bit R> <2-bit G> <2-bit B> + +<indexed RGB color> ::= (0 | 1) | 00...11 | 000...111 | 0000...1111 | 00000...11111 + ; map to 6-bit RGB color value defined in <6-bit color palette> + +<8-bit websafe color> ::= 00000000...11111111 + ; See G.7 for websafe color palette definition + +<indexed websafe color> ::= (0 | 1) | 00...11 | 000...111 | 0000...1111 | + 00000...11111 | 000000...111111 | 0000000...1111111 + ; map to 8-bit websafe color value defined in <8-bit color palette> + +<2-bit R> ::= <2-bit color value> ; Red color value + +<2-bit G> ::= <2-bit color value> ; green color value + +<2-bit B> ::= <2-bit color value> ; blue color value + +<2-bit color value> ::= 00...11 ; 00, 01, 10 and 11 for color value 0, 85, 170 and 255 + ; defined in 0-255 color range respectively + +<12-bit RGB color> ::= <4-bit R> <4-bit G> <4-bit B> ; + +<4-bit R> ::= <4-bit color value> ; Red color value + +<4-bit G> ::= <4-bit color value> ; green color value + +<4-bit B> ::= <4-bit color value> ; blue color value + +<4-bit color value> ::= 0000...1111 ; multiply by 17 to convert to 8 bit color value + +<24-bit RGB color> ::= <8-bit R> <8-bit G> <8-bit B> ; + +<8-bit R> ::= <8-bit color value> ; Red color value + +<8-bit G> ::= <8-bit color value> ; green color value + +<8-bit B> ::= <8-bit color value> ; blue color value + +<8-bit color value> ::= 00000000...1111111 ; intensity value of color value + +<default colors> := (0 | (1 <default line color>)) ; use black when first bit is 0 + (0 | (1 <default fill color>)) ; use black when first bit is 0 + (0 | (1 <background color>)) ; use white when first bit is 0 + ; If above color(s) are not + ; specified, use BLACK as <default line color> and <default fill color>, and use + ; WHITE as <background color>. + +<default line color> ::= <draw color> + +<default fill color> ::= <draw color> + +<background color> ::= <draw color> + +### Codec Parameters + +<codec parameters> ::= <element mask> <attribute mask> <generic parameters> + +<coordinate parameters> + +<coordinate parameters> ::= ( 0 <flat coordinate parameters> ) ; *flat coordinate mode* + | ( 1 <compact coordinate parameters> ) ; *compact coordinate mode* + +<element mask> ::= <mask> ; *true for at least one local envelope element in the drawing* + <mask> ; *true for at least one polyline element in the drawing* + <mask> ; *true for at least one circular polyline element in the drawing* + <mask> ; *true for at least one Bezier polyline element in the drawing* + <mask> ; *true for at least one simple shape element in the drawing* + <mask> ; *true for at least one reuse element in the drawing* + <mask> ; *true for at least one group element in the drawing* + <mask> ; *true for at least one animation element in the drawing* + ( 0 | ( 1 ; *extension bit. 1 for rare masks are followed by* + <mask> ; *true for at least one polygon element in the drawing* + <mask> ; *true for at least one special shape element in the drawing* + <mask> ; *true for at least one frame element in the drawing* + <mask> ; *true for at least one text element in the drawing* + <mask> ; *true for at least one extended element in the drawing* + ) ; *The decoder should decide how many bits to be used by <element type>* + ) ; *according to number of “1”s in the <element mask>. Number of bits* + ; *used by <element type> can be 0 (if only one “1” in <element mask>),* + ; *1 (if 2 “1”s), 2 (if 3 or 4 “1”s), 3 (if 5-8 “1”s) or 4(if more than 8* + ; *“1”s). Value of <element type> that is to represent a specific element* + ; *type is same as the order of the specific mask in the <element mask>* + ; *that represents this type of element. For example, if <element mask> is* + ; *011000010, <element type> will use 2 bits and value 00, 01, 10* + ; *(11 is not used) represent polyline, circular polyline and animation* + ; *elements respectively.* + ; *Note that <mask> for local envelope has no meanings when in flat* + ; *coordinate mode but still* + ; *exists* + +<attribute masks> ::= <line type mask> <line width mask> <line color mask> <fill mask> + +<line type mask> ::= <mask> ; true when at least one element uses line type attribute + <line width mask> ::= <mask> ; true when at least one element uses line width attribute + <fill mask> ::= <mask> ; true when at least one element uses fill attribute + <line color mask> ::= <mask> ; true when at least one element uses line color + +#### Generic Parameters + +<generic parameters> ::= (0 | (1 <angle resolution> <angle in bits> ) ; 0 for default (22.5 degree, 3 bits) + (0 | (1 <scale resolution> <scale in bits> ) ; 0 for default (1/4, 3 bits) + (0 | (1 <index in bits> ) ; 0 for default (both 3 bits) + [<curve offset in bits> ] + ; <curve offset in bits> appear when <mask> for <circular polyline element> + ; or <polygon element> is true + +<angle resolution> ::= 00...11 ; 00 for angle unit is 1.40625 degree; 01 for angle unit is 5.625 degree + ; 10 for angle unit is 11.25 degree; 11 for angle unit is 22.5 degree + +<angle in bits> ::= 000...111 ; number of bits used by <angle value> is from 1 to 8 bits + +<angle value> ::= 'signed angleInBits+1-bit integer' + ; angle unit is decided by <angle resolution> + ; 0 degree is defined as positive direction of the X axis and + ; positive angle value is clockwise. + ; -180 degree is represented by maximum negative digit + +<scale resolution> ::= 00..11 ; 00 for 1/4 as scale unit. 01 for 1/16 as scale unit + ; 10 for 1/64 as scale unit; 11 for 1/256 as scale unit + +<scale in bits> ::= 0000...1111 ; number of bits used by <scale value> is from 1 to 16 bits + +<scale value> ::= 'signed scaleInBits+1-bits integer' + ; scale unit is decided by <scale resolution> + ; negative scale value means scaling at + ; opposite direction + +<index in bits> ::= 0000...1111 ; number of bits used by <index> are from 1 to 16 bits + +<index> ::= <index value> + +<index value> ::= 'unsigned IndexInBits+1-bit integer' + +<curve offset in bits> ::= 0 | 1 ; 0 for using 4 bits (15 levels) + ; 1 for using 5 bits (31 levels) + +#### Compact Coordinate Parameters + +<compact coordinate parameters> ::= <aspect ratio> <TransXYInBits1> + +<parameters X-1> <parameters Y-1> <redefine resolution hint> + +<aspect ratio> ::= 00 | ; aspect ratio = 1:1 + ( ( 01 ; aspect ratio = 4:3 + +``` + +| 10 ; aspect ratio = 16:9 +| 1100 ; aspect ratio = 64:27 +| 1101 ; aspect ratio = 256:81 +| 1110 ; aspect ratio = 1024:243 +| 1111 ; aspect ratio = 4096:729 +)[ <display orientation> ] ; <display orientation> appears in standard WVG +) ; character size WVG uses landscape only +<display orientation> ::= 0 | 1 ; 0 for landscape, 1 for portrait +<parameters X-1> ::= <MaxXlnBits1> <coordinate parameters> +<parameters Y-1> ::= <MaxYlnBits1> <coordinate parameters> +<coordinate parameters> ::= 00 | ( <peak value> <peak position> <peak width> ) + ; peak value default to 1.0 when 00 is defined +<MaxXlnBits1> ::= 00...11 ; Number of bits used by <X>. + ; This determines the number of grid lines in the X direction. +<MaxYlnBits1> ::= 00...11 ; Number of bits used by <Y>. + ; This determines the number of grid lines in the Y direction. + ; 00 for 15, 01 for 31, 10 for 63, 11 for 127 +<peak value> ::= 01...11 ; 01 for 1.5, 10 for 2.0, 11 for 2.5 +<peak position> ::= 0000...1100 ; 0-12. Peak position = value/12 from envelope left. + | 1101 ; reserved + | 1110 ; reserved + | 1111 ; reserved +<peak width> ::= 00...11 ; 00 for 0.3, 01 for 0.4, 10 for 0.5, 11 for 0.6 + ; <peak width> value are to the scale of total global envelope width. + ; 10 (0.5) and 11 (0.6) are not allowed when <peak value> is 11 (2.5) + ; 11 (0.6) is not allowed when <peak value> is 10 (2.0) +<redefine resolution hint> ::= <hint> ; true when at least one element uses 'redefine resolution' attribute +<TransXYlnBits1> ::= 00..11 ; number of bits to encode translation and center of transform + ; 00 for 5 bits, 01 for 6 bits, 10 for 7 bits, 11 for 8 bits + ; In global scope and at X axis, it uses unit of (global envelope width/ (number of X grid lines -1 )) + ; In global scope and at Y axis, it uses unit of (global envelope height/ (number of Y grid lines -1 )) + ; In local scope, its unit is same as local coordinate unit. + +``` + +#### Flat Coordinate Parameters + +``` + +<flat coordinate parameters> ::= <drawing width> ( 0 | 1 (<drawing height>)) ; 0 means height = width + <MaxXlnBits2><MaxYlnBits2> <XYAllPositive> + <TransXYlnBits2> <NumPointslnBits> + +``` + +<OffsetXInBitsLevel1> <OffsetYInBitsLevel1> + +<OffsetXInBitsLevel2> <OffsetYInBitsLevel2> + +<drawing width> ::= 'unsigned 16-bit integer' + +<drawing height> ::= 'unsigned 16-bit integer' + +<MaxXInBits2> ::= 'unsigned\_4\_bit\_integer' + +*; number of bits to encode X coordination* + +<MaxYInBits2> ::= 'unsigned\_4\_bit\_integer' + +*; number of bits to encode Y coordination* + +<XYAllPositive> ::= "unsigned\_1\_bit\_integer" + +*; 0 means not all x/y are positive* + +*; 1 means all x/y are positive* + +<TransXYInBits2> ::= 'unsigned\_4\_bit\_integer'    *; number of bits to encode translation and center of transform* + +<OffsetXInBitsLevel1> ::= 'unsigned\_4\_bit\_integer' + +<OffsetYInBitsLevel1> ::= 'unsigned\_4\_bit\_integer' + +<OffsetXInBitsLevel2> ::= 'unsigned\_4\_bit\_integer' + +<OffsetYInBitsLevel2> ::= 'unsigned\_4\_bit\_integer' + +<NumPointsInBits> ::= 'unsigned\_4\_bit\_integer' + +#### Animation Settings + +<animation settings> ::= [ <animation mode> ]                     *;appear when <animation element> exist* + +<animation mode> ::= 0 | 1         *; 0 for simple animation; 1 for standard animation* + +#### Element + +<elements> := <number of elements> <element> { <element> } + +<number of elements> ::= (0 'unsigned 7-bit integer') + +| (1 'unsigned 15-bit integer') + + + +<element> :=       <element type> ( <basic element> | + +<frame element> | <group element> | <re-use element> | + +<animation element> | <extended element> | <local envelope element> ) + +<element type> ::= | 0...1 | 00..11 | 000...111 | 0000...1111                 *; empty is allowed* + +*; decided by <element mask>. Please refer to <element mask>* + +<animation element> := <simple animation element> | <standard animation element> + +*; if <animation mode> is 0, all animation elements in the drawing are <simple animation element>* + +*; if <animation mode> is 1, all animation elements in the drawing are <standard animation element>* + +<basic element>::= <basic element header> ( <polyline element> | <circular polyline element> + +| <Bezier polyline element> | <polygon element> | <simple shape element> + +| <special shape element> | <text element> ) + +#### Basic Element Header + +``` + +<basic element header> ::= ( <offset bit use> ; when in flat coordinate mode + | <resolution and offset bit> ) ; when in compact coordinate mode + [ 0 | ( 1 <attributes set> ) ] ; appears when <attribute masks> does not equal + ; to 0000 + ; 0 for using default attributes defined in <drawing header> + ; 1 for using the following specific attributes + +<Offset Bit Use> ::= <Offset X Use><Offset Y Use> +<Offset X Use> ::= 0 | 1 + ; when in compact coordinate mode, 0 means offset X will use 3 bits., + ; 1 means use 4 bits + ; when in flat coordinate mode, 0 means offset X will use <OffsetXInBitsLevel1>, + ; 1 means use <OffsetXInBitsLevel2> + +<Offset Y Use> ::= 0 | 1 + ; when in compact coordinate mode, 0 means offset X will use 3 bits, + ; 1 means use 4 bits + ; when in flat coordinate mode, 0 means offset X will use <OffsetYInBitsLevel1>, + ; 1 means use <OffsetYInBitsLevel2> + +<resolution and offset bit>::= ( 0 | ( 1 <offset bit use> ) ) + ; only when <redefine resolution hint> is false or in local scope + ; 0 for absolute coordinate, 1 for relative coordinates + | ( 0 ( 0 | ( 1 <offset bit use> ) ) + ; when <redefine resolution hint> is true and in global scope + ; 0 for absolute coordinate, 1 for relative coordinates + | ( 1 <coordinate resolution> <offset bit use> ) + ; when <redefine resolution hint> is true and in global scope + ; redefine resolution, always use relative coordinates + +<coordinate resolution> ::= 000...111 ; decide the grid line interval by a scale of width + ; or height of the global envelope whichever is short. + ; 0-7 for 1/27, 1/32, 1/38, 1/48, 1/64, + ; 1/85, 1/128 and 1/160 respectively + +``` + +#### Element Attributes + +``` + +<attribute set> ::= [ <line type> ] ; appear when <line type mask> is true + [ <line width> ] ; appear when <line width mask> is true + +``` + +[ 0 | (1 <line color>) ]      ; *appear when <line color mask> is true and* +                                          ; *<line width> is not zero* +                                          ; *0 for <default line color>, 1 for specified color* + +[ 0 | (1                                    ; *0 for no fill; 1 for with fill* +             (0 | (1 <fill color>))      ; *0 for <default fill color>, 1 for specified color* +             )                                    ; *appear when <fill mask> is true* + ]                                    ; *Note: line type and line width are not used by <text element> but* +                                          ; *still exist here. If not filled, then background of text output will* +                                          ; *be transparent. If filled, then fill color will be used as text background.* + +<line width> ::= 00...11                    ; *00 for no line, 01 for Fine, 10 for medium, 11 for thick* + +                                         ; *00 is only valid with fill* + +<line type> ::= 00...11                    ; *0 for solid, 1 for dash line, 2 for dotted line* + +<fill color> ::= <draw color> + +<line color> ::= <draw color> + +<OverrideAttributeSet> ::= 0 | (1 <line type>) + +                    0 | (1 <line width>) + +                    0 | (1 <line color>) + +                    0 | (1 <fill> ) + +                    0 | (1 <fill color>) + +                                         ; *0 for no overriding, 1 for overriding with specified attribute* + +<fill> ::= 0 | 1                            ; *0 means no fill, 1 means fill* + +#### Transform + +<Transform> ::= <TranslateX><TranslateY> + +                    0 | (1 <Angle> <ScaleX><ScaleY> <CX> <CY>) ; *optional other transforms* + +<Angle> ::= 0 | (1 <Angle Value> )                    ; *0 means angle will use default value which is 0* + +<TranslateX> ::= 0 | (1 <TranslateX Value> ) ; *0 means translate x will use default value which is 0* + +<TranslateX Value> ::= 'signed\_TransXYInBits2\_bit integer'      ; *when in flat coordinate mode* + +                    | 'signed TransXYInBits1+5 bit integer'            ; *when in compact coordinate mode* + +<TranslateY> ::= 0 | (1 <TranslateY Value> ) ; *0 means translate y will use default value which is 0* + +<TranslateY Value> ::= 'signed\_TransXYInBits2\_bit integer'      ; *when in flat coordinate mode* + +                    | 'signed TransXYInBits1+5-bit integer'            ; *when in compact coordinate mode* + +<ScaleX> ::= 0 | (1 <Scale value> )                    ; *0 means scale will use default value which is 1.0* + +<ScaleY> ::= 0 | (1 <Scale value> )                    ; *0 means scale will use default value which is same as* + +                                         ; *absolute value of <ScaleX>* + +<CX> ::= 0 | (1 <CX value> )                    ; *translation of rotation and scale center; 0 means it will use default* + +                                         ; *value which is at the left border of the drawing (x=0 in the flat* + +                                         ; *coordinate system or the global envelope)* + +``` + +<CX value> ::= 'signed_TransXYInBits2_bit integer' ; when in flat coordinate mode + | <X> ; when in compact coordinate mode +<CY> ::= 0 | (1 <CY value> ) ; 0 means it will use default value which is + ; (y=0 in the flat coordinate system or the global envelope) +<CY value> ::= 'signed_TransXYInBits2_bit integer' ; when in flat coordinate mode + | <Y> ; when in compact coordinate mode + +``` + +#### Polyline Element + +``` + +<polyline element> ::= [ <numberOfPoints> ] <First Point> { <Next Point> } [ <point terminator> ] + ; specifies a start point, zero or many intermediate points and an end point. + ; <numberOfPoints> appears only when in flat coordinate mode + ; <point terminator> appears only when in compact coordinate mode +<point terminator> ::= 111...111111 ; Absolute mode in character size WVG. Same number of + ; bits of <MaxXInBits0> or <MaxXYInBits0> + | 1111...1111111 ; Absolute mode in standard WVG. Same number of bits of + ; <MaxXInBits1> or <MaxLocalXYInBits> + | ( 100 | 1000 ) ; Offset mode (relative). + ; use 100 when <Offset X Use> = 0 + ; use 1000 when <Offset X Use> = 1 + +``` + +#### Circular Polyline Element + +``` + +<circular polyline element> ::= <curve hint> [ <numberOfPoints> ] <FirstPoint> <curve offset> <point> + { <curve offset> <NextPoint> } [ <offset terminator> ] + ; <numberOfPoints> appears only when use + ; flat coordinate mode + ; <offset terminator> appears only when use + ; compact coordinate mode +<curve hint> ::= <hint> +<curve offset> ::= ( 0 | (1 <curve offset value>) ) ; when <curve hint> is true + | <curve offset value> ; when <curve hint> is false +<offset value> ::= 'signed 4-bit integer' ; when <curve offset in bits> = 0 + ; or in character size WVG + | 'signed 5-bit integer' ; when <curve offset in bits> = 1 + ; Curve offset ratio $r = e/L$ + ; Where $e$ is actual curve offset (can be positive or negative), + +``` + +*; L is distance between adjacent nodes* + +*; We use a signed integer value v to represent. $v = \text{round}(r * k)$ ;* + +*; Where $k = 2^n - 2$ (n is number of bits used for <offset value>)* + +``` +<offset terminator> ::= ( 1 <curve offset bits> ) ; when <curve hint> is true + | < curve offset bits > ; when <curve hint> is false +<curve offset bits> ::= 1000 ; when <curve offset in bits> = 0 + | 10000 ; when <curve offset in bits> = 1 +``` + +#### Bezier Polyline Element + +``` +<Bezier polyline element> ::= [ <NumberOfPoints> ] + <First Point> {<OnCurve> <Next Point>} [ 1 <point terminator> ] + ; Same data format for PolyBezCurve, and PolygonBezCurve + ; <numberOfPoints> appears only when in flat coordinate mode + ; "1 <point terminator>" appears only when in compact coordinate mode +<NumberOfPoints> ::= 'unsigned_NumberOfPointsInBits_bit integer' +<OnCurve> ::= 0 | 1 + ; 0 – off curve + ; 1 – on curve +``` + +NOTE: Only cubic and quadratic Bezier curves are supported. It means only one or two successive off-curve points are allowed. The first point of a curve must be on-curve. The last point must also be on-curve if it is Bezier polyline but is not necessary for Bezier polygon. + +#### Polygon Element + +*Polygon element is actually a closed polyline (including circular and Bezier polyline)* + +``` +<polygon element> ::= ( 00 <polyline element> ) | ( 01 <circular polyline element> ) + | ( 10 <Bezier polyline element> ) +``` + +#### Simple Shape Element + +``` +<simple shape element> ::= ( 0 <rectangle element> ) | ( 1 <ellipse element> ) +<rectangle element> ::= <Point> <Width> <Height> <rounded flag> <Angle> +<ellipse element> ::= <Point> <Width> <Height> <Angle> +<Width> ::= <X> | <Offset X> ; <Offset X> is used when <Offset Bit Use> exists in the <basic element header> + ; if the element is in global scope in compact coordinate mode, use unit of + ; (global envelope width/ (number of X grid lines – 1 )) +<Height> ::= 0 | ( 1 <HeightValue> ) ; 0 means the height is same as width, height will not be encoded +<HeightValue> ::= <Y> | <Offset Y> + ; <Offset Y> is used when <Offset Bit Use> exists in the <basic element header> + ; if the element is in global scope in compact coordinate mode, use unit of + ; (global envelope height/ (number of Y grid lines – 1 )) +``` + +<rounded flag> ::= 0 | 1 *; 0 for straight corner, 1 for rounded corner* + +#### **Special Shape Element** + +<special shape element> ::= <point> <angle> + +00 ( <vertex> < diameter > *; regular polygon* + | 01 ( <vertex> <vertex angle> < diameter > *; star* + | 10 ( <rectangle size> <rows> <columns> ) *; grid* + | 11 *; not used* + +<diameter> ::= <X> | <Offset X> *; diameter of circle or vertex* +*; <Offset X> is used when <Offset Bit Use> exists in the <basic element header>* +*; if the element is in global scope in compact coordinate mode, use unit of* +*; $(\text{global envelope width}/ (\text{number of X grid lines} - 1))$* + +<rectangle size> ::= <width> <height> + +<vertex> ::= 000...111 *; number of vertex = <vertex> + 3* + +<vertex angle> ::= 00...11 *; 00 for 0 degree, 01 for 36 degree* +*; 10 for 60 degree, 11 for 90 degree* + +<rows> ::= 0000...1111 *; rows = <rows> + 1* + +<columns> ::= 0000...1111 *; columns = <columns> + 1* + +#### **Text Element** + +<text element> ::= <point> <font size> <angle> <text code mode> <string length> { <char> } +*; <point> is top-left corner of the text.* + +<font size> ::= <Y> | <Offset Y> *; <Offset Y> is used when <Offset Bit Use> exists in the <basic element header>* +*; if the element is in global scope in compact coordinate mode, use unit of* +*; $(\text{global envelope height}/ (\text{number of Y grid lines} - 1))$* + +#### **Local Envelope Element** + +<local envelope element> ::= ( 0 <local envelope description> <point> ) +*; local start* +*; <point> is top-left corner of the local envelope in global coordinates.* +*; Elements in the local envelope scope use local coordinates and measurements* + | 1 *; local end* + +<local envelope description> ::= <coordinate resolution> <MaxLocalXYInBits> + +<MaxLocalXYInBits> ::= 00...11 *; 00 for 3 bits(max value 7), 01 for 4 bits (max value 15),* + +; 10 for 5 bits (max value 31), 11 for 6 bits (max value 63) + +#### Group Element + +<group element> ::= (0 (0 | (1 <transform>)) <display> ) ; start of group. Transform is optional + | 1 ; end of group + +<display> ::= 0 | 1 ; 0 – no display when render; 1 – display when render + +#### Re-use Element + +<re-use element> ::= <element index> ; point to the element to be re-used + +; only <basic element>, <group element> and + +; <re-use element> can be reused + +<transform> ; re-use with transformation + +0 | (1 <array parameter>) ; array. It should be performed as the last step + +0 | (1 <OverrideAttributeSet> ) + +<element index> ::= <index value> ; the element sequence number in whole drawing. Start from 0. + +<array parameter> ::= <columns> [ <array width> ] <rows> [ <array height> ] + +; <array height> indicates whole height of the array, appears when <rows> is non-zero + +; element interval at X direction equals to <width>/<columns> + +; <array width> indicates whole width of the array, appears when <columns> is non-zero + +; element interval at Y direction equals to <height>/<rows> + +; The top left element in the array is at the position specified in <transform> + +<array width> ::= <X> ; if the element is in globale scope in compact coordinate mode, use unit of + ; (global envelope width/ (number of X grid lines –1 )) + +<array height> ::= 0 | (1 <Y> ) ; 0 means the height is same as width, height will not be encoded + ; if the element is in globale scope in compact coordinate mode, use unit of + ; (global envelope height/ (number of Y grid lines –1 )) + +#### Frame Element + +<Frame> ::= <KeepLastFrameContentFlag><HasFilledColorFlag>[< fill color >] + ; <fill color> is new background color for the frame + +<KeepLastFrameContentFlag> ::= 'unsigned 1-bit integer' + +; keep the image of the last frame on the screen, or clear it + +; value 0 - Do not keep last frame content. + +; value 1 - Keep last frame content. + +<HasFilledColorFlag> ::= 'unsigned 1-bit integer' + +; value 0 - no filled color + +; value 1 - has filled color + +#### Simple Animation Element + +<simple animation element> ::= <cycle type> + +( 0 | ( 1 <visibility parameter> ) + +( 0 | ( 1 <transform> ) ; begin transform + +( 0 | ( 1 <transform> ) ; end transform + +( 0 | 1 ) ; 0 for no bouncing. 1 for bouncing + +<rotation direction> + +<round rotation flag> + +<round rotation flag> ::= 0 | 1 ; 0 for no round rotation. + +; 1 for round rotation and will override angles defined in <transform> + +<cycle type> ::= 0 | 1 ; 0 indicates short animation cycle; 1 indicates long animation cycle + +<visibility parameter> ::= <visibility timing> + +<visibility timing> ::= 0000...1111 | 00000000...11111111 + +; One blinking cycle is divided into four equal time steps for short + +; animation cycle or eight steps for long animation cycle. <visibility timing> is a map of time steps in + +; which 0 represents invisible and 1 represents visible. Note that in above map, consequence time steps + +; is from left to right, or from first order to later order in bit stream. + +<rotation direction> ::= 0 | 1 ; 1 for clockwise rotating. 0 for counter-clockwise rotating + +NOTE: For all individual values in the transform, linear interpolation is used. + +#### Standard Animation Element + +<standard animation element> ::= <element index> <BeginTransform><EndTransform><Rotation Direction> + +<Round> 0 | ( 1 <BeginColor><EndColor> ) <BeginTime><Duration><ExistAfter> + +<BeginTransform> ::= 0 | ( 1 <Transform> ) ; begin position + +; 0 – means use (start from) default transform: + +; Angle=0, TranslateX=0, TranslateY=0, ScaleX=256, ScaleY=256, Cx=0, Cy=0 + +; 1 – means Transform follows + +<EndTransform> ::= 0 | ( 1 <Transform> ) ; end position + +; 0 – means use (end at) default transform + +; Angle=0, TranslateX=0, TranslateY=0, ScaleX=256, ScaleY=256, Cx=0, Cy=0 + +; 1 – means Transform follows + +<Rotation Direction> ::= 0 | 1 ; 0 – counter clockwise + +; 1 – clockwise + +<Round> ::= 0 | 1 ; 0 – no rotation + +; 1 – rotate 360 degrees + +<BeginColor> ::= ( 0 | ( 1 <line color> ) ) ( 0 | ( 1 <fill color> ) ) +*;0 – use default colors* +*;1 – use specified colors* + +<EndColor> ::= ( 0 | ( 1 <line color> ) ) ( 0 | ( 1 <fill color> ) ) +*;0 – use default colors* +*;1 – use specified colors* + +<BeginTime> ::= 'unsigned 12-bit integer' ; <BeginTime> is in units of 10ms + +<Duration> ::= 'unsigned 12-bit integer' ; <Duration> is in units of 10ms + +<ExistAfter> ::= 0 | ( 1 <AnimationRepeat> ) ; 0 – animation element will disappear after the animation is finished +*; 1 – animation element will persist after the animation is finished* + +<AnimationRepeat> ::= 0 | ( 1 <Bouncing> ) ; 0 – no repeat, animated element will stay +*; at <EndTransform>* +*; 1 – animation will repeat, duration will be <Duration>* + +<Bouncing> ::= 0 | 1 ; 0 – no bouncing, animation will repeat as from begin +*; position to end position* +*; 1 – repeat with bouncing. Animation will be* +*; repeated as end position ->* +*; begin position, then begin position->end position,* +*; then end position->begin position ...* + +NOTE: For all individual values in the transform, linear interpolation is used. Similarly, color interpolation uses linear RGB color space. Out of range color values are allowed. + +#### Extended Element + +<Extended> ::= <SizeOfSize><Size><ExtendedElementType>{<payload>} + +<SizeOfSize> ::= 'unsigned\_5\_bit integer' +*; the bit size of the Size field* + +<Size> ::= 'unsigned-<SizeOfSize>-bit integer' +*; size of extended element data after ExtendedElementType, in bytes* + +<ExtendedElementType> ::= 'unsigned\_8\_bit integer' +*; element type of extended element* + +<payload> ::= 'unsigned\_8\_bit integer' +*; encoded extended element data. The size should be the same as the Size field of Extended, above.* + +### Position and Measurement + +<First Point> ::= <point> ; first point of a polyline or polygon (including circular and +*; Bezier polygons)* + +<Next Point> ::= <point> | ; when use absolute mode +<Offset> ; when use offset mode +*; in flat coordinate system, only offset mode is used.* + +<point> ::= <X> <Y> + +<X> ::= 'signed MaxXInBits2-bit integer' ; when in flat coordinate mode and <XYAllPositive> = 0 + | 'unsigned MaxXInBits2-bit integer' ; when in flat coordinate mode and <XYAllPositive> = 1 + | 'unsigned MaxXInBits1+4-bit integer' ; when in compact coordinate mode and in global scope + | 'unsigned MaxLocalXYInBits+3-bit integer' ; when in compact coordinate mode and in local scope + | 'unsigned MaxXInBits0+3-bit integer' ; when in character size WVW (use standard header) + | 'unsigned MaxXYBits0+3-bit integer' ; when in character size WVW (use compact header) + +<Y> ::= 'signed MaxYInBits2-bit integer' ; when in flat coordinate mode and <XYAllPositive> = 0 + | 'unsigned MaxYInBits2-bit integer' ; when in flat coordinate mode and <XYAllPositive> = 1 + | 'unsigned MaxYInBits1+4-bit integer' ; when in compact coordinate mode and in global scope + | 'unsigned MaxLocalXYInBits+3-bit integer' ; when in compact coordinate mode and in local scope + | 'unsigned MaxYInBits0+3-bit integer' ; when in character size WVW (use standard header) + | 'unsigned MaxXYBits0+3-bit integer' ; when in character size WVW (use compact header) + +; Note: in compact coordinate mode, <X> and <Y> do not use the maximum number of the unsigned integer + +<Offset> ::= <Offset X> <Offset Y> + +<Offset X> ::= <signed offset X> ; when used by <Next Point> + | <unsigned offset X> ; when used in other cases + +<Offset Y> ::= <signed offset Y> ; when used by <Next Point> + | <unsigned offset Y> ; when used in other cases + +<signed offset X> = 'signed OffsetXInBitsLevel1-bit integer' + ; when in flat coordinate mode and <offset bit use> = 0 + | 'signed OffsetXInBitsLevel2-bit integer' + ; when in flat coordinate mode and <offset bit use> = 1 + | 'signed 3-bit integer' ; when in compact coordinate mode and <offset bit use> = 0 + | 'signed 4-bit integer' ; when in compact coordinate mode and <offset bit use> = 0 + +<signed offset Y> = 'signed OffsetYInBitsLevel1-bit integer' + ; when in flat coordinate mode and <offset bit use> = 0 + | 'signed OffsetYInBitsLevel2-bit integer' + ; when in flat coordinate mode and <offset bit use> = 1 + | 'signed 3-bit integer' ; when in compact coordinate mode and <offset bit use> = 0 + | 'signed 4-bit integer' ; when in compact coordinate mode and <offset bit use> = 0 + +<unsigned offset X> ::= 'unsigned OffsetXInBitsLevel1-bit integer' + ; when in flat coordinate mode and <offset bit use> = 0 + | 'unsigned OffsetXInBitsLevel2-bit integer' + ; when in flat coordinate mode and <offset bit use> = 1 + | 'unsigned 3-bit integer' ; when in compact coordinate mode and <offset bit use> = 0 + | 'unsigned 4-bit integer' ; when in compact coordinate mode and <offset bit use> = 1 + +<unsigned offset Y> ::= 'unsigned OffsetYInBitsLevel1-bit integer' + +*;when in flat coordinate mode and <offset bit use> = 0* + +| 'unsigned OffsetYInBitsLevel2-bit integer' + +*;when in flat coordinate mode and <offset bit use> = 1* + +| 'unsigned 3-bit integer' *;when in compact coordinate mode and <offset bit use> = 0* + +| 'unsigned 4-bit integer' *;when in compact coordinate mode and <offset bit use> = 1* + +## G.7 Web Safe Color Palette + +*Websafe color palette can be defined as in following C syntax using 24-bit RGB color (in form of {red, blue, green}). The first index of the array indicates value of <8-bit websafe color>* + +``` +int websafePalette[256][3] = +{ + { 255, 255, 255 }, { 255, 204, 255 }, { 255, 153, 255 }, { 255, 102, 255 }, + { 255, 51, 255 }, { 255, 0, 255 }, { 255, 255, 204 }, { 255, 204, 204 }, + { 255, 153, 204 }, { 255, 102, 204 }, { 255, 51, 204 }, { 255, 0, 204 }, + { 255, 255, 153 }, { 255, 204, 153 }, { 255, 153, 153 }, { 255, 102, 153 }, + { 255, 51, 153 }, { 255, 0, 153 }, { 204, 255, 255 }, { 204, 204, 255 }, + { 204, 153, 255 }, { 204, 102, 255 }, { 204, 51, 255 }, { 204, 0, 255 }, + { 204, 255, 204 }, { 204, 204, 204 }, { 204, 153, 204 }, { 204, 102, 204 }, + { 204, 51, 204 }, { 204, 0, 204 }, { 204, 255, 153 }, { 204, 204, 153 }, + { 204, 153, 153 }, { 204, 102, 153 }, { 204, 51, 153 }, { 204, 0, 153 }, + { 153, 255, 255 }, { 153, 204, 255 }, { 153, 153, 255 }, { 153, 102, 255 }, + { 153, 51, 255 }, { 153, 0, 255 }, { 153, 255, 204 }, { 153, 204, 204 }, + { 153, 153, 204 }, { 153, 102, 204 }, { 153, 51, 204 }, { 153, 0, 204 }, + { 153, 255, 153 }, { 153, 204, 153 }, { 153, 153, 153 }, { 153, 102, 153 }, + { 153, 51, 153 }, { 153, 0, 153 }, { 102, 255, 255 }, { 102, 204, 255 }, + { 102, 153, 255 }, { 102, 102, 255 }, { 102, 51, 255 }, { 102, 0, 255 }, + { 102, 255, 204 }, { 102, 204, 204 }, { 102, 153, 204 }, { 102, 102, 204 }, + { 102, 51, 204 }, { 102, 0, 204 }, { 102, 255, 153 }, { 102, 204, 153 }, + { 102, 153, 153 }, { 102, 102, 153 }, { 102, 51, 153 }, { 102, 0, 153 }, + { 51, 255, 255 }, { 51, 204, 255 }, { 51, 153, 255 }, { 51, 102, 255 }, + { 51, 51, 255 }, { 51, 0, 255 }, { 51, 255, 204 }, { 51, 204, 204 }, + { 51, 153, 204 }, { 51, 102, 204 }, { 51, 51, 204 }, { 51, 0, 204 }, + { 51, 255, 153 }, { 51, 204, 153 }, { 51, 153, 153 }, { 51, 102, 153 }, + { 51, 51, 153 }, { 51, 0, 153 }, { 0, 255, 255 }, { 0, 204, 255 }, + { 0, 153, 255 }, { 0, 102, 255 }, { 0, 51, 255 }, { 0, 0, 255 }, + { 0, 255, 204 }, { 0, 204, 204 }, { 0, 153, 204 }, { 0, 102, 204 }, + { 0, 51, 204 }, { 0, 0, 204 }, { 0, 255, 153 }, { 0, 204, 153 }, + { 0, 153, 153 }, { 0, 102, 153 }, { 0, 51, 153 }, { 0, 0, 153 }, + { 255, 255, 102 }, { 255, 204, 102 }, { 255, 153, 102 }, { 255, 102, 102 }, + { 255, 51, 102 }, { 255, 0, 102 }, { 255, 255, 51 }, { 255, 204, 51 }, + { 255, 153, 51 }, { 255, 102, 51 }, { 255, 51, 51 }, { 255, 0, 51 }, + { 255, 255, 0 }, { 255, 204, 0 }, { 255, 153, 0 }, { 255, 102, 0 }, + { 255, 51, 0 }, { 255, 0, 0 }, { 204, 255, 102 }, { 204, 204, 102 }, + { 204, 153, 102 }, { 204, 102, 102 }, { 204, 51, 102 }, { 204, 0, 102 }, + { 204, 255, 51 }, { 204, 204, 51 }, { 204, 153, 51 }, { 204, 102, 51 }, + { 204, 51, 51 }, { 204, 0, 51 }, { 204, 255, 0 }, { 204, 204, 0 }, + { 204, 153, 0 }, { 204, 102, 0 }, { 204, 51, 0 }, { 204, 0, 0 }, + { 153, 255, 102 }, { 153, 204, 102 }, { 153, 153, 102 }, { 153, 102, 102 }, + { 153, 51, 102 }, { 153, 0, 102 }, { 153, 255, 51 }, { 153, 204, 51 }, + { 153, 153, 51 }, { 153, 102, 51 }, { 153, 51, 51 }, { 153, 0, 51 }, + { 153, 255, 0 }, { 153, 204, 0 }, { 153, 153, 0 }, { 153, 102, 0 }, + { 153, 51, 0 }, { 153, 0, 0 }, { 102, 255, 102 }, { 102, 204, 102 }, + { 102, 153, 102 }, { 102, 102, 102 }, { 102, 51, 102 }, { 102, 0, 102 }, + { 102, 255, 51 }, { 102, 204, 51 }, { 102, 153, 51 }, { 102, 102, 51 }, + { 102, 51, 51 }, { 102, 0, 51 }, { 102, 255, 0 }, { 102, 204, 0 }, + +``` + +``` + +{ 102, 153, 0 }, { 102, 102, 0 }, { 102, 51, 0 }, { 102, 0, 0 }, +{ 51, 255, 102 }, { 51, 204, 102 }, { 51, 153, 102 }, { 51, 102, 102 }, +{ 51, 51, 102 }, { 51, 0, 102 }, { 51, 255, 51 }, { 51, 204, 51 }, +{ 51, 153, 51 }, { 51, 102, 51 }, { 51, 51, 51 }, { 51, 0, 51 }, +{ 51, 255, 0 }, { 51, 204, 0 }, { 51, 153, 0 }, { 51, 102, 0 }, +{ 51, 51, 0 }, { 51, 0, 0 }, { 0, 255, 102 }, { 0, 204, 102 }, +{ 0, 153, 102 }, { 0, 102, 102 }, { 0, 51, 102 }, { 0, 0, 102 }, +{ 0, 255, 51 }, { 0, 204, 51 }, { 0, 153, 51 }, { 0, 102, 51 }, +{ 0, 51, 51 }, { 0, 0, 51 }, { 0, 255, 0 }, { 0, 204, 0 }, +{ 0, 153, 0 }, { 0, 102, 0 }, { 0, 51, 0 }, { 17, 17, 17 }, +{ 34, 34, 34 }, { 68, 68, 68 }, { 85, 85, 85 }, { 119, 119, 119 }, +{ 136, 136, 136 }, { 170, 170, 170 }, { 187, 187, 187 }, { 221, 221, 221 }, +{ 238, 238, 238 }, { 192, 192, 192 }, { 128, 0, 0 }, { 128, 0, 128 }, +{ 0, 128, 0 }, { 0, 128, 128 }, { 0, 0, 0 }, { 0, 0, 0 }, +{ 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 }, +{ 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 }, +{ 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 }, +{ 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 }, +{ 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 }, +{ 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 }, { 0, 0, 0 } +}; + +``` + +# --- Annex H (informative): Development Guidelines for Creation of Polyphony Using SP-MIDI + +While Scalable Polyphony-MIDI (SP-MIDI) [38] is a full-featured standard for synthesizing music, using a few guidelines SP-MIDI [38, 39] can be optimized for wireless devices. These guidelines can be grouped as optimizing individual notes, and to minimize the overall size of a melody. + +## --- H.1. Running status + +In the Musical Instrument Digital Interface (MIDI) standard, a key-on or a key-off event will use at most three bytes each, cf. [40]. However, in case several key events occur on the same MIDI-channel, running status can be used. In principle running status means that the first byte of, e.g. key-on is omitted. In addition, the key-on event having a velocity of zero is equivalent to the key-off event. Thus, combining running status and using key-on with zero velocity, as the key-off event will reduce the number of bytes needed to encode key events. + +EXAMPLE: Without running status, the sequence + +91 2E 23 8E, 91 2B 50 8E, 81 2E 64 00, 81 2B 64 00 + +means “Key 2E ON” Velocity 23 MIDI Ch 1”, “Key 2B ON Velocity 50 MIDI Ch 1”, “Key 2E OFF Velocity 64 MIDI Ch 1”, “Key 2B OFF Velocity 64 MIDI Ch 1”. Using running status will reduce the sequence into + +91 2E 23 8E, 2B 50 8E, 2E 00 00, 2B 00 00, + +That is, the command byte is omitted and velocity zero is used for key off. + +## --- H.2 File type considerations + +The SP-MIDI content can be stored in, a Standard MIDI File (SMF) of type 0 or type 1 [40]. In a type 0 SMF, one header chunk and one track chunk is used. In a type 1 SMF one header chunk and several track chunks are used. SMF type 2 should not be used + +## --- H.3 File size reduction + +In general it is more efficient to store the MIDI data as a type 1 file. The increased efficiency is reached if each track contains one MIDI channel and one instrument (This is often the case). Evidently, running status can be applied on each individual track reducing the track size. To further reduce the size of the file use one track per used MIDI channel. That is, if a temple/conductor track exists merge it with the first instrument track. Remove, all meta events which are not necessary, e.g. "track name", "lyric". To summarize, the following measures can be taken in order to reduce the SMF: + +- 1) use SMF type 1 (or check if type 1 is smaller than type 0 and use the smallest); +- 2) use running status; +- 3) one and only one instrument per track. Try not to change channels; +- 4) do not change tempo in the middle of the music, i.e., only set tempo once; +- 5) use beat, instead of SMPTE, to set tempo; +- 6) copyright is on automatically; +- 7) remove controller messages, which are optional according to [39]; +- 8) turn off the options below: + +- sequence Number - MIDI sequence ids; +- text - embedded text for anything; + +- sequence / track name; +- instrument name; +- lyric; +- marker - for synchronization purposes; +- cue point; +- midi channel prefix - associate channels with all events following; +- sequencer-specific settings. + +Items 1 to 3 above optimize the notes, while items 4 to 8 optimize the overall melody. The above measures will provide an SMF, which is ready for compression. However, prior to compression the composer/content author can consider to use few values for key velocity and thereby increasing the redundancy of the file. + +## --- H.4 Restrictions + +Content creators should not expect the full support for the following features: + +- MIDI message channel pressure; +- MIDI message pitch bend; +- individual stereophonic panoramic (pan) as expressed in table 5 in [39]; +- MIDI message master volume. + +Content creators should not expect a time granularity better than 5ms to be supported by the SME. + +To ensure interoperability, the first value of the MIP table should be no more than 6 voices. + +# Annex I (normative): SMS in MME + +## I.1 General + +An EPS network using SMS in MME delivers short message services over EPS NAS signalling. + +For the architecture and the definition of reference points for SMS in MME see 3GPP TS 23.272 [45], annex C. + +Between the architecture and the reference points for SMS in MME and the architecture and the reference points shown in subclause 4.1, figure 5, of the present specification the following mapping can be established: + +**Table I.1: Mapping between architecture and reference points for SMS in MME and the present specification** + +| | SMS in MME | present specification | +|--------------------------------------------------------------------------------------|--------------------------------|-------------------------| +| Network entities | HSS | HLR | +| | MME | MSC + VLR | +| | E-UTRAN | (not shown in figure 5) | +| | UE | MS | +| | (not applicable) | MME (NOTE 1) | +| Reference points | S6a | (not shown in figure 5) | +| | S6c/C | 2 | +| | SGd | 3 | +| | (not applicable, MME internal) | 4 | +| | Uu + S1-MME | 5 | +| | (not applicable) | 6 | +| NOTE 1: In figure 5, the MME is only acting as a relay for SMS transfer via the SGs. | | | + +For the purpose of supporting SMS in MME, the MME shall implement the requirements specified in the present specification for the MSC and the VLR with the following modifications: + +- 1) "GSM/UMTS system" is to be replaced with "EPS". +- 2) Throughout the text and in the figures, message names, parameter names and cause values: + - "MSC" is to be replaced with "MME"; + - "VLR" is to be replaced with "MME internal subscriber register"; + - "HLR" is to be replaced with "HSS/HLR"; + - "MS" is to be replaced with "UE"; + - "non GPRS" is to be replaced with "EPS"; + - "IMSI detached" is to be replaced with "EPS detached". +- 3) The protocol used on reference point 2 (reference point S6c) is based on Diameter (see 3GPP TS 29.338 [50]). + +- 4) The protocol used on reference point 3 is based on Diameter (see 3GPP TS 29.338 [50]). +- 5) Reference point 4 is MME internal, and operations performed on this reference point are not standardized. In the message flows of clause 10, the MME replaces the combination of MSC and VLR, and messages exchanged between MSC and VLR are replaced with MME internal communication. +- 6) The protocol used between HSS and MME (reference point S6a) is based on Diameter (see 3GPP TS 29.272 [46]). In the alert procedure in subclause 10.3: + +MAP ReadyForSM is to be replaced with Diameter NotifyRequest (ReadyforSM). + +## --- I.2 Registration of MME for SMS + +The registration (and removal of registration) procedures for SMS in MME are described in 3GPP TS 23.272 [45]. + +I.2.1 Void + +I.2.2 Void + +--- + +Annex J (informative): +Change history + +| TSG | TSG TDoc | Vers | CR | Rev | Ph | Cat | Subject | New Vers | Work Item | +|------|-----------|-------|-----|-----|------|-----|--------------------------------------------------------------------------------------------------------------|----------|------------| +| T#4 | TP-99126 | 2.0.0 | New | | | | Creation of 3GPP 23.040 v3.0.0 out of GSM 03.40 v7.1.0 | 3.0.0 | | +| T#4 | TP-99124 | 3.0.0 | 001 | | R99 | A | Clarification concerning SMSC address checking in the MS for concatenated messages and replace message types | 3.1.0 | TEI | +| T#4 | TP-99146 | 3.0.0 | 002 | | R99 | A | Guidance regarding the SMSC address in a Status Report | 3.1.0 | TEI | +| T#5 | TP-99177 | 3.1.0 | 003 | | R99 | A | Change to reserved port number range for SMS | 3.2.0 | TEI | +| T#5 | TP-99177 | 3.1.0 | 004 | | R99 | B | New TP-PID value for delivery of ANSI-136 Short Messages | 3.2.0 | SMS | +| T#5 | TP-99177 | 3.1.0 | 005 | | R99 | D | IEI values in concatenated SM's | 3.2.0 | SMS | +| T#6 | TP-99237 | 3.2.0 | 007 | | R99 | F | Adaptations for UMTS | 3.3.0 | TEI | +| T#6 | TP-99237 | 3.2.0 | 006 | | R99 | C | Duplicate messages | 3.3.0 | TEI | +| T#6 | TP-99237 | 3.2.0 | 008 | | R99 | A | Concatenated Short Message | 3.3.0 | TEI | +| T#7 | TP-000024 | 3.3.0 | 009 | | R99 | B | Enhancement of the Message Content in SMS | 3.4.0 | MMS | +| T#7 | TP-000024 | 3.3.0 | 010 | | R99 | B | Multiple Information Elements | 3.4.0 | TEI | +| T#7 | TP-000024 | 3.3.0 | 011 | | R99 | B | SMS E-MAIL PARAMETERS | 3.4.0 | TEI | +| - | - | 3.4.0 | - | - | R99 | - | Editorial graphics update to make visible | 3.4.1 | - | +| T#8 | TP-000073 | 3.4.1 | 012 | | R99 | F | Alignment in Enhanced Messaging Service | 3.5.0 | EMS | +| T#8 | TP-000073 | 3.4.1 | 014 | | R99 | F | Correction to text on SMS TimeZone | 3.5.0 | TEI | +| T#8 | TP-000073 | 3.4.1 | 015 | | R99 | F | Correction of TP-PID | 3.5.0 | TEI | +| T#8 | TP-000074 | 3.5.0 | 013 | | Rel4 | B | Addition of numbering plan value for Service Centre Specific Addresses | 4.0.0 | TEI | +| T#9 | TP-000144 | 4.0.0 | 016 | | Rel4 | F | Presence of TP-PI | 4.1.0 | SMS TEI | +| T#9 | TP-000144 | 4.0.0 | 017 | | Rel4 | D | Big endian integer representation | 4.1.0 | SMS TEI | +| T#9 | TP-000144 | 4.0.0 | 018 | | Rel4 | B | SMS Address fields section needs clarification | 4.1.0 | SMS TEI | +| T#9 | TP-000144 | 4.0.0 | 019 | | Rel4 | B | User prompt indication | 4.1.0 | SMS TEI | +| T#11 | TP-010029 | 4.1.0 | 020 | | Rel4 | C | Predefined animations for EMS | 4.2.0 | TEI4 | +| T#11 | TP-010029 | 4.1.0 | 021 | | Rel4 | C | Message Waiting Indication Status storage on the USIM | 4.2.0 | UICC1-CPHS | +| T#12 | TP-010128 | 4.2.0 | 023 | | Rel4 | F | Clarification of User Prompt Indicator | 4.3.0 | TEI4 | +| T#12 | TP-010128 | 4.2.0 | 025 | | Rel4 | F | Clarification of Email Addressing for Email – SMS Interworking | 4.3.0 | TEI4 | +| T#12 | TP-010128 | 4.2.0 | 026 | | Rel4 | F | Removal of duplicated values in TP-PID section | 4.3.0 | TEI4 | +| T#12 | TP-010128 | 4.2.0 | 027 | | Rel4 | F | Application Port Addressing Clarification | 4.3.0 | TEI4 | +| T#12 | TP-010128 | 4.3.0 | 022 | | Rel5 | B | Addition of text and background colour | 5.0.0 | MESS5-EMS | +| T#12 | TP-010128 | 4.3.0 | 024 | | Rel5 | B | Object Distribution Indicator | 5.0.0 | MESS5-EMS | +| T#12 | TP-010149 | 4.3.0 | 028 | 1 | Rel5 | B | Extended Objects in EMS | 5.0.0 | MESS5-EMS | +| T#13 | TP-010194 | 5.0.0 | 029 | | Rel5 | B | Hyperlink Information Element | 5.1.0 | TEI5 | +| T#13 | TP-010194 | 5.0.0 | 031 | | Rel5 | A | Removal of EMS PID | 5.1.0 | TEI5 | +| T#13 | TP-010194 | 5.0.0 | 033 | | Rel5 | B | EMS Delivery Request | 5.1.0 | TEI5 | +| T#14 | TP-010280 | 5.1.0 | 034 | | Rel5 | F | Correction of Data Format Delivery Request | 5.2.0 | TEI5 | +| T#14 | TP-010280 | 5.1.0 | 035 | | Rel5 | F | Information Element Classification | 5.2.0 | TEI5 | +| T#14 | TP-010280 | 5.1.0 | 036 | | Rel5 | F | Clarification of LZSS compression for “EXTENDED OBJECTS” in EMS | 5.2.0 | MESS5_E MS | +| T#14 | TP-010280 | 5.1.0 | 037 | | Rel5 | F | Extended Object Positioning | 5.2.0 | TEI5 | +| T#14 | TP-010280 | 5.1.0 | 040 | | Rel5 | F | Correction on SMS Information Element Data Length | 5.2.0 | TEI5 | +| T#15 | TP-020015 | 5.2.0 | 041 | | Rel5 | B | Wireless Vector Graphics in EMS | 5.3.0 | MESS5_E MS | +| T#15 | TP-020079 | 5.2.0 | 042 | 1 | Rel5 | B | Polyphonic Extended Object | 5.3.0 | MESS5_E MS | +| T#15 | TP-020015 | 5.2.0 | 045 | | Rel5 | A | MO-SMS duplicate message response | 5.3.0 | TEI5 | +| T#15 | TP-020015 | 5.2.0 | 046 | 1 | Rel5 | B | Subaddressing scheme for SMS | 5.3.0 | TEI5 | +| T#15 | TP-020015 | 5.2.0 | 047 | | Rel5 | B | Alternate Reply Address Element | 5.3.0 | TEI5 | +| T#15 | TP-020015 | 5.2.0 | 048 | | Rel5 | C | Extended Object Data Request Command | 5.3.0 | MESS5_E MS | +| T#16 | TP-020104 | 5.3.0 | 049 | | Rel5 | F | Clarification of bit value combinations within TP-PI | 5.4.0 | TEI5 | +| T#16 | TP-020104 | 5.3.0 | 050 | | Rel5 | F | References to the TP-RD bit | 5.4.0 | TEI5 | +| T#16 | TP-020104 | 5.3.0 | 051 | | Rel5 | F | TP-DCS values for SIM data download | 5.4.0 | TEI5 | +| T#16 | TP-020104 | 5.3.0 | 054 | | Rel5 | C | Clarification of the requirement for type 0 Short Messages | 5.4.0 | TEI5 | +| T#16 | TP-020104 | 5.3.0 | 055 | | Rel5 | F | Occurrence of the Reply Address Element | 5.4.0 | TEI5 | +| T#16 | TP-020104 | 5.3.0 | 056 | | Rel5 | F | WVG Corrections and Clarifications | 5.4.0 | MESS5-EMS | +| T#16 | TP-020104 | 5.3.0 | 057 | | Rel5 | F | WVG Corrections and Clarifications | 5.4.0 | MESS5-EMS | + +| | | | | | | | | | | +|---------|-----------|--------|------|---|--------|---|------------------------------------------------------------------------------------------------------------------|--------|---------------| +| T#16 | TP-020104 | 5.3.0 | 058 | | Rel5 | F | WVG Clarifications for websafe color | 5.4.0 | MESS5-EMS | +| T#16 | TP-020104 | 5.3.0 | 059 | | Rel5 | F | Add repeat and bouncing to Standard Animation for consistency with Simple Animation | 5.4.0 | MESS5-EMS | +| T#16 | TP-020104 | 5.3.0 | 060 | | Rel5 | F | Allow angle applied to special shape grid for consistency with other special shape elements | 5.4.0 | MESS5-EMS | +| T#17 | TP-020204 | 5.4.0 | 061 | | Rel5 | F | Error in MS example error | 5.5.0 | TEI5 | +| T#17 | TP-020204 | 5.5.0 | 062 | | Rel6 | F | Identification of a directory number in the User Data Field | 6.0.0 | TEI6 | +| T#17 | | 6.0.0 | | | | | Addition of compression_test_vectors.zip to the specification zip-file | 6.0.1 | | +| T#20 | TP-030114 | 6.0.1 | 063 | | Rel6 | F | Reserved values in TP-Status | 6.1.0 | TEI6 | +| T#20 | TP-030114 | 6.0.1 | 067 | | Rel6 | A | Missing SMSs over MSC even if the MS is capable of such sending | 6.1.0 | TEI6 | +| T#21 | TP-030173 | 6.1.0 | 068 | | Rel6 | C | Videomail message waiting indication in TP-UDH | 6.2.0 | TEI6 | +| T#23 | TP-040049 | 6.2.0 | 070 | | Rel6 | A | Correction of error message for MAP_ForwardShortMessage | 6.3.0 | TEI5 | +| T#23 | TP-040059 | 6.2.0 | 071 | 1 | Rel6 | C | Procedure for confirming the existence of an SMS interworking agreement | 6.3.0 | TEI6 | +| T#24 | TP-040096 | 6.3.0 | 072 | 1 | Rel6 | B | Enhanced Voice Mail Information | 6.4.0 | TEI6 | +| T#24 | TP-040094 | 6.3.0 | 073 | | Rel6 | F | Optional IEI's | 6.4.0 | TEI6 | +| T#25 | TP-040200 | 6.4.0 | 076 | 1 | Rel6 | B | Special Message Indication – introduction of Multiple Subscriber Profiles | 6.5.0 | TEI4, TEI6 | +| T#25 | TP-040171 | 6.4.0 | 077 | | Rel6 | F | Enhanced Voice Mail Information – access number priority | 6.5.0 | TEI6 | +| CT#30 | CP-050545 | 6.5.0 | 082 | 1 | Rel-6 | F | Reference corrections | 6.6.0 | TEI6 | +| CT#31 | CP-060113 | 6.6.0 | 0084 | - | Rel-6 | F | Correction of reference [28] | 6.7.0 | TEI6 | +| CT#33 | CP-060457 | 6.7.0 | 0087 | | Rel-6 | F | Max user data length in GSM 7bit concatenated uncompressed message with 16 bit reference number | 6.8.0 | TEI6 | +| 2006-10 | | 6.8.0 | | | | | Adds compression test vectors file (identical to those of v6.6.0). | 6.8.1 | | +| 2007-03 | CP-070145 | 6.8.1 | 0088 | 2 | Rel-7 | B | Addition of capability to route MT-SMs via the HPLMN of the receiving MS | 7.0.0 | SMSviaH | +| 2007-03 | CP-070154 | 6.8.1 | 0091 | - | Rel-7 | F | Mapping of SIP error codes to RP-ERROR | 7.0.0 | SMSIP | +| 2007-03 | CP-070154 | 6.8.1 | 0090 | 1 | Rel-7 | B | SMS over IP | 7.0.0 | SMSIP | +| 2007-03 | CP-070155 | 6.8.1 | 0089 | 1 | Rel-7 | F | MNRR correction | 7.0.0 | TEI7 | +| 2007-03 | | 7.0.0 | | | | | Version 7.0.1 created by MCC (Figure 3 was the area of overlapping CRs- "MNRR" box split according to CR#0089r1) | 7.0.1 | | +| 2007-12 | CP-070815 | 7.0.1 | 0092 | 1 | Rel-8 | C | SMS Router Optimization | 8.0.0 | TEI8 | +| 2008-03 | CP-080137 | 8.0.0 | 0094 | | Rel-8 | | language specific extension of the GSM7 alphabet | 8.1.0 | TEI8 | +| 2008-06 | CP-080337 | 8.1.0 | 0100 | 1 | Rel-8 | A | Correction to clearing of mobile not reachable flags | 8.2.0 | TEI | +| 2008-09 | CP-080536 | 8.2.0 | 0101 | 1 | Rel-8 | F | SMS 16 bit port addressing. Clarification of IANA's role | 8.3.0 | TEI8 | +| 2008-09 | | 8.2.0 | | | | | Editorial corrections by MCC | 8.3.0 | | +| 2009-03 | CP-090122 | 8.3.0 | 0104 | 1 | Rel-8 | A | SM termination correction | 8.4.0 | SMSIP | +| 2009-03 | | | | | Rel-8 | | Editorial cleanup by MCC | 8.4.0 | | +| 2009-06 | CP-090413 | 8.4.0 | 0107 | | Rel-8 | F | UE reachability notification from IP-SM-GW | 8.5.0 | SAES | +| 2009-06 | CP-090430 | 8.5.0 | 0106 | 1 | Rel-9 | B | SMS Message Loop prevention | 9.0.0 | TEI9 | +| 2009-09 | CP-090679 | 9.0.0 | 0109 | 1 | Rel-9 | A | Clarification of reset of UNRI and UNRR | 9.1.0 | TEI8 | +| 2010-03 | CP-100135 | 9.1.0 | 0110 | 2 | Rel-9 | F | SMS. Removal of obsolete reference to TS 43.047 | 9.2.0 | TEI9 | +| 2010-06 | CP-100501 | 9.2.0 | 0111 | 5 | Rel-9 | F | RP-OA modification in SMS Router | 9.3.0 | TEI9 | +| 2011-03 | CP-110197 | 9.3.0 | 0112 | 1 | Rel-10 | F | MS recovery from SMS memory full situation | 10.0.0 | TEI10 | +| 2011-12 | | 10.0.0 | | | | F | Correction of mapping of SIP transport errors to RP-ERRORs | 11.0.0 | | +| | CP-110882 | | 0113 | | Rel-11 | | | | TEI11 | +| 2012-03 | CP-120125 | 11.0.0 | 0116 | 1 | Rel-11 | F | IETF reference update | 11.1.0 | TEI11 | +| 2012-06 | | 11.1.0 | | | | B | | 11.2.0 | SIMTC-PS_Only | +| | CP-120315 | | 0117 | 6 | Rel-11 | | Support of SMS in MME | | | +| 2012-06 | | 11.1.0 | | | | B | | 11.2.0 | SIMTC-PS_Only | +| | CP-120315 | | 0119 | 2 | Rel-11 | | Mobile station not reachable flag stored in the MME | | | +| 2012-06 | | 11.1.0 | | | | B | SMS network structure update for supporting SMS over SGs | 11.2.0 | | +| | CP-120309 | | 0124 | 1 | Rel-11 | | | | TEI11 | +| 2012-06 | | 11.1.0 | | | | B | Addition of application port address for device triggering | 11.2.0 | SIMTC-Reach | +| | CP-120315 | | 0126 | 1 | Rel-11 | | | | | +| 2012-06 | | 11.1.0 | | | | B | | 11.2.0 | SIMTC-Reach | +| | CP-120315 | | 0125 | 1 | Rel-11 | | Addition of external identifier | | | +| 2012-09 | | 11.2.0 | | | | F | | 11.3.0 | SIMTC-Reach | +| | CP-120589 | | 0128 | | Rel-11 | | External Identifier at the SMS Router | | | +| 2012-09 | | 11.2.0 | | | | B | | 11.3.0 | SIMTC-Reach | +| | CP-120589 | | 0129 | 1 | Rel-11 | | Functionalities to be supported by SMS Router | | | +| 2012-09 | | 11.2.0 | | | | F | | 11.3.0 | SIMTC-PS_Only | +| | CP-120589 | | 0131 | 1 | Rel-11 | | Clarification on Support of SMS in MME | | | +| 2012-09 | | 11.2.0 | | | | F | | 11.3.0 | SIMTC-Reach | +| | CP-120589 | | 0132 | | Rel-11 | | Alert-SC based on IMSI | | | + +| | | | | | | | | | | +|---------|-----------|--------|------|---|--------|---|------------------------------------------------|--------|---------------| +| 2012-09 | CP-120590 | 11.2.0 | 0130 | 5 | Rel-11 | B | Registration of MME for SMS | 11.3.0 | SIMTC-PS_Only | +| 2012-12 | CP-120803 | 11.3.0 | 0133 | 1 | Rel-11 | B | Filtering function to be supported by SMS-GMSC | 11.4.0 | SIMTC-Reach | +| 2012-12 | CP-120803 | 11.3.0 | 0134 | 1 | Rel-11 | F | Removal of Annex I.2 | 11.4.0 | SIMTC-PS_Only | +| 2013-03 | CP-130086 | 11.4.0 | 0135 | 5 | Rel-11 | F | Device triggering using TP-PID | 11.5.0 | SIMTC-Reach | +| 2013-03 | CP-130108 | 11.4.0 | 0136 | 1 | Rel-11 | F | Correction of S6c reference | 11.5.0 | SIMTC-PS_Only | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23057/02db3d5ca2c08af069727d3709c4a6fb_img.jpg b/marked/Rel-11/23_series/23057/02db3d5ca2c08af069727d3709c4a6fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..625346517dde0cf3940523f0dd8d35fce39dd8c6 --- /dev/null +++ b/marked/Rel-11/23_series/23057/02db3d5ca2c08af069727d3709c4a6fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cee24ed4a1390e796f63cb67c661784de26e5ec887446e5cfe65f5500c333d5e +size 7787 diff --git a/marked/Rel-11/23_series/23057/17f0cf80b9c38adb460d4ca836960da7_img.jpg b/marked/Rel-11/23_series/23057/17f0cf80b9c38adb460d4ca836960da7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06699e04aeea04e391d522bc8ac60e6efec4326a --- /dev/null +++ b/marked/Rel-11/23_series/23057/17f0cf80b9c38adb460d4ca836960da7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0a681d5eda357d7b7e9407605aff5f9ab643388d1df0d8d5527ac934a3de152 +size 36707 diff --git a/marked/Rel-11/23_series/23057/2db815c41ab92ee70773412b284e1431_img.jpg b/marked/Rel-11/23_series/23057/2db815c41ab92ee70773412b284e1431_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85354101af4c4f7dd499dedce5ec5084222eeb07 --- /dev/null +++ b/marked/Rel-11/23_series/23057/2db815c41ab92ee70773412b284e1431_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5e6caf2f0015577ea6293696fd72d645ea241803135f455861cf7400e54d626 +size 30837 diff --git a/marked/Rel-11/23_series/23057/42c65f5cb106938992fc73c05c8713d2_img.jpg b/marked/Rel-11/23_series/23057/42c65f5cb106938992fc73c05c8713d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea23e969ef9ef62fc1ee53158c17d6f42548e268 --- /dev/null +++ b/marked/Rel-11/23_series/23057/42c65f5cb106938992fc73c05c8713d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98adc9bc0b66c25156772c8eecea37a751f5344020e3ca5a1d4291d2dcb9c266 +size 52059 diff --git a/marked/Rel-11/23_series/23057/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/23_series/23057/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47ef3fe9876d7abd7de7203c857d46c49bdf3f81 --- /dev/null +++ b/marked/Rel-11/23_series/23057/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3649f7f15ec0c9e3a6f341790e370f95dc1edd9ea72f9c1679b6b1c6bb1e1da0 +size 115025 diff --git a/marked/Rel-11/23_series/23057/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-11/23_series/23057/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4aa5cdf34bfd655c02bf43fe16de1863e76061e --- /dev/null +++ b/marked/Rel-11/23_series/23057/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02b02519809c31e8e12106cfa0dc5c2bb680e354b352690735ad790b03f78d41 +size 54536 diff --git a/marked/Rel-11/23_series/23057/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/23_series/23057/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ac13f152f0613fac5baa752d656770d670df1dc --- /dev/null +++ b/marked/Rel-11/23_series/23057/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:605e5691e08eb41ef239b6e44858fe82b0a14adc395162e5badf8cc6e30414ed +size 37285 diff --git a/marked/Rel-11/23_series/23057/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-11/23_series/23057/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec6abfcf425091fc9f79dd3f9c43fe793e4389ce --- /dev/null +++ b/marked/Rel-11/23_series/23057/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0c811fe83b6f4ce075499f057bcfc4b5afb69a1609f772933d980fd24a1f1a5 +size 77806 diff --git a/marked/Rel-11/23_series/23057/86f2406a1f65ffd689d0796f95fe7588_img.jpg b/marked/Rel-11/23_series/23057/86f2406a1f65ffd689d0796f95fe7588_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57ce1754950ea6d0515d03195c2d4406a2eec973 --- /dev/null +++ b/marked/Rel-11/23_series/23057/86f2406a1f65ffd689d0796f95fe7588_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29b718e5bb029b175a4437912a7a9b47020358ad5792b9d8a8293780f22a3114 +size 27849 diff --git a/marked/Rel-11/23_series/23057/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/23_series/23057/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f63367e68258e7e6156cb8515674d7ab42ac977f --- /dev/null +++ b/marked/Rel-11/23_series/23057/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82460c02ffb67a0e31ed5cf85d09903251c14b7b6a983eadad4eb6a9cb48f9e1 +size 152027 diff --git a/marked/Rel-11/23_series/23057/9edb407536d4d4d4a6ac391527af047c_img.jpg b/marked/Rel-11/23_series/23057/9edb407536d4d4d4a6ac391527af047c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..368c38ebe2caf519e2de4ed7ae8fcdfc9216699c --- /dev/null +++ b/marked/Rel-11/23_series/23057/9edb407536d4d4d4a6ac391527af047c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b31b6f2aee867739397f5462a866471a1a7b39121f1e2c0f32ed65f074af360 +size 34550 diff --git a/marked/Rel-11/23_series/23057/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-11/23_series/23057/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd684fc3f8a4b5e5e9cc76d3c990c78790566d17 --- /dev/null +++ b/marked/Rel-11/23_series/23057/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3613f1c14eb02c01385f815a62ef097f702df2c1e1d5e02a03bd6be5caea0aa5 +size 103762 diff --git a/marked/Rel-11/23_series/23057/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/23_series/23057/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcc2496dd38b5a78b9a2988ad425fccad78982a9 --- /dev/null +++ b/marked/Rel-11/23_series/23057/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b7972c147e9347685374735465d68d32ed201b1038aa7311f0e112014ae9ad1 +size 70467 diff --git a/marked/Rel-11/23_series/23057/b63f41ca262d8ce9ef8affb62607f32b_img.jpg b/marked/Rel-11/23_series/23057/b63f41ca262d8ce9ef8affb62607f32b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06699e04aeea04e391d522bc8ac60e6efec4326a --- /dev/null +++ b/marked/Rel-11/23_series/23057/b63f41ca262d8ce9ef8affb62607f32b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0a681d5eda357d7b7e9407605aff5f9ab643388d1df0d8d5527ac934a3de152 +size 36707 diff --git a/marked/Rel-11/23_series/23057/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/23_series/23057/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3978a67082e633c16830224206177fa778100ea --- /dev/null +++ b/marked/Rel-11/23_series/23057/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:032d0ea07483b1b3d3359d27dead745a2d53bf65e1f65603eea0cff571472c9c +size 107005 diff --git a/marked/Rel-11/23_series/23057/cf018d13814389b0bd7f94a2f9bb812a_img.jpg b/marked/Rel-11/23_series/23057/cf018d13814389b0bd7f94a2f9bb812a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..494b68bad9f59c6f224c33e80d615d80afeab5ac --- /dev/null +++ b/marked/Rel-11/23_series/23057/cf018d13814389b0bd7f94a2f9bb812a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8ed4ca4fb4c2e433506cddabca19ee763bae5e865ffa57ca11a4315fb051a5b +size 35388 diff --git a/marked/Rel-11/23_series/23057/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/marked/Rel-11/23_series/23057/ea4fd10a9a501c602f2bea0f7f711877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..281b4dbfdfd941129f9d6052b72d5c2d77f7d290 --- /dev/null +++ b/marked/Rel-11/23_series/23057/ea4fd10a9a501c602f2bea0f7f711877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4faf4604bd5a00455245a9d618e4f9425bb283362392016aaa701c14947f486f +size 53792 diff --git a/marked/Rel-11/23_series/23057/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg b/marked/Rel-11/23_series/23057/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21bb6490e895039a9940e0239ce116db2d151b1a --- /dev/null +++ b/marked/Rel-11/23_series/23057/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05f67aa07b68f12e91f3afd9251f01aba44921c028be87d9ed1a57daab199308 +size 80541 diff --git a/marked/Rel-11/23_series/23057/f4b570ddd089f54943d46e9f8776f9f9_img.jpg b/marked/Rel-11/23_series/23057/f4b570ddd089f54943d46e9f8776f9f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cefd4852c0249b9fba9ba6c020918fc5e698af13 --- /dev/null +++ b/marked/Rel-11/23_series/23057/f4b570ddd089f54943d46e9f8776f9f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5038bb35d5b54ffe5c0b060107b7db81c9c19fe596069328f5661f8b2d1ddf1 +size 35352 diff --git a/marked/Rel-11/23_series/23057/raw.md b/marked/Rel-11/23_series/23057/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5bd475deabd00c41d6ad14b1335605ea8cdc32ba --- /dev/null +++ b/marked/Rel-11/23_series/23057/raw.md @@ -0,0 +1,2956 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Abbreviations ..... | 12 | +| 4 MExE basic principles ..... | 14 | +| 4.1 Generic MExE aspects ..... | 14 | +| 4.2 High level architecture ..... | 14 | +| 4.3 Multiple classmark support ..... | 15 | +| 4.3.1 Classmark 1 service support in non-Classmark 1 MExE devices ..... | 15 | +| 4.3.2 Classmark 2 service support in non-Classmark 2 MExE devices ..... | 16 | +| 4.3.3 Classmark 3 service support in non-Classmark 3 MExE devices ..... | 16 | +| 4.3.4 Classmark 4 service support in non-Classmark 4 MExE devices ..... | 16 | +| 5 Generic MExE functions (excluding security)..... | 16 | +| 5.1 User profile..... | 16 | +| 5.1.1 Location of, access to, and security of, the user profile ..... | 16 | +| 5.1.2 Support of the user profile ..... | 17 | +| 5.1.3 User interface personalisation ..... | 18 | +| 5.1.3.1 MExE user interface personalisation ..... | 18 | +| 5.1.3.2 Support of MExE user interface personalisation ..... | 18 | +| 5.1.4 Virtual home environment..... | 19 | +| 5.2 Capability and content negotiation..... | 19 | +| 5.2.1 User profile and capability negotiation relationship..... | 20 | +| 5.2.2 Capability negotiation characteristics..... | 20 | +| 5.2.3 Client content capability report ..... | 22 | +| 5.2.4 Server role in capability negotiation..... | 22 | +| 5.2.5 Client-driven negotiation..... | 22 | +| 5.3 Provisioning and management of services ..... | 22 | +| 5.3.1 Service discovery..... | 22 | +| 5.3.2 Service transfer ..... | 23 | +| 5.3.3 Service installation and configuration ..... | 23 | +| 5.3.4 Service management..... | 23 | +| 5.3.5 Service termination..... | 23 | +| 5.3.6 Service deletion ..... | 23 | +| 5.4 User control of application connections..... | 24 | +| 5.4.1 Journaling of network events..... | 24 | +| 5.4.2 User notification ..... | 24 | +| 5.5 Quality of service ..... | 24 | +| 5.5.1 Introduction ..... | 26 | +| 5.5.2 MExE QoS support..... | 26 | +| 5.5.3 MExE QoS manager..... | 27 | +| 5.5.4 Network control API ..... | 27 | +| 5.5.5 MExE QoS API ..... | 27 | +| 5.5.6 Sources of bearer service parameters ..... | 28 | +| 5.5.7 QoS streams..... | 28 | +| 5.5.8 QoS security ..... | 28 | +| 5.6 Charging..... | 28 | +| 5.6.1 Generic charging support ..... | 29 | +| 6 Generic MExE Security ..... | 29 | +| 6.1 Introduction ..... | 29 | +| 6.2 MExE executable integrity..... | 29 | +| 6.2.1 Full signature verification..... | 30 | +| 6.2.2 Optimised pre-launch signature verification ..... | 30 | +| 6.3 MExE executable permissions ..... | 30 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------------------------|----| +| 6.3.1 | MExE executable permissions for operator, manufacturer and third party security domains ..... | 30 | +| 6.3.2 | MExE executable permissions for untrusted MExE executables..... | 33 | +| 6.4 | Handling of MExE executables when their valid root public key is not available ..... | 34 | +| 6.4.1 | Launching of MExE executables when their valid RPK is not available..... | 35 | +| 6.4.2 | Currently executing secure MExE executables when their valid RPK is no longer available ..... | 35 | +| 6.5 | User permission types ..... | 35 | +| 6.6 | Root Public keys..... | 36 | +| 6.6.1 | Operator root public key..... | 36 | +| 6.6.1.1 | Caching of root public keys ..... | 37 | +| 6.6.1.2 | MExE device actions on detection of valid (U)SIM application and/or power up..... | 37 | +| 6.6.2 | Manufacturer root public key ..... | 39 | +| 6.6.3 | Third party root public key ..... | 39 | +| 6.7 | Certification and authorisation architecture ..... | 40 | +| 6.7.1 | Certification requirements ..... | 40 | +| 6.7.1.1 | MExE terminal requirements for certificate processing ..... | 40 | +| 6.7.2 | Certification administration requirements ..... | 41 | +| 6.7.3 | Example certification process..... | 41 | +| 6.7.4 | Certificate Chain Verification ..... | 42 | +| 6.8 | Usage of Signed Content..... | 44 | +| 6.8.1 | Signed packages used for installation..... | 44 | +| 6.8.2 | Installation of root certificates in a signed data package..... | 45 | +| 6.8.3 | Installation of other signed data ..... | 45 | +| 6.9 | Certificate Format ..... | 46 | +| 6.9.1 | Certificate extension for removal of network access..... | 46 | +| 6.9.1.1 | X.509 version 3 ..... | 46 | +| 6.10 | Certificate management..... | 46 | +| 6.10.1 | Certificate configuration message (CCM)..... | 47 | +| 6.10.1.1 | CCM numbering convention ..... | 50 | +| 6.10.1.2 | CCM order of transmission..... | 50 | +| 6.10.1.3 | CCM field mapping convention ..... | 50 | +| 6.10.1.4 | Authorised CCM download mechanisms ..... | 50 | +| 6.11 | Separation of I/O streams ..... | 50 | +| 6.12 | Core software download..... | 51 | +| 6.13 | Administrator Concept ..... | 51 | +| 6.13.1 | Administrator root public key ..... | 51 | +| 6.13.2 | Provisioned mechanism for designating administrative responsibilities and adding third parties in a MExE device ..... | 52 | +| 6.13.3 | MExE administrator determination mechanism..... | 52 | +| 6.13.3.1 | Determining the administrator of the MExE device ..... | 52 | +| 6.13.3.2 | Determining the administrator of the MExE device, for MExE-(U)SIM supporting third party certificates ..... | 53 | +| 6.13.3.2.1 | Administrator of the MExE device is the user ..... | 53 | +| 6.13.3.2.2 | Administrator of the MExE device is not the user ..... | 54 | +| 6.13.4 | Administrator root certificate download mechanism ..... | 55 | +| 7 | MExE Classmark 1 (WAP environment)..... | 56 | +| 7.1 | Introduction ..... | 56 | +| 7.1.1 | WAP MExE devices..... | 56 | +| 7.1.2 | High level architecture..... | 56 | +| 7.2 | Non Security..... | 56 | +| 7.2.1 | WAP components..... | 56 | +| 7.2.2 | Services..... | 57 | +| 7.2.2.1 | User interface ..... | 57 | +| 7.2.2.2 | Access points ..... | 57 | +| 7.2.2.3 | Transferring ..... | 58 | +| 7.2.2.3.1 | WSP and HTTP/1.1 Proxy Function ..... | 58 | +| 7.2.3 | WAP charging support ..... | 59 | +| 7.2.4 | CC/PP over WSP (Classmark 1) ..... | 59 | +| 7.3 | Security..... | 59 | +| 7.3.1 | Call control ..... | 59 | +| 7.3.2 | Local phonebook ..... | 59 | + +| | | | +|-----------------------------|--------------------------------------------------------------------|-----------| +| 8 | MExE Classmark 2 (PersonalJava environment)..... | 59 | +| 8.1 | Introduction ..... | 59 | +| 8.1.1 | Classmark 2 MExE devices..... | 60 | +| 8.1.2 | High level architecture..... | 60 | +| 8.2 | Non Security..... | 60 | +| 8.2.1 | High level functions ..... | 60 | +| 8.2.1.1 | Optional Java packages..... | 60 | +| 8.2.1.2 | Required and optional PersonalJava APIs ..... | 61 | +| 8.2.1.3 | Required and optional JavaPhone APIs..... | 61 | +| 8.2.1.3.1 | Application installation ..... | 62 | +| 8.2.1.3.2 | Power..... | 62 | +| 8.2.1.3.3 | Datagram recipient addressing..... | 62 | +| 8.2.1.4 | Required and optional MExE PersonalJava APIs..... | 62 | +| 8.2.1.5 | Mandated services and applications ..... | 63 | +| 8.2.1.5.1 | Network protocol support..... | 63 | +| 8.2.2 | CC/PP over HTTP (Classmark 2)..... | 63 | +| 8.2.3 | Java charging support..... | 63 | +| 8.3 | Security..... | 63 | +| 8.3.1 | PersonalJava security..... | 63 | +| 8.3.1.1 | Java applet certification in PersonalJava ..... | 63 | +| 8.3.1.2 | Java application signature verification in PersonalJava ..... | 63 | +| 8.3.1.3 | Java loading native libraries in PersonalJava ..... | 64 | +| 8.3.2 | Installing MExE native libraries..... | 64 | +| 9 | MExE Classmark 3 (J2ME CLDC environment) ..... | 64 | +| 9.1 | Introduction ..... | 64 | +| 9.1.1 | Classmark 3 MExE devices..... | 64 | +| 9.1.2 | High level architecture..... | 64 | +| 9.1.3 | High level functionality ..... | 65 | +| 9.2 | Non Security..... | 65 | +| 9.2.1 | Connected Limited Device Configuration (CLDC) ..... | 65 | +| 9.2.2 | Mobile Information Device Profile (MIDP)..... | 65 | +| 9.2.2.1 | Networking ..... | 66 | +| 9.2.2.2 | MID Applications (MIDlet)..... | 66 | +| 9.2.2.3 | MIDlet Suites ..... | 66 | +| 9.2.2.4 | Record Storage..... | 66 | +| 9.2.3 | Required and optional MExE APIs ..... | 66 | +| 9.2.4 | Service discovery and management ..... | 66 | +| 9.2.5 | Transfer of capability negotiation information in Classmark 3..... | 67 | +| 9.3 | Security..... | 67 | +| 9.3.1 | CLDC security..... | 67 | +| 10 | MExE classmark 4 (CLI Compact environment) ..... | 67 | +| 10.1 | Introduction ..... | 67 | +| 10.1.1 | High level architecture..... | 68 | +| 10.2 | Non security ..... | 68 | +| 10.2.1 | High level functionality ..... | 68 | +| 10.2.2 | Network protocol support..... | 69 | +| 10.2.3 | Power Management..... | 69 | +| 10.2.4 | CLI charging support..... | 69 | +| 10.2.5 | CC/PP over HTTP or WSP (Classmark 4) ..... | 69 | +| 10.3 | Security..... | 70 | +| 10.3.1 | CLI Security ..... | 70 | +| <b>Annex A (normative):</b> | <b>MExE profile of PKCS#15 .....</b> | <b>71</b> | +| A.1 | PKCS#15 certificate object attributes presentation ..... | 71 | +| A.1.1 | Object common attributes ..... | 71 | +| A.1.2 | Certificate common attributes ..... | 71 | +| A.1.3 | Certificate attributes ..... | 71 | +| A.1.4 | Specific X.509 certificate attributes ..... | 71 | +| A.2 | MExE profile of PKCS#15 ..... | 71 | + +| | | | +|-------------------------------|----------------------------------------------------------------------|-----------| +| A.3 | Coding and storage in MExE-(U)SIM ..... | 72 | +| <b>Annex B (informative):</b> | <b>PKCS#15 certificate objects ASN1 expanded syntax extract.....</b> | <b>73</b> | +| <b>Annex C (normative):</b> | <b>Access restriction certificate extension.....</b> | <b>75</b> | +| <b>Annex D (informative):</b> | <b>MExE executable life cycle.....</b> | <b>76</b> | +| D.1 | State of a MExE executable ..... | 76 | +| D.2 | Released state ..... | 78 | +| D.3 | Uninstalled Execution state..... | 79 | +| D.4 | Verification ..... | 80 | +| <b>Annex E (informative):</b> | <b>MExE conformance requirements.....</b> | <b>81</b> | +| Annex F (informative): | Change history..... | 85 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the stage 2 and stage 3 description of the Mobile Execution Environment (MExE). Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1. + +The present document includes information applicable to network operators, service providers and terminal, switch and database manufacturers. + +The present document contains the core functions for a Mobile Execution Environment (MExE) which are sufficient to provide a complete service. + +MExE uses a number of technologies to realise the requirements of the stage 1 description (3GPP TS 22.057). The present document describes how the service requirements are realised with the selected technologies. The TS is devised into clauses each covering the aspects relating to particular MExE technologies, it is intended that this specification will evolve along with the MExE technologies. A generic clause of the specification covers areas of MExE common to all technologies. + +Implementation of this specification outside the UE (User Equipment) is outside the scope of this specification. + +# --- 2 References + +- 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.057: "Mobile Execution Environment (MExE); Stage 1". +- [3] Personal Java 1.1.1 or higher, Sun Microsystems <http://www.javasoft.com/products/personaljava/>. +- [4] JavaPhone API version 1.0, <http://java.sun.com/products/javaphone/>. +- [5] Void. +- [6] Wireless Application Protocol (WAP) June 2000 Conformance Release <http://www.wapforum.org>. +- [7] Void. +- [8] Void. +- [9] Hypertext Transfer Protocol – HTTP/1.1, IETF document RFC2616, <http://www.w3.org/Protocols/rfc2616/rfc2616>. +- [10] Void. +- [11] 3GPP TR 22.170: "Universal Mobile Telecommunications System (UMTS); Service aspects; Provision of Services in UMTS - The Virtual Home Environment". +- [12] 3GPP TS 22.121: "The Virtual Home Environment; Stage 1". +- [13] Void. +- [14] 3GPP TS 22.101: "Service Aspects; Service Principles". +- [15] CC/PP Exchange Protocol based on HTTP Extension Framework; W3C <http://www.w3.org/Mobile/CCPP>. + +- [16] Composite Capability/Preference Profiles (CC/PP): A user side framework for content negotiation; <http://www.w3.org/Mobile/CCPP>. +- [17] UAProf Specification <http://www.wapforum.org/what/technical.htm>. +- [18] JDK 1.1 security <http://www.javasoft.com/products/jdk/1.1/docs/guide/security/index.html>. +- [19] Java 2 security <http://www.javasoft.com/products/jdk/1.2/docs/guide/security/index.html>. +- [20] Java security tutorial <http://java.sun.com/docs/books/tutorial/security1.2/overview/index.html>. +- [21] OCF 1.1.: "Smartcard API specified by OpenCard Consortium <http://www.opencard.org>. +- [22] RFC 1738: "Uniform Resource Locators (URL)" <http://www.w3.org/pub/WWW/Addressing/rfc1738.txt>. +- [23] The MD5 Message Digest Algorithm", Rivest, R., RFC 1321, April 1992. URL: <ftp://ftp.isi.edu/in-notes/rfc1321.txt>. +- [24] ISO/IEC 10118-3 (1996): "Information technology - Security techniques - Hash-functions - Part 3: Dedicated hash-functions". +- [25] IETF RFC 2368: "The mailto URL scheme". +- [26] ITU-T Recommendation X.509: "Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks". +- [27] 3GPP TS 51.011: "Specification of the Subscriber Identity Module – Mobile Equipment (SIM - ME) interface". +- [28] 3GPP TS 23.107: "QoS Concept and Architecture". +- [29] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General Aspects". +- [30] 3GPP TS 24.008: "Mobile radio interface layer 3 specification, Core Network Protocols; Stage 3". +- [31] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2". +- [32] PKCS #15 "Cryptographic Token Information Syntax Standard" version 1.1, RSA Laboratories, June 2000 URL: [ftp://ftp.rsa.com/pub/pkcs/pkcs-15/pkcs-15v1\\_1.doc](ftp://ftp.rsa.com/pub/pkcs/pkcs-15/pkcs-15v1_1.doc). +- [33] RFC 2510 (1999): "Internet X.509 Public Key Infrastructure Certificate Management Protocols". +- [34] Connected Limited Device configuration, J2ME version 1.0, <http://java.sun.com/j2me/docs/>. +- [35] Mobile Information Device Profile, J2ME version 1.0, <http://java.sun.com/j2me/docs/>. +- [36] eXtensible Markup Language (XML) 1.0, W3C Recommendation. URL: <http://www.w3.org/XML>. +- [37] Resource Definition Framework (RDF) Model and Syntax, W3C Recommendation. URL: <http://www.w3.org/RDF>. +- [38] UML Partners: Unified Modelling Language. URL: <http://www.omg.org>. +- [39] 3GPP TS 31.102: "Characteristics of the USIM applications". +- [40] RFC 2396 (1998): "Uniform Resource Identifiers (URI): Generic Syntax". T. Berners-Lee, R. Fielding, L. Masinter. +- [41] RFC 2616 (1999): "Hypertext Transfer Protocol -- HTTP/1.1". R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee. +- [42] Description of the "JAR Manifest" file encoding, Sun Microsystems. URL: <http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html> + +- [43] RFC 2459 (1999): "Internet X.509 Public Key Infrastructure Certificate and CRL Profile". +R. Housley, W. Ford, W. Polk, D. Solo. +- [44] 3GPP TR 21.905: Vocabulary for 3GPP Specifications. +- [45] WAP Binary XML Content Format Specification (WBXML), +<http://www.wapforum.org/what/technical.htm>. +- [46] RFC 1766: "Tags for the Identification of Languages". +- [47] WAP Certificate and CRL Profiles, WAP-211-WAPCert +<http://www.wapforum.org/what/technical.htm>. +- [48] 3GPP TS 23.227 "Applications and User interaction in the UE-Principles and specific requirements". +- [49] PKCS#1 "RSA Cryptographic Standard" " version 2.0, RSA Laboratories, October 1998 +URL: <http://www.rsasecurity.com/rsalabs/pkcs/pkcs-1/index.html>. +- [50] Common Language Infrastructure, ECMA specification ECMA-335, +<http://www.ecma.ch/ecma1/STAND/ecma-335.htm>. +- [51] Simple Object Access Protocol version 1.1, (SOAP), URL : <http://www.w3.org/TR/2000/NOTE-SOAP-20000508/>. +- [52] PKCS#7 "Cryptographic Message Syntax Standard" " version 1.5, RSA Laboratories, November 1993 +URL: <http://www.rsasecurity.com/rsalabs/pkcs/pkcs-7/index.html>. + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**administrator:** administrator of the MExE device is the entity that has the control of the third party trusted domain, and all resources associated with the domain + +NOTE 1: The administrator of the MExE device could be the user, the operator, the manufacturer, the service provider, or a third party as designated by the owner of the MExE device. + +**best effort QoS (Quality of Service):** best effort QoS refers to the lowest of all QoS traffic classes + +NOTE 2: If the guaranteed QoS cannot be delivered, the bearer network delivers the QoS which can also be called best effort QoS, TS 23.107 [28]. + +**certificate:** entity that contains the issuer's public key, identification of the issuer, identification of the signer, and possibly other relevant information + +NOTE 3: Also, a certificate contains a signed hash of the contents. The signer can be a 3rd. party other than the issuer. + +**delivered QoS:** actual QoS parameter values with which the content was delivered over the lifetime of a QoS session, TS 23.107 [28]. + +**End Entity:** user of PKI certificates and/or end user system that is the subject of a certificate. + +**fine grain:** refers to the capabilities of the Java security system to allow applications, sections of code or Java classes to be assigned permissions to perform a specific set of privileged operations + +NOTE 4: The smallest programming element that can be given permission attributes is a Java class [19]. + +**key pair:** key pairs are matching private and public keys + +NOTE 5: If a block of data is encrypted using the private key, the public key from the pair can be used to decrypt it. The private key is never divulged to any other party, but the public key is available, e.g. in a certificate. + +**Operator:** term operator as used in this specification refers to the term Home Environment, defined as "Home Environment: The home environment is responsible for enabling a user to obtain UMTS services in a consistent manner regardless of the user's location or terminal used (within the limitations of the serving network and current terminal)" in TR 21.905 [44]. + +**negotiated QoS:** response to a QoS request, the network shall negotiate each QoS attribute to a level that is in accordance with the available network resources + +NOTE 6: After QoS negotiation, the bearer network shall always attempt to provide adequate resources to support all of the negotiated QoS profiles, TS 23.060 [31]. + +**personal certificate:** certificate loaded by the user or a user application which is limited to the application that it is intended for, and is not a MExE Certificate + +NOTE 7: E.g. an e-mail application could load certificates for its usage. Personal certificates are out of scope for MExE. + +**phonebook:** dataset of personal or entity attributes + +NOTE 8: The simplest form is a set of name-number pairs as defined by GSM SIMs. A phonebook may also be supported on a (U)SIM. + +**Mobile Execution Environment (MExE):** is defined in detail in the present document, but the scope of MExE does not include the operating system, or the manufacturer's execution environment + +**MExE API:** consists of interfaces present in the MExE device and exposed to MExE executables + +NOTE 9: The APIs which are outside of the scope of this specification, are not part of MExE API. + +**MExE certificate:** used in the realisation of MExE security domains + +NOTE 10: A MExE Certificate can be used to verify downloaded MExE executables. Use of the word "certificate" in this document implies a MExE certificate. Other varieties of certificate will be explicitly qualified as a e.g. "Personal Certificate". + +**MExE device:** UE (User Equipment) that supports MExE functionality in the ME (Mobile Equipment) + +NOTE 11: The implementation of MExE shall be in the same physical device as the MT (Mobile Termination). Implementation of MExE functionality in the TE (Terminal Equipment) outside of the physical device containing the MT (Mobile Termination) is for further study. + +**MExE executable:** is one or more applet, application, or content, which conforms to the MExE specification and may execute on any MExE device, conforming to the appropriate classmark + +**MExE Java VM:** this is a standard Java virtual machine used to execute MExE Java applets and applications + +**MExE native library:** this is a downloaded native library that can be accessed by MExE executables + +**MExE Server:** node supporting MExE services in the MExE service environment + +NOTE 12: The MExE server may be a web or WAP server providing services for users to download MExE executables. MExE server is not necessarily a special network element but may utilize the normal Internet service environment. + +**MExE-(U)SIM:** (U)SIM that is capable of storing a security certificate that is accessible using standard mechanisms + +**MIDP application:** MIDP application, or "MIDlet", is one that uses only the APIs defined by the MIDP and CLDC specifications. + +**MIDlet suite:** collection of MIDP Applications, or MIDlets packaged together and share resources within the context of a single Java Virtual Machine + +**owner:** owner of the MExE device + +NOTE 13: An owner could be a user, operator (e.g. where the MExE device is obtained as part of a subscription and the cost of the MExE device is subsidised), service provider, or a third party (e.g. the MExE device is owned by the user's company and this company wishes to control how the MExE device is used) + +**power up event:** abstract event that occurs when the MExE device is cold started (i.e. switched on) + +**QoS session:** Lifetime of PDP context, the period between the opening and closing of a network connection whose characteristics are defined by a QoS profile + +NOTE 14: Multiple QoS sessions may exist, each with a different QoS profile, TS 23.107 [28]. + +**QoS profile:** comprises of a number of QoS parameters + +NOTE 15: A QoS profile is associated with each QoS session. The QoS profile defines the performance expectations placed on the bearer network, TS 23.107 [28]. + +**requested QoS:** QoS profile is requested at the beginning of a QoS session + +NOTE 16: QoS modification requests are also possible during the lifetime of a QoS session, TS 23.107 [28] and TS 23.060 [31]. + +**sandbox:** sandbox is a safe area to run Java code. Untrusted Java code executing in a sandbox has access to only certain resources, JDK 1.1 security [18]. + +**service:** service (which may consist of an application or applet, and its related content) is a set of functions offered to a user by an organisation, and may be performed on the MExE device and/or remotely + +**service name:** identifier associated with a service, which could be a string, a fully qualified Java class name, a unique URI or other identifier + +**session:** period between the launching of a MExE executable and its execution termination + +NOTE 17: A WAP-session is established between the mobile and the WAP Gateway. The duration of a WAP-session can range from a second to years. The WAP-session can be associated with a particular subscription in the WAP Gateway. + +**signature:** "Signing" is the process of encrypting a hash of the data using a private key + +NOTE 18: If the signature can be decrypted using the public key, then the signature is valid. + +**signed JAR file:** archives of Java classes or data that contain signatures that also include a way to identify the signer in the manifest [42] (the Manifest contains a file which has attributes defined in it) + +**subscribed QoS:** network will not grant a QoS greater than that subscribed + +NOTE 19: The QoS profile subscription parameters are held in the HLR. An end user may have several QoS subscriptions. For security and the prevention of damage to the network, the end user cannot directly modify the QoS subscription profile data, TS 23.060 [31]. + +**user:** user of the MExE device + +**valid (U)SIM application:** identification by the MExE ME that a valid SIM card, or USIM application on the UICC, has been detected (e.g. through insertion of (U)SIM card, power up of MExE device etc.) + +NOTE 20: Whenever this specification refers to valid (U)SIM, it implies a valid SIM card or USIM application on the UICC. + +Further definitions specific to MExE are given in TS 22.057 [2]. + +## 3.2 Abbreviations + +For the purposes of the present document the following abbreviations apply: + +| | | +|------|-----------------------------------| +| AA | Attribute Authority | +| API | Application Programming Interface | +| APDU | Application protocol data unit | + +| | | +|-----------|---------------------------------------------------------------------------------| +| ARPK | Administrator Root Public Key | +| CA | Certification Authority | +| CC/PP | Composite Capability/Preference Profiles | +| CGI | Common Gateway Interface | +| CCM | Certificate Configuration Message | +| CLDC | Connected Limited Device Configuration | +| CLI | Common Language Infrastructure | +| CP-Admin | Certificate Present (in the MExE (U)SIM) - Administrator | +| CP-TP | Certificate Present (in the MExE (U)SIM) - Third Party | +| CRL | Certificate Revocation List | +| Diff-serv | Differentiated Services | +| DTMF | Dual Tone Multiple Frequency | +| GSM | Global System for Mobile Communication | +| GPRS | General Packet Radio Service | +| HTTP | HyperText Transfer Protocol | +| HTTPS | HyperText Transport Protocol Secure (https is http/1.1 over SSL, i.e. port 443) | +| IETF | Internet Engineering Task Force | +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| JAD | Java Application Descriptor | +| J2ME | Java 2 Micro Edition | +| J2SE | Java 2 Standard Edition | +| JTAPI | Java Telephony Application Programming Interface | +| JAR file | Java Archive File | +| ME | Mobile Equipment | +| MIDP | Mobile Information Device Profile | +| MIDlet | MIDP Application | +| MMI | Man-Machine Interface | +| MRPK | Manufacturer Root Public Key | +| MSE | MExE Service Environment | +| MSISDN | Mobile Subscriber ISDN Number | +| MT | Mobile Termination | +| OCF | OpenCard Framework | +| OEM | Original Equipment Manufacturer | +| OCSP | Online Certificate Status Protocol | +| ORPK | Operator Root Public Key | +| QoS | Quality of Service | +| PDP | Packet Data Protocol | +| PKI | Public Key Infrastructure | +| RDF | Resource Description Format | +| RFC | Request For Comments | +| RPK | Root Public Key | +| SCVP | Simple Certificate Verification Protocol | +| SIM | Subscriber Identity Module | +| SMS | Short Message Service | +| SOAP | Simple Object Access Protocol | +| SSL | Secure Socket Layer | +| TE | Terminal Equipment | +| TLS | Transport Layer Security | +| TP | Third Party | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UI | User Interface | +| UMTS | Universal Mobile Telecommunications System | +| URL | Uniform Resource Locator | +| URI | Uniform Resource Identifier | +| USIM | Universal Subscriber Identity Module | +| USSD | Unstructured Supplementary Service Data | +| VM | Virtual Machine | +| WAE | Wireless Application Environment | +| WAP | Wireless Application Protocol | +| WBXML | WAP Binary XML | + +| | | +|------|-------------------------------------------| +| WDP | Wireless Datagram Protocol | +| WMLS | Wireless Markup Language Script | +| WSP | Wireless Session Protocol | +| WTA | Wireless Telephony Applications | +| WTAI | Wireless Telephony Applications Interface | +| WTLS | Wireless Transport Layer Security | +| WTP | Wireless Transaction Protocol | +| WWW | World Wide Web | +| XML | Extensible Markup Language | + +Further abbreviations are given in 3GPP TS 22.057 [2] and 3GPP TR 21.905 [44]. + +# 4 MExE basic principles + +## 4.1 Generic MExE aspects + +Support of at least one MExE classmark is mandatory. A MExE device may also include optional support for applications from any other MExE classmark (refer to clause 4.3 "Multiple Classmark support"). + +This clause defines the common aspects of all MExE compliant devices, independent of MExE technology. + +Considering the wide and diverse range of current and future technology and devices that (will) use wireless communication and provide services based thereon a one-size-fits-all approach is unrealistic. Instead the present document categorises devices by giving them different MExE classmarks. In this specification the following MExE classmarks are defined: + +- MExE classmark 1 - based on WAP (Wireless Application Protocol) [6] - requires limited input and output facilities (e.g. as simple as a 3 lines by 15 characters display and a numeric keypad) on the client side, and is designed to provide quick and cheap information access even over narrow and slow data connections. +- MExE classmark 2 - based on PersonalJava [3] - provides and utilises a run-time system requiring more processing, storage, display and network resources, but supports more powerful applications and more flexible MMIs. +- MExE classmark 3 – based on J2ME CLDC and MIDP environment [34] and [35] – supports Java applications running on resource-constrained devices. +- MExE classmark 4 – based on Common Language Infrastructure [50] Compact Profile – supports CLI based applications running on a broad range of connected devices. + +Content negotiation allows for flexible choice of formats available from a server or adaptation of a service to the actual classmark of a specific client device. + +Bi-directional capability negotiation between the MExE Service Environment and MExE device (including MExE classmark), supports the transfer of capabilities between the client and the server. + +## 4.2 High level architecture + +The following architectural model shows an example of how standardised transport mechanisms are used to transfer MExE services between the MExE device and the MExE service environment, or to support the interaction between two MExE devices executing a MExE service. + +The MExE service environment could, as shown in figure 1 "Generic MExE architecture", consist of several service nodes each providing MExE services that can be transferred to the MExE device using mechanisms such as (but not limited to) fixed/mobile/cordless network protocols, Bluetooth, infrared, serial links, wireless optimised protocols, standard Internet protocols. These service nodes may exist in the circuit switched domain, packet switched domain, IP multimedia core network subsystem or in the internet space (e.g. SMS service centres, multimedia messaging servers, internet servers etc.). The MExE service environment may also include a proxy server to translate content defined in standard Internet protocols into their wireless optimised derivatives. + +For the versatile support of MExE services, the wireless network shall provide the MExE device with access to a range of bearer services on the radio interface to support application control and transfer from the MExE service environment. + +As MExE also applies to fixed and cordless environments, MExE device may also access MExE services via non-wireless access mechanisms. + +![Figure 1: Generic MExE architecture flowchart. The process starts with 'Verification' at the top, leading to 'Validation'. From 'Validation', three paths emerge: 'Untrusted' leading to a terminal node (dot in circle), 'Trusted' (In Operator or Manufacturer or Third Party Domain) leading to a terminal node (dot in circle), and 'Deleted' leading to a large 'X' mark.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` + +graph TD + Start(( )) --> Validation[Validation] + Validation --> Untrusted[Untrusted] + Validation --> Trusted["Trusted +In Operator or Manufacturer +or Third Party Domain"] + Validation --> Deleted[Deleted] + Untrusted --> End1(( )) + Trusted --> End2(( )) + Deleted --> End3[X] + +``` + +Figure 1: Generic MExE architecture flowchart. The process starts with 'Verification' at the top, leading to 'Validation'. From 'Validation', three paths emerge: 'Untrusted' leading to a terminal node (dot in circle), 'Trusted' (In Operator or Manufacturer or Third Party Domain) leading to a terminal node (dot in circle), and 'Deleted' leading to a large 'X' mark. + +Figure 1: Generic MExE architecture + +## 4.3 Multiple classmark support + +Support of multiple MExE classmarks on a MExE device is optional. + +A given MExE Classmark identifies support by a MExE device for a defined level of MExE functionality as defined by that classmark. Support of MExE classmarks by a MExE device shall enable flexible support of MExE functionality. A MExE device may support any multiple combinations of MExE classmarks. + +The support of any other functionality by a MExE device is also possible, and is out of scope of this specification. + +NOTE: Some implementation issues may arise from the multiple support of classmarks on a device, e.g.: + +- 1) In conforming to all of the requirements, how are mandatory requirements in one classmark compatible with optional requirements for another? +- 2) With KJava and pJava on one device, MIDP can be on top of a JavaVM. Which of the classmarks will it be then? In conforming with both Classmark 2 and 3 requirements, are 2 VMs required in one device? + +### 4.3.1 Classmark 1 service support in non-Classmark 1 MExE devices + +Support of Classmark 1 executables in non-classmark 1 MExE devices is optional. + +To allow access to services designed for MExE Classmark 1 devices, MExE devices other than Classmark 1 will need to support full or a subset of WAP protocol as identified below. Due to the fast evolution of new technologies, support of WAP in Classmarks other than Classmark 1 is not mandated by MExE specification. However WAP is a possibility + +for the integrity of service provisioning as well as quick access to information by feature rich devices (e.g. Java devices). + +If Classmark 1 services are supported by non-Classmark 1 devices, Classmark 1 services shall execute in the same manner as they execute in a MExE Classmark 1 device. For that purpose, a MExE non-Classmark 1 device shall comply with data profile class (Class C) of WAP Class Conformance Requirement Specification [6]. + +NOTE: A more specific reference to the WAP Class Conformance Requirement Specification shall be supplied when available. + +### 4.3.2 Classmark 2 service support in non-Classmark 2 MExE devices + +Support of Classmark 2 executables in non-classmark 2 MExE devices is optional. + +If Classmark 2 services are supported by non-Classmark 2 devices, Classmark 2 services shall execute in the same manner as they execute in a MExE Classmark 2 device. + +### 4.3.3 Classmark 3 service support in non-Classmark 3 MExE devices + +Support of Classmark 3 executables in non-classmark 3 MExE devices is optional. + +If Classmark 3 services are supported by non-Classmark 3 devices, Classmark 3 services shall execute in the same manner as they execute in a MExE Classmark 3 device. + +### 4.3.4 Classmark 4 service support in non-Classmark 4 MExE devices + +Support of Classmark 4 executables in non-classmark 4 MExE devices is optional. If Classmark 4 services are supported by non-Classmark 4 devices, Classmark 4 services shall execute in the same manner as they execute in a MExE Classmark 4 device. + +# --- 5 Generic MExE functions (excluding security) + +## 5.1 User profile + +Support of the user profile is optional. + +NOTE: The user profile is not yet specified in an interoperable way. Support of the user profile will be defined when it has been fully specified in a fully interoperable way. + +The user profile (which may consist of sub user profiles for a user) contains the characterisation of the MExE device as defined by the user and service provider. Further, it is also possible for multiple users of a MExE device to each have their own user profiles. The user profile is not unique to the MExE device, and this clause identifies the usage and content of the user profile from a MExE perspective only, and does not identify the generic support of user profiles in general. Refer to TS 22.101 [14] for further details on the user profile. + +### 5.1.1 Location of, access to, and security of, the user profile + +As multiple user profiles may be defined, the user is able to set up or receive calls/connections associated with different user profiles simultaneously by securely activating a user profile (with each user profile being associated with at least one unique identifier). Refer to table 5 "Security domains and actions" in the Security clause 6.3 "MExE executable permissions" for further details on user profile activation. + +The user's characterisation of the MExE device in the user profile may be modified at any time by the user and the service provider, and changes affected at the earliest possible opportunity. + +The security clause shall apply to all user profiles at all times, whether activated or not + +The user profile shall be securely managed by the MExE device, and stored in a secure area of the MExE device (either (U)SIM or ME). The service provider may also retain the user profile in the network for service optimisation. User private data in the user profile may also be stored in the network, however only with the user permission. + +The support of more than one user profile is not mandatory. + +### 5.1.2 Support of the user profile + +The user profile acts as a repository (which is always available in the MExE device) defining the MExE device behaviour. + +MExE preferences and personalisation are supported in the user profile (e.g. UMTS portability and support of VHE defined in TS 22.121 [12] and other 22-series specifications), which in turn is based on the Composite Capability/Preference Profile (CC/PP) specification from W3C [16]. + +MExE preferences and personalisation may not only be recorded directly in the user profile as supported by CC/PP (the direct referencing mechanism), but may also be retrieved from a URL (the indirect referencing mechanism) [22]. + +Generally, the user profile's CC/PP framework provides the mechanism for the standardised format of preferences, and its use of Resource Description Framework (RDF) permits the interoperable encoding of MExE preferences and personalisation. Future extensions will be supported by the W3C mechanism, allowing for evolution and development of MExE preferences and personalisation. + +The set of preferences which are supported in the user profile consists of the following: + +- user interface personalisation; +- the user's personalisation of the user interface; +- service personalisation and management; +- the user's generic service management information. + +The coding and presentation of the above characteristics in the user profile is defined by the Composite Capability/Preference Profile (CC/PP) specification from W3C [16], and referenced by the MExE capability negotiation in clause 5.2 "Capability and content negotiation". + +The following user preference information is supported by UAProf [17]. A MExE device shall support the following property in table 1 "Mandatory UAProf properties" of the UAProf schema for user preference information. + +**Table 1: Mandatory UAProf properties** + +| Attribute | Description | Resolution Rule | Type | Sample Values | +|----------------------------|----------------------------------------------------------------------------|-----------------|---------|---------------| +| AcceptDownloadableSoftware | Indicates the user's preference on whether to accept downloadable software | Locked | Boolean | "Yes", "No" | + +It is recommended that a MExE device supports the following UAProf properties in table 2 "Recommended UAProf properties": + +**Table 2: Recommended UAProf properties** + +| Attribute | Description | Resolution Rule | Type | Sample | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------|---------------------------| +| CcppAccept-Language | User's preference for document language. Property value is a list of natural languages, where each item in the list is the name of a language as defined by RFC 1766 [46]. | Append | Literal (Bag) | "zh-CN", "en fr" | +| PreferenceForFrames | User's preference for displaying frames | Locked | Boolean | "Yes", "No" | +| WapPushMsgPriority | User's settings for WAP Push message priorities | Locked | Literal | "critical", "low", "none" | + +Also, there is in UAProf [17] support for indicating MExE device's capabilities related to UI features, e.g. capability for displaying images or frames, as well as capability information about input and output methods. + +### 5.1.3 User interface personalisation + +Support of user interface personalisation as detailed in this clause is optional. + +The MExE device interface consists of the buttons, menus, screens and MMI as designed and provided by the MExE device manufacturer; the nature of this MExE device interface is naturally evolving, MExE device specific and proprietary to the individual manufacturers of the industry. This interface is the one normally seen by the user in normal operation of his MExE device. This specification does not place any requirements or limitations on the individual manufacturers' MExE device interface. + +The MExE MMI, in turn, is the interface available to the user to support MExE services and functionality on the MExE device. The nature of the MExE MMI interface, like the normal MExE device interface described above, is not standardised in any way, to allow for manufacturer innovation, cater for evolving market needs, and permit manufacturer differentiation. The MExE MMI, depending on different manufacturer implementations, may consist of the normal MExE device interface, the normal MExE device interface with modifications, a different interface to the normal MExE device interface, or some combinations thereof etc. MExE services operate within, and using the capabilities of, the MExE MMI. + +User interface personalisation consists of two parts. The first part refers to the user's ability to request, and verify, the preferred changes to the user interface; thus the user's preferences, as supported by the specific MExE device, require to be recorded. The second part refers to the MExE device's support of the user's preferences for the interface, within the capabilities of an MExE device. By defining the user interface personalisation to consist of two stages, the preferences which have been recorded by the user may be transferred (as part of the user profile, e.g. CcppAccept-Language and/or PreferenceForFrames), and thereby provide portability of the user's preferences. + +#### 5.1.3.1 MExE user interface personalisation + +Personalisation of the user interface offers the MExE Service Environment and or the user, the ability to inform the MExE device of the desired extent of personalisation. All support of the user interface personalisation is optional, not mandatory on any class of MExE device, and subject to the capabilities of the MExE device. Depending on the capability of the MExE device, the personalisation may be fully supported, partially supported, interpreted or ignored. + +Personalisation of the user interface is not restricted to modifying the appearance of the MMI, but also the modification of MMI parameters (e.g. programming of the voicemail number). The user's personalisation of the interface is retained as part of the user profile. + +#### 5.1.3.2 Support of MExE user interface personalisation + +MExE user interface personalisation is supported via the preferences in the user profile, which in turn is based on the Composite Capability/Preference Profile (CC/PP) specification from W3C [16]. + +User interface personalisation may not only be reported in the CC/PP request to the server (the direct referencing mechanism), but indeed the client may point to a URL (the indirect referencing mechanism) from where the user interface personalisation preferences may be retrieved. + +Generally, the user profile's CC/PP framework provides the mechanism for the standardised format of preferences, and its use of Resource Description Framework (RDF) permits the interoperable encoding of user interface personalisation. Future extensions will be supported by the W3C mechanism, allowing for evolution and development of MExE user interface personalisation. + +### 5.1.4 Virtual home environment + +Virtual Home Environment (VHE) (see TR 22.170 [11] and TS 22.121 [12]) is defined as a concept for personalised service portability across network boundaries and between terminals. MExE is identified by VHE as one of the mechanisms which may be used to support VHE. + +The characteristics of the VHE (to reflect any user or home environment modification of the user's VHE) shall be stored as part of the user profile. + +## 5.2 Capability and content negotiation + +Support of capability negotiation for all MExE devices is mandatory, while support of content negotiation is optional. + +Interaction between the MExE device and the MSE for WWW/WAP browsing and service discovery shall be supported by the use of the hypertext transfer protocol HTTP/1.1 [9], or an HTTP/1.1 derived protocol (e.g. WSP as defined in Wireless Application Protocol [6]). Communication between the MExE device and the MSE supports: + +### - Capability negotiation + +The MExE device connects to the MSE by using HTTP/1.1 or an HTTP/1.1 derived protocol. Capability negotiation between the MExE device and the MSE only takes place for the first time after the MExE device has connected to the MSE, and the MSE is informed about the MExE device. Without this first initial contact from the MExE device, the MSE has no knowledge of the MExE device. After the first initial contact the MSE may connect to the MExE device by using HTTP/1.1 or an HTTP/1.1 derived protocol. + +Capability negotiation represents the mechanism by which the MExE device and the MSE interact to inform each other of the specific mechanisms, capabilities and support which each is able to provide or support within the scope of a MExE service interaction. The capability negotiation normally takes place prior to any content transfer between the two entities. + +Capability negotiation is used by the MExE device to inform the MSE of its capabilities. The MExE device may be informed by the MSE of its use of the MExE device's capabilities. The MExE device may also spontaneously inform the MSE of its capabilities (i.e. following a change in MExE support, such as removal of MExE device from a docking station with its keyboard, mouse and monitor). A subset of characteristics which may be transferred between the MExE device and the MSE during the capability negotiation are identified in clause 5.2.1 "Capability negotiation characteristics". + +### - Content negotiation + +Content negotiation represents the means by which the MExE device and the MSE inform each other of the requested and available form of content. If needed, the content negotiation may take place following capability negotiation between the two. The methods for content negotiation are the basic HTTP/1.1. or WSP methods explained in [9] and [6]. + +Content negotiation is used to select the best representation of an entity when there are multiple representations of the entity available from the MSE. The entity (e.g. a service, an image, etc) is located behind a URI, and the application in the MExE device connects to the URI by using HTTP/1.1 or an HTTP/1.1 derived protocol. The best representation of an entity can be decided by the server (server-driven negotiation) or by the client application (agent-driven negotiation). + +Both the capability and the content negotiation has the same purpose: to optimise the content according to client's capabilities. The term "content negotiation" has been used e.g. in the HTTP specification and the HTTP/1.1. and the WSP contain headers to perform the content negotiation. However, the capability negotiation in MExE aims at extending the basic HTTP and WSP methods for content negotiation by using CC/PP framework. + +The content negotiation transferred between the MExE device and the MSE is identified in clause 5.2.3 "Client content capability report" onwards. + +### 5.2.1 User profile and capability negotiation relationship + +The user profile contains the user's preferences. Support of the user's preferences will depend on the capabilities of the MExE device. If the capabilities change, then the degree of support of the user's preferences may change too. + +The capability negotiation between the MExE device and the MSE, as shown in figure 2 "Model of user profile and capability relationship", contains those user preferences which the MExE device is able to support. + +In this way the MSE will serve a MExE device with the lowest common denominator of the users preferences, the MExE device capabilities and the provided service characteristics and support the user's preferences to the maximum degree. + +![Figure 2: Model of user profile and capability relationship. The diagram shows a vertical stack of three boxes: 'Signature' at the top, 'Manifest (attributes)' in the middle, and 'Contents (Java classes, native code, certificate, etc...)' at the bottom. A line connects the 'Manifest (attributes)' box to an external box labeled 'MExE-Implementation-Type: .....'. The entire stack is enclosed in a larger rectangular frame.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +Figure 2: Model of user profile and capability relationship. The diagram shows a vertical stack of three boxes: 'Signature' at the top, 'Manifest (attributes)' in the middle, and 'Contents (Java classes, native code, certificate, etc...)' at the bottom. A line connects the 'Manifest (attributes)' box to an external box labeled 'MExE-Implementation-Type: .....'. The entire stack is enclosed in a larger rectangular frame. + +**Figure 2: Model of user profile and capability relationship** + +### 5.2.2 Capability negotiation characteristics + +The method for capability negotiation is based on the Composite Capability/ Preferences Profiles (CC/PP) specification made by W3C [16]. The properties and the actual schema, table 3 "UAProf properties supported by MExE", is based on the WAP UAProf specification [17]. The CC/PP framework is intended to provide an efficient mechanism for enabling enhanced content and service negotiation through a standardised format for user agent profiles. The use of Resource Description Framework (RDF) [37] in CC/PP allows for interoperable encoding of the profile metadata in XML [36] and supports multiple vocabularies to provide for future extensibility. The WAP UAProf is based on the CC/PP framework. The purpose of the UAProf outlined in this document is to specify: + +- an RDF based schema and vocabulary for CC/PP in the context of the WAP UAProf that includes the class definitions and semantics of attributes described in a user agent profile, and +- guidelines for schema extensibility to support a composite profile that enables future additions to the vocabulary and schema. + +Not all capabilities have to be reported in the request to the server but instead, the client may point to URL(s) where the server may fetch the properties. An MSE may, or may not, use the client capability information. + +The generic set of capabilities which may be negotiated between the client and the server consists of the subsequently identified properties in the UAProf schema [17]. + +A MExE device shall support the properties in the UAProf schema for capability negotiation defined in table 3 "UAProf properties supported by MExE" as "mandated properties". + +It is recommended that MExE device supports the properties defined in the table 3 "UAProf properties supported by MExE" as "recommended properties". It is not required that a MExE device shall send all the "recommended properties", when sending a request, however it should be possible for the MExE device to send one or more of the "recommended properties", with user permission. + +The mandatory and recommended properties in table 3 "UAProf properties supported by MExE" are specified in WAP UAProf [17]. + +Support of the properties of the UAProf schema in this specification shall not be limited to those listed in table 3 "UAProf properties supported by MExE". A MExE device may support any other properties from WAP UAProf specification [17]. + +**Table 3: UAProf properties supported by MExE** + +| <b>Mandated Properties</b> | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|--|---------------|-----------------------------------------------------------------------| +| Attribute | Description | | Type | Sample | +| MexeClassmarks | List of supported MExE classmarks (Note 1) | | Literal (bag) | "1", "2", "3" | +| MexeSpec | The first two digits of the MExE Specification version that the MExE device conforms to | | Literal | "3.3", "4.1" | +| MexeSecureDomains | Indicates whether the device supports the MExE security domains | | Boolean | "Yes", "No" | +| <b>Recommended Properties</b> | | | | | +| Vendor | MExE device vendor | | Literal | "Lexus", "Ford" | +| Model | MExE device model number | | Literal | "Mustang 90", "Q10" | +| SoftwareNumber | The number of the MExE device specific software. | | Literal | "1.0", "2.7.0" | +| ScreenSize | The size of the MExE device's screen in units of pixels. | | Dimension | "160x160", "640x480" | +| ScreenSizeChar | Size of the MExE device's screen in units of characters (based on the standard font). | | Dimension | "12x4", "16x8" | +| ColorCapable | Whether the MExE device display supports colour | | Boolean | "Yes", "No" | +| AudioInputEncoder | List of audio input encoders supported by the MExE device | | Literal (bag) | "G.711" | +| VideoInputEncoder | List of video input encoders supported by the MExE device | | Literal (bag) | "MPEG-1", "MPEG-2", "H.261" | +| PointingResolution | Type of resolution of the pointing accessory supported by the MExE device | | Literal | "Character", "Line", "Pixel" | +| CcppAccept-Language | List of preferred document languages | | Literal (bag) | "zh-CN" "en fr" | +| Keyboard | Type of keyboard supported by the MExE device as an indicator of ease of text entry. | | Literal | "Disambiguating", "Qwerty", "PhoneKeypad" | +| SupportedBearers | List of bearers supported by the MExE device. | | Literal (Bag) | "GPRS", "GUTS", "SMS", CSD", "USSD" | +| JavaPlatform | List of Java platforms and profiles installed on the device | | Literal (Bag) | "Pjava/1.1.3-compatible", "MIDP1.0-compatible", "J2SE/1.0-compatible" | +| <b>Proposed New Recommended Property</b> | | | | | +| CLIPlatform (Note 2) | List of CLI profiles installed on the device | | Literal (Bag) | "CLI-Compact/1.0-compatible", "CLI-Standard/1.0-compatible" | +| NOTE 1: In pre-release 4.0.0 specifications the attribute MexeClassmark (as opposed to MexeClassmarks) which was a literal (as opposed to as Literal, Bag) indicating only one MExE classmark was notified. | | | | | +| NOTE 2: The property name "CLIPlatform" is proposed as a placeholder. Once a decision has been made the final property name will be proposed to UAProf for UAProf approval. | | | | | + +Generally, the combination of user profile and MExE device logic will determine the information sent in the capability negotiation from the MExE device to the MExE Service Environment. As an example, for the support of VideoInputEncoder information the user's profile controls if and when VideoInputEncoder information may be sent to the MExE Service Environment (e.g. never sent, always sent, only after user confirmation). + +The capability negotiation process shall be used by the client to permit transfer of capabilities from the client to the server. By transferring its capabilities, the client will support efficient use of resources both over the radio interface as well as in the client or server. Capability negotiation shall be performed prior to transfer over the radio interface to verify as far as possible the ability of the client to support any services to be downloaded. + +In order to transfer the capability information between the MExE device and the MSE, CC/PP method is used with the schema defined in the WAP UAProf working group. + +### 5.2.3 Client content capability report + +The client may perform content negotiation capabilities to the server by using appropriate HTTP/1.1 or WSP request headers. The following methods are available for content negotiation: + +- Client software (product): `User-Agent` header; +- MIME media types: `Accept` header; +- Character set: `Accept-Charset` header; +- Content encoding: `Accept-Encoding` header; +- Language: `Accept-Language` header. + +There is no need for MExE to specify any tokens for content negotiation, as these headers are already defined in HTTP and WSP. The formats for these headers are specified in [9] and [6]. + +### 5.2.4 Server role in capability negotiation + +The server may request the capabilities of a client whenever required, and shall enquire of the client's capabilities prior to making each transaction resulting in a set of transfers to the client; the characteristics which may be reported in the client capability report are identified in the list above. + +In server-driven negotiation the server signals to the client that the response entity was selected from a set of available representation. + +### 5.2.5 Client-driven negotiation + +If the server cannot specify an optimal version for the client basing on the CC/PP sent over to the server, the server may also indicate to client which type of versions are available and let the client make the decision. This method is already available in HTTP1.1. In client-driven negotiation the client selects the best representation after having received an initial response from the server. + +## 5.3 Provisioning and management of services + +Support of management of services as detailed in this clause is mandatory. + +The MExE device shall be capable of supporting services in a standard (WAP or Java) execution environment independently of the MExE device manufacturer. Service provisioning provides a standardised method for a MExE device to discover and install services. It includes download and installation of the service's client application. Once discovered and delivered, services are managed by the user, under the principles stated in 3GPP TS 23.227 [48]. Management of services provides the user with the capability to: + +- control the transfer of services; +- install and configure services; +- control the execution of services; +- terminate or suspend executing services; +- delete services; + +on his MExE device. + +### 5.3.1 Service discovery + +A MExE user is able to request (or be informed about) the range of MExE services available from the MExE server to which it is connected. To be able to interactively discover the services via standard mechanisms such as WSP or HTTP, a MExE device should feature a browser which is a common tool for service discovery. The request, and transfer of information on MExE services from the MExE server is supported by the use of the capability negotiation mechanism. + +All services available in the network continue to be available to the user, in addition to MExE services. + +An example of an alternative means of receiving information on MExE services, is the use of an application on the MExE device which the user interrogates to provide services information (from various sources), and which in turn then obtains such information and presents it to the user. Such an example is not subject to standardisation. + +### 5.3.2 Service transfer + +The standardisation of the transferral of MExE services to a MExE device is outside the scope of this specification. + +Examples of possible ways of supporting service transfer are from a MExE server or from another user MExE device (e.g. using wireless and standard protocols and mechanisms such as HTTP, FTP, proprietary protocols and mechanisms, via a serial link, infrared, Bluetooth data exchange, etc.). + +The above examples are not exhaustive. Regardless of the means of transfer, all services are required to conform with the security requirements in clause 8 "Security". + +### 5.3.3 Service installation and configuration + +Installation of a service may result in changes to the MExE device user interface using icons, browsers or menus as applicable depending on the capability of the MExE device to support them. The name of the installed service may be contained in the package in which it was received (i.e. a JAR file or script), assigned by the user during configuration, or some other means. After installation, the service may be configured. Configuration of the service includes setting the user permissions that apply to the service (e.g. blanket permission for call origination). Configuration may be performed automatically based on the user profile. + +The user controls whether a service transferred to the MExE device is automatically configured and installed in the MExE device. If automatic configuration and/or installation is enabled, the user is notified once it is completed. In the event that there is no authorisation for the automatic installation and/or configuration of a transferred service, the user is notified. + +Subsequent user modification of a service's configuration (e.g. by modification of user profile settings) shall take effect at the earliest possible opportunity thereafter. + +### 5.3.4 Service management + +The MExE device shall support the ability to determine which services are transferred to, resident, installed or executing on the MExE device. The information relating to the services shall include the name as a minimum and the version number if available. + +The user controls which services are permitted or denied to be transferred, resident, installed, configured or executing on the MExE device via the user profile, e.g. AcceptDownloadableSoftware. The user profile permits characteristics such as security level, identification of specific services etc. to manage services on the MExE device. + +### 5.3.5 Service termination + +A MExE device shall support the termination of services. + +A service may terminate by itself, or be terminated by the provider of the service or by the user. The user is in charge of the service, except when the service provider may appropriately control the service as part of user support. + +The mechanism for terminating a service is out of scope of standardisation and shall be provided on a service by service basis by the provider of the service. + +### 5.3.6 Service deletion + +A MExE device shall support the deletion of services. + +A service may be deleted (i.e. removed) from the MExE device with the authorisation of the user. The deletion may be initiated by the authoriser of the service or by the user. + +## 5.4 User control of application connections + +Support of the user control of application connections is mandatory and shall follow the principles and requirements stated in 3GPP TS 23.227 [48]. + +This clause addresses the generic aspects of connection control supported by both WAP and Java classmark MExE devices. + +In order to allow the user to maintain control over connections on his MExE device and the ability to initiate connections, the user shall be able to terminate or suspend any active connection associated with an application in the MExE environment of the MExE device. The user shall be able to obtain information about all connections associated with applications on the MExE device (e.g. requesting information, being informed by the MExE device etc.). Behaviour of the application following termination or suspension of its connection is undefined. + +The specific support of connection control by WAP classmark MExE devices is identified in subsequent clause 7.3.1 "Call control", the security aspects of connection control are identified in clause 8 "Security", and the user control of connection authorisation is identified in clause 5.1 "User profile". + +### 5.4.1 Journaling of network events + +Support of the journaling of network events is mandatory. + +To support the user in monitoring (potentially chargeable) network events initiated by services in the MExE environment, the MExE device shall maintain a record of network events initiated by MExE executables on the MExE device. + +Network events for the purposes of journaling, are defined as events which result in the origination of connections by a service in the MExE environment of the MExE device. Examples of such events (any (potentially chargeable) network event initiated by services in the MExE environment) are: + +- Sending an SMS message; +- Sending an USSD message; +- Initiating a circuit switched connection; +- Initiating a packet switched connection; +- Sending data over a packet switched connection. + +The length, format and longevity of the journal is undefined and subject to manufacturers' discretion. + +The journal shall be managed by the MExE device, and not be accessible by MExE executables. + +### 5.4.2 User notification + +Support of user notification is optional. + +It is recommended that the MExE device should clearly display an indicator whenever network activity is in progress. + +Ideally, this would be an icon on the phone's screen which is displayed whenever the MExE device is sending/receiving SMS, USSD, data call, voice call, or packets. + +However, there are certain cases when this indicator need not be displayed, especially if it is obvious by some other means that the MExE device is performing network actions. + +## 5.5 Quality of service + +Support of Quality of Service is optional. + +Quality of Service (QoS), TS 23.107 [28] is seen by the end user as a measure of the amount of network resources given to an application by the underlying network. The network may employ a number of QoS mechanisms, but the end user / MExE executable is not involved in these. The end user / MExE executable requires an interface into the network QoS through a visible set of standard parameters. + +A QoS aware MExE executable may request a QoS from the network at the beginning of a QoS session. Changes in the level of QoS provided shall be notified to the end user / MExE executable. An end user may request a change in the QoS through the MExE device MMI. A MExE executable may have several QoS streams open simultaneously. + +When the MExE execution environment supports QoS, the MExE executable shall be able to dynamically request a change in the level of QoS at connection setup request or subsequently during the connection. The end user / MExE executable may receive a rejection to a QoS modification request, upon which the end user / MExE executable must be notified. + +The end user's service level QoS subscription parameters are stored in the network, they identify the maximum permissible QoS that a user may negotiate with the network. Several QoS subscriptions may be possible for one user. MExE is neither aware nor able to determine or modify the end user's service level QoS subscriptions. + +Clause 9 "Quality of Service" defines the necessary functions for a MExE device to accommodate QoS management and provisioning. QoS management may be available directly to the MExE executables themselves, or to the MExE environment. + +### 5.5.1 Introduction + +Support of quality of service for MExE devices supporting bearers defined by QoS as defined in this clause is optional. + +QoS aware MExE executables may be executing on the MExE device. To ensure correct operation with the QoS provisioning of the bearer network(s) the associated API's and the MExE QoS manager shall be supported by MExE device supporting bearers defined by QoS – see figure 3 "Logical MExE device QoS manager elements". Non QoS aware MExE executables shall operate with the defined QoS by the user or the network. + +![Figure 3: Logical MExE device QoS manager elements. The diagram shows four vertical columns representing different elements. The first three columns contain stylized waveforms, while the fourth column is empty. The entire diagram is enclosed in a rectangular frame with a thick black border at the top and bottom.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +Figure 3: Logical MExE device QoS manager elements. The diagram shows four vertical columns representing different elements. The first three columns contain stylized waveforms, while the fourth column is empty. The entire diagram is enclosed in a rectangular frame with a thick black border at the top and bottom. + +Figure 3: Logical MExE device QoS manager elements + +### 5.5.2 MExE QoS support + +In the logical architecture depicted in figure 3 "Logical MExE device QoS manager elements", a conceptual entity, a MExE QoS manager exists between the MExE executable and the Network Control API. A QoS API for MExE executables is provided and an API to the network is provided. The MExE QoS functions accommodate standard methods of end to end QoS provisioning. + +For a MExE device supporting bearers defined by QoS, it is recommended that the MExE device shall support the following basic QoS operations: + +- The end user should be able to manage the QoS directly via the MMI. + +For MExE devices supporting bearers defined by QoS, the MExE device shall optionally support the following basic QoS operations: + +- a mapping between the QoS requirements of the MExE executable and the network layer; +- MExE executables shall be able to indicate and interpret QoS values of the network via the MExE QoS Manager; +- MExE executables shall be able to modify the QoS dynamically; +- MExE executables shall be able to react to changes in the provided QoS; + +MExE introduces two new elements to cater for QoS – the MExE QoS manager and the QoS API. The MExE QoS manager shall handle the fact that the network may not have QoS capabilities. + +### 5.5.3 MExE QoS manager + +As a conceptual entity, the MExE QoS manager is responsible for: + +- Managing the QoS streams for MExE executables; +- Notification of the negotiated and delivered QoS to the end user / MExE executable. + +The MExE QoS manager shall support the MExE QoS API according to the bearer supported by the MExE device, and provide functions such as: + +- insert additional QoS signalling parameters; +- add the functionality of the MExE QoS API at best effort, if the network does not support it directly; +- translate between the QoS parameters from the MExE executable and those of the network; +- monitor the QoS delivered by the network and manage QoS requests between the MExE executable and the network; +- be informed by the MExE executable of the requested QoS traffic class; +- be informed by the MExE executable of the lowest QoS traffic class which can be accepted by the MExE executable; +- attempt to re-negotiate the QoS if it falls below the lowest QoS traffic class. + +The MExE QoS manager may request information from the network regarding the QoS available. + +The MExE QoS manager does not need to know the end user's subscribed QoS, this is held within the network and used to validate a requested QoS level. + +The MExE QoS manager may also be accessed through the MExE device's MMI. + +### 5.5.4 Network control API + +The network control API shall provide the QoS manager with access to the network specific QoS control (e.g. as defined for GPRS/UMTS in TS 24.007 [29] and TS 24.008 [30]). + +The MExE QoS manager may perform some QoS control, even if it is not provided in the network control. + +### 5.5.5 MExE QoS API + +The MExE QoS API provides the MExE executable with an interface to the QoS management. It does not require the MExE executable to have any knowledge of the underlying network, or how QoS is implemented in the network. + +The QoS API shall provide the MExE executable with a standard set of parameters. Refer to TS 23.107 [28] for details of these parameters (see note 1). + +NOTE 1: The FLOWSPEC parameters, defined by the IETF Integrated Services Working Group, provide the QoS information required by QoS capable network elements. + +Table 4 "Example parameters" shows the set of example parameters. + +**Table 4: Example parameters** + +| Parameter | Units | Type | +|----------------------|------------|-----------------------------------| +| Token Bucket Rate | bytes /sec | 32-bit IEEE floating point number | +| Token Bucket Size | bytes | 32-bit IEEE floating point number | +| Peak Data Rate | bytes/sec | 32-bit IEEE floating point number | +| Minimum Policed Unit | bytes | 32-bit integer | +| Maximum Packet Size | bytes | 32-bit integer | +| Latency | micro secs | 32-bit integer | +| Delay Variation | micro secs | 32-bit integer | +| Service Type | | service type | + +As a minimum the following three parameters shall be supported by the MExE QoS manager: + +- Token Bucket Rate; +- Token Bucket Size; +- Peak Data Rate. + +NOTE 2: The discussion of UMTS bearer service parameters as well as radio access bearer parameters is still going on. Especially the bitrate parameters and reliability parameter are under discussion, TS 23.107 [28]. + +If the MExE executable does not provide a full set of QoS parameters, then the MExE QoS manager shall provide QoS parameters based on information available to it (e.g. from the MMI settings), see clause 5.5.6 "Sources of Bearer Service Parameters". + +### 5.5.6 Sources of bearer service parameters + +A set of QoS parameters (QoS profile) specify the service provided to the user by the network. At bearer service establishment or modification different QoS profiles have to be taken into account. This is based on: + +- The MExE device capabilities; +- The MExE device or the TE within the terminating network; +- A QoS profile in the QoS subscription (describes the upper limits); +- Default QoS profile (of the user or network); +- A Network specific QoS profile characterising for example the current resource availability or other network capabilities. + +### 5.5.7 QoS streams + +Several MExE executables may be executing in the MExE device, each with a different QoS requirement. Also, a MExE executable may operate several QoS streams, each with different parameter settings. The MExE QoS manager within the MExE device shall be able to deal with each stream independently. + +### 5.5.8 QoS security + +Only the end user, MExE executable or the network using a QoS stream should be able to modify the QoS of that stream. + +## 5.6 Charging + +Support of charging is outside the scope of MExE standardisation. + +The following informative clauses provide a brief overview of the charging possibilities enabled by MExE. + +### 5.6.1 Generic charging support + +The standard GSM/UMTS charging records contain information sufficient to associate bearer usage and SMS/USSD messages with a subscriber. + +Third party service providers and/or service providers may define charging regimes for MExE services (e.g. on a MExE or WAP server). + +# --- 6 Generic MExE Security + +## 6.1 Introduction + +In order to manage the MExE and prevent attack from unfriendly sources or transferred applications unintentionally damaging the MExE device a security system is required. This clause defines the MExE security architecture. + +The basis of MExE security is: + +- a framework of permissions which defines the permissions transferred MExE executables have within the MExE device; +- the secure storage of these permissions (and permission type as defined in clause 6.5 "User permission types"); +- conditions within the execution environment that ensure that MExE executables can only perform actions for which they have permission. + +The MExE permissions framework is defined in 3GPP TS 22.057 [2] and is as follows (there is no implied hierarchy): + +- MExE Security Operator Domain (MExE executables authorised by the HPLMN operator, as described in clause 6.3.1 "MExE executable permissions for operator, manufacturer and third party security domains"); +- MExE Security Manufacturer Domain (MExE executables authorised by the ME manufacturer, as described in clause 6.3.1 "MExE executable permissions for operator, manufacturer and third party security domains"); +- MExE Security Third Party Domain (trusted MExE executables authorised by trusted third parties, as described in clause 6.3.1 "MExE executable permissions for operator, manufacturer and third party security domains"); +- MExE Untrusted Area. Untrusted MExE executables are not permitted to execute in a security domain (i.e. Operator domain, Manufacturer domain or Third Party domain) and execute in the Untrusted area, and have very reduced privileges as described in clause 6.3.2. "MExE executable permissions for untrusted MExE executables". + +A MExE device shall support either all three security domains or no domains. If the security domains are not supported, then all applications shall be untrusted. The MExE device shall not support any subset of the three security domains. Support of the MExE Untrusted area is mandatory. + +## 6.2 MExE executable integrity + +If the 3 MExE security domains defined in clause 6.1 "Generic security" are not supported, then the pre-verification of MExE executables at launch time described in this clause is optional. + +A potential threat is that MExE executables may be securely authenticated at the time of download, but tampered with or corrupted prior to being launched. Further a certificate may be compromised or expired. Authentication of a MExE + +executable at the time of download does not ensure that the MExE executable has not been modified when it is subsequently launched. Furthermore, authentication of a MExE executable at the time of launch does not ensure that the MExE executable is not modified during execution. Similarly, verification of the certificate at the time of download may not ensure that the certificate is valid at time of application launch, and verification of the certificate at the time of launch does not ensure that the certificate remains valid during execution. + +Therefore, the MExE device shall ensure application integrity immediately prior to application execution. + +Application integrity is defined as the state in which:- + +- application code has not been modified since authentication; and +- the certificate containing the root public key is checked and known to be valid. + +The mechanism by which the device preserves integrity is an implementation detail, dependant on the application storage mechanism and access. Examples of mechanisms that contribute to such application integrity could include : + +- Storage of applications in a memory area that cannot be compromised on the device; +- Preventing launch of the application when the MExE device becomes aware that the certificate is invalidated; +- Full signature verification prior to each application invocation (see clause 6.2.1 "Full signature verification"); +- Optimised pre-launch signature verification (see clause 6.2.2 "Optimised pre-launch signature verification"); +- Periodic full signature verification by separate process during application execution. + +The list of examples is not exhaustive and any other mechanisms ensuring application integrity may be equally considered. + +A MExE device may furthermore ensure that the application code has not been modified during application execution. + +### 6.2.1 Full signature verification + +Full signature verification assumes that the procedure of validation for downloaded MExE executables and certificates is used. For more details see clause 6.7 "Certification and Authorization Architecture". + +### 6.2.2 Optimised pre-launch signature verification + +This is an optional feature which is used to eliminate the potentially excessive overhead of checking a signature again after initial full certificate verification has already been performed. + +To use this process the MExE device shall create a hash of the executable object (executable object fingerprint) as if checking the signature. This shall be stored in a protected verified application list, along with indication of the domain permissions for the application. The hash used shall be the same type as that used for signing the object. When launching an application or downloading an applet, the hash shall be performed as for when computing the signature. The verified application list shall then be checked; if the hash value is present and the entry has not expired then the application or applet may execute. If no list entry exists for this object, or the entry has expired, the process shall then proceed with the full signature verification. Note that the lists for applications and applets should be separate and that an implementation determines management policy for the lists (e.g., ageing policy, which entries to delete when trying to add a new entry to a full list etc.). One restriction imposed that shall be enforced is that the maximum number of uses for an entry before it is marked invalid is limited to some maximum value. + +In the event that a new CCM is received by the MExE device, all verified application list entries shall be marked invalid unless some mechanism to determine the validity of an authorising certificate entry for each application is provided by the MExE device implementation. + +## 6.3 MExE executable permissions + +Support of MExE executable permissions as detailed in this clause is mandatory. + +### 6.3.1 MExE executable permissions for operator, manufacturer and third party security domains + +The following table 5 "Security domains and actions" specifies the permissions of operator, manufacturer and third party security domains in the order of restriction. + +The actions listed in the security table 5 "Security domains and actions" are generic actions. These actions can only be performed by MExE executables via application programming interfaces (APIs) (which are intrinsically part of the MExE implementation) The security restrictions shall apply to MExE executables whether the API functionality is called directly or indirectly by the MExE executable. Explicit user permission is required for all actions by MExE executables in all domains. Types of user permission are defined in clause 6.5 "User permission types". + +Untrusted MExE executables are not permitted access to any actions which access the phone functionality (phone functionality includes all the actions in table 5 "Security domains and actions") except for the exceptions identified in clause 6.3.2 "MExE executable permissions for untrusted MExE executables". + +Actions available using interfaces giving access to the phone functionality (either in existence at the time of approval of this specification or not) that are not listed in the security table 5 "Security domains and actions" shall be categorised into one of the groups in the security table 5 "Security domains and actions" by comparing its action against the groups in order as they are listed in the table 5 "Security domains and actions". If an action can be categorised into a more restrictive group near the top of the table, then it shall not be again categorised into another, less restrictive, group further down in the table. For example, if a new action eventually results in forwarding a call, it shall be categorised into Network access. If the action is totally new, it shall be categorised into some of the groups by comparing its functionality to the group description below and by comparing with the list of actions listed in the table within the group. + +1. Device core function access includes functions, which are an essential part of the phone functionality . +2. Support of core software download, which allows updating the ME radio, characteristics and properties by changing the core software in the ME (e.g. a new CODEC may be loaded into a ME, a new air interface, etc.) +3. (U)SIM smart card low level access includes functions, which allow communications at the transport service access point (send and receive application protocol data unit). +4. Network security access includes all functionalities which relate to CHV, CHV2, UNBLOCK CHV and UNBLOCK CHV2 (verification, management, reading or modifying), GSM authentication, GSM ciphering. +5. Network property access includes functions, which enable the management of operator-related data parameters and network settings. +6. Network services access includes all functionalities which result in or need interaction via the operator's network. +7. User private data access includes all functionalities which relate to management, reading or modifying of data that the user has stored in the MExE device including user preferences. +8. MExE security functions access includes all functionalities which, through an API relate to certificate handling in the MExE device; end to end encryption, signed content, hashing, access to public, private, secret keys stored in the MExE device or in a smart card. +9. Application access includes the functionalities which relate to launch provisioned functionality, MExE executables, external executables ((U)SIM tool kit application,...) usage. +10. Lifecycle management includes the functionalities which are needed for installing or removing MExE executables in the MExE device. +11. Terminal data access includes the functions which relate to accessing terminal data, i.e. not user data. +12. Peripheral access includes the functionalities related to peripherals other than user interface peripherals usage through a high level software application interface. +13. Input output user interface access includes the functionalities related to the user interface and user notification means usage. + +**Table 5: Security domains and actions** + +| Actions | MExE Security Domains | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|------------------|--|--|--| +| | Operator | Manufacturer | Third Party | | | | +| <b>Device core function access</b><br>Start/stop radio<br>Turn on/off device<br>Write time and/or date<br>Activate a user profile<br>Modify a user profile | No | | | | | | +| <b>Support of Core Software Download</b><br>e.g. Update ME software | No | Yes | No | | | | +| <b>(U)SIM smart card low level access<sup>11</sup></b><br>Send APDU<br>Slot management (power on/off, reset, port lock...) | No | | | | | | +| <sup>11</sup> – Access to (U)SIM is provided using more high level API as phonebook, application launching | | | | | | | +| <b>Network Security access</b><br>Run algorithm<br>Verify CHV/2 or UNBLOCK CHV/2<br>Activate/deactivate CHV<br>Modify CHV/2 | No | | | | | | +| <b>Network property access</b><br>Get IMSI<br>Get home network<br>Select network | Yes | No | | | | | +| <b>Network services access</b><br>Initiate a voice/data connection <sup>3</sup><br>Accept a voice/data connection <sup>3</sup><br>Call forward <sup>4</sup><br>Multiparty call <sup>4</sup><br>Call deflection <sup>4</sup><br>Explicit call transfer <sup>4</sup><br>Terminate an existing connection<br>Hold an existing connection<br>Resume an existing connection<br>Send point-point message (e.g. SMS, USSD) <sup>4</sup><br>Query network status<br>Get signal level<br>Get call list<br>QoS management | Yes | | Yes <sup>6</sup> | | | | +| <sup>3</sup> – A network connection may be via any supported bearer service | | | | | | | +| <sup>4</sup> – Multiparty, deflection, and explicit call transfer shall be permitted only to numbers explicitly supplied by the user to the MExE Executable. Modification of call forward numbers stored in the network shall only be permitted to numbers explicitly supplied by the user to the operator. | | | | | | | +| <sup>6</sup> – The Third Party domain's permission to access the networking action depends on the provisioning mechanism as described in clause 6.13.3 "Determining the administrator of the MExE device" | | | | | | | +| <b>User private data access <sup>1</sup></b><br>Read<br>Write<br>Get properties<br>Delete<br>Get Location Information<br>Read stored SMS<br>Delete stored SMS<br>Modify user preferences | Yes <sup>2</sup><br>Yes <sup>2</sup><br>Yes <sup>2</sup><br>Yes <sup>2</sup><br>Yes <sup>2</sup><br>Yes <sup>2</sup><br>Yes <sup>2</sup><br>Yes <sup>7</sup> | | | | | | +| <sup>1</sup> – User private data includes user files, phonebook, MSISDN, etc located on the MExE device. | | | | | | | +| <sup>2</sup> – The user shall be able to specify data access permissions within the capabilities of the MExE device. It is not applied to user preferences | | | | | | | +| <sup>7</sup> – Trusted applications only have permission to modify user preferences, and not to activate or deactivate them. The user shall be able to specify for each domain, the preferences that applications in that domain can access. All other preferences shall not be accessible to that domain. The default shall be that there is no access. Single action user permission is the only type of user permission that shall be possible for changes to User Preferences. | | | | | | | + +| Actions | MExE Security Domains | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------|-------------| +| | Operator | Manufacturer | Third Party | +| <b>MExE security functions access</b> | | | | +| Install a certificate for a given domain | | Yes <sup>5</sup> | | +| Uninstall a certificate for a given domain | | | | +| Replace a certificate for a given domain | | Yes <sup>5</sup> | | +| Data encryption API | | | | +| Verify a signature API | | Yes <sup>5</sup> | | +| Compute a digital signature API | | | | +| Hash a content API | | Yes | | +| Non repudiation API | | Yes | | +| | | Yes | | +| | | Yes | | +| | | Yes | | +| | | Yes | | +| | | Yes | | +| <sup>5</sup> – Only the organisation whose public key is certified (or the organisation that certified the public key) can add, delete or replace a particular certificate. | | | | +| <b>Application access</b> | | | | +| Get application list | | Yes <sup>8</sup> | | +| Launch an application | | Yes <sup>8</sup> | | +| Get application status | | Yes <sup>8</sup> | | +| Stop, suspend, resume an application | | Yes <sup>9</sup> | | +| <sup>8</sup> – ME provisioned functionality access is limited to manufacturer domain.<br>(U)SIM tool kit application access is limited to operator domain.<br>MExE executable access is limited to MExE executable issued by the same issuer (identify by the certificate) of launched MExE executable | | | | +| <sup>9</sup> – Access is limited to MExE executable which launch the application. But the end user, shall have a way to stop the launched application, MExE environment may stop the launched application or launched application may stop itself. | | | | +| <b>Lifecycle management</b> | | Yes | | +| Install a MExE Executable | | | | +| Uninstall a MExE executable | | | | +| <b>Terminal data access</b> | | | | +| Get manufacturer software version | | Yes | | +| Read time and date | | Yes | | +| <b>Peripheral access</b> | | Yes | | +| Sound generation to speaker (e.g. via stream) | | | | +| Set speaker volume | | | | +| printer access | | | | +| Monitor the power state | | | | +| Change the power state | | | | +| Activate/ access Serial port (RS232, IrDA, Bluetooth, USB ...) access | | | | +| Activate/access Parallel port | | | | +| Activate/access Smart card other than (U)SIM card (Send APDU, Slot management) | | | | +| <b>Input output User interface access</b> | | | | +| Input device (keyboard, mouse ...) | | Yes <sup>10</sup> | | +| Output device (display ) | | Yes <sup>10</sup> | | +| Output notification device(smart icon, sound, light, vibrator ...) | | Yes | | +| <sup>10</sup> – Access request requires no user permission. | | | | + +The lists in the groups in table 5 "Security domains and actions" are not exhaustive, and other actions which are of the same category shall be included in the group for the purposes of requesting user permission. + +This clause identifies the permissions for MExE executables in the 3 security domains (operator, manufacturer and Third Party). The permissions do not apply to untrusted MExE executables which are not permitted to execute within the domains. + +### 6.3.2 MExE executable permissions for untrusted MExE executables + +When the Security Domains are not supported then all executables are untrusted and they execute in the untrusted area for which the executable permissions are defined as follow in table 6 "Executable permissions for untrusted MExE executables". + +In order to facilitate untrusted MExE executables having some limited access to MExE device functionality beyond their very limited privileges, some of the access permissions in the previous table 5 "Security domains and actions" are extended to untrusted MExE executables and described in table 6 "Executable permissions for untrusted MExE executables" as well as in clause 6.11 "Separation of I/O streams". + +The untrusted MExE executables permitted to use these facilities shall be MExE executables the user has downloaded him or herself, and not be MExE executables that have been pushed to the user. MExE executables on the MExE device due to the user having visited a particular Web site are considered to be MExE executables that the user had downloaded him or herself. + +Untrusted MExE executables shall not be permitted access to any other functions. + +**Table 6: Executable permissions for untrusted MExE executables** + +| | Classmark 1 | Classmark 2 | Classmark 4 | Classmark 3 | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------| +| <b>User Interface</b> | An untrusted, uninstalled MExE executable (e.g. an applet) can access the user interface output and input without user permission, but the sending of user data to a server to which the MExE executables has a session connection (e.g. as part of a browser session) requires user permission.<br>An installed untrusted MExE executable shall only be able to access the user interface output and input with user permission (clearly, for the usability of untrusted MExE executables such as games, blanket user permission should be sought and given, and this is permissible). | | | Untrusted MExE executables can access the user interface output and input without the user permission. | +| <b>File, Persistent Data</b> | File access is not permitted for untrusted MExE executables.<br>But, untrusted MExE executables can access files only in the MExE executable's own directory. | | | But, persistent data may be stored via the MIDP record management system (stores are shared between MIDlets in the same MIDlet Suite). | +| <b>Transmission over the Access Network</b> | Untrusted MExE executables shall be able to exchange data, voice, HTTP requests, etc. over the Access Network under the following conditions:<br>The recipient of a transmission (e.g. a phone number, a URL, a server name, etc.) shall be presented to the user for permission by a provisioned functionality of the MExE device itself, even if this recipient was already presented by the executable (this facility would support, for example, "click to dial" buttons/links in untrusted MExE executables).<br>It shall not be possible for an application to use a transmission channel that it did not initiate (except for MIDlets within the same MIDlet suite). | | | | +| <b>Generate DTMF</b> | Untrusted MExE executables shall be able to generate DTMF tones under the following conditions:<br>An untrusted MExE executable is only permitted to send DTMF tones in a currently active call. The request to generate DTMF tones in the currently active call, shall result in the characters which the tones represent being presented to the user for permission by a provisioned functionality of the MExE device. | | | | +| <b>Add Phonebook Entry</b> | Untrusted MExE executables shall be able to add a phonebook entry (i.e. name and number only) under the following conditions:<br>The name and the number to be added shall be displayed to the user for permission by a provisioned functionality of the MExE device and not by the MExE executable itself. The phonebook entry shall not be added without user permission. The function shall not be able to modify or delete any phonebook entry. | | | | +| <b>Executable Interaction</b> | Executable interaction is not permitted for untrusted MExE executables (except for MIDlets within the same MIDlet suite). | | | | + +NOTE: The functionality of "Generate DTMF tones" and "Add Phonebook Entry" is not supported by the MIDP at the moment. + +## 6.4 Handling of MExE executables when their valid root public key is not available + +This clause considers the effect on MExE executables when the root public key of a secure domain (e.g. operator, manufacturer, third party) is no longer available (e.g. when the UICC is being physically removed, or the root public key is no longer valid). + +### 6.4.1 Launching of MExE executables when their valid RPK is not available + +It shall not be possible to launch a MExE executable to run in a security domain unless the root public key of that security domain is available and valid. + +### 6.4.2 Currently executing secure MExE executables when their valid RPK is no longer available + +On detection that the valid root public key of a secure domain is no longer present, the MExE device shall permit MExE executables currently executing in the secure domain controlled by that root public key to continue executing. Furthermore, if the same RPK is available again, the executable is allowed to keep on executing. However, if a different RPK is validated, the currently running MExE executables (under the old RPK) in that secure domain shall be terminated. + +## 6.5 User permission types + +Support of user permission types is mandatory. + +The term "user permission" is defined to mean that the user can give permission for a specific action in one of the ways defined in table 7 "User Permissions". Support single action permission is mandatory, but support of blanket permission and session permission is optional. + +Any request for user permission as described in table 7 "User Permissions" must display a user friendly name identifying the signer of the corresponding MExE executable, if available. The "subject" field of the certificate of the signer ("subject" here refers to the "subject" fields of WTLS and X.509 certificates and an equivalent field for any other format of certificate) shall be made available to the user upon request. If an application, for which user permission is being sought, is untrusted, the fact that the application is untrusted shall be at least visually indicated to the user, if the MExE device is capable of visual indication, whenever user permission is sought. Other means of indication are additionally permitted. If the MExE device is not capable of visual indication, or is not designed for use by a human user, other means of indication shall be used. + +The MExE device shall allow user control of permissions relating to all action groups listed in the table 5 "Security domains and actions" that are required by the MExE executable and supported by the MExE device. + +Multiple action group permissions may be controlled in a single user action on the MExE device regardless of the permission type as listed in table 7 "User Permissions". In such case, these action group permissions shall be made explicit to the user. + +Note that blanket permission cannot be used for uninstalled MExE executables e.g. applets, WMLS. + +**Table 7: User Permissions** + +| <b>Permission Type</b> | <b>User Permissions</b> | | | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | <b>Description</b> | <b>Invocation</b> | <b>Revocation</b> | +| blanket permission | The user gives blanket permission to the MExE executable for the specified action, and the MExE executable subsequently uses the user's original permission for the identified subsequent actions whenever the MExE executable is running. | Typically such permission would be given at MExE executable configuration or run time. | The blanket permission maybe revoked by the user at any time. The user permission no longer applies once the MExE executable has been removed. | +| session permission | The user gives permission to the MExE executable for the specified action during a specific run time session of an MExE executable, and the MExE executable subsequently uses the user's permission for the identified subsequent actions whilst the MExE executable session is still running. | Typically such permission would be given at MExE executable run time. | The session permission maybe revoked by the user at any time. The user permission no longer applies once the MExE executable run time session has terminated. | +| single action permission | The user gives a single permission to the MExE executable for the specified action; if the MExE executable subsequently wishes to repeat the action it must again request the user's permission for the identified subsequent action. | Typically such permission would be given at MExE executable run time. | The user permission no longer applies once the action has terminated. | + +## 6.6 Root Public keys + +If the 3 MExE security domains defined in clause 6.1 "Generic security" are not supported, then the root public key management described in this clause is optional. + +The definition of the secure mechanism in this clause to mark as valid a root public key certificate on the ME, is out of the scope of this specification. + +### 6.6.1 Operator root public key + +The ME may support secure storage for one or more certificates, each of which contains an operator root public key. The ME shall support the use and management of a certificate containing an operator root public key stored on the MExE-(U)SIM and in the ME. The ME shall behave according to clause 6.6.1.2 "ME actions on SIM insertion and/or power up". For support of public key management on the SIM and the USIM refer to TS 51.011 [27] and TS 31.102 [39] respectively. The certificate contains a root public key generated either by the operator, or by a CA trusted by the operator. + +If the MExE device does not contain a valid operator root public key, then the certificate chain to MExE executable previously executing in the Operator Domain will be invalid, and the MExE executables will be excluded from the operator domain. + +The user shall not be able to add or delete any type of operator public key (root or contained in a certificate). + +Optionally, the operator may install a corresponding disaster-recovery root public key stored in the MExE device, enabling the operator to use a secure mechanism (involving the disaster-recovery key) to replace the certificate containing the standard operator root public key. It shall not be possible to use the disaster recovery operator root public key to replace the operator root public key unless both public keys are from the same operator. + +There shall be no more than one valid operator root public key on the MExE device at any one time. A valid operator root public key on the (U)SIM shall always have precedence over any operator root public key on the ME. Any operator root public key(s) on the ME shall be marked invalid when a valid operator root public key is present on the (U)SIM. + +An application signed by an operator shall not be able to execute in the Operator Domain unless the root public key of that operator is installed in the MExE device (either ME or MExE-(U)SIM) and is marked as trusted. + +#### 6.6.1.1 Caching of root public keys + +The ME shall behave as if it reads the operator root public key from the secure area every time the ME needs the key to verify a signature. Examples of the secure area include an area on a (U)SIM or a secure, persistent area on the ME. + +If the ME uses a mechanism for caching public keys, it shall do so in a way that maintains the integrity of the secure area and is consistent with the keys stored in the secure area. With the exception of improved performance, the operation of the device using cached public keys must be indistinguishable from that of a device that reads the key from the secure area every time it uses the key for verification. + +No cached version of a key may exist beyond the expiration or termination of the key in the secure area. For example, if the ME caches a root public key held on the (U)SIM, the ME shall purge the cache when the (U)SIM application is stopped (or the SIM card is withdrawn). + +#### 6.6.1.2 MExE device actions on detection of valid (U)SIM application and/or power up + +This clause defines the sequence of actions on identification by the MExE ME that a valid SIM card, or USIM application on the UICC, has been detected (e.g. through insertion of (U)SIM card, power up of MExE device etc.). More specifically, these actions relate to the enabling or disabling of the operator domain and the status of the operator applications on the ME. + +The requirements in this clause ensure that the operator domain on the ME belongs to the same operator as the operator that issued the valid (U)SIM application (if detected) in the MExE device and, if there is an operator root public key (ORPK) on the MExE-(U)SIM, that trusted operator applications on the MExE device were verified using that ORPK. + +The ME shall support the use and management of an Operator root public key (ORPK) on the MExE-(U)SIM. + +On power up the MExE device shall behave as dictated by figure 4 "MExE device behaviour on power up" below. + +![Flowchart of MExE administrator determination mechanism](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` +graph TD; Start[MExE administrator determination mechanism] --> Q1{Is the administrator root public key in the MExE-(U)SIM?}; Q1 -- Yes --> End1([Owner of the administrator root public key is the Administrator]); Q1 -- No --> Q2{Is the administrator root public key in the MExE device?}; Q2 -- Yes --> End1; Q2 -- No --> End2([User acts as the Administrator]); +``` + +The flowchart illustrates the MExE administrator determination mechanism. It begins with a rectangular box labeled "MExE administrator determination mechanism". An arrow points down to a decision diamond: "Is the administrator root public key in the MExE-(U)SIM?". If the answer is "Yes", the flow proceeds to a rounded rectangular box: "Owner of the administrator root public key is the Administrator". If the answer is "No", the flow proceeds to another decision diamond: "Is the administrator root public key in the MExE device?". If the answer is "Yes", the flow proceeds to the same rounded rectangular box: "Owner of the administrator root public key is the Administrator". If the answer is "No", the flow proceeds to a rounded rectangular box: "User acts as the Administrator". + +Flowchart of MExE administrator determination mechanism + +Figure 4: MExE device behaviour on power up + +Note that the procedure in Figure 4 "MExE device behaviour on power up" checks for a match between the Operator ID on the (U)SIM and the Operator ID from the ORPK in the ME. Currently, one mechanism for defining the Operator ID on the (U)SIM is through use of the MCC+MNC. As an additional note, on DCS1900, the MCC+MNC is 6 digits, but + +elsewhere it is 5 digits. The MExE device needs to know how many digits to use. However, this is outside the scope of this specification. The implementations of MExE devices need to establish agreements on using the MCC+MNC as the Operator ID on the (U)SIM. Likewise, the implementations of MExE devices need to establish agreements on how to define the Operator ID belonging to the ORPK. + +The ME shall only read the ORPK from the MExE-(U)SIM when required and shall not store a ORPK from the MExE-(U)SIM on the ME in a manner inconsistent with that detailed in clause 6.6.1.1 "Caching of root public keys". + +When an operator root public key stored on the ME is marked as invalid, all operator applications verified using that root public key or by certificates verified by a chain that terminates with that root public key, shall cease operation as soon as possible and shall be marked as untrusted. + +Removal of the (U)SIM shall not cause the status (i.e. valid or invalid) of any operator root public key on the MExE device to change. + +### 6.6.2 Manufacturer root public key + +The ME shall support secure storage for a certificate containing a manufacturer root public key. The certificate contains a root public key generated by the manufacturer of the MExE device, or by a CA trusted by the manufacturer of the MExE device. + +If the ME does not contain a valid manufacturer root public key, then the certificate chain to MExE executable previously executing in the Manufacturer Domain will be invalid, and the MExE executables will be excluded from the manufacturer domain and marked as untrusted. + +The user shall not be able to add or delete any type of manufacturer public key (root or contained in a certificate). + +The Manufacturer shall put a root public key and optionally its corresponding disaster-recovery key in the ME at the time of manufacture, and use a proprietary secure mechanism (e.g. using the disaster-recovery key) to replace the certificate containing the manufacturer root public key. It shall not be possible to use the disaster recovery manufacturer root public key to replace the standard manufacturer root public key unless both public keys are from the same manufacturer. + +An application signed by a manufacturer shall not be able to run in the Manufacturer Domain unless the root public key of that manufacturer is installed in the ME and is marked as trusted. + +The manufacturer, and only the manufacturer, may use a secure mechanism to mark as valid/invalid a certificate containing the manufacturer root public key on the ME. It shall only be possible to use this mechanism to mark a certificate containing a new manufacturer root public key on the ME as valid, when all manufacturer root public keys are marked as invalid. + +There shall be no more than one valid manufacturer root public key on the ME at any one time. Any other manufacturer root public key(s) on the ME device shall be marked invalid when a different manufacturer root public key is marked as valid on the ME. + +### 6.6.3 Third party root public key + +The ME shall support secure storage for at least one certificate containing a third party root public key. The ME shall support the use and management of certificates containing Third Party root public keys stored on the MExE-(U)SIM and in ME. For support of public key management on the SIM and the USIM refer to TS 51.011 [27] and TS 31.102 [39] respectively. The MExE device may contain root public key(s) generated by CA(s) implicitly trusted by the user. The user will be able to securely install (using a secure transport) or remove Third Party root public keys at any time using a system administrative tool. + +The Manufacturer, Operator and Administrator may at their discretion, securely install certificates containing Third Party root public key(s) on behalf of the user, e.g. at the time of manufacture by the Manufacturer. See clause 6.10 "Certificate management" for details of Administrator control of Third Party certificate download. + +If a Third Party public key is deleted or becomes invalid, then the certificate chain to MExE executables previously executing in the Third Party Domain certified by that public key will become "untrusted". + +There may be any number of Third Party root public keys on the MExE device. + +The third party domain administrator, i.e. the Administrator (user or other body) shall be able to enable and disable Third Party root public keys by using CCM, see clause 6.10.1 "Certificate configuration message (CCM)". The process of adding/removing public keys and enabling/disabling public key are independent. + +All third party certificates shall be subject to restrictions imposed by valid certificate configuration messages. + +See clause 6.10 "Certificate management" for the management of Third Party root public keys. + +## 6.7 Certification and authorisation architecture + +If the 3 MExE security domains defined in clause 6.1 "Generic security" are not supported, then the certificate and authorisation architecture described in this clause is optional. + +In order to enforce the MExE security framework a MExE device is required to operate an authentication mechanism for verifying downloaded MExE executables. A successful authentication will result in the MExE executable being trusted; and able to be executed in a security domain (as determined by the root public key of its certification tree). + +As the MExE device may want to authenticate content from many sources, a public key based solution is mandatory. Before trusting MExE executables, the MExE device will therefore check that the MExE executable was signed with a private key, for which the MExE device has the corresponding public key. The corresponding public key held in the MExE device must either be a root public key (securely installed in the MExE device, e.g. at manufacture) or a signed public key provided in a certificate. The MExE device must be able to verify certificates, i.e. have the public key (as a root key or in a certificate) corresponding to the private key used to sign the certificate. Support of certificate chains is therefore mandatory. + +The requirements on authorisation and certification are given in clause 6.7.1 "Certification requirements". An example authorisation and certification process is described in clause 6.7.3 "Example certification process". + +### 6.7.1 Certification requirements + +A MExE device cannot verify certified MExE executables of a particular domain unless it has a root public key for that particular domain. + +Root public keys shall be securely installed in the MExE device, say, at the time of manufacture. + +It is recommended that a "disaster recovery" root public key be securely installed on the MExE device, to be used to install new root public keys when all other root public keys on the MExE device are invalid. + +Third Party Domain root public keys will typically be installed along with and integrated into the MExE device browser, as is done for PC-based browsers. + +A MExE executable can only be verified if the MExE device contains a valid root or certified public keys corresponding to the private key used to sign the MExE executable. + +A MExE device shall support at least one level of certificate under operator, manufacturer or Third Party root public keys. The MExE device shall support at least one level of certificate chain analysis in a signed content package, as shown in figure 5 "Trust hierarchy". + +A certificate (other than one containing a root public key) shall only be considered valid if the signature on the certificate is verified by a valid public key (root or contained in a certificate) already present on the MExE device and if the certificate being verified has not expired. + +Public keys shall not be shared between domains. + +#### 6.7.1.1 MExE terminal requirements for certificate processing + +A MExE device shall support the processing of X509 certificates profiled in the "WAP Certificate and CRL Profile" [47] together with additional requirements defined in the MExE specification, see clause 6.9.1.1 "X509 version 3". The certificate chain depth is still mandated to be one level only, as mentioned in clause 6.7.1 "Certificate requirements" and indicated in figure 5 "Trust hierarchy". + +A MExE device shall support the SHA1WithRSA signature algorithm. The object identifier value can be found in [49]. A MExE device may also support other signature algorithms. + +MExE devices may also support the processing of other certificate formats. + +![Flowchart titled 'MExE administrator determination mechanism, for MExE-(U)SIM supporting third party certificates'. The process starts with 'Is user the administrator?'. If 'Yes', it checks 'Is certificate on MExE (U)SIM?'. If 'No', 'User is the administrator'. If 'Yes', it checks 'Certificate type?'. If 'CP-TP', it checks 'Query user: Add CP-TP to TP?'. If 'No', 'User is the administrator, but TP loses network access'. If 'Yes', it checks 'Query user: User wishes temporary CP-Admin?'. If 'Yes', 'CP-Admin certificate owner is temporary administrator'. If 'No', it goes to 'Cases (a), (b), (c)'. If 'CP-Admin', it checks 'Check with administrator certificate'. If 'Case (d)', it checks 'Check with CCM to add/disallow to TP list'. If 'No', 'Current administrator is retained'. If 'Yes', 'Current administrator retained, but TP loses network access'. If 'Is user the administrator?' is 'No', it checks 'Is certificate on MExE (U)SIM?'. If 'Yes', it checks 'Certificate type?'. If 'CP-TP', it checks 'Query user: Add CP-TP to TP?'. If 'No', 'Current administrator is retained'. If 'Yes', it checks 'Query user: User wishes temporary CP-Admin?'. If 'Yes', 'CP-Admin certificate owner is temporary administrator'. If 'No', it goes to 'Cases (a), (b), (c)'. If 'CP-Admin', it checks 'Check with administrator certificate'. If 'Case (d)', it checks 'Check with CCM to add/disallow to TP list'. If 'No', 'Current administrator is retained'. If 'Yes', 'Current administrator retained, but TP loses network access'. If 'Is certificate on MExE (U)SIM?' is 'No', 'Current administrator is retained'.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +graph TD + Root["MExE administrator determination mechanism, for MExE-(U)SIM supporting third party certificates"] --> Q1{Is user the administrator?} + Q1 -- Yes --> Q2{Is certificate on MExE (U)SIM?} + Q1 -- No --> Q3{Is certificate on MExE (U)SIM?} + Q2 -- No --> A1([User is the administrator]) + Q2 -- Yes --> Q4{Certificate type?} + Q4 -- CP-TP --> Q5{Query user: Add CP-TP to TP?} + Q4 -- CP-Admin --> Q6{Query user: User wishes temporary CP-Admin?} + Q5 -- No --> A2([User is the administrator, but TP loses network access]) + Q5 -- Yes --> Q6 + Q6 -- Yes --> A3([CP-Admin certificate owner is temporary administrator.]) + Q6 -- No --> Cases["Cases (a), (b), (c)"] + Q3 -- Yes --> Q7{Certificate type?} + Q3 -- No --> A4([Current administrator is retained]) + Q7 -- CP-TP --> Q8{Query user: Add CP-TP to TP?} + Q7 -- CP-Admin --> Q9{Check with administrator certificate} + Q8 -- No --> A4 + Q8 -- Yes --> Q9 + Q9 -- Case (d) --> Q10{Check with CCM to add/disallow to TP list} + Q9 -- Cases --> A3 + Q10 -- No --> A4 + Q10 -- Yes --> A5([Current administrator retained, but TP loses network access]) + +``` + +Flowchart titled 'MExE administrator determination mechanism, for MExE-(U)SIM supporting third party certificates'. The process starts with 'Is user the administrator?'. If 'Yes', it checks 'Is certificate on MExE (U)SIM?'. If 'No', 'User is the administrator'. If 'Yes', it checks 'Certificate type?'. If 'CP-TP', it checks 'Query user: Add CP-TP to TP?'. If 'No', 'User is the administrator, but TP loses network access'. If 'Yes', it checks 'Query user: User wishes temporary CP-Admin?'. If 'Yes', 'CP-Admin certificate owner is temporary administrator'. If 'No', it goes to 'Cases (a), (b), (c)'. If 'CP-Admin', it checks 'Check with administrator certificate'. If 'Case (d)', it checks 'Check with CCM to add/disallow to TP list'. If 'No', 'Current administrator is retained'. If 'Yes', 'Current administrator retained, but TP loses network access'. If 'Is user the administrator?' is 'No', it checks 'Is certificate on MExE (U)SIM?'. If 'Yes', it checks 'Certificate type?'. If 'CP-TP', it checks 'Query user: Add CP-TP to TP?'. If 'No', 'Current administrator is retained'. If 'Yes', it checks 'Query user: User wishes temporary CP-Admin?'. If 'Yes', 'CP-Admin certificate owner is temporary administrator'. If 'No', it goes to 'Cases (a), (b), (c)'. If 'CP-Admin', it checks 'Check with administrator certificate'. If 'Case (d)', it checks 'Check with CCM to add/disallow to TP list'. If 'No', 'Current administrator is retained'. If 'Yes', 'Current administrator retained, but TP loses network access'. If 'Is certificate on MExE (U)SIM?' is 'No', 'Current administrator is retained'. + +Figure 5: Trust hierarchy + +The boxes below the root keys represent individual public key certificates. The solid boxes represent the minimum MExE, and the dotted boxes represent possible further support for public key certificates (either at the first or subsequent levels). + +### 6.7.2 Certification administration requirements + +For control of third party certificates, the MExE device supports storage of a certificate containing an administrator root public key as detailed in clause 6.13.1 "Administrator root public key". + +This certificate is managed separately from the hierarchy of Figure 5 "Trust Hierarchy" discussed in clause 6.7.1 "Certification requirements". The administrator root public key in this certificate is primarily used for designating an administrator of the third party certificates. Note, the administrator root public key does not implicitly define a security domain, and is used in complement with the root public keys of the operator, manufacturer, and third party domains. + +The relationship of the administrator certificate (and root public key) to the management of third party certificates is detailed in part of clause 6.10 "Certificate management". + +The relationship of the administrator certificate to the mechanism for determining if a third party certificate is trusted is detailed in part of clause 6.10.1 "Certificate configuration message (CCM)". + +Mechanisms for designating an administrator are detailed in clause 6.13.2 "Provisioned mechanism for designating administrative responsibilities and adding third parties in a MExE device". + +### 6.7.3 Example certification process + +The following processes might be followed in order to securely download a Third Party application to a MExE device. + +Root public keys for a number of Certification Authorities (CAs) are installed in the MExE device, along with the MExE device browser, at manufacture. These root public keys can be used to verify certificates for Third Party MExE executables. + +1. A third party software developer generates a private and public key pair (or obtains such a pair from a CA). +2. The third party software developer obtains a certificate for the public key from a CA. The certificate contains the developer public key, signed with the private key of the CA. +3. The 3rd party software developer adds all the certificates required in the key chain in the JAR. +4. The MExE device downloads a MExE executable of the third party software developer. +5. The MExE device verifies the certificate using the root public key, contained in the browser, of the relevant CA, and extracts the third party software developer public key and may store it in the certificate store for future use. + +6. The MExE device verifies that the MExE executable was signed using the private key corresponding to the third party software developer public key and installs or rejects the MExE executable accordingly. + +All downloaded applications shall follow the procedure described in clause 6.7.4 "Certificate Chain Verification" in order to verify the application signature and the certificate chain. If the 3 security domains are not supported, the procedure described in the next clause is optional. + +### 6.7.4 Certificate Chain Verification + +This clause presents the procedure of validation of any downloaded MExE executable. It checks for the presence of the signature used to sign the application as well as the presence and integrity of all the certificates needed to successfully verify the signature. As a result, the application under scrutiny is deemed trusted or untrusted, i.e. will be allowed execution in one of the secure domains or in untrusted area, or otherwise the application will not be allowed to be executed and will be deleted. In any outcome of the verification, the user is notified about the result. The user also may wish to see certificate details if the application is allowed to be executed on the MExE device. + +The MExE device shall follow "certificate verification" procedure as described below. The procedure shall contain at least the following logical phases (not necessarily in the order stated below): + +**Signature and Certificate Verification Supported:** Checks whether signature and certificate verification procedure is supported on the MExE ME. + +**Executable with Signature and End Entity Certificate (note):** Checks whether the executable contains a signature together with the corresponding end entity certificate. + +**Valid Application Signature (note):** This phase comprises the following checks: + +- Check if the signature and the end entity certificate formats are supported by the device. If this check fails, the application is classified as untrusted. +- Check if the signature algorithm is supported/known by the device. If this check fails, the application is classified as untrusted. +- Check if the signature can be cryptographically verified by using the accompanying end entity certificate . If this check fails, the application is not allowed execution and is deleted. + +**Complete set of Intermediate Certificates Available (note):** Checks if all the necessary intermediate certificates (certificates between the RPK and the end entity certificate) are available. + +**Valid RPK on (U)SIM/ME:** Checks if a valid RPK (not expired) exists on the (U)SIM or on the ME that could verify a certificate chain originating from the end entity certificate accompanying the application. + +NOTE: These steps could include validation (e.g. expiration, revocation, etc.) checking by means of e.g. OCSP, SCVP, CRL-Consultation, and etc. The use of certificate revocation checking is recommended but is not mandated or defined in this specification. + +**Certificate Chain Cryptographically Verified:** Checks if all the certificates from the end entity certificate to the RPK can be verified cryptographically. Certificate verification shall be performed according to the functional requirements given in clause 6.1 "Basic Path Validation" of RFC 2459 [43] excluding revocation checking. + +**Secure Domains Supported:** Checks whether MExE ME supports secure domains. + +Only if all the above checks are successful, the downloaded application is deemed trusted and is allowed to be executed in the designated trusted domain (operator, manufacturer, trusted third party). Otherwise, the application is either untrusted (execution in the untrusted area only is allowed) or deleted (execution is not allowed at all) as per the figure 6 "Certificate Chain Verification Diagram" and as explained above. The executable shall only be designated into one of the trusted domains, and it shall be possible to verify the certificate chain unambiguously to one and only one root public key. + +The MExE ME shall allow for a "user notification" procedure as described below. + +It shall be possible to display certificate details to the user if requested, however, since the terminal might not have a display or might not be meant for a human user the methods presented in "user notification" section are not discussed any further in this specification. Figure 6 "Certificate Chain Verification Diagram" shows an example of the certificate chain verification procedure. + +![Flowchart of Certificate Chain Verification. It starts with 'Validation', which branches into 'Untrusted', 'Trusted' (In Operator or Manufacturer or Third Party Domain), and 'Deleted'. 'Untrusted' and 'Trusted' lead to end nodes, while 'Deleted' leads to an 'X'.](8269648391c59363ea61243864a2adf7_img.jpg) + +### Verification + +``` +graph TD; Start(( )) --> Validation[Validation]; Validation --> Untrusted[Untrusted]; Validation --> Trusted["Trusted<br/>In Operator or Manufacturer<br/>or Third Party Domain"]; Validation --> Deleted[Deleted]; Untrusted --> End1(( )); Trusted --> End2(( )); Deleted --> X[X]; +``` + +Flowchart of Certificate Chain Verification. It starts with 'Validation', which branches into 'Untrusted', 'Trusted' (In Operator or Manufacturer or Third Party Domain), and 'Deleted'. 'Untrusted' and 'Trusted' lead to end nodes, while 'Deleted' leads to an 'X'. + +**Figure 6: Certificate Chain Verification Diagram** + +## 6.8 Usage of Signed Content + +### 6.8.1 Signed packages used for installation + +If the 3 MExE security domains defined in clause 6.1 "Generic security" are not supported, then the signed packages used for installation, described in this clause, are optional. + +The Java Archive (JAR) file format shall be supported on classmark 2 and 3 MExE devices for securely packaging objects that are to be downloaded and installed on the ME. The method for securely packaging objects for MExE classmark 1 devices may be referenced from the WAP specifications in a future release of this specification. A MExE device may support other proprietary means of downloading and installing objects. + +The JAR file shall contain a manifest file that has at least the following attribute: + +`MExE-Implementation-Type` + +The information contained within the manifest file is represented as so-called "name: value" pairs, where "name" is represented by `MExE-Implementation-Type`. Groups of name-value pairs are known as a "section", where sections are separated from other sections by empty lines. + +The `MExE-Implementation-Type` value shall be one of the following:- + +#### - **"MExENativeLibrary"** + +in the case of a MExE Native Library (as described in 8.3.2 "Installing MExE native libraries"); + +#### - **"TTPCertificate"** + +in the case of a certificate containing a 3<sup>rd</sup> party root public key (as described in 6.8.2 "Installation of root certificates in a signed data package"); + +#### - **"ManufacturerCertificate"** + +in the case of a certificate containing a manufacturer root public key (as described in 6.8.2 "Installation of root certificates in a signed data package"); + +#### - **"OperatorCertificate"** + +in the case of a certificate containing an operator root public key (as described in clause 6.8.2 "Installation of root certificates in a signed data package"); + +#### - **"AdminCertificate"** + +in the case of an administrator certificate, which shall consist of a section containing both the administrator certificate and a CCM (as described in clause 6.8.2 "Installation of root certificates in a signed data package"); or + +#### - **"OrdinaryTTPCertificate"** + +in the case of a certificate or certificate list containing 3rd party public key(s). An example of a certificate list syntax can be found in [52] + +#### - **"OrdinaryManufacturerCertificate"** + +in the case of a certificate or certificate list containing manufacturer public key(s). An example of a certificate list syntax can be found in [52] + +#### - **"OrdinaryOperatorCertificate"** + +in the case of a certificate or certificate list containing operator public key(s). An example of a certificate list syntax can be found in [52] + +#### - **"CCM"** + +in the case of a CCM (as described in clause 6.8.2 "Installation of root certificates in a signed data package"); or + +#### - *-free-format-value-* + +in the case of proprietary binaries or Java classes such as native DSP code, provisioned functionality upgrades and patches (as described in clause 6.8.3 "Installation of other signed data"). + +Refer to [42] for full details of how to encode the "name: value" pairs and "section" in a JAR manifest file. + +See figure 7 "Signed packages". When a download of a JAR file is completed, the system installer shall read the manifest to determine what types of files are contained in the JAR, and install them appropriately. + +Note that a signed package containing a library which does not have a manifest attribute "MExE-Implementation-Type: MExENativeLibrary" shall be considered to be some type of upgrade to libraries that are intrinsically part of the MExE device implementation rather than a "MExE native library". E.g. + +MExE-Implementation-Type: ManufacturerUpgrade (something.dll) + +(Recommended behaviour for the server is that it uses the capability information supplied from the MExE device to determine how to offer appropriate upgrades.) + +![Diagram of a signed package structure showing Signature, Manifest (attributes), and Contents (Java classes, native code, certificate, etc.). A line points from the Manifest (attributes) box to a box labeled MExE-Implementation-Type: ....](9edb407536d4d4d4a6ac391527af047c_img.jpg) + +The diagram illustrates the internal structure of a signed package. It is represented as a vertical stack of three rectangular boxes. The top box is labeled "Signature". The middle box is labeled "Manifest (attributes)". The bottom box is labeled "Contents (Java classes, native code, certificate, etc...)". A line originates from the "Manifest (attributes)" box and points to an external box on the right labeled "MExE-Implementation-Type: ....". + +Diagram of a signed package structure showing Signature, Manifest (attributes), and Contents (Java classes, native code, certificate, etc.). A line points from the Manifest (attributes) box to a box labeled MExE-Implementation-Type: .... + +Figure 7: Signed packages + +### 6.8.2 Installation of root certificates in a signed data package + +Root certificates in a signed package (whose signature verifies as described in clause 6.6 "Root Public keys" to the Manufacturer root, Operator root, or the Administrator root), may be installed to the root public key store on the MExE device. Note that the certificate thus packaged does not necessarily belong to the manufacturer domain. The types of certificate that can be present and installed by packages are given in table 8 "Allowed certificate types in signed packages". The MExE device shall store the root public key as indicated by the certificate type. + +When a certificate containing an Administrator root public key is thus contained in a signed package, the signed package (e.g. a JAR file in the case of Java based MExE classmarks) shall contain two files: the Administrator root public key and the CCM. + +Table 8: Allowed certificate types in signed packages + +| Signature on Package | Allowed Certificate types in package | +|----------------------|----------------------------------------------------| +| Administrator | Third Party | +| Manufacturer | Administrator, Manufacturer, Operator, Third Party | +| Operator | Administrator, Operator, Third Party | + +### 6.8.3 Installation of other signed data + +A signed package of proprietary binaries or Java classes such as native DSP code, provisioned functionality upgrades and patches, whose signature verifies as described in clause 6.6.2 "Manufacturer root public key" as belonging to the Manufacturer Domain may be installed. The use of such binaries is outside the scope of MExE, but the manufacturer shall be responsible for ensuring that the integrity of MExE is not compromised. + +Support of this feature is optional. + +## 6.9 Certificate Format + +### 6.9.1 Certificate extension for removal of network access + +MExE defines the certificate extension (attribute) "access-Restriction". If the access-Restriction extension is present in a certificate used to verify the signature on a trusted application or in any certificate in the certificate chain used to verify that signature, then the application shall not be permitted the capabilities listed under "network service access" in the security table, (table 5 "Security domains and actions"). This restriction applies irrespective of any user permission for network service access that may or may not be requested by the application and/or given by the user. + +The extension prevents the trusted applications of developers who do not need network service access from writing applications that can perform network service access. + +The support of this extension in the operator domain is mandatory. The support of this extension in the manufacturer and third party domains is optional. + +The extension is defined for X.509 version 3 only. Support for WTLS, X9.68 certificate formats is for further study. + +#### 6.9.1.1 X.509 version 3 + +The MExE certificate format as specified in clause 6.7.1.1 "MExE terminal requirements for certificate processing" shall support the X.509 version 3 access-Restriction extension. + +X509 version 3 provides a mechanism to define extensions. An Object identifier (OID) is defined for each private extension as defined in ITU-T Recommendation X509 [26]. The extension is defined to be within the ETSI Object Identifier (OID) name space. + +This extension shall apply irrespective of the presence or otherwise of any other X.509 key usage or extended key usage field. + +Normal use of the "critical" flag for extensions apply. That is, if this extension is marked as critical in the certificate used to verify the signature on the application or in any certificate in the chain used to verify the signature and this extension cannot be processed in the MExE device then the certificate shall be considered invalid. + +The syntax of the extension is defined in annex C "Access restriction certificate extension". + +## 6.10 Certificate management + +If the 3 MExE security domains defined in clause 6.1 "Generic security" are not supported, then the certificate management described in this clause is optional. The manufacturer may load initial third party certificates on the ME. Downloaded certificates shall be verified by an existing trusted certificate and placed in the domain defined by the root public key at the top of the verification chain for the downloaded certificate. + +The administrator root certificate shall be provided on the (U)SIM if support for certificate storage on the (U)SIM exists (e.g. MExE-(U)SIM) or in the MExE device. For (U)SIMs not having certificate storage the administrator root may be downloaded using the root download procedure described in clause 6.13.4 "Administrator root certificate download mechanism". + +The actions that may be performed for a given certificate are: + +- addition; +- deletion; +- mark un-trusted (un-trusted certificates cannot be used to verify applications or other certificates. This process may be preferred to certificate deletion as there is a chance that the certificate may become trusted again in the near future); +- mark trusted (marking as trusted is the process of allowing an untrusted certificate to come into use again); +- modify fine grain access permissions (proposed as a future enhancement). + +The ability to perform these actions depend on the certificate type being modified as well as the access level of the entity performing the operation. + +Users may add a third party certificate as long as it is certified by an existing trusted certificate. Using a provisioned functionality, users may delete Third Party certificates. + +The Administrator may mark trusted/untrusted Third-Party certificates using Certificate Configuration Messages (see clause 6.10.1 "Certificate configuration message (CCM)"). + +Users cannot add or delete any Operator or Manufacturer certificate containing a root public key. + +An example of public key infrastructure certificate management protocols can be found in RFC 2510 [33]. + +### 6.10.1 Certificate configuration message (CCM) + +If the 3 MExE security domains defined in clause 6.1 "Generic security" are not supported, then the certificate configuration message described in this clause is optional. + +The MExE device shall use the CCM to determine the third party certificates (and only the Third Party certificates) that are trusted for use on the MExE device. The CCM shall only be used to enable or disable third party certificates and can not be used to delete certificates. The CCM may be periodically fetched or downloaded to a MExE device by the Administrator to dynamically configure the third party list using the mechanisms defined in clause 6.10.1.4 "Authorised CCM download mechanisms". + +The Certificate Configuration Message shall be as shown in figure 8 "Format of a CCM". This message is essentially a simplified version of a certificate revocation list to satisfy a particular use case. More complex usage requires a full certificate revocation list. + +The MExE device may additionally support other means of enabling/disabling root certificates. + +![](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +| Bit | | | | | | | | Octet | +|--------------------------------------------------------------------|---|---|---|---|---|---|---|---------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| Version | | | | | | | | 0 | +| Certificate Advice | | | | | | | | 1 | +| Issue Timestamp | | | | | | | | 2 – 8 | +| . | | | | | | | | | +| . | | | | | | | | | +| Expiry Timestamp | | | | | | | | 9 – 15 | +| . | | | | | | | | | +| . | | | | | | | | | +| SignerInfo | | | | | | | | 16 | +| Listlength | | | | | | | | 17 – 18 | +| Fingerprint 1 Hashtype | | | | | | | | 19 | +| Hashvalue<br>(Variable length k according to hash type) | | | | | | | | 20 | +| . | | | | | | | | | +| . | | | | | | | | | +| Fingerprint 2 Hashtype | | | | | | | | k+20 | +| Hashvalue<br>(Variable length m according to hash type) | | | | | | | | | +| . | | | | | | | | | +| . | | | | | | | | | +| Fingerprint 3 Hashtype | | | | | | | | (k+20)+m+1 | +| Hashvalue<br>(Variable length) | | | | | | | | | +| . | | | | | | | | | +| . | | | | | | | | | +| Fingerprint n Hashtype | | | | | | | | etc. | +| Hashvalue<br>(Variable length) | | | | | | | | | +| . | | | | | | | | | +| . | | | | | | | | | +| CCM Signature Hashtype | | | | | | | | Listlength+19 | +| CCM signature<br>(Variable length according to CCM signature type) | | | | | | | | | + +**Figure 8: Format of a CCM** + +**Version** = The CCM format version is 0. All other values are reserved for future use. + +**Certificate Advice** = enumerated { enable all present and future Third Party certificates (0), disable all present and future Third Party certificates (1), enable present list only (2), enable CCM list (3), disable CCM list (4) }. All other values are reserved for future use. + +**Issue and Expiry Timestamps** = Fields used to identify the issue and expiry date of the CCM. The issue timestamp indicates a time before the current time of day (GMT) when a CCM message must be considered invalid. The expiry timestamp (GMT) identifies the time when a CCM is to be deemed no longer valid. The receiver shall use these parameters to detect a replay attack. A MExE device maintains information on the last valid CCM message received. A replay attack is an attacker replaying a previous valid CCM message to a MExE device in order to change the security settings. This is particularly dangerous for CCM messages used to enable certificates. Administrators should try and set the expiration time to be no longer than the next expected system update time of CCM information. CCM messages used to enable-all (rather than disable-all) certificates should be very short lived as the danger of these being used in a replay attack should be considered serious. + +The encoding of time (GMT) shall be coded as an OCTET SEQUENCE of seven octets in length as follows: + +| Octet 0 | 1 | 2 | 3 | 4 | 5 | Octet 6 | +|---------|-------|-----|------|--------|--------|---------| +| Year | Month | Day | Hour | Minute | Second | | + +| Element | Size (bits) | Range | +|-------------------|------------------------------------------------------------------------------------|---------------------------| +| Year | 16 | (0 – 65535) <sub>10</sub> | +| Month | 8 | (1 – 12) <sub>10</sub> | +| Day | 8 | (1 – 31) <sub>10</sub> | +| Hour | 8 | (0- 23) <sub>10</sub> | +| Minute | 8 | (0 – 59) <sub>10</sub> | +| Second (see note) | 8 | (0 – 60) <sub>10</sub> | +| NOTE: | The second field range includes the value 60 in order to accommodate leap seconds. | | + +For example, 1<sup>st</sup> January, 2001 00:00:30 would be encoded as: 07 d1 01 01 00 00 1E. + +**SignerInfo** = one octet indicating the type of signer information for this CCM. The only currently defined value is device-admin = 0. In this case, no further signer information follows as it is implicit. All other values are reserved for future use. + +**Listlength** = The total length of the fingerprint list not including the final CCM signature. Shall be zero when certificateAdvice = enable-all, disable-all or enable present list. + +**Hashtype** = enumerated { signature (0), MD5 (1), SHA-1 (2) } All other values are reserved for future use. + +The length of the Hashvalue field, number of octets output by the selected hash type, is 16 for MD5 [23] or 20 for SHA-1, ISO/IEC 10118-3 [24]. + +The list entries shall contain certificate *fingerprints* in the form of hashes of the encoded signed certificates. The full hash output for the specified algorithm shall be used to generate the fingerprint. A list generator shall check to insure that no two list entries match when creating a list. For an ITU-T Recommendation X.509v3 [26] or X9.68 (currently being drafted) certificate the fingerprint hash shall be computed over the ASN.1 encoded signed certificate object, first octet to last octet. For WTLS certificates the hash shall be computed over the signed WTLS certificate in network transmission format, first octet to last octet. + +The signature type and length shall be indicated by the administrator certificate, which shall be present on the MExE device. If no administrator certificate is on the MExE device or if the signature is not verified, the message shall be rejected. + +Upon receipt of a valid certificate configuration message the MExE device shall go through the third party certificate list, computing fingerprints if they are not stored with the certificate and enabling or disabling each certificate according to the following conditions: + +- certificateAdvice is enable-all      all Third Party certificates shall be enabled; +- certificateAdvice is disable-all      all Third Party certificates shall be disabled; + - certificateAdvice is enable present list only      enable all Third Party certificates currently on MExE device, do not enable any future certificates (this option allows the list to be frozen at time of manufacture) until Administrator changes; +- certificateAdvice is enable-list      if its fingerprint occurs in the CCM, it shall be enabled, otherwise it shall be disabled; +- certificateAdvice is disable-list      if its fingerprint occurs in the CCM, it shall be disabled, otherwise it shall be enabled. + +For future releases, the setting of fine grained permissions for each certificate is expected to be supported. + +An implementation shall keep track of the domain that authorised a given executable. If a CCM message is received while MExE executables are currently executing, the implementation shall check to ensure that any executables no longer in the Third Party domain, have their permissions re-configured appropriately and actions that are no longer permissible are terminated. + +#### 6.10.1.1 CCM numbering convention + +Bits are grouped into octets. The bits of an octet are shown horizontally and are numbered from 0 to 7. Multiple octets are shown vertically and are numbered from 0 to n. + +#### 6.10.1.2 CCM order of transmission + +Frames are transferred in units of octets, in ascending numerical octet order (i.e., octet 0, 1, ..., n-1, n). The order of bit transmission is specific to the underlying protocols used to transport the CCM. + +#### 6.10.1.3 CCM field mapping convention + +When a field is contained within a single octet, the lowest bit number of the field represents the lowest-order value. When a field spans more than one octet, the order of bit values within each octet progressively decreases as the octet number increases. In that part of the field contained in a given octet the lowest bit number represents the lowest-order value. + +For example, a 16 bit number can be represented as shown in figure 9 "Field mapping convention". + +| Bit | | | | | | | | | +|----------|----------|----------|----------|----------|----------|-------|-------|--------------------------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| $2^{15}$ | $2^{14}$ | $2^{13}$ | $2^{12}$ | $2^{11}$ | $2^{10}$ | $2^9$ | $2^8$ | 1 <sup>st</sup> Octet of field | +| $2^7$ | $2^6$ | $2^5$ | $2^4$ | $2^3$ | $2^2$ | $2^1$ | $2^0$ | 2 <sup>nd</sup> Octet of field | + +Figure 9: Field mapping convention + +#### 6.10.1.4 Authorised CCM download mechanisms + +The download of third party certificate lists by a remote administrator shall be performed by using a secure mechanism as defined below. The download mechanisms shall use HTTP over IP and/or the WAP Protocol. The URL from which the CCM is downloaded shall be in the administrator certificate if the CCM was not downloaded with the Administrator certificate. The format for storing the URL information with the certificate shall be as shown in figure 10 "CCM Message URL storage format": + +![Diagram showing the CCM Message URL storage format with four fields: Urltype, CharacterSet, UrlLength, and URL. The first three fields are single bytes, and the URL field is a variable-length string.](02db3d5ca2c08af069727d3709c4a6fb_img.jpg) + +| | | | | +|--|--|--|--| +| | | | | +|--|--|--|--| + +Diagram showing the CCM Message URL storage format with four fields: Urltype, CharacterSet, UrlLength, and URL. The first three fields are single bytes, and the URL field is a variable-length string. + +Figure 10: CCM Message URL storage format + +Urltype= one byte, enumerated {WAP (0), HTTP (1)}. All other values are reserved for future use. + +CharacterSet = one byte, Internet Assigned Numbers Authority assigned character set. + +UrlLength = one byte unsigned integer, length of the URL in octets. + +URL = a field where the format for storing the URL information in the certificate shall be defined as part of the enhanced administrator mechanism. + +When the administrator is changed, then the CCM shall also be changed. If there is URL information with the certificate as described in figure 10 "CCM Message URL storage format", then the new CCM shall be obtained using the URL. If the Administrator certificate was downloaded in a JAR file, the CCM shall be obtained from the same JAR file. + +## 6.11 Separation of I/O streams + +Support of the separation of I/O streams is mandatory. + +Except for the MExE Classmark 3 executables (MIDlets) from the same MIDlet Suite, there shall be strict separation of the user interface input and output streams between different MExE executables, i.e. it shall not be possible for one MExE executable to access the user interface input or output of another MExE executable. In particular, it shall not be + +possible for an untrusted MExE executable to access the user interface input and output destined for or proceeding from a trusted MExE executable. (This requirement is to prevent a long lived malicious MExE executable from eavesdropping upon or interfering with the user to MExE executables communications, for instance PINs, of a trusted MExE executable). + +## 6.12 Core software download + +Support of core software download is optional. + +Core software download enables the MExE device radio, characteristics and properties to be updated by changing the software in the MExE device. E.g. a new CODEC may be loaded into a MExE device, a new air interface, etc. This process could include the transfer of executable code and software patches over the air. + +This updating of core software (e.g. the Software Defined Radio (SDR) concept) can in principle be generically supported within the MExE framework by a MExE service that executes in the manufacturer security domain, and uses handset manufacturer proprietary APIs. Possible scenarios for the support of this functionality include: + +- A MExE service that can be transferred to, and executed in, the manufacturer domain. The service would use manufacturer APIs to perform the software update, radio re-configuration, etc. +- A core software download application that executes in the manufacturers' domain that acts like a user agent in conjunction with a server to transfer software as needed or requested by the user. The core software download application uses manufacturer APIs to perform the software update, radio re-configuration, etc. + +Similar functionality may be supported by a downloaded MExE service using manufacturer's OEM classes. All such OEM classes shall comply with the MExE security requirements in table 5 "Security domains and actions" and table 6 "Executable permissions for untrusted MExE executables". + +The support of core software download functionality in a MExE device shall only be under the control of the MExE device manufacturer. + +## 6.13 Administrator Concept + +### 6.13.1 Administrator root public key + +To help with the control of Third-Party certificates, the ME shall support secure storage for a certificate containing an administrator root public key. The ME shall support the use and management of a certificate containing an Administrator root public key stored on the MExE-(U)SIM and in the ME. The ME shall behave according to clause 6.13.3 "Determining the administrator of the MExE MS". For support of public key management on the SIM and the USIM refer to TS 51.011 [27] and TS 31.102 [39] respectively. + +A secure mechanism may be used to mark as valid/invalid a certificate containing the administrator root public key on the MExE device. It shall only be possible to use this mechanism to mark a certificate containing a new administrator root public key on the ME as valid, when all administrator root public keys are marked as invalid. + +There shall be no more than one valid administrator root public key on the MExE device at any one time. A valid administrator root public key on the (U)SIM shall always have precedence over any administrator root public key on the ME. Any administrator root public key(s) on the ME shall be marked invalid when a valid administrator root public key is present on the (U)SIM. + +The MExE device shall support the administrator designation mechanism explained in clause 6.13.2 "Provisioned mechanism for designating administrative responsibilities and adding third parties in a MExE device" and the secure downloading of CCMs explained in clause 6.10.1.4 "Authorised CCM download mechanisms". + +The user shall not be able to delete an administrator root public key or certificate. + +The system shall support a mechanism (as part of a provisioned functionality and/or inherently part of the MExE implementation) allowing the owner of the MExE device to manage the administrator root public key (including the download of a new administrator root public key) as defined in clause 6.13.3.2.1 "Administrator of the MExE device is the user". This mechanism shall be secure so that only the owner can use this functionality. + +The administrator root public key can be downloaded to the MExE device as described in clause 6.13.4 "Administrator root certificate download mechanism". + +If the Administrator root public key is stored in the (U)SIM, the ME shall only read the Administrator root public key from the MExE-(U)SIM when required and shall not store the Administrator root public key from the MExE-(U)SIM on the ME in a manner inconsistent with that detailed in clause 6.6.1.1 "Caching of root public keys". + +See clause 6.10 "Certificate management" for the management of Administrator root public keys. + +The same root public key may be used for both the Administrator role and the operator or manufacturer domain. This facility does not imply any increased right of the manufacturer or operator to take the Administrator role. + +If the same root public key is used for the operator domain and Administrator role and this root public key is stored on the MExE-(U)SIM (see TS 51.011 [27] and TS 31.102 [39]), there shall be separate entries relating to each use of the root public key in the operator and administrator trusted certificate directory files. These entries in the operator and Administrator trusted certificate directory files may point to the same root public key in the certificate data file. + +If the root public key to be shared is not stored on the (U)SIM, then procedures relating to this are out of the scope of this specification. + +### 6.13.2 Provisioned mechanism for designating administrative responsibilities and adding third parties in a MExE device + +If the 3 MExE security domains defined in clause 6.1 "Generic security" are not supported, then the administrator concept described in this clause is optional. + +All applications in the Third-Party security domain are to be signed by a key which shall be verified back to a Third Party root public key on the MExE device. The Third Party root public keys shall be managed (e.g. addition/mark trusted/mark untrusted) by an administrator that is designated by the owner of the MExE device using the MExE administrator provisioning mechanism. A mechanism is required to be provided to enable the owner of the MExE device to dynamically assign an administrator. The mechanism shall support the following cases: + +- the user is the owner; +- the owner is at a remote location. In this case the owner could be the operator, a service provider or a third party; +- the owner of the MExE-(U)SIM wants to be a temporary administrator. + +### 6.13.3 MExE administrator determination mechanism + +The administrator of the MExE device shall be determined by a two part logical process with the first part shown in the flowchart in figure 11 "MExE administrator determination mechanism". The second part of the logical process is in figure 12 "MExE administrator determination mechanism, for MExE-(U)SIM supporting third party certificates". + +During power-up or MExE-(U)SIM insertion event, the provisioned mechanism shall look for an administrator root public key that is stored on the MExE-(U)SIM. + +#### 6.13.3.1 Determining the administrator of the MExE device + +If an administrator root public key cannot be found on the MExE-(U)SIM, the provisioned mechanism shall look for one on the MExE device. This leads to the following two cases: + +- administrator root public key is absent + - if the administrator root public key is absent, then the user shall automatically become the administrator of the MExE device. +- administrator root public key is present + - if an administrator root public key is present, this root public key shall be used for all remote administration authentication, implying that the owner of the administrator root public key is the administrator. Note that the owner of the administrator root public key could be the user. + +![Flowchart of the MExE administrator determination mechanism. The process starts with 'MExE administrator determination mechanism'. It then checks 'Is the administrator root public key in the MExE-(U)SIM?'. If 'Yes', the result is 'Owner of the administrator root public key is the Administrator'. If 'No', it checks 'Is the administrator root public key in the MExE device?'. If 'Yes', the result is 'Owner of the administrator root public key is the Administrator'. If 'No', the result is 'User acts as the Administrator'.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` + +graph TD + Start[MExE administrator determination mechanism] --> Q1{Is the administrator root public key in the MExE-(U)SIM?} + Q1 -- Yes --> A1([Owner of the administrator root public key is the Administrator]) + Q1 -- No --> Q2{Is the administrator root public key in the MExE device?} + Q2 -- Yes --> A1 + Q2 -- No --> A2([User acts as the Administrator]) + +``` + +Flowchart of the MExE administrator determination mechanism. The process starts with 'MExE administrator determination mechanism'. It then checks 'Is the administrator root public key in the MExE-(U)SIM?'. If 'Yes', the result is 'Owner of the administrator root public key is the Administrator'. If 'No', it checks 'Is the administrator root public key in the MExE device?'. If 'Yes', the result is 'Owner of the administrator root public key is the Administrator'. If 'No', the result is 'User acts as the Administrator'. + +**Figure 11: MExE administrator determination mechanism** + +#### 6.13.3.2 Determining the administrator of the MExE device, for MExE-(U)SIM supporting third party certificates + +The second part of the administrator determination mechanism is subsequently defined (see figure 12 "MExE administrator mechanism, for MExE-(U)SIM supporting third party certificates "), and shall be initiated after a power-up or MExE-(U)SIM insertion event is processed. + +The following clauses 6.13.3.2.1 "Administrator of the MExE device is the user" and 6.13.3.2.2 "Administrator of the MExE device is not the user" assume that Third Party certificates can be added using the MExE-(U)SIM, however Third Party certificates may be added using a non-(U)SIM approach (e.g. inserted at the time of manufacture, signed package download etc.). + +##### 6.13.3.2.1 Administrator of the MExE device is the user + +If the administrator is the user, then a check shall be made to determine whether there is a MExE-(U)SIM. If a MExE-(U)SIM is present, then a check shall then be made to determine whether there is a Third Party or an Administrator certificate containing a root public key in the MExE-(U)SIM. The second part of the administrator determination mechanism shall allow the MExE device to determine (via a format) what type of certificate is present: + +- certificate present - third party (CP-TP) + +If a Third Party certificate containing a root public key is present in the MExE-(U)SIM then this certificate shall be considered by the MExE device as a Third Party certificate, whilst that valid MExE-(U)SIM application is present in the MExE device. The user shall be queried to allow or disallow the certificate as a Third Party. + +- certificate present - administrator (CP-Admin) + +If a temporary Administrator certificate containing a root public key is present in the MExE-(U)SIM, the user shall be queried whether to allow the certificate on the MExE-(U)SIM to take temporary control of the third party domain. By temporary control, it is meant that once the card is removed the administrator reverts back to the user administrator settings (i.e. the Administrator becomes the User). The above mechanism implies that the previous configuration settings for the administrator shall be saved, so that they may be restored. If the user + +disallows the MExE-(U)SIM certificate, the Third Party Domain shall not be able to use any of the network capabilities in the third party domain as identified in the network access section of the security table 5 "Security domains and actions". + +If an administrator certificate is not present on the MExE-(U)SIM and the administrator is the user, the user shall continue to be the administrator and may make use of all functionality. + +##### 6.13.3.2.2 Administrator of the MExE device is not the user + +If the administrator is not the user, then a check is made to determine if there is a MExE-(U)SIM. If a MExE-(U)SIM is present, then a check is made to see if there is a Third Party or an Administrator certificate containing a root public key in the MExE-(U)SIM. + +If an Administrator certificate containing a root public key is present in the MExE-(U)SIM, then a comparison is made of this certificate's root public key with the Administrator root public key on the MExE device for the following cases: + +- Case (a): they are the same; +- Case (b): they are not the same, but the MExE device certificate is cross-certified with the MExE-(U)SIM certificate (a cross-certificate exists on the MExE device); +- Case (c): they are not the same, but the MExE device certificate has a line of trust back to the MExE-(U)SIM certificate domain; +- Case (d): they are not the same. + +If the owner of the public key in the certificate on the MExE-(U)SIM is to be a temporary administrator (CP-Admin), then in cases (a), (b) and (c), the temporary administrator shall be the owner of the CP-Admin root public key. In case (d), the Third Party domain shall not use any of the network capabilities in the third party domain as identified in the network access section of the security table 5 "Security domains and actions". + +If the certificate is to be a Third Party certificate containing a root public key, then the certificate (CP-TP) shall be verified with the CCM and based on the content and permissions of the CCM, the certificate shall be added to the Third Party list or rejected. + +![Flowchart of MExE administrator determination mechanism. The process starts with 'Is user the administrator?'. If Yes, it checks 'Is certificate on MExE (U)SIM?'. If No, 'User is the administrator'. If Yes, it checks 'Certificate type?'. If CP-TP, it checks 'Query user: Add CP-TP to TP?'. If No, 'User is the administrator, but TP loses network access'. If Yes, it checks 'Query user: User wishes temporary CP-Admin?'. If Yes, 'CP-Admin certificate owner is temporary administrator.' (Cases (a), (b), (c)). If No, it checks 'Check with administrator certificate' (Case (d)). If Yes, 'Current administrator is retained'. If No, it checks 'Check with CCM to add/disallow to TP list'. If Yes, 'Current administrator is retained'. If No, 'Current administrator retained, but TP loses network access'. If 'Is user the administrator?' is No, it checks 'Is certificate on MExE (U)SIM?'. If Yes, it checks 'Certificate type?'. If CP-TP, it checks 'Query user: Add CP-TP to TP?'. If No, 'User is the administrator, but TP loses network access'. If Yes, it checks 'Query user: User wishes temporary CP-Admin?'. If Yes, 'CP-Admin certificate owner is temporary administrator.' (Cases (a), (b), (c)). If No, it checks 'Check with administrator certificate' (Case (d)). If Yes, 'Current administrator is retained'. If No, it checks 'Check with CCM to add/disallow to TP list'. If Yes, 'Current administrator is retained'. If No, 'Current administrator retained, but TP loses network access'. If 'Is certificate on MExE (U)SIM?' is No, 'Current administrator is retained'.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +**MExE administrator determination mechanism, for MExE-(U)SIM supporting third party certificates** + +``` + +graph TD + Start[MExE administrator determination mechanism, for MExE-(U)SIM supporting third party certificates] --> Q1{Is user the administrator?} + Q1 -- Yes --> Q2{Is certificate on MExE (U)SIM?} + Q1 -- No --> Q3{Is certificate on MExE (U)SIM?} + Q2 -- No --> A1([User is the administrator]) + Q2 -- Yes --> Q4{Certificate type?} + Q4 -- CP-TP --> Q5{Query user: Add CP-TP to TP?} + Q4 -- CP-Admin --> Q6{Query user: User wishes temporary CP-Admin?} + Q5 -- No --> A2([User is the administrator, but TP loses network access]) + Q5 -- Yes --> Q6 + Q6 -- Yes --> A3([CP-Admin certificate owner is temporary administrator. Cases (a), (b), (c)]) + Q6 -- No --> Q7{Check with administrator certificate Case (d)} + Q7 -- Yes --> A4([Current administrator is retained]) + Q7 -- No --> Q8{Check with CCM to add/disallow to TP list} + Q8 -- Yes --> A4 + Q8 -- No --> A5([Current administrator retained, but TP loses network access]) + Q3 -- No --> A4 + Q3 -- Yes --> Q9{Certificate type?} + Q9 -- CP-TP --> Q5 + Q9 -- CP-Admin --> Q6 + Q9 -- CP-Admin --> Q7 + Q9 -- CP-TP --> Q5 + +``` + +Flowchart of MExE administrator determination mechanism. The process starts with 'Is user the administrator?'. If Yes, it checks 'Is certificate on MExE (U)SIM?'. If No, 'User is the administrator'. If Yes, it checks 'Certificate type?'. If CP-TP, it checks 'Query user: Add CP-TP to TP?'. If No, 'User is the administrator, but TP loses network access'. If Yes, it checks 'Query user: User wishes temporary CP-Admin?'. If Yes, 'CP-Admin certificate owner is temporary administrator.' (Cases (a), (b), (c)). If No, it checks 'Check with administrator certificate' (Case (d)). If Yes, 'Current administrator is retained'. If No, it checks 'Check with CCM to add/disallow to TP list'. If Yes, 'Current administrator is retained'. If No, 'Current administrator retained, but TP loses network access'. If 'Is user the administrator?' is No, it checks 'Is certificate on MExE (U)SIM?'. If Yes, it checks 'Certificate type?'. If CP-TP, it checks 'Query user: Add CP-TP to TP?'. If No, 'User is the administrator, but TP loses network access'. If Yes, it checks 'Query user: User wishes temporary CP-Admin?'. If Yes, 'CP-Admin certificate owner is temporary administrator.' (Cases (a), (b), (c)). If No, it checks 'Check with administrator certificate' (Case (d)). If Yes, 'Current administrator is retained'. If No, it checks 'Check with CCM to add/disallow to TP list'. If Yes, 'Current administrator is retained'. If No, 'Current administrator retained, but TP loses network access'. If 'Is certificate on MExE (U)SIM?' is No, 'Current administrator is retained'. + +**Figure 12: MExE administrator determination mechanism, for MExE-(U)SIM supporting third party certificates** + +### 6.13.4 Administrator root certificate download mechanism + +MExE devices supporting (U)SIMs without certificates shall at least support the following procedure to download the administrator root certificate. + +1. Upon sign-up with an administrator the user and administrator will make contact. +2. The administrator service centre will obtain any required information from the user and inform the user by SMS or other means of the location of the administrator root certificate. +3. The user will initiate the download of the Administrator root certificate using a signed package. +4. Once the procedure is complete the MExE device shall compute the hash of the received Administrator certificate containing root public key. +5. The user will contact the administrator and enters on the MExE device at least the first 8 bytes using decimal value of the hash of the Administrator root public key information provided by the administrator. The MExE device compares the beginning of computed hash value and the abbreviated hash value entered by the user. If these two values are the same, the provisioning process will be complete. If the two values are different this shall be indicated to the user who should inform the administrator of this. + +Alternative methods to download an administrator root certificate may be used where appropriate but must insure that the certificate is received by the MExE device unaltered. + +# --- 7 MExE Classmark 1 (WAP environment) + +## 7.1 Introduction + +Classmark 1 MExE devices are based on Wireless Application protocol (WAP). + +The Wireless Application Protocol is a standard to present and deliver wireless information and telephony services on mobile phones as well as other wireless terminals. Supporting mandatory features of WAP, WAP enabled devices provide access to the World Wide Web based content for small mobile devices. + +### 7.1.1 WAP MExE devices + +Support of WAP in a MExE classmark 1 device as detailed in this clause is mandatory. + +WAP MExE devices shall be based on the WAP specifications [6]. In addition to the base specifications in [6], further developments made in the WAP specifications shall form part of this MExE specification. + +WAP MExE devices shall implement the WAP version as specified in reference [6], or a later version, under the condition that the version of WAP is backward compatible with the version specified in reference [6]. + +The existing WAP specification covers security, creation and transfer of WAP executables and content, access, and execution. + +### 7.1.2 High level architecture + +The WAP architecture provides a scalable and extensible environment for application development for mobile communication devices. This is achieved through a layered design of the entire protocol stack. + +The key features of WAP include: + +- Markup language (WML) and a script language (WMLScript) designed to create applications on the small displays of handheld devices. WML does not assume that a QWERTY keyboard or a mouse is available for user input. Unlike the flat structure of HTML documents, WML documents are divided into a set of well defined units of user interactions. One unit of interaction is called a card, and services are created by letting the user navigate back and forth between cards from one or several WML documents. WML has a smaller set of markup tags that makes it more appropriate to implement in handheld devices, than, say, HTML. +- Light-weight protocol stack to minimise the required bandwidth and to guarantee that a maximum number of wireless network types can run WAP applications. For example, GSM SMS/USSD, circuit switched data (CSD), and GPRS. +- A framework for Wireless Telephony Applications (WTA) allows access to telephony functionality such as call control, phone book and messaging from within WMLScript scripts. This allows operators to develop telephony applications integrated into WML/WMLScript services. + +Since WAP is based on a scalable layered architecture, each layer can develop independently of the others. This makes it possible to switch onto new bearers, to use new transport protocols, without major changes in the other layers. + +## 7.2 Non Security + +### 7.2.1 WAP components + +Mandatory and optional components of WAP are specified in the WAP specifications. Services and applications shall be able to determine the presence of optional parts of the functionality. + +### 7.2.2 Services + +WAP is a general purpose application based on World Wide Web (WWW) technologies and philosophies. Many services can be provided to both WAP clients and traditional WWW clients, from the same server. Services are created based on the same information space. The major difference is the user interface. The user interface of WAP services is realised by the Wireless Markup Language, WML [6], and has a menu tree oriented structure, instead of the traditional flat structure of HTML pages. + +Typical WAP services provided to mobile phones may include (this list is not exhaustive): + +- | | | +|-----------------------|---------------------------------| +| – News | – Telephony Services | +| – Weather information | – Time Tables | +| – Package Tracking | – Access to corporate databases | +| – Stocks | – Sports | + +#### 7.2.2.1 User interface + +The user interface of WAP services is realised by the Wireless Markup Language, WML [6]. WML does not define the user interface itself, the implementation of the browser defines how the WML data is presented to the user (e.g. hyperlinks are blue and underlined). The script language, WMLScript [6], may be used to enhance the standard browsing and presentation facilities of WML with behavioural capabilities, and to access the device and its peripheral functionality. + +#### 7.2.2.2 Access points + +Services may be hosted on standard HTTP servers and can be created with proven technologies; CGI, Java Servlets. URLs are used to address services. + +The WAP network topology is shown in figure 13 "WAP network topology". + +![Figure 13: WAP network topology diagram showing the flow from WAP Client(s) through a WAP Gateway to an HTTP/1.1 Server and other network nodes.](42c65f5cb106938992fc73c05c8713d2_img.jpg) + +The diagram illustrates the WAP network topology. At the bottom left, two mobile phones labeled 'WAP Client(s)' are shown. One phone has a speech bubble containing 'WML'. A dashed line labeled 'GSM network' connects these clients to a 'WAP Gateway' (represented by a server icon). Above the WAP Gateway, a solid line labeled 'Internet/intranet' connects it to an 'HTTP/1.1 Server' (another server icon). To the left of the HTTP/1.1 Server, a box labeled 'Programs for Interaction & Dynamic content' is connected to it. This box is further connected to 'Databases Interfaces' (represented by a cylinder icon). Above the Internet/intranet line, three server icons are labeled 'Other Servers (e.g. proxies, firewalls)'. Below the WAP Gateway, three more server icons are labeled 'Other Network Nodes (e.g SMS-C)'. + +Figure 13: WAP network topology diagram showing the flow from WAP Client(s) through a WAP Gateway to an HTTP/1.1 Server and other network nodes. + +**Figure 13: WAP network topology** + +Mobile phones access services by sending a request with a URI to the WAP gateway. The URI is used to identify the origin server on which the service is available. The request is sent from the mobile phone by the WAP protocols over one of the available bearer networks. The WAP Gateway is a WAP to HTTP/1.1 proxy that translates the WAP request into an HTTP/1.1 request (from binary form to text). The HTTP/1.1 request is passed on to the server identified by the URI. + +The HTTP server may have multiple access points to various databases and other services available in the infrastructure network. Once the request has been serviced a response is sent back to the WAP Gateway, which in turn translates it into a WAP response (from text to binary form) and sends it down to the mobile phone. + +Note that WAP does not specify anything "behind" the WAP Gateway. However it is assumed that the origin server is an HTTP/1.1 server, and that the WAP Gateway has access to the TCP/IP network on which the origin server is hosted. + +#### 7.2.2.3 Transferring + +The core of WSP [6] is a binary version of the Hypertext Transfer Protocol - HTTP/1.1 [9]. The core function of WSP is the same as for HTTP/1.1. A client sends a request to the server using an appropriate request method with a URI and information about the client. The server responds with a status code and possibly (if success) the requested content. + +There is a differentiation between an origin server and a WSP server. The origin server is where the content is stored, and the WSP server is where the WSP session terminates. The WSP server is also typically the WAP gateway. + +In addition to the basic HTTP/1.1 function, WSP has some functions that can not be found in HTTP/1.1, they are: + +- Session Establishment and Management +Before a request is sent, the WSP client can establish a session with the server. During session establishment the client and server exchange static headers. The header are cached for the duration of the session, thus they need to be sent in every single request within the session. Static headers may be: Accept headers, User-agent header, etc. In addition, capabilities such as supported optional protocol functions, the maximum service data unit the protocol can handle, the maximum number of simultaneously outstanding requests, supported header code pages, etc. can also be exchanged during session establishment. +- Header encoding +WSP is using a compact binary header encoding to minimise the number of bytes sent over the air. +- Asynchronous transactions +WSP allows for multiple asynchronous transactions, that is, unordered transactions. +- Transaction Abort +WSP support abortion of an outstanding transaction. +- Datagram transport +WSP together with the helper protocol Wireless Transaction Protocol, WTP [9], can run over a datagram transport such as SMS or UDP. The WDP can also be used for non-IP bearers. +- Push +WSP supports the push of data from server to client. This can be done within and outside of a session. It can be done with and without acknowledgement from the client. Push of indications down to mobile phones is an essential function many wireless applications. + +##### 7.2.2.3.1 WSP and HTTP/1.1 Proxy Function + +The WAP Architecture is a client-proxy-server architecture. The client is typically a mobile phone, the data gateway is the WAP Gateway and the server is the origin server (a standard HTTP server). The WAP Gateway translates the binary WSP header into text formatted HTTP/1.1 headers and passes them on to the origin server. In the opposite direction the WAP Gateway translates the text formatted HTTP/1.1 header into binary WSP headers. If the WAP Gateway receives a header it does not recognise it simply passes it on as an unknown header. Unknown headers that are not part of the WSP Header Code page or Extended code pages (negotiated at session establishment) are sent in plain text for the client to interpret as best it can. + +### 7.2.3 WAP charging support + +The WAP protocol suite in [6], with upgrades as identified in this specification, does not specify mechanisms for charging (e.g. charging records) or subscription management. WAP is bearer independent and is running as an application on top of the bearer network. However the WAP architecture suggests that appropriate charging information can be collected in the WAP Gateway; the point of convergence for all WAP traffic. + +The WAP security protocol can be used for authentication of the subscriber. + +### 7.2.4 CC/PP over WSP (Classmark 1) + +In Classmark 1, according to the WAP User Agent Profile Specification [17], the CC/PP description is encoded with WBXML [45] after which it is carried over by WSP [17]. + +## 7.3 Security + +### 7.3.1 Call control + +WAP telephony services are written in WML and WMLScript. The WAP Telephony API (WTAI) exposes telephony functions to service authors as a set of libraries. The WTAI function libraries can be accessed from WML as URIs, and from WMLScript as script functions. The following libraries have been specified: + +- Public library +This includes functions that are available in all networks, and can be provided by any third party service provider; and not only the network operator. The user must acknowledge the function before it is carried out. Functions have been specified, which can be used e.g. to initiate a mobile originated call, send DTMF tones and add phonebook entry. +- Network Common library +This includes functions that are available in all networks, and can be provided only by the network operator. E.g. functions for advanced call control, accessing the phonebook, and sending and reading network text (SMS) have been specified. +- Network Specific library +Functions that are only available in certain types of networks, and can be provided only by the network operator. For GSM, e.g. functions for call reject, call hold, call transfer, multiparty, getting location information and sending USSD have been specified. + +The WML and WMLScript author uses the WTAI libraries to create web services for mobile phones with telephony capabilities. + +Call control shall be performed using WTA. + +### 7.3.2 Local phonebook + +WAP Telephony API (WTAI) is used to access the information stored in the phonebook on the MExE device or the (U)SIM. Phonebook entries consist of name, number and identity. Phonebook entries can be read, written, deleted, and searched for. + +# --- 8 MExE Classmark 2 (PersonalJava environment) + +## 8.1 Introduction + +Classmark 2 specifies Personal Java enabled devices with the addition of the JavaPhone API. + +The Personal Java [3] application environment is the standard Java environment optimised for consumer electronic devices designed to support World Wide Web content including Java applets. The Personal Java API is a feature level subset of J2SE with some Java packages optional and some API modifications necessary for the needs of small portable devices (for example an optimised version of the Abstract Windowing Toolkit targeted to small displays). + +JavaPhone [4] is a vertical extension to the Personal Java platform that defines APIs for telephony control, messaging, address book and calendar information, etc. + +### 8.1.1 Classmark 2 MExE devices + +Support of PersonalJava in a MExE classmark 2 device as detailed in this clause is mandatory. + +MExE Classmark 2 devices shall be based on the API for Personal Java, which defines the required and optional components of Personal Java /JavaPhone APIs that shall be used to realise a Classmark 2 compliant MExE device. + +The APIs primarily define the functions available to a Personal Java based MExE device such that services (specified in the form of Java classes and interfaces) can control such a MExE device in a standardised way. + +Many aspects of the MExE Classmark 2 API specification are optional. Services and applications shall be able to determine the presence of optional parts of the functionality. When optional parts of the functionality are implemented, the API shall be supported. + +### 8.1.2 High level architecture + +![Figure 14: Basic functional architecture of a PersonalJava MExE device. The diagram shows a hierarchical structure of APIs. At the top is 'MExE Applications'. Below it is a dashed line labeled 'MExE API'. Below that is a box for 'Optional Java APIs'. Below that is a dashed line labeled 'JavaPhone API'. Below that is a box split into 'Optional JavaPhone APIs' and 'Required JavaPhone APIs'. Below that is a dashed line labeled 'Personal Java API'. At the bottom is a box split into 'Optional PersonalJava APIs' and 'Required PersonalJava APIs'. Arrows indicate the flow from MExE Applications down through the various API layers to the final PersonalJava APIs.](efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg) + +Figure 14: Basic functional architecture of a PersonalJava MExE device. The diagram shows a hierarchical structure of APIs. At the top is 'MExE Applications'. Below it is a dashed line labeled 'MExE API'. Below that is a box for 'Optional Java APIs'. Below that is a dashed line labeled 'JavaPhone API'. Below that is a box split into 'Optional JavaPhone APIs' and 'Required JavaPhone APIs'. Below that is a dashed line labeled 'Personal Java API'. At the bottom is a box split into 'Optional PersonalJava APIs' and 'Required PersonalJava APIs'. Arrows indicate the flow from MExE Applications down through the various API layers to the final PersonalJava APIs. + +Figure 14: Basic functional architecture of a PersonalJava MExE device + +The functional architecture of a Java MExE classmark 2 device is shown in figure 14 "Basic functional architecture of a PersonalJava MExE device". Java applets, applications, and services access functionality via the MExE PersonalJava API. The MExE PersonalJava API is based on a combination of optional Java APIs and the Wireless Profile of the JavaPhone API [4]. The JavaPhone API is based on the PersonalJava API [3]. + +## 8.2 Non Security + +### 8.2.1 High level functions + +#### 8.2.1.1 Optional Java packages + +The use of Java encourages development of modular interfaces and minimal required functionality. Additional functionality is provided by optional APIs specified in terms of the Java language. Java packages are containers for the highest level of functionality in the Java language. In some cases, optional Java packages are specified in terms of Java classes and interfaces. Classes and interfaces are elements contained inside packages. + +The following table 9 "Optional Java packages of the Wireless Profile of the JavaPhone APIs" specifies the defined optional Java packages of the Wireless Profile of the JavaPhone APIs [4]. Within some of the packages, certain classes and methods may be individually specified as optional by the JavaPhone API specification. + +Where a mandatory package is identified, it is implicit that any packages called by that mandatory package are also mandatory. + +**Table 9: Optional Java packages of the Wireless Profile of the JavaPhone APIs** + +| <b>JavaPhone API</b> | <b>Java package</b> | <b>Optional/Mandatory</b> | +|-----------------------------------------|------------------------------------------|---------------------------| +| Addressbook | Javax.pim.addressbook | Mandatory | +| User Profile | Javax.pim.userprofile | Mandatory | +| Calendar | Javax.pim.calendar | Mandatory | +| Network | Java.net | Mandatory | +| Datagram | Javax.net.datagram | Mandatory | +| Power Monitor | Javax.power.monitor | Mandatory | +| Power Management | Javax.power.management | Optional | +| Install | Javax.install | Optional | +| Communications | Java.comm | Optional | +| SSL | Javax.net.ssl | Optional | +| JTAPI Core Package | Javax.telephony | Mandatory | +| JTAPI Core Capabilities Package | Javax.telephony.capabilities | Mandatory | +| JTAPI Core Events Package | Javax.telephony.events | Mandatory | +| JTAPI Call Control Package | Javax.telephony.callcontrol | Optional | +| JTAPI Call Control Capabilities Package | Javax.telephony.callcontrol.capabilities | Optional | +| JTAPI Call Control Events Package | Javax.telephony.callcontrol.events | Optional | +| JTAPI Phone Package | Javax.telephony.phone | Optional | +| JTAPI Phone Capabilities Package | Javax.telephony.phone.capabilities | Optional | +| JTAPI Phone Events Package | Javax.telephony.phone.events | Optional | +| JTAPI Mobile Package | Javax.telephony.mobile | Mandatory | +| | Java.math | Optional | +| | Java.rmi | Optional | +| | Java.rmi.dgc | Optional | +| | Java.rmi.registry | Optional | +| | Java.rmi.server | Optional | +| | Java.security | Optional | +| | Java.security.interfaces | Optional | +| | Java.sql | Optional | +| | Java.io | Optional | + +#### 8.2.1.2 Required and optional PersonalJava APIs + +MExE classmark 2 devices shall support the PersonalJava specification [3]. The PersonalJava APIs provide a standardised and readily implementable execution environment as a means for applications, applets, and content: + +- to access and personalise the user interface via the java.awt packages; +- to utilise both Internet and Intranet connections via the java.net package. + +#### 8.2.1.3 Required and optional JavaPhone APIs + +The JavaPhone APIs extend the PersonalJava APIs to provide functionality unique to telephony devices. MExE classmark 2 devices shall support the Wireless Profile of the JavaPhone API specification [4]. MExE classmark 2 devices shall support all APIs specified as required by the Wireless Profile in the JavaPhone API specification. All APIs that are optional in the Wireless Profile shall be optional in MExE classmark 2 devices. + +##### 8.2.1.3.1 Application installation + +MExE classmark 2 devices shall support the following JAR file manifest entries (as described in the JavaPhone specification) as described below: + +###### - Implementation-Title + +the Implementation-Title shall be used in any textual description of the application which is displayed in the UI element used to launch the application. E.g. the text displayed with an icon. + +###### - Main-Icon + +the use of icons to launch applications is optional, however if icons are used as elements to launch the application, then the icon file within the JAR file named by the Main-Icon attribute shall be displayed, and may be scaled if desired. + +###### - Main-Class and Class-Path + +when the application is launched, the MExE Java VM shall be supplied with the classpath and shall call the main() method in the class named by the Main-Class attribute. + +##### 8.2.1.3.2 Power + +MExE classmark 2 devices shall support the Power Monitor package (javax.power.monitor) as specified by the JavaPhone API to access the power level of the MExE device and receive notifications concerning changes in power states. + +Note that the Power Monitor package does not specify the minimum required events that should be generated under certain circumstances. MExE classmark 2 device shall at least implement the following event generation: + +###### - BatteryCritical + +shall be generated when the battery is at a critically low level. + +###### - BatteryNormal + +shall be generated when the battery is no longer low. + +All the other event generation should be supported by the implementation. + +##### 8.2.1.3.3 Datagram recipient addressing + +The syntax described in Concrete Addressing [4] specifies the format to be used for raw text-only GSM SMS messages, UDP datagram via IP, and WAP datagram via GSM SMS message(s). + +As a minimum, the formats above shall be supported if the MExE device supports the relevant bearer/transport combination. + +NOTE: For the purposes of this clause, "GSM SMS" means SMS as defined by the 3GPP specifications including 3GPP TS 23.040. + +#### 8.2.1.4 Required and optional MExE PersonalJava APIs + +MExE classmark 2 devices shall not be required to support any other Java APIs. + +MExE classmark 2 devices may optionally support any other Java APIs which comply with the MExE security requirements in table 5 "Security domains and actions", such as: + +- OCF SmartCard API OpenCard, available from [21]. If the MExE device supports smartcards other than the (U)SIM, and the smartcard is open to 3<sup>rd</sup> party applications, then the opencard.core.terminal section of the OpenCard API may be used to access the card. + +#### 8.2.1.5 Mandated services and applications + +##### 8.2.1.5.1 Network protocol support + +Support for network protocols in MExE classmark 2 devices is specified in the following table 10 "Support for network protocols": + +**Table 10: Support for network protocols** + +| Protocol | Optional/Mandatory | +|--------------|--------------------| +| HTTP/1.1 [9] | Mandatory | +| HTTPS | Mandatory | +| Gopher | Optional | +| ftp | Optional | +| mailto [25] | Mandatory | +| File | Optional | + +### 8.2.2 CC/PP over HTTP (Classmark 2) + +In Classmark 2 the CC/PP is carried over by using CC/PP over HTTP [15] and optionally CC/PP over WSP [17]. + +### 8.2.3 Java charging support + +MExE Java devices do not require any additional specific charging (e.g. charging records) or subscription management. Java usage of network resources is bearer independent and runs as applications on top of the bearer network. + +## 8.3 Security + +If the 3 MExE security domains defined in clause 6.1 "Generic security" are not supported, then the Java security described in this clause is optional. + +### 8.3.1 PersonalJava security + +There are two types of Java security [20]: sandbox, and fine grain. + +The sandbox model [18] has just one domain; there is no concept of a *partly trusted* domain. The sandbox meaning of "trusted" means it is totally unrestricted to access all system resources. + +Using the sandbox system, each MExE security domain shall be implemented as running in a sandbox, configured with different privileges corresponding to those of the domain. If the security domains are not supported then the Java sandbox security model shall be supported and it shall be configured for untrusted MExE executables support only, as defined in clause 6.3 "MExE executable permissions". Using the fine grain Java security system [19], each MExE security domain will be a set of constraints within which a Java fine grain security domain can be configured. + +#### 8.3.1.1 Java applet certification in PersonalJava + +Support for trusted applets is optional. Although a Java application shall be executed in a trusted domain if its certification can be validated, a Java Applet will not necessarily be executed in a trusted domain even if it does have a valid signature. It will be up to the implementers to decide if "trusted" Applets will be supported. (In certain implementations, all Applets may be always executed as "untrusted".) + +#### 8.3.1.2 Java application signature verification in PersonalJava + +The verification of the certification of the application or applet shall be performed as described in clause 6.6 "Root Public keys" and clause 6.13.2 "Provisioned mechanism for designating administrative responsibilities and adding third parties in a MExE MS". + +#### 8.3.1.3 Java loading native libraries in PersonalJava + +The MExE Java VM may be able to load native libraries that are intrinsically part of the MExE device implementation and MExE native libraries. The MExE Java VM shall not load other native libraries. + +### 8.3.2 Installing MExE native libraries + +A signed native library whose signature verifies as described in clause 6.6.2 "Manufacturer root public key" as belonging to the Manufacturer Domain may be installed as a "MExE native library". + +A MExE native library may be called by a MExE executable, and shall not compromise the MExE security system. + +Support of MExE native library signed package installation is optional. + +# --- 9 MExE Classmark 3 (J2ME CLDC environment) + +## 9.1 Introduction + +Classmark 3 MExE devices are based on the Connected Limited Device Configuration (CLDC) with the Mobile Information Device Profile (MIDP). + +Java 2 Micro Edition (J2ME) is a version of the Java 2 platform targeted at consumer electronics and embedded devices. CLDC consists of a virtual machine and a set of APIs suitable for providing tailored runtime environments. The J2ME CLDC is targeted at resource constrained connected devices (e.g. memory size, processor speed etc.). + +### 9.1.1 Classmark 3 MExE devices + +Support of CLDC/MIDP in a MExE classmark 3 device as detailed in this clause is mandatory. + +MExE Classmark 3 devices are based on the J2ME Connected Limited Device Configuration (CLDC) with the Mobile Information Device Profile (MIDP). + +All APIs defined by CLDC and MIDP shall be supported by a MExE classmark 3 device. + +### 9.1.2 High level architecture + +![Figure 15: Functional architecture of a Classmark 3 MExE device. The diagram shows four stacked layers: MExE Applications at the top, followed by OEM APIs, then MIDP APIs, and CLDC APIs at the bottom. Arrows indicate that MExE Applications can access all three layers below it. OEM APIs can access MIDP APIs and CLDC APIs. MIDP APIs can access CLDC APIs.](86f2406a1f65ffd689d0796f95fe7588_img.jpg) + +``` +graph TD; A[MExE Applications] --> B[OEM APIs]; A --> C[MIDP APIs]; A --> D[CLDC APIs]; B --> C; B --> D; C --> D; +``` + +Figure 15: Functional architecture of a Classmark 3 MExE device. The diagram shows four stacked layers: MExE Applications at the top, followed by OEM APIs, then MIDP APIs, and CLDC APIs at the bottom. Arrows indicate that MExE Applications can access all three layers below it. OEM APIs can access MIDP APIs and CLDC APIs. MIDP APIs can access CLDC APIs. + +**Figure 15: Functional architecture of a Classmark 3 MExE device** + +The functional architecture of a Classmark 3 MExE device is shown in figure 15 "Functional architecture of a Classmark 3 MExE device". The MExE API is based on the combination of CLDC APIs and MIDP APIs. OEM specific APIs are outside the scope of MExE specification. CLDC and MIDP APIs are defined in J2ME [34] and [35]. + +### 9.1.3 High level functionality + +J2ME CLDC and MIDP addresses a large market of resource-constrained devices and is aimed to provide complete end-to-end solution for creating dynamically extensible networked products and applications. It allows the use of Java programming language as the standard platform for secure delivery of dynamic content for the extensible next-generation devices. + +In order to fit into various types of the devices and support extensibility, J2ME defines in *Configuration* a minimum platform with a virtual machine features and minimum libraries which are available on all devices of similar class. In a *Profile* J2ME addresses the specific demand of a certain category of the devices allowing additional APIs. Profile is implemented on top of configuration (see figure 15 "Functional architecture of a Classmark 3 MExE device"). + +Classmark 3 MExE device shall be based on the following types of configuration and profile: Connected Limited Device Configuration (CLDC) and Mobile Information Device Profile (MIDP). + +## 9.2 Non Security + +### 9.2.1 Connected Limited Device Configuration (CLDC) + +Classmark 3 devices shall support CLDC specification [34]. + +CLDC provides only high level libraries without focus on any specific device categories. Defining "the lowest common denominator" of Java technology all features included in CLDC must be generally applicable to a wide variety of the devices. CLDC does not address to a certain device category. Such features are specified in a profile. CLDC does not define any optional features. + +The classes provided by CLDC are either subset of J2SE (Standard Edition) classes or CLDC specific classes which can be mapped onto J2SE. Classes belonging to the packages: Java.io, Java.lang, Java.util are a subset of corresponding Java2SE libraries, while classes specified in javax.microedition.io are specific CLDC classes, which, however, can be mapped onto Java2SE. + +Javax.microedition.io provides generic connection framework for supporting input/output and networking in a generalized and extensible manner. The framework is a functional subset of Java2SE classes which can be mapped to common low-level hardware or to any Java2SE implementation. It does not provide a set of different kinds of abstractions for different forms of communications, but rather a set of related abstractions are used at the application programming level. + +The framework uses a hierarchy of Connection interfaces that group together classes of protocols with the same semantics. The actual supported protocols or implementation of the specific protocols is outside the scope of CLDC Generic Connection Framework and is maintained at the profile level. + +The basic set of available Connection interfaces is the following: + +- Connection; +- ContentConnection; +- Datagram; +- DatagramConnection; +- InputConnection; +- OutputConnection; +- StreamConnection; +- StreamConnectionNotifier + +### 9.2.2 Mobile Information Device Profile (MIDP) + +MExE classmark 3 devices shall support MIDP specification [35]. MIDP is based on CLDC. Some of the features of CLDC are modified or extended by MIDP [35]. + +#### 9.2.2.1 Networking + +While CLDC specifies only a generic Connector used for all types of connections, MIDP extends connectivity support by providing support of the subset of the HTTP protocol. HttpURLConnection API provides the additional functionality to set request header, parse response headers and perform HTTP specific functions. The API must support RFC 2396 [40] and RFC 2616 [41]. + +The MIDP does not provide support for datagrams. If a Datagram API is to be implemented, the DatagramConnection interface defined in CLDC shall be used. + +#### 9.2.2.2 MID Applications (MIDlet) + +A MIDP application (or MIDlet) uses the APIs defined by the MIDP and CLDC specifications. One or more MIDlets may be packed in one JAR file. Sharing of data between MIDlets is controlled by the individual APIs (e.g. Record Management System API). + +Application Management Software provides an environment in which a MIDlet is installed, started, stopped and uninstalled. Each JAR file can be accompanied by an Application Descriptor (a text file consisting of name/value pairs), which is used to manage MIDlet and is used by MIDlet for configuration specific attributes. With the help of descriptor file, verification prior to software download is done to ensure that the MIDlet is suited to the device: Java Application Manager checks if the application already exists on the device, verifies the version number (whether an update is needed or not) and reading the JAR-file-size information ensures that there is sufficient amount of memory on the device to save the file. The minimum attributes which the Application Descriptor must contain are the following: + +- MIDlet-Name; +- MIDlet-Version; +- MIDlet-Vendor; +- MIDlet-Jar-URL; +- MIDlet-Jar-Size. + +Mandatory and optional attributes are defined in [35]. If the mandatory attributes are not identical in the descriptor file and in the manifest file, the JAR file shall not be installed. + +#### 9.2.2.3 MIDlet Suites + +MIDlets may be packaged together in a single JAR file, forming a MIDlet suite. MIDlets in a MIDlet suite share the classes in the JAR file and the persistent storage is the MIDP Record Management System. + +MIDlets in a MIDlet suite may be discovered, transferred, installed and deleted together as a packaged set of MIDlets. The deletion of a MIDlet in a MIDlet suite may result in the deletion of the entire MIDlet suite, in which case the user shall be notified of the deletion of the MIDlet suite. + +#### 9.2.2.4 Record Storage + +The MIDP provides a mechanism for MIDlets to persistently store data and later retrieve it. The persistent storage mechanism is called Record Management System. Record stores are created in platform-dependent locations and are not exposed to MIDlets. The record store maintains a version number, which is incremented each time the content of the record store is modified. A record store is shared between all MIDlets in a MIDlet suite. + +### 9.2.3 Required and optional MExE APIs + +Support of any other Java APIs besides CLDC and MIDP is not mandated in a Classmark 3 MExE device. A Classmark 3 MExE device may optionally support any other Java APIs which comply with the MExE security requirements. + +### 9.2.4 Service discovery and management + +A browser installed on a MExE device should support MIME type text/vnd.sun.j2me.app-descriptor. This support allows the user to browse and discover a Java application which can then be downloaded. Capability negotiation information in the request header can determine which application to present. MIDlets and MIDlet suites should be indicated to the user, and if the MExE device has a display, may be presented as an icon and a tag or as a textual tag only. + +A JAD file can be downloaded and used to determine if the MIDlet is deemed suitable for download and installation. If it is suitable, the JAR file can be downloaded and installed. If not, the MExE device should be able to prompt the user so that the user might choose to take such actions such as deletion of some existing applications if there is not enough space to install the new application. If the application chosen to be installed already exists on the device, the user should be notified so that he could take further actions either to download the chosen version or to retain the existing one. + +The user should be able either to launch the MIDlet immediately or later. + +### 9.2.5 Transfer of capability negotiation information in Classmark 3 + +In Classmark 3 the CC/PP is carried over by using CC/PP over HTTP [15] and optionally CC/PP over WSP [17]. + +Also MIDP itself provides a simple mechanism for applications to indicate the capabilities they require. The Java Application Descriptor File (JAD), which is a file that can be stored and downloaded separately to the application itself, contains information such as application name, version number, JAR file size, data storage requirements etc. The Application Descriptor can accompany the JAR file and can be used to ensure prior to the actual application download that the application suits the MExE device. The JAD file is described in more details in the clause 9.2.2.2 " MID Applications (MIDlet)". + +## 9.3 Security + +If the 3 MExE security domains defined in clause 6.1 "Generic security" are not supported, then the Java security described in this clause is optional. + +### 9.3.1 CLDC security + +A Java execution environment running on a Classmark 3 MExE device shall comply with the security requirements defined in the CLDC specification [34]. That is, it shall comply with both the low-level virtual machine security requirements and the application-level security requirements. + +The application-level CLDC security requirements define a sandbox security model where Java classfiles are verified. Java APIs available to the application are limited to those APIs which have been defined by the configuration and profiles supported by the MExE device. Downloading and management of the Java applications on the MExE device takes place at the native level, no user-definable Java class loaders are provided and the set of APIs available to a MIDlet is closed. + +The low-level CLDC virtual machine security requirements define a Java classfile pre-verification mechanism which takes place off- MExE device (e.g. on the server prior to downloading) and inserts a special attribute called a "stack map" into class files to facilitate runtime verification of the same classfiles. + +# --- 10 MExE classmark 4 (CLI Compact environment) + +## 10.1 Introduction + +Classmark 4 specifies CLI Compact Profile enabled devices. + +The CLI [50] environment is a programming language neutral, OS and CPU portable environment. The CLI can support applications and services written in a wide range of programming languages, for example Visual Basic, ECMAScript and C#. The CLI Compact Profile specifies a minimal set of class libraries, supporting common runtime library features as well as web services infrastructure, including HTTP [9], TCP/IP, XML [36] & SOAP [51]. Such devices not only may have limited memory and CPU capability, but also limited (or no) display. + +### 10.1.1 High level architecture + +![Figure 16: Basic functional architecture of a CLI MExE device. The diagram shows a hierarchical structure of software layers. At the top is 'MExE Applications'. Below it is 'Platform Extensions'. Below that is 'Optional CLI APIs'. At the bottom is 'CLI Compact Profile APIs'. Arrows indicate dependencies: 'MExE Applications' depends on 'Platform Extensions', 'Optional CLI APIs', and 'CLI Compact Profile APIs'. 'Platform Extensions' depends on 'Optional CLI APIs' and 'CLI Compact Profile APIs'. 'Optional CLI APIs' depends on 'CLI Compact Profile APIs'.](2db815c41ab92ee70773412b284e1431_img.jpg) + +``` +graph TD; A[MExE Applications] --> B[Platform Extensions]; A --> C[Optional CLI APIs]; A --> D[CLI Compact Profile APIs]; B --> C; B --> D; C --> D; +``` + +Figure 16: Basic functional architecture of a CLI MExE device. The diagram shows a hierarchical structure of software layers. At the top is 'MExE Applications'. Below it is 'Platform Extensions'. Below that is 'Optional CLI APIs'. At the bottom is 'CLI Compact Profile APIs'. Arrows indicate dependencies: 'MExE Applications' depends on 'Platform Extensions', 'Optional CLI APIs', and 'CLI Compact Profile APIs'. 'Platform Extensions' depends on 'Optional CLI APIs' and 'CLI Compact Profile APIs'. 'Optional CLI APIs' depends on 'CLI Compact Profile APIs'. + +Figure 16: Basic functional architecture of a CLI MExE device + +The functional architecture of a CLI MExE classmark 4 device is shown in Figure 16 "Basic functional architecture of a CLI MExE device". CLI based applications and services access functionality via the MExE CLI Compact Profile API. Additional CLI APIs and OEM specific APIs are outside the scope of the MExE specification. The CLI Compact Profile APIs are defined in CLI specified by ECMA [50]. + +## 10.2 Non security + +Support of CLI Compact Profile in a MExE classmark 4 UE as detailed in this clause is mandatory. + +MExE Classmark 4 devices shall be based CLI Compact Profile specifications [50]. The specifications define the runtime environment and APIs available to a CLI based MExE device such that services (specified in the form of language independent classes and interfaces) can control such a device in a standardised way. + +All mandatory components of the CLI compact profile shall be included. Additional CLI APIs or OEM APIs may be available. It shall be possible for services and applications to determine the presence of additional parts of the functionality. When an additional optional CLI component is implemented, the component shall be fully implemented. + +### 10.2.1 High level functionality + +CLI provides a language-neutral, CPU and OS portable, secure infrastructure for executing applications and services that interoperate seamlessly with highly available web services. The CLI Compact Profile provides a mobile client-focussed subset of these services on a broad market of connected devices. Using multiple programming languages for application and service creation allows adoption of a large pool of programming talent, as well as interoperability between existing service components. + +Functionality is exposed to applications and services in the form of classes and interfaces. Classes can be written in any supported language. APIs can be exposed to the developer using the language syntax of choice. Classes and interfaces are collected into namespaces, which aim to represent a coherent, mutually-dependant set of functionality. + +The following Table 11 "CLI Compact Profile Namespaces" specifies the defined mandatory namespaces, i.e. the namespaces defined in the CLI Compact Profile containing classes which are required for CLI Compact Profile conformance. + +**Table 11: CLI Compact Profile Namespaces** + +| <b>CLI Compact Profile Namespaces</b> | +|----------------------------------------| +| <b>System</b> | +| <b>System.Collections</b> | +| <b>System.Globalization</b> | +| <b>System.IO</b> | +| <b>System.Text</b> | +| <b>System.Threading</b> | +| <b>System.Runtime.CompilerServices</b> | +| <b>System.Reflection</b> | +| <b>System.Net</b> | +| <b>System.XML</b> | + +The namespaces outlined in Table 11 define the core of the CLI programming model. The System namespace defines data types, including simple data types such as integers, collections such as arrays, and string data types with methods for textual manipulation. System.Globalization enables applications to adapt at runtime to user and cultural UI preferences by modifying list sorting order, currency symbol selection, date and calendar formats, input methods, and language presentation within text strings. The programming model supports threads, with thread manipulation primitives defined in System.Threading. System.Reflection enables programmatic inspection of application metadata such as class structure, properties, and data types on method parameters. System.Net includes support for transport-independent sockets, HTTP connections, and infrastructure for consuming web services. System.XML enables simple parsing and construction of XML objects. + +### 10.2.2 Network protocol support + +Support for network protocols in MExE classmark 4 devices is specified in the following Table 12 "Support for network protocols in Classmark 4 devices": + +**Table 12: Support for network protocols in Classmark 4 devices** + +| Protocol | Optionality | +|--------------|-------------| +| HTTP/1.1 [9] | Mandatory | +| HTTPS | Mandatory | +| SOAP [51] | Mandatory | +| Gopher | Optional | +| ftp | Optional | +| mailto [25] | Optional | +| File | Optional | + +### 10.2.3 Power Management + +MExE Classmark 4 devices have no application or service accessible APIs to detect the power level of the device. Classmark 4 applications or services may be paused by the MExE device if power passes below a certain threshold. Such an activity is implementation dependant. + +### 10.2.4 CLI charging support + +MExE CLI devices do not require any additional specific charging (e.g. charging records) or subscription management. Use of network resources from a CLI application or service is bearer independent and runs as applications on top of the bearer network. + +### 10.2.5 CC/PP over HTTP or WSP (Classmark 4) + +In Classmark 4 the CC/PP is carried over by using CC/PP over HTTP [15] and optionally CC/PP over WSP [17]. + +## 10.3 Security + +### 10.3.1 CLI Security + +Support of CLI security in a MExE classmark 4 device, as detailed in this clause, is mandatory. + +The CLI specification includes a detailed algorithm to verify the safety and integrity of CLI application code, known as "application verification" [50]. An application is either verified as "safe" or "unsafe". The result of the application verification process is presented to the rest of the CLI runtime environment before program execution. This is distinct from the certificate and signature verification that MExE performs before executing an application inside the MExE environment. + +Applications that are verified as unsafe may contain code that could potentially access the environment in an unauthorized manner. For example, code that uses pointer arithmetic or accesses arrays using out-of-bounds indices would be deemed unsafe. An unsafe application shall not be permitted to execute in the MExE environment. Once an application is verified as safe, this information is passed on to the rest of the CLI runtime environment, which will then apply the MExE security policy, as specified under clause 6.1, "Generic Security". + +The CLI runtime environment may be able to load libraries that are intrinsically part of the MExE device implementation. Such intrinsic libraries may contain unsafe code, however other libraries containing unsafe code are prohibited. + +# --- Annex A (normative): MExE profile of PKCS#15 + +## A.1 PKCS#15 certificate object attributes presentation + +Details from PKCS#15 [32] in this Annex A.1 "PKCS#15 certificate object attributes presentation" are for information only. + +### A.1.1 Object common attributes + +| | | +|----------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| Label | human readable label to describe the certificate | +| Flags | indicates whether the object is private (e.g. CHV authentication request), whether the object is read only. | +| Authentication object identifier | a cross-reference back to the authentication object, which describes the properties of a CHV, used to protect this object. | + +### A.1.2 Certificate common attributes + +| | | +|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | the identifier is used for correlation between the public key contained in the certificate and the associated private key. | +| Authority | indicates whether the certificate is for an authority (i.e. CA or AA) or not. | +| Request identifier | used to search a certificate : Issuer and serial number SHA-1 hash, or issuer public key SHA-1hash, or public key subject SHA-1 hash. | +| Thumbprint | used as secure way to verify that no one has tampered with a certificate: hash on to be signed certificate (internet). MExE uses the thumbprint to enable or disable a certificate through the certificate configuration message (CCM). | + +### A.1.3 Certificate attributes + +Type of certificate indicates the type of certificate: WTLS, X509, SPKI, PGP, X9.68. + +| | | +|-------|--------------------------------------------| +| Value | direct value or indirect file path or URL. | +|-------|--------------------------------------------| + +MExE only supports storage of WTLS, X509, X9.68 certificates. + +### A.1.4 Specific X.509 certificate attributes + +For information see PKCS#15 [32]. + +## --- A.2 MExE profile of PKCS#15 + +**PKCS15CommonObjectAttributes.label** must be present. The value content is unspecified. + +**PKCS15CommonObjectAttributes.Flag** must be present. The value shall be private, not modifiable by MExE device. + +**PKCS15CommonObjectAttributes.Authentication** must be present. The value shall be "CHV1". The certificates files are protected by CHV1, because MExE need also IMSI to manage domains availability. + +**PKCS15CommonCertificateAttributes.Id** must be present. The value content is unspecified. + +**PKCS15CommonCertificateAttributes.Authority** must be present if and only if certificate is a CA certificate. The value is true. + +**PKCS15CommonCertificateAttributes.RequestId** must be at least present if certificate is an operator or third party root certificate. The value shall be the same as the ones used in the issuer/authority key identifier field of the certificates, provided by this issuer (as in RFC 2459 [43]). The aim of this attribute is to give a easy way to search a key issuer of a received certificate without reading all certificates content. + +**PKCS15CommonCertificateAttributes.Thumbprint** must be at least present if certificate is a third party root certificate. The value shall be the same as the ones used in CCM. The aim of this attribute is to give a easy way to search a certificate with reference included in CCM message. + +Domain attribute presence and value shall be added as soon as it will be available in PKCS#15 v1.1. + +**PKCS15 (type) CertificateAttributes.value** must be present Value is a indirect file path (path, index, offset). Index and offset default value is 0. + +Specific X509 attributes are not supported: + +**PKCS15X509CertificateAttributes.subject** must not be present. + +**PKCS15X509CertificateAttributes.issuer** must not be present. + +**PKCS15X509CertificateAttributes.serialNumber** must not be present. + +The MExE device shall recognise all optional present fields above. The MExE device shall accept and ignore all unused fields or new field extensions. + +## --- A.3 Coding and storage in MExE-(U)SIM + +See detail of file hierarchy and file properties in (U)SIM document TS 51.011 [27] and TS 31.102 [39]. + +Since the domain attribute is not available in PKCS#15 v1.0, MExE creates one directory file for each trusted domain. If the domain attribute is available in the next PKCS#15 versions, for future new domains, MExE may create a common directory file. See abstract syntax definition and coding detail in PKCS#15 document [32]. + +The address of the certificate descriptor Elementary File is fixed. + +According to PKCS#15 [32] clause 6.6 "Certificates", the contents of a certificate descriptor Elementary File must be the *value* of the DER encoding of a **SEQUENCE OF PKCS15Certificate** (i.e. excluding the outermost tag and length bytes). + +The address of the certificate data Elementary File is unspecified. + +According to PKCS#15 [32] clause 6.6 "Certificates", the certificate data value is coded according to the related certificate type (e.g. DER for X5.09, base64 for SPKI and PGP, WTLS network format for WTLS, DER or PER for X9.68). + +# Annex B (informative): PKCS#15 certificate objects ASN1 expanded syntax extract + +``` +{ -- sequence of certificate + +x509Certificate, [0] x509AttributeCertificate, [1] spkiCertificate, [2] pgpCertificate, +[3] wtlsCertificate, [4] x9-68Certificate : { + + commonObjectAttributes { + + label "" UTF8 string OPTIONAL, + + flags {private (0), modifiable (1)} bit string OPTIONAL, -- + + authId octet string OPTIONAL, -- + + }, + + CommonCertificateAttributes { + + iD octet string, + + authority boolean default not an authority, + + requestId { + + idtype integer + + IdValue octet string + + pkcs15IssuerAndSerialNumber PKCS15KEY-IDENTIFIER ::= + + {SYNTAX PKCS15-OPAQUE.&Type IDENTIFIED BY 1} + + -- As defined in RFC [CMS] + + pkcs15SubjectKeyId PKCS15KEY-IDENTIFIER ::= + + {SYNTAX OCTET STRING IDENTIFIED BY 2} + + -- From x509v3 certificate extension + + pkcs15IssuerAndSerialNumberHash PKCS15KEY-IDENTIFIER ::= + + {SYNTAX OCTET STRING IDENTIFIED BY 3} + + -- Assumes SHA-1 hash of DER encoding of IssuerAndSerialNumber + + pkcs15SubjectKeyHash PKCS15KEY-IDENTIFIER ::= + + {SYNTAX OCTET STRING IDENTIFIED BY 4} + + -- Hash method defined in Section 7. + + pkcs15IssuerKeyHash PKCS15KEY-IDENTIFIER ::= + + {SYNTAX OCTET STRING IDENTIFIED BY 5} + + -- Hash method defined in Section 7. + + } OPTIONAL, + + thumbprint [0] OOB CertHash OPTIONAL, -- hash on to be signed certificate, used for +secure certificate identification as CCM using + + }, + + [1] typeAttributes { + + value indirect : path : { +``` + +``` + + path octet string, -- '4331'H Reference by file identifier + index integer OPTIONAL, -- 'XXXX'H offset in file + [0] length integer OPTIONAL, -- 'XXXX'H length in file + } +-- other optional attributes are defined for X509 certificate + } +}, +} + +``` + +# --- Annex C (normative): Access restriction certificate extension + +access-Restriction extension + +id-ETSI OBJECT IDENTIFIER ::= {ITU identified-organization (3) ETSI } ::= {ETSI} + +id-mexe OBJECT IDENTIFIER ::= {ETSI MExE} + +Id-mexe-accessRestriction ::= {id-mexe 1} + +AccessRestriction ::= BIT STRING { + +    network\_service\_access (0),} + +# Annex D (informative): MExE executable life cycle + +This is a conceptual description of the life cycle of a MExE executable. There may be small deviations in a specific classmark. + +The Unified Modelling Language (UML) [38] is used in the description. (This is a brief description of the symbols. A rounded rectangle is a state. An arrow is a transition between states. A dot is an initial state indicating the starting state when the enclosing state is entered. A circle with a dot is a final state. When a final state is activated the enclosing state ends.) + +Figures in parenthesis are references to clauses in the specification. + +## D.1 State of a MExE executable + +The life cycle of MExE executables (clause 5.3 "Provisioning and management of services") is described using a state machine. In a MExE device a MExE executable can have the following states and transitions between states. + +![State machine diagram for MExE executable life cycle within a Verification state.](f4b570ddd089f54943d46e9f8776f9f9_img.jpg) + +``` +stateDiagram-v2 + [*] --> Validation + Validation --> Untrusted + Validation --> Trusted + Validation --> Deleted + Untrusted --> [*] + Trusted --> [*] + Deleted --> [*] +``` + +The diagram illustrates the state life cycle of a MExE executable within a 'Verification' state. It begins with an initial state (dot) leading to the 'Validation' state. From 'Validation', three transitions are possible: to 'Untrusted', 'Trusted', or 'Deleted' states. Both 'Untrusted' and 'Trusted' states lead to final states (circle with dot), indicating the end of the executable's life cycle. The 'Trusted' state is further detailed as being 'In Operator or Manufacturer or Third Party Domain'. The 'Deleted' state leads to a final state marked with an 'X', also indicating the end of the life cycle. + +State machine diagram for MExE executable life cycle within a Verification state. + +| State or Transition (=>) | Description | +|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial => Discovered | The MExE executable is discovered (clause 5.3.1 "Service discovery"). | +| Discovered | The MExE executable is discovered and can be installed or executed without installation. (Only executables useable on the MExE device should enter this state.) | +| Discovered => Resident | The discovered executable is selected to be installed and the executable is transferred (clause 5.3.2 "Service transfer") to the MExE device for installation. | +| Discovered => Uninstalled Execution | The discovered executable is selected to be executed without installation. | +| Discovered => final state | The executable is undiscovered. | +| Resident | The executable is stored in the MExE device. It has been transferred or is pre-loaded. | +| Verification | This is the initial sub-state of the Resident state. This is a composite state. There is a description of the Verification state in D.4. | +| Verification => Configuration | The result of the verification indicates that the executable can be installed in one of the Domains. | +| Configuration | This is a sub-state of the Resident state. The executable can be configured, manually or automatically (clause 5.3.3 "Service installation and configuration"). | +| Configuration => Released | The service is released for execution. | +| Released | This is a sub-state of the Resident state. The executable is resident, configured and released for execution. This is a composite state and there is a description of it in D.2. | +| Released => Configuration | The executable is blocked for execution or an executable has changes security domain (The user shall have the possibility to review the configuration before the executable is released for execution with different privileges.). | +| Resident => final state | The Resident state is left when the service is deleted (clause 5.3.6 "Service deletion"). From the MExE device point of view the executable does not exist any more. (The Integrity and Certification Validation (clause 6.10 "Certificate management") can also force a deletion) | +| Uninstalled Execution | The executable is executed without installation. This is a composite state. There is a description of the Uninstalled Execution state in D.3. | +| Uninstalled Execution => final state | The Uninstalled Execution state is left when the executable terminates by itself or when the user terminates the executable (clause 5.3.5 "Service termination"). From the MExE device point of view the executable does not exist any more. | +| Uninstalled Execution => Resident | This is a possible but unusual transition. A MExE executable that has been used for uninstalled execution is installed without retransferring. | + +## D.2 Released state + +A MExE executable in the Released state is resident, configured and released for execution. + +![Flowchart titled 'Verification' showing the process of validating an executable. It starts with 'Validation', which branches into 'Untrusted', 'Trusted' (In Operator or Manufacturer or Third Party Domain), and 'Deleted'. 'Untrusted' and 'Trusted' lead to a final state (bullseye symbol), while 'Deleted' leads to an 'X' symbol.](17f0cf80b9c38adb460d4ca836960da7_img.jpg) + +``` + +graph TD + Start(( )) --> Validation[Validation] + Validation --> Untrusted[Untrusted] + Validation --> Trusted["Trusted +In Operator or Manufacturer +or Third Party Domain"] + Validation --> Deleted[Deleted] + Untrusted --> End1(( )) + Trusted --> End2(( )) + Deleted --> End3[X] + +``` + +Flowchart titled 'Verification' showing the process of validating an executable. It starts with 'Validation', which branches into 'Untrusted', 'Trusted' (In Operator or Manufacturer or Third Party Domain), and 'Deleted'. 'Untrusted' and 'Trusted' lead to a final state (bullseye symbol), while 'Deleted' leads to an 'X' symbol. + +| State or Transition (=>) | Description | +|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Passive | This is the initial state. The executable can be invoked. | +| Passive => Verification | The MExE executable is invoked. | +| Verification (or Optimised Verification) | The verification can either be done according to the Verification state described in D.4 or as an Optimised Verification described in (clause 6.2.2 "Optimised application signature verification"). | +| Verification => Executing | The result of the verification indicates that the executable may be executed. The Activated state and its sub-state Executing are entered. | +| Verification => final state | The MExE executable has changed its security state and it must not be executed. | +| Activated | The MExE executable is activated. | +| Executing | This is a sub-state of Activated. The executable executes (if it is not waiting for user permission). | +| Executing => final state | The Executing state is left when the executable terminates by itself. The Activated state is left and the Passive state is entered. | +| Waiting for user permission | This is a sub-state to Executing. (If there is support for multi-threaded applications, this state can be a state concurrent to the Executing state.) The MExE executable is waiting for permission to perform some action (clause 6.3.1 "MExE executable permissions for operator, manufacturer and third party security domains"). | +| Suspended | This is a sub-state of Activated. The execution is suspended (clause 5.3 "Provisioning and management of services"). | +| Activated => Passive | The Activated state is left when the executable terminates by itself or when the user terminates the executable (clause 5.3.5 "Service termination"). | + +## D.3 Uninstalled Execution state + +In the Uninstalled Execution state a MExE executable is executed without installation. + +![State transition diagram for the Verification state. It starts with an initial state leading to a 'Validation' state. From 'Validation', there are three transitions: 'Untrusted' leading to a final state, 'Trusted' (In Operator or Manufacturer or Third Party Domain) leading to a final state, and 'Deleted' leading to a state with an 'X' (error state).](b63f41ca262d8ce9ef8affb62607f32b_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Validation + Validation --> Untrusted + Validation --> Trusted + Validation --> Deleted + Untrusted --> [*] + Trusted --> [*] + Deleted --> [*] : X + state "Trusted<br/>In Operator or Manufacturer<br/>or Third Party Domain" as Trusted + +``` + +State transition diagram for the Verification state. It starts with an initial state leading to a 'Validation' state. From 'Validation', there are three transitions: 'Untrusted' leading to a final state, 'Trusted' (In Operator or Manufacturer or Third Party Domain) leading to a final state, and 'Deleted' leading to a state with an 'X' (error state). + +| State or Transition (=>) | Description | +|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transferring | This is the initial state of Uninstalled Execution. The MExE executable is transferred to the MExE device. | +| Transferring => Verification | If the executable is signed the Verification state is entered after the transferring is finished. | +| Transferring => Executing | If the executable is not signed the Executing state is entered. (To allow streaming, this can be done before the transfer is finished.) | +| Verification | This is a composite state. There is a description of the Verification state in D.4. | +| Verification => Executing | The result of verification indicates that the executable may be executed. | +| Verification => final state | The result of verification indicates that the executable must not be executed and the Uninstalled Execution state is ended. | +| Executing | The MExE executable is executing. | +| Executing => final state | The Executing state is left when the execution terminates by itself (The Uninstalled Execution state is left.) | +| Waiting for user permission | This is a sub-state to Executing. (If there is support for multi-threaded applications, this state can be a state concurrent to the Executing state.) The MExE executable is waiting for permission to perform some action (clause 6.3.1 "MExE executable permissions for operator, manufacturer and third party security domains"). | +| Suspended | The execution is suspended (clause 5.3 "Provisioning and management of services") | + +## D.4 Verification + +The integrity and certification validation (clause 6.10 "Certificate management") is done in the Verification state. The result of validation determines the change of state. + +![State transition diagram for the Verification state. The diagram is titled 'Verification' and is enclosed in a rounded rectangle. It starts with an initial state (solid dot) pointing to a 'Validation' state. From 'Validation', three arrows lead to 'Untrusted', 'Trusted' (with subtext 'In Operator or Manufacturer or Third Party Domain'), and 'Deleted' states. 'Untrusted' and 'Trusted' both lead to final states (bullseye symbol). 'Deleted' leads to a large 'X' symbol, indicating an invalid or terminal state.](cf018d13814389b0bd7f94a2f9bb812a_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Validation + Validation --> Untrusted + Validation --> Trusted + Validation --> Deleted + Untrusted --> [*] + Trusted --> [*] + Deleted --> X + +``` + +State transition diagram for the Verification state. The diagram is titled 'Verification' and is enclosed in a rounded rectangle. It starts with an initial state (solid dot) pointing to a 'Validation' state. From 'Validation', three arrows lead to 'Untrusted', 'Trusted' (with subtext 'In Operator or Manufacturer or Third Party Domain'), and 'Deleted' states. 'Untrusted' and 'Trusted' both lead to final states (bullseye symbol). 'Deleted' leads to a large 'X' symbol, indicating an invalid or terminal state. + +| State | Description | +|--------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| Validation | This is the initial state. The integrity and certification validation (clause 6.10 "Certificate management") is done. | +| Untrusted | The executable is untrusted (clause 6.1 "Generic security") | +| Trusted in Operator Domain | The executable is verified to belong to the Operator Domain (clause 6.1 "Generic security"). | +| Trusted in Manufacturer Domain | The executable is verified to belong to the Manufacturer Domain (clause 6.1 "Generic security"). | +| Trusted in Third Party Domain | The executable is verified to belong to the Third Party Domain (clause 6.1 "Generic security"). | +| Deleted | The executable is not permitted in any Domain and it is deleted. | + +# Annex E (informative): MExE conformance requirements + +The table of Conformance Requirements define the minimum set of features that a conformant MExE device must implement. + +Legend:- + +M - Mandatory feature/requirement + +O - Optional feature + +N/A - Feature is not applicable: the MExE specification does not prevent this feature from being implemented; however, support of this feature is not required for a MExE device to be regarded as being compliant with a specific MExE Classmark device. Therefore the specification does not indicate whether the feature is optional or mandatory. + +M/O – Support as such is required. Mandatory and Optional features are gathered into a table + +| ID | Requirement | Reference | CM1 | CM2 | CM3 | +|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----|-----|-----| +| 4-1 | Support of at least one MExE classmark on a MExE device | 4 | M | M | M | +| 4-2 | Support of multiple combinations of MExE classmarks | 10.1 | O | O | O | +| 4-3 | Support of WAP | 4.2.5 | M | O | O | +| 4-4 | If Classmark 1 services are supported by non-Classmark 1 devices, Classmark 1 services shall execute in the same manner as they execute in a MExE Classmark 1 device | 4.5.1 | N/A | M | M | +| 4-5 | Support of PersonalJava | 8.1, 8.1.1 | O | M | O | +| 4-6 | If Classmark 2 services are supported by non-Classmark 2 devices, Classmark 2 services shall execute in the same manner as they execute in a MExE Classmark 2 device. | 4.5.2 | M | N/A | M | +| 4-7 | Support of CLDC and MIDP | 9.1, 9.1.1 | O | O | M | +| 4-8 | If Classmark 3 services are supported by non-Classmark 3 devices, Classmark 3 services shall execute in the same manner as they execute in a MExE Classmark 3 device. | 4.5.3 | M | M | N/A | +| 4-9 | Support of capability negotiation process | 4.2 | M | M | M | +| 4-10 | Support for interaction between the MExE device and the MSE by the use of HTTP/1.1or HTTP/1.1 derived protocol (e.g. WSP) | 4.2 | M | M | M | +| 4-11 | Support of the properties in the UAProf schema for capability negotiation | 5.2.1 | M/O | M/O | M/O | +| 4-12 | Support of content negotiation | 4.2 | O | O | O | +| 4-13 | Support of user profiles | 5.2 | O | O | O | +| 4-14 | Support of more than one user profile (if user profiles supported) | 5.2.2 | O | O | O | +| 4-15 | Ability to retain the user profile in the network (if user profiles supported) | 5.2.2 | O | O | O | +| 4-16 | User permission for retaining the user profile in the network (if user profiles supported) | 5.2.2 | M | M | M | +| 4-17 | Support of direct and indirect referencing mechanisms in retrieval of MExE preferences (if user profiles supported) | 8.2.2 | O | O | O | +| 4-18 | Support of the properties in the UAProf schema for user preference information (if user profiles supported) | 8.2.2 | M | M | M | +| 4-19 | Support of user interface personalisation | 5.1 | O | O | O | +| 4-20 | Support of direct and indirect referencing mechanisms in retrieval of user interface personalisation preferences | 5.1.1 | O | O | O | +| 4-21 | Ability to support VHE | 9.2.5 | O | O | O | + +| ID | Requirement | Reference | CM1 | CM2 | CM3 | +|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-----|-----|-----| +| 4-22 | Storage of the VHE characteristics as a part of the user profile (if VHE and user profile is supported) | 9.2.5 | M | M | M | +| 4-23 | Capability to discover new services | 5.1.3.1 | M | M | M | +| 4-24 | Support for a browser for service discovery | 5.1.3.1 | O | O | O | +| 4-25 | Ability to control service installation and configuration | 4.10.3 | N/A | M | M | +| 4-26 | Ability to determine which services are transferred to, resident, configured or executing on the MExE device (provide the name and, if available, version number) | 4.10.4 | M | M | M | +| 4-27 | Service termination capability | 4.10.5 | M | M | M | +| 4-28 | Capability to delete a service | 4.10.6 | M | M | M | +| 4-29 | User's ability to terminate or suspend any active connection associated with any MExE executable | 5.3 | M | M | M | +| 4-30 | User's ability to obtain information on all connections associated with any MExE executable on the MExE device | 5.3 | M | M | M | +| 4-31 | Support of journaling of network events by MExE executables | 5.4 | M | M | M | +| 4-32 | Management of the journal by the MExE device, with no access to it by MExE executables | 5.4 | M | M | M | +| 4-33 | Indicate whenever network activity is in progress | 5.4.1 | O | O | O | +| 4-34 | Support of QoS management by MExE | 5.4.2, 9 | O | O | O | +| 4-35 | Support of core software download functionality | 5.5 | O | O | O | +| 4-36 | Core software download (if supported) only under control of the MExE device manufacturer | 5.5 | M | M | M | +| 5-1 | Call control using WTA scripts | 7.3.1 | M | O | O | +| 6-1 | Support of the Wireless Profile of the JavaPhone API specification (Optional Java packages of Wireless Profile of the JavaPhone APIs as presented in Table 9 "Optional Java packages of the Wireless Profile of the JavaPhone APIs") | 8.2.1.1,<br>8.2.1.3 | O | M/O | O | +| 6-2 | Support of the JAR file manifest entries as per JavaPhone specification | 8.2.1.3.1 | O | M | O | +| 6-3 | The use of icons to launch applications | 8.2.1.3.1 | O | O | O | +| 6-4 | If icons are used as elements to launch the application, then the icon file within the JAR file named by the Main-Icon attribute shall be displayed | 8.2.1.3.1 | O | M | O | +| 6-5 | Implementation of "BatteryCritical", "BatteryNormal" event generation | 8.2.1.3.2 | O | M | O | +| 6-6 | Support for the following formats in Datagram recipient addressing: raw text-only GSM SMS message, UDP datagram via IP, and WAP datagram via GSM SMS message(s) | 8.2.1.3.3 | O | M | O | +| 6-7 | Support any other Java APIs which comply with the MExE security requirements in Table 5 "Security domains and actions" | 8.2.1.4 | O | O | O | +| 6-8 | Support for network protocols as per table 10 "Support for network protocols" | 8.2.1.5.1 | O | M/O | O | +| 6-9 | Support of MIDlet discovery and management via a browser using MIME type text/vnd.sun.j2me.app-descriptor | 9.2.4 | O | O | O | +| 6-10 | Indication of MIDlets and MIDlet suites to the user (with a tag or icon and tag) | 9.2.4 | O | O | O | +| 7-1 | Support of charging regimes of MExE services (charging mechanisms are outside the scope of MExE specification). | 5.6.1 | O | O | O | +| 8-1 | Support of the untrusted area | 6.1 | M | M | M | +| 8-2 | Support of all three security domains together (i.e. operator, manufacturer and third party), or no security domains at all | 6.1 | M | M | M | +| 8-3 | Security restrictions shall apply to MExE executables when API functionality is directly or indirectly called by MExE executables | 6.3 | M | M | M | +| 8-4 | Support for permissions of operator, manufacturer and third party security domains in the order of restriction (as defined in table 5 of MExE specification). | 6.3.1 | M | M | M | +| 8-5 | Access by MExE untrusted executables limited to the functionality specified in the table 6 of MExE specification | 6.3.2 | M | M | M | +| 8-6 | Separation of the user interface input and output streams between different MExE executables (except for the MIDlets in the same MIDlet suite) | 6.11 | M | M | M | +| 8-7 | Support of single action permission with a prompt for the user | 6.5 | M | M | M | +| 8-8 | Support of session permission and blanket permission with a prompt for the user | 6.5 | O | O | O | +| 8-9 | Indication to the user whenever user permission is sought by an untrusted MExE executable | 6.5 | M | M | M | + +| ID | Requirement | Reference | CM1 | CM2 | CM3 | +|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----|-----|-----| +| 8-10 | Ability of the user to request to be informed of the "subject" field of the certificate of the signer (if secure domains supported) | 6.5 | M | M | M | +| 8-11 | Support for public key based solution of content authentication (if secure domains supported) | 6.7 | M | M | M | +| 8-12 | Support of certificate chains (if secure domains supported) | 6.7 | M | M | M | +| 8-13 | Support at least one level of certificate under operator, manufacturer or Third Party root public keys (if secure domains supported) | 6.7 | M | M | M | +| 8-14 | Secure installation of root public keys in the MExE device (if secure domains supported) | 6.7.1 | M | M | M | +| 8-15 | Prohibition to share public keys between domains (if secure domains supported) | 6.7.1 | M | M | M | +| 8-16 | Support the use and management of an operator root public key on the (U)SIM (if secure domains supported) | 6.6.1 | M | M | M | +| 8-17 | Prohibition of the user to add or delete any type of operator public keys (if secure domains supported) | 6.6.1 | M | M | M | +| 8-18 | Support of operator and manufacturer disaster recovery root public keys (if secure domains supported) | 8.5. | O | O | O | +| 8-19 | Support of the use and management of the operator root public key (if secure domains supported) | 8.5.1. | M | M | M | +| 8-20 | Support of the use and management of the manufacturer root public key (if secure domains supported) | 6.6.2 | M | M | M | +| 8-21 | Support of the use and management of the third party root public keys (if secure domains supported) | 6.6.3 | M | M | M | +| 8-22 | Support of the use and management of the administrator root public key (if secure domains supported) | 6.13.1 | M | M | M | +| 8-23 | Support of the administrator designation mechanism (if secure domains supported) | 6.13.1 | M | M | M | +| 8-24 | Support of the certificate configuration management (if secure domains supported) | 6.10 | M | M | M | +| 8-25 | Use of the CCM by MExE device to determine the third party certificates that are trusted for the use on the MExE device (if secure domains supported) | 6.10.1 | M | M | M | +| 8-26 | Additional support of other means to enable/disable root certificates (if secure domains supported) | 6.10.1 | O | O | O | +| 8-27 | Support of authorised CCM download mechanisms (if secure domains supported) | 8.7. | M | M | M | +| 8-28 | When the administrator is changed, then the CCM shall also be changed. (if secure domains supported) | 8.7. | M | M | M | +| 8-29 | Support of provisioned mechanism for designating administrative responsibilities and adding third parties in a MExE device (if secure domains supported) | 6.13.2 | M | M | M | +| 8-30 | Support of the cases: the user is the owner, the user is at remote location, the owner of the MExE-(U)SIM wants to be a temporary administrator (if secure domains supported) | 6.13.2 | M | M | M | +| 8-31 | Support for determining the administrator of the MExE device (if secure domains supported) | 6.13.3 | M | M | M | +| 8-32 | Either sandbox or fine grain Java security shall be supported | 8.3.1 | N/A | M | N/A | +| 8-33 | Support for trusted applets (if secure domains supported) | 8.3.1 | N/A | O | O | +| 8-34 | Verification of the certification of the application or applet (if secure domains supported) | 8.3.1.2 | M | M | M | +| 8-35 | Java loading native libraries that are intrinsically part of the MExE device implementation, and MExE native libraries | 8.3.1.3 | O | O | O | +| 8-36 | No loading of other native libraries | 8.3.1.3 | N/A | M | N/A | +| 8-37 | Support of the JAR file format devices for securely packaging objects that are to be downloaded and installed on the MExE device | 10.3.1 | N/A | M | M | +| 8-38 | Support for other proprietary means of downloading and installing objects | 10.3.1 | O | O | O | +| 8-39 | Support of MExE native library signed package installation | 8.3.2 | N/A | O | O | +| 8-40 | Support for the case when a certificate containing an Administrator root public key is thus contained in a signed package, the signed package (JAR) shall contain two files: the Administrator root public key and the CCM (if secure domains supported). | 6.8.2 | N/A | M | M | +| 8-41 | Support of installation of other signed data (e.g. proprietary binaries or Java classes such as native DSP code, provisioned functionality upgrades and patches) (if secure domains supported). | 6.8.3 | O | O | O | + +| ID | Requirement | Reference | CM1 | CM2 | CM3 | +|------|-------------------------------------------------------------------------------------------------------------|-----------|-----|-----|-----| +| 8-42 | Support for administrator root certificate mechanism (if secure domains supported). | 6.13.4 | M | M | M | +| 8-43 | Support of alternative methods to download an administrator root certificate (if secure domains supported). | 6.13.4 | O | O | O | +| 8-44 | Support of optimised signature verification of applications (if secure domains supported). | 6.8.1 | O | O | O | +| 9-1 | Support of QoS API by MExE device | 9 | O | O | O | +| 9-2 | Support of a basic QoS operations | 5.5.2 | O | O | O | +| 9-3 | Support of MExE QoS API by MExE QoS Manager | 5.5.3 | O | O | O | +| 9-4 | Provision of the MExE QoS Manager functions | 5.5.3 | O | O | O | +| 9-5 | Ability to manage QoS through the MExE device's MMI | 5.5.3 | O | O | O | +| 9-6 | QoS control by MExE QoS Manager, if it is not provided in the network control | 5.5.4 | O | O | O | +| 9-7 | Provision of a standard set of parameters by a QoS API to MExE executable | 5.5.5 | O | O | O | +| 9-8 | Ability of MExE QoS Manager to deal independently with each of the several simultaneous QoS streams | 5.5.7 | O | O | O | + +# Annex F (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|-----|-----|-----|------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 2002 | T#16 | TP-020102 | 118 | - | - | Restructuring of the MExE-specification | 5.0.0 | 6.0.0 | +| 2002 | T#17 | TP-020202 | 119 | - | - | CC/PP section cleanup | 6.0.0 | 6.1.0 | +| 2002 | T#17 | TP-020202 | 120 | - | - | Adding new attributes to the JAR manifest file | 6.0.0 | 6.1.0 | +| 2003 | T#21 | TP-030169 | 122 | - | - | Correcting figure and table numbering | 6.1.0 | 6.2.0 | +| 2007-06 | SP-36 | - | - | - | - | Update to Rel-7 version (MCC) | 6.2.0 | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | - | Update to Rel-8 version (MCC) | 7.0.0 | 8.0.0 | +| 2009-12 | SP-46 | - | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | +| 2011-03 | SP-51 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | <b>11.0.0</b> | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23066/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/Rel-11/23_series/23066/030c758fd425016b03290c8f11bef69d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11f4455957b48bb00b4090a6449ac6e545263fa6 --- /dev/null +++ b/marked/Rel-11/23_series/23066/030c758fd425016b03290c8f11bef69d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dee8faf72db1027f62fced34e45339217e58d9227429419254f112ecccd51ed3 +size 47396 diff --git a/marked/Rel-11/23_series/23066/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-11/23_series/23066/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e44fa3a78fdb6c65e5dec9d03b91302875e50ea --- /dev/null +++ b/marked/Rel-11/23_series/23066/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:708c60db66188ba9060149be66517baee4b7c7d72aaedf8de94c2b4b3d6dc2bf +size 105614 diff --git a/marked/Rel-11/23_series/23066/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/Rel-11/23_series/23066/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22f76b551b6c5740ac89ca22eabf2a794318e95a --- /dev/null +++ b/marked/Rel-11/23_series/23066/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c4cf3a9d78fe4a0b050bd30a70d03ef8fd17c59a6d1a286e8d9f2b3af4d6d67 +size 43452 diff --git a/marked/Rel-11/23_series/23066/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/marked/Rel-11/23_series/23066/1316d63eca7b84e13c27f55f0027b7b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..080e327f9babef00d3295e7562e4bf89761d0a2b --- /dev/null +++ b/marked/Rel-11/23_series/23066/1316d63eca7b84e13c27f55f0027b7b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ae2172281f52c0bab07084921bf8b96686ff77ad5767ca81bce2104fd1ba191 +size 63877 diff --git a/marked/Rel-11/23_series/23066/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/23_series/23066/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebe52f835bb8430e3bd9b5e4396530b350035b61 --- /dev/null +++ b/marked/Rel-11/23_series/23066/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7da746ba7a8c268f92031eb6d91b8642078d01e190ad62bca2d59c483e94733 +size 79620 diff --git a/marked/Rel-11/23_series/23066/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-11/23_series/23066/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c755354df0a37282e2f8ad4c1581082eaac6672e --- /dev/null +++ b/marked/Rel-11/23_series/23066/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81ba6ca85ca1d8e431d09e12adbc2d2739073b9ac30a37ed9b53796471e9a9e4 +size 62674 diff --git a/marked/Rel-11/23_series/23066/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Rel-11/23_series/23066/1ce027dfd26183da52137cf990213724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cff430d8c69a313e4f2a5194b9a6ac879415b693 --- /dev/null +++ b/marked/Rel-11/23_series/23066/1ce027dfd26183da52137cf990213724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7606f181cd19246105b1c4e5945d5044f17933360da05442c0e5474ffc377ee3 +size 60544 diff --git a/marked/Rel-11/23_series/23066/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg b/marked/Rel-11/23_series/23066/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0209f4bf990267d27694aef49870fa280e9a9e77 --- /dev/null +++ b/marked/Rel-11/23_series/23066/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aeaba5d740b1149eebb58be145bc12fee0f9dd47639e7c5dd4ad8c43fe651274 +size 83322 diff --git a/marked/Rel-11/23_series/23066/21327313f7b18a481da0c87a6472a80d_img.jpg b/marked/Rel-11/23_series/23066/21327313f7b18a481da0c87a6472a80d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e0a19b4b723c87512eea54659274f144fba3fb1 --- /dev/null +++ b/marked/Rel-11/23_series/23066/21327313f7b18a481da0c87a6472a80d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4dec1832b4963aa04615b1f90c921857e192ed7372d5c32233ecb7e03b2ed394 +size 30171 diff --git a/marked/Rel-11/23_series/23066/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/23_series/23066/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc56ba1b518879755b15f61263e6e0a0f101f7a0 --- /dev/null +++ b/marked/Rel-11/23_series/23066/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1f49afb1648b32119b7782bb49df4cb47409fac0987592d50c35cb19b9a6815 +size 55474 diff --git a/marked/Rel-11/23_series/23066/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23066/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d3df32c796182cfec6c976aed8df15ed2806324 --- /dev/null +++ b/marked/Rel-11/23_series/23066/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4131af410c52cc5315a3382eb4c7851e8f99b8880aa02aa9b75bbe44817a1440 +size 71196 diff --git a/marked/Rel-11/23_series/23066/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/23_series/23066/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81239d360c59a77db75dd2458b3a77bc99c128ba --- /dev/null +++ b/marked/Rel-11/23_series/23066/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9d559a67cdd9b2d14193164fec2609fc590d256b143c51b4492e58ed7976551 +size 94511 diff --git a/marked/Rel-11/23_series/23066/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-11/23_series/23066/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49710e1f8c6a20191525574a8ac10d2d48fdacf4 --- /dev/null +++ b/marked/Rel-11/23_series/23066/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec0e037eba865bcb4c0b05d9c38ebd56a09546d4076eb286e572b52456d79bbe +size 70586 diff --git a/marked/Rel-11/23_series/23066/3493d7ba4c86f944e159de1bf45ff03d_img.jpg b/marked/Rel-11/23_series/23066/3493d7ba4c86f944e159de1bf45ff03d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d065ed9894bdb2d5b07b63db4c4bf16bdc93367 --- /dev/null +++ b/marked/Rel-11/23_series/23066/3493d7ba4c86f944e159de1bf45ff03d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e83a0030951b4162edcdd2d1b0932ee5784f23b0e4fa4654c861433ff3298cb6 +size 63415 diff --git a/marked/Rel-11/23_series/23066/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/Rel-11/23_series/23066/408c4798ea60469e0728a7cbbd598668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef37987429440da8dec6246732625cc75b6b47fe --- /dev/null +++ b/marked/Rel-11/23_series/23066/408c4798ea60469e0728a7cbbd598668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af1f1e35c6afc6174aaadccd3b3a527bfd65de857567d5f656782b4959a2e0df +size 75416 diff --git a/marked/Rel-11/23_series/23066/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Rel-11/23_series/23066/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea9da57e7de75b235818d9269d7943f5d7c5909d --- /dev/null +++ b/marked/Rel-11/23_series/23066/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:feecd464e51eda71400cf53f052ad048817e667bfec1798d3cfdcd9adf295ef2 +size 57515 diff --git a/marked/Rel-11/23_series/23066/474a819357587e34949a3e110ff19b30_img.jpg b/marked/Rel-11/23_series/23066/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da47f6805ae1aaa8a0cccb67e0c2a602588f8233 --- /dev/null +++ b/marked/Rel-11/23_series/23066/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:952bbe8a7049a4785d34ee9a08b44185f70353f6f86f91344557dd82f6505bc5 +size 72548 diff --git a/marked/Rel-11/23_series/23066/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/Rel-11/23_series/23066/4f148853ae68fdcf5e43f7604cab457d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44df76cd91084770eba52252066cb35a4dd8f108 --- /dev/null +++ b/marked/Rel-11/23_series/23066/4f148853ae68fdcf5e43f7604cab457d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b4db319eae5e533f2153c576d4e1da817f74ef4a01d135b48e80bc067380f2c +size 57095 diff --git a/marked/Rel-11/23_series/23066/52e112d1ba42a3c660bf62a0fea927d3_img.jpg b/marked/Rel-11/23_series/23066/52e112d1ba42a3c660bf62a0fea927d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a2be19f500c532bfe6d7a77390dd4d9b400429e --- /dev/null +++ b/marked/Rel-11/23_series/23066/52e112d1ba42a3c660bf62a0fea927d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b75fccf864b5a66f74473bb4223bb749de5cb261e05ae4fc41702be0792284b +size 46851 diff --git a/marked/Rel-11/23_series/23066/552328a9daaf3bc0069424b500025880_img.jpg b/marked/Rel-11/23_series/23066/552328a9daaf3bc0069424b500025880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a4d2bc1653bac33d09d2c0129d6a7244d85a75c --- /dev/null +++ b/marked/Rel-11/23_series/23066/552328a9daaf3bc0069424b500025880_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9475db346dc5c82f2f42fb405717d57c0d2a926a348e20b32c2927d69a7e891a +size 82812 diff --git a/marked/Rel-11/23_series/23066/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/23_series/23066/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c5066d7f0f5da52df6a13c137cbe43f79d32234 --- /dev/null +++ b/marked/Rel-11/23_series/23066/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ac2398b6839fa7070047512311f912ddc23a396774b387583ac47ffde328759 +size 54495 diff --git a/marked/Rel-11/23_series/23066/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-11/23_series/23066/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9ede98885179e0c0a63033caa7803f72533609c --- /dev/null +++ b/marked/Rel-11/23_series/23066/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5fb36e9c5ff1e7780f61badfcc194d89dfb805d7d1f9cd26d06e5b4dbd12cf1 +size 58910 diff --git a/marked/Rel-11/23_series/23066/5bba23cc120ad806779f82df1c01bebf_img.jpg b/marked/Rel-11/23_series/23066/5bba23cc120ad806779f82df1c01bebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7ccb813631e26274a7c26e97fb1ef3aa48f01f5 --- /dev/null +++ b/marked/Rel-11/23_series/23066/5bba23cc120ad806779f82df1c01bebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:818e10d6e7c660283501eeaf880f991ce16d0caf4d65b094a07ffa9f4ecdcfb6 +size 61899 diff --git a/marked/Rel-11/23_series/23066/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/23_series/23066/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..022b6ec2be6842e80f4e1e96c4e86ddbe39281e7 --- /dev/null +++ b/marked/Rel-11/23_series/23066/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a6cae02e68ed522c9808aa3246a92faac8596a20cc297e8b078d81d94da4ff0 +size 96720 diff --git a/marked/Rel-11/23_series/23066/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-11/23_series/23066/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc10eccb63e26b7b7838c4ba693b9cd1a92afc73 --- /dev/null +++ b/marked/Rel-11/23_series/23066/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1196273005fb4d09df0c522b037e3b7381d561ef346679f75cae8cf4faa52dc7 +size 132056 diff --git a/marked/Rel-11/23_series/23066/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/Rel-11/23_series/23066/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..366b2e6de86884249d3861304a42cd6a738d604d --- /dev/null +++ b/marked/Rel-11/23_series/23066/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9ee2e9858abb948a23c4fba7c981b4a20b847b29e9c599de4efe1cc26942f5a +size 59309 diff --git a/marked/Rel-11/23_series/23066/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-11/23_series/23066/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d6957708285ae2dd23a9efdfb7456ae106b39d7 --- /dev/null +++ b/marked/Rel-11/23_series/23066/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8849ecd298dae8ac90032c25010c203beab6e5c4096da6f94d8a4cad3011d7b9 +size 95442 diff --git a/marked/Rel-11/23_series/23066/74d23510f27b21403a7be84820821863_img.jpg b/marked/Rel-11/23_series/23066/74d23510f27b21403a7be84820821863_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4ce62ef84bb319e49f736068eaacbdd31f2559c --- /dev/null +++ b/marked/Rel-11/23_series/23066/74d23510f27b21403a7be84820821863_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb89af89aa23e7cadbf90feea931edac5d704329f82d33ca724aa103baaae28f +size 87628 diff --git a/marked/Rel-11/23_series/23066/76d19e4271bf243b20d55a98efd51483_img.jpg b/marked/Rel-11/23_series/23066/76d19e4271bf243b20d55a98efd51483_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfec6dd3bfc1f964f1019b38d50c7e97236ab31e --- /dev/null +++ b/marked/Rel-11/23_series/23066/76d19e4271bf243b20d55a98efd51483_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52edb2600d1f2fc291bef2bfd0c8c3c2325893966738bd155096359fc0399cd1 +size 42934 diff --git a/marked/Rel-11/23_series/23066/7722d62e33dcc894cc8555e9474c5606_img.jpg b/marked/Rel-11/23_series/23066/7722d62e33dcc894cc8555e9474c5606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5cba1112f85f4720afeaca468527acabed1d574 --- /dev/null +++ b/marked/Rel-11/23_series/23066/7722d62e33dcc894cc8555e9474c5606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04caefc38bea8312c94062c3710b00f71e271419cc6c3e77e40b47c0f4367877 +size 51151 diff --git a/marked/Rel-11/23_series/23066/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/23_series/23066/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec572a833eae079adcf95774089fe1e87082c925 --- /dev/null +++ b/marked/Rel-11/23_series/23066/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58e26ca08f326f5bc4bec2d03dd0fede7c3ca17739c67853af387d6a611d1028 +size 65862 diff --git a/marked/Rel-11/23_series/23066/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg b/marked/Rel-11/23_series/23066/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e329213d93cbe0fb9d84c9380529b97084e43cd --- /dev/null +++ b/marked/Rel-11/23_series/23066/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:966d6ab2f663d1b7c42c37f5efa84ac62f3ae81df7d3bd96e0684b158191e1c9 +size 82664 diff --git a/marked/Rel-11/23_series/23066/805c475f0859e607af0530ba43194bf1_img.jpg b/marked/Rel-11/23_series/23066/805c475f0859e607af0530ba43194bf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1012158352ab6d5cba6551f792d47b5a9b5a11a4 --- /dev/null +++ b/marked/Rel-11/23_series/23066/805c475f0859e607af0530ba43194bf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d20ee4b420fb73db35da0e955e46e8b830d616cce41e1c80dd23d2f23a845056 +size 87130 diff --git a/marked/Rel-11/23_series/23066/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/23_series/23066/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9265d0bdae89a695cc30fb701176e12b7c4f74e --- /dev/null +++ b/marked/Rel-11/23_series/23066/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ce0c169e1688a584f14cfb5000aaad02fe6fda3e80ee6eb87e9ce9234890e0a +size 54592 diff --git a/marked/Rel-11/23_series/23066/8658cfab6a458b4a80ab2e384c61ff89_img.jpg b/marked/Rel-11/23_series/23066/8658cfab6a458b4a80ab2e384c61ff89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55c8ada8852c3b637a7eb9271748de982c24828d --- /dev/null +++ b/marked/Rel-11/23_series/23066/8658cfab6a458b4a80ab2e384c61ff89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00be89473a2142f6b488bc7e83f536c144db5668f3857f04daa8c0c3edb71938 +size 105192 diff --git a/marked/Rel-11/23_series/23066/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/23_series/23066/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5e7b1e571070c35870714c910c4b8d261a7d282 --- /dev/null +++ b/marked/Rel-11/23_series/23066/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6856262ea596e89f52b998c14e591cfc492a9e0fdfd396e2f1337619c1484f01 +size 29770 diff --git a/marked/Rel-11/23_series/23066/9b9262a549828579ab904148450734f6_img.jpg b/marked/Rel-11/23_series/23066/9b9262a549828579ab904148450734f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faa7b9629519b2cf7f2753a4f31424d0d7f3063a --- /dev/null +++ b/marked/Rel-11/23_series/23066/9b9262a549828579ab904148450734f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d6cd7d26cb746f3ea5aafbf553b29bbd3483848bebd104274f822df326af0aa +size 74152 diff --git a/marked/Rel-11/23_series/23066/9cb54072e43a6b6717eb16036a7640a2_img.jpg b/marked/Rel-11/23_series/23066/9cb54072e43a6b6717eb16036a7640a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..297905bf721f4e3742ebb60516a74b0b17d31c1d --- /dev/null +++ b/marked/Rel-11/23_series/23066/9cb54072e43a6b6717eb16036a7640a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36c3f753409d5398051ff3adae6145c19e61f234da9e35dfeebae7c18fcda786 +size 26157 diff --git a/marked/Rel-11/23_series/23066/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-11/23_series/23066/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d76aaf1da0133ee06e431e5336e238fa602d8074 --- /dev/null +++ b/marked/Rel-11/23_series/23066/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1f67c0acc2038b9f2bf2b47dbbbfebaf80c48546f121ae75f7fcbdd8c962981 +size 57691 diff --git a/marked/Rel-11/23_series/23066/9f50279046b74a4e66a1a0144c3b1d11_img.jpg b/marked/Rel-11/23_series/23066/9f50279046b74a4e66a1a0144c3b1d11_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f96bbf26bfc229254b014f8eb2062a799f9f368 --- /dev/null +++ b/marked/Rel-11/23_series/23066/9f50279046b74a4e66a1a0144c3b1d11_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db11bfb282c9dc1eea431bdec6dc7fe77e2366160ddaf29f3f726032a943196d +size 90069 diff --git a/marked/Rel-11/23_series/23066/a47713c2491e6ce619259ed2f196fd24_img.jpg b/marked/Rel-11/23_series/23066/a47713c2491e6ce619259ed2f196fd24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2604893a951a5426361de96e207289d535d3cf36 --- /dev/null +++ b/marked/Rel-11/23_series/23066/a47713c2491e6ce619259ed2f196fd24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6dccf325adad7811baf7131e067516a00a3824237a5c237f19ca55936528a18 +size 64699 diff --git a/marked/Rel-11/23_series/23066/aa6e28822419dba9f22129fee66c9c4c_img.jpg b/marked/Rel-11/23_series/23066/aa6e28822419dba9f22129fee66c9c4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e941a9cb320cca6b96aacf829260d44bbbdc5bfd --- /dev/null +++ b/marked/Rel-11/23_series/23066/aa6e28822419dba9f22129fee66c9c4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b23e49bee745e50849f5aada5056e7120f7660edd89c1254011b562cabda0722 +size 55606 diff --git a/marked/Rel-11/23_series/23066/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/23_series/23066/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab7e5b5822b21a68599afdf230f974b478378289 --- /dev/null +++ b/marked/Rel-11/23_series/23066/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bb06daab11273fe11ad2be55fd35fd662d8cc9ec6ccc85f600af7150ba31511 +size 56880 diff --git a/marked/Rel-11/23_series/23066/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/23_series/23066/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfc8c50a6c8e011c6396c117433578cc72ea7482 --- /dev/null +++ b/marked/Rel-11/23_series/23066/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f06143da367f6e9c54a904d857ccc38c773f802528f17e216a1f4ce6cdf385a +size 103336 diff --git a/marked/Rel-11/23_series/23066/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-11/23_series/23066/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c720f1f5d3ad2a6e39e3de7c211b236257abab6b --- /dev/null +++ b/marked/Rel-11/23_series/23066/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e17903c564b88ce2cefe589e03dea6e7aa6f7557a051e19290e6eebe43023e8c +size 123907 diff --git a/marked/Rel-11/23_series/23066/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/marked/Rel-11/23_series/23066/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52fd5ffe74902316a5ed052e1fb0270f92f93ff4 --- /dev/null +++ b/marked/Rel-11/23_series/23066/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd44e260c90309c05c7074ccff0325242572456e663616652753170b55c8c221 +size 47282 diff --git a/marked/Rel-11/23_series/23066/c0c7f65c51c83fbe595b47326f6b089a_img.jpg b/marked/Rel-11/23_series/23066/c0c7f65c51c83fbe595b47326f6b089a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d875c014057be8f535c3b83d454abb32ff0e7a0 --- /dev/null +++ b/marked/Rel-11/23_series/23066/c0c7f65c51c83fbe595b47326f6b089a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77f60b0bd3b91c2b0b2eaabc73217ef8697932dc717f8550c1b568baec406c2e +size 69731 diff --git a/marked/Rel-11/23_series/23066/c419b566d720267c499087add1506018_img.jpg b/marked/Rel-11/23_series/23066/c419b566d720267c499087add1506018_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9361750b282aeead10ad123fe2202075db37b650 --- /dev/null +++ b/marked/Rel-11/23_series/23066/c419b566d720267c499087add1506018_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edc6ead628cae36cc0c6832b5df0e21094d6244fc35af3c858048474f02083ab +size 36140 diff --git a/marked/Rel-11/23_series/23066/c649cad02e45d7d9a16f3f5bdb332219_img.jpg b/marked/Rel-11/23_series/23066/c649cad02e45d7d9a16f3f5bdb332219_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28b18b315d4919463f8a9020440b8f43e0413778 --- /dev/null +++ b/marked/Rel-11/23_series/23066/c649cad02e45d7d9a16f3f5bdb332219_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9642c7684a132e6a44fb0f0a09163ae6f9dab5f10804212472f2b33aa88cef97 +size 51310 diff --git a/marked/Rel-11/23_series/23066/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Rel-11/23_series/23066/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7736ff89bc6c41011f9bbed0026888a7b64d30ff --- /dev/null +++ b/marked/Rel-11/23_series/23066/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9568fd8c3ee054deece227238f631ea329eb9b6df67d88512b62c2c45453ea4 +size 90079 diff --git a/marked/Rel-11/23_series/23066/d9cfc30025244dcd75766061f27ee09f_img.jpg b/marked/Rel-11/23_series/23066/d9cfc30025244dcd75766061f27ee09f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddd9bb55b89466571cf58a0803dc9726f4b6becd --- /dev/null +++ b/marked/Rel-11/23_series/23066/d9cfc30025244dcd75766061f27ee09f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44ad293641a7d9030869c9cbafd891c5cfbedb1bc64cbd5607e0a7fcf5cc76ec +size 85571 diff --git a/marked/Rel-11/23_series/23066/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/23_series/23066/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4881a55f7c72f6847c6f8b3c6553877bf3b680c9 --- /dev/null +++ b/marked/Rel-11/23_series/23066/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccf1839aa5260fe93c1d9bb9731bdb970d78da3ab92dd649a6798247f1fa4401 +size 70585 diff --git a/marked/Rel-11/23_series/23066/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/23_series/23066/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..285ce89aee32c1c2b371fdde236c8de310eb6284 --- /dev/null +++ b/marked/Rel-11/23_series/23066/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85614e4956cab1a9812ef5613315204934703110f2b1fe3452defddd49bf7994 +size 75027 diff --git a/marked/Rel-11/23_series/23066/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/marked/Rel-11/23_series/23066/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed71a39f29b99f17c4863045cede9d25b7700f85 --- /dev/null +++ b/marked/Rel-11/23_series/23066/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0ffdd533c874e98e785d9bc9c75003c72126518d5f21aee6be61ccb1da6d053 +size 53112 diff --git a/marked/Rel-11/23_series/23066/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/Rel-11/23_series/23066/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca2debc8859280a4c42f468a5dcc4f8480825514 --- /dev/null +++ b/marked/Rel-11/23_series/23066/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67c7359d52e52bab9f14e6f0671569b1956bb8c46d3e31ec3006f968b250e4d2 +size 100878 diff --git a/marked/Rel-11/23_series/23066/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-11/23_series/23066/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f06f55d834185a02381a8628f4b6877649006e69 --- /dev/null +++ b/marked/Rel-11/23_series/23066/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:623d79e10a3547e5b7c0cb6d9eb0f0c2bab31f9184e1a8e5d55475d37755cb85 +size 158110 diff --git a/marked/Rel-11/23_series/23066/raw.md b/marked/Rel-11/23_series/23066/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fac5b08428524643382726484ebfe830da18679b --- /dev/null +++ b/marked/Rel-11/23_series/23066/raw.md @@ -0,0 +1,2553 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 General..... | 9 | +| 4.1 Overview ..... | 9 | +| 4.2 Compatibility..... | 10 | +| 4.3 Common Functionality of the MNP-SRF ..... | 11 | +| 5 Common Architecture for call setup..... | 14 | +| 6 Functional requirements of network entities..... | 16 | +| 6.1 Procedure MNP_MT_GMSC_Set_MNP_Parameters ..... | 16 | +| 6.2 Procedure MNP_MT_GMSC_Check_MNP_Indicators..... | 17 | +| 6.3 Procedure MNP_SRF_Check_MNP_Indicator..... | 18 | +| <b>Annex A (normative): IN Call-Related Technical Realisation .....</b> | <b>19</b> | +| A.1 Architecture..... | 19 | +| A.1.1 Network Options ..... | 19 | +| A.1.2 No NP Query required – Number is not subject for portability ..... | 19 | +| A.1.3 NP Query in Number Range Holder Network ..... | 20 | +| A.1.3.1 TQoD – Number is not ported..... | 20 | +| A.1.3.2 TQoD – Number is ported..... | 21 | +| A.1.3.3 QoHR – Number is ported..... | 22 | +| A.1.4 NP Query in Originating Network ..... | 23 | +| A.1.4.1 OQoD – Number is not ported ..... | 23 | +| A.1.4.2 OQoD – Number is ported ..... | 24 | +| A.1.4.3 IN-Query for CAMEL pre-paid service ..... | 25 | +| A.2 Information flows..... | 27 | +| A.3 Functional requirements of network entities..... | 33 | +| A.3.1 Functional requirement of GMSC..... | 33 | +| A.3.1.1 Procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR..... | 33 | +| A.3.1.2 Procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD..... | 35 | +| A.3.2 Functional requirement of MSC..... | 36 | +| A.3.2.1 Procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD ..... | 36 | +| A.3.3 Functional requirement of NPDB ..... | 38 | +| A.3.3.1 Process IN_QUERY_NPDB ..... | 38 | +| A.4 Contents of messages..... | 39 | +| A.4.1 Messages on the ISUP interface..... | 39 | +| A.4.1.1 IAM for ETSI ISUP interface..... | 39 | +| A.4.1.2 IAM for ANSI ISUP interface..... | 39 | +| A.4.2 Messages on the MSC - NPDB interface..... | 39 | +| A.4.2.1 INITIAL DP ..... | 39 | +| A.4.2.2 INITIAL DP negative response..... | 40 | +| A.4.2.3 CONNECT ..... | 40 | +| A.4.2.4 CONTINUE..... | 40 | +| A.4.2.5 RELEASE CALL ..... | 40 | +| A.4.2.6 ProvideInstruction:Start ..... | 40 | +| A.4.2.7 ConnectionControl:Connect ..... | 41 | + +| | | | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| <b>Annex B (normative):</b> | <b>Handling of Non-Call Related Signalling.....</b> | <b>42</b> | +| B.1 | Handling of Non-call Related Signalling..... | 42 | +| B.1.1 | Routeing Conventions..... | 42 | +| B.1.2 | Network Architecture..... | 42 | +| B.2 | Signalling Scenarios..... | 44 | +| B.2.1 | Non-call Related Signalling Message for a Non-ported Number – Indirect Routeing..... | 44 | +| B.2.2 | Non-call Related Signalling Message for a Ported or Non-ported Number – Direct Routeing..... | 45 | +| B.2.3 | Non-call Related Signalling Message for a Ported Number - Indirect Routeing..... | 46 | +| B.3 | Functional Requirements of Network Entities..... | 46 | +| B.3.1 | Procedure MNP_SRF_Non_Call_Related..... | 46 | +| B.4 | Signalling Scenarios (informative) ..... | 49 | +| B.4.1 | Delivery of SMS to a Non-ported Number – Direct Routeing – MNP-SRF acts as SCCP Relay..... | 49 | +| B.4.2 | Delivery of SMS to a Non-ported Number - Direct Routeing – MNP-SRF acts as Higher-level Relay .. | 50 | +| B.4.3 | Delivery of SMS to a Ported Number – Indirect Routeing ..... | 51 | +| B.4.4 | Delivery of SMS to a Ported Number – Direct Routeing ..... | 51 | +| B.4.5 | International SOR for a Non-ported Number..... | 53 | +| B.4.6 | SOR for a Ported Number – Indirect Routeing ..... | 54 | +| B.4.7 | Any Time Interrogation for a Ported Number – Indirect Routeing..... | 55 | +| B.4.8 | Any Time Interrogation for a Ported Number – Direct Routeing ..... | 56 | +| B.4.9 | CCBS where the Busy Subscriber is a Ported Subscriber - Direct Routeing..... | 57 | +| B.4.10 | Calling Name Presentation Flows – MNP-SRF acts as SCCP Relay ..... | 58 | +| <b>Annex C (normative):</b> | <b>MNP Signalling Relay Function - Call Related Signalling.....</b> | <b>59</b> | +| C.1 | Handling of Call Related Signalling ..... | 59 | +| C.2 | Functional Requirements of Network Entities..... | 60 | +| C.2.1 | Procedure MNP_SRF_MATF_Call_Related..... | 60 | +| C.2.2 | Process SRI_NPLR ..... | 60 | +| C.2.3 | Procedure MNP_SRF_MATF_Info_Request ..... | 61 | +| C.2.4 | Process ATI_NPLR..... | 61 | +| C.3 | Call Scenarios ..... | 66 | +| C.3.1 | Call to a Non-Ported Number or Number Ported into the Network..... | 67 | +| C.3.2 | Call to a Ported Number – Originating Network = Subscription Network – Direct Routeing ..... | 68 | +| C.3.3 | Mobile Originated Call to a Ported or not known to be Ported Number – Originating Network<br>≠Subscription Network– Direct Routeing..... | 69 | +| C.3.4 | Call to a Ported Number – Indirect Routeing..... | 70 | +| C.3.5 | Call to a Ported Number – Indirect Routeing with Reference to Subscription Network ..... | 71 | +| C.3.6 | MNP Info Query - Direct Routeing..... | 72 | +| C.3.7 | MNP Info Query - Indirect Routeing ..... | 73 | +| C.4 | Information Flows..... | 74 | +| C.5 | Contents of the messages ..... | 79 | +| C.5.1 | Send Routeing Info..... | 80 | +| C.5.2 | Send Routeing Info ack..... | 80 | +| C.6 | Handling of MAP to ISUP mapping (informative)..... | 80 | +| C.6.1 | ETSI Mapping direction: ISUP to MAP ..... | 80 | +| C.6.2 | ETSI Mapping direction: MAP to ISUP ..... | 80 | +| C.6.3 | ANSI Mapping direction: ISUP to MAP ..... | 81 | +| C.6.4 | ANSI Mapping direction: MAP to ISUP ..... | 81 | +| <b>Annex D:</b> | <b>Void.....</b> | <b>82</b> | +| Annex E (informative): | Change history..... | 83 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3<sup>rd</sup> 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 several alternatives for the realisation of Mobile Number Portability. + +The present document includes information applicable to network operators, service providers, switch and database manufacturers and national regulators. + +It is left to operator and implementation decisions which option, or combination of options, is used, taking into account the regulatory and architectural constraints that may prevail. The possible implications of these options on internal node functions and on signalling performance are not covered in the present document. + +Normative Annex A of the present document describes the technical realisation of the handling of calls to ported UMTS or GSM mobile subscribers using IN technology. + +Normative Annex C of the present document describes the technical realisation of the handling of calls to ported UMTS or GSM mobile subscribers using Signalling Relay technology. + +Normative Annex A and Normative Annex C describe alternative solutions. The network operator may choose the solution to be used in his network. + +Normative Annex B of the present document describes the technical realisation of the handling of non-call related SCCP signalling for ported UMTS or GSM mobile subscribers using Signalling Relay technology. + +The present document does not specify the porting process. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 21.905: "3G Vocabulary". +- [2] 3GPP TS 22.066: "Support of Mobile Number Portability (MNP); Service description. Stage 1". +- [3] 3GPP TS 23.018: "Basic call handling; Technical realisation". +- [4] ETSI ETS 300 009 (1991): "Integrated Services Digital Network (ISDN); CCITT Signalling System No. 7 – Signalling Connection Control Part (SCCP) [connectionless services] to support international interconnection". +- [5] ETSI ETS 300 374-1: "Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 1: protocol specification". +- [6] ITU-T Recommendation Q.769.1; ISDN User Part (ISUP); Enhancements for the support of Number Portability". +- [7] ETSI EN 300 356-2 V4.1: "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 4 for the international interface; Part 2: ISDN supplementary services [ITU-T Recommendation Q.730 modified]". +- [8] CTIA report on Wireless Number Portability, Version 2.0.0. +- [9] ANSI T1.660 – 1998, American National Standards for Telecommunications – Signaling System Number 7 – NumberPortability Call Completion to a Portable Number. + +- [10] ANSI T1.111-1996, American National Standards for Telecommunication – Signalling System No. 7 (SS7) Message Transfer Part (MTP). + - [11] ANSI T1.112-1996, American National Standards for Telecommunication – Signalling System No. 7 (SS7) Signalling Connection Control Part (SCCP). +- Note: Translation Types 10 and 14 will be published in the next revision of ANSI T1.112. +- [12] American National Standard for Telecommunications – Signalling System Number 7 (SS7) - ISDN User Part (ISUP) - ANSI T1.113-1995. + - [13] American National Standard for Telecommunications - Signalling System Number 7 (SS7) – Transaction Capabilities Application Part (TCAP) - ANSI T1.114-1996. + - [14] ETSI EN 302 097 V1.2: "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP); Enhancements for support of Number Portability (NP)". + - [15] TI - Technical Requirements No. 3, April 1999, Number Portability Database and Global Title Translation. + - [16] 3GPP TS 23.096: "Mobile Name Identification Supplementary Service – Stage 2". + - [17] North American Numbering Council (NANC) Functional Requirement Specification, Number Portability Administration Center- Service Management System (NPAC-SMS), Version 1.0, May 25, 1995; Version 2.0, June 2, 1997. + - [18] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4 – Stage 2". +- + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**donor network:** subscription network from which a number is ported in the porting process. This may or may not be the number range holder network + +**interrogating network entity:** entity that submits a non-call related signalling message to interrogate the HLR + +**interrogating network:** network in which the interrogating network entity resides + +**mobile number portability:** ability for a mobile subscriber to change mobile network subscription within the same country whilst retaining his/her original MSISDN(s). Additional regulatory constraints apply in North America. + +**mobile number portability information:** an information set relevant to Mobile Number Portability for a mobile subscriber. It may contain one or more of Routeing Number, generic IMSI MSISDN, and Number Portability Status. + +**network operator:** GSM PLMN operator + +**non-call related signalling message:** all signalling messages where the MSISDN is used to route the message on SCCP level except MAP SRI without OR parameter set (i.e. SRI\_SMS, SRI for SOR, Send\_IMSI, CCBS\_Request etc) + +**North American GSM Number portability:** the ability for a subscriber to change subscription between North American GSM networks and other subscription networks within a regulated geographical area within North America. + +**number portability database:** operational database (used in real time at call set-up) which provides portability information + +**number portability location register:** internal MAP application terminating function (MATF) in the MNP-SRF network entity with an (unspecified) interface with a NPDB + +**number portability status:** information indicating the status of number portability for a mobile subscriber. It may be one of: own number ported out, own number not ported out, foreign number ported in, foreign number ported to a foreign network, foreign number not known to be ported + +**number range holder network:** network to which the number range containing the ported number has been allocated + +**originating network:** network where the calling party is located + +**portability domain:** set of GSM PLMNs in a country between which MSISDNs may be ported or a set of North American GSM Mobile networks and other subscription networks within a regulated geographical area within North America + +**portability network:** a PLMN or ,in North America, a PSTN or an ISDN network + +**portable number:** E.164 number that can be ported between networks in one nation + +**ported number:** portable number that has undergone the porting process + +**ported subscriber:** subscriber of a ported number + +**porting process:** description of the transfer of a number between network operators + +**recipient network:** network that receives the number in the porting process. This network becomes the subscription network when the porting process is complete + +**routeing number:** routeing number is the data stored against the ported number or the non-ported number in the Number Portability Database. The routeing number points to Subscription Network or Recipient Network + +**service key:** service Key can identify to the entity holding the Number Portability Database that the service logic for Mobile Number Portability should apply. The Service Key value for Mobile Number Portability is administered in the MSC, and is passed transparently to the entity holding the Number Portability Database + +**service provider:** entity that offers service subscriptions to individual subscribers and contracts with a network operator to implement services for a specific MSISDN. A service provider may contract with more than one network operator + +**service provider portability:** transfer of numbers between two unique Service Providers + +**subscription network:** network with which the customer's Service Provider has a contract to implement the customer's services for a specific MSISDN + +NOTE: The term “recipient network” is used during the porting process. The recipient network becomes the “subscription network” after the completion of the porting process. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|----------------------------------------------| +| CCBS | Call Completion on Busy Subscriber | +| CCF | Call Completion Function | +| CdPA | Called Party Address | +| CgPA | Calling Party Address | +| CNAP | Calling Name Presentation | +| CNDB | Calling Name Database | +| CRMNP | Call Related Mobile Number Portability | +| FCI | Forward Call Indicator | +| GAP | Generic Address Parameter | +| GMSC | Gateway MSC | +| GMSCB | The GMSC in HPLMNB | +| GTT | Global Title Translation | +| HLR | Home Location Register | +| HPLMNB | The subscription network of the B subscriber | +| IAM | Initial Address Message | +| IDP | Initial Detection Point | +| IE | Information Element | +| INE | Interrogating Network Entity | +| IF | Information Flow | +| IPLMN | Interrogating PLMN | +| MATF | MAP application Terminating Function | +| MNP | Mobile Number Portability | + +| | | +|---------|-----------------------------------------------------| +| MNP-SRF | Signalling Relay Function for support of MNP | +| MSA | Mobile Station of the A subscriber | +| MSB | Mobile Station of the B subscriber | +| MSC | Mobile-services Switching Centre | +| MSISDN | Mobile Station International ISDN Number | +| MSRN | Mobile Station Roaming Number | +| NANP | North American Numbering Plan | +| NAGNP | North American GSM Number Portability | +| NPDB | Number Portability Database | +| NPLMN | The number range holder network of the B subscriber | +| NPLR | Number Portability Location Register | +| OQoD | Originating call Query on Digit Analysis | +| PLMN | Public Land Mobile Network | +| QoHR | Query on HLR Release | +| RN | Routeing Number | +| SMS | Short Message Service | +| SOR | Support of Optimal Routeing | +| SRI | Send Routeing Information | +| STP | Signalling Transfer Point | +| TQoD | Terminating call Query on Digit Analysis | +| TT | Translation Type | +| VMSC | The Visited MSC | +| VMSB | The VMSC of the B subscriber | + +Further GSM related abbreviations are given in 3GPP TS 21.905: "3G Vocabulary". + +# 4 General + +## 4.1 Overview + +Mobile Number Portability (MNP) is the ability for a UMTS or GSM mobile subscriber to change the subscription network within a portability domain whilst retaining her original MSISDN or MSISDNs. + +North American GSM Number Portability (NAGNP) is the ability for a subscriber to change subscription between North American GSM networks and other subscription networks within a regulated geographical area within North America. + +As part of the porting process administrative actions have to be performed by the network operators of the number range holder network, donor network, recipient network and, as an option, by operators of other national UMTS or GSM networks as follows: + +### **a) if the number range holder network is identical with the donor network:** + +| | | +|-------------------------------------------|----------------------------------------------------------------------------------------------------------------| +| Recipient network: | add an entry in the HLR;<br>add an entry in the Number Portability Database. | +| Donor network: | add an entry in the Number Portability Database;<br>delete the entry related to the ported MSISDNs in the HLR. | +| Other networks in the portability domain: | add an entry in the Number Portability Database (if direct routeing is used). | + +### **b) if the number range holder network is identical with the recipient network:** + +| | | +|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| Recipient network: | add an entry in the HLR;<br>delete any entry related to the ported MSISDN in the Number Portability Database. | +| Donor network: | delete any entry related to the ported MSISDN in the Number Portability Database;<br>delete the entry related to the ported MSISDNs in the HLR. | +| Other networks in the portability domain: | delete any entry related to the ported MSISDN in the Number Portability Database. | + +### **c) if the number range holder network is different from both the recipient and the donor network:** + +| | | +|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| Recipient network: | add an entry in the HLR;<br>add an entry in the Number Portability Database. | +| Number range holder network: | update the Number Portability Database | +| Donor network: | delete (or update) the entry in the Number Portability Database;<br>delete the entry related to the ported MSISDNs in the HLR. | +| Other networks in the portability domain: | update the Number Portability Database (if an entry for the ported MSISDN exists). | + +Note that the order of sequence for the administrative actions to be performed both within a network and by different network operators is significant with respect to prevention of disruption in service to the mobile subscriber and prevention of looping calls between networks during the porting process. + +Termination of a subscription for a ported number results in the deletion of any entry in an HLR and NPDB of that number. + +If a call fails because databases are not correctly synchronised, the network entity that detects the inconsistency will raise an MNP specific alarm to the operation and maintenance subsystem. + +The present document does not specify the porting process. It specifies the functionality needed to set-up calls to both ported and non ported subscribers including the functionality needed to query an NPDB for MNP information (in order to be able to charge correctly for CAMEL pre-paid calls and SMS) (Normative Annex A and Normative Annex C), and the functionality needed to relay non-call related signalling messages to the HLR in the subscription network (Normative Annex B). + +## 4.2 Compatibility + +The IAM sent to the subscription network may contain additional routeing information. Within a portability domain the method how to convey the Routeing Number in the IAM between two portability networks shall be agreed upon by the two network operators involved (for an ITU-T ISUP solution see [6] and for an ANSI ISUP solution see [8] and [9]). + +In general, IN-based and MNP-SRF (call-related) solutions are compatible and may coexist in the same portability domain. The only restriction refers to the case where the number range holder network relays call-related MAP messages (i.e. SRI for national calls) to the subscription network. If this solution is selected by at least one network operator within a portability domain, all the portability networks and transit networks affected must fulfil the following requirements: + +1. The SCCP interfaces between networks in a portability domain must be agreed. This refers to the SCCP addressing mechanism being used (e.g. number lengths, natures of address and translation types for call-related MAP messages). +For messages that do not cross network boundaries the SCCP addressing mechanism is a choice of the network operator. +2. The subscription network must be able to generate the SRI ack to allow the onward routeing of the call from the number range holder network to the subscription network. + +In the rest of the possible architectures for MNP, no interworking problems have been identified. In these cases, network architectures used within one portability network (e.g. IN, MNP-SRF) are regarded as operator dependent. + +In order to avoid loops and incompatibility situations, all the networks within a portability domain shall use the same routeing convention either direct routeing, indirect routeing or indirect routeing with reference to the Subscription network. As an alternative, indirect routeing can interwork successfully with direct routeing if the routeing number is transferred in the IAM or if dedicated traffic connections are used. + +## 4.3 Common Functionality of the MNP-SRF + +In a PLMN that supports mobile number portability, SCCP messages sent to an HLR may be relayed by an MNP-SRF. Depending on the implemented solution (IN-based or MNP-SRF-based), on the type of message (call-related, non-call-related or MNP information request) and on the porting status of the called subscriber, the MNP-SRF may modify the SCCP called party address and route the message to a different HLR or to the subscription network, or terminate the dialogue and response to the INE. + +Figure 1 shows the general steering functionality for SCCP message routeing. It shows the SCCP routeing principle for mobile number portability within a network. + +Note that call related messages in the IN-based solution are not routed to the MNP-SRF. Therefore Normative Annex A of the present document does not mention the MNP-SRF. + +However, the usage of the IN-based solution for the call-related messages should allow operators to have the routeing of the non call-related messages determined in the same database. See [7] for the description of the access of the MNP-SRF (node with relay capability) to the NPDB (external database). + +In order to guard against the possibility that the porting data for an MSISDN is inconsistent between PLMNs in a porting domain, the SCCP hop counter may be used to prevent indefinite looping of messages between PLMNs. The MNP-SRF would then decrement the SCCP hop counter for every message that is relayed. It should be noted that the use of the SCCP hop counter requires the use of non segmented SCCP XUDT messages as defined in ITU-T 1996 SCCP recommendations or in the ANSI T1.112-1996 SCCP recommendations for North America, reference [11]. + +![Flowchart titled 'Process SCCP_Steering_Function' (1(1)) showing SCCP message routing logic. It starts with 'Idle', followed by 'SCCP message', then an 'OPTION' block. The 'OPTION' block branches into 'IN-based' and 'MNP-SRF-based' paths. The 'IN-based' path includes a 'call related' decision leading to either 'to HLR' or 'to MNP-SRF', both ending in 'Idle'. The 'MNP-SRF-based' path leads directly to 'to MNP-SRF' and then 'Idle'. A note indicates this is a 'general Steering Function for SCCP routeing'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> SCCP1[SCCP message]; SCCP1 --> OPTION{OPTION}; OPTION -- IN-based --> CR{call related}; OPTION -- MNP-SRF-based --> SCCP2[SCCP message]; CR -- yes --> SCCP3[SCCP message]; CR -- no --> SCCP4[SCCP message]; SCCP3 --> HLR[to HLR]; HLR --> Idle2([Idle]); SCCP4 --> MNP_SRF1[to MNP-SRF]; MNP_SRF1 --> Idle3([Idle]); SCCP2 --> MNP_SRF2[to MNP-SRF]; MNP_SRF2 --> Idle4([Idle]); +``` + +Flowchart titled 'Process SCCP\_Steering\_Function' (1(1)) showing SCCP message routing logic. It starts with 'Idle', followed by 'SCCP message', then an 'OPTION' block. The 'OPTION' block branches into 'IN-based' and 'MNP-SRF-based' paths. The 'IN-based' path includes a 'call related' decision leading to either 'to HLR' or 'to MNP-SRF', both ending in 'Idle'. The 'MNP-SRF-based' path leads directly to 'to MNP-SRF' and then 'Idle'. A note indicates this is a 'general Steering Function for SCCP routeing'. + +**Figure 1: Steering Function for SCCP Message routeing** + +Figure 2 shows the process MNP\_SRF in the MNP-SRF. The procedures MNP\_SRF\_MATF\_Call\_Related, MNP\_SRF\_Non\_Call\_Related and MNP\_SRF\_MATF\_Info\_Request are described in Normative Annex C and Normative Annex B of the present document. Note that in networks which support the IN-based solution for call related signalling, a distinction on SCCP level for call related and non-call related messages is needed and that the MNP-SRF does not require to include MATF's since call related messages and MNP information request messages are not terminated at the MNP-SRF. + +The test “MNP info-request” is a test on the SCCP Translation Type if a dedicated Translation Type value for MNP information request messages is used in the network. The handling of SCCP messages in the MNP-SRF in networks which do not make use of a dedicated Translation Type value for MNP information request messages is for further study. + +The test "call-related" is a test on the SCCP Translation Type if a dedicated Translation Type value for call related messages is used in the network. The handling of SCCP messages in the MNP-SRF in networks which do not make use of a dedicated Translation Type value for call related messages is for further study. + +![Flowchart for Process MNP_SRF. It starts with an IDLE state, followed by an SCCP message input. A decision 'MNP info request' follows. If 'yes', it goes to a process block 'MNP_SRF_MATF_Info_Request' (see Annex C) and returns to IDLE. If 'no', it goes to a 'call-related' decision. If 'yes', it goes to a process block 'MNP_SRF_MATF_Call_Related' (see Normative Annex C), then a 'terminate?' decision. If 'yes', it goes to IDLE; if 'no', it outputs an SCCP message and returns to IDLE. If 'no' from 'call-related', it goes to a process block 'MNP_SRF_Non_Call_Related' (see Annex B), then a 'terminate?' decision. If 'yes', it goes to IDLE; if 'no', it outputs an SCCP message and returns to IDLE.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +**Process MNP\_SRF** 1(1) + +Process in the MNP\_SRF to relay SCCP messages + +``` +graph TD; Start([ ]) --> IDLE1([IDLE]); IDLE1 --> SCCP1{{SCCP message}}; SCCP1 --> MNP_Req{MNP info request}; MNP_Req -- yes --> MNP_Req_Proc[MNP_SRF_MATF_Info_Request]; MNP_Req_Proc --> AnnexC[see Annex C]; AnnexC --> IDLE2([IDLE]); MNP_Req -- no --> CallRel{call-related}; CallRel -- yes --> CallRel_Proc[MNP_SRF_MATF_Call_Related]; CallRel_Proc --> NormAnnexC[see Normative Annex C]; CallRel_Proc --> Terminate1{terminate?}; Terminate1 -- yes --> IDLE3([IDLE]); Terminate1 -- no --> SCCP2{{SCCP message}}; SCCP2 --> IDLE4([IDLE]); CallRel -- no --> NonCallRel_Proc[MNP_SRF_Non_Call_Related]; NonCallRel_Proc --> AnnexB[see Annex B]; NonCallRel_Proc --> Terminate2{terminate?}; Terminate2 -- yes --> IDLE5([IDLE]); Terminate2 -- no --> SCCP3{{SCCP message}}; SCCP3 --> IDLE6([IDLE]); +``` + +Flowchart for Process MNP\_SRF. It starts with an IDLE state, followed by an SCCP message input. A decision 'MNP info request' follows. If 'yes', it goes to a process block 'MNP\_SRF\_MATF\_Info\_Request' (see Annex C) and returns to IDLE. If 'no', it goes to a 'call-related' decision. If 'yes', it goes to a process block 'MNP\_SRF\_MATF\_Call\_Related' (see Normative Annex C), then a 'terminate?' decision. If 'yes', it goes to IDLE; if 'no', it outputs an SCCP message and returns to IDLE. If 'no' from 'call-related', it goes to a process block 'MNP\_SRF\_Non\_Call\_Related' (see Annex B), then a 'terminate?' decision. If 'yes', it goes to IDLE; if 'no', it outputs an SCCP message and returns to IDLE. + +Figure 2: Process MNP\_SRF + +# 5 Common Architecture for call setup + +Figure 3 shows the general architecture of a portability domain for routing of calls. The more detailed architecture within the networks depends on the chosen solution (IN-based or MNP/SRF-based) and options and is described in Normative Annex A and Normative Annex C of the present document. + +The architecture for non-call related signalling is described in Normative Annex B of the present document. + +![Figure 3: General architecture of a portability domain for routing of calls. The diagram shows a 'Portability domain' containing three network types: 'Number range holder network', 'Subscription network', and 'Other national network'. Arrows indicate call routing paths: IAM(1) enters from the left; IAM(2) goes from 'Other national network' to 'Number range holder network'; IAM(3) goes from 'Number range holder network' to 'Subscription network'; SRI(4) goes from 'Number range holder network' to 'Subscription network'; SRI ack(5) goes from 'Subscription network' to 'Number range holder network'; IAM(6) goes from 'Number range holder network' to 'Subscription network'; IAM(7) goes from 'Subscription network' to 'Other national network'; and IAM(8) exits to the right.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +Figure 3: General architecture of a portability domain for routing of calls. The diagram shows a 'Portability domain' containing three network types: 'Number range holder network', 'Subscription network', and 'Other national network'. Arrows indicate call routing paths: IAM(1) enters from the left; IAM(2) goes from 'Other national network' to 'Number range holder network'; IAM(3) goes from 'Number range holder network' to 'Subscription network'; SRI(4) goes from 'Number range holder network' to 'Subscription network'; SRI ack(5) goes from 'Subscription network' to 'Number range holder network'; IAM(6) goes from 'Number range holder network' to 'Subscription network'; IAM(7) goes from 'Subscription network' to 'Other national network'; and IAM(8) exits to the right. + +**Figure 3: General architecture of a portability domain for routing of calls** + +The following routing conventions are identified: + +1. Direct Routing of calls is a PLMN option that allows to route calls directly from the PLMN supporting this option to the ported subscriber's subscription network. +2. Indirect Routing of calls is a PLMN option which allows to route calls from the PLMN supporting this option via the number range holder network to the ported subscriber's subscription network. +3. Indirect Routing of calls with reference to the subscription network is a PLMN option for PLMN operators having chosen the MNP-SRF solution for call related signalling described in Normative Annex C. If all PLMNs within a portability domain support this option, calls are routed from the originating network to the number range holder network. The number range holder network obtains onward routing information from the subscription network and routes the call onward to the ported subscriber's subscription network. + +The following action in the different networks can be identified: + +1. If the call is originated outside the portability domain, the IAM (1) is received by the number range holder network. +- 2a. If the call is originated in another national network and the other national network does not support originating call query (i.e. Indirect Routing of calls is applicable), the IAM (2) is received by the number range holder network. +- 2b. If the call is originated in another national network and the other national network supports originating call query (i.e. Direct Routing of calls is applicable), the IAM (7) containing the routing number is sent to the + +subscription network. If the routeing number is not used in the IAM sent from the national originating network to the subscription network, all transit networks involved are required to look up an NPDB in order to retrieve routeing information to route the call to the subscription network without looping. + +- 3a. If the call is originated in the subscription network and the subscription network does not support originating call query (i.e. Indirect Routeing of calls is applicable), the IAM (3) is received by the number range holder network. +- 3b. If the call is originated in the subscription network and the subscription network supports originating call query (i.e. Direct Routeing of calls is applicable), it sends an IAM (8) containing the MSRN to the visited network of the called subscriber. +- 3c. If the subscription network receives IAM (6 or 7) containing the routeing number, it sends an IAM (8) containing the MSRN to the visited network of the called subscriber. +- 4a. If the call is routed via the number range holder network, and the number range holder network supports the MNP-SRF/MATF solution with the option 'MATF in subscription network' described in Normative Annex C of the present document (i.e. Indirect Routeing of calls with reference to the subscription network is applicable), the number range holder network sends SRI (4) to the subscription network. The subscription network returns SRI ack (5) containing the routeing number. The number range holder network then sends IAM (6) containing the routeing number to the subscription network. If the routeing number is not used in the IAM sent from the number range holder network to the subscription network, all transit networks involved are required to look up an NPDB in order to retrieve routeing information to route the call to the subscription network without looping. +- 4b. If the call is routed via the number range holder network, and the number range holder network supports the IN solution described in Normative Annex A of the present document or the MNP-SRF/MATF solution with the option 'MATF inside number range holder network' described in Normative Annex C of the present document, the number range holder network sends IAM (6) containing the routeing number to the subscription network. + +# 6 Functional requirements of network entities + +## 6.1 Procedure MNP\_MT\_GMSC\_Set\_MNP\_Parameters + +The procedure MNP\_MT\_GMSC\_Set\_MNP\_Parameters is shown in figure 4. It is called from the process MT\_GMSC defined in 3G TS 23.018 [3]. + +![Flowchart for Procedure MNP_MT_GMSC_Set_MNP_Parameters](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +Procedure MNP\_MT\_GMSC\_Set\_MNP\_Parameters 1(1) + +``` +graph TD; Start([ ]) --> Decision{ }; Decision -- No --> End(( )); Decision -- Yes --> Process[Mark NPDB query done]; Process --> End; +``` + +The flowchart illustrates the procedure MNP\_MT\_GMSC\_Set\_MNP\_Parameters. It begins with a start symbol (a circle with a vertical line), leading to a decision diamond. The decision diamond is labeled 'IAM parameters indicate that NPDB query has been done'. If the answer is 'No', the flow proceeds directly to the end symbol (a circle with an 'X'). If the answer is 'Yes', the flow proceeds to a process box labeled 'Mark NPDB query done', which then leads to the end symbol. + +Flowchart for Procedure MNP\_MT\_GMSC\_Set\_MNP\_Parameters + +Figure 4: Procedure MNP\_MT\_GMSC\_Set\_MNP\_Parameters + +## 6.2 Procedure MNP\_MT\_GMSC\_Check\_MNP\_Indicators + +The procedure MNP\_MT\_GMSC\_Check\_MNP\_Indicators is shown in figure 5. It is called from the process MT\_GMSC defined in 3G TS 23.018 [3]. + +![Flowchart for Procedure MNP_MT_GMSC_Check_MNP_Indicators. It starts with a connector, followed by an OPTION block for 'NPDB query check supported'. If 'Yes', it goes to a decision 'NPDB query is marked done'. If 'Yes', result is 'Fail'; if 'No', result is 'Routeing number'. If 'No' from the OPTION block, it also leads to 'Routeing number'.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +Procedure MNP\_MT\_GMSC\_Check\_MNP\_Indicators 1(1) + +``` +graph TD; Start([ ]) --> OPTION{OPTION}; NPDB_query_check_supported[NPDB query check supported] --- OPTION; OPTION -- Yes --> NPDB_query_is_marked_done{NPDB query is marked done}; NPDB_query_check_supported --- NPDB_query_is_marked_done; NPDB_query_is_marked_done -- Yes --> Result_Fail[Result:= Fail]; NPDB_query_is_marked_done -- No --> Result_Routing_number[Result:= Routeing number]; OPTION -- No --> Result_Routing_number; Result_Fail --> End_Fail((X)); Result_Routing_number --> End_Routing_number((X)); +``` + +Flowchart for Procedure MNP\_MT\_GMSC\_Check\_MNP\_Indicators. It starts with a connector, followed by an OPTION block for 'NPDB query check supported'. If 'Yes', it goes to a decision 'NPDB query is marked done'. If 'Yes', result is 'Fail'; if 'No', result is 'Routeing number'. If 'No' from the OPTION block, it also leads to 'Routeing number'. + +Figure 5: Procedure MNP\_MT\_GMSC\_Check\_MNP\_Indicators + +## 6.3 Procedure MNP\_SRF\_Check\_MNP\_Indicator + +The procedure MNP\_SRF\_Check\_MNP\_Indicator is shown in figure 6. It is called from the procedures MNP\_SRF\_Non\_Call\_Related and MNP\_SRF\_MATF\_Call\_Related. + +![Flowchart for Procedure MNP_SRF_Check_MNP_Indicator. The process starts with a cylinder symbol, leading to a decision diamond labeled 'Check NPDB query in MNP-SRF?'. If 'no', it ends at an 'X' symbol. If 'yes', it leads to another decision diamond labeled 'previous NPDB query is done?'. If 'yes', it goes to a box 'set: terminate' and ends at an 'X' symbol. If 'no', it ends at an 'X' symbol.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +Procedure MNP\_SRF\_Check\_MNP\_Indicator 1(1) + +``` +graph TD; Start(( )) --> D1{Check NPDB query in MNP-SRF?}; D1 -- no --> X1(X); D1 -- yes --> D2{previous NPDB query is done?}; D2 -- yes --> T[set: terminate]; T --> X2(X); D2 -- no --> X3(X); +``` + +Flowchart for Procedure MNP\_SRF\_Check\_MNP\_Indicator. The process starts with a cylinder symbol, leading to a decision diamond labeled 'Check NPDB query in MNP-SRF?'. If 'no', it ends at an 'X' symbol. If 'yes', it leads to another decision diamond labeled 'previous NPDB query is done?'. If 'yes', it goes to a box 'set: terminate' and ends at an 'X' symbol. If 'no', it ends at an 'X' symbol. + +Figure 6: Procedure MNP\_SRF\_Check\_MNP\_Indicator + +# --- Annex A (normative): IN Call-Related Technical Realisation + +## A.1 Architecture + +### A.1.1 Network Options + +There are two IN-based solutions for querying the NPDB :- + +- i. ETSI Core INAP +- ii. ANSI IN Query. + +The following network operator options are defined for the MT calls in the GMSC: + +- Terminating call Query on Digit Analysis (TQoD); +- Query on HLR Release (QoHR). + +In a GSM network that supports the IN-based approach for call related MNP, each GMSC shall support at least one of these options. + +The following network operator option is defined for MO calls in VMSCA and for forwarded calls in the GMSC and VMSCB: + +- Originating call Query on Digit Analysis (OQoD). + +In a GSM network which supports the IN-based approach for call related MNP, it is a network operator decision, taking into account the regulatory and architectural constraints that may prevail, whether or not VMSCs and GMSCs support this option. + +The use of OQoD in transit switches in a PLMN while avoiding multiple database interrogations is for further study. + +The interworking between the CCF and the SSF for MNP is for further study. + +Note that for different number ranges different options may be chosen. + +An IN-based solution for querying the NPDB may also be used by the gsmSCF in order to be able to apply different charging tariffs for CAMEL pre-paid subscribers' calls or short messages established/sent when roaming in their home PLMN and directed to ported and non-ported mobile subscribers, depending on whether or not the called and the calling subscriber subscribe to the same PLMN. + +..... + +### A.1.2 No NP Query required – Number is not subject for portability + +Figure A.1.2 shows the architecture for a call to a number that is not subject for portability. This can be for several reasons like for example: + +- the national regulator has stipulated some number series as being non-portable or; +- in an initial phase only a limited amount of subscribers might port in certain number blocks and some operators might want to treat the call routeing according to traditional routeing plans without any change. + +![Diagram of a call to a non-ported number. It shows three network domains: (Inter)national Originating network, Number range holder/subscription network, and Visited network. The call flow is: 1. Call from Originating Exchange to GMSCB. 2. GMSCB sends SRI to HLRB. 3. HLRB sends MSRN request to VMSCB/VLRB. 4. VMSCB/VLRB returns MSRN to HLRB. 5. HLRB sends SRI ack to GMSCB. 6. GMSCB routes call to VMSCB/VLRB.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +graph LR + subgraph Originating_network [ (Inter)national Originating network ] + OE[Originating Exchange] + end + subgraph Number_range_holder [ Number range holder/subscription network ] + HLRB[(HLRB)] + GMSCB[GMSCB] + end + subgraph Visited_network [ Visited network ] + VMSCB_VLRB[VMSCB/VLRB] + end + OE -- 1 --> GMSCB + GMSCB -- 2 --> HLRB + HLRB -- 3 --> VMSCB_VLRB + VMSCB_VLRB -- 4 --> HLRB + HLRB -- 5 --> GMSCB + GMSCB -- 6 --> VMSCB_VLRB + +``` + +Diagram of a call to a non-ported number. It shows three network domains: (Inter)national Originating network, Number range holder/subscription network, and Visited network. The call flow is: 1. Call from Originating Exchange to GMSCB. 2. GMSCB sends SRI to HLRB. 3. HLRB sends MSRN request to VMSCB/VLRB. 4. VMSCB/VLRB returns MSRN to HLRB. 5. HLRB sends SRI ack to GMSCB. 6. GMSCB routes call to VMSCB/VLRB. + +**Figure A.1.2: Call to a non-ported number, no NP query required** + +- 1 From an Originating Exchange a call is set up to MSISDN. The call is routed to the Number range holder network being the Subscription network. +- 2 When GMSCB receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to the HLRB including the MSISDN in the request. +- 3 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered; +- 4 The MSC/VLRB returns an MSRN back to the HLRB. +- 5 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. +- 6 GMSCB uses the MSRN to route the call to VMSCB. + +### A.1.3 NP Query in Number Range Holder Network + +#### A.1.3.1 TQoD – Number is not ported + +Figure A.1.3.1 shows the architecture for a call where the Originating network has no knowledge whether the MSISDN is ported or not and uses the traditional routeing plans for routeing the call to the Number range holder network for further routeing decisions. + +![Diagram illustrating the call setup procedure for a non-ported number using TQoD. The diagram shows three network domains: (Inter)national Originating network, Number range holder/subscription network, and Visited network. The call flow is as follows: 1. Call from Originating Exchange to GMSCB. 2. GMSCB sends database query to NPDB. 3. NPDB responds to GMSCB. 4. GMSCB sends MAP SRI to HLRB. 5. HLRB requests MSRN from VMSCB/VLRB. 6. VMSCB/VLRB returns MSRN to HLRB. 7. HLRB responds to GMSCB. 8. GMSCB routes call to VMSCB/VLRB.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +graph LR + subgraph Originating_network ["(Inter)national Originating network"] + OE[Originating Exchange] + end + subgraph Number_range_holder ["Number range holder/subscription network"] + NPDB[(NPDB)] + HLRB[(HLRB)] + GMSCB[GMSCB] + end + subgraph Visited_network ["Visited network"] + VMSCB_VLRB[VMSCB/VLRB] + end + OE -- 1 --> GMSCB + GMSCB -- 2 --> NPDB + NPDB -- 3 --> GMSCB + GMSCB -- 4 --> HLRB + HLRB -- 5 --> VMSCB_VLRB + VMSCB_VLRB -- 6 --> HLRB + HLRB -- 7 --> GMSCB + GMSCB -- 8 --> VMSCB_VLRB + +``` + +Diagram illustrating the call setup procedure for a non-ported number using TQoD. The diagram shows three network domains: (Inter)national Originating network, Number range holder/subscription network, and Visited network. The call flow is as follows: 1. Call from Originating Exchange to GMSCB. 2. GMSCB sends database query to NPDB. 3. NPDB responds to GMSCB. 4. GMSCB sends MAP SRI to HLRB. 5. HLRB requests MSRN from VMSCB/VLRB. 6. VMSCB/VLRB returns MSRN to HLRB. 7. HLRB responds to GMSCB. 8. GMSCB routes call to VMSCB/VLRB. + +**Figure A.1.3.1: Call to a non-ported number using TQoD procedure** + +- 1 From an Originating Exchange a call is set up to MSISDN. The call is routed to the Number range holder network being the Subscription network. +- 2 When GMSCB receives the ISUP IAM, it will send a database query to the NPDB as a result of analysis of the received MSISDN. The MSISDN is included in the query to the NPDB. +- 3 The NPDB detects that the MSISDN is not ported and responds back to the GMSCB to continue the normal call setup procedure for MT calls. +- 4 The GMSCB requests routing information by submitting a MAP SRI to the HLRB, including the MSISDN in the request. +- 5 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber owning the MSISDN currently is registered. +- 6 The MSC/VLRB returns an MSRN back to the HLRB. +- 7 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. +- 8 GMSCB uses the MSRN to route the call to VMSCB. + +Note that the NPDB may be outside the number range holder network if a shared NPDB is used. + +#### A.1.3.2 TQoD – Number is ported + +Figure A.1.3.2 shows the architecture for a call where the Originating network has no knowledge whether the MSISDN is ported or not and uses the traditional routing plans for routing the call to the Number range holder network for further routing decisions. + +![Diagram of Figure A.1.3.2: Call to a ported number using TQoD procedure. The diagram shows four network domains: (International) Originating network, Number range holder network, Subscription network, and Visited network. The flow is: 1. Call from Originating Exchange to GMSCA in Number range holder network. 2. GMSCA sends database query to NPDB. 3. NPDB responds with routing number. 4. Call routed to GMSCB in Subscription network. 5. GMSCB sends MAP SRI to HLRB. 6. HLRB requests MSRN from VMSCB/VLRB in Visited network. 7. VMSCB/VLRB returns MSRN to HLRB. 8. HLRB responds to GMSCB. 9. GMSCB routes call to VMSCB/VLRB.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +graph LR + subgraph Originating_network [ (International) Originating network ] + OE[Originating Exchange] + end + subgraph Number_range_holder_network [ Number range holder network ] + NPDB[(NPDB)] + GMSCA[GMSCA] + end + subgraph Subscription_network [ Subscription network ] + HLRB[(HLRB)] + GMSCB[GMSCB] + end + subgraph Visited_network [ Visited network ] + VMSCB_VLRB[VMSCB/VLRB] + end + + OE -- 1 --> GMSCA + GMSCA -- 2 --> NPDB + NPDB -- 3 --> GMSCA + GMSCA -- 4 --> GMSCB + GMSCB -- 5 --> HLRB + HLRB -- 6 --> VMSCB_VLRB + VMSCB_VLRB -- 7 --> HLRB + HLRB -- 8 --> GMSCB + GMSCB -- 9 --> VMSCB_VLRB + +``` + +Diagram of Figure A.1.3.2: Call to a ported number using TQoD procedure. The diagram shows four network domains: (International) Originating network, Number range holder network, Subscription network, and Visited network. The flow is: 1. Call from Originating Exchange to GMSCA in Number range holder network. 2. GMSCA sends database query to NPDB. 3. NPDB responds with routing number. 4. Call routed to GMSCB in Subscription network. 5. GMSCB sends MAP SRI to HLRB. 6. HLRB requests MSRN from VMSCB/VLRB in Visited network. 7. VMSCB/VLRB returns MSRN to HLRB. 8. HLRB responds to GMSCB. 9. GMSCB routes call to VMSCB/VLRB. + +**Figure A.1.3.2: Call to a ported number using TQoD procedure** + +- 1 From an Originating Exchange a call is set up to MSISDN. The call is routed to the Number range holder network. +- 2 When GMSCA receives the ISUP IAM, it will send a database query, including the MSISDN, to the NPDB as a result of analysis of the received MSISDN. +- 3 The NPDB detects that the MSISDN is ported and responds back to the GMSCA with a Routeing Number pointing out the Subscription network. +- 4 The call is routed to the Subscription network based on the Routeing Number carried in ISUP IAM message; also the MSISDN is included in IAM. +- 5 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB, including the MSISDN in the request. The capability to route messages to the correct HLR is required. +- 6 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered. +- 7 The MSC/VLRB returns an MSRN back to the HLRB. +- 8 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. +- 9 GMSCB uses the MSRN to route the call to VMSCB. + +Note that the NPDB may be outside the number range holder network if a shared NPDB is used. + +#### A.1.3.3 QoHR – Number is ported + +Figure A.1.3.3 shows the architecture for a call where the Originating network has no knowledge whether the MSISDN is ported or not and uses the traditional routeing plans for routeing the call to the Number range holder network for further routeing decisions. + +![Diagram of the QoHR procedure for a call to a ported number. The diagram shows four network domains: (Inter)national Originating network, Number range holder network, Subscription network, and Visited network. The flow is as follows: 1. Call from Originating Exchange to GMSCA. 2. GMSCA sends MAP SRI to HLRA. 3. HLRA returns 'Unknown Subscriber'. 4. GMSCA sends database query to NPDB. 5. NPDB identifies ported status and returns Routeing Number. 6. Call routed to Subscription network via GMSCB. 7. GMSCB sends MAP SRI to HLRB. 8. HLRB requests MSRN from VMSCB/VLRB. 9. VMSCB/VLRB returns MSRN. 10. HLRB returns SRI ack with MSRN. 11. GMSCB routes call to VMSCB/VLRB.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Diagram of the QoHR procedure for a call to a ported number. The diagram shows four network domains: (Inter)national Originating network, Number range holder network, Subscription network, and Visited network. The flow is as follows: 1. Call from Originating Exchange to GMSCA. 2. GMSCA sends MAP SRI to HLRA. 3. HLRA returns 'Unknown Subscriber'. 4. GMSCA sends database query to NPDB. 5. NPDB identifies ported status and returns Routeing Number. 6. Call routed to Subscription network via GMSCB. 7. GMSCB sends MAP SRI to HLRB. 8. HLRB requests MSRN from VMSCB/VLRB. 9. VMSCB/VLRB returns MSRN. 10. HLRB returns SRI ack with MSRN. 11. GMSCB routes call to VMSCB/VLRB. + +**Figure A.1.3.3: Call to a ported number using QoHR procedure** + +- 1 From an Originating Exchange a call is set up to MSISDN. The call is routed to the Number range holder network. +- 2 When GMSCA receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to the HLRA including the MSISDN in the request. +- 3 The HLRA returns a MAP SRI ack with an “Unknown Subscriber” error since no record was found for the subscriber in the HLRA. +- 4 When GMSCA receives the error indication from the HLRA, this will trigger the sending of a database query to the NPDB, including the MSISDN in the query. +- 5 The NPDB detects that the MSISDN is ported and responds back to the GMSCA with a Routeing Number pointing out the Subscription network. +- 6 The call is routed to the Subscription network based on the Routeing Number carried in ISUP IAM message; also the MSISDN is included in IAM. +- 7 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB, including the MSISDN in the request. The capability to route messages to the correct HLR is required. +- 8 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered. +- 9 The MSC/VLRB returns an MSRN back to the HLRB. +- 10 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. +- 11 GMSCB uses the MSRN to route the call to VMSCB. + +Note that the NPDB may be outside the number range holder network if a shared NPDB is used. + +### A.1.4 NP Query in Originating Network + +#### A.1.4.1 OQoD – Number is not ported + +Figure A.1.4.1 shows the architecture for a call where already the Originating network has the knowledge whether the MSISDN is ported or not and can route the call directly to the Subscription network that in this case is the same as the Number range holder network. + +![Diagram illustrating the call flow for a non-ported number using the OQoD procedure. The diagram shows three network domains: National Originating network, Number range holder/Subscription network, and Visited network. The flow involves a Mobile Subscriber (MS) initiating a call to the VMSCA, which then queries the NPDB. The NPDB indicates the number is not ported, and the call is routed to the GMSCB. The GMSCB sends an SRI to the HLRB, which then queries the VMSCB/VLRB for the MSRN. The VMSCB/VLRB returns the MSRN to the HLRB, which then responds to the GMSCB. Finally, the GMSCB routes the call to the VMSCB/VLRB.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +graph LR + subgraph National_Originating_network [National Originating network] + NPDB[(NPDB)] + VMSCA[VMSCA] + end + subgraph Number_range_holder_Subscription_network [Number range holder/Subscription network] + HLRB[(HLRB)] + GMSCB[GMSCB] + end + subgraph Visited_network [Visited network] + VMSCB_VLRB[VMSCB/VLRB] + end + + 1((1)) --> VMSCA + VMSCA -- 2((2)) --> NPDB + NPDB -- 3((3)) --> VMSCA + VMSCA -- 4((4)) --> GMSCB + GMSCB -- 5((5)) --> HLRB + HLRB -- 6((6)) --> VMSCB_VLRB + VMSCB_VLRB -- 7((7)) --> HLRB + HLRB -- 8((8)) --> GMSCB + GMSCB -- 9((9)) --> VMSCB_VLRB + +``` + +Diagram illustrating the call flow for a non-ported number using the OQoD procedure. The diagram shows three network domains: National Originating network, Number range holder/Subscription network, and Visited network. The flow involves a Mobile Subscriber (MS) initiating a call to the VMSCA, which then queries the NPDB. The NPDB indicates the number is not ported, and the call is routed to the GMSCB. The GMSCB sends an SRI to the HLRB, which then queries the VMSCB/VLRB for the MSRN. The VMSCB/VLRB returns the MSRN to the HLRB, which then responds to the GMSCB. Finally, the GMSCB routes the call to the VMSCB/VLRB. + +**Figure A.1.4.1: Call to a non-ported number using OQoD procedure** + +- 1 A call is initiated by Mobile Subscriber A towards Mobile Subscriber B, using the MSISDN of the called subscriber. +- 2 When VMSCA receives the call setup indication, it will send a database query to the NPDB as a result of analysis of the received MSISDN, including the MSISDN in the query. +- 3 The NPDB detects that the MSISDN is not ported and responds back to the VMSCA to continue the normal call setup procedure for MO calls. Depending on database configuration option, the NPDB could either return a Routeing Number on not ported calls, as done for ported calls, or the call is further routed using the MSISDN number only towards the Number range holder network. +- 4 The call is routed to the Number range holder/Subscription network based on the MSISDN or Routeing Number carried in ISUP IAM message. +- 5 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB, including the MSISDN in the request. +- 6 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered. +- 7 The MSC/VLRB returns an MSRN back to the HLRB. +- 8 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. +- 9 GMSCB uses the MSRN to route the call to VMSCB. + +Note that the NPDB may be outside the national originating network if a shared NPDB is used. + +#### A.1.4.2 OQoD – Number is ported + +Figure A.1.4.2 shows the architecture for a call where already the Originating network has the knowledge that the MSISDN is ported and can route the call directly to the Subscription network without involving the Number range holder network. + +![Diagram illustrating the call routing procedure for a ported number using OQoD. The diagram shows three network domains: National Originating network, Subscription network, and Visited network. The National Originating network contains an NPDB and a VMSCA. The Subscription network contains an HLRB and a GMSCB. The Visited network contains a VMSCB/VLRB. The call flow is numbered 1 through 9: 1. Call initiation to VMSCA; 2. VMSCA to NPDB query; 3. NPDB response to VMSCA; 4. VMSCA to GMSCB routing; 5. GMSCB to HLRB SRI request; 6. HLRB to VMSCB/VLRB MSRN request; 7. VMSCB/VLRB to HLRB MSRN response; 8. HLRB to GMSCB SRI ack; 9. GMSCB to VMSCB/VLRB call routing.](26d664119ad25250780f554633444e54_img.jpg) + +Diagram illustrating the call routing procedure for a ported number using OQoD. The diagram shows three network domains: National Originating network, Subscription network, and Visited network. The National Originating network contains an NPDB and a VMSCA. The Subscription network contains an HLRB and a GMSCB. The Visited network contains a VMSCB/VLRB. The call flow is numbered 1 through 9: 1. Call initiation to VMSCA; 2. VMSCA to NPDB query; 3. NPDB response to VMSCA; 4. VMSCA to GMSCB routing; 5. GMSCB to HLRB SRI request; 6. HLRB to VMSCB/VLRB MSRN request; 7. VMSCB/VLRB to HLRB MSRN response; 8. HLRB to GMSCB SRI ack; 9. GMSCB to VMSCB/VLRB call routing. + +**Figure A.1.4.2: Call to a ported number using OQoD procedure** + +- 1 A call is initiated by Mobile Subscriber A towards Mobile Subscriber B, using the MSISDN of the called subscriber. +- 2 When VMSCA receives the call setup indication, it will send a database query to the NPDB as a result of analysis of the received MSISDN including the MSISDN in the query. +- 3 The NPDB detects that the MSISDN is ported and responds back to the VMSCA with a Routeing Number pointing out the Subscription network. +- 4 The call is routed to the Subscription network based on the Routeing Number carried in ISUP IAM message; also the MSISDN is included in IAM. +- 5 The GMSCB requests routeing information by submitting a MAP SRI to the HLRB, including the MSISDN in the request. The capability to route messages to the correct HLR is required. +- 6 The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered. +- 7 The MSC/VLRB returns an MSRN back to the HLRB. +- 8 The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. +- 9 GMSCB uses the MSRN to route the call to VMSCB. + +Note that the NPDB may be outside the national originating network if a shared NPDB is used. + +#### A.1.4.3 IN-Query for CAMEL pre-paid service + +Figure A.1.4.3 shows the architecture for a call or MO-Short-Message originated by a CAMEL pre-paid subscriber while roaming in the Home PLMN where the gsmSCF needs to know whether or not calling and called subscriber subscribe to the same PLMN in order to apply the correct charging tariff. + +![Diagram of IN-Query for pre-paid service. A dashed box labeled 'National Originating network' contains three components: NPDB (a cylinder), gsmSCF (a rectangle), and VMSCA (a rectangle). Arrows with numbered circles indicate the sequence of messages: 1. External input to VMSCA; 2. VMSCA to gsmSCF; 3. gsmSCF to NPDB; 4. NPDB to gsmSCF; 5. gsmSCF to VMSCA; 6. VMSCA to external output.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +National +Originating network + +``` + +graph TD + subgraph National_Originating_network [National Originating network] + NPDB[(NPDB)] + gsmSCF[gsmSCF] + VMSCA[VMSCA] + end + 1((1)) --> VMSCA + VMSCA -- 2((2)) --> gsmSCF + gsmSCF -- 3((3)) --> NPDB + NPDB -- 4((4)) --> gsmSCF + gsmSCF -- 5((5)) --> VMSCA + VMSCA -- 6((6)) --> Out[ ] + style Out fill:none,stroke:none + +``` + +Diagram of IN-Query for pre-paid service. A dashed box labeled 'National Originating network' contains three components: NPDB (a cylinder), gsmSCF (a rectangle), and VMSCA (a rectangle). Arrows with numbered circles indicate the sequence of messages: 1. External input to VMSCA; 2. VMSCA to gsmSCF; 3. gsmSCF to NPDB; 4. NPDB to gsmSCF; 5. gsmSCF to VMSCA; 6. VMSCA to external output. + +**Figure A.1.4.3: IN-Query for pre-paid service** + +- 1 A call or short message is initiated by Mobile Subscriber A towards Mobile Subscriber B, using the MSISDN of the called subscriber. +- 2 When VMSCA receives the call setup indication, it will send a CAP IDP message to the gsmSCF. The IDP contains the called party's MSISDN. +- 3 If the calling subscriber roams in her Home PLMN and the called subscriber's MSISDN indicates that the called subscriber subscribes to a PLMN within the calling subscriber's Home Country, the gsmSCF queries the NPDB based on the called party's MSISDN. +Otherwise the tariff to be applied does not depend on the called subscriber's porting status and enough information to apply the correct tariff is available; go to 5. +- 4 The NPDB returns a routing number to the gsmSCF pointing out the called subscriber's subscription network. Based on this information the gsmSCF applies the appropriate tariff for pre-paid subscriber A. +- 5 The gsmSCF returns CAP AC and CAP CUE messages to the VMSCA. +- 6 The call or short message is set up. + +Note that the NPDB and gsmSCF may be integrated within one physical entity. + +## A.2 Information flows + +In the following figures the NPDB is shown as belonging to the Number range holder network or to the national originating network. However, the NPDB may be shared within one portability domain i.e. nation-wide. + +Figure A.2.1 shows the information flow for successful QoHR. + +![Sequence diagram showing information flows for successful QoHR between Number range holder network, subscription network, and visited network.](088921fa3f5a44c8551815122517eefd_img.jpg) + +The diagram illustrates the information flow for a successful Quality of Service Handover (QoHR) across three network domains: Number range holder network, subscription network, and visited network. + +- Number range holder network:** Contains GMSC, HLR, and NPDB. The process starts with an incoming IAM message to the GMSC. The GMSC sends an SRI (Service Request Information) message to the HLR. The HLR responds with a "neg. result" (negative result) to the GMSC. The GMSC then sends a "query" message to the NPDB. The NPDB responds with "routing" information to the GMSC. Finally, the GMSC sends an IAM message to the subscription network's GMSC. +- subscription network:** Contains GMSC and HLR. The GMSC receives the IAM message from the Number range holder network's GMSC. It then sends an SRI message to its HLR. The HLR responds with an SRI ack (acknowledgment) to the GMSC. +- visited network:** Contains VLR and VMSC. The subscription network's GMSC sends an IAM message to the VMSC. The VMSC sends a PRN (Page Request) message to the VLR. The VLR responds with a PRN ack (acknowledgment) to the VMSC. The VMSC then sends an IAM message to the VLR. + +Sequence diagram showing information flows for successful QoHR between Number range holder network, subscription network, and visited network. + +Figure A.2.1 + +Figure A.2.2 shows the information flow for unsuccessful QoHR (unallocated number). + +![Sequence diagram for unsuccessful QoHR (unallocated number) showing interactions between GMSC, HLR, and NPDB within a Number range holder network.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +This sequence diagram illustrates the information flow for an unsuccessful Quality of Service Handover Request (QoHR) due to an unallocated number. The diagram is contained within a box labeled "Number range holder network" and features three vertical lifelines: GMSC, HLR, and NPDB. The sequence of messages is as follows: + + +- An external **IAM** (Initial Address Message) is received by the **GMSC** from the left. +- The **GMSC** sends an **SRI** (Send Routing Information) message to the **HLR**. +- The **HLR** responds with a **negative result** message back to the **GMSC**. +- Upon receiving the negative result, the **GMSC** sends a **"query"** message to the **NPDB**. +- The **NPDB** returns a **"result"** message to the **GMSC**. +- Finally, the **GMSC** sends an external **REL** (Release) message to the left. + +Sequence diagram for unsuccessful QoHR (unallocated number) showing interactions between GMSC, HLR, and NPDB within a Number range holder network. + +Figure A.2.2 + +Figure A.2.3 shows the information flow for successful TQoD. + +![Sequence diagram for successful TQoD showing interactions between Number range holder network (GMSC, HLR, NPDB), subscription network (GMSC, HLR), and visited network (VLR, VMSC).](805c475f0859e607af0530ba43194bf1_img.jpg) + +This sequence diagram illustrates the information flow for a successful Traffic Quality of Service (TQoD) handover across three network domains. The lifelines are organized into three boxes: "Number range holder network" (containing GMSC, HLR, NPDB), "subscription network" (containing GMSC, HLR), and "visited network" (containing VLR, VMSC). The sequence of messages is as follows: + + +- An external **IAM** is received by the **GMSC** in the Number range holder network. +- The **GMSC** sends a **"query"** message to the **NPDB**. +- The **NPDB** returns a **"routing"** message to the **GMSC**. +- The **GMSC** then sends an **IAM** message to the **GMSC** in the subscription network. +- The **GMSC** in the subscription network sends an **SRI** message to its **HLR**. +- The **HLR** in the subscription network sends a **PRN** (Provide Roaming Number) message to the **VLR** in the visited network. +- The **VLR** in the visited network responds with a **PRN ack** (acknowledgment) message back to the **HLR**. +- The **HLR** in the subscription network sends an **SRI ack** message back to the **GMSC**. +- Finally, the **GMSC** in the subscription network sends an **IAM** message to the **VMSC** in the visited network. + +Sequence diagram for successful TQoD showing interactions between Number range holder network (GMSC, HLR, NPDB), subscription network (GMSC, HLR), and visited network (VLR, VMSC). + +Figure A.2.3 + +Figure A.2.4 shows the information flow for unsuccessful TQoD (number not ported). + +![Sequence diagram showing information flow for unsuccessful TQoD. Lifelines: GMSC, HLR, NPDB (Number range holder network); VLR, VMSC (visited network). Messages include IAM, query, result, SRI, PRN, PRN ack, SRI ack, and IAM.](474a819357587e34949a3e110ff19b30_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant HLR + participant NPDB + participant VLR + participant VMSC + + Note over GMSC, NPDB: Number range holder network + Note over VLR, VMSC: visited network + + [External]-->>GMSC: IAM + GMSC->>NPDB: "query" + NPDB-->>GMSC: "result" + GMSC->>HLR: SRI + HLR->>VLR: PRN + VLR-->>HLR: PRN ack + HLR-->>GMSC: SRI ack + GMSC->>VMSC: IAM + +``` + +The diagram illustrates the signaling sequence for an unsuccessful TQoD (Number Not Ported) scenario. It involves two networks: the Number range holder network (containing GMSC, HLR, and NPDB) and the visited network (containing VLR and VMSC). The sequence starts with an incoming IAM to the GMSC. The GMSC sends a "query" to the NPDB, which returns a "result". The GMSC then sends an SRI to the HLR. The HLR sends a PRN to the VLR, which responds with a PRN ack. The HLR then sends an SRI ack back to the GMSC. Finally, the GMSC sends an IAM to the VMSC. + +Sequence diagram showing information flow for unsuccessful TQoD. Lifelines: GMSC, HLR, NPDB (Number range holder network); VLR, VMSC (visited network). Messages include IAM, query, result, SRI, PRN, PRN ack, SRI ack, and IAM. + +Figure A.2.4 + +Figure A.2.5 shows the information flow for successful OQoD (number ported). + +![Sequence diagram showing information flow for successful OQoD (number ported) across National originating network A, subscription network B, and visited network B.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +The diagram illustrates the signaling flow for a successful OQoD (number ported) call setup. It involves three main network entities: National originating network A, subscription network B, and visited network B. The components and their interactions are as follows: + +- National originating network A:** Contains VMSC and NPDB. The process starts with a "Set-up" message to the VMSC. The VMSC sends a "query" to the NPDB, which responds with "routing". The VMSC then sends an "IAM" (Initial Address Message) to the GMSC in subscription network B. +- subscription network B:** Contains GMSC and HLR. The GMSC receives the "IAM" and sends an "SRI" (Send Routing Information) to the HLR. The HLR responds with an "SRI ack". +- visited network B:** Contains VLR and VMSC. The HLR sends a "PRN" (Paging Request) to the VLR, which responds with a "PRN ack". The HLR then sends an "IAM" to the VMSC in visited network B. + +``` +sequenceDiagram + participant VMSC_A as VMSC + participant NPDB_A as NPDB + participant GMSC_B as GMSC + participant HLR_B as HLR + participant VLR_B as VLR + participant VMSC_B as VMSC + + Note left of VMSC_A: Set-up + VMSC_A->>NPDB_A: query + NPDB_A-->>VMSC_A: routing + VMSC_A->>GMSC_B: IAM + GMSC_B->>HLR_B: SRI + HLR_B-->>GMSC_B: SRI ack + HLR_B->>VLR_B: PRN + VLR_B-->>HLR_B: PRN ack + HLR_B->>VMSC_B: IAM +``` + +Sequence diagram showing information flow for successful OQoD (number ported) across National originating network A, subscription network B, and visited network B. + +Figure A.2.5 + +Figure A.2.6 shows the information flow for unsuccessful OQoD (number not ported in). + +![Sequence diagram showing information flow for unsuccessful OQoD between originating network (VMSCA, NPDB) and Number range holder network (GMSC).](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +The diagram illustrates the information flow for an unsuccessful OQoD (Number not ported in) scenario. It is divided into two main network domains: the **originating network** and the **Number range holder network**. + +- originating network:** Contains two entities, **VMSCA** and **NPDB**. + - An external **Set-up** message (dashed arrow) enters the **VMSCA**. + - The **VMSCA** sends a **"query"** message (dashed arrow) to the **NPDB**. + - The **NPDB** responds with a **"routing"** message (dashed arrow) back to the **VMSCA**. + - Below the NPDB is another unlabeled box, and between the VMSCA and NPDB is the label **IAM**. +- Number range holder network:** Contains the entity **GMSC**. + - A dashed arrow points from the **VMSCA** to the **GMSC**. + - Inside the **GMSC**, the text indicates: **continue as shown in figures A.2.1, A.2.2, A.2.3 and A.2.4**. + +Sequence diagram showing information flow for unsuccessful OQoD between originating network (VMSCA, NPDB) and Number range holder network (GMSC). + +Figure A.2.6 + +## --- A.3 Functional requirements of network entities + +### A.3.1 Functional requirement of GMSC + +#### A.3.1.1 Procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_QoHR + +The procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_QoHR is shown in figure A.1.3. It is called from the procedure Obtain\_Routeing\_Address defined in 3G TS 23.018 [3]. + +The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams. + +The query to NPDB contains the service key for MNP query and the called party's MSISDN. + +![Flowchart for Procedure MOBILE_NUMBER_PORTABILITY_QoHR. It starts with a QoHR trigger, followed by two decision diamonds. The first checks if the NPDB query is marked done; if yes, it ends. If no, it checks if the called party number is within the porting out number range. If no, it sets Result := not ported and ends. If yes, it sends a 'query' signal, waits, and then handles one of four signals: negative Response, Abort, 'result', or 'routing'. 'result' and 'routing' lead to Result := not ported and Result := Number ported respectively, both ending the procedure.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +### Procedure MOBILE\_NUMBER\_PORTABILITY\_QoHR 1(1) + +Procedure in the GMSC to handle Query on HLR Release for Mobile Number Portability + +Signals to/from the right are to/from the NPDB + +``` +graph TD; QoHR((QoHR)) --> D1{ }; D1 -- yes --> T1[NPDB query is marked done]; D1 -- no --> D2{ }; D2 -- yes --> T2[called party number within porting out number range]; D2 -- no --> R1[Result := not ported]; T2 -- yes --> S1{{"query"}}; S1 --> W([Wait]); W --> S2{{negative Response}}; W --> S3{{Abort}}; W --> S4{{"result"}}; W --> S5{{"routing"}}; S2 --> S3; S3 --> S4; S4 --> R2[Result := not ported]; S5 --> R3[Result := Number ported]; R1 --> E1((X)); R2 --> E2((X)); R3 --> E3((X)); +``` + +Flowchart for Procedure MOBILE\_NUMBER\_PORTABILITY\_QoHR. It starts with a QoHR trigger, followed by two decision diamonds. The first checks if the NPDB query is marked done; if yes, it ends. If no, it checks if the called party number is within the porting out number range. If no, it sets Result := not ported and ends. If yes, it sends a 'query' signal, waits, and then handles one of four signals: negative Response, Abort, 'result', or 'routing'. 'result' and 'routing' lead to Result := not ported and Result := Number ported respectively, both ending the procedure. + +Figure A.3.1.1: Procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_QoHR + +#### A.3.1.2 Procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_TQoD + +The procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_TQoD is shown in figure A.3.1.2. It is called from the procedure Obtain\_Routeing\_Address defined in 3G TS 23.018 [3]. + +The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams. + +The "query" to NPDB contains the service key for MNP query and the called party's MSISDN. + +![State transition diagram for Procedure MOBILE_NUMBER_PORTABILITY_TQoD. The process starts at an initial state, leading to an 'OR' decision. If 'true', it goes to a 'Result := not ported' state. If 'false', it goes to a 'TQoD' state. From 'TQoD', a 'yes' signal leads to a decision 'NPDB query is marked done'. If 'yes', it goes to 'IDP NPDB Query' and then 'Wait'. If 'no', it goes to another decision 'called party number within porting out number range'. If 'yes', it goes to 'IDP NPDB Query' and then 'Wait'. If 'no', it goes to 'Result := not ported'. From 'Wait', four signals are possible: 'negative Response', 'Abort', 'Continue', and 'Connect'. 'negative Response' and 'Abort' lead to 'Result := not ported'. 'Continue' leads to 'Result := not ported'. 'Connect' leads to 'Result := Number ported'. All final states lead to an exit state.](8658cfab6a458b4a80ab2e384c61ff89_img.jpg) + +Procedure MOBILE\_NUMBER\_PORTABILITY\_TQoD 1(1) + +Procedure in the GMSC to handle Terminating call Query on Digit Analysis for Mobile Number Portability + +Signals to/from the right are to/from the NPDB + +``` + +stateDiagram-v2 + [*] --> OR + state "OR" as OR + OR --> TQoD : false + OR --> Result_not_ported_1[Result := not ported] : true + TQoD --> NPDB_query_done{NPDB query is marked done} : yes + NPDB_query_done --> IDP_NPDB_Query[IDP NPDB Query] : yes + NPDB_query_done --> Called_party_range{called party number within porting out number range} : no + Called_party_range --> IDP_NPDB_Query : yes + Called_party_range --> Result_not_ported_1 : no + IDP_NPDB_Query --> Wait + Wait --> negative_Response[negative Response] + Wait --> Abort[Abort] + Wait --> Continue[Continue] + Wait --> Connect[Connect] + negative_Response --> Result_not_ported_2[Result := not ported] + Abort --> Result_not_ported_2 + Continue --> Result_not_ported_2 + Connect --> Result_number_ported[Result := Number ported] + Result_not_ported_1 --> [*] + Result_not_ported_2 --> [*] + Result_number_ported --> [*] + +``` + +State transition diagram for Procedure MOBILE\_NUMBER\_PORTABILITY\_TQoD. The process starts at an initial state, leading to an 'OR' decision. If 'true', it goes to a 'Result := not ported' state. If 'false', it goes to a 'TQoD' state. From 'TQoD', a 'yes' signal leads to a decision 'NPDB query is marked done'. If 'yes', it goes to 'IDP NPDB Query' and then 'Wait'. If 'no', it goes to another decision 'called party number within porting out number range'. If 'yes', it goes to 'IDP NPDB Query' and then 'Wait'. If 'no', it goes to 'Result := not ported'. From 'Wait', four signals are possible: 'negative Response', 'Abort', 'Continue', and 'Connect'. 'negative Response' and 'Abort' lead to 'Result := not ported'. 'Continue' leads to 'Result := not ported'. 'Connect' leads to 'Result := Number ported'. All final states lead to an exit state. + +Figure A.3.1.2: Procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_TQoD + +### A.3.2 Functional requirement of MSC + +#### A.3.2.1 Procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_OQoD + +The procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_OQoD is shown in figure A.3.2.1. It is called from the procedure Outgoing\_Call\_Setup\_MSC and from the process MT\_CF\_MSC defined in 3G TS 23.018 [3]. + +The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams. + +The MSC may recognise own numbers as not being within the ported number range. For foreign numbers however, the MSC will not in general know whether the number is portable. The test "called party number is a portable national MSISDN" takes the "yes" exit if the number is a foreign national MSISDN or an own portable MSISDN. + +The "query" to NPDB contains the service key for MNP query and the called party's MSISDN. + +![Flowchart for Procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD. It starts with an OQoD symbol, leading to a decision diamond 'called party number is a portable national MSISDN'. If 'no', it ends with an 'X'. If 'yes', it goes to a 'query' block, then a 'Wait' block. From 'Wait', it branches into four paths: 'negative Response' (ends with 'X'), 'Abort' (ends with 'X'), 'result' (ends with 'X'), and 'routing' (leads to 'set routeing number' for IAM, then ends with 'X').](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +Procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_OQoD 1(1) + +Procedure in the MSC to handle Originating call Query on Digit Analysis for Mobile Number Portability + +Signals to/from the right are to/from the NPDB + +``` + +graph TD + Start([ ]) --> OQoD((OQoD)) + OQoD --> Dec1{ } + Dec1 -- no --> X1((X)) + Dec1 -- yes --> Dec2{called party number +is a portable national MSISDN} + Dec2 -- no --> X1 + Dec2 -- yes --> Query[/"query"/] + Query --> Wait([Wait]) + Wait --> NegRes[/negative +Response/] + Wait --> Abort[/Abort/] + Wait --> Result[/"result"/] + Wait --> Routing[/"routing"/] + NegRes --> X2((X)) + Abort --> X2 + Result --> X2 + Routing --> SetRoute[set routeing +number] + SetRoute -- for IAM --> X2 + +``` + +Flowchart for Procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_OQoD. It starts with an OQoD symbol, leading to a decision diamond 'called party number is a portable national MSISDN'. If 'no', it ends with an 'X'. If 'yes', it goes to a 'query' block, then a 'Wait' block. From 'Wait', it branches into four paths: 'negative Response' (ends with 'X'), 'Abort' (ends with 'X'), 'result' (ends with 'X'), and 'routing' (leads to 'set routeing number' for IAM, then ends with 'X'). + +Figure A.3.2.1: Procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_OQoD + +### A.3.3 Functional requirement of NPDB + +#### A.3.3.1 Process IN\_QUERY\_NPDB + +The process IN\_QUERY\_NPDB is shown in figure A.3.3.1. + +![Flowchart for Process IN_QUERY_NPDB. It starts with an 'Idle' state, followed by a 'query' input. A decision diamond checks if the syntax on CdPA is correct. If 'no', it goes to 'Set error type' and then 'negative Response'. If 'yes', it goes to another decision diamond to 'Check Called Party Address Portability Status'. From there, if 'Number not ported', it goes to 'Send RN on Number Not Ported in OQoD' and then to a 'result' output. If 'Number ported', it goes to 'set: Routeing number' and then to a 'routing' output. Both 'result' and 'routing' lead to a final 'Idle' state. Callouts explain symbols: 'Process in the NPDB to handle NPDB queries', 'Signals to/from the left are to/from the MSC', 'service key indicates NPDB query', and 'Syntax check on CdPA correct?'.](fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg) + +``` +graph TD; Start([Idle]) --> Query{{"query"}}; Query --> SyntaxCheck{Syntax check on CdPA correct?}; SyntaxCheck -- no --> SetError[Set error type]; SetError --> NegativeResponse{negative Response}; SyntaxCheck -- yes --> PortabilityCheck{Check Called Party Address Portability Status}; PortabilityCheck -- "Number not ported" --> SendRN[Send RN on Number Not Ported in OQoD]; PortabilityCheck -- "Number ported" --> SetRouteing[set: Routeing number]; SendRN --> Result{result}; SetRouteing --> Routing{routing}; NegativeResponse --> End([Idle]); Result --> End; Routing --> End; +``` + +Flowchart for Process IN\_QUERY\_NPDB. It starts with an 'Idle' state, followed by a 'query' input. A decision diamond checks if the syntax on CdPA is correct. If 'no', it goes to 'Set error type' and then 'negative Response'. If 'yes', it goes to another decision diamond to 'Check Called Party Address Portability Status'. From there, if 'Number not ported', it goes to 'Send RN on Number Not Ported in OQoD' and then to a 'result' output. If 'Number ported', it goes to 'set: Routeing number' and then to a 'routing' output. Both 'result' and 'routing' lead to a final 'Idle' state. Callouts explain symbols: 'Process in the NPDB to handle NPDB queries', 'Signals to/from the left are to/from the MSC', 'service key indicates NPDB query', and 'Syntax check on CdPA correct?'. + +Figure A.3.3.1: Process IN\_QUERY\_NPDB + +## A.4 Contents of messages + +This clause specifies the content of the following messages: + +On the ISUP interface: + +IAM. + +On the MSC - NPDB interface: + +"query"; + +"routing"; + +"result". + +**Messages in the MSC – NPDB interface are mapped into ETSI Core INAP or ANSI IN Query messages according to the protocols on this interface. This is listed in the following table:** + +| Messages in MSC-NPDB interface | INAP messages | ANSI IN Query messages | +|--------------------------------|--------------------------|---------------------------| +| "query" | INITIAL DP | ProvideInstruction:Start | +| "routing" | CONNECT<br>CONTINUE | ConnectionControl:Connect | +| "result" | CONTINUE<br>RELEASE CALL | ConnectionControl:Connect | + +In the tables that follow, information elements are shown as mandatory (M), conditional (C) or optional (O). A mandatory information element shall always be present. A conditional information element shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional element may be present or absent, at the discretion of the application at the sending entity. + +### A.4.1 Messages on the ISUP interface + +#### A.4.1.1 IAM for ETSI ISUP interface + +This message is specified in [14]. It is necessary for the IAM to contain the information needed to route the call to the subscription network of the ported subscriber. The ways in which this may be coded are shown in [14]. + +#### A.4.1.2 IAM for ANSI ISUP interface + +This message is specified in [8] and [9]. It is necessary for the IAM to contain the information needed to route the call to the subscription network of the ported subscriber. The ways in which this may be coded are shown in [8] and [9]. + +### A.4.2 Messages on the MSC - NPDB interface + +#### A.4.2.1 INITIAL DP + +**This message is specified in [5]. The following information elements are required:** + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------| +| Service Key | M | Identifies the requested IN service (MNP query) | +| Called Party Number | M | The possibly ported MSISDN | + +#### A.4.2.2 INITIAL DP negative response + +This message is specified in [5]. The negative response information element can take the following values: + +1. missing parameter; +2. unexpected data value; +3. unexpected parameter; +4. system failure. + +#### A.4.2.3 CONNECT + +This message is specified in [5]. It shall be ensured that the information in the Connect message shall be aligned with the coding supported in the ISUP signalling. + +#### A.4.2.4 CONTINUE + +This message is specified in [5]. This message does not contain any information element. + +#### A.4.2.5 RELEASE CALL + +**This message is specified in [5]. The following information elements are required:** + +| Information element name | Required | Description | +|--------------------------|----------|---------------------------------------------| +| Cause | M | Indicates the reason for releasing the call | + +#### A.4.2.6 ProvideInstruction:Start + +| Parameter | Type | Number of Octets | Contents | +|-------------------------------|----------------|------------------|-------------------------------------------| +| Package Type Identifier | M | 1 | Query with Permission | +| Component Type Identifier | M | 1 | Invoke (last) | +| Operation Code Identifier | M | 1 | National TCAP | +| Operation Code | M | 2 | provideInstruction:Start (reply required) | +| Service Key | M | 11* | 10 digit called party number digits | +| Digits (calling party number) | M <sup>1</sup> | 6-9 | 3,6 or 10 ANI digits | +| Digits (LATA) | M <sup>1</sup> | 6 | LATA ID | +| Originating Station Type | M <sup>1</sup> | 1 | Binary value of ANI II digits | + +Note: + +\* = Value specific for number portability + +<sup>1</sup> = This mandatory parameter is required for the message but the content is not essential for number portability. + +#### A.4.2.7 ConnectionControl:Connect + +| Parameter | Type | Number of Octets | Contents | +|---------------------------|----------------|------------------|-----------------------------------------------| +| Package Type Identifier | M | 1 | Response | +| Component Type Identifier | M | 1 | Invoke (last) | +| Operation Code Identifier | M | 1 | National TCAP | +| Operation Code | M | 2 | connectionControl:Connect (no reply required) | +| Digits (Carrier) | M <sup>1</sup> | 6 | 3 or 4 digit CIC | +| Digits (Routing Number) | M | 9* | 10 digit RN or Dialed Number | +| Billing Indicators | M <sup>1</sup> | 4 | Unspecified | + +Note: + +\* = Value specific for number portability + +<sup>1</sup> = This mandatory parameter is required for the message but the content is not essential for number portability. + +# Annex B (normative): Handling of Non-Call Related Signalling + +## B.1 Handling of Non-call Related Signalling + +### B.1.1 Routeing Conventions + +Figure B.1.1 illustrates the routeing of non-call related signalling messages between networks in a number portability environment. + +![Diagram illustrating the routeing of non-call related signalling messages in a number portability environment. The diagram shows a 'Portability domain' containing three networks: 'Number Range Holder Network', 'Subscription Network', and 'Other network'. Message (1) enters from outside to the Number Range Holder Network. Message (5) goes from Number Range Holder Network to Subscription Network. Message (4) goes from Number Range Holder Network to Other network. Message (2) goes from Other network to Number Range Holder Network. Message (3) goes from Other network to Subscription Network.](52e112d1ba42a3c660bf62a0fea927d3_img.jpg) + +``` + +graph TD + subgraph Portability_domain [Portability domain] + direction TB + subgraph NumberRangeHolder [Number Range Holder Network] + end + subgraph Subscription [Subscription Network] + end + subgraph Other [Other network] + end + NumberRangeHolder -- "Message (5)" --> Subscription + NumberRangeHolder -- "Message (4)" --> Other + Other -- "Message (2)" --> NumberRangeHolder + Other -- "Message (3)" --> Subscription + end + External(( )) -- "Message (1)" --> NumberRangeHolder + +``` + +Diagram illustrating the routeing of non-call related signalling messages in a number portability environment. The diagram shows a 'Portability domain' containing three networks: 'Number Range Holder Network', 'Subscription Network', and 'Other network'. Message (1) enters from outside to the Number Range Holder Network. Message (5) goes from Number Range Holder Network to Subscription Network. Message (4) goes from Number Range Holder Network to Other network. Message (2) goes from Other network to Number Range Holder Network. Message (3) goes from Other network to Subscription Network. + +**Figure B.1.1: Routeing of non-call related signalling messages in a number portability environment** + +If a non-call related signalling message is originated outside the portability domain, this message (1) is received by the number range holder network. The number range holder network routes the message (5) onward to the subscription network. + +If a non-call related signalling message is originated in a network inside the portability domain and this network supports direct routeing, this message (3) is routed to the subscription network. + +If a non-call related signalling message is originated in a network inside the portability domain and this network does not support direct routeing, the message (2, 4) is routed to the number range holder network. The number range holder network routes the message (5) onward to the subscription network. This is referred to as indirect routeing. + +### B.1.2 Network Architecture + +In a PLMN that supports MNP, non-call related signalling messages as mentioned in section B.1.1 are relayed by an MNP-Signalling Relay Function (MNP-SRF). The MNP-SRF provides re-routeing capability for signalling messages addressed using the MSISDN. The MNP-SRF obtains routeing information from the NP database to identify the subscription network associated with a particular national MSISDN. The interface between the MNP-SRF and the NP database is considered implementation dependent and is not detailed further. For further details see clause 4.3. + +From the perspective of the PLMN in which the MNP-SRF resides, the MSISDN in the CdPA represents either: + +- 1 An own number ported out. +- 2 An own number not ported out. + +- 3 A foreign number ported in. +- 4 A foreign number ported to a foreign network. +- 5 A foreign number not known to be ported. + +When a PLMN supports direct routeing (clause B.1.1), all non-call related signalling messages where the MSISDN in the CdPA belongs to a number range owned by a PLMN in the portability domain and all non-call related signalling messages which are relayed towards the network, are routed to the PLMN's MNP-SRF for treatment. + +In case 2 and 3 the MNP-SRF relays the message to the Subscriber Database supporting the Network Service e.g. HLR and Calling Name Database. + +In case 1, 4 and 5 the MNP-SRF relays the message to subscription network. + +When a PLMN does not support direct routeing, only non-call related signalling messages where the MSISDN in the CdPA belongs to a number range owned by the PLMN itself and all non-call related signalling messages which are relayed towards the network are routed to the PLMN's MNP-SRF for treatment. All other messages are routed to the number range holder network. + +For this routeing convention, only cases 1, 2 and 3 are applicable: + +In case 2 and 3 the MNP-SRF relays the message to the Subscriber Database supporting the Network Service e.g. HLR and Calling Name Database. + +In case 1 the MNP-SRF relays the message to the subscription network. + +## B.2 Signalling Scenarios + +### B.2.1 Non-call Related Signalling Message for a Non-ported Number – Indirect Routeing + +Figure B.2.1 shows the MNP-SRF operation for routeing a non-call related signalling message for a non-ported number where the interrogating network is inside the portability domain and indirect routeing is used or the interrogating network is outside the portability domain. + +![Diagram of MNP-SRF operation for a non-ported number.](030c758fd425016b03290c8f11bef69d_img.jpg) + +The diagram illustrates the MNP-SRF operation for routing a non-call related signalling message for a non-ported number. It shows two main components: the Interrogating Network (INE) and the Number Range Holder Network (Subscription Network). The INE is represented by a dashed rectangle containing a box labeled 'INE'. The Number Range Holder Network is represented by a dashed rectangle containing three components: a cylinder labeled 'HLRB', a box labeled 'MNP SRFB', and a dashed cylinder labeled 'NPDB'. An arrow points from the INE to the MNP SRFB, labeled 'SCCP CdPA = MSISDN, TT=0'. Another arrow points from the MNP SRFB to the HLRB, labeled 'SCCP CdPA = HLRB address'. A dashed double-headed arrow connects the MNP SRFB and the NPDB. + +Diagram of MNP-SRF operation for a non-ported number. + +**Figure B.2.1: MNP-SRF operation for routeing a non-call related signalling message for a non-ported number where the interrogating network is inside the portability domain and indirect routeing is used or the interrogating network is outside the portability domain** + +NOTE: that the TT may have a different value, e.g. TT=17 in the case of CCBS Requests and TT=14 in the case of ANSI Routing of SRI\_For\_Short Message. + +The Interrogating Network Entity (INE) submits a non-call related signalling message. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being non-ported using information that may be retrieved from an NP database. Figure B.2.1 shows an example where the MNP-SRF function then re-routes the message to HLRB. + +### B.2.2 Non-call Related Signalling Message for a Ported or Non-ported Number – Direct Routeing + +Figure B.2.2 shows the MNP-SRF operation for routing a non-call related signalling message for a ported or non-ported number where the interrogating network supports direct routing. If the interrogating network is the subscription network, MNP-SRFA and MNP-SRFB coincide; i.e. the signalling message passes the MNP-SRF only once. + +![Diagram illustrating the MNP-SRF operation for routing a non-call related signalling message for a ported or non-ported number where the interrogating network supports direct routing. The diagram shows two networks: Interrogating Network and Subscription Network. In the Interrogating Network, an INE sends a message to MNP SRFA with SCCP CdPA = MSISDN, TT=0. MNP SRFA then sends a message to MNP SRFB in the Subscription Network with SCCP CdPA = RN (+ MSISDN), TT=0. MNP SRFB then sends a message to HLRB with SCCP CdPA = HLRB address. Both networks have NPDB databases.](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) + +``` + +graph LR + subgraph Interrogating Network + INE[INE] -- "SCCP CdPA = MSISDN, TT=0"¹ --> SRFA[MNP SRFA] + NPDB1[(NPDB)] <--> SRFA + end + subgraph Subscription Network + SRFB[MNP SRFB] -- "SCCP CdPA = HLRB address" --> HLRB[(HLRB)] + NPDB2[(NPDB)] <--> SRFB + end + SRFA -- "SCCP CdPA = RN (+ MSISDN), TT=0"² --> SRFB + +``` + +Diagram illustrating the MNP-SRF operation for routing a non-call related signalling message for a ported or non-ported number where the interrogating network supports direct routing. The diagram shows two networks: Interrogating Network and Subscription Network. In the Interrogating Network, an INE sends a message to MNP SRFA with SCCP CdPA = MSISDN, TT=0. MNP SRFA then sends a message to MNP SRFB in the Subscription Network with SCCP CdPA = RN (+ MSISDN), TT=0. MNP SRFB then sends a message to HLRB with SCCP CdPA = HLRB address. Both networks have NPDB databases. + +**Figure B.2.2: MNP-SRF operation for routing a non-call related signalling message for a ported or non-ported number where the interrogating network supports direct routing** + +NOTE 1: the TT may have a different value, e.g. TT=17 in the case of CCBS Requests and TT=14 in the case of ANSI Routing of SRI\_For\_Short Message . + +NOTE 2: the CdPA may have different values in the GT address and the nature of address fields. + +The Interrogating Network Entity (INE) submits a non-call related signalling message. When MNP-SRFA receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the subscription network using information that may be retrieved from an NP database. The MNP-SRF function then modifies the CdPA according to the rules agreed for the portability domain and routes the message to MNP-SRFB in the subscription network. + +When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information that may be retrieved from an NP database. Figure B.2.2 shows an example where the MNP-SRF function then re-routes the message to HLRB. + +### B.2.3 Non-call Related Signalling Message for a Ported Number - Indirect Routeing + +Figure B.2.3 shows the MNP-SRF operation for indirectly routeing (i.e. via the number range holder network) a non-call related signalling message for a ported subscriber. + +![Diagram of MNP-SRF operation for indirect routeing. It shows three network entities: Interrogating Network, Number Range Holder Network, and Subscription Network. The Interrogating Network contains an INE. The Number Range Holder Network contains an NPDB and an MNP SRFA. The Subscription Network contains an HLRB, an MNP SRFB, and an NPDB. The INE sends a message to the MNP SRFA with SCCPCdPA = MSISDN, TT=j. The MNP SRFA sends a message to the MNP SRFB with SCCPCdPA = RN (+ MSISDN), TT=j. The MNP SRFB sends a message to the HLRB with SCCPCdPA = HLRB address.](67d03c9e89620d73e3786c869e559752_img.jpg) + +``` + +graph LR + subgraph Interrogating Network + INE[INE] + end + subgraph Number Range Holder Network + NPDB1[NPDB] + MNP_SRFA[MNP SRFA] + end + subgraph Subscription Network + HLRB[(HLRB)] + MNP_SRFB[MNP SRFB] + NPDB2[NPDB] + end + INE -- "SCCPCdPA = MSISDN, TT=j" --> MNP_SRFA + MNP_SRFA -- "SCCPCdPA = RN (+ MSISDN), TT=j" --> MNP_SRFB + MNP_SRFB -- "SCCPCdPA = HLRB address" --> HLRB + +``` + +Diagram of MNP-SRF operation for indirect routeing. It shows three network entities: Interrogating Network, Number Range Holder Network, and Subscription Network. The Interrogating Network contains an INE. The Number Range Holder Network contains an NPDB and an MNP SRFA. The Subscription Network contains an HLRB, an MNP SRFB, and an NPDB. The INE sends a message to the MNP SRFA with SCCPCdPA = MSISDN, TT=j. The MNP SRFA sends a message to the MNP SRFB with SCCPCdPA = RN (+ MSISDN), TT=j. The MNP SRFB sends a message to the HLRB with SCCPCdPA = HLRB address. + +**Figure B.2.3: MNP-SRF operation for indirectly routeing (i.e. via the number range holder network) a non-call related signalling message for a ported subscriber** + +NOTE 1: the TT may have a different value, e.g. TT=17 in the case of CCBS Requests and TT=14 in the case of ANSI Routing of SRI\_For\_Short Message. + +NOTE 2: the CdPA may have different values in the GT address and the nature of address fields. + +The Interrogating Network Entity (INE) submits a non-call related signalling message. This message is routed on MSISDN global title to MNP-SRFA in the number range holder network. + +When MNP-SRFA receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the subscription network using information that may be retrieved from an NP database. The MNP-SRF function then modifies the CdPA according to the rules agreed for the portability domain and routes the message to MNP-SRFB in the subscription network. + +When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information that may be retrieved from an NP database. Figure B.2.3 shows an example where the MNP-SRF function then re-routes the message to HLRB. + +## B.3 Functional Requirements of Network Entities + +### B.3.1 Procedure MNP\_SRF\_Non\_Call\_Related + +Figure B.3.1 shows the procedure MNP\_SRF\_Non\_Call\_Related. This procedure handles non-call related signalling messages. It is called from the process MNP\_SRF (see chapter 4.3). + +The check “CdPA contains own number ported out?” identifies all mobile numbers from number ranges allocated to the network the MNP-SRF is located in and which are ported to other networks. In this case the message is relayed to the subscription network. + +The check “CdPA contains own number not ported out?” identifies all mobile numbers from the number ranges allocated to the network the MNP-SRF is located in and which are still served by the network the MNP-SRF is located in, i.e. the numbers are not ported out. In this case the message is relayed to the HLR in the network. + +The check “CdPA contains foreign number ported in?” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF is located in and which are served by the network the MNP-SRF is located in, i.e. the numbers are ported in. In this case the message is relayed to the HLR in the network. + +The check “CdPA contains foreign number ported to a foreign network?” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF is located in and which are not served by the MNP-SRF is located in and not served by the network the number range is allocated to, i.e. the numbers are ported to a foreign network. In this case the message is relayed to the subscription network. + +The remaining numbers “CdPA contains number not known to be ported ?” are mobile numbers from the number ranges not allocated to the network the MNP-SRF is located in and which are also not served by the network the MNP-SRF is located in. In this case the message is relayed to the number range holder network. + +![Flowchart for Procedure MNP_SRF_Non_Call_Related. It starts with a connector symbol and proceeds through a series of decision diamonds: 'CdPA contains own number not ported out?', 'CdPA contains foreign number ported in?', 'terminate?', 'CdPA contains own number ported out?', and 'CdPA contains foreign number ported to a 3rd network'. Between the last two decisions is a process block 'MNP_SRF_Check_MNP_Indicator'. The flowchart includes several process blocks for updating CdPA (Routing Number + MSISDN or Subscriber Database Address) and ends with a merge connector symbol. Dashed boxes provide additional context for certain steps.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +### Procedure MNP\_SRF\_Non\_Call\_Related + +Procedure in MNP\_SRF to handle the Signaling Retention of Mobile Portability for Non Call Related + +Procedure MNP\_SRF\_Non\_Call\_Related FPAR IN/OUT Called Address + +``` + +graph TD + Start([ ]) --> D1{CdPA contains own number not ported out?} + D1 -- Yes --> P4[CdPA := Subscriber Database Address] + D1 -- No --> D2{CdPA contains foreign number ported in?} + D2 -- Yes --> P4 + D2 -- No --> P1[MNP_SRF_Check_MNP_Indicator] + P1 --> D3{terminate?} + D3 -- Yes --> Merge(( )) + D3 -- No --> D4{CdPA contains own number ported out?} + D4 -- Yes --> P3[CdPA := Routing Number + MSISDN] + D4 -- No --> D5{CdPA contains foreign number ported to a 3rd network} + D5 -- Yes --> P2[CdPA := Routing Number + MSISDN] + D5 -- No --> P1 + P2 --> Merge + P3 --> Merge + P4 --> Merge + P1 -.-> Note1[CdPA contains a foreign number not known to be ported!] + Note1 -.-> Note2[The use of a routing number is a matter for agreement within a portability cluster] + Note2 -.-> P1 + +``` + +Flowchart for Procedure MNP\_SRF\_Non\_Call\_Related. It starts with a connector symbol and proceeds through a series of decision diamonds: 'CdPA contains own number not ported out?', 'CdPA contains foreign number ported in?', 'terminate?', 'CdPA contains own number ported out?', and 'CdPA contains foreign number ported to a 3rd network'. Between the last two decisions is a process block 'MNP\_SRF\_Check\_MNP\_Indicator'. The flowchart includes several process blocks for updating CdPA (Routing Number + MSISDN or Subscriber Database Address) and ends with a merge connector symbol. Dashed boxes provide additional context for certain steps. + +Figure B.3.1: Procedure MNP\_SRF\_Non\_Call\_Related + +## B.4 Signalling Scenarios (informative) + +This (informative) chapter contains examples of signalling scenarios. + +### B.4.1 Delivery of SMS to a Non-ported Number – Direct Routeing – MNP-SRF acts as SCCP Relay + +Figure B.4.1 shows the MNP-SRF operation for delivering an SMS message to a non-ported number. + +![Diagram illustrating the SRF operation for delivering an SMS message to a non-ported number where the SRI_for_SM message is submitted by a national interrogating network. The diagram shows two networks: National Interrogating Network = Subscription Network and Visited Network. The process involves six steps: 1. SMSC sends Forward_SM (MSISDN) to SMS-GMSCA. 2. SMS-GMSCA sends SRI_for_SM (MSISDN, CdPA = MSISDN, TT=0, CgPA = SMS-GMSCA address) to MNP-SRFB. 3. MNP-SRFB sends SRI_for_SM (MSISDN, CdPA = HLRB address, CgPA = SMS-GMSCA address) to HLRB. 4. HLRB sends SRI_for_SM ack (VMSCB address, CdPA = SMS-GMSCA address, CgPA = HLRB address) to MNP-SRFB. 5. MNP-SRFB sends Forward_SM (VMSCB address) to VMSCB. 6. VMSCB sends Forward_SM (VMSCB address) to MSB.](1316d63eca7b84e13c27f55f0027b7b5_img.jpg) + +The diagram illustrates the signalling flow for SMS delivery to a non-ported number. It is divided into two main network domains: the National Interrogating Network (Subscription Network) and the Visited Network. + +- Step 1:** The SMSC in the National Interrogating Network sends a `Forward_SM (MSISDN)` message to the SMS-GMSCA. +- Step 2:** The SMS-GMSCA generates an `SRI_for_SM` message with `CdPA = MSISDN, TT=0` and `CgPA = SMS-GMSCA address`, and sends it to the MNP-SRFB. +- Step 3:** The MNP-SRFB analyses the MSISDN and identifies it as non-ported. It updates the `CdPA` to the HLRB address and sends the `SRI_for_SM (MSISDN, CdPA = HLRB address, CgPA = SMS-GMSCA address)` message to the HLRB. +- Step 4:** The HLRB responds with an `SRI_for_SM ack` message containing the `VMSCB address`, `CdPA = SMS-GMSCA address`, and `CgPA = HLRB address` to the MNP-SRFB. +- Step 5:** The MNP-SRFB then forwards the `Forward_SM (VMSCB address)` message to the VMSCB in the Visited Network. +- Step 6:** Finally, the VMSCB delivers the message to the MSB. + +Diagram illustrating the SRF operation for delivering an SMS message to a non-ported number where the SRI\_for\_SM message is submitted by a national interrogating network. The diagram shows two networks: National Interrogating Network = Subscription Network and Visited Network. The process involves six steps: 1. SMSC sends Forward\_SM (MSISDN) to SMS-GMSCA. 2. SMS-GMSCA sends SRI\_for\_SM (MSISDN, CdPA = MSISDN, TT=0, CgPA = SMS-GMSCA address) to MNP-SRFB. 3. MNP-SRFB sends SRI\_for\_SM (MSISDN, CdPA = HLRB address, CgPA = SMS-GMSCA address) to HLRB. 4. HLRB sends SRI\_for\_SM ack (VMSCB address, CdPA = SMS-GMSCA address, CgPA = HLRB address) to MNP-SRFB. 5. MNP-SRFB sends Forward\_SM (VMSCB address) to VMSCB. 6. VMSCB sends Forward\_SM (VMSCB address) to MSB. + +**Figure B.4.1: SRF operation for delivering an SMS message to a non-ported number where the SRI\_for\_SM message is submitted by a national interrogating network** + +1. The SMSC forwards a SM to the SMS-GMSC via a proprietary interface. +2. The SMS-GMSC generates a routeing enquiry for SM delivery. The MAP `SRI_for_SM` message is routed to the network's MNP-SRF. +3. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the `CdPA` and identifies the MSISDN as being non-ported using information which may be retrieved from an NP database. The MNP-SRF function then populates the `CdPA` with an HLRB address. After modifying the `CdPA`, the message is routed to HLRB. +4. HLRB responds to the routeing enquiry by sending back an `SRI_for_SM` ack with the address of the VMSC. +5. The SMS-GMSC can now deliver the message to the VMSCB using a `Forward_SM` message. +6. VMSCB further delivers the message to MSB. + +### B.4.2 Delivery of SMS to a Non-ported Number - Direct Routeing – MNP-SRF acts as Higher-level Relay + +Figure B.4.2 shows the MNP-SRF operation for delivering an SMS message to a non-ported number where the SRI\_for\_SM message is submitted by a national interrogating network. For further details of the higher level relay function (e.g. TC relay), the reader is referred to [7]. + +![Diagram illustrating the SRF operation for delivering an SMS message to a non-ported number. The diagram shows two main network domains: National Interrogating Network = Subscription Network and Visited Network. The process involves seven steps: 1. SMSC sends Forward_SM (MSISDN) to SMS-GMSCA. 2. SMS-GMSCA sends SRI_for_SM (MSISDN, CdPA=MSISDN, TT=0, CgPA=SMS-GMSCA address) to MNP-SRFB. 3. MNP-SRFB sends SRI_for_SM (MSISDN, CdPA=HLRB address, CgPA=MNP-SRFB address) to HLRB. 4. HLRB sends SRI_for_SM ack (VMSCB address, CdPA=MNP-SRFB address, CgPA=HLRB address) to MNP-SRFB. 5. MNP-SRFB sends SRI_for_SM ack (VMSCB address, CdPA=SMS-GMSCA address, CgPA=MNP-SRFB address) to SMS-GMSCA. 6. SMS-GMSCA sends Forward_SM (VMSCB address) to VMSCB in the Visited Network. 7. VMSCB sends the message to MSB.](1ce027dfd26183da52137cf990213724_img.jpg) + +The diagram illustrates the flow of an SMS message through various network components. On the left, the 'National Interrogating Network = Subscription Network' contains an HLRB, MNP-SRFB, and SMS-GMSCA. On the right, the 'Visited Network' contains a VMSCB and MSB. An external SMSC is shown on the far left. Arrows indicate the sequence of messages: 1. SMSC to SMS-GMSCA (Forward\_SM (MSISDN)); 2. SMS-GMSCA to MNP-SRFB (SRI\_for\_SM (MSISDN, CdPA=MSISDN, TT=0, CgPA=SMS-GMSCA address)); 3. MNP-SRFB to HLRB (SRI\_for\_SM (MSISDN, CdPA=HLRB address, CgPA=MNP-SRFB address)); 4. HLRB to MNP-SRFB (SRI\_for\_SM ack (VMSCB address, CdPA=MNP-SRFB address, CgPA=HLRB address)); 5. MNP-SRFB to SMS-GMSCA (SRI\_for\_SM ack (VMSCB address, CdPA=SMS-GMSCA address, CgPA=MNP-SRFB address)); 6. SMS-GMSCA to VMSCB (Forward\_SM (VMSCB address)); 7. VMSCB to MSB. + +Diagram illustrating the SRF operation for delivering an SMS message to a non-ported number. The diagram shows two main network domains: National Interrogating Network = Subscription Network and Visited Network. The process involves seven steps: 1. SMSC sends Forward\_SM (MSISDN) to SMS-GMSCA. 2. SMS-GMSCA sends SRI\_for\_SM (MSISDN, CdPA=MSISDN, TT=0, CgPA=SMS-GMSCA address) to MNP-SRFB. 3. MNP-SRFB sends SRI\_for\_SM (MSISDN, CdPA=HLRB address, CgPA=MNP-SRFB address) to HLRB. 4. HLRB sends SRI\_for\_SM ack (VMSCB address, CdPA=MNP-SRFB address, CgPA=HLRB address) to MNP-SRFB. 5. MNP-SRFB sends SRI\_for\_SM ack (VMSCB address, CdPA=SMS-GMSCA address, CgPA=MNP-SRFB address) to SMS-GMSCA. 6. SMS-GMSCA sends Forward\_SM (VMSCB address) to VMSCB in the Visited Network. 7. VMSCB sends the message to MSB. + +**Figure B.4.2: SRF operation for delivering an SMS message to a non-ported number where the SRI\_for\_SM message is submitted by a national interrogating network** + +1. The SMSC forwards a SM to the SMS-GMSCA via a proprietary interface. +2. The SMS-GMSCA generates a routeing enquiry for SM delivery. The MAP SRI\_for\_SM message is routed to the network's MNP-SRF. +3. When MNP-SRFB receives the message it terminates the TCAP dialogue and an MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the TCAP portion of the message and identifies the MSISDN as being non-ported using information which may be retrieved from an NP database. The MNP-SRF function then initiates a new dialogue and routes the message to HLRB. +4. HLRB responds to the routeing enquiry by sending back an SRI\_for\_SM ack with the address of the VMSC. +5. MNP-SRFB responds to the routeing enquiry by sending back an SRI\_for\_SM ack with the address of the VMSC to the SMS-GMSCA. +6. The SMS-GMSCA can now deliver the message to the VMSCB using a Forward\_SMS message. +7. VMSCB further delivers the message to MSB. + +### B.4.3 Delivery of SMS to a Ported Number – Indirect Routeing + +Figure B.4.3 shows the MNP-SRF operation for delivering an SMS message to a ported number where the interrogating network does not support direct routeing. + +The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRF(s). If the MNP-SRF(s) use(s) a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. + +![Diagram of SRF operation for delivering an SMS message to a ported number where the interrogating network does not support direct routeing. The diagram shows four network domains: (Inter-)national Interrogating Network, Number Range Holder Network, Subscription Network, and Visited Network. The flow involves an SMSC forwarding an SMS to an SMS-GMSCA, which then sends an SRI_for_SM enquiry to the Number Range Holder Network's MNP-SRFB'. The MNP-SRFB' identifies the number as ported and routes the enquiry to the Subscription Network's MNP-SRFB. The MNP-SRFB identifies the number as ported into its network and routes the enquiry to the HLRB. The HLRB responds with an SRI_for_SM ack containing the VMSCB address. The SMS-GMSCA then forwards the SMS to the VMSCB, which finally delivers it to the MSB.](552328a9daaf3bc0069424b500025880_img.jpg) + +The diagram illustrates the following message flow: + +- 1** SMSC → SMS-GMSCA: Forward\_SM (MSISDN) +- 2** SMS-GMSCA → MNP-SRFB' (Number Range Holder Network): SRI\_for\_SM (MSISDN) +CdPA = MSISDN, TT=0 +CgPA = SMS-GMSCA address +- 3** MNP-SRFB' → MNP-SRFB (Subscription Network): SRI\_for\_SM (MSISDN) +CdPA = RN (+MSISDN) +CgPA = SMS-GMSCA address +- 4** MNP-SRFB → HLRB: SRI\_for\_SM (MSISDN) +CdPA = HLRB address +CgPA = SMS-GMSCA address +- 5** HLRB → MNP-SRFB': SRI\_for\_SM ack (VMSCB address) +CdPA = SMS-GMSCA address +CgPA = HLRB address +- 6** SMS-GMSCA → VMSCB (Visited Network): Forward\_SM (VMSCB address) +- 7** VMSCB → MSB + +Diagram of SRF operation for delivering an SMS message to a ported number where the interrogating network does not support direct routeing. The diagram shows four network domains: (Inter-)national Interrogating Network, Number Range Holder Network, Subscription Network, and Visited Network. The flow involves an SMSC forwarding an SMS to an SMS-GMSCA, which then sends an SRI\_for\_SM enquiry to the Number Range Holder Network's MNP-SRFB'. The MNP-SRFB' identifies the number as ported and routes the enquiry to the Subscription Network's MNP-SRFB. The MNP-SRFB identifies the number as ported into its network and routes the enquiry to the HLRB. The HLRB responds with an SRI\_for\_SM ack containing the VMSCB address. The SMS-GMSCA then forwards the SMS to the VMSCB, which finally delivers it to the MSB. + +**Figure B.4.3: SRF operation for delivering an SMS message to a ported number where the interrogating network does not support direct routeing** + +1. The SMSC forwards a SM to the SMS-GMSC via a proprietary interface. +2. The SMS-GMSC generates a routeing enquiry for SM delivery. The MAP SRI\_for\_SM message is routed to the number range holder network's MNP-SRF. +3. When MNP-SRFB' receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. As the message is non-call related, the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. After modifying the CdPA, the message is routed to MNP-SRFB in the subscription network. +4. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. +5. HLRB responds to the routeing enquiry by sending back an SRI\_for\_SM ack with the address of the VMSC. +6. The SMS-GMSC can now deliver the message to the VMSCB using a Forward\_SMS message. +7. VMSCB further delivers the message to MSB. + +### B.4.4 Delivery of SMS to a Ported Number – Direct Routeing + +Figure B.4.4 shows the MNP-SRF operation for delivering an SMS message to a ported number where the interrogating network supports direct routeing. + +The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs. If the MNP-SRFs use a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. + +![Diagram illustrating the SRF operation for delivering an SMS message to a ported number where the interrogating network supports direct routing. The diagram shows three network domains: National Interrogating Network, Subscription Network, and Visited Network. The process involves seven steps: 1. SMSC forwards SM to SMS-GMSCA. 2. SMS-GMSCA sends SRI_for_SM to MNP-SRFA. 3. MNP-SRFA routes SRI_for_SM to MNP-SRFB. 4. MNP-SRFB sends SRI_for_SM to HLRB. 5. HLRB responds with SRI_for_SM ack to MNP-SRFB. 6. MNP-SRFB routes SRI_for_SM ack to SMS-GMSCA. 7. SMS-GMSCA forwards SM to VMSCB, which then delivers it to MSB.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +The diagram illustrates the SRF operation for delivering an SMS message to a ported number where the interrogating network supports direct routing. It shows the flow of messages between the National Interrogating Network, Subscription Network, and Visited Network. + +**National Interrogating Network:** Contains SMSC, SMS-GMSCA, and MNP-SRFA. + +**Subscription Network:** Contains HLRB and MNP-SRFB. + +**Visited Network:** Contains VMSCB and MSB. + +**Message Flow:** + +- SMSC forwards SM (MSISDN) to SMS-GMSCA. +- SMS-GMSCA generates SRI\_for\_SM (MSISDN) with CdPA = MSISDN, TT=0 and CgPA = SMS-GMSCA address, routing it to MNP-SRFA. +- MNP-SRFA receives SRI\_for\_SM (MSISDN) with CdPA = RN (+MSISDN), TT=0 and CgPA = SMS-GMSCA address, routing it to MNP-SRFB. +- MNP-SRFB receives SRI\_for\_SM (MSISDN) with CdPA = HLRB address and CgPA = SMS-GMSCA address, routing it to HLRB. +- HLRB responds with SRI\_for\_SM ack (VMSCB address) with CdPA = SMS-GMSCA address and CgPA = HLRB address, routing it to MNP-SRFB. +- MNP-SRFB routes SRI\_for\_SM ack (VMSCB address) with CdPA = SMS-GMSCA address and CgPA = HLRB address to SMS-GMSCA. +- SMS-GMSCA forwards SM (VMSCB address) to VMSCB, which then delivers it to MSB. + +Diagram illustrating the SRF operation for delivering an SMS message to a ported number where the interrogating network supports direct routing. The diagram shows three network domains: National Interrogating Network, Subscription Network, and Visited Network. The process involves seven steps: 1. SMSC forwards SM to SMS-GMSCA. 2. SMS-GMSCA sends SRI\_for\_SM to MNP-SRFA. 3. MNP-SRFA routes SRI\_for\_SM to MNP-SRFB. 4. MNP-SRFB sends SRI\_for\_SM to HLRB. 5. HLRB responds with SRI\_for\_SM ack to MNP-SRFB. 6. MNP-SRFB routes SRI\_for\_SM ack to SMS-GMSCA. 7. SMS-GMSCA forwards SM to VMSCB, which then delivers it to MSB. + +**Figure B.4.4: SRF operation for delivering an SMS message to a ported number where the interrogating network supports direct routing** + +1. The SMSC forwards a SM to the SMS-GMSC via a proprietary interface. +2. The SMS-GMSC generates a routeing enquiry for SM delivery. The MAP SRI\_for\_SM message is routed to the network's MNP-SRF. +3. When MNP-SRFA receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. As the message is non-call related, the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. After modifying the CdPA, the message is routed to MNP-SRFB in the subscription network. +4. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. +5. HLRB responds to the routeing enquiry by sending back an SRI\_for\_SM ack with the address of the VMSC. +6. The SMS-GMSC can now deliver the message to the VMSCB using a Forward\_SMS message. +7. VMSCB further delivers the message to MSB. + +### B.4.5 International SOR for a Non-ported Number + +Figure B.4.5 shows the MNP-SRF operation for optimally routeing an international call to a non-ported number. + +The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRF. If the MNP-SRF uses a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. + +![Diagram illustrating the SRF operation for optimally routing an international call to a non-ported number. The diagram shows three network domains: International Originating/Interrogating Network, Subscription Network = Number Range Holder Network, and Visited Network. The flow involves 7 steps: 1. MSA originates a call to MSISDN. 2. VMSCA routes the call to the originating network's GMSCA (IAM (MSISDN)). 3. GMSCA sends an SRI (OR, MSISDN) to the MNP SRFB (CdPA = MSISDN, TT=0; CgPA = GMSCA address). 4. MNP SRFB sends an SRI (OR, MSISDN) to the HLRB (CdPA = HLRB address; CgPA = GMSCA address). 5. HLRB sends an SRI ack (MSRN) to the GMSCA (CdPA = GMSCA address; CgPA = HLRB address). 6. GMSCA routes the call to VMSCB (IAM (MSRN)). 7. VMSCB establishes a traffic channel to MSB.](3493d7ba4c86f944e159de1bf45ff03d_img.jpg) + +The diagram illustrates the signaling flow for an international call to a non-ported number. It is divided into three main network areas: International Originating/Interrogating Network, Subscription Network = Number Range Holder Network, and Visited Network. + +- International Originating/Interrogating Network:** Contains MSA, VMSCA, and GMSCA. +- Subscription Network = Number Range Holder Network:** Contains HLRB and MNP SRFB. +- Visited Network:** Contains VMSCB and MSB. + +The sequence of operations is as follows: + +- MSA originates a call to MSISDN. +- VMSCA routes the call to the originating network's GMSCA (IAM (MSISDN)). +- GMSCA sends an SRI (OR, MSISDN) to the MNP SRFB. The message parameters are: CdPA = MSISDN, TT=0; CgPA = GMSCA address. +- MNP SRFB sends an SRI (OR, MSISDN) to the HLRB. The message parameters are: CdPA = HLRB address; CgPA = GMSCA address. +- HLRB sends an SRI ack (MSRN) to the GMSCA. The message parameters are: CdPA = GMSCA address; CgPA = HLRB address. +- GMSCA routes the call to VMSCB (IAM (MSRN)). +- VMSCB establishes a traffic channel to MSB. + +Diagram illustrating the SRF operation for optimally routing an international call to a non-ported number. The diagram shows three network domains: International Originating/Interrogating Network, Subscription Network = Number Range Holder Network, and Visited Network. The flow involves 7 steps: 1. MSA originates a call to MSISDN. 2. VMSCA routes the call to the originating network's GMSCA (IAM (MSISDN)). 3. GMSCA sends an SRI (OR, MSISDN) to the MNP SRFB (CdPA = MSISDN, TT=0; CgPA = GMSCA address). 4. MNP SRFB sends an SRI (OR, MSISDN) to the HLRB (CdPA = HLRB address; CgPA = GMSCA address). 5. HLRB sends an SRI ack (MSRN) to the GMSCA (CdPA = GMSCA address; CgPA = HLRB address). 6. GMSCA routes the call to VMSCB (IAM (MSRN)). 7. VMSCB establishes a traffic channel to MSB. + +**Figure B.4.5: SRF operation for optimally routeing an international call to a non-ported number** + +- MSA originates a call to MSISDN. +- VMSCA routes the call to the originating network's GMSCA. +- When GMSCA receives the ISUP IAM, it requests routing information by submitting a MAP SRI with SOR parameter set to the number range holder network of the dialed MSISDN. Within the number range holder network, the message is routed to the network's MNP-SRF. +- When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being non-ported using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. +- When HLRB receives the SRI, it responds to the GMSCA by sending back an SRI ack with a MSRN. +- GMSCA uses the MSRN to route the call to VMSCB. +- VMSCB further establishes a traffic channel to MSB. + +### B.4.6 SOR for a Ported Number – Indirect Routeing + +Figure B.4.6 shows the MNP-SRF operation for optimally routeing a call (using SOR) to a ported number where the interrogating network does not support direct routeing. + +The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs. If the MNP-SRFs use a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. + +![Diagram illustrating the MNP-SRF operation for optimally routeing a call (using SOR) to a ported number where the interrogating network does not support direct routeing. The diagram shows four network domains: International Originating/Interrogating Network, Number Range Holder Network, Subscription Network, and Visited Network. The call flow involves an MSA originating a call to an MSISDN, which is routed through a VMSCB and GMSCA. The GMSCA sends an SRI (SOR, MSISDN) to the Number Range Holder Network's MNP-SRFB'. The MNP-SRFB' identifies the number as ported and routes the SRI to the Subscription Network's MNP-SRFB. The MNP-SRFB then sends an SRI (SOR, MSISDN) to the HLRB. The HLRB responds with an SRI ack (MSRN). The GMSCA then routes the call to the Visited Network's VMSCB, which establishes a traffic channel to the MSB.](c0c7f65c51c83fbe595b47326f6b089a_img.jpg) + +The diagram illustrates the message flow for MNP-SRF operation in an indirect routing scenario. It involves four main network components: International Originating/Interrogating Network, Number Range Holder Network, Subscription Network, and Visited Network. + +- International Originating/Interrogating Network:** Contains MSA, VMSCB, and GMSCA. The MSA originates a call to MSISDN (1). The VMSCB routes the call to the GMSCA (2) via an IAM (MSISDN) message. +- Number Range Holder Network:** Contains MNP-SRFB'. The GMSCA sends an SRI (SOR, MSISDN) to the MNP-SRFB' (3). The MNP-SRFB' identifies the number as ported and routes the SRI to the Subscription Network's MNP-SRFB (4). The MNP-SRFB' also receives an SRI ack (MSRN) from the HLRB (6). +- Subscription Network:** Contains HLRB and MNP-SRFB. The MNP-SRFB receives the SRI (SOR, MSISDN) from the MNP-SRFB' (4) and sends an SRI (SOR, MSISDN) to the HLRB (5). The HLRB responds with an SRI ack (MSRN) (6). +- Visited Network:** Contains VMSCB and MSB. The GMSCA routes the call to the VMSCB (7) via an IAM (MSRN) message. The VMSCB establishes a traffic channel to the MSB (8). + +Message details: + +- Step 3:** SRI (SOR, MSISDN), CdPA = MSISDN, TT=0, CgPA = GMSCA address +- Step 4:** SRI (SOR, MSISDN), CdPA = RN (+MSISDN), TT=0, CgPA = GMSCA address +- Step 5:** SRI (SOR, MSISDN), CdPA = HLRB address, CgPA = GMSCA address +- Step 6:** SRI ack (MSRN), CdPA = GMSCA address, CgPA = HLRB address + +Diagram illustrating the MNP-SRF operation for optimally routeing a call (using SOR) to a ported number where the interrogating network does not support direct routeing. The diagram shows four network domains: International Originating/Interrogating Network, Number Range Holder Network, Subscription Network, and Visited Network. The call flow involves an MSA originating a call to an MSISDN, which is routed through a VMSCB and GMSCA. The GMSCA sends an SRI (SOR, MSISDN) to the Number Range Holder Network's MNP-SRFB'. The MNP-SRFB' identifies the number as ported and routes the SRI to the Subscription Network's MNP-SRFB. The MNP-SRFB then sends an SRI (SOR, MSISDN) to the HLRB. The HLRB responds with an SRI ack (MSRN). The GMSCA then routes the call to the Visited Network's VMSCB, which establishes a traffic channel to the MSB. + +**Figure B.4.6: MNP-SRF operation for optimally routeing a call (using SOR) to a ported number where the interrogating network does not support direct routeing** + +1. MSA originates a call to MSISDN. +2. VMSCA routes the call to the network's GMSCA. +3. When GMSCA receives the ISUP IAM, it requests routeing information by submitting a MAP SRI with SOR parameter set to the number range holder network of the dialled MSISDN. Within the number range holder network, the message is routed to the network's MNP-SRF. +4. When MNP-SRFB' receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. As the message is non-call related, the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. After modifying the CdPA, the message is routed to MNP-SRFB in the subscription network. +5. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. +6. When HLRB receives the SRI, it responds to the GMSCA by sending back an SRI ack with a MSRN. +7. GMSCA uses the MSRN to route the call to VMSCB. +8. VMSCB further establishes a traffic channel to MSB. + +### B.4.7 Any Time Interrogation for a Ported Number – Indirect Routing + +Figure B.4.7 shows the MNP-SRF operation for routing an Any\_Time\_Interrogation message for a ported number where the interrogating network does not support direct routing. + +The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs. If the MNP-SRFs use a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. + +![Diagram illustrating the MNP-SRF operation for routing an Any_Time_Interrogation (ATI) message for a ported number via indirect routing. The diagram shows two networks: Subscription Network and Number Range Holder Network. The Subscription Network contains gsmSCF, MNP SRFB, and HLRB. The Number Range Holder Network contains MNP SRFB'. The message flow is: 1. gsmSCF sends ATI (MSISDN) to MNP SRFB' (CdPA = MSISDN, TT=0, CgPA = gsmSCF address). 2. MNP SRFB' receives the message, identifies the MSISDN as being ported, and routes it to MNP SRFB in the Subscription Network (CdPA = RN (+MSISDN), TT=0, CgPA = gsmSCF address). 3. MNP SRFB receives the message, identifies the MSISDN as being ported into the network, and routes it to HLRB (CdPA = HLRB address, CgPA = gsmSCF address). 4. HLRB responds with ATI ack (CdPA = gsmSCF address, CgPA = HLRB address).](7722d62e33dcc894cc8555e9474c5606_img.jpg) + +``` + +sequenceDiagram + participant gsmSCF + participant MNP_SRFB as MNP SRFB + participant HLRB + participant MNP_SRFB_prime as MNP SRFB' + + Note left of gsmSCF: Subscription Network + Note right of MNP_SRFB_prime: Number Range Holder Network + + gsmSCF->>MNP_SRFB_prime: 1. ATI (MSISDN) +CdPA = MSISDN, TT=0 +CgPA = gsmSCF address + MNP_SRFB_prime->>MNP_SRFB: 2. ATI (MSISDN) +CdPA = RN (+MSISDN), TT=0 +CgPA = gsmSCF address + MNP_SRFB->>HLRB: 3. ATI (MSISDN) +CdPA = HLRB address +CgPA = gsmSCF address + HLRB->>gsmSCF: 4. ATI ack +CdPA = gsmSCF address +CgPA = HLRB address + +``` + +Diagram illustrating the MNP-SRF operation for routing an Any\_Time\_Interrogation (ATI) message for a ported number via indirect routing. The diagram shows two networks: Subscription Network and Number Range Holder Network. The Subscription Network contains gsmSCF, MNP SRFB, and HLRB. The Number Range Holder Network contains MNP SRFB'. The message flow is: 1. gsmSCF sends ATI (MSISDN) to MNP SRFB' (CdPA = MSISDN, TT=0, CgPA = gsmSCF address). 2. MNP SRFB' receives the message, identifies the MSISDN as being ported, and routes it to MNP SRFB in the Subscription Network (CdPA = RN (+MSISDN), TT=0, CgPA = gsmSCF address). 3. MNP SRFB receives the message, identifies the MSISDN as being ported into the network, and routes it to HLRB (CdPA = HLRB address, CgPA = gsmSCF address). 4. HLRB responds with ATI ack (CdPA = gsmSCF address, CgPA = HLRB address). + +**Figure B.4.7: MNP-SRF operation for routing an Any\_Time\_Interrogation message for a ported number where the interrogating network does not support direct routing** + +1. The gsmSCF generates an Any\_Time\_Interrogation (ATI) message. The message is routed to the number range holder network's MNP-SRF. +2. When MNP-SRFB' receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. As the message is non-call related, the MNP-SRF function then populates the CdPA with either a routing number or a concatenation of a routing number and MSISDN. After modifying the CdPA, the message is routed to MNP-SRFB in the subscription network. +3. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. +4. HLRB responds to the ATI by sending back an ATI ack with the requested information. + +### B.4.8 Any Time Interrogation for a Ported Number – Direct Routing + +Figure B.4.8 shows the MNP-SRF operation for routing an Any\_Time\_Interrogation message for a ported number where the interrogating network supports direct routing. + +The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRF. If the MNP-SRF uses a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. + +![Diagram of MNP-SRF operation for direct routing of ATI messages.](21327313f7b18a481da0c87a6472a80d_img.jpg) + +The diagram illustrates the message flow within a 'Subscription Network' (indicated by a dashed box). It features three main components: gsmSCF, MNP SRFB, and HLRB. The flow is numbered 1 to 3: + +- Step 1:** gsmSCF sends an ATI (MSISDN) message to MNP SRFB. The message parameters are: CdPA = MSISDN, TT=0; CgPA = gsmSCF address. +- Step 2:** MNP SRFB sends an ATI (MSISDN) message to HLRB. The message parameters are: CdPA = HLRB address; CgPA = gsmSCF address. +- Step 3:** HLRB sends an ATI ack message back to gsmSCF. The message parameters are: CdPA = gsmSCF address; CgPA = HLRB address. + +Diagram of MNP-SRF operation for direct routing of ATI messages. + +**Figure B.4.8: MNP-SRF operation for routing an Any\_Time\_Interrogation message for a ported number where the interrogating network supports direct routing** + +1. The gsmSCF generates an Any\_Time\_Interrogation (ATI) message. The message is routed to the network's MNP-SRF. +2. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. +3. HLRB responds to the ATI by sending back an ATI ack with the requested information. + +### B.4.9 CCBS where the Busy Subscriber is a Ported Subscriber - Direct Routeing + +Figure B.4.9 shows the MNP-SRF operation for routeing a CCBS Request for a ported number where the interrogating network supports direct routeing. + +The message flows for this scenario are based on the use of an SCCP-relay function in the MNP-SRFs. If the MNP-SRFs use a higher-level relay function (e.g. TC-relay), then the response message will go via the MNP-SRF as shown in B.4.2. For further details of the signalling relay functions, the reader is referred to [7]. + +![Diagram illustrating the MNP-SRF operation for routeing a CCBS Request for a ported number where the interrogating network supports direct routeing. The diagram shows four main components: Network visited by A, Subscription Network of A, Subscription Network of B, and Network visited by B. The sequence of messages is: 1. VMSCB sends a Release (cause = subscriber busy) to VLRA/VMSCA. 2. VLRA/VMSCA sends a Register_CC_Entry to HLRA. 3. HLRA sends a CCBS Request (MSISDN) to MNP-SRFA. 4. MNP-SRFA sends a CCBS Request (MSISDN) to MNP-SRFB. 5. MNP-SRFB sends a CCBS Request (MSISDN) to HLRB. 6. HLRB sends a CCBS Requestack to HLRA.](408c4798ea60469e0728a7cbbd598668_img.jpg) + +The diagram illustrates the following message flow: + +- Step 1:** VMSCB (Network visited by B) sends a **Release (cause = subscriber busy)** message to VLRA/VMSCA (Network visited by A). +- Step 2:** VLRA/VMSCA sends a **Register\_CC\_Entry** message to HLRA (Subscription Network of A). The message contains: +CdPA = HLR address +CgPA = VLRA address +- Step 3:** HLRA sends a **CCBS Request (MSISDN)** message to MNP-SRFA. The message contains: +CdPA = MSISDN, TT=17 +CgPA = HLRA address +- Step 4:** MNP-SRFA sends a **CCBS Request (MSISDN)** message to MNP-SRFB. The message contains: +CdPA = RN (+MSISDN), TT=17 +CgPA = HLRA address +- Step 5:** MNP-SRFB sends a **CCBS Request (MSISDN)** message to HLRB (Subscription Network of B). The message contains: +CdPA = HLRB address +CgPA = HLRA address +- Step 6:** HLRB sends a **CCBS Requestack** message to HLRA. The message contains: +CdPA = HLRA address +CgPA = HLRB address + +Diagram illustrating the MNP-SRF operation for routeing a CCBS Request for a ported number where the interrogating network supports direct routeing. The diagram shows four main components: Network visited by A, Subscription Network of A, Subscription Network of B, and Network visited by B. The sequence of messages is: 1. VMSCB sends a Release (cause = subscriber busy) to VLRA/VMSCA. 2. VLRA/VMSCA sends a Register\_CC\_Entry to HLRA. 3. HLRA sends a CCBS Request (MSISDN) to MNP-SRFA. 4. MNP-SRFA sends a CCBS Request (MSISDN) to MNP-SRFB. 5. MNP-SRFB sends a CCBS Request (MSISDN) to HLRB. 6. HLRB sends a CCBS Requestack to HLRA. + +**Figure B.4.9: MNP-SRF operation for routeing a CCBS Request for a ported number where the interrogating network supports direct routeing** + +1. The VMSCA receives a ISUP Release message with cause value 'subscriber busy' from VMSCB. +2. VLRA/VMSCA sends a Register\_CC\_Entry to HLRA using the HLRA address as CdPA on SCCP. +3. The HLRA sends a CCBS Request message to the networks MNP-SRFA. +4. When MNP-SRFA receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an NP database. As the message is non-call related, the MNP-SRF function then populates the CdPA with either a routeing number or a concatenation of a routeing number and MSISDN. After modifying the CdPA, the message is routed to MNP-SRFB in the subscription network. +5. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. +6. HLRB can now respond to HLRA by sending back a CCBS ack message. + +### B.4.10 Calling Name Presentation Flows – MNP-SRF acts as SCCP Relay + +Figure B.4.10 shows the MNP-SRF operation for delivering an CNAP message to an ANSI Calling Name Database. + +![Diagram illustrating the SRF operation for delivering an CNAP message to the CNDB. The diagram shows four steps: 1. MSC sends a Query with Permission (MSISDN) to MNP SRFB. 2. MNP SRFB routes the query to CNDB. 3. CNDB responds with a Query with Permission ack (Calling Name) to MNP SRFB. 4. MNP SRFB routes the response back to MSC.](c419b566d720267c499087add1506018_img.jpg) + +The diagram illustrates the interaction between an MSCA, an MNP SRFB, and a CNDB within a National Interrogating Network (Subscription Network). The sequence of messages is as follows: + +``` + + sequenceDiagram + participant MSCA + participant MNP_SRFB as MNP SRFB + participant CNDB + + Note over MSCA, CNDB: National Interrogating Network = Subscription Network + + Note left of MSCA: 1 + MSCA->>MNP_SRFB: Query with Permission (MSISDN) +CdPA = MSISDN, TT=5 +CgPA = MSCA address + Note right of MNP_SRFB: 2 + MNP_SRFB->>CNDB: Query with Permission (MSISDN) +CdPA = CNDB address +CgPA = MSCA address + Note right of CNDB: 3 + CNDB->>MNP_SRFB: Query with Permission ack (Calling Name) +CdPA = MSCA address +CgPA = CNDB address + Note left of MNP_SRFB: 4 + MNP_SRFB->>MSCA: Query with Permission ack (Calling Name) + +``` + +Diagram illustrating the SRF operation for delivering an CNAP message to the CNDB. The diagram shows four steps: 1. MSC sends a Query with Permission (MSISDN) to MNP SRFB. 2. MNP SRFB routes the query to CNDB. 3. CNDB responds with a Query with Permission ack (Calling Name) to MNP SRFB. 4. MNP SRFB routes the response back to MSC. + +**Figure B.4.10: SRF operation for delivering an CNAP message to the CNDB** + +1. An incoming call ( an Initial Address message with Generic Name parameter set to “presentation allowed” ) is received at a MSC. The MSC interrogates the VLR to determine if the called party is subscribed to the CNAP service. The VLR Response indicates that the called party is subscribed to CNAP; +2. The MSC generates a TCAP message “Query With Permission”. The Query With Permission message is routed to the network’s MNP-SRF; +3. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies which CNDB the MSISDN is populated using information which may be retrieved from an NP database. The MNP-SRF function then populates the CdPA with an CNDB address. After modifying the CdPA, the message is routed to CNDB; +4. CNDB responds to the routing enquiry by sending back a Query With Permission ack with the address of the MSC. The MSC can now deliver the Calling Name to the terminating subscriber . + +# --- Annex C (normative): MNP Signalling Relay Function - Call Related Signalling + +## C.1 Handling of Call Related Signalling + +The MAP messages affected by MNP are the MAP\_SEND\_ROUTING\_INFORMATION (SRI) message without OR parameter set sent to the HLR and the MAP\_ANY\_TIME\_INTERROGATION (ATI) message with parameter MNP-requestedInfo present terminated in the MNP-SRF. + +In a PLMN supporting MNP with direct routeing using signalling relay, all incoming calls and calls originated in the network for which the called party number is within the ranges owned by any network in the portability domain, the gateway MSCs will send an SRI such that it will be handled by the MNP-SRF in that network. + +In a PLMN supporting MNP with direct routeing, where the called party number is within the ranges owned by any network in the portability domain, the INE sends an MNP Information request (ATI) such that it will be handled by the MNP-SRF in the network. + +In a PLMN supporting MNP with indirect routeing using signalling relay, all incoming calls and calls originating in the network, for which the called party number is within the range owned by the network, the gateway MSCs will send SRI such that it will be handled by the MNP-SRF in that network. + +In a PLMN supporting MNP with indirect routeing, the INE sends an MNP Information Request (ATI) such that it will be handled by the MNP-SRF in the Number Range Holder Network. + +The MNP-SRF obtains routeing information from the NP database to identify the subscription network associated with a particular national MSISDN. The interface between the MNP-SRF and the NP database is considered implementation dependent and is not detailed further. + +From the perspective of the PLMN in which the MNP-SRF resides, the CdPA represents one of: + +1. An own number ported out. +2. An own number not ported out. +3. A foreign number ported in. +4. A foreign number ported to a foreign network. +5. A foreign number not known to be ported. + +Cases 4 and 5 are applicable only for direct routeing. + +For SRI: + +In case 1, the MNP-SRF may perform one of the following depending on agreements within the number portability domain. + +- a. An SRI response is sent containing the necessary routeing information to route the call to the subscription network. This is performed by an internal MAP Application Termination Function (MATF) known as the Number Portability Location Register (NPLR). +- b. If indirect routeing of calls with reference to the subscription network is used, the message is relayed to the MNP-SRF in the subscription network, whose NPLR provides the necessary routeing information in an SRI response. The use of an NPLR in the subscription network can only be by agreement within the number portability domain. + +In cases 2 and 3, the MNP-SRF relays the message to the HLR. For further details of the signalling relay function, the reader is referred to [7]. + +In case 4, an SRI response is sent, containing the necessary routeing information to route the call to the subscription network. + +In case 5, an SRI response is sent, containing the necessary routing information to route the call to the number range holder network. + +For ATI: + +In all cases the MNP information request (ATI) is sent to the MNP\_SRF\_MATF\_Info\_Request procedure/MAP Application Termination Function (MATF) for handling. A response is sent to the INE containing MNP information or an error is returned. + +## --- C.2 Functional Requirements of Network Entities + +### C.2.1 Procedure MNP\_SRF\_MATF\_Call\_Related + +Figure C.2.2 shows the procedure MNP\_SRF\_MATF\_Call\_Related. This procedure handles call-related signalling messages. It is called from the process MNP\_SRF (see clause 4.3). + +The check “message has been relayed” identifies all call related signalling messages which are relayed from the number range holder network towards the subscription network in the case of Indirect Routing with reference to subscription network implementation. These messages only refer to numbers ported into the network. + +The check “own number not ported out” identifies all mobile numbers from number ranges allocated to the network the MNP-SRF/MATF is located in and which are not ported to other networks. In this case the call related message is relayed to the HLR in the network. + +The check “foreign number ported in” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF/MATF is located in and which are served by the network the MNP-SRF/MATF is located in. In this case the call related message is relayed to the HLR in the network. + +The check “foreign number not known to be ported” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF/MATF is located in and which are also not served by the network the MNP-SRF/MATF is located in. In this case the call is sent to the SRF\_MATF procedure for handling. + +The check “foreign number ported to foreign network” identifies all mobile numbers from the number ranges not allocated to the network the MNP-SRF/MATF is located in and which are not served by the network the MNP-SRF is located in and not served by the network the number range is allocated to, i.e. the number is ported between two other networks. In this case the call related message is sent to the SRF\_MATF procedure for handling. + +The remaining cases “own number ported out” are mobile numbers allocated to the network the MNP-SRF/MATF is located in and which are served by other networks, i.e. the number is ported out to another network. In this case the call is relayed to the MATF in the subscription network if this option is the one used by the operator, or sent to the SRF\_MATF procedure for handling if not. + +### C.2.2 Process SRI\_NPLR + +Figure C.2.2.2 shows the process SRI\_NPLR. + +The check “unknown subscriber” identifies a subscriber without any associated available information. + +If the GMSC is in the database own network then a routing number is provided to route to the number range holder network. + +If the GMSC is not in the database own network then the enquiry has been routed from the number range holder network, so the call should fail. + +The database query uses the MSISDN received at the application level in the SRI, rather than the CdPA of the SCCP level. + +If an error must be set as a result of the check “terminate”, the user error “unknown subscriber” shall be used. If version 3 or higher of the MAP protocol is in use, then the diagnostic “NPDB mismatch” may be used. + +The check “HPLMN MSISDN Range” identifies if the MSISDN received in the SRI exists in a MSISDN Range owned by the HPLMN. This is a North American Network implementation option and allows a MAP Error “Unknown Subscriber” to be sent to the GMSC instead of the MSISDN. + +The check “HPLMN RN Range” identifies if the Routeing Number assigned to the MSISDN within the SRI\_NPLR is assigned to the HPLMN. This is a North American Network implementation option and allows a MAP Error “Unknown Subscriber” to be sent to the GMSC instead of the RN+MSISDN. + +### C.2.3 Procedure MNP\_SRF\_MATF\_Info\_Request + +Figure C.2.3.1 shows the procedure MNP\_SRF\_MATF\_Info\_Request. This procedure handles an information request signalling message to provide MNP information for a subscriber. It is called from the process MNP\_SRF (see clause 4.3). + +### C.2.4 Process ATI\_NPLR + +Figure C.2.3.2 shows the process ATI\_NPLR. + +The database query uses the MSISDN received at the application level in the ATI, rather than the CdPA of the SCCP level. + +![Flowchart for Procedure MNP_SRF_MATF_Call_Related. It starts with 'Query Database'. If 'own number, not ported out', it goes to 'CdPA := HLR address' and ends. If 'no', it checks 'foreign number, ported in'. If 'yes', it goes to 'CdPA := HLR address' and ends. If 'no', it checks 'foreign number, not known to be ported'. If 'yes', it goes to 'MATF' -> 'set: terminate' and ends. If 'no', it checks 'foreign number, ported to other foreign network'. If 'yes', it goes to 'MATF' -> 'set: terminate' and ends. If 'no', it goes to 'Indirect Routeing with Reference to Subscription Network' -> 'OPTION'. From 'OPTION', 'yes' leads to 'MATF' -> 'set: terminate' and ends, while 'no' leads to 'CdPA := RN + MSISDN' and ends. A dashed box indicates that for the 'yes' path from 'OPTION', it 'must be own number, ported out'. Another 'OPTION' at the top right leads to 'message has been relayed' (no) or back to 'Query Database' (yes). A third 'OPTION' in the middle right leads to 'Indirect Routeing with Reference to Subscription Network' (yes) or 'MATF' -> 'set: terminate' and ends (no). From the 'MATF' -> 'set: terminate' path in the third 'OPTION', a 'routeing error' leads to 'SCCP error handling' and back to the 'MATF' block.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +### Procedure MNP\_SRF\_MATF\_Call\_Related 1(1) + +Procedure in the MNP-SRF for call related signalling + +``` +graph TD + QueryDatabase[Query Database] --> D1{ } + D1 -- "own number, not ported out" --> CdPA_HLR[CdPA := HLR address] + D1 -- "no" --> D2{ } + D2 -- "foreign number, ported in" --> D2_Yes{yes} + D2_Yes -- yes --> CdPA_HLR + D2 -- "no" --> D3{ } + D3 -- "foreign number, not known to be ported" --> D3_Yes{yes} + D3_Yes -- yes --> MATF1[MATF] + MATF1 --> set1[set: terminate] + set1 --> End1((X)) + D3 -- "no" --> D4{ } + D4 -- "foreign number, ported to other foreign network" --> D4_Yes{yes} + D4_Yes -- yes --> MATF2[MATF] + MATF2 --> set2[set: terminate] + set2 --> End2((X)) + D4 -- "no" --> Indirect1[Indirect Routeing with Reference to Subscription Network] + Indirect1 --> OPTION1{OPTION} + OPTION1 -- yes --> MATF3[MATF] + MATF3 --> set3[set: terminate] + set3 --> End3((X)) + OPTION1 -- no --> CdPA_RN[CdPA := RN + MSISDN] + CdPA_RN --> End4((X)) + Note1[must be own number, ported out] -.-> set3 + QueryDatabase -- no --> MessageRelayed{message has been relayed} + MessageRelayed -- yes --> QueryDatabase + MessageRelayed -- no --> Indirect2[Indirect Routeing with Reference to Subscription Network] + Indirect2 --> OPTION2{OPTION} + OPTION2 -- yes --> Indirect2 + OPTION2 -- no --> MATF4[MATF] + MATF4 --> set4[set: terminate] + set4 --> End5((X)) + MATF4 -- "routeing error" --> SCCP[SCCP error handling] + SCCP --> MATF4 +``` + +Flowchart for Procedure MNP\_SRF\_MATF\_Call\_Related. It starts with 'Query Database'. If 'own number, not ported out', it goes to 'CdPA := HLR address' and ends. If 'no', it checks 'foreign number, ported in'. If 'yes', it goes to 'CdPA := HLR address' and ends. If 'no', it checks 'foreign number, not known to be ported'. If 'yes', it goes to 'MATF' -> 'set: terminate' and ends. If 'no', it checks 'foreign number, ported to other foreign network'. If 'yes', it goes to 'MATF' -> 'set: terminate' and ends. If 'no', it goes to 'Indirect Routeing with Reference to Subscription Network' -> 'OPTION'. From 'OPTION', 'yes' leads to 'MATF' -> 'set: terminate' and ends, while 'no' leads to 'CdPA := RN + MSISDN' and ends. A dashed box indicates that for the 'yes' path from 'OPTION', it 'must be own number, ported out'. Another 'OPTION' at the top right leads to 'message has been relayed' (no) or back to 'Query Database' (yes). A third 'OPTION' in the middle right leads to 'Indirect Routeing with Reference to Subscription Network' (yes) or 'MATF' -> 'set: terminate' and ends (no). From the 'MATF' -> 'set: terminate' path in the third 'OPTION', a 'routeing error' leads to 'SCCP error handling' and back to the 'MATF' block. + +Figure C.2.2: Procedure MNP\_SRF\_MATF\_Call\_Related + +![Flowchart for Procedure MATF. It starts with a connector symbol (oval with vertical line), followed by a process block 'perform TCAP handling'. A callout box to the right of the process block contains the text 'this includes passing the operation (SRI) to the application'. The process block leads to a circle with an 'X' inside. There is also an empty note box in the top left corner.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +**Procedure MATF** + +1(1) + +``` +graph TD; A([ ]) --> B[perform TCAP handling]; B --> C((X)); B --- D["this includes passing the operation (SRI) to the application"]; E[ ] -.-> F[ ]; +``` + +Flowchart for Procedure MATF. It starts with a connector symbol (oval with vertical line), followed by a process block 'perform TCAP handling'. A callout box to the right of the process block contains the text 'this includes passing the operation (SRI) to the application'. The process block leads to a circle with an 'X' inside. There is also an empty note box in the top left corner. + +**Figure C.2.2.1: Procedure MATF** + +![Flowchart for Process SRI_NPLR. It starts with an IDLE state, receives an SRI from a MAP process, checks for missing or unexpected data, queries a database, and then follows various logic paths based on whether the number is ported, if it's a GSMC in its own network, or if it's an unknown subscriber. It includes options to check HPLMN ranges and ultimately sets a response (RN, MSISDN, or error) before sending an SRI ack back to the MAP process.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +**Process SRI\_NPLR** 1(1) + +Process in the NPLR +to handle an incoming +SRI + +``` + +graph TD + Start([ ]) --> IDLE([IDLE]) + IDLE --> SRI_In[/SRI/] + SRI_In --- MapProc1[from MAP process] + SRI_In --> DataMissing{data missing} + + DataMissing -- yes --> ExitPoint(( )) + DataMissing -- no --> UnexpectedData{unexpected data} + + UnexpectedData -- yes --> ExitPoint + UnexpectedData -- no --> QueryDB[Query Database] + + QueryDB --> ForeignNum{Foreign number, +Ported in} + + ForeignNum -- yes --> Option1{OPTION} + ForeignNum -- no --> GSMC{GSMC in own +network} + + GSMC -- no --> ExitPoint + GSMC -- yes --> MNP_SRF[[MNP_SRF_Check_ +MNP_Indicator]] + + MNP_SRF --> Terminate{terminate} + Terminate -- yes --> ExitPoint + Terminate -- no --> UnknownSub{unknown +subscriber} + + UnknownSub -- yes --> Option2{OPTION} + UnknownSub -- no --> Option3{OPTION} + + %% Left Branch from ForeignNum yes + Option1 --- CheckHPLMN1[Check HPLMN +RN RANGE] + Option1 --- RNinHPLMN1[RN in HPLMN +RN Ranges] + Option1 -- yes --> SetErrorUnk[Set: error +Unknown +Subscriber] + Option1 -- no --> SetRN1[Set: RN +(+MSISDN)] + SetRN1 --- PointSub[pointing to subscription +network] + + %% Middle Branch from UnknownSub yes + Option2 --- CheckHPLMN2[Check HPLMN +MSISDN RANGE] + Option2 --- DNinHPLMN[DN in HPLMN +MSISDN Range] + Option2 -- yes --> SetMSISDN[Set: MSISDN] + Option2 -- no --> SetRN2[Set: RN +(+MSISDN)] + + %% Right Branch from UnknownSub no + Option3 --- OmitRN[omit routeing +number] + Option3 -- yes --> ExitPoint + Option3 -- no --> SetRN3[Set: RN +(+MSISDN)] + SetRN3 --- PointNum[pointing to number +range owner network] + + SetErrorUnk --> SRI_Ack[/SRI ack/] + SetRN1 --> SRI_Ack + SetMSISDN --> SRI_Ack + SetRN2 --> SRI_Ack + SetRN3 --> SRI_Ack + ExitPoint --> SetError[Set: error] + SetError --> SRI_Ack + + SRI_Ack --- MapProc2[to MAP process] + SRI_Ack --> End([ ]) + +``` + +Flowchart for Process SRI\_NPLR. It starts with an IDLE state, receives an SRI from a MAP process, checks for missing or unexpected data, queries a database, and then follows various logic paths based on whether the number is ported, if it's a GSMC in its own network, or if it's an unknown subscriber. It includes options to check HPLMN ranges and ultimately sets a response (RN, MSISDN, or error) before sending an SRI ack back to the MAP process. + +Figure C.2.2.2: Process SRI\_NPLR + +![Flowchart for Procedure MNP_SRF_MATF_Info_Request. It starts with a connector symbol, followed by a process block 'perform TCAP handling'. A note to the right of this block states 'this includes passing the operation (ATI) to the application'. The flowchart ends with a circle containing an 'X'.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +Procedure MNP\_SRF\_MATF\_Info\_Request 1(1) + +``` +graph TD; A([ ]) --> B[perform TCAP handling]; B --> C((X)); B --- D["this includes passing the operation (ATI) to the application"]; +``` + +Flowchart for Procedure MNP\_SRF\_MATF\_Info\_Request. It starts with a connector symbol, followed by a process block 'perform TCAP handling'. A note to the right of this block states 'this includes passing the operation (ATI) to the application'. The flowchart ends with a circle containing an 'X'. + +Figure C.2.3.1: Procedure MATF\_Info\_Request + +![Flowchart for Process ATI_NPLR showing the logic for handling an incoming ATI message, including checks for acceptance, data validity, and subscriber knowledge, leading to either a negative response or an acknowledgement.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +Process ATI\_NPLR + +1(1) + +Process in the NPLR + to handle an incoming ATI + +``` + + graph TD + Start([ ]) --> Idle1([Idle]) + Idle1 --> ATI[/ATI/] + ATI --- FromMAP[From MAP process] + ATI --> Accepted{ATI +accepted?} + Accepted -- no --> SetError[Set error] + Accepted -- yes --> Unexpected{Unexpected +data?} + Unexpected -- yes --> SetError + Unexpected -- no --> Missing{data missing?} + Missing -- yes --> SetError + Missing -- no --> Query[Query Database] + Query --> MSISDN{MSISDN +known?} + MSISDN -- no --> SetErrorUnknown[Set error:= +Unknown +subscriber] + MSISDN -- yes --> SetMNP[Set MNP +information] + SetMNP --- See3GTS[See 3G TS 23.078] + SetError --> NegResp1{ATI negative +Response} + SetErrorUnknown --> NegResp2{ATI negative +Response} + SetMNP --> ATIAck{ATI Ack} + ATIAck --- ToMAP[To MAP process] + NegResp1 --> Idle2([Idle]) + NegResp2 --> Idle2 + ATIAck --> Idle2 + +``` + +Flowchart for Process ATI\_NPLR showing the logic for handling an incoming ATI message, including checks for acceptance, data validity, and subscriber knowledge, leading to either a negative response or an acknowledgement. + +Figure C.2.3.2: Process ATI\_NPLR + +## C.3 Call Scenarios + +The notation TT=SRI in diagrams in this section assumes that SRI=CRMNP for ETSI and SRI = Translation Type 14 for ANSI. The use of other translation types is for further study. The message flows for the following scenarios are based on the use of an SCCP relay function in MNP-SRF(s). The message flows for the higher level relay function (e.g. TC relay) in MNP-SRF are not covered here, but the principle can be found in B.4.2. For further details of the signalling relay function, the reader is referred to [7]. + +### C.3.1 Call to a Non-Ported Number or Number Ported into the Network + +Figure C.3.1 shows the signalling involved for a call to a non-ported number or number ported into the network (see 3G TS 23.018 [3]). + +![Diagram of call signalling for a non-ported number. The diagram shows three network domains: Originating Network, Subscription Network or number range holder Network if non-ported, and Visited Network. The flow starts at the Originating Exchange (1) sending an IAM to the GMSCB. The GMSCB sends an SRI to the MNP_SRF/MATF (2). The MNP_SRF/MATF sends an SRI to the HLRB (3). The HLRB sends an SRI ack to the GMSCB (4). The GMSCB then sends an IAM to the VMSCB (5), which finally reaches the MSB (6).](74d23510f27b21403a7be84820821863_img.jpg) + +The diagram illustrates the signalling flow for a call to a non-ported number across three network domains: + +- Originating Network:** Contains the **Originating Exchange**. +- Subscription Network or number range holder Network if non-ported:** Contains the **GMSCB**, **MNP\_SRF/MATF**, **HLRB**, and **NPDB**. +- Visited Network:** Contains the **VMSCB** and **MSB**. + +Signalling steps: + +- 1:** **Originating Exchange** sends **IAM ((RN+)MSISDN)** to **GMSCB**. +- 2:** **GMSCB** sends **SRI (MSISDN)** to **MNP\_SRF/MATF**. +CdPA = MSISDN, TT=SRI +CgPA = GMSCB address +- 3:** **MNP\_SRF/MATF** sends **SRI (MSISDN)** to **HLRB**. +CdPA = HLRB address +CgPA = GMSCB address +- 4:** **HLRB** sends **SRI ack (MSRN)** to **GMSCB**. +CdPA = GMSCB address +CgPA = HLRB address +- 5:** **GMSCB** sends **IAM (MSRN)** to **VMSCB**. +- 6:** **VMSCB** sends **IAM (MSRN)** to **MSB**. + +Additional interactions: **MNP\_SRF/MATF** has a bidirectional connection to **NPDB**. **HLRB** has a bidirectional connection to **MNP\_SRF/MATF**. + +Diagram of call signalling for a non-ported number. The diagram shows three network domains: Originating Network, Subscription Network or number range holder Network if non-ported, and Visited Network. The flow starts at the Originating Exchange (1) sending an IAM to the GMSCB. The GMSCB sends an SRI to the MNP\_SRF/MATF (2). The MNP\_SRF/MATF sends an SRI to the HLRB (3). The HLRB sends an SRI ack to the GMSCB (4). The GMSCB then sends an IAM to the VMSCB (5), which finally reaches the MSB (6). + +**Figure C.3.1: Call to a non-ported number** + +1. From an Originating Exchange a call is set up to MSISDN. The call is routed to the subscription network being the number range holder network, if the number is non-ported. +2. When GMSCB receives the ISUP IAM, it requests routing information by submitting a MAP SRI to the MNP\_SRF/MATF. The TT on SCCP may be set to 'SRI'. +3. When the MNP\_SRF/MATF receives the message, the MNP\_SRF/MATF analyses the MSISDN in the CdPA and identifies the MSISDN as being non-ported. The MNP\_SRF/MATF function then replaces the CdPA by an HLRB address. After modifying the CdPA, the message is routed to HLRB. +4. When HLRB receives the SRI, it responds to the GMSCB by sending an SRI ack with an MSRN that identifies the MSB in the VMSCB. +5. GMSCB uses the MSRN to route the call to VMSCB. + +### C.3.2 Call to a Ported Number – Originating Network = Subscription Network – Direct Routeing + +Figure C.3.2 shows the signalling involved for a call to a ported number via direct routeing where the call is originated in the subscription network. + +![Diagram of call signalling for a ported number within the subscription network. The diagram shows the flow from MSA to VMSCA, then to GMSCA, then to MNP_SRF/MATF, then to HLRA, and finally back to GMSCA, which then routes the call back to VMSCA. The NPDB is shown as a dashed box connected to the MNP_SRF/MATF. The call is originated in the subscription network, so the call is routed directly to the GMSCA. The MNP_SRF/MATF function identifies the MSISDN as being ported into the network and replaces the CdPA by an HLRA address. The HLRA function then responds with an SRI ack with an MSRN that identifies the MSB in the VMSCB. The GMSCA function then uses the MSRN to route the call to the VMSCB.](a47713c2491e6ce619259ed2f196fd24_img.jpg) + +Originating Network += Subscription Network + +The diagram illustrates the following components and message flows: + +- MSA** (Mobile Station) originates a call to **VMSCA** (Step 1). +- VMSCA** routes the call to the network's **GMSCA** via an **IAM (MSISDN)** message (Step 2). +- When **GMSCA** receives the ISUP IAM, it requests routing information by submitting a **MAP SRI** to the **MNP\_SRF/MATF** (Step 3). The message includes: + - SRI (MSISDN) + - CdPA = MSISDN, TT=SRI + - CgPA = GMSCA address +- When the **MNP\_SRF/MATF** receives the message, it analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network. The **MNP\_SRF/MATF** function then replaces the CdPA by an **HLRA** address. After modifying the CdPA, the message is routed to **HLRA** (Step 4). +- When **HLRA** receives the SRI, it responds to the **GMSCA** by sending an **SRI ack (MSRN)** (Step 5). The message includes: + - SRI ack (MSRN) + - CdPA = GMSCA address + - CgPA = HLRA address +- GMSCA** uses the MSRN to route the call to **VMSCA** via an **IAM (MSRN)** message (Step 6). + +The **NPDB** (Number Portability Database) is shown as a dashed box connected to the **MNP\_SRF/MATF**. + +Diagram of call signalling for a ported number within the subscription network. The diagram shows the flow from MSA to VMSCA, then to GMSCA, then to MNP\_SRF/MATF, then to HLRA, and finally back to GMSCA, which then routes the call back to VMSCA. The NPDB is shown as a dashed box connected to the MNP\_SRF/MATF. The call is originated in the subscription network, so the call is routed directly to the GMSCA. The MNP\_SRF/MATF function identifies the MSISDN as being ported into the network and replaces the CdPA by an HLRA address. The HLRA function then responds with an SRI ack with an MSRN that identifies the MSB in the VMSCB. The GMSCA function then uses the MSRN to route the call to the VMSCB. + +**Figure C.3.2: Call to a ported number via direct routeing where the call is originated in the subscription network** + +1. MSA originates a call to MSISDN. +2. VMSCA routes the call to the network's GMSCA. +3. When GMSCA receives the ISUP IAM, it requests routing information by submitting a MAP SRI to the MNP\_SRF/MATF. The TT on SCCP may be set to 'SRI'. +4. When the MNP\_SRF/MATF receives the message, it analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network. The MNP\_SRF/MATF function then replaces the CdPA by an HLRA address. After modifying the CdPA, the message is routed to HLRA. +5. When HLRA receives the SRI, it responds to the GMSCA by sending an SRI ack with an MSRN that identifies the MSB in the VMSCB. +6. GMSCA uses the MSRN to route the call to VMSCB. + +### C.3.3 Mobile Originated Call to a Ported or not known to be Ported Number – Originating Network $\neq$ Subscription Network– Direct Routeing + +Figure C.3.3 shows the signalling involved for a national mobile originated call to a number not Subscribed in the originating network via direct routeing. The scenario describes signalling in the originating network using direct routeing in the cases when an own number is ported out, a foreign number is not known to be ported or a foreign number is ported to other foreign network. + +![Diagram of mobile originated call signaling in the originating network. The diagram shows the flow of messages between the MSA, VMSCA, GMSCA, and MNP_SRF/MATF. The NPDB is shown as a dashed cylinder connected to the MNP_SRF/MATF. The signaling steps are: 1. MSA sends an IAM (MSISDN) to VMSCA. 2. VMSCA routes the call to GMSCA. 3. GMSCA sends an SRI (MSISDN) to MNP_SRF/MATF. 4. MNP_SRF/MATF responds with an SRI ack (RN + MSISDN) to GMSCA. 5. GMSCA routes the call to the subscription network via an IAM ((RN +) MSISDN).](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) + +Originating Network + +The diagram illustrates the signaling flow within the Originating Network (enclosed in a dashed box). The components involved are: + + +- MSA**: Mobile Station Attendant, which originates the call. +- VMSCA**: Visited Mobile Switching Center A, which routes the call from the MSA. +- GMSCA**: Gateway Mobile Switching Center A, which handles the routing request. +- MNP\_SRF/MATF**: Mobile Number Portability Service Resolving Function / Mobile Attendant Transfer Function, which checks the NPDB for routing information. +- NPDB**: Number Portability Database, shown as a dashed cylinder. + + The signaling steps are numbered 1 through 5: + + +- The MSA sends an **1** IAM (MSISDN) to the VMSCA. +- The VMSCA routes the call to the GMSCA via **2** IAM (MSISDN). +- The GMSCA sends an **3** SRI (MSISDN) to the MNP\_SRF/MATF. The message includes: + - CdPA = MSISDN, TT=SRI + - CgPA = GMSCA address +- The MNP\_SRF/MATF responds with an **4** SRI ack (RN + MSISDN). The message includes: + - CdPA = GMSCA address + - CgPA = MNP\_SRF address +- Finally, the GMSCA routes the call to the subscription network via **5** IAM ((RN +) MSISDN). + +Diagram of mobile originated call signaling in the originating network. The diagram shows the flow of messages between the MSA, VMSCA, GMSCA, and MNP\_SRF/MATF. The NPDB is shown as a dashed cylinder connected to the MNP\_SRF/MATF. The signaling steps are: 1. MSA sends an IAM (MSISDN) to VMSCA. 2. VMSCA routes the call to GMSCA. 3. GMSCA sends an SRI (MSISDN) to MNP\_SRF/MATF. 4. MNP\_SRF/MATF responds with an SRI ack (RN + MSISDN) to GMSCA. 5. GMSCA routes the call to the subscription network via an IAM ((RN +) MSISDN). + +**Figure C.3.3: National mobile originated call to a ported number via direct routeing** + +1. MSA originates a call to MSISDN. +2. VMSCA routes the call to the network's GMSCA. +3. When GMSCA receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to the MNP\_SRF/MATF. The TT on SCCP may be set to 'SRI'. +4. When the MNP\_SRF/MATF receives the message, it analyses the MSISDN in the CdPA and identifies the MSISDN as not known to be ported or being ported to another network. As the message is a SRI message, the MNP\_SRF/MATF responds to the GMSCA by sending an SRI ack with a RN + MSISDN; For the case the number is not known to be ported the routeing number may be omitted. +5. GMSCA uses the (RN +) MSISDN to route the call to GMSCB in the subscription network. Depending on the interconnect agreement, the RN will be added in the IAM or not. + +### C.3.4 Call to a Ported Number – Indirect Routeing + +Figure C.3.4 shows the signalling involved for a call to a ported number via indirect routeing. + +![Diagram illustrating the signalling for a call to a ported number via indirect routeing. It shows the interaction between an Originating Network (with an Originating Exchange) and a Number Range Holder Network (containing an NPDB, MNP_SRF/MATF, and a GMSCA). The sequence of messages is: 1. IAM (MSISDN) from Originating Exchange to GMSCA; 2. SRI (MSISDN) from GMSCA to MNP_SRF/MATF; 3. SRI ack (RN + MSISDN) from MNP_SRF/MATF to GMSCA; 4. IAM ((RN +) MSISDN) from GMSCA to the next network. Details for step 2: CdPA = MSISDN, TT=SRI, CgPA = GMSCA address. Details for step 3: CdPA = GMSCA address, CgPA = MNP_SRF address.](76d19e4271bf243b20d55a98efd51483_img.jpg) + +Diagram illustrating the signalling for a call to a ported number via indirect routeing. It shows the interaction between an Originating Network (with an Originating Exchange) and a Number Range Holder Network (containing an NPDB, MNP\_SRF/MATF, and a GMSCA). The sequence of messages is: 1. IAM (MSISDN) from Originating Exchange to GMSCA; 2. SRI (MSISDN) from GMSCA to MNP\_SRF/MATF; 3. SRI ack (RN + MSISDN) from MNP\_SRF/MATF to GMSCA; 4. IAM ((RN +) MSISDN) from GMSCA to the next network. Details for step 2: CdPA = MSISDN, TT=SRI, CgPA = GMSCA address. Details for step 3: CdPA = GMSCA address, CgPA = MNP\_SRF address. + +**Figure C.3.4: Call to a ported number via indirect routeing** + +1. From an Originating Exchange a call is set up to MSISDN. The call is routed to the number range holder network. +2. When GMSCA in the number range holder network receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to MNP\_SRF/MATF. The TT on SCCP may be set to 'SRI'. +3. When the MNP\_SRF/MATF receives the message, it analyses the MSISDN in the CdPA and identifies the MSISDN as being ported to another network. As the message is an SRI message, the MNP\_SRF/MATF responds to the GMSCA by sending an SRI ack with a RN + MSISDN. +4. GMSCA uses the RN + MSISDN to route the call to GMSCB in the subscription network. Depending on the interconnect agreement, the RN will be added in the IAM or not. + +### C.3.5 Call to a Ported Number – Indirect Routeing with Reference to Subscription Network + +Figure C.3.5 shows the signalling involved for a call to a ported number where indirect routeing with reference to the subscription network is used. + +![Diagram of signalling for a call to a ported number with indirect routeing. The diagram shows three main entities: (Inter) national Originating Network, Number Range Holder Network, and Subscription Network. The flow starts at the Originating Exchange (1) sending an IAM (MSISDN) to the GMSCA. The GMSCA sends an SRI (MSISDN) to the MNP_SRF/MATF (2). The MNP_SRF/MATF sends an SRI (MSISDN) to the HLRB (3). The HLRB sends an SRI ack (MSRN) to the MNP_SRF/MATF (4). The MNP_SRF/MATF sends an SRI ack (RN + MSISDN) to the GMSCA (5). The GMSCA sends an IAM ((RN +) MSISDN) to the GMSCB (6). The GMSCB sends an SRI (MSISDN) to the MNP_SRF/MATF (7). The MNP_SRF/MATF sends an SRI ack (MSRN) to the GMSCB (8). The GMSCB sends an IAM (MSRN) to the VMSCB (9).](9b9262a549828579ab904148450734f6_img.jpg) + +The diagram illustrates the signalling flow for a call to a ported number using indirect routeing with reference to the subscription network. It involves three main network components: (Inter) national Originating Network, Number Range Holder Network, and Subscription Network. + +- 1** From the Originating Exchange, an ISUP IAM (MSISDN) is sent to the GMSCA. +- 2** The GMSCA sends a MAP SRI (MSISDN) to the MNP\_SRF/MATF. The message includes CdPA = MSISDN, TT=SRI, and CgPA = GMSCA address. +- 3** The MNP\_SRF/MATF sends a MAP SRI (MSISDN) to the HLRB. The message includes CdPA = RN + MSISDN, TT=SRI, and CgPA = GMSCA address. +- 4** The HLRB sends a MAP SRI ack (MSRN) to the MNP\_SRF/MATF. The message includes CdPA = GMSCB address and CgPA = HLRB address. +- 5** The MNP\_SRF/MATF sends a MAP SRI ack (RN + MSISDN) to the GMSCA. The message includes CdPA = GMSCA address and CgPA = MNP\_SRF address. +- 6** The GMSCA sends an ISUP IAM ((RN +) MSISDN) to the GMSCB. +- 7** The GMSCB sends a MAP SRI (MSISDN) to the MNP\_SRF/MATF. The message includes CdPA = MSISDN, TT=SRI, and CgPA = GMSCB address. +- 8** The MNP\_SRF/MATF sends a MAP SRI ack (MSRN) to the GMSCB. The message includes CdPA = GMSCB address and CgPA = HLRB address. +- 9** The GMSCB sends an ISUP IAM (MSRN) to the VMSCB. + +Diagram of signalling for a call to a ported number with indirect routeing. The diagram shows three main entities: (Inter) national Originating Network, Number Range Holder Network, and Subscription Network. The flow starts at the Originating Exchange (1) sending an IAM (MSISDN) to the GMSCA. The GMSCA sends an SRI (MSISDN) to the MNP\_SRF/MATF (2). The MNP\_SRF/MATF sends an SRI (MSISDN) to the HLRB (3). The HLRB sends an SRI ack (MSRN) to the MNP\_SRF/MATF (4). The MNP\_SRF/MATF sends an SRI ack (RN + MSISDN) to the GMSCA (5). The GMSCA sends an IAM ((RN +) MSISDN) to the GMSCB (6). The GMSCB sends an SRI (MSISDN) to the MNP\_SRF/MATF (7). The MNP\_SRF/MATF sends an SRI ack (MSRN) to the GMSCB (8). The GMSCB sends an IAM (MSRN) to the VMSCB (9). + +**Figure C.3.5: National or international originated call to a ported number where indirect routeing with reference to the subscription network is used** + +1. From an Originating Exchange a call is set up to MSISDN. The call is routed to the number range holder network. +2. When GMSCA in the number range holder network receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to the MNP\_SRF/MATF. The TT on SCCP may be set to ‘SRI’. +3. When MNP\_SRF/MATF receives the message, MNP\_SRF/MATF operation is triggered. The MNP\_SRF/MATF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported to another network. As the message is a SRI message, the MNP\_SRF/MATF function relays the message to the subscription network by adding a routeing number to the CdPA which information may be retrieved from a database. After modifying the CdPA, the message is routed to the subscription network. +4. When MNP\_SRF/MATF in the subscription network receives the SRI, it responds to the GMSCA in the number range holder network by sending a SRI ack with a RN + MSISDN. +5. GMSCA uses the (RN +) MSISDN to route the call to GMSCB in the subscription network; Depending on the interconnect agreement, the RN will be added in the IAM or not. +6. When GMSCB in the subscription network receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to MNP\_SRF/MATF. The TT on SCCP may be set to ‘SRI’. +7. When MNP\_SRF/MATF receives the message, MNP\_SRF/MATF operation is triggered. The MNP\_SRF/MATF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported into the network. The MNP\_SRF/MATF function then replaces the CdPA by an HLRB address which information may be retrieved from a database. After modifying the CdPA, the message is routed to HLRB. +8. When HLRB receives the SRI, it responds to the GMSCB by sending an SRI ack with an MSRN that identifies the MSB in the VMSCB. +9. GMSCB uses the MSRN to route the call to VMSCB. + +**NOTE:** The MNP\_SRF/MATF in this scenario has only information about all ported numbers to one subscription network, except those for which subscription information is held in the subscription networks HLR. In this scenario the routeing depends always on the number range holder and the subscription network. + +### C.3.6 MNP Info Query - Direct Routeing + +![Diagram of MNP-SRF operation for providing MNP Information where direct routeing applies. The diagram shows an Interrogating Network (dashed box) containing an NPDB (cylinder), an MNP SRFA (square), and an INE (square). The INE sends an ATI (MSISDN) message to the MNP SRFA. The MNP SRFA sends an ATI ack (MNP Info) message to the NPDB. The NPDB sends an ATI ack (MNP Info) message to the INE.](9cb54072e43a6b6717eb16036a7640a2_img.jpg) + +Interrogating Network + +``` +graph TD + subgraph IN [Interrogating Network] + NPDB[(NPDB)] + MNP[MNP SRFA] + INE[INE] + INE -- "ATI (MSISDN) +SCCP CdPA = MSISDN, +TT=MNPInfoRequest" --> MNP + MNP -- "ATI ack (MNP Info) +SCCP CdPA = INE" --> NPDB + NPDB -- "ATI ack (MNP Info) +SCCP CdPA = INE" --> INE + end +``` + +Diagram of MNP-SRF operation for providing MNP Information where direct routeing applies. The diagram shows an Interrogating Network (dashed box) containing an NPDB (cylinder), an MNP SRFA (square), and an INE (square). The INE sends an ATI (MSISDN) message to the MNP SRFA. The MNP SRFA sends an ATI ack (MNP Info) message to the NPDB. The NPDB sends an ATI ack (MNP Info) message to the INE. + +**Figure C.3.6: MNP-SRF operation for providing MNP Information where direct routeing applies** + +In a PLMN using a MNP-SRF based MNP solution supporting direct routeing, the INE always sends the MNP information request, containing the CdPA, to the MNP-SRF in that network. + +The INE may query the MNP information for the called party number or the calling party number. + +The INE requesting MNP information may be a gsmSCF for prepaid services (see 3GPP TS 23.078 [18]). + +In order to provide enough information for a CAMEL SCP to charge correctly for CAMEL Pre-Paid Calls and SMS to national MSISDNs originated in the HPLMN, operators should ensure that the NPDB contains, at least, MNP information for 'own numbers ported out' and 'foreign numbers ported in'. + +### C.3.7 MNP Info Query - Indirect Routeing + +![Diagram of MNP-SRF operation for Providing MNP information where indirect routeing applies. It shows an Interrogating Network (INE) sending an ATI (MSISDN) request to an MNP SRFB in a Number Range Holder Network, which then queries an NPDB and returns an ATI ack (MNP info) to the INE.](c649cad02e45d7d9a16f3f5bdb332219_img.jpg) + +The diagram illustrates the interaction between an Interrogating Network (INE) and a Number Range Holder Network (MNP SRFB) for MNP information retrieval. The INE is located within the Interrogating Network, and the MNP SRFB is located within the Number Range Holder Network. The MNP SRFB is connected to an NPDB (Number Portability Database). + +The sequence of messages is as follows: + +- The INE sends an **ATI (MSISDN)** message to the MNP SRFB. The SCCP addressing is: **SCCP CdPA = MSISDN, TT=MNPInfoRequest**. +- The MNP SRFB responds with an **ATI ack (MNP info)** message. The SCCP addressing is: **SCCP CgPA = MNP SRFB address** and **CdPA = INE address**. + +Diagram of MNP-SRF operation for Providing MNP information where indirect routeing applies. It shows an Interrogating Network (INE) sending an ATI (MSISDN) request to an MNP SRFB in a Number Range Holder Network, which then queries an NPDB and returns an ATI ack (MNP info) to the INE. + +**Figure C.3.7: MNP-SRF operation for Providing MNP information where indirect routeing applies** + +The Interrogating Network Entity (INE) submits a MNP Information request message to the MNP-SRFB, which triggers MNP-SRF operation. The MNP-SRF functionality analyses the MSISDN in the application level and queries an MNP database to get the MNP information. The INE may query the MNP information for the called party number or the calling party number. + +The INE requesting MNP information may be a gsmSCF for prepaid services (see 3GPP TS 23.078 [18]). + +## C.4 Information Flows + +Figure C.4.1 shows the information flow for a successful delivery of a call to a non-ported number or number ported into the network. The figure is related to figure C.3.1. + +![Sequence diagram showing information flow for call delivery between Originating Network, Subscription Network (GMSCB, MNP_SRFB/MATF, HLRB), and Visited Network (VMSCB).](aa6e28822419dba9f22129fee66c9c4c_img.jpg) + +The diagram illustrates the sequence of messages for a successful call delivery. It is divided into three main entities: Originating Network, Subscription Network (containing GMSCB, MNP\_SRFB/MATF, and HLRB), and Visited Network (containing VMSCB). The flow is as follows: + +- Originating Network** sends an **IAM ((RN+ )MSISDN)** message to the **GMSCB**. +- GMSCB** sends an **SRI (MSISDN)** message to **MNP\_SRFB/MATF**. The message includes **CdPA = MSISDN, TT=SRI**. +- MNP\_SRFB/MATF** sends an **SRI (MSISDN)** message to **HLRB**. The message includes **CdPA = HLRB address**. +- HLRB** sends a **PRN** message to **VMSCB**. +- VMSCB** sends a **PRN ack (MSRN)** message back to **HLRB**. +- HLRB** sends an **SRI ack (MSRN)** message back to **GMSCB**. +- GMSCB** sends an **IAM (MSRN)** message to **VMSCB**. + +Sequence diagram showing information flow for call delivery between Originating Network, Subscription Network (GMSCB, MNP\_SRFB/MATF, HLRB), and Visited Network (VMSCB). + +**Figure C.4.1: Successful delivery of a call to a non-ported subscriber or number ported into the network** + +Figure C.4.2 shows the signalling involved for a call to a ported number via direct routing where the call is originated in the subscription network. The figure is related to figure C.3.2. + +![Sequence diagram showing call signalling for a ported number. Lifelines: VMSCA, GMSCA, MNP_SRFA/MATF, HLRA, VMSCB. The diagram shows the flow of IAM, SRI, PRN, and their acknowledgements between these entities.](5bba23cc120ad806779f82df1c01bebf_img.jpg) + +``` +sequenceDiagram + participant VMSCA + participant GMSCA + participant MNP_SRFA/MATF + participant HLRA + participant VMSCB + + Note left of VMSCA: National Originating Network = Subscription Network + Note right of VMSCB: Visited Network + + VMSCA->>GMSCA: IAM (MSISDN) + GMSCA->>MNP_SRFA/MATF: SRI (MSISDN) +CdPA = MSISDN, TT=SRI + MNP_SRFA/MATF->>HLRA: SRI (MSISDN) +CdPA = HLRA address + HLRA->>VMSCB: PRN + VMSCB->>HLRA: PRN ack (MSRN) + HLRA->>GMSCA: SRI ack (MSRN) + GMSCA->>VMSCB: IAM (MSRN) +``` + +Sequence diagram showing call signalling for a ported number. Lifelines: VMSCA, GMSCA, MNP\_SRFA/MATF, HLRA, VMSCB. The diagram shows the flow of IAM, SRI, PRN, and their acknowledgements between these entities. + +**Figure C.4.2: Successful delivery of a call to a ported number via direct routing where the call is originated in the subscription network** + +Figure C.4.3 shows the signalling involved for a national mobile originated call to a ported number via direct routing. The figure is related to figure C.3.3. + +![Sequence diagram showing signalling for a national mobile originated call to a ported number via direct routing. It involves three networks: National Originating Network, Subscription Network, and Visited Network, with various components like GMSA, MNP_SRFA/MATF, GMSB, MNP_SRFB/MATF, HLRB, and VMSCB.](9f50279046b74a4e66a1a0144c3b1d11_img.jpg) + +The diagram illustrates the signalling flow for a national mobile originated call to a ported number via direct routing. It is divided into three network domains: National Originating Network, Subscription Network, and Visited Network. + +- National Originating Network:** Contains GMSCA and MNP\_SRFA/MATF. The call starts with an IAM (MSISDN) entering GMSCA. GMSCA sends an SRI (MSISDN) with CdPA = MSISDN and TT=\$RI to MNP\_SRFA/MATF. MNP\_SRFA/MATF responds with an SRI ack (RN + MSISDN) to GMSCA. GMSCA then sends an IAM ((RN +) MSISDN) to the Subscription Network. +- Subscription Network:** Contains GMSCB, MNP\_SRFB/MATF, and HLRB. GMSCB receives the IAM and sends an SRI (MSISDN) with CdPA = MSISDN and TT=\$RI to MNP\_SRFB/MATF. MNP\_SRFB/MATF sends an SRI (MSISDN) with CdPA = HLRB address to HLRB. HLRB sends a PRN to VMSCB in the Visited Network. VMSCB responds with a PRN ack (MSRN) to HLRB. HLRB sends an SRI ack (MSRN) to GMSCB. +- Visited Network:** Contains VMSCB. It receives the PRN from HLRB and sends a PRN ack (MSRN) back to HLRB. Finally, HLRB sends an IAM (MSRN) to VMSCB. + +Sequence diagram showing signalling for a national mobile originated call to a ported number via direct routing. It involves three networks: National Originating Network, Subscription Network, and Visited Network, with various components like GMSA, MNP\_SRFA/MATF, GMSB, MNP\_SRFB/MATF, HLRB, and VMSCB. + +**Figure C.4.3: Successful delivery of a national mobile originated call to a ported number via direct routing** + +Figure C.4.4 shows the signalling involved for a national mobile originated call to a not known to be ported number via direct routeing. The figure is related to figure C.3.3. + +![Sequence diagram showing signalling for a national mobile originated call. Lifelines: National Originating Network (GMSCA, MNP_SRFA/MATF), Number Range Holder Network (GMSCB, MNP_SRFB/MATF), and Visited Network (HLRB, VMSCB).](7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg) + +``` +sequenceDiagram + participant External + subgraph National Originating Network + GMSCA + MNP_SRFA/MATF + end + subgraph Number Range Holder Network + GMSCB + MNP_SRFB/MATF + end + subgraph Visited Network + HLRB + VMSCB + end + External->>GMSCA: IAM (MSISDN) + GMSCA->>MNP_SRFA/MATF: SRI (MSISDN) +CdPA = MSISDN, TT=SRI + MNP_SRFA/MATF-->>GMSCA: SRI ack ((RN +) MSISDN) + GMSCA->>GMSCB: IAM ((RN +) MSISDN) + GMSCB->>MNP_SRFB/MATF: SRI (MSISDN) +CdPA = MSISDN, TT=SRI + MNP_SRFB/MATF->>HLRB: SRI (MSISDN) +CdPA = HLRB address + HLRB->>VMSCB: PRN + VMSCB-->>HLRB: PRN ack (MSRN) + HLRB-->>GMSCB: SRI ack (MSRN) + HLRB->>VMSCB: IAM (MSRN) +``` + +The diagram illustrates the signalling flow for a national mobile originated call. It begins with an IAM (MSISDN) message entering the National Originating Network. Inside, an SRI (MSISDN) is sent from the GMSCA to the MNP\_SRFA/MATF, with the Called Party Address (CdPA) set to the MSISDN and the Transaction Type (TT) set to SRI. The MNP\_SRFA/MATF responds with an SRI ack containing the routing number (RN) and MSISDN. The National Originating Network then forwards an IAM message with the RN and MSISDN to the Number Range Holder Network's GMSCB. The GMSCB sends an SRI (MSISDN) to its MNP\_SRFB/MATF, with CdPA as MSISDN and TT as SRI. The MNP\_SRFB/MATF sends an SRI (MSISDN) to the HLRB, with CdPA as the HLRB address. The HLRB sends a PRN to the VMSCB, which responds with a PRN ack containing the MSRN. The HLRB then sends an SRI ack (MSRN) back to the GMSCB and an IAM (MSRN) to the VMSCB. + +Sequence diagram showing signalling for a national mobile originated call. Lifelines: National Originating Network (GMSCA, MNP\_SRFA/MATF), Number Range Holder Network (GMSCB, MNP\_SRFB/MATF), and Visited Network (HLRB, VMSCB). + +**Figure C.4.4: Successful delivery of a national mobile originated call to a not known to be ported number via direct routeing** + +Figure C.4.5 shows the signalling involved for a call to a ported number via indirect routeing. The figure is related to figure C.3.4. + +![Sequence diagram showing the signalling for a call to a ported number via indirect routeing. It involves four main network entities: Originating Network, Number Range Holder Network, Subscription Network, and Visited Network. The sequence of messages includes IAM, SRI, SRI ack, PRN, and PRN ack between various sub-components like GMSCA, MNP_SRFA/MATF, GMSCB, MNP_SRFB/MATF, HLRB, and VMSCB.](d9cfc30025244dcd75766061f27ee09f_img.jpg) + +``` +sequenceDiagram + participant ON as Originating Network + participant GMSCA as GMSCA + participant MNP_SRFA as MNP_SRFA/MATF + participant GMSCB as GMSCB + participant MNP_SRFB as MNP_SRFB/MATF + participant HLRB as HLRB + participant VMSCB as VMSCB + + Note right of ON: IAM(MSISDN) + ON->>GMSCA: IAM(MSISDN) + GMSCA->>MNP_SRFA: SRI (MSISDN) +CdPA = MSISDN, TT=SRI + MNP_SRFA-->>GMSCA: SRI ack (RN + MSISDN) + GMSCA->>GMSCB: IAM ((RN +) MSISDN) + GMSCB->>MNP_SRFB: SRI (MSISDN) +CdPA = MSISDN, TT=SRI + MNP_SRFB->>HLRB: SRI (MSISDN) +CdPA = HLRB address + HLRB->>VMSCB: PRN + VMSCB-->>HLRB: PRN ack (MSRN) + HLRB-->>GMSCB: SRI ack (MSRN) + GMSCB->>VMSCB: IAM (MSRN) +``` + +Sequence diagram showing the signalling for a call to a ported number via indirect routeing. It involves four main network entities: Originating Network, Number Range Holder Network, Subscription Network, and Visited Network. The sequence of messages includes IAM, SRI, SRI ack, PRN, and PRN ack between various sub-components like GMSCA, MNP\_SRFA/MATF, GMSCB, MNP\_SRFB/MATF, HLRB, and VMSCB. + +Figure C.4.5: Successful delivery of a call to a ported number via indirect routeing + +Figure C.4.6 shows the signalling involved for a call to a ported number where indirect routing with reference to the subscription network is used. The figure is related to figure C.3.5. + +![Sequence diagram showing successful delivery for a call to a ported number where indirect routing with reference to the subscription network is used. The diagram involves three network entities: Number Range Holder Network, Subscription Network, and Visited Network. The sequence of messages is as follows: 1. IAM (MSISDN) is received by GMSCA. 2. GMSCA sends SRI (MSISDN) with CdPA = MSISDN, TT=SRI to MNP_SRFA/MATF. 3. MNP_SRFA/MATF sends SRI (MSISDN) with CdPA = RN + MSISDN, TT=SRI to GMSCB. 4. GMSCB sends SRI ack (RN + MSISDN) to MNP_SRFA/MATF. 5. MNP_SRFA/MATF sends IAM ((RN +) MSISDN) to GMSCA. 6. GMSCA sends SRI (MSISDN) with CdPA = MSISDN, TT=SRI to MNP_SRFB/MATF. 7. MNP_SRFB/MATF sends SRI (MSISDN) with CdPA = HLRB address to HLRB. 8. HLRB sends PRN to VMSCB. 9. VMSCB sends PRN ack (MSRN) to HLRB. 10. HLRB sends SRI ack (MSRN) to GMSCB. 11. GMSCB sends IAM (MSRN) to VMSCB.](1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg) + +``` + +sequenceDiagram + participant External + subgraph Number Range Holder Network + GMSCA + MNP_SRFA/MATF + end + subgraph Subscription Network + GMSCB + MNP_SRFB/MATF + HLRB + end + subgraph Visited Network + VMSCB + end + External->>GMSCA: IAM (MSISDN) + GMSCA->>MNP_SRFA/MATF: SRI (MSISDN) +CdPA = MSISDN, TT=SRI + MNP_SRFA/MATF->>GMSCB: SRI (MSISDN) +CdPA = RN + MSISDN, TT=SRI + GMSCB->>MNP_SRFA/MATF: SRI ack (RN + MSISDN) + MNP_SRFA/MATF->>GMSCA: IAM ((RN +) MSISDN) + GMSCA->>MNP_SRFB/MATF: SRI (MSISDN) +CdPA = MSISDN, TT=SRI + MNP_SRFB/MATF->>HLRB: SRI (MSISDN) +CdPA = HLRB address + HLRB->>VMSCB: PRN + VMSCB->>HLRB: PRN ack (MSRN) + HLRB->>GMSCB: SRI ack (MSRN) + GMSCB->>VMSCB: IAM (MSRN) + +``` + +Sequence diagram showing successful delivery for a call to a ported number where indirect routing with reference to the subscription network is used. The diagram involves three network entities: Number Range Holder Network, Subscription Network, and Visited Network. The sequence of messages is as follows: 1. IAM (MSISDN) is received by GMSCA. 2. GMSCA sends SRI (MSISDN) with CdPA = MSISDN, TT=SRI to MNP\_SRFA/MATF. 3. MNP\_SRFA/MATF sends SRI (MSISDN) with CdPA = RN + MSISDN, TT=SRI to GMSCB. 4. GMSCB sends SRI ack (RN + MSISDN) to MNP\_SRFA/MATF. 5. MNP\_SRFA/MATF sends IAM ((RN +) MSISDN) to GMSCA. 6. GMSCA sends SRI (MSISDN) with CdPA = MSISDN, TT=SRI to MNP\_SRFB/MATF. 7. MNP\_SRFB/MATF sends SRI (MSISDN) with CdPA = HLRB address to HLRB. 8. HLRB sends PRN to VMSCB. 9. VMSCB sends PRN ack (MSRN) to HLRB. 10. HLRB sends SRI ack (MSRN) to GMSCB. 11. GMSCB sends IAM (MSRN) to VMSCB. + +**Figure C.4.6: Successful delivery for a call to a ported number where indirect routing with reference to the subscription network is used** + +## C.5 Contents of the messages + +This clause contains detailed description of the messages shown in this part B of the specification. + +The contents of the messages used on the gsmSCF – MNP-SRF interface are specified in 3G TS 23.078 [19]. When the message is sent from the NPLR to the gsmSCF, the MNP specific information are defined as in clause C.5.2. The gsmSCF may transit the information received from NPLR to the gateway MSC with the CAP Connect message in order to avoid a subsequent SRI message. + +### C.5.1 Send Routing Info + +The contents of this message are specified in 3G TS 23.018 [3]. + +### C.5.2 Send Routeing Info ack + +The contents of this message are specified in 3G TS 23.018 [3]. In the case that the message is sent from the NPLR to the GMSC, the following MNP specific information is defined: + +| Information element name | Required | Description | +|--------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Imsi | M | The IMSI returned by an NPLR is a generic IMSI, i.e. it is not tied necessarily to the Subscriber. MCC and MNC values in this IMSI shall point to the Subscription Network of the B Subscriber | +| Msrn | C | When returned from the NPLR, this parameter contains a Routeing Number that points to Subscription Network. If concatenate addressing is used, it also contains the MSISDN in addition to the Routeing Number. In the case of a number which is not known to be ported, the Routeing Number may be omitted as an operator option. If the routeing number is omitted, this parameter contains only the MSISDN. | +| Msisdn | C | MSISDN of the B subscriber. This information element shall be present if MSRN contains the routeing number to reach the subscription network for B subscriber and the MSISDN is not contained in the MSRN information element. | +| MNP Indicator | U | Indicates the number portability status of the subscriber. | + +## C.6 Handling of MAP to ISUP mapping (informative) + +Different configurations can be possible within a portability domain depending on the versions of MAP and ISUP protocols being used. The following sections describe possible interworking scenarios. + +### C.6.1 ETSI Mapping direction: ISUP to MAP + +The GMSC always constructs the Send Routeing Info message using the MSISDN. If the incoming IAM corresponds to a ported number the GMSC shall retrieve the MSISDN from the corresponding parameter in the IAM. + +### C.6.2 ETSI Mapping direction: MAP to ISUP + +In MAP SRIack messages from NPLR, MAP versions 1 and 2 only support concatenate addressing for MNP. If MSISDN parameter is present in the SRIack, this means that separate addressing is used in MAP; this is only possible if MAP version 3 is used. MAP version 3 can also support concatenate addressing. In all cases, when a Routeing Number is returned, it is included in the MSRN parameter of the SRIack. + +Regardless of how MAP is established, the possible mappings of the parameters in ISUP IAM message is one of these 4 options (see also [6]): + +1. CdPN parameter includes only the MSISDN. +2. CdPN parameter includes both RN and MSISDN concatenated. +3. CdPN parameter includes the MSISDN and NRN parameter includes the Routeing Number. +4. CdPN parameter includes the Routeing Number and CDN parameter includes the MSISDN. + +In all cases, the method to transport the routeing number in the IAM depends on the interfaces agreed by the operators in the portability domain. + +### C.6.3 ANSI Mapping direction: ISUP to MAP + +The GMSC always constructs the Send Routeing Info message using the MSISDN. If the incoming IAM corresponds to a ported number the GMSC shall retrieve the MSISDN from the corresponding parameter in the IAM. + +The IAM message is specified for ANSI ISUP implementation in [8] and [9]. + +### C.6.4 ANSI Mapping direction: MAP to ISUP + +In MAP SRIack messages from NPLR, MAP versions 1 and 2 only support concatenate addressing for MNP. If MSISDN parameter is present in the SRI Ack, this means that separate addressing is used in MAP; this is only possible if MAP version 3 is used. MAP version 3 can also support concatenate addressing. In all cases, when a Routeing Number is returned, it is included in the MSRN parameter of the SRI Ack. + +**Regardless of how MAP is established, the possible mappings of the parameters in ISUP IAM message is one of these 4 options (see also [8] and [9]):** + +| MAP Parameters | SRI Ack | | ISUP Parameters | IAM | +|----------------|-----------------|---------|---------------------|------| +| IMSI | Subscriber IMSI | | CdPN | MSRN | +| MSRN | MSRN | MAPS TO | GAP | N/A | +| MSISDN | Not Present | | FCI Bit M Indicator | 1 | +| MNP Indicator | Not Present | | | | + +| MAP Parameters | SRI Ack | | ISUP Parameters | IAM | +|----------------|--------------------|---------|---------------------|------------| +| IMSI | Default IMSI | | CdPN | Dialled DN | +| MSRN | Dialled DN | MAPS TO | GAP | N/A | +| MSISDN | Not Present | | FCI Bit M Indicator | 1 | +| MNP Indicator | NotKnownToBePorted | | | | + +| MAP Parameters | SRI Ack | | ISUP Parameters | IAM | +|----------------|--------------------|---------|---------------------|------------| +| IMSI | Default IMSI | | CdPN | RN | +| MSRN | RN | MAPS TO | GAP | Dialled DN | +| MSISDN | Dialled DN | | FCI Bit M Indicator | 1 | +| MNP Indicator | OwnNumberPortedOut | | | | + +| MAP Parameters | SRI Ack | | ISUP Parameters | IAM | +|----------------|--------------|---------|---------------------|------------| +| IMSI | Default IMSI | | CdPN | RN | +| MSRN | RN | MAPS TO | GAP | Dialled DN | +| MSISDN | Dialled DN | | FCI Bit M Indicator | 1 | + +| | | | | | +|---------------|----------------------------------------------|--|--|--| +| MNP Indicator | Foreign Number<br>PortedToForeign<br>Network | | | | +|---------------|----------------------------------------------|--|--|--| + +In all cases, the method to transport the routing number in the IAM depends on the interfaces agreed by the operators in the portability domain. + +--- + +# Annex D: Void + +# Annex E (informative): Change history + +| TSG CN# | Spec | Version | CR | <Phase> | New Version | Subject/Comment | +|-------------------|-----------|---------|-------|---------|-------------|-------------------------------------------------------------------------------------------------------------------------| +| #03 | GSM 03.66 | 7.1.0 | | | | Transferred to 3GPP CN2 | +| Aug 1999 | 23.066 | | | | 3.0.0 | | +| #05<br>Oct 1999 | 23.066 | 3.0.0 | 001 | | 3.1.0 | Harmonisation of terminology <b>interrogating</b> | +| #05<br>Oct 1999 | 23.066 | 3.0.0 | 002 | | 3.1.0 | Proposed changes to B.4.2 Delivery of SMS to a Non-ported Number - Direct Routeing – MNP-SRF acts as Higher-level Relay | +| #05<br>Oct 1999 | 23.066 | 3.0.0 | 003 | | 3.1.0 | Clarification of NPLR functionality in not known to be ported case | +| #07<br>Mar 2000 | 23.066 | 3.1.0 | 007r1 | R99 | 3.2.0 | Editorial cleanup | +| #07<br>Mar 2000 | 23.066 | 3.1.0 | 008r4 | R99 | 3.2.0 | Alignment of IN interface with Fixed Networks | +| #07<br>Mar 2000 | 23.066 | 3.1.0 | 009r3 | R99 | 3.2.0 | Detection of database synchronisation errors in SRF | +| #07<br>Mar 2000 | 23.066 | 3.1.0 | 012r2 | R99 | 3.2.0 | Result of Public Enquiry 9953 | +| #07<br>Mar 2000 | 23.066 | 3.1.0 | 015r1 | R99 | 3.2.0 | Clarification of NPDB error detection and MNP specific call handling | +| #08<br>Jun 2000 | 23.066 | 3.2.0 | 019r2 | R99 | 3.3.0 | North American Service Provider Number Portability impacts for Mobile Number Portability | +| #11<br>Mar 2001 | 23.066 | 3.3.0 | | Rel-4 | 4.0.0 | Release 4 after CN#11 | +| #16<br>Mar 2002 | 23.066 | 4.0.0 | | Rel-4 | 4.0.1 | References updated | +| #16<br>Jun 2002 | 23.066 | 4.0.1 | | Rel-5 | 5.0.0 | Release 5 after CN#16 | +| #20<br>Jun 2003 | 23.066 | 5.0.0 | 023r1 | Rel-5 | 5.1.0 | IN-based solution for correct charging of calls to ported or non-ported subscribers originated by pre-paid subscribers | +| #21<br>Sep 2003 | 23.066 | 5.1.0 | 026r1 | Rel-5 | 5.2.0 | Incorrect CAMEL pre-paid charging in MNP networks | +| CN#22<br>Dec 2003 | 23.066 | 5.2.0 | 027 | Rel-5 | 5.3.0 | Incorrect implementation of CR 023r1 | +| CN#22<br>Dec 2003 | 23.066 | 5.2.0 | 028r1 | Rel-5 | 5.3.0 | MNP correction for prepaid charging | +| CN#26 | 23.066 | 5.3.0 | | Rel-6 | 6.0.0 | Release 6 after CN#26 | +| CT#36 | 23.066 | 6.0.0 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.066 | 7.0.0 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | - | 8.0.0 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | - | 9.0.0 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | - | 10.0.0 | - | Rel-11 | 11.0.0 | Update to Rel-11 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23067/1bf34e86af3591c80bfbc1c318f811c0_img.jpg b/marked/Rel-11/23_series/23067/1bf34e86af3591c80bfbc1c318f811c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8df79fa3fdbf00c8e807e606762d1fbbc57fcd7b --- /dev/null +++ b/marked/Rel-11/23_series/23067/1bf34e86af3591c80bfbc1c318f811c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e7454fc979f025b6dcd27076e6c9497ff2643d1ca49ee2a5df988156d180c72 +size 58370 diff --git a/marked/Rel-11/23_series/23067/414cf5c0e2959c558de57a9fb5c2134a_img.jpg b/marked/Rel-11/23_series/23067/414cf5c0e2959c558de57a9fb5c2134a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c26ea6d379f027e26f1ddb55ea207c1e3f61194e --- /dev/null +++ b/marked/Rel-11/23_series/23067/414cf5c0e2959c558de57a9fb5c2134a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb546b1988f2e3bb169bb7b4e57205ffb45a6f4c536dd01a0c008e3e2566247a +size 27883 diff --git a/marked/Rel-11/23_series/23067/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/23_series/23067/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe1cee2e32dcdcaef75fd4f4373330faa00d776a --- /dev/null +++ b/marked/Rel-11/23_series/23067/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d97317a147d0b230e803c5fc421f5c5f923988a3ee076f9b71b6437e9ba2e98a +size 87997 diff --git a/marked/Rel-11/23_series/23067/96b0240f56d14453b5da05ec30fd5c6e_img.jpg b/marked/Rel-11/23_series/23067/96b0240f56d14453b5da05ec30fd5c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50c3c0454339983ea4de49a841e3f6dafd578751 --- /dev/null +++ b/marked/Rel-11/23_series/23067/96b0240f56d14453b5da05ec30fd5c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a75d7334ebcde0da487453a859022e92e4be5609b791a29eb5e690aa40750f85 +size 79422 diff --git a/marked/Rel-11/23_series/23067/b057cbcc73029e4684d3821b3f303e42_img.jpg b/marked/Rel-11/23_series/23067/b057cbcc73029e4684d3821b3f303e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2326bb93821217cb739e7e0aca9065e38cf999b --- /dev/null +++ b/marked/Rel-11/23_series/23067/b057cbcc73029e4684d3821b3f303e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c22bee7358eee7e38f7247adecd11e86b7011d5514ab2be21b0944a3b4168da9 +size 48487 diff --git a/marked/Rel-11/23_series/23067/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-11/23_series/23067/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8710011110d368b829c1a10b411d77379b33a478 --- /dev/null +++ b/marked/Rel-11/23_series/23067/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:194991cfb7d1ffc760064d0efc6ea8344646e0decbe50c1d2156d95969bebc82 +size 41457 diff --git a/marked/Rel-11/23_series/23067/c0e369274e53b2e5364666be6f786c7a_img.jpg b/marked/Rel-11/23_series/23067/c0e369274e53b2e5364666be6f786c7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcd0e15c4154911479dca4bd12daaeb817d88a11 --- /dev/null +++ b/marked/Rel-11/23_series/23067/c0e369274e53b2e5364666be6f786c7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe12567d7445251fe9c0259a8fb0172cada3d880c06379225d805d0584521c9f +size 40931 diff --git a/marked/Rel-11/23_series/23067/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/Rel-11/23_series/23067/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13671d010f8ffcecafb9284e0ba00412d4d7ee5a --- /dev/null +++ b/marked/Rel-11/23_series/23067/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16d568af51523fb53c2cd9e5cc784e17002a7bdd0e1f62581c1e25c7c89b7fd2 +size 30633 diff --git a/marked/Rel-11/23_series/23067/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg b/marked/Rel-11/23_series/23067/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d46f8d2b0a433153cf97f54fec3ed663048344e --- /dev/null +++ b/marked/Rel-11/23_series/23067/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c1443c84eb5f4438f8b3fc16f51cc624141fccaadaa1b4323be443e8efc4e61 +size 32739 diff --git a/marked/Rel-11/23_series/23067/raw.md b/marked/Rel-11/23_series/23067/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dab30ee788f1834c879336f9eaf96cae8ab6115d --- /dev/null +++ b/marked/Rel-11/23_series/23067/raw.md @@ -0,0 +1,907 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 Main concepts ..... | 7 | +| 5 General architecture ..... | 10 | +| 6 Compatibility issues..... | 10 | +| 7 Transmission ..... | 10 | +| 8 Information storage..... | 10 | +| 8.1 Stored in the HLR ..... | 10 | +| 8.1.1 State transition model ..... | 11 | +| 8.1.2 Transfer of information from HLR to VLR ..... | 11 | +| 8.2 Stored in the VLR ..... | 11 | +| 8.3 Stored in the MSC ..... | 11 | +| 8.4 Stored in the SIM ..... | 12 | +| 8.5 Stored in the GCR (GSM only)..... | 12 | +| 9 Identities..... | 12 | +| 10 Operation and maintenance aspects ..... | 12 | +| 11 Functions and information flow ..... | 13 | +| 11.1 Subscription..... | 13 | +| 11.2 Change of subscription..... | 13 | +| 11.3 Call set-up ..... | 13 | +| 11.3.1 Mobile originated calls ..... | 13 | +| 11.3.1.1 Indication of priority ..... | 13 | +| 11.3.1.2 Subscription checking..... | 13 | +| 11.3.1.3 Authentication and ciphering..... | 13 | +| 11.3.1.4 Indication of priority to the BSC/RNC ..... | 14 | +| 11.3.1.5 Choice of radio channel ..... | 14 | +| 11.3.1.6 Indication of priority to the Mobile Station ..... | 14 | +| 11.3.2 Mobile terminated calls ..... | 14 | +| 11.3.2.1 Indication of priority ..... | 14 | +| 11.3.2.2 Indication of priority to the BSC/RNC ..... | 15 | +| 11.3.2.3 Authentication and ciphering..... | 15 | +| 11.3.2.4 Termination with called subscriber in idle mode or group receive mode ..... | 15 | +| 11.3.2.5 Termination with called subscriber in dedicated mode ..... | 15 | +| 11.3.3 Voice group call or voice broadcast call (GSM only)..... | 16 | +| 11.3.3.1 Indication of priority to the related MSC..... | 16 | +| 11.3.3.2 Authentication and ciphering..... | 16 | +| 11.3.3.3 Indication of priority to the called Mobile Stations ..... | 16 | +| 11.4 Pre-emption ..... | 16 | +| 11.4.1 Choice of communication to pre-empt..... | 16 | +| 11.4.2 Release procedures ..... | 16 | +| 11.5 Pre-emption at handover/relocation ..... | 16 | +| 11.6 Overview of call related signalling ..... | 16 | +| 11.7 Overview of call independent signalling..... | 24 | +| 11.7.1 Registration..... | 24 | +| 11.7.2 Interrogation ..... | 24 | + +Annex A (informative): Change history..... 25 + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the stage 2 description of the enhanced Multi-Level Precedence and Pre-emption Service (eMLPP) which provides different call priorities in combination with fast call set-up and pre-emption for different applications according to 3GPP TS 22.067. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. + +- [1] 3GPP TR 21.905: "3G Vocabulary". +- [2] 3GPP TS 22.101: "UMTS Service Principles". +- [3] 3GPP TS 22.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage 1". +- [4] 3GPP TS 23.011: "Technical realization of supplementary services". +- [5] 3GPP TS 43.068: "Voice Group Call Service (VGCS) - Stage 2". +- [6] 3GPP TS 43.069: "Voice Broadcast Service (VBS) - Stage 2". +- [7] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification". +- [8] ITU-T Recommendation Q.85: "Stage 2 description for community of interest supplementary services (clause 3: Multi-Level Precedence and Pre-emption MLPP)". +- [9] ITU-T Recommendation Q.735: "Stage 3 description for community of interest supplementary services using SS No. 7 (clause 3: Multi-Level Precedence and Pre-emption (MLPP))". +- [10] *Void* +- [11] 3GPP TS 25.331: "RRC Protocol Specification". +- [12] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling". +- [13] 3GPP TS 24.008: "Core Network Protocols - Stage 3". +- [14] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture". +- [15] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 22.067 and the following apply: + +**resource pre-emption:** the termination of a call of a low priority user such that resources can be made available for a precedence call of higher priority. Resource pre-emption could be initiation resource pre-emption or handover resource pre-emption + +**called-party pre-emption:** termination of a call to a particular user when a higher priority call is directed towards that specific user. Called party pre-emption is decided by the Mobile Station. In case of point-to-point calls, this shall be performed by Call Waiting with automatic acceptance of the waiting call by the Mobile Station + +**compatible Mobile Station:** mobile stations which support eMLPP and therefore have precedence and pre-emption capabilities + +**non-compatible Mobile Station:** mobile stations which do not support eMLPP + +**SIM:** subscriber Identity Module. This specification makes no distinction between SIM and USIM. + +Handover: This specification uses the term handover for GSM and the same term meaning relocation in UMTS. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3G TR 21.905 apply. + +# --- 4 Main concepts + +The enhanced Multi-Level Precedence and Pre-emption service (eMLPP) provides different levels of precedence for call set-up and for call continuity in case of handover. + +There are seven priority levels which are defined in 3GPP TS 22.067. The highest level (A) is reserved for network internal use. The second highest level (B) may be used for network internal use or, optionally, depending on regional requirements, for subscription. These two levels (A and B) may only be used locally, i.e. in the domain of one MSC. The other five priority levels are offered for subscription and may be applied globally, e.g. on inter switch trunks, if supported by all related network elements, and also for interworking with ISDN networks providing the MLPP service. + +The seven priority levels are defined as follows: + +- A (highest, for network internal use) +- B (for network internal use or, optionally, for subscription) +- 0 (for subscription) +- 1 (for subscription) +- 2 (for subscription) +- 3 (for subscription) +- 4 (lowest, for subscription). + +Levels A and B shall be mapped to level 0 for priority treatment outside of the MSC area in which they are applied. + +As a network specific configuration, the ability to pre-empt other calls of lower priority and the application of fast call set-up procedures can be assigned to each priority level. An example for an eMLPP configuration is given in 3GPP TS 22.067. + +NOTE 1: The present specification defines the concepts for handling of priorities in the network including the indication whether pre-emption or fast call set-up procedures are to be applied. Note that the call set-up procedures themselves are specified in the corresponding stage 2 descriptions of the services where they are to be used. There is presently only a requirement for VBS and VGCS (3GPP TS 43.069 and 3GPP TS 43.068, respectively). + +NOTE 2: The network operator has to assure that the particular eMLPP configuration he applies and the subscriptions he issues are co-ordinated with the network planning (especially for blocking) and the implementation options applied (e.g. the use of OACSU) in order to guarantee the service performance for the subscriber. + +Considering aspects of priority handling, the following issues can be considered for each call: + +- a) contention during the initial random access (no specific definitions apply for eMLPP. Delays due to access collision have to be managed by a corresponding planning of the network resources); +- b) in GSM, contention in gaining radio resources during the call set-up phase and during handover (this item relates to the assignment of SDCCH and TCH for which queuing and pre-emption mechanisms are applied for eMLPP); +in UMTS, contention in gaining radio resources during the call set-up phase and during relocation (this item relates to the assignment of DCCH and DTCH for which queuing and pre-emption mechanisms are applied for eMLPP); +A pre-emption might already be performed as a network option on the basis of the establishment cause if a network specific eMLPP configuration assigns a certain priority level to a particular establishment cause. +- c) contention in gaining terrestrial resources inside the GSM or UMTS network (this item relates to the assignment of terrestrial channels between the GSM or UMTS network nodes. Priority actions shall be performed on basis of the MLPP service implementations. The eMLPP priority levels A and B shall be mapped to the MLPP priority level 0. No further specific definitions apply for eMLPP); +- d) contention in gaining terrestrial resources in external networks (this item relates to interworking with external networks which shall be performed on basis of the MLPP service if provided in the related external networks.); +- e) application of different call set-up procedures in relation to the priority levels and the network specific configuration (three classes of set-up performance are defined in 3GPP TS 22.067, one very fast class for VBS or VGCS emergency call services, one class for fast but normal set-up times and one class allowing some delay in the set-up. The application of the corresponding procedures shall be decided by the network on the basis of the requested priority level); +- f) automatic answering of calls if the incoming call exceeds a defined priority level (if the MS is in idle mode), or called party pre-emption (if the called subscriber is engaged in communication of a lower priority); +- g) the means by which the called user is informed of priority issues and is able to make appropriate decisions if no called party pre-emption applies; +- h) the accommodation of non-compatible Mobile Stations. + +The definitions in the present specification focus on the issues under item b), e), f), g) and h). Items c) and d) are related to the MLPP service implementation for the signalling system No. 7 according to ITU-T Recommendations Q.85 and Q.735. + +For a call establishment, a subscriber shall be able to select any one of the priority levels he has subscribed to. + +Priorities shall be treated in the network as defined in 3GPP TS 22.067. Priority treatment is different for point-to-point calls and voice broadcast calls or voice group calls, respectively: + +- mobile originated point-to-point call: + +The priority level depends on the calling subscriber. If the user has no eMLPP subscription, the call shall have a default priority level defined in the network. If the user has an eMLPP subscription, the call shall have the priority level selected by the user at set-up or the priority level predefined by the subscriber as default priority level by registration. + +- mobile terminated point-to-point calls: + +The priority level depends on the calling party. For this, interworking with the ISDN MLPP service is required. If the call is not an MLPP call, i.e. no priority level is defined, the call shall be treated in the mobile network with a default priority level. If the call is an MLPP call, the call shall be treated with the priority level provided by the interfacing network. + +- mobile to mobile point-to-point calls: + +The priority shall be treated for the calling subscriber as for mobile originated calls and for the called subscriber as for mobile terminated calls. However, an interworking with MLPP is not required if both the calling subscriber and the called subscriber are located in the same MSC area. + +- Voice Broadcast Calls (VBS) and Voice Group Calls (VGCS): + +The link on the voice broadcast call channel or voice group call channel shall have the priority level as defined in the corresponding registration for the related voice broadcast call or voice group call in the GCR. At the early stage of a voice broadcast call or voice group call establishment, before the GCR request is made and the voice broadcast call channel or voice group call channels are assigned, the procedure shall be the same as for point-to-point calls. If the GCR response includes a priority level it shall be applied to the dedicated link of the calling mobile station as well. + +Queuing and resource pre-emption shall then be applied as appropriate according to the network service configuration. In addition, automatic answering or called party pre-emption shall be applied as appropriated according to the Mobile Station's internal service configuration. + +The MSC shall maintain a record of the priority level of each call in progress in its area such that it can arbitrate over resources in a defined manner. + +The priority level can be included in the CM\_SERVICE\_REQUEST message in the case that a user establishing a point-to-point call is using a compatible Mobile Station (see clause 6). + +If the subscriber has not selected a priority level for that call or uses a non compatible Mobile Station (see clause 6), the priority level shall be assigned according to the respective VLR data. + +The priority level of a call shall be determined by the MSC. Accordingly, the MSC shall request channel assignment with an indication of the priority level and the pre-emption capability of that call. For this the MSC shall use the priority message element as defined in 3GPP TS 48.008. Mapping of the priority information in this message element on the network specific eMLPP configuration shall be performed in the MSC. Queuing and resource pre-emption shall be performed accordingly if necessary. + +In GSM, in addition to the priority signalling, the requirement for a direct assignment of a TCH shall be included in the establishment cause of the CHAN\_REQ message in order to support a fast call set-up procedure in the BSC at the earliest possible stage of the call establishment for high priority calls if applicable. + +In UMTS, in addition to the priority signalling, the RRC CONNECTION REQUEST message shall be included the establishment cause. + +Automatic answering or, if necessary, called-party pre-emption has to be performed by the Mobile Station as defined in the following: + +- point-to-point calls: + +If the user is in idle mode, the Mobile Station shall automatically connect to an incoming call of a sufficient priority level. The priority level shall be included in the paging message and in the set-up message. If the user is in dedicated mode and has a subscription to Call Waiting, a Call Waiting indication including the priority level of the call shall be given to the Mobile Station which automatically accepts the waiting call. + +There is no called party pre-emption for point-to-point calls without Call Waiting. + +- voice group calls and voice broadcast calls: + +Notifications for other voice group calls, voice broadcast calls or information on paging for point-to-point calls shall be given to the Mobile Stations involved in on-going voice group calls or voice broadcast calls as defined in 3GPP TS 43.068 and 3GPP TS 43.069, respectively. The notifications include the related priority level of the call. In case of a notified call with higher priority where called-party pre-emption applies, the Mobile Station shall automatically leave the on-going voice group call or voice broadcast call and react according to the type of the notified call type. + +For both cases, the priority level applied shall be included, either in the paging message or Call Waiting indication, or in the notification message, in order to enable the Mobile Station to decide on an automatic reaction (automatic answering or called-party pre-emption) or to indicate the incoming, non pre-empting call to the user. + +The priority information of the assignment request shall also be applied for BSS internal and also UTRAN internal handover. For external handover, the MSC shall include the priority information in the handover request according to the definition in 3GPP TS 48.008 (for GSM) and TS 25.413 (for UMTS) in the same way as for the assignment request. + +# --- 5 General architecture + +No specific requirements are identified. + +# --- 6 Compatibility issues + +eMLPP cannot be applied with standard GSM Phase 1 or Phase 2 Mobile Stations (non compatible Mobile Stations) with all service aspects. A dedicated Mobile Station (compatible Mobile Station) with eMLPP capability is required. + +Specific functions a compatible Mobile Station shall provide are: + +- priority selection via MMI for call establishment in case of an eMLPP subscription including priority levels above level 4; +- analysis of the priority level included in a paging message, Call Waiting indication or notification into a voice group call or voice broadcast call, respectively; +- automatic reaction on basis of the analysed priority level in case of an incoming call while in dedicated mode, group transmit mode or group receive mode, respectively, according to the user defined Mobile Station configuration (for each subscribed priority level the user shall be able to configure the Mobile Station for automatic acceptance or indication or rejection of an incoming call); + +NOTE: Functions related to notifications are only required for Mobile Stations providing VBS or VGCS functions as defined in 3GPP TS 43.069 and 3GPP TS 43.068, respectively. + +However, if eMLPP is provided in a network, it can be applied to non compatible Mobile Stations in the following way: + +- calls of subscribers which have no specific eMLPP subscription shall be treated for resource pre-emption with a default priority level. + +This shall also apply independent of the use of compatible or non compatible Mobile Stations; + +- calls of eMLPP subscribers which use a non compatible Mobile Station shall be treated for resource pre-emption with the subscriber's default priority level; +- calls to eMLPP subscribers which use a non compatible Mobile Station shall be indicated to the user by Call Waiting as normal. + +# --- 7 Transmission + +No specific requirements are identified. + +# --- 8 Information storage + +## 8.1 Stored in the HLR + +Information concerning the maximum priority level which a subscriber is entitled to use at call establishment shall be stored in the HLR. + +If the maximum priority level is above level 4, one level shall be indicated as default level. This default level shall be used for mobile originated calls if no priority selection is performed by the user at call establishment. + +The default selection can be performed by the subscriber by means of a registration procedure. + +NOTE The priority levels in the subscription are related to point-to-point calls. VBS and VGCS calls are treated with the priority level defined in the GCR for a certain group ID in a certain group call area which can be different to the priority levels explicitly defined in the eMLPP subscription. However, these levels are then implicitly defined with the subscribed group IDs. + +eMLPP may have the following logical states (refer to 3GPP TS 23.011 for an explanation of the notation): + +| <b>Provisioning State</b> | <b>Registration State</b> | <b>Activation State</b> | <b>HLR Induction State</b> | +|---------------------------|---------------------------|-------------------------|----------------------------| +| (Not Provisioned, | Not Registered, | Not Active | Not Induced) | +| (Provisioned, | Registered, | Active and Operative | Not Induced) | + +The HLR shall store the logical state of eMLPP (which shall be one of the valid states listed above) on a per subscriber basis. + +### 8.1.1 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of eMLPP. The state changes are caused by actions of the service provider. + +Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram. + +![State transition model for eMLPP diagram showing two states and two transitions.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +``` + +stateDiagram-v2 + [*] --> State1 : (Not Provisioned, Not Registered, Not Active, Not Induced) + State1 --> State2 : Provision + State2 --> State1 : Withdrawal + state " (Not Provisioned, Not Registered, Not Active, Not Induced) " as State1 + state " (Provisioned, Registered, Active and Operative, Not Induced) " as State2 + +``` + +The diagram illustrates the state transition model for eMLPP. It consists of two states represented by ovals. The left state is labeled "(Not Provisioned, Not Registered, Not Active, Not Induced)". The right state is labeled "(Provisioned, Registered, Active and Operative, Not Induced)". A curved arrow labeled "Provision" points from the left state to the right state. A curved arrow labeled "Withdrawal" points from the right state back to the left state. + +State transition model for eMLPP diagram showing two states and two transitions. + +**Figure 1: State transition model for eMLPP** + +### 8.1.2 Transfer of information from HLR to VLR + +If the provisioning state for eMLPP is “Provisioned” then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of eMLPP, the maximum priority level and the default priority level. + +If any of the eMLPP subscriber data is changed, the HLR shall send to the VLR the complete eMLPP subscriber data. + +## 8.2 Stored in the VLR + +For eMLPP, the VLR shall store the service state information, the maximum priority level a subscriber is entitled to use and the default priority level received from the HLR. + +## 8.3 Stored in the MSC + +The network specific service configuration of eMLPP defined by the network operator as specified in 3GPP TS 22.067 shall be stored within each MSC. This includes information on resource pre-emption actions for any given levels of incoming and on-going call priority. An example for a network specific service configuration is given in 3GPP TS 22.067. + +## 8.4 Stored in the SIM + +Each compatible Mobile Station shall be aware of the automatic answering actions for any given levels of priority so that when in idle mode or dedicated mode or group receive mode or group transmit mode, it can decide on the necessary reactions to be taken according to the priority information of the incoming call. + +For this, the SIM shall store the following data: + +| Priority level | Subscription available | Automatic answering applies | Fast set-up actions (note) | +|----------------|------------------------|-----------------------------|----------------------------| +| A | yes/no | yes/no | yes/no | +| B | yes/no | yes/no | yes/no | +| 0 | yes/no | yes/no | yes/no | +| 1 | yes/no | yes/no | yes/no | +| 2 | yes/no | yes/no | yes/no | +| 3 | yes/no | yes/no | yes/no | +| 4 | yes/no | -- | yes/no | + +NOTE: Fast set-up actions which shall be performed by the Mobile Stations if indicated in the SIM data are the use of the appropriate establishment cause and the reaction on accelerated establishment procedures allowed by the network (see subclause 11.6). + +The automatic reaction of the Mobile Station for automatic answering or called party pre-emption shall be predefined by the user via MMI. For each subscribed priority level the user shall be able to configure the Mobile Station for automatic acceptance or indication or rejection of an incoming call. + +In addition, the Mobile Station shall verify a priority level selected by the user at call establishment against the priority levels stored on the SIM and act accordingly as defined in subclause 11.5.1.2. + +The Mobile Station shall perform automatically the related functions for a fast call set-up if related with a selected priority. + +## 8.5 Stored in the GCR (GSM only) + +In the network, specific service configurations for VBS and VGCS calls which are registered in the GCR, a priority level shall be assigned to each voice broadcast call or voice group call configuration, according to 3GPP TS 43.069 and 3GPP TS 43.068, respectively. + +# 9 Identities + +No specific requirements are identified. + +# 10 Operation and maintenance aspects + +NOTE: A list and short description of the operation and maintenance aspects will be given. This includes the options and parameters which can be set by the operator. + +- Handling of timers; +- registration aspects etc. + +# 11 Functions and information flow + +## 11.1 Subscription + +When the subscriber record is created in the HLR, the maximum priority level a subscriber is entitled to use shall be included. + +## 11.2 Change of subscription + +The network operator can change the maximum priority level of any eMLPP subscriber at any time. A change of subscription shall not affect any on-going calls at the moment of change. The subscriber cannot change the maximum priority level via the MMI. + +## 11.3 Call set-up + +### 11.3.1 Mobile originated calls + +#### 11.3.1.1 Indication of priority + +The Mobile Station may indicate the priority of each call initiated. If no priority is indicated by the user or a non-compatible Mobile Station is used then the default priority level shall be applied which is stored in the VLR. The selection of priority shall be an MMI function. + +Mobile stations indicate the priority of their call in the signalling that takes place during the call establishment process. + +No preferential treatment will be possible during this initial random access until the point at which the priority information is received by the network (CM\_SERV\_REQ message). Alternatively, a resource pre-emption might already take place on basis of an establishment cause. + +In GSM, prior to the indication of the selected priority level in the CM\_SERV\_REQ message, the BSC may decide on the assignment of an SDCCH or direct assignment of a TCH on the basis of the establishment cause in the CHAN\_REQ message. This allows the BSC to support a fast call set-up at the earliest stage of the call establishment. The establishment cause for emergency calls or an establishment cause indicating the request for fast call set-up shall be able to trigger this function. + +In UMTS, prior to the indication of the selected priority level in the CM\_SERV\_REQ message, the RNC shall receive the establishment cause in the RRC CONNECTION SETUP REQUEST. + +#### 11.3.1.2 Subscription checking + +The Mobile Station shall verify the selected priority level against the priority levels stored in the SIM. If the selected priority is not allowed, then the priority of the call shall be modified to that of the nearest allowed priority level below the requested level. + +The MSC shall request the VLR to verify if the subscriber is allowed to use the selected priority level. + +#### 11.3.1.3 Authentication and ciphering + +A GSM network may wish to omit or postpone authentication and ciphering in order to provide for a faster call set-up. + +If the network decides to omit or postpone authentication and ciphering for a call it can send a CM\_SERV\_ACC message in reply to the CM\_SERV\_REQ message. + +#### 11.3.1.4 Indication of priority to the BSC/RNC + +In GSM, the channel assignment request to the BSC shall also include the priority level and pre-emption capability of the connection as defined in 3GPP TS 48.008. The MSC maps the eMLPP priority on these priority levels. In addition, the eMLPP priority shall be explicitly indicated to the BSC in the assignment request. The BSC shall store the priority level in order to decide on later actions, e.g. to arrange notifications to the Mobile Station according to priorities. + +In UMTS, the RAB assignment request to the RNC may also include the priority level and pre-emption capability of the connection as defined in TS 25.413 [12]. The MSC maps the eMLPP priority on these priority levels. In addition, the eMLPP priority shall be explicitly indicated to the RNC in the RAB assignment request. Values for radio access bearer service attributes defined in TS 23.107 [14] should be taken into account for mapping from eMLPP priority into priority related information element in RANAP. The RNC shall store the priority level in order to decide on later actions, e.g. to arrange notifications to the Mobile Station according to priorities. + +#### 11.3.1.5 Choice of radio channel + +If an appropriate radio channel is available the BSC (for GSM) or the RNC (for UMTS) shall assign it as normal. If no channels are available then the BSC (for GSM) or the RNC (for UMTS) shall perform queuing according to the priority levels. If the assignment request has a pre-emption capability indicator, pre-emption shall be performed. + +In addition, the network related service configuration defines the set-up class in relation to a priority level and therefore the allowable delay of the call establishment (see 3GPP TS 22.067). By using this information, the MSC shall decide whether OACSU may be applied for a call or not. + +#### 11.3.1.6 Indication of priority to the Mobile Station + +The network shall include the assigned priority level in a CALL\_PROCEEDING message if the network supports priority. + +The Mobile Station shall store the priority level requested by the user, possibly overridden by the level received by the network, to perform automatic answering of calls or pre-emption of on-going calls. + +NOTE: When the mobile station connects to the R98 or older network, the mobile station may not receive priority granted even if the network supports priority. + +### 11.3.2 Mobile terminated calls + +#### 11.3.2.1 Indication of priority + +For a mobile terminated call, the priority level is defined in the ISUP set-up message to the VMSC. It may also be present in the MAP\_PROVIDE\_ROAMING\_NUMBER request (see 3GPP TS 29.002 [15]). The priority and pre-emption indications used in the ISUP shall follow the definitions of the MLPP service as defined in the ITU-T recommendations Q.85 and Q.735, respectively. + +In GSM, a PAGING REQUEST message on CCCH may also include a priority level as described in GSM 04.08 [10], subsection 'Paging initiation using paging subchannel on CCCH'. + +NOTE: A mobile stations in idle mode which are going to respond to a paging message do not need to analyse the priority level in the paging request message but can take the priority level provided in the set-up message. A mobile stations in group receive mode or an MS in class-B mode that communicates on GPRS radio channels when a dedicated channel is needed need to analyse the priority level in the paging request message in order to decide to respond to the paging request. (see TS 23.060 subclause 16.2.2) + +#### 11.3.2.2 Indication of priority to the BSC/RNC + +In GSM, the channel assignment request to the BSC may include the priority level and pre-emption capability of the connection as defined in 3GPP TS 48.008. The MSC maps the eMLPP priority on these priority levels. In addition, the eMLPP priority shall be explicitly indicated to the BSC in the assignment request. The BSC shall store the priority level in order to decide on later actions, e.g. to arrange notifications to the Mobile Station according to priorities. + +In UMTS, the RAB assignment request to the RNC may include the priority level and pre-emption capability of the connection as defined in TS 25.413. The MSC maps the eMLPP priority on these priority levels. In addition, the eMLPP priority shall be explicitly indicated to the RNC in the RAB assignment request. Values for radio access bearer service attributes defined in TS 23.107 [14] should be taken into account for mapping from eMLPP priority into priority related information element in RANAP. The RNC shall store the priority level in order to decide on later actions, e.g. to arrange notifications to the Mobile Station according to priorities. + +#### 11.3.2.3 Authentication and ciphering + +The network may wish to omit or postpone authentication and ciphering in order to provide for a faster call set-up according to the priority level to be applied for the call and the network specific service configuration stored in the MSC. + +If the network decides to omit or postpone authentication and ciphering for a call it, can send the SETUP message immediately after reception of the initial layer 3 message. + +#### 11.3.2.4 Termination with called subscriber in idle mode or group receive mode + +In this case the Mobile Station shall be paged in the normal manner, but with the paging messages also containing the priority level of the call. In addition, the priority level will be provided with the SETUP message. + +The Mobile Station in group receive mode shall consult the internal service configuration list stored on the SIM to check whether it should automatically respond to the paging request. If it does respond to the paging request and if a following Call Control SETUP message (received as a response to paging response) specifies a priority different from + +the one specified in the paging request, this fact is not a reason for the mobile station to reject the (point-to-point) call for which the SETUP message was received. + +The Mobile Station in idle mode does not need to analyse the priority level from the paging request message but can derive it from the SETUP message and then decide on automatic acceptance of the call. + +In the case where the called subscriber is using a non compatible Mobile Station, automatic answering is not possible. + +#### 11.3.2.5 Termination with called subscriber in dedicated mode + +In the case where the called subscriber has a subscription for eMLPP and for Call Waiting and is using a compatible Mobile Station, the Mobile Station shall be informed of the priority of the new call together with the call waiting indication. The Mobile Station will then consult the internal service configuration list stored on the SIM to establish whether it should automatically accept the waiting call without consulting the user, or whether the call waiting facility will be used as normal. + +In the case where the called subscriber has no subscription for Call Waiting, called party pre-emption is not possible. + +In the case where the called subscriber is using a non compatible Mobile Station and has a subscription for Call Waiting, Call Waiting shall be performed as normal. + +### 11.3.3 Voice group call or voice broadcast call (GSM only) + +#### 11.3.3.1 Indication of priority to the related MSC + +For each voice group call or voice broadcast call service configuration registered in the GCR as defined in 3GPP TS 43.068 and 3GPP TS 43.069, respectively, a priority level is assigned at registration of the GCR data by the service provider. The priority level will be provided by the GCR together with the call attributes. + +#### 11.3.3.2 Authentication and ciphering + +Authentication of the calling service subscriber shall be performed equivalent to the standard mobile originated call case as defined in subclause 11.5.1.3. If the GCR response provides a priority level then the calling service subscriber shall be treated with the GCR defined priority. If not, then the calling service subscriber shall be treated with his selected priority or with his default priority as known in the VLR as long as he has an own link with the network (see 3GPP TS 43.068 and 3GPP TS 43.069). The priority which applies to the voice group call channel or voice broadcast call channel is defined in the GCR. + +Authentication and ciphering of the calling service subscriber might therefore be performed, omitted or postponed (see subclause 11.3.1.3). + +#### 11.3.3.3 Indication of priority to the called Mobile Stations + +The priority level shall be indicated together with the related paging messages or notification messages and treated in the Mobile Station as defined in 3GPP TS 43.068 and 3GPP TS 43.069, respectively. + +## 11.4 Pre-emption + +### 11.4.1 Choice of communication to pre-empt + +For all resources where pre-emption may be required, namely radio channels, A-interface (for GSM) or Iu interface (for UMTS) channels and inter switch trunks, the network specific service configuration stored within the MSC shall be used to determine whether pre-emption should occur, and if so, which communication to pre-empt. The MSC shall inform the BSS (for GSM) or RNC (for UMTS) about priority and pre-emption by using the priority message element in the assignment request as defined in 3GPP TS 48.008 (for GSM) and TS 25.413 [12] (for UMTS). Mapping of the priority information in this message element on the network specific eMLPP configuration shall be performed in the MSC. + +### 11.4.2 Release procedures + +Suitable messages shall be passed from the point at which the pre-emption is to occur, to other affected entities. In the case of fast call set-up, such pre-indication may need to be foregone to meet the required set-up time. + +The indication to the pre-empted user shall be performed by an indication for congestion as defined in 3GPP TS 22.101. + +## 11.5 Pre-emption at handover/relocation + +When an on-going call is handed over or relocated into a fully used cell, the BSC or RNC shall perform queuing and pre-emption if necessary according to the priority and pre-emption capability information received with the assignment request. + +In case of BSS external handover or RNC relocation, the priority and pre-emption capability information shall be included in the handover request as defined in 3GPP TS 48.008 (for GSM) and TS 25.413 [12] (for UMTS). + +## 11.6 Overview of call related signalling + +In this overview, the message structure to implement the specified concept is identified, and brief details are given of each message. + +A diagrammatic representation of the transport procedures to be used to carry the priority information in case of standard point-to-point calls are given in figures 1 to 6. The message flow is not represented completely. + +The corresponding message flows in case of voice group calls or voice broadcast calls are given in 3GPP TS 23.068 and 3GPP TS 23.069, respectively. + +![Sequence diagram showing signalling information required for the prioritisation at mobile originating call establishment without fast call set-up (for GSM). The diagram shows message flows between MS, BSS, and MSC.](96b0240f56d14453b5da05ec30fd5c6e_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note left of MS: Initial RACH_CHAN_REQ: Standard message. + MS->>BSS: RACH_CHAN_REQ + BSS-->>MS: IMM_ASS + MS->>BSS: SABM (SERV_REQ) + BSS->>MSC: COM L3 INFO + BSS-->>MS: UA (SERV REQ) + MSC->>BSS: AUTH_REQ + BSS-->>MS: AUTH_RES + MSC->>BSS: CIPH_MOD_CMD + BSS-->>MS: CIPH_MOD_COM + MS->>MSC: SETUP + MSC-->>BSS: CALL_PROCEEDING + BSS-->>MS: ASS_CMD + MSC->>BSS: ASS_REQ + MS->>BSS: SABM + BSS-->>MS: UA + MS->>BSS: ASS_COM + BSS->>MSC: ASS_COM + +``` + +Sequence diagram showing signalling information required for the prioritisation at mobile originating call establishment without fast call set-up (for GSM). The diagram shows message flows between MS, BSS, and MSC. + +**Figure 2: Signalling information required for the prioritisation at mobile originating call establishment without fast call set-up (for GSM)** + +**Initial RACH\_CHAN\_REQ:** Standard message. + +**IMM\_ASS:** Standard message. + +**SABM (SERV\_REQ):** Modified form of the current L3-MM CM SERVICE REQUEST where the priority level is provided in addition if a priority selection is performed by the user. In case of no priority selection or use of a non-compatible Mobile Station the Mobile Station shall send a standard service request message and the network shall apply a default priority to their request. + +**UA (SERV\_REQ):** Standard message. + +**COM\_L3\_INFO:** The MSC is provided with initial information about the requested service together with the selected priority level if applicable. + +**AUTH\_REQ:** Standard message. + +**AUTH\_RES:** Standard message. + +**CIPH\_MOD\_CMD:** Standard message. + +**CIPH\_MOD\_COM:** Standard message. + +**SETUP:** Standard message. + +**CALL\_PROCEEDING:** The network shall include the assigned priority level in a CALL\_PROCEEDING message when the network supports priority. + +**ASS\_REQ:** This message is sent from the MSC to the BSC including the call priority and pre-emption capability to be applied as defined in 3GPP TS 48.008, according to the priority information the MSC has obtained from the service request or from the VLR data. In addition, the eMLPP level is included as explicit information. + +**ASS\_CMD:** Standard message. + +**SABM:** Standard message. + +**UA:** Standard message. + +**ASS\_COM:** Standard message. + +###### Release 9 + +![Sequence diagram showing signalling information required for the prioritisation at mobile originating call establishment with fast call set-up (for GSM). The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is as follows: 1. MS sends [SYSTEM INFO] to BSS. 2. MS sends RACH (CHAN_REQ) to BSS. 3. BSS sends IMM_ASS to MS. 4. MS sends SABM (SERV_REQ) to BSS. 5. BSS sends COM_L3_INFO to MSC. 6. BSS sends UA (SERV_REQ) to MS. 7. BSS sends SETUP to MSC. 8. MSC sends CALL_PROCEEDING to BSS. 9. BSS sends CHAN_MOD_MODIFY to MS. 10. MS sends CHAN_MOD_MODIFY_ACK to BSS.](b057cbcc73029e4684d3821b3f303e42_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note left of MS: MS + MS->>BSS: [SYSTEM INFO] + MS->>BSS: RACH (CHAN_REQ) + BSS-->>MS: IMM_ASS + MS->>BSS: SABM (SERV_REQ) + BSS->>MSC: COM_L3_INFO + BSS-->>MS: UA (SERV_REQ) + BSS->>MSC: SETUP + MSC-->>BSS: CALL_PROCEEDING + BSS-->>MS: CHAN_MOD_MODIFY + MS->>BSS: CHAN_MOD_MODIFY_ACK + +``` + +Sequence diagram showing signalling information required for the prioritisation at mobile originating call establishment with fast call set-up (for GSM). The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is as follows: 1. MS sends [SYSTEM INFO] to BSS. 2. MS sends RACH (CHAN\_REQ) to BSS. 3. BSS sends IMM\_ASS to MS. 4. MS sends SABM (SERV\_REQ) to BSS. 5. BSS sends COM\_L3\_INFO to MSC. 6. BSS sends UA (SERV\_REQ) to MS. 7. BSS sends SETUP to MSC. 8. MSC sends CALL\_PROCEEDING to BSS. 9. BSS sends CHAN\_MOD\_MODIFY to MS. 10. MS sends CHAN\_MOD\_MODIFY\_ACK to BSS. + +**Figure 3: Signalling information required for the prioritisation at mobile originating call establishment with fast call set-up (for GSM)** + +**SYSTEM INFO:** *The network may provide information on the BCCH system information, that a MM connection is provisional granted after establishment of the main signalling link.* + +*If such information is provided on the BCCH and the user has selected a fast call set-up, the Mobile Station shall immediately send a SETUP message to the network after the main signalling link is established.* + +**Initial RACH CHAN\_REQ:** Standard message. + +**IMM\_ASS:** Standard message. + +**SABM (SERV\_REQ):** Modified form of the current L3-MM CM SERVICE REQUEST where the priority level is provided in addition if a priority selection is performed by the user. + +**UA (SERV\_REQ):** Standard message. + +**COM\_L3\_INFO:** The MSC is provided with initial information about the requested service together with the selected priority level if applicable. + +If the network itself decides not to perform ciphering, it shall send an CM\_SERV\_ACC message. + +**SETUP:** Standard message. + +**CALL\_PROCEEDING:** The network shall include the assigned priority level in a CALL\_PROCEEDING message when the network supports priority + +**ASS\_REQ:** This standard message is sent from the MSC to the BSC including the call priority and pre-emption capability to be applied as defined in 3GPP TS 48.008, according to the priority information the MSC has obtained from the service request or from the VLR data. In addition, the eMLPP level is included as explicit information. + +**CHAN\_MOD\_MODIFY:** Standard message. + +**CHAN\_MOD\_MODIFY\_ACK:** Standard message. + +![Sequence diagram showing signalling information for mobile terminating call establishment between MS, BSS, and MSC.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note right of MSC: SETUP (prec.) +req. ind. + MSC->>BSS: PAGING + BSS->>MS: PAG_REQ + MS->>BSS: RACH (CHAN_REQ) + BSS->>MS: IMM_ASS + MS->>BSS: SABM (PAG_RSP) + BSS->>MSC: PAG_RSP + MSC->>BSS: AUTH_REQ + BSS->>MS: AUTH_RES + MSC->>BSS: CIPH_MOD_CMD + BSS->>MS: CIPH_MOD_COM + MSC->>BSS: SETUP + BSS->>MS: CALL_CONF + MSC->>BSS: ASS_REQ + BSS->>MS: ASS_CMD + MS->>BSS: SABM + BSS->>MS: UA + MS->>BSS: ASS_COM + BSS->>MSC: ASS_COM + +``` + +Sequence diagram showing signalling information for mobile terminating call establishment between MS, BSS, and MSC. + +**Figure 4: Signalling information required for the prioritisation at mobile terminating call establishment without fast call set-up and without called-party pre-emption (for GSM)** + +**SETUP (prec.) req. ind.:** In addition to the basic call requirements, the contents of the set-up information flow shall contain the information on the requested MLPP priority level. + +**PAGING:** Modified paging command including the priority level to be applied. + +**PAG\_REQ:** Modified paging message including the related priority level. + +**Initial RACH CHAN\_REQ:** Standard message. + +**IMM\_ASS:** Standard message. + +**SABM (PAG\_RSP):** Standard message. + +**UA (PAG\_RSP):** Standard message. + +**PAG\_RSP:** Standard message. + +**AUTH\_REQ:** Standard message. + +**AUTH\_RES:** Standard message. + +**CIPH\_MOD\_CMD:** Standard message. + +**CIPH\_MOD\_COM:** Standard message. + +**SETUP:** Standard message. + +**CALL\_CONF:** Standard message. + +**ASS\_REQ:** This standard message is sent from the MSC to the BSC including the call priority and pre-emption capability to be applied as defined in 3GPP TS 48.008, according to the priority information the MSC has obtained from the incoming set-up message. In addition, the eMLPP level is included as explicit information. + +**ASS\_CMD:** Standard message. + +**SABM:** Standard message. + +**UA:** Standard message. + +**ASS\_COM:** Standard message. + +![Sequence diagram showing signalling information required for prioritisation at mobile terminating call establishment with fast call set-up and without called-party pre-emption. The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is as follows: 1. An external SETUP (prec.) req. ind. message arrives at the MSC. 2. The MSC sends a PAGING message to the BSS. 3. The BSS sends a PAG_REQ message to the MS. 4. The MS responds with a RACH (CHAN_REQ) message to the BSS. 5. The BSS sends an IMM_ASS message to the MS. 6. The MS responds with a SABM (PAG_RSP) message to the BSS. 7. The BSS sends a UA (PAG_RSP) message to the MSC. 8. The MSC sends a SETUP message to the MS. 9. The MS responds with a CALL_CONF message to the MSC. 10. The MSC sends a CHAN_MOD_MODIFY message to the MS. 11. The MS responds with a CHAN_MOD_MODIFY_ACK message to the BSS.](1bf34e86af3591c80bfbc1c318f811c0_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note right of MSC: SETUP (prec.) req. ind. + MSC->>BSS: PAGING + BSS->>MS: PAG_REQ + MS->>BSS: RACH (CHAN_REQ) + BSS->>MS: IMM_ASS + MS->>BSS: SABM (PAG_RSP) + BSS->>MSC: UA (PAG_RSP) + MSC->>MS: SETUP + MS->>MSC: CALL_CONF + MSC->>MS: CHAN_MOD_MODIFY + MS->>BSS: CHAN_MOD_MODIFY_ACK + +``` + +Sequence diagram showing signalling information required for prioritisation at mobile terminating call establishment with fast call set-up and without called-party pre-emption. The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is as follows: 1. An external SETUP (prec.) req. ind. message arrives at the MSC. 2. The MSC sends a PAGING message to the BSS. 3. The BSS sends a PAG\_REQ message to the MS. 4. The MS responds with a RACH (CHAN\_REQ) message to the BSS. 5. The BSS sends an IMM\_ASS message to the MS. 6. The MS responds with a SABM (PAG\_RSP) message to the BSS. 7. The BSS sends a UA (PAG\_RSP) message to the MSC. 8. The MSC sends a SETUP message to the MS. 9. The MS responds with a CALL\_CONF message to the MSC. 10. The MSC sends a CHAN\_MOD\_MODIFY message to the MS. 11. The MS responds with a CHAN\_MOD\_MODIFY\_ACK message to the BSS. + +**Figure 5: Signalling information required for the prioritisation at mobile terminating call establishment with fast call set-up and without called-party pre-emption** + +**SETUP (prec.) req. ind.:** In addition to the basic call requirements, the contents of the set-up information flow shall contain the information on the requested MLPP priority level. + +**PAGING:** Modified paging command including the priority level to be applied. + +**PAG\_REQ:** Modified paging message including the related priority level. + +**Initial RACH CHAN\_REQ:** Standard message. A new establishment cause shall be provided to indicate the requirement for the direct assignment of a TCH (very early assignment) for the support of fast call set-up procedure. + +**IMM\_ASS:** Standard message. + +**SABM (PAG\_RSP):** Standard message. + +**UA (PAG\_RSP):** Standard message. + +**PAG\_RSP:** Standard message. + +For fast call set-up the network shall immediately send a SETUP message to the Mobile Station. Authentication and ciphering may not be performed or delayed by the network.] + +**SETUP:** Modified message with an indication of the priority level. + +**CALL\_CONF:** Standard message. + +**ASS\_REQ:** This standard message is sent from the MSC to the BSC including the call priority and pre-emption capability to be applied as defined in 3GPP TS 48.008, according to the priority information the MSC has obtained from incoming set-up message. In addition, the eMLPP level is included as explicit information. + +**CHAN\_MOD\_MODIFY:** Standard message. + +**CHAN\_MOD\_MODIFY\_ACK:** Standard message. + +![Sequence diagram showing signalling information for called-party pre-emption. The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is as follows: 1. An external SETUP (prec.) req. ind. message is received by the MSC from the right. 2. The MSC sends a SETUP message to the BSS. 3. The BSS sends a CALL_CONF message to the MS. 4. The BSS sends an ALERT message to the MSC. 5. The BSS sends a HOLD message to the MSC. 6. The MSC sends a HOLD_ACK message to the BSS. 7. The BSS sends a CONNECT message to the MS. 8. The BSS sends a CONN_ACK message to the MSC.](c0e369274e53b2e5364666be6f786c7a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note right of MSC: SETUP (prec.) +req. ind. + MSC->>BSS: SETUP + BSS->>MS: CALL_CONF + BSS->>MSC: ALERT + BSS->>MSC: HOLD + MSC->>BSS: HOLD_ACK + BSS->>MS: CONNECT + BSS->>MSC: CONN_ACK + +``` + +Sequence diagram showing signalling information for called-party pre-emption. The diagram involves three entities: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence of messages is as follows: 1. An external SETUP (prec.) req. ind. message is received by the MSC from the right. 2. The MSC sends a SETUP message to the BSS. 3. The BSS sends a CALL\_CONF message to the MS. 4. The BSS sends an ALERT message to the MSC. 5. The BSS sends a HOLD message to the MSC. 6. The MSC sends a HOLD\_ACK message to the BSS. 7. The BSS sends a CONNECT message to the MS. 8. The BSS sends a CONN\_ACK message to the MSC. + +**Figure 6: Signalling information required for the called-party pre-emption in case of an existing telephony call and subscription for HOLD** + +Call Waiting should always be subscribed together with eMLPP. If not, no called party pre-emption is possible for point-to-point calls. + +**SETUP (prec.) req. ind.:** In addition to the basic call requirements, the contents of the set-up information flow shall contain the information on the requested MLPP priority level. + +**SETUP:** Modified SETUP message with an indication of the priority level. + +**CALL\_CONF:** Standard message with cause user busy. + +On reception of the SETUP message a compatible Mobile Station decides on called party pre-emption. If called party pre-emption applies, the Mobile Station shall automatically accept the waiting call and put the other call on hold. + +A non compatible Mobile Station shall not be harmed by the priority information and shall perform Call Waiting functions as normal. + +**ALERT:** Standard message. ALERTING may be omitted in case of called party pre-emption. + +**HOLD:** Standard message. + +**HOLD\_ACK:** Standard message. + +**CONNECT:** Standard message. + +**CONN\_ACK:** Standard message. + +NOTE: In case of an incoming data call a mode modify procedure has to be performed which is not included in figure 6. + +![Sequence diagram showing signalling information for called-party pre-emption. Lifelines: MS, BSS, MSC. The sequence starts with SETUP (prec.) req. ind. from MSC to BSS. BSS sends SETUP to MS. MS responds with CALL_CONF, ALERT, RELEASE_COM, CONNECT, and CONN_ACK messages back to BSS.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note right of MSC: SETUP (prec.) +req. ind. + MSC->>BSS: SETUP + BSS->>MS: CALL_CONF + BSS->>MS: ALERT + BSS->>MS: RELEASE_COM + BSS->>MS: CONNECT + BSS->>MS: CONN_ACK + +``` + +Sequence diagram showing signalling information for called-party pre-emption. Lifelines: MS, BSS, MSC. The sequence starts with SETUP (prec.) req. ind. from MSC to BSS. BSS sends SETUP to MS. MS responds with CALL\_CONF, ALERT, RELEASE\_COM, CONNECT, and CONN\_ACK messages back to BSS. + +**Figure 7: Signalling information required for the called-party pre-emption in case of point-to-point data calls or no subscription for HOLD** + +Call Waiting should always be subscribed together with eMLPP. If not, no called party pre-emption is possible for point-to-point calls. + +**SETUP (prec.) req. ind.:** In addition to the basic call requirements, the contents of the set-up information flow shall contain the information on the requested MLPP priority level. + +**SETUP:** Modified SETUP message with an indication of the priority level. + +**CALL\_CONF:** Standard message with cause user busy. + +On reception of the SETUP message a compatible Mobile Station decides on called party pre-emption. If called party pre-emption applies, the Mobile Station shall automatically accept the waiting call and clear the existing data call. + +A non compatible Mobile Station shall not be harmed by the priority information and shall perform Call Waiting functions as normal. + +**ALERT:** Standard message. ALERTING may be omitted in case of called party pre-emption. + +**RELEASE\_COM:** Standard message which shall be send immediately after the ALERT with a new cause for called party pre-emption. + +**CONNECT:** Standard message. + +**CONN\_ACK:** Standard message. + +## 11.7 Overview of call independent signalling + +### 11.7.1 Registration + +At the beginning of registration subscription, provision of the supplementary service and sufficiency of registration information has to be checked. + +The default priority level has to be registered in the network. + +When the mobile subscriber registers eMLPP, the network shall attempt to register the service. The network will return notification of acceptance of the request. This notification will include the default priority level. + +If the system cannot accept a registration request, the network sends a notification that eMLPP registration was not successful to the served mobile subscriber. + +The information flow for registration of eMLPP is shown in figure 8. + +![Sequence diagram for Figure 8: Registration of eMLPP. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The MS sends a 'Register eMLPP' message to the MSC. The MSC then sends a 'Register eMLPP' message to the VLR. The VLR sends a 'Register eMLPP' message to the HLR. The HLR returns an 'Acknowledge' message to the VLR. The VLR returns an 'Acknowledge' message to the MSC. The MSC returns an 'Acknowledge' message to the MS.](f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + MS->>MSC: Register eMLPP + MSC->>VLR: Register eMLPP + VLR->>HLR: Register eMLPP + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Acknowledge +``` + +Sequence diagram for Figure 8: Registration of eMLPP. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The MS sends a 'Register eMLPP' message to the MSC. The MSC then sends a 'Register eMLPP' message to the VLR. The VLR sends a 'Register eMLPP' message to the HLR. The HLR returns an 'Acknowledge' message to the VLR. The VLR returns an 'Acknowledge' message to the MSC. The MSC returns an 'Acknowledge' message to the MS. + +Figure 8: Registration of eMLPP + +### 11.7.2 Interrogation + +The mobile subscriber can request the status of the supplementary service, the maximum and default priority levels and be informed if the service is provided to him/her and on the actual maximum and default priority levels. This procedure is illustrated in figure 9. + +![Sequence diagram for Figure 9: Interrogation of eMLPP. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The MS sends an 'Interrogate eMLPP' message to the MSC. The MSC then sends an 'Interrogate eMLPP' message to the VLR. The VLR returns an 'Acknowledge' message to the MSC. The MSC returns an 'Acknowledge' message to the MS. The HLR lifeline is shown but not used in this sequence.](414cf5c0e2959c558de57a9fb5c2134a_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + MS->>MSC: Interrogate eMLPP + MSC->>VLR: Interrogate eMLPP + VLR-->>MSC: Acknowledge + MSC-->>MS: Acknowledge +``` + +Sequence diagram for Figure 9: Interrogation of eMLPP. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The MS sends an 'Interrogate eMLPP' message to the MSC. The MSC then sends an 'Interrogate eMLPP' message to the VLR. The VLR returns an 'Acknowledge' message to the MSC. The MSC returns an 'Acknowledge' message to the MS. The HLR lifeline is shown but not used in this sequence. + +Figure 9: Interrogation of eMLPP + +# Annex A (informative): Change history + +| Change history | | | | | | | +|----------------|-----------|---------|-------|---------|-------------|---------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | <Phase> | New Version | Subject/Comment | +| Apr 1999 | GSM 03.67 | 6.0.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.067 | | | | 3.0.0 | Approved at CN#03 | +| CN#07 | 23.067 | 3.0.0 | 001 | R99 | 3.1.0 | Cause pre-emption removed from HOLD message | +| CN#10 | 23.067 | 3.1.0 | 002r2 | R99 | 3.2.0 | The accepted priority in the call proceeding message | +| CN#10 | 23.067 | 3.1.0 | 007r3 | R99 | 3.2.0 | Correction of Pre-emption service (eMLPP) | +| CN#10 | 23.067 | 3.1.0 | 008r1 | R99 | 3.2.0 | Correction of Pre-emption service (eMLPP) | +| CN#10 | 23.067 | 3.2.0 | 004 | Rel-4 | 4.0.0 | Correction of abbreviations | +| CN#10 | 23.067 | 3.2.0 | 005r1 | Rel-4 | 4.0.0 | MS strategy in case of discrepancy of priority in MT | +| CN#10 | 23.067 | 3.2.0 | 006r1 | Rel-4 | 4.0.0 | Automatic answering | +| CN#12 | 23.067 | 4.0.0 | 010r1 | Rel-4 | 4.1.0 | Remove the statement when MS receives no priority granted | +| CN#16 | 23.067 | 4.1.0 | 010r1 | Rel-4 | 4.1.1 | References updated | +| CN#16 | 23.067 | 4.1.1 | 010r1 | Rel-5 | 5.0.0 | Release 5 after CN#16 | +| CN#19 | 23.067 | 5.0.0 | 011r1 | Rel-6 | 6.0.0 | Optional additional eMLPP priority level for subscription to accommodate Priority Service | +| CN#27 | 23.067 | 6.0.0 | 012r1 | Rel-6 | 6.1.0 | Clarification on mapping of eMLPP priorities | +| CT#30 | 23.067 | 6.1.0 | 0017 | Rel-7 | 7.0.0 | Correction to priority for calling subscriber's link in a voice group/ voice broadcast call | +| CT#31 | 23.067 | 7.0.0 | 0018 | Rel-7 | 7.1.0 | Correction on references to non existing specifications | +| CT#41 | 23.067 | 7.1.0 | 0019 | Rel-8 | 8.0.0 | eMLPP Priority in MAP SRI, PRN and PSI request | +| CT#42 | 23.067 | 8.0.0 | | Rel-8 | 8.0.1 | Copyright Notification updated | +| CT#46 | - | 8.0.1 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | - | 9.0.0 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | - | 10.0.0 | - | Rel-11 | 11.0.0 | Update to Rel-11 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23078/0073ee258067e591778333101c5d2edb_img.jpg b/marked/Rel-11/23_series/23078/0073ee258067e591778333101c5d2edb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0135fe6c8f462532d48860eb78215a75fcf95ea --- /dev/null +++ b/marked/Rel-11/23_series/23078/0073ee258067e591778333101c5d2edb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ed283ea9fe00582726d508504b7c48122d0823c32f7528485270819f3841b94 +size 109410 diff --git a/marked/Rel-11/23_series/23078/013b84b66269966497a082962b189f16_img.jpg b/marked/Rel-11/23_series/23078/013b84b66269966497a082962b189f16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e5440fd56bc0ca8a2f9d540269b5eda2ba9d5c6 --- /dev/null +++ b/marked/Rel-11/23_series/23078/013b84b66269966497a082962b189f16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75dae41d63f04e2b6a8484abbd64bdbfca9a85572c31198fcc6b6ba27efd5255 +size 100355 diff --git a/marked/Rel-11/23_series/23078/050e99bf626cb208bd2646b0e0b80708_img.jpg b/marked/Rel-11/23_series/23078/050e99bf626cb208bd2646b0e0b80708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5bbf1d06074415e81edb7278de21e09892c9e14 --- /dev/null +++ b/marked/Rel-11/23_series/23078/050e99bf626cb208bd2646b0e0b80708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98802b091a9a17be4a9e7bbba7c6ff8216fd8370af5578ffb805a7890b00e609 +size 130412 diff --git a/marked/Rel-11/23_series/23078/057e0fadbc74743547d314f6fd0ff686_img.jpg b/marked/Rel-11/23_series/23078/057e0fadbc74743547d314f6fd0ff686_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e5bea1520a32c4248358432b3e5a42dd1c8f77a --- /dev/null +++ b/marked/Rel-11/23_series/23078/057e0fadbc74743547d314f6fd0ff686_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7612e0605223612bb1f76c620a1bca6e73cc50868406e9ec75bd60b695eec344 +size 30526 diff --git a/marked/Rel-11/23_series/23078/0b13c8043bf78842cd0980770eb9d60b_img.jpg b/marked/Rel-11/23_series/23078/0b13c8043bf78842cd0980770eb9d60b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddc3d8225229f240610220aef846ce3fc13f3eef --- /dev/null +++ b/marked/Rel-11/23_series/23078/0b13c8043bf78842cd0980770eb9d60b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5c796cea8e24704cf619f328a4933e7c7e5c2c4b5f4ec885a4a38c5ecb2e195 +size 143076 diff --git a/marked/Rel-11/23_series/23078/0bb475bf99a4fb0082c265e9fcfd3433_img.jpg b/marked/Rel-11/23_series/23078/0bb475bf99a4fb0082c265e9fcfd3433_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a7dbf3e4c57d6eec6447104035ae126208a6062 --- /dev/null +++ b/marked/Rel-11/23_series/23078/0bb475bf99a4fb0082c265e9fcfd3433_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c77efd774ed491c6c8136288af16cefc36ae23c38ff1b5d46386362bbd20b79 +size 133264 diff --git a/marked/Rel-11/23_series/23078/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/Rel-11/23_series/23078/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..260cddfe5cfdae82dc3379313f3c3f92c19df222 --- /dev/null +++ b/marked/Rel-11/23_series/23078/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3602dcbcbaf6bb4827a552c629cdceec49e899865a645133f76662cb83f8ba77 +size 47101 diff --git a/marked/Rel-11/23_series/23078/12b3831f83d090aaff6aecb06354f250_img.jpg b/marked/Rel-11/23_series/23078/12b3831f83d090aaff6aecb06354f250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66487cb2d371cd4f3544cc8e579acff5979c9625 --- /dev/null +++ b/marked/Rel-11/23_series/23078/12b3831f83d090aaff6aecb06354f250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6e7da6c08ef38b548c89388f94da265fe93d0b9271633a3aa09a6a629c116ea +size 126323 diff --git a/marked/Rel-11/23_series/23078/16d37be41edfc66b146ef046b128beb1_img.jpg b/marked/Rel-11/23_series/23078/16d37be41edfc66b146ef046b128beb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a3020f21a4dd2756dab85b4956aff759eb1bfa9 --- /dev/null +++ b/marked/Rel-11/23_series/23078/16d37be41edfc66b146ef046b128beb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:631faba57a18bff0c3f602663902728b26d190434f1b08b16c52867b971e3cf5 +size 137392 diff --git a/marked/Rel-11/23_series/23078/1ad74e556b36766c9338db8124ad80cd_img.jpg b/marked/Rel-11/23_series/23078/1ad74e556b36766c9338db8124ad80cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a474529a66ba9c5dd3f7e0d8a7e6bb98ac05b96 --- /dev/null +++ b/marked/Rel-11/23_series/23078/1ad74e556b36766c9338db8124ad80cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10646b71140c72ea28b8833d38cf8032563cbbf90dabe471ff38c254515d0ceb +size 24499 diff --git a/marked/Rel-11/23_series/23078/1b39bec1cdf850bbcbbd693f5c36dbf4_img.jpg b/marked/Rel-11/23_series/23078/1b39bec1cdf850bbcbbd693f5c36dbf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70fa6d328fe6c0e5c8057cc7bcb080a07edd1913 --- /dev/null +++ b/marked/Rel-11/23_series/23078/1b39bec1cdf850bbcbbd693f5c36dbf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecf4ce87c2250339c21ef7deacbb8bae0a5bf4fb13045df312f99910f2c6e0f0 +size 37082 diff --git a/marked/Rel-11/23_series/23078/1c877fb0cc57a813ade0008fa01971f0_img.jpg b/marked/Rel-11/23_series/23078/1c877fb0cc57a813ade0008fa01971f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b09ca300b292bce9dbc8908f50f95774c4e30ca --- /dev/null +++ b/marked/Rel-11/23_series/23078/1c877fb0cc57a813ade0008fa01971f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3ab46e98cc613e314f34a0c84b4f3cb97a39502bb238df1f29ba0ec0cd72d12 +size 123454 diff --git a/marked/Rel-11/23_series/23078/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg b/marked/Rel-11/23_series/23078/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70b2936db31085e4863270e812013784491b7d15 --- /dev/null +++ b/marked/Rel-11/23_series/23078/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef852870b84fccef67bf2fb76d694b6fa10b5c82ba9baf168c1a7a90d7fc39f7 +size 89770 diff --git a/marked/Rel-11/23_series/23078/20279ab9a6371e79466939c3e2815089_img.jpg b/marked/Rel-11/23_series/23078/20279ab9a6371e79466939c3e2815089_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..057daefe585bebbee63265b78fdb8ae1bdb4bd77 --- /dev/null +++ b/marked/Rel-11/23_series/23078/20279ab9a6371e79466939c3e2815089_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b06f99f95a57168f894409e8d5e6eb8752d409c47ce1d7d1e5f44322aa5ff042 +size 127706 diff --git a/marked/Rel-11/23_series/23078/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/Rel-11/23_series/23078/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36ab1bde04be16101288a64f5335483857d9b3ba --- /dev/null +++ b/marked/Rel-11/23_series/23078/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b1365f1bd8bbae1a530a954e55831a357e1275deea85cd54d4ab4df35e6d7d8 +size 66434 diff --git a/marked/Rel-11/23_series/23078/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/Rel-11/23_series/23078/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..792c16c6dfacf9de072e4599db25670a458b84d0 --- /dev/null +++ b/marked/Rel-11/23_series/23078/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6366af6a3ebd7455d2da3c4554ad1bfcbbb8c9966ae5275d0ede616a19cf1883 +size 114104 diff --git a/marked/Rel-11/23_series/23078/27fc71a666ffdf8fdc4ce84d9d585008_img.jpg b/marked/Rel-11/23_series/23078/27fc71a666ffdf8fdc4ce84d9d585008_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5786e2f5a24f20719ca34702160704b31e5ee853 --- /dev/null +++ b/marked/Rel-11/23_series/23078/27fc71a666ffdf8fdc4ce84d9d585008_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f4d7976df6513f0a5bf394b9bc164a159fa7967e6c1b01c63cfa9336e564384 +size 28231 diff --git a/marked/Rel-11/23_series/23078/29178b001cb4c04e0c5ab60662ce5d80_img.jpg b/marked/Rel-11/23_series/23078/29178b001cb4c04e0c5ab60662ce5d80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31244e389c389112bf0334b2f2073c04d3e183fa --- /dev/null +++ b/marked/Rel-11/23_series/23078/29178b001cb4c04e0c5ab60662ce5d80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c3e83ed1ad14c403ee29e50be9d76b4eb5718e7de753008a7c36fee6963debc +size 131112 diff --git a/marked/Rel-11/23_series/23078/3266235a9ab34f9ae9ca85d937edea26_img.jpg b/marked/Rel-11/23_series/23078/3266235a9ab34f9ae9ca85d937edea26_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc51234b06445f9d0594658af6dbf6730b221cb2 --- /dev/null +++ b/marked/Rel-11/23_series/23078/3266235a9ab34f9ae9ca85d937edea26_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:722a865dbc0728fda8ad8220ba95dfce15af855393c876f7a4ae7ff2d437ba83 +size 141509 diff --git a/marked/Rel-11/23_series/23078/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/23_series/23078/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b8cf0dd1f4d4d0aa66361f41290fa639beb6118 --- /dev/null +++ b/marked/Rel-11/23_series/23078/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9093286358d6921077525c44adad59ccf67dfb258c48fba683c8d1c80fc59cfc +size 99289 diff --git a/marked/Rel-11/23_series/23078/3415aece02e272cc4901fec45d2676c4_img.jpg b/marked/Rel-11/23_series/23078/3415aece02e272cc4901fec45d2676c4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1950deaba737bed4e5024e35f66783162108d6e --- /dev/null +++ b/marked/Rel-11/23_series/23078/3415aece02e272cc4901fec45d2676c4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d393db2cf8e92d7e89f0d8a8d9558ba069f68aa99ceb5e97de12948fde78ff36 +size 157512 diff --git a/marked/Rel-11/23_series/23078/35ddc8b19bd31dedba7ba2d696f43bd0_img.jpg b/marked/Rel-11/23_series/23078/35ddc8b19bd31dedba7ba2d696f43bd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d01eeac4250867a721d2e3a9f55e2b0d93f38d99 --- /dev/null +++ b/marked/Rel-11/23_series/23078/35ddc8b19bd31dedba7ba2d696f43bd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:faeb7a59786a90c0d68b343a42c5e513ad609207279926ef0b939a92c4d5fd88 +size 126892 diff --git a/marked/Rel-11/23_series/23078/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-11/23_series/23078/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a28729c9d2563ea69ed0e9bb7a133587a8642f91 --- /dev/null +++ b/marked/Rel-11/23_series/23078/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f7af3e7656f0914ccc67f0955fd324b31cbd1a7da80d4c5730e7a9381a6bf65 +size 81891 diff --git a/marked/Rel-11/23_series/23078/3c586c53df312a3694ee1ad0e7fd0960_img.jpg b/marked/Rel-11/23_series/23078/3c586c53df312a3694ee1ad0e7fd0960_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc6e42d9a25eb4d2aca157ba735a7ea848e65def --- /dev/null +++ b/marked/Rel-11/23_series/23078/3c586c53df312a3694ee1ad0e7fd0960_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9fc64ad8a5314296f9c33aafe2a6b1bc73175b4408856d21543bf57808513e0 +size 113017 diff --git a/marked/Rel-11/23_series/23078/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg b/marked/Rel-11/23_series/23078/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f941b9adceae0e64b29e9016aa1ab258a2ea6f0 --- /dev/null +++ b/marked/Rel-11/23_series/23078/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10ad255f8bb2bce7711d5b83551b59d04c4dcab522a776526ad6a081f0bd258a +size 76058 diff --git a/marked/Rel-11/23_series/23078/45b71f54324c8fd8c2830610b367dced_img.jpg b/marked/Rel-11/23_series/23078/45b71f54324c8fd8c2830610b367dced_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2956e05453a0dd98ca86d375a20d013cfbe9b5bb --- /dev/null +++ b/marked/Rel-11/23_series/23078/45b71f54324c8fd8c2830610b367dced_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a16fbca9330cddfd0b07607b5e7e266a442e9d127ffcceb19b922d3d10164d04 +size 97587 diff --git a/marked/Rel-11/23_series/23078/4753dd817f88f9e8bc58fcce3df36ea6_img.jpg b/marked/Rel-11/23_series/23078/4753dd817f88f9e8bc58fcce3df36ea6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7241e5c071d7ae958c88728efe3762640eb76a7e --- /dev/null +++ b/marked/Rel-11/23_series/23078/4753dd817f88f9e8bc58fcce3df36ea6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96e3fb60df6e51ae6d484ee33945e5c1e04f0f1dad5e51f89ccef8e86c7e907c +size 99247 diff --git a/marked/Rel-11/23_series/23078/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-11/23_series/23078/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..406b4d8c1fe02452867450ac3c75ff1b0a626b0f --- /dev/null +++ b/marked/Rel-11/23_series/23078/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c176c31587fe27ec4eb01e082d0576ccdc48ed397a8ec8fe6e5ca964cc98d7a2 +size 150906 diff --git a/marked/Rel-11/23_series/23078/55a415876cf7b7c2509c0318bb857efa_img.jpg b/marked/Rel-11/23_series/23078/55a415876cf7b7c2509c0318bb857efa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..913c40d7223a92d200a167371f23f7aab6146c4e --- /dev/null +++ b/marked/Rel-11/23_series/23078/55a415876cf7b7c2509c0318bb857efa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23e7c8f5a02309203ee1703244d63afd62323c600eddb8f0590f22b65c4983aa +size 64542 diff --git a/marked/Rel-11/23_series/23078/5635bd67a8ba929382fd61dede8952c7_img.jpg b/marked/Rel-11/23_series/23078/5635bd67a8ba929382fd61dede8952c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b88e66c8e3e46a3ef2a67147f8eeae73c95b4b79 --- /dev/null +++ b/marked/Rel-11/23_series/23078/5635bd67a8ba929382fd61dede8952c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:378f7e7cfc2444923a419daa527d444c1ae85e5309d8e2b4e6eb47e636d87286 +size 60625 diff --git a/marked/Rel-11/23_series/23078/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/23_series/23078/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9ee5587424cf985652e6bc647879f44bb0416aa --- /dev/null +++ b/marked/Rel-11/23_series/23078/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:382a4cc058ae3373ee0617ff95973341bdc2f87e14262d2b685bee0d673cb36f +size 193465 diff --git a/marked/Rel-11/23_series/23078/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-11/23_series/23078/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..734fb072444f42dbb8c3bc8b456b244dee479052 --- /dev/null +++ b/marked/Rel-11/23_series/23078/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27428b4350c852c70204a4842d9cecb62ad07d2042a906ad2edc0fb409d50cf0 +size 179711 diff --git a/marked/Rel-11/23_series/23078/5d819f259411162c4e3371915818ae22_img.jpg b/marked/Rel-11/23_series/23078/5d819f259411162c4e3371915818ae22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afd30bb319414a64cd87747db68524ee84aac57d --- /dev/null +++ b/marked/Rel-11/23_series/23078/5d819f259411162c4e3371915818ae22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:179750334682c21823c5b97932e9c98655c75dfbe9149696dbb8e8b4855c6a47 +size 124801 diff --git a/marked/Rel-11/23_series/23078/603738e78a489658732e33631dd15f17_img.jpg b/marked/Rel-11/23_series/23078/603738e78a489658732e33631dd15f17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..011ad0c1d830f05051a3d702a72395ee97cfd1cd --- /dev/null +++ b/marked/Rel-11/23_series/23078/603738e78a489658732e33631dd15f17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cb0e9b0b049c08778d64b50daa0eb2ee89fb2a16e3bcde2b0ce73c420444a92 +size 99930 diff --git a/marked/Rel-11/23_series/23078/648f8b0b99ad83e654879fbf6e04a384_img.jpg b/marked/Rel-11/23_series/23078/648f8b0b99ad83e654879fbf6e04a384_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb52fe79e56fd5429ee6764a50e462f728c56a49 --- /dev/null +++ b/marked/Rel-11/23_series/23078/648f8b0b99ad83e654879fbf6e04a384_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d4c92c154b41fc8afcabad1c2ffbd32a5894a74c85ee57901ab7e206d882c8c +size 94146 diff --git a/marked/Rel-11/23_series/23078/64c568012a5ac681059e21a8fb8ac616_img.jpg b/marked/Rel-11/23_series/23078/64c568012a5ac681059e21a8fb8ac616_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04b6478ed2139076b822d5f17d2ffee5dd20b857 --- /dev/null +++ b/marked/Rel-11/23_series/23078/64c568012a5ac681059e21a8fb8ac616_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fed3a794edc3faf08278dd7a2b1987c8617cdaf4b4c20fbbc5581a0592b0620 +size 127037 diff --git a/marked/Rel-11/23_series/23078/65dfb5b0cce768997b08d0030d483f76_img.jpg b/marked/Rel-11/23_series/23078/65dfb5b0cce768997b08d0030d483f76_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a41f652d7c7d52a069fa4db564b258b0e693e88 --- /dev/null +++ b/marked/Rel-11/23_series/23078/65dfb5b0cce768997b08d0030d483f76_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fcc0c3fd56e3cb55157e29120a0d78b7ab8baa1fd43cfec673dfb98851628af +size 155713 diff --git a/marked/Rel-11/23_series/23078/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-11/23_series/23078/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..181ee815ff1c5e3a811b66af3a35c9d2ccd395fa --- /dev/null +++ b/marked/Rel-11/23_series/23078/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ae16fed3fb34a56d85380bd43112621824fbd20ed0a226937d60df4aa615d8e +size 139308 diff --git a/marked/Rel-11/23_series/23078/664aee1b67663744929d6a9b6d5377de_img.jpg b/marked/Rel-11/23_series/23078/664aee1b67663744929d6a9b6d5377de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ba48cb421b4e5a3614e28a94866528c96a3195d --- /dev/null +++ b/marked/Rel-11/23_series/23078/664aee1b67663744929d6a9b6d5377de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:883b6feb5c86aa11d895276d99c52a4ba2f3b1a70adc91305e68b618d3cf7dc3 +size 123595 diff --git a/marked/Rel-11/23_series/23078/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/marked/Rel-11/23_series/23078/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a84ae9ab5ca8162dce4bdb4a2c308e5b416caff0 --- /dev/null +++ b/marked/Rel-11/23_series/23078/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e5b98f51253c986714a8b8ce03c942f6275169a618cd6760e57d847fa040cf8 +size 151971 diff --git a/marked/Rel-11/23_series/23078/68d8089266ace7197304b43dcaf5d08e_img.jpg b/marked/Rel-11/23_series/23078/68d8089266ace7197304b43dcaf5d08e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daac2c9af0e63406795bc77820dee2274eb31bbe --- /dev/null +++ b/marked/Rel-11/23_series/23078/68d8089266ace7197304b43dcaf5d08e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d78b6738bb21b1f2419e20333963fbf4bdd4df32c96839027a9541ecc3d76e90 +size 49512 diff --git a/marked/Rel-11/23_series/23078/6ab3a17141dc89ebcbf489fe15919355_img.jpg b/marked/Rel-11/23_series/23078/6ab3a17141dc89ebcbf489fe15919355_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89954ef0b0e7b7f66baddc245b394067192beac8 --- /dev/null +++ b/marked/Rel-11/23_series/23078/6ab3a17141dc89ebcbf489fe15919355_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c8b4ef864465234152108547e39b5574b71a2f0e3dfaf3fab5afd64aba648a9 +size 63312 diff --git a/marked/Rel-11/23_series/23078/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/marked/Rel-11/23_series/23078/6be06b7dc72bb42afcb3465394667c3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0804a5f2ff397e71721f69ae30126223e1c1abfd --- /dev/null +++ b/marked/Rel-11/23_series/23078/6be06b7dc72bb42afcb3465394667c3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:996cfba61bc7c63df0f91224b82208176a2e079c9d190195d3b9ac133837eaaa +size 37892 diff --git a/marked/Rel-11/23_series/23078/6c5c4041e081d25a3f7e13f5fd2a3390_img.jpg b/marked/Rel-11/23_series/23078/6c5c4041e081d25a3f7e13f5fd2a3390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5852c67507c784be47d56d45417a4e6b6f6500d --- /dev/null +++ b/marked/Rel-11/23_series/23078/6c5c4041e081d25a3f7e13f5fd2a3390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7d8973e1ebb6dc10bd913ae762acaa8bffb91e948b4bd7f3efbd5c9bd82ed5e +size 116503 diff --git a/marked/Rel-11/23_series/23078/6de875eb7a49c3352b45075b92e5ea9b_img.jpg b/marked/Rel-11/23_series/23078/6de875eb7a49c3352b45075b92e5ea9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cb3573414bf86b692aa86a98af5e35b1281960b --- /dev/null +++ b/marked/Rel-11/23_series/23078/6de875eb7a49c3352b45075b92e5ea9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19b00150fdbe3980ceaa2832a4a05159f6ef83ab16acb9a95267d80612cdf8eb +size 164346 diff --git a/marked/Rel-11/23_series/23078/72d448a65347c51989171748789c7d4b_img.jpg b/marked/Rel-11/23_series/23078/72d448a65347c51989171748789c7d4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7ed31015b544a195dabbf844146c64c90010ba4 --- /dev/null +++ b/marked/Rel-11/23_series/23078/72d448a65347c51989171748789c7d4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9f3d776ff917ff094501d149cea1cf73bb690ba2b9371b9ca5747969b5aa927 +size 95999 diff --git a/marked/Rel-11/23_series/23078/74b47701fe8a059c632b40e009c57a96_img.jpg b/marked/Rel-11/23_series/23078/74b47701fe8a059c632b40e009c57a96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc371a7a2c73a0a9cacb9e46a631659c3fa7ee3a --- /dev/null +++ b/marked/Rel-11/23_series/23078/74b47701fe8a059c632b40e009c57a96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abac9f8f1ffe7cc843f0ea58b829ba8af8be7e6037144d9a54f7d7aa5af98f9d +size 148004 diff --git a/marked/Rel-11/23_series/23078/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-11/23_series/23078/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58b8a0ec4cb0f0c243abad81ff8d7bf6ebc5ea8d --- /dev/null +++ b/marked/Rel-11/23_series/23078/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9eb9df7ef61bfb19b3cbe932e96b5cf385555176cef297d006f6376586c9011f +size 122847 diff --git a/marked/Rel-11/23_series/23078/7d2489babb3bf789de160fddd90c535b_img.jpg b/marked/Rel-11/23_series/23078/7d2489babb3bf789de160fddd90c535b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..631126b349a07384c2a24816dbb7aa3df5ec9300 --- /dev/null +++ b/marked/Rel-11/23_series/23078/7d2489babb3bf789de160fddd90c535b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3307182faeecec83709b5946549292856a458ec6ba6ac5881ffa4158479f770 +size 132987 diff --git a/marked/Rel-11/23_series/23078/841943891f19fcd045f406339e8d5655_img.jpg b/marked/Rel-11/23_series/23078/841943891f19fcd045f406339e8d5655_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3701e88f2592931023f30eb41ca637b52b155dfa --- /dev/null +++ b/marked/Rel-11/23_series/23078/841943891f19fcd045f406339e8d5655_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f48cb65d37332858c1582a5551399f0c0cd583e079d27e53f7dc95d64b7110c6 +size 124922 diff --git a/marked/Rel-11/23_series/23078/8c05782074bb11421b43f2d5d6799b62_img.jpg b/marked/Rel-11/23_series/23078/8c05782074bb11421b43f2d5d6799b62_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90d01be4c61af7944e668831cc7c5513175f6fb0 --- /dev/null +++ b/marked/Rel-11/23_series/23078/8c05782074bb11421b43f2d5d6799b62_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76ee3a8e9856a46a795450bad1bd1fb90b1261de335b1e9496a08aa33535cb3d +size 129009 diff --git a/marked/Rel-11/23_series/23078/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-11/23_series/23078/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..512397d5f60723eb4c7ae1ea81afdbbb719d1f00 --- /dev/null +++ b/marked/Rel-11/23_series/23078/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf7b222847bd21398f4f11cbc900fe29b2bb4ce5bb66554db9b1973e4fe93fd4 +size 118103 diff --git a/marked/Rel-11/23_series/23078/8d7444ed03f97cc793846fdac8e2ed3a_img.jpg b/marked/Rel-11/23_series/23078/8d7444ed03f97cc793846fdac8e2ed3a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42f6d01b9e7ac49e245a0bd5de94e929680b9d7d --- /dev/null +++ b/marked/Rel-11/23_series/23078/8d7444ed03f97cc793846fdac8e2ed3a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e09077898d70236a8d895f7adf87b396d9030114d3005cc160513d007d6c54a4 +size 123765 diff --git a/marked/Rel-11/23_series/23078/8f78b5d84dca49cf2769440c7942a27d_img.jpg b/marked/Rel-11/23_series/23078/8f78b5d84dca49cf2769440c7942a27d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae66d10f64461efc2a7fa521f555ea256cc514be --- /dev/null +++ b/marked/Rel-11/23_series/23078/8f78b5d84dca49cf2769440c7942a27d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96c277e92a8e29b7b11890755f3e3c93e21e7d72307ec4971ce52190f29414c0 +size 93766 diff --git a/marked/Rel-11/23_series/23078/931bd52904f67b17796a38b47af51e30_img.jpg b/marked/Rel-11/23_series/23078/931bd52904f67b17796a38b47af51e30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8744480deaf5486357aa883c83d0f7aee4c116b0 --- /dev/null +++ b/marked/Rel-11/23_series/23078/931bd52904f67b17796a38b47af51e30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d41365e977cf5d30276fec300865441e9498102f498203d07e0de2f48ca7ab2 +size 126468 diff --git a/marked/Rel-11/23_series/23078/933a097f8f087e901730352801e25555_img.jpg b/marked/Rel-11/23_series/23078/933a097f8f087e901730352801e25555_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a4c0b637259c35960ef90a2198b42b26dfb4ef5 --- /dev/null +++ b/marked/Rel-11/23_series/23078/933a097f8f087e901730352801e25555_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc192cb14c4b0b4348c4247af5ee230489d329c545acac4881e6e1a7e66adf0a +size 135820 diff --git a/marked/Rel-11/23_series/23078/93bd00a00fa28558486f0664550699b1_img.jpg b/marked/Rel-11/23_series/23078/93bd00a00fa28558486f0664550699b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d16b7fe79033a01a4d139bf882aa9edf908fdfbf --- /dev/null +++ b/marked/Rel-11/23_series/23078/93bd00a00fa28558486f0664550699b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd0fb7b1bf2d67cae2a1a8692056fdeac1386ac46fc3ff89351b3bcd74636565 +size 115191 diff --git a/marked/Rel-11/23_series/23078/945d192fc4d644bec26d9bb4f52465e8_img.jpg b/marked/Rel-11/23_series/23078/945d192fc4d644bec26d9bb4f52465e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..483db1c8044b7f984471578d748c22b02f102280 --- /dev/null +++ b/marked/Rel-11/23_series/23078/945d192fc4d644bec26d9bb4f52465e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcf2d4a59f54b95e02818d321ec657e27b0b203cc4ed2bc753c9357a06b9c299 +size 78864 diff --git a/marked/Rel-11/23_series/23078/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Rel-11/23_series/23078/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8183ddea37f736e5c3f85818ced8f7cadd76211 --- /dev/null +++ b/marked/Rel-11/23_series/23078/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39b74386620069a1088405e9ccdc3b2f60166246ac83c3357cdbfcb27340c2ef +size 151364 diff --git a/marked/Rel-11/23_series/23078/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-11/23_series/23078/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07194a1316aa085a8d2785816f89b515af527f4f --- /dev/null +++ b/marked/Rel-11/23_series/23078/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8287b365c08507de3332ca2b540fc04897418f76aaa13a3c3a7f1697d247c23e +size 125986 diff --git a/marked/Rel-11/23_series/23078/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-11/23_series/23078/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b69cfb080b96d8ffe1b617b8651b01f5c2941ce --- /dev/null +++ b/marked/Rel-11/23_series/23078/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8892d415be5c8cb56d848671eed1094efe16ac4812a6337c23a5b25507d2b862 +size 65550 diff --git a/marked/Rel-11/23_series/23078/a78d57764cafb6417c6967b92aafc57a_img.jpg b/marked/Rel-11/23_series/23078/a78d57764cafb6417c6967b92aafc57a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab55c7e003b5c00372ea61ba95a9f5738323b963 --- /dev/null +++ b/marked/Rel-11/23_series/23078/a78d57764cafb6417c6967b92aafc57a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f4bf8398f2a43278f1842366e9c489616769de70123243470a955ea4674ad85 +size 145450 diff --git a/marked/Rel-11/23_series/23078/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-11/23_series/23078/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9675cb53efffde3bcced8cd58a948419f6a2336a --- /dev/null +++ b/marked/Rel-11/23_series/23078/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94752b63e86a74dbf38ae27bd6ddadcede75d47fbed7f6796dbd8b63219b445b +size 85829 diff --git a/marked/Rel-11/23_series/23078/adb6959da20fc632728dccd25cf75dc3_img.jpg b/marked/Rel-11/23_series/23078/adb6959da20fc632728dccd25cf75dc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..699a3de0acfb0dd0bf5028f7399afdf5562ec535 --- /dev/null +++ b/marked/Rel-11/23_series/23078/adb6959da20fc632728dccd25cf75dc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37f0b246b8a34f0265680fca03982b4d282eb3e60e3a9b52c70cc4e685049a17 +size 147866 diff --git a/marked/Rel-11/23_series/23078/b2c7dd553083e499d689a596043199fe_img.jpg b/marked/Rel-11/23_series/23078/b2c7dd553083e499d689a596043199fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4ce6d62fda687e7c8ac8914598cb656f975e99d --- /dev/null +++ b/marked/Rel-11/23_series/23078/b2c7dd553083e499d689a596043199fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bab60161c6818ec07b55388eb391bd7317e0bd88c66ebc1496228577c4ae747 +size 105532 diff --git a/marked/Rel-11/23_series/23078/b2f6158e74f297659bf41c5939b2c1e0_img.jpg b/marked/Rel-11/23_series/23078/b2f6158e74f297659bf41c5939b2c1e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79fe09df65202e379c32f4afbe3f10342f7fb255 --- /dev/null +++ b/marked/Rel-11/23_series/23078/b2f6158e74f297659bf41c5939b2c1e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bf685e4bfb39a6b646f34300a6536d6f0d6e0e239c0514f55de2dc152cdd68f +size 155012 diff --git a/marked/Rel-11/23_series/23078/b6b9a551526c85203f6b1a4664d490ab_img.jpg b/marked/Rel-11/23_series/23078/b6b9a551526c85203f6b1a4664d490ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c629bf40cecebaf7d022df0e928517abce2d7edc --- /dev/null +++ b/marked/Rel-11/23_series/23078/b6b9a551526c85203f6b1a4664d490ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9b68de04f34429573d4faaf7d31d3e938cd7de9cd616981f5ffc61025011242 +size 25264 diff --git a/marked/Rel-11/23_series/23078/b6f6f51bf96aef85ffe1dcd9d57f398b_img.jpg b/marked/Rel-11/23_series/23078/b6f6f51bf96aef85ffe1dcd9d57f398b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20d4e7d96f20420e5d24bb626ba543effcf54f43 --- /dev/null +++ b/marked/Rel-11/23_series/23078/b6f6f51bf96aef85ffe1dcd9d57f398b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d69642c1875303f469b03c5e998bc79a5b01856bbc401dbd89cc5abe968af4fc +size 154749 diff --git a/marked/Rel-11/23_series/23078/b7321a97441b64ca21fa3647d44cfeb0_img.jpg b/marked/Rel-11/23_series/23078/b7321a97441b64ca21fa3647d44cfeb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b86a3fc3203b50ce8ce11e891535db1571b9f83d --- /dev/null +++ b/marked/Rel-11/23_series/23078/b7321a97441b64ca21fa3647d44cfeb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2002a8f21847398642403b249f1247b27e1c39dfc9c5d015aa80854fd7129b5e +size 89700 diff --git a/marked/Rel-11/23_series/23078/b7ad33d883b9848a765e0abcc9ddc938_img.jpg b/marked/Rel-11/23_series/23078/b7ad33d883b9848a765e0abcc9ddc938_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa486e9440dad06bdd29198a53425e3810341336 --- /dev/null +++ b/marked/Rel-11/23_series/23078/b7ad33d883b9848a765e0abcc9ddc938_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52c93270334f971099052b7b7b311346fc510ff7b211fe8310d59e47bcadc386 +size 88055 diff --git a/marked/Rel-11/23_series/23078/bb05ab992ddf5a3b73266ddac3d4817e_img.jpg b/marked/Rel-11/23_series/23078/bb05ab992ddf5a3b73266ddac3d4817e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc87ba731664fa6986ee327a351ee52dd70078de --- /dev/null +++ b/marked/Rel-11/23_series/23078/bb05ab992ddf5a3b73266ddac3d4817e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:657971ed4a0e0f91aa3d7b0cec40640316f2a9acee403e8dee29d33654416b91 +size 102355 diff --git a/marked/Rel-11/23_series/23078/bf9abec3605f1a8d00ae6524a9af02ed_img.jpg b/marked/Rel-11/23_series/23078/bf9abec3605f1a8d00ae6524a9af02ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..717ddc078fc4b6b4eca3fc4c09343f01f9645762 --- /dev/null +++ b/marked/Rel-11/23_series/23078/bf9abec3605f1a8d00ae6524a9af02ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e75467d0c73c8391cdf0dbe1ba2a8843b07e570532c23e81368ec9c3ebf2db3 +size 129447 diff --git a/marked/Rel-11/23_series/23078/c6c25a5d67fcb6d05140189ce16969b6_img.jpg b/marked/Rel-11/23_series/23078/c6c25a5d67fcb6d05140189ce16969b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..039ba1ea4c93c68f5caa99b76ef2064ca224d133 --- /dev/null +++ b/marked/Rel-11/23_series/23078/c6c25a5d67fcb6d05140189ce16969b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f152d5f274c14af8443170186eb63da4da943bfa84fc7a431321567d3c33f417 +size 149328 diff --git a/marked/Rel-11/23_series/23078/c94fdc8aee435b1f4ed6917e28b1db5c_img.jpg b/marked/Rel-11/23_series/23078/c94fdc8aee435b1f4ed6917e28b1db5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12475e883e35c3b4be79be9d9017626a7a5d608c --- /dev/null +++ b/marked/Rel-11/23_series/23078/c94fdc8aee435b1f4ed6917e28b1db5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e16b5e00041faaaa64114f0d041b4554400490cda91021a65574c302376e02e +size 108150 diff --git a/marked/Rel-11/23_series/23078/cf7af5b6b161907424726dae95ab477f_img.jpg b/marked/Rel-11/23_series/23078/cf7af5b6b161907424726dae95ab477f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..569a4f2889cc4b0feadace306ac2b9b749a43c37 --- /dev/null +++ b/marked/Rel-11/23_series/23078/cf7af5b6b161907424726dae95ab477f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e5990074a0794ba392bc69060385a385c7f5723c5ea55c8aeebfd7c4eea0642 +size 26431 diff --git a/marked/Rel-11/23_series/23078/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-11/23_series/23078/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c56afaf3dc1c1b7392175b3e47ab14885635ae1 --- /dev/null +++ b/marked/Rel-11/23_series/23078/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91335e82c448439f38e190efa841f4ab3d161c953a6e48576c26823e44969df7 +size 132669 diff --git a/marked/Rel-11/23_series/23078/d1aa8db844a6bb8519d74e48d1cf5343_img.jpg b/marked/Rel-11/23_series/23078/d1aa8db844a6bb8519d74e48d1cf5343_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dbead73129b76e846fd5dc3d8821c3a9cec3d76 --- /dev/null +++ b/marked/Rel-11/23_series/23078/d1aa8db844a6bb8519d74e48d1cf5343_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a84236ca57d6fc4eac4b35cbd0497b8e2bb8e1875417d1b49ecc3ffd4394e20b +size 148876 diff --git a/marked/Rel-11/23_series/23078/d2afc712b2091264729f5caa5e84710d_img.jpg b/marked/Rel-11/23_series/23078/d2afc712b2091264729f5caa5e84710d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19d07153bcae78ea0949a4a8ac910d3bb8e5b97b --- /dev/null +++ b/marked/Rel-11/23_series/23078/d2afc712b2091264729f5caa5e84710d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d42c1084d94303be6192df9b094fe66f5abbdce97a3d6bfcb37df5ed788f57eb +size 108872 diff --git a/marked/Rel-11/23_series/23078/da90447206621f137780272a2bf807a4_img.jpg b/marked/Rel-11/23_series/23078/da90447206621f137780272a2bf807a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8dafe0451f079ef04e303fb0b3350e1c98b6330 --- /dev/null +++ b/marked/Rel-11/23_series/23078/da90447206621f137780272a2bf807a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4159b6e592def4c06c528d7f979167fb4eeee26904dd378245b65f554709c499 +size 47379 diff --git a/marked/Rel-11/23_series/23078/dad4e3b63cbcfc60f981c4c771bc9881_img.jpg b/marked/Rel-11/23_series/23078/dad4e3b63cbcfc60f981c4c771bc9881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..065fee62ddef6700db0fb19b6dd6c0557793c348 --- /dev/null +++ b/marked/Rel-11/23_series/23078/dad4e3b63cbcfc60f981c4c771bc9881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bb8610f685fa38e7cdf961bf8769dd3f12351b64063ef09d3a3a455e579d1b0 +size 27327 diff --git a/marked/Rel-11/23_series/23078/dbe8bef1723acb3e03e8616be4faf939_img.jpg b/marked/Rel-11/23_series/23078/dbe8bef1723acb3e03e8616be4faf939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a93b5a9258afd208ad937da503e3668e41ed698f --- /dev/null +++ b/marked/Rel-11/23_series/23078/dbe8bef1723acb3e03e8616be4faf939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d04f2324b8a6b2b05c9144c7c70afaa57d4be7434c61026a1bcf249e5c32b3c0 +size 118920 diff --git a/marked/Rel-11/23_series/23078/df935fc9efbd024af4ba77e46bb0bb19_img.jpg b/marked/Rel-11/23_series/23078/df935fc9efbd024af4ba77e46bb0bb19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d0d8b816bd51664c9082af5510ae831536a2c54 --- /dev/null +++ b/marked/Rel-11/23_series/23078/df935fc9efbd024af4ba77e46bb0bb19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:502f1205c3feae281bf82f383f379ed27f5009d447b1aaeb6c8970983222a8ce +size 21523 diff --git a/marked/Rel-11/23_series/23078/dfd09f348b50c9255f3cfe67985db9bc_img.jpg b/marked/Rel-11/23_series/23078/dfd09f348b50c9255f3cfe67985db9bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..472f35d67002fef96b8a4908d3309f29af22008f --- /dev/null +++ b/marked/Rel-11/23_series/23078/dfd09f348b50c9255f3cfe67985db9bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbb47eecf07ed3b2b986d31efd514109a3234f84b7f2b5772257360f7b28662f +size 94344 diff --git a/marked/Rel-11/23_series/23078/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-11/23_series/23078/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..070386a15ed1f1894ac8a892b15befd31786c225 --- /dev/null +++ b/marked/Rel-11/23_series/23078/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f648670a14f15bf0af41d7d933d748103f96022769164e8bf1d21eedd6dfa4b +size 122545 diff --git a/marked/Rel-11/23_series/23078/e4b6ed98fad76b79cb9f85783e13086a_img.jpg b/marked/Rel-11/23_series/23078/e4b6ed98fad76b79cb9f85783e13086a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24f654b2de8ef4dd49a50bb2257265b8e22d7500 --- /dev/null +++ b/marked/Rel-11/23_series/23078/e4b6ed98fad76b79cb9f85783e13086a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41c45dd19ac964ab627205eb5e27c56b450d2dcfb0ff695570beeefdbe99ea8f +size 97794 diff --git a/marked/Rel-11/23_series/23078/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg b/marked/Rel-11/23_series/23078/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2afbed423b044f066cb29afbad8708f6887eb756 --- /dev/null +++ b/marked/Rel-11/23_series/23078/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86085bb32102e9ea632cf5ffb2dcc1a616ed94885eaf4228c70da7adf48d1f5d +size 95381 diff --git a/marked/Rel-11/23_series/23078/ecc70c8f5fc197f5adbc582a65f4092e_img.jpg b/marked/Rel-11/23_series/23078/ecc70c8f5fc197f5adbc582a65f4092e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b53b7717a4465553149511cb715ce5a3f8b7a0c4 --- /dev/null +++ b/marked/Rel-11/23_series/23078/ecc70c8f5fc197f5adbc582a65f4092e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9a3617f3fb65335e76c4eb8b7cdca68a8332893594b2cbb0ec468518c59061e +size 141734 diff --git a/marked/Rel-11/23_series/23078/f1b85c71870212806267cd518f360784_img.jpg b/marked/Rel-11/23_series/23078/f1b85c71870212806267cd518f360784_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..807988ef76bad0dbbda985244a95fdd3081f209c --- /dev/null +++ b/marked/Rel-11/23_series/23078/f1b85c71870212806267cd518f360784_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5df89ee44ab8dcf94302625ddaf2f8764ccf5733c12d4e632a8abed28de06315 +size 127713 diff --git a/marked/Rel-11/23_series/23078/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Rel-11/23_series/23078/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9a9e09d1afc80809dbed93af243780ebbc46c73 --- /dev/null +++ b/marked/Rel-11/23_series/23078/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7aff524db1f1371ec90ed5ab5cb075a04f559a71f54f74925253b4d7f150b89f +size 151815 diff --git a/marked/Rel-11/23_series/23078/f814714d4415807ccec0645e664397e6_img.jpg b/marked/Rel-11/23_series/23078/f814714d4415807ccec0645e664397e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ff9cabf0ddad1f8c450b4582bb2dd197246f769 --- /dev/null +++ b/marked/Rel-11/23_series/23078/f814714d4415807ccec0645e664397e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25703e1ef1da05e1ff89640dfb2bfce2efe3683d0a1b3cf588f238d96b2a9640 +size 124864 diff --git a/marked/Rel-11/23_series/23078/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg b/marked/Rel-11/23_series/23078/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fa1a1ebd8b6339ef952ced3ee147e3c5afec36c --- /dev/null +++ b/marked/Rel-11/23_series/23078/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8c7b158ed2064c32fa8548ce2dd4e9afb6abcb7e6e829a4398ba84d5d4f080f +size 95616 diff --git a/marked/Rel-11/23_series/23078/fb0319c4dcc4ab3fe727d783a67a355a_img.jpg b/marked/Rel-11/23_series/23078/fb0319c4dcc4ab3fe727d783a67a355a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c46fcf0ad8ef10c0aa50b7f9ee4e7ac1fa2e364 --- /dev/null +++ b/marked/Rel-11/23_series/23078/fb0319c4dcc4ab3fe727d783a67a355a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00b7e1efa31af357cc29b9801b0c1fdd2c4d08fb69c38e3da0459a541e39f3ea +size 190741 diff --git a/marked/Rel-11/23_series/23078/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-11/23_series/23078/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39e8c469c382010e366b4a0506a1938a4d5adef8 --- /dev/null +++ b/marked/Rel-11/23_series/23078/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2257f67ea64f8d32711bf74e8970fa8c25a80dbe6b7769ff8979776a2475c4f1 +size 151761 diff --git a/marked/Rel-11/23_series/23078/fdc14f5fb012540451a6e7d2f890062f_img.jpg b/marked/Rel-11/23_series/23078/fdc14f5fb012540451a6e7d2f890062f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df3b82f4ffd6009ebfc7031b636d932c660a1f05 --- /dev/null +++ b/marked/Rel-11/23_series/23078/fdc14f5fb012540451a6e7d2f890062f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34f92745dc1cb604b2dd844c8d33c100fc2c0a3c68c216815c1edb63509ca266 +size 122284 diff --git a/marked/Rel-11/23_series/23082/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-11/23_series/23082/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ef14c502de8187283502322c81a871bd90e001f --- /dev/null +++ b/marked/Rel-11/23_series/23082/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a09f178e8fef1e0028bfcb95ec921e9fa628a64b70dab05a2e4a2ea5ddcc2d13 +size 35439 diff --git a/marked/Rel-11/23_series/23082/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-11/23_series/23082/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fef73c79b3135d68a5438a53a60ca75a5a3dc9c7 --- /dev/null +++ b/marked/Rel-11/23_series/23082/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:402c23114acb6b9b2e966b45fdf3d9cb2c38abaa95c151e3cf8367d3296b694d +size 39433 diff --git a/marked/Rel-11/23_series/23082/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-11/23_series/23082/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..581ba4290c6368ca675230e1200a5ae7a016dcc0 --- /dev/null +++ b/marked/Rel-11/23_series/23082/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c91f135d7c6924296084ee6f47b921b1fda61cd124e8953625281b06c503088 +size 93170 diff --git a/marked/Rel-11/23_series/23082/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-11/23_series/23082/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23208adf3b38cc915a2d012c7ae33f7c0f23da79 --- /dev/null +++ b/marked/Rel-11/23_series/23082/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25cd988aab49e573c44979987714f299bdaed10454e94af14004c15f4a9dc5fa +size 75813 diff --git a/marked/Rel-11/23_series/23082/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/23_series/23082/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3bad654c61d01302ddcc1a0200731fdb5516f8a --- /dev/null +++ b/marked/Rel-11/23_series/23082/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7599d1fb3be1971e5edf247d922dd0fb637d2b4cc7ed1371fb49aae7515a3c60 +size 112878 diff --git a/marked/Rel-11/23_series/23082/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/Rel-11/23_series/23082/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd2b05b5651eea08c8d8ebcdd013eb3c8bacddea --- /dev/null +++ b/marked/Rel-11/23_series/23082/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e358f94079514261d4821712eab69e5e866dcf1c907550eefeeb4f112d4accc +size 74349 diff --git a/marked/Rel-11/23_series/23082/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/Rel-11/23_series/23082/1b893df61c2b73b7a85e65fc1f58e203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fa8ae3330b7224aead214e7af71ac731ac311e9 --- /dev/null +++ b/marked/Rel-11/23_series/23082/1b893df61c2b73b7a85e65fc1f58e203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a4fffbfce3cb3ef34ed47e530d2653bceb9efeebca643911042dda3027d92df +size 52341 diff --git a/marked/Rel-11/23_series/23082/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Rel-11/23_series/23082/1ce027dfd26183da52137cf990213724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d58678f1a7320d84601bc80b43dce935993c415 --- /dev/null +++ b/marked/Rel-11/23_series/23082/1ce027dfd26183da52137cf990213724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3047ff2765edb7a1b4143ed0722b96eafcfbe13f0061aab70f3d6709acea5610 +size 33656 diff --git a/marked/Rel-11/23_series/23082/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg b/marked/Rel-11/23_series/23082/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2b9d0c1ddbf2ebf0bce65ef87927ea08a796a24 --- /dev/null +++ b/marked/Rel-11/23_series/23082/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96869cf806d5ef6b848aafced9ec108f239acaef1f6eba2e7141faafedaa78a2 +size 53898 diff --git a/marked/Rel-11/23_series/23082/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/23_series/23082/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b54b1901052a93ae674f03f91fa1e3e7508cb32 --- /dev/null +++ b/marked/Rel-11/23_series/23082/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:186d6b178afd837474d8f22d64dc9a30363feb46a45e89afc048e40eb3f6fd15 +size 91467 diff --git a/marked/Rel-11/23_series/23082/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-11/23_series/23082/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a460e57be4e1c523be7abf3371f6903a349148e9 --- /dev/null +++ b/marked/Rel-11/23_series/23082/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbb691671b92852db5783e42e63cc443dfed0130281af882d822abc484f1cba9 +size 42924 diff --git a/marked/Rel-11/23_series/23082/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/23_series/23082/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7fdb40df11c06eee737901644ff19ff83992f72 --- /dev/null +++ b/marked/Rel-11/23_series/23082/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4660e6027facbca872ad8900ade933d6d5cac2b4b28deba731fd2d3efe58c765 +size 110026 diff --git a/marked/Rel-11/23_series/23082/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-11/23_series/23082/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f3165380dc17ac681860aff9c12207ee69e64dd --- /dev/null +++ b/marked/Rel-11/23_series/23082/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7ebb5f35817733af1976eb7afa78434887053a72b436c57bbf45248a93c1140 +size 91790 diff --git a/marked/Rel-11/23_series/23082/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-11/23_series/23082/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8ba9bad5e2d7f8afc0f0328444ab1299cd8796d --- /dev/null +++ b/marked/Rel-11/23_series/23082/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ca70bc36965feac205b08105e720db74d78e9aa1cc2ae16272c61ae587753dd +size 95087 diff --git a/marked/Rel-11/23_series/23082/31ef15d175af5babdbf4d2fbac884c1b_img.jpg b/marked/Rel-11/23_series/23082/31ef15d175af5babdbf4d2fbac884c1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..396551dd7f1eacb92f6b0828114a2d5893fd34b6 --- /dev/null +++ b/marked/Rel-11/23_series/23082/31ef15d175af5babdbf4d2fbac884c1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a9a3f928dd806135ab89c41b6dea7789b8cf1d0011c5ddd07728f18fffde8ae +size 50363 diff --git a/marked/Rel-11/23_series/23082/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/23_series/23082/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8d2ac881519cf2d932bb760b750f5fdb8ed42c4 --- /dev/null +++ b/marked/Rel-11/23_series/23082/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b1292029efea3febce3f59e0492fe9d49be69ecf2a7690ddb4bc09ebd3e2d05 +size 263317 diff --git a/marked/Rel-11/23_series/23082/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-11/23_series/23082/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63c7610453445e3a19c981f4f9bab0e6930ca3dd --- /dev/null +++ b/marked/Rel-11/23_series/23082/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cbd9620b9b09b9dea919e48aef0ae21f294ae232d944c42f3ff565b2408a87e +size 94460 diff --git a/marked/Rel-11/23_series/23082/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-11/23_series/23082/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8655c372551524cbe83e51ec1cfe45750f3d7966 --- /dev/null +++ b/marked/Rel-11/23_series/23082/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6227a1cb9a33caa49137161c228074b7706da4c3f70673aa03b38bd1866cb385 +size 36415 diff --git a/marked/Rel-11/23_series/23082/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-11/23_series/23082/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..742044a54530c9297e7d41e5a73c2a0aa482bbef --- /dev/null +++ b/marked/Rel-11/23_series/23082/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb4c4acdccc79938ba5adbf4dd8c3942410f75046a73af36d2665035d9b18c85 +size 105398 diff --git a/marked/Rel-11/23_series/23082/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/Rel-11/23_series/23082/4f148853ae68fdcf5e43f7604cab457d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09efe073b566558141623ad54024d9c86475e279 --- /dev/null +++ b/marked/Rel-11/23_series/23082/4f148853ae68fdcf5e43f7604cab457d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c17442e3953ad8f40f3c28a17a916492b7a1ec4e90160a1364dfc8c12750cfa +size 29814 diff --git a/marked/Rel-11/23_series/23082/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/23_series/23082/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b58cd69f27ad791beba2e7a40f0e7266cb16d6ef --- /dev/null +++ b/marked/Rel-11/23_series/23082/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74d83f56d0e34d85e4c893286be9a4ca46d66f25e88804c1127cc299598b7b5e +size 149316 diff --git a/marked/Rel-11/23_series/23082/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/23_series/23082/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..859abff84448c051accb7dcd91ef60018886c777 --- /dev/null +++ b/marked/Rel-11/23_series/23082/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:717b1e6172af785f0ffdf1afdc12a66627cc414dbb3879a22ff5ebc62fd9b893 +size 134864 diff --git a/marked/Rel-11/23_series/23082/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-11/23_series/23082/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecd7e2d665196c3ad94554396021f62caaf76b33 --- /dev/null +++ b/marked/Rel-11/23_series/23082/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24099790c64d717813bd17c133a86d99f88970cf55934b4160974d63b267bbbe +size 90301 diff --git a/marked/Rel-11/23_series/23082/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/23_series/23082/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f57e03636eb8a62a44d6bd6e2c20675aea01ce6 --- /dev/null +++ b/marked/Rel-11/23_series/23082/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6035db6a5b18b3d3308ecd31520bf4c90419af20ce064323e460be34b73e6a61 +size 33221 diff --git a/marked/Rel-11/23_series/23082/64544fbada794f3cdf4f78f5d83613e4_img.jpg b/marked/Rel-11/23_series/23082/64544fbada794f3cdf4f78f5d83613e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e203f7f81b6d5c7b0073c0e703103031df51826 --- /dev/null +++ b/marked/Rel-11/23_series/23082/64544fbada794f3cdf4f78f5d83613e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d20a72ed202b7c84fab9a54c8f282baf8f0acdfcaad680929669518ecd095e43 +size 70962 diff --git a/marked/Rel-11/23_series/23082/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-11/23_series/23082/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5380b42d18025882d8fa72b0a7ae537d0835c08 --- /dev/null +++ b/marked/Rel-11/23_series/23082/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26aad01f735550617b8ba0b0ce19fef8e7b9ec60fc2a3bca24c7a1bf9d59c0f7 +size 35747 diff --git a/marked/Rel-11/23_series/23082/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/23_series/23082/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..177f7ff49d3faf2c47261f4eea475739e2af7e08 --- /dev/null +++ b/marked/Rel-11/23_series/23082/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3fdf37a9df5c04fb3586f0e0bea627c96fea745aeaef37313997f3c553f68ef +size 109709 diff --git a/marked/Rel-11/23_series/23082/677bcb564410628b8b966ad87b394888_img.jpg b/marked/Rel-11/23_series/23082/677bcb564410628b8b966ad87b394888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dacd82f593af5cd9a07413978267c754268e472b --- /dev/null +++ b/marked/Rel-11/23_series/23082/677bcb564410628b8b966ad87b394888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:866f10b6f0d8883af3d80bb960f42358f9f75176f9f82025ad38dc1f1df1f72a +size 35827 diff --git a/marked/Rel-11/23_series/23082/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-11/23_series/23082/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a756259b733fa9dc069f6fd62e7af3e194328ac0 --- /dev/null +++ b/marked/Rel-11/23_series/23082/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42f595c83d9ab19bbae97d29313fcfb4629883c6b09ffb52ab178aa259fa6232 +size 110710 diff --git a/marked/Rel-11/23_series/23082/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/23_series/23082/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..262d046ede022a33e3fa0e7faf9dae9e2f7356d2 --- /dev/null +++ b/marked/Rel-11/23_series/23082/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02eb673143e6b9c41c658a04f283c49d1626e42feaf51fc93364f02799f5328e +size 103840 diff --git a/marked/Rel-11/23_series/23082/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/marked/Rel-11/23_series/23082/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c9ed4a87f46cac435138e2524a84d11d58b9f24 --- /dev/null +++ b/marked/Rel-11/23_series/23082/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32de7791a92ee6bb1251877ed9eaa382ce91af3fc5bf070d08959a51918c5a6c +size 31653 diff --git a/marked/Rel-11/23_series/23082/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-11/23_series/23082/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ba18e6161c05a6f1fbc743998639cc65f3841e5 --- /dev/null +++ b/marked/Rel-11/23_series/23082/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07e9179f661466fd3421e9fd5e58509ff1d8255947da310e7141591bbc553752 +size 71609 diff --git a/marked/Rel-11/23_series/23082/742a5484e7dd016256ab99921bbd635d_img.jpg b/marked/Rel-11/23_series/23082/742a5484e7dd016256ab99921bbd635d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d73f0b8f37fe90c58aa6035348a67fda31108ba --- /dev/null +++ b/marked/Rel-11/23_series/23082/742a5484e7dd016256ab99921bbd635d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:235ba48fabcd2d73e2c1187a805e04889f0bd5bc5510f5a78c087e5cac5ffa6c +size 116780 diff --git a/marked/Rel-11/23_series/23082/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/23_series/23082/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea75f7bab25a00a776cf5b052a9dd577c7ef313d --- /dev/null +++ b/marked/Rel-11/23_series/23082/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:148124f451112fcab4afd5a93a6eaaca8012d0a2f97a7381c4eecf5097a55df8 +size 91937 diff --git a/marked/Rel-11/23_series/23082/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23082/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3043d7dfef2e77e7bbd45b79a45353b4482a19a7 --- /dev/null +++ b/marked/Rel-11/23_series/23082/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:054f2b744c50cee9049f6c13262a37232fc3af1d59fd39b9b6190d78f93cdf29 +size 96651 diff --git a/marked/Rel-11/23_series/23082/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/23_series/23082/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5503070d67118020ae5c076ddebc3faa0dec90ac --- /dev/null +++ b/marked/Rel-11/23_series/23082/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4798c4f62bf6a07f59df39dada1a2b3f0ad0b82f5ed4cd0ace8287ad7eee2508 +size 121788 diff --git a/marked/Rel-11/23_series/23082/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/23_series/23082/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed9bd5f9a48231affee25f04f2dbe04c621a6fb6 --- /dev/null +++ b/marked/Rel-11/23_series/23082/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7e825e97bf9d7e2331857ae726deb92861b361079a1763fa30780a633f39c2e +size 77510 diff --git a/marked/Rel-11/23_series/23082/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/23_series/23082/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3b13019722307b2f5a8a64dbd1572a03ba9649e --- /dev/null +++ b/marked/Rel-11/23_series/23082/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65c5e6e7b6733aeb858354b9c769a96465a8e4c756b79f82ffcfdfdc2c0318d8 +size 85243 diff --git a/marked/Rel-11/23_series/23082/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-11/23_series/23082/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b00fd134d450d9a266692e752cb079bb602abd7 --- /dev/null +++ b/marked/Rel-11/23_series/23082/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc676f42ab3ee244a5902a8adb66afafc6f559f839ae792de06e623bc862630e +size 114089 diff --git a/marked/Rel-11/23_series/23082/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-11/23_series/23082/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c12dcaf89adb8b27435a7505e839e3d03d8acfd4 --- /dev/null +++ b/marked/Rel-11/23_series/23082/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d64c0e170309299a519ac09cdd2dace49adafc1c5d674ec1270ea8f4977d314b +size 150776 diff --git a/marked/Rel-11/23_series/23082/9e26cd5584f423e1b2155fb341db579f_img.jpg b/marked/Rel-11/23_series/23082/9e26cd5584f423e1b2155fb341db579f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d955ba0cc54c31092c4402e1c07a8a2a93fa6de5 --- /dev/null +++ b/marked/Rel-11/23_series/23082/9e26cd5584f423e1b2155fb341db579f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f88f13f1197da91171b8f35c6f37fe1b3a3d29e146439f68280411c360d681b0 +size 28800 diff --git a/marked/Rel-11/23_series/23082/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/23_series/23082/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2c52cd2ef7594b151f7cf126387bed5d57f73c5 --- /dev/null +++ b/marked/Rel-11/23_series/23082/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c79f557768b90b04f4b3fe1b6b867266c73b00e96643c04005e68389e922ed68 +size 98225 diff --git a/marked/Rel-11/23_series/23082/9ed248b025d766251d58be10b01a1cc0_img.jpg b/marked/Rel-11/23_series/23082/9ed248b025d766251d58be10b01a1cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d763ecbaab1be6fe3b806de8124c5cad163fe83 --- /dev/null +++ b/marked/Rel-11/23_series/23082/9ed248b025d766251d58be10b01a1cc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b8b529f2cc059859c93a51f1591d2321134dbc212d8759d03c3ba5abd7d3e5d +size 32427 diff --git a/marked/Rel-11/23_series/23082/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/23_series/23082/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8aafda134404aaba3ede212d6d9ffb7d13a9521f --- /dev/null +++ b/marked/Rel-11/23_series/23082/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f216f773e0598b23a84e3d4500c58c4990d680bba1210ed9493f16f18c35f5d3 +size 103155 diff --git a/marked/Rel-11/23_series/23082/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-11/23_series/23082/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e149973aea93ccdb771b7163a0e06367586ada1a --- /dev/null +++ b/marked/Rel-11/23_series/23082/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87d3595c770b6b6b46a972e94eea90f625f1988ac14f23840bba59df1434eaff +size 148928 diff --git a/marked/Rel-11/23_series/23082/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/marked/Rel-11/23_series/23082/a1890b9a9b85f13e67ed59bbad623659_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..873cf0d4f5a060cbcc203ec41727b3dafeccc169 --- /dev/null +++ b/marked/Rel-11/23_series/23082/a1890b9a9b85f13e67ed59bbad623659_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c78bd2dde11a3a38e7fe33a06feee321b9e6cf740436c7b59e5c5c85fa8489c +size 27421 diff --git a/marked/Rel-11/23_series/23082/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg b/marked/Rel-11/23_series/23082/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17204942e7f4b501fe6baa2b38f5d3ca9c6099cc --- /dev/null +++ b/marked/Rel-11/23_series/23082/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebd7938a4720cff6f69430ea69d0175324cc9cefc7871e0586a024bbb6f2e9c7 +size 50222 diff --git a/marked/Rel-11/23_series/23082/a4bfa2343d75076b79f7e33d93915e00_img.jpg b/marked/Rel-11/23_series/23082/a4bfa2343d75076b79f7e33d93915e00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89fdc81b4794decc0bf3ca6bd46fb898d9a31e0e --- /dev/null +++ b/marked/Rel-11/23_series/23082/a4bfa2343d75076b79f7e33d93915e00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7ae362983ee06a7b9dd27555fa721cd362bd0af999338f9921d0625525b5fc1 +size 32948 diff --git a/marked/Rel-11/23_series/23082/adc59ed6840bcb2d392ea323abfccedc_img.jpg b/marked/Rel-11/23_series/23082/adc59ed6840bcb2d392ea323abfccedc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e415ea6219b565373295ca2e501415c44f01b66a --- /dev/null +++ b/marked/Rel-11/23_series/23082/adc59ed6840bcb2d392ea323abfccedc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9b46020ca0b33e6cdadef97fa63872edd429a632b69c2f69069d47d50c7a631 +size 53270 diff --git a/marked/Rel-11/23_series/23082/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-11/23_series/23082/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57b874f106d87b2a23212e4bb6bfa25da216a204 --- /dev/null +++ b/marked/Rel-11/23_series/23082/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65f6aab43530c987d0514d588c9482f3879184aeecc3c5a32b2964e94632777e +size 34511 diff --git a/marked/Rel-11/23_series/23082/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/Rel-11/23_series/23082/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fecd69c3b6224f83a7bd150e3be94b007737691 --- /dev/null +++ b/marked/Rel-11/23_series/23082/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9562b8163e1a1c9725332d6526cc3a14a2509c3b2ae03c6fec0456fc71d0453f +size 27948 diff --git a/marked/Rel-11/23_series/23082/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/marked/Rel-11/23_series/23082/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..549846973d569dfe1a0770536afd26981d960a81 --- /dev/null +++ b/marked/Rel-11/23_series/23082/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1777665639b5433c7ff2392b0c42124e565b5bbcc280627ae79942c2bf5e8716 +size 89330 diff --git a/marked/Rel-11/23_series/23082/c0c7f65c51c83fbe595b47326f6b089a_img.jpg b/marked/Rel-11/23_series/23082/c0c7f65c51c83fbe595b47326f6b089a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69bbf085db8e92ed1c7ea8b23fab72cf55325907 --- /dev/null +++ b/marked/Rel-11/23_series/23082/c0c7f65c51c83fbe595b47326f6b089a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d855489d949aaae6bee6dde7dffd8a614347cde1c3d1ca57298c160e41481685 +size 28564 diff --git a/marked/Rel-11/23_series/23082/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/Rel-11/23_series/23082/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1ff5be34cf20a3aea93b32f166b9bc2889eef20 --- /dev/null +++ b/marked/Rel-11/23_series/23082/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ddf0ae4e812de048e7f8e3be494da2feaba29729a08822e92b0265779a7fba8 +size 31480 diff --git a/marked/Rel-11/23_series/23082/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/Rel-11/23_series/23082/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f2218c594b17e12a49f060228e7512d9a179103 --- /dev/null +++ b/marked/Rel-11/23_series/23082/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb88664574f05e2402c55b75a191c715f2182b13b8301d497321610aa2bf8df3 +size 32768 diff --git a/marked/Rel-11/23_series/23082/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-11/23_series/23082/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b00fd134d450d9a266692e752cb079bb602abd7 --- /dev/null +++ b/marked/Rel-11/23_series/23082/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc676f42ab3ee244a5902a8adb66afafc6f559f839ae792de06e623bc862630e +size 114089 diff --git a/marked/Rel-11/23_series/23082/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/23_series/23082/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b2966b4f95d1905f845d01f759958a007beb555 --- /dev/null +++ b/marked/Rel-11/23_series/23082/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f59436964d659c9486a6961a804f408d3049fa1093682b38ab69cbd95bba0e15 +size 112694 diff --git a/marked/Rel-11/23_series/23082/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/23_series/23082/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94f5dc89af124961784fafcf14fceb81337f11c6 --- /dev/null +++ b/marked/Rel-11/23_series/23082/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:486aeb24c8b6525150c7d1f8dacf3c53d132216a2fca5d5b8e95b68f85ba1274 +size 114051 diff --git a/marked/Rel-11/23_series/23082/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-11/23_series/23082/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14ea06b49a894942d96ae134f1a6147d903d9681 --- /dev/null +++ b/marked/Rel-11/23_series/23082/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4432e996357fc5b7c1baf14006167fd56427af0b5dd6279d36b50f86bb696871 +size 63367 diff --git a/marked/Rel-11/23_series/23082/e417ae35ab07134888be901c201d54cd_img.jpg b/marked/Rel-11/23_series/23082/e417ae35ab07134888be901c201d54cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98bb11abc7dadb7b82267d513f82b0378d8c856d --- /dev/null +++ b/marked/Rel-11/23_series/23082/e417ae35ab07134888be901c201d54cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d125b917d261e04afdfceb67eb9f83521055e1dac34714ee044c53b02e8a6fd +size 114359 diff --git a/marked/Rel-11/23_series/23082/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-11/23_series/23082/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acf31eb836351986986bb12474d050b3d84ab882 --- /dev/null +++ b/marked/Rel-11/23_series/23082/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6db4100e9936a379bdfd55326d0a16807848fd7c46fc20bfb39292f85d878e9f +size 33341 diff --git a/marked/Rel-11/23_series/23082/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-11/23_series/23082/f0a97d0d3818a253c1d2a009966081b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92200cbc90045e19a143873a0cb5131f691c2a26 --- /dev/null +++ b/marked/Rel-11/23_series/23082/f0a97d0d3818a253c1d2a009966081b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8263d0a755f286925fc0cbdf0af128e1942adccbf3644e90d81e94455004bec2 +size 32195 diff --git a/marked/Rel-11/23_series/23082/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-11/23_series/23082/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec15a6708fc2ab342f3683cb5352483654513346 --- /dev/null +++ b/marked/Rel-11/23_series/23082/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:097f6a3dd33f948a001013d1e0fb2061bc4778dd2bca98859278b0035f8e9581 +size 51524 diff --git a/marked/Rel-11/23_series/23082/fc07df3b799d63e7e6c7760ca077ee99_img.jpg b/marked/Rel-11/23_series/23082/fc07df3b799d63e7e6c7760ca077ee99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d5a717c3fa7903f9bf4a5f567457fbef75919ff --- /dev/null +++ b/marked/Rel-11/23_series/23082/fc07df3b799d63e7e6c7760ca077ee99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec6ded7cb661b14b4e2e31b367d55609bc909de9910c21c72b0de64d528c6c3d +size 37949 diff --git a/marked/Rel-11/23_series/23082/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23082/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..638fa279171ffa8376267f3c94510e68494cbf1c --- /dev/null +++ b/marked/Rel-11/23_series/23082/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52c4bb0423a8603dfb5f47e3e6ae29c2eebc4f19f62104bc68429c2843c191b2 +size 73847 diff --git a/marked/Rel-11/23_series/23082/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-11/23_series/23082/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a5cc052442408e88fd264fcad8706a4cbe72093 --- /dev/null +++ b/marked/Rel-11/23_series/23082/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a75430112eeaff5c712641851b7ed73874b295d4cce0d3176f5243b2cf566fbc +size 65506 diff --git a/marked/Rel-11/23_series/23082/raw.md b/marked/Rel-11/23_series/23082/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8cdd93a2a68ed0a36fbc66154b574cd12f10f325 --- /dev/null +++ b/marked/Rel-11/23_series/23082/raw.md @@ -0,0 +1,3729 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 0 Scope..... | 7 | +| 0.1 References ..... | 7 | +| 0.2 Abbreviations ..... | 7 | +| 0.3 The forwarded-to number..... | 8 | +| 0.4 Cross phase compatibility ..... | 8 | +| 0.5 Support of Long Forwarded-to Numbers ..... | 8 | +| 0.6 Data stored in the HLR for all call forwarding services ..... | 8 | +| 1 Call forwarding unconditional (CFU)..... | 9 | +| 1.1 Handling of call forwarding unconditional ..... | 9 | +| 1.1.1 Registration..... | 9 | +| 1.1.2 Erasure ..... | 11 | +| 1.1.3 Activation ..... | 13 | +| 1.1.4 Deactivation..... | 15 | +| 1.1.5 Interrogation ..... | 17 | +| 1.2 Functions and information flows..... | 18 | +| 1.3 Information stored in the HLR ..... | 20 | +| 1.4 State transition model..... | 21 | +| 1.5 Transfer of information from HLR to VLR ..... | 22 | +| 1.6 Information stored in the VLR ..... | 22 | +| 1.7 Handover ..... | 22 | +| 1.8 Cross phase compatibility ..... | 23 | +| 1.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber..... | 23 | +| 1.8.2 HLR only supports Phase 1 updating of subscriber information ..... | 23 | +| 1.8.3 VLR only supports Phase 1 updating of subscriber information ..... | 23 | +| 1.8.4 GMSC only supports Phase 1 call handling..... | 23 | +| 1.8.5 GMSC does not support CAMEL or supports CAMEL Phase 1 only ..... | 23 | +| 1.9 Contents of Messages..... | 24 | +| 1.9.1 Messages on the C interface (MSC-HLR)..... | 24 | +| 1.9.1.1 Send Routing Info ..... | 24 | +| 1.9.1.2 Send Routing Info ack ..... | 24 | +| 1.9.2 Messages on the Um, B and D interfaces (MS – network) ..... | 24 | +| 1.9.2.1 RegisterSS..... | 24 | +| 1.9.2.2 ActivateSS ..... | 24 | +| 1.9.2.3 InterrogateSS ..... | 25 | +| 1.9.3 Information flows on the J interface (HLR – gsmSCF) ..... | 25 | +| 1.9.3.1 Any Time Subscription Interrogation ..... | 25 | +| 1.9.3.2 Any Time Subscription Interrogation ack ..... | 25 | +| 1.9.3.3 Any Time Modification ..... | 25 | +| 1.9.3.4 Any Time Modification ack..... | 25 | +| 1.10 Exceptional Procedures ..... | 26 | +| 1.10.1 MS does not support Long Forwarded-to Numbers ..... | 26 | +| 1.10.2 HLR does not support Long Forwarded-to Numbers ..... | 26 | +| 1.10.3 GMSC does not support Long Forwarded-to Numbers ..... | 26 | +| 2 Call forwarding on mobile subscriber busy ..... | 26 | +| 2.1 Handling of call forwarding on mobile subscriber busy ..... | 26 | +| 2.1.1 Registration..... | 26 | +| 2.1.2 Erasure ..... | 29 | +| 2.1.3 Activation ..... | 30 | +| 2.1.4 Deactivation..... | 33 | +| 2.1.5 Interrogation ..... | 34 | +| 2.2 Functions and information flows..... | 34 | +| 2.2.1 Call re-routed from VLR ..... | 34 | +| 2.2.2 Call re-routed from HLR ..... | 34 | +| 2.3 Information stored in the HLR ..... | 41 | +| 2.4 State transition model..... | 41 | +| 2.5 Transfer of information from HLR to VLR ..... | 42 | + +| | | | +|---------|-------------------------------------------------------------------------------|----| +| 2.6 | Information stored in the VLR ..... | 42 | +| 2.7 | Handover ..... | 42 | +| 2.8 | Cross phase compatibility ..... | 43 | +| 2.8.1 | MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber..... | 43 | +| 2.8.2 | HLR only supports Phase 1 updating of subscriber information ..... | 43 | +| 2.8.3 | VLR only supports Phase 1 updating of subscriber information ..... | 43 | +| 2.8.4 | VLR only supports Phase 1 call handling ..... | 43 | +| 2.8.5 | VLR does not support CAMEL or supports CAMEL Phase 1 only ..... | 43 | +| 2.8.6 | GMSC only supports Phase 1 call handling ..... | 44 | +| 2.8.7 | GMSC does not support CAMEL or supports CAMEL Phase 1 only ..... | 44 | +| 2.9 | Contents of messages ..... | 44 | +| 2.9.1 | Messages on the B interface (MSC-VLR)..... | 44 | +| 2.9.1.1 | Send Info For Incoming Call ack..... | 44 | +| 2.9.2 | Messages on the D interface (VLR-HLR)..... | 44 | +| 2.9.2.1 | Insert Subscriber Data..... | 44 | +| 2.9.2.2 | Update Location..... | 45 | +| 2.9.2.3 | Provide Roaming Number ..... | 45 | +| 2.9.2.4 | Restore Data..... | 45 | +| 2.9.3 | Messages on the E interface (VMSC-GMSC)..... | 45 | +| 2.9.3.1 | Resume Call Handling ..... | 45 | +| 2.9.4 | Messages on the MSC internal interface ..... | 46 | +| 2.9.4.1 | Perform Call Forwarding ..... | 46 | +| 2.9.4.2 | Perform Call Forwarding ack ..... | 46 | +| 2.10 | Support of Long Forwarded-to Numbers ..... | 46 | +| 2.10.1 | MS does not support Long Forwarded-to Numbers ..... | 46 | +| 2.10.2 | HLR does not support Long Forwarded-to Numbers ..... | 46 | +| 2.10.3 | GMSC does not support Long Forwarded-to Numbers ..... | 46 | +| 2.10.4 | MSC/VLR does not support Long Forwarded-to Numbers ..... | 46 | +| 3 | Call forwarding on no reply ..... | 47 | +| 3.1 | Handling of call forwarding on no reply ..... | 47 | +| 3.1.1 | Registration..... | 47 | +| 3.1.2 | Erasure ..... | 49 | +| 3.1.3 | Activation ..... | 50 | +| 3.1.4 | Deactivation..... | 52 | +| 3.1.5 | Interrogation ..... | 53 | +| 3.2 | Functions and information flows..... | 53 | +| 3.3 | Information stored in the HLR ..... | 57 | +| 3.4 | State transition model..... | 57 | +| 3.5 | Transfer of information from HLR to VLR ..... | 58 | +| 3.6 | Information stored in the VLR ..... | 58 | +| 3.7 | Handover ..... | 59 | +| 3.8 | Cross phase compatibility ..... | 59 | +| 3.8.1 | MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber..... | 59 | +| 3.8.2 | HLR only supports Phase 1 updating of subscriber information ..... | 59 | +| 3.8.3 | VLR only supports Phase 1 updating of subscriber information ..... | 59 | +| 3.8.4 | VLR only supports Phase 1 call handling ..... | 59 | +| 3.8.5 | VLR does not support CAMEL or supports CAMEL Phase 1 only ..... | 60 | +| 3.9 | Contents of messages ..... | 60 | +| 3.10 | Support of Long Forwarded-to Numbers ..... | 60 | +| 4 | Call forwarding on mobile subscriber not reachable ..... | 60 | +| 4.1 | Handling of call forwarding on mobile subscriber not reachable ..... | 60 | +| 4.1.1 | Registration..... | 60 | +| 4.1.2 | Erasure ..... | 63 | +| 4.1.3 | Activation ..... | 64 | +| 4.1.4 | Deactivation..... | 66 | +| 4.1.5 | Interrogation ..... | 67 | +| 4.2 | Functions and information flows..... | 67 | +| 4.2.1 | Call re-routed from VLR ..... | 67 | +| 4.2.2 | Call re-routed from HLR ..... | 67 | +| 4.2.3 | Call re-routed from HLR for Pre-Paging..... | 77 | + +| | | | +|------------------------|-------------------------------------------------------------------------------|----| +| 4.3 | Information stored in the HLR ..... | 81 | +| 4.4 | State transition model..... | 82 | +| 4.5 | Transfer of information from HLR to VLR ..... | 83 | +| 4.6 | Information stored in the VLR ..... | 83 | +| 4.7 | Handover ..... | 83 | +| 4.8 | Cross phase compatibility ..... | 84 | +| 4.8.1 | MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber..... | 84 | +| 4.8.2 | HLR only supports Phase 1 updating of subscriber information ..... | 84 | +| 4.8.3 | VLR only supports Phase 1 updating of subscriber information ..... | 84 | +| 4.8.4 | GMSC only supports Phase 1 call handling ..... | 84 | +| 4.8.5 | VLR only supports Phase 1 call handling ..... | 84 | +| 4.8.6 | VLR does not support CAMEL or supports CAMEL Phase 1 only ..... | 85 | +| 4.8.7 | GMSC does not support CAMEL or supports CAMEL Phase 1 only ..... | 85 | +| 4.9 | Contents of messages ..... | 85 | +| 4.10 | Support of Long Forwarded-to Numbers ..... | 85 | +| Annex A (informative): | Change history..... | 86 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP). + +The present document defines the stage 2 of the Call Forwarding (CF) supplementary services for 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. + +# --- 0 Scope + +The present document gives the stage 2 description of the call forwarding supplementary services. + +The group of supplementary services call offering supplementary services is divided into 4 different supplementary services: + +- | | | | +|------------------------------------------------------|---------|-------------| +| - Call forwarding unconditional | (CFU) | (clause 1); | +| - Call forwarding on mobile subscriber busy | (CFB) | (clause 2); | +| - Call forwarding on no reply | (CFNRy) | (clause 3); | +| - Call forwarding on mobile subscriber not reachable | (CFNRc) | (clause 4). | + +## 0.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP specifications". +- [2] 3GPP TS 22.004: "General on supplementary services". +- [3] 3GPP TS 22.082: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) Supplementary Services - Stage 1". +- [4] 3GPP TS 23.011: "Technical realization of Supplementary Services". +- [5] 3GPP TS 23.015: "Technical realisation of Operator Determined Barring (ODB)". +- [6] 3GPP TS 22.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description, Stage 1". +- [7] 3GPP TS 23.018: "Basic Call Handling; Technical ealization". +- [8] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3 – Stage 2". +- [9] 3GPP TS 23.079: "Support of Optional Routeing (SOR); Technical realization". +- [10] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [11] 3GPP TS 23.093: "Completion of Calls to Busy Subscriber (CCBS) ; Stage2". +- [12] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service; Stage 2". + +## 0.2 Abbreviations + +For the purposes of the present document, the abbreviations defined in 3G TR 21.905 apply. + +## 0.3 The forwarded-to number + +As indicated in 3GPP TS 22.082 the forwarded-to numbers are stored in the international format. + +If according to 3GPP TS 22.082 the served subscriber is provided with a Translation Information Flag (TIF-CSI) then the HPLMN shall treat the forwarded-to number transparently at the time of registration, i.e. not perform any checks or translations. In this case the forwarded-to number shall be stored in the format as it was received from the MS. + +Therefore, if transferred, the forwarded-to number is transferred from the HLR to other network entities and stored in the VLR always in the format as stored in the HLR.. + +## 0.4 Cross phase compatibility + +For the following supplementary services, a number of changes exist between the present document and the Phase 1 specification: + +- Call forwarding unconditional; +- Call forwarding on mobile subscriber busy; +- Call forwarding on no reply; +- Call forwarding on mobile subscriber not reachable. + +The main body of the present document assumes that all network entities comply with this version of the service. In each case an additional clause (clause x.6) defines the additional requirements for when one or more network entities or the MS complies with the Phase 1 specifications for the supplementary service procedures. + +## 0.5 Support of Long Forwarded-to Numbers + +For the following supplementary services, it shall be possible to register a long forwarded-to number which was not possible in previous versions of the services: + +- Call forwarding unconditional; +- Call forwarding on mobile subscriber busy; +- Call forwarding on no reply; +- Call forwarding on mobile subscriber not reachable. + +The main body of the present document assumes that all network entities comply with this version of the service. In each case an additional clause (clause x.10) defines the additional requirements when one or more network entities and/or the mobile station does not support Long Forwarded-to Numbers. + +The functionality specified in this document does not imply any constraint on the length of a forwarded to number, except where such a constraint is explicitly stated. + +## 0.6 Data stored in the HLR for all call forwarding services + +The following data are stored in the HLR in common for all call forwarding services: + +- The "notification to CSE flag". This flag applies for all call forwarding services. When the data for any Call Forwarding are changed, the HLR checks this flag. If the flag is set, the change is reported to the gsmSCF(s) defined by the gsmSCF address list. See 3GPP TS 23.078. +- The "gsmSCF address list", which is a list of gsmSCF addresses to which Notification on Change of Subscriber Data is to be sent. This list applies to all call forwarding services. See 3GPP TS 23.078. + +# --- 1 Call forwarding unconditional (CFU) + +## 1.1 Handling of call forwarding unconditional + +### 1.1.1 Registration + +At the beginning of registration subscription to the basic service, provision of the supplementary service and sufficiency of registration information has to be checked (see figure 1.2). + +The following information has to be registered in the network: + +- 1) the forwarded-to number (possibly including a sub-address); +- 2) information as to whether all calls or all calls of a specific basic service group should be forwarded. + +#### **The basic service group code** + +If the registration request received by the HLR does not contain any basic service group code, the registration shall be performed for all subscribed basic service groups for which CFU is provided, see figure 1.2. + +#### **The forwarded-to number** + +If the forwarded-to number is a number in the HPLMN country, it may be entered by the served mobile subscriber in three different formats, independent of his actual location, according to the schemes: + +- 1) national (significant) number; +- 2) (trunk) prefix plus national (significant) number; +- 3) international prefix, country code, national (significant) number. + +The received number may have to be converted to an international number before further processing. + +The network may also validate the forwarded-to number before accepting the call forwarding registration request. + +If a served mobile subscriber is provided with the Translation Information Flag (TIF-CSI) as part of the CAMEL subscriber data (refer to TS 23.078), the network shall accept and store the forwarded-to number transparently at the time of registration. In this case the network shall neither convert nor validate the received number. Therefore the forwarded-to number may not comply with the schemes indicated above. + +For further details related to the handling of the forwarded-to number refer to figure 1.2. + +#### **Supplementary Service interaction** + +Possible interaction situations between CFU and other call forwarding and barring supplementary services must then be checked. This is described in figure 1.2. Also see technical specifications 3GPP TS 22.004 and 3GPP TS 22.082. For interaction between CFU and other supplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technical specification for those supplementary services. + +#### **Interaction with CAMEL Phase 2 or higher** + +Possible interaction between CFU and CAMEL Phase 2 or higher is described in figure 1.2. If CAMEL Phase 2 or higher is not supported in the HLR, processing continues from the "No" exit of the test "Result=Pass". + +#### **Notifications to the subscriber** + +When the mobile subscriber registers CFU, the network shall attempt to register and activate the service. The network will return notification of acceptance of the request. This notification will include the forwarded-to number and possibly the basic service group code to which CFU is registered. + +If the system cannot accept a registration request, the network sends a notification that CFU registration was not successful to the served mobile subscriber. + +The information flow for registration of CFU is shown in figure 1.1. + +![Sequence diagram showing the registration of call forwarding unconditional (CFU) between MS, MSC, VLR, and HLR. The sequence starts with MS sending a Register CFU to MSC. MSC then sends a Register CFU to VLR. VLR sends a Register CFU to HLR. HLR returns an Acknowledge to VLR, which is labeled CFU1. VLR then sends an Acknowledge to MSC. Finally, MSC sends a Release complete message back to MS, with a sub-parameter \Facility.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFU1 + MS->>MSC: Register CFU + MSC->>VLR: Register CFU + VLR->>HLR: Register CFU + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete +  \Facility +``` + +Sequence diagram showing the registration of call forwarding unconditional (CFU) between MS, MSC, VLR, and HLR. The sequence starts with MS sending a Register CFU to MSC. MSC then sends a Register CFU to VLR. VLR sends a Register CFU to HLR. HLR returns an Acknowledge to VLR, which is labeled CFU1. VLR then sends an Acknowledge to MSC. Finally, MSC sends a Release complete message back to MS, with a sub-parameter \Facility. + +**Figure 1.1: Registration of call forwarding unconditional** + +![Flowchart of the CFU1 Call forwarding unconditional registration process. The process starts at an 'idle' state, proceeds to 'register CFU', then checks if 'BS included in request' is 'no' (leading to 'set BS = all BS') or 'yes'. It then checks if 'CFU provided' is 'yes'. If 'no', it checks if a 'subset of required BS provided' is 'yes'. If 'yes', it checks if 'BAIC active' is 'yes'. If 'yes', it checks if 'BAOC active' is 'yes'. If 'yes', it calls 'CAMEL_Check_CF_Interaction' (referencing GSM 03.78). If the result is 'PASS', it checks if the 'valid ftn' is 'yes' (with a note: 'Not, e.g.: - special service number; - own number.'). If 'yes', it checks the 'number type' ('national' or 'international'). If 'international', it calls 'convert to international (from HPLMN)'. All paths lead to connector '1'. Connector '2' leads to a decision 'ftn in HPLMN country'. If 'no', it calls 'set error'. If 'yes', it leads to a decision 'BOIC/BOIC-exHC active'. If 'yes', it leads to connector '3'. If 'no', it calls 'make any operative BIC-Roam and CCF services quiescent', then 'set result', then 'acknowledge', and finally returns to 'idle'.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Process CFU1 382\_12(1) + +``` + +graph TD + idle1([idle]) --> registerCFU[register CFU] + registerCFU --> BS_included{BS included in request} + BS_included -- no --> setBS["set BS = all BS"] + setBS --> CFU_provided{CFU provided} + BS_included -- yes --> CFU_provided + CFU_provided -- no --> subset{subset of required BS provided} + subset -- no --> connector2((2)) + subset -- yes --> BAIC_active{BAIC active} + BAIC_active -- yes --> connector2 + BAIC_active -- no --> BAOC_active{BAOC active} + BAOC_active -- yes --> connector2 + BAOC_active -- no --> CAMEL[CAMEL_Check_CF_Interaction] + CAMEL --> Result{Result = PASS} + Result -- No --> valid{valid ftn} + Result -- yes --> connector1((1)) + valid -- no --> connector2 + valid -- yes --> number_type{number type} + number_type -- national --> connector1 + number_type -- international --> convert["convert to international (from HPLMN)"] + convert --> connector1 + connector2 --> ftn_in_HPLMN{ftn in HPLMN country} + ftn_in_HPLMN -- no --> set_error[set error] + ftn_in_HPLMN -- yes --> BOIC_active{BOIC/BOIC-exHC active} + BOIC_active -- yes --> connector3((3)) + BOIC_active -- no --> quiescent["make any operative BIC-Roam and CCF services quiescent"] + quiescent --> set_result[set result] + set_result --> acknowledge[acknowledge] + acknowledge --> idle2([idle]) + +``` + +Not, e.g.: + +- special service number; +- own number. + +BS: Basic Service group. + ftn: forwarded-to number. + CCF: "Conditional" Call Forwarding. + BAOC: Barring of All Outgoing Calls. + BOIC: Barring of Outgoing International Calls. + BOIC-exHC: Barring of Outgoing International Calls - except those directed to HPLMN Country. + BAIC: Barring of All Incoming Calls. + BIC-Roam: Barring of Incoming Calls when Roaming outside the home PLMN country. + +See GSM 03.78 + +Flowchart of the CFU1 Call forwarding unconditional registration process. The process starts at an 'idle' state, proceeds to 'register CFU', then checks if 'BS included in request' is 'no' (leading to 'set BS = all BS') or 'yes'. It then checks if 'CFU provided' is 'yes'. If 'no', it checks if a 'subset of required BS provided' is 'yes'. If 'yes', it checks if 'BAIC active' is 'yes'. If 'yes', it checks if 'BAOC active' is 'yes'. If 'yes', it calls 'CAMEL\_Check\_CF\_Interaction' (referencing GSM 03.78). If the result is 'PASS', it checks if the 'valid ftn' is 'yes' (with a note: 'Not, e.g.: - special service number; - own number.'). If 'yes', it checks the 'number type' ('national' or 'international'). If 'international', it calls 'convert to international (from HPLMN)'. All paths lead to connector '1'. Connector '2' leads to a decision 'ftn in HPLMN country'. If 'no', it calls 'set error'. If 'yes', it leads to a decision 'BOIC/BOIC-exHC active'. If 'yes', it leads to connector '3'. If 'no', it calls 'make any operative BIC-Roam and CCF services quiescent', then 'set result', then 'acknowledge', and finally returns to 'idle'. + +Figure 1.2: CFU1 Call forwarding unconditional registration process + +### 1.1.2 Erasure + +A previous registration can be erased in either of the following three ways: + +- the subscriber can specifically erase a previous registration (to a basic service group) with an appropriate control procedure; +- the subscriber can register information for CFU (to a basic service group), thus causing previous registrations of CFU to be overridden (in the network this shall be handled as an erasure immediately followed by a registration); +- all information is erased as a result of withdrawal of the supplementary service (administrative handling). + +#### **The basic service group code** + +If the erasure request received by the HLR does not contain any basic service group code, the erasure request applies for all basic service groups for which CFU is registered. See figure 1.4. + +#### **Supplementary Service interaction** + +Possible interaction situations between CFU and other supplementary services must then be checked. This is shown in figure 1.4. Also see technical specifications 3GPP TS 22.004 and 3GPP TS 22.082. For interaction between CFU and other supplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technical specification for those supplementary services. + +#### **Notifications to the subscriber** + +When the mobile subscriber erases CFU, the network shall attempt to erase (and thus deactivate) the service. The network shall send an indication of acceptance or rejection of the erasure request to the served mobile station. + +The information flow for erasure of CFU is shown in figure 1.3. + +![Sequence diagram showing the erasure of call forwarding unconditional (CFU) between MS, MSC, VLR, and HLR. The MS sends an 'Erase CFU' message to the MSC. The MSC sends an 'Erase CFU' message to the VLR. The VLR sends an 'Erase CFU' message to the HLR. The HLR returns an 'Acknowledge' message to the VLR. The VLR returns an 'Acknowledge' message to the MSC. The MSC returns a 'Release complete' message to the MS, with a sub-parameter '\Facility'.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFU2 + MS->>MSC: Erase CFU + MSC->>VLR: Erase CFU + VLR->>HLR: Erase CFU + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note right of MS: \Facility +``` + +Sequence diagram showing the erasure of call forwarding unconditional (CFU) between MS, MSC, VLR, and HLR. The MS sends an 'Erase CFU' message to the MSC. The MSC sends an 'Erase CFU' message to the VLR. The VLR sends an 'Erase CFU' message to the HLR. The HLR returns an 'Acknowledge' message to the VLR. The VLR returns an 'Acknowledge' message to the MSC. The MSC returns a 'Release complete' message to the MS, with a sub-parameter '\Facility'. + +**Figure 1.3: Erasure of call forwarding unconditional** + +![Flowchart for Process CFU2: Call forwarding unconditional erasure process. The process starts at an 'idle' state, followed by an 'erase CFU' step. It then enters a loop: a decision 'BS included in request' (no leads to 'set BS = all BS', yes leads to 'CFU provided'). 'CFU provided' (no leads to 'set error', yes leads to 'make any quiescent BIC-Roam and CCF services operative'). Both 'set result' and 'set error' lead to 'acknowledge', which then returns to the 'idle' state.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +**Process CFU2** + +382\_14(1) + +BS: Basic Service group. + CCF: "Conditional" Call Forwarding. + BIC-Roam: Barring of Incoming Calls when Roaming outside the home PLMN country. + +``` + +graph TD + idle1([idle]) --> erase[erase CFU] + erase --> BS_incl{BS included in request} + BS_incl -- no --> set_BS[set BS = all BS] + BS_incl -- yes --> CFU_prov{CFU provided} + set_BS --> CFU_prov + CFU_prov -- no --> set_err[set error] + CFU_prov -- yes --> make_quiescent[make any quiescent BIC-Roam and CCF services operative] + make_quiescent --> set_res[set result] + set_res --> ack{acknowledge} + set_err --> ack + ack --> idle2([idle]) + +``` + +Flowchart for Process CFU2: Call forwarding unconditional erasure process. The process starts at an 'idle' state, followed by an 'erase CFU' step. It then enters a loop: a decision 'BS included in request' (no leads to 'set BS = all BS', yes leads to 'CFU provided'). 'CFU provided' (no leads to 'set error', yes leads to 'make any quiescent BIC-Roam and CCF services operative'). Both 'set result' and 'set error' lead to 'acknowledge', which then returns to the 'idle' state. + +**Figure 1.4: CFU2 Call forwarding unconditional erasure process** + +### 1.1.3 Activation + +The network initially checks subscription to the basic service and registration status of the supplementary service, see figure 1.6. + +Possible interaction situations between CFU and other supplementary services must then be checked. The SDL diagrams in figure 1.6 shows the function to be performed in the HLR in order to deal with the interactions between CFU and the call restriction and conditional call forwarding services. Also see 3GPP TS 22.004 [2] and 3GPP TS 22.082 [3]. For interaction between CFU and other supplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technical specification for those supplementary services. + +CFU may be active simultaneously with ACR (see 3GPP TS 23.088 [12]). If CFU and ACR are active simultaneously, then the ACR supplementary service shall take precedence over the CFU supplementary service, i.e. a call which is + +terminated for the served subscriber when CLI presentation is restricted shall be rejected according to the ACR supplementary service. + +#### **The Basic Service Group Code** + +If the activation request received by the HLR doesn't contain any basic service group code, the activation request shall apply to all subscribed basic service groups against which a CFU forwarded-to number is registered. If a forwarded-to number is not registered against even a subset of the required basic service group, the request will be rejected. + +Note that according to 3GPP TS 22.004 [2], a request for activation shall still be accepted although the CFU supplementary service was already active for all basic service groups. + +#### **Notification to the subscriber** + +The network will return notification of acceptance, partial acceptance or rejection of the request to the mobile station. + +The information flow for activation of CFU is shown in figure 1.5. + +![Sequence diagram showing the activation of call forwarding unconditional (CFU) between MS, MSC, VLR, and HLR. The MS sends an 'Activate CFU' message to the MSC. The MSC sends an 'Activate CFU' message to the VLR. The VLR sends an 'Activate CFU' message to the HLR. The HLR responds with an 'Acknowledge' message to the VLR. The VLR sends an 'Acknowledge' message to the MSC. The MSC sends a 'Release complete' message to the MS, with a sub-field '\Facility'.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFU3 + MS->>MSC: Activate CFU + MSC->>VLR: Activate CFU + VLR->>HLR: Activate CFU + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility +``` + +Sequence diagram showing the activation of call forwarding unconditional (CFU) between MS, MSC, VLR, and HLR. The MS sends an 'Activate CFU' message to the MSC. The MSC sends an 'Activate CFU' message to the VLR. The VLR sends an 'Activate CFU' message to the HLR. The HLR responds with an 'Acknowledge' message to the VLR. The VLR sends an 'Acknowledge' message to the MSC. The MSC sends a 'Release complete' message to the MS, with a sub-field '\Facility'. + +**Figure 1.5: Activation of call forwarding unconditional** + +![Flowchart for Process CFU3: Call forwarding unconditional activation process. The process starts at 'idle', goes to 'activate CFU', then checks if CFU is registered for the required BS. If 'no', it goes to 'set error'. If 'yes', it checks if BAIC is active. If 'yes', it goes to 'set error'. If 'no', it checks if BAOC is active. If 'yes', it goes to 'set error'. If 'no', it checks if BOIC/BOIC-exHC is active. If 'yes', it goes to 'set error'. If 'no', it checks if ftn is in HPLMN country. If 'yes', it goes to 'set result'. If 'no', it goes to 'set error'. Both 'set result' and 'set error' lead to 'acknowledge', which then returns to 'idle'.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +**Process CFU3** 382\_16(1) + +CCF: "Conditional" Call Forwarding. + BS: Basic Service group. + ftn: forwarded-to number. + BAIC: Barring of All Incoming Calls. + BAOC: Barring of All Outgoing Calls. + BOIC: Barring of Outgoing International Calls. + BOIC-exHC: Barring of Outgoing International Calls - except those directed to HPLMN Country. + +``` + +graph TD + idle1([idle]) --> activate[activate CFU] + activate --> CFU_registered{CFU registered for required BS} + CFU_registered -- no --> set_error1[set error] + CFU_registered -- yes --> BAIC_active{BAIC active} + BAIC_active -- yes --> set_error1 + BAIC_active -- no --> BAOC_active{BAOC active} + BAOC_active -- yes --> set_error1 + BAOC_active -- no --> BOIC_exHC_active{BOIC/BOIC-exHC active} + BOIC_exHC_active -- yes --> set_error1 + BOIC_exHC_active -- no --> ftn_in_HPLMN{ftn in HPLMN country} + ftn_in_HPLMN -- yes --> set_result[set result] + ftn_in_HPLMN -- no --> set_error2[set error] + set_result --> acknowledge{{acknowledge}} + set_error2 --> acknowledge + set_error1 --> acknowledge + acknowledge --> idle2([idle]) + +``` + +make any operative BIC-Roam and CCF services quiescent + +Flowchart for Process CFU3: Call forwarding unconditional activation process. The process starts at 'idle', goes to 'activate CFU', then checks if CFU is registered for the required BS. If 'no', it goes to 'set error'. If 'yes', it checks if BAIC is active. If 'yes', it goes to 'set error'. If 'no', it checks if BAOC is active. If 'yes', it goes to 'set error'. If 'no', it checks if BOIC/BOIC-exHC is active. If 'yes', it goes to 'set error'. If 'no', it checks if ftn is in HPLMN country. If 'yes', it goes to 'set result'. If 'no', it goes to 'set error'. Both 'set result' and 'set error' lead to 'acknowledge', which then returns to 'idle'. + +**Figure 1.6: CFU3 Call forwarding unconditional activation process** + +### 1.1.4 Deactivation + +The previous activation can be deactivated in either of the following three ways: + +- the subscriber can specifically deactivate a previous activation (to a basic service group) with an appropriate control procedure; +- the subscriber can register information for CFU (to a basic service group), thus causing previous registrations and activations of CFU to be overridden (this shall be handled in the same way as an erasure (implying deactivation) immediately followed by a registration (implying activation)); +- the service is deactivated as a result of withdrawal of the supplementary service (administrative handling). + +Possible interaction situations between CFU and other supplementary services must be checked. The SDL diagram in figure 1.8 shows the function to be performed in the HLR in order to deal with the possible interactions between CFU and the conditional call forwarding services. + +#### The Basic Service Group Code + +The CFU deactivation request may specify a basic service group for which deactivation is required. If the deactivation request received by the HLR doesn't contain any basic service group code, the deactivation request shall apply to all basic services for which CFU is active, see figure 1.8. + +If the deactivation request received by the HLR contains a basic service group code, only information related to the specified basic service group(s) is affected. Note that according to 3GPP TS 22.004, a request for deactivation shall still be accepted even if the CFU supplementary service was already deactive for all basic service groups. + +The user shall receive a notification of acceptance or rejection of the CFU deactivation request. + +The information flow for deactivation of call forwarding unconditional is shown in figure 1.7. + +![Sequence diagram showing the information flow for deactivation of call forwarding unconditional between MS, MSC, VLR, and HLR.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFU4 + + MS->>MSC: Deactivate CFU + MSC->>VLR: Deactivate CFU + VLR->>HLR: Deactivate CFU + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility +``` + +The diagram illustrates a sequence of messages between four network entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence is as follows: 1. The MS sends a 'Deactivate CFU' message to the MSC. 2. The MSC forwards this to the VLR. 3. The VLR sends a 'Deactivate CFU' message to the HLR. 4. The HLR responds with an 'Acknowledge' message back to the VLR. 5. The VLR then sends an 'Acknowledge' message back to the MSC. 6. Finally, the MSC sends a 'Release complete' message back to the MS, with a sub-parameter '\Facility'. + +Sequence diagram showing the information flow for deactivation of call forwarding unconditional between MS, MSC, VLR, and HLR. + +**Figure 1.7: Deactivation of call forwarding unconditional** + +![Flowchart for Process CFU4: Call forwarding unconditional deactivation process. The process starts at an 'idle' state, proceeds to 'deactivate CFU', then checks if 'BS included in request'. If 'no', it sets 'BS = all BS'. If 'yes', it checks if 'CFU active for subset BS'. If 'no', it sets an 'error'. If 'yes', it checks if 'BIC-Roam or conditional forwarding quiescent'. If 'no', it goes to 'set result'. If 'yes', it 'make quiescent services operative' then goes to 'set result'. Both 'set result' and 'set error' lead to 'acknowledge', which then returns to an 'idle' state.](8307f6b04df072c9332f9987e034272c_img.jpg) + +**Process CFU4** 382\_18(1) + +BS: Basic Service group. +BIC-Roam: Barring of Incoming Calls when Roaming outside the home PLMN country. + +``` +graph TD; idle1([idle]) --> deactivate[deactivate CFU]; deactivate --> BS_included{BS included in request}; BS_included -- no --> set_BS[set BS = all BS]; BS_included -- yes --> CFU_active{CFU active for subset BS}; set_BS --> CFU_active; CFU_active -- no --> set_error[set error]; CFU_active -- yes --> BIC_Roam{BIC-Roam or conditional forwarding quiescent}; BIC_Roam -- no --> set_result[set result]; BIC_Roam -- yes --> make_quiescent[make quiescent services operative]; make_quiescent --> set_result; set_error --> acknowledge{acknowledge}; set_result --> acknowledge; acknowledge --> idle2([idle]); +``` + +Flowchart for Process CFU4: Call forwarding unconditional deactivation process. The process starts at an 'idle' state, proceeds to 'deactivate CFU', then checks if 'BS included in request'. If 'no', it sets 'BS = all BS'. If 'yes', it checks if 'CFU active for subset BS'. If 'no', it sets an 'error'. If 'yes', it checks if 'BIC-Roam or conditional forwarding quiescent'. If 'no', it goes to 'set result'. If 'yes', it 'make quiescent services operative' then goes to 'set result'. Both 'set result' and 'set error' lead to 'acknowledge', which then returns to an 'idle' state. + +**Figure 1.8: CFU4 Call forwarding unconditional deactivation process** + +### 1.1.5 Interrogation + +#### Data request + +The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. Interrogation of CFU is handled by the HLR which returns the required information or error to the MS, see figure 1.9. + +![Sequence diagram showing the interrogation of call forwarding unconditional. Lifelines: MS, MSC, VLR, HLR. The sequence starts with MS sending 'Interrogate CFU' to MSC. MSC then sends 'Interrogate CFU' to VLR. VLR sends 'Interrogate CFU' to HLR. HLR returns 'Acknowledge' to VLR. VLR returns 'Acknowledge' to MSC. Finally, MSC sends 'Release complete' with a '\Facility' parameter back to MS.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note left of MS: + MS->>MSC: Interrogate CFU + MSC->>VLR: Interrogate CFU + VLR->>HLR: Interrogate CFU + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note right of MS: \Facility +``` + +Sequence diagram showing the interrogation of call forwarding unconditional. Lifelines: MS, MSC, VLR, HLR. The sequence starts with MS sending 'Interrogate CFU' to MSC. MSC then sends 'Interrogate CFU' to VLR. VLR sends 'Interrogate CFU' to HLR. HLR returns 'Acknowledge' to VLR. VLR returns 'Acknowledge' to MSC. Finally, MSC sends 'Release complete' with a '\Facility' parameter back to MS. + +**Figure 1.9: Interrogation of call forwarding unconditional** + +## 1.2 Functions and information flows + +The following Mobile Additional Function has been identified for the PLMN: + +MAF007 + +Call forwarding unconditional authorizations examination + +The ability of a PLMN component to determine the authorizations relating to CFU. + +See figure 1.10. + +Location: HLR. + +The information flow for call forwarding unconditional is shown in figure 1.11. + +![Flowchart for Process MAF007: Call forwarding unconditional authorisations examination (HLR). The process starts at an 'idle' state, moves to 'initiate handling of CFU', then checks if 'active for this BS'. If 'no', it sets indicator to 'set up normal call'. If 'yes', it checks if 'number of forwardings reached'. If 'yes', it sets an error. If 'no', it increments a counter, gets the forwarded-to number, and sets the forwarding cause to CFU. Next, it checks 'notification to calling subscriber'. If 'yes', it sets indicator to 'notify calling subscriber'. If 'no', it checks if 'served subscribers MSISDN can be presented'. Depending on 'yes' or 'no', it sets redirecting presentation to 'allowed' or 'restricted'. All paths eventually lead to 'continue call handling' and return to the 'idle' state.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Process MAF007 + +382\_1A(1) + +``` + +graph TD + Start([idle]) --> Init[initiate handling of CFU] + Init --> Active{active for this BS} + Active -- no --> SetNormal[set indicator = +'set up normal call'] + Active -- yes --> Reached{number of forwardings reached} + Reached -- yes --> SetError[set error] + Reached -- no --> Increment[increment counter +get forwarded-to number +set forwarding cause=CFU] + Increment --> Notify{notification to calling subscriber} + Notify -- yes --> SetNotify[set indicator = +'notify calling subscriber'] + Notify -- no --> MSISDN{served subscribers +MSISDN can be +presented} + MSISDN -- yes --> Allowed[set redirecting +presentation = +allowed] + MSISDN -- no --> Restricted[set redirecting +presentation = +restricted] + + SetError --> Continue[continue call handling] + SetNormal --> Continue + SetNotify --> Continue + Allowed --> Continue + Restricted --> Continue + Continue --> End([idle]) + +``` + +BS : Basic Service group. + +Flowchart for Process MAF007: Call forwarding unconditional authorisations examination (HLR). The process starts at an 'idle' state, moves to 'initiate handling of CFU', then checks if 'active for this BS'. If 'no', it sets indicator to 'set up normal call'. If 'yes', it checks if 'number of forwardings reached'. If 'yes', it sets an error. If 'no', it increments a counter, gets the forwarded-to number, and sets the forwarding cause to CFU. Next, it checks 'notification to calling subscriber'. If 'yes', it sets indicator to 'notify calling subscriber'. If 'no', it checks if 'served subscribers MSISDN can be presented'. Depending on 'yes' or 'no', it sets redirecting presentation to 'allowed' or 'restricted'. All paths eventually lead to 'continue call handling' and return to the 'idle' state. + +**Figure 1.10: MAF007 Call forwarding unconditional authorisations examination (HLR)** + +![Two sequence diagrams illustrating information flow for call forwarding unconditional. The top diagram shows interactions between MSa/TEa, GMSC, HLRb, MSCb, and LEc β. The bottom diagram shows interactions between MSa/TEa, GMSC, HLRb, MSCb, HLRc, and SCCβ. Both diagrams show messages like Set-up, Info request, Info ack, Set-up, and Notification with return options OR1 and OR2.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +**Top Sequence Diagram:** + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant MSCb + participant LEc_β as LEc β + + MSa/TEa-->>GMSC: Set-up + GMSC-->>HLRb: Info request + HLRb-->>GMSC: Info ack MAF007 + GMSC-->>MSCb: Set-up OR1:N + GMSC-->>LEc_β: Set-up OR1:Y + GMSC-->>MSa/TEa: Notification OR2:Y + +``` + +**Bottom Sequence Diagram:** + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant MSCb + participant HLRc + participant SCC_β as SCCβ + + MSa/TEa-->>GMSC: Set-up + GMSC-->>HLRb: Info request + HLRb-->>GMSC: Info ack MAF007 + GMSC-->>MSCb: Set-up OR1:N + GMSC-->>HLRc: Information request OR1:Y + HLRc-->>GMSC: Information acknowledge + GMSC-->>SCC_β: Set-up + GMSC-->>MSa/TEa: Notification OR2:Y + +``` + +NOTE: info: information            Y: Yes +req: request                      N: No +ack: acknowledge +OR1: Forwarding requested +OR2: Notification to calling subscriber required + +Two sequence diagrams illustrating information flow for call forwarding unconditional. The top diagram shows interactions between MSa/TEa, GMSC, HLRb, MSCb, and LEc β. The bottom diagram shows interactions between MSa/TEa, GMSC, HLRb, MSCb, HLRc, and SCCβ. Both diagrams show messages like Set-up, Info request, Info ack, Set-up, and Notification with return options OR1 and OR2. + +**Figure 1.11: Information flow for call forwarding unconditional** + +## 1.3 Information stored in the HLR + +The following logical states are applicable for CFU +(refer to 3GPP TS 23.011 for an explanation of the notation): + +| Provisioning State | Registration State | Activation State | HLR Induction State | +|--------------------|--------------------|-----------------------|---------------------| +| (Not Provisioned, | Not Registered, | Not Active, | Not Induced) | +| (Provisioned, | Not Registered, | Not Active, | Not Induced) | +| (Provisioned, | Registered, | Not Active, | Not Induced) | +| (Provisioned, | Registered, | Active and Quiescent, | Not Induced) | +| (Provisioned, | Registered, | Active and Operative, | Not Induced) | + +The registration and activation state may be different for each applicable elementary basic service group. + +The provisioning state shall be on a per subscriber basis, and hence the same for all basic service groups. + +The HLR shall store: + +- the state of CFU (which shall be one of the valid states listed above) for each applicable elementary basic service group; +- the subscription option "notification to the calling party" on a per subscriber basis; + +This subscription option takes one of the following values: + +- no notification; +- notification. +- the subscription option "MSISDN of the served subscriber can be presented to the forwarded-to subscriber" on a per subscriber basis; + +This subscription option takes one of the following values: + +- presentation restricted; +- presentation allowed. +- the registration parameter "forwarded-to number" (possibly including a forwarded-to sub-address) for each applicable elementary basic service group. +- the default forwarded-to number (containing less than 16 digits) for each applicable elementary basic service group. + +Note that the value "Active and Quiescent" of the activation state is required in case of interaction with Operator Determined Barring (see 3GPP TS 23.015). + +## 1.4 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of CFU. The state changes are either caused by actions of the service provider, the mobile user or the network. + +Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence, they are not shown in the diagram. + +The diagram only shows operations on an elementary basic service group. + +![State transition model for CFU diagram showing five states and their transitions.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +stateDiagram-v2 + S0: (Not Provisioned, Not Registered, Not Active, Not Induced) + S1: (Provisioned, Not Registered, Not Active, Not Induced) + S2: (Provisioned, Registered, Not Active, Not Induced) + S3: (Provisioned, Registered, Active and Quiescent, Not Induced) + S4: (Provisioned, Registered, Active and Operative, Not Induced) + + S0 --> S1 : Provision + S1 --> S0 : Withdrawal + S1 --> S2 : Registration + S2 --> S1 : Erasure + S1 --> S3 : Erasure + S3 --> S1 : Erasure + S3 --> S0 : Withdrawal + S3 --> S4 : SS Interaction ended + S4 --> S3 : SS Interaction started + S2 --> S4 : Activation + S4 --> S2 : Deactivation + S4 --> S0 : Withdrawal + S4 --> S0 : Deactivation + S1 --> S0 : Withdrawal + +``` + +The diagram illustrates the state transition model for CFU (Call Forwarding Unconditional). It consists of five states represented by ovals, each containing a logical description of the service state. Transitions between states are indicated by arrows with associated labels. + +- State 0 (Top):** (Not Provisioned, Not Registered, Not Active, Not Induced) +- State 1 (Middle Left):** (Provisioned, Not Registered, Not Active, Not Induced) +- State 2 (Bottom Left):** (Provisioned, Registered, Not Active, Not Induced) +- State 3 (Middle Right):** (Provisioned, Registered, Active and Quiescent, Not Induced) +- State 4 (Bottom Right):** (Provisioned, Registered, Active and Operative, Not Induced) + +State transition model for CFU diagram showing five states and their transitions. + +Figure 1.12: State transition model for CFU + +## 1.5 Transfer of information from HLR to VLR + +If the provisioning state for CFU is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of CFU for all relevant elementary basic service groups. + +If the logical state of CFU is changed while a subscriber is registered on a VLR then for the affected basic service groups, the HLR shall inform the VLR of the new logical state of CFU. + +## 1.6 Information stored in the VLR + +For CFU the VLR shall store the service state information received from the HLR for all relevant elementary basic service groups. + +## 1.7 Handover + +Handover will have no impact on the control procedure and the operation of the service. + +## 1.8 Cross phase compatibility + +### 1.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber + +In response to a CFU interrogation request, if the MS or any network element involved is of Phase 1, only information concerning basic service groups for which the activation state has the value "Active and Operative" will be returned. This means, for example, that the subscriber will not be aware that the forwarded to number is registered if CFU is deactivated. A subaddress (if registered) will not be included in the response. + +Note that if any network element involved is of Phase 1, CFU Registration requests which use a subaddress and all CFU Activation and Deactivation requests will be rejected, as these are not specified in Phase 1. + +### 1.8.2 HLR only supports Phase 1 updating of subscriber information + +The VLR shall ignore the subscription option "notification to the calling party" and the registration parameter "forwarded to number" when received from a Phase 1 HLR. + +If the VLR receives the SS-Status parameter from a Phase 1 HLR it shall act if it has received the SS-Status parameter with the values shown in the following: + +- 1) Activated => A bit = 1, Q bit = 0; +- 2) Deactivated => A bit = 0, Q bit = 0 or 1 + +### 1.8.3 VLR only supports Phase 1 updating of subscriber information + +When passing CFU information to a Phase 1 VLR, the HLR shall send the service state information in a form which the VLR can accept, based on the logical state held in the HLR, as follows: + +- 1) (Provisioned, Not Registered, Not Active, Not Induced) +=> Erased, Deactivated; +- 2) (Provisioned, Registered, Not Active, Not Induced) +=> Registered, Deactivated; +- 3) (Provisioned, Registered, Active and Operative, Not Induced) +=> Registered, Activated; +- 4) (Provisioned, Registered, Active and Quiescent, Not Induced) +=> Registered, Deactivated. + +The HLR shall not pass a subaddress to a Phase 1 VLR. + +### 1.8.4 GMSC only supports Phase 1 call handling + +When a call is forwarded unconditionally, the HLR shall not pass the subaddress to a Phase 1 GMSC. Calls shall be forwarded without the subaddress. + +### 1.8.5 GMSC does not support CAMEL or supports CAMEL Phase 1 only + +If the activation state of CFU is "Active and Operative" and if the forwarded-to number is registered in a format other than international and if the GMSC does not support CAMEL or supports CAMEL Phase 1 only, then when a request for routing information for a mobile terminated call is received in the HLR, CFU shall not be invoked, i.e. the mobile terminated call establishment will be continued towards the served mobile subscriber. + +## 1.9 Contents of Messages + +### 1.9.1 Messages on the C interface (MSC-HLR) + +#### 1.9.1.1 Send Routing Info + +This message is specified in 3GPP TS 23.018. + +**Send Routing Info contains the following IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|---------------------------------------------------------------------------------------------| +| Long FTN supported | C | Shall be present if the GMSC supports Long Forwarded-to Numbers; otherwise shall be absent. | + +#### 1.9.1.2 Send Routing Info ack + +This message is specified in 3GPP TS 23.018. + +**Send Routing Info ack contains the following amendment to the Forwarded-to number IE and an additional IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Forwarded-to number | C | E.164 number of the C subscriber. Shall be present if the HLR has determined that the call is to be forwarded and at least one of the HLR and GMSC does not support Long Forwarded-to Numbers; otherwise shall be absent. | +| Long forwarded-to number | C | Number of the C subscriber. Shall be present if the HLR has determined that the call is to be forwarded and Long Forwarded-to Numbers are supported by the HLR and the GMSC; otherwise shall be absent. | + +### 1.9.2 Messages on the Um, B and D interfaces (MS – network) + +#### 1.9.2.1 RegisterSS + +**This message corresponds to the MAP\_REGISTER\_SS service specified in 3GPP TS 29.002.** + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------------------------------| +| Long FTN supported | C | Shall be present if the MS supports Long Forwarded-to Numbers; otherwise shall be absent. | + +#### 1.9.2.2 ActivateSS + +**This message corresponds to the MAP\_ACTIVATE\_SS service specified in 3GPP TS 29.002.** + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------------------------------| +| Long FTN supported | C | Shall be present if the MS supports Long Forwarded-to Numbers; otherwise shall be absent. | + +#### 1.9.2.3 InterrogateSS + +**This message corresponds to the MAP\_INTERROGATE\_SS service specified in 3GPP TS 29.002.** + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------------------------------| +| Long FTN supported | C | Shall be present if the MS supports Long Forwarded-to Numbers; otherwise shall be absent. | + +### 1.9.3 Information flows on the J interface (HLR – gsmSCF) + +#### 1.9.3.1 Any Time Subscription Interrogation + +This IF is specified in 3GPP TS 23.078. + +**Any Time Subscription Interrogation contains the following IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------------------------------------------------------------------------| +| Long FTN supported | C | Shall be present if the gsmSCF supports Long Forwarded-to Numbers; otherwise shall be absent. | + +#### 1.9.3.2 Any Time Subscription Interrogation ack + +This IF is specified in 3GPP TS 23.078. + +**The Call forwarding SS data IE within the Any Time Subscription Interrogation ack IF contains the following amendment to the Forwarded-to number IE and an additional IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------| +| Forwarded-to number | C | Shall be present if at least one of the HLR and the gsmSCF does not support Long Forwarded-to Numbers; otherwise shall be absent. | +| Long forwarded-to number | C | Shall be present if the HLR and the gsmSCF support Long Forwarded-to Numbers; otherwise shall be absent. | + +#### 1.9.3.3 Any Time Modification + +This IF is specified in 3GPP TS 23.078. + +**Any Time Modification contains the following IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------------------------------------------------------------------------| +| Long FTN supported | C | Shall be present if the gsmSCF supports Long Forwarded-to Numbers; otherwise shall be absent. | + +#### 1.9.3.4 Any Time Modification ack + +This IF is specified in 3GPP TS 23.078. + +**The Call forwarding SS data IE within the Any Time Modification ack IF contains the following amendment to the Forwarded-to number IE and an additional IE specific to Long Forwarded-to Numbers.** + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------| +| Forwarded-to number | C | Shall be present if at least one of the HLR and the gsmSCF does not support Long Forwarded-to Numbers; otherwise shall be absent. | +| Long forwarded-to number | C | Shall be present if the HLR and the gsmSCF support Long Forwarded-to Numbers; otherwise shall be absent. | + +## 1.10 Exceptional Procedures + +### 1.10.1 MS does not support Long Forwarded-to Numbers + +The MS shall indicate whether it supports Long Forwarded-to Numbers in the RegisterSS, ActivateSS and InterrogateSS messages. + +If the MS does not support Long Forwarded-to Numbers, and a long forwarded-to number is registered, the acknowledgement message shall not contain a forwarded-to number. + +### 1.10.2 HLR does not support Long Forwarded-to Numbers + +The HLR shall not allow a subscriber to register a long forwarded-to number. + +### 1.10.3 GMSC does not support Long Forwarded-to Numbers + +The HLR can determine from the Send Routing Info message whether the GMSC supports Long Forwarded-to Numbers. + +If the GMSC does not support Long Forwarded-to Numbers and the HLR identifies that CFU should be invoked, then: + +- If the registered forwarded-to number contains a maximum of 15 digits then the HLR shall populate the Forwarded-to number parameter in the Send Routing Info ack message with the registered forwarded-to number. +- If the registered forwarded-to number contains more than 15 digits then + - If a default forwarded-to number (containing a maximum of 15 digits) is stored in the HLR, the HLR shall populate the Forwarded-to number parameter in the Send Routing Info ack message with the default forwarded-to number + - Otherwise, the HLR shall instruct the GMSC to release the call. + +# 2 Call forwarding on mobile subscriber busy + +## 2.1 Handling of call forwarding on mobile subscriber busy + +### 2.1.1 Registration + +The same rules apply for the registration of Call Forwarding on Mobile Subscriber Busy as were described for Call Forwarding Unconditional in clause 1.1.1 above, with the exception of the checking of interaction with other supplementary services. Basic registration of information is illustrated in figure 2.2. + +#### Supplementary Service Interaction + +Possible interaction situations between CFB and other supplementary services must then be checked. This is described in figure 2.2. Also see 3GPP TS 22.004 and 3GPP TS 22.082. For interaction between CFB and other supplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technical specification for those supplementary services. + +#### **Interaction with CAMEL Phase 2 or higher** + +Possible interaction between CFB and CAMEL Phase 2 or higher is described in figure 2.2. If CAMEL Phase 2 or higher is not supported in the HLR, processing continues from the "No" exit of the test "Result=Pass". + +The information flow for registration of CFB is shown in figure 2.1. + +![Sequence diagram showing the registration of call forwarding on a mobile subscriber busy. Lifelines: MS, MSC, VLR, HLR. The sequence starts with MS sending 'Register CFB' to MSC. MSC sends 'Register CFB' to VLR. VLR sends 'Register CFB' to HLR. HLR returns 'Acknowledge' to VLR. VLR returns 'Acknowledge' to MSC. MSC sends 'Release complete' to MS, with a sub-message '\Facility'.](088921fa3f5a44c8551815122517eefd_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFB1 + MS-->>MSC: Register CFB + MSC-->>VLR: Register CFB + VLR-->>HLR: Register CFB + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility +``` + +Sequence diagram showing the registration of call forwarding on a mobile subscriber busy. Lifelines: MS, MSC, VLR, HLR. The sequence starts with MS sending 'Register CFB' to MSC. MSC sends 'Register CFB' to VLR. VLR sends 'Register CFB' to HLR. HLR returns 'Acknowledge' to VLR. VLR returns 'Acknowledge' to MSC. MSC sends 'Release complete' to MS, with a sub-message '\Facility'. + +**Figure 2.1: Registration of call forwarding on mobile subscriber busy** + +![Flowchart for Process CFB1: Call forwarding on mobile subscriber busy registration process. The process starts at 'idle', goes to 'register CFB', then checks if 'BS included in request' is 'no' (leading to 'set BS = all BS') or 'yes'. It then checks 'CFB provided' (yes/no), 'subset of required BS provided' (yes/no), 'BAIC active' (yes/no), and 'BAOC active' (yes/no). If 'no' at any point, it leads to connector '2'. If 'yes' to all, it goes to 'CAMEL Check_CF_Interaction' (referencing GSM 03.78), then 'Result = Pass?' (yes/no). If 'no', it checks 'valid fn' (yes/no). If 'yes', it checks 'number type' (national/international). If 'international', it goes to 'convert to international (from HPLMN)' then to connector '1'. If 'yes' to 'Result = Pass?', it leads to connector '3'. Connector '1' leads to decision 'BOIC active' (yes/no). 'yes' leads to connector '3'. 'no' leads to 'BOIC-exHC active' (yes/no). 'yes' leads to 'fin in VPLMN country' (yes/no). 'yes' leads to connector '3'. 'no' leads to 'fin in HPLMN country' (yes/no). 'yes' leads to connector '3'. 'no' leads to connector '2'. 'BOIC-exHC active' (no) leads to 'BIC-Roam active' (yes/no). 'yes' leads to connector '3'. 'no' leads to 'CFU active' (yes/no). 'yes' leads to connector '2'. 'no' leads to 'set result' then 'acknowledge' then 'idle'. Connector '2' leads to 'set error' then 'acknowledge'. Connector '3' leads to 'fin in VPLMN country' (yes/no). 'yes' leads to connector '3'. 'no' leads to 'rearming outside HPLMN country' (yes/no). 'yes' leads to connector '3'. 'no' leads to 'set error' then 'acknowledge'.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +**Process CFB1** 382\_22(1) + +``` + +graph TD + idle1([idle]) --> register[register CFB] + register --> BS_incl{BS included in request} + BS_incl -- no --> set_BS[set BS = all BS] + set_BS --> CFB_prov{CFB provided} + BS_incl -- yes --> CFB_prov + CFB_prov -- no --> conn2_1((2)) + CFB_prov -- yes --> subset{subset of required BS provided} + subset -- no --> conn2_1 + subset -- yes --> BAIC{BAIC active} + BAIC -- yes --> conn2_1 + BAIC -- no --> BAOC{BAOC active} + BAOC -- yes --> conn2_1 + BAOC -- no --> CAMEL[CAMEL Check_CF_Interaction] + CAMEL --> Result{Result = Pass?} + Result -- no --> valid_fn{valid fn} + valid_fn -- no --> conn2_1 + valid_fn -- yes --> num_type{number type} + num_type -- national --> conn1_1((1)) + num_type -- international --> convert[convert to international from HPLMN] + convert --> conn1_1 + Result -- yes --> conn3_1((3)) + conn1_2((1)) --> BOIC{BOIC active} + BOIC -- yes --> conn3_2((3)) + BOIC -- no --> BOIC_exHC{BOIC-exHC active} + BOIC_exHC -- yes --> fin_V{fin in VPLMN country} + fin_V -- yes --> conn3_2 + fin_V -- no --> fin_H{fin in HPLMN country} + fin_H -- yes --> conn3_2 + fin_H -- no --> conn2_2((2)) + BOIC_exHC -- no --> BIC_Roam{BIC-Roam active} + BIC_Roam -- yes --> conn3_2 + BIC_Roam -- no --> CFU{CFU active} + CFU -- yes --> conn2_2 + CFU -- no --> set_res[set result] + set_res --> ack[acknowledge] + ack --> idle2([idle]) + conn2_2 --> set_err1[set error] + set_err1 --> ack + conn3_2 --> fin_V_2{fin in VPLMN country} + fin_V_2 -- yes --> conn3_2 + fin_V_2 -- no --> rearm{rearming outside HPLMN country} + rearm -- yes --> conn3_2 + rearm -- no --> set_err2[set error] + set_err2 --> ack + +``` + +Not, e.g.: + +- special service number; +- own number. + +See GSM 03.78 + +BS: Basic Service group. + fn: forwarded-to number. + BAOC: Barring of All Outgoing Calls. + BOIC: Barring of Outgoing International Calls. + BOIC-exHC: Barring of Outgoing International Calls except those directed to HPLMN Country. + BAIC: Barring of All Incoming Calls. + BIC-Roam: Barring of Incoming Calls when Roaming outside the home PLMN country. + +Flowchart for Process CFB1: Call forwarding on mobile subscriber busy registration process. The process starts at 'idle', goes to 'register CFB', then checks if 'BS included in request' is 'no' (leading to 'set BS = all BS') or 'yes'. It then checks 'CFB provided' (yes/no), 'subset of required BS provided' (yes/no), 'BAIC active' (yes/no), and 'BAOC active' (yes/no). If 'no' at any point, it leads to connector '2'. If 'yes' to all, it goes to 'CAMEL Check\_CF\_Interaction' (referencing GSM 03.78), then 'Result = Pass?' (yes/no). If 'no', it checks 'valid fn' (yes/no). If 'yes', it checks 'number type' (national/international). If 'international', it goes to 'convert to international (from HPLMN)' then to connector '1'. If 'yes' to 'Result = Pass?', it leads to connector '3'. Connector '1' leads to decision 'BOIC active' (yes/no). 'yes' leads to connector '3'. 'no' leads to 'BOIC-exHC active' (yes/no). 'yes' leads to 'fin in VPLMN country' (yes/no). 'yes' leads to connector '3'. 'no' leads to 'fin in HPLMN country' (yes/no). 'yes' leads to connector '3'. 'no' leads to connector '2'. 'BOIC-exHC active' (no) leads to 'BIC-Roam active' (yes/no). 'yes' leads to connector '3'. 'no' leads to 'CFU active' (yes/no). 'yes' leads to connector '2'. 'no' leads to 'set result' then 'acknowledge' then 'idle'. Connector '2' leads to 'set error' then 'acknowledge'. Connector '3' leads to 'fin in VPLMN country' (yes/no). 'yes' leads to connector '3'. 'no' leads to 'rearming outside HPLMN country' (yes/no). 'yes' leads to connector '3'. 'no' leads to 'set error' then 'acknowledge'. + +**Figure 2.2: CFB1 Call forwarding on mobile subscriber busy registration process** + +### 2.1.2 Erasure + +The same rules apply for the erasure of CFB as were described for CFU in clause 1.1.2 above. However, no checks for interaction with other supplementary services are required for erasure of CFB, see figure 2.4. + +The information flow for registration of CFB is shown in figure 2.3. + +![Sequence diagram showing the information flow for the erasure of call forwarding on mobile subscriber busy (CFB) between MS, MSC, VLR, and HLR.](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFB2 + MS-->>MSC: Erase CFB + MSC-->>VLR: Erase CFB + VLR-->>HLR: Erase CFB + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility + +``` + +Sequence diagram showing the information flow for the erasure of call forwarding on mobile subscriber busy (CFB) between MS, MSC, VLR, and HLR. + +Figure 2.3: Erasure of call forwarding on mobile subscriber busy + +![Flowchart for the CFB2 Call forwarding on mobile subscriber busy erasure process.](f2ea0f64a770b22b902820457d262265_img.jpg) + +``` + +graph TD + Start([idle]) --> Process[erase CFB] + Process --> Decision1{BS included in request} + Decision1 -- no --> SetBS[set BS = all BS] + SetBS --> Decision2{CFB provided} + Decision1 -- yes --> Decision2 + Decision2 -- no --> SetError[set error] + Decision2 -- yes --> SetResult[set result] + SetError --> Acknowledge{acknowledge} + SetResult --> Acknowledge + Acknowledge --> End([idle]) + +``` + +Process CFB2 382\_24(1) + +BS: Basic Service group. + +Flowchart for the CFB2 Call forwarding on mobile subscriber busy erasure process. + +Figure 2.4: CFB2 Call forwarding on mobile subscriber busy erasure process + +### 2.1.3 Activation + +The same rules apply for the activation of CFB as were described for CFU in clause 1.1.3 above, with the exception of the checking of interaction with other supplementary services. Basic activation of CFNRc is illustrated in figure 2.6. + +#### **Supplementary Service Interaction** + +Possible interaction situations between CFB and other supplementary services must then be checked. This is described in figure 2.6. Also see 3GPP TS 22.004 [2] and 3GPP TS 22.082 [3]. For interaction between CFB and other supplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technical specification for those supplementary services. + +CFB may be active simultaneously with ACR (see 3GPP TS 23.088 [12]). If CFB and ACR are active simultaneously, then the ACR supplementary service shall take precedence over the CFB service, i.e. a call which is terminated for the served subscriber when CLI presentation is restricted shall be rejected according to the ACR supplementary service. + +The information flow for activation of call forwarding on MS busy is shown in figure 2.5. + +![Sequence diagram showing the activation of call forwarding on MS busy between MS, MSC, VLR, and HLR.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFB3 + MS-->>MSC: Activate CFB + MSC-->>VLR: Activate CFB + VLR-->>HLR: Activate CFB + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility +``` + +The diagram illustrates the sequence of messages for activating call forwarding on a busy mobile station (MS). It involves four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence starts with the MS sending an 'Activate CFB' message to the MSC. The MSC then forwards this to the VLR, which in turn sends it to the HLR. The HLR, associated with 'CFB3', responds with an 'Acknowledge' message back to the VLR. The VLR then sends an 'Acknowledge' message to the MSC. Finally, the MSC sends a 'Release complete' message to the MS, with a sub-parameter '\Facility'. + +Sequence diagram showing the activation of call forwarding on MS busy between MS, MSC, VLR, and HLR. + +**Figure 2.5: Activation of call forwarding on MS busy** + +![Flowchart for Process CFB3: Call forwarding on mobile subscriber busy activation process. The flow starts with 'idle', followed by 'activate CFB'. A decision 'CFB registered for required BS' leads to 'set error' if 'no', or to 'BAIC active' if 'yes'. 'BAIC active' leads to 'set error' if 'yes', or to 'BOIC-Roam active' if 'no'. 'BOIC-Roam active' leads to 'set error' if 'yes', or to 'reaming outside HPLMN country' if 'no'. 'reaming outside HPLMN country' leads to 'set error' if 'yes', or to 'BAOC active' if 'no'. 'BAOC active' leads to 'set error' if 'yes', or to 'BOIC active' if 'no'. 'BOIC active' leads to 'set error' if 'yes', or to 'BOIC-exHC active' if 'no'. 'BOIC-exHC active' leads to 'ftn in VPLMN country' if 'yes', or to 'set error' if 'no'. 'ftn in VPLMN country' leads to 'set error' if 'yes', or to 'ftn in HPLMN country' if 'no'. 'ftn in HPLMN country' leads to 'set error' if 'yes', or to 'CFU active' if 'no'. 'CFU active' leads to 'set result' if 'yes', or to 'set error' if 'no'. All 'set error' blocks lead to 'acknowledge', which leads to 'idle'.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +**Process CFB3** 382\_26(1) + +BS: Basic Service group. +ftn: forwarded-to number. +BAOC: Barring of All Outgoing Calls. +BOIC: Barring of Outgoing International Calls. +BOIC-exHC: Barring of Outgoing International Calls - except those directed to HPLMN Country. +BAIC: Barring of All Incoming Calls. + +``` +graph TD; idle1([idle]) --> activate[activate CFB]; activate --> CFB_reg{CFB registered for required BS}; CFB_reg -- no --> set_error1[set error]; CFB_reg -- yes --> BAIC_active{BAIC active}; BAIC_active -- yes --> set_error1; BAIC_active -- no --> BOIC_Roam_active{BOIC-Roam active}; BOIC_Roam_active -- yes --> set_error1; BOIC_Roam_active -- no --> reaming{reaming outside HPLMN country}; reaming -- yes --> set_error1; reaming -- no --> BAOC_active{BAOC active}; BAOC_active -- yes --> set_error1; BAOC_active -- no --> BOIC_active{BOIC active}; BOIC_active -- yes --> set_error1; BOIC_active -- no --> BOIC_exHC_active{BOIC-exHC active}; BOIC_exHC_active -- yes --> ftn_VPLMN{ftn in VPLMN country}; BOIC_exHC_active -- no --> set_error1; ftn_VPLMN -- yes --> set_error1; ftn_VPLMN -- no --> ftn_HPLMN{ftn in HPLMN country}; ftn_HPLMN -- yes --> set_error1; ftn_HPLMN -- no --> CFU_active{CFU active}; CFU_active -- yes --> set_result[set result]; CFU_active -- no --> set_error1; set_error1 --> acknowledge{acknowledge}; set_result --> acknowledge; acknowledge --> idle2([idle]); +``` + +Flowchart for Process CFB3: Call forwarding on mobile subscriber busy activation process. The flow starts with 'idle', followed by 'activate CFB'. A decision 'CFB registered for required BS' leads to 'set error' if 'no', or to 'BAIC active' if 'yes'. 'BAIC active' leads to 'set error' if 'yes', or to 'BOIC-Roam active' if 'no'. 'BOIC-Roam active' leads to 'set error' if 'yes', or to 'reaming outside HPLMN country' if 'no'. 'reaming outside HPLMN country' leads to 'set error' if 'yes', or to 'BAOC active' if 'no'. 'BAOC active' leads to 'set error' if 'yes', or to 'BOIC active' if 'no'. 'BOIC active' leads to 'set error' if 'yes', or to 'BOIC-exHC active' if 'no'. 'BOIC-exHC active' leads to 'ftn in VPLMN country' if 'yes', or to 'set error' if 'no'. 'ftn in VPLMN country' leads to 'set error' if 'yes', or to 'ftn in HPLMN country' if 'no'. 'ftn in HPLMN country' leads to 'set error' if 'yes', or to 'CFU active' if 'no'. 'CFU active' leads to 'set result' if 'yes', or to 'set error' if 'no'. All 'set error' blocks lead to 'acknowledge', which leads to 'idle'. + +**Figure 2.6: CFB3 Call forwarding on mobile subscriber busy activation process** + +### 2.1.4 Deactivation + +The same rules apply for the deactivation of CFB as were described for CFU in clause 1.1.4 above, see figure 2.8. + +The information flow for deactivation of call forwarding on mobile subscriber busy is shown in figure 2.7. + +![Sequence diagram showing the interaction between MS, MSC, VLR, and HLR for deactivation of call forwarding on mobile subscriber busy.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFB4 + MS->>MSC: Deactivate CFB + MSC->>VLR: Deactivate CFB + VLR->>HLR: Deactivate CFB + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility +``` + +Sequence diagram showing the interaction between MS, MSC, VLR, and HLR for deactivation of call forwarding on mobile subscriber busy. + +Figure 2.7: Deactivation of call forwarding on mobile subscriber busy + +![Flowchart for Process CFB4 (382_28(1)) detailing the deactivation process. It starts at 'idle', proceeds to 'deactivate CFB', then checks if 'BS included in request'. If 'no', it goes to 'set BS = all BS'. If 'yes', it checks if 'CFB active for subset BS'. If 'no', it goes to 'set error'. If 'yes', it goes to 'set result'. Both 'set error' and 'set result' lead to 'acknowledge', which then returns to 'idle'. A note indicates 'BS: Basic Service group.'](1b893df61c2b73b7a85e65fc1f58e203_img.jpg) + +``` +graph TD + idle1([idle]) --> deactivate[deactivate CFB] + deactivate --> BS_included{BS included in request} + BS_included -- no --> set_BS[set BS = all BS] + set_BS --> BS_included + BS_included -- yes --> CFB_active{CFB active for subset BS} + CFB_active -- no --> set_error[set error] + CFB_active -- yes --> set_result[set result] + set_error --> acknowledge{acknowledge} + set_result --> acknowledge + acknowledge --> idle2([idle]) +``` + +Flowchart for Process CFB4 (382\_28(1)) detailing the deactivation process. It starts at 'idle', proceeds to 'deactivate CFB', then checks if 'BS included in request'. If 'no', it goes to 'set BS = all BS'. If 'yes', it checks if 'CFB active for subset BS'. If 'no', it goes to 'set error'. If 'yes', it goes to 'set result'. Both 'set error' and 'set result' lead to 'acknowledge', which then returns to 'idle'. A note indicates 'BS: Basic Service group.' + +Figure 2.8: CFB4 Call forwarding on mobile subscriber busy deactivation process + +### 2.1.5 Interrogation + +#### Data request + +The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. Interrogation of CFB is handled by the VLR which returns the required information or error to the MS, see figure 2.9. + +![Sequence diagram showing the interrogation of call forwarding on mobile subscriber busy. The diagram involves four entities: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate CFB' to MSC. 2. MSC sends 'Interrogate CFB' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release complete' back to MS, with a sub-parameter '\Facility'.](a1890b9a9b85f13e67ed59bbad623659_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: Interrogate CFB + MSC->>VLR: Interrogate CFB + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note right of MS: \Facility +``` + +Sequence diagram showing the interrogation of call forwarding on mobile subscriber busy. The diagram involves four entities: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate CFB' to MSC. 2. MSC sends 'Interrogate CFB' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release complete' back to MS, with a sub-parameter '\Facility'. + +Figure 2.9: Interrogation of call forwarding on mobile subscriber busy + +## 2.2 Functions and information flows + +### 2.2.1 Call re-routed from VLR + +The following Mobile Additional Function has been identified for the PLMN: + +MAF008 + +Call forwarding on mobile subscriber busy authorizations examination + +The ability of a PLMN component to determine the authorizations relating to call forwarding on mobile subscriber busy. See figure 2.10. + +Location: VLR. + +The information flows for forwarding to fixed terminal and to mobile station are shown in figures 2.11 & 2.12 and 2.13 & 2.14 respectively. + +### 2.2.2 Call re-routed from HLR + +The following Mobile Additional Function has been identified for the PLMN: + +MAF008 + +Call forwarding on mobile subscriber busy authorizations examination + +The ability of a PLMN component to determine the authorizations relating to call forwarding on mobile subscriber busy. See figure 2.10. + +Location: HLR. + +The information flow for call forwarding on mobile subscriber busy with busy state as a result of CCBS blocking is shown in figure 2.14a. + +![Flowchart for Process MAF008: Call forwarding on mobile subscriber busy authorisations examination (VLR and HLR).](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +Process MAF008 + +382\_2A(1) + +NDUB: Network Determined User Busy. +UDUB: User Determined User Busy. +BS: Basic Service group. + +``` +graph TD; idle1([idle]) --> initiate[initiate handling of CFB]; initiate --> active{active for this BS}; active -- no --> continue[continue call handling]; active -- yes --> reached{number of forwardings reached}; reached -- yes --> error[set error]; reached -- no --> increment[increment counter<br/>get forwarded-to number<br/>set forwarding cause=CFB]; increment --> udub{UDUB or NDUB}; udub -- UDUB --> continue; udub -- NDUB --> notify_fwd{notification to forwarding subscriber}; notify_fwd -- yes --> set_ind1[set indicator = 'notify forwarding subscriber']; notify_fwd -- no --> notify_call{notification to calling subscriber}; notify_call -- yes --> set_ind2[set indicator = 'notify calling subscriber']; set_ind1 --> served{ served subscribers<br/>MSISDN can be presented}; set_ind2 --> served; served -- yes --> set_redir1[set redirecting presentation = allowed]; served -- no --> set_redir2[set redirecting presentation = restricted]; set_error[set error] --> continue; set_redir1 --> continue; set_redir2 --> continue; continue --> idle2([idle]); +``` + +The flowchart illustrates the process for call forwarding on a mobile subscriber busy. It begins with an 'idle' state, followed by 'initiate handling of CFB'. A decision 'active for this BS' follows; if 'no', it proceeds to 'continue call handling' and back to 'idle'. If 'yes', it checks 'number of forwardings reached'. If 'yes', it 'set error' and proceeds to 'continue call handling'. If 'no', it 'increment counter', 'get forwarded-to number', and 'set forwarding cause=CFB'. Next, it checks 'UDUB or NDUB'. If 'UDUB', it proceeds to 'continue call handling'. If 'NDUB', it checks 'notification to forwarding subscriber'. If 'yes', it 'set indicator = 'notify forwarding subscriber''. If 'no', it checks 'notification to calling subscriber'. If 'yes', it 'set indicator = 'notify calling subscriber''. Both indicator settings lead to a decision 'served subscribers MSISDN can be presented'. If 'yes', it 'set redirecting presentation = allowed'. If 'no', it 'set redirecting presentation = restricted'. All three outcomes ('set error', 'set redirecting presentation = allowed', and 'set redirecting presentation = restricted') lead to 'continue call handling', which then returns to the 'idle' state. + +Flowchart for Process MAF008: Call forwarding on mobile subscriber busy authorisations examination (VLR and HLR). + +Figure 2.10: MAF008 Call forwarding on mobile subscriber busy authorisations examination (VLR and HLR) + +![Sequence diagram showing information flow for call forwarding on mobile subscriber busy (to fixed terminal) (NDUB). Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, LEc. The diagram shows messages like Set-up, Info req, Info ack, Release, Notification, and various response codes (NDUB, MAF008, OR1:N, OR1:Y, OR2:Y, OR3:Y).](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant LEc + + Note left of MSa/TEa: Set-up + MSa/TEa-->>GMSC: Set-up + GMSC-->>HLRb: Info req + HLRb-->>GMSC: Info ack + Note right of HLRb: Set-up + GMSC-->>MSCb: Set-up + MSCb-->>VLRb: Info request + VLRb-->>MSCb: Page MS + Note right of MSCb: NDUB + MSCb-->>VLRb: Busy subscriber (NDUB) + Note right of VLRb: MAF008 + VLRb-->>MSCb: OR1:N Impossible call completion + Note right of HLRb: Release + GMSC-->>MSa/TEa: Release + Note right of VLRb: OR1:Y Connect to following address + VLRb-->>MSCb: + Note right of MSb: Set-up + MSb-->>LEc: + Note right of MSCb: OR2:Y + MSCb-->>MSb: Notif + Note right of HLRb: Notification + Note right of MSCb: OR3:Y + GMSC-->>MSa/TEa: Notification + +``` + +Sequence diagram showing information flow for call forwarding on mobile subscriber busy (to fixed terminal) (NDUB). Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, LEc. The diagram shows messages like Set-up, Info req, Info ack, Release, Notification, and various response codes (NDUB, MAF008, OR1:N, OR1:Y, OR2:Y, OR3:Y). + +NOTE: NDUB: Network Determined User Busy + info: information Y: Yes + req: request N: No + ack: acknowledge + notif: notification + OR1: Call to be forwarded + OR2: Notification to forwarding subscriber required + OR3: Notification to calling subscriber required + +**Figure 2.11: Information flow for call forwarding on mobile subscriber busy (to fixed terminal) (NDUB)** + +![Sequence diagram showing information flow for call forwarding on mobile subscriber busy (to fixed terminal) (UDUB). Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, LEc. The diagram shows messages like Set-up, Info req, Info ack, Release, Notification, and various response codes (UDUB, MAF008, OR1:N, OR2:Y).](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant LEc + + Note left of MSa/TEa: Set-up + MSa/TEa-->>GMSC: Set-up + GMSC-->>HLRb: Info req + HLRb-->>GMSC: Info ack + GMSC-->>MSCb: Set-up + MSCb-->>VLRb: Info request + VLRb-->>MSCb: Page MS + MSCb-->>MSb: Set-up + MSb-->>MSCb: UDUB + MSCb-->>VLRb: Busy subscriber (UDUB) + VLRb-->>GMSC: MAF008 + GMSC-->>MSa/TEa: Release + VLRb-->>MSCb: OR1:N Impossible call completion + MSCb-->>MSb: Set-up + MSb-->>LEc: Set-up + LEc-->>MSCb: OR2:Y + MSCb-->>GMSC: Notification + GMSC-->>MSa/TEa: Notification + +``` + +Sequence diagram showing information flow for call forwarding on mobile subscriber busy (to fixed terminal) (UDUB). Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, LEc. The diagram shows messages like Set-up, Info req, Info ack, Release, Notification, and various response codes (UDUB, MAF008, OR1:N, OR2:Y). + +NOTE: UDUB: User Determined User Busy + info: information Y: Yes + req: request N: No + ack: acknowledge + notif: notification + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + +**Figure 2.12: Information flow for call forwarding on mobile subscriber busy (to fixed terminal) (UDUB)** + +![Sequence diagram showing information flow for call forwarding on mobile subscriber busy (to mobile station) (NDUB). Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, HLRC, MSCc. The diagram shows messages like Set-up, Info req, Info ack, Release, Notification, and various responses including NDUB and call forwarding options (OR1:N, OR2:Y, OR3:Y).](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant HLRC + participant MSCc + + Note left of MSa/TEa: Set-up + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb-->>GMSC: Info ack + GMSC->>MSCb: Set-up + MSCb->>VLRb: Info request + VLRb-->>MSCb: Page MS + Note right of MSCb: NDUB + MSCb->>VLRb: Busy subscriber + VLRb-->>MSCb: MAF008 (NDUB) + Note right of VLRb: OR1:N + MSCb->>VLRb: Impossible call completion + Note left of MSa/TEa: Release + MSa/TEa-->>GMSC: Release + GMSC->>VLRb: OR1:Y + VLRb-->>GMSC: Connect to following address + GMSC->>MSb: Information req + MSb-->>HLRC: Information ack + HLRC->>MSCc: Set-up + Note right of MSCb: OR2:Y + MSCb->>MSb: Notif + Note right of MSCb: OR3:Y + GMSC->>MSa/TEa: Notification + Note left of MSa/TEa: Notif + MSa/TEa-->>GMSC: Notif + +``` + +Sequence diagram showing information flow for call forwarding on mobile subscriber busy (to mobile station) (NDUB). Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, HLRC, MSCc. The diagram shows messages like Set-up, Info req, Info ack, Release, Notification, and various responses including NDUB and call forwarding options (OR1:N, OR2:Y, OR3:Y). + +NOTE: NDUB: Network Determined User Busy + info: information Y: Yes + req: request N: No + ack: acknowledge + notif: notification + OR1: Call to be forwarded + OR2: Notification to forwarding subscriber required + OR3: Notification to calling subscriber required + +**Figure 2.13: Information flow for call forwarding on mobile subscriber busy (to mobile station) (NDUB)** + +![Sequence diagram showing information flow for call forwarding on mobile subscriber busy (to mobile station) (UDUB).](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant HLRc + participant MSCc + + Note left of MSa/TEa: Set-up + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb-->>GMSC: Info ack + GMSC->>MSCb: Set-up + MSCb->>VLRb: Info request + VLRb-->>MSCb: Page MS + MSCb->>MSb: Set-up + Note right of MSb: UDUB + MSb-->>MSCb: UDUB + MSCb->>VLRb: Busy subscriber + Note right of VLRb: MAF008 (UDUB) + VLRb-->>MSCb: OR1:N Impossible call completion + MSCb->>GMSC: Release + GMSC-->>MSa/TEa: Release + VLRb-->>MSCb: OR1:Y Connect to following address + MSCb->>HLRc: Information req + HLRc-->>MSCb: Information ack + MSCb->>MSCc: Set-up + MSCb-->>GMSC: OR2:Y Notification + GMSC-->>MSa/TEa: Notif + +``` + +Sequence diagram showing information flow for call forwarding on mobile subscriber busy (to mobile station) (UDUB). + +NOTE: UDUB: User Determined User Busy + info: information Y: Yes + req: request N: No + ack: acknowledge + notif: notification + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + +**Figure 2.14: Information flow for call forwarding on mobile subscriber busy + (to mobile station) (UDUB)** + +![Sequence diagrams showing information flow for call forwarding on mobile subscriber busy with busy state as a result of CCBS blocking. The top diagram shows interactions between MSa/TEa, GMSC, HLRb, MSCb, and LEc β. The bottom diagram shows interactions between MSa/TEa, GMSC, HLRb, MSCb, HLRc, and SCcβ. Both diagrams detail messages like Set-up, Info request, Info ack, Set-up, OR1:N, OR1:Y, Notification, and OR2:Y.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +The diagram consists of two sequence diagrams illustrating the information flow for call forwarding when a mobile subscriber is busy due to CCBS blocking. + +**Top Sequence Diagram:** Participants: MSa/TEa, GMSC, HLRb, MSCb, LEc β. The sequence starts with a 'Set-up' message from MSa/TEa to GMSC. GMSC sends an 'Info request' to HLRb. HLRb responds with 'Info ack' (containing MAF008). GMSC then sends a 'Set-up' message to MSCb. MSCb sends 'OR1:N' (No) back to GMSC. GMSC sends another 'Set-up' message to MSCb. MSCb sends 'OR1:Y' (Yes) back to GMSC. GMSC sends a 'Notification' back to MSa/TEa. Finally, GMSC sends 'OR2:Y' to MSa/TEa. + +**Bottom Sequence Diagram:** Participants: MSa/TEa, GMSC, HLRb, MSCb, HLRc, SCcβ. The sequence starts with a 'Set-up' message from MSa/TEa to GMSC. GMSC sends an 'Info request' to HLRb. HLRb responds with 'Info ack' (containing MAF008). GMSC then sends a 'Set-up' message to MSCb. MSCb sends 'OR1:N' (No) back to GMSC. GMSC sends an 'Information request' to HLRc. HLRc responds with 'Information acknowledge'. GMSC sends a 'Set-up' message to SCcβ. SCcβ sends a 'Notification' back to GMSC. Finally, GMSC sends 'OR2:Y' to MSa/TEa. + +Sequence diagrams showing information flow for call forwarding on mobile subscriber busy with busy state as a result of CCBS blocking. The top diagram shows interactions between MSa/TEa, GMSC, HLRb, MSCb, and LEc β. The bottom diagram shows interactions between MSa/TEa, GMSC, HLRb, MSCb, HLRc, and SCcβ. Both diagrams detail messages like Set-up, Info request, Info ack, Set-up, OR1:N, OR1:Y, Notification, and OR2:Y. + +NOTE: info: information      Y: Yes + req: request            N: No + ack: acknowledge + OR1: Forwarding requested + OR2: Notification to calling subscriber required + +**Figure 2.14a: Information flow for call forwarding on mobile subscriber busy with busy state as a result of CCBS blocking (see 3GPP TS 23.093 [11] clause 11.2.2)** + +## 2.3 Information stored in the HLR + +**The following logical states are applicable for CFB +(refer to 3GPP TS 23.011 for an explanation of the notation):** + +| <b>Provisioning State</b> | <b>Registration State</b> | <b>Activation State</b> | <b>HLR Induction State</b> | +|---------------------------|---------------------------|-------------------------|----------------------------| +| (Not Provisioned, | Not Registered, | Not Active, | Not Induced) | +| (Provisioned, | Not Registered, | Not Active, | Not Induced) | +| (Provisioned, | Registered, | Not Active, | Not Induced) | +| (Provisioned, | Registered, | Active and Quiescent, | Not Induced) | +| (Provisioned, | Registered, | Active and Operative, | Not Induced) | + +The registration and activation state may be different for each applicable elementary basic service group. + +The provisioning state shall be on a per subscriber basis, and hence the same for all basic service groups. + +The HLR shall store: + +- the state of CFB (which shall be one of the valid states listed above) for each applicable elementary basic service group; +- the subscription option "notification to the calling party" on a per subscriber basis; + +This subscription option takes one of the following values: + +- no notification; +- notification. +- the subscription option "notification to the forwarding party" on a per subscriber basis; + +This subscription option takes one of the following values: + +- no notification; +- notification. + +the subscription option " MSISDN of the served subscriber can be presented to the forwarded-to subscriber" on a per subscriber basis; + +This subscription option takes one of the following values: + +- presentation restricted; +- presentation allowed. + +- the registration parameter "forwarded-to number" (possibly including a forwarded-to sub-address) for each applicable elementary basic service group. +- the default forwarded-to number (containing less than 16 digits) for each applicable elementary basic service group. + +## 2.4 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of CFB. The state changes are either caused by actions of the service provider, the mobile user or the network. + +Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence, they are not shown in the diagram. The diagram only shows operations on an elementary basic service group. + +![State transition model for CFB showing four states and their transitions.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` + +stateDiagram-v2 + [*] --> S0 : (Not Provisioned, Not Registered, Not Active, Not Induced) + S0 --> S1 : Provision + S0 --> S2 : Withdrawal + S0 --> S3 : Withdrawal + S1 --> S0 : Withdrawal + S1 --> S2 : Erasure + S1 --> S3 : Registration + S2 --> S0 : Withdrawal + S2 --> S3 : SS Interaction started + S3 --> S0 : Withdrawal + S3 --> S1 : SS Interaction ended + S3 --> S2 : Deactivation + S3 --> S1 : Erasure + S2 --> S3 : Activation + S2 --> S1 : Deactivation + +``` + +The diagram illustrates the state transition model for CFB (Call Forwarding Basic) across four states: + +- (Not Provisioned, Not Registered, Not Active, Not Induced)**: Initial state. Transitions to **(Provisioned, Not Registered, Not Active, Not Induced)** via **Provision**; to **(Provisioned, Registered, Active and Quiescent, Not Induced)** via **Withdrawal**; and to **(Provisioned, Registered, Not Active, Not Induced)** via **Withdrawal**. +- (Provisioned, Not Registered, Not Active, Not Induced)**: Transitions to **(Not Provisioned, Not Registered, Not Active, Not Induced)** via **Withdrawal**; to **(Provisioned, Registered, Active and Quiescent, Not Induced)** via **Erasure**; and to **(Provisioned, Registered, Not Active, Not Induced)** via **Registration**. +- (Provisioned, Registered, Active and Quiescent, Not Induced)**: Transitions to **(Not Provisioned, Not Registered, Not Active, Not Induced)** via **Withdrawal**; to **(Provisioned, Not Registered, Not Active, Not Induced)** via **SS Interaction ended**; to **(Provisioned, Registered, Not Active, Not Induced)** via **Deactivation**; and to **(Provisioned, Registered, Active and Operative, Not Induced)** via **SS Interaction started**. +- (Provisioned, Registered, Active and Operative, Not Induced)**: Transitions to **(Not Provisioned, Not Registered, Not Active, Not Induced)** via **Withdrawal**; to **(Provisioned, Not Registered, Not Active, Not Induced)** via **Erasure**; to **(Provisioned, Registered, Active and Quiescent, Not Induced)** via **Deactivation**; and to **(Provisioned, Registered, Not Active, Not Induced)** via **Activation**. + +State transition model for CFB showing four states and their transitions. + +Figure 2.15: State transition model for CFB + +## 2.5 Transfer of information from HLR to VLR + +If the provisioning state for CFB is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of CFB for all relevant elementary basic service groups. + +If the registration state for CFB is "Registered" then, when the subscriber registers on a VLR, the HLR shall send that VLR the registration parameter "forwarded-to number" for all relevant elementary basic service groups and information about the subscription options "notification to the calling party", "notification to the forwarding party" and "MSISDN of the served subscriber can be presented to the forwarded-to subscriber". + +If the logical state or the registration parameter "forwarded-to number" of CFB is changed while a subscriber is registered on a VLR then for the affected basic service groups, the HLR shall inform the VLR respectively of the new logical state or the new registration parameter of CFB. + +If information about the subscription options "notification to the calling party" and "notification to the forwarding party" of CFB is changed while a subscriber is registered on a VLR and the registration state of CFB is "Registered" then the HLR shall inform the VLR of the new information about the subscription options of CFB. + +## 2.6 Information stored in the VLR + +For CFB the VLR shall store the service state information, the registration parameter "forward-to number" and the subscription options received from the HLR. + +## 2.7 Handover + +Handover will have no impact on the control procedure and the operation of the service. + +## 2.8 Cross phase compatibility + +### 2.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber + +In response to a CFB interrogation request, if the MS or any network element involved is of Phase 1, only information concerning basic service groups for which the activation state has the value "Active and Operative" will be returned. This means that the subscriber will not be aware that the forwarded to number is registered if CFB is deactivated or active (quiescent). A subaddress (if registered) will not be included. + +Note that if any network element involved is of Phase 1, CFB Registration requests which use a subaddress and all CFB Activation and Deactivation requests will be rejected, as these are not specified in Phase 1. + +### 2.8.2 HLR only supports Phase 1 updating of subscriber information + +If the VLR receives the SS-Status parameter from a Phase 1 HLR it shall act if it has received the SS-Status parameter with the values shown in the following: + +- | | | +|----------------------------|-----------------------------------------------------| +| 1) Registered, Activated | => P bit = 1, R bit = 1, A bit = 1, Q bit = 0; | +| 2) Registered, Deactivated | => P bit = 1, R bit = 1, A bit = 0, Q bit = 0 or 1; | +| 3) Erased | => P bit = 1, R bit = 0, A bit = 0, Q bit = 0 or 1. | + +### 2.8.3 VLR only supports Phase 1 updating of subscriber information + +When passing CFB information to a Phase 1 VLR, the HLR shall send the service state information in a form which the VLR can accept, based on the logical state held in the HLR, as follows: + +- | | | +|-----------------------------------------------------------------|-----------------------------| +| 1) (Provisioned, Not Registered, Not Active, Not Induced) | => Erased, Deactivated; | +| 2) (Provisioned, Registered, Not Active, Not Induced) | => Registered, Deactivated; | +| 3) (Provisioned, Registered, Active and Operative, Not Induced) | => Registered, Activated; | +| 4) (Provisioned, Registered, Active and Quiescent, Not Induced) | => Registered, Deactivated. | + +The HLR shall not pass a subaddress to a Phase 1 VLR. + +### 2.8.4 VLR only supports Phase 1 call handling + +When a call is forwarded on busy, as the HLR does not pass the subaddress to the VLR, calls shall be forwarded without the subaddress. + +### 2.8.5 VLR does not support CAMEL or supports CAMEL Phase 1 only + +When passing CFB information to a VLR not supporting CAMEL or supporting CAMEL Phase 1 only, the HLR shall send the registration parameter "forwarded-to number" only if it is registered in a format which the VLR can accept, i.e. international format. + +If the registration state for CFB is "Registered" and the forwarded-to number is registered in a format other than international, then when updating a VLR not supporting CAMEL or supporting CAMEL Phase 1 only the HLR shall modify the service state information of CFB as follows. + +- | | | +|-------------------------------------------------------|--| +| 1) (Provisioned, Registered, Not Active, Not Induced) | | +|-------------------------------------------------------|--| + +=> (Provisioned, Not Registered, Not Active, Not Induced) + +2) (Provisioned, Registered, Active and Operative, Not Induced) + +=> (Provisioned, Not Registered, Not Active, Not Induced) + +3) (Provisioned, Registered, Active and Quiescent, Not Induced) + +=> (Provisioned, Not Registered, Not Active, Not Induced) + +According to the definitions in clause 2.5 no forwarded-to number will be passed to the VLR in these cases. The modification of the service state information sent to the VLR shall have no impact on the service state information stored in the HLR. + +If the VLR supports Phase 1 updating of subscriber information only, a further translation of the service state information as defined in clause 2.8.3 shall be performed by the HLR. + +### 2.8.6 GMSC only supports Phase 1 call handling + +When a call is forwarded on busy, the HLR shall not pass the subaddress to a Phase 1 GMSC. Calls shall be forwarded without the subaddress. + +### 2.8.7 GMSC does not support CAMEL or supports CAMEL Phase 1 only + +If the activation state of CFB is "Active and Operative" and if the forwarded-to number is registered in a format other than international and if the GMSC does not support CAMEL or supports CAMEL Phase 1 only, then when a request for routing information for a mobile terminated call is received in the HLR, CFB shall not be invoked. The HLR shall return a busy subscriber error. + +## 2.9 Contents of messages + +The same additions apply for CFB as for CFU, see clause 1.9. The following additions are specific to CFB. + +### 2.9.1 Messages on the B interface (MSC-VLR) + +#### 2.9.1.1 Send Info For Incoming Call ack + +This message is specified in 3GPP TS 23.018. + +**Send Info For Incoming Call ack contains the following amendment to the Forwarded-to number IE, specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------| +| Forwarded-to number | M | Number of the C subscriber. | + +### 2.9.2 Messages on the D interface (VLR-HLR) + +#### 2.9.2.1 Insert Subscriber Data + +This message corresponds to the MAP-INSERT-SUBSCRIBER-DATA service specified in 3GPP TS 29.002. + +**Insert Subscriber Data contains the following IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|----------------------------------------------------------------------------------------------------------| +| Long forwarded-to number | C | Shall be present if the subscriber has a long forwarded-to number registered; otherwise shall be absent. | + +#### 2.9.2.2 Update Location + +This message corresponds to the MAP\_UPDATE\_LOCATION service specified in 3GPP TS 29.002. + +##### **Update Location contains the following IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|--------------------------------------------------------------------------------------------| +| Long FTN supported | C | Shall be present if the VLR supports Long Forwarded-to Numbers; otherwise shall be absent. | + +#### 2.9.2.3 Provide Roaming Number + +This message is specified in 3GPP TS 23.018. + +##### **Provide Roaming Number contains the following IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------------------------------------------------| +| Long FTN supported | C | Shall be present if the GMSC and the HLR both support Long Forwarded-to Numbers; otherwise shall be absent. | + +#### 2.9.2.4 Restore Data + +This message corresponds to the MAP\_RESTORE\_DATA service specified in 3G TS 29.002. + +##### **Restore Data contains the following IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|--------------------------------------------------------------------------------------------| +| Long FTN supported | C | Shall be present if the VLR supports Long Forwarded-to Numbers; otherwise shall be absent. | + +### 2.9.3 Messages on the E interface (VMSC-GMSC) + +#### 2.9.3.1 Resume Call Handling + +This message is specified in 3GPP TS 23.079. + +##### **Resume Call Handling contains the following amendment to the Forwarded-to number IE and an additional IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------| +| Forwarded-to number | C | E.164 number of the C subscriber. Shall be present if the VMSC does not support Long Forwarded-to Numbers; otherwise shall be absent. | +| Long forwarded-to number | C | Number of the C subscriber. Shall be present if the VMSC supports Long Forwarded-to Numbers; otherwise shall be absent. | + +### 2.9.4 Messages on the MSC internal interface + +#### 2.9.4.1 Perform Call Forwarding + +This message is specified in 3GPP TS 23.018. + +##### **Perform Call Forwarding contains the following amendment to the Forwarded-to number IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------| +| Forwarded-to number | M | Number of the C subscriber. | + +#### 2.9.4.2 Perform Call Forwarding ack + +This message is specified in 3GPP TS 23.018. + +##### **Perform Call Forwarding ack contains the following amendment to the Forwarded-to number IE specific to Long Forwarded-to Numbers:** + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Forwarded-to number | M | Number of the C subscriber.<br>NOTE: This number may be different from the Forwarded-to number received in the Perform Call Forwarding, as a result of CAMEL handling. | + +## 2.10 Support of Long Forwarded-to Numbers + +### 2.10.1 MS does not support Long Forwarded-to Numbers + +The handling for CFB is the same as that for CFU, see clause 1.10.1. + +### 2.10.2 HLR does not support Long Forwarded-to Numbers + +The handling for CFB is the same as that for CFU, see clause 1.10.2. + +### 2.10.3 GMSC does not support Long Forwarded-to Numbers + +The MSC/VLR can determine from the PRN whether the GMSC supports Long Forwarded-to Numbers. If the GMSC does not support Long Forwarded-to Numbers and a long forwarded-to number is registered for CFB, then on invocation of CFB, ORLCF shall not be invoked. + +### 2.10.4 MSC/VLR does not support Long Forwarded-to Numbers + +The handling for CFB in the HLR is the same as that for CFU, see clause 1.10.3. + +The VLR shall indicate whether it supports Long Forwarded-to Numbers in the Update Location and Restore Data messages to the HLR. If the VLR does not support Long Forwarded-to Numbers and a Long Forwarded-to Number is registered for CFB, then: + +- If a default forwarded-to number (containing a maximum of 15 digits) is stored in the HLR, the HLR shall send to the VLR an Insert Subscriber Data message containing the default forwarded-to number in the Forwarded-to number parameter. +- Otherwise, the HLR shall send the VLR the following service state information: + +(Provisioned, Not Registered, Not Active, Not Induced) + +For an MT call, if the following conditions are met then the HLR shall include the Forwarding interrogation required parameter in the first Send Routing Info ack: + +- The GMSC supports Optimal Routeing and Long Forwarded-to Numbers, and +- The MSC/VLR does not support Long Forwarded-to Numbers, and +- CFB is active and operative, and +- A long forwarded-to number is registered for CFB. + +According to the rules of Optimal Routeing, when the GMSC receives a Resume Call Handling message from the MSC/VLR, it shall send a second Send Routing Info message to the HLR allowing the HLR to insert the correct long forwarded-to number. + +# 3 Call forwarding on no reply + +## 3.1 Handling of call forwarding on no reply + +### 3.1.1 Registration + +The same rules apply for the registration of Call Forwarding on No Reply as were described for Call Forwarding Unconditional in clause 1.1.1 above, with the exceptions described below. Basic registration of information is illustrated in figure 3.2. + +#### The No Reply Condition Timer + +If a value for the no reply condition timer is not included in the registration request received from the MS, then the previous value set by the mobile user or the network operator applies. + +#### Supplementary Service Interaction + +Possible interaction situations between CFNRy and other supplementary services must then be checked. This is described in figure 3.2. Also see 3GPP TS 22.004 and 3GPP TS 22.082. For interaction between CFNRy and other supplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technical specification for those supplementary services. + +#### Interaction with CAMEL Phase 2 or higher + +Possible interaction between CFNRy and CAMEL Phase 2 or higher is described in figure 3.2. If CAMEL Phase 2 or higher is not supported in the HLR, processing continues from the "No" exit of the test "Result=Pass". + +The information flow for registration of call forwarding on no reply is shown in figure 3.1. + +![Sequence diagram showing the registration of call forwarding on no reply between MS, MSC, VLR, and HLR.](fc07df3b799d63e7e6c7760ca077ee99_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFNRy1 + + MS->>MSC: Register CFNRy + MSC->>VLR: Register CFNRy + VLR->>HLR: Register CFNRy + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility +``` + +The diagram illustrates the sequence of messages for registering Call Forwarding on No Reply (CFNRy). It involves four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence starts with the MS sending a 'Register CFNRy' message to the MSC. The MSC then forwards this to the VLR, which in turn sends it to the HLR. The HLR responds with an 'Acknowledge' message back to the VLR. The VLR then sends an 'Acknowledge' message back to the MSC. Finally, the MSC sends a 'Release complete' message back to the MS, with a note indicating '\Facility'. + +Sequence diagram showing the registration of call forwarding on no reply between MS, MSC, VLR, and HLR. + +Figure 3.1: Registration of call forwarding on no reply + +![Flowchart for Process CFNRy1: Call forwarding on no reply registration process. The process starts with 'idle', followed by 'register CNRy'. It then checks if 'BS included in request' is 'no' (leading to 'set BS = all BS') or 'yes'. The 'yes' path leads to 'CFNRy provided'. If 'no', it goes to connector '2'. If 'yes', it checks 'subset of required BS provided'. If 'no', it goes to connector '2'. If 'yes', it checks 'BAIC active'. If 'yes', it goes to connector '2'. If 'no', it checks 'BAOC active'. If 'yes', it goes to connector '2'. If 'no', it calls 'CAMEL Check_CF_Interaction' (See GSM 03.78). If 'Result=Pass?' is 'yes', it goes to connector '3'. If 'no', it checks 'valid ftn'. If 'no', it goes to connector '2'. If 'yes', it checks 'number type'. If 'national', it goes to connector '1'. If 'international', it calls 'convert to international (from HPLMN)' and then goes to connector '1'. The 'set BS = all BS' path also leads to connector '1'. Connector '1' leads to a decision 'BOIC active'. If 'yes', it goes to connector '3'. If 'no', it checks 'BOIC-exHC active'. If 'yes', it checks 'fin in VPLMN country'. If 'yes', it goes to connector '3'. If 'no', it checks 'fin in HPLMN country'. If 'yes', it goes to connector '3'. If 'no', it goes to 'set error'. If 'BOIC-exHC active' is 'no', it checks 'BIC-Roam active'. If 'yes', it checks 'no roaming outside HPLMN country'. If 'yes', it goes to connector '3'. If 'no', it goes to 'set error'. If 'BIC-Roam active' is 'no', it checks 'CFU active'. If 'yes', it goes to connector '3'. If 'no', it goes to 'set result'. Both 'set error' and 'set result' lead to 'acknowledge' and then 'idle'.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +Process CFNRy1 382\_32(1) + +``` + +graph TD + idle1([idle]) --> register[register CNRy] + register --> BS_incl{BS included in request} + BS_incl -- no --> set_BS[set BS = all BS] + BS_incl -- yes --> CFNRy_prov{CFNRy provided} + set_BS --> conn1((1)) + CFNRy_prov -- no --> conn2((2)) + CFNRy_prov -- yes --> subset{subset of required BS provided} + subset -- no --> conn2 + subset -- yes --> BAIC{BAIC active} + BAIC -- yes --> conn2 + BAIC -- no --> BAOC{BAOC active} + BAOC -- yes --> conn2 + BAOC -- no --> CAMEL[CAMEL Check_CF_Interaction] + CAMEL --> Result{Result=Pass?} + Result -- yes --> conn3((3)) + Result -- no --> valid{valid ftn} + valid -- no --> conn2 + valid -- yes --> num_type{number type} + num_type -- national --> conn1 + num_type -- international --> convert[convert to international from HPLMN] + convert --> conn1 + conn1 --> BOIC{BOIC active} + BOIC -- yes --> conn3 + BOIC -- no --> BOIC_exHC{BOIC-exHC active} + BOIC_exHC -- yes --> fin_V{fin in VPLMN country} + fin_V -- yes --> conn3 + fin_V -- no --> fin_H{fin in HPLMN country} + fin_H -- yes --> conn3 + fin_H -- no --> set_err1[set error] + BOIC_exHC -- no --> BIC_Roam{BIC-Roam active} + BIC_Roam -- yes --> no_roam{no roaming outside HPLMN country} + no_roam -- yes --> conn3 + no_roam -- no --> set_err2[set error] + BIC_Roam -- no --> CFU{CFU active} + CFU -- yes --> conn3 + CFU -- no --> set_res[set result] + set_err1 --> ack{acknowledge} + set_err2 --> ack + set_res --> ack + ack --> idle2([idle]) + +``` + +Not, e.g.: +- special service number; +- own number. + +BS: Basic Service group. + ftn: forwarded-to number. + BAOC: Barring of All Outgoing Calls. + BOIC: Barring of Outgoing International Calls. + BOIC-exHC: Barring of Outgoing International Calls except those directed to HPLMN Country. + BAIC: Barring of All Incoming Calls. + BIC-Roam: Barring of Incoming Calls when Roaming outside the home PLMN country. + +Flowchart for Process CFNRy1: Call forwarding on no reply registration process. The process starts with 'idle', followed by 'register CNRy'. It then checks if 'BS included in request' is 'no' (leading to 'set BS = all BS') or 'yes'. The 'yes' path leads to 'CFNRy provided'. If 'no', it goes to connector '2'. If 'yes', it checks 'subset of required BS provided'. If 'no', it goes to connector '2'. If 'yes', it checks 'BAIC active'. If 'yes', it goes to connector '2'. If 'no', it checks 'BAOC active'. If 'yes', it goes to connector '2'. If 'no', it calls 'CAMEL Check\_CF\_Interaction' (See GSM 03.78). If 'Result=Pass?' is 'yes', it goes to connector '3'. If 'no', it checks 'valid ftn'. If 'no', it goes to connector '2'. If 'yes', it checks 'number type'. If 'national', it goes to connector '1'. If 'international', it calls 'convert to international (from HPLMN)' and then goes to connector '1'. The 'set BS = all BS' path also leads to connector '1'. Connector '1' leads to a decision 'BOIC active'. If 'yes', it goes to connector '3'. If 'no', it checks 'BOIC-exHC active'. If 'yes', it checks 'fin in VPLMN country'. If 'yes', it goes to connector '3'. If 'no', it checks 'fin in HPLMN country'. If 'yes', it goes to connector '3'. If 'no', it goes to 'set error'. If 'BOIC-exHC active' is 'no', it checks 'BIC-Roam active'. If 'yes', it checks 'no roaming outside HPLMN country'. If 'yes', it goes to connector '3'. If 'no', it goes to 'set error'. If 'BIC-Roam active' is 'no', it checks 'CFU active'. If 'yes', it goes to connector '3'. If 'no', it goes to 'set result'. Both 'set error' and 'set result' lead to 'acknowledge' and then 'idle'. + +Figure 3.2: CFNRy1 Call forwarding on no reply registration process + +### 3.1.2 Erasure + +The same rules apply for the erasure of Call Forwarding on No Reply as were described for Call Forwarding Unconditional in clause 1.1.2 above. However, no checks for interaction with other supplementary services are required for erasure of CFNRy, see figures 3.3 and 3.4. + +![Sequence diagram showing the erasure of call forwarding on no reply (CFNRy) between MS, MSC, VLR, and HLR.](1ce027dfd26183da52137cf990213724_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFNRy2 + + MS-->>MSC: Erase CFNRy + MSC-->>VLR: Erase CFNRy + VLR-->>HLR: Erase CFNRy + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note right of MS: \Facility +``` + +Sequence diagram showing the erasure of call forwarding on no reply (CFNRy) between MS, MSC, VLR, and HLR. + +Figure 3.3: Erasure of call forwarding on no reply + +![Flowchart for Process CFNRy2 (382_34(1)) detailing the erasure process logic.](a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg) + +``` +graph TD + idle1([idle]) --> erase[erase CFNRy] + erase --> BS_included{BS included in request} + BS_included -- no --> set_BS[set BS = all BS] + set_BS --> CFNRy_provided{CFNRy provided} + BS_included -- yes --> CFNRy_provided + CFNRy_provided -- no --> set_error[set error] + CFNRy_provided -- yes --> set_result[set result] + set_error --> acknowledge{acknowledge} + set_result --> acknowledge + acknowledge --> idle2([idle]) +``` + +Process CFNRy2 382\_34(1) + +BS: Basic Service group. + +Flowchart for Process CFNRy2 (382\_34(1)) detailing the erasure process logic. + +Figure 3.4: CFNRy2 Call forwarding on no reply erasure process + +### 3.1.3 Activation + +The same rules apply for the activation of Call Forwarding on No Reply as were described for Call Forwarding Unconditional in clause 1.1.3 above, with the exception of the checking of interaction with other supplementary services. Basic activation of CFNRy is illustrated in figure 3.6. + +#### Supplementary Service Interaction + +Possible interaction situations between CFNRy and other supplementary services must then be checked. This is described in figure 3.6. Also see 3GPP TS 22.004 [2] and 3GPP TS 22.082 [3]. For interaction between CFNRy and other supplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technical specification for those supplementary services. + +CFNRy may be active simultaneously with ACR (see 3GPP TS 23.088 [12]). If CFNRy and ACR are active simultaneously, then the ACR supplementary service shall take precedence over the CFNRy service, i.e. a call which is terminated for the served subscriber when CLI presentation is restricted shall be rejected according to the ACR supplementary service. + +The information flow for activation of CFNRy is shown in figure 3.5. + +![Sequence diagram showing the activation of Call Forwarding on No Reply (CFNRy) between MS, MSC, VLR, and HLR.](9ed248b025d766251d58be10b01a1cc0_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFNRy3 + + MS->>MSC: Activate CFNRy + MSC->>VLR: Activate CFNRy + VLR->>HLR: Activate CFNRy + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility +``` + +The diagram illustrates the sequence of messages for activating Call Forwarding on No Reply (CFNRy). It involves four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence starts with the MS sending an 'Activate CFNRy' message to the MSC. The MSC then sends an 'Activate CFNRy' message to the VLR. The VLR sends an 'Activate CFNRy' message to the HLR. The HLR responds with an 'Acknowledge' message to the VLR. The VLR then sends an 'Acknowledge' message to the MSC. Finally, the MSC sends a 'Release complete' message to the MS, which includes a '\Facility' parameter. + +Sequence diagram showing the activation of Call Forwarding on No Reply (CFNRy) between MS, MSC, VLR, and HLR. + +**Figure 3.5: Activation of call forwarding on no reply** + +![Flowchart for Process CFNRy3: Call forwarding on no reply activation process. The process starts at 'idle', goes to 'activate CFNRy', then checks if CFNRy is registered for the required BS. If no, it goes to 'set error'. If yes, it checks if BAIC is active. If yes, it goes to 'set error'. If no, it checks if BOIC-Roam is active. If yes, it goes to 'set error'. If no, it checks if BOIC is active. If yes, it goes to 'set error'. If no, it checks if BOIC-exHC is active. If yes, it checks if ftn is in VPLMN country. If yes, it goes to 'set error'. If no, it checks if ftn is in HPLMN country. If yes, it goes to 'set error'. If no, it checks if CFU is active. If yes, it goes to 'set error'. If no, it goes to 'set result'. All 'set error' blocks lead to 'acknowledge'. 'set result' also leads to 'acknowledge'. 'acknowledge' leads to 'idle'.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +**Process CFNRy3** 382\_36(1) + +BS: Basic Service group. +ftn: forwarded-to number. +BAOC: Barring of All Outgoing Calls. +BOIC: Barring of Outgoing International Calls. +BOIC-exHC: Barring of Outgoing International Calls except those directed to HPLMN Country. +BAIC: Barring of All Incoming Calls. + +``` +graph TD; idle1([idle]) --> activate[activate CFNRy]; activate --> reg{CFNRy registered for required BS}; reg -- no --> set_err1[set error]; reg -- yes --> baic{BAIC active}; baic -- yes --> set_err2[set error]; baic -- no --> roam{BOIC-Roam active}; roam -- yes --> set_err3[set error]; roam -- no --> boic{BOIC active}; boic -- yes --> set_err4[set error]; boic -- no --> exhc{BOIC-exHC active}; exhc -- yes --> ftn_v{ftn in VPLMN country}; exhc -- no --> ftn_h{ftn in HPLMN country}; ftn_v -- yes --> set_err5[set error]; ftn_v -- no --> ftn_h; ftn_h -- yes --> set_err6[set error]; ftn_h -- no --> cfu{CFU active}; cfu -- yes --> set_err7[set error]; cfu -- no --> set_res[set result]; set_err1 --> ack{acknowledge}; set_err2 --> ack; set_err3 --> ack; set_err4 --> ack; set_err5 --> ack; set_err6 --> ack; set_err7 --> ack; set_res --> ack; ack --> idle2([idle]); +``` + +Flowchart for Process CFNRy3: Call forwarding on no reply activation process. The process starts at 'idle', goes to 'activate CFNRy', then checks if CFNRy is registered for the required BS. If no, it goes to 'set error'. If yes, it checks if BAIC is active. If yes, it goes to 'set error'. If no, it checks if BOIC-Roam is active. If yes, it goes to 'set error'. If no, it checks if BOIC is active. If yes, it goes to 'set error'. If no, it checks if BOIC-exHC is active. If yes, it checks if ftn is in VPLMN country. If yes, it goes to 'set error'. If no, it checks if ftn is in HPLMN country. If yes, it goes to 'set error'. If no, it checks if CFU is active. If yes, it goes to 'set error'. If no, it goes to 'set result'. All 'set error' blocks lead to 'acknowledge'. 'set result' also leads to 'acknowledge'. 'acknowledge' leads to 'idle'. + +Figure 3.6: CFNRy3 Call forwarding on no reply activation process + +### 3.1.4 Deactivation + +The same rules apply for the deactivation of CFNRy as were described for CFU in clause 1.1.4 above, see figure 3.7 and 3.8. + +![Sequence diagram showing the deactivation of call forwarding on no reply (CFNRy) between MS, MSC, VLR, and HLR.](aeb2a26a07219661191294dba528067a_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFNRy4 + MS-->>MSC: Deactivate CFNRy + MSC-->>VLR: Deactivate CFNRy + VLR-->>HLR: DeactivateCFNRy + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility +``` + +Sequence diagram showing the deactivation of call forwarding on no reply (CFNRy) between MS, MSC, VLR, and HLR. + +Figure 3.7: Deactivation of call forwarding on no reply + +![Flowchart for the CFNRy4 Call forwarding on no reply deactivation process.](adc59ed6840bcb2d392ea323abfccedc_img.jpg) + +``` +graph TD + idle1([idle]) --> deactivate[deactivate CFNRy] + deactivate --> BS_included{BS included in request} + BS_included -- no --> set_BS[set BS = all BS] + set_BS --> BS_included + BS_included -- yes --> CFNRy_active{CFNRy active for subset BS} + CFNRy_active -- no --> set_error[set error] + CFNRy_active -- yes --> set_result[set result] + set_error --> acknowledge{acknowledge} + set_result --> acknowledge + acknowledge --> idle2([idle]) +``` + +Flowchart for the CFNRy4 Call forwarding on no reply deactivation process. + +Figure 3.8: CFNRy4 Call forwarding on no reply deactivation process + +### 3.1.5 Interrogation + +#### Data request + +The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. Interrogation of CFNRy is handled by the VLR which returns the required information or error to the MS, see figure 3.9. + +![Sequence diagram showing the interrogation of call forwarding on no reply (CFNRy). The diagram involves four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate CFNRy' to MSC. 2. MSC sends 'Interrogate CFNRy' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release complete' back to MS, with a sub-parameter '\Facility'.](c0c7f65c51c83fbe595b47326f6b089a_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note left of MS: Data request + MS->>MSC: Interrogate CFNRy + MSC->>VLR: Interrogate CFNRy + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note right of MS: \Facility +``` + +Sequence diagram showing the interrogation of call forwarding on no reply (CFNRy). The diagram involves four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate CFNRy' to MSC. 2. MSC sends 'Interrogate CFNRy' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release complete' back to MS, with a sub-parameter '\Facility'. + +Figure 3.9: Interrogation of call forwarding on no reply + +## 3.2 Functions and information flows + +The following Mobile Additional Function has been identified for the PLMN: + +#### MAF009 + +#### Call forwarding on no reply authorizations examination + +The ability of a PLMN component to determine the authorizations relating to call forwarding on no reply. See figure 3.10. + +Location: VLR. + +The information flows for forwarding to fixed terminal and to mobile station are shown in figures 3.11 and 3.12 respectively. + +![Flowchart for Process MAF009: Call forwarding on no reply authorisations examination (VLR).](0a73b03fba21af142d619a9a662e6490_img.jpg) + +Process MAF009 + +382\_3A(1) + +BS : Basic Service group. + +``` + +graph TD + Start([idle]) --> Init[/initiate handling +of CFNRy/] + Init --> Active{active +for this +BS} + Active -- no --> EndIndicator[set indicator = +'set up +normal call'] + Active -- yes --> Reached{number +of forwardings +reached} + Reached -- yes --> SetError[set +error] + Reached -- no --> Increment[increment counter +get forwarded-to number +set forwarding cause=CFNRy +set no reply condition timer] + Increment --> NotifyForwarding{notification +to forwarding +subscriber} + NotifyForwarding -- yes --> IndicatorForwarding[set indicator = +'notify forwarding +subscriber'] + NotifyForwarding -- no --> NotifyCalling{notification +to calling +subscriber} + NotifyCalling -- yes --> IndicatorCalling[set indicator = +'notify calling +subscriber'] + IndicatorForwarding --> MSISDN{served +subscribers MSISDN +can be presented} + IndicatorCalling --> MSISDN + NotifyCalling -- no --> MSISDN + MSISDN -- yes --> Allowed[set redirecting +presentation = +allowed] + MSISDN -- no --> Restricted[set redirecting +presentation = +restricted] + SetError --> Continue[continue +call +handling] + Allowed --> Continue + Restricted --> Continue + EndIndicator --> Continue + Continue --> Idle([idle]) + +``` + +Flowchart for Process MAF009: Call forwarding on no reply authorisations examination (VLR). + +**Figure 3.10: MAF009 Call forwarding on no reply authorisations examination (VLR)** + +![Sequence diagram showing information flow for call forwarding on no reply to a fixed terminal. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, LEc. The process involves Set-up, Info req/ack, timer expiration, and subsequent Release and Notification messages.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant LEc + + Note left of MSa/TEa: MAF009 + + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb-->>GMSC: Info ack + GMSC->>MSCb: Set-up + MSCb->>VLRb: Info req + VLRb-->>MSCb: Info ack + Note right of MSCb: start timer + Note right of MSCb: timer expires + MSCb->>VLRb: Info req + VLRb-->>MSCb: Impossible call completion + Note right of MSCb: OR1:N + MSCb->>GMSC: Release + GMSC-->>MSa/TEa: Release + VLRb->>MSCb: Connect to following address + Note right of VLRb: OR1:Y + MSCb->>MSb: Set-up + Note right of MSCb: OR2:Y + Note right of MSCb: OR3:Y + MSCb->>MSb: Notif + GMSC-->>MSa/TEa: Notification + MSa/TEa-->>GMSC: Notif + +``` + +Sequence diagram showing information flow for call forwarding on no reply to a fixed terminal. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, LEc. The process involves Set-up, Info req/ack, timer expiration, and subsequent Release and Notification messages. + +NOTE: info: information Y: Yes + req: request N: No + ack: acknowledge + notif: notification + conf: confirmation + OR1: Call to be forwarded + OR2: Notification to forwarding subscriber required + OR3: Notification to calling subscriber required + +**Figure 3.11: Information flow for call forwarding on no reply + (to fixed terminal)** + +![Sequence diagram showing information flow for call forwarding on no reply to mobile station. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, HLRc, MSCc. The process involves Set-up, Info req/ack, Release, Connect to following address, Info request/acknowledge, and final Set-up and Notification messages.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant HLRc + participant MSCc + + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb-->>GMSC: Info ack + GMSC->>MSCb: Set-up + Note over VLRb,MSCb: MAF009 + VLRb->>MSCb: Info req + MSCb-->>VLRb: Info ack + MSCb->>MSb: Set-up + Note right of MSb: start timer + MSb-->>MSCb: Call conf + Note right of MSCb: timer expires + MSCb->>VLRb: Info req + Note over VLRb,MSCb: impossible call completion + Note over VLRb,MSCb: OR1:N + GMSC-->>MSa/TEa: Release + HLRb-->>GMSC: Release + Note over VLRb,MSCb: Connect to following address + Note over VLRb,MSCb: OR1:Y + VLRb->>MSCb: Connect to following address + MSCb->>HLRc: Info request + HLRc-->>MSCb: Info acknowledge + MSCb->>MSCc: Set-up + MSCb->>MSb: Notif + Note over MSCb: OR2:Y + MSCb->>MSa/TEa: Notification + Note over MSCb: OR3:Y + MSa/TEa-->>GMSC: Notif + +``` + +Sequence diagram showing information flow for call forwarding on no reply to mobile station. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, HLRc, MSCc. The process involves Set-up, Info req/ack, Release, Connect to following address, Info request/acknowledge, and final Set-up and Notification messages. + +NOTE:   info:   information            Y: Yes +             req:   request                    N: no +             ack:   acknowledge +             notif: notification +             conf: confirmation +             OR1: Call to be forwarded +             OR2: Notification to forwarding subscriber required +             OR3: Notification to calling subscriber required + +**Figure 3.12: Information flow for call forwarding on no reply + (to mobile station)** + +## 3.3 Information stored in the HLR + +The following logical states are applicable for CFNRy (refer to 3GPP TS 23.011 for an explanation of the notation): + +| <b>Provisioning State</b> | <b>Registration State</b> | <b>Activation State</b> | <b>HLR Induction State</b> | +|---------------------------|---------------------------|-------------------------|----------------------------| +| (Not Provisioned, | Not Registered, | Not Active, | Not Induced) | +| (Provisioned, | Not Registered, | Not Active, | Not Induced) | +| (Provisioned, | Registered, | Not Active, | Not Induced) | +| (Provisioned, | Registered, | Active and Quiescent, | Not Induced) | +| (Provisioned, | Registered, | Active and Operative, | Not Induced) | + +The registration and activation state may be different for each applicable elementary basic service group. + +The provisioning state shall be on a per subscriber basis, and hence the same for all basic service groups. + +The HLR shall store: + +- the state of CFNRy (which shall be one of the valid states listed above) for each applicable elementary basic service group; +- the subscription option "notification to the calling party" on a per subscriber basis; + +This subscription option takes one of the following values: + +- no notification; +- notification. +- the subscription option "notification to the forwarding party" on a per subscriber basis; + +This subscription option takes one of the following values: + +- no notification; +- notification. +- the subscription option "MSISDN of the served subscriber can be presented to the forwarded-to subscriber" on a per subscriber basis; + +This subscription option takes one of the following values: + +- presentation restricted; +- presentation allowed. +- the registration parameter "forwarded-to number" (possibly including a forwarded-to sub-address) for each applicable elementary basic service group; +- the registration parameter "no reply condition timer" for each applicable elementary basic service group. + +This parameter may take values in the range 5 - 30 seconds in steps of 5 seconds. + +- the default forwarded-to number (containing less than 16 digits) for each applicable elementary basic service group. + +## 3.4 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of CFNRy. The state changes are either caused by actions of the service provider, the mobile user or the network. + +Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence, they are not shown in the diagram. The diagram only shows operations on an elementary basic service group. + +![State transition model for CFNRy. The diagram shows four states and their transitions. State 1 (top): (Not Provisioned, Not Registered, Not Active, Not Induced). State 2 (left): (Provisioned, Not Registered, Not Active, Not Induced). State 3 (right): (Provisioned, Registered, Active and Quiescent, Not Induced). State 4 (bottom): (Provisioned, Registered, Not Active, Not Induced). State 5 (bottom right): (Provisioned, Registered, Active and Operative, Not Induced). Transitions: Withdrawal from State 1 to State 2 and State 3. Provision from State 2 to State 1. Withdrawal from State 2 to State 1. Erasure from State 3 to State 2. Registration from State 4 to State 3. Erasure from State 4 to State 2. Deactivation from State 4 to State 1. Activation from State 4 to State 5. SS Interaction ended from State 5 to State 3. SS Interaction started from State 3 to State 5. Deactivation from State 5 to State 1.](e417ae35ab07134888be901c201d54cd_img.jpg) + +``` + +stateDiagram-v2 + [*] --> S1 : (Not Provisioned, Not Registered, Not Active, Not Induced) + S1 --> S2 : Withdrawal + S2 --> S1 : Provision + S2 --> S1 : Withdrawal + S3 --> S2 : Erasure + S4 --> S3 : Registration + S4 --> S2 : Erasure + S4 --> S1 : Deactivation + S4 --> S5 : Activation + S5 --> S3 : SS Interaction ended + S3 --> S5 : SS Interaction started + S5 --> S1 : Deactivation + +``` + +State transition model for CFNRy. The diagram shows four states and their transitions. State 1 (top): (Not Provisioned, Not Registered, Not Active, Not Induced). State 2 (left): (Provisioned, Not Registered, Not Active, Not Induced). State 3 (right): (Provisioned, Registered, Active and Quiescent, Not Induced). State 4 (bottom): (Provisioned, Registered, Not Active, Not Induced). State 5 (bottom right): (Provisioned, Registered, Active and Operative, Not Induced). Transitions: Withdrawal from State 1 to State 2 and State 3. Provision from State 2 to State 1. Withdrawal from State 2 to State 1. Erasure from State 3 to State 2. Registration from State 4 to State 3. Erasure from State 4 to State 2. Deactivation from State 4 to State 1. Activation from State 4 to State 5. SS Interaction ended from State 5 to State 3. SS Interaction started from State 3 to State 5. Deactivation from State 5 to State 1. + +Figure 3.13: State transition model for CFNRy + +## 3.5 Transfer of information from HLR to VLR + +If the provisioning state for CFNRy is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of CFNRy for all relevant elementary basic service groups. + +If the registration state for CFNRy is "Registered" then, when the subscriber registers on a VLR, the HLR shall send that VLR the registration parameter "forwarded-to number" and "no reply condition timer" for all relevant elementary basic service groups and information about the subscription options "notification to the calling party", "notification to the forwarding party" and "MSISDN of the served subscriber can be presented to the forwarded-to subscriber". + +If the logical state, the registration parameter "forwarded-to number" or the registration parameter "no reply condition timer" of CFNRy is changed while a subscriber is registered on a VLR then for the affected basic service groups, the HLR shall inform the VLR respectively of the new logical state or the new registration parameter of CFNRy. + +If information about the subscription options "notification to the calling party" and "notification to the forwarding party" of CFNRy is changed while a subscriber is registered on a VLR and the registration state of CFNRy is "Registered" then the HLR shall inform the VLR of the new information about the subscription options of CFNRy. + +## 3.6 Information stored in the VLR + +For CFNRy the VLR shall store the service state information, the registration parameter "forward-to number", the registration parameter "no reply condition timer" and the subscription options received from the HLR. + +## 3.7 Handover + +Handover will have no impact on the control procedure and the operation of the service. + +## 3.8 Cross phase compatibility + +### 3.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber + +In response to a CFNRy interrogation request, if the MS or any network element involved is of Phase 1, only information concerning basic service groups for which the activation state has the value "Active and Operative" will be returned. This means that the subscriber will not be aware that the forwarded to number is registered if CFNRy is deactivated or active (quiescent). A subaddress (if registered) will not be included. + +Note that if any network element involved is of Phase 1, CFNRy Registration requests which use a subaddress and all CFNRy Activation and Deactivation requests will be rejected, as these are not specified in Phase 1. + +### 3.8.2 HLR only supports Phase 1 updating of subscriber information + +If the VLR receives the SS-Status parameter from a Phase 1 HLR it shall act if it has received the SS-Status parameter with the values shown in the following: + +- 1) Registered, Activated => P bit =1, R bit = 1, A bit = 1, Q bit = 0; +- 2) Registered, Deactivated => P bit =1, R bit = 1, A bit = 0, Q bit = 0 or 1; +- 3) Erased=> P bit =1, R bit = 0, A bit = 0, Q bit = 0 or 1. + +### 3.8.3 VLR only supports Phase 1 updating of subscriber information + +When passing CFNRy information to a Phase 1 VLR, the HLR shall send the service state information in a form which the VLR can accept, based on the logical state held in the HLR, as follows: + +- 1) (Provisioned, Not Registered, Not Active, Not Induced) +=> Erased, Deactivated; +- 2) (Provisioned, Registered, Not Active, Not Induced) +=> Registered, Deactivated; +- 3) (Provisioned, Registered, Active and Operative, Not Induced) +=> Registered, Activated; +- 4) (Provisioned, Registered, Active and Quiescent, Not Induced) +=> Registered, Deactivated. + +The HLR shall not pass a subaddress to a Phase 1 VLR. + +### 3.8.4 VLR only supports Phase 1 call handling + +When a call is forwarded on no reply, as the HLR does not pass the subaddress to the VLR, calls shall be forwarded without the subaddress. + +### 3.8.5 VLR does not support CAMEL or supports CAMEL Phase 1 only + +When passing CFNRy information to a VLR not supporting CAMEL or supporting CAMEL Phase 1 only, the HLR shall send the registration parameter "forwarded-to number" only if it is registered in a format which the VLR can accept, i.e. international format. + +If the registration state for CFNRy is "Registered" and the forwarded-to number is registered in a format other than international, then when updating a VLR not supporting CAMEL or supporting CAMEL Phase 1 only the HLR shall modify the service state information of CFNRy as follows. + +- 1) (Provisioned, Registered, Not Active, Not Induced) +=> (Provisioned, Not Registered, Not Active, Not Induced) +- 2) (Provisioned, Registered, Active and Operative, Not Induced) +=> (Provisioned, Not Registered, Not Active, Not Induced) +- 3) (Provisioned, Registered, Active and Quiescent, Not Induced) +=> (Provisioned, Not Registered, Not Active, Not Induced) + +According to the definitions in clause 3.5 no forwarded-to number will be passed to the VLR in these cases. The modification of the service state information sent to the VLR shall have no impact on the service state information stored in the HLR. + +If the VLR supports Phase 1 updating of subscriber information only, a further translation of the service state information as defined in clause 3.8.3 shall be performed by the HLR. + +## 3.9 Contents of messages + +The same additions apply for CFNRy as for CFB, see clause 2.9 (additions to Send Routing Info and Send Routing Info ack are not used in this case). + +## 3.10 Support of Long Forwarded-to Numbers + +The handling for early CFNRc is the same as that for CFU, see clause 1.10. + +The handling for late CFNRy is the same as that for CFB, see clause 2.10. + +# --- 4 Call forwarding on mobile subscriber not reachable + +## 4.1 Handling of call forwarding on mobile subscriber not reachable + +### 4.1.1 Registration + +The same rules apply for the registration of Call Forwarding on Mobile Subscriber Not Reachable as were described for Call Forwarding Unconditional in clause 1.1.1 above, with the exception of the checking of interaction with other supplementary services. Basic registration of information is illustrated in figure 4.2. + +#### Supplementary Service Interaction + +Possible interaction situations between CFNRc and other supplementary services must then be checked. This is described in figure 4.2. Also see 3GPP TS 22.004 and 3GPP TS 22.082. For interaction between CFNRc and other supplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technical specification for those supplementary services. + +#### Interaction with CAMEL Phase 2 or higher + +Possible interaction between CFNRc and CAMEL Phase 2 or higher is described in figure 4.2. If CAMEL Phase 2 or higher is not supported in the HLR, processing continues from the "No" exit of the test "Result=Pass". + +The information flow for registration of call forwarding on mobile subscriber not reachable is shown in figure 4.1. + +![Sequence diagram showing the registration of call forwarding on a mobile subscriber not reachable. Lifelines: MS, MSC, VLR, HLR. The MS sends a 'Register CFNRc' message to the MSC. The MSC then sends 'Register CFNRc' to the VLR, which in turn sends 'Register CFNRc' to the HLR. The HLR returns 'CFNRc1' to the VLR. The VLR sends an 'Acknowledge' message back to the MSC. Finally, the MSC sends a 'Release complete' message with a '\Facility' parameter back to the MS.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note left of MS: + MS->>MSC: Register CFNRc + MSC->>VLR: Register CFNRc + VLR->>HLR: Register CFNRc + HLR-->>VLR: CFNRc1 + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete +\Facility +``` + +Sequence diagram showing the registration of call forwarding on a mobile subscriber not reachable. Lifelines: MS, MSC, VLR, HLR. The MS sends a 'Register CFNRc' message to the MSC. The MSC then sends 'Register CFNRc' to the VLR, which in turn sends 'Register CFNRc' to the HLR. The HLR returns 'CFNRc1' to the VLR. The VLR sends an 'Acknowledge' message back to the MSC. Finally, the MSC sends a 'Release complete' message with a '\Facility' parameter back to the MS. + +**Figure 4.1: Registration of call forwarding on mobile subscriber not reachable** + +![Flowchart for Process CFNRc1: Call forwarding on mobile subscriber not reachable registration process. The process starts with 'idle', followed by 'register CFNRc'. It then checks if the BS is included in the request. If no, it sets BS = all BS. If yes, it checks if CFNRc is provided. If no, it goes to connector 2. If yes, it checks if a subset of required BS is provided. If no, it goes to connector 2. If yes, it checks if BAIC is active. If yes, it goes to connector 2. If no, it checks if BAOC is active. If yes, it goes to connector 2. If no, it calls CAMEL Check_CF_Interaction (See GSM 03.78). If Result = Pass? is yes, it goes to connector 3. If no, it checks if the ftn is valid (Not, e.g.: - special service number; - own number.). If no, it goes to connector 2. If yes, it checks the number type (national or international). If international, it converts to international from HPLMN. Both national and international paths lead to connector 1. Connector 1 leads to a decision 'BOIC active'. If yes, it goes to connector 3. If no, it checks 'BOIC-exHC active'. If yes, it checks 'fin in VPLMN country'. If yes, it goes to connector 3. If no, it checks 'fin in HPLMN country'. If yes, it goes to connector 3. If no, it sets error. If 'BOIC-exHC active' is no, it checks 'BIC-Roam active'. If yes, it checks 'no roaming outside HPLMN country'. If yes, it goes to connector 3. If no, it sets error. If 'BIC-Roam active' is no, it checks 'CFU active'. If yes, it sets result. If no, it sets error. All three error and result paths merge and lead to 'acknowledge', which then leads to 'idle'. A legend defines BS, ftn, BAOC, BOIC, BOIC-exHC, BAIC, and BIC-Roam.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +Process CFNRc1 382\_42(1) + +``` + +graph TD + idle1([idle]) --> register[register CFNRc] + register --> BS_incl{BS included in request} + BS_incl -- no --> set_BS[set BS = all BS] + set_BS --> CFNRc_prov{CFNRc provided} + BS_incl -- yes --> CFNRc_prov + CFNRc_prov -- no --> conn2((2)) + CFNRc_prov -- yes --> subset{subset of required BS provided} + subset -- no --> conn2 + subset -- yes --> BAIC{BAIC active} + BAIC -- yes --> conn2 + BAIC -- no --> BAOC{BAOC active} + BAOC -- yes --> conn2 + BAOC -- no --> CAMEL[CAMEL Check_CF_Interaction] + CAMEL --> Result{Result = Pass?} + Result -- yes --> conn3((3)) + Result -- no --> valid_ftn{valid ftn} + valid_ftn -- no --> conn2 + valid_ftn -- yes --> number_type{number type} + number_type -- national --> conn1((1)) + number_type -- international --> convert[convert to international from HPLMN] + convert --> conn1 + conn1 --> BOIC{BOIC active} + BOIC -- yes --> conn3 + BOIC -- no --> BOIC_exHC{BOIC-exHC active} + BOIC_exHC -- yes --> fin_V{fin in VPLMN country} + fin_V -- yes --> conn3 + fin_V -- no --> fin_H{fin in HPLMN country} + fin_H -- yes --> conn3 + fin_H -- no --> set_error1[set error] + BOIC_exHC -- no --> BIC_Roam{BIC-Roam active} + BIC_Roam -- yes --> no_roam{no roaming outside HPLMN country} + no_roam -- yes --> conn3 + no_roam -- no --> set_error2[set error] + BIC_Roam -- no --> CFU{CFU active} + CFU -- yes --> set_result[set result] + CFU -- no --> set_error3[set error] + set_error1 --> merge1(( )) + set_error2 --> merge1 + set_error3 --> merge1 + merge1 --> acknowledge{{acknowledge}} + acknowledge --> idle2([idle]) + +``` + +Not, e.g.: + +- special service number; +- own number. + +BS: Basic Service group. + ftn: forwarded-to number. + BAOC: Barring of All Outgoing Calls. + BOIC: Barring of Outgoing International Calls. + BOIC-exHC: Barring of Outgoing International Calls except those directed to HPLMN Country. + BAIC: Barring of All Incoming Calls. + BIC-Roam: Barring of Incoming Calls when Roaming outside the home PLMN country. + +Flowchart for Process CFNRc1: Call forwarding on mobile subscriber not reachable registration process. The process starts with 'idle', followed by 'register CFNRc'. It then checks if the BS is included in the request. If no, it sets BS = all BS. If yes, it checks if CFNRc is provided. If no, it goes to connector 2. If yes, it checks if a subset of required BS is provided. If no, it goes to connector 2. If yes, it checks if BAIC is active. If yes, it goes to connector 2. If no, it checks if BAOC is active. If yes, it goes to connector 2. If no, it calls CAMEL Check\_CF\_Interaction (See GSM 03.78). If Result = Pass? is yes, it goes to connector 3. If no, it checks if the ftn is valid (Not, e.g.: - special service number; - own number.). If no, it goes to connector 2. If yes, it checks the number type (national or international). If international, it converts to international from HPLMN. Both national and international paths lead to connector 1. Connector 1 leads to a decision 'BOIC active'. If yes, it goes to connector 3. If no, it checks 'BOIC-exHC active'. If yes, it checks 'fin in VPLMN country'. If yes, it goes to connector 3. If no, it checks 'fin in HPLMN country'. If yes, it goes to connector 3. If no, it sets error. If 'BOIC-exHC active' is no, it checks 'BIC-Roam active'. If yes, it checks 'no roaming outside HPLMN country'. If yes, it goes to connector 3. If no, it sets error. If 'BIC-Roam active' is no, it checks 'CFU active'. If yes, it sets result. If no, it sets error. All three error and result paths merge and lead to 'acknowledge', which then leads to 'idle'. A legend defines BS, ftn, BAOC, BOIC, BOIC-exHC, BAIC, and BIC-Roam. + +Figure 4.2: CFNRc1 Call forwarding on mobile subscriber not reachable registration process + +### 4.1.2 Erasure + +The same rules apply for the erasure of CFNRc as were described for CFU in clause 1.1.2 above. However, no checks for interaction with other supplementary services are required for erasure of CFNRc, see figure 4.4. + +The information flow for registration of CFNRc is shown in figure 4.3. + +![Sequence diagram showing the information flow for erasure of call forwarding on a mobile subscriber not reachable. Lifelines: MS, MSC, VLR, HLR. The sequence starts with MS sending 'Erase CFNRc' to MSC. MSC sends 'Erase CFNRc' to VLR. VLR sends 'Erase CFNRc' to HLR. HLR returns 'CFNRc2' to VLR. VLR sends 'Acknowledge' to MSC. MSC sends 'Release complete' with '\Facility' to MS.](a4bfa2343d75076b79f7e33d93915e00_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFNRc2 + MS-->>MSC: Erase CFNRc + MSC-->>VLR: Erase CFNRc + VLR-->>HLR: Erase CFNRc + HLR-->>VLR: CFNRc2 + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note right of MS: \Facility +``` + +Sequence diagram showing the information flow for erasure of call forwarding on a mobile subscriber not reachable. Lifelines: MS, MSC, VLR, HLR. The sequence starts with MS sending 'Erase CFNRc' to MSC. MSC sends 'Erase CFNRc' to VLR. VLR sends 'Erase CFNRc' to HLR. HLR returns 'CFNRc2' to VLR. VLR sends 'Acknowledge' to MSC. MSC sends 'Release complete' with '\Facility' to MS. + +Figure 4.3: Erasure of call forwarding on mobile subscriber not reachable + +![Flowchart for Process CFNRc2, labeled 382_44(1). It starts at an 'idle' state, proceeds to 'erase CFNRc', then checks if 'BS included in request'. If 'no', it goes to 'set BS = all BS' and then to the next decision. If 'yes', it goes directly to the next decision. The next decision is 'CFNRc provided'. If 'no', it goes to 'set error'. If 'yes', it goes to 'set result'. Both 'set error' and 'set result' lead to 'acknowledge', which then returns to the 'idle' state. A note indicates 'BS: Basic Service group.'](31ef15d175af5babdbf4d2fbac884c1b_img.jpg) + +``` +graph TD + idle1([idle]) --> erase[erase CFNRc] + erase --> BS_incl{BS included in request} + BS_incl -- no --> set_BS[set BS = all BS] + set_BS --> CFNRc_prov{CFNRc provided} + BS_incl -- yes --> CFNRc_prov + CFNRc_prov -- no --> set_err[set error] + CFNRc_prov -- yes --> set_res[set result] + set_err --> ack{acknowledge} + set_res --> ack + ack --> idle2([idle]) + note right of idle1: BS: Basic Service group. +``` + +Flowchart for Process CFNRc2, labeled 382\_44(1). It starts at an 'idle' state, proceeds to 'erase CFNRc', then checks if 'BS included in request'. If 'no', it goes to 'set BS = all BS' and then to the next decision. If 'yes', it goes directly to the next decision. The next decision is 'CFNRc provided'. If 'no', it goes to 'set error'. If 'yes', it goes to 'set result'. Both 'set error' and 'set result' lead to 'acknowledge', which then returns to the 'idle' state. A note indicates 'BS: Basic Service group.' + +Figure 4.4: CFNRc2 Call forwarding on mobile subscriber not reachable erasure process + +### 4.1.3 Activation + +The same rules apply for the activation of CFNRc as were described for CFU in clause 1.1.3 above, with the exception of the checking of interaction with other supplementary services. Basic activation of CFNRc is illustrated in figure 4.6. + +#### Supplementary Service Interaction + +Possible interaction situations between CFNRc and other supplementary services must then be checked. This is described in figure 4.6. Also see 3GPP TS 22.004 [2] and 3GPP TS 22.082 [3]. For interaction between CFNRc and other supplementary services (i.e. not call barring or call forwarding services), the reader is referred to the respective technical specification for those supplementary services. + +CFNRc may be active simultaneously with ACR (see 3GPP TS 23.088 [12]). If CFNRc and ACR are active simultaneously, then the ACR supplementary service shall take precedence over the CFNRc service, i.e. a call which is terminated for the served subscriber when CLI presentation is restricted shall be rejected according to the ACR supplementary service. + +The information flow for activation of call forwarding on MS not reachable is shown in figure 4.5. + +![Sequence diagram showing the activation of call forwarding on MS not reachable. The diagram involves four lifelines: MS, MSC, VLR, and HLR. The sequence starts with the MS sending an 'Activate CFNRc' message to the MSC. The MSC then sends an 'Activate CFNRc' message to the VLR. The VLR sends an 'Activate CFNRc' message to the HLR. The HLR responds with 'CFNRc3'. The VLR then sends an 'Acknowledge' message back to the MSC. Finally, the MSC sends a 'Release complete' message to the MS, with a sub-parameter '\Facility'.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + MS->>MSC: Activate CFNRc + MSC->>VLR: Activate CFNRc + VLR->>HLR: Activate CFNRc + HLR-->>VLR: CFNRc3 + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note over MS,MSC: \Facility + +``` + +Sequence diagram showing the activation of call forwarding on MS not reachable. The diagram involves four lifelines: MS, MSC, VLR, and HLR. The sequence starts with the MS sending an 'Activate CFNRc' message to the MSC. The MSC then sends an 'Activate CFNRc' message to the VLR. The VLR sends an 'Activate CFNRc' message to the HLR. The HLR responds with 'CFNRc3'. The VLR then sends an 'Acknowledge' message back to the MSC. Finally, the MSC sends a 'Release complete' message to the MS, with a sub-parameter '\Facility'. + +Figure 4.5: Activation of call forwarding on MS not reachable + +![Flowchart titled 'Process CFNRc3' detailing the activation process for call forwarding on a mobile subscriber not reachable. The process starts at an 'idle' state, followed by an 'activate CFNRc' input. A decision diamond 'CFNRc registered for required BS' follows. If 'no', it goes to 'set error'. If 'yes', it checks 'BAIC active'. If 'yes', it goes to 'set result'. If 'no', it checks 'BIC-Roam active'. If 'yes', it goes to 'set result'. If 'no', it checks 'roaming outside HPLMN country'. If 'no', it checks 'BAOC active'. If 'yes', it goes to 'set result'. If 'no', it checks 'BOIC active'. If 'yes', it goes to 'set result'. If 'no', it checks 'BOIC-exHC active'. If 'yes', it checks 'ftn in VPLMN country'. If 'no', it checks 'ftn in HPLMN country'. If 'yes', it goes to 'set result'. If 'no', it goes to 'set error'. Finally, it reaches an 'acknowledge' state and returns to 'idle'.](742a5484e7dd016256ab99921bbd635d_img.jpg) + +Process CFNRc3 382\_46(1) + +``` + +graph TD + Start([idle]) --> Input[/activate CFNRc/] + Input --> Decision1{CFNRc registered +for required BS} + Decision1 -- no --> SetError1[set error] + Decision1 -- yes --> Decision2{BAIC +active} + Decision2 -- yes --> SetResult[set result] + Decision2 -- no --> Decision3{BIC-Roam +active} + Decision3 -- yes --> SetResult + Decision3 -- no --> Decision4{roaming +outside HPLMN +country} + Decision4 -- yes --> SetResult + Decision4 -- no --> Decision5{BAOC +active} + Decision5 -- yes --> SetResult + Decision5 -- no --> Decision6{BOIC +active} + Decision6 -- yes --> SetResult + Decision6 -- no --> Decision7{BOIC-exHC +active} + Decision7 -- yes --> Decision8{ftn in VPLMN +country} + Decision8 -- yes --> SetResult + Decision8 -- no --> Decision9{ftn in HPLMN +country} + Decision9 -- yes --> SetResult + Decision9 -- no --> SetError2[set error] + Decision7 -- no --> Decision10{CFU +active} + Decision10 -- yes --> SetError3[set error] + Decision10 -- no --> SetResult + SetError1 --> Ack[acknowledge] + SetError2 --> Ack + SetError3 --> Ack + SetResult --> Ack + Ack --> End([idle]) + +``` + +BS: Basic Service group. + ftn: forwarded-to number. + BAOC: Barring of All Outgoing Calls. + BOIC: Barring of Outgoing International Calls. + BOIC-exHC: Barring of Outgoing International Calls - except those directed to HPLMN Country. + BAIC: Barring of All Incoming Calls. + +Flowchart titled 'Process CFNRc3' detailing the activation process for call forwarding on a mobile subscriber not reachable. The process starts at an 'idle' state, followed by an 'activate CFNRc' input. A decision diamond 'CFNRc registered for required BS' follows. If 'no', it goes to 'set error'. If 'yes', it checks 'BAIC active'. If 'yes', it goes to 'set result'. If 'no', it checks 'BIC-Roam active'. If 'yes', it goes to 'set result'. If 'no', it checks 'roaming outside HPLMN country'. If 'no', it checks 'BAOC active'. If 'yes', it goes to 'set result'. If 'no', it checks 'BOIC active'. If 'yes', it goes to 'set result'. If 'no', it checks 'BOIC-exHC active'. If 'yes', it checks 'ftn in VPLMN country'. If 'no', it checks 'ftn in HPLMN country'. If 'yes', it goes to 'set result'. If 'no', it goes to 'set error'. Finally, it reaches an 'acknowledge' state and returns to 'idle'. + +Figure 4.6: CFNRc3 Call forwarding on mobile subscriber not reachable activation process + +### 4.1.4 Deactivation + +The same rules apply for the deactivation of CFNRc as were described for CFU in clause 1.1.4 above, see figure 4.8. + +The information flow for deactivation of call forwarding on mobile subscriber not reachable is shown in figure 4.7. + +![Sequence diagram showing the interaction between MS, MSC, VLR, and HLR for deactivation of call forwarding. MS sends 'Deactivate CFNRc' to MSC. MSC sends 'Deactivate CFNRc' to VLR. VLR sends 'Deactivate CFNRc' to HLR. HLR returns 'Acknowledge' to VLR. VLR returns 'Acknowledge' to MSC. MSC sends 'Release complete' with '\Facility' to MS.](677bcb564410628b8b966ad87b394888_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: CFNRc4 + MS->>MSC: Deactivate CFNRc + MSC->>VLR: Deactivate CFNRc + VLR->>HLR: Deactivate CFNRc + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility + +``` + +Sequence diagram showing the interaction between MS, MSC, VLR, and HLR for deactivation of call forwarding. MS sends 'Deactivate CFNRc' to MSC. MSC sends 'Deactivate CFNRc' to VLR. VLR sends 'Deactivate CFNRc' to HLR. HLR returns 'Acknowledge' to VLR. VLR returns 'Acknowledge' to MSC. MSC sends 'Release complete' with '\Facility' to MS. + +Figure 4.7: Deactivation of call forwarding on mobile subscriber not reachable + +![Flowchart for Process CFNRc4. It starts at 'idle', goes to 'deactivate CFNRc', then checks 'BS included in request'. If 'no', it goes to 'set BS = all BS' and then to the next decision. If 'yes', it goes directly to the next decision 'CFNRc active for subset BS'. If 'no' to the second decision, it goes to 'set error'. If 'yes', it goes to 'set result'. Both 'set error' and 'set result' lead to 'acknowledge', which then leads back to 'idle'. A note indicates BS: Basic Service group.](2438c4dd81a8b76ec881d47d87b11fc3_img.jpg) + +``` + +graph TD + Start([idle]) --> Deactivate{deactivate CFNRc} + Deactivate --> BSIncluded{BS included in request} + BSIncluded -- no --> SetBS[set BS = all BS] + SetBS --> CFNRcActive{CFNRc active for subset BS} + BSIncluded -- yes --> CFNRcActive + CFNRcActive -- no --> SetError[set error] + CFNRcActive -- yes --> SetResult[set result] + SetError --> Acknowledge{acknowledge} + SetResult --> Acknowledge + Acknowledge --> End([idle]) + Note right of End: BS: Basic Service group. + +``` + +Flowchart for Process CFNRc4. It starts at 'idle', goes to 'deactivate CFNRc', then checks 'BS included in request'. If 'no', it goes to 'set BS = all BS' and then to the next decision. If 'yes', it goes directly to the next decision 'CFNRc active for subset BS'. If 'no' to the second decision, it goes to 'set error'. If 'yes', it goes to 'set result'. Both 'set error' and 'set result' lead to 'acknowledge', which then leads back to 'idle'. A note indicates BS: Basic Service group. + +Figure 4.8: CFNRc4 Call forwarding on mobile subscriber not reachable deactivation process + +### 4.1.5 Interrogation + +#### Data request + +The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. Interrogation of CFNRc is handled by the VLR which returns the required information or error to the MS, see figure 4.9. + +![Sequence diagram showing the interrogation of call forwarding on mobile subscriber not reachable. The diagram involves four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate CFNRc' to MSC. 2. MSC sends 'Interrogate CFNRc' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release complete' back to MS, with a sub-parameter '\Facility'.](9e26cd5584f423e1b2155fb341db579f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note left of MS: Data request + MS->>MSC: Interrogate CFNRc + MSC->>VLR: Interrogate CFNRc + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note right of MS: \Facility + +``` + +Sequence diagram showing the interrogation of call forwarding on mobile subscriber not reachable. The diagram involves four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate CFNRc' to MSC. 2. MSC sends 'Interrogate CFNRc' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release complete' back to MS, with a sub-parameter '\Facility'. + +Figure 4.9: Interrogation of call forwarding on mobile subscriber not reachable + +## 4.2 Functions and information flows + +### 4.2.1 Call re-routed from VLR + +The following Mobile Additional Function has been identified for the PLMN: + +#### MAF010 + +Examination of call forwarding on mobile subscriber not reachable authorizations + +The ability of a PLMN component to determine the authorizations relating to call forwarding on mobile subscriber not reachable in case the mobile subscriber is not reachable in the VLR, in case of no paging response or radio congestion. See figure 4.10. + +Location: VLR. + +The information flows for forwarding to fixed terminal and to mobile station are shown in figures 4.11 and 4.12 respectively. These flows represent the case where the mobile subscriber is not reachable in the VLR, and that this fact was not detected at interrogation from the HLR. This situation occurs if the MSC requests the VLR to provide information for a mobile terminating call towards a subscriber who is detached in the VLR. + +Figures 4.13 and 4.14 show the information flows in case of no paging response. + +Figures 4.15 and 4.16 show the information flows in case of radio congestion. + +### 4.2.2 Call re-routed from HLR + +The following Mobile Additional Function has been identified for the PLMN: + +#### MAF010 + +Examination of call forwarding on mobile subscriber not reachable authorizations + +The ability of a PLMN component to determine the authorizations relating to call forwarding on mobile subscriber not reachable in case the mobile subscriber is deregistered or purged in the HLR or not reachable in the VLR. See figure 4.10. + +Location: HLR. + +The information flows for forwarding to fixed terminal and to mobile station are shown in figures 4.17 and 4.18 respectively. These flows represent the case where the call is re-routed from the HLR because information from the VLR indicates that the subscriber cannot be reached in the VLR. This situation occurs if the VLR detects at roaming number request time that the subscriber concerned is detached or that there is no roaming number available. + +Figures 4.19 and 4.20 show the information flows for forwarding to fixed terminal and to mobile station respectively in case where the call is re-routed by the HLR because the subscriber is deregistered or purged in the HLR. + +![Flowchart for Process MAF010: Call forwarding on mobile subscriber not reachable authorisations examination (VLR and HLR).](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) + +Process MAF010 + +382\_4A(1) + +``` +graph TD; Start([idle]) --> Init{initiate handling of CFNRc}; Init --> BS{active for this BS}; BS -- no --> EndIndicator[set indicator = 'mobile subscriber not reachable']; BS -- yes --> CountReached{number of forwardings reached}; CountReached -- yes --> SetError[set error]; CountReached -- no --> Increment[increment counter<br/>get forwarded-to number<br/>set forwarding cause=CFNRc]; Increment --> Notify{notification to calling subscriber}; Notify -- yes --> SetIndicator[set indicator = 'notify calling subscriber']; Notify -- no --> MSISDN{serviced subscribers MSISDN can be presented}; MSISDN -- yes --> SetAllowed[set redirecting presentation = allowed]; MSISDN -- no --> SetRestricted[set redirecting presentation = restricted]; SetError --> Continue{continue call handling}; SetRestricted --> Continue; SetAllowed --> Continue; SetIndicator --> Continue; EndIndicator --> Continue; Continue --> End([idle]); +``` + +BS : Basic Service group. + +Flowchart for Process MAF010: Call forwarding on mobile subscriber not reachable authorisations examination (VLR and HLR). + +Figure 4.10: MAF010 Call forwarding on mobile subscriber not reachable authorisations examination (VLR and HLR) + +![Sequence diagram showing information flow for call forwarding. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, LEc. The sequence includes messages: Set-up, Info req, Provide Roam No, Roam No, Info ack, Set-up (to MSCb), Info req (MAF010), Info ack, Release, Release (to MSa/TEa), Set-up (to LEc, OR1:Y), Notification (to MSa/TEa, OR2:Y), and Notif (to MSa/TEa).](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant LEc + + Note left of MSa/TEa: Set-up + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb->>VLRb: Provide Roam No + VLRb->>HLRb: Roam No + HLRb->>GMSC: Info ack + GMSC->>MSCb: Set-up + MSCb->>VLRb: Info req + Note right of VLRb: MAF010 + VLRb->>MSCb: Info ack + MSCb->>GMSC: Release + GMSC->>MSa/TEa: Release + MSCb->>LEc: Set-up + Note right of MSCb: OR1:Y + MSCb->>GMSC: Notification + Note right of MSCb: OR2:Y + GMSC->>MSa/TEa: Notif +``` + +Sequence diagram showing information flow for call forwarding. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, LEc. The sequence includes messages: Set-up, Info req, Provide Roam No, Roam No, Info ack, Set-up (to MSCb), Info req (MAF010), Info ack, Release, Release (to MSa/TEa), Set-up (to LEc, OR1:Y), Notification (to MSa/TEa, OR2:Y), and Notif (to MSa/TEa). + +NOTE: info: information Y: Yes +req: request N: No +ack: acknowledge +notif: notification +Roam No: roaming number +OR1: Call to be forwarded +OR2: Notification to calling subscriber required + +**Figure 4.11: Information flow for call forwarding on mobile subscriber not reachable in case of mobile subscriber not reachable in the VLR (to fixed terminal) (re-routing by VLR)** + +![Sequence diagram showing information flow for call forwarding. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, HLRC, MSCc. The diagram shows messages like Set-up, Info req, Provide Roam No, Info ack, Release, Notification, and OR1/OR2 responses between these entities.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant HLRC + participant MSCc + + Note right of VLRb: MAF010 + + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb->>VLRb: Provide Roam No + VLRb->>HLRb: Roam No + HLRb->>GMSC: Info ack + GMSC->>MSCb: Set-up + MSCb->>HLRC: Info req + HLRC->>MSCb: Info ack + MSCb->>GMSC: Release + GMSC->>MSa/TEa: Release + MSCb-->>HLRC: OR1:N + MSCb-->>HLRC: OR1:Y + HLRC->>MSCc: Info req + MSCc->>HLRC: Info ack + HLRC->>MSCc: Set-up + MSCb-->>GMSC: OR2:Y + GMSC->>MSa/TEa: Notification + +``` + +Sequence diagram showing information flow for call forwarding. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, HLRC, MSCc. The diagram shows messages like Set-up, Info req, Provide Roam No, Info ack, Release, Notification, and OR1/OR2 responses between these entities. + +NOTE: info: information Y: Yes + req: request N: No + ack: acknowledge + notif: notification + Roam No: roaming number + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + +**Figure 4.12: Information flow for call forwarding on mobile subscriber not reachable in case of mobile subscriber not reachable in the VLR (to mobile station) (re-routing by VLR)** + +![Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable. Lifelines: MSa/TEa, GMSC, HLRb, VLDb, MSCb, MSb, LEc. The process involves Set-up, Info req, Provide roam No, Roam No, Info ack, Set-up, Info req, Page MS, Paging, no response, Absent subscriber, MAF010, OR1:N, Impossible call completion, Release, OR1:Y, Connect to following address, Set-up, Notification, OR2:Y, and Notif messages.](5e9af8986a5845504f251d3079da8078_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLDb + participant MSCb + participant MSb + participant LEc + + Note left of MSa/TEa: Set-up + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb->>VLDb: Provide roam No + VLDb->>HLRb: Roam No + HLRb->>GMSC: Info ack + GMSC->>MSCb: Set-up + MSCb->>VLDb: Info req + VLDb->>MSCb: Page MS + MSCb->>MSb: Paging + Note right of MSCb: no response + VLDb->>MSCb: Absent subscriber + Note right of VLDb: MAF010 + Note right of VLDb: OR1:N + VLDb->>MSCb: Impossible call completion + Note left of MSa/TEa: Release + MSa/TEa->>GMSC: Release + Note right of VLDb: OR1:Y + VLDb->>MSCb: Connect to following address + MSCb->>MSb: Set-up + MSb->>LEc: Set-up + Note left of MSa/TEa: Notif + MSa/TEa->>GMSC: Notif + GMSC->>MSCb: Notification + Note right of MSCb: OR2:Y + +``` + +Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable. Lifelines: MSa/TEa, GMSC, HLRb, VLDb, MSCb, MSb, LEc. The process involves Set-up, Info req, Provide roam No, Roam No, Info ack, Set-up, Info req, Page MS, Paging, no response, Absent subscriber, MAF010, OR1:N, Impossible call completion, Release, OR1:Y, Connect to following address, Set-up, Notification, OR2:Y, and Notif messages. + +NOTE: info: information Y: Yes + req: request N: No + ack: acknowledge + notif: notification + roam: roaming + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + +**Figure 4.13: Information flow for call forwarding on mobile subscriber not reachable in case of no paging response (to fixed terminal) (re-routing by VLR)** + +![Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable due to no paging response. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, HLRc, MSCc. The process involves Set-up, Info req, Provide roam No, Roam No, Info ack, Set-up, Info req, Page MS, no response, Absent subscriber, MAF010, OR1:N, Impossible call completion, Release, OR1:Y, Connect to following address, Info req, Info ack, Set-up, Notification, OR2:Y, and Notif messages.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant HLRc + participant MSCc + + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb->>VLRb: Provide roam No + VLRb-->>HLRb: Roam No + HLRb-->>GMSC: Info ack + GMSC->>MSCb: Set-up + MSCb->>VLRb: Info req + VLRb->>MSCb: Page MS + MSCb->>MSb: Paging + Note over MSb: no response + MSCb-->>VLRb: Absent subscriber + Note right of VLRb: MAF010 + Note right of VLRb: OR1:N + VLRb->>MSCb: Impossible call completion + MSCb-->>GMSC: Release + GMSC-->>MSa/TEa: Release + Note right of VLRb: OR1:Y + VLRb->>MSCb: Connect to following address + MSCb->>HLRc: Info req + HLRc-->>MSCb: Info ack + MSCb->>MSCc: Set-up + Note right of MSCb: OR2:Y + MSCb-->>GMSC: Notification + GMSC-->>MSa/TEa: Notif + +``` + +Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable due to no paging response. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, HLRc, MSCc. The process involves Set-up, Info req, Provide roam No, Roam No, Info ack, Set-up, Info req, Page MS, no response, Absent subscriber, MAF010, OR1:N, Impossible call completion, Release, OR1:Y, Connect to following address, Info req, Info ack, Set-up, Notification, OR2:Y, and Notif messages. + +NOTE: info: information            Y: Yes + req: request                    N: No + ack: acknowledge + notif: notification + roam: roaming + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + +**Figure 4.14: Information flow for call forwarding on mobile subscriber not reachable in case of no paging response (to mobile station) (re-routing by VLR)** + +![Sequence diagram showing information flow for call forwarding on mobile subscriber not reachable in case of radio congestion (to fixed terminal) (re-routing by VLR).](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant LEc + + Note right of MSCb: radio congestion + + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb->>VLRb: Provide roam No + VLRb->>HLRb: Roam No + HLRb->>GMSC: Info ack + GMSC->>MSCb: Set-up + MSCb->>VLRb: Info req + VLRb->>MSCb: Complete call + Note right of MSCb: radio congestion + VLRb->>MSCb: Radio congestion + Note right of VLRb: MAF010 + Note right of VLRb: OR1:N + VLRb->>MSCb: Impossible call completion + MSCb->>GMSC: Release + MSa/TEa->>GMSC: Release + Note right of VLRb: OR1:Y + VLRb->>MSCb: Connect to following address + MSCb->>MSb: Set-up + Note right of MSCb: OR2:Y + MSCb->>GMSC: Notification + GMSC->>MSa/TEa: Notif + +``` + +Sequence diagram showing information flow for call forwarding on mobile subscriber not reachable in case of radio congestion (to fixed terminal) (re-routing by VLR). + +NOTE: info: information            Y: Yes + req: request                    N: No + ack: acknowledge + notif: notification + roam: roaming + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + +**Figure 4.15: Information flow for call forwarding on mobile subscriber not reachable in case of radio congestion (to fixed terminal) (re-routing by VLR)** + +![Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable due to radio congestion. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, HLRc, MSCc. The process involves Set-up, Info req/ack, Provide/Roam No, radio congestion handling (MAF010, OR1:N), Release, Connect to following address (OR1:Y), Info req/ack, Set-up, Notification (OR2:Y), and final Release/Notif.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant HLRc + participant MSCc + + Note left of MSa/TEa: Set-up + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb->>VLRb: Provide roam No + VLRb->>HLRb: Roam No + HLRb->>GMSC: Info ack + GMSC->>MSCb: Set-up + MSCb->>VLRb: Info req + VLRb->>MSCb: Complete call + Note right of MSCb: radio congestion + MSCb->>VLRb: Radio congestion + Note right of VLRb: MAF010 + Note right of VLRb: OR1:N + VLRb->>MSCb: Impossible call completion + Note left of MSa/TEa: Release + MSa/TEa->>GMSC: Release + Note right of VLRb: OR1:Y + VLRb->>MSCc: Connect to following address + MSCc->>HLRc: Info req + HLRc->>MSCc: Info ack + MSCc->>HLRc: Set-up + Note right of MSCb: OR2:Y + MSCb->>GMSC: Notification + Note left of MSa/TEa: Notif + MSa/TEa->>GMSC: Notif + +``` + +Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable due to radio congestion. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, HLRc, MSCc. The process involves Set-up, Info req/ack, Provide/Roam No, radio congestion handling (MAF010, OR1:N), Release, Connect to following address (OR1:Y), Info req/ack, Set-up, Notification (OR2:Y), and final Release/Notif. + +NOTE: info: information            Y: Yes + req: request                    N: No + ack: acknowledge + notif: notification + roam: roaming + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + +**Figure 4.16: Information flow for call forwarding on mobile subscriber not reachable in case of radio congestion (to mobile station) (re-routing by VLR)** + +![Sequence diagram for Figure 4.17 showing call forwarding to a fixed terminal. The flow starts with a Set-up from MSa/TEa to GMSC. GMSC sends an Info request to HLRb, which asks VLRb for a roaming number. VLRb responds 'Not reachable'. HLRb sends 'MAF010' and 'Info ack' to GMSC. GMSC sends a 'Release' to MSa/TEa. Based on OR1:Y, GMSC then sends a 'Set-up' to LEc and a 'Notification' back to MSa/TEa.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant LEc + + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info request + HLRb->>VLRb: Provide roaming No + VLRb-->>HLRb: Not reachable + Note over HLRb, GMSC: MAF010 + HLRb-->>GMSC: Info ack + GMSC-->>MSa/TEa: Release + Note right of GMSC: OR1:N + Note right of GMSC: OR1:Y + GMSC->>LEc: Set-up + Note right of GMSC: OR2:Y + GMSC-->>MSa/TEa: Notification + +``` + +Sequence diagram for Figure 4.17 showing call forwarding to a fixed terminal. The flow starts with a Set-up from MSa/TEa to GMSC. GMSC sends an Info request to HLRb, which asks VLRb for a roaming number. VLRb responds 'Not reachable'. HLRb sends 'MAF010' and 'Info ack' to GMSC. GMSC sends a 'Release' to MSa/TEa. Based on OR1:Y, GMSC then sends a 'Set-up' to LEc and a 'Notification' back to MSa/TEa. + +NOTE: info: information Y: Yes +ack: acknowledge N: No +OR1: Call to be forwarded +OR2: Notification to calling subscriber required + +**Figure 4.17: Information flow for call forwarding on mobile subscriber not reachable in case of mobile subscriber not reachable in the VLR (to fixed terminal) (re-routing by HLR)** + +![Sequence diagram for Figure 4.18 showing call forwarding to a mobile station. Similar to 4.17, but after the initial failure, GMSC sends an 'Information request' to HLRc. HLRc requests a roaming number from VLRc. VLRc provides the 'Roaming No'. HLRc sends 'Information acknowledge' to GMSC. GMSC then sends 'Set-up' to MSCc and a 'Notif' to MSa/TEa.](64544fbada794f3cdf4f78f5d83613e4_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant HLRc + participant VLRc + participant MSCc + + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb->>VLRb: Provide roaming No + VLRb-->>HLRb: Not reachable + Note over HLRb, GMSC: MAF010 + HLRb-->>GMSC: Info ack + GMSC-->>MSa/TEa: Release + Note right of GMSC: OR1:N + Note right of GMSC: OR1:Y + GMSC->>HLRc: Information request + HLRc->>VLRc: Provide roaming No + VLRc-->>HLRc: Roaming No + HLRc-->>GMSC: Information acknowledge + GMSC->>MSCc: Set-up + Note right of GMSC: OR2:Y + GMSC-->>MSa/TEa: Notif + +``` + +Sequence diagram for Figure 4.18 showing call forwarding to a mobile station. Similar to 4.17, but after the initial failure, GMSC sends an 'Information request' to HLRc. HLRc requests a roaming number from VLRc. VLRc provides the 'Roaming No'. HLRc sends 'Information acknowledge' to GMSC. GMSC then sends 'Set-up' to MSCc and a 'Notif' to MSa/TEa. + +NOTE: info: information Y: Yes +req: request N: No +ack: acknowledge +notif: notification +OR1: Call to be forwarded +OR2: Notification to calling subscriber required + +**Figure 4.18: Information flow for call forwarding on mobile subscriber not reachable in case of mobile subscriber not reachable in the VLR (to mobile station) (re-routing by HLR)** + +![Sequence diagram showing information flow for call forwarding between MSa/TEa, GMSC, HLRb, VLRb, and LEc. The diagram shows messages like Set-up, Info request, Info ack, Release, and Notification with parameters like OR1:N, OR1:Y, and OR2:Y.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant LEc + + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info request + HLRb-->>GMSC: Info ack + Note right of HLRb: MAF010 + GMSC-->>MSa/TEa: Release + Note right of GMSC: OR1:N + GMSC->>LEc: Set-up + Note right of GMSC: OR1:Y + GMSC-->>MSa/TEa: Notification + Note right of GMSC: OR2:Y +``` + +Sequence diagram showing information flow for call forwarding between MSa/TEa, GMSC, HLRb, VLRb, and LEc. The diagram shows messages like Set-up, Info request, Info ack, Release, and Notification with parameters like OR1:N, OR1:Y, and OR2:Y. + +NOTE: info: information Y: Yes +ack: acknowledge N: No +OR1: Call to be forwarded +OR2: Notification to calling subscriber required + +**Figure 4.19: Information flow for call forwarding on mobile subscriber not reachable in case of mobile subscriber deregistered or purged (to fixed terminal) (re-routing by HLR)** + +![Sequence diagram showing information flow for call forwarding on mobile subscriber not reachable. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, HLRC, VLRc, MSCc. The sequence starts with a Set-up from MSa/TEa to GMSC. GMSC sends an Info req to HLRb. HLRb responds with MAF010 and Info ack. GMSC sends a Release to MSa/TEa and an OR1:N to HLRb. HLRb sends an Information request to HLRC. HLRC responds with Provide roaming No and Roaming No. HLRb sends an Information acknowledge to GMSC. GMSC sends a Set-up to MSCc. Finally, GMSC sends an OR2:Y to MSa/TEa and a Notif to MSa/TEa.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant HLRC + participant VLRc + participant MSCc + + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb-->>GMSC: MAF010 + HLRb-->>GMSC: Info ack + GMSC-->>MSa/TEa: Release + GMSC->>HLRb: OR1:N + HLRb->>HLRC: Information request + HLRC-->>VLRc: Provide roaming No + HLRC-->>VLRc: Roaming No + HLRb-->>GMSC: Information acknowledge + GMSC->>MSCc: Set-up + GMSC-->>MSa/TEa: OR2:Y + GMSC-->>MSa/TEa: Notif + +``` + +Sequence diagram showing information flow for call forwarding on mobile subscriber not reachable. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, HLRC, VLRc, MSCc. The sequence starts with a Set-up from MSa/TEa to GMSC. GMSC sends an Info req to HLRb. HLRb responds with MAF010 and Info ack. GMSC sends a Release to MSa/TEa and an OR1:N to HLRb. HLRb sends an Information request to HLRC. HLRC responds with Provide roaming No and Roaming No. HLRb sends an Information acknowledge to GMSC. GMSC sends a Set-up to MSCc. Finally, GMSC sends an OR2:Y to MSa/TEa and a Notif to MSa/TEa. + +NOTE: info: information Y: Yes + req: request N: No + ack: acknowledge + notif: notification + No: number + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + +**Figure 4.20: Information flow for call forwarding on mobile subscriber not reachable in case of mobile subscriber deregistered or purged (to mobile station) (re-routing by HLR)** + +### 4.2.3 Call re-routed from HLR for Pre-Paging + +If the Pre-Paging is performed by the VPLMN, in addition to clause 4.2.2, the following Mobile Additional Function has been identified for Pre-Paging in the PLMN. In this case, the clause 4.2.1 is not identified for Pre-Paging in the PLMN: + +MAF010 + +Examination of call forwarding on mobile subscriber not reachable authorizations + +The ability of a PLMN component to determine the authorizations relating to call forwarding on mobile subscriber not reachable in case of no paging response or radio congestion for Pre-Paging in the VLR. See figure 4.10. + +Location: HLR. + +The information flows for forwarding to fixed terminal and to mobile station are shown in figures 4.21 and 4.22 respectively. These flows represent the case where the call is re-routed from the HLR because of no paging response for Pre-Paging from the MSC + +Figures 4.23 and 4.24 show the information flows in case of radio congestion for Pre-Paging. + +![Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, LEc. The process involves setup, info request, provide roam no, page MS, no response, absent subscriber, info ack, release, and notification messages.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant LEc + + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb->>VLRb: Provide roam No + VLRb->>MSCb: Page MS + MSCb->>MSb: Paging + Note over MSCb: no response + MSCb-->>VLRb: Absent subscriber + VLRb-->>HLRb: Absent subscriber + Note over HLRb: MAF010 + HLRb-->>GMSC: Info ack + Note over GMSC: OR1:N + GMSC-->>MSa/TEa: Release + Note over GMSC: OR1:Y + GMSC->>MSa/TEa: Set-up + Note over GMSC: OR2:Y + GMSC->>LEc: ---------------------------------------------------------------------------------> + GMSC-->>MSa/TEa: Notification + +``` + +Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, LEc. The process involves setup, info request, provide roam no, page MS, no response, absent subscriber, info ack, release, and notification messages. + +NOTE: info: information         Y: Yes + req: request             N: No + ack: acknowledge + roam: roaming + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + +**Figure 4.21: Information flow for call forwarding on mobile subscriber not reachable in case of no paging response for Pre-Paging (to fixed terminal) (re-routing by HLR)** + +![Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable in case of no paging response (to mobile station) (re-routing by HLR).](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant HLRC + participant VLRc + participant MSCc + + Note left of MSa/TEa: Set-up + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb->>VLRb: Provide roam No + VLRb->>MSCb: Page MS + MSCb->>MSb: Paging + Note right of MSCb: no response + MSCb->>VLRb: Absent subscriber + VLRb->>HLRb: Absent subscriber + HLRb->>GMSC: Info ack MAF 010 + GMSC->>MSa/TEa: Rel + Note left of GMSC: OR1:N + GMSC->>HLRC: OR1:Y + GMSC->>HLRC: Info req + HLRC->>VLRc: Provide roam No + Note right of VLRc: (Note 1) + VLRc->>HLRC: Roam No + HLRC->>GMSC: Info ack + GMSC->>MSCc: Set-up + Note left of GMSC: OR2:Y + GMSC->>MSa/TEa: Notif + +``` + +Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable in case of no paging response (to mobile station) (re-routing by HLR). + +NOTE: info: information Y: Yes + req: request N: No + ack: acknowledge + Rel: Release + roam: roaming + Notif: Notification + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + NOTE 1: The procedure of the paging would be performed. + +**Figure 4.22: Information flow for call forwarding on mobile subscriber not reachable in case of no paging response (to mobile station) (re-routing by HLR)** + +![Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable due to radio congestion. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, LEc. The process involves Set-up, Info req, Provide roam No, Page MS, radio congestion detection, Absent subscriber handling, and subsequent routing decisions (OR1, OR2).](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLRb + participant MSCb + participant MSb + participant LEc + + Note left of MSa/TEa: Set-up + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb->>VLRb: Provide roam No + VLRb->>MSCb: Page MS + Note right of MSCb: radio congestion + MSCb->>VLRb: Absent subscriber + VLRb->>HLRb: Absent subscriber + Note left of HLRb: MAF010 + HLRb->>GMSC: Info ack + GMSC->>MSa/TEa: OR1:N + Note left of MSa/TEa: Release + MSa/TEa->>GMSC: Release + GMSC->>MSa/TEa: OR1:Y + Note left of MSa/TEa: Set-up + MSa/TEa->>GMSC: Set-up + Note right of LEc: -----> + GMSC->>LEc: OR2:Y + Note left of MSa/TEa: Notification + MSa/TEa->>GMSC: Notification + +``` + +Sequence diagram showing information flow for call forwarding on a mobile subscriber not reachable due to radio congestion. Lifelines: MSa/TEa, GMSC, HLRb, VLRb, MSCb, MSb, LEc. The process involves Set-up, Info req, Provide roam No, Page MS, radio congestion detection, Absent subscriber handling, and subsequent routing decisions (OR1, OR2). + +NOTE: info: information Y: Yes + req: request N: No + ack: acknowledge + roam: roaming + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + +**Figure 4.23: Information flow for call forwarding on mobile subscriber not reachable in case of radio congestion for Pre-Paging (to fixed terminal) (re-routing by HLR)** + +![Sequence diagram showing information flow for call forwarding on mobile subscriber not reachable in case of radio congestion. Lifelines: MSa/TEa, GMSC, HLRb, VLrb, MSCb, MSb, HLRC, VLRC, MSCc. The diagram shows messages like Set-up, Info req, Provide roam No, Page MS, radio congestion, Absent subscriber, Info ack, Rel, OR1, OR2, and Set-up.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +``` + +sequenceDiagram + participant MSa/TEa + participant GMSC + participant HLRb + participant VLrb + participant MSCb + participant MSb + participant HLRC + participant VLRC + participant MSCc + + Note left of MSa/TEa: Set-up + MSa/TEa->>GMSC: Set-up + GMSC->>HLRb: Info req + HLRb->>VLrb: Provide roam No + VLrb->>MSCb: Page MS + Note right of MSCb: radio congestion + MSCb->>VLrb: Absent subscriber + VLrb->>HLRb: Absent subscriber + HLRb->>GMSC: Info ack MAF 010 + GMSC->>MSa/TEa: Rel + Note left of GMSC: OR1 :N + Note left of GMSC: OR1 :Y + GMSC->>HLRC: Info req + HLRC->>VLRC: Provide roam No + Note right of VLRC: (Note 1) + VLRC->>HLRC: Roam No + HLRC->>GMSC: Info ack + GMSC->>MSCc: Set-up + GMSC->>MSa/TEa: Notif + Note left of GMSC: OR2 :Y + +``` + +Sequence diagram showing information flow for call forwarding on mobile subscriber not reachable in case of radio congestion. Lifelines: MSa/TEa, GMSC, HLRb, VLrb, MSCb, MSb, HLRC, VLRC, MSCc. The diagram shows messages like Set-up, Info req, Provide roam No, Page MS, radio congestion, Absent subscriber, Info ack, Rel, OR1, OR2, and Set-up. + +NOTE: info: information Y: Yes + req: request N: No + ack: acknowledge + Rel: Release + roam: roaming + Notif: Notification + OR1: Call to be forwarded + OR2: Notification to calling subscriber required + NOTE 1: The procedure of the paging would be performed. + +**Figure 4.24: Information flow for call forwarding on mobile subscriber not reachable in case of radio congestion (to mobile station) (re-routing by HLR)** + +## 4.3 Information stored in the HLR + +The following logical states are applicable for CFNRc (refer to 3GPP TS 23.011 for an explanation of the notation): + +| Provisioning State | Registration State | Activation State | HLR Induction State | +|--------------------|--------------------|-----------------------|---------------------| +| (Not Provisioned, | Not Registered, | Not Active, | Not Induced) | +| (Provisioned, | Not Registered, | Not Active, | Not Induced) | +| (Provisioned, | Registered, | Not Active, | Not Induced) | +| (Provisioned, | Registered, | Active and Quiescent, | Not Induced) | +| (Provisioned, | Registered, | Active and Operative, | Not Induced) | + +The registration and activation state may be different for each applicable elementary basic service group. + +The provisioning state shall be on a per subscriber basis, and hence the same for all basic service groups. + +The HLR shall store: + +- the state of CFNRc (which shall be one of the valid states listed above) for each applicable elementary basic service group; +- the subscription option "notification to the calling party" on a per subscriber basis; + +This subscription option takes one of the following values: + +- no notification; +- notification. +- the subscription option " MSISDN of the served subscriber can be presented to the forwarded-to subscriber" on a per subscriber basis; + +This subscription option takes one of the following values: + +- presentation restricted; +- presentation allowed. +- the registration parameter "forwarded-to number" (possibly including a forwarded-to sub-address) for each applicable elementary basic service group. +- the default forwarded-to number (containing less than 16 digits) for each applicable elementary basic service group. + +## 4.4 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of CFNRc. The state changes are either caused by actions of the service provider, the mobile user or the network. + +Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence, they are not shown in the diagram. + +The diagram only shows operations on an elementary basic service group. + +![State transition model for CFNRc. The diagram shows four states: (Not Provisioned, Not Registered, Not Active, Not Induced), (Provisioned, Not Registered, Not Active, Not Induced), (Provisioned, Registered, Active and Quiescent, Not Induced), and (Provisioned, Registered, Not Active, Not Induced). Transitions include Withdrawal, Provision, Erasure, Registration, Deactivation, Activation, and SS Interaction (started/ended).](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +``` + +stateDiagram-v2 + [*] --> S0 : (Not Provisioned, Not Registered, Not Active, Not Induced) + S0 --> S1 : (Provisioned, Not Registered, Not Active, Not Induced) : Provision + S1 --> S0 : Withdrawal + S1 --> S2 : (Provisioned, Registered, Active and Quiescent, Not Induced) : Registration + S2 --> S1 : Erasure + S2 --> S3 : (Provisioned, Registered, Not Active, Not Induced) : Deactivation + S3 --> S2 : Activation + S3 --> S1 : Erasure + S3 --> S0 : Withdrawal + S2 --> S0 : Withdrawal + S2 --> S3 : SS Interaction ended + S3 --> S2 : SS Interaction started + +``` + +State transition model for CFNRc. The diagram shows four states: (Not Provisioned, Not Registered, Not Active, Not Induced), (Provisioned, Not Registered, Not Active, Not Induced), (Provisioned, Registered, Active and Quiescent, Not Induced), and (Provisioned, Registered, Not Active, Not Induced). Transitions include Withdrawal, Provision, Erasure, Registration, Deactivation, Activation, and SS Interaction (started/ended). + +Figure 4.25: State transition model for CFNRc + +## 4.5 Transfer of information from HLR to VLR + +If the provisioning state for CFNRc is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of CFNRc for all relevant elementary basic service groups. + +If the registration state for CFNRc is "Registered" then, when the subscriber registers on a VLR, the HLR shall send that VLR the registration parameter "forwarded-to number" for all relevant elementary basic service groups and information about the subscription options "notification to the calling party" and "MSISDN of the served subscriber" can be presented to the forwarded-to subscriber". + +If the logical state or the registration parameter "forwarded-to number" of CFNRc is changed while a subscriber is registered on a VLR then for the affected basic service groups, the HLR shall inform the VLR respectively of the new logical state or the new registration parameter of CFNRc. + +If information about the subscription option "notification to the calling party" of CFNRc is changed while a subscriber is registered on a VLR and the registration state of CFNRc is "Registered" then the HLR shall inform the VLR of the new information about the subscription option of CFNRc. + +## 4.6 Information stored in the VLR + +For CFNRc the VLR shall store the service state information, the registration parameter "forward-to number" and the subscription options received from the HLR. + +## 4.7 Handover + +Handover will have no impact on the control procedure and the operation of the service. + +## 4.8 Cross phase compatibility + +### 4.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber + +In response to a CFNRc interrogation request, if the MS or any network element involved is of Phase 1, only information concerning basic service groups for which the activation state has the value "Active and Operative" will be returned. This means that the subscriber will not be aware that the forwarded to number is registered if CFNRc is deactivated or active (quiescent). A subaddress (if registered) will not be included. + +Note that if any network element involved is of Phase 1, CFNRc Registration requests which use a subaddress and all CFNRc Activation and Deactivation requests will be rejected, as these are not specified in Phase 1. + +### 4.8.2 HLR only supports Phase 1 updating of subscriber information + +If the VLR receives the SS-Status parameter from a Phase 1 HLR it shall act if it has received the SS-Status parameter with the values shown in the following: + +- 1) Registered, Activated => P bit = 1, R bit = 1, A bit = 1, Q bit = 0; +- 2) Registered, Deactivated => P bit = 1, R bit = 1, A bit = 0, Q bit = 0 or 1; +- 3) Erased => P bit = 1, R bit = 0, A bit = 0, Q bit = 0 or 1. + +### 4.8.3 VLR only supports Phase 1 updating of subscriber information + +When passing CFNRc information to a Phase 1 VLR, the HLR shall send the service state information in a form which the VLR can accept, based on the logical state held in the HLR, as follows: + +- 1) (Provisioned, Not Registered, Not Active, Not Induced) +=> Erased, Deactivated; +- 2) (Provisioned, Registered, Not Active, Not Induced) +=> Registered, Deactivated; +- 3) (Provisioned, Registered, Active and Operative, Not Induced) +=> Registered, Activated; +- 4) (Provisioned, Registered, Active and Quiescent, Not Induced) +=> Registered, Deactivated. + +The HLR shall not pass a subaddress to a Phase 1 VLR. + +### 4.8.4 GMSC only supports Phase 1 call handling + +When a call is forwarded on not reachable at the GMSC, the HLR shall not pass the subaddress to a Phase 1 GMSC. Calls shall be forwarded without the subaddress. + +### 4.8.5 VLR only supports Phase 1 call handling + +When a call is forwarded on not reachable at the VMSC, as the HLR does not pass the subaddress to the VLR, calls shall be forwarded without the subaddress. + +### 4.8.6 VLR does not support CAMEL or supports CAMEL Phase 1 only + +When passing CFNRc information to a VLR not supporting CAMEL or supporting CAMEL Phase 1 only, the HLR shall send the registration parameter "forwarded-to number" only if it is registered in a format which the VLR can accept, i.e. international format. + +If the registration state for CFNRc is "Registered" and the forwarded-to number is registered in a format other than international, then when updating a VLR not supporting CAMEL or supporting CAMEL Phase 1 only the HLR shall modify the service state information of CFNRc as follows: + +- 1) (Provisioned, Registered, Not Active, Not Induced) +=> (Provisioned, Not Registered, Not Active, Not Induced); +- 2) (Provisioned, Registered, Active and Operative, Not Induced) +=> (Provisioned, Not Registered, Not Active, Not Induced); +- 3) (Provisioned, Registered, Active and Quiescent, Not Induced) +=> (Provisioned, Not Registered, Not Active, Not Induced). + +According to the definitions in clause 4.5 no forwarded-to number will be passed to the VLR in these cases. The modification of the service state information sent to the VLR shall have no impact on the service state information stored in the HLR. + +If the VLR supports Phase 1 updating of subscriber information only, a further translation of the service state information as defined in clause 4.8.3 shall be performed by the HLR. + +### 4.8.7 GMSC does not support CAMEL or supports CAMEL Phase 1 only + +If the activation state of CFNRc is "Active and Operative" and if the forwarded-to number is registered in a format other than international and if the GMSC does not support CAMEL or supports CAMEL Phase 1 only, then when a request for routing information for a mobile terminated call is received in the HLR, CFNRc shall not be invoked in the HLR. The mobile terminated call establishment shall be continued towards the MSCb. + +NOTE: CFNRc will be handled in the VLRb according to the service state information for CFNRc stored there. + +## 4.9 Contents of messages + +The same additions apply for CFNRc as for CFB, see clause 2.9. + +## 4.10 Support of Long Forwarded-to Numbers + +The handling for CFNRc is the same as that for CFB, see clause 2.10. + +# Annex A (informative): Change history + +| Change history | | | | | | | +|----------------|-----------|---------|--------|---------|-------------|------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | <Phase> | New Version | Subject/Comment | +| Apr 1999 | GSM 03.82 | 8.0.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.082 | | | R99 | 3.0.0 | Approved at CN#03 | +| CN#05 | 23.082 | 3.0.0 | 001 | R99 | 3.1.0 | Addition of the description related to Pre-Paging in case of "Absent Subscriber" | +| CN#07 | 23.082 | 3.1.0 | 003r3 | R99 | 3.2.0 | Introduction of 'Notification to CSE flag' to the call forwarding supplementary service. | +| CN#07 | 23.082 | 3.1.0 | 004r2 | R99 | 3.2.0 | Addition of Long Forwarded-to Numbers | +| CN#07 | 23.082 | 3.1.0 | 005 | R99 | 3.2.0 | Inclusion of TIF-CSI | +| CN#08 | 23.082 | 3.2.0 | 006 | R99 | 3.3.0 | Indication in PRN of support of Long FTNs | +| CN#08 | 23.082 | 3.2.0 | 007r1 | R99 | 3.3.0 | Interworking cases for Long Forwarded-to Numbers | +| CN#09 | 23.082 | 3.3.0 | 008r1 | R99 | 3.4.0 | SDL refresh | +| CN#10 | 23.082 | 3.4.0 | 009r1 | R99 | 3.5.0 | Correction of message between VLR and HLR | +| CN#11 | 23.082 | 3.5.0 | | Rel-4 | 4.0.0 | Release 4 after CN#11 | +| CN#12 | 23.082 | 4.0.0 | 010 | Rel-4 | 4.1.0 | Interworking cases for Long Forwarded-to Numbers | +| CN#13 | 23.082 | 4.1.0 | 012 | Rel-4 | 4.2.0 | Clarifications on long forwarded-to numbers | +| CN#16 | 23.082 | 4.2.0 | 014 | Rel-4 | 4.3.0 | "Long FTN Supported" to be transferred from VLR to HLR with Restore Data | +| CN#16 | 23.082 | 4.3.0 | | Rel-5 | 5.0.0 | Release 5 after CN#16 | +| CN#26 | 23.082 | 5.0.0 | | Rel-6 | 6.0.0 | Release 6 after CN#26 | +| CT#36 | 23.082 | 6.0.0 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#37 | 23.082 | 7.0.0 | 0015r1 | Rel-7 | 7.1.0 | | +| CT#38 | 23.082 | 7.1.0 | 0016 | Rel-7 | 7.2.0 | Information flows for Call Forwarding on Busy handling in HLR | +| CT#42 | 23.082 | 7.2.0 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | - | 8.0.0 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | - | 9.0.0 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2011-12 | 23.082 | 10.0.0 | 0017r1 | Rel-11 | 11.0.0 | CF interactions with ACR | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23085/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23085/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e03dc890d27175cc32b91a5f77530325a646f6c9 --- /dev/null +++ b/marked/Rel-11/23_series/23085/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b14ac00f3f98be1e19c2e5042506e4ae41bcd8e26464ed899557cf12978e88e +size 77312 diff --git a/marked/Rel-11/23_series/23085/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23085/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bc607ce994a6f8d507a27cf68eab6f7cfa003b2 --- /dev/null +++ b/marked/Rel-11/23_series/23085/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:617c0b91a5a433120a48d4d2e425aad3f36006ea75ca04a53e40b2b4f411ac10 +size 62405 diff --git a/marked/Rel-11/23_series/23085/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Rel-11/23_series/23085/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2eecc2529fdde0d4a685a3fe83aafe20852e2171 --- /dev/null +++ b/marked/Rel-11/23_series/23085/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a81794e32b5b078abbc8c96b0b5b7c8e84b277837f69bf301b13ad0b974d5017 +size 38898 diff --git a/marked/Rel-11/23_series/23085/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/23_series/23085/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11b396cf2223b9af99345bddbc51784db2e47131 --- /dev/null +++ b/marked/Rel-11/23_series/23085/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e8d3432cd95a0f78be7d251ab570e3a6c0a4b36176d526b51d0cd5ba0a43fa4 +size 136364 diff --git a/marked/Rel-11/23_series/23085/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-11/23_series/23085/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a445b6ad76c1c885f7012f6f239df14de6b1e4a9 --- /dev/null +++ b/marked/Rel-11/23_series/23085/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea2471b7ef048f80632f5a9fad9eddff6f7993ec1747eab80dc4ec38a610424e +size 26471 diff --git a/marked/Rel-11/23_series/23085/f57a881fcbcaf494a7dedc4f61224991_img.jpg b/marked/Rel-11/23_series/23085/f57a881fcbcaf494a7dedc4f61224991_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68c1e3829b8be6410211d5b002d596bb7c11cbb1 --- /dev/null +++ b/marked/Rel-11/23_series/23085/f57a881fcbcaf494a7dedc4f61224991_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b2e2a4022fb5494fa8d05b619c8eb71ab41df099d2ebfd05ae78d468a815bfe +size 20929 diff --git a/marked/Rel-11/23_series/23085/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23085/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44ea218f1c8f78a41ce9d64c195a6904729dcf9b --- /dev/null +++ b/marked/Rel-11/23_series/23085/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccec95544d812ca1c595b47c2410c0ed973746e7660e767d333c6b8f248b8c58 +size 82163 diff --git a/marked/Rel-11/23_series/23085/raw.md b/marked/Rel-11/23_series/23085/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7be82711e6c6eff9a6b60a861f561cc04fd9f021 --- /dev/null +++ b/marked/Rel-11/23_series/23085/raw.md @@ -0,0 +1,751 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------|----| +| Foreword ..... | 4 | +| 0 Scope..... | 5 | +| 0.1 References ..... | 5 | +| 0.2 Definitions..... | 5 | +| 0.3 Abbreviations ..... | 6 | +| 1 Closed user group (CUG) ..... | 6 | +| 1.1 Handling of Closed User Group..... | 6 | +| 1.1.1 Mobile Originated (MO) CUG call handling ..... | 6 | +| 1.1.1.1 MO CUG call handling at the MSC..... | 7 | +| 1.1.1.2 MO CUG call handling at the VLR..... | 7 | +| 1.1.2 Mobile Terminated (MT) CUG call handling ..... | 7 | +| 1.1.2.1 MT CUG handling at the GMSC..... | 7 | +| 1.1.2.2 MT CUG handling functions at the HLR ..... | 7 | +| 1.1.2.3 MT CUG handling functions at the MSC..... | 8 | +| 1.1.2.4 MT CUG handling functions at the VLR ..... | 8 | +| 1.1.3 CUG subscriber roaming requirements ..... | 8 | +| 1.1.4 CUG interworking requirements ..... | 9 | +| 1.1.4.1 Non-CUG GSM PLMNs ..... | 9 | +| 1.1.4.2 Interworking to Non-CUG networks ..... | 9 | +| 1.1.5 Supplementary service interactions..... | 9 | +| 1.1.5.1 Interaction with Call Forwarding..... | 9 | +| 1.1.5.2 Interaction with call waiting ..... | 9 | +| 1.1.5.3 Interaction with Anonymous Call Rejection ..... | 10 | +| 1.2 Functions and information flows..... | 10 | +| 1.2.1 Functions ..... | 10 | +| 1.2.2 Information flows ..... | 12 | +| 1.3 Information stored in the HLR ..... | 18 | +| 1.4 Information stored in the VLR..... | 19 | +| 1.5 Handover..... | 19 | +| 1.6 Cross phase compatibility ..... | 20 | +| 1.6.1 MSC, VLR only support phase 1 ..... | 20 | +| 1.6.2 GMSC only supports phase 1 ..... | 20 | +| Annex A (informative): Change history..... | 21 | + +# --- Foreword + +This Technical Specification has been produced by the 3<sup>rd</sup> 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. + +# --- 0 Scope + +The present document gives the stage 2 description of the closed user group supplementary service. + +The community of interest supplementary service defined is: + +- closed user group(CUG) (see clause 1). + +## 0.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: " Vocabulary for 3GPP Specifications ". + +[2] 3GPP TS 22.085: "Closed User Group (CUG) Supplementary Services; Stage 1". + +[3] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service; Stage 2". + +## 0.2 Definitions + +CUG terminology defined in 3GPP TS 22. 085 [2] is applicable to the present document. In addition, the following definitions apply. + +**CUG Authorisation Functions:** Checks performed by the network to ensure that the integrity of a CUG related call is guaranteed. CUG calls are rejected if they do not meet the criteria of these checks. + +**CUG call:** CUG call, in signalling terms, is a call where CUG information is passed from the originating switching entity to the destination entity. + +**CUG Index:** Code used to select a CUG for an outgoing call, or to indicate an incoming CUG call. Indices are passed between the user and the network and have significance only within the context of a users subscription. + +**CUG Interlock Code:** Code which uniquely identifies a CUG within a network. The Interlock code is passed from the point of origin to the destination in a CUG call to identify the CUG which has been invoked. + +**CUG Related Call Barring:** CUG related call barring is call barring applied to a CUG subscriber by the home network when roaming in a non-CUG network. The user is unable to remove CUG related call barring. + +**Explicit CUG Invocation:** Explicit CUG invocation is where a calling user attempts to invoke a CUG by passing CUG information to the network in a call request. + +**Implicit CUG Invocation:** Implicit CUG invocation is where the user invokes some default characteristic of a CUG without providing any CUG information in the call request. + +**Normal Call:** Normal call in the context of this CUG TS is a call established from a CUG subscriber where no CUG information is passed from the originating switching entity to the destination entity. + +**Outgoing Access Indicator:** Indication passed from the point of origin to the destination in a CUG call to indicate that the calling user has subscribed to the Outgoing Access inter-CUG accessibility subscription option. + +## 0.3 Abbreviations + +In addition to those listed below abbreviations used in the present document are listed in 3GPP TR 21.905 [1]. + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------|-----------------------------------------------| +| BS | Basic Service | +| CI | CUG Index | +| CUG | Closed User Group | +| IA | Incoming Access | +| IC | Interlock Code | +| IC(pref) | Interlock code of the preferential CUG | +| IC+OA | Interlock Code and Outgoing Access indicator. | +| ICB | Incoming Calls Barred within the CUG | +| OA | Outgoing Access | +| OCB | Outgoing Calls Barred within the CUG | +| Pref CUG | Preferential CUG | +| SOA | Suppress OA | +| SPC | Suppress Preferential CUG | + +# --- 1 Closed user group (CUG) + +The responsibilities of GSM network nodes with respect to CUG are described in the CUG handling clause. The Functions subclause 1.2.1 describes the CUG service logic and how CUG information is used. The flow of CUG information in various call cases is shown in the Information Flows subclause 1.2.2. + +## 1.1 Handling of Closed User Group + +A GSM PLMN supporting the CUG supplementary service must guarantee the integrity of any CUG which it handles. It is not however mandatory for a PLMN to support the CUG supplementary service. + +A CUG is uniquely identified within a network by a CUG Interlock Code. The Interlock Code is transferred between terrestrial network entities to indicate a CUG call. + +A user identifies a CUG by a CUG Index. A CUG Index is used to select or indicate the use of a specific CUG in relation to a call. The index is locally transferred between the mobile station and serving VLR and only has significance within the context of an individual subscription. + +### 1.1.1 Mobile Originated (MO) CUG call handling + +A CUG subscriber may invoke a CUG by providing the network with a CUG Index at call establishment. This is termed Explicit CUG invocation. Alternatively, if the subscription allows, some default characteristic of a CUG may be invoked automatically if no CUG information is provided. This is termed Implicit CUG invocation. The network may optionally indicate the use of an implicitly invoked CUG to the calling user. + +A CUG subscriber may suppress certain CUG attributes by providing suppression indicators during call set-up. The provision of such suppression indicators results in explicit CUG invocation. + +Any non-CUG related Call Barring supplementary service requirements shall be discharged before CUG authorisation occurs. + +#### 1.1.1.1 MO CUG call handling at the MSC + +The MSC shall pass any user provided CUG information to the VLR at call establishment. + +If an Interlock Code, or Interlock code with Outgoing Access indicator, is received from the VLR the MSC shall establish a CUG call with the destination network using this information. If a CUG Index is received from the VLR the MSC shall pass this to the calling MS. + +If the CUG call authorisation is unsuccessful the MSC shall pass an indication to the mobile station. + +#### 1.1.1.2 MO CUG call handling at the VLR + +Authorisation of a MO CUG call is performed by the serving VLR. Authorisation is determined by the information provided by the user, the subscription information stored in the VLR and the MO CUG call authorisation function, see Functions clause. + +Successful authorisation may result in a normal MO call (call without CUG information transferred to the called party) or a MO CUG call (call with CUG information transferred to the called party). + +When a CUG call is to be made the VLR passes CUG information to the MSC to be used in the call establishment. Note, the VLR may optionally pass a CUG Index to the MSC (to be passed to the calling user) to indicate that a CUG has been implicitly invoked. This parameter is not passed to the call destination. + +In the case of a normal call, no CUG information is passed to the MSC and the call is established normally. + +On authorisation failure the VLR shall reject the call providing a suitable indication to the serving MSC which is passed to the calling party. + +### 1.1.2 Mobile Terminated (MT) CUG call handling + +The terminating network is responsible for enforcing the integrity of a CUG related call. The terminating network must therefore ensure that the calling party attributes and the called party subscription meet CUG restrictions. The terminating network provides the called user with an indication of an incoming CUG call. + +Non-CUG related Call Barring supplementary service requirements are discharged before CUG authorisations. Call forwarding requirements are discharged after CUG authorisations. + +#### 1.1.2.1 MT CUG handling at the GMSC + +The GMSC shall pass any CUG information contained in an incoming call establishment message to the HLR in the routing enquiry. + +The GMSC shall continue the call establishment using the CUG information received from the HLR rather than that which was initially received. Note, in rare circumstances the HLR may discard CUG parameters, see the Call Forwarding interaction. + +If a CUG call fails the GMSC shall return an indication to the originating network. + +#### 1.1.2.2 MT CUG handling functions at the HLR + +Authorisation of a MT CUG call is performed at the called parties HLR. Authorisation is determined by the information received in the call establishment signalling, the called party subscription information stored in the HLR, and the MT CUG call authorisation function, see Functions clause. + +On successful authorisation, the HLR supplies the GMSC with CUG information for the continuation of the call establishment. On unsuccessful authorisations the HLR rejects the call supplying an indication of the reason for failure. + +#### 1.1.2.3 MT CUG handling functions at the MSC + +The MSC shall pass any CUG related information received in incoming call establishment signalling to the VLR. + +If the VLR returns CUG information to the serving MSC in response, the MSC shall pass the information to the called party in the call set-up signalling. + +If the CUG call is rejected by the VLR (due to the call forwarding interaction) the MSC shall return an indication to the originating network. + +#### 1.1.2.4 MT CUG handling functions at the VLR + +When the VLR receives an incoming call enquiry for a CUG subscriber, it shall attempt to provide a CUG call indication to the called party. The indication is sent depending on the attributes of the incoming call and the called parties subscription, as shown in table 1.1. The indication is achieved by sending the CUG Index, associated with the Interlock Code of the invoked CUG, to the called user. + +**Table 1.1: CUG Index provision at terminating VLR** + +| Calling Party CUG Information | Interlock check | Called party subscription | | Normal subscriber | | +|-------------------------------|-----------------|---------------------------|----|-------------------|--| +| | | CUG subscriber | | | | +| | | No IA | IA | | | +| | | | | | | + +| | | No ICB | ICB | No ICB | ICB | | +|-----------------------------------|----------|--------|-----|----------|----------|----------| +| Interlock | Match | Index | - | Index | - | - | +| | No Match | - | - | - | - | | +| Interlock<br>+ Outgoing<br>Access | Match | Index | - | Index | No Index | No Index | +| | No Match | - | - | No Index | - | | +| No CUG<br>Info. | - | - | - | No Index | - | No Index | + +NOTE: "-" = Not Applicable, this check is not performed since such calls are rejected by the called parties HLR. + +### 1.1.3 CUG subscriber roaming requirements + +Normal CUG restrictions apply to CUG subscribers when roaming in CUG supporting GSM PLMNs. Extra restrictions (specified in GSM 02.85) are applied to CUG subscribers roaming in non-CUG GSM VPLMNs to preserve the integrity of CUG. + +These restrictions are applied by the application of call barring programmes which are not under user control. Such restrictions only apply to a subscribers ability to make outgoing calls using CUG related basic services. Extra restrictions are not applicable in the MT call case since the requirements are met by the HLR MT CUG authorisation function and by CUG interworking restrictions. + +When a CUG subscriber first roams into a network not supporting CUG, the HLR will pass to the VLR subscription data indicating that normal Outgoing Call Barring is active for each basic service which is affected by CUG and for which the user has no CUG Outgoing Access. + +The HLR shall store the status of the CUG related barring separately from the previous user controlled status and CUG related barring shall take precedence over the user controlled status. + +The user may still perform SS operations on the user controlled Outgoing Call Barring services. The status of the barring service as a result of these operations will be stored in the HLR in the normal way, however the HLR will ensure that the VLR in the non-CUG network continues to have the CUG related call barring programs active as described above. + +When entering a CUG supporting network the CUG related barring activations shall be removed and the user controlled barring status restored. + +### 1.1.4 CUG interworking requirements + +#### 1.1.4.1 Non-CUG GSM PLMNs + +If a GSM switching entity receives a CUG Interlock code in a call establishment message but does not support the CUG service, it shall abort the call, reason for rejection: Incompatible Destination. However if an Interlock and Outgoing Access indicator are received the call shall continue to be established as a normal call with no CUG information. + +#### 1.1.4.2 Interworking to Non-CUG networks + +If a GSM switching entity is unable to interwork with a destination switching entity for a CUG call , it shall abort the call, reason for rejection: Incompatible Destination. However if the call was a CUG call indicating outgoing access the GSM switching entity shall attempt to establish the call as a normal call (no CUG information). + +### 1.1.5 Supplementary service interactions + +#### 1.1.5.1 Interaction with Call Forwarding + +The interaction between CUG and Call Forwarding services is specified in GSM 02.85. The interaction is applied after the calling and called party CUG call has been successfully authorised, and Call Forwarding has been invoked. The interaction is the same for all types of call forwarding. + +In the case of Call Forward Unconditional and Call Forwarding on Mobile Subscriber Not Reachable (invoked at HLR), the interaction is applied at the forwarding parties HLR. + +In the case of CFB, CFNRy, CFNRc (invoked at the serving VLR) the interaction is applied at the forwarding parties serving VLR. + +Table 1.2 indicates the requirements on the forwarding node when CUG and call forwarding interact. In each case the resultant information sent to the relevant MSC (either gateway or serving MSC) is given. This information should be used by the MSC for the forwarding or rejection. Note that the CUG information for the forwarding part of the call may be different from that initially used. The interlock code used for forwarding is always that of the calling party. + +**Table 1.2: CUG-Call Forwarding interaction** + +| Forwarded Party CUG Information | Interlock check | Forwarding party subscription for BS | | | | Normal subscriber | | +|---------------------------------|-----------------|--------------------------------------|--------|--------------|--------|-----------------------------|--| +| | | CUG subscriber | | | | | | +| | | No OA | | OA | | | | +| | | No OCB | OCB | No OCB | OCB | | | +| Interlock | Match | IC | Reject | IC | Reject | - | | +| Interlock +Outgoing Access | Match | IC | Reject | IC+OA | Normal | Interlock + Outgoing Access | | +| | No Match | Reject | | Interlock+OA | | | | +| No CUG Info. | - | Reject | | Normal call | | Normal call | | + +NOTE: "-" = Not applicable. + +Reason for rejection in all cases: + +Called party supplementary service interaction violation. + +#### 1.1.5.2 Interaction with call waiting + +There is no interaction with call waiting, however a CUG call indication shall be provided with the call waiting indication if the criteria for indicating a CUG call are met. + +#### 1.1.5.3 Interaction with Anonymous Call Rejection + +If a CUG call is offered to a called user belonging to the same closed user group then there is no interaction with the Anonymous Call Rejection supplementary service; even if the calling number is withheld and the called user has the Anonymous Call Rejection supplementary service the CUG call shall still be permitted. + +If the called user also has the incoming access capability within the closed user group supplementary service, and if the offered call to the called user is also a non-closed user group call or a closed user group call to which the called party does not belong, if the calling party number is withheld and the called user has the Anonymous Call Rejection supplementary service the call shall be denied as specified in 3GPP TS 23.088 [3] section 8. + +## 1.2 Functions and information flows + +### 1.2.1 Functions + +The following Mobile Additional Functions (MAF) have been identified for the CUG supplementary service: + +#### MAF14 + +Mobile Originated CUG call authorisation. + +The ability of a PLMN to determine whether a subscriber is authorised to attempt the establishment of a call request related to CUG. See figure 1.1. + +Location: VLR. + +The purpose of this function is to check the provisioning of CUG against the requested Basic Service, perform an Index to Interlock conversion where an Index is provided, check whether O/G calls are barred within the CUG, deal with preferential CUGs, OA and any CUG related suppression indicators. + +The call request may contain either no CUG information or combinations of the following CUG parameters: CUG Index, Suppress Outgoing Access indicator, Suppress Preferential CUG indicator. + +On successful authorisation the call is established with one of the following: no CUG information, CUG Interlock Code, CUG Interlock Code and Outgoing Access indicator. If a CUG is implicitly invoked the VLR may optionally provide the related CUG Index as an indication to the calling user. + +On unsuccessful authorisation the call is rejected and a rejection reason given. + +Table 1.3 specifies the VLRs response to CUG related call establishment requests. + +**Table 1.3: MO CUG Call Authorisation Function (VLR)** + +| Calling user subscrip. for Basic Service | Information provided by calling user | | | | | +|------------------------------------------|--------------------------------------|---------------------------|-------------------|-------------------------|---------------------------| +| | No CUG Info. | CUG Index (CI) or CI+SPC | Suppress OA (SOA) | Suppress Pref CUG (SPC) | CI+SOA or CI+SOA+SPC | +| CUG without Pref CUG. No OA | Reject<br>note 1 | Interlock<br>note 2, 3, 4 | Reject<br>note 1 | Reject<br>note 1 | Interlock<br>note 2, 3, 4 | +| CUG with Pref CUG. No OA | IC(pref) | Interlock<br>note 2, 3, 4 | IC(pref) | Reject<br>note 1 | Interlock<br>note 2, 3, 4 | +| CUG with OA and without Pref CUG | Normal call | IC+OA<br>note 3, 4, 5 | Reject<br>note 1 | Normal call | Interlock<br>note 2, 3, 4 | +| CUG with Pref CUG and with OA | IC(pref)+OA | IC+OA<br>note 3, 4, 5 | IC(pref) | Normal call | Interlock<br>note 2, 3, 4 | +| Normal subscriber | Normal call | Normal call | Normal call | Normal call | Normal call | + +NOTE 1: "Inconsistent access information - no CUG selected". + +NOTE 2: If the intra-CUG restriction option "Outgoing calls barred within the CUG" is applicable for the requested CUG, the call shall be rejected, reason for rejection "Outgoing calls barred within the CUG". + +NOTE 3: If an index is provided which is not recognised by the network the call is rejected, reason for rejection "Unknown CUG Index". + +NOTE 4: If an index is provided which does not match with the interlock(s) of the requested basic service the call is rejected, reason for rejection "Inconsistent access information - Index incompatible with requested basic service". + +NOTE 5: If a CUG is selected using a CUG Index but the intra-CUG restriction option "Outgoing calls barred within the CUG" is applicable, and the calling user subscription includes OA for the requested Basic Service the call shall be attempted as a normal call with no CUG information included in the call establishment signalling. + +An SDL indicating when the authorisation function is invoked in the VLR is shown in figure 1.1. Inputs and outputs to the SDL apply to the serving MSC. + +#### MAF15 + +Mobile Terminated CUG call authorisation. + +The ability of a PLMN to compare received calling party information against a called party subscription for CUG integrity. See figure 1.2. + +Location: HLR. + +The purpose of this function is to identify a match between calling and called party CUG attributes for a given basic service, whilst enforcing intra-CUG communication restrictions. If no match is obtained the call is rejected. + +The calling party CUG attributes may be either a CUG Interlock Code or a CUG Interlock Code and Outgoing Access indicator. + +Table 1.4 indicates the HLRs response to incoming CUG calls, or incoming calls to CUG subscribers. + +On successful authorisation the call establishment is continued using one of the following: no CUG information, CUG Interlock Code, Interlock Code and Outgoing Access indicator. + +On unsuccessful authorisation the call is rejected and a rejection reason given. + +**Table 1.4: MT CUG Call Authorisation Function (HLR)** + +| Calling Party CUG Information | Inter-lock check | Called party subscription for Basic Service | | | | Normal subs. | | +|------------------------------------|------------------|---------------------------------------------|---------------|----------------|---------------|---------------|--| +| | | CUG subscriber | | | | | | +| | | No IA | | IA | | | | +| | | No ICB | ICB | No ICB | ICB | | | +| Interlock Code (IC) | Match | Interlock Code | Reject note 1 | Interlock Code | Reject note 1 | Reject note 2 | | +| | No Match | Reject note 2 | | Reject note 2 | | | | +| Interlock +Outgoing Access (IC+OA) | Match | IC+OA | Reject note 1 | IC+OA | IC+OA | IC+OA | | +| | No Match | Reject note 2 | | IC+OA | | | | +| No CUG Info. | - | Reject note 3 and 4 | | Normal call | | Normal call | | + +Notes on reasons for rejections: + +NOTE 1: "Incoming calls barred within the CUG". + +NOTE 2: "Interlock mismatch". + +NOTE 3: "Requested basic service violates CUG constraints" A non-CUG call has invoked (via a particular basic service) a CUG which does not have an Incoming Access capability. + +NOTE 4: See subclause 1.6. + +An SDL indicating when the function is invoked in the HLR is shown in figure 1.2. Inputs and outputs to the SDL apply to the GMSC. + +### 1.2.2 Information flows + +The information flows for the CUG supplementary service are shown in figures 1.3 to 1.7. + +List of figures: + +- figure 1.3 Mobile Originated CUG calls; +- figure 1.4 Mobile Terminated CUG calls; +- figure 1.5 MT CUG call handling at the called party MSC/VLR; +- figure 1.6 Interworking with Non-ISDN/Non-GSM networks; +- figure 1.7 CUG interworking with Non-CUG GSM PLMN. + +NOTE to figures 1.3 to 1.7: + +"Conditional CUG Info" means that CUG information may or may not be present in the signalling message depending on the call case. These figures are intended to cover all call cases described in the CUG authorisation functions. + +![Flowchart for Process CUG_MAF014: Mobile Originated CUG call authorisation (VLR).](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Process CUG\_MAF014 + +385\_11(1) + +``` +graph TD; idle1([idle]) --> request{outgoing call request}; request --> decision1{CUG provisioned on requested basic service}; decision1 -- no --> normal[perform normal call authorisation]; decision1 -- yes --> mo[perform MO CUG authorisation]; mo --> decision2{CUG authorisation outcome}; decision2 -- fail --> reject[reject call (cause)]; decision2 -- pass --> complete[complete call (conditional CUG info)]; normal --> response{response to call request}; complete --> join(( )); reject --> join; response --> join; join --> idle2([idle]); +``` + +The flowchart illustrates the process for Mobile Originated CUG call authorisation (VLR). It begins with an 'idle' state, followed by an 'outgoing call request'. A decision is made regarding whether the CUG is provisioned on the requested basic service. If 'no', it proceeds to 'perform normal call authorisation', which leads to a 'response to call request'. If 'yes', it proceeds to 'perform MO CUG authorisation', which leads to a 'CUG authorisation outcome' decision. If the outcome is 'fail', it proceeds to 'reject call (cause)'. If the outcome is 'pass', it proceeds to 'complete call (conditional CUG info)'. Both 'response to call request', 'complete call (conditional CUG info)', and 'reject call (cause)' lead to a common junction point, which then leads back to the 'idle' state. There are two callouts: 'Authorisation criteria are defined in table 1.3.' pointing to the 'perform MO CUG authorisation' block, and 'The content of (conditional CUG info) and (cause) are detailed in table 1.3.' pointing to the 'reject call (cause)' block. + +Flowchart for Process CUG\_MAF014: Mobile Originated CUG call authorisation (VLR). + +Figure 1.1: MAF014 Mobile Originated CUG call authorisation (VLR) + +![Flowchart for Process CUG_MAF015 (Mobile Terminated CUG call authorisation).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Process CUG\_MAF015 + +385\_12(1) + +``` + +graph TD + Start([idle]) --> Incoming[/incoming +call/] + Incoming --> Provisioned{CUG provisioned for +the called party against +the basic service requested} + + Provisioned -- no --> InfoProvided{CUG +info +provided} + Provisioned -- yes --> PerformMT[perform +MT CUG +authorisation] + + InfoProvided -- yes --> PerformMT + InfoProvided -- no --> PerformNormal[perform +normal call +authorisation] + + PerformMT --> Outcome{CUG +authorisation +outcome} + + Outcome -- pass --> Complete[complete call +(conditional +CUG info)] + Outcome -- fail --> Reject[reject +call +(cause)] + + PerformNormal --> Response[response +to call +request] + + Complete --> End([idle]) + Reject --> End + Response --> End + + subgraph Notes + Note1[Authorisation criteria are defined +in table 1.4.] + Note2[The content of (conditional +CUG info) and (cause) are +detailed in table 1.4.] + end + + PerformMT -.- Note1 + Complete -.- Note2 + Reject -.- Note2 + +``` + +Flowchart for Process CUG\_MAF015 (Mobile Terminated CUG call authorisation). + +**Figure 1.2: MAF015 Mobile Terminated CUG call authorisation (HLR)** + +![Sequence diagrams for Mobile Originated CUG calls showing four scenarios: 1. MO CUG call request (conditional setup), 2. MO CUG call authorisation unsuccessful (reject), 3. Successfully authorised MO CUG call (destination network does not support CUG), 4. Destination network supports CUG, MT CUG Authorisation unsuccessful. Includes lifelines for MS, MSC, VLR, and NWb-GMSC.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates four sequence scenarios for Mobile Originated (MO) CUG calls between a Mobile Station (MS), Mobile Switching Center (MSC), Visitor Location Register (VLR), and NWb-GMSC. + +**Scenario 1: MO CUG call request** + +- MS sends a **Set-up** message to MSC. +- MSC sends a **(Conditional User CUG Info)** message to VLR. +- VLR sends a **Send info O/G call** message to NWb-GMSC. +- NWb-GMSC returns a **(Conditional User CUG Info)** message to VLR. + +**Scenario 2: MO CUG call authorisation unsuccessful** + +- MSC sends a **Reject** message to VLR. +- VLR returns a **(Cause)** message to MSC. +- MSC sends a **Disconnect** message to MS. +- MS returns a **(Cause)** message to MSC. +- MAF14: Fail + +**Scenario 3: Successfully authorised MO CUG call, destination network does not support CUG** + +- MSC sends a **Complete** message to VLR. +- VLR returns a **(Conditional CUG Info)** message to MSC. +- MSC sends a **Set-up** message to MS. +- MS sends an **Indication\*** message to MSC. +- MSC returns a **(Conditional CUG Info)** message to VLR. +- MSC sends a **Disconnect** message to MS. +- MS returns a **(Cause)** message to MSC. +- MAF14: Pass + +**Scenario 4: Destination network supports CUG, MT CUG Authorisation unsuccessful** + +- MSC sends a **Set-up** message to VLR. +- VLR returns a **(Conditional CUG Info)** message to MSC. +- MSC sends an **Indication\*** message to MS. +- MS returns a **(Index)** message to MSC. +- MSC sends a **Disconnect** message to MS. +- MS returns a **(Cause)** message to MSC. +- MAF15: Fail + +**Scenario 5: Destination network supports CUG, MT CUG Authorisation successful** + +- MSC sends an **Answer** message to VLR. +- VLR returns a **(Cause)** message to MSC. +- MAF15: Pass + +Sequence diagrams for Mobile Originated CUG calls showing four scenarios: 1. MO CUG call request (conditional setup), 2. MO CUG call authorisation unsuccessful (reject), 3. Successfully authorised MO CUG call (destination network does not support CUG), 4. Destination network supports CUG, MT CUG Authorisation unsuccessful. Includes lifelines for MS, MSC, VLR, and NWb-GMSC. + +NOTE: MAF14: MO CUG call Authorisation + MAF15: MT CUG call Authorisation + \*: Optional message + +**Figure 1.3: Mobile Originated CUG calls** + +![Sequence diagram for Mobile Terminated CUG calls between NWa, GMSCb, HLRb, and MSCb. It shows an incoming CUG call, an unsuccessful MT CUG call authorisation (MAF15: Fail), and a successful MT CUG call (MAF15: Pass).](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant NWa + participant GMSCb + participant HLRb + participant MSCb + + Note left of NWa: Incoming CUG call + NWa->>GMSCb: Set-up + Note right of GMSCb: (Conditional CUG Info) + GMSCb->>HLRb: Routing Request + Note right of HLRb: (Conditional CUG Info) + + Note left of NWa: Unsuccessful MT CUG call authorisation + HLRb-->>GMSCb: MAF15: Fail + GMSCb-->>NWa: Reject + Note right of GMSCb: (Cause) + NWa-->>GMSCb: Disconnect + Note right of GMSCb: (Cause) + + Note left of NWa: Successful MT CUG call + HLRb-->>GMSCb: MAF15: Pass + GMSCb-->>NWa: Routing info. + Note right of GMSCb: (Conditional CUG Info) + NWa->>GMSCb: Set-up + Note right of GMSCb: (Conditional CUG Info) + +``` + +Sequence diagram for Mobile Terminated CUG calls between NWa, GMSCb, HLRb, and MSCb. It shows an incoming CUG call, an unsuccessful MT CUG call authorisation (MAF15: Fail), and a successful MT CUG call (MAF15: Pass). + +NOTE: MAF15: MT CUG call authorisation. + +**Figure 1.4: Mobile Terminated CUG calls** + +![Sequence diagram for MT CUG call handling at called party MSC/VLR between GMSCb, VLRb, MSCb, and MSb. It shows a successful incoming CUG call at the B party MSC/VLR.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +``` + +sequenceDiagram + participant GMSCb + participant VLRb + participant MSCb + participant MSb + + Note left of GMSCb: Successful incoming CUG call at B party MSC/VLR + GMSCb->>VLRb: Set-up + Note right of VLRb: (Conditional CUG Info) + VLRb-->>GMSCb: I/C Call + Note right of GMSCb: (Conditional CUG Info) + GMSCb->>VLRb: Complete + Note right of VLRb: (Conditional Index) + VLRb->>MSCb: Set-up + Note right of MSCb: (Conditional Index) + +``` + +Sequence diagram for MT CUG call handling at called party MSC/VLR between GMSCb, VLRb, MSCb, and MSb. It shows a successful incoming CUG call at the B party MSC/VLR. + +**Figure 1.5: MT CUG call handling at called party MSC/VLR** + +MSC                                              VLR                                              IWMSC                                              LE + +#### Successfully authorised MO CUG call, via interworking exchange + +![Sequence diagram for Figure 1.6 showing MO CUG call authorization via interworking exchange between MSC, VLR, IWMSC, and LE.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` + +sequenceDiagram + participant MSC + participant VLR + participant IWMSC + participant LE + + Note over VLR: MAF14:Pass + VLR-->>MSC: Complete + Note over MSC: (CUG Info) + MSC->>VLR: Set-up + Note over VLR: (CUG Info) + VLR->>IWMSC: OR1: No + IWMSC-->>VLR: Release + Note over VLR: (Cause) + VLR->>IWMSC: OR1: Yes + IWMSC->>LE: Set-up + Note over LE: No CUG Info + +``` + +Sequence diagram for Figure 1.6 showing MO CUG call authorization via interworking exchange between MSC, VLR, IWMSC, and LE. + +NOTE: MAF14: MO CUG call Authorisation +OR1: CUG Info = IC+OA + +**Figure 1.6: Interworking with Non-ISDN/Non-GSM networks** + +MS                                              GMSCa                                              GMSCb                                              HLRb + +#### Successfully authorised MO CUG call to non-CUG GSM network + +![Sequence diagram for Figure 1.7 showing MO CUG call authorization to a non-CUG GSM network between MS, GMSCa, GMSCb, and HLRb.](f57a881fcbcaf494a7dedc4f61224991_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GMSCa + participant GMSCb + participant HLRb + + GMSCa->>GMSCb: Set-up + Note over GMSCb: (CUG Info) + GMSCb->>GMSCa: OR1:No + GMSCa-->>GMSCb: Release + Note over GMSCb: (Cause) + GMSCa-->>MS: Disconnect + Note over MS: (Cause) + GMSCb->>HLRb: OR1:Yes + HLRb->>GMSCb: Set-up + Note over GMSCb: No CUG Info + +``` + +Sequence diagram for Figure 1.7 showing MO CUG call authorization to a non-CUG GSM network between MS, GMSCa, GMSCb, and HLRb. + +NOTE: OR1: CUG Info = IC+OA + +**Figure 1.7: CUG Interworking with Non-CUG GSM PLMN** + +## 1.3 Information stored in the HLR + +For the supplementary service Closed User Group the HLR shall store: + +- per subscription (IMSI) a list of CUG Interlock codes up to a maximum specified in GSM 02.85. + +Against each Interlock code the following parameters shall be stored: + +- CUG Index; +- Intra-CUG restrictions; +which may take one of the following values: + - None; + - Incoming calls barred within the CUG; + - Outgoing calls barred within the CUG. +- Application to basic services; +which may take one of the following types of value: + - List of Basic Services Groups for which the CUG applies; + - All basic services. + +Against each Basic Service Group which is subject to CUG, the following shall be stored: + +- Inter-CUG accessibility; +which may take one of the following values: + - None designated; + - Outgoing Access; + - Incoming Access; + - Outgoing and Incoming Access. +- Preferential CUG; +which may take one of the following types of value: + - CUG Index; + - None designated. + +## 1.4 Information stored in the VLR + +For the supplementary service Closed User Group the VLR shall store: + +- per subscription (IMSI) a list of CUG Interlock codes up to a maximum specified in GSM 02.85. + +Against each Interlock code the following parameters shall be stored: + +- CUG Index; +- Intra-CUG restrictions; +which may take one of the following values: + - None; + - Incoming calls barred within the CUG; + - Outgoing calls barred within the CUG. +- Application to basic services; +which may take one of the following types of value: + - List of Basic Services Groups for which the CUG applies; + - All basic services. + +Against each Basic Service Group which is subject to CUG, the following shall be stored: + +- Inter-CUG accessibility; +which may take one of the following values: + - None designated; + - Outgoing Access; + - Incoming Access; + - Outgoing and Incoming Access. +- Preferential CUG; +which may take one of the following types of value: + - CUG Index; + - None designated. + +## 1.5 Handover + +Handover will have no impact on the control procedures and operation of the service. + +## 1.6 Cross phase compatibility + +### 1.6.1 MSC, VLR only support phase 1 + +See subclause 1.1.3 "CUG subscriber roaming requirements". + +### 1.6.2 GMSC only supports phase 1 + +When a routing request according to MAP phase 1 from GMSC (no CUG info) is received in the HLR and the called party does not have Incoming Access capability the HLR shall reject the routing request with the error "Call barred" instead the error "CUG-Reject". + +NOTE: The error "CUG-Reject" is not available in the MAP phase 1 protocol. + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|-----------|---------|------|-----|--------|-----|---------|-------------------------------------------------------| +| TSG CN# | Spec | Old Ver | CR | Rev | Phase | Cat | New Ver | Subject/Comment | +| Apr 1999 | GSM 03.85 | 6.0.0 | | | R97 | | | Transferred to 3GPP CN1 | +| CN#03 | 23.085 | | | | R99 | | 3.0.0 | Approved at CN#03 | +| | 23.085 | 3.0.0 | | | R99 | | 3.0.1 | References updated from 2G to 3G | +| CN#09 | 23.085 | 3.0.1 | 001 | 1 | R99 | F | 3.1.0 | SDL refresh | +| CN#11 | 23.085 | 3.1.0 | | | Rel-4 | | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.085 | 4.0.0 | | | Rel-5 | | 5.0.0 | Release 5 after CN#16 | +| CN#26 | 23.085 | 5.0.0 | | | Rel-6 | | 6.0.0 | Release 6 after CN#26 | +| CT#30 | 23.085 | 6.0.0 | 002 | | Rel-6 | | 6.1.0 | Incorrect References | +| CT#36 | 23.085 | 6.1.0 | | | Rel-7 | | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.085 | 7.0.0 | | | Rel-8 | | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.085 | 8.0.0 | - | - | Rel-9 | | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.085 | 9.0.0 | - | - | Rel-10 | | 10.0.0 | Update to Rel-10 version (MCC) | +| 2011-09 | 23.085 | 10.0.0 | 0003 | | Rel-11 | | 11.0.0 | Addition of Anonymous Call Rejection in the CS domain | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23093/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-11/23_series/23093/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0595a78841e84fed3cf038e8a4a711693690e7a --- /dev/null +++ b/marked/Rel-11/23_series/23093/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c64b5c8c6b426436f0f01ff4539b1a8934d40156b65170741c39a89ab7c6722 +size 145013 diff --git a/marked/Rel-11/23_series/23093/09797d4289ec96309d21a9a993153dab_img.jpg b/marked/Rel-11/23_series/23093/09797d4289ec96309d21a9a993153dab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b4b9960045cdd7e089e033e4e312654c4309fca --- /dev/null +++ b/marked/Rel-11/23_series/23093/09797d4289ec96309d21a9a993153dab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f2469bb92f44e8f1bb6af7616a6437b535bf82093a946cd20c8cccf7fe0036a +size 52202 diff --git a/marked/Rel-11/23_series/23093/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-11/23_series/23093/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb805358063249ad5fb91ac643a760db21dc84a6 --- /dev/null +++ b/marked/Rel-11/23_series/23093/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5eb652ffdc5ab7658eb7911f2747ce7a1b4373fcbb5d8d59bd479a460901d94b +size 76042 diff --git a/marked/Rel-11/23_series/23093/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-11/23_series/23093/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0477a4ea78c155993e16c7e2d9de8200191a6514 --- /dev/null +++ b/marked/Rel-11/23_series/23093/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9da1b8bccc356b5c86f88e2810db07d27331c252165d1f88c4c4ab8cbcb94ad2 +size 74378 diff --git a/marked/Rel-11/23_series/23093/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-11/23_series/23093/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..739a5b1d88fae43fbb9f30446b85939f85f85fe0 --- /dev/null +++ b/marked/Rel-11/23_series/23093/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00558b327bf50162451307362918e3a858727f70d87eecff1296998d8b39598b +size 55670 diff --git a/marked/Rel-11/23_series/23093/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-11/23_series/23093/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5da38bd7682ed0efbf69d7cf9e7420e1507f0043 --- /dev/null +++ b/marked/Rel-11/23_series/23093/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9aa9f47d6eacc12f7352454061638c27859fa41f4a725c809b0f7ca973564482 +size 82919 diff --git a/marked/Rel-11/23_series/23093/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-11/23_series/23093/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c51b473d42c98c9dbda03ff6c9aa925123dc0d7 --- /dev/null +++ b/marked/Rel-11/23_series/23093/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e3c88d2a5d0997f06e09af6602b2ad6803a66cadbe1ab99052bcbe6feb5bacf +size 58075 diff --git a/marked/Rel-11/23_series/23093/18722c46c9e8475524e634dedd08bac2_img.jpg b/marked/Rel-11/23_series/23093/18722c46c9e8475524e634dedd08bac2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..013b7795f5ce141de40ec56e369385184a052ec8 --- /dev/null +++ b/marked/Rel-11/23_series/23093/18722c46c9e8475524e634dedd08bac2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f890a637a047b4336f70558365c463cad2f435be817a312496fd3b017de72374 +size 53863 diff --git a/marked/Rel-11/23_series/23093/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/23_series/23093/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..214efdf0194e4a8fc1808a1c75498cfdabbc1fae --- /dev/null +++ b/marked/Rel-11/23_series/23093/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:089afd7f3c7a28ceac86e9c05e7fedff6e05ef1860f897c7342c3d73f74fed37 +size 86933 diff --git a/marked/Rel-11/23_series/23093/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/Rel-11/23_series/23093/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..243dc7ee49e23f848f8bca667174d01bee4af840 --- /dev/null +++ b/marked/Rel-11/23_series/23093/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:895385e82759528864e581461a1ca00a1443063eacaffa212a53ec4d8aafd348 +size 93620 diff --git a/marked/Rel-11/23_series/23093/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg b/marked/Rel-11/23_series/23093/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81228eae8321a03f0f9172ee3cafbdb32f06e3a4 --- /dev/null +++ b/marked/Rel-11/23_series/23093/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64d88cef37816120e84aa8a7ee847f106787a75957d5edc50ecac2707cbcc90e +size 118774 diff --git a/marked/Rel-11/23_series/23093/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-11/23_series/23093/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b293d4a0d3b42f5b23f19dd52fbdc7d2b9df375 --- /dev/null +++ b/marked/Rel-11/23_series/23093/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c68f3f198b0bd3b32dcbc9a9f871485050c2dd02b3b6641b9894b9350bfaf90 +size 56817 diff --git a/marked/Rel-11/23_series/23093/223792b3652794024244c277cc46394b_img.jpg b/marked/Rel-11/23_series/23093/223792b3652794024244c277cc46394b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b366a58e98c82083d232bed476e381c941e3fed5 --- /dev/null +++ b/marked/Rel-11/23_series/23093/223792b3652794024244c277cc46394b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baf0bbbd0d6ab42703de160ebf7eb41d11fc8365c3fc4ba694885e14b1387a13 +size 77035 diff --git a/marked/Rel-11/23_series/23093/245166735676c675f98f535bc4c6f0a1_img.jpg b/marked/Rel-11/23_series/23093/245166735676c675f98f535bc4c6f0a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..940b5c466a1a7ba98ab7fa37548e5860a8004e48 --- /dev/null +++ b/marked/Rel-11/23_series/23093/245166735676c675f98f535bc4c6f0a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf939ea1e0a392e5f0b578e1ed5c7eeb5def240b53ba4ffe37ea01fdb1045ab5 +size 59685 diff --git a/marked/Rel-11/23_series/23093/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23093/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47da503fcd6ce4d2026e3e8ca60954627ab20c34 --- /dev/null +++ b/marked/Rel-11/23_series/23093/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbac53e040758a99413020fd8311c54e5f4b6fc4b597597e646938d8177e3855 +size 177893 diff --git a/marked/Rel-11/23_series/23093/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-11/23_series/23093/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df7de143977ef7f7487bd416e75a002c307d4ba4 --- /dev/null +++ b/marked/Rel-11/23_series/23093/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae334281eec8f3719fc9ee02b0c95d3a3cf042453755b0137ec86c9f6209c380 +size 132025 diff --git a/marked/Rel-11/23_series/23093/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-11/23_series/23093/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edc09509ed1eb7990a6dea8cc302ee2cd43ae950 --- /dev/null +++ b/marked/Rel-11/23_series/23093/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a77ebd32a88e2f21883745baf979b1bf9074fbce51b5a7d748feefe389bb636a +size 94536 diff --git a/marked/Rel-11/23_series/23093/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/23_series/23093/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adaadbd03d00d714eb40fe609127c08c9e563b86 --- /dev/null +++ b/marked/Rel-11/23_series/23093/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:744e2e6a722f7edd8023e6a742c8d5f9038ca8a22962a3be161226f6bebd8915 +size 77705 diff --git a/marked/Rel-11/23_series/23093/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg b/marked/Rel-11/23_series/23093/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..911683d0077fc8879b4941f073fed506a0cfa65b --- /dev/null +++ b/marked/Rel-11/23_series/23093/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7d677ea2abc9c0912dd7fdb92df2acadb0a1ab21dc622a2ac046ceead402c91 +size 47417 diff --git a/marked/Rel-11/23_series/23093/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-11/23_series/23093/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bf811bc38618cc03dcb711df219fef4dd205143 --- /dev/null +++ b/marked/Rel-11/23_series/23093/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d5c9a25aaa6c70d96adf41b8f923175fcd92e88fd5625f939f4f2ef43cbc370 +size 97885 diff --git a/marked/Rel-11/23_series/23093/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-11/23_series/23093/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44e3faf4b560191594f9063a0b578764fc870b59 --- /dev/null +++ b/marked/Rel-11/23_series/23093/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9855471ee7e434c361e3f34d815f999173013d876e7076b7c5580e0dfd9dcc24 +size 83700 diff --git a/marked/Rel-11/23_series/23093/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/23_series/23093/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acbb91b353d91cd8777cf4f83d0dcb143d7e5d4b --- /dev/null +++ b/marked/Rel-11/23_series/23093/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bd7f3b77d12840b5402d91d36b90d4b1e705292213d481f6c460a321c06304c +size 101240 diff --git a/marked/Rel-11/23_series/23093/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/23_series/23093/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5297d30b0b11811f443ef8c717ac9eeee6eb80ca --- /dev/null +++ b/marked/Rel-11/23_series/23093/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:809ef9a3bf5eaaca749401273be5d0110365e42a08f7e255a25dc63bf9d5382f +size 108614 diff --git a/marked/Rel-11/23_series/23093/3334fcca5dac808f4fd3840aba35bc2e_img.jpg b/marked/Rel-11/23_series/23093/3334fcca5dac808f4fd3840aba35bc2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d421e0b6cd953ce19bf7c44d8de776f186babf9 --- /dev/null +++ b/marked/Rel-11/23_series/23093/3334fcca5dac808f4fd3840aba35bc2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df334efa4ac9a4f23d3cfb79414da6f86c19a9d429bdac3798cb50fc2a14cacb +size 71688 diff --git a/marked/Rel-11/23_series/23093/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-11/23_series/23093/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f47cefc0672c26dd68efa1cd6b7054a024d1f475 --- /dev/null +++ b/marked/Rel-11/23_series/23093/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:113a9ecc2e67b2dde6bfd3711051a8c8d3665c7df9e8bd79119ba5153ab4d41e +size 58826 diff --git a/marked/Rel-11/23_series/23093/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-11/23_series/23093/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11ff666c8c1269513f67056efd6e35c9f1fdfe26 --- /dev/null +++ b/marked/Rel-11/23_series/23093/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7f8360861154d818a294c23d87da08686657c1c9abb0830ba9810a23158c6f4 +size 73165 diff --git a/marked/Rel-11/23_series/23093/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-11/23_series/23093/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cc433f84aec98bfbd533c91eacf2efa38137e74 --- /dev/null +++ b/marked/Rel-11/23_series/23093/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbf6ed9fa5f7fa4b971433c85515accb3504a2016d7a0a69700273718006bed8 +size 118809 diff --git a/marked/Rel-11/23_series/23093/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-11/23_series/23093/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ecf4f5f9ba9092b28ee09920e65903050350d29 --- /dev/null +++ b/marked/Rel-11/23_series/23093/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ed9518579cf1ecec0eb27d50c05b52818669d269d61f3e1d11e102680b578b4 +size 82780 diff --git a/marked/Rel-11/23_series/23093/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-11/23_series/23093/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bd590377336f774f5a7bda03534be93efe4b02d --- /dev/null +++ b/marked/Rel-11/23_series/23093/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec30d8fc9daf4cf4828761a105aebb95320c8eb1a43b98777e66c36efe5845a7 +size 76186 diff --git a/marked/Rel-11/23_series/23093/3ec35c497a0765a1a885c85f214b1bef_img.jpg b/marked/Rel-11/23_series/23093/3ec35c497a0765a1a885c85f214b1bef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52ed13630775ba90ad73ab3873f9e3f21a63dba5 --- /dev/null +++ b/marked/Rel-11/23_series/23093/3ec35c497a0765a1a885c85f214b1bef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c6dfcd1815409457c36a4ca31bb48bcfde5d515d498e61cce395a4568d65cae +size 52831 diff --git a/marked/Rel-11/23_series/23093/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-11/23_series/23093/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bcd812b76a800d11a1284f923c45ea524dff1c9 --- /dev/null +++ b/marked/Rel-11/23_series/23093/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a504f72d9fa10ded8c979fafd24195833d200d8cea8d6a277c05fcabd6acfb7a +size 97992 diff --git a/marked/Rel-11/23_series/23093/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-11/23_series/23093/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4a46f76386b428fc3950bc8163af671f49675e2 --- /dev/null +++ b/marked/Rel-11/23_series/23093/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e5af6b56ecda22d98d7ce2e1cef6115a502aab54f6372033546128de512f6cb +size 104814 diff --git a/marked/Rel-11/23_series/23093/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-11/23_series/23093/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19e9ca0e7d2fe44786450f94125b414f6c9a59b5 --- /dev/null +++ b/marked/Rel-11/23_series/23093/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64afe411e771d57c333b601de93569863e7f554e7f8e7cb3dcd8e2b431e2c573 +size 77502 diff --git a/marked/Rel-11/23_series/23093/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-11/23_series/23093/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..495a8d819dd2804b605402622770050f1105f8ce --- /dev/null +++ b/marked/Rel-11/23_series/23093/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f92a9f0a63ed34804f5eb198b04212a6041374828c91a3628d0bdd91c0192315 +size 68850 diff --git a/marked/Rel-11/23_series/23093/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-11/23_series/23093/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d6e821c4cdd0b7be25c6ec705385bc469336cca --- /dev/null +++ b/marked/Rel-11/23_series/23093/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7521ff8aad3ffdb84f203335425677c57cff01745314217a6ff5242071c542e1 +size 39871 diff --git a/marked/Rel-11/23_series/23093/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-11/23_series/23093/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..343401d577b5737fb066b9d0e5c672dd66239741 --- /dev/null +++ b/marked/Rel-11/23_series/23093/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03b8a23bf8013c8328fe14eaab0661964f01e3f76d4f37cf9bf012469de012c7 +size 56058 diff --git a/marked/Rel-11/23_series/23093/511f9b05a4c458937dd12c30936fd7d6_img.jpg b/marked/Rel-11/23_series/23093/511f9b05a4c458937dd12c30936fd7d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1c38e4b81905d260c4cca3061ff2490d3051b0b --- /dev/null +++ b/marked/Rel-11/23_series/23093/511f9b05a4c458937dd12c30936fd7d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b52c31a72bdbbde11e99e7d5422dadd425d44122dacd4b3fbd3b4a1c6c66576 +size 69554 diff --git a/marked/Rel-11/23_series/23093/536768a30136cd5c2d57f46c25d1d804_img.jpg b/marked/Rel-11/23_series/23093/536768a30136cd5c2d57f46c25d1d804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88cb93e836b4920d15894fcd825b84455d6b560f --- /dev/null +++ b/marked/Rel-11/23_series/23093/536768a30136cd5c2d57f46c25d1d804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32b8caad7f39ff8b40036ab5d7516743f64b3925342cae7bcdccd0f53f93f419 +size 60561 diff --git a/marked/Rel-11/23_series/23093/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-11/23_series/23093/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8173dba552c6ddcf171f079152b5fe91ae7a9d14 --- /dev/null +++ b/marked/Rel-11/23_series/23093/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64d4e046ab4a8ff5f6a95ca51570d25e89cb3ce5e5c4d03b81e9f31c8f41af82 +size 115678 diff --git a/marked/Rel-11/23_series/23093/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-11/23_series/23093/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac75c7c82b582cd2ba31d57c550a53fb7590ce8d --- /dev/null +++ b/marked/Rel-11/23_series/23093/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9d1a46c707cc261bb4fb0826a047a0f4ddd6b79de73fc8ce653d52bc7439953 +size 85841 diff --git a/marked/Rel-11/23_series/23093/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/23_series/23093/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c812be3dd0902bcb9ecbd40e4384ade06c57e74 --- /dev/null +++ b/marked/Rel-11/23_series/23093/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:537dff2909430e6944869c786223804c8e203893fa7962d640d96c6ba903c09f +size 192619 diff --git a/marked/Rel-11/23_series/23093/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-11/23_series/23093/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf752045c7018c9f3117faefff476a688e17b726 --- /dev/null +++ b/marked/Rel-11/23_series/23093/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c02ec0994d33f4c8d155b236cec306f7011f7327fdc3336e25e1dd916a8daf3 +size 72473 diff --git a/marked/Rel-11/23_series/23093/5e022ae60ba810b1e6de0645671b9dd3_img.jpg b/marked/Rel-11/23_series/23093/5e022ae60ba810b1e6de0645671b9dd3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d3e684620aa6ddd8ad84ef04fa6d154d0b20694 --- /dev/null +++ b/marked/Rel-11/23_series/23093/5e022ae60ba810b1e6de0645671b9dd3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c19648af5bbb1ef07bfae0419f6da454bceb061852d6c626c8a773bbf5e67d60 +size 48692 diff --git a/marked/Rel-11/23_series/23093/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-11/23_series/23093/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b36c4a50438f93947220b9c0c334c1ee5d36571 --- /dev/null +++ b/marked/Rel-11/23_series/23093/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7df99b65600ed2289a5450790ceb1346bb984e431fe0d09ea97a8c2718efb0a9 +size 111720 diff --git a/marked/Rel-11/23_series/23093/6059b0a3a051cc20b414d51a4e412f3e_img.jpg b/marked/Rel-11/23_series/23093/6059b0a3a051cc20b414d51a4e412f3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63183e2060b09d2c9de0fc8f8fed0fd67bd0a279 --- /dev/null +++ b/marked/Rel-11/23_series/23093/6059b0a3a051cc20b414d51a4e412f3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2edf6153240fa0ca7522463f417e3e749c98a0b2c58f689f8fb1a6c2a28353d2 +size 51871 diff --git a/marked/Rel-11/23_series/23093/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/23_series/23093/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4dc754a56e71700db59e978d539f476574fe150b --- /dev/null +++ b/marked/Rel-11/23_series/23093/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58e71849ab0219ce47c3590a54d1c1501433297f0034f8dfd9ae1e39446b80a6 +size 95585 diff --git a/marked/Rel-11/23_series/23093/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg b/marked/Rel-11/23_series/23093/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6c8dff383dbe00221cf0c87159bb3ad65f7c1b0 --- /dev/null +++ b/marked/Rel-11/23_series/23093/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9524be84459e3986417e5e70c9aadc6520ebb8e0ea79bd9ece8165ce393c7f07 +size 85871 diff --git a/marked/Rel-11/23_series/23093/649426750a89fa0e5d7c1736d5cf72c6_img.jpg b/marked/Rel-11/23_series/23093/649426750a89fa0e5d7c1736d5cf72c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03e4e4a5a4458e23f5d739d6a6583d9fd23efbe7 --- /dev/null +++ b/marked/Rel-11/23_series/23093/649426750a89fa0e5d7c1736d5cf72c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6130057551cf27540fc74740f6b246dbb051150657ee97a821ca6be52f5dd476 +size 204736 diff --git a/marked/Rel-11/23_series/23093/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-11/23_series/23093/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0e01a46059ad95a58c8302f76235e869bfa000c --- /dev/null +++ b/marked/Rel-11/23_series/23093/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a07430a32cb6799fc53f58238848ffc675e4f4355a69bb2841ff6e6b6a098dd9 +size 148887 diff --git a/marked/Rel-11/23_series/23093/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/23_series/23093/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e49b9faf8be0eca39516d7547d3f0a7b31515871 --- /dev/null +++ b/marked/Rel-11/23_series/23093/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c5d79ff59d45907d1bae58d09114b16d31b8656c0c88a0f6c209d705ab9ed77 +size 84165 diff --git a/marked/Rel-11/23_series/23093/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/marked/Rel-11/23_series/23093/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ced9b4261304ea5b352efb6e898f427dd3f7225 --- /dev/null +++ b/marked/Rel-11/23_series/23093/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23f86893ffdba9e23b40674835bf315eeb13f11b083125cd2dca02e62d246bb9 +size 46082 diff --git a/marked/Rel-11/23_series/23093/69467ece0a576b4c2ec3e0c89ba61527_img.jpg b/marked/Rel-11/23_series/23093/69467ece0a576b4c2ec3e0c89ba61527_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf037d668e52e1d05d7f80aa5f3b2f0b7cc6af70 --- /dev/null +++ b/marked/Rel-11/23_series/23093/69467ece0a576b4c2ec3e0c89ba61527_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f501fe22475be17fd76705bbda3dbecc6a49e312b7a41cf41dbe2a4faf7d32aa +size 68037 diff --git a/marked/Rel-11/23_series/23093/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-11/23_series/23093/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ae39f6f38bb7e65125e2dbab2bacdd926682681 --- /dev/null +++ b/marked/Rel-11/23_series/23093/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:933a5c1e0f0baa6ea3440b41dd08720d5ed3ff4e23be997bf837d21d001d4560 +size 140583 diff --git a/marked/Rel-11/23_series/23093/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-11/23_series/23093/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6bdad6810e020db9761aff1a80abadbb469beba --- /dev/null +++ b/marked/Rel-11/23_series/23093/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21f3fdad208cf0d3c810212f604a94a317628e16862a6c3fd87ba7f61c16add6 +size 80845 diff --git a/marked/Rel-11/23_series/23093/6e9d059430baba0c363e33749f68b107_img.jpg b/marked/Rel-11/23_series/23093/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..848357b04bdd033e747d8e73b9396aad22fc55e1 --- /dev/null +++ b/marked/Rel-11/23_series/23093/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c46d675a403cfeba55cc899f0830143cfff6f67dca58f2f2bf281c548ff7dbde +size 98038 diff --git a/marked/Rel-11/23_series/23093/710ff83dc4a77abbe489fbf1a462845a_img.jpg b/marked/Rel-11/23_series/23093/710ff83dc4a77abbe489fbf1a462845a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dccebdc4f5955a4374aa47bc8c5a176ecd27ff78 --- /dev/null +++ b/marked/Rel-11/23_series/23093/710ff83dc4a77abbe489fbf1a462845a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79e63e9dd940a7e6dff57d17258f7e55add363a5a4ba63186ac9474273006280 +size 124546 diff --git a/marked/Rel-11/23_series/23093/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-11/23_series/23093/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d5510ea51f4ae97ac733b1d9332fcd483c68ded --- /dev/null +++ b/marked/Rel-11/23_series/23093/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:171746ebe771436603c75edc28be2047b912709233505dd2765f0c3f63e6a8b5 +size 118340 diff --git a/marked/Rel-11/23_series/23093/72d448a65347c51989171748789c7d4b_img.jpg b/marked/Rel-11/23_series/23093/72d448a65347c51989171748789c7d4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef83f0f0177d085439aa33141b9c3ae3e69a6bee --- /dev/null +++ b/marked/Rel-11/23_series/23093/72d448a65347c51989171748789c7d4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a7794e9de0e16cffe5937fe94eda9c530f49803a4f42633c8da4dd4a29de0c5 +size 84302 diff --git a/marked/Rel-11/23_series/23093/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-11/23_series/23093/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd3adb8fc5418b24e7a4904b0103880d26d6a8c4 --- /dev/null +++ b/marked/Rel-11/23_series/23093/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80d57ee5b0b502e0d986dfd1133dc386db1b8f5bb05e949d5957711105640217 +size 70037 diff --git a/marked/Rel-11/23_series/23093/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-11/23_series/23093/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb75a6faa4bfb99619ee3e00cbdce1092c9bbb3a --- /dev/null +++ b/marked/Rel-11/23_series/23093/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e9816024be4be123d846c72c27c0bcc06b9a1977be12d76e8951c17e3ea6eaa +size 62026 diff --git a/marked/Rel-11/23_series/23093/819f1d00e68b342a246b64fa888a97f9_img.jpg b/marked/Rel-11/23_series/23093/819f1d00e68b342a246b64fa888a97f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05df9a7c04a05410fa8777506a20ced9ee16c085 --- /dev/null +++ b/marked/Rel-11/23_series/23093/819f1d00e68b342a246b64fa888a97f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19afc2e392e3c483efef07f9eb87d0dec22bed67a69edca4b24439a5323a1ec6 +size 29230 diff --git a/marked/Rel-11/23_series/23093/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-11/23_series/23093/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..052880d3a4a862afeece194fd4e6a02a2d26876a --- /dev/null +++ b/marked/Rel-11/23_series/23093/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e9ceec06889dccfb0b2ac0c531b67f9472b31af47508fd3ff4b498e2cec9da1 +size 144945 diff --git a/marked/Rel-11/23_series/23093/884c44b6cb9fbe15347e0562a6085df2_img.jpg b/marked/Rel-11/23_series/23093/884c44b6cb9fbe15347e0562a6085df2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9951785570be804f7ed1433568dcfafa1947742f --- /dev/null +++ b/marked/Rel-11/23_series/23093/884c44b6cb9fbe15347e0562a6085df2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b88d266366ac383b2d9a3c3f01981348aea692959549c1a0ab0578872743cb3 +size 144223 diff --git a/marked/Rel-11/23_series/23093/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-11/23_series/23093/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4420b1a730adf0fa0a08a76a94e65dcc8cd12b16 --- /dev/null +++ b/marked/Rel-11/23_series/23093/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a65399b032b6e41e03f044fb981411b56f7d907e16223b4f41760fb1fb612889 +size 88624 diff --git a/marked/Rel-11/23_series/23093/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-11/23_series/23093/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f94729e6d2a1502327fe09673c836e6fee91622f --- /dev/null +++ b/marked/Rel-11/23_series/23093/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd489f4fcd5ad3789d4cfa26659a4838029bbccb18b9255105b8b7430d0936e2 +size 118169 diff --git a/marked/Rel-11/23_series/23093/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg b/marked/Rel-11/23_series/23093/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..414ba1e4e0d6b58301bfa8bb65d985cc353e69b9 --- /dev/null +++ b/marked/Rel-11/23_series/23093/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:602bded55a987a9bba1c4a45706802d0e4d1595ada6c174d8b1421a0e8616cd0 +size 45761 diff --git a/marked/Rel-11/23_series/23093/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg b/marked/Rel-11/23_series/23093/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58eac139190b18d7d3adbd022e4eb55426ac41e9 --- /dev/null +++ b/marked/Rel-11/23_series/23093/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15072f224d271637455aa539347dd4ed1286bc83da51d97675324304240d22c7 +size 57111 diff --git a/marked/Rel-11/23_series/23093/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-11/23_series/23093/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62c827036409be7a66545ee22308373b914c99fe --- /dev/null +++ b/marked/Rel-11/23_series/23093/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed8c1c5a017ac15014d5cadbf74c255030cec4dc5375ca4fa37666c99bff6c20 +size 132709 diff --git a/marked/Rel-11/23_series/23093/92724c769da9d46b730fde1a6dccb023_img.jpg b/marked/Rel-11/23_series/23093/92724c769da9d46b730fde1a6dccb023_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d39de3fc8e76d8a3fc1b35c50e61dd0d97656de --- /dev/null +++ b/marked/Rel-11/23_series/23093/92724c769da9d46b730fde1a6dccb023_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29534aae1b5bb570e588714c1d7371fadc8b6da44455068819eb4e87a47a1076 +size 62652 diff --git a/marked/Rel-11/23_series/23093/93bd00a00fa28558486f0664550699b1_img.jpg b/marked/Rel-11/23_series/23093/93bd00a00fa28558486f0664550699b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..479adcaa94f3e6d46c3fef88def25c648f400b09 --- /dev/null +++ b/marked/Rel-11/23_series/23093/93bd00a00fa28558486f0664550699b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5601cb4bbf9c8dc0b2b7b1d5c0aa5b0756c387602a81616828e4d808615e5205 +size 110521 diff --git a/marked/Rel-11/23_series/23093/9958beca8f65818eb0ff893647af94de_img.jpg b/marked/Rel-11/23_series/23093/9958beca8f65818eb0ff893647af94de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bede250ee0a2c912e045f10ffc644afd530aac79 --- /dev/null +++ b/marked/Rel-11/23_series/23093/9958beca8f65818eb0ff893647af94de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d090f183f332ad0b2799913e5b5a2629d25bfff4e484debff9ffcc0373db6acf +size 61651 diff --git a/marked/Rel-11/23_series/23093/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/marked/Rel-11/23_series/23093/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6c224a2d783bfdd2d77bdd01f2afd02147f1124 --- /dev/null +++ b/marked/Rel-11/23_series/23093/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7698a01c1d4f5c95e341830c5d9834590012badfed554528b0108224dcd2bb0 +size 77987 diff --git a/marked/Rel-11/23_series/23093/9ba75f891de20483c291538e38701d96_img.jpg b/marked/Rel-11/23_series/23093/9ba75f891de20483c291538e38701d96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..670ab254b70e60dbe2acb2bc3bf0092593bcf45a --- /dev/null +++ b/marked/Rel-11/23_series/23093/9ba75f891de20483c291538e38701d96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61b2a9ffb84790d3732d73d8cb17ac97a7823e98cab9dc73b128cee17fed5459 +size 136215 diff --git a/marked/Rel-11/23_series/23093/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-11/23_series/23093/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20b17f9dbcb459ac2b8a1657fd4bf2778809d478 --- /dev/null +++ b/marked/Rel-11/23_series/23093/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ddb2ca3b9c57e1ada26bc392f3bbf1122bf2798414efc79621b9a681717fe66 +size 99556 diff --git a/marked/Rel-11/23_series/23093/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Rel-11/23_series/23093/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..531f57ed2caf7323938c81178c67b7fd32b9c1bd --- /dev/null +++ b/marked/Rel-11/23_series/23093/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffd19f18e0b545486ce3ef8b52b7fef2ad6480df84a9495eb68e9172e8c767be +size 129812 diff --git a/marked/Rel-11/23_series/23093/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/Rel-11/23_series/23093/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f771859b1076117648b0250b1c92437e1d6e667e --- /dev/null +++ b/marked/Rel-11/23_series/23093/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97d9d9067b9c0cea08ff6d3c51d54d08bc9eef06efb21547d5900bb391294132 +size 98280 diff --git a/marked/Rel-11/23_series/23093/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/23_series/23093/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ddaf1a2453b6b872d09fcac044b3cc6e5d7d96f --- /dev/null +++ b/marked/Rel-11/23_series/23093/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32d1a63428f8dbeac1f57de3627ca77540d18839168d308c98b363a716200005 +size 115359 diff --git a/marked/Rel-11/23_series/23093/9ef15a4afab1416db28b91184862a3a5_img.jpg b/marked/Rel-11/23_series/23093/9ef15a4afab1416db28b91184862a3a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06e1916027fa031ee917b289db6dede39598c69c --- /dev/null +++ b/marked/Rel-11/23_series/23093/9ef15a4afab1416db28b91184862a3a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5caf509e518d6e1f9272244100f1fdc1a03975416d73e6fa00fb0fadd7e57f9c +size 245519 diff --git a/marked/Rel-11/23_series/23093/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/23_series/23093/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7f3aedf5968da0e51ead2c49943dd6692ef72a1 --- /dev/null +++ b/marked/Rel-11/23_series/23093/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee8dfcc16d89adb1e82bf6aca0de19cafbfe7199d12f2922f241d0c33243c2ec +size 89264 diff --git a/marked/Rel-11/23_series/23093/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-11/23_series/23093/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a7e7f00f8ef4d95225b90501169b18b05640284 --- /dev/null +++ b/marked/Rel-11/23_series/23093/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7a3d93701ded8a7e702b06bba2e09cfc20a32302246c01fec384e9265820786 +size 157950 diff --git a/marked/Rel-11/23_series/23093/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/23_series/23093/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..024913c4153febf8a3b3b35f2fb4f8e9b045b3a1 --- /dev/null +++ b/marked/Rel-11/23_series/23093/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2ca2d501e4b8b4f14edcf84bbc2a55623f6edfdbf24c918f78c33683190cac3 +size 123902 diff --git a/marked/Rel-11/23_series/23093/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/23_series/23093/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20540ff1dc1b447f39bc204644e5f6b3fe957afb --- /dev/null +++ b/marked/Rel-11/23_series/23093/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc9db70e0dfb7911ad0403729104d2cb3b9d5eb2f4e40ecc89827f327b5b377c +size 141147 diff --git a/marked/Rel-11/23_series/23093/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-11/23_series/23093/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2e0bf9b0a9525d987f05488122a3895ceea2574 --- /dev/null +++ b/marked/Rel-11/23_series/23093/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad0c7360bb04771e0c8ccbc13a1f9671180b5fe99c7a0c8bf6d06c8cb5cec721 +size 91318 diff --git a/marked/Rel-11/23_series/23093/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-11/23_series/23093/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8932d0c1d541dcf3aa48e908b31374fdec3d2b2c --- /dev/null +++ b/marked/Rel-11/23_series/23093/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcbe5068563c11d5ce3ff9cd1f37ee190e0bd02704f64eb609913d186b95d488 +size 76689 diff --git a/marked/Rel-11/23_series/23093/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-11/23_series/23093/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6edabf5138d554fce85c6b086d6b86820b7aa3ea --- /dev/null +++ b/marked/Rel-11/23_series/23093/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8badb21c207e5292ef5b1318038abd77544ffb048959cf6866a6402316e8287e +size 55796 diff --git a/marked/Rel-11/23_series/23093/b02ba0b73e95416eb547976f6145b169_img.jpg b/marked/Rel-11/23_series/23093/b02ba0b73e95416eb547976f6145b169_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c2d473cc700fd1398457d2cd5d0816fb4219ce8 --- /dev/null +++ b/marked/Rel-11/23_series/23093/b02ba0b73e95416eb547976f6145b169_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e1a3b76274179119d525390fcde11639ad20d12083f4e1b94b5b6f2fe027c7c +size 145755 diff --git a/marked/Rel-11/23_series/23093/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg b/marked/Rel-11/23_series/23093/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9eb6f7a02248f667a6504e0542a8d3d55f97742e --- /dev/null +++ b/marked/Rel-11/23_series/23093/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96fe8ac6f46cc726daf4588c77d3ea8559a99ac7ab59b4f1ead37681e4befde3 +size 137178 diff --git a/marked/Rel-11/23_series/23093/b13465efdac63129aef9b6f1787d0d00_img.jpg b/marked/Rel-11/23_series/23093/b13465efdac63129aef9b6f1787d0d00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b77a4930d98a7735e587e88ff42e1899fbfce1e --- /dev/null +++ b/marked/Rel-11/23_series/23093/b13465efdac63129aef9b6f1787d0d00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff741c40ee4f43df4e88a32dc5be97b6708bfdce732c784e8a485efafe611967 +size 68024 diff --git a/marked/Rel-11/23_series/23093/b50f38be091844d58b11e3d47bc71e73_img.jpg b/marked/Rel-11/23_series/23093/b50f38be091844d58b11e3d47bc71e73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8f7efbb366ccebb8f81d2c6830997bd02afb4c6 --- /dev/null +++ b/marked/Rel-11/23_series/23093/b50f38be091844d58b11e3d47bc71e73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3640044c5ef0fbfa856df48e7a837c75b82b52132d38b606ebc0c0dce9a5174c +size 63518 diff --git a/marked/Rel-11/23_series/23093/b55cd9b5721bd8aabc979c85316924e4_img.jpg b/marked/Rel-11/23_series/23093/b55cd9b5721bd8aabc979c85316924e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c9db879ade41b33c8328917740735402ac90c3b --- /dev/null +++ b/marked/Rel-11/23_series/23093/b55cd9b5721bd8aabc979c85316924e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9b7ee7d87ae9aa2e19c55266b169ec23099943e4fade48ce227adba648c81fd +size 95801 diff --git a/marked/Rel-11/23_series/23093/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Rel-11/23_series/23093/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ec27a480bfda661c81a9f05510c10dd8caffa98 --- /dev/null +++ b/marked/Rel-11/23_series/23093/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07eff49503b72ef1a7b007c2c12e3a4847cf31b9baafde85eacd7f60219763d9 +size 91949 diff --git a/marked/Rel-11/23_series/23093/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-11/23_series/23093/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78f58d67d9151c25ea143d0ab5baef3c590e7498 --- /dev/null +++ b/marked/Rel-11/23_series/23093/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9af8251b9fd0ee6a919318b8937e60402ea83da75e08333868105e2c3dbb3336 +size 88621 diff --git a/marked/Rel-11/23_series/23093/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-11/23_series/23093/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4c680fe9c9f4968588bb9f158874d7dcb23d20c --- /dev/null +++ b/marked/Rel-11/23_series/23093/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48212051ca74fecfd121b4bc12be3169819536d90a2f47e6f95dd21f82eb4c5c +size 99714 diff --git a/marked/Rel-11/23_series/23093/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-11/23_series/23093/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab5f0b1ff2cc530239ec19cdb71b1ea2e5ffd2f7 --- /dev/null +++ b/marked/Rel-11/23_series/23093/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8a17a3ed8a357248d19f814df97952a9d3822a264eac85d529208277c1be600 +size 139214 diff --git a/marked/Rel-11/23_series/23093/c21bad844b5cb6026c067a1f43ce67c3_img.jpg b/marked/Rel-11/23_series/23093/c21bad844b5cb6026c067a1f43ce67c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7795a5d01791c49e502aa66b3700df2eb7a6b46e --- /dev/null +++ b/marked/Rel-11/23_series/23093/c21bad844b5cb6026c067a1f43ce67c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7facbaeb5e4d99d60ed6009cdfe542b254d8a5e9faa16282441dcc0df5cf4780 +size 143747 diff --git a/marked/Rel-11/23_series/23093/c817f3df24c6107d07c517dce71ed086_img.jpg b/marked/Rel-11/23_series/23093/c817f3df24c6107d07c517dce71ed086_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfd57c0227217714be2541e05dee8d4683025823 --- /dev/null +++ b/marked/Rel-11/23_series/23093/c817f3df24c6107d07c517dce71ed086_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41378bdbd283c8176c561a72fc196dacce89fef990f4f4e11f2617e5d1a01a5e +size 29083 diff --git a/marked/Rel-11/23_series/23093/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/23_series/23093/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3796b229c52764a472202c52f3fb6207207f56d4 --- /dev/null +++ b/marked/Rel-11/23_series/23093/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a62d0b67254b4b4a62884d1116fdd789277d63d29a2f0ee3f4a99491bcce312a +size 97769 diff --git a/marked/Rel-11/23_series/23093/cc7baa8e5118f4b42c01166637c738ea_img.jpg b/marked/Rel-11/23_series/23093/cc7baa8e5118f4b42c01166637c738ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f228738762ae77253ffaf468e5a80ee2ea705324 --- /dev/null +++ b/marked/Rel-11/23_series/23093/cc7baa8e5118f4b42c01166637c738ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0eff68ad2029dcd8af9af90fbdb50f3ef8b6bde175ad30ca0fd640333b84ae43 +size 134974 diff --git a/marked/Rel-11/23_series/23093/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-11/23_series/23093/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52fa271daf8c613de6718801bf8ec952f2e1036a --- /dev/null +++ b/marked/Rel-11/23_series/23093/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2140b476283449438392880121250ae019306bc1722f547aa9b811c2e4511fd8 +size 57460 diff --git a/marked/Rel-11/23_series/23093/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-11/23_series/23093/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68f60e9b4ba486afa068bd1ab56294aa74f7c79d --- /dev/null +++ b/marked/Rel-11/23_series/23093/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f98c397da39996c7a65caccfb78e8479885352a2d0f240ad95ef28b24c41900 +size 62642 diff --git a/marked/Rel-11/23_series/23093/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg b/marked/Rel-11/23_series/23093/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0652f51e7e04dac99349af0ed2bf6495e7e72e6 --- /dev/null +++ b/marked/Rel-11/23_series/23093/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93b7b630f72046da8325730fc1af0a5c59f69f524bf47aa20c52d9e3b2f8e619 +size 111800 diff --git a/marked/Rel-11/23_series/23093/d2417b04116c354deccb25d98a84a0fb_img.jpg b/marked/Rel-11/23_series/23093/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eda6e3eb86c772300e8f2a012de8810e1af840d1 --- /dev/null +++ b/marked/Rel-11/23_series/23093/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7bff4dded6b595b41d10d76744010b34765cb28c9f526a2dcee0c9000a0a84c +size 155795 diff --git a/marked/Rel-11/23_series/23093/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-11/23_series/23093/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41d6b30cab288b040c7af3244a51b3e8b72394d2 --- /dev/null +++ b/marked/Rel-11/23_series/23093/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d391e5c5754a5b4e96ff688c58a841e21ff5d9e4be943f9075093e117cb87e3 +size 132673 diff --git a/marked/Rel-11/23_series/23093/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-11/23_series/23093/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71ed649571512766e16115895f11075d6612b64a --- /dev/null +++ b/marked/Rel-11/23_series/23093/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a35d70f8988cbfd7c2b2477c1a89e9e43d1f1e01d2c1ab0b08733786f3c15a92 +size 107637 diff --git a/marked/Rel-11/23_series/23093/db7a693cf26f527ac6c0d4d41da20858_img.jpg b/marked/Rel-11/23_series/23093/db7a693cf26f527ac6c0d4d41da20858_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..254dc6a15f740ae90506cf8ae60eebbbcd491dd2 --- /dev/null +++ b/marked/Rel-11/23_series/23093/db7a693cf26f527ac6c0d4d41da20858_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f74c8b7c266d4e2b254bf5bdefa39772acc47dc983a42c4d003180e991987317 +size 75575 diff --git a/marked/Rel-11/23_series/23093/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-11/23_series/23093/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88fa5668f3ec4fbf3b34a7610a18cc9ccadbd562 --- /dev/null +++ b/marked/Rel-11/23_series/23093/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c8ba732a2662553513d17e7b053c802593e02cc69e0d61d395c10ce8af0d4de +size 96057 diff --git a/marked/Rel-11/23_series/23093/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-11/23_series/23093/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8dacf27364c7f8c06ed5784ec2554d012794159 --- /dev/null +++ b/marked/Rel-11/23_series/23093/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5efe51cc49c725a9b76453780ce19d3b72165e7c1bb98c866dd24cc9a89fe5e +size 147199 diff --git a/marked/Rel-11/23_series/23093/e18841eb4a995df8354a793459e12fd0_img.jpg b/marked/Rel-11/23_series/23093/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3e7c4ac08f1284a964643b462a54ec8bf4adfac --- /dev/null +++ b/marked/Rel-11/23_series/23093/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0de7aad2889cedb13c18e799ac7cb6289c56374774d0e4975ea13d297310b2ee +size 94218 diff --git a/marked/Rel-11/23_series/23093/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-11/23_series/23093/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce867271da2a95cd10244ae99b77a3b73d96271f --- /dev/null +++ b/marked/Rel-11/23_series/23093/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbd467097b21dc0e59a858ba5dfe6a7bdadc4e1401181eb6e562793b43461b74 +size 96554 diff --git a/marked/Rel-11/23_series/23093/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-11/23_series/23093/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6503b9ddd23b54e1504a03561113e5c5e3e319f --- /dev/null +++ b/marked/Rel-11/23_series/23093/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cac5764d07aa03cde7072b95cd2554d2d343f6d5b24aed23a8e9fd953cd6c2d6 +size 86883 diff --git a/marked/Rel-11/23_series/23093/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Rel-11/23_series/23093/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41a7b1b9875ad7f482de361c5acc58cdd85a315e --- /dev/null +++ b/marked/Rel-11/23_series/23093/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32808c4d06deb36bd7c672a5dfb7be02d82453c47c763d29575d213c5432a875 +size 123287 diff --git a/marked/Rel-11/23_series/23093/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-11/23_series/23093/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8e61d5f11de1b7e3b283527d3ab4f044a735feb --- /dev/null +++ b/marked/Rel-11/23_series/23093/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7335006e0e99b6af50f35ba50e401140e2b643511acab3313998ff2b7498a66 +size 137260 diff --git a/marked/Rel-11/23_series/23093/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/marked/Rel-11/23_series/23093/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb681f2f663ee0e444b0e8436674665ae1980265 --- /dev/null +++ b/marked/Rel-11/23_series/23093/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6d4199e8d0ed2742266dcfe3bd6472fde06764571551c21aa9fc2075c4d7562 +size 114371 diff --git a/marked/Rel-11/23_series/23093/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg b/marked/Rel-11/23_series/23093/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d179c959912e12e6fea10243a31845fc49dfaf90 --- /dev/null +++ b/marked/Rel-11/23_series/23093/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98dc76314497328d388bad728794b9fe0060f6ece7d17ef0583fad32daa5e21a +size 61051 diff --git a/marked/Rel-11/23_series/23093/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-11/23_series/23093/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5268134cb9c9430883a34af459e2dc7c2f45fc2c --- /dev/null +++ b/marked/Rel-11/23_series/23093/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2532a63014f80d1a19ca17274aae89f209ee71407fa020c1f8f2d0c4793bfe0 +size 71293 diff --git a/marked/Rel-11/23_series/23093/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-11/23_series/23093/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d1e66db155b899531440d85c26ebc1fb667e3ce --- /dev/null +++ b/marked/Rel-11/23_series/23093/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34dda6dccc408fd7a9e1defcb7e9508b9b250a0e6031b226e86775d0042cf372 +size 74088 diff --git a/marked/Rel-11/23_series/23093/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23093/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4840e0a9f761f4c3769555cfe463537fe372ac7e --- /dev/null +++ b/marked/Rel-11/23_series/23093/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c4c7f870793d510901e34d8739a05eead5033898785b7e9edc3436c4643439f +size 138977 diff --git a/marked/Rel-11/23_series/23093/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-11/23_series/23093/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2d10f02022b296fd6a2a4a3402c2af19c14a912 --- /dev/null +++ b/marked/Rel-11/23_series/23093/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f994efd2ae9d9bd20df448bc4eaf4a9653194db480b5541dfda80b0ed9e188d +size 123035 diff --git a/marked/Rel-11/23_series/23093/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/Rel-11/23_series/23093/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a06ce34d9c080856ea99d4cb61723687bf5f6da8 --- /dev/null +++ b/marked/Rel-11/23_series/23093/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94e3ff77eaa5b721ceeba2f45e0fc61e2415c8d3df63b5c71fcb6c1ab8ec2492 +size 127480 diff --git a/marked/Rel-11/23_series/23093/raw.md b/marked/Rel-11/23_series/23093/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bfda14a1de4a90e2ded53504ea18ea80a3df6d15 --- /dev/null +++ b/marked/Rel-11/23_series/23093/raw.md @@ -0,0 +1,4959 @@ + + + + +**Error:** + +**2** + +**Error: Reference source not** + +# Contents + +| | | +|----------------------------------------------------------------------|----| +| Foreword..... | 5 | +| 1 Scope..... | 6 | +| 2 Normative references..... | 6 | +| 3 Definitions and abbreviations..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations..... | 7 | +| 4 General..... | 7 | +| 4.1 Overview..... | 7 | +| 4.2 Architecture..... | 7 | +| 4.2.1 Architectural overview during roaming..... | 8 | +| 5 Handling of completion of calls to busy subscriber..... | 9 | +| 5.1 CCBS Timers..... | 9 | +| 5.2 Information flows..... | 9 | +| 5.3 Activation..... | 14 | +| 5.4 Deactivation..... | 15 | +| 5.5 Interrogation..... | 16 | +| 5.6 Messages and their contents..... | 16 | +| 5.6.1 Information elements used in the messages..... | 17 | +| 5.6.1.1 Call Information information element..... | 17 | +| 5.6.1.2 AddressOfB information element..... | 17 | +| 5.6.1.3 CCBS Description information element..... | 17 | +| 5.6.2 Messages between MS and MSC..... | 18 | +| 5.6.3 Messages between MSC and VLR (B-interface)..... | 19 | +| 5.6.3.1 Messages between MSC and VLR in the originating network..... | 19 | +| 5.6.3.2 Messages between MSC and VLR in the destination network..... | 21 | +| 5.6.4 Messages between VLR and HLR (D-interface)..... | 22 | +| 5.6.4.1 Messages between VLR and HLR in the originating network..... | 22 | +| 5.6.4.2 Messages between VLR and HLR in the destination network..... | 24 | +| 5.6.5 Messages between MSC and HLR (C-interface)..... | 25 | +| 5.6.6 Messages between MSC - MSC (E-interface)..... | 25 | +| 5.6.7 Existing parameters containing CCBS specific information..... | 25 | +| 6 Monitoring and CCBS Call Reporting..... | 26 | +| 6.1 Monitoring..... | 26 | +| 6.1.1 Overview..... | 26 | +| 6.1.2 Monitoring Subscriber B-state information..... | 26 | +| 6.1.3 Monitoring Subscriber A state information..... | 26 | +| 6.2 MSC/VLR Monitoring Model..... | 27 | +| 6.2.1 Subscriber status..... | 27 | +| 6.2.1.1 Idle..... | 28 | +| 6.2.1.2 Not Idle..... | 28 | +| 6.2.1.3 Not Reachable..... | 28 | +| 6.2.2 Reporting of subscriber state transitions..... | 29 | +| 6.2.2.1 Start Reporting of Monitoring Events..... | 29 | +| 6.2.2.2 Stop Reporting of Monitoring Events..... | 29 | +| 6.3 CCBS Call Reporting..... | 30 | +| 6.3.1 Overview..... | 30 | +| 6.3.2 Originating Network (A-side)..... | 30 | +| 6.3.3 Destination Network (B-side)..... | 30 | +| 6.3.3.1 Interaction of Event Reporting and CCBS Call Report..... | 30 | +| 6.4 Location Update..... | 30 | +| 7 Mobility..... | 31 | +| 7.1 Mobility during Activation..... | 31 | +| 7.2 Number used within CCBS Call..... | 31 | +| 7.3 MS does Location Update..... | 31 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------------------------|------------| +| 7.4 | Mobility during CCBS Call in the destination network..... | 31 | +| 8 | Interaction with other supplementary services..... | 32 | +| 8.1 | Call forwarding unconditional (CFU)..... | 32 | +| 8.2 | Call forward on busy (CFB)..... | 32 | +| 8.3 | Call forwarding on no reply (CFNRy)..... | 32 | +| 8.4 | Call forwarding on MS not reachable (CFNRc)..... | 32 | +| 8.5 | Call Waiting (CW)..... | 33 | +| 8.6 | Multipart service (MPTY)..... | 33 | +| 8.7 | Closed user group (CUG)..... | 33 | +| 8.8 | Advice Of Charge (AoC)..... | 33 | +| 8.9 | Barring of all outgoing calls (BAOC)..... | 33 | +| 8.10 | Barring of outgoing international calls (BOIC)..... | 33 | +| 8.11 | Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC)..... | 33 | +| 8.12 | Barring of all incoming calls (BAIC)..... | 33 | +| 8.13 | Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam)..... | 34 | +| 8.14 | Completion of calls to busy subscriber (CCBS)..... | 34 | +| 9 | Interaction with other network features..... | 35 | +| 9.1 | Customised Applications for Mobile network Enhanced Logic (CAMEL)..... | 35 | +| 9.2 | Support of Optimal Routeing (SOR)..... | 35 | +| 10 | Interworking with other networks..... | 36 | +| 10.1 | Interworking with network entities not supporting CCBS..... | 36 | +| 10.1.1 | CCBS not supported by MSC A..... | 36 | +| 10.1.2 | CCBS not supported by HLR B..... | 36 | +| 10.1.3 | CCBS not supported by MSC B..... | 37 | +| 11 | Network entity functions..... | 38 | +| 11.1 | Originating Network Processes..... | 38 | +| 11.1.1 | Processes and procedures in MSC/VLR..... | 38 | +| 11.1.2 | Processes and procedures in HLR..... | 60 | +| 11.2 | Destination Network Processes..... | 91 | +| 11.2.1 | Procedures in GMSC..... | 91 | +| 11.2.2 | Processes and procedures in HLR..... | 97 | +| 11.2.3 | Procedures in MSC/VLR..... | 127 | +| 11.3 | Processes and procedures common in originating and destination network entities..... | 139 | +| 12 | Information stored in the HLRs..... | 155 | +| 12.1 | Originating Network Data..... | 155 | +| 12.2 | Destination Network Data..... | 156 | +| 12.3 | Transfer of information from HLR to VLR..... | 156 | +| 13 | State transition model..... | 157 | +| 13.1 | State transition model for the CCBS service in the originating network..... | 157 | +| 13.2 | State transition model for the CCBS service in the destination network..... | 157 | +| 13.3 | State transition model for a CCBS Request..... | 158 | +| 13.4 | Information stored in the VLRs..... | 159 | +| <b>Annex A (informative):</b> | <b>Message flow diagrams showing a successful CCBS request.....</b> | <b>160</b> | +| Annex B (informative): | Change history..... | 164 | + +# --- Foreword + +This Technical Specification has been produced by the 3GPP. + +This specification gives the stage 2 description of the Completion of Calls to Busy Subscriber (CCBS) supplementary service 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 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 + +This Technical Specification gives the stage 2 description of the Completion of Calls to Busy Subscriber (CCBS) supplementary service. + +# --- 2 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: "3G Vocabulary". +- [2] 3GPP TS 22.030: "Man Machine Interface (MMI) of the Mobile Station (MS)". +- [3] 3GPP TS 22.093: "Completion of calls to busy subscriber (CCBS) supplementary services - Stage 1". +- [4] 3GPP TS 23.011: "Technical realization of supplementary services - General Aspects". +- [5] 3GPP TS 23.018: "Basic Call Handling - Technical Realization". +- [6] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) - Stage 2". +- [7] 3GPP TS 23.079: "Support for Optimal Routeing (SOR) - Technical Realization". +- [8] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols Stage3". +- [9] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [10] ETSI ETS 300 358: "ISDN Completion of Calls to Busy Subscriber (CCBS) supplementary service; Functional capabilities and information flows". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +**Destination B:** The entity addressed in the original call set up, which is busy when first called by subscriber A. Similarly, MSC B, VLR B and HLR B are the network elements pertaining to Destination B when Destination B is a GSM mobile. + +**Originating queue:** The queue that manages CCBS requests for a subscriber, when that subscriber is the originator of those CCBS Requests. + +**SSAP:** Supplementary Service Application Part. SSAP is the protocol used for CCBS procedures on the interface between the originating and destination network. Communication across this interface is performed using SCCP Connectionless Signalling (Refer to ETS 300 358). + +**Subscriber A:** The user of MS A, requesting CCBS. Similarly, MSC A, VLR A and HLR A are the network elements pertaining to Subscriber A. + +**Subscriber B:** The user of destination B, who may not necessarily subscribe to CCBS. + +**Subscriber C:** The user of MS C, who is the forwarded-to-party when call forwarding applies. Similarly, MSC C, VLR C and HLR C are the network elements pertaining to Subscriber C. + +**Target queue:** The queue that manages CCBS requests for a subscriber, when that subscriber is the target of CCBS Requests. + +**Timers:** For each of the service timers, the location, start and stop conditions and action on expiry are given - Refer to subclause 5.1. + +## 3.2 Abbreviations + +Abbreviations used in this specification are listed in 3GPP TR 21.905. + +# --- 4 General + +## 4.1 Overview + +The CCBS service allows a calling subscriber A, encountering a NDUB destination B, to be notified when destination B becomes idle and to have the network automatically generate a CCBS call to destination B, if subscriber A desires. Subscriber A may make distinct CCBS requests for calls to the same destination B for different basic services. + +## 4.2 Architecture + +Figure 4.2.1 is an architectural overview of the CCBS service when interworking between the originating and the destination networks involved. The originating network may be a mobile network or a fixed network and the destination network may also be a mobile network or a fixed network. + +The call related signalling for CCBS is performed on ISUP links on the following interfaces: + +VMSC A - GMSC B; + +VMSC A - DLE; + +OLE - GMSC B; + +whereas the specific CCBS procedures are performed via the SSAP protocol, which is signalled on the following interfaces: + +HLR A - HLR B; + +HLR A - DLE; + +OLE - HLR B. + +![Architectural overview showing common point of interworking](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the architectural overview of a common point of interworking between an Originating Network and a Destination Network, connected via Transit Network(s). The diagram is split into two horizontal sections by a central cloud labeled 'TRANSIT NETWORK(S)'. + +**Originating Network (Left):** + +- Fixed Network:** Contains an OLE (Office of Originating Equipment) connected to the Transit Network(s) via ISUP and SSAP signaling. +- Mobile Network:** Contains an HLR A (Home Location Register), VLRA (Visitor Location Register), and VMSC A (Visited Mobile Switching Center). HLR A is connected to the Transit Network(s) via SSAP. VLRA is connected to HLR A. VMSC A is connected to VLRA and to the Transit Network(s) via ISUP. + +**Destination Network (Right):** + +- Fixed Network:** Contains a DLE (Office of Destination Equipment) connected to the Transit Network(s) via ISUP and SSAP signaling. +- Mobile Network:** Contains an HLR B (Home Location Register), VLRB (Visitor Location Register), and VMSC B (Visited Mobile Switching Center). HLR B is connected to the Transit Network(s) via SSAP. A MAP (Mobile Application Part) signaling path is shown between the Transit Network(s) and HLR B. VLRB is connected to HLR B. VMSC B is connected to VLRB and to the Transit Network(s) via ISUP. A GMSC B (Gateway Mobile Switching Center) is also connected to the Transit Network(s) via ISUP and to VMSC B via ISUP. + +Architectural overview showing common point of interworking + +**Figure 4.2.1: Architectural overview showing common point of interworking** + +### 4.2.1 Architectural overview during roaming + +Either the originating subscriber A or the destination subscriber B or both may be located outside of their HPLMNs during the CCBS service. When all the involved networks support CCBS service the normal handling described in this specification applies. When some network entities do not support CCBS service refer to clause 10 where the exceptions are described in more detail. + +The signalling between different networks described in the subclause 4.2 applies also during roaming. HLR A and HLR B belongs always to the HPLMN of the subscriber whereas VLRA and MSC A and GMSC, VLRB and MSC B respectively may belong to a HPLMN or VPLMN. Refer to TS 23.018 where call handling in the mobile network is described in more detail. + +# 5 Handling of completion of calls to busy subscriber + +Registration and erasure of CCBS are not applicable. Activation and Invocation of CCBS are intrinsic parts of the operation of the service, and are described in this section. + +## 5.1 CCBS Timers + +The timers used to control the operation of CCBS can be considered to consist of two groups i.e. the timers which operate on a per subscriber basis (see table 1) and the service duration timers (T3 and T7) which operate on a per CCBS Request basis (see table 2). + +**Table 1: CCBS Service Timers** + +| Timer | Name | Value | Run At | Started | Stopped | Expiry | +|-------|------------------------|--------|--------|-------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------| +| T1 | Retention | >15s | MSC A | Busy (CCBS Possible) sent to MS A | CCBS Request received from MS A | Discard retained information | +| T4 | Recall | 20-30s | MSC A | CCBS Recall sent to MS A and MS A is idle | Subscriber A initiates CCBS setup or rejects CCBS Recall | Cancel request | +| T8 | Destination idle guard | 0-15s | HLR B | Event Report received from VLR B indicating destination B is idle | Event Report received from VLR B indicating destination B is no longer idle | Inform originating network that Destination B is free | +| T9 | Recall B | 40-55s | HLR B | Remote User Free sent to the A-side | Request cancelled, completed or suspended | Cancel request | +| T10 | CCBS notification | 20-30s | MSC A | CCBS Recall sent to MS A and MS A is not idle | Subscriber A initiates CCBS setup, rejects CCBS Recall or requests suspension | Suspend request | +| T11 | CCBS resume | 20-25s | HLR A | HLR A receives a resume request and there are more than one suspended request in subscriber A's queue | Remote User Free received from destination network | Resume next suspended request in queue | +| T12 | CCBS Call Guard | 20-30s | HLRA | HLRA receives a CCBS RUF Ack and starts to wait CCBS Call Report | CCBS Call Report received | Cancel request | + +**Table 2: Service Duration Timers** + +| Timer | Name | Value | Run At | Started | Stopped | Expiry | +|-------|------------------------------|--------|--------|-------------------------------------------------------------------|--------------------------------|----------------| +| T3 | Originating service duration | 15-45m | HLR A | Acknowledgement to CCBS Request received from destination network | Request cancelled or completed | Cancel request | +| T7 | Terminating service duration | >45m | HLR B | HLR B acknowledges successful activation of a CCBS Request | Request cancelled or completed | Cancel request | + +## 5.2 Information flows + +Figures 5.2.1 and 5.2.2 show the flow of information between network elements for a mobile to mobile call for the following: + +Figure 5.2.1: Successful CCBS request, destination B busy when request made, subscriber A free when destination B becomes free. + +Figure 5.2.2: Subscriber A is not idle when destination B becomes free. + +Figures 5.2.3 and 5.2.4 show the flow of information between network elements for a mobile to fixed call for the same situations described in figures 5.2.1 and 5.2.2 respectively. + +Each information flow diagram has been divided where appropriate into four distinct phases of operation. These are as follows: + +- (1) Pre-conditions (Initial Call encountering NDUB and CCBS possible in the destination network). The detailed description of the basic call handling can be found in TS 23.018; +- (2) Activation; +- (3) Invocation; +- (4) Operation (CCBS Call Set-up). + +![](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Sequence diagram illustrating a Successful CCBS request. The diagram shows the interaction between MS (A), MSC/VLR (A), HLR (A), GMSC, HLR (B), and MSC (B). + +The process is divided into four main phases, numbered 1 to 4 in circles on the right side of the diagram. + +- Phase 1:** MS (A) sends a **Set-up** message to MSC/VLR (A). MSC/VLR (A) sends an **IAM** message to GMSC. GMSC sends an **Info Req** message to HLR (B). HLR (B) sends a **PRN** message to MSC (B). MSC (B) sends a **MSRN** message to HLR (B). HLR (B) sends an **Info Req Ack** message to GMSC. GMSC sends an **IAM** message to MSC (B). MSC (B) sends a **RELEASE (Busy, CCBS Possible)** message to GMSC. GMSC sends a **RELEASE (Busy, CCBS Possible)** message to MSC/VLR (A). MSC/VLR (A) sends a **CCBS Poss** message to MS (A). A dashed line separates Phase 1 and Phase 2. +- Phase 2:** MS (A) sends a **CCBS Request** message to MSC/VLR (A). MSC/VLR (A) sends a **CCBS Request** message to HLR (A). HLR (A) sends a **CCBS Request** message to HLR (B). HLR (B) sends a **Start Reporting** message to MSC (B). HLR (B) sends a **CCBS Request Ack** message to HLR (A). HLR (A) sends a **CCBS Request Ack** message to MSC/VLR (A). MSC/VLR (A) sends a **CCBS Request Ack** message to MS (A). A dashed line separates Phase 2 and Phase 3. +- Phase 3:** MSC (B) sends a **Release** message to HLR (B). HLR (B) sends an **Event Report (Idle & Reachable)** message to HLR (A). HLR (A) sends a **Remote User Free** message to MSC/VLR (A). MSC/VLR (A) sends a **CCBS RUF** message to MS (A). MS (A) sends a **CCBS Call Info** message to MSC/VLR (A). MSC/VLR (A) sends a **CCBS Call Info Ack** message to MS (A). MS (A) sends a **CCBS Recall** message to MSC/VLR (A). A dashed line separates Phase 3 and Phase 4. +- Phase 4:** MS (A) sends a **CCBS Set-up** message to MSC/VLR (A). MSC/VLR (A) sends a **CCBS RUF Ack** message to HLR (A). MSC/VLR (A) sends an **IAM (CCBS Call)** message to GMSC. GMSC sends an **Info Req (CCBS Call)** message to HLR (B). HLR (B) sends a **PRN (CCBS Call)** message to MSC (B). MSC (B) sends a **PRN Ack** message to HLR (B). HLR (B) sends an **Info Req Ack** message to GMSC. GMSC sends an **IAM (CCBS Call)** message to MSC (B). MSC (B) sends a **Set-up** message to MS (A). MSC (B) sends an **ACM/ANM/CPG** message to GMSC. GMSC sends an **ACM/ANM/CPG** message to MSC/VLR (A). MSC/VLR (A) sends an **Alert/Connect** message to MS (A). HLR (B) sends a **CCBS Call Report** message to HLR (A). HLR (A) sends a **TC-END** message to MSC/VLR (A). MSC/VLR (A) sends a **CCBS Call Report (Success)** message to HLR (A). HLR (B) sends a **Stop Reporting** message to MSC (B). + +Timing points T1 through T9 are indicated by vertical dashed lines and labels. + +Figure 5.2.1: Successful CCBS request. Destination B busy when request activated, subscriber A free when destination B becomes free (mobile-to-mobile) + +![](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Sequence diagram illustrating the processing of a single CCBS request when the source subscriber is not idle at the time the destination becomes free. + +**Participants:** MS (A), MSC/VLR (A), HLR (A), GMSC, HLR (B), MSC (B). + +**Sequence of Events:** + +- Initial Call Setup and Release:** + - MS (A) sends a **Set-up** to MSC/VLR (A). + - MSC/VLR (A) sends an **IAM** to GMSC. + - GMSC sends an **Info Req** to HLR (B). + - HLR (B) sends a **PRN** to MSC (B). + - MSC (B) returns an **MSRN** to HLR (B). + - HLR (B) returns an **Info Req Ack** to GMSC. + - GMSC sends an **IAM** to MSC (B). + - MSC (B) returns a **RELEASE (Busy, CCBS Possible)** to GMSC. + - GMSC sends a **RELEASE (Busy, CCBS Possible)** to MSC/VLR (A). + - MSC/VLR (A) sends a **CCBS Poss** to MS (A). +- CCBS Request and Reporting:** + - MS (A) sends a **CCBS Request** to MSC/VLR (A) at time **T1**. + - MSC/VLR (A) sends a **CCBS Request** to HLR (A). + - HLR (A) sends a **CCBS Request** to HLR (B). + - HLR (B) sends a **Start Reporting** to MSC (B). + - HLR (B) returns a **CCBS Request Ack** to HLR (A). + - HLR (A) sends a **CCBS Request Ack** to MSC/VLR (A) at time **T3**. + - MSC/VLR (A) sends a **CCBS Request Ack** to MS (A). + - MSC (B) receives a **Release** from an external source. + - MSC (B) sends an **Event Report (Idle & Reachable)** to HLR (B) at time **T8**. + - HLR (B) sends a **Remote User Free** to HLR (A) at time **T8**. + - HLR (A) sends a **CCBS RUF** to MSC/VLR (A) at time **T9**. + - MSC/VLR (A) sends a **CCBS Call Info** to MS (A). + - MS (A) returns a **CCBS Call Info Ack** to MSC/VLR (A). + - MS (A) sends a **CCBS Recall** to MSC/VLR (A) at time **T10**. +- Timeout and Resumption:** + - At time **T10 Expires**, MSC/VLR (A) sends a **CCBS RUF Ack** to HLR (A). + - HLR (A) sends a **CCBS Suspend** to HLR (B) at time **T9**. + - HLR (B) sends a **Stop Reporting (Note 1)** to MSC (B). + - HLR (A) receives a **Note: T3 & T7 are not stopped** from HLR (B). + - MS (A) becomes idle. + - MSC/VLR (A) sends a **Start Reporting** to HLR (A). + - HLR (A) sends a **Start Reporting Ack** to MSC/VLR (A). + - MSC/VLR (A) sends an **Event Report (Idle & Reach)** to HLR (A). + - HLR (A) sends a **CCBS Resume** to HLR (B). + - HLR (B) sends a **Start Reporting (Note 2)** to MSC (B). + - HLR (B) returns a **Start Reporting Ack** to HLR (A). + +Note 1 : Stop Reporting is sent if there are only suspended requests in the queue + +Note 2 : Start Reporting is sent if MSC B is not monitoring destination B + +**Figure 5.2.2: Subscriber A not idle when destination B becomes free (mobile-to-mobile); +Processing of a single request** + +![](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Sequence diagram illustrating a Successful CCBS request. The diagram shows interactions between MS (A), MSC/VLR (A), HLR (A), and DLE (B). + +**Sequence of Messages:** + +- MS (A) sends **Set-up** to MSC/VLR (A). MSC/VLR (A) sends **IAM** to DLE (B). DLE (B) responds with **RELEASE (Busy, CCBS Possible)** to MSC/VLR (A). MSC/VLR (A) sends **CCBS Poss** to MS (A). A dashed line separates this initial phase from the rest. +- MS (A) sends **CCBS Request** to MSC/VLR (A) at time **T1**. MSC/VLR (A) sends **CCBS Request** to HLR (A). HLR (A) sends **CCBS Request** to DLE (B). DLE (B) responds with **CCBS Request Ack** to HLR (A). HLR (A) sends **CCBS Request Ack** to MSC/VLR (A). MSC/VLR (A) sends **CCBS Request Ack** to MS (A). A dashed line separates this phase from the next. +- DLE (B) sends **Release** to HLR (A). HLR (A) sends **Remote User Free** to MSC/VLR (A). MSC/VLR (A) sends **CCBS RUF** to HLR (A). HLR (A) sends **CCBS Call Info** to MSC/VLR (A). MSC/VLR (A) sends **CCBS Call Info Ack** to HLR (A). HLR (A) sends **CCBS Recall** to MSC/VLR (A). MSC/VLR (A) sends **CCBS Set-up** to MS (A) at time **T4**. A dashed line separates this phase from the final one. +- MSC/VLR (A) sends **CCBS RUF Ack** to HLR (A). HLR (A) sends **IAM (CCBS Call)** to DLE (B). DLE (B) responds with **ACM/ANM/CPG** to MSC/VLR (A). MSC/VLR (A) sends **Alert/Connect** to MS (A). DLE (B) sends **TC-END** to HLR (A). HLR (A) sends **CCBS Call Report (success)** to MSC/VLR (A) at time **T3**. + +**Timing Markers:** + +- T1**: Time of CCBS Request from MS (A). +- T3**: Time of CCBS Call Report (success) from HLR (A). +- T4**: Time of CCBS Set-up from MSC/VLR (A). + +Figure 5.2.3: Successful CCBS request. Destination B busy when request activated, subscriber A free when destination B becomes free (mobile-to-fixed) + +![](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Sequence diagram illustrating the activation process for CCBS (Call Completion on Busy Subscriber) when the destination becomes free. The diagram shows interactions between MS (A), MSC/VLR (A), HLR (A), and DLE (B). + +**Sequence of Messages:** + +- MS (A) sends **Set-up** to MSC/VLR (A). +- MSC/VLR (A) sends **IAM** to DLE (B). +- DLE (B) responds with **RELEASE (Busy, CCBS Possible)** to MSC/VLR (A). +- MSC/VLR (A) sends **CCBS Poss** to MS (A) at timer **T1**. +- MS (A) sends **CCBS Request** to MSC/VLR (A) at timer **T1**. +- MSC/VLR (A) sends **CCBS Request** to HLR (A). +- HLR (A) sends **CCBS Request** to DLE (B). +- DLE (B) responds with **CCBS Request Ack** to HLR (A) at timer **T3**. +- HLR (A) sends **CCBS Request Ack** to MSC/VLR (A). +- MSC/VLR (A) sends **CCBS Request Ack** to MS (A). +- DLE (B) receives a **Release** message. +- DLE (B) sends **Remote User Free** to HLR (A). +- HLR (A) sends **CCBS RUF** to MSC/VLR (A). +- MSC/VLR (A) sends **CCBS Call Info** to MS (A). +- MS (A) responds with **CCBS Call Info Ack** to MSC/VLR (A). +- MS (A) sends **CCBS Recall** to MSC/VLR (A) at timer **T10**. +- Timer **T10 Expires** at MSC/VLR (A). +- MSC/VLR (A) sends **CCBS RUF Ack** to HLR (A). +- HLR (A) sends **CCBS Suspend** to DLE (B). +- HLR (A) sends **Start Reporting** to MSC/VLR (A). +- MSC/VLR (A) sends **Start Reporting Ack** to HLR (A). +- MS (A) becomes idle. +- MSC/VLR (A) sends **Event Report (Idle&Reach)** to HLR (A). +- HLR (A) sends **CCBS Resume** to DLE (B). + +**Notes:** + +- Timer **T1** is used for CCBS Poss and CCBS Request. +- Timer **T3** is used for CCBS Request Ack. +- Timer **T10** is used for CCBS Recall. +- Note: T3 & T7 are not stopped**. + +Figure 5.2.4: Subscriber A not idle when destination B becomes free (mobile-to-fixed) + +## 5.3 Activation + +Activation of a CCBS Request is carried out by subscriber A. VLR A is considered to be transparent during the activation operation. + +The information flows shown in figures 5.2.1 to 5.2.4 inclusive show the information flow for the activation process. + +## 5.4 Deactivation + +Subscriber A may deactivate CCBS in any of the following ways: + +- Deactivate all outstanding CCBS requests; or +- Deactivate a specific CCBS Request. + +The different deactivation operations are identified by different MMI commands as specified in TS 22.030. + +Deactivation of CCBS requests by subscriber A shall be performed at HLR A. + +To deactivate all outstanding CCBS requests, the Deactivate CCBS operation request shall contain the SS-Code only. + +To deactivate a specific CCBS request, the Deactivate CCBS operation request shall contain the following parameters: + +- SS-Code; +- CCBS Index. + +On receipt of the deactivation request, HLR A shall cancel the CCBS request, i.e. remove all record of a CCBS request from the subscriber A's originating CCBS queue and instruct the destination B network to cancel the corresponding CCBS request in the destination CCBS queue of subscriber B. HLR A shall return a result indicating whether the deactivation attempt was successful or not. + +![Sequence diagram showing the successful deactivation of CCBS requests. The diagram involves five lifelines: MS A, MSC A, VLR A, HLR A, and Destination B Network. The sequence of messages is: 1. MS A sends 'Deactivate CCBS' to MSC A. 2. MSC A sends 'Deactivate CCBS' to VLR A. 3. VLR A sends 'Deactivate CCBS' to HLR A. 4. HLR A sends 'CCBS Cancel' to Destination B Network (with a note). 5. HLR A sends 'Acknowledge' to VLR A. 6. VLR A sends 'Acknowledge' to MSC A. 7. MSC A sends 'Acknowledge' to MS A.](18722c46c9e8475524e634dedd08bac2_img.jpg) + +``` +sequenceDiagram + participant MS A + participant MSC A + participant VLR A + participant HLR A + participant Destination B Network + + MS A->>MSC A: Deactivate CCBS + MSC A->>VLR A: Deactivate CCBS + VLR A->>HLR A: Deactivate CCBS + HLR A->>Destination B Network: CCBS Cancel (note) + HLR A->>VLR A: Acknowledge + VLR A->>MSC A: Acknowledge + MSC A->>MS A: Acknowledge +``` + +Sequence diagram showing the successful deactivation of CCBS requests. The diagram involves five lifelines: MS A, MSC A, VLR A, HLR A, and Destination B Network. The sequence of messages is: 1. MS A sends 'Deactivate CCBS' to MSC A. 2. MSC A sends 'Deactivate CCBS' to VLR A. 3. VLR A sends 'Deactivate CCBS' to HLR A. 4. HLR A sends 'CCBS Cancel' to Destination B Network (with a note). 5. HLR A sends 'Acknowledge' to VLR A. 6. VLR A sends 'Acknowledge' to MSC A. 7. MSC A sends 'Acknowledge' to MS A. + +**Figure 5.4.1: Successful deactivation of all CCBS Requests/a specific CCBS request** + +NOTE: CCBS Cancel shall be sent for each CCBS Request that is cancelled in HLR A. + +NOTE: In the case where a subscriber attempts to perform a deactivation operation but the subscriber is not provisioned with the CCBS service then, the subscriber shall receive an indication that the CCBS service is not provisioned for him. + +## 5.5 Interrogation + +Interrogation of CCBS shall be carried by request to HLR A. HLR A then returns the required information or error to MS A, see figure 5.5.1. MSC A and VLR A are considered to be transparent during the interrogation operation. + +![Sequence diagram showing the general interrogation of completion of calls to busy subscriber. The diagram involves four lifelines: MS A, MSC A, VLR A, and HLR A. The sequence of messages is: 1. MS A sends 'Interrogate CCBS' to MSC A. 2. MSC A sends 'Interrogate CCBS' to VLR A. 3. VLR A sends 'Interrogate CCBS' to HLR A. 4. HLR A sends 'Acknowledge' back to VLR A. 5. VLR A sends 'Acknowledge' back to MSC A. 6. MSC A sends 'Acknowledge' back to MS A.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` +sequenceDiagram + participant MS A + participant MSC A + participant VLR A + participant HLR A + Note left of MS A: Interrogate CCBS + MS A->>MSC A: Interrogate CCBS + Note right of MSC A: Interrogate CCBS + MSC A->>VLR A: Interrogate CCBS + Note right of VLR A: Interrogate CCBS + VLR A->>HLR A: Interrogate CCBS + Note right of HLR A: Acknowledge + HLR A-->>VLR A: Acknowledge + Note right of VLR A: Acknowledge + VLR A-->>MSC A: Acknowledge + Note right of MSC A: Acknowledge + MSC A-->>MS A: Acknowledge +``` + +Sequence diagram showing the general interrogation of completion of calls to busy subscriber. The diagram involves four lifelines: MS A, MSC A, VLR A, and HLR A. The sequence of messages is: 1. MS A sends 'Interrogate CCBS' to MSC A. 2. MSC A sends 'Interrogate CCBS' to VLR A. 3. VLR A sends 'Interrogate CCBS' to HLR A. 4. HLR A sends 'Acknowledge' back to VLR A. 5. VLR A sends 'Acknowledge' back to MSC A. 6. MSC A sends 'Acknowledge' back to MS A. + +**Figure 5.5.1: General interrogation of completion of calls to busy subscriber** + +The Interrogate CCBS operation request shall contain the SS-Code only. + +In response to a general interrogation, MS A shall be given the AddressOfB, BasicServiceCode and CCBS index for each CCBS Request in the queue. The entries shall be ordered in the chronological order, the oldest entry shall be presented first. + +If there are no CCBS Requests in the queue, MS A shall be given an indication that no entries exist in the queue. + +**NOTE:** In the case where a subscriber attempts to perform an interrogation operation but the subscriber is not provisioned with the CCBS service then, the subscriber shall receive an indication that the CCBS service is not provisioned for him. + +## 5.6 Messages and their contents + +This clause contains the detailed description of the information flows used by CCBS. + +Each Information Element, IE is marked as (M) Mandatory, (C) Conditional or (O) Optional. A mandatory information element shall always be present. A conditional information shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional information element may be present or absent, at the discretion of the application at the sending entity. This categorisation is a functional classification, i.e., stage 2 information and not a stage 3 classifications to be used for the protocol. + +The stage 2 and stage 3 message and information element names are not necessarily identical. + +### 5.6.1 Information elements used in the messages + +In this clause constructed information elements are described. + +#### 5.6.1.1 Call Information information element + +Call Information information element is formed in the MSC A during the CCBS activation. This information element contains unmodified copy of the SETUP message received from the MS A. If CCBS Request is activated, the Call Information is stored in the HLR A. During CCBS Recall Call Information is relayed back to the MS. Refer to SETUP Container information element defined in TS 24.008. + +#### 5.6.1.2 AddressOfB information element + +AddressOfB information element is formed in the MSC A during the CCBS activation. It contains the number of the destination B dialled by the A-user. + +**Table 5.6.1.2: Structure of AddressOfB information element** + +| Parent Information Element | Child Information element name | Information element Required | Information element description | +|----------------------------|-------------------------------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| AddressOfB | B subscriber number,<br>B subscriber subaddress | M<br>C | The number of the destination B dialled by the A-user;<br>Shall be present if it was dialled by the A-user;<br>otherwise shall be absent | + +#### 5.6.1.3 CCBS Description information element + +CCBS Description information element is formed in the HLR A during the CCBS activation. + +**Table 5.6.1.3: Structure of CCBS Description information element** + +| Parent Information Element | Child Information element name | Information element Required | Information element description | +|----------------------------|-------------------------------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCBS Description | CCBS Index,<br>AddressOfB,<br>BasicServiceGroup | M<br>M<br>M | CCBS Index (range 1 - 5) identifies the request in the network.<br>The structure of the AddressOfB is defined in table 5.6.1.2;<br>BasicServiceGroup related to the original call. | + +### 5.6.2 Messages between MS and MSC + +These messages are used in the originating network. + +**Table 5.6.2: Messages between MS and MSC** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|----------------------|----------------|------------------------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCBS POSSIBLE | MSC | - | - | This message contains no information elements. | +| CCBS REQUEST | MS | - | - | This message contains no information elements. | +| CCBS REQUEST ACK | MSC | CCBS Index,<br>AddressOfB,<br>BasicServiceGroup | M<br>O<br>O | CCBS Index (range 1 - 5) identifies the request in the network. The structure of the AddressOfB is defined in table 5.6.1.2<br>BasicServiceGroup related to the original call. | +| CCBS REQUEST ERROR | MSC | Error | M | The information element can take the following values:<br>- Short term denial<br>- Long term denial | +| DEACTIVATE CCBS | MS | CCBS Index | C | If CCBS Index is present the corresponding request shall be deleted, otherwise all requests shall be deleted. | +| DEACTIVATE CCBS ACK | MSC | DeactivateResult | M | The information element can take the following values:<br>- Success<br>- Not Provisioned | +| INTERROGATE CCBS | MS | - | - | This message contains no information elements. | +| INTERROGATE CCBS ACK | MSC | List(1-5) of CCBS Description;<br>No Entries;<br>Not Provisioned | C<br>C<br>C | The list shall contain one entry for each CCBS Request for which the HLR stores data or; the queue is empty or; CCBS is not provisioned for the subscriber<br>Exactly one of these information elements shall be present. The structure of the CCBS Description is defined in table 5.6.1.3. | +| CCBS CALL INFO | MSC | Call Information | M | The content of the Call Information is defined in the subclause 5.6.1.1. | +| CCBS CALL INFO ACK | MS | GSM BC | M | GSM BC indicates the BC the MS prefers to use. The network may allocate a traffic channel accordingly. | +| CCBS CALL INFO ERROR | MS | Error | M | The information element can take the following values:<br>- Incompatible Terminal | +| CCBS RECALL | MSC | CCBS Description,<br>Alerting Pattern | M,<br>C | The structure of the CCBS Description is defined in table 5.6.1.3.<br>Alerting Pattern shall be present if it was received in the CCBS RUF message | +| CCBS SETUP | MS | - | - | The content of the message is the same as the MO Set-up message has. Refer to TS 24.008. | +| CCBS RECALL REJECT | MS | Cause | M | The MS shall indicate the reason of CCBS Recall rejection. The information element can take the following values:<br>- Recall Rejected by the user<br>- UDUB<br>- ACMmax exceeded | + +### 5.6.3 Messages between MSC and VLR (B-interface) + +#### 5.6.3.1 Messages between MSC and VLR in the originating network + +These messages are used in the originating network. Some messages are used also in the terminating network. They are marked accordingly. + +**Table 5.6.3.1: Messages between MSC and VLR in the originating network** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|-----------------------------------|----------------|---------------------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CALL END | MSC | - | - | This message contains no information elements.<br><br>The message is used also in the terminating network. | +| CCBS CALL DELIVERY | MSC | Outcome | M | The information element indicates whether CCBS Call was successful or failure. It can take the following values:<br>- Success;<br>- Failure;<br>- NDUB;<br>- Busy;<br>- Absent Subscriber..<br><br>The message is used also in the terminating network. | +| CCBS REQUEST | MSC | - | - | This message contains no information elements | +| CCBS REQUEST ACK | VLR | CCBS Index,<br><br>AddressOfB,<br><br>BasicServiceGroup | M<br><br>O<br><br>O | CCBS Index (range 1 - 5) identifies the request in the network. The structure of the AddressOfB is defined in table 5.6.1.2<br><br>BasicServiceGroup related to the original call. | +| CCBS REQUEST ERROR | VLR | Error | M | The information element can take the following values:<br>- Short term denial;<br>- Long term denial. | +| COMPLETE RECALL | VLR | Call Information | M | The content of the Call Information is defined in the subclause 5.6.1.1. | +| COMPLETE RECALL ACK | MSC | - | - | This message contains no information elements | +| COMPLETE RECALL NEGATIVE RESPONSE | MSC | Negative Response | M | The negative information element can take the following values:<br>- Absent Subscriber;<br>- Incompatible Terminal;<br>- Radio Congestion. | +| DEACTIVATE CCBS | MSC | CCBS Index | C | If CCBS Index is present the corresponding request shall be deleted, otherwise all requests shall be deleted. | +| DEACTIVATE CCBS ACK | VLR | DeactivateResult | M | The information element can take the following values:<br>- Success;<br>- Not Provisioned. | +| INTERROGATE CCBS | MSC | - | - | This message contains no information elements | + +**Table 5.6.3.1: Messages between MSC and VLR in the originating network, cont.** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|---------------------------------------------------------|----------------|----------------------------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| INTERROGATE<br>CCBS ACK | VLR | List(1-5) of CCBS Description;<br>No Entries;<br><br>Not Provisioned | C<br><br>C<br><br>C | The list shall contain one entry for each CCBS Request for which the HLR stores data; or the queue is empty; or<br><br>CCBS is not provisioned for the subscriber.<br><br>Exactly one of these information elements shall be present. The structure of the CCBS Description is defined in table 5.6.1.3. | +| NOT IDLE | MSC | - | - | This message contains no information elements. The message is used also in the terminating network. | +| PAGE MS FOR RECALL | VLR | Location area ID,<br><br>TMSI | M<br><br>O | Location area in which the MS is to be paged<br><br>TMSI to be broadcast to identify the MS | +| PAGE MS FOR RECALL NEGATIVE RESPONSE | MSC | Negative Response | M | The negative information element can take the following values:<br>- Unknown LAI;<br>- Absent Subscriber;<br>- Busy Subscriber. | +| PROCESS ACCESS REQUEST | MSC | - | - | Refer to TS 23.018 | +| RADIO FAILURE | MSC | - | - | This message contains no information elements.<br><br>The message is used also in the terminating network. | +| RECALL | VLR | CCBS Description<br><br>Alerting Pattern | M<br><br>C | The structure of the CCBS Description is defined in table 5.6.1.3.<br><br>Alerting Pattern shall be present if it was received in the CCBS RUF message | +| RECALL ACK | MSC | Cause | M | The information element can take the following values:<br>- Accept;<br>- Rejected;<br>- T4 Expiry;<br>- T10 Expiry;<br>- Radio Failure;<br>- UDUB, busy;<br>- UDUB, idle;<br>- Incompatible terminal. | +| SEARCH FOR MS<br>MSC FOR RECALL | VLR | - | - | This message contains no information elements | +| SEARCH FOR MS<br>MSC FOR RECALL<br>ACK | MSC | - | - | This message contains no information elements | +| SEARCH FOR MS<br>MSC FOR RECALL<br>NEGATIVE<br>RESPONSE | MSC | Negative Response | M | The negative information element can take the following values:<br>- Absent Subscriber;<br>- Busy Subscriber; | +| SEND INFO FOR<br>OUTGOING CALL | MSC | - | - | Refer to TS 23.018 | +| START STATUS<br>ENQUIRY | VLR | - | - | This message contains no information elements.<br><br>The message is used also in the terminating network. | +| STATUS ENQUIRY<br>RESULT | MSC | Status | M | The information element can take the following values:<br>- CCBS Idle;<br>- CCBS Not Idle.<br><br>The message is used also in the terminating network. | +| STOP STATUS<br>ENQUIRY | VLR | - | - | This message contains no information elements.<br><br>The message is used also in the terminating network. | + +#### 5.6.3.2 Messages between MSC and VLR in the destination network + +These messages are used in the destination network. Some messages are used also in the originating network. They are marked accordingly. + +**Table 5.6.3.2: Messages between MSC and VLR in the destination network** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|-----------------------------------------------|----------------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CALL END | MSC | - | - | Refer to table 5.6.3.1 | +| CCBS CALL DELIVERY | MSC | - | - | Refer to table 5.6.3.1 | +| START STATUS ENQUIRY | VLR | - | - | Refer to table 5.6.3.1 | +| STATUS ENQUIRY RESULT | MSC | - | - | Refer to table 5.6.3.1 | +| STOP STATUS ENQUIRY | VLR | - | - | Refer to table 5.6.3.1 | +| RADIO FAILURE | MSC | - | - | Refer to table 5.6.3.1 | +| NOT IDLE | MSC | - | - | Refer to table 5.6.3.1 | +| COMPLETE CALL | VLR | -<br><br>Indicator | -<br><br>C | Refer to TS 23.018<br>In addition:<br>The information element shall be present if the call is CCBS Call; otherwise it shall be absent. | +| PROCESS CALL WAITING | VLR | -<br><br>Indicator | -<br><br>C | Refer to TS 23.018<br>In addition:<br>The information element shall be present if the call is CCBS Call; otherwise it shall be absent. | +| SEND INFO FOR INCOMING CALL ACK | VLR | -<br><br>CCBS Target | -<br><br>C | Refer to TS 23.018<br>In addition:<br>The information element shall be present if the B subscriber can be target of CCBS request; otherwise it shall be absent. | +| SEND INFO FOR INCOMING CALL NEGATIVE RESPONSE | VLR | -<br><br>CCBS Target | -<br><br>C | Refer to TS 23.018<br>In addition:<br>The information element shall be present if the B subscriber can be target of CCBS request; otherwise it shall be absent. | + +### 5.6.4 Messages between VLR and HLR (D-interface) + +#### 5.6.4.1 Messages between VLR and HLR in the originating network + +These messages are used between VLR - HLR in the originating network. Some messages are used also in the destination network. They are marked accordingly. + +**Table 5.6.4.1: Messages between VLR and HLR in the originating network** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|--------------------|----------------|--------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCBS REQUEST | VLR | Call Information | M | The content of the Call Information is defined in the subclause 5.6.1.1. | +| | | ISDN BC | M | ISDN BC derived for the initial call. | +| | | ISDN HLC | C | Shall be present if ISDN HLC was present in the initial call; otherwise shall be absent. | +| | | ISDN LLC | C | Shall be present if ISDN LLC was present in the initial call; otherwise shall be absent. | +| | | Presentation Indicator | C | Shall be present if CLIR was invoked for the initial call; otherwise shall be absent. | +| | | Translated B No | M | The number used for routing purposes stored in international E.164 format. | +| | | CAMEL Invoked | C | Shall be present if MO CAMEL was invoked in the initial call; otherwise shall be absent. | +| | | Basic Service Group | M | GSM Elementary Basic Service Group which corresponds to the basic service used for initial call set-up | +| | | AddressOfB | M | The structure of the AddressOfB is defined in table 5.6.1.2 | +| CCBS REQUEST ACK | HLR | CCBS Index | M | CCBS Index (range 1 - 5) identifies the request in the network. The structure of the AddressOfB is defined in table 5.6.1.2 | +| | | AddressOfB | O | | +| | | Basic Service Group | O | BasicServiceGroup related to the original call. | +| CCBS REQUEST ERROR | HLR | Error | M | The information element can take the following values:<br>- Short term denial;<br>- Long term denial; | +| CCBS RUF | HLR | Call Information | M | The content of the Call Information is defined in the subclause 5.6.1.1. | +| | | CCBS Description | M | The content of the CCBS Description is defined in table 5.6.1.3. | +| | | Translated B No | M | The number used for routing purposes in international E.164 format. | +| | | Replace B No | C | The information element shall be present if the HLR instructs the MSC to replace the destination B number with the translated B number; otherwise it shall be absent. | +| | | Alerting Pattern | C | Alerting Pattern shall be present if the HLR has determined an alerting category or an alerting level for the CCBS recall | +| CCBS RUF ACK | VLR | Result | M | The information element indicates whether CCBS Recall was accepted. It can take the following values:<br>- RUF Accepted;<br>- RUF Rejected;<br>- T4 Expiry;<br>- T10 Expiry;<br>- UDUB, idle;<br>- UDUB, busy. | +| CCBS RUF ERROR | VLR | Error | M | The information element indicates the reason why CCBS Recall could not be successfully delivered. It can take the following values:<br>- IMSI Detached;<br>- Restricted Area;<br>- No Page Response;<br>- Incompatible Terminal;<br>- Absent Subscriber;<br>- Radio Failure;<br>- Ccomp Busy;<br>- System Failure. | + +Table 5.6.4.1: Messages between VLR and HLR in the originating network, cont. + +| Message | Message sender | Information element name | Information element Required | Information element description | +|------------------------|----------------|-----------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EVENT REPORT | VLR | Status | M | The information element contains subscriber status. It can take the following values:<br>- CCBS Idle;<br>- CCBS Not Idle;<br>- CCBS Not Reachable.<br><br>The message is used also in the terminating network. | +| EVENT REPORT ACK | HLR | - | - | This message contains no information elements<br><br>The message is used also in the terminating network. | +| EVENT REPORT_ERROR | HLR | Error | M | The information element contains no application specific error values.<br><br>The message is used also in the terminating network. | +| START REPORTING | HLR | - | - | This message contains no information elements.<br><br>The message is used also in the terminating network. | +| START REPORTING ACK | VLR | Status | M | The information element contains subscriber status. It can take the following values:<br>- CCBS Idle;<br>- CCBS Not Idle;<br>- CCBS Not Reachable.<br><br>The message is used also in the terminating network. | +| START REPORTING ERROR | VLR | Error | M | The information element contains no application specific error values.<br><br>The message is used also in the terminating network. | +| CONTINUE MONITORING | HLR | - | - | This message contains no information elements.<br><br>The message is used also in the terminating network. | +| STOP REPORTING | HLR | - | - | This message contains no information elements.<br><br>The message is used also in the terminating network. | +| CCBS CALL REPORT | VLR | Mode<br><br>Outcome<br><br>Status | M<br><br>M<br><br>C | The information element indicates the reporting mode. It can take the following values :<br>- A;<br>- B.<br><br>The information element indicates the outcome of the CCBS Call. It can take the following values:<br>- Success;<br>- Busy (only for mode A);<br>- NDUB (only for mode B)<br>- Failure.<br><br>The information element contains subscriber status. It is set only for mode B. It can take the following values:<br>- CCBS Idle;<br>- CCBS Not Idle;<br>- CCBS Not Reachable.<br><br>The message is used also in the terminating network. | +| CCBS CALL REPORT ACK | HLR | - | - | This message contains no information elements.<br><br>The message is used also in the terminating network. | +| CCBS CALL REPORT ERROR | HLR | Error | M | The information element contains no application specific error values.<br><br>The message is used also in the terminating network. | +| DEACTIVATE CCBS | VLR | CCBS Index | C | If CCBS Index is present the corresponding request shall be deleted, otherwise all requests shall be deleted. | +| DEACTIVATE CCBS ACK | HLR | DeactivateResult | M | The information element can take the following values:<br>- Success;<br>- Not Provisioned. | +| DEACTIVATE CCBS ERROR | HLR | Error | M | The information element contains no application specific error values. | + +**Table 5.6.4.1: Messages between VLR and HLR in the originating network, cont.** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|------------------------|----------------|----------------------------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| INTERROGATE CCBS | VLR | - | - | This message contains no information elements. | +| INTERROGATE CCBS ACK | HLR | List(1-5) of CCBS Description;<br>No Entries;<br><br>Not Provisioned | C<br><br>C<br><br>C | The list shall contain one entry for each CCBS Request for which the HLR stores data or; the queue is empty or;<br><br>CCBS is not provisioned for the subscriber.<br><br>Exactly one of these information elements shall be present. The structure of the CCBS Description is defined in table 5.6.1.3. | +| INTERROGATE CCBS ERROR | HLR | Error | M | The information element contains no application specific error values. | + +#### 5.6.4.2 Messages between VLR and HLR in the destination network + +These messages are used between VLR - HLR in the destination network. Some messages are used also in the originating network. They are marked accordingly. + +**Table 5.6.4.2: Messages between VLR and HLR in the destination network** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|------------------------|----------------|-------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| EVENT REPORT | VLR | - | - | Refer to table 5.6.4.1 | +| EVENT REPORT ACK | HLR | - | - | Refer to table 5.6.4.1 | +| EVENT REPORT ERROR | HLR | - | - | Refer to table 5.6.4.1 | +| START REPORTING | HLR | - | - | Refer to table 5.6.4.1 | +| START REPORTING ACK | VLR | - | - | Refer to table 5.6.4.1 | +| START REPORTING ERROR | VLR | - | - | Refer to table 5.6.4.1 | +| CONTINUE MONITORING | HLR | - | - | Refer to table 5.6.4.1 | +| STOP REPORTING | HLR | - | - | Refer to table 5.6.4.1 | +| CCBS CALL REPORT | VLR | - | - | Refer to table 5.6.4.1 | +| CCBS CALL REPORT ACK | HLR | - | - | Refer to table 5.6.4.1 | +| CCBS CALL REPORT ERROR | HLR | - | - | Refer to table 5.6.4.1 | +| PROVIDE ROAMING NUMBER | HLR | <br><br>CCBS Call Reporting Request | <br><br>C | Refer to TS 23.018<br>In addition:<br>The information element shall be present for CCBS Call roaming number enquiry; otherwise it shall be absent. | + +### 5.6.5 Messages between MSC and HLR (C-interface) + +**Table 5.6.5: Messages between MSC and HLR** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|-------------------------------------|----------------|-------------------------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SEND ROUTING INFO | MSC | -<br>CCBS Supported<br>CCBS Call Indicator | -<br>C<br>C | Refer to TS 23.018<br>In addition:<br>The information element shall be present if GMSC supports CCBS; otherwise it shall be absent.<br>The information element shall be present, if SRI is for CCBS Call; otherwise it shall be absent. | +| SEND ROUTING INFO_ACK | HLR | -<br>CCBS Target<br>Keep CCBS Call Indicator<br>Forwarding Reason | -<br>C<br>C<br>C | Refer to TS 23.018<br>In addition:<br>The information element shall be present if the call is forwarded on busy and the subscriber B can be target of CCBS requests; otherwise it shall be absent.<br>The information element shall be present if the VMSC supports CCBS and SRI enquiry was for CCBS Call; otherwise it shall be absent.<br>The reason CFBusy shall be present if the HLR has determined that the call is to be forwarded for that CCBS case. | +| SEND ROUTING INFO NEGATIVE RESPONSE | HLR | -<br>Negative Response | -<br>- | Refer to TS 23.018<br>New value(s) for existing parameter(s):<br>- Busy_CCBS_Possible;<br>- Busy_CCBS_Not Possible. | + +### 5.6.6 Messages between MSC - MSC (E-interface) + +**Table 5.6.6: Messages between MSC and MSC** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|----------------------|----------------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RESUME CALL HANDLING | MSC | -<br>CCBS Target | -<br>C | Refer to TS 23.079<br>In addition:<br>The information element shall be present if the call is forwarded on busy and the subscriber B can be target of CCBS requests; otherwise it shall be absent. | + +### 5.6.7 Existing parameters containing CCBS specific information + +Mobile Station Classmark 2 (refer to TS 24.008) contains information whether “Network initiated MO CM connection request” is supported or not. This information is vital for the recall mechanism. + +CC capabilities (refer to TS 24.008) contains information whether “Prolonged Clearing Procedures” are supported or not. This information is vital for the activation mechanism. + +SS-Code and SS-Status (refer to TS 29.002) contains information whether CCBS service is provisioned to the subscriber. Both originating and destination CCBS service have their own SS-Code. + +# 6 Monitoring and CCBS Call Reporting + +## 6.1 Monitoring + +### 6.1.1 Overview + +Monitoring is the process where the subscriber state is observed and reported. When monitoring is started, the current subscriber state is reported and any subsequent changes of subscriber state are reported until monitoring is stopped. + +Monitoring subscriber state information will be necessary against MS B and may also be necessary against MS A. + +For both these cases the monitoring functionality is located in the appropriate serving VMSC/VLR and is controlled from the appropriate HLR. The actions on the A-side and B-side for monitoring are completely independent and the following description is generic to cover either case. The HLR sends an explicit Start Reporting signal to the VLR to initiate monitoring. The VLR acknowledges the request confirming that monitoring has started and indicates the current status of the subscriber state in the VMSC/VLR. The VLR will continue to send an Event Report to the HLR whenever the appropriate subscriber state transition event occurs. The HLR sends an explicit Stop Reporting signal to the VLR when reporting on the subscriber state transitions is no longer required. + +### 6.1.2 Monitoring Subscriber B-state information + +The CCBS service requires monitoring of the subscriber state at the called destination network (B-side). This monitoring enables the HLR B to be aware of any transition of subscriber state in VMSC/VLR B while there is an active CCBS Request in the HLR B queue. The basic service operation is that, when the destination B subscriber state becomes Idle, the HLR B is informed and a Remote User Free indication is sent towards the originating A network at the appropriate time. If subsequently to that event the destination B subscriber state becomes not Idle or not reachable, then the HLR B is informed by the VMSC/VLR B in order that it can take an appropriate action towards HLR A, e.g. defer sending of the Remote User Free indication. + +### 6.1.3 Monitoring Subscriber A state information: + +Monitoring Subscriber A state information will be necessary if the Remote User Free indication from Destination B network cannot be acted upon because e.g. MS A is not idle or not reachable and leads to the CCBS request being suspended. The service action in this event is that, when the subscriber state subsequently becomes Idle, the HLR A is informed and a Resume indication is sent towards the destination B network at the appropriate time. + +## 6.2 MSC/VLR Monitoring Model + +The Monitoring model represents the information related to the status of the subscriber connection in the MSC/VLR. A generic monitoring model is used in the MSC/VLR covering the needs of both subscriber A and subscriber B state information for CCBS. The MSC/VLR monitoring model for CCBS is shown in figure 6.2.1. Note that state transitions reported to the HLR are shown as solid lines. + +![Figure 6.2.1: MSC/VLR Monitoring Model. A state transition diagram with three states: NOT IDLE, NOT REACHABLE, and IDLE. NOT IDLE and NOT REACHABLE are at the top, and IDLE is at the bottom. Solid lines represent state transitions reported to the HLR: NOT IDLE to IDLE, NOT REACHABLE to IDLE, and IDLE to NOT IDLE. Dashed lines represent other state transitions: NOT IDLE to NOT REACHABLE and NOT REACHABLE to NOT IDLE.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +``` + +stateDiagram-v2 + [*] --> NOT IDLE + [*] --> NOT REACHABLE + NOT IDLE --> IDLE + NOT REACHABLE --> IDLE + IDLE --> NOT IDLE + NOT IDLE -.-> NOT REACHABLE + NOT REACHABLE -.-> NOT IDLE + +``` + +Figure 6.2.1: MSC/VLR Monitoring Model. A state transition diagram with three states: NOT IDLE, NOT REACHABLE, and IDLE. NOT IDLE and NOT REACHABLE are at the top, and IDLE is at the bottom. Solid lines represent state transitions reported to the HLR: NOT IDLE to IDLE, NOT REACHABLE to IDLE, and IDLE to NOT IDLE. Dashed lines represent other state transitions: NOT IDLE to NOT REACHABLE and NOT REACHABLE to NOT IDLE. + +Figure 6.2.1: MSC/VLR Monitoring Model + +### 6.2.1 Subscriber status + +The monitoring model in the MSC/VLR makes use of the three subscriber states described in table 6.2.1. + +NOTE: Refer to TS 23.078 for equivalent subscriber state description. + +Table 6.2.1: Subscriber States + +| Subscriber states | Description (for monitoring purposes) | Notes | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| IDLE | The state of the MS is neither "NOT IDLE" nor "NOT REACHABLE" | "Assumed Idle" | +| NOT IDLE | The MS is engaged on a transaction for a MO or MT circuit switched call | "CAMEL busy" | +| NOT REACHABLE | The MSC/VLR can determine from its internal data that the MS is not reachable e.g. IMSI detached, Restricted Area, No Page Response. | "Network Determined Not Reachable" | + +For each subscriber state a description can be found on the entry events, functions and exit events. + +#### 6.2.1.1 Idle + +Entry events: + +- Indication of last call released (Mobile Originated or Mobile Terminated); +- Indication of radio link failure; +- Indication of MS activity related to e.g. MO-SMS, MT-SMS and CISS; +- IMSI Attached; +- Location Update. + +Functions: + +- Events leading to a transition to the Not Idle or Not Reachable subscriber state are awaited. + +Exit events: + +- A Mobile Originated Set-up message is received from the MS for first (and only) call; +- A Mobile Terminated Set-up message is sent to the MS for first (and only) call. +- IMSI Detached; +- Roaming in LA not allowed; +- No Page Response; +- An exception condition is encountered e.g. Cancel Location indication received. + +#### 6.2.1.2 Not Idle + +Entry events: + +- A Mobile Originated Set-up message is received from the MS for first (and only) call; +- A Mobile Terminated Set-up message is sent to the MS for first (and only) call. + +Functions: + +- Events leading to a transition to the Idle or Not Reachable subscriber state are awaited. + +Exit events: + +- Indication of last call released (Mobile Originated or Mobile Terminated); +- Indication of radio link failure; +- An exception condition is encountered e.g. Cancel Location indication received. + +#### 6.2.1.3 Not Reachable + +Entry events: + +- IMSI Detached; +- Roaming in LA not allowed; +- No Page Response. + +Functions: + +- Events leading to a transition to the Idle or Not Idle subscriber state are awaited. + +Exit events: + +- Indication of MS activity related to e.g. MO-SMS, MT-SMS and CISS; +- IMSI Attached; +- Location Update; +- A Mobile Originated Set-up message is received from the MS for first (and only) call; +- A Mobile Terminated Set-up message is sent to the MS for first (and only) call; +- An exception condition is encountered e.g. Cancel Location indication received. + +### 6.2.2 Reporting of subscriber state transitions + +Transitions between subscriber states are reported from the MSC/VLR, while monitoring in the MSC/VLR is on going. The table 6.2.2 indicates which transitions are monitored in the MSC/VLR and whether these are reported to the HLR for the CCBS service. An appropriate Event Report signal is sent from the VLR to the HLR when a relevant state transition occurs. The Event Report signal includes a status parameter which reflects the subscriber state information. + +**Table 6.2.2: Reporting of Subscriber States Transitions** + +| Subscriber state transition event | Event reporting HLR informed | Event report Subscriber status | +|-----------------------------------|------------------------------|--------------------------------| +| IDLE to NOT IDLE | Yes | CCBS Not Idle | +| IDLE to NOT REACHABLE | Yes | CCBS Not Reachable | +| NOT IDLE to IDLE | Yes | CCBS Idle | +| NOT IDLE to NOT REACHABLE | No | - | +| NOT REACHABLE to IDLE | Yes | CCBS Idle | +| NOT REACHABLE to NOT IDLE | No | - | + +#### 6.2.2.1 Start Reporting of Monitoring Events + +When a Start Reporting signal is received from the HLR, the VLR shall acknowledge the request confirming that monitoring has started and indicate the current status of the subscriber state in the MSC/VLR. The VLR shall subsequently continue to send the Event Reports indicated in table 6.2.2 whenever the appropriate subscriber state transition event occurs. + +Note where a single user has a CCBS request activated against him and has an outstanding CCBS request suspended against someone else, (i.e. is effectively both destination B and CCBS subscriber A) reporting on both A-side and B-side is required. In this case, the VLR shall only send a single Event Report as indicated in table 6.2.2 whenever the appropriate subscriber state transition event occurs. The HLR shall not send another Start Reporting signal to the VLR if monitoring is already ongoing in the MSC/VLR for either A-side or the B-side. + +#### 6.2.2.2 Stop Reporting of Monitoring Events + +When a Stop Reporting signal is received from the HLR, the VLR shall stop sending the Event Reports. + +## 6.3 CCBS Call Reporting + +### 6.3.1 Overview + +As well as monitoring of the subscriber state, it is also necessary to report the result of the CCBS Call. The basic reporting requirements are as follows from both the A-side and the B-side. + +#### CCBS Call Reporting - A-side: + +The CCBS service logic in the originating network HLR A requires a report on the outcome of the CCBS Call resulting from the acceptance of the CCBS Recall by Subscriber A. The VLR A sends a CCBS Call Report to the HLR A indicating the outcome of the CCBS call processing in MSC/VLR A when e.g. an address complete message (ACM) is received from the destination B network. CCBS Call Reporting on the A-side is completely independent of any monitoring of subscriber state information. The sending of CCBS Call Report is required even when there is no monitoring ongoing in the MSC/VLR. + +#### CCBS Call Reporting- B-side: + +The CCBS service logic in the destination network HLR B requires a report on the outcome of CCBS Call processing in the MSC/VLR B. The HLR B initiates the CCBS call outcome reporting in the VLR when the VLR is normally queried to provide routing information for mobile terminated calls (by including an CCBS indicator in the PRN message). The VLR B sends a CCBS Call Report to the HLR B indicating the outcome of the CCBS call processing and the new status of the subscriber state in the MSC/VLR B when e.g. MS B is alerted to the CCBS Call. + +### 6.3.2 Originating Network (A-side) + +When a CCBS RUF signal is received by the VLR, CCBS processing in the MSC/VLR leads to a CCBS Recall signal being sent to the MS. When the response to the CCBS Recall is received, the VLR shall subsequently send a CCBS Call Report when the relevant processing for the outgoing CCBS call to the destination network is completed as shown in the SDLs for MSC/VLR A. + +### 6.3.3 Destination Network (B-side) + +When an initiate CCBS Call Reporting Request signal (B-side) is received by the VLR in the Provide Roaming Number message, the VLR shall subsequently send a CCBS Call Report when the relevant processing of the incoming CCBS call is completed as shown in the SDLs for MSC/VLR B. + +#### 6.3.3.1 Interaction of Event Reporting and CCBS Call Report + +Reporting on subscriber state transitions will be ongoing in the MSC/VLR B when a report on the CCBS call outcome is required. + +When a subscriber state transition from IDLE to NOT IDLE occurs due to an incoming CCBS call, an Event Report shall not be sent. Instead, a CCBS Call Report (containing CCBS call outcome information and the status) shall be sent to the HLR B. After the CCBS Call Report has been sent, normal Event Reporting will continue i.e. the VLR shall subsequently send only the Event Reports indicated in table 6.2.2 when the next appropriate subscriber state transition event occurs. + +## 6.4 Location Update + +The MS may roam to a new MSC/VLR area while monitoring is ongoing in the previous MSC/VLR. When the VLR receives a Cancel Location signal from the HLR due to normal mobility management procedures, any ongoing CCBS related activities associated with the subscriber shall cease. + +If the A-side monitoring is ongoing when the HLR receives a Location Update request from the VLR, the Location Update signal is considered to indicate that the subscriber state is idle and the appropriate CCBS process in the HLR is informed. The normal mobility management procedures will lead to a Cancel Location signal being sent to the old VLR causing the Event Reporting to stop. + +If the B-side monitoring is ongoing when the HLR receives a Location Update request from the VLR, the normal mobility management procedures are followed. On successful completion of Location Update procedure, the HLR shall send a Start Reporting signal to the new VLR. If during the handling of the normal Location Updating procedure, it is detected that the new MSC/VLR does not support CCBS, the HLR shall not send a Start Reporting signal to the new VLR. + +NOTE: There is no impact to the MS due to CCBS monitoring, i.e. normal Location Update procedures apply. + +# 7 Mobility + +The handling for CCBS specific mobility is described below. + +## 7.1 Mobility during Activation + +In order to allow the activation of CCBS when the call is released, the CC connection towards the MS shall be kept, to avoid any problems of mobility with the MS A. + +Therefore the MSC shall maintain the CC connection with the MS A while T1 is running and until either T1 expires or the MSC sends a CCBS REQUEST ACK or CCBS REQUEST ERROR to the MS. After MSC has sent CCBS REQUEST ACK or CCBS REQUEST ERROR, the MSC A shall release the CC connection with MS. + +## 7.2 Number used within CCBS Call + +The activating MSC A shall store the originally dialled number in the Call Information container. The TranslatedBNo parameter shall contain destination B address stored in international E.164 format. + +If the MS A is registered outside of the HPLMN during the initial call or when Remote\_User\_Free is received from the destination B network the HLR A may request the recall MSC A to change the number used for CCBS Call to the TranslatedBNo instead. Refer to the SDLs for originating MSC/VLR. + +If CAMEL service was activated in the original call the HLR A shall not request to change the number used for the CCBS Call. + +## 7.3 MS does Location Update + +CCBS does place extra requirements for the Location Update procedure in the HLR when MS is monitored. Refer to subclause 6.4. + +## 7.4 Mobility during CCBS Call in the destination network + +If MS registers to non-supporting network special handling has to be applied. Refer to subclause 10.1.3. + +# 8 Interaction with other supplementary services + +TS 22.093 specifies a number of interactions between CCBS and other supplementary services. Additional details of how these interactions apply are as follows. + +## 8.1 Call forwarding unconditional (CFU) + +If a call to destination B is forwarded to subscriber C by CFU and MS C is NDUB, the GMSC shall inform MSC A that CCBS is not possible when it releases the call. Refer to Process MT\_GMSC (see TS 23.018) for further details. + +If destination B activates CFU after subscriber A has activated a CCBS Request against destination B, HLR B shall not process CCBS Requests in the queue which are related to the relevant Basic Service Group, except that T7 shall continue for each CCBS Request in the destination B queue. If T7 expires for a particular request, HLR B shall cancel the request, as described in the SDLs shown in figure 11.2.2.1. + +If MSC B is monitoring MS B when CFU is activated by destination B and all the CCBS Requests in the destination B queue subsequently become "Active and Quiescent", then HLR B shall send "Stop Reporting" to MSC B. If destination B deactivates CFU resulting in one or more requests becoming "Active and Operative" in the destination B queue then, HLR B shall send "Start Reporting" to MSC B if monitoring is not already ongoing. + +A CCBS Call shall be forwarded without the CCBS call Indicator. + +## 8.2 Call forward on busy (CFB) + +If a call to destination B is forwarded to subscriber C by CFB and MS C is NDUB, the forwarding switch (GMSC or VMSC) shall inform MSC A that CCBS is possible when it releases the call. Refer to Process MT\_GMSC or Process ICH\_MSC (see TS 23.018) for further details. + +If destination B activates CFB after subscriber A has activated a CCBS Request against destination B, HLR B shall continue to process CCBS Requests in the queue. If a CCBS Call subsequently arrives at MSC B and MS B is NDUB, a network provider option exists as to whether: + +- the CCBS call shall be treated as when MS B is busy for the CCBS call, without CFB active; or +- the CCBS call shall be forwarded without the CCBS call Indicator. + +## 8.3 Call forwarding on no reply (CFNRy) + +If a call to destination B is forwarded to subscriber C by CFNRy and MS C is NDUB, the forwarding switch (VMSC) shall inform MSC A that CCBS is not possible when it releases the call. Refer to Process MT\_GMSC or Process ICH\_MSC (see TS 23.018) for further details + +If destination B activates CFNRy after subscriber A has activated a CCBS Request against destination B, HLR B shall continue to process CCBS Requests in the queue. + +A CCBS call shall be forwarded without the CCBS call Indicator. + +## 8.4 Call forwarding on MS not reachable (CFNRc) + +If a call to destination B is forwarded to subscriber C by CFNRc and MS C is NDUB, the forwarding switch (GMSC or VMSC) shall inform MSC A that CCBS is not possible when it releases the call. Refer to Process MT\_GMSC or Process ICH\_MSC (see TS 23.018) for further details. + +If destination B activates CFNRc after subscriber A has activated a CCBS Request against destination B, HLR B shall continue to process CCBS Requests in the queue. + +The CCBS call shall be forwarded without the CCBS call Indicator. + +## 8.5 Call Waiting (CW) + +No impact. + +## 8.6 Multiparty service (MPTY) + +No impact. + +## 8.7 Closed user group (CUG) + +No impact. + +## 8.8 Advice Of Charge (AoC) + +If subscriber A accepts a "CCBS Recall" indication but ACMmax exceeds, then MSC A shall cancel the associated request and shall not establish the CCBS Call. + +## 8.9 Barring of all outgoing calls (BAOC) + +If subscriber A accepts a "CCBS Recall" indication but MSC A detects that BAOC is active and operative, then MSC A shall cancel the associated request and shall not establish the CCBS Call. + +## 8.10 Barring of outgoing international calls (BOIC) + +If subscriber A accepts a "CCBS Recall" indication but the CCBS Call would be an international call and MSC A detects that BOIC is active and operative, then MSC A shall cancel the associated request and shall not establish the CCBS Call. + +## 8.11 Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC) + +If subscriber A accepts a "CCBS Recall" indication but the CCBS Call would be an international call except to the home PLMN country and MSC A detects that BOIC-exHC is active and operative, then MSC A shall cancel the associated request and shall not establish the CCBS Call. + +## 8.12 Barring of all incoming calls (BAIC) + +If a CCBS Request arrives at HLR B and HLR B detects that BAIC is active and operative for the relevant Basic Service Group, then HLR B shall not accept the activation attempt and shall indicate short term denial in the response. + +If MSC B is monitoring MS B when BAIC is activated by destination B then all the CCBS Requests in the destination B queue subsequently become "Active and Quiescent" and HLR B shall send "Stop Reporting" to MSC B. If destination B deactivates BAIC resulting in one or more requests becoming "Active and Operative" in the destination B queue then, HLR B shall send "Start Reporting" to MSC B if monitoring is not already ongoing. + +If barring of all incoming calls becomes active and operative for a particular Basic Service Group for destination B, such that a CCBS call from subscriber A is not permitted, HLR B shall cancel the associated request related to the Basic Service Group and select the next non-suspended request in the queue for processing for other Basic Service Groups. + +## 8.13 Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam) + +If a CCBS Request arrives at HLR B and HLR B detects that BIC-Roam is active and operative for the relevant Basic Service Group, then HLR B shall not accept the activation attempt and shall indicate short term denial in the response. + +If MSC B is monitoring MS B when BIC-Roam is activated by destination B then all the CCBS Requests in the destination B queue subsequently become "Active and Quiescent" and HLR B shall send "Stop Reporting" to MSC B. If destination B deactivates BIC-Roam resulting in one or more requests becoming "Active and Operative" in the destination B queue then, HLR B shall send "Start Reporting" to MSC B if monitoring is not already ongoing. + +If barring of incoming calls when roaming outside the home PLMN country becomes active and operative for a particular Basic Service Group for destination B, such that a CCBS call from subscriber A is not permitted, HLR B shall cancel the associated request related to the Basic Service Group and select the next non-suspended request in the queue for processing for other Basic Service Groups. + +## 8.14 Completion of calls to busy subscriber (CCBS) + +Subscriber A may have successfully activated one or more CCBS requests against different destinations B, and also have one or more CCBS requests successfully activated against him by different subscribers. In this case, HLR A shall co-ordinate the different requests. + +Checking for an identical CCBS request already existing shall include checks in both directions, i.e. if subscriber A activates a CCBS Request against destination B, HLR A shall check subscriber A's originating queue for any previous requests activated by subscriber A against destination B for the same basic service group. HLR A shall also check subscriber A's target queue for any requests activated by destination B against subscriber A for the same basic service group. + +# --- 9 Interaction with other network features + +TS 22.093 specifies a number of interactions between CCBS and other network features. + +## 9.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) + +For a terminating CAMEL based service which changes the destination B address for the original call which subsequently encounters NDUB, the GMSC shall inform originating network that CCBS is not possible when it releases the call. + +If an originating CAMEL based service determines for a CCBS Call a different destination B Address than for the original call, the CCBS Call shall be released and the associated CCBS Request shall be cancelled. + +If the CAMEL based service requests a call set-up to an alternative destination after the original call has met Busy, CCBS Possible condition, the CCBS activation shall be allowed if the alternative call set-up also encounters Busy condition. + +## 9.2 Support of Optimal Routeing (SOR) + +The CCBS supporting GMSC shall include CCBS Supported indicator to the SRI message. + +If HLR B receives a request for routeing information when destination B is blocked (i.e. the HLR B is waiting for an SRI for a CCBS call set-up) and the SRI does not include a CCBS call indicator nor CCBS supported in the GMSC indicator and the request is from a GMSC not in the same PLMN as HLR B, then HLR B shall return an SRI negative response indicating OR not allowed. This will force the GMSC to route the call to a GMSC in the same PLMN as HLR B (see TS 23.079). + +The GMSC in HPLMN B should be able to include the CCBS Call indicator in the non-OR SRI, and the CCBS call set-up will proceed, although it won't be optimally routed. + +If the HLR receives an SRI indicating a CCBS-capable GMSC but not a CCBS call while awaiting SRI for a CCBS call, it can treat the request as if the B-subscriber were busy, regardless of where the GMSC is. + +# 10 Interworking with other networks + +The point of interworking shall be the interface between HLR A and HLR B. The flow of information across this interface shall be identical to that between exchanges for the ISDN version of CCBS. + +Interworking with ISDNs which support the ISDN version of CCBS is therefore available without further modification. + +Interworking with networks other than ISDNs, e.g. private networks, is not specified here, but is not precluded. + +CCBS shall be able to interwork through networks which do not support CCBS. In this situation, the CCBS service may fail. + +## 10.1 Interworking with network entities not supporting CCBS + +CCBS requires support of the service by the following entities for it to operate as specified above: + +- MS A; +- MSC A; +- VLR A; +- HLR A; +- GMSC; +- HLR B; +- MSC B; +- VLR B. + +The following shows the actions required to cover the situations where these entities do not support CCBS. Note that the situation is further complicated by mobility. For example, MSC A may support CCBS when the initial request is made, but if subscriber A has changed location, the new MSC A may not support CCBS. + +It is assumed that the entities support the service at the points in the call where actions are initiated by them, and that an entity which receives an indication for the CCBS service but does not support it can indicate its lack of support to the sending entity. + +### 10.1.1 CCBS not supported by MSC A + +HLR A knows whether the MSC A supports CCBS or not through the transfer of subscriber data. + +MS B becomes idle + +When HLR A receives the "Remote User Free" indication for a particular CCBS Request and detects that the MSC A where MS A is currently registered does not support CCBS, then HLR A shall suspend the corresponding CCBS Request and shall send "CCBS Suspend" to HLR B. When MS A registers in a different MSC which supports CCBS, HLR A shall resume the corresponding CCBS Request and shall send "CCBS Resume" to HLR B, continuing as if MS A had become free. + +### 10.1.2 CCBS not supported by HLR B + +Initial call encounters busy + +If an MSC B that supports CCBS recognises that HLR B does not support CCBS then "CCBS Not Possible" will be generated in the CCBS diagnostic. + +### 10.1.3 CCBS not supported by MSC B + +HLR B knows whether the MSC B supports CCBS or not through the transfer of subscriber data. + +CCBS Request + +If MSC B does not support CCBS, HLR B acknowledge the request and start T7. No processing of the destination B queue and subsequently no monitoring of destination B will be possible until destination B registers in a supporting MSC. + +# CCBS Call set-up + +If HLR B knows that MSC B does not support CCBS the HLR B shall delete the corresponding CCBS Request and shall request a Roaming No without including the CCBS Call indicator in the request. Within Send Routeing Info Ack the HLR shall inform the GMSC to remove CCBS Call Indicator from the IAM message. + +After a "Remote User Free" has been sent from MSC B but before the CCBS call set-up is completed, destination B may register in an MSC which does not support the service. MSC B shall accept the CCBS call, but MSC B will not be able to inform HLR B of the successful completion of the CCBS call, so the request will remain active in HLR B until the recall B timer (T9) expires and the request is cancelled. + +# --- 11 Network entity functions + +The following SDL diagrams describe the various processes and procedures within individual network entities for handling CCBS. The SDL diagrams are as follows: + +## 11.1 Originating Network Processes + +### 11.1.1 Processes and procedures in MSC/VLR + +Figure 11.1.1.1: Process MSC\_CCBS\_Recall\_Manager + +This process controls the CCBS Recall handling in the MSC and controls timers T4 and T10 + +Figure 11.1.1.2: Process VLR\_CCBS\_Recall\_Manager + +This process controls the CCBS Recall handling in the VLR and reports the result of the Recall directly to the HLR. + +Figure 11.1.1.3: Process OCH\_CCBS\_VLR + +This process controls the CCBS Call Setup in the VLR + +Figure 11.1.1.4: Procedure CCBS\_Check\_OG\_Call + +This procedure checks whether the outgoing call meets various conditions set by the CCBS supplementary service. If CCBS is not implemented Pass exit shall be taken. + +Figure 11.1.1.5: Procedure CCBS\_Check\_If\_CCBS\_Possible + +This procedure is called when Release message is received from the destination network. It checks whether CCBS activation is possible. + +Figure 11.1.1.6: Procedure CCBS\_Activation\_MSC + +If CCBS activation is possible this procedure is called. It handles the dialogue between MS and MSC and MSC and HLR respectively. + +Figure 11.1.1.7: Procedure Page\_MS\_MSC\_For\_Recall + +During CCBS recall this procedure handles paging of the MS if the location area id is known. + +Figure 11.1.1.8: Procedure Search\_For\_MS\_MSC\_For\_Recall + +During CCBS recall this procedure handles paging of the MS on MSC side if the location area id is not known. + +Figure 11.1.1.9: Procedure Search\_For\_MS\_VLR\_Recall + +During CCBS recall this procedure handles paging of the MS on VLR side if the location area id is not known. + +Figure 11.1.1.10: Procedure Complete\_Recall\_MSC + +During CCBS recall this procedure handles early channel allocation and establish CC connection with the MS. + +Figure 11.1.1.11: Procedure CCBS\_OCH\_Report\_Success + +This procedure is called when CCBS call is successfully delivered to the destination network. The procedure informs HLR of successful call delivery. + +Figure 11.1.1.12: Procedure CCBS\_OCH\_Report\_Failure + +This procedure is called when CCBS call delivery failed to the destination network. The procedure informs HLR of call delivery failure. + +![State transition diagram for Process MSC_CCBS_Recall_Manager. It starts with an initial state leading to 'Idle'. From 'Idle', two parallel transitions occur: 'Search_For_MS_MSC_For_Recall' and 'Page_MS_For_Recall'. These lead to 'Search_For_MS_MSC_For_Recall' and 'Page_MS_MSC_For_Recall' respectively. Both lead to a 'Result=Pass' decision. If 'Yes', it goes to 'Process_Access_Request_MSC' (referenced to GSM 03.18). If 'No', it goes to 'Release call resources'. From 'Process_Access_Request_MSC', another 'Result=Pass' decision occurs. If 'Yes', it goes to 'Wait_For_Recall_Result'. If 'No', it goes to 'Release call resources'. Both 'Wait_For_Recall_Result' and 'Release call resources' lead to the final 'Idle' state.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +Process MSC\_CCBS\_Recall\_Manager + +1(4) + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Search_For_MS_MSC_For_Recall + Idle --> Page_MS_For_Recall + Search_For_MS_MSC_For_Recall --> Search_For_MS_MSC_For_Recall + Page_MS_For_Recall --> Page_MS_MSC_For_Recall + Search_For_MS_MSC_For_Recall --> Result_Pass_1{Result=Pass} + Page_MS_MSC_For_Recall --> Result_Pass_1 + Result_Pass_1 -- Yes --> Process_Access_Request_MSC + Result_Pass_1 -- No --> Release_call_resources + Process_Access_Request_MSC --> Result_Pass_2{Result=Pass} + Result_Pass_2 -- Yes --> Wait_For_Recall_Result + Result_Pass_2 -- No --> Release_call_resources + Wait_For_Recall_Result --> Idle + Release_call_resources --> Idle +``` + +Signals to/from the left are to/from the BSS. signals to/from the right are to/from the VLR unless specified otherwise + +Refer to GSM 03.18 + +State transition diagram for Process MSC\_CCBS\_Recall\_Manager. It starts with an initial state leading to 'Idle'. From 'Idle', two parallel transitions occur: 'Search\_For\_MS\_MSC\_For\_Recall' and 'Page\_MS\_For\_Recall'. These lead to 'Search\_For\_MS\_MSC\_For\_Recall' and 'Page\_MS\_MSC\_For\_Recall' respectively. Both lead to a 'Result=Pass' decision. If 'Yes', it goes to 'Process\_Access\_Request\_MSC' (referenced to GSM 03.18). If 'No', it goes to 'Release call resources'. From 'Process\_Access\_Request\_MSC', another 'Result=Pass' decision occurs. If 'Yes', it goes to 'Wait\_For\_Recall\_Result'. If 'No', it goes to 'Release call resources'. Both 'Wait\_For\_Recall\_Result' and 'Release call resources' lead to the final 'Idle' state. + +Figure 11.1.1.1: Process MSC\_CCBS\_Recall\_Manager (sheet 1 of 4) + +![Flowchart for Process MSC_CCBS_Recall_Manager. The process starts with 'Wait_For_Recall_Result', followed by 'Complete Recall', then 'Complete_Recall_MSC'. A decision 'Result' follows, with 'Pass' leading to 'TCH allocated := False' and 'Fail' leading to 'Release call resources'. The 'Pass' path also includes 'TCH allocated := True' and 'TCH_allocated'. Both 'TCH allocated := False' and 'TCH allocated := True' lead to 'Wait_For_Recall'. 'Release call resources' leads to 'Idle'. 'Wait_For_Recall' leads to 'Recall' (message), then 'Recall' (decision). A decision 'MS = Busy' follows, with 'Yes' leading to 'Start T10' and 'No' leading to 'Start T4'. Both 'Start T10' and 'Start T4' lead to 'Wait_For_Recall_Response'. A note on the left asks 'Is the MS engaged on a circuit switched call'. A note on the right explains signal directions.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Process MSC\_CCBS\_Recall\_Manager + +2(4) + +``` +graph TD; A[Wait_For_Recall_Result] --> B[Complete Recall]; B --> C[Complete_Recall_MSC]; C --> D{Result}; D -- Pass --> E[TCH allocated := False]; D -- Fail --> F[Release call resources]; D -- TCH_allocated --> G[TCH allocated := True]; E --> H[Wait_For_Recall]; G --> H; F --> I[Idle]; H --> J[Recall]; J --> K{Recall}; K --> L{MS = Busy}; L -- Yes --> M[Start T10]; L -- No --> N[Start T4]; M --> O[Wait_For_Recall_Response]; N --> O; +``` + +Signals to/from the left are to/from the BSS. signals to/from the right are to/from the VLR unless specified otherwise + +Is the MS engaged on a circuit switched call + +Flowchart for Process MSC\_CCBS\_Recall\_Manager. The process starts with 'Wait\_For\_Recall\_Result', followed by 'Complete Recall', then 'Complete\_Recall\_MSC'. A decision 'Result' follows, with 'Pass' leading to 'TCH allocated := False' and 'Fail' leading to 'Release call resources'. The 'Pass' path also includes 'TCH allocated := True' and 'TCH\_allocated'. Both 'TCH allocated := False' and 'TCH allocated := True' lead to 'Wait\_For\_Recall'. 'Release call resources' leads to 'Idle'. 'Wait\_For\_Recall' leads to 'Recall' (message), then 'Recall' (decision). A decision 'MS = Busy' follows, with 'Yes' leading to 'Start T10' and 'No' leading to 'Start T4'. Both 'Start T10' and 'Start T4' lead to 'Wait\_For\_Recall\_Response'. A note on the left asks 'Is the MS engaged on a circuit switched call'. A note on the right explains signal directions. + +Figure 11.1.1.1: Process MSC\_CCBS\_Recall\_Manager (sheet 2 of 4) + +![State transition diagram for Process MSC_CCBS_Recall_Manager. It starts at 'Wait_For_Recall_Response' and branches based on events: CCBS_Recall_Reject (Cause), T4 Expiry, T10 Expiry, and Release Transaction. The CCBS_Recall_Reject path leads to 'Stop T4 Stop T10' and then a 'Cause' decision. The 'Cause' decision has three paths: 'Rejected ACMMMax exceeded' (leading to 'Cause:= Rejected'), 'UDUB' (leading to 'MS = Busy' decision), and 'No' (leading to 'Cause:= UDUB, idle'). The 'MS = Busy' decision has 'Yes' (leading to 'Cause:= UDUB, busy') and 'No' (leading to 'Cause:= UDUB, idle') paths. All cause paths lead to 'Recall_Ack (Cause)', which then leads to 'Release call resources' and finally 'Idle'. A note indicates that signals to/from the left are to/from the BSS, and signals to/from the right are to/from the VLR unless specified otherwise. Another note asks if the MS is engaged on a circuit switched call.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Process MSC\_CCBS\_Recall\_Manager 3(4) + +``` +stateDiagram-v2 + [*] --> Wait_For_Recall_Response + state "CCBS_Recall_Reject (Cause)" as CCBS_Recall_Reject + state "T4 Expiry" as T4_Expiry + state "T10 Expiry" as T10_Expiry + state "Release Transaction" as Release_Transaction + state "Stop T4 Stop T10" as Stop_T4_Stop_T10 + state "Cause" as Cause + state "MS = Busy" as MS_Busy + state "Cause:= UDUB, busy" as Cause_UDUB_busy + state "Cause:= UDUB, idle" as Cause_UDUB_idle + state "Cause:= Rejected" as Cause_Rejected + state "Cause:= T4 Expiry" as Cause_T4_Expiry + state "Cause:= T10 Expiry" as Cause_T10_Expiry + state "Cause:= Radio failure" as Cause_Radio_failure + state "Recall_Ack (Cause)" as Recall_Ack + state "Release call resources" as Release_call_resources + state "Idle" as Idle + + Note right of [*]: Signals to/from the left are to/from the BSS. signals to/from the right are to/from the VLR unless specified otherwise + Note left of MS_Busy: Is the MS engaged on a circuit switched call + + Wait_For_Recall_Response --> CCBS_Recall_Reject + Wait_For_Recall_Response --> T4_Expiry + Wait_For_Recall_Response --> T10_Expiry + Wait_For_Recall_Response --> Release_Transaction + + CCBS_Recall_Reject --> Stop_T4_Stop_T10 + Stop_T4_Stop_T10 --> Cause + + Cause --> Cause_Rejected : Rejected ACMMMax exceeded + Cause --> MS_Busy : UDUB + Cause --> Cause_UDUB_idle : No + + MS_Busy --> Cause_UDUB_busy : Yes + MS_Busy --> Cause_UDUB_idle : No + + Cause_UDUB_busy --> Recall_Ack + Cause_UDUB_idle --> Recall_Ack + Cause_Rejected --> Recall_Ack + T4_Expiry --> Cause_T4_Expiry + T10_Expiry --> Cause_T10_Expiry + Release_Transaction --> Cause_Radio_failure + + Cause_T4_Expiry --> Recall_Ack + Cause_T10_Expiry --> Recall_Ack + Cause_Radio_failure --> Recall_Ack + + Recall_Ack --> Release_call_resources + Release_call_resources --> Idle +``` + +State transition diagram for Process MSC\_CCBS\_Recall\_Manager. It starts at 'Wait\_For\_Recall\_Response' and branches based on events: CCBS\_Recall\_Reject (Cause), T4 Expiry, T10 Expiry, and Release Transaction. The CCBS\_Recall\_Reject path leads to 'Stop T4 Stop T10' and then a 'Cause' decision. The 'Cause' decision has three paths: 'Rejected ACMMMax exceeded' (leading to 'Cause:= Rejected'), 'UDUB' (leading to 'MS = Busy' decision), and 'No' (leading to 'Cause:= UDUB, idle'). The 'MS = Busy' decision has 'Yes' (leading to 'Cause:= UDUB, busy') and 'No' (leading to 'Cause:= UDUB, idle') paths. All cause paths lead to 'Recall\_Ack (Cause)', which then leads to 'Release call resources' and finally 'Idle'. A note indicates that signals to/from the left are to/from the BSS, and signals to/from the right are to/from the VLR unless specified otherwise. Another note asks if the MS is engaged on a circuit switched call. + +Figure 11.1.1.1: Process MSC\_CCBS\_Recall\_Manager (sheet 3 of 4) + +![Flowchart for Process MSC_CCBS_Recall_Manager (sheet 4 of 4)](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +Process MSC\_CCBS\_Recall\_Manager + +4(4) + +``` + +graph TD + Start([Wait_For_Recall_Response]) --> CCBS_Setup[/CCBS_Setup/] + CCBS_Setup --> Dec1{BasicServiceGroup +of the call = +BasicServiceGroup received +from HLR} + + Dec1 -- No --> Cause1[Cause := +Incompatible +terminal] + Cause1 --> Ack1[/Recall_Ack +(Cause)/] + Ack1 --> Idle1([Idle]) + + Dec1 -- Yes --> Dec2{ReplaceBNo} + + Dec2 -- True --> Trans[Use TranslatedBNo +instead of the originally +dialed B number] + Dec2 -- False --> StopT[Stop T4 +Stop T10] + Trans --> StopT + + StopT --> Cause2[Cause := +Accept] + Cause2 --> Ack2[/Recall_Ack +(Cause)/] + Ack2 --> Report[CCBS_Report_ +Not_Idle] + Report --> OGCall[OG_Call_ +Setup_MSC] + OGCall --> Check[CCBS_Check_ +Last_Call] + Check --> Release[Release +call +resources] + Release --> Idle2([Idle]) + + subgraph Notes + Note1[Signals to/from the left +are to/from the BSS. +signals to/from the right +are to/from the VLR +unless specified otherwise] + Note2[Refer to GSM 03.18] + end + +``` + +Signals to/from the left are to/from the BSS. signals to/from the right are to/from the VLR unless specified otherwise + +BasicServiceGroup of the call = BasicServiceGroup received from HLR + +Use TranslatedBNo instead of the originally dialed B number + +Refer to GSM 03.18 + +Flowchart for Process MSC\_CCBS\_Recall\_Manager (sheet 4 of 4) + +Figure 11.1.1.1: Process MSC\_CCBS\_Recall\_Manager (sheet 4 of 4) + +![Flowchart for Process VLR_CCBS_Recall_Manager. It starts at Idle, receives CCBS_RUF, checks parameters (see GSM 03.18), and then checks Result. If Result fails, it sends a Negative Response. If it passes, it checks if IMSI is Detached or if Roaming in LA is Allowed. If either is true, it sends an error (IMSI_Detached or Restricted_Area). If both pass, it checks if Location area ID is known. If not, it searches for MS_VLR_Recall. If that fails, it goes to connector 1. If it passes, it pages the MS for recall and waits for a request. If the location area ID is known, it pages the MS for recall and waits for a request. If the location area ID is not known, it sends a CCBS_RUF Error and goes to Idle. A note indicates signals to/from the left are to/from the MSC, and to/from the right are to/from the HLR.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +### Process VLR\_CCBS\_Recall\_Manager 1(4) + +``` +graph TD; Start([Idle]) --> CCBS_RUF[/CCBS_RUF/]; CCBS_RUF --> Check[Check Parameters]; Check -.-> Note1[See GSM 03.18]; Check --> Result{Result}; Result -- Fail --> Error1[Error:= Negative Response]; Error1 --> CCBS_RUF_Error[/CCBS_RUF Error (Error)/]; CCBS_RUF_Error --> NotReachable[/Not Reachable/]; NotReachable --> Idle1([Idle]); Result -- Pass --> IMSI{IMSI Detached}; IMSI -- Yes --> Error2[Error := IMSI_Detached]; IMSI -- No --> Roaming{Roaming in LA Allowed}; Roaming -- No --> Error3[Error:= Restricted_Area]; Roaming -- Yes --> LocID{Location area ID known}; LocID -- No --> Search[Search_For_MS_VLR_Recall]; Search --> ResultPass{Result=Pass}; ResultPass -- Yes --> ToMonitoring[To CCBS_Monitoring_VLR]; ToMonitoring -.-> NotReachable; ResultPass -- No --> Connector1((1)); LocID -- Yes --> PageMS[/Page_MS_For_Recall/]; PageMS --> Wait[Wait_For_Recall_Request]; Note2[Signals to and from the left are to/from the MSC. Signals to and from the right are to/from the HLR unless specified otherwise]; +``` + +Flowchart for Process VLR\_CCBS\_Recall\_Manager. It starts at Idle, receives CCBS\_RUF, checks parameters (see GSM 03.18), and then checks Result. If Result fails, it sends a Negative Response. If it passes, it checks if IMSI is Detached or if Roaming in LA is Allowed. If either is true, it sends an error (IMSI\_Detached or Restricted\_Area). If both pass, it checks if Location area ID is known. If not, it searches for MS\_VLR\_Recall. If that fails, it goes to connector 1. If it passes, it pages the MS for recall and waits for a request. If the location area ID is known, it pages the MS for recall and waits for a request. If the location area ID is not known, it sends a CCBS\_RUF Error and goes to Idle. A note indicates signals to/from the left are to/from the MSC, and to/from the right are to/from the HLR. + +Figure 11.1.1.2: Process VLR\_CCBS\_Recall\_Manager (sheet 1 of 4) + +![Flowchart for Process VLR_CCBS_Recall_Manager (sheet 2 of 4). The process starts with 'Wait_For_Recall_Request'. It branches into 'Page MS For Recall negative response' (left) and 'Process Access Request' (right). The left path checks for 'Absent Subscriber' and 'Busy Subscriber'. The right path checks 'Process Access Request_VLR' and 'Result = Pass'. Both paths lead to error handling or completion states.](8269648391c59363ea61243864a2adf7_img.jpg) + +Process VLR\_CCBS\_Recall\_Manager 2(4) + +``` + +graph TD + Start([Wait_For_Recall_Request]) --> Branch1(( )) + Branch1 --> LeftPath[Page MS For Recall negative response] + Branch1 --> RightPath[Process Access Request] + LeftPath --> Absent{Absent Subscriber} + Absent -- Yes --> Not_Reachable{Not_Reachable} + Not_Reachable --> To_CCBS[To CCBS_Monitoring_VLR] + Absent -- No --> Busy{Busy Subscriber} + Busy -- Yes --> Error_CComp[Error := CComp_Busy] + Busy -- No --> Error_System[Error := System_Failure] + RightPath --> VLR_Request[Process Access Request_VLR] + VLR_Request --> Result{Result = Pass} + Result -- No --> Error_Absent[Error := Absent_Subscriber] + Result -- Yes --> Complete[Complete Recall] + Error_CComp --> CCBS_RUF[CCBS_RUF_Error (Error)] + Error_System --> CCBS_RUF + Error_Absent --> CCBS_RUF + CCBS_RUF --> Idle([Idle]) + Complete --> Wait_Complete[Wait_For_Complete_Call_Result] + +``` + +Signals to and from the left are to/from the MSC. Signals to and from the right are to/from the HLR unless specified otherwise + +Refer to GSM 03.18 + +This check does not determine whether a CC connection is established but rather that another call is in the establishment phase + +Flowchart for Process VLR\_CCBS\_Recall\_Manager (sheet 2 of 4). The process starts with 'Wait\_For\_Recall\_Request'. It branches into 'Page MS For Recall negative response' (left) and 'Process Access Request' (right). The left path checks for 'Absent Subscriber' and 'Busy Subscriber'. The right path checks 'Process Access Request\_VLR' and 'Result = Pass'. Both paths lead to error handling or completion states. + +Figure 11.1.1.2: Process VLR\_CCBS\_Recall\_Manager (sheet 2 of 4) + +![State transition diagram for Process VLR_CCBS_Recall_Manager. It starts at 'Wait_for_Complete_Recall_Result'. A 'Complete Recall ack' leads to 'Recall' then 'Wait_For_Recall_Response'. A 'Complete Recall negative response' leads to a 'Negative Response' decision. From 'Negative Response', 'Incompatible_Terminal' leads to 'Error := Incompatible Terminal', 'Absent_Subscriber Radio_Congestion' leads to 'Error := Radio_Failure', and 'ELSE' leads to 'Error := System_Failure'. All three error states lead to a merge point, then to 'CCBS_RUF Error (Error)' and finally 'Idle'. A note indicates signals are to/from MSC on the left and HLR on the right.](32ff77da4286b58c4778033acaa10836_img.jpg) + +Process VLR\_CCBS\_Recall\_Manager 3(4) + +``` +stateDiagram-v2 + [*] --> Wait_for_Complete_Recall_Result + state "Complete Recall ack" as Complete_Recall_ack + state "Complete Recall negative response" as Complete_Recall_negative_response + state "Negative Response" as Negative_Response + state "Recall" as Recall + state "Error := Incompatible Terminal" as Error_Incompatible_Terminal + state "Error := Radio_Failure" as Error_Radio_Failure + state "Error := System_Failure" as Error_System_Failure + state "CCBS_RUF Error (Error)" as CCBS_RUF_Error + state "Wait_For_Recall_Response" as Wait_For_Recall_Response + state "Idle" as Idle + + Wait_for_Complete_Recall_Result --> Complete_Recall_ack + Wait_for_Complete_Recall_Result --> Complete_Recall_negative_response + Complete_Recall_ack --> Recall + Complete_Recall_negative_response --> Negative_Response + Negative_Response --> Incompatible_Terminal : Incompatible_Terminal + Negative_Response --> Absent_Subscriber_Radio_Congestion : Absent_Subscriber Radio_Congestion + Negative_Response --> ELSE : ELSE + Incompatible_Terminal --> Error_Incompatible_Terminal + Absent_Subscriber_Radio_Congestion --> Error_Radio_Failure + ELSE --> Error_System_Failure + Error_Incompatible_Terminal --> Merge + Error_Radio_Failure --> Merge + Error_System_Failure --> Merge + Merge --> CCBS_RUF_Error + CCBS_RUF_Error --> Idle + Recall --> Wait_For_Recall_Response +``` + +Signals to and from the left are to/from the MSC. Signals to and from the right are to/from the HLR unless specified otherwise + +State transition diagram for Process VLR\_CCBS\_Recall\_Manager. It starts at 'Wait\_for\_Complete\_Recall\_Result'. A 'Complete Recall ack' leads to 'Recall' then 'Wait\_For\_Recall\_Response'. A 'Complete Recall negative response' leads to a 'Negative Response' decision. From 'Negative Response', 'Incompatible\_Terminal' leads to 'Error := Incompatible Terminal', 'Absent\_Subscriber Radio\_Congestion' leads to 'Error := Radio\_Failure', and 'ELSE' leads to 'Error := System\_Failure'. All three error states lead to a merge point, then to 'CCBS\_RUF Error (Error)' and finally 'Idle'. A note indicates signals are to/from MSC on the left and HLR on the right. + +Figure 11.1.1.2: Process VLR\_CCBS\_Recall\_Manager (sheet 3 of 4) + +![State transition diagram for Process VLR_CCBS_Recall_Manager. It starts with Wait_For_Recall_Response, followed by a transition to Recall_Ack (Cause). A decision diamond 'Cause' has three branches: 'Radio Failure' leading to 'Error := Radio_Failure', 'Incompatible Terminal' leading to 'Error := Incompatible_Terminal', and 'ELSE' leading to 'Result := Cause'. All three branches lead to a transition 'CCBS_RUF_Ack (Result)'. From there, a decision diamond 'Result' has two branches: 'RUF Accepted' leading to 'Wait_For_Call_Delivery', and 'ELSE' leading to 'CCBS_RUF_Error (Error)'. The 'RUF Accepted' path continues through 'CCBS_Call_Delivery (Outcome)', 'Mode:=A', and 'CCBS_Call_Report (Mode, Outcome)' to the 'Idle' state. The 'ELSE' path from 'Result' also leads to 'CCBS_RUF_Error (Error)'. Both 'CCBS_RUF_Error (Error)' and 'CCBS_Call_Report (Mode, Outcome)' lead to the 'Idle' state.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +Process VLR\_CCBS\_Recall\_Manager 4(4) + +``` +stateDiagram-v2 + [*] --> Wait_For_Recall_Response + state "Wait_For_Recall_Response" as Wait_For_Recall_Response + state "Recall_Ack (Cause)" as Recall_Ack_Cause + state "Cause" as Cause + state "Error := Radio_Failure" as Error_Radio_Failure + state "Error := Incompatible_Terminal" as Error_Incompatible_Terminal + state "Result := Cause" as Result_Cause + state "CCBS_RUF_Ack (Result)" as CCBS_RUF_Ack_Result + state "Result" as Result + state "RUF Accepted" as RUF_Accepted + state "Wait_For_Call_Delivery" as Wait_For_Call_Delivery + state "CCBS_Call_Delivery (Outcome)" as CCBS_Call_Delivery_Outcome + state "Mode:=A" as Mode_A + state "CCBS_Call_Report (Mode, Outcome)" as CCBS_Call_Report_Mode_Outcome + state "CCBS_RUF_Error (Error)" as CCBS_RUF_Error_Error + state "Idle" as Idle + + Wait_For_Recall_Response --> Recall_Ack_Cause + Recall_Ack_Cause --> Cause + Cause --> Error_Radio_Failure : Radio Failure + Cause --> Error_Incompatible_Terminal : Incompatible Terminal + Cause --> Result_Cause : ELSE + Error_Radio_Failure --> CCBS_RUF_Ack_Result + Error_Incompatible_Terminal --> CCBS_RUF_Ack_Result + Result_Cause --> CCBS_RUF_Ack_Result + CCBS_RUF_Ack_Result --> Result + Result --> RUF_Accepted : RUF Accepted + Result --> CCBS_RUF_Error_Error : ELSE + RUF_Accepted --> Wait_For_Call_Delivery + Wait_For_Call_Delivery --> CCBS_Call_Delivery_Outcome + CCBS_Call_Delivery_Outcome --> Mode_A + Mode_A --> CCBS_Call_Report_Mode_Outcome + CCBS_Call_Report_Mode_Outcome --> Idle + CCBS_RUF_Error_Error --> Idle +``` + +State transition diagram for Process VLR\_CCBS\_Recall\_Manager. It starts with Wait\_For\_Recall\_Response, followed by a transition to Recall\_Ack (Cause). A decision diamond 'Cause' has three branches: 'Radio Failure' leading to 'Error := Radio\_Failure', 'Incompatible Terminal' leading to 'Error := Incompatible\_Terminal', and 'ELSE' leading to 'Result := Cause'. All three branches lead to a transition 'CCBS\_RUF\_Ack (Result)'. From there, a decision diamond 'Result' has two branches: 'RUF Accepted' leading to 'Wait\_For\_Call\_Delivery', and 'ELSE' leading to 'CCBS\_RUF\_Error (Error)'. The 'RUF Accepted' path continues through 'CCBS\_Call\_Delivery (Outcome)', 'Mode:=A', and 'CCBS\_Call\_Report (Mode, Outcome)' to the 'Idle' state. The 'ELSE' path from 'Result' also leads to 'CCBS\_RUF\_Error (Error)'. Both 'CCBS\_RUF\_Error (Error)' and 'CCBS\_Call\_Report (Mode, Outcome)' lead to the 'Idle' state. + +Figure 11.1.1.2: Process VLR\_CCBS\_Recall\_Manager (sheet 4 of 4) + +![Flowchart for Process OCH_CCBS_VLR. It starts with an oval connector, followed by an 'Idle' state (oval), then a 'Send info For Outgoing Call' process (parallelogram) with a note 'From GSM 03.18 Procedure OG_Call_Setup_MSC', then an 'OG_Call_Subscription_Check_VLR' process (rectangle) with a note 'See GSM 03.18', and finally an 'Idle' state (oval).](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +Process OCH\_CCBS\_VLR 1(1) + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> SendInfo[/Send info For Outgoing Call/]; SendInfo -.-> Note1[Note: From GSM 03.18 Procedure OG_Call_Setup_MSC]; SendInfo --> OGCall[OG_Call_Subscription_Check_VLR]; OGCall -.-> Note2[See GSM 03.18]; OGCall --> Idle2([Idle]); +``` + +Flowchart for Process OCH\_CCBS\_VLR. It starts with an oval connector, followed by an 'Idle' state (oval), then a 'Send info For Outgoing Call' process (parallelogram) with a note 'From GSM 03.18 Procedure OG\_Call\_Setup\_MSC', then an 'OG\_Call\_Subscription\_Check\_VLR' process (rectangle) with a note 'See GSM 03.18', and finally an 'Idle' state (oval). + +Figure 11.1.1.3: Process OCH\_CCBS\_VLR + +![Flowchart for Procedure CCBS_Check_OG_Call. It starts with a connector, followed by a decision 'CCBS Provisioned and ME supports CCBS'. If 'No', it goes to 'Result := Pass'. If 'Yes', it goes to 'Reconnect'. If 'Reconnect' is 'True', it goes to 'Result := Pass'. If 'Reconnect' is 'False', it goes to 'CCBS Call'. If 'CCBS Call' is 'No', it goes to 'Result := Pass'. If 'CCBS Call' is 'Yes', it goes to 'TranslatedBNo := Routing address in international E.164 format'. Then it goes to a decision 'Translated B No received from HLR = CCBS Call translated target'. If 'Yes', it goes to 'Set CCBS_Call_Indicator to IAM message'. If 'No', it goes to 'Result := Fail'. Both 'Set CCBS_Call_Indicator to IAM message' and 'TranslatedBNo := Routing address in international E.164 format' lead to 'Store Call Information'. From 'Store Call Information', it goes to 'Result := Pass'.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +Procedure CCBS\_Check\_OG\_Call 1(1) + +``` +graph TD; Start([ ]) --> D1{CCBS Provisioned and ME supports CCBS}; D1 -- No --> ResultPass1[Result := Pass]; D1 -- Yes --> D2{Reconnect}; D2 -- True --> ResultPass1; D2 -- False --> D3{CCBS Call}; D3 -- No --> ResultPass1; D3 -- Yes --> T1[TranslatedBNo := Routing address in international E.164 format]; T1 --> D4{Translated B No received from HLR = CCBS Call translated target}; D4 -- Yes --> T2[Set CCBS_Call_Indicator to IAM message]; D4 -- No --> ResultFail[Result := Fail]; T2 --> T3[Store Call Information]; T1 --> T3; T3 --> ResultPass2[Result := Pass]; ResultFail --> End(( )); ResultPass1 --> End; ResultPass2 --> End; +``` + +Flowchart for Procedure CCBS\_Check\_OG\_Call. It starts with a connector, followed by a decision 'CCBS Provisioned and ME supports CCBS'. If 'No', it goes to 'Result := Pass'. If 'Yes', it goes to 'Reconnect'. If 'Reconnect' is 'True', it goes to 'Result := Pass'. If 'Reconnect' is 'False', it goes to 'CCBS Call'. If 'CCBS Call' is 'No', it goes to 'Result := Pass'. If 'CCBS Call' is 'Yes', it goes to 'TranslatedBNo := Routing address in international E.164 format'. Then it goes to a decision 'Translated B No received from HLR = CCBS Call translated target'. If 'Yes', it goes to 'Set CCBS\_Call\_Indicator to IAM message'. If 'No', it goes to 'Result := Fail'. Both 'Set CCBS\_Call\_Indicator to IAM message' and 'TranslatedBNo := Routing address in international E.164 format' lead to 'Store Call Information'. From 'Store Call Information', it goes to 'Result := Pass'. + +Figure 11.1.1.4: Procedure CCBS\_Check\_OG\_Call + +![Flowchart for Procedure CCBS_Check_If_CCBS_Possible. The process starts with a connector, followed by a decision 'Call Completion Treatment Indicator present in SI2?'. If 'Yes', it goes to 'Call Completion Treatment Indicator set to reject call completion service request?'. If 'No', it goes to 'CCBS Provisioned'. From 'Call Completion Treatment Indicator set to reject call completion service request?', 'Yes' leads to 'Initial result' and 'No' leads to 'CCBS Provisioned'. From 'CCBS Provisioned', 'Yes' leads to 'Reconnect' and 'No' leads to 'Initial result'. From 'Reconnect', 'True' leads to 'Initial result' and 'False' leads to a decision 'Cause = Busy or Cause = No circuit channel available'. From 'Cause = Busy or Cause = No circuit channel available', 'Yes' leads to 'CCBS Call' and 'No' leads to 'Initial result'. From 'CCBS Call', 'Yes' leads to 'Outcome := Failure' or 'Outcome := Busy', and 'No' leads to 'CCBS Possible'. From 'Outcome := Failure' or 'Outcome := Busy', it goes to 'CCBS_Call_Delivery (Outcome)'. From 'CCBS_Call_Delivery (Outcome)', 'Yes' leads to 'To VLR_CCBS_Recall_Manager' and 'No' leads to 'CCBS Possible'. From 'CCBS Possible', 'Yes' leads to 'ME supports CCBS' and 'No' leads to 'Initial result'. From 'ME supports CCBS', 'Yes' leads to 'Initial result := CCBS_Possible' and 'No' leads to 'Initial result := CCBS_Not_Possible'. From 'Initial result := CCBS_Possible', it goes to 'Result := CCBS_Possible'. From 'Initial result := CCBS_Not_Possible', it goes to 'Clear stored call information', then 'Initial result := CCBS_Not_Possible', then 'Result := CCBS_Not_Possible'. Both 'Result := CCBS_Possible' and 'Result := CCBS_Not_Possible' lead to a final connector.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +Procedure CCBS\_Check\_If\_CCBS\_Possible 1(1) + +``` + +graph TD + Start(( )) --> D1{Call Completion Treatment Indicator present in SI2?} + D1 -- Yes --> D2{Call Completion Treatment Indicator set to reject call completion service request?} + D1 -- No --> D3{CCBS Provisioned} + D2 -- Yes --> D10{Initial result} + D2 -- No --> D3 + D3 -- Yes --> D4{Reconnect} + D3 -- No --> D10 + D4 -- True --> D10 + D4 -- False --> D5{Cause = Busy or Cause = No circuit channel available} + D5 -- Yes --> D6{CCBS Call} + D5 -- No --> D10 + D6 -- Yes --> P1[Outcome := Failure] + D6 -- Yes --> P2[Outcome := Busy] + D6 -- No --> D7{CCBS Possible} + P1 --> P3{CCBS_Call_Delivery (Outcome)} + P2 --> P3 + P3 -- Yes --> P4[To VLR_CCBS_Recall_Manager] + P3 -- No --> D7 + D7 -- Yes --> D8{ME supports CCBS} + D7 -- No --> D10 + D8 -- Yes --> P5[Initial result := CCBS_Possible] + D8 -- No --> P6[Initial result := CCBS_Not_Possible] + P5 --> P7[Result := CCBS_Possible] + P6 --> P8[Clear stored call information] + P8 --> P9[Initial result := CCBS_Not_Possible] + P9 --> P10[Result := CCBS_Not_Possible] + P7 --> End((( ))) + P10 --> End + +``` + +Flowchart for Procedure CCBS\_Check\_If\_CCBS\_Possible. The process starts with a connector, followed by a decision 'Call Completion Treatment Indicator present in SI2?'. If 'Yes', it goes to 'Call Completion Treatment Indicator set to reject call completion service request?'. If 'No', it goes to 'CCBS Provisioned'. From 'Call Completion Treatment Indicator set to reject call completion service request?', 'Yes' leads to 'Initial result' and 'No' leads to 'CCBS Provisioned'. From 'CCBS Provisioned', 'Yes' leads to 'Reconnect' and 'No' leads to 'Initial result'. From 'Reconnect', 'True' leads to 'Initial result' and 'False' leads to a decision 'Cause = Busy or Cause = No circuit channel available'. From 'Cause = Busy or Cause = No circuit channel available', 'Yes' leads to 'CCBS Call' and 'No' leads to 'Initial result'. From 'CCBS Call', 'Yes' leads to 'Outcome := Failure' or 'Outcome := Busy', and 'No' leads to 'CCBS Possible'. From 'Outcome := Failure' or 'Outcome := Busy', it goes to 'CCBS\_Call\_Delivery (Outcome)'. From 'CCBS\_Call\_Delivery (Outcome)', 'Yes' leads to 'To VLR\_CCBS\_Recall\_Manager' and 'No' leads to 'CCBS Possible'. From 'CCBS Possible', 'Yes' leads to 'ME supports CCBS' and 'No' leads to 'Initial result'. From 'ME supports CCBS', 'Yes' leads to 'Initial result := CCBS\_Possible' and 'No' leads to 'Initial result := CCBS\_Not\_Possible'. From 'Initial result := CCBS\_Possible', it goes to 'Result := CCBS\_Possible'. From 'Initial result := CCBS\_Not\_Possible', it goes to 'Clear stored call information', then 'Initial result := CCBS\_Not\_Possible', then 'Result := CCBS\_Not\_Possible'. Both 'Result := CCBS\_Possible' and 'Result := CCBS\_Not\_Possible' lead to a final connector. + +Figure 11.1.1.5: Procedure CCBS\_Check\_If\_CCBS\_Possible + +![State transition diagram for CCBS_Activation_MSC. The process starts at a connector, checks if CCBS is possible, starts timer T1, and then waits for a CCBS request. From the wait state, three transitions are possible: a successful CCBS request (stopping T1, clearing stored info, and sending an ack), a T1 expiry (releasing the transaction, clearing stored info, and ending), or a release transaction (stopping T1 and returning to the wait state).](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +Procedure CCBS\_Activation\_MSC + +1(2) + +``` +stateDiagram-v2 + [*] --> CCBS_Possible + CCBS_Possible --> Start_T1 + Start_T1 --> RR_connection + RR_connection --> Wait_For_CCBS_Request + state "CCBS_Possible" as CCBS_Possible + state "Start T1" as Start_T1 + state "RR connection may be converted to an SDCCH" as RR_connection + state "Wait For CCBS_Request" as Wait_For_CCBS_Request + state "CCBS_Request" as CCBS_Request + state "T1 Expiry" as T1_Expiry + state "Release transaction" as Release_transaction + state "Stop T1" as Stop_T1 + state "Clear Stored Call Information" as Clear_Stored_Info + state "MSC A Wait for CCBS Request Ack" as MSC_A_Wait + state [*] as End + + Wait_For_CCBS_Request --> CCBS_Request + Wait_For_CCBS_Request --> T1_Expiry + Wait_For_CCBS_Request --> Release_transaction + + CCBS_Request --> Stop_T1 + Stop_T1 --> Clear_Stored_Info + Clear_Stored_Info --> MSC_A_Wait + + T1_Expiry --> Release_transaction + Release_transaction --> Stop_T1 + Stop_T1 --> Clear_Stored_Info + Clear_Stored_Info --> End + + Note right of T1_Expiry: Internal timer expiry +``` + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from HLR unless marked otherwise + +State transition diagram for CCBS\_Activation\_MSC. The process starts at a connector, checks if CCBS is possible, starts timer T1, and then waits for a CCBS request. From the wait state, three transitions are possible: a successful CCBS request (stopping T1, clearing stored info, and sending an ack), a T1 expiry (releasing the transaction, clearing stored info, and ending), or a release transaction (stopping T1 and returning to the wait state). + +Figure 11.1.1.6: Procedure CCBS\_Activation\_MSC (sheet 1 of 2) + +![Sequence diagram for Procedure CCBS_Activation_MSC. Lifeline MSC A starts with 'Wait for CCBS Request Ack'. It branches into three paths: 1) 'CCBS Request_Ack' -> 'Release (CCBS Request Ack)' -> 'Release transaction' -> End. 2) 'CCBS Request_Error' -> 'Release (CCBS Error)' -> 'Release transaction' -> End. 3) 'Release transaction' -> End. A note indicates signals to the left are to/from BSS and to the right are to/from HLR.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +Procedure CCBS\_Activation\_MSC + +2(2) + +``` +sequenceDiagram + participant MSC A + Note right of MSC A: Signals to/from the left are to/from the BSS; signals to/from the right are to/from HLR unless marked otherwise + Note left of MSC A: + MSC A->>MSC A: Wait for CCBS Request Ack + alt Path 1: CCBS Request_Ack + MSC A->>Left: CCBS Request_Ack + Left->>Left: Release (CCBS Request Ack) + Left->>Left: Release transaction + Left-->>End: + alt Path 2: CCBS Request_Error + MSC A->>Center: CCBS Request_Error + Center->>Center: Release (CCBS Error) + Center->>Center: Release transaction + Center-->>End: + alt Path 3: Release transaction + MSC A->>Right: Release transaction + Right-->>End: + Note right of End: + Note left of End: +``` + +Sequence diagram for Procedure CCBS\_Activation\_MSC. Lifeline MSC A starts with 'Wait for CCBS Request Ack'. It branches into three paths: 1) 'CCBS Request\_Ack' -> 'Release (CCBS Request Ack)' -> 'Release transaction' -> End. 2) 'CCBS Request\_Error' -> 'Release (CCBS Error)' -> 'Release transaction' -> End. 3) 'Release transaction' -> End. A note indicates signals to the left are to/from BSS and to the right are to/from HLR. + +Figure 11.1.1.6: Procedure CCBS\_Activation\_MSC (sheet 2 of 2) + +![Flowchart for Procedure Page_MS_MSC_For_Recall](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +Procedure Page\_MS\_MSC\_For\_Recall + +PAGE\_M1(2) + +Procedure in the MSC, + to page an MS in a + specified location area + +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([ ]) --> IDKnown{Location +area ID +known} + IDKnown -- No --> NegResp[Regative +response:= +Unknown LAI] + IDKnown -- Yes --> MSConn{MS +connection +exists} + + MSConn -- Yes --> SetAccess[Set access +connection +status] + MSConn -- No --> StartTimer[Start Page +response +timer] + + SetAccess --> ResPass[Result:= +Pass] + ResPass --> End1((X)) + + StartTimer --> Page[/Page/] + Page --> Wait[Wait_For_ +Page_ +Response] + + NegResp --> NegPage[/Page MS For +Recall +negative +response/] + NegPage --> ResFail[Result:= +Fail] + ResFail --> End2((X)) + + RRNote[Does an RR connection exist] -.- MSConn + LocNote[In specified +location area] -.- Page + +``` + +Flowchart for Procedure Page\_MS\_MSC\_For\_Recall + +**Figure 11.1.1.7: Procedure Page\_MS\_MSC\_For\_Recall (sheet 1 of 2)** + +![Flowchart for Procedure Page_MS_MSC_For_Recall. It starts with 'Wait_For_Page_Response' and branches into three paths: 'MS connection established' leading to 'Set access connection status' and 'Result:= Pass'; 'Page response timer expired' leading to 'Negative response:= Absent Subscriber' and 'Page MS For Recall negative response' leading to 'Result:= Fail'; and 'CM Service Request' (for circuit-switched call) leading to 'CM Service Request' (to process OCH_MSC), then 'Negative response:= Busy Subscriber', 'Page MS For Recall negative response', and 'Result:= Fail'. All three paths end at a connector symbol.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +Procedure Page\_MS\_MSC\_For\_Recall + +PAGE\_M2(2) + +Procedure in the MSC, to page an MS in a specified location area + +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([Wait_For_Page_Response]) --> J1(( )); J1 --> MS_Conn_Established{MS connection established}; J1 --> Page_Response_Timer_Expired{Page response timer expired}; J1 --> CM_Service_Request_1{CM Service Request}; MS_Conn_Established --> Set_Access_Connection_Status[Set access connection status]; Set_Access_Connection_Status --> Result_Pass[Result:= Pass]; Result_Pass --> Connector1((X)); Page_Response_Timer_Expired --> Negative_Response_Absent[Negative response:= Absent Subscriber]; Negative_Response_Absent --> Page_MS_For_Recall_Negative_Response_1{{Page MS For Recall negative response}}; Page_MS_For_Recall_Negative_Response_1 --> Result_Fail_1[Result:= Fail]; Result_Fail_1 --> Connector2((X)); CM_Service_Request_1 --> CM_Service_Request_2{{CM Service Request}}; CM_Service_Request_2 --> Negative_Response_Busy[Negative response:= Busy Subscriber]; Negative_Response_Busy --> Page_MS_For_Recall_Negative_Response_2{{Page MS For Recall negative response}}; Page_MS_For_Recall_Negative_Response_2 --> Result_Fail_2[Result:= Fail]; Result_Fail_2 --> Connector3((X)); +``` + +Flowchart for Procedure Page\_MS\_MSC\_For\_Recall. It starts with 'Wait\_For\_Page\_Response' and branches into three paths: 'MS connection established' leading to 'Set access connection status' and 'Result:= Pass'; 'Page response timer expired' leading to 'Negative response:= Absent Subscriber' and 'Page MS For Recall negative response' leading to 'Result:= Fail'; and 'CM Service Request' (for circuit-switched call) leading to 'CM Service Request' (to process OCH\_MSC), then 'Negative response:= Busy Subscriber', 'Page MS For Recall negative response', and 'Result:= Fail'. All three paths end at a connector symbol. + +Figure 11.1.1.7: Procedure Page\_MS\_MSC\_For\_Recall (sheet 2 of 2) + +![Flowchart for Procedure Search_For_MS_MSC_For_Recall. The process starts with a decision 'MS connection exists?'. If 'Yes', it goes to 'Set access connection status' and then 'Result:= Pass'. If 'No', it goes to 'Start Page response timer', then 'Page' (with a note 'In all location areas'), then 'Wait_For_Search_Response'. From 'Wait_For_Search_Response', it branches into three paths: 1) 'MS connection established' -> 'Search_For_MS_MSC_For_Recall Ack' -> 'Set access connection status' -> 'Result:= Pass'. 2) 'Page response timer expired' -> 'Set negative response: Absent Subscriber' -> 'Search For MS MSC For Recall negative response' -> 'Result:= Fail'. 3) 'CM Service Request' (for circuit-switched call) -> 'CM Service Request' (to GSM 03.18 Process OCH_MSC) -> 'Set negative response: Busy Subscriber' -> 'Search For MS MSC For Recall negative response' -> 'Result:= Fail'. All three paths end at a circle with an 'X' symbol.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +Procedure Search\_For\_MS\_MSC\_For\_Recall + +1(1) + +Procedure in the MSC to search for an MS (page in all location areas) + +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([ ]) --> Decision{MS connection exists?}; Decision -- Yes --> SetAccess[Set access connection status]; SetAccess --> ResultPass1[Result:= Pass]; ResultPass1 --> End1((X)); Decision -- No --> StartTimer[Start Page response timer]; StartTimer --> Page{Page}; Note1[In all location areas] -.-> Page; Page --> WaitResponse{Wait_For_Search_Response}; WaitResponse --> MSConnEst{MS connection established}; MSConnEst --> SearchAck{Search_For_MS_MSC_For_Recall Ack}; SearchAck --> SetAccess2[Set access connection status]; SetAccess2 --> ResultPass2[Result:= Pass]; ResultPass2 --> End2((X)); WaitResponse --> TimerExp{Page response timer expired}; TimerExp --> NegResp1[Set negative response: Absent Subscriber]; NegResp1 --> SearchNeg1{Search For MS MSC For Recall negative response}; SearchNeg1 --> ResultFail1[Result:= Fail]; ResultFail1 --> End3((X)); WaitResponse --> CMReq1{CM Service Request}; Note2[For circuit-switched call] -.-> CMReq1; CMReq1 --> CMReq2{CM Service Request}; Note3[To GSM 03.18 Process OCH_MSC] -.-> CMReq2; CMReq2 --> NegResp2[Set negative response: Busy Subscriber]; NegResp2 --> SearchNeg2{Search For MS MSC For Recall negative response}; SearchNeg2 --> ResultFail2[Result:= Fail]; ResultFail2 --> End4((X)); +``` + +Flowchart for Procedure Search\_For\_MS\_MSC\_For\_Recall. The process starts with a decision 'MS connection exists?'. If 'Yes', it goes to 'Set access connection status' and then 'Result:= Pass'. If 'No', it goes to 'Start Page response timer', then 'Page' (with a note 'In all location areas'), then 'Wait\_For\_Search\_Response'. From 'Wait\_For\_Search\_Response', it branches into three paths: 1) 'MS connection established' -> 'Search\_For\_MS\_MSC\_For\_Recall Ack' -> 'Set access connection status' -> 'Result:= Pass'. 2) 'Page response timer expired' -> 'Set negative response: Absent Subscriber' -> 'Search For MS MSC For Recall negative response' -> 'Result:= Fail'. 3) 'CM Service Request' (for circuit-switched call) -> 'CM Service Request' (to GSM 03.18 Process OCH\_MSC) -> 'Set negative response: Busy Subscriber' -> 'Search For MS MSC For Recall negative response' -> 'Result:= Fail'. All three paths end at a circle with an 'X' symbol. + +Figure 11.1.1.8: Procedure Search\_For\_MS\_MSC\_For\_Recall + +![Flowchart for Procedure Search_For_MS_VLR_Recall. It starts with a connector, followed by a decision 'Search_For_MS_MSC_For_Recall'. If 'Wait_For_Search_Result', it branches into two paths: 'Search_For_MS_MSC_For_Recall_Ack' leading to 'Update Location Area ID' and 'Result:= Pass'; and 'Search_For_MS_MSC_For_Recall negative response' leading to 'Transfer negative cause to the parent process' and 'Result:= Fail'. Both paths end with a connector.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +Procedure Search\_For\_MS\_VLR\_Recall 1(1) + +Procedure in the VLR to search for an MS (i.e. page in all location areas) + +Signals to/from the left are to/from the MSC + +``` +graph TD; Start([ ]) --> Decision{Search_For_MS_MSC_For_Recall}; Decision --> Wait([Wait_For_Search_Result]); Wait --> Branch(( )); Branch --> Ack[/Search_For_MS_MSC_For_Recall_Ack/]; Branch --> Negative[/Search_For_MS_MSC_For_Recall negative response/]; Ack --> Update[Update Location Area ID]; Update --> Pass[Result:= Pass]; Pass --> End1((X)); Negative --> Transfer[Transfer negative cause to the parent process]; Transfer --> Fail[Result:= Fail]; Fail --> End2((X)); +``` + +Flowchart for Procedure Search\_For\_MS\_VLR\_Recall. It starts with a connector, followed by a decision 'Search\_For\_MS\_MSC\_For\_Recall'. If 'Wait\_For\_Search\_Result', it branches into two paths: 'Search\_For\_MS\_MSC\_For\_Recall\_Ack' leading to 'Update Location Area ID' and 'Result:= Pass'; and 'Search\_For\_MS\_MSC\_For\_Recall negative response' leading to 'Transfer negative cause to the parent process' and 'Result:= Fail'. Both paths end with a connector. + +Figure 11.1.1.9: Procedure Search\_For\_MS\_VLR\_Recall + +![Sequence diagram for Complete_Recall_MSC procedure. It starts with CM_Serv_Prompt and Wait_For_CM_Serv_Prompt_Response. It then branches into Release transaction, Connection_type_not_supported, and Start_CC. The Start_CC path leads to CCBS_Call_Info and Wait_For_Ack, which then leads to a decision diamond for BasicServiceGroup. The Release transaction and Connection_type_not_supported paths lead to negative responses and eventually to Complete_Recall_negative_Response and Result:= Fail.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +Procedure Complete\_Recall\_MSC 1(2) + +``` +sequenceDiagram + participant User + participant MSC + Note right of MSC: Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + + User->>MSC: CM_Serv_Prompt + MSC-->>User: Wait_For_CM_Serv_Prompt_Response + + alt Release transaction + MSC-->>User: Release transaction + User-->>MSC: Negative response:= Absent subscriber + else Connection_type_not_supported + MSC-->>User: Connection_type_not_supported + else Start_CC + MSC-->>User: Start_CC + User-->>MSC: CCBS_Call_Info + MSC-->>User: Wait_For_Ack + Note right of MSC: BasicServiceGroup of the CCBS_Call_Info = BasicServiceGroup received from HLR + User->>MSC: CCBS_Call_Info_Confirmed + Note right of MSC: Decision diamond for BasicServiceGroup + alt No + MSC-->>User: Negative response:= Incompatible Terminal + else Yes + Note right of MSC: Connection to point 1 + end + end + + Note right of MSC: Incompatible Terminal, Release (UDUB), Release transaction + User-->>MSC: Negative response:= Incompatible Terminal + User-->>MSC: Negative response:= CComp Busy + User-->>MSC: Negative response:= Absent subscriber + + Note right of MSC: Merge point for negative responses + MSC-->>User: Complete_Recall_negative_Response + User-->>MSC: Result:= Fail + Note right of MSC: End point (circle with X) +``` + +Sequence diagram for Complete\_Recall\_MSC procedure. It starts with CM\_Serv\_Prompt and Wait\_For\_CM\_Serv\_Prompt\_Response. It then branches into Release transaction, Connection\_type\_not\_supported, and Start\_CC. The Start\_CC path leads to CCBS\_Call\_Info and Wait\_For\_Ack, which then leads to a decision diamond for BasicServiceGroup. The Release transaction and Connection\_type\_not\_supported paths lead to negative responses and eventually to Complete\_Recall\_negative\_Response and Result:= Fail. + +Figure 11.1.1.10: Procedure Complete\_Recall\_MSC (sheet 1 of 2) + +![Flowchart for Procedure Complete_Recall_MSC. It starts with a circle labeled '1' leading to a decision 'Early traffic channel allocation?'. If 'No', it goes to 'Complete_Recall_Ack' and 'Result := Pass'. If 'Yes', it goes to 'Establish_Originating_TCH_If Required' (referencing GSM 03.18), then to a decision 'Result = Pass'. If 'Yes', it goes to 'Complete_Recall_Ack' and 'Result := TCH_allocated'. If 'No', it goes to 'Negative response := Radio_congestion', then to 'Complete_Recall_negative_Response' and 'Result := Fail'. All three final results lead to terminal circles with an 'X'.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Procedure Complete\_Recall\_MSC 2(2) + +``` +graph TD; Start((1)) --> Decision1{Early traffic channel allocation?}; Decision1 -- No --> Ack1{{Complete_Recall_Ack}}; Ack1 --> Result1[Result := Pass]; Result1 --> End1((X)); Decision1 -- Yes --> Process1[Establish_Originating_TCH_If Required]; Process1 -.-> Ref[Refer GSM 03.18]; Process1 --> Decision2{Result = Pass}; Decision2 -- Yes --> Ack2{{Complete_Recall_Ack}}; Ack2 --> Result2[Result := TCH_allocated]; Result2 --> End2((X)); Decision2 -- No --> Negative[Negative response := Radio_congestion]; Negative --> Ack3{{Complete_Recall_negative_Response}}; Ack3 --> Result3[Result := Fail]; Result3 --> End3((X)); +``` + +Flowchart for Procedure Complete\_Recall\_MSC. It starts with a circle labeled '1' leading to a decision 'Early traffic channel allocation?'. If 'No', it goes to 'Complete\_Recall\_Ack' and 'Result := Pass'. If 'Yes', it goes to 'Establish\_Originating\_TCH\_If Required' (referencing GSM 03.18), then to a decision 'Result = Pass'. If 'Yes', it goes to 'Complete\_Recall\_Ack' and 'Result := TCH\_allocated'. If 'No', it goes to 'Negative response := Radio\_congestion', then to 'Complete\_Recall\_negative\_Response' and 'Result := Fail'. All three final results lead to terminal circles with an 'X'. + +Figure 11.1.1.10: Procedure Complete\_Recall\_MSC (sheet 2 of 2) + +![Flowchart for Procedure CCBS_OCH_Report_Success. The flow starts with a connector symbol, followed by a decision 'CCBS Call'. If 'No', it goes to an exit connector. If 'Yes', it goes to a decision 'Reconnect'. If 'Reconnect' is 'True', it goes to the exit connector. If 'Reconnect' is 'False', it goes to a process 'Outcome := Success', then to an output 'CCBS Call Delivery (Outcome)' which is linked to 'To VLR_CCBS_Recall_Manager', then to a process 'Clear stored call information', and finally to the exit connector.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +Procedure CCBS\_OCH\_Report\_Success 1(1) + +``` +graph TD; Start([ ]) --> CCBS{CCBS Call}; CCBS -- No --> Exit(( )); CCBS -- Yes --> Reconnect{Reconnect}; Reconnect -- True --> Exit; Reconnect -- False --> Outcome[Outcome := Success]; Outcome --> Delivery{{CCBS Call Delivery (Outcome)}}; Delivery -.-> Manager[To VLR_CCBS_Recall_Manager]; Delivery --> Clear[Clear stored call information]; Clear --> Exit; +``` + +Flowchart for Procedure CCBS\_OCH\_Report\_Success. The flow starts with a connector symbol, followed by a decision 'CCBS Call'. If 'No', it goes to an exit connector. If 'Yes', it goes to a decision 'Reconnect'. If 'Reconnect' is 'True', it goes to the exit connector. If 'Reconnect' is 'False', it goes to a process 'Outcome := Success', then to an output 'CCBS Call Delivery (Outcome)' which is linked to 'To VLR\_CCBS\_Recall\_Manager', then to a process 'Clear stored call information', and finally to the exit connector. + +Figure 11.1.1.11: Procedure CCBS\_OCH\_Report\_Success + +![Flowchart for Procedure CCBS_OCH_Report_Failure](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +Procedure CCBS\_OCH\_Report\_Failure + +1(1) + +``` +graph TD; Start([ ]) --> CCBS_Call{CCBS Call}; CCBS_Call -- No --> Join(( )); CCBS_Call -- Yes --> Reconnect{Reconnect}; Reconnect -- True --> Join; Reconnect -- False --> Outcome[Outcome := Failure]; Outcome --> Delivery{{CCBS Call Delivery (Outcome)}}; Delivery --> Join; ToManager[To VLR_CCBS_Recall_Manager] -.-> Delivery; +``` + +The flowchart illustrates the procedure for reporting a failure in a CCBS\_OCH call. It begins with an oval connector symbol, leading to a decision diamond labeled 'CCBS Call'. If the answer is 'No', the flow proceeds to a circular connector symbol. If the answer is 'Yes', it proceeds to another decision diamond labeled 'Reconnect'. If 'Reconnect' is 'True', the flow proceeds to the same circular connector symbol. If 'Reconnect' is 'False', the flow proceeds to a rectangular process block labeled 'Outcome := Failure'. This is followed by a pentagonal output block labeled 'CCBS Call Delivery (Outcome)'. A dashed box labeled 'To VLR\_CCBS\_Recall\_Manager' is connected to this output block. Finally, the flow proceeds to the circular connector symbol. + +Flowchart for Procedure CCBS\_OCH\_Report\_Failure + +Figure 11.1.1.12: Procedure CCBS\_OCH\_Report\_Failure + +### 11.1.2 Processes and procedures in HLR + +Figure 11.1.2.1: Block diagram of HLRA processes + +Figure 11.1.2.2: Process HLRA\_Request\_Manager + +This process is in charge of the user interface procedures and queue handling, i.e. whether the request to processed is present in the queue or not. + +The process has three states, "Idle", "Operative" and "Operative Resuming". In the "Idle" state the queue is empty and the only actions to queue are creation of new request and interrogation of the queue. In other states activation, interrogation and deactivation procedures similarly, that is why they are grouped under "\*" state. + +Whenever the first request is created the process changes it's state to "Operative", in this state there are request(s) in the queue and none of them are suspended. + +When HLRA\_Request reports of suspension the process changes it's state to "Operative Resuming" and the HLRA\_Resume is started with correct trigger signal i.e. idle indication from MSC or recall end is waited. + +Only NET suspended request can be selected and resumed, USER type suspended requests remain as suspended until them are marked as NET suspended. This happens when idle indication is received from the MSC. + +The resuming process is paused if there is new suspended request with cause code Not reach i.e. The resuming starts again when idle condition is met again or there is a new recall with successful outcome i.e. the recall ends without Not Reach indication. + +The resuming process will be stopped, if there are no suspended requests in the queue any more. The process changes it's state to normal "Operative" or "Idle" state. + +Figure 11.1.2.3: Process HLRA\_Request + +This process is created during the activation of service and contains all related data. The process has five different states, "Wait\_For\_Answer", "Active", "Recall", "Suspended" and "Frozen". During its creation the process sends CCBS\_Request via SSAP interface to destination network B containing all call related data as well originating networks retention capabilities. + +In the "Wait\_For\_Answer" state process receives response from destination network which is further relayed to the HLRA\_Request\_Manager. In case of positive acknowledgement destination network returns info whether the retention is supported in both networks. + +In "Active" state process waits recall from destination network, however process can vanish if operation timer T3 expires or explicit deletion is received from the user or destination network. In case of deletion the process informs the queue. When the recall arrives the process transits to the "Recall" state. + +In the "Recall" state process waits the recall outcome, either positive or negative. Depending of the recall outcome the request can be deleted, retained or suspended. If the request is to be retained the process transits back to the "Active" state. If the request is suspended due to the T10 expiry, CCBS\_Busy condition or the MS is not reachable the process transits to the suspended state. + +If the request is deleted during "Recall" due SSAP\_Cancel, T3 expiry or explicit deletion the queue is updated immediately and the request changes it's state to "Recall Deleted" where it waits the recall to end. + +In the "Suspended" state actions the request can be resumed if the MS is known to be CCBS\_Idle or the request can be deleted due to the explicit deletion or timer T3 expiry. + +The request is placed in "Frozen" state whenever it receives Remote User Free indication from the destination network and the request can't be fulfilled due service interaction or lack of support in MSCVLR. The request shall indicate suspended back to the destination network and stay in the queue. If the service becomes later possible, the request will revert back "Active" state and indicate resumed to the destination network. + +Whenever the state of the process is changed, the new state is stored and the procedure CCBS\_Notify\_SS\_Invocation is called. + +Figure 11.1.2.4: Process HLRA\_Recall\_Manager + +This process has two different states, "Idle" and "CCBS\_Busy". + +The process let's only one individual process to be in recall state in a time and have a dialogue open to the MSC and it changes it's state to "CCBS\_Busy". In this state other requests are suspended immediately and marked as NET suspended with cause code = Busy. + +In "CCBS\_Busy" state the process waits recall reporting from the MSC. Possible inputs from the MSC are CCBS\_RUF\_Ack, CCBS\_RUF\_Error and CCBS\_Call\_Report. CCBS\_Call\_Report can be received if the subscriber has accepted the recall, otherwise the process changes it's state back to "Idle". If the process receives Query\_State request from the HLRA\_Resume during the recall the process informs the resume process whether a recall is being processed. + +Figure 11.1.2.5: Process HLRA\_Resume + +The process has four different states, "Idle", "Resume pending", "Wait For Selection" and "Resuming". The process is started when a request is suspended. For the first suspended request it is also set the trigger point i.e. when it is correct to send out selection request for resuming. Two triggers are provided, A\_Idle from the monitoring process and Recall\_End from the recall handling. If the trigger is set to A\_Idle the monitoring process is also started. + +When the process is started and correct trigger is set the process waits in the "Resume pending" state to receive a permission to start resuming. When the permission is received the process asks for the first NET request to resumed. If A\_Idle signal is received from the monitoring process the resuming process asks the queue manager to set all suspended requests as NET type in order to allow the selection. + +When there are no active suspended request in the queue any more the resuming process is stopped i.e. when the "Deleted" signal in the HLRA\_Request\_Manager is handled. + +Figure 11.1.2.6: Process HLRA\_Monitoring + +Monitoring process has two different states, "Idle" and "Monitoring". Receival of "A\_Query" signal transits the process to "Monitoring" state. In this state the process reports "Idle" condition to the resuming process and starts the monitoring again in the MSC if location update or restore data happens. + +Figure 11.1.2.7: Procedure HLRA\_CCBS\_Check\_Interactions + +This procedure checks whether the Remote User Free indication can be delivered to the MSCVLR or not. + +Figure 11.1.2.8: Procedure CCBS\_Notify\_SS\_Invocation + +This procedure is called by the process HLRA\_Request whenever there is a change of state. The procedure informs the gsmSCF of the state change if the SS-CSI applicable to CCBS is stored in the HLR. + +![UML Block Definition Diagram for HLRA_Processes. The diagram shows four internal process blocks: HLRA_Request_Manager(1,1), HLRA_Request(0,5), HLRA_Resume(1,1), and HLRA_Monitoring(1,1), and one external process block: HLRA_Recall_Manager(1,1). It defines interfaces and messages for interactions with VLRA, CCBS_Coordinator_HLR, and Destination network B.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +Block HLRA\_Processes 1(1) + +``` + +classDiagram + class HLRA_Request_Manager_1_1["HLRA_Request_Manager(1,1)"] + class HLRA_Request_0_5["HLRA_Request(0,5)"] + class HLRA_Resume_1_1["HLRA_Resume(1,1)"] + class HLRA_Monitoring_1_1["HLRA_Monitoring(1,1)"] + class HLRA_Recall_Manager_1_1["HLRA_Recall_Manager(1,1)"] + + HLRA_Request_Manager_1_1 --> HLRA_Request_0_5 + HLRA_Request_0_5 --> HLRA_Request_Manager_1_1 + HLRA_Request_0_5 --> HLRA_Resume_1_1 + HLRA_Resume_1_1 --> HLRA_Request_0_5 + HLRA_Resume_1_1 --> HLRA_Monitoring_1_1 + HLRA_Monitoring_1_1 --> HLRA_Resume_1_1 + HLRA_Monitoring_1_1 --> HLRA_Recall_Manager_1_1 + HLRA_Recall_Manager_1_1 --> HLRA_Resume_1_1 + +``` + +**Interfaces and Messages:** + +- VLRA (Left):** + - Outgoing from HLRA\_Request\_Manager(1,1): CCBS\_Request, Interrogate\_CCBS, Deactivate\_CCBS + - Incoming to HLRA\_Request\_Manager(1,1): CCBS\_Request\_Ack, CCBS\_Request\_Error, Interrogate\_CCBS\_Ack, Deactivate\_CCBS\_Ack + - Outgoing from HLRA\_Resume(1,1): Start\_Reporting\_Ack, Event\_Report + - Incoming to HLRA\_Resume(1,1): Start\_Reporting, Stop\_Reporting + - Outgoing from HLRA\_Recall\_Manager(1,1): CCBS\_RUF\_Ack, CCBS\_RUF\_Error + - Incoming to HLRA\_Recall\_Manager(1,1): CCBS\_RUF +- CCBS\_Coordinator\_HLR (Left):** + - Outgoing to HLRA\_Resume(1,1): A\_Idle + - Incoming from HLRA\_Resume(1,1): A\_Query, Stop\_Monitoring +- Destination network B (Right):** + - Outgoing to HLRA\_Request(0,5): CCBS\_Request, CCBS\_Suspend, CCBS\_Resume, CCBS\_Cancel + - Incoming from HLRA\_Request(0,5): CCBS\_Request\_Ack, CCBS\_Reject\_Request, Remote\_User\_Free, CCBS\_Cancel, CCBS\_END + +**Internal Message Flows:** + +- HLRA\_Request\_Manager(1,1) to HLRA\_Resume(1,1): Set\_All\_Active, Select\_Active\_Req, Select\_First\_Req +- HLRA\_Resume(1,1) to HLRA\_Request\_Manager(1,1): Set\_Trigger\_Recall\_End, Set\_Trigger\_A\_Idle, Reset\_Trigger\_A\_Idle, Select\_Resp, Not\_Selected, Stop\_Resume +- HLRA\_Resume(1,1) to HLRA\_Monitoring(1,1): Recall, Recall\_End +- HLRA\_Monitoring(1,1) to HLRA\_Resume(1,1): Query\_Status +- HLRA\_Recall\_Manager(1,1) to HLRA\_Resume(1,1): Recall + +UML Block Definition Diagram for HLRA\_Processes. The diagram shows four internal process blocks: HLRA\_Request\_Manager(1,1), HLRA\_Request(0,5), HLRA\_Resume(1,1), and HLRA\_Monitoring(1,1), and one external process block: HLRA\_Recall\_Manager(1,1). It defines interfaces and messages for interactions with VLRA, CCBS\_Coordinator\_HLR, and Destination network B. + +Figure 11.1.2.1: HLRA Processes + +NOTE: Figure 11.1.2.1 is one possible method of implementing queue processing in HLR A. Manufacturers are not constrained to follow the implementation given in figure 11.1.2.1. However, the external behaviour of HLR A shall appear to be the same. + +#### Description of above signals: + +#### Relation HLRA\_Request\_Manager and HLRA\_Request + +CCBS\_Request\_Ack signal is acknowledgement of a successful activation from the individual request to the queue manager. + +CCBS\_Request\_Error signal is sent if the destination networks queue is full or the destination networks queue size is set to zero. The individual request is deleted from the originating side. + +Suspend is used within HLRA\_Request and HLRA\_Request\_Manager. The queue shall update it's internal information. + +Delete is used within HLRA\_Request\_Manager and HLRA\_Request. The queue manager instructs the individual request the request to die. + +Deleted is used within HLRA\_Request\_Manager and HLRA\_Request. The individual request informs the queue of its expiry. + +Resume is used within HLRA\_Request\_Manager and HLRA\_Request. The individual request is resumed and it shall inform the destination network of the resumption. + +#### Relation HLRA\_Request\_Manager and HLRA\_Resume + +Set\_Trigger\_Recall\_End is used within the HLRA\_Request\_Manager and HLRA\_Resume. If resuming is not ongoing this signal set the resuming process to the "ResumePending" state and query is sent to the recall process. + +Set\_Trigger\_A\_Idle is used within the HLRA\_request\_manager and HLRA\_resume. If resuming is not ongoing this signal set the resuming process to the "ResumePending" state. In all cases this causes "A\_Query" signal to be sent. + +Reset\_Trigger\_A\_Idle is used within the HLRA\_request\_manager and HLRA\_resume. This signal sets the resuming process to the "ResumePending" state and causes "A\_Query" signal to be sent. + +Select\_Resp is used within the HLRA\_request\_manager and HLRA\_resume. This signal informs the resuming process to start T11. + +Not\_Selected is used within the HLRA\_request\_manager and HLRA\_resume. This signal informs the resuming process that the selection was not done and the process will transit to "ResumePending" state. + +Stop\_Resume is used within the HLRA\_request\_manager and HLRA\_resume. This signal informs the resuming process to stop it's actions and stop the monitoring also. + +Set\_All\_Active is used within the HLRA\_Resume and HLRA\_request\_manager. This signal informs the queue to set all suspended requests as NET suspended and later on they can be resumed. + +Select\_Active\_Req is used within the HLRA\_Resume and HLRA\_request\_manager. This signal informs the queue to select first NET suspended request to be resumed. If successful the request process will return "Select\_Resp", otherwise "Not\_Selected". + +Select\_First\_Req is used within the HLRA\_Resume and HLRA\_request\_manager. This signal informs the queue to select first suspended request to be resumed. If successful the request process will return "Select\_Resp", otherwise "Not\_Selected". + +#### Relation HLRA\_Recall\_Manager and HLRA\_Request + +Recall is used within HLRA\_Request and HLRA\_Recall\_Manager. It contains all call related data in order to form the CCBS\_Call. + +Completed is used within the HLRA\_Recall\_Manager and HLRA\_Request. It informs the request of successful CCBS\_Call and causes the request to vanish. + +Failure is used within the HLRA\_Recall\_Manager and HLRA\_Request. It informs the request of unsuccessful CCBS\_Call and causes the request to vanish. + +Busy is used within the HLRA\_Recall\_Manager and HLRA\_Request. It informs the request of unsuccessful CCBS\_Call and causes the request to vanish if retention is not supported. + +Suspend is used within HLRA\_Recall\_Manager and HLRA\_Request. The request shall change it's state and report the suspension to the queue manager. + +#### Relation HLRA\_Monitoring and HLRA\_Resume + +A\_Query is used within HLRA\_Resume and HLRA\_Monitoring. It instruct the HLRA\_Monitoring to start it's actions and return the idle condition when possible. + +A\_Idle is used within HLRA\_Monitoring and HLRA\_Resume. It informs the resuming process that the subscriber is now CCBS\_Idle and not CCBS\_Busy. + +Stop\_Monitoring is used with HLRA\_Resume and HLRA\_Monitoring. It instructs the monitoring process to stop it's actions and stop the monitoring from VLR also. + +Location\_Update/Restore\_Data events are tracked and external reporting is started again. + +![State transition diagram for Process HLRA_RequestManager(1,1).](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +Process HLRA\_RequestManager(1,1) 1(10) + +The diagram illustrates the state transitions for the HLRA\_RequestManager process. It consists of two main state machines. The top state machine starts at an initial state (oval) and transitions to an IDLE state (oval). From IDLE, it receives a CCBS\_Request (input from MSCVLR), checks parameters (see GSM 03.18), and evaluates the result. If the result passes, it sends an HLRA\_Request, updates the queue, and transitions to an OPERATIVE state. If the result fails, it sets an error response and sends a CCBS\_Request\_Error back to the MSCVLR, returning to the IDLE state. The bottom state machine starts at an IDLE state, receives a Deactivate\_CCBS request from the MSC\_VLR, checks parameters (see GSM 03.18), and evaluates the result. If the result passes, it checks if CCBS is provisioned. If not provisioned, it sets a 'Not Provisioned' result and sends a Deactivate\_CCBS\_Ack to the MSC\_VLR. If provisioned, it sets a 'Success' result and sends a Deactivate\_CCBS\_Ack to the MSC\_VLR. Both acks lead back to the IDLE state. If the initial result fails, it sets a negative response and sends a Deactivate\_CCBS\_Error to the MSC\_VLR, returning to the IDLE state. Annotations include 'There is not any request in the IDLE state' for the top IDLE state, 'From MSCVLR' for the top CCBS\_Request, 'See GSM 03.18' for parameter checks, 'To MSCVLR' for outgoing messages, and 'From MSC\_VLR' for the Deactivate\_CCBS input. + +``` +stateDiagram-v2 + [*] --> IDLE1 : IDLE + IDLE1 --> CCBS_Request1 : CCBS_Request (From MSCVLR) + CCBS_Request1 --> Check_Parameters1 : Check Parameters (See GSM 03.18) + Check_Parameters1 --> Result1 : Result + Result1 -- Pass --> HLRA_Request : HLRA_Request + HLRA_Request --> Update_the_queue : Update the queue + Update_the_queue --> OPERATIVE : OPERATIVE + Result1 -- Fail --> Error1 : Error := Negative response + Error1 --> CCBS_Request_Error1 : CCBS_Request_Error(Error) (To MSCVLR) + CCBS_Request_Error1 --> IDLE1 : IDLE + + IDLE2 : IDLE --> Deactivate_CCBS : Deactivate_CCBS (From MSC_VLR) + Deactivate_CCBS --> Check_Parameters2 : Check Parameters (See GSM 03.18) + Check_Parameters2 --> Result2 : Result + Result2 -- Pass --> CCBS_provisioned : CCBS provisioned + CCBS_provisioned -- No --> Deactivate_Result1 : Deactivate_Result := Not Provisioned + CCBS_provisioned -- Yes --> Deactivate_Result2 : Deactivate_Result := Success + Deactivate_Result1 --> Deactivate_CCBS_Ack1 : Deactivate_CCBS_Ack(Deactivate_Result) (To MSC_VLR) + Deactivate_Result2 --> Deactivate_CCBS_Ack1 + Deactivate_CCBS_Ack1 --> IDLE2 : IDLE + Result2 -- Fail --> Error2 : Error := Negative response + Error2 --> Deactivate_CCBS_Error : Deactivate_CCBS_Error(Error) (To MSCVLR) + Deactivate_CCBS_Error --> IDLE2 : IDLE +``` + +State transition diagram for Process HLRA\_RequestManager(1,1). + +Figure 11.1.2.2: Process HLRA\_Request\_Manager (sheet 1 of 10) + +![Flowchart for Process HLRA_RequestManager(1,1). The process starts with an entry point, followed by 'Interrogate_CCBS' (From MSC_VLR), 'Check_Parameters' (See GSM 03.18), and a 'Result' decision. If 'Fail', it goes to 'Error := Negative response' and then 'Interrogate_CCBS_Ack (Error)' (To MSC_VLR). If 'Pass', it goes to 'CCBS provisioned' decision. If 'No', it goes to 'Result := Not_Provisioned' and then 'Interrogate_CCBS_Ack (Result)' (To MSC_VLR). If 'Yes', it goes to 'Queue empty' decision. If 'Yes', it goes to 'Result := No Entries' and then 'Interrogate_CCBS_Ack (Result)' (To MSC_VLR). If 'No', it goes to 'Query the queue := List', 'Result := List', and then 'Interrogate_CCBS_Ack (Result)' (To MSC_VLR). All three 'Interrogate_CCBS_Ack' paths merge at a final junction point.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +Process HLRA\_RequestManager(1,1) + +2(10) + +``` +graph TD; Entry([*]) --> Interrogate_CCBS{Interrogate_CCBS}; Note1[From MSC_VLR] -.-> Interrogate_CCBS; Interrogate_CCBS --> Check_Parameters[Check_Parameters]; Note2[See GSM 03.18] -.-> Check_Parameters; Check_Parameters --> Result{Result}; Result -- Fail --> Error[Error := Negative response]; Error --> Interrogate_CCBS_Ack_Error{Interrogate_CCBS_Ack (Error)}; Note3[To MSC_VLR] -.-> Interrogate_CCBS_Ack_Error; Interrogate_CCBS_Ack_Error --> Exit1([*]); Result -- Pass --> CCBS_provisioned{CCBS provisioned}; CCBS_provisioned -- No --> Not_Provisioned[Result := Not_Provisioned]; Not_Provisioned --> Interrogate_CCBS_Ack_Result1{Interrogate_CCBS_Ack (Result)}; Note4[To MSC_VLR] -.-> Interrogate_CCBS_Ack_Result1; CCBS_provisioned -- Yes --> Queue_empty{Queue empty}; Queue_empty -- Yes --> No_Entries[Result := No Entries]; No_Entries --> Interrogate_CCBS_Ack_Result2{Interrogate_CCBS_Ack (Result)}; Note5[To MSC_VLR] -.-> Interrogate_CCBS_Ack_Result2; Queue_empty -- No --> Query_queue[Query the queue := List]; Query_queue --> Result_List[Result := List]; Result_List --> Interrogate_CCBS_Ack_Result3{Interrogate_CCBS_Ack (Result)}; Note6[To MSC_VLR] -.-> Interrogate_CCBS_Ack_Result3; Interrogate_CCBS_Ack_Result1 --> Merge(( )); Interrogate_CCBS_Ack_Result2 --> Merge; Interrogate_CCBS_Ack_Result3 --> Merge; Merge --> Exit2([*]); +``` + +Flowchart for Process HLRA\_RequestManager(1,1). The process starts with an entry point, followed by 'Interrogate\_CCBS' (From MSC\_VLR), 'Check\_Parameters' (See GSM 03.18), and a 'Result' decision. If 'Fail', it goes to 'Error := Negative response' and then 'Interrogate\_CCBS\_Ack (Error)' (To MSC\_VLR). If 'Pass', it goes to 'CCBS provisioned' decision. If 'No', it goes to 'Result := Not\_Provisioned' and then 'Interrogate\_CCBS\_Ack (Result)' (To MSC\_VLR). If 'Yes', it goes to 'Queue empty' decision. If 'Yes', it goes to 'Result := No Entries' and then 'Interrogate\_CCBS\_Ack (Result)' (To MSC\_VLR). If 'No', it goes to 'Query the queue := List', 'Result := List', and then 'Interrogate\_CCBS\_Ack (Result)' (To MSC\_VLR). All three 'Interrogate\_CCBS\_Ack' paths merge at a final junction point. + +Figure 11.1.2.2: Process HLRA\_Request\_Manager (sheet 2 of 10) + +![State transition diagram for Process HLRA_RequestManager(1,1). The diagram shows transitions between states based on messages from HLRA and MSC_VLR. It starts at an initial state *(IDLE) and branches into two main paths: one for successful requests (CCBS_Request_Ack) and one for errors (CCBS_Request_Error). The error path includes a queue update and a decision point 'Queue empty'.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +Process HLRA\_RequestManager(1,1) + +3(10) + +``` +stateDiagram-v2 + [*] --> *(IDLE) + state "*(IDLE)" as *(IDLE) + state "CCBS_Request_Ack" as CCBS_Request_Ack + state "CCBS_Request_Error(Error)" as CCBS_Request_Error + state "Update the queue" as Update the queue + state "Queue empty" as Queue empty + state "There is at least one request in the queue" as There is at least one request in the queue + state "-" as - + state "IDLE" as IDLE + + *(IDLE) --> CCBS_Request_Ack + *(IDLE) --> CCBS_Request_Error + CCBS_Request_Ack --> CCBS_Request_Ack + CCBS_Request_Error --> CCBS_Request_Error + CCBS_Request_Ack --> Queue empty + CCBS_Request_Error --> Update the queue + Update the queue --> Queue empty + Queue empty --> CCBS_Request_Ack : No + Queue empty --> IDLE : Yes + There is at least one request in the queue --> - + - --> Queue empty +``` + +The diagram illustrates the state transitions for the Process HLRA\_RequestManager(1,1). It begins with an initial state **\*(IDLE)**. From this state, two transitions are possible: **CCBS\_Request\_Ack** (receiving a request from HLRA and sending an acknowledgment to MSC\_VLR) and **CCBS\_Request\_Error(Error)** (receiving an error from HLRA and sending an error to MSC\_VLR). Both transitions lead to self-loops on their respective states. The **CCBS\_Request\_Ack** state also leads to a decision point **Queue empty**. If the queue is not empty (**No**), it loops back to the **CCBS\_Request\_Ack** state. If the queue is empty (**Yes**), it transitions to the **IDLE** state. The **CCBS\_Request\_Error(Error)** state leads to an **Update the queue** state, which then leads to the **Queue empty** decision point. If the queue is not empty (**No**), it loops back to the **CCBS\_Request\_Ack** state. If the queue is empty (**Yes**), it transitions to the **IDLE** state. A note indicates that if there is at least one request in the queue, it leads to a state **-**, which then loops back to the **Queue empty** decision point. + +State transition diagram for Process HLRA\_RequestManager(1,1). The diagram shows transitions between states based on messages from HLRA and MSC\_VLR. It starts at an initial state \*(IDLE) and branches into two main paths: one for successful requests (CCBS\_Request\_Ack) and one for errors (CCBS\_Request\_Error). The error path includes a queue update and a decision point 'Queue empty'. + +Figure 11.1.2.2: Process HLRA\_Request\_Manager (sheet 3 of 10) + +![Flowchart for Process HLRA_RequestManager(1,1). The process starts at an initial state '(IDLE)', receives a 'CCBS_Request' from 'MSCVLR', checks parameters (referencing GSM 03.18), and then evaluates the 'Result'. If 'Fail', it sets an error and sends a 'Negative response'. If 'Pass', it checks if the 'Queue full'. If 'Yes', it sets a 'Short_Term_Denial' error. If 'No', it checks if it's an 'Identical request'. If 'Yes', it deletes the existing entry and updates the queue. Finally, it sends an 'HLRA_Request', updates the queue, and reaches the end state '-'. Error states lead to a 'CCBS_Request_Error(Error)' message to 'MSCVLR'.](5801c19431e76330430e92a598cc7a16_img.jpg) + +Process HLRA\_RequestManager(1,1) + +4(10) + +``` +graph TD; Start([*(IDLE)]) --> Request{CCBS_Request}; FromMSCVLR[From MSCVLR] -.-> Request; Request --> Check[Check Parameters]; SeeGSM[See GSM 03.18] -.-> Check; Check --> Result{Result}; Result -- Fail --> ErrorNeg[Error := Negative response]; Result -- Pass --> QueueFull{Queue full}; QueueFull -- Yes --> ErrorShort[Error := Short_Term_Denial]; QueueFull -- No --> Identical{Identical request}; Identical -- Yes --> Delete[/Delete/]; NoteDelete[To HLRA_Request. The existing entry should be deleted] -.-> Delete; Delete --> UpdateQ1[Update the queue]; Identical -- No --> HLRA[HLRA_Request]; UpdateQ1 --> HLRA; HLRA --> UpdateQ2[Update the queue]; UpdateQ2 --> End([-]); ErrorNeg --> ErrorOut{CCBS_Request_Error(Error)}; ErrorShort --> ErrorOut; ErrorOut -- ToMSCVLR[To MSCVLR] -.-> End; +``` + +Flowchart for Process HLRA\_RequestManager(1,1). The process starts at an initial state '(IDLE)', receives a 'CCBS\_Request' from 'MSCVLR', checks parameters (referencing GSM 03.18), and then evaluates the 'Result'. If 'Fail', it sets an error and sends a 'Negative response'. If 'Pass', it checks if the 'Queue full'. If 'Yes', it sets a 'Short\_Term\_Denial' error. If 'No', it checks if it's an 'Identical request'. If 'Yes', it deletes the existing entry and updates the queue. Finally, it sends an 'HLRA\_Request', updates the queue, and reaches the end state '-'. Error states lead to a 'CCBS\_Request\_Error(Error)' message to 'MSCVLR'. + +Figure 11.1.2.2: Process HLRA\_Request\_Manager (sheet 4 of 10) + +![State transition diagram for Process HLRA_RequestManager(1,1).](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +Process HLRA\_RequestManager(1,1) 5(10) + +``` +stateDiagram-v2 + [*] --> Suspend + Suspend --> Type + Type --> Mark_USER: USER + Type --> Mark_NET: NET + Mark_USER --> Set_Trigger_A + Mark_NET --> Sus_Cause + Sus_Cause --> Set_Trigger_A: Not_Reach + Sus_Cause --> Set_Trigger_Recall_End: ELSE + Set_Trigger_A --> OPERATIVE_RESUMING + Set_Trigger_Recall_End --> OPERATIVE_RESUMING +``` + +The diagram illustrates the state transitions for the HLRA\_RequestManager process. It begins at an initial state **\*(IDLE)**, which transitions to a **Suspend** state (Type, Sus\_Cause). A note indicates this is **From individual HLRA\_Request**. The **Suspend** state leads to a **Type** decision diamond. From **Type**, the **USER** path leads to **Mark request USER suspended**, with a note that **USER suspended requests can't be selected until MSCVLR reports idle condition**. The **NET** path leads to **Mark request NET suspended**, with a note that **NET suspended requests can be selected when Idle condition is met or Recall\_Manager reports Recall\_End**. Both **Mark** states lead to a **Set\_Trigger\_A Idle (Sus\_Cause)** state. The **USER** path has a note **To HLRA\_Resume NOTE: Request can resumed when idle condition is met**. The **NET** path from **Mark request NET suspended** leads to a **Sus\_Cause** decision diamond. From **Sus\_Cause**, the **Not\_Reach** path leads to **Reset\_Trigger\_A Idle (Sus\_Cause)**, with a note **To HLRA\_Resume NOTE: Resuming is paused until idle condition is met**. The **ELSE** path from **Sus\_Cause** leads to **Set\_Trigger\_Recall\_End**, with a note **To HLRA\_Resume NOTE: Resuming can be started when recall is ended**. Both **Set\_Trigger\_A Idle (Sus\_Cause)** and **Set\_Trigger\_Recall\_End** lead to the **OPERATIVE\_RESUMING** state, which has a note **In this state there is at least one suspended requests**. + +State transition diagram for Process HLRA\_RequestManager(1,1). + +Figure 11.1.2.2: Process HLRA\_Request\_Manager (sheet 5 of 10) + +![Flowchart for Process HLRA_RequestManager(1,1). The process starts at OPERATIVE, receives a Deactivate_CCBS message from MSC_VLR, checks parameters, and then evaluates the result. If it passes, it checks if all requests can be deleted. If not, it checks if the request exists; if yes, it deletes it individually, otherwise it deletes all requests. Both deletion paths lead to Result := Success. If the result fails, it sets an error and sends a Deactivate_CCBS Error message to MSC_VLR before returning to OPERATIVE. After success, it sends a Deactivate_CCBS_Ack to MSC_VLR, updates the queue, and checks if it's empty. If empty, it goes to IDLE; otherwise, it returns to OPERATIVE.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +Process HLRA\_RequestManager(1,1) + +6(10) + +``` +graph TD; Start([OPERATIVE]) --> In{Deactivate_CCBS}; In -.-> FromMSC[From MSC_VLR]; In --> Check[Check_Parameters]; Check --> Result{Result}; Result -- Pass --> DeleteAll{Delete all requests}; Result -- Fail --> Error[Error := Negative response]; Error --> OutError{Deactivate_CCBS Error(Error)}; OutError -.-> ToMSC[To MSC_VLR]; OutError --> EndError([OPERATIVE]); DeleteAll -- Yes --> DeleteAllPath[Delete]; DeleteAll -- No --> RequestExists{Request exists}; RequestExists -- Yes --> DeletePath[Delete]; RequestExists -- No --> Merge(( )); DeletePath --> DeleteAllPath; DeletePath -.-> Note[To HLRA_Request NOTE: To all individual requests]; DeletePath --> Merge; DeletePath -.-> ToIndividual[To individual HLRA_Request]; Merge --> Success[Result := Success]; Success --> Ack{Deactivate_CCBS_Ack(Result)}; Ack -.-> ToMSC; Ack --> Update[Update the queue]; Update --> QueueEmpty{Queue empty}; QueueEmpty -- Yes --> Idle([IDLE]); QueueEmpty -- No --> EndOperative([OPERATIVE]); +``` + +Flowchart for Process HLRA\_RequestManager(1,1). The process starts at OPERATIVE, receives a Deactivate\_CCBS message from MSC\_VLR, checks parameters, and then evaluates the result. If it passes, it checks if all requests can be deleted. If not, it checks if the request exists; if yes, it deletes it individually, otherwise it deletes all requests. Both deletion paths lead to Result := Success. If the result fails, it sets an error and sends a Deactivate\_CCBS Error message to MSC\_VLR before returning to OPERATIVE. After success, it sends a Deactivate\_CCBS\_Ack to MSC\_VLR, updates the queue, and checks if it's empty. If empty, it goes to IDLE; otherwise, it returns to OPERATIVE. + +Figure 11.1.2.2: Process HLRA\_Request\_Manager (sheet 6 of 10) + +![SDL diagram for Process HLRA_RequestManager showing state transitions from OPERATIVE to IDLE based on queue status.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +Process HLRA\_RequestManager(1,1) + +7(10) + +``` + +graph TD + Start([OPERATIVE]) --> Input[/Deleted/] + Input -.-> From[From individual +HLRA_Request] + Input --> Action[Update the +request queue] + Action --> Decision{Queue +empty} + Decision -- No --> End1([OPERATIVE]) + Decision -- Yes --> End2([IDLE]) + +``` + +SDL diagram for Process HLRA\_RequestManager showing state transitions from OPERATIVE to IDLE based on queue status. + +**Figure 11.1.2.2: Process HLRA\_Request\_Manager (sheet 7 of 10)** + +![Flowchart for Process HLRA_RequestManager(1,1). The process starts at OPERATIVE RESUMING, then Deactivate_CCBS (From MSC_VLR), Check_Parameters (See GSM 03.18). A Result decision follows. If Fail, Error := Negative response, Deactivate_CCBS Error(Error) (To MSCVLR), and back to OPERATIVE RESUMING. If Pass, a Delete all requests decision follows. If Yes, Delete (To HLRA_Request NOTE: To all individual requests). If No, a Request exists decision follows. If Yes, Delete (To individual HLRA_Request). Both Delete paths merge at a junction. Then Result := Success, Deactivate_CCBS Ack(Result) (To MSC_VLR), Update the queue, and Any suspended requests decision. If Yes, back to OPERATIVE RESUMING. If No, Stop_Resume (To HLRA_Resume) and Queue empty decision. If No, back to OPERATIVE. If Yes, IDLE.](5e9af8986a5845504f251d3079da8078_img.jpg) + +Process HLRA\_RequestManager(1,1) 8(10) + +``` +graph TD; Start([OPERATIVE RESUMING]) --> Deact1{Deactivate_CCBS}; Deact1 -.-> FromMSC[From MSC_VLR]; Deact1 --> Check[Check_Parameters]; Check -.-> GSM[See GSM 03.18]; Check --> Result{Result}; Result -- Fail --> Error[Error := Negative response]; Error --> Deact2{Deactivate_CCBS Error(Error)}; Deact2 -.-> ToMSC[To MSCVLR]; Deact2 --> Resum1([OPERATIVE RESUMING]); Result -- Pass --> DeleteAll{Delete all requests}; DeleteAll -- Yes --> Delete1{Delete}; Delete1 -.-> ToHLRA[To HLRA_Request NOTE: To all individual requests]; DeleteAll -- No --> RequestExists{Request exists}; RequestExists -- Yes --> Delete2{Delete}; Delete2 -.-> ToIndiv[To individual HLRA_Request]; RequestExists -- No --> Junction(( )); Delete1 --> Junction; Delete2 --> Junction; Junction --> Success[Result := Success]; Success --> Deact3{Deactivate_CCBS Ack(Result)}; Deact3 -.-> ToMSC2[To MSC_VLR]; Deact3 --> Update[Update the queue]; Update --> AnySuspended{Any suspended requests}; AnySuspended -- Yes --> Resum2([OPERATIVE RESUMING]); AnySuspended -- No --> Stop[Stop_Resume]; Stop -.-> ToHLRA2[To HLRA_Resume]; Stop --> QueueEmpty{Queue empty}; QueueEmpty -- No --> Operative([OPERATIVE]); QueueEmpty -- Yes --> Idle([IDLE]); +``` + +Flowchart for Process HLRA\_RequestManager(1,1). The process starts at OPERATIVE RESUMING, then Deactivate\_CCBS (From MSC\_VLR), Check\_Parameters (See GSM 03.18). A Result decision follows. If Fail, Error := Negative response, Deactivate\_CCBS Error(Error) (To MSCVLR), and back to OPERATIVE RESUMING. If Pass, a Delete all requests decision follows. If Yes, Delete (To HLRA\_Request NOTE: To all individual requests). If No, a Request exists decision follows. If Yes, Delete (To individual HLRA\_Request). Both Delete paths merge at a junction. Then Result := Success, Deactivate\_CCBS Ack(Result) (To MSC\_VLR), Update the queue, and Any suspended requests decision. If Yes, back to OPERATIVE RESUMING. If No, Stop\_Resume (To HLRA\_Resume) and Queue empty decision. If No, back to OPERATIVE. If Yes, IDLE. + +Figure 11.1.2.2: Process HLRA\_Request\_Manager (sheet 8 of 10) + +![Flowchart for Process HLRA_RequestManager(1,1). The process starts at OPERATIVE RESUMING, proceeds to Deleted (From individual HLRA_Request), then Update the request queue. A decision 'Any suspended requests' follows. If Yes, it returns to OPERATIVE RESUMING. If No, it goes to Stop_Resume (To HLRA_Resume), then a decision 'Queue empty'. If Queue empty is No, it goes to OPERATIVE. If Queue empty is Yes, it goes to IDLE.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +Process HLRA\_RequestManager(1,1) + +9(10) + +``` +graph TD; A([OPERATIVE RESUMING]) --> B[/Deleted +From individual HLRA_Request/]; B --> C[Update the request queue]; C --> D{Any suspended requests}; D -- Yes --> A; D -- No --> E[/Stop_Resume +To HLRA_Resume/]; E --> F{Queue empty}; F -- No --> G([OPERATIVE]); F -- Yes --> H([IDLE]); +``` + +Flowchart for Process HLRA\_RequestManager(1,1). The process starts at OPERATIVE RESUMING, proceeds to Deleted (From individual HLRA\_Request), then Update the request queue. A decision 'Any suspended requests' follows. If Yes, it returns to OPERATIVE RESUMING. If No, it goes to Stop\_Resume (To HLRA\_Resume), then a decision 'Queue empty'. If Queue empty is No, it goes to OPERATIVE. If Queue empty is Yes, it goes to IDLE. + +Figure 11.1.2.2: Process HLRA\_Request\_Manager (sheet 9 of 10) + +![Flowchart for Process HLRA_RequestManager(1,1). The process starts at OPERATIVE RESUMING and branches into two parallel paths. The left path involves Set_All_Active, marking USER suspended requests as NET suspended, and then checking for any NET suspended requests. The right path involves Select_Active_Req, Select_First_Req, and marking USER suspended requests as NET suspended. Both paths converge to a decision diamond 'Any NET suspended request'. If Yes, it proceeds to Select the first NET suspended request, Update queue, and Resume. If No, it proceeds to 'Any suspended requests'. From 'Any suspended requests', if Yes, it goes to Not_Selected and back to OPERATIVE RESUMING. If No, it goes to Stop_Resume and OPERATIVE. From 'Resume', it checks 'Any more suspended requests'. If Yes, it goes to Select_Resp and back to OPERATIVE RESUMING. If No, it goes to OPERATIVE. Various notes and messages are associated with the steps.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +Process HLRA\_RequestManager(1,1) 10(10) + +``` +graph TD; Start([OPERATIVE RESUMING]) --> SetAll[Set_All_Active]; Start --> SelectActive[Select_Active_Req]; Start --> SelectFirst[Select_First_Req]; SetAll --> MarkUser1[Mark all USER suspended requests as NET suspended]; SelectActive --> MarkUser2[Mark all USER suspended requests as NET suspended]; SelectFirst --> MarkUser2; MarkUser1 --> AnyNET[Any NET suspended request]; MarkUser2 --> AnyNET; AnyNET -- Yes --> SelectFirstNET[Select the first NET suspended request]; SelectFirstNET --> UpdateQueue[Update queue, remove suspend marking for request]; UpdateQueue --> Resume[Resume]; AnyNET -- No --> AnySuspended[Any suspended requests]; Resume --> AnyMore[Any more suspended requests]; AnyMore -- Yes --> SelectResp[Select_Resp]; AnyMore -- No --> StopResume[Stop_Resume]; SelectResp --> ToHLRA1[To HLRA_Resume NOTE: T11 is started]; StopResume --> ToHLRA2[To HLRA_Resume]; AnySuspended -- Yes --> NotSelected[Not Selected]; AnySuspended -- No --> StopResume; NotSelected --> ToHLRA3[To HLRA_Resume NOTE: T11 is not started, Resume waits A_Idle]; ToHLRA1 --> EndResuming1([OPERATIVE RESUMING]); StopResume --> EndOperative([OPERATIVE]); ToHLRA3 --> EndResuming2([OPERATIVE RESUMING]); +``` + +From HLRA\_Resume + +From HLRA\_Resume + +From HLRA\_Resume + +From HLRA\_Resume + +From HLRA\_Resume + +To individual HLRA\_Request + +To HLRA\_Resume NOTE: T11 is started + +To HLRA\_Resume + +To HLRA\_Resume NOTE: T11 is not started, Resume waits A\_Idle + +Flowchart for Process HLRA\_RequestManager(1,1). The process starts at OPERATIVE RESUMING and branches into two parallel paths. The left path involves Set\_All\_Active, marking USER suspended requests as NET suspended, and then checking for any NET suspended requests. The right path involves Select\_Active\_Req, Select\_First\_Req, and marking USER suspended requests as NET suspended. Both paths converge to a decision diamond 'Any NET suspended request'. If Yes, it proceeds to Select the first NET suspended request, Update queue, and Resume. If No, it proceeds to 'Any suspended requests'. From 'Any suspended requests', if Yes, it goes to Not\_Selected and back to OPERATIVE RESUMING. If No, it goes to Stop\_Resume and OPERATIVE. From 'Resume', it checks 'Any more suspended requests'. If Yes, it goes to Select\_Resp and back to OPERATIVE RESUMING. If No, it goes to OPERATIVE. Various notes and messages are associated with the steps. + +Figure 11.1.2.2: Process HLRA\_Request\_Manager (sheet 10 of 10) + +![Flowchart for Process HLRA_Request. It starts with a decision 'Retain supported'. If 'Yes', it sends 'CCBS_Request (Retain_Supported)' to destination network B (with a note that it contains originating network's retain capabilities) and then enters 'WAIT_FOR_ANSWER'. If 'No', it sends 'CCBS_Request' to destination network B (with a note that it contains no retain support info) and then enters 'WAIT_FOR_ANSWER'. From 'WAIT_FOR_ANSWER', it receives either 'CCBS_Request_Ack(Retain_supported)' or 'CCBS_Reject_Request(Cause)'. The 'Ack' path leads to 'Store received Retain_supported value', 'Start T3', 'CCBS_Request_Ack' (sent to HLRA_Request_Manager), 'State := Request', 'CCBS_Notify_SS_Invocation', and finally 'ACTIVE'. The 'Reject' path leads to 'Error := Cause', 'CCBS_Request_Error(Error)' (sent to HLRA_Request_Manager), and an error termination symbol.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +### Process HLRA\_Request + +1(5) + +``` +graph TD; Start([ ]) --> Retain{Retain supported}; Retain -- Yes --> CCBS_Retain[CCBS_Request (Retain_Supported)]; Retain -- No --> CCBS_NoRetain[CCBS_Request]; CCBS_Retain --> Note1[To destination network B. NOTE: This signal contains also info of originating network's retain capabilities.]; CCBS_NoRetain --> Note2[To destination network B. NOTE: This signal does not contain any information of the retain support.]; Note1 --> WAIT1((WAIT_FOR_ANSWER)); Note2 --> WAIT1; WAIT1 --> WAIT2((WAIT_FOR_ANSWER)); WAIT2 --> Ack{CCBS_Request_Ack(Retain_supported)}; WAIT2 --> Reject{CCBS_Reject_Request(Cause)}; Ack --> Store[Store received Retain_supported value]; Store --> StartT3[Start T3]; StartT3 --> CCBS_Ack[CCBS_Request_Ack]; CCBS_Ack --> Note3[To HLRA_Request_Manager]; CCBS_Ack --> State[State := Request]; State --> Notify[CCBS_Notify_SS_Invocation]; Notify --> ACTIVE([ACTIVE]); Reject --> Error[Error := Cause]; Error --> CCBS_Error[CCBS_Request_Error(Error)]; CCBS_Error --> Note4[To HLRA_Request_Manager]; CCBS_Error --> ErrorEnd((X)); +``` + +**FPAR** +All the data in the original CCBS\_Request + +**Retain supported** + +**Yes** + +**No** + +**CCBS\_Request (Retain\_Supported)** + +**CCBS\_Request** + +To destination network B. NOTE: This signal contains also info of originating network's retain capabilities. + +To destination network B. NOTE: This signal does not contain any information of the retain support. + +**WAIT\_FOR\_ANSWER** + +**WAIT\_FOR\_ANSWER** + +**CCBS\_Request\_Ack(Retain\_supported)** + +**CCBS\_Reject\_Request(Cause)** + +From destination network B. NOTE: Retain\_supported parameter contains info whether retain is supported for this request all along the network path. The parameter is received only if retain supported was send in the CCBS\_Request signal. + +**Store received Retain\_supported value** + +**Start T3** + +**CCBS\_Request\_Ack** + +To HLRA\_Request\_Manager + +**State := Request** + +**CCBS\_Notify\_SS\_Invocation** + +**ACTIVE** + +**Error := Cause** + +**CCBS\_Request\_Error(Error)** + +To HLRA\_Request\_Manager + +Flowchart for Process HLRA\_Request. It starts with a decision 'Retain supported'. If 'Yes', it sends 'CCBS\_Request (Retain\_Supported)' to destination network B (with a note that it contains originating network's retain capabilities) and then enters 'WAIT\_FOR\_ANSWER'. If 'No', it sends 'CCBS\_Request' to destination network B (with a note that it contains no retain support info) and then enters 'WAIT\_FOR\_ANSWER'. From 'WAIT\_FOR\_ANSWER', it receives either 'CCBS\_Request\_Ack(Retain\_supported)' or 'CCBS\_Reject\_Request(Cause)'. The 'Ack' path leads to 'Store received Retain\_supported value', 'Start T3', 'CCBS\_Request\_Ack' (sent to HLRA\_Request\_Manager), 'State := Request', 'CCBS\_Notify\_SS\_Invocation', and finally 'ACTIVE'. The 'Reject' path leads to 'Error := Cause', 'CCBS\_Request\_Error(Error)' (sent to HLRA\_Request\_Manager), and an error termination symbol. + +Figure 11.1.2.3: Process HLRA\_Request (sheet 1 of 5) + +![State transition diagram for Process HLRA_Request. The process starts in the ACTIVE state. Transitions include Remote_User_Free, T3 Expiry, CCBS_Cancel, and Delete. Remote_User_Free leads to HLRA_CCBS_CHECK_INTERACTIONS. T3 Expiry leads to Cause := T3-Timeout, then CCBS_Cancel(Cause) to destination network B, then Deleted to HLRA_Request_Manager. CCBS_Cancel leads to Deleted to HLRA_Request_Manager. Delete leads to CCBS_Cancel to destination network B. All three Deleted states lead to connector 1. Connector 1 leads to State := Deleted, then CCBS_Notify_SS_Invocation. Connector 2 leads to CCBS_Suspend to destination network B. HLRA_CCBS_CHECK_INTERACTIONS leads to Result. Result Pass leads to Recall to HLRA_Recall_Manager, then State := Recall, then CCBS_Notify_SS_Invocation, then RECALL. Result Fail leads to CCBS_Suspend to destination network B, then State := Frozen, then CCBS_Notify_SS_Invocation, then FROZEN.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +### Process HLRA\_Request + +2(5) + +``` +stateDiagram-v2 + [*] --> ACTIVE + ACTIVE --> Remote_User_Free + ACTIVE --> T3_Expiry + ACTIVE --> CCBS_Cancel + ACTIVE --> Delete + + Remote_User_Free --> HLRA_CCBS_CHECK_INTERACTIONS + T3_Expiry --> Cause_T3_Timeout: Cause := T3-Timeout + Cause_T3_Timeout --> CCBS_Cancel_Cause: CCBS_Cancel(Cause) + CCBS_Cancel_Cause --> Deleted_HLRA_Manager + CCBS_Cancel --> Deleted_HLRA_Manager + Delete --> CCBS_Cancel_Dest_Net_B: To destination network B + Deleted_HLRA_Manager --> Connector_1: 1 + CCBS_Cancel_Dest_Net_B --> Connector_1 + Connector_1 --> State_Deleted: State := Deleted + State_Deleted --> CCBS_Notify_SS_Invocation_Deleted + CCBS_Notify_SS_Invocation_Deleted --> [*] + + HLRA_CCBS_CHECK_INTERACTIONS --> Result + Result -- Pass --> Recall + Recall --> State_Recall: State := Recall + State_Recall --> CCBS_Notify_SS_Invocation_Recall + CCBS_Notify_SS_Invocation_Recall --> RECALL + + Result -- Fail --> CCBS_Suspend_Fail + CCBS_Suspend_Fail --> State_Frozen: State := Frozen + State_Frozen --> CCBS_Notify_SS_Invocation_Frozen + CCBS_Notify_SS_Invocation_Frozen --> FROZEN + + CCBS_Cancel_Cause --> Deleted_HLRA_Manager + Deleted_HLRA_Manager --> Connector_1 + CCBS_Cancel_Dest_Net_B --> Connector_1 + Connector_1 --> State_Deleted + State_Deleted --> CCBS_Notify_SS_Invocation_Deleted + CCBS_Notify_SS_Invocation_Deleted --> [*] + + CCBS_Cancel_Cause --> CCBS_Suspend_Fail + CCBS_Suspend_Fail --> State_Frozen + State_Frozen --> CCBS_Notify_SS_Invocation_Frozen + CCBS_Notify_SS_Invocation_Frozen --> FROZEN +``` + +State transition diagram for Process HLRA\_Request. The process starts in the ACTIVE state. Transitions include Remote\_User\_Free, T3 Expiry, CCBS\_Cancel, and Delete. Remote\_User\_Free leads to HLRA\_CCBS\_CHECK\_INTERACTIONS. T3 Expiry leads to Cause := T3-Timeout, then CCBS\_Cancel(Cause) to destination network B, then Deleted to HLRA\_Request\_Manager. CCBS\_Cancel leads to Deleted to HLRA\_Request\_Manager. Delete leads to CCBS\_Cancel to destination network B. All three Deleted states lead to connector 1. Connector 1 leads to State := Deleted, then CCBS\_Notify\_SS\_Invocation. Connector 2 leads to CCBS\_Suspend to destination network B. HLRA\_CCBS\_CHECK\_INTERACTIONS leads to Result. Result Pass leads to Recall to HLRA\_Recall\_Manager, then State := Recall, then CCBS\_Notify\_SS\_Invocation, then RECALL. Result Fail leads to CCBS\_Suspend to destination network B, then State := Frozen, then CCBS\_Notify\_SS\_Invocation, then FROZEN. + +Figure 11.1.2.3: Process HLRA\_Request (sheet 2 of 5) + +![Two state transition diagrams for Process HLRA_Request. The top diagram starts with RECALL and branches into Completed, Busy, and Failure (Cause) states. The bottom diagram starts with RECALL and branches into Delete, CCBS_Cancel, CCBS_END, and T3 Expiry states.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +**Process HLRA\_Request** 3(5) + +``` +stateDiagram-v2 + [*] --> RECALL + RECALL --> Completed + RECALL --> Busy + RECALL --> Failure_Cause: From HLRA_Recall_Manager + RECALL --> Failure_Cause: From HLRA_Recall_Manager + + Completed --> Retain_supported + Retain_supported --> Deleted: False + Retain_supported --> State_Completed: True + State_Completed --> CCBS_Notify_SS_Invocation + CCBS_Notify_SS_Invocation --> [*] + + Busy --> Retain_supported + Retain_supported --> Deleted: False + Retain_supported --> State_Active: True + State_Active --> CCBS_Notify_SS_Invocation + CCBS_Notify_SS_Invocation --> ACTIVE + + Failure_Cause --> Cause + Cause --> T4_exp: T4 exp + Cause --> else + T4_exp --> Cause_T4_Timeout: Cause := T4-Timeout + Cause_T4_Timeout --> CCBS_Cancel_Cause: To destination network B + CCBS_Cancel_Cause --> Deleted + Deleted --> To_HLRA_Request_Manager + Deleted --> 1 + + else + CCBS_Cancel --> To_destination_network_B + end + + ACTIVE --> 3 + + state RECALL + RECALL --> Delete + RECALL --> CCBS_Cancel + RECALL --> CCBS_END + RECALL --> T3_Expiry: T3 Expiry + + Delete --> CCBS_Cancel + CCBS_Cancel --> Deleted + Deleted --> To_HLRA_Request_Manager + Deleted --> 1 +``` + +The diagram illustrates the state transitions for the Process HLRA\_Request. It is divided into two main sections. + +**Top Section:** Starts with the initial state **RECALL**. Transitions lead to **Completed**, **Busy**, and **Failure (Cause)** states. The **Completed** state leads to a decision **Retain\_supported**. If **False**, it leads to **Deleted**, which then leads to **To HLRA\_Request\_Manager**. If **True**, it leads to **State := Completed**, then **CCBS\_Notify\_SS\_Invocation**, which ends with a crossed-out transition. The **Busy** state also leads to **Retain\_supported**. If **True**, it leads to **State := Active**, then **CCBS\_Notify\_SS\_Invocation**, which leads to the **ACTIVE** state. The **Failure (Cause)** state, reached from **HLRA\_Recall\_Manager**, leads to a **Cause** decision. If **T4 exp**, it leads to **Cause := T4-Timeout**, then **CCBS\_Cancel( Cause)** (To destination network B), then **Deleted**, which leads to **To HLRA\_Request\_Manager** and connector **1**. If **else**, it leads to **CCBS\_Cancel**, which leads to **To destination network B**. Connector **3** is also shown. + +**Bottom Section:** Starts with the initial state **RECALL**. Transitions lead to **Delete**, **CCBS\_Cancel**, **CCBS\_END**, and **T3 Expiry** states. **Delete** leads to **CCBS\_Cancel**. **CCBS\_Cancel** leads to **Deleted**, which leads to **To HLRA\_Request\_Manager** and connector **1**. **CCBS\_END** and **T3 Expiry** also lead to **Deleted**. **CCBS\_Cancel** is also reached from **destination network B**. + +Two state transition diagrams for Process HLRA\_Request. The top diagram starts with RECALL and branches into Completed, Busy, and Failure (Cause) states. The bottom diagram starts with RECALL and branches into Delete, CCBS\_Cancel, CCBS\_END, and T3 Expiry states. + +Figure 11.1.2.3: Process HLRA\_Request (sheet 3 of 5) + +![State transition diagram for Process HLRA_Request. The process starts in the RECALL state and transitions to SUSPENDED via Suspend (Type, Sus_Cause) actions. From SUSPENDED, it can transition to RESUME, T3 Expiry, CCBS_Cancel, or Delete states. RESUME leads to CCBS_Resume and connector 3. T3 Expiry leads to Cause := T3-Timeout and then CCBS_Cancel(Cause) to connector 3. CCBS_Cancel leads to Deleted and connector 1. Delete leads to CCBS_Cancel and connector 1.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +### Process HLRA\_Request + +4(5) + +``` +stateDiagram-v2 + [*] --> RECALL + RECALL --> Suspend_1: Suspend (Type, Sus_Cause) + Suspend_1 --> CCBS_Suspend + CCBS_Suspend --> Suspend_2: Suspend (Type, Sus_Cause) + Suspend_2 --> State := Suspend + State := Suspend --> CCBS_Notify_SS_Invocation + CCBS_Notify_SS_Invocation --> SUSPENDED + SUSPENDED --> RESUME + SUSPENDED --> T3_Expiry + SUSPENDED --> CCBS_Cancel + SUSPENDED --> Delete + RESUME --> CCBS_Resume + CCBS_Resume --> 3 + T3_Expiry --> Cause := T3-Timeout + Cause := T3-Timeout --> CCBS_Cancel_Cause: CCBS_Cancel(Cause) + CCBS_Cancel_Cause --> 3 + CCBS_Cancel --> Deleted + Deleted --> 1 + Delete --> CCBS_Cancel_Delete: CCBS_Cancel + CCBS_Cancel_Delete --> 1 +``` + +The diagram illustrates the state transitions for the Process HLRA\_Request. It begins in the RECALL state, where a Suspend (Type, Sus\_Cause) action is triggered by the From HLRA\_Recall\_Manager. This leads to the CCBS\_Suspend state, which then transitions to another Suspend (Type, Sus\_Cause) state triggered by the To destination network B. This is followed by a State := Suspend action triggered by the To HLRA\_Request\_Manager, which leads to the CCBS\_Notify\_SS\_Invocation state and finally the SUSPENDED state. From the SUSPENDED state, there are four possible transitions: RESUME, T3 Expiry, CCBS\_Cancel, and Delete. The RESUME transition is triggered by the From HLRA\_Request\_Manager and leads to the CCBS\_Resume state, which then leads to connector 3. The T3 Expiry transition leads to the Cause := T3-Timeout state, which then leads to the CCBS\_Cancel(Cause) state, which then leads to connector 3. The CCBS\_Cancel transition is triggered by the From destination network B and leads to the Deleted state, which then leads to connector 1. The Delete transition is triggered by the From HLRA\_Request\_Manager and leads to the CCBS\_Cancel state, which then leads to connector 1. + +State transition diagram for Process HLRA\_Request. The process starts in the RECALL state and transitions to SUSPENDED via Suspend (Type, Sus\_Cause) actions. From SUSPENDED, it can transition to RESUME, T3 Expiry, CCBS\_Cancel, or Delete states. RESUME leads to CCBS\_Resume and connector 3. T3 Expiry leads to Cause := T3-Timeout and then CCBS\_Cancel(Cause) to connector 3. CCBS\_Cancel leads to Deleted and connector 1. Delete leads to CCBS\_Cancel and connector 1. + +Figure 11.1.2.3: Process HLRA\_Request (sheet 4 of 5) + +![Flowchart for Process HLRA_Request (sheet 5 of 5). The diagram shows two main paths starting from a 'FROZEN' state. The top path handles 'T3 Expiry', 'CCBS_Cancel', and 'Location_Update' events. 'T3 Expiry' leads to 'Cause := T3-Timeout' and then 'CCBS_Cancel(Cause)' to destination network B. 'CCBS_Cancel' leads to 'Deleted' and connector '1'. 'Location_Update' leads to 'HLRA_CCBS_CHECK_INTERACTIONS', then a 'Result' decision. 'Fail' leads to connector '2'. 'Pass' leads to 'Type := NET Sus_Cause := Temporary', then 'Suspend(Type, Sus_Cause)' to HLRA_Request_Manager, and connector '4'. A note for 'Suspend' states: 'Although the request can be handled due the interaction has been removed the HLRA_Resume process is invoked in order to resume the request in well organized manner.' The bottom path starts from another 'FROZEN' state, receives 'Delete' from HLRA_Request_Manager, sends 'CCBS_Cancel' to destination network B, and ends at connector '1'.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +### Process HLRA\_Request + +5(5) + +``` +graph TD + subgraph TopPath [ ] + F1([FROZEN]) --> T3Expiry{{T3 Expiry}} + F1 --> CCBS_Cancel1{{CCBS_Cancel}} + F1 --> Location_Update{{Location_Update}} + T3Expiry --> Cause["Cause := T3-Timeout"] + Cause --> CCBS_Cancel2{{CCBS_Cancel(Cause)}} + CCBS_Cancel2 --> Deleted{{Deleted}} + Deleted --> C1((1)) + CCBS_Cancel1 --> Deleted + Location_Update --> HLRA_Check[HLRA_CCBS_CHECK_INTERACTIONS] + HLRA_Check --> Result{Result} + Result -- Fail --> C2((2)) + Result -- Pass --> Type["Type := NET Sus_Cause := Temporary"] + Type --> Suspend{{Suspend(Type, Sus_Cause)}} + Suspend --> C4((4)) + end + subgraph BottomPath [ ] + F2([FROZEN]) --> Delete{{Delete}} + Delete --> CCBS_Cancel3{{CCBS_Cancel}} + CCBS_Cancel3 --> C1b((1)) + end + Note1[From destination network B] -.-> T3Expiry + Note2[To destination network B] -.-> CCBS_Cancel2 + Note3[To HLRA_Request_Manager] -.-> Deleted + Note4[From HLRA_Request_Manager] -.-> Delete + Note5[To destination network B] -.-> CCBS_Cancel3 + Note6[To HLRA_Request_Manager +Note: Although the request can be handled due the interaction has been removed the HLRA_Resume process is invoked in order to resume the request in well organized manner.] -.-> Suspend +``` + +Flowchart for Process HLRA\_Request (sheet 5 of 5). The diagram shows two main paths starting from a 'FROZEN' state. The top path handles 'T3 Expiry', 'CCBS\_Cancel', and 'Location\_Update' events. 'T3 Expiry' leads to 'Cause := T3-Timeout' and then 'CCBS\_Cancel(Cause)' to destination network B. 'CCBS\_Cancel' leads to 'Deleted' and connector '1'. 'Location\_Update' leads to 'HLRA\_CCBS\_CHECK\_INTERACTIONS', then a 'Result' decision. 'Fail' leads to connector '2'. 'Pass' leads to 'Type := NET Sus\_Cause := Temporary', then 'Suspend(Type, Sus\_Cause)' to HLRA\_Request\_Manager, and connector '4'. A note for 'Suspend' states: 'Although the request can be handled due the interaction has been removed the HLRA\_Resume process is invoked in order to resume the request in well organized manner.' The bottom path starts from another 'FROZEN' state, receives 'Delete' from HLRA\_Request\_Manager, sends 'CCBS\_Cancel' to destination network B, and ends at connector '1'. + +Figure 11.1.2.3: Process HLRA\_Request (sheet 5 of 5) + +![State transition diagram for Process HLRA_RecallManager. It shows two main state machines. The left one starts at IDLE, transitions to Recall (triggered by From individual HLRA_Request), then to Recall (action: To HLRA_Resume to stop T11), then to CCBS_RUF (action: To MSC_VLR), and finally to CCBS_BUSY. A Query_Status transition from IDLE leads to From HLRA_Resume, then to Recall_End (action: To HLRA_Resume), and back to IDLE. The right state machine starts at CCBS_BUSY, transitions to Recall (triggered by From individual HLRA_Request), then to a state with Type := NET, Sus_Cause := Busy, then to Suspend (Type, Sus_Cause) (action: To individual HLRA_Request), and finally back to CCBS_BUSY.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +Process HLRA\_RecallManager 1(4) + +``` +stateDiagram-v2 + [*] --> IDLE + IDLE --> Recall_L + state "Recall" as Recall_L + Recall_L --> Recall_L_A + state "Recall" as Recall_L_A + Recall_L_A --> CCBS_RUF + state "CCBS_RUF" as CCBS_RUF + CCBS_RUF --> CCBS_BUSY_L + state "CCBS_BUSY" as CCBS_BUSY_L + IDLE --> Query_Status + state "Query_Status" as Query_Status + Query_Status --> From_HLRA_Resume + state "From HLRA_Resume" as From_HLRA_Resume + From_HLRA_Resume --> Recall_End + state "Recall_End" as Recall_End + Recall_End --> To_HLRA_Resume + state "To HLRA_Resume" as To_HLRA_Resume + To_HLRA_Resume --> IDLE + CCBS_BUSY_R --> Recall_R + state "CCBS_BUSY" as CCBS_BUSY_R + state "Recall" as Recall_R + Recall_R --> Type_Sus_Cause + state "Type := NET<br/>Sus_Cause := Busy" as Type_Sus_Cause + Type_Sus_Cause --> Suspend + state "Suspend (Type, Sus_Cause)" as Suspend + Suspend --> To_individual_HLRA_Request + state "To individual HLRA_Request" as To_individual_HLRA_Request + To_individual_HLRA_Request --> CCBS_BUSY_R +``` + +State transition diagram for Process HLRA\_RecallManager. It shows two main state machines. The left one starts at IDLE, transitions to Recall (triggered by From individual HLRA\_Request), then to Recall (action: To HLRA\_Resume to stop T11), then to CCBS\_RUF (action: To MSC\_VLR), and finally to CCBS\_BUSY. A Query\_Status transition from IDLE leads to From HLRA\_Resume, then to Recall\_End (action: To HLRA\_Resume), and back to IDLE. The right state machine starts at CCBS\_BUSY, transitions to Recall (triggered by From individual HLRA\_Request), then to a state with Type := NET, Sus\_Cause := Busy, then to Suspend (Type, Sus\_Cause) (action: To individual HLRA\_Request), and finally back to CCBS\_BUSY. + +Figure 11.1.2.4: Process HLRA\_Recall\_Manager (sheet 1 of 4) + +![State transition diagram for Process HLRA_RecallManager. It starts in CCBS_BUSY, receives CCBS_RUF_Ack (Result) from MSC_VLR, then checks the Result. If RUF Accepted, it starts T12 and returns to CCBS_BUSY. If T4 expiry, UDUB_Idle, or RUF Rejected, it sets Cause := Result, sends Failure (Cause) to individual HLRA_Request, then Recall_End to HLRA_Resume, and ends in IDLE. If T10 expiry or UDUB_Busy, it sets Type := USER, Sus_Cause := Busy, sends Suspend (Type, Sus_Cause) to individual HLRA_Request, then Recall_End to HLRA_Resume, and ends in IDLE.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +Process HLRA\_RecallManager 2(4) + +``` +stateDiagram-v2 + [*] --> CCBS_BUSY + CCBS_BUSY --> CCBS_RUF_Ack{CCBS_RUF_Ack (Result)} + note right of CCBS_RUF_Ack: From MSC_VLR + CCBS_RUF_Ack --> Result{Result} + Result --> Start_T12[Start T12] : RUF Accepted + Start_T12 --> CCBS_BUSY + Result --> Cause[Cause := Result] : T4 expiry, UDUB_Idle, RUF Rejected + Cause --> Failure{Failure (Cause)} + note right of Failure: To individual HLRA_Request + Failure --> Recall_End{Recall_End} + note right of Recall_End: To HLRA_Resume + Recall_End --> IDLE + Result --> Type[Type := USER, Sus_Cause := Busy] : T10 expiry, UDUB_Busy + Type --> Suspend{Suspend (Type, Sus_Cause)} + note right of Suspend: To individual HLRA_Request + Suspend --> Recall_End +``` + +State transition diagram for Process HLRA\_RecallManager. It starts in CCBS\_BUSY, receives CCBS\_RUF\_Ack (Result) from MSC\_VLR, then checks the Result. If RUF Accepted, it starts T12 and returns to CCBS\_BUSY. If T4 expiry, UDUB\_Idle, or RUF Rejected, it sets Cause := Result, sends Failure (Cause) to individual HLRA\_Request, then Recall\_End to HLRA\_Resume, and ends in IDLE. If T10 expiry or UDUB\_Busy, it sets Type := USER, Sus\_Cause := Busy, sends Suspend (Type, Sus\_Cause) to individual HLRA\_Request, then Recall\_End to HLRA\_Resume, and ends in IDLE. + +Figure 11.1.2.4: Process HLRA\_Recall\_Manager (sheet 2 of 4) + +![State transition diagram for Process HLRA_RecallManager. It starts at CCBS_BUSY, transitions to T12 expiry and CCBS_RUF (Error) from MSC_VLR. From CCBS_RUF, it goes to an Error decision. ELSE leads to Cause := Failure, then to individual HLRA_Request (Cause) and Recall_End (To HLRA_Resume), ending at IDLE. The Error decision also leads to Type := NET Sus_Cause := Not Reach (with reasons: IMSI Detached, Restricted Area, No Page Response, Absent_Subscriber, Radio Failure, CComp Busy), then to Suspend (Type, Sus_Cause) with a note about resuming, ending at IDLE. T12 expiry leads to Close the communication between HLR and VLR, which also ends at IDLE.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +Process HLRA\_RecallManager 3(4) + +``` +stateDiagram-v2 + [*] --> CCBS_BUSY + CCBS_BUSY --> T12_expiry + CCBS_BUSY --> CCBS_RUF_Error + CCBS_RUF_Error --> Error + T12_expiry --> Close_Communication + Close_Communication --> IDLE + Error -- ELSE --> Cause_Failure + Cause_Failure --> Failure_Cause + Failure_Cause --> Recall_End + Recall_End --> IDLE + Error --> Type_Net_Sus_Cause_Not_Reach + Type_Net_Sus_Cause_Not_Reach --> Suspend_Type_Sus_Cause + Suspend_Type_Sus_Cause --> IDLE + + note right of CCBS_RUF_Error: From MSC_VLR + note right of Failure_Cause: To individual HLRA_Request + note right of Recall_End: To HLRA_Resume + note right of Suspend_Type_Sus_Cause: To individual HLRA_Request + NOTE: Because MS is not reachable resuming is not started + note right of Type_Net_Sus_Cause_Not_Reach: IMSI Detached + Restricted Area + No Page Response + Absent_Subscriber + Radio Failure + CComp Busy +``` + +State transition diagram for Process HLRA\_RecallManager. It starts at CCBS\_BUSY, transitions to T12 expiry and CCBS\_RUF (Error) from MSC\_VLR. From CCBS\_RUF, it goes to an Error decision. ELSE leads to Cause := Failure, then to individual HLRA\_Request (Cause) and Recall\_End (To HLRA\_Resume), ending at IDLE. The Error decision also leads to Type := NET Sus\_Cause := Not Reach (with reasons: IMSI Detached, Restricted Area, No Page Response, Absent\_Subscriber, Radio Failure, CComp Busy), then to Suspend (Type, Sus\_Cause) with a note about resuming, ending at IDLE. T12 expiry leads to Close the communication between HLR and VLR, which also ends at IDLE. + +Figure 11.1.2.4: Process HLRA\_Recall\_Manager (sheet 3 of 4) + +![EPC diagram for Process HLRA_RecallManager. The process starts at CCBS_BUSY, receives a CCBS_Call_Report (Outcome) from CCBS_Coordinator_HLR, stops T12, and then checks the Outcome. If Success, it sends a Completed message to individual HLRA_Request. If Failure, it sets Cause := Failure and sends a Failure (Cause) message to individual HLRA_Request. If Busy, it sends a Busy message to individual HLRA_Request. All three messages lead to a Recall_End function, which sends a To HLRA_Resume message and ends at IDLE.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +Process HLRA\_RecallManager + +4(4) + +``` +graph TD; Start([CCBS_BUSY]) --> Event{CCBS_Call_Report (Outcome)}; Note1[From CCBS_Coordinator_HLR] -.-> Event; Event --> Function[Stop T12]; Function --> Decision{Outcome}; Decision -- Success --> Event2{Completed}; Note2[To individual HLRA_Request] -.-> Event2; Event2 --> Junction(( )); Decision -- Failure --> Function2[Cause := Failure]; Function2 --> Event3{Failure (Cause)}; Note3[To individual HLRA_Request] -.-> Event3; Event3 --> Junction; Decision -- Busy --> Event4{Busy}; Note4[To individual HLRA_Request] -.-> Event4; Event4 --> Junction; Junction --> Function3{Recall_End}; Note5[To HLRA_Resume] -.-> Function3; Function3 --> End([IDLE]); +``` + +EPC diagram for Process HLRA\_RecallManager. The process starts at CCBS\_BUSY, receives a CCBS\_Call\_Report (Outcome) from CCBS\_Coordinator\_HLR, stops T12, and then checks the Outcome. If Success, it sends a Completed message to individual HLRA\_Request. If Failure, it sets Cause := Failure and sends a Failure (Cause) message to individual HLRA\_Request. If Busy, it sends a Busy message to individual HLRA\_Request. All three messages lead to a Recall\_End function, which sends a To HLRA\_Resume message and ends at IDLE. + +Figure 11.1.2.4: Process HLRA\_Recall\_Manager (sheet 4 of 4) + +![State transition diagram for Process HLRA_Resume. It shows three main state transition paths. Path 1: An unlabeled oval state transitions to an IDLE state. Path 2: A *(IDLE) state transitions via a Stop_Resume action (from HLRA_Request_Manager) to a Stop_Monitoring action (to HLRA_Monitoring), which then leads to an IDLE state. Path 3: A * state transitions via a Reset_Trigger_A_Idle (Sus_Cause) action (from HLRA_Request_Manager with a note about subscriber reachability) to an A_Query (Sus_Cause) action (to HLRA_Monitoring), which then leads to a RESUME_PENDING state. A fourth path shows a *(IDLE) state transitioning via a Set_Trigger_A_Idle (Sus_Cause) action (from HLRA_Request_Manager with a note about suspended requests) to an A_Query (Sus_Cause) action (to HLRA_Monitoring), which then leads to a - state.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +Process HLRA\_Resume 1(3) + +``` +stateDiagram-v2 + [*] --> IDLE + *(IDLE) --> Stop_Resume : From HLRA_Request_Manager + Stop_Resume --> Stop_Monitoring : To HLRA_Monitoring + Stop_Monitoring --> IDLE + [*] --> Reset_Trigger_A_Idle : From HLRA_Request_Manager. Note: The subscriber is not reachable and the possibly ongoing resuming is stopped until A_Idle input is received. + Reset_Trigger_A_Idle --> A_Query : To HLRA_Monitoring + A_Query --> RESUME_PENDING + *(IDLE) --> Set_Trigger_A_Idle : From HLRA_Request_Manager. Note: Suspended request was marked inactive and needs A_Idle input in order to be resumed. Ongoing resuming continues. + Set_Trigger_A_Idle --> A_Query : To HLRA_Monitoring + A_Query --> [-] +``` + +State transition diagram for Process HLRA\_Resume. It shows three main state transition paths. Path 1: An unlabeled oval state transitions to an IDLE state. Path 2: A \*(IDLE) state transitions via a Stop\_Resume action (from HLRA\_Request\_Manager) to a Stop\_Monitoring action (to HLRA\_Monitoring), which then leads to an IDLE state. Path 3: A \* state transitions via a Reset\_Trigger\_A\_Idle (Sus\_Cause) action (from HLRA\_Request\_Manager with a note about subscriber reachability) to an A\_Query (Sus\_Cause) action (to HLRA\_Monitoring), which then leads to a RESUME\_PENDING state. A fourth path shows a \*(IDLE) state transitioning via a Set\_Trigger\_A\_Idle (Sus\_Cause) action (from HLRA\_Request\_Manager with a note about suspended requests) to an A\_Query (Sus\_Cause) action (to HLRA\_Monitoring), which then leads to a - state. + +Figure 11.1.2.5: Process HLRA\_Resume (sheet 1 of 3) + +![SDL diagram for Process HLRA_Resume showing state transitions between IDLE, RESUME_PENDING, and WAIT_FOR_SELECTION states with various input and output signals.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +Process HLRA\_Resume 2(3) + +``` + +stateDiagram-v2 + IDLE --> Set_Trigger_A_Idle_Sus_Cause : From HLRA_Request_Manager + Set_Trigger_A_Idle_Sus_Cause --> A_Query : To HLRA_Monitoring + A_Query --> RESUME_PENDING + + IDLE --> Set_Trigger_Recall_End : From HLRA_Request_Manager + Set_Trigger_Recall_End --> Query_Status : To HLRA_Recall_Manager + Query_Status --> RESUME_PENDING + + state RESUME_PENDING { + direction LR + [*] --> A_Idle : From HLRA_Monitoring + A_Idle --> Select_First_Req : To HLRA_Request_Manager (NOTE: All requests can be resumed) + Select_First_Req --> WAIT_FOR_SELECTION + + [*] --> Recall_End : From HLRA_Recall_Manager + Recall_End --> Select_Active_Req : To HLRA_Request_Manager + Select_Active_Req --> WAIT_FOR_SELECTION + + [*] --> Set_Trigger_Recall_End_2 : From HLRA_Request_Manager + Set_Trigger_Recall_End_2 --> Query_Status_2 : To HLRA_Recall_Manager + Query_Status_2 --> RESUME_PENDING_2 : RESUME_PENDING + } + +``` + +From HLRA\_Request\_Manager + +Set\_Trigger\_A\_Idle (Sus\_Cause) + +To HLRA\_Monitoring + +A\_Query + +Set\_Trigger\_Recall\_End + +From HLRA\_Request\_Manager + +To HLRA\_Recall\_Manager + +Query\_Status + +IDLE + +RESUME\_PENDING + +From HLRA\_Monitoring + +A\_Idle + +From HLRA\_Recall\_Manager + +Recall\_End + +From HLRA\_Request\_Manager + +Set\_Trigger\_Recall\_End + +To HLRA\_Request\_Manager +NOTE: All requests can be resumed + +Select\_First\_Req + +To HLRA\_Recall\_Manager + +Select\_Active\_Req + +WAIT\_FOR\_SELECTION + +Query\_Status + +RESUME\_PENDING + +SDL diagram for Process HLRA\_Resume showing state transitions between IDLE, RESUME\_PENDING, and WAIT\_FOR\_SELECTION states with various input and output signals. + +Figure 11.1.2.5: Process HLRA\_Resume (sheet 2 of 3) + +![SDL state transition diagram for Process HLRA_Resume sheet 3 of 3. It shows transitions from states WAIT_FOR_SELECTION and RESUMING based on inputs from HLRA_Request_Manager, HLRA_Monitoring, and HLRA_Recall_Manager.](c07e21a8d65991db04263322f859c94f_img.jpg) + +Process HLRA\_Resume +3(3) + +``` + +stateDiagram-v2 + state WAIT_FOR_SELECTION { + direction TB + } + state RESUMING { + direction TB + } + + WAIT_FOR_SELECTION --> Select_Resp : From HLRA_Request_Manager + Select_Resp --> Start_T11 + Start_T11 --> RESUMING + + WAIT_FOR_SELECTION --> Not_Selected : From HLRA_Request_Manager + Not_Selected --> RESUME_PENDING + + WAIT_FOR_SELECTION --> A_Idle : From HLRA_Monitoring + WAIT_FOR_SELECTION --> Recall : From HLRA_Recall_Manager + + RESUMING --> T11_expiry + T11_expiry --> Select_Active_Req : To HLRA_Request_Manager + Select_Active_Req --> WAIT_FOR_SELECTION + + RESUMING --> A_Idle_2 : From HLRA_Monitoring + A_Idle_2 --> Set_All_Active : To HLRA_Request_Manager + Set_All_Active --> Dash_State : "-" + + RESUMING --> Recall_2 : From HLRA_Recall_Manager + Recall_2 --> Stop_T11 + Stop_T11 --> RESUME_PENDING_2 : RESUME_PENDING + +``` + +SDL state transition diagram for Process HLRA\_Resume sheet 3 of 3. It shows transitions from states WAIT\_FOR\_SELECTION and RESUMING based on inputs from HLRA\_Request\_Manager, HLRA\_Monitoring, and HLRA\_Recall\_Manager. + +Figure 11.1.2.5: Process HLRA\_Resume (sheet 3 of 3) + +![State transition diagram for Process HLRA_Monitoring(1,1).](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +Process HLRA\_Monitoring(1,1) + +1(2) + +The diagram illustrates the state transitions for Process HLRA\_Monitoring(1,1). It consists of three main vertical paths. The left path shows a transition from an unlabeled oval state to an IDLE state. The middle path starts at an IDLE state, followed by an A\_Query (Sus\_Cause) message, a Start\_Reporting state, and a WAIT\_FOR\_ANSWER state. From WAIT\_FOR\_ANSWER, an Event\_Report (Status) message is sent. A decision diamond 'Status = CCBS\_Idle' follows. If 'No', it leads to a join point. If 'Yes', it leads to another decision diamond 'Sus\_Cause = Nrc'. If 'Yes' to 'Sus\_Cause = Nrc', it leads to the join point. If 'ELSE', it leads to an A\_Idle message, which then leads to the join point. The join point leads to a MONITORING state. The right path starts at an \*(IDLE) state, followed by a Stop\_Monitoring message, a Stop\_Reporting state, and an IDLE state. A note on the left of the bottom decision diamonds states: 'NOTE: Using the previous history data i.e. Sus\_Cause value to prevent any unnecessary signaling is one possible implementation. The manufacturer is allowed to use other technics to achieve efficient solution.' A note on the top right states: 'Signals to / from left are to / from CCBS\_Coordinator\_HLR unless shown otherwise. Signals to / from right are to / from HLRA\_Resume unless shown otherwise.' There is also an empty note box in the top left corner. + +``` +graph TD; subgraph LeftPath; S1([ ]) --> IDLE1([IDLE]); end; subgraph MiddlePath; IDLE2([IDLE]) --> A_Query{{A_Query (Sus_Cause)}}; A_Query --> Start_Reporting{Start_Reporting}; Start_Reporting --> WAIT_FOR_ANSWER1([WAIT_FOR_ANSWER]); WAIT_FOR_ANSWER1 --> Event_Report{{Event_Report (Status)}}; Event_Report --> Status_Dec{Status = CCBS_Idle}; Status_Dec -- No --> Join(( )); Status_Dec -- Yes --> Sus_Cause_Dec{Sus_Cause = Nrc}; Sus_Cause_Dec -- Yes --> Join; Sus_Cause_Dec -- ELSE --> A_Idle{{A_Idle}}; A_Idle --> Join; Join --> MONITORING([MONITORING]); end; subgraph RightPath; IDLE3([*(IDLE)]) --> Stop_Monitoring{{Stop_Monitoring}}; Stop_Monitoring --> Stop_Reporting{Stop_Reporting}; Stop_Reporting --> IDLE4([IDLE]); end; +``` + +NOTE: Using the previous history data i.e. Sus\_Cause value to prevent any unnecessary signaling is one possible implementation. The manufacturer is allowed to use other technics to achieve efficient solution. + +Signals to / from left are to / from CCBS\_Coordinator\_HLR unless shown otherwise. Signals to / from right are to / from HLRA\_Resume unless shown otherwise. + +State transition diagram for Process HLRA\_Monitoring(1,1). + +Figure 11.1.2.6: Process HLRA\_Monitoring (sheet 1 of 2) + +![State transition diagram for Process HLRA_Monitoring. It consists of two vertical flowcharts. The top flowchart starts at MONITORING, goes to Event_Report (status), then to a status decision diamond. From status, the ELSE path leads to MONITORING, and the CCBS_Idle path leads to an A_Idle output and then to MONITORING. The bottom flowchart starts at MONITORING, goes to Location_Update, then to a CCBS supported in VLR decision diamond. From this diamond, the No path leads to MONITORING, and the Yes path leads to an A_Idle output and then to IDLE.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +Process HLRA\_Monitoring(1,1) + +2(2) + +Signals to / from left are to / from CCBS\_Coordinator\_HLR unless shown otherwise. +Signals to / from right are to / from HLRA\_Resume unless shown otherwise + +``` +graph TD; subgraph TopFlowchart; M1((MONITORING)) --> ER1{{Event_Report (status)}}; ER1 --> S1{status}; S1 -- ELSE --> M2((MONITORING)); S1 -- CCBS_Idle --> AI1{{A_Idle}}; AI1 --> M2; end; subgraph BottomFlowchart; M3((MONITORING)) --> LU1{{Location_Update}}; LU1 --> CV{CCBS supported in VLR}; CV -- No --> M4((MONITORING)); CV -- Yes --> AI2{{A_Idle}}; AI2 --> I1((IDLE)); end; +``` + +State transition diagram for Process HLRA\_Monitoring. It consists of two vertical flowcharts. The top flowchart starts at MONITORING, goes to Event\_Report (status), then to a status decision diamond. From status, the ELSE path leads to MONITORING, and the CCBS\_Idle path leads to an A\_Idle output and then to MONITORING. The bottom flowchart starts at MONITORING, goes to Location\_Update, then to a CCBS supported in VLR decision diamond. From this diamond, the No path leads to MONITORING, and the Yes path leads to an A\_Idle output and then to IDLE. + +Figure 11.1.2.6: Process HLRA\_Monitoring (sheet 2 of 2) + +![Flowchart for Procedure HLRA_CCBS_Check_Interactions. It starts with a connector, followed by three decision diamonds: 'VLR area known', 'CCBS supported in current MSCVLR', and 'CAMEL invoked in the original call'. If 'VLR area known' is No, it goes to 'Result := Fail'. If 'CCBS supported in current MSCVLR' is No, it goes to 'Result := Fail'. If 'CAMEL invoked in the original call' is No, it goes to 'Result := Pass'. If 'CAMEL invoked in the original call' is Yes, it goes to another decision 'CAMEL supported in MSC'. If 'CAMEL supported in MSC' is No, it goes to 'Result := Fail'. If 'CAMEL supported in MSC' is Yes, it goes to 'Result := Pass'. All 'Result' boxes lead to connectors.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +Procedure HLRA\_CCBS\_Check\_Interactions 1(1) + +``` +graph TD; Start([ ]) --> D1{VLR area known}; D1 -- No --> R3[Result := Fail]; D1 -- Yes --> D2{CCBS supported in current MSCVLR}; D2 -- No --> R3; D2 -- Yes --> D3{CAMEL invoked in the original call}; D3 -- No --> R1[Result := Pass]; D3 -- Yes --> D4{CAMEL supported in MSC}; D4 -- No --> R3; D4 -- Yes --> R2[Result := Pass]; R1 --> End1(( )); R2 --> End2(( )); R3 --> End3(( )); +``` + +Flowchart for Procedure HLRA\_CCBS\_Check\_Interactions. It starts with a connector, followed by three decision diamonds: 'VLR area known', 'CCBS supported in current MSCVLR', and 'CAMEL invoked in the original call'. If 'VLR area known' is No, it goes to 'Result := Fail'. If 'CCBS supported in current MSCVLR' is No, it goes to 'Result := Fail'. If 'CAMEL invoked in the original call' is No, it goes to 'Result := Pass'. If 'CAMEL invoked in the original call' is Yes, it goes to another decision 'CAMEL supported in MSC'. If 'CAMEL supported in MSC' is No, it goes to 'Result := Fail'. If 'CAMEL supported in MSC' is Yes, it goes to 'Result := Pass'. All 'Result' boxes lead to connectors. + +Figure 11.1.2.7: Procedure HLRA\_CCBS\_Check\_Interactions + +![Flowchart for Procedure CCBS_Notify_SS_Invocation. The process starts at a connector, leads to a decision 'SS-CSI stored in HLR?'. If 'Yes', it moves to 'SS-CSI applies to CCBS?'. If 'Yes', it triggers 'SS Invocation Notify (State)'. If 'No' to either decision, the flow bypasses to the final connector.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +### Procedure CCBS\_Notify\_SS\_Invocation + +1(1) + +Procedure in the MSC to notify + the gsmSCF of the CCBS invocation + +Signals to/from the left + are to/from the gsmSCF. + +``` + +graph TD + Start([ ]) --> D1{SS-CSI stored +in HLR?} + D1 -- No --> End([ ]) + D1 -- Yes --> D2{SS-CSI applies +to CCBS?} + D2 -- No --> End + D2 -- Yes --> Action[SS Invocation +Notify (State)] + Action --> End + +``` + +Flowchart for Procedure CCBS\_Notify\_SS\_Invocation. The process starts at a connector, leads to a decision 'SS-CSI stored in HLR?'. If 'Yes', it moves to 'SS-CSI applies to CCBS?'. If 'Yes', it triggers 'SS Invocation Notify (State)'. If 'No' to either decision, the flow bypasses to the final connector. + +**Figure 11.1.2.8: Procedure CCBS\_Notify\_SS\_Invocation** + +## 11.2 Destination Network Processes + +### 11.2.1 Procedures in GMSC + +Figure 11.2.1.1: Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Call + +This procedure checks from the IAM message whether the call is CCBS call. If that is the case the CCBS Call parameter is set to the Send Routeing Info message. This functionality shall be applied only to the initial call leg. The procedure initialises also the CCBS Possible variable as True, the variable is accessible to all CCBS specific procedures in the GMSC. + +Figure 11.2.1.2: Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Indicators + +This procedure sets the CCBS\_Call indicator to the outgoing IAM message when needed. This functionality shall be applied only to the initial call leg. + +Figure 11.2.1.3: Procedure CCBS\_MT\_GMSC\_Remove\_Indicators\_Store\_FWT + +This procedure removes CCBS\_Call indicator from the forwarded IAM message and also stores the forwarding type. It also checks whether subscriber B can be target of CCBS Requests and stores that information for later use. + +Figure 11.2.1.4: Procedure CCBS\_MT\_GMSC\_Remove\_Indicators + +This procedure removes CCBS\_Call indicator from the outgoing IAM message. CCBS activation is not possible for this call because T-CSI modified destination address. + +Figure 11.2.1.5: Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Possible + +This procedure contains the core logic to handle various interactions with CAMEL, OR and received Release message content. The procedure alters CCBS specific global variable CCBS Target which controls setting of the diagnostic field in the Release message towards the originating network. + +Global variables Reconnect and Resume Call are specific to CAMEL and OR interaction respectively. They are initialised and updated in the process MT\_GMSC or MT\_CF\_MSC, refer to TS 23.018. + +![Flowchart for Procedure CCBS_MT_GMSC_Check_CCBS_Call. It starts with a connector, followed by a decision 'Reconnect = True or Resume Call = True'. If 'Yes', it goes to 'CCBS Call parameter := False'. If 'No', it goes to a decision 'CCBS Call Indicator = True' (with a note 'Test the indicator in received IAM message'). If 'Yes', it goes to 'CCBS Call parameter := True'. If 'No', it goes to 'CCBS Call parameter := False'. All three 'CCBS Call parameter' blocks lead to 'CCBS Possible := True' (with a note about this global variable). Finally, it reaches an exit connector.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Call 1(1) + +``` +graph TD; Start([ ]) --> D1{Reconnect = True or Resume Call = True}; D1 -- Yes --> P1[CCBS Call parameter := False]; D1 -- No --> D2{CCBS Call Indicator = True}; Note1[Test the indicator in received IAM message] -.-> D2; D2 -- Yes --> P2[CCBS Call parameter := True]; D2 -- No --> P3[CCBS Call parameter := False]; P1 --> P4[CCBS Possible := True]; P2 --> P4; P3 --> P4; Note2[This global variable is specific to CCBS handling. It is set to True by default but indication from HLR or the first call leg's result may lead CCBS Not Possible case. This variable covers the functionality of the other CCBS specific procedures in GMSC] -.-> P4; P4 --> End(( )); +``` + +Flowchart for Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Call. It starts with a connector, followed by a decision 'Reconnect = True or Resume Call = True'. If 'Yes', it goes to 'CCBS Call parameter := False'. If 'No', it goes to a decision 'CCBS Call Indicator = True' (with a note 'Test the indicator in received IAM message'). If 'Yes', it goes to 'CCBS Call parameter := True'. If 'No', it goes to 'CCBS Call parameter := False'. All three 'CCBS Call parameter' blocks lead to 'CCBS Possible := True' (with a note about this global variable). Finally, it reaches an exit connector. + +Figure 11.2.1.1: Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Call + +![Flowchart for Procedure CCBS_MT_GMSC_Check_CCBS_Indicators. It starts with a connector, followed by a decision 'Reconnect = True or Resume Call = True'. If 'Yes', it goes to 'CCBS Call Indicator := False'. If 'No', it goes to 'CCBS Call' decision. If 'Yes', it goes to 'Keep CCBS Call Indicator' decision. If 'False', it goes to 'CCBS Call Indicator := False'. If 'True', it goes to 'CCBS Call Indicator := True' and 'Indicator to the outgoing IAM message'. All three paths lead to a final connector.](38d82ffe820e339811b396206f40a201_img.jpg) + +Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Indicators 1(1) + +``` +graph TD; Start([ ]) --> D1{Reconnect = True or Resume Call = True}; D1 -- Yes --> P3[CCBS Call Indicator := False]; D1 -- No --> D2{CCBS Call}; D2 -- Yes --> D3{Keep CCBS Call Indicator}; D2 -- No --> P2[CCBS Call Indicator := False]; D3 -- True --> P1[CCBS Call Indicator := True]; D3 -- False --> P2; P1 --> End(( )); P2 --> End; P3 --> End; +``` + +Test the parameter received in SRI. If absent, False exit shall be taken. + +Indicator to the outgoing IAM message + +Flowchart for Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Indicators. It starts with a connector, followed by a decision 'Reconnect = True or Resume Call = True'. If 'Yes', it goes to 'CCBS Call Indicator := False'. If 'No', it goes to 'CCBS Call' decision. If 'Yes', it goes to 'Keep CCBS Call Indicator' decision. If 'False', it goes to 'CCBS Call Indicator := False'. If 'True', it goes to 'CCBS Call Indicator := True' and 'Indicator to the outgoing IAM message'. All three paths lead to a final connector. + +Figure 11.2.1.2: Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Indicators + +![Flowchart for Procedure CCBS_MT_GMSC_Remove_Indicators_Store_FWT. The process starts with a connector, followed by a decision 'Reconnect = True or Resume Call = True'. If 'Yes', it goes to the end connector. If 'No', it goes to 'CCBS Target'. A note next to 'CCBS Target' says 'Test the parameter received in SRI Ack. If absent False exit shall be taken.' If 'True', it goes to 'FWD on Busy'. If 'False', it goes to 'CCBS Possible := False'. A note next to 'CCBS Possible := False' says 'ALTer GMSC internal variable. Default is True.' If 'FWD on Busy' is 'True', it goes to the end connector. If 'False', it goes to 'CCBS Possible := False'. From 'CCBS Possible := False', it goes to 'CCBS Call'. If 'Yes', it goes to 'Remove CCBS Indicator'. If 'No', it goes to the end connector. From 'Remove CCBS Indicator', it goes to the end connector.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +Procedure CCBS\_MT\_GMSC\_Remove\_Indicators\_Store\_FWT 1(1) + +``` +graph TD; Start([ ]) --> D1{Reconnect = True or Resume Call = True}; D1 -- Yes --> End(( )); D1 -- No --> D2{CCBS Target}; Note1[Test the parameter received in SRI Ack. If absent False exit shall be taken.] -.-> D2; D2 -- True --> D3{FWD on Busy}; D2 -- False --> P1[CCBS Possible := False]; Note2[ALTer GMSC internal variable. Default is True.] -.-> P1; D3 -- True --> End; D3 -- False --> P1; P1 --> D4{CCBS Call}; D4 -- Yes --> P2[Remove CCBS Indicator]; D4 -- No --> End; P2 --> End; +``` + +Flowchart for Procedure CCBS\_MT\_GMSC\_Remove\_Indicators\_Store\_FWT. The process starts with a connector, followed by a decision 'Reconnect = True or Resume Call = True'. If 'Yes', it goes to the end connector. If 'No', it goes to 'CCBS Target'. A note next to 'CCBS Target' says 'Test the parameter received in SRI Ack. If absent False exit shall be taken.' If 'True', it goes to 'FWD on Busy'. If 'False', it goes to 'CCBS Possible := False'. A note next to 'CCBS Possible := False' says 'ALTer GMSC internal variable. Default is True.' If 'FWD on Busy' is 'True', it goes to the end connector. If 'False', it goes to 'CCBS Possible := False'. From 'CCBS Possible := False', it goes to 'CCBS Call'. If 'Yes', it goes to 'Remove CCBS Indicator'. If 'No', it goes to the end connector. From 'Remove CCBS Indicator', it goes to the end connector. + +Figure 11.2.1.3: Procedure CCBS\_MT\_GMSC\_Remove\_Indicators\_Store\_FWT + +![Flowchart for Procedure CCBS_MT_GMSC_Remove_Indicators. It starts with a connector, followed by a decision diamond 'Reconnect = True or Resume Call = True'. If 'Yes', it goes to a later connector. If 'No', it goes to a process box 'CCBS Possible := False', then to another decision diamond 'CCBS Call'. If 'CCBS Call' is 'Yes', it goes to 'Remove CCBS Indicator' then to the later connector. If 'CCBS Call' is 'No', it goes directly to the later connector.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +Procedure CCBS\_MT\_GMSC\_Remove\_Indicators 1(1) + +``` +graph TD; Start([ ]) --> Decision1{Reconnect = True or Resume Call = True}; Decision1 -- Yes --> Join(( )); Decision1 -- No --> Process1[CCBS Possible := False]; Process1 --> Decision2{CCBS Call}; Decision2 -- Yes --> Process2[Remove CCBS Indicator]; Process2 --> Join; Decision2 -- No --> Join; +``` + +Flowchart for Procedure CCBS\_MT\_GMSC\_Remove\_Indicators. It starts with a connector, followed by a decision diamond 'Reconnect = True or Resume Call = True'. If 'Yes', it goes to a later connector. If 'No', it goes to a process box 'CCBS Possible := False', then to another decision diamond 'CCBS Call'. If 'CCBS Call' is 'Yes', it goes to 'Remove CCBS Indicator' then to the later connector. If 'CCBS Call' is 'No', it goes directly to the later connector. + +Figure 11.2.1.4: Procedure CCBS\_MT\_GMSC\_Remove\_Indicators + +![Flowchart for Procedure CCBS_MT_GMSC_Check_CCBS_Possible. The process starts with a connector, followed by a decision 'Call Completion Treatment Indicator present in SII2?'. If 'No', it goes to 'Call Completion Treatment Indicator set to Reject Call Completion Service Request?'. If 'Yes', it goes to 'CCBS Possible'. From 'CCBS Possible', if 'False', it goes to 'Release'. If 'True', it goes to 'Reconnect = True or Resume Call = True'. If 'Yes', it goes to 'Cause = Busy or Cause = No circuit channel available'. If 'Yes', it sets 'CCBS Target := True'. If 'No', it goes to 'Forwarded call'. If 'Yes', it goes to 'CCBS Possible diagnostic set'. If 'No', it goes to 'CCBS Possible := False' and 'CCBS Target := False'. From 'CCBS Possible diagnostic set', if 'Yes', it goes to 'CCBS Target parameter set'. If 'No', it goes to 'Alter the GMSC internal variable. CCBS activation is no longer possible' and 'Alter the GMSC internal variable. The variable controls setting of the diagnostic value', then to 'CCBS Possible := False' and 'CCBS Target := False'. From 'CCBS Target parameter set', if 'Yes', it goes to 'CCBS Target := True'. If 'No', it goes to 'Resume Call Handling' and 'CCBS Possible := False' and 'CCBS Target := False'. All paths lead to an end connector.](d2417b04116c354deccb25d98a84a0fb_img.jpg) + +Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Possible 1(1) + +``` + +graph TD + Start([ ]) --> D1{Call Completion Treatment Indicator present in SII2?} + D1 -- No --> D2{Call Completion Treatment Indicator set to Reject Call Completion Service Request?} + D1 -- Yes --> D3{CCBS Possible} + D2 -- Yes --> D3 + D2 -- No --> D3 + D3 -- False --> Release[Release] + D3 -- True --> D4{Reconnect = True or Resume Call = True} + D4 -- Yes --> D5{Cause = Busy or Cause = No circuit channel available} + D4 -- No --> D6{Forwarded call} + D5 -- Yes --> T1[CCBS Target := True] + D5 -- No --> T2[CCBS Target := False] + D6 -- Yes --> D7{CCBS Possible diagnostic set} + D6 -- No --> D8{Received message} + D7 -- Yes --> T3[CCBS Target parameter set] + D7 -- No --> A1[Alter the GMSC internal variable. CCBS activation is no longer possible] + A1 --> A2[Alter the GMSC internal variable. The variable controls setting of the diagnostic value] + A2 --> T4[CCBS Possible := False] + A2 --> T5[CCBS Target := False] + T3 -- Yes --> T6[CCBS Target := True] + T3 -- No --> RH[Resume Call Handling] + RH --> T7[CCBS Possible := False] + RH --> T8[CCBS Target := False] + T1 --> End(( )) + T2 --> End + T4 --> End + T5 --> End + T6 --> End + T7 --> End + T8 --> End + +``` + +Flowchart for Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Possible. The process starts with a connector, followed by a decision 'Call Completion Treatment Indicator present in SII2?'. If 'No', it goes to 'Call Completion Treatment Indicator set to Reject Call Completion Service Request?'. If 'Yes', it goes to 'CCBS Possible'. From 'CCBS Possible', if 'False', it goes to 'Release'. If 'True', it goes to 'Reconnect = True or Resume Call = True'. If 'Yes', it goes to 'Cause = Busy or Cause = No circuit channel available'. If 'Yes', it sets 'CCBS Target := True'. If 'No', it goes to 'Forwarded call'. If 'Yes', it goes to 'CCBS Possible diagnostic set'. If 'No', it goes to 'CCBS Possible := False' and 'CCBS Target := False'. From 'CCBS Possible diagnostic set', if 'Yes', it goes to 'CCBS Target parameter set'. If 'No', it goes to 'Alter the GMSC internal variable. CCBS activation is no longer possible' and 'Alter the GMSC internal variable. The variable controls setting of the diagnostic value', then to 'CCBS Possible := False' and 'CCBS Target := False'. From 'CCBS Target parameter set', if 'Yes', it goes to 'CCBS Target := True'. If 'No', it goes to 'Resume Call Handling' and 'CCBS Possible := False' and 'CCBS Target := False'. All paths lead to an end connector. + +Figure 11.2.1.5: Procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Possible + +### 11.2.2 Processes and procedures in HLR + +Figure 11.2.2.1: Block diagram of HLRB\_processes + +Figure 11.2.2.2: Process HLRB\_Request\_Manager + +This process has the task of controlling the queue and determining whether requests to be processed are present in the queue or not. + +The process has two states "idle" and "active". In the "idle" state there are no "operative" requests in the queue i.e. there are only suspended requests or no requests at all. In the "active" state there is at least one "operative" request in the queue which needs processing. A transition from "idle" to "active" will trigger this process to start the process "HLRB\_Recall\_Manager". Only a transition from "active" to "idle" will result in this process stopping the process "HLRB\_Recall\_Manager". + +Figure 11.2.2.3: Process HLRB\_Request + +This process represents an individual CCBS request on the destination side. Reception of signals on the external interface (SSAP signalling) are handled by this process. + +Retention is handled by this process. The individual request is informed by the Recall manager process about the outcome of the CCBS Call. The individual request is in charge to decide on whether it will stay in the destination queue (retention) or not according to its data stored. + +T7 expiry is controlled by the individual request in that way, that it remembers T7 expiry when it is the selected request (i.e. a CCBS Recall has been initiated for this request). The event is detected after the CCBS Recall when retention has kept the request in the queue. + +Figure 11.2.2.4: Process HLRB\_Recall Manager + +This process is in charge of the recall handling. It is started and stopped by the process "HLRB\_Request\_Manager" depending on whether there are operative requests in the terminating queue or not. + +As soon as this process is started, it will start the process "HLRB\_Monitoring" and wait for a response from this process. The response indicates that user B is idle guarded i.e. a CCBS Recall can be initiated. Hence, the process asks the request manager for selection of an individual request from the terminating queue. + +When an individual process is selected, the process initiates a CCBS Recall via the individual request (since the external interface is tied to the individual request), starts T9 and takes over control of the blocking function while waiting for the CCBS Call. Control of blocking is done by sending the signal "Recall\_Block" to process "HLRB\_Blocking". + +While waiting for the outcome of the CCBS Call, the process will be informed either by the selected individual request in the case of negative outcome (suspension or cancellation, both hidden to the process), or by process "HLRB\_Monitoring" in the case the CCBS Call has reached the terminating PLMN. + +Figure 11.2.2.5: Process HLRB\_Monitoring + +This process takes care of monitoring events received from MSC/VLR and detects potential conditions for initiating a CCBS Recall. + +The process is controlled by the "HLRB\_Recall\_Manager" process which was formerly in charge of detecting the recall condition. + +When the process is started, it invokes the monitoring function in the MSC/VLR and awaits the first event report. The process keeps track of the subscriber state changes by running a state machine which reflects the subscriber states. When there is a transition from subscriber state "not idle" to "idle", then T8 is started. As soon as T8 expires, the process changes state again in order to remember that the subscriber is now idle guarded and a recall could be initiated + +Whether a CCBS Recall is initiated or not depends on whether the process "HLRB\_Recall\_Manager" has asked for this information by sending a "B\_Query" signal to the monitoring process. The process "HLRB\_Monitoring" gives this information only if the "B\_Query" signal has been received. This is done by sending the signal "B\_Guarded" to the Recall Manager and it is only done once per request. The monitoring process keeps track on whether a query was received or not by appropriate state changes. + +As the monitoring process is in charge for the idle guard function, it also controls the blocking of incoming calls during the idle guard time (T8). Hence, when the recall manager process has sent a "B\_Query" (i.e. a CCBS request needs to be processed) then the monitoring process starts the corresponding blocking along with T8. The blocking is only stopped if T8 does not expire. If T8 expires, then blocking is still needed for the following CCBS Recall. The responsibility for controlling the blocking (i.e. switching it off) is given to the recall manager process. + +Figure 11.2.2.6: Process HLRB\_Blocking + +This process controls the CCBS Call delivery reporting when the processes are in the proper state. This means that the reporting functionality of the outcome of the CCBS Call is not blindly triggered whenever there is a terminating CCBS Call. + +The process has three different states: "idle", "Blocking" and "Recall Blocking". The "Idle" state reflects the case when blocking is disabled. In the "Blocking" state all incoming calls are blocked (e.g. while T8 is running). The "Recall Blocking" state allows one CCBS Call to pass, which will trigger the CCBS Call delivery reporting in the MSC/VLR via the TS 23.018 process "SRI\_HLR". When this happens, the process will automatically change back to state "Blocking" as no other CCBS Call is expected for now. + +When the process has detected that destination B is idle, it will start the blocking. Hence, the blocking process will change state to "Blocking". As soon as the process "HLRB\_Recall\_Manager" has initiated a CCBS Recall, it will cause a state change in the blocking process to state "Recall Blocking". When the CCBS Call is received, "result = OK" indication in signal "SRI\_Received\_Ack" will trigger the reporting mechanism for CCBS Call delivery via a PRN request in the TS 23.018 process "SRI\_HLR". + +For Figure 11.2.2.6, sheet 2: The procedure Handle\_CFB is specified in TS 23.018, clause 7.3.2.6. + +Figure 11.2.2.7: Procedure HLRB\_CCBS\_Check\_Interactions + +This procedure checks whether the request is frozen due to the supplementary service interactions. + +Figure 11.2.2.8: Procedure CCBS\_Handling\_HLR + +This procedure is called during Send Routeing Info message handling in the HLR. If blocking is active only CCBS Calls can proceed, others will fail with busy or forward indication. For CCBS Call CCBS Call Indicator is set to the Provide Roaming Number message. + +Figure 11.2.2.9: Procedure CCBS\_Report\_PRN\_Failure + +This procedure is called if Provide Roaming Number returns an error. For CCBS call is then generated an internal call report. + +The handling of multiple requests in HLR B can be further clarified by the diagram shown in figure 11.2.2.1. + +![UML State Machine Diagram for Block HLRB_Processes](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +**Block HLRB\_Processes** 1(1) + +The diagram illustrates the state transitions and events for the HLRB\_Processes block. It features five main states: HLRB\_Request\_Manager(1,1), HLRB\_Request(0,5), HLRB\_Recall\_Manager(1,1), HLRB\_Blocking(1,1), and HLRB\_Monitoring(1,1). Transitions are triggered by specific messages and result in specific actions. The diagram also shows interactions with external entities: Originating network A, CCBS\_Coordinator\_HLR, and HLR. + +``` +stateDiagram-v2 + [*] --> HLRB_Request_Manager(1,1) + HLRB_Request_Manager(1,1) --> HLRB_Request(0,5): Selection_Req + HLRB_Request(0,5) --> HLRB_Request_Manager(1,1): Re-Activated, Deleted, Inactive + HLRB_Request(0,5) --> HLRB_Recall_Manager(1,1): End + HLRB_Recall_Manager(1,1) --> HLRB_Request(0,5): Send_RUF, Recall_Report + HLRB_Recall_Manager(1,1) --> HLRB_Blocking(1,1): Start_Blocking, Recall_Block + HLRB_Recall_Manager(1,1) --> HLRB_Monitoring(1,1): Call_Delivery, B_Guarded + HLRB_Blocking(1,1) --> HLRB_Monitoring(1,1): Start_Blocking, Stop_Blocking + HLRB_Monitoring(1,1) --> HLRB_Blocking(1,1): Start_Blocking, Stop_Blocking + HLRB_Monitoring(1,1) --> HLRB_Recall_Manager(1,1): Event_Report, CCBS_Call_Report + HLRB_Monitoring(1,1) --> HLRB_Request(0,5): Start_Monitoring, Stop_Monitoring, B_Query +``` + +**States:** + +- HLRB\_Request\_Manager(1,1)**: Initial state. Transitions to HLRB\_Request(0,5) on Selection\_Req. Transitions from HLRB\_Request(0,5) on Re-Activated, Deleted, Inactive. +- HLRB\_Request(0,5)**: Transitions to HLRB\_Request\_Manager(1,1) on Re-Activated, Deleted, Inactive. Transitions to HLRB\_Recall\_Manager(1,1) on End. Transitions from HLRB\_Recall\_Manager(1,1) on Send\_RUF, Recall\_Report. +- HLRB\_Recall\_Manager(1,1)**: Transitions to HLRB\_Request(0,5) on Send\_RUF, Recall\_Report. Transitions to HLRB\_Blocking(1,1) on Start\_Blocking, Recall\_Block. Transitions to HLRB\_Monitoring(1,1) on Call\_Delivery, B\_Guarded. +- HLRB\_Blocking(1,1)**: Transitions to HLRB\_Recall\_Manager(1,1) on Start\_Blocking, Recall\_Block. Transitions to HLRB\_Monitoring(1,1) on Start\_Blocking, Stop\_Blocking. Transitions from HLRB\_Monitoring(1,1) on Start\_Blocking, Stop\_Blocking. +- HLRB\_Monitoring(1,1)**: Transitions to HLRB\_Recall\_Manager(1,1) on Event\_Report, CCBS\_Call\_Report. Transitions to HLRB\_Blocking(1,1) on Start\_Blocking, Stop\_Blocking. Transitions from HLRB\_Blocking(1,1) on Start\_Blocking, Stop\_Blocking. Transitions to HLRB\_Request(0,5) on Start\_Monitoring, Stop\_Monitoring, B\_Query. + +**External Interactions:** + +- Originating network A**: + - Sends CCBS\_Request to HLRB\_Request\_Manager(1,1). + - Receives CCBS\_Request\_Ack, CCBS\_Reject\_Request from HLRB\_Request\_Manager(1,1). + - Sends Remote\_User\_Free, CCBS\_Cancel, CCBS\_End to HLRB\_Request(0,5). + - Receives CCBS\_Resume, CCBS\_Cancel, CCBS\_Suspend from HLRB\_Request(0,5). +- HLR**: + - Sends Select\_Request to HLRB\_Request\_Manager(1,1). + - Receives Start\_Recall\_Manager, Stop\_Recall\_Manager, Select\_Request\_Response from HLRB\_Recall\_Manager(1,1). +- CCBS\_Coordinator\_HLR**: + - Sends Start\_Reporting, Stop\_Reporting to HLRB\_Monitoring(1,1). + - Receives Event\_Report, CCBS\_Call\_Report from HLRB\_Monitoring(1,1). + +**Notes:** + +- Instances of process Request can be created by the process Request\_Manager. + +UML State Machine Diagram for Block HLRB\_Processes + +Figure 11.2.2.1: HLRB\_Processes + +#### Description of above signals + +#### Relation Originating Network and HLRB\_Request\_Manager + +CCBS\_Request: When the originating network attempts to activate CCBS, it sends a CCBS\_Request message to HLRB Request Manager. + +CCBS\_Request\_Ack: When the HLRB\_Request\_Manager acknowledges the activation, it sends CCBS\_Request Ack to originating network. + +CCBS\_Reject: If the HLRB\_Request\_Manager does not accept the activation attempt, it sends CCBS\_Reject to the originating network indicating long term or short term denial. + +#### Relation Originating Network and HLRB\_Request + +CCBS\_Suspend: If the originating network suspends a CCBS Request, it sends CCBS\_Suspend to HLRB Request. + +CCBS\_Resume: When a request that was suspended is now resumed, the originating network sends a CCBS\_Resume message to HLRB Request. + +CCBS\_Cancel: When a request is cancelled in the originating network, it sends a CCBS\_Cancel message to HLRB Request. + +Remote\_User\_Free: HLRB\_Request sends Remote\_User\_Free to the originating network to inform the originating network that destination B is now idle. + +CCBS\_Cancel: If a CCBS Request is cancelled in the destination network, HLRB\_Request sends CCBS\_Cancel to the originating network. + +TC\_END: If a CCBS Call is successfully delivered to destination B, then HLRB\_Request ends the dialogue with the originating network by sending a TC\_END message. + +#### Relation HLRB\_Request\_Manager and HLRB\_Request + +Selection\_Request: Once destination B is idle guarded, then the HLRB\_Request\_Manager will select the first non-suspended request in the queue for processing by sending "Select\_Request" to HLRB\_Request. + +Inactive: When a CCBS Request is either suspended or unselectable due to the supplementary service interaction, HLRB\_Request informs HLRB\_Request\_Manager so that the queue status can be updated. + +Re-Activated: When either a suspended CCBS Request is resumed or the supplementary service interaction with the request ends, then HLRB\_Request informs HLRB\_Request\_Manager so that the queue status can be updated. + +Deleted: When a CCBS Request is cancelled, then HLRB\_Request informs HLRB\_Request\_Manager so that the queue status can be updated. + +#### Relation HLRB\_Recall\_Manager and HLRB\_Blocking + +Stop\_Blocking: When the Recall manager process is stopped by the Request Manager process or the Recall manager receives and 'End' signal from the Request manager, the Recall manager sends "Stop\_Blocking" to HLRB\_Blocking. + +Recall\_Block: When a "Send RUF" signal is sent to HLRB\_Request, the HLRB\_Recall\_Manager also sends "Recall Block" to HLRB\_Blocking so that one CCBS Call can be delivered to destination B, but other normal incoming calls are blocked. + +#### **Relation HLRB Recall\_Manager and HLRB\_Request\_Manager** + +Select\_Request: On reception of a "B\_Guarded" signal, the Recall manager sends "Select\_Request" to the Request manager. The Request manager then selects the first non-suspended request in the queue for processing. + +Start\_Recall\_Manager: When a CCBS Request is successfully activated, the Request manager sends "Start\_Recall\_Manager" to HLRB\_Recall\_Manager which subsequently causes the recall manager process to start the monitoring process. + +Stop\_Recall\_Manager: The Request manager can stop the Recall manager process by sending a "Stop\_Recall\_Manager" signal + +Select\_Request\_Response: When the Request manager has selected a request for processing it sends a response to the recall manager causing the recall manager to initiate a CCBS Recall. + +#### **Relation HLRB\_Recall\_Manager and HLRB\_Request** + +Send\_RUF: The Recall manager requests the individual process to send a Remote User Free indication to the originating network by sending a "Send\_RUF" signal to the individual process. + +Recall\_Report: The Recall manager informs the individual process of the result of processing a CCBS Recall by sending a "Recall Report" signal. + +END: When a CCBS Request is suspended or cancelled the HLRB\_Request process sends an "End" signal to the Recall Manager process. + +#### **Relation HLRB\_Recall\_Manager and HLRB\_Monitoring** + +Start\_Monitoring: When the Recall manager process is started by the Request manager process, the Recall manager sends "Start\_Monitoring" to the HLRB\_Monitoring process to request the status of destination B + +Stop\_Monitoring: When the Recall manager process is stopped by the Request manager process, the Recall manager sends "Stop\_Monitoring" to the HLRB\_Monitoring process. + +B\_Query: HLRB\_Recall\_Manager requests the HLRB\_monitoring process to get informed when destination B has become idle guarded. + +#### **Relation HLRB\_Monitoring and HLRB\_Recall\_Manager** + +B\_Guarded: HLRB\_Monitoring informs the HLRB\_Recall\_Manager that destination B has become idle guarded. + +Call\_Delivery: HLRB\_Monitoring informs the HLRB\_Recall\_Manager about the delivery of the CCBS call. + +![State transition diagram for Process HLRB_RequestManager. It shows states Idle, Active, and Deleted, and transitions for CCBS_Request, HLRB_Request, and CCBS_Reject_Request. Includes notes on retention information and signal directions.](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +**Process HLRB\_RequestManager** 1(3) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Idle + Idle --> CCBS_Request_Retain_supported: CCBS service provisioned in destination network + CCBS_Request_Retain_supported --> Decision1{ } + Decision1 -- No --> Reason_long_term_denial: Reason := long term denial + Decision1 -- Yes --> Decision2{queue full} + Reason_long_term_denial --> CCBS_Reject_Request_Reason: CCBS_Reject_Request (Reason) + Decision2 -- Yes --> Reason_short_term_denial: Reason := short term denial + Decision2 -- No --> HLRB_Request + Reason_short_term_denial --> CCBS_Reject_Request_Reason + HLRB_Request --> Update_queue1: Update request queue + Update_queue1 --> Decision3{ } + Decision3 -- No --> Retain_supported_False: Retain_supported := False + Decision3 -- Yes --> CCBS_Request_Ack_Retain_supported + Retain_supported_False --> CCBS_Request_Ack_Retain_supported + CCBS_Request_Ack_Retain_supported --> Store_Retain_supported: Store Retain supported + Store_Retain_supported --> Start_Recall_Manager1: Start_Recall_Manager + Start_Recall_Manager1 --> Active1: Active + CCBS_Reject_Request_Reason --> End1: - + CCBS_Reject_Request_Reason --> Re-Activated + Re-Activated --> Update_queue2: Update request queue + Update_queue2 --> Start_Recall_Manager2: Start_Recall_Manager + Start_Recall_Manager2 --> Active2: Active + Deleted --> Update_queue3: Update request queue + Update_queue3 --> End2: - + +``` + +**Notes:** + +- In this state there are either no CCBS Requests in the queue or the queue contains only inactive (suspended or quiescent) requests +- Signals to and from the left are to and from the originating network unless specified otherwise +- Note: Retention information may be received in the CCBS Request. Refer to ETS 300 358 +- From HLRB\_Request +- CCBS service provisioned in destination network +- Retention supported in the Destination B network +- Note: Retention information may be sent in the CCBS Request Ack Refer to ETS 300 358 +- To HLRB\_Recall\_Manager +- In this state, there is at least one active request + +State transition diagram for Process HLRB\_RequestManager. It shows states Idle, Active, and Deleted, and transitions for CCBS\_Request, HLRB\_Request, and CCBS\_Reject\_Request. Includes notes on retention information and signal directions. + +Figure 11.2.2.2: Process HLRB\_REQUEST\_MANAGER (sheet 1 of 3) + +![Flowchart for Process HLRB_RequestManager (sheet 2 of 3). The process starts at 'Active' and branches into three main paths: 'Deleted' (From HLRB_Request), 'Inactive' (From HLRB_Request), and 'CCBS_Request (Retain_supported)'. The 'Deleted' path leads to 'Update request queue' and then to a 'Queue empty' decision. If 'Yes', it goes to 'Stop_Recall_Manger' (To HLRB_Recall_Manager) and ends at 'Idle'. If 'No', it goes to a central decision diamond. The 'Inactive' path leads to 'Update request queue' and then to the same central decision diamond. The 'CCBS_Request (Retain_supported)' path leads to a 'queue full' decision. If 'Yes', it goes to 'Reason := short term denial' and then to 'CCBS_Reject_Request (Reason)'. If 'No', it goes to 'HLRB_Request', 'Update request queue', and then to a 'Retention supported in the Destination B network' decision. If 'Yes', it goes to 'CCBS_Request_Ack(Retain_supported)'. If 'No', it goes to 'Retain_supported := False' and then to 'CCBS_Request_Ack(Retain_supported)'. The central decision diamond checks if 'Only inactive requests in queue'. If 'Yes', it goes to 'Stop_Recall_Manger' (To HLRB_Recall_Manager) and ends at 'Idle'. If 'No', it goes to 'Continue_Monitoring' (To CCBS_Coordinator_HLR' and ends at '-'. A 'NOTE: Retention information may be sent in the CCBS Request Ack' is associated with the 'CCBS_Request_Ack(Retain_supported)' block. A 'Note: Retention information may be received in the CCBS Request. Refer to ETS 300 358' is associated with the 'CCBS_Request (Retain_supported)' block.](c0ca823603794512478906b302176bca_img.jpg) + +Process HLRB\_RequestManager 2(3) + +``` + +graph TD + Active1([Active]) --> Deleted[Deleted] + Deleted -- "From HLRB_Request" --> UpdateQueue1[Update request queue] + Inactive[Inactive] -- "From HLRB_Request" --> UpdateQueue2[Update request queue] + CCBS_Request[CCBS_Request +(Retain_supported)] -- "Note: Retention information +may be received in the +CCBS Request. +Refer to ETS 300 358" --> QueueFull{queue full} + UpdateQueue1 --> QueueEmpty{Queue empty} + UpdateQueue2 --> CentralDecision{Only inactive +requests in queue} + QueueFull -- Yes --> Reason["Reason := +short term +denial"] + QueueFull -- No --> HLRB_Request[HLRB_Request] + HLRB_Request --> UpdateQueue3[Update request queue] + UpdateQueue3 --> RetainSupported{Retention supported +in the Destination B +network} + RetainSupported -- Yes --> CCBS_Ack[CCBS_Request_Ack +(Retain_supported)] + RetainSupported -- No --> RetainFalse["Retain_supported +:= False"] + RetainFalse --> CCBS_Ack + CCBS_Ack -- "NOTE: Retention information +may be sent in the CCBS +Request Ack +Refer to ETS 300 358" --> StoreRetain[Store Retain +supported] + StoreRetain --> Active2([Active]) + Reason --> CCBS_Reject[CCBS_Reject_Request +(Reason)] + CCBS_Reject --> Active2 + QueueEmpty -- Yes --> StopRecall[Stop_Recall_ +Manger] + StopRecall -- "To HLRB_Recall_Manager" --> Idle([Idle]) + QueueEmpty -- No --> CentralDecision + CentralDecision -- Yes --> StopRecall + CentralDecision -- No --> ContinueMonitoring[Continue_ +Monitoring] + ContinueMonitoring -- "To CCBS_Coordinator_ +HLR" --> EndDash([-]) + +``` + +Flowchart for Process HLRB\_RequestManager (sheet 2 of 3). The process starts at 'Active' and branches into three main paths: 'Deleted' (From HLRB\_Request), 'Inactive' (From HLRB\_Request), and 'CCBS\_Request (Retain\_supported)'. The 'Deleted' path leads to 'Update request queue' and then to a 'Queue empty' decision. If 'Yes', it goes to 'Stop\_Recall\_Manger' (To HLRB\_Recall\_Manager) and ends at 'Idle'. If 'No', it goes to a central decision diamond. The 'Inactive' path leads to 'Update request queue' and then to the same central decision diamond. The 'CCBS\_Request (Retain\_supported)' path leads to a 'queue full' decision. If 'Yes', it goes to 'Reason := short term denial' and then to 'CCBS\_Reject\_Request (Reason)'. If 'No', it goes to 'HLRB\_Request', 'Update request queue', and then to a 'Retention supported in the Destination B network' decision. If 'Yes', it goes to 'CCBS\_Request\_Ack(Retain\_supported)'. If 'No', it goes to 'Retain\_supported := False' and then to 'CCBS\_Request\_Ack(Retain\_supported)'. The central decision diamond checks if 'Only inactive requests in queue'. If 'Yes', it goes to 'Stop\_Recall\_Manger' (To HLRB\_Recall\_Manager) and ends at 'Idle'. If 'No', it goes to 'Continue\_Monitoring' (To CCBS\_Coordinator\_HLR' and ends at '-'. A 'NOTE: Retention information may be sent in the CCBS Request Ack' is associated with the 'CCBS\_Request\_Ack(Retain\_supported)' block. A 'Note: Retention information may be received in the CCBS Request. Refer to ETS 300 358' is associated with the 'CCBS\_Request (Retain\_supported)' block. + +Figure 11.2.2.2: Process HLRB\_REQUEST\_MANAGER (sheet 2 of 3) + +![State transition diagram for Process HLRB_RequestManager. The diagram shows a state transition from 'Active' to 'Select_Request' (triggered by 'From HLRB_Recall_Manager'), followed by 'Select the first active request', 'Selection_Request' (sent 'To HLRB_Request'), and 'Select_Request Response (Request)' (sent 'To HLRB_Recall_Manager'). A transition from 'Re-Activated' (triggered by 'From HLRB_request') leads to 'Update request queue'. Both 'Update request queue' and the response message lead to a final state.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +Process HLRB\_RequestManager + +3(3) + +``` +stateDiagram-v2 + [*] --> Active + Active --> Select_Request : From HLRB_Recall_Manager + Select_Request --> Select the first active request + Select the first active request --> Selection_Request : To HLRB_Request + Selection_Request --> Select_Request_Response : To HLRB_Recall_Manager + Select_Request_Response --> [*] + Re-Activated --> Update request queue + Update request queue --> [*] +``` + +State transition diagram for Process HLRB\_RequestManager. The diagram shows a state transition from 'Active' to 'Select\_Request' (triggered by 'From HLRB\_Recall\_Manager'), followed by 'Select the first active request', 'Selection\_Request' (sent 'To HLRB\_Request'), and 'Select\_Request Response (Request)' (sent 'To HLRB\_Recall\_Manager'). A transition from 'Re-Activated' (triggered by 'From HLRB\_request') leads to 'Update request queue'. Both 'Update request queue' and the response message lead to a final state. + +Figure 11.2.2.2: Process HLRB\_REQUEST\_MANAGER (sheet 3 of 3) + +![Flowchart for Process HLRB_Request. It starts with 'Start T7' leading to 'Operative'. From 'Operative', it branches to 'Selection_Request' (from HLRB_Request_Manager) leading to 'Selected', and 'SS_Event' (from Supplementary service handling) leading to 'HLRB_CCBS_Check_Interactions'. From 'HLRB_CCBS_Check_Interactions', it goes to 'Result'. If 'Fail', it goes to 'Inactive' (to HLRB_Request_Manager) leading to 'Quiescent Operative'. If 'Pass', it leads to 'Operative'. A note indicates signals are from the originating network unless specified otherwise.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +Process HLRB\_Request + +1(6) + +``` +graph TD; Start([Start T7]) --> Operative1([Operative]); Operative1 --> Selection_Request{{Selection_Request}}; Selection_Request --> Selected([Selected]); Selection_Request -.-> From_HLRB[From HLRB_Request_Manager]; Operative1 --> SS_Event{{SS_Event}}; SS_Event --> HLRB_CCBS[HLRB_CCBS_Check_Interactions]; SS_Event -.-> From_SS[From Supplementary service handling indicating that service status has been changed]; HLRB_CCBS --> Result{Result}; Result -- Fail --> Inactive{{Inactive}}; Inactive --> Quiescent([Quiescent Operative]); Inactive -.-> To_HLRB[To HLRB_Request_Manager]; Result -- Pass --> Operative2([Operative]); +``` + +Signals to and from the left are to and from the originating network unless specified otherwise + +Flowchart for Process HLRB\_Request. It starts with 'Start T7' leading to 'Operative'. From 'Operative', it branches to 'Selection\_Request' (from HLRB\_Request\_Manager) leading to 'Selected', and 'SS\_Event' (from Supplementary service handling) leading to 'HLRB\_CCBS\_Check\_Interactions'. From 'HLRB\_CCBS\_Check\_Interactions', it goes to 'Result'. If 'Fail', it goes to 'Inactive' (to HLRB\_Request\_Manager) leading to 'Quiescent Operative'. If 'Pass', it leads to 'Operative'. A note indicates signals are from the originating network unless specified otherwise. + +Figure 11.2.2.3: Process HLRB\_REQUEST (sheet 1 of 6) + +![EPC diagram for Process HLRB_Request. It starts with a function block '(Selected)', which branches into two parallel paths. The left path contains a function block 'T7_Expiry', followed by an EPC function block 'Reason := T7_Expiry', and then a function block 'CCBS_Cancel (Reason)'. The right path contains a function block 'CCBS_Cancel'. Both paths converge at a function block 'Deleted', which is connected to an EPC function block 'To HLRB_Request_Manager'. The process ends with an end connector symbol.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +Process HLRB\_Request + +2(6) + +``` +graph TD; A["*(Selected)"] --> B["T7_Expiry"]; A --> C["CCBS_Cancel"]; B --> D["Reason := T7_Expiry"]; D --> E["CCBS_Cancel (Reason)"]; E --> F["Deleted"]; C --> F; F --> G["To HLRB_Request_Manager"]; F --> H[End]; +``` + +EPC diagram for Process HLRB\_Request. It starts with a function block '(Selected)', which branches into two parallel paths. The left path contains a function block 'T7\_Expiry', followed by an EPC function block 'Reason := T7\_Expiry', and then a function block 'CCBS\_Cancel (Reason)'. The right path contains a function block 'CCBS\_Cancel'. Both paths converge at a function block 'Deleted', which is connected to an EPC function block 'To HLRB\_Request\_Manager'. The process ends with an end connector symbol. + +Figure 11.2.2.3: Process HLRB\_REQUEST (sheet 2 of 6) + +![Flowchart for Process HLRB_Request. It starts with 'Selected' leading to a horizontal line. From this line, five paths emerge: 1) 'Send_RUF' (with 'From HLRB_Recall_Manager') leading to 'Remote_User_Free' and then to a connector '-'. 2) 'CCBS_Suspend' leading to 'Inactive' (with 'To HLRB_Request_Manager') leading to 'End' (with 'To HLRB_Recall_Manager') leading to 'Suspended'. 3) 'CCBS_Cancel' leading to 'Deleted' (with 'To HLRB_Request_Manager') leading to 'End' (with 'To HLRB_Recall_Manager') leading to 'Stop T7' and then an error symbol (X). 4) 'T7_Expiry' (no associated manager). 5) 'SS_Event' (with 'From Supplementary service handling indicating that service status has been changed').](e18841eb4a995df8354a793459e12fd0_img.jpg) + +Process HLRB\_Request 3(6) + +``` +graph TD; Selected([Selected]) --> H1(( )); H1 --> Send_RUF[Send_RUF]; Send_RUF -.-> From_HLRB_Recall_Manager1[From HLRB_Recall_Manager]; Send_RUF --> Remote_User_Free{Remote_User_Free}; Remote_User_Free --> Connector1([ - ]); H1 --> CCBS_Suspend[CCBS_Suspend]; CCBS_Suspend --> Inactive[Inactive]; Inactive -.-> To_HLRB_Request_Manager1[To HLRB_Request_Manager]; Inactive --> End1[End]; End1 -.-> To_HLRB_Recall_Manager1[To HLRB_Recall_Manager]; End1 --> Suspended([Suspended]); H1 --> CCBS_Cancel[CCBS_Cancel]; CCBS_Cancel --> Deleted[Deleted]; Deleted -.-> To_HLRB_Request_Manager2[To HLRB_Request_Manager]; Deleted --> End2[End]; End2 -.-> To_HLRB_Recall_Manager2[To HLRB_Recall_Manager]; End2 --> Stop_T7[Stop T7]; Stop_T7 --> Error((X)); H1 --> T7_Expiry[/T7_Expiry/]; H1 --> SS_Event[/SS_Event/]; SS_Event -.-> From_SSH[From Supplementary service handling indicating that service status has been changed]; +``` + +Flowchart for Process HLRB\_Request. It starts with 'Selected' leading to a horizontal line. From this line, five paths emerge: 1) 'Send\_RUF' (with 'From HLRB\_Recall\_Manager') leading to 'Remote\_User\_Free' and then to a connector '-'. 2) 'CCBS\_Suspend' leading to 'Inactive' (with 'To HLRB\_Request\_Manager') leading to 'End' (with 'To HLRB\_Recall\_Manager') leading to 'Suspended'. 3) 'CCBS\_Cancel' leading to 'Deleted' (with 'To HLRB\_Request\_Manager') leading to 'End' (with 'To HLRB\_Recall\_Manager') leading to 'Stop T7' and then an error symbol (X). 4) 'T7\_Expiry' (no associated manager). 5) 'SS\_Event' (with 'From Supplementary service handling indicating that service status has been changed'). + +Figure 11.2.2.3: Process HLRB\_REQUEST (sheet 3 of 6) + +![Flowchart for Process HLRB_Request. It starts with 'Selected' (oval), followed by 'Recall_Report (Outcome)' (input) from 'From HLRB_Recall_Manager'. A decision diamond 'Outcome' has three paths: 'NDUB' leads to 'Retain supported' (decision); 'Failure' leads to 'CCBS_Cancel' (output); 'Success' leads to 'CCBS_End' (output). 'Retain supported' has 'True' leading to 'Operative' (oval) and 'False' leading to 'CCBS_Cancel'. 'CCBS_Cancel', 'CCBS_End', and a 'Reason:= Outcome' (process) block (reached via 'T9_Expiry' from 'Success') all lead to 'Deleted' (output) to 'To HLRB_Request_Manager'. The process ends at an exit symbol (X).](0b998e3ad8f9d104768642612605cb35_img.jpg) + +Process HLRB\_Request 4(6) + +``` +graph TD; Selected([Selected]) --> Recall_Report{Recall_Report (Outcome)}; Recall_Report -.-> From_HLRB_Recall_Manager[From HLRB_Recall_Manager]; Recall_Report --> Outcome{Outcome}; Outcome -- NDUB --> Retain_supported{Retain supported}; Outcome -- Failure --> CCBS_Cancel{CCBS_Cancel}; Outcome -- Success --> CCBS_End{CCBS_End}; Outcome -- T9_Expiry --> Reason[Reason:= Outcome]; Retain_supported -- True --> Operative([Operative]); Retain_supported -- False --> CCBS_Cancel; CCBS_Cancel --> Deleted{Deleted}; CCBS_End --> Deleted; Reason --> CCBS_Cancel_Reason{CCBS_Cancel (Reason)}; CCBS_Cancel_Reason --> Deleted; Deleted -.-> To_HLRB_Request_Manager[To HLRB_Request_Manager]; Deleted --> Exit((X)); +``` + +Flowchart for Process HLRB\_Request. It starts with 'Selected' (oval), followed by 'Recall\_Report (Outcome)' (input) from 'From HLRB\_Recall\_Manager'. A decision diamond 'Outcome' has three paths: 'NDUB' leads to 'Retain supported' (decision); 'Failure' leads to 'CCBS\_Cancel' (output); 'Success' leads to 'CCBS\_End' (output). 'Retain supported' has 'True' leading to 'Operative' (oval) and 'False' leading to 'CCBS\_Cancel'. 'CCBS\_Cancel', 'CCBS\_End', and a 'Reason:= Outcome' (process) block (reached via 'T9\_Expiry' from 'Success') all lead to 'Deleted' (output) to 'To HLRB\_Request\_Manager'. The process ends at an exit symbol (X). + +Figure 11.2.2.3: Process HLRB\_REQUEST (sheet 4 of 6) + +![Flowchart for Process HLRB_Request. It starts with a 'Suspended' state. Two paths lead from 'Suspended': one through 'CCBS_Resume' to 'Re-Activated' (with an output 'To HLRB_Request_Manager') and then to 'Operative'; the other through 'SS_Event' (with an input 'From Supplementary service handling indicating that service status has been changed') to 'HLRB_CCBS_Check_Interactions', then to a 'Result' decision. From 'Result', a 'Fail' leads to 'Quiescent Suspended' and a 'Pass' leads to 'Suspended'.](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) + +Process HLRB\_Request 5(6) + +``` +graph TD; Suspended1([Suspended]) --> CCBS_Resume{{CCBS_Resume}}; Suspended1 --> SS_Event{{SS_Event}}; SS_Event -.-> SS_Event_Note[From Supplementary service handling indicating that service status has been changed]; CCBS_Resume --> Re-Activated{{Re-Activated}}; Re-Activated -.-> Re-Activated_Note[To HLRB_Request_Manager]; Re-Activated --> Operative([Operative]); SS_Event --> HLRB_CCBS_Check_Interactions[HLRB_CCBS_Check_Interactions]; HLRB_CCBS_Check_Interactions --> Result{Result}; Result -- Fail --> Quiescent_Suspended([Quiescent Suspended]); Result -- Pass --> Suspended2([Suspended]); +``` + +Flowchart for Process HLRB\_Request. It starts with a 'Suspended' state. Two paths lead from 'Suspended': one through 'CCBS\_Resume' to 'Re-Activated' (with an output 'To HLRB\_Request\_Manager') and then to 'Operative'; the other through 'SS\_Event' (with an input 'From Supplementary service handling indicating that service status has been changed') to 'HLRB\_CCBS\_Check\_Interactions', then to a 'Result' decision. From 'Result', a 'Fail' leads to 'Quiescent Suspended' and a 'Pass' leads to 'Suspended'. + +Figure 11.2.2.3: Process HLRB\_REQUEST (sheet 5 of 6) + +![Flowchart for Process HLRB_Request (sheet 6 of 6). It shows two main paths: one starting from 'Quiescent Operative' and another from 'Quiescent Suspended'. Both paths involve an 'SS_Event' (From Supplementary service handling indicating that service status has been changed), followed by 'HLRB_CCBS_Check_Interactions'. A 'Result' decision follows. If 'Pass', the 'Quiescent Operative' path leads to 'Re-Activated' (To HLRB_Request_Manager) and then to 'Operative', while the 'Quiescent Suspended' path leads to 'Suspended'. If 'Fail', both paths return to their initial 'Quiescent' states. A third path from 'Quiescent Suspended' goes through 'CCBS_Resume' to 'Quiescent Operative'.](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) + +Process HLRB\_Request 6(6) + +``` +graph TD; subgraph Path1 [ ]; QO1([Quiescent Operative]) --> SE1{{SS_Event}}; SE1 -.-> SE1_desc[From Supplementary service handling indicating that service status has been changed]; SE1 --> HCI1[HLRB_CCBS_Check_Interactions]; HCI1 --> R1{Result}; R1 -- Pass --> RA{{Re-Activated}}; RA -.-> RA_desc[To HLRB_Request_Manager]; RA --> O([Operative]); R1 -- Fail --> QO1; end; subgraph Path2 [ ]; QS1([Quiescent Suspended]) --> SE2{{SS_Event}}; SE2 -.-> SE2_desc[From Supplementary service handling indicating that service status has been changed]; SE2 --> HCI2[HLRB_CCBS_Check_Interactions]; HCI2 --> R2{Result}; R2 -- Pass --> S([Suspended]); R2 -- Fail --> QS1; end; QS2([Quiescent Suspended]) --> CR{{CCBS_Resume}}; CR --> QO2([Quiescent Operative]); +``` + +Flowchart for Process HLRB\_Request (sheet 6 of 6). It shows two main paths: one starting from 'Quiescent Operative' and another from 'Quiescent Suspended'. Both paths involve an 'SS\_Event' (From Supplementary service handling indicating that service status has been changed), followed by 'HLRB\_CCBS\_Check\_Interactions'. A 'Result' decision follows. If 'Pass', the 'Quiescent Operative' path leads to 'Re-Activated' (To HLRB\_Request\_Manager) and then to 'Operative', while the 'Quiescent Suspended' path leads to 'Suspended'. If 'Fail', both paths return to their initial 'Quiescent' states. A third path from 'Quiescent Suspended' goes through 'CCBS\_Resume' to 'Quiescent Operative'. + +Figure 11.2.2.3: Process HLRB\_REQUEST (sheet 6 of 6) + +![State machine diagram for Process HLRB_RecallManager. It shows two main state transitions starting from an initial state. The left path goes from an initial state to Idle, then to Wait_For_B_Guarded, then branches into two options: one leading to B_Guarded (From HLRB_Monitoring) -> Select_Request (To HLRB_Request_Manager) -> Wait_For_Selection_Request, and another leading to Stop_Recall_Manager (From HLRB_Request_Manager) -> Stop_Monitoring (To HLRB_Monitoring) -> Stop_Blocking (To HLRB_Blocking) -> Idle. The right path starts at Idle, goes through Start_Recall_Manager (From HLRB_Request_Manager) -> Start_Monitoring (To HLRB_Monitoring) -> B_Query (To HLRB_Monitoring) -> Wait_For_B_Guarded.](a5404b7275b06497eecf9b5883604753_img.jpg) + +Process HLRB\_RecallManager 1(3) + +``` +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> Wait_For_B_Guarded1[Wait_For_B_Guarded] + Wait_For_B_Guarded1 --> B_Guarded[From HLRB_Monitoring] + B_Guarded --> Select_Request[To HLRB_Request_Manager] + Select_Request --> Wait_For_Selection_Request[Wait_For_Selection_Request] + Wait_For_B_Guarded1 --> Stop_Recall_Manager[From HLRB_Request_Manager] + Stop_Recall_Manager --> Stop_Monitoring[To HLRB_Monitoring] + Stop_Monitoring --> Stop_Blocking[To HLRB_Blocking] + Stop_Blocking --> Idle2[Idle] + Idle3[Idle] --> Start_Recall_Manager[From HLRB_Request_Manager] + Start_Recall_Manager --> Start_Monitoring[To HLRB_Monitoring] + Start_Monitoring --> B_Query[To HLRB_Monitoring] + B_Query --> Wait_For_B_Guarded1 +``` + +State machine diagram for Process HLRB\_RecallManager. It shows two main state transitions starting from an initial state. The left path goes from an initial state to Idle, then to Wait\_For\_B\_Guarded, then branches into two options: one leading to B\_Guarded (From HLRB\_Monitoring) -> Select\_Request (To HLRB\_Request\_Manager) -> Wait\_For\_Selection\_Request, and another leading to Stop\_Recall\_Manager (From HLRB\_Request\_Manager) -> Stop\_Monitoring (To HLRB\_Monitoring) -> Stop\_Blocking (To HLRB\_Blocking) -> Idle. The right path starts at Idle, goes through Start\_Recall\_Manager (From HLRB\_Request\_Manager) -> Start\_Monitoring (To HLRB\_Monitoring) -> B\_Query (To HLRB\_Monitoring) -> Wait\_For\_B\_Guarded. + +Figure 11.2.2.4: Process HLRB\_RECALL\_MANAGER (sheet 1 of 3) + +![State transition diagram for Process HLRB_RecallManager. It shows two main paths starting from a common 'Wait_For_Selectio_Response' state. The left path involves 'Select_Request_Response (Request)' from HLRB_Request_Manager, followed by 'Send_RUF' to HLRB_Request, 'Recall_Block' to HLRB_Blocking, 'Start T9', and ending at 'Wait_For_CCBS_Call'. The right path involves 'Stop_Recall_Manager' from HLRB_Request_Manager, followed by 'Stop_Monitoring' to HLRB_Monitoring, 'Stop_Blocking' to HLRB_Blocking, and ending at 'Idle'.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +Process HLRB\_RecallManager 2(3) + +``` +stateDiagram-v2 + [*] --> Wait_For_Selectio_Response + state "Wait_For_Selectio_Response" as Wait_For_Selectio_Response + state "Select_Request_Response (Request)" as Select_Request_Response + state "Send_RUF" as Send_RUF + state "Recall_Block" as Recall_Block + state "Start T9" as Start_T9 + state "Wait_For_CCBS_Call" as Wait_For_CCBS_Call + state "Stop_Recall_Manager" as Stop_Recall_Manager + state "Stop_Monitoring" as Stop_Monitoring + state "Stop_Blocking" as Stop_Blocking + state "Idle" as Idle + + Wait_For_Selectio_Response --> Select_Request_Response + Select_Request_Response --> Send_RUF + Send_RUF --> Recall_Block + Recall_Block --> Start_T9 + Start_T9 --> Wait_For_CCBS_Call + + Wait_For_Selectio_Response --> Stop_Recall_Manager + Stop_Recall_Manager --> Stop_Monitoring + Stop_Monitoring --> Stop_Blocking + Stop_Blocking --> Idle +``` + +From HLRB\_Request\_Manager + +To HLRB\_Request + +To HLRB\_Blocking + +From HLRB\_Request\_Manager + +To HLRB\_Monitoring + +To HLRB\_Blocking + +State transition diagram for Process HLRB\_RecallManager. It shows two main paths starting from a common 'Wait\_For\_Selectio\_Response' state. The left path involves 'Select\_Request\_Response (Request)' from HLRB\_Request\_Manager, followed by 'Send\_RUF' to HLRB\_Request, 'Recall\_Block' to HLRB\_Blocking, 'Start T9', and ending at 'Wait\_For\_CCBS\_Call'. The right path involves 'Stop\_Recall\_Manager' from HLRB\_Request\_Manager, followed by 'Stop\_Monitoring' to HLRB\_Monitoring, 'Stop\_Blocking' to HLRB\_Blocking, and ending at 'Idle'. + +Figure 11.2.2.4: Process HLRB\_RECALL\_MANAGER (sheet 2 of 3) + +![State transition diagram for Process HLRB_RecallManager. It shows two main state machines. The left one starts at 'Wait_For_CCBS_Call', goes to 'End' (receiving 'From HLRB_Request'), then 'Stop T9', then 'Stop_Blocking' (sending 'To HLRB_Blocking'), then 'B_Query' (sending 'To HLRB_Monitoring'), and finally 'Wait_For_B_Guarded'. The right one starts at 'Stop_Recall_Manager' (receiving 'From HLRB_Request_Manager'), goes to 'Stop T9', then 'Stop_Monitoring' (sending 'To HLRB_Monitoring'), then 'Stop_Blocking' (sending 'To HLRB_Blocking'), and finally 'Idle'. A central 'Call_Delivery (Outcome)' (receiving 'From HLRB_Monitoring or CCBS_Report_PRN_Failure') leads to 'Stop T9', which then leads to 'Recall_Report (Outcome)' (sending 'To HLRB_Request'). A 'T9 Expiry' event leads to 'Outcome := T9 Expiry', which also leads to 'Recall_Report (Outcome)'.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +Process HLRB\_RecallManager 3(3) + +``` +stateDiagram-v2 + [*] --> Wait_For_CCBS_Call + state "Wait_For_CCBS_Call" as Wait_For_CCBS_Call + state "End" as End + state "Stop T9" as Stop_T9_1[Stop T9] + state "Stop_Blocking" as Stop_Blocking_1[Stop_Blocking] + state "B_Query" as B_Query + state "Wait_For_B_Guarded" as Wait_For_B_Guarded + + state "Stop_Recall_Manager" as Stop_Recall_Manager + state "Stop T9" as Stop_T9_2[Stop T9] + state "Stop_Monitoring" as Stop_Monitoring + state "Stop_Blocking" as Stop_Blocking_2[Stop_Blocking] + state "Idle" as Idle + + state "Call_Delivery (Outcome)" as Call_Delivery + state "T9 Expiry" as T9_Expiry + state "Outcome := T9 Expiry" as Outcome_T9 + state "Recall_Report (Outcome)" as Recall_Report + + Wait_For_CCBS_Call --> End + End --> Stop_T9_1 + Stop_T9_1 --> Stop_Blocking_1 + Stop_Blocking_1 --> B_Query + B_Query --> Wait_For_B_Guarded + + Stop_Recall_Manager --> Stop_T9_2 + Stop_T9_2 --> Stop_Monitoring + Stop_Monitoring --> Stop_Blocking_2 + Stop_Blocking_2 --> Idle + + Call_Delivery --> Stop_T9_2 + T9_Expiry --> Outcome_T9 + Outcome_T9 --> Recall_Report + Recall_Report --> Stop_T9_2 + + Note right of End: From HLRB_Request + Note right of Call_Delivery: From HLRB_Monitoring or CCBS_Report_PRN_Failure + Note right of Stop_Recall_Manager: From HLRB_Request_Manager + Note right of Stop_Blocking_1: To HLRB_Blocking + Note right of B_Query: To HLRB_Monitoring + Note right of Stop_Monitoring: To HLRB_Monitoring + Note right of Stop_Blocking_2: To HLRB_Blocking + Note right of Recall_Report: To HLRB_Request +``` + +State transition diagram for Process HLRB\_RecallManager. It shows two main state machines. The left one starts at 'Wait\_For\_CCBS\_Call', goes to 'End' (receiving 'From HLRB\_Request'), then 'Stop T9', then 'Stop\_Blocking' (sending 'To HLRB\_Blocking'), then 'B\_Query' (sending 'To HLRB\_Monitoring'), and finally 'Wait\_For\_B\_Guarded'. The right one starts at 'Stop\_Recall\_Manager' (receiving 'From HLRB\_Request\_Manager'), goes to 'Stop T9', then 'Stop\_Monitoring' (sending 'To HLRB\_Monitoring'), then 'Stop\_Blocking' (sending 'To HLRB\_Blocking'), and finally 'Idle'. A central 'Call\_Delivery (Outcome)' (receiving 'From HLRB\_Monitoring or CCBS\_Report\_PRN\_Failure') leads to 'Stop T9', which then leads to 'Recall\_Report (Outcome)' (sending 'To HLRB\_Request'). A 'T9 Expiry' event leads to 'Outcome := T9 Expiry', which also leads to 'Recall\_Report (Outcome)'. + +Figure 11.2.2.4: Process HLRB\_RECALL\_MANAGER (sheet 3 of 3) + +![Flowchart for Process HLRB_Monitoring. It starts with an oval connector, leading to an 'Idle' state (oval). From 'Idle', it goes to a 'Start_Monitoring' process (chevron), which receives input 'From HLRB_Recall_Manager'. This leads to a decision diamond 'CCBS supported in VLR'. If 'No', it goes to 'Wait' (oval). If 'Yes', it goes to 'Start_Reporting' (chevron), which outputs 'To CCBS_Coordinator_HLR', and then to 'Wait' (oval).](17431d8b59408f09df7552d8bdbaa015_img.jpg) + +Process HLRB\_Monitoring + +1(7) + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> StartMonitoring{{Start_Monitoring}}; StartMonitoring -.-> FromHLRB[From HLRB_Recall_Manager]; StartMonitoring --> Decision{CCBS supported in VLR}; Decision -- No --> Wait1([Wait]); Decision -- Yes --> StartReporting{{Start_Reporting}}; StartReporting -.-> ToCCBS[To CCBS_Coordinator_HLR]; StartReporting --> Wait2([Wait]); +``` + +Flowchart for Process HLRB\_Monitoring. It starts with an oval connector, leading to an 'Idle' state (oval). From 'Idle', it goes to a 'Start\_Monitoring' process (chevron), which receives input 'From HLRB\_Recall\_Manager'. This leads to a decision diamond 'CCBS supported in VLR'. If 'No', it goes to 'Wait' (oval). If 'Yes', it goes to 'Start\_Reporting' (chevron), which outputs 'To CCBS\_Coordinator\_HLR', and then to 'Wait' (oval). + +Figure 11.2.2.5: Process HLRB\_MONITORING (sheet 1 of 7) + +![State transition diagram for Process HLRB_Monitoring. The diagram is split into two sections. The top section starts with a 'Wait' state, leading to an 'Event_Report (Status)' from 'CCBS_Coordinator_HLR'. A 'Status' decision diamond follows, with 'CCBS_Idle' leading to 'Start T8' -> 'Start_Blocking' (to 'HLRB_Blocking') -> 'B_Idle No_B_Query', and 'CCBS_Not_Idle CCBS_Not_Reachable' leading to 'B_Not_Idle No_B_Query'. A 'B_Query' from 'HLRB_Recall_Manager' and a 'Stop_Monitoring' from 'HLRB_Recall_Manager' (leading to 'Stop_Reporting' to 'CCBS_Coordinator_HLR' -> 'Idle') also originate from the 'Wait' state. The bottom section starts with a 'Wait' state, leading to a 'Location Update' from 'CCBS_Coordinator_HLR'. A decision diamond 'CCBS supported in the MSCVLR' follows, with 'Yes' leading to 'Start_Reporting' (to 'CCBS_Coordinator_HLR') and 'No' leading to an empty state symbol.](6e9d059430baba0c363e33749f68b107_img.jpg) + +Process HLRB\_Monitoring 2(7) + +``` +graph TD + subgraph Top_Section + W1([Wait]) --> ER{Event_Report +(Status)} + ER -.-> F1[From CCBS_Coordinator_HLR] + ER --> S{Status} + S -- CCBS_Idle --> ST8[Start T8] + ST8 --> SB{Start_Blocking} + SB -.-> TH[To HLRB_Blocking] + SB --> BI([B_Idle +No_B_Query]) + S -- "CCBS_Not_Idle +CCBS_Not_Reachable" --> BNI([B_Not_Idle +No_B_Query]) + W1 --> BQ[/B_Query/] + BQ -.-> F2[From HLRB_Recall_Manager] + W1 --> SM{Stop_Monitoring} + SM -.-> F3[From HLRB_Recall_Manager] + SM --> SR{Stop_Reporting} + SR -.-> F4[To CCBS_Coordinator_HLR] + SR --> I([Idle]) + end + subgraph Bottom_Section + W2([Wait]) --> LU{Location Update} + LU -.-> F5[From CCBS_Coordinator_HLR] + LU --> D{CCBS supported +in the MSCVLR} + D -- Yes --> ST{Start_Reporting} + ST -.-> F6[To CCBS_Coordinator_HLR] + D -- No --> End([-]) + end +``` + +State transition diagram for Process HLRB\_Monitoring. The diagram is split into two sections. The top section starts with a 'Wait' state, leading to an 'Event\_Report (Status)' from 'CCBS\_Coordinator\_HLR'. A 'Status' decision diamond follows, with 'CCBS\_Idle' leading to 'Start T8' -> 'Start\_Blocking' (to 'HLRB\_Blocking') -> 'B\_Idle No\_B\_Query', and 'CCBS\_Not\_Idle CCBS\_Not\_Reachable' leading to 'B\_Not\_Idle No\_B\_Query'. A 'B\_Query' from 'HLRB\_Recall\_Manager' and a 'Stop\_Monitoring' from 'HLRB\_Recall\_Manager' (leading to 'Stop\_Reporting' to 'CCBS\_Coordinator\_HLR' -> 'Idle') also originate from the 'Wait' state. The bottom section starts with a 'Wait' state, leading to a 'Location Update' from 'CCBS\_Coordinator\_HLR'. A decision diamond 'CCBS supported in the MSCVLR' follows, with 'Yes' leading to 'Start\_Reporting' (to 'CCBS\_Coordinator\_HLR') and 'No' leading to an empty state symbol. + +Figure 11.2.2.5: Process HLRB\_MONITORING (sheet 2 of 7) + +![State transition diagram for Process HLRB_Monitoring. It consists of two main parts. The top part shows transitions from state 'B_Not_Idle No_B_Query' based on 'Event_Report (Status)' from 'CCBS_Coordinator_HLR', 'B_Query' from 'HLRB_Recall_Manager', and 'Stop_Monitoring' from 'HLRB_Recall_Manager'. The bottom part shows transitions from state 'B_Not_Idle No_B_Query' based on 'CCBS_Call_Report (Outcome, Status)' from 'CCBS_Coordinator_HLR', 'Call_Delivery (Outcome)' to 'HLRB_Recall_Manager', and 'Location Update' from 'CCBS_Coordinator_HLR'. Various decision diamonds like 'Status', 'CCBS_Idle', and 'CCBS supported in the MSCVLR' lead to states like 'B_Idle No_B_Query', 'Idle', or back to 'B_Not_Idle No_B_Query'.](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +Process HLRB\_Monitoring 3(7) + +``` +stateDiagram-v2 + [*] --> B_Not_Idle_No_B_Query_1: B_Not_Idle No_B_Query + B_Not_Idle_No_B_Query_1 --> Event_Report_Status: Event_Report (Status) + Event_Report_Status --> Status_1: Status + Status_1 --> CCBS_Idle_1: CCBS_Idle + Status_1 --> CCBS_Not_Idle_CCBS_Not_Reachable_1: CCBS_Not_Idle CCBS_Not_Reachable + CCBS_Idle_1 --> Start_T8: Start T8 + Start_T8 --> Start_Blocking: Start_Blocking + Start_Blocking --> B_Idle_No_B_Query_1: B_Idle No_B_Query + CCBS_Not_Idle_CCBS_Not_Reachable_1 --> To_HLRB_Blocking: To HLRB_Blocking + To_HLRB_Blocking --> B_Not_Idle_No_B_Query_1 + B_Not_Idle_No_B_Query_1 --> B_Query: B_Query + B_Query --> B_Not_Idle_B_Query_1: B_Not_Idle B_Query + B_Not_Idle_No_B_Query_1 --> Stop_Monitoring: Stop_Monitoring + Stop_Monitoring --> Stop_Reporting: Stop_Reporting + Stop_Reporting --> Idle: Idle + + [*] --> B_Not_Idle_No_B_Query_2: B_Not_Idle No_B_Query + B_Not_Idle_No_B_Query_2 --> CCBS_Call_Report_Outcome_Status: CCBS_Call_Report (Outcome, Status) + CCBS_Call_Report_Outcome_Status --> Call_Delivery_Outcome: Call_Delivery (Outcome) + Call_Delivery_Outcome --> Status_2: Status + Status_2 --> CCBS_Idle_2: CCBS_Idle + Status_2 --> CCBS_Not_Idle_CCBS_Not_Reachable_2: CCBS_Not_Idle CCBS_Not_Reachable + CCBS_Idle_2 --> B_Idle_No_B_Query_2: B_Idle No_B_Query + CCBS_Not_Idle_CCBS_Not_Reachable_2 --> B_Not_Idle_No_B_Query_2 + B_Not_Idle_No_B_Query_2 --> Location_Update: Location Update + Location_Update --> CCBS_supported_in_the_MSCVLR: CCBS supported in the MSCVLR + CCBS_supported_in_the_MSCVLR --> Decision_1: { } + Decision_1 --> Yes: Yes + Decision_1 --> No: No + Yes --> Start_Reporting: Start_Reporting + Start_Reporting --> To_CCBS_Coordinator_HLR: To CCBS_Coordinator_HLR + To_CCBS_Coordinator_HLR --> Decision_1 + No --> B_Not_Idle_No_B_Query_2 +``` + +State transition diagram for Process HLRB\_Monitoring. It consists of two main parts. The top part shows transitions from state 'B\_Not\_Idle No\_B\_Query' based on 'Event\_Report (Status)' from 'CCBS\_Coordinator\_HLR', 'B\_Query' from 'HLRB\_Recall\_Manager', and 'Stop\_Monitoring' from 'HLRB\_Recall\_Manager'. The bottom part shows transitions from state 'B\_Not\_Idle No\_B\_Query' based on 'CCBS\_Call\_Report (Outcome, Status)' from 'CCBS\_Coordinator\_HLR', 'Call\_Delivery (Outcome)' to 'HLRB\_Recall\_Manager', and 'Location Update' from 'CCBS\_Coordinator\_HLR'. Various decision diamonds like 'Status', 'CCBS\_Idle', and 'CCBS supported in the MSCVLR' lead to states like 'B\_Idle No\_B\_Query', 'Idle', or back to 'B\_Not\_Idle No\_B\_Query'. + +Figure 11.2.2.5: Process HLRB\_MONITORING (sheet 3 of 7) + +![State transition diagram for Process HLRB_Monitoring. It shows two main state machines. The top one starts at 'B_Not_Idle B_Query', goes to 'Event_Report (Status)' (from CCBS_Coordinator_HLR), then to a 'Status' decision. If 'CCBS_Idle', it goes to 'Start T8' -> 'Start_Blocking' (to HLRB_Blocking) -> 'B_Idle B_Query'. If 'CCBS_Not_Idle CCBS_Not_Reachable', it goes to a terminal state '-'. If 'Stop_Monitoring' (from HLRB_Recall_Manager) is received, it goes to 'Stop_Reporting' (to CCBS_Coordinator_HLR) -> 'Idle'. The bottom state machine starts at 'B_Not_Idle B_Query', goes to 'Location Update' (from CCBS_Coordinator_HLR), then to a decision 'CCBS supported in the MSCVLR'. If 'Yes', it goes to 'Start_Reporting' (to CCBS_Coordinator_HLR) -> terminal state '-'. If 'No', it goes directly to terminal state '-'.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +Process HLRB\_Monitoring 4(7) + +``` +stateDiagram-v2 + [*] --> B_Not_Idle_B_Query_1 : B_Not_Idle B_Query + B_Not_Idle_B_Query_1 --> Event_Report_Status : From CCBS_Coordinator_HLR + Event_Report_Status --> Status + Status --> Start_T8 : CCBS_Idle + Status --> CCBS_Not_Idle_CCBS_Not_Reachable : CCBS_Not_Idle CCBS_Not_Reachable + Start_T8 --> Start_Blocking : To HLRB_Blocking + Start_Blocking --> B_Idle_B_Query : B_Idle B_Query + CCBS_Not_Idle_CCBS_Not_Reachable --> End_1 : - + B_Not_Idle_B_Query_2 : B_Not_Idle B_Query --> Location_Update : From CCBS_Coordinator_HLR + Location_Update --> CCBS_supported_in_the_MSCVLR : CCBS supported in the MSCVLR + CCBS_supported_in_the_MSCVLR --> Start_Reporting : Yes + Start_Reporting --> End_2 : To CCBS_Coordinator_HLR + CCBS_supported_in_the_MSCVLR --> End_2 : No + End_2 --> [*] : - + Stop_Monitoring : From HLRB_Recall_Manager --> Stop_Reporting : To CCBS_Coordinator_HLR + Stop_Reporting --> Idle : Idle +``` + +State transition diagram for Process HLRB\_Monitoring. It shows two main state machines. The top one starts at 'B\_Not\_Idle B\_Query', goes to 'Event\_Report (Status)' (from CCBS\_Coordinator\_HLR), then to a 'Status' decision. If 'CCBS\_Idle', it goes to 'Start T8' -> 'Start\_Blocking' (to HLRB\_Blocking) -> 'B\_Idle B\_Query'. If 'CCBS\_Not\_Idle CCBS\_Not\_Reachable', it goes to a terminal state '-'. If 'Stop\_Monitoring' (from HLRB\_Recall\_Manager) is received, it goes to 'Stop\_Reporting' (to CCBS\_Coordinator\_HLR) -> 'Idle'. The bottom state machine starts at 'B\_Not\_Idle B\_Query', goes to 'Location Update' (from CCBS\_Coordinator\_HLR), then to a decision 'CCBS supported in the MSCVLR'. If 'Yes', it goes to 'Start\_Reporting' (to CCBS\_Coordinator\_HLR) -> terminal state '-'. If 'No', it goes directly to terminal state '-'. + +Figure 11.2.2.5: Process HLRB\_MONITORING (sheet 4 of 7) + +![State transition diagram for Process HLRB_Monitoring. It shows two main state transition paths starting from 'B_Idle No_B_Query'. The first path handles 'Event_Report (Status)', 'T8 Expiry', 'B_Query', and 'Stop_Monitoring'. The second path handles 'CCBS_Call_Report (Outcome, Status)' and 'Location Update'. Transitions lead to states like 'B_Not_Idle No_B_Query', 'B_Idle_Guarded No_B_Query', 'B_Idle B_Query', 'Idle', and back to 'B_Not_Idle No_B_Query'.](cc7baa8e5118f4b42c01166637c738ea_img.jpg) + +Process HLRB\_Monitoring 5(7) + +``` +stateDiagram-v2 + [*] --> B_Idle_No_B_Query_1: B_Idle No_B_Query + B_Idle_No_B_Query_1 --> Event_Report_Status: Event_Report (Status) + Event_Report_Status --> Status_1: Status + Status_1 --> B_Not_Idle_No_B_Query_1: B_Not_Idle No_B_Query + Status_1 --> CCBS_Idle_1: CCBS_Idle + Status_1 --> CCBS_Not_Idle_CCBS_Not_Reachable_1: CCBS_Not_Idle CCBS_Not_Reachable + Event_Report_Status --> T8_Expiry: T8 Expiry + T8_Expiry --> B_Idle_Guarded_No_B_Query_1: B_Idle_Guarded No_B_Query + Event_Report_Status --> B_Query: B_Query + B_Query --> B_Idle_B_Query_1: B_Idle B_Query + Event_Report_Status --> Stop_Monitoring: Stop_Monitoring + Stop_Monitoring --> Stop_T8_1: Stop T8 + Stop_T8_1 --> Stop_Blocking_1: Stop_Blocking + Stop_Blocking_1 --> Stop_Reporting_1: Stop_Reporting + Stop_Reporting_1 --> Idle_1: Idle + + [*] --> B_Idle_No_B_Query_2: B_Idle No_B_Query + B_Idle_No_B_Query_2 --> CCBS_Call_Report_Outcome_Status: CCBS_Call_Report (Outcome, Status) + CCBS_Call_Report_Outcome_Status --> Call_Delivery_Outcome: Call_Delivery (Outcome) + Call_Delivery_Outcome --> Status_2: Status + Status_2 --> CCBS_Idle_2: CCBS_Idle + Status_2 --> CCBS_Not_Idle_CCBS_Not_Reachable_2: CCBS_Not_Idle CCBS_Not_Reachable + CCBS_Call_Report_Outcome_Status --> Location_Update: Location Update + Location_Update --> CCBS_supported_in_the_MSCVLR: CCBS supported in the MSCVLR + CCBS_supported_in_the_MSCVLR --> Stop_T8_2: Stop T8 + Stop_T8_2 --> Stop_Blocking_2: Stop_Blocking + Stop_Blocking_2 --> B_Not_Idle_No_B_Query_2: B_Not_Idle No_B_Query + CCBS_supported_in_the_MSCVLR --> Start_Reporting_2: Start_Reporting + Start_Reporting_2 --> [*] +``` + +**Top State Transition Path:** + +- Initial State: **B\_Idle No\_B\_Query** +- Transitions: **Event\_Report (Status)** (From CCBS\_Coordinator\_HLR), **T8 Expiry**, **B\_Query** (From HLRB\_Recall\_Manager), **Stop\_Monitoring** (From HLRB\_Recall\_Manager) +- Decision: **Status** + - Path: **CCBS\_Idle** leads to state **-** + - Path: **CCBS\_Not\_Idle CCBS\_Not\_Reachable** leads to state **B\_Not\_Idle No\_B\_Query** +- Other Transitions: **Stop T8**, **Stop\_Blocking** (To HLRB\_Blocking), **Stop\_Reporting** (To CCBS\_Coordinator\_HLR) +- Final States: **B\_Not\_Idle No\_B\_Query**, **-**, **B\_Idle\_Guarded No\_B\_Query**, **B\_Idle B\_Query**, **Idle** + +**Bottom State Transition Path:** + +- Initial State: **B\_Idle No\_B\_Query** +- Transitions: **CCBS\_Call\_Report (Outcome, Status)** (From CCBS\_Coordinator\_HLR), **Location Update** (From CCBS\_Coordinator\_HLR) +- Decision: **CCBS supported in the MSCVLR** + - Path: **No** leads to **Stop T8**, then **Stop\_Blocking** (To HLRB\_Blocking), resulting in state **B\_Not\_Idle No\_B\_Query** + - Path: **Yes** leads to **Start\_Reporting** (To CCBS\_Coordinator\_HLR), resulting in state **-** +- Other Transitions: **Call\_Delivery (Outcome)** (To HLRB\_Recall\_Manager) +- Decision: **Status** + - Path: **CCBS\_Idle** leads to state **-** + - Path: **CCBS\_Not\_Idle CCBS\_Not\_Reachable** leads to state **B\_Not\_Idle No\_B\_Query** + +State transition diagram for Process HLRB\_Monitoring. It shows two main state transition paths starting from 'B\_Idle No\_B\_Query'. The first path handles 'Event\_Report (Status)', 'T8 Expiry', 'B\_Query', and 'Stop\_Monitoring'. The second path handles 'CCBS\_Call\_Report (Outcome, Status)' and 'Location Update'. Transitions lead to states like 'B\_Not\_Idle No\_B\_Query', 'B\_Idle\_Guarded No\_B\_Query', 'B\_Idle B\_Query', 'Idle', and back to 'B\_Not\_Idle No\_B\_Query'. + +Figure 11.2.2.5: Process HLRB\_MONITORING (sheet 5 of 7) + +![State transition diagram for Process HLRB_Monitoring. It shows two main state machines. The top one starts at 'B_Idle B_Query' and handles 'Event_Report (Status)' from 'CCBS_Coordinator_HLR', 'T8 Expiry', and 'Stop_Monitoring' from 'HLRB_Recall_Manager'. The bottom one starts at 'B_Idle B_Query' and handles 'CCBS_Call_Report (Outcome, Status)' from 'CCBS_Coordinator_HLR', 'Call_Delivery (Outcome)' from 'HLRB_Recall_Manager', and 'Location Update' from 'CCBS_Coordinator_HLR'. Both machines include decision points for 'Status' and 'CCBS supported in the MSCVLR', leading to various 'Stop' or 'Start' actions and resulting states like 'B_Not_Idle B_Query', 'B_Idle_Guarded No_B_Query', and 'Idle'.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +Process HLRB\_Monitoring 6(7) + +``` +stateDiagram-v2 + [*] --> B_Idle_B_Query_1: B_Idle B_Query + B_Idle_B_Query_1 --> Event_Report_Status: Event_Report (Status) + Event_Report_Status --> Status_1: Status + Status_1 --> CCBS_Not_Idle_1: CCBS_Not_Idle CCBS_Not_Reachable + Status_1 --> CCBS_Idle_1: CCBS_Idle + Status_1 --> Stop_T8_1: Stop T8 + Stop_T8_1 --> Stop_Blocking_1: Stop_Blocking + Stop_Blocking_1 --> B_Not_Idle_B_Query_1: B_Not_Idle B_Query + CCBS_Idle_1 --> [*] + B_Idle_B_Query_1 --> T8_Expiry: T8 Expiry + T8_Expiry --> B_Guarded: B_Guarded + B_Guarded --> B_Idle_Guarded_No_B_Query: B_Idle_Guarded No_B_Query + B_Idle_B_Query_1 --> Stop_Monitoring: Stop_Monitoring + Stop_Monitoring --> Stop_T8_2: Stop T8 + Stop_T8_2 --> Stop_Blocking_2: Stop_Blocking + Stop_Blocking_2 --> Stop_Reporting: Stop_Reporting + Stop_Reporting --> Idle: Idle + + [*] --> B_Idle_B_Query_2: B_Idle B_Query + B_Idle_B_Query_2 --> CCBS_Call_Report_Outcome_Status: CCBS_Call_Report (Outcome, Status) + CCBS_Call_Report_Outcome_Status --> Call_Delivery_Outcome: Call_Delivery (Outcome) + Call_Delivery_Outcome --> Status_2: Status + Status_2 --> CCBS_Not_Idle_2: CCBS_Not_Idle CCBS_Not_Reachable + Status_2 --> CCBS_Idle_2: CCBS_Idle + CCBS_Not_Idle_2 --> B_Not_Idle_B_Query_2: B_Not_Idle B_Query + CCBS_Idle_2 --> [*] + B_Idle_B_Query_2 --> Location_Update: Location Update + Location_Update --> CCBS_Supported_in_the_MSCVLR: CCBS supported in the MSCVLR + CCBS_Supported_in_the_MSCVLR --> Stop_T8_3: Stop T8 + Stop_T8_3 --> Stop_Blocking_3: Stop_Blocking + Stop_Blocking_3 --> B_Not_Idle_B_Query_3: B_Not_Idle B_Query + CCBS_Supported_in_the_MSCVLR --> Start_Reporting_2: Start_Reporting + Start_Reporting_2 --> B_Idle_B_Query_3: B_Idle B_Query +``` + +State transition diagram for Process HLRB\_Monitoring. It shows two main state machines. The top one starts at 'B\_Idle B\_Query' and handles 'Event\_Report (Status)' from 'CCBS\_Coordinator\_HLR', 'T8 Expiry', and 'Stop\_Monitoring' from 'HLRB\_Recall\_Manager'. The bottom one starts at 'B\_Idle B\_Query' and handles 'CCBS\_Call\_Report (Outcome, Status)' from 'CCBS\_Coordinator\_HLR', 'Call\_Delivery (Outcome)' from 'HLRB\_Recall\_Manager', and 'Location Update' from 'CCBS\_Coordinator\_HLR'. Both machines include decision points for 'Status' and 'CCBS supported in the MSCVLR', leading to various 'Stop' or 'Start' actions and resulting states like 'B\_Not\_Idle B\_Query', 'B\_Idle\_Guarded No\_B\_Query', and 'Idle'. + +Figure 11.2.2.5: Process HLRB\_MONITORING (sheet 6 of 7) + +![State transition diagram for Process HLRB_Monitoring. It shows two main state machines. The top one starts at 'B_Idle_Guarded No_B_Query' and transitions based on 'Event_Report (Status)', 'B_Query', or 'Stop_Monitoring'. The bottom one starts at 'B_Idle_Guarded No_B_Query' and transitions based on 'CCBS_Call_Report (Outcome, Status)' or 'Location Update'.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +Process HLRB\_Monitoring 7(7) + +``` +stateDiagram-v2 + [*] --> B_Idle_Guarded_No_B_Query_1 : B_Idle_Guarded No_B_Query + B_Idle_Guarded_No_B_Query_1 --> Event_Report_Status : From CCBS_Coordinator_HLR + B_Idle_Guarded_No_B_Query_1 --> B_Query : From HLRB_Recall_Manager + B_Idle_Guarded_No_B_Query_1 --> Stop_Monitoring : From HLRB_Recall_Manager + Event_Report_Status --> Status_1 : CCBS_Idle + Event_Report_Status --> Start_T8 : CCBS_Not_Idle, CCBS_Not_Reachable + Status_1 --> B_Not_Idle_No_B_Query_1 : CCBS_Idle + Start_T8 --> B_Idle_No_B_Query_1 : CCBS_Idle + B_Query --> Start_Blocking : To HLRB_Blocking + Start_Blocking --> B_Guarded : To HLRB_Recall_Manager + B_Guarded --> B_Idle_No_B_Query_2 : - + Stop_Monitoring --> Stop_Reporting : To CCBS_Coordinator_HLR + Stop_Reporting --> Idle : - + + [*] --> B_Idle_Guarded_No_B_Query_2 : B_Idle_Guarded No_B_Query + B_Idle_Guarded_No_B_Query_2 --> CCBS_Call_Report_Outcome_Status : From CCBS_Coordinator_HLR + B_Idle_Guarded_No_B_Query_2 --> Location_Update : From CCBS_Coordinator_HLR + CCBS_Call_Report_Outcome_Status --> Call_Delivery_Outcome : To HLRB_Recall_Manager + Call_Delivery_Outcome --> Status_2 : CCBS_Idle + Status_2 --> B_Not_Idle_No_B_Query_3 : CCBS_Not_Idle, CCBS_Not_Reachable + Status_2 --> B_Idle_No_B_Query_4 : CCBS_Idle + Location_Update --> CCBS_supported_in_the_MSCVLR : CCBS_supported in the MSCVLR + CCBS_supported_in_the_MSCVLR --> Decision : Yes/No + Decision --> Start_Reporting : Yes + Start_Reporting --> To_CCBS_Coordinator_HLR : To CCBS_Coordinator_HLR + Decision --> B_Not_Idle_No_B_Query_5 : No +``` + +State transition diagram for Process HLRB\_Monitoring. It shows two main state machines. The top one starts at 'B\_Idle\_Guarded No\_B\_Query' and transitions based on 'Event\_Report (Status)', 'B\_Query', or 'Stop\_Monitoring'. The bottom one starts at 'B\_Idle\_Guarded No\_B\_Query' and transitions based on 'CCBS\_Call\_Report (Outcome, Status)' or 'Location Update'. + +Figure 11.2.2.5: Process HLRB\_MONITORING (sheet 7 of 7) + +![State transition diagram for Process HLRB_BLOCKING. The diagram shows two main state transition paths. The top path starts at an initial state (oval), transitions to an 'Idle' state (oval), then to a 'Stop_Blocking' transition (chevron), which leads to another 'Idle' state (oval). A note indicates the 'Stop_Blocking' transition is triggered 'From HLRB_Recall_Manager or HLRB_Monitoring'. The bottom path starts at an 'Idle' state (oval), which branches into two transitions: 'SRI_Received' (chevron) and 'Start_Blocking' (chevron). The 'SRI_Received' transition is triggered 'From GSM 03.18 SRI_HLR (CCBS_Handling_HLR)'. It leads to a state 'Result := OK', which then leads to 'SRI_Received_Ack(Result)' (chevron), which is sent 'To GSM 03.18 SRI_HLR (CCBS_Handling_HLR)', and finally to a state labeled '-' (oval). The 'Start_Blocking' transition is triggered 'From HLRB_Monitoring' and leads to a 'Blocking' state (oval).](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +Process HLRB\_BLOCKING 1(3) + +``` +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> Stop_Blocking{Stop_Blocking} + Stop_Blocking --> Idle2[Idle] + note right of Stop_Blocking: From HLRB_Recall_Manager or HLRB_Monitoring + + Idle3[Idle] --> SRI_Received{SRI_Received} + SRI_Received --> Result[Result := OK] + Result --> SRI_Received_Ack{SRI_Received_Ack(Result)} + SRI_Received_Ack --> Dash[-] + note right of SRI_Received: From GSM 03.18 SRI_HLR (CCBS_Handling_HLR) + note right of SRI_Received_Ack: To GSM 03.18 SRI_HLR (CCBS_Handling_HLR) + + Idle3 --> Start_Blocking{Start_Blocking} + Start_Blocking --> Blocking[Blocking] + note right of Start_Blocking: From HLRB_Monitoring +``` + +State transition diagram for Process HLRB\_BLOCKING. The diagram shows two main state transition paths. The top path starts at an initial state (oval), transitions to an 'Idle' state (oval), then to a 'Stop\_Blocking' transition (chevron), which leads to another 'Idle' state (oval). A note indicates the 'Stop\_Blocking' transition is triggered 'From HLRB\_Recall\_Manager or HLRB\_Monitoring'. The bottom path starts at an 'Idle' state (oval), which branches into two transitions: 'SRI\_Received' (chevron) and 'Start\_Blocking' (chevron). The 'SRI\_Received' transition is triggered 'From GSM 03.18 SRI\_HLR (CCBS\_Handling\_HLR)'. It leads to a state 'Result := OK', which then leads to 'SRI\_Received\_Ack(Result)' (chevron), which is sent 'To GSM 03.18 SRI\_HLR (CCBS\_Handling\_HLR)', and finally to a state labeled '-' (oval). The 'Start\_Blocking' transition is triggered 'From HLRB\_Monitoring' and leads to a 'Blocking' state (oval). + +Figure 11.2.2.6: Process HLRB\_BLOCKING (sheet 1 of 3) + +![Flowchart for Process HLRB_BLOCKING. It starts with 'Blocking' and branches into 'SRI_Received', 'Recall_Block', and 'Stop_Blocking'. 'SRI_Received' leads to 'Handle_CFB' and then to a 'Result = Forward?' decision. 'Recall_Block' leads to 'Recall Blocking'. 'Stop_Blocking' leads to 'Idle'. The 'Result = Forward?' decision leads to 'CCBS Target := True' or 'CCBS Target := False' if 'max queue size > 0 and CCBS supported in the VMSC?'. Otherwise, it leads to 'Result := Fail' or 'Result = Busy?'. 'Result = Busy?' leads to 'Result := Fail' or a decision 'max queue size > 0 and CCBS supported in the VMSC?'. The second decision leads to 'Result := Busy, CCBS Possible' or 'Result := Busy, CCBS Not Possible'. All paths converge to 'SRI_Received_Ack(Result, CCBS_Target)' and then to an end state.](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +### Process HLRB\_BLOCKING + +2(3) + +``` +graph TD + Blocking([Blocking]) --> SRI_Received{SRI_Received} + HLRB_Recall_Manager[From HLRB_Recall_Manager] --> Recall_Block{Recall_Block} + HLRB_Monitoring[From HLRB_Monitoring] --> Stop_Blocking{Stop_Blocking} + SRI_Received --> Handle_CFB[Handle_CFB] + Note1[See TS 23.018] -.-> Handle_CFB + Handle_CFB --> Result_Forward{Result = Forward?} + Recall_Block --> Recall_Blocking([Recall Blocking]) + Stop_Blocking --> Idle([Idle]) + Result_Forward -- No --> Result_Fail[Result := Fail] + Result_Forward -- Yes --> CCBS_Queue{max queue size > 0 and CCBS supported in the VMSC?} + CCBS_Queue -- No --> Result_Fail + CCBS_Queue -- Yes --> CCBS_Target[CCBS Target := True] + CCBS_Queue -- No --> CCBS_Target_False[CCBS Target := False] + CCBS_Target --> Result_Forward_Wait[Result := Forward] + CCBS_Target_False --> Result_Forward_Wait + Result_Fail --> SRI_Ack[SRI_Received_Ack(Result, CCBS_Target)] + Result_Forward_Wait --> SRI_Ack + Result_Forward -- Yes --> Result_Busy{Result = Busy?} + Result_Busy -- No --> Result_Fail + Result_Busy -- Yes --> CCBS_Queue_2{max queue size > 0 and CCBS supported in the VMSC?} + CCBS_Queue_2 -- No --> Result_Fail + CCBS_Queue_2 -- Yes --> Result_Busy_Possible[Result := Busy, CCBS Possible] + CCBS_Queue_2 -- No --> Result_Busy_NotPossible[Result := Busy, CCBS Not Possible] + Result_Busy_Possible --> SRI_Ack + Result_Busy_NotPossible --> SRI_Ack + Note2[To GSM 03.18 SRI_HLR (CCBS_Handling_HLR)] -.-> SRI_Ack + SRI_Ack --> End([-]) +``` + +Flowchart for Process HLRB\_BLOCKING. It starts with 'Blocking' and branches into 'SRI\_Received', 'Recall\_Block', and 'Stop\_Blocking'. 'SRI\_Received' leads to 'Handle\_CFB' and then to a 'Result = Forward?' decision. 'Recall\_Block' leads to 'Recall Blocking'. 'Stop\_Blocking' leads to 'Idle'. The 'Result = Forward?' decision leads to 'CCBS Target := True' or 'CCBS Target := False' if 'max queue size > 0 and CCBS supported in the VMSC?'. Otherwise, it leads to 'Result := Fail' or 'Result = Busy?'. 'Result = Busy?' leads to 'Result := Fail' or a decision 'max queue size > 0 and CCBS supported in the VMSC?'. The second decision leads to 'Result := Busy, CCBS Possible' or 'Result := Busy, CCBS Not Possible'. All paths converge to 'SRI\_Received\_Ack(Result, CCBS\_Target)' and then to an end state. + +Figure 11.2.2.6: Process HLRB\_BLOCKING (sheet 2 of 3) + +![Flowchart for Process HLRB_BLOCKING. It starts with 'Recall Blocking', followed by 'SRI_Received' (From GSM 03.18 SRI_HLR (CCBS_Handling_HLR)). A decision 'CCBS Call?' follows. If 'Yes', it goes to 'CCBS supported in VMSC?'. If 'No', it goes to 'Handle_CFB' (See TS 23.018). From 'CCBS supported in VMSC?', 'Yes' leads to 'Keep CCBS Call Indicator := True' and 'Result := OK', while 'No' leads to 'Keep CCBS Call Indicator := False'. Both lead to 'SRI_Received_Ack(Result)' (To GSM 03.18 SRI_HLR (CCBS_Handling_HLR)) and then 'Blocking'. From 'Handle_CFB', it goes to 'Result = Forward?'. If 'Yes', it goes to 'max queue size > 0 and CCBS supported in the VMSC?'. If 'No', it goes to 'Result = Busy?'. From 'max queue size > 0 and CCBS supported in the VMSC?', 'Yes' leads to 'CCBS Target := True' and 'Result := Forward', while 'No' leads to 'CCBS Target := False'. Both lead to 'SRI_Received_Ack(Result)' (To GSM 03.18 SRI_HLR (CCBS_Handling_HLR)) and then 'Recall Blocking'. From 'Result = Busy?', 'Yes' leads to 'Result := Fail', while 'No' leads to 'max queue size > 0 and CCBS supported in the VMSC?'. From this second 'max queue size > 0 and CCBS supported in the VMSC?' decision, 'Yes' leads to 'Result := Busy, CCBS Possible' and 'No' leads to 'Result := Busy, CCBS Not Possible'. Both lead to 'SRI_Received_Ack(Result)' (To GSM 03.18 SRI_HLR (CCBS_Handling_HLR)) and then 'Recall Blocking'.](c21bad844b5cb6026c067a1f43ce67c3_img.jpg) + +Process HLRB\_BLOCKING 3(3) + +``` +graph TD; Start([Recall Blocking]) --> SRI_Received{{SRI_Received}}; SRI_Received -.-> SRI_Received_Info[From GSM 03.18 SRI_HLR (CCBS_Handling_HLR)]; SRI_Received --> CCBS_Call{CCBS Call?}; CCBS_Call -- Yes --> CCBS_Supported{CCBS supported in VMSC?}; CCBS_Call -- No --> Handle_CFB[Handle_CFB]; Handle_CFB -.-> Handle_CFB_Info[See TS 23.018]; CCBS_Supported -- Yes --> Keep_Indicator_True[Keep CCBS Call Indicator := True]; CCBS_Supported -- No --> Keep_Indicator_False[Keep CCBS Call Indicator := False]; Keep_Indicator_True --> Result_OK[Result := OK]; Keep_Indicator_False --> Result_OK; Result_OK --> SRI_Ack_1{{SRI_Received_Ack(Result)}}; SRI_Ack_1 -.-> SRI_Ack_1_Info[To GSM 03.18 SRI_HLR (CCBS_Handling_HLR)]; SRI_Ack_1 --> Blocking([Blocking]); Handle_CFB --> Result_Forward{Result = Forward?}; Result_Forward -- Yes --> MaxQueue_1{max queue size > 0 and CCBS supported in the VMSC?}; Result_Forward -- No --> Result_Busy_1{Result = Busy?}; MaxQueue_1 -- Yes --> CCBS_Target_True[CCBS Target := True]; MaxQueue_1 -- No --> CCBS_Target_False[CCBS Target := False]; CCBS_Target_True --> Result_Forward_Wait[Result := Forward]; CCBS_Target_False --> Result_Forward_Wait; Result_Busy_1 -- Yes --> Result_Fail[Result := Fail]; Result_Busy_1 -- No --> MaxQueue_2{max queue size > 0 and CCBS supported in the VMSC?}; MaxQueue_2 -- Yes --> Result_Busy_Possible[Result := Busy, CCBS Possible]; MaxQueue_2 -- No --> Result_Busy_NotPossible[Result := Busy, CCBS Not Possible]; Result_Fail --> SRI_Ack_2{{SRI_Received_Ack(Result)}}; Result_Forward_Wait --> SRI_Ack_2; Result_Busy_Possible --> SRI_Ack_2; Result_Busy_NotPossible --> SRI_Ack_2; SRI_Ack_2 -.-> SRI_Ack_2_Info[To GSM 03.18 SRI_HLR (CCBS_Handling_HLR)]; SRI_Ack_2 --> Recall_Blocking([Recall Blocking]); +``` + +Flowchart for Process HLRB\_BLOCKING. It starts with 'Recall Blocking', followed by 'SRI\_Received' (From GSM 03.18 SRI\_HLR (CCBS\_Handling\_HLR)). A decision 'CCBS Call?' follows. If 'Yes', it goes to 'CCBS supported in VMSC?'. If 'No', it goes to 'Handle\_CFB' (See TS 23.018). From 'CCBS supported in VMSC?', 'Yes' leads to 'Keep CCBS Call Indicator := True' and 'Result := OK', while 'No' leads to 'Keep CCBS Call Indicator := False'. Both lead to 'SRI\_Received\_Ack(Result)' (To GSM 03.18 SRI\_HLR (CCBS\_Handling\_HLR)) and then 'Blocking'. From 'Handle\_CFB', it goes to 'Result = Forward?'. If 'Yes', it goes to 'max queue size > 0 and CCBS supported in the VMSC?'. If 'No', it goes to 'Result = Busy?'. From 'max queue size > 0 and CCBS supported in the VMSC?', 'Yes' leads to 'CCBS Target := True' and 'Result := Forward', while 'No' leads to 'CCBS Target := False'. Both lead to 'SRI\_Received\_Ack(Result)' (To GSM 03.18 SRI\_HLR (CCBS\_Handling\_HLR)) and then 'Recall Blocking'. From 'Result = Busy?', 'Yes' leads to 'Result := Fail', while 'No' leads to 'max queue size > 0 and CCBS supported in the VMSC?'. From this second 'max queue size > 0 and CCBS supported in the VMSC?' decision, 'Yes' leads to 'Result := Busy, CCBS Possible' and 'No' leads to 'Result := Busy, CCBS Not Possible'. Both lead to 'SRI\_Received\_Ack(Result)' (To GSM 03.18 SRI\_HLR (CCBS\_Handling\_HLR)) and then 'Recall Blocking'. + +Figure 11.2.2.6: Process HLRB\_BLOCKING (sheet 3 of 3) + +![Flowchart for Procedure HLRB_CCBS_Check_Interactions. It starts with a connector symbol, followed by three decision diamonds: 'CFU active & operative for the request', 'BAIC active & operative for the request', and 'BIC-Roam active & operative for the request'. Each decision has a 'Yes' path leading to 'Result := Fail' and a 'No' path leading to the next decision. All 'No' paths lead to 'Result := Pass'. Both 'Result := Pass' and 'Result := Fail' lead to an exit connector symbol.](b50f38be091844d58b11e3d47bc71e73_img.jpg) + +Procedure HLRB\_CCBS\_Check\_Interactions + +1(1) + +``` +graph TD; Start([ ]) --> D1{CFU active & operative for the request}; D1 -- Yes --> Fail[Result := Fail]; D1 -- No --> D2{BAIC active & operative for the request}; D2 -- Yes --> Fail; D2 -- No --> D3{BIC-Roam active & operative for the request}; D3 -- Yes --> Fail; D3 -- No --> Pass[Result := Pass]; Pass --> End(( )); Fail --> End +``` + +Flowchart for Procedure HLRB\_CCBS\_Check\_Interactions. It starts with a connector symbol, followed by three decision diamonds: 'CFU active & operative for the request', 'BAIC active & operative for the request', and 'BIC-Roam active & operative for the request'. Each decision has a 'Yes' path leading to 'Result := Fail' and a 'No' path leading to the next decision. All 'No' paths lead to 'Result := Pass'. Both 'Result := Pass' and 'Result := Fail' lead to an exit connector symbol. + +Figure 11.2.2.7: Procedure HLRB\_Check\_Interactions + +![Flowchart for Procedure CCBS_Handling_HLR](72d448a65347c51989171748789c7d4b_img.jpg) + +Procedure CCBS\_Handling\_HLR + +1(1) + +``` +graph TD; Start([ ]) --> SRI_Received{{SRI_Received}}; SRI_Received -.-> To_HLRB_Blocking[To HLRB_Blocking]; SRI_Received --> Wait_For_Answer([Wait For Answer]); Wait_For_Answer --> SRI_Received_Ack{{SRI_Received Ack (Result)}}; SRI_Received_Ack -.-> From_HLRB_Blocking[From HLRB_Blocking]; SRI_Received_Ack --> Result{Result}; Result -- OK --> CCBS_Call{CCBS Call}; CCBS_Call -- No --> Set_result[Set result]; CCBS_Call -- Yes --> Set_CCBS_Indicator[Set CCBS Call Indicator in PRN]; Set_CCBS_Indicator --> Set_result; Result -- Fail --> Set_neg_resp_Forwarding_violation[Set neg.resp Forwarding violation]; Set_neg_resp_Forwarding_violation --> Set_result; Result -- Busy --> Set_neg_resp_Busy_subscriber[Set neg.resp Busy subscriber]; Set_neg_resp_Busy_subscriber --> Set_result; Result -- Forward --> Set_Forwarding_Info[Set Forwarding Info]; Set_Forwarding_Info --> Set_result; Set_result -.-> From_result_code[From result code received in SRI_Received_Ack]; Set_result --> End((X)) +``` + +The flowchart illustrates the 'Procedure CCBS\_Handling\_HLR'. It begins with an oval connector, leading to a decision block 'SRI\_Received'. A dashed arrow points from this block to 'To HLRB\_Blocking'. The flow then proceeds to a process block 'Wait For Answer', followed by another decision block 'SRI\_Received Ack (Result)'. A dashed arrow points from this block to 'From HLRB\_Blocking'. The flow then reaches a decision block 'Result'. From 'Result', four paths emerge: 'OK', 'Fail', 'Busy', and 'Forward'. The 'OK' path leads to a decision block 'CCBS Call'. If 'No', it proceeds to 'Set result'. If 'Yes', it proceeds to 'Set CCBS Call Indicator in PRN', which then leads to 'Set result'. The 'Fail' path leads to 'Set neg.resp Forwarding violation', which then leads to 'Set result'. The 'Busy' path leads to 'Set neg.resp Busy subscriber', which then leads to 'Set result'. The 'Forward' path leads to 'Set Forwarding Info', which then leads to 'Set result'. A dashed arrow points from 'Set result' to 'From result code received in SRI\_Received\_Ack'. Finally, the flowchart ends at a circle with an 'X'. + +Flowchart for Procedure CCBS\_Handling\_HLR + +Figure 11.2.2.8: Procedure CCBS\_Handling\_HLR + +![Flowchart for Procedure CCBS_Report_PRN_Failure. It starts with a connector symbol, followed by a decision 'CCBS call'. If 'No', it goes to an exit connector. If 'Yes', it performs 'Outcome := Failure', then a 'Call_Delivery (Outcome)' process which also connects to 'To HLRB_Recall Manager', and finally reaches an exit connector.](3ec35c497a0765a1a885c85f214b1bef_img.jpg) + +Procedure CCBS\_Report\_PRN\_Failure + +1(1) + +``` +graph TD; Start([ ]) --> CCBS{CCBS call}; CCBS -- No --> Exit1(( )); CCBS -- Yes --> Outcome[Outcome := Failure]; Outcome --> CallDelivery{Call_Delivery (Outcome)}; CallDelivery --> HLRB[To HLRB_Recall Manager]; CallDelivery --> Exit2(( )); +``` + +Flowchart for Procedure CCBS\_Report\_PRN\_Failure. It starts with a connector symbol, followed by a decision 'CCBS call'. If 'No', it goes to an exit connector. If 'Yes', it performs 'Outcome := Failure', then a 'Call\_Delivery (Outcome)' process which also connects to 'To HLRB\_Recall Manager', and finally reaches an exit connector. + +Figure 11.2.2.9: Procedure CCBS\_Report\_PRN\_Failure + +### 11.2.3 Procedures in MSC/VLR + +Figure 11.2.3.1: Procedure CCBS\_MT\_MSC\_Check\_Forwarding + +This procedure is called to set the CCBS Target variable. That variable is used in later phase to set the correct diagnostic value to the Release message. + +Figure 11.2.3.2: Procedure CCBS\_Handle\_PRN + +This procedure is called to store CCBS call indicator when roaming number is reserved in the VLR. + +Figure 11.2.3.3: Procedure CCBS\_ICH\_Set\_CCBS\_Call\_Indicator + +This procedure is called when VLR receives Send Info For Incoming Call message. If MSRN is related to the CCBS call, CCBS call indicator is set for call handling. + +Figure 11.2.3.4: Procedure CCBS\_ICH\_MSC\_Report\_Failure + +This procedure is called when CCBS call fails in the destination MSC and the reason is detected in the MSC side. + +Figure 11.2.3.5: Procedure CCBS\_ICH\_VLR\_Report\_Failure + +This procedure is called when CCBS call fails in the destination MSC and the reason is detected in the VLR side. + +Figure 11.2.3.6: Procedure CCBS\_ICH\_Report\_Not\_Reachable + +This procedure is called when call fails in the destination MSC with special cause of Not\_Reachable. On normal call Not\_Reachable message is sent to the monitoring process, on CCBS call subscriber is reported being absent. + +Figure 11.2.3.7: Procedure CCBS\_ICH\_Handle\_NDUB + +This procedure is called when call encounters NDUB condition in the destination MSC. It is a network option to forward the call or release the call. + +Figure 11.2.3.8: Procedure CCBS\_ICH\_Handle\_UDUB + +This procedure is called when call encounters UDUB condition in the destination MSC. + +Figure 11.2.3.9: Procedure CCBS\_ICH\_MSC\_Report\_Success + +This procedure is called when CCBS call is successfully delivered in the destination MSC and the event is detected in the MSC side. + +Figure 11.2.3.10: Procedure CCBS\_ICH\_VLR\_Report\_Success + +This procedure is called when CCBS call is successfully delivered in the destination MSC and the event is detected in the VLR side. + +Figure 11.2.3.11: Procedure CCBS\_ICH\_Set\_CCBS\_Target + +This procedure is called if when a call encounters busy condition in the destination MSC. If busy cause is NDUB and the user has elected to be target of CCBS requests, CCBS Target is set to True. + +![Flowchart for Procedure CCBS_MT_MSC_Check_Forwarding. It starts with a connector symbol, followed by a decision diamond 'CCBS target'. A note 'Parameter is set when SIFC_Ack is received from VLR' is linked to this diamond. If 'True', it goes to another decision diamond with a note 'Cause = Busy or Cause = No circuit channel available'. If 'Yes', it goes to a process box 'CCBS Target := True'. If 'No', it goes to a process box 'CCBS Target := False'. Both process boxes lead to a final connector symbol. A note 'Alter the internal variable which controls setting of the diagnostic field' is linked to the 'CCBS Target := True' box.](b13465efdac63129aef9b6f1787d0d00_img.jpg) + +Procedure CCBS\_MT\_MSC\_Check\_Forwarding 1(1) + +``` +graph TD; Start([ ]) --> CCBS_target{CCBS target}; Note1[Parameter is set when SIFC_Ack is received from VLR] -.-> CCBS_target; CCBS_target -- True --> Decision{ }; Note2[Cause = Busy or Cause = No circuit channel available] -.-> Decision; Decision -- Yes --> TrueProcess[CCBS Target := True]; Note3[Alter the internal variable which controls setting of the diagnostic field] -.-> TrueProcess; Decision -- No --> FalseProcess[CCBS Target := False]; TrueProcess --> End(( )); FalseProcess --> End; +``` + +Flowchart for Procedure CCBS\_MT\_MSC\_Check\_Forwarding. It starts with a connector symbol, followed by a decision diamond 'CCBS target'. A note 'Parameter is set when SIFC\_Ack is received from VLR' is linked to this diamond. If 'True', it goes to another decision diamond with a note 'Cause = Busy or Cause = No circuit channel available'. If 'Yes', it goes to a process box 'CCBS Target := True'. If 'No', it goes to a process box 'CCBS Target := False'. Both process boxes lead to a final connector symbol. A note 'Alter the internal variable which controls setting of the diagnostic field' is linked to the 'CCBS Target := True' box. + +Figure 11.2.3.1: Procedure CCBS\_MT\_MSC\_Check\_Forwarding + +![Flowchart for Procedure CCBS_Handle_PRN. It starts with a connector symbol (oval), followed by a process block 'Store CCBS Call indicator along with the MSRN', and ends with a circle containing an 'X'.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +Procedure CCBS\_Handle\_PRN 1(1) + +``` +graph TD; A([ ]) --> B[Store CCBS Call indicator along with the MSRN]; B --> C((X)); +``` + +Flowchart for Procedure CCBS\_Handle\_PRN. It starts with a connector symbol (oval), followed by a process block 'Store CCBS Call indicator along with the MSRN', and ends with a circle containing an 'X'. + +Figure 11.2.3.2: Procedure CCBS\_Handle\_PRN + +![Flowchart for Procedure CCBS_ICH_Set_CCBS_Call_Indicator. It starts with a connector symbol, followed by a decision diamond 'MSRN for CCBS_Call'. If 'No', it goes to an exit connector. If 'Yes', it goes to an output symbol 'CCBS_Call' (labeled 'To CCBS_Monitoring_VLR'), then to a process block 'Indicator := CCBS_Call', and finally to an exit connector.](921f8fa0f7ce2c9956f20d33162c13a2_img.jpg) + +Procedure CCBS\_ICH\_Set\_CCBS\_Call\_Indicator 1(1) + +``` +graph TD; Start([ ]) --> Decision{MSRN for CCBS_Call}; Decision -- No --> Exit1(( )); Decision -- Yes --> Output[/CCBS_Call/]; Output -.-> ToCCBS[To CCBS_Monitoring_VLR]; Output --> Process[Indicator := CCBS_Call]; Process --> Exit2(( )); +``` + +Flowchart for Procedure CCBS\_ICH\_Set\_CCBS\_Call\_Indicator. It starts with a connector symbol, followed by a decision diamond 'MSRN for CCBS\_Call'. If 'No', it goes to an exit connector. If 'Yes', it goes to an output symbol 'CCBS\_Call' (labeled 'To CCBS\_Monitoring\_VLR'), then to a process block 'Indicator := CCBS\_Call', and finally to an exit connector. + +Figure 11.2.3.3: Procedure CCBS\_ICH\_Set\_CCBS\_Call\_Indicator + +![Flowchart for Procedure CCBS_ICH_MSC_Report_Failure. It starts with a connector symbol, followed by a decision diamond 'CCBS Call'. If 'No', it goes to an exit connector. If 'Yes', it goes to a process box 'Outcome := Failure', then to a delivery symbol 'CCBS_Call_Delivery (Outcome)' which points to 'To CCBS_Monitoring_VLR', and finally to an exit connector.](536768a30136cd5c2d57f46c25d1d804_img.jpg) + +Procedure CCBS\_ICH\_MSC\_Report\_Failure 1(1) + +``` +graph TD; Start([ ]) --> CCBS_Call{CCBS Call}; CCBS_Call -- No --> Exit1(( )); CCBS_Call -- Yes --> Outcome[Outcome := Failure]; Outcome --> Delivery{CCBS_Call_Delivery (Outcome)}; Delivery --> ToMonitoring[To CCBS_Monitoring_VLR]; Delivery --> Exit2(( )); +``` + +Flowchart for Procedure CCBS\_ICH\_MSC\_Report\_Failure. It starts with a connector symbol, followed by a decision diamond 'CCBS Call'. If 'No', it goes to an exit connector. If 'Yes', it goes to a process box 'Outcome := Failure', then to a delivery symbol 'CCBS\_Call\_Delivery (Outcome)' which points to 'To CCBS\_Monitoring\_VLR', and finally to an exit connector. + +Figure 11.2.3.4: Procedure CCBS\_ICH\_MSC\_Report\_Failure + +![Flowchart for Procedure CCBS_ICH_VLR_Report_Failure. It starts with a connector symbol, leading to a decision diamond 'CCBS Call'. If 'No', it goes to an exit connector. If 'Yes', it goes to a process box 'Outcome := Failure', then to a delivery symbol 'CCBS_Call_Delivery (Outcome)' which points to 'To CCBS_Monitoring_VLR', and finally to an exit connector.](245166735676c675f98f535bc4c6f0a1_img.jpg) + +Procedure CCBS\_ICH\_VLR\_Report\_Failure 1(1) + +``` +graph TD; Start([ ]) --> CCBS_Call{CCBS Call}; CCBS_Call -- No --> Exit1(( )); CCBS_Call -- Yes --> Outcome[Outcome := Failure]; Outcome --> Delivery{CCBS_Call_Delivery (Outcome)}; Delivery --> ToMonitoring_VLR[To CCBS_Monitoring_VLR]; Delivery --> Exit2(( )); +``` + +Flowchart for Procedure CCBS\_ICH\_VLR\_Report\_Failure. It starts with a connector symbol, leading to a decision diamond 'CCBS Call'. If 'No', it goes to an exit connector. If 'Yes', it goes to a process box 'Outcome := Failure', then to a delivery symbol 'CCBS\_Call\_Delivery (Outcome)' which points to 'To CCBS\_Monitoring\_VLR', and finally to an exit connector. + +Figure 11.2.3.5: Procedure CCBS\_ICH\_VLR\_Report\_Failure + +![Flowchart for Procedure CCBS_ICH_Report_Not_Reachable. It starts with a connector symbol, leading to a decision diamond 'CCBS Call'. If 'No', it goes to 'Not_Reachable' which then points to 'To CCBS_Monitoring_VLR'. If 'Yes', it goes to a process box 'Outcome := Absent Subscriber', then to 'CCBS_Call_Delivery (Outcome)' which points to 'To CCBS_Monitoring_VLR'. Both paths converge to an end connector symbol.](92724c769da9d46b730fde1a6dccb023_img.jpg) + +Procedure CCBS\_ICH\_Report\_Not\_Reachable 1(1) + +``` +graph TD; Start([ ]) --> CCBS_Call{CCBS Call}; CCBS_Call -- No --> Not_Reachable[/Not_Reachable/]; CCBS_Call -- Yes --> Outcome["Outcome := Absent Subscriber"]; Not_Reachable --> To_VLR1[To CCBS_Monitoring_VLR]; Outcome --> CCBS_Call_Delivery[/CCBS_Call_Delivery (Outcome)/]; CCBS_Call_Delivery --> To_VLR2[To CCBS_Monitoring_VLR]; To_VLR1 --> End((X)); To_VLR2 --> End +``` + +Flowchart for Procedure CCBS\_ICH\_Report\_Not\_Reachable. It starts with a connector symbol, leading to a decision diamond 'CCBS Call'. If 'No', it goes to 'Not\_Reachable' which then points to 'To CCBS\_Monitoring\_VLR'. If 'Yes', it goes to a process box 'Outcome := Absent Subscriber', then to 'CCBS\_Call\_Delivery (Outcome)' which points to 'To CCBS\_Monitoring\_VLR'. Both paths converge to an end connector symbol. + +Figure 11.2.3.6: Procedure CCBS\_ICH\_Report\_Not\_Reachable + +![Flowchart for Procedure CCBS_ICH_Handle_NDUB. It starts with 'Busy condition := NDUB', then a decision 'CCBS Call'. If 'No', it goes to 'Result := Forward'. If 'Yes', it goes to a 'Network option: Release or forward' block. From there, 'Forward' leads to 'Outcome := Failure' and 'Release' leads to 'Outcome := NDUB'. Both lead to 'CCBS_Call_Delivery (Outcome)' blocks, which then lead to 'To CCBS_Monitoring_VLR' blocks. Both 'To CCBS_Monitoring_VLR' blocks lead to 'Result := Forward' and 'Result := Release' blocks, which both lead to an exit symbol.](db7a693cf26f527ac6c0d4d41da20858_img.jpg) + +Procedure CCBS\_ICH\_Handle\_NDUB 1(1) + +``` +graph TD; Start([ ]) --> Busy[Busy condition := NDUB]; Busy --> CCBS{CCBS Call}; CCBS -- No --> ResultF[Result := Forward]; CCBS -- Yes --> NetOpt[Network option: Release or forward]; NetOpt -- Forward --> OutcomeF[Outcome := Failure]; NetOpt -- Release --> OutcomeNDUB[Outcome := NDUB]; OutcomeF --> DeliveryF{{CCBS_Call_Delivery (Outcome)}}; OutcomeNDUB --> DeliveryNDUB{{CCBS_Call_Delivery (Outcome)}}; DeliveryF --> MonitoringF[To CCBS_Monitoring_VLR]; DeliveryNDUB --> MonitoringNDUB[To CCBS_Monitoring_VLR]; MonitoringF --> ResultF; MonitoringNDUB --> ResultR[Result := Release]; ResultF --> Exit((X)); ResultR --> Exit +``` + +Flowchart for Procedure CCBS\_ICH\_Handle\_NDUB. It starts with 'Busy condition := NDUB', then a decision 'CCBS Call'. If 'No', it goes to 'Result := Forward'. If 'Yes', it goes to a 'Network option: Release or forward' block. From there, 'Forward' leads to 'Outcome := Failure' and 'Release' leads to 'Outcome := NDUB'. Both lead to 'CCBS\_Call\_Delivery (Outcome)' blocks, which then lead to 'To CCBS\_Monitoring\_VLR' blocks. Both 'To CCBS\_Monitoring\_VLR' blocks lead to 'Result := Forward' and 'Result := Release' blocks, which both lead to an exit symbol. + +Figure 11.2.3.7: Procedure CCBS\_ICH\_Handle\_NDUB + +![UML Sequence diagram for Procedure CCBS_ICH_Handle_UDUB. The diagram shows a lifeline with a start symbol (oval), a message box 'Busy condition := UDUB', and an end symbol (circle with X). A note box is present in the top left corner.](8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg) + +Procedure CCBS\_ICH\_Handle\_UDUB 1(1) + +``` +sequenceDiagram + participant User + Note left of User: + User->>User: Busy condition := UDUB + Note right of User: +``` + +UML Sequence diagram for Procedure CCBS\_ICH\_Handle\_UDUB. The diagram shows a lifeline with a start symbol (oval), a message box 'Busy condition := UDUB', and an end symbol (circle with X). A note box is present in the top left corner. + +Figure 11.2.3.8: Procedure CCBS\_ICH\_Handle\_UDUB + +![Flowchart for Procedure CCBS_ICH_MSC_Report_Success. It starts with a connector symbol, followed by a decision diamond 'CCBS_Call'. If 'Yes', it goes to a process box 'Outcome := Success', then to an output box 'CCBS_Call_Delivery (Outcome)'. A dashed box labeled 'To CCBS_Monitoring_VLR' is connected to this output. If 'No', it bypasses the process and output boxes. All paths lead to a final connector symbol.](9958beca8f65818eb0ff893647af94de_img.jpg) + +Procedure CCBS\_ICH\_MSC\_Report\_Success 1(1) + +``` +graph TD; Start([ ]) --> CCBS_Call{CCBS_Call}; CCBS_Call -- Yes --> Outcome[Outcome := Success]; Outcome --> CCBS_Call_Delivery{{CCBS_Call_Delivery (Outcome)}}; CCBS_Call_Delivery -.-> ToCCBS_Monitoring_VLR[To CCBS_Monitoring_VLR]; CCBS_Call -- No --> End(( )); CCBS_Call_Delivery --> End; +``` + +Flowchart for Procedure CCBS\_ICH\_MSC\_Report\_Success. It starts with a connector symbol, followed by a decision diamond 'CCBS\_Call'. If 'Yes', it goes to a process box 'Outcome := Success', then to an output box 'CCBS\_Call\_Delivery (Outcome)'. A dashed box labeled 'To CCBS\_Monitoring\_VLR' is connected to this output. If 'No', it bypasses the process and output boxes. All paths lead to a final connector symbol. + +Figure 11.2.3.9: Procedure CCBS\_ICH\_MSC\_Report\_Success + +![Flowchart for Procedure CCBS_ICH_VLR_Report_Success. It starts with a connector symbol, followed by a decision diamond 'CCBS_Call'. If 'Yes', it goes to a process box 'Outcome := Success', then to an output box 'CCBS_Call_Delivery (Outcome)'. A dashed box 'To CCBS_Monitoring_VLR' is connected to this output. If 'No', it bypasses the process and output boxes. All paths lead to a final connector symbol.](fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg) + +Procedure CCBS\_ICH\_VLR\_Report\_Success 1(1) + +``` +graph TD; Start([ ]) --> CCBS_Call{CCBS_Call}; CCBS_Call -- Yes --> Outcome["Outcome := Success"]; Outcome --> CCBS_Call_Delivery[/CCBS_Call_Delivery (Outcome)/]; CCBS_Call_Delivery -.-> ToCCBS_Monitoring_VLR[To CCBS_Monitoring_VLR]; CCBS_Call -- No --> End(( )); CCBS_Call_Delivery --> End; ToCCBS_Monitoring_VLR -.-> End; +``` + +Flowchart for Procedure CCBS\_ICH\_VLR\_Report\_Success. It starts with a connector symbol, followed by a decision diamond 'CCBS\_Call'. If 'Yes', it goes to a process box 'Outcome := Success', then to an output box 'CCBS\_Call\_Delivery (Outcome)'. A dashed box 'To CCBS\_Monitoring\_VLR' is connected to this output. If 'No', it bypasses the process and output boxes. All paths lead to a final connector symbol. + +Figure 11.2.3.10: Procedure CCBS\_ICH\_VLR\_Report\_Success + +![Flowchart for Procedure CCBS_ICH_Set_CCBS_Target. The process starts with a connector symbol, leading to a decision 'Busy condition'. If 'UDUB', it goes to a 'CCBS Target := False' block. If 'NDUB', it goes to another decision 'CCBS Allowed'. A note 'Has destination B elected to be a target of requests' is associated with this decision. If 'No', it goes to the 'CCBS Target := False' block. If 'Yes', it goes to a 'CCBS Target := True' block. Both blocks lead to an end connector symbol.](3334fcca5dac808f4fd3840aba35bc2e_img.jpg) + +Procedure CCBS\_ICH\_Set\_CCBS\_Target 1(1) + +``` +graph TD; Start([ ]) --> Busy{Busy condition}; Busy -- UDUB --> False[CCBS Target := False]; Busy -- NDUB --> Allowed{CCBS Allowed}; Note[Has destination B elected to be a target of requests] -.-> Allowed; Allowed -- No --> False; Allowed -- Yes --> True[CCBS Target := True]; True --> End(( )); False --> End; +``` + +Flowchart for Procedure CCBS\_ICH\_Set\_CCBS\_Target. The process starts with a connector symbol, leading to a decision 'Busy condition'. If 'UDUB', it goes to a 'CCBS Target := False' block. If 'NDUB', it goes to another decision 'CCBS Allowed'. A note 'Has destination B elected to be a target of requests' is associated with this decision. If 'No', it goes to the 'CCBS Target := False' block. If 'Yes', it goes to a 'CCBS Target := True' block. Both blocks lead to an end connector symbol. + +Figure 11.2.3.11: Procedure CCBS\_ICH\_Set\_CCBS\_Target + +## 11.3 Processes and procedures common in originating and destination network entities + +Figure 11.3.1: Process CCBS\_Monitoring\_VLR + +This process is responsible for monitoring the subscriber in VLR and also controls the MSC monitoring process. + +Figure 11.3.2: Process CCBS\_Monitoring\_MSC + +This process is responsible for monitoring subscriber in MSC. + +Figure 11.3.3: Process CCBS\_Coordinator\_HLR + +This process co-ordinates HLRA and HLRB monitoring interaction. Start and Stop Reporting messages are sent only once towards MSC, CCBS\_Call\_Report messages are directed to correct queue and Status information is distributed to both queues when needed. + +Figure 11.3.4: Procedure CCBS\_Set\_Diagnostic\_For\_Release + +This procedure is called to set the diagnostic field to the Release message. The diagnostic is set according to the internal CCBS Target variable. + +Figure 11.3.5: Procedure CCBS\_Report\_Not\_Idle + +This procedure is called when either MO or MT setup is received or sent to the MS. It informs the VLR monitoring process that the MS is engaged with a call. + +Figure 11.3.6: Procedure CCBS\_Report\_MS\_Activity + +This procedure is called when Process\_Access\_Request is successfully performed. It informs the VLR monitoring process and may cause transition to the Idle state. + +Figure 11.3.7: Procedure CCBS\_Check\_Last\_Call + +This procedure is called when a call is ending. If the call is the last CC connection to the MS, that is reported to the VLR monitoring process. + +![Flowchart for Process CCBS_MONITORING_VLR. It starts at 'Idle', goes through 'Start_Reporting', 'Check_Parameters' (referencing GSM 03.18), and a 'Result' decision. If 'Pass', it sets 'Event_Reporting := True' and checks if 'IMSI Detached'. If 'Yes', it checks if 'Roaming in LA allowed'. If 'No', it sets 'Status := CCBS_Not_Reachable' and ends at 'Monitoring Detached'. If 'Yes', it sends 'Start_Status_Enquiry' to 'CCBS_Monitoring_MSC', waits for a response, and checks the 'CCBS_Not_Idle' result. If 'Yes', it sets 'Status := CCBS_Not_Idle' and ends at 'Monitoring Not Idle'. If 'No', it sets 'Status := CCBS_Idle' and ends at 'Monitoring Idle'. If 'Fail' at the 'Result' decision, it sets 'Error := Negative response', sends 'Start_Reporting_Error(Error)', and ends at 'Idle'. A note indicates signals are to/from HLR unless shown otherwise.](93bd00a00fa28558486f0664550699b1_img.jpg) + +Process CCBS\_MONITORING\_VLR 1(4) + +``` +graph TD; Idle1([Idle]) --> Start_Reporting[/Start_Reporting/]; Start_Reporting --> Check_Parameters[Check_Parameters]; Check_Parameters -.-> GSM[See GSM 03.18]; Check_Parameters --> Result{Result}; Result -- Fail --> Error[Error := Negative response]; Error --> Start_Reporting_Error[/Start_Reporting_Error(Error)/]; Start_Reporting_Error --> Idle2([Idle]); Result -- Pass --> Event_Reporting[Event_Reporting := True]; Event_Reporting --> IMSI_Detached{IMSI Detached}; IMSI_Detached -- Yes --> Roaming{Roaming in LA allowed}; IMSI_Detached -- No --> Roaming; Roaming -- No --> Status_Not_Reachable[Status := CCBS_Not_Reachable]; Status_Not_Reachable --> Start_Reporting_Ack1[/Start_Reporting_Ack(Status)/]; Start_Reporting_Ack1 --> Monitoring_Detached([Monitoring Detached]); Roaming -- Yes --> Start_Status_Enquiry[/Start_Status_Enquiry/]; Start_Status_Enquiry -.-> MSC[To CCBS_Monitoring_MSC]; Start_Status_Enquiry --> Wait_For_Response([Wait_For_Response]); Wait_For_Response --> Status_Enquiry_Result[/Status_Enquiry Result/]; Status_Enquiry_Result -.-> From_MSC[From CCBS_Monitoring_MSC]; Status_Enquiry_Result --> CCBS_Not_Idle{CCBS_Not_Idle}; CCBS_Not_Idle -- Yes --> Status_Not_Idle[Status := CCBS_Not_Idle]; Status_Not_Idle --> Start_Reporting_Ack2[/Start_Reporting_Ack(Status)/]; Start_Reporting_Ack2 --> Monitoring_Not_Idle([Monitoring Not Idle]); CCBS_Not_Idle -- No --> Status_Idle[Status := CCBS_Idle]; Status_Idle --> Start_Reporting_Ack3[/Start_Reporting_Ack(Status)/]; Start_Reporting_Ack3 --> Monitoring_Idle([Monitoring Idle]); +``` + +Signals to / from left are to / from HLR unless shown otherwise + +Flowchart for Process CCBS\_MONITORING\_VLR. It starts at 'Idle', goes through 'Start\_Reporting', 'Check\_Parameters' (referencing GSM 03.18), and a 'Result' decision. If 'Pass', it sets 'Event\_Reporting := True' and checks if 'IMSI Detached'. If 'Yes', it checks if 'Roaming in LA allowed'. If 'No', it sets 'Status := CCBS\_Not\_Reachable' and ends at 'Monitoring Detached'. If 'Yes', it sends 'Start\_Status\_Enquiry' to 'CCBS\_Monitoring\_MSC', waits for a response, and checks the 'CCBS\_Not\_Idle' result. If 'Yes', it sets 'Status := CCBS\_Not\_Idle' and ends at 'Monitoring Not Idle'. If 'No', it sets 'Status := CCBS\_Idle' and ends at 'Monitoring Idle'. If 'Fail' at the 'Result' decision, it sets 'Error := Negative response', sends 'Start\_Reporting\_Error(Error)', and ends at 'Idle'. A note indicates signals are to/from HLR unless shown otherwise. + +Figure 11.3.1: Process CCBS\_Monitoring\_VLR (sheet 1 of 4) + +![Flowchart for Process CCBS_MONITORING_VLR. The diagram is split into two parts. The top part shows transitions from 'Monitoring Not Idle' to 'Monitoring Idle' or 'Monitoring Detached' based on 'Call_End', 'Detach', or 'Radio Failure' events. The bottom part shows transitions from 'Monitoring Detached' back to 'Monitoring Not Idle' or 'Monitoring Idle' based on 'Not_Idle', 'Location_Update', or 'MS_Activity' events, with status updates and event reporting logic.](d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg) + +Process CCBS\_MONITORING\_VLR 2(4) + +``` +graph TD + subgraph Top_Part [ ] + MNI1([Monitoring Not Idle]) --> CE{{Call_End}} + MNI1 --> D{{Detach}} + MNI1 --> RF{{Radio Failure}} + CE --> S1[Status := CCBS_Idle] + S1 --> ER1{Event_Reporting} + ER1 -- True --> ES1{{Event_Report (Status)}} + ES1 --> MI1([Monitoring Idle]) + ER1 -- False --> MI1 + D --> RF + RF --> MD1([Monitoring Detached]) + end + + subgraph Bottom_Part [ ] + MD2([Monitoring Detached]) --> NI{{Not_Idle}} + MD2 --> LU{{Location_Update}} + MD2 --> MA{{MS_Activity}} + NI --> MNI2([Monitoring Not Idle]) + LU --> S2[Status := CCBS_Idle] + S2 --> ER2{Event_Reporting} + ER2 -- True --> ES2{{Event_Report (Status)}} + ES2 --> MI2([Monitoring Idle]) + ER2 -- False --> MI2 + MA --> CM{CM Serv Type} + CM -- CSC --> End([ - ]) + CM -- SMS --> S2 + end + + Note1[From GSM 03.18 Processes OCH_MSC or ICH_MSC] -.-> CE + Note2[Signals to / from left are to / from HLR unless shown otherwise] -.-> RF + Note3[From GSM 03.18 Processes OCH_MSC or ICH_MSC +From GSM 03.93 Process MSC_CCBS Recall_Manager] -.-> NI + Note4[From GSM 03.18 Process_Access_Request_VLR] -.-> MA +``` + +Flowchart for Process CCBS\_MONITORING\_VLR. The diagram is split into two parts. The top part shows transitions from 'Monitoring Not Idle' to 'Monitoring Idle' or 'Monitoring Detached' based on 'Call\_End', 'Detach', or 'Radio Failure' events. The bottom part shows transitions from 'Monitoring Detached' back to 'Monitoring Not Idle' or 'Monitoring Idle' based on 'Not\_Idle', 'Location\_Update', or 'MS\_Activity' events, with status updates and event reporting logic. + +Figure 11.3.1: Process CCBS\_Monitoring\_VLR (sheet 2 of 4) + +![State transition diagram for Process CCBS_MONITORING_VLR. The diagram shows two main state transition paths. The top path starts at 'Monitoring Idle' and branches into 'Not_Idle', 'Radio Failure', 'Not Reachable', and 'Detach'. 'Not_Idle' leads to 'Status := CCBS_Not_Idle' and then to 'Event_Reporting'. 'Not Reachable' leads to 'Status := CCBS_Not_Reachable' and then to 'Event_Reporting'. Both 'Event_Reporting' decisions lead to 'Monitoring Not Idle' (True) or back to 'Monitoring Idle' (False). The bottom path starts at '*(Idle)' and branches into 'Continue Monitoring' and 'CCBS_Call'. 'CCBS_Call' leads to 'Event_Reporting := False' and then to a final state '-'. 'Continue Monitoring' also leads to the final state '-'. Annotations include: 'From GSM 03.18 Processes OCH_MSC or ICH_MSC From GSM 03.93 Process MSC_CCBS_Recall_Manager' for 'Not_Idle'; 'From GSM 03.18 Process ICH_VLR or VLR_CCBS_Recall_Manager' for 'Not Reachable'; 'Signals to / from left are to / from HLR unless shown otherwise'; and 'From GSM 03.18 Process ICH_VLR' for 'CCBS_Call'.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) + +Process CCBS\_MONITORING\_VLR + +3(4) + +``` +stateDiagram-v2 + [*] --> Monitoring_Idle : Monitoring Idle + Monitoring_Idle --> Not_Idle + Monitoring_Idle --> Radio_Failure : Radio Failure + Monitoring_Idle --> Not_Reachable + Monitoring_Idle --> Detach + Not_Idle --> Status_Net_Idle : Status := CCBS_Not_Idle + Status_Net_Idle --> Event_Reporting_Net + Event_Reporting_Net --> Monitoring_Net_Idle : True + Event_Reporting_Net --> Monitoring_Idle : False + Not_Reachable --> Status_Net_Reachable : Status := CCBS_Not_Reachable + Status_Net_Reachable --> Event_Reporting_Net_R + Event_Reporting_Net_R --> Monitoring_Detached : True + Event_Reporting_Net_R --> Monitoring_Idle : False + [*] --> Idle : *(Idle) + Idle --> Continue_Monitoring + Idle --> CCBS_Call + CCBS_Call --> Event_Reporting_False : Event_Reporting := False + Event_Reporting_False --> End : - + Continue_Monitoring --> End : - +``` + +From GSM 03.18 Processes OCH\_MSC or ICH\_MSC +From GSM 03.93 Process MSC\_CCBS\_Recall\_Manager + +Signals to / from left are to / from HLR unless shown otherwise + +From GSM 03.18 Process ICH\_VLR or VLR\_CCBS\_Recall\_Manager + +From GSM 03.18 Process ICH\_VLR + +State transition diagram for Process CCBS\_MONITORING\_VLR. The diagram shows two main state transition paths. The top path starts at 'Monitoring Idle' and branches into 'Not\_Idle', 'Radio Failure', 'Not Reachable', and 'Detach'. 'Not\_Idle' leads to 'Status := CCBS\_Not\_Idle' and then to 'Event\_Reporting'. 'Not Reachable' leads to 'Status := CCBS\_Not\_Reachable' and then to 'Event\_Reporting'. Both 'Event\_Reporting' decisions lead to 'Monitoring Not Idle' (True) or back to 'Monitoring Idle' (False). The bottom path starts at '\*(Idle)' and branches into 'Continue Monitoring' and 'CCBS\_Call'. 'CCBS\_Call' leads to 'Event\_Reporting := False' and then to a final state '-'. 'Continue Monitoring' also leads to the final state '-'. Annotations include: 'From GSM 03.18 Processes OCH\_MSC or ICH\_MSC From GSM 03.93 Process MSC\_CCBS\_Recall\_Manager' for 'Not\_Idle'; 'From GSM 03.18 Process ICH\_VLR or VLR\_CCBS\_Recall\_Manager' for 'Not Reachable'; 'Signals to / from left are to / from HLR unless shown otherwise'; and 'From GSM 03.18 Process ICH\_VLR' for 'CCBS\_Call'. + +Figure 11.3.1: Process CCBS\_Monitoring\_VLR (sheet 3 of 4) + +![State transition diagram for Process CCBS_MONITORING_VLR. The diagram is split into two main sections. The top section shows transitions from an initial '(Idle)' state to 'Cancel_Location', 'Event_Report_Error', 'CCBS_Call_Report_Error', and 'Stop_Reporting'. 'Cancel_Location' leads to 'Stop_Status_Enquiry' (which then goes to 'Idle'). 'Event_Report_Error', 'CCBS_Call_Report_Error', and 'Stop_Reporting' all lead to a common junction. A note indicates signals are from the left or HLR. The bottom section shows transitions from an initial '(Idle, Wait_For_Response)' state. 'CCBS_Call_Delivery (Outcome)' leads to 'Event_Reporting := True', which then leads to an 'Outcome' decision. The 'Outcome' decision has three paths: 'Absent_Subscriber' (leading to 'Mode := B', 'Status := CCBS_Not_Reachable', 'Outcome := Failure', 'CCBS_Call_Report', and 'Monitoring Detached'), 'Failure' (leading to 'Mode := B', 'Derive status from the current process state', 'CCBS_Call_Report', and a self-loop), and 'Success NDUB' (leading to 'Mode := B', 'Status := CCBS_Not_Idle', 'CCBS_Call_Report', and 'Monitoring Not Idle'). A note indicates only MT CCBS Call reporting interacts with this process.](9ba75f891de20483c291538e38701d96_img.jpg) + +Process CCBS\_MONITORING\_VLR 4(4) + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Cancel_Location + Cancel_Location --> Stop_Status_Enquiry + Stop_Status_Enquiry --> Idle + [*] --> Event_Report_Error + [*] --> CCBS_Call_Report_Error + [*] --> Stop_Reporting + Event_Report_Error --> Junction1 + CCBS_Call_Report_Error --> Junction1 + Stop_Reporting --> Junction1 + Junction1 --> Stop_Status_Enquiry + Note right of Junction1: Signals to / from left are to / from HLR unless shown otherwise + + [*] --> Idle_Wait + Idle_Wait --> CCBS_Call_Delivery + CCBS_Call_Delivery --> Event_Reporting + Event_Reporting --> Outcome + Outcome --> Absent_Subscriber + Outcome --> Failure + Outcome --> Success_NDUB + Absent_Subscriber --> Mode_Absent + Mode_Absent --> Outcome_Absent + Outcome_Absent --> CCBS_Call_Report_Absent + CCBS_Call_Report_Absent --> Monitoring_Detached + Failure --> Mode_Failure + Mode_Failure --> Derive_Status + Derive_Status --> CCBS_Call_Report_Failure + CCBS_Call_Report_Failure --> Idle_Wait + Success_NDUB --> Mode_Success + Mode_Success --> CCBS_Call_Report_Success + CCBS_Call_Report_Success --> Monitoring_Not_Idle + Note right of CCBS_Call_Delivery: Note: Only MT CCBS Call reporting is interacting with the monitoring process. MO call reporting is shown on VLR_CCBS_Recall_Manager +``` + +From subscriber datahandling in VLR + +To CCBS\_Monitoring\_MSC + +Signals to / from left are to / from HLR unless shown otherwise + +From GSM 03.18 Processes ICH\_MSC or ICH\_VLR + +Note: Only MT CCBS Call reporting is interacting with the monitoring process. MO call reporting is shown on VLR\_CCBS\_Recall\_Manager + +State transition diagram for Process CCBS\_MONITORING\_VLR. The diagram is split into two main sections. The top section shows transitions from an initial '(Idle)' state to 'Cancel\_Location', 'Event\_Report\_Error', 'CCBS\_Call\_Report\_Error', and 'Stop\_Reporting'. 'Cancel\_Location' leads to 'Stop\_Status\_Enquiry' (which then goes to 'Idle'). 'Event\_Report\_Error', 'CCBS\_Call\_Report\_Error', and 'Stop\_Reporting' all lead to a common junction. A note indicates signals are from the left or HLR. The bottom section shows transitions from an initial '(Idle, Wait\_For\_Response)' state. 'CCBS\_Call\_Delivery (Outcome)' leads to 'Event\_Reporting := True', which then leads to an 'Outcome' decision. The 'Outcome' decision has three paths: 'Absent\_Subscriber' (leading to 'Mode := B', 'Status := CCBS\_Not\_Reachable', 'Outcome := Failure', 'CCBS\_Call\_Report', and 'Monitoring Detached'), 'Failure' (leading to 'Mode := B', 'Derive status from the current process state', 'CCBS\_Call\_Report', and a self-loop), and 'Success NDUB' (leading to 'Mode := B', 'Status := CCBS\_Not\_Idle', 'CCBS\_Call\_Report', and 'Monitoring Not Idle'). A note indicates only MT CCBS Call reporting interacts with this process. + +Figure 11.3.1: Process CCBS\_Monitoring\_VLR (sheet 4 of 4) + +![](61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg) + +Process CCBS\_MONITORING\_MSC 1(1) + +Signals to/from the left are to/from the VLR; + signals to/from the right are to/from the BSS + unless marked otherwise + +``` + + stateDiagram-v2 + [*] --> Idle + Idle --> Start_Status_Enquiry + note right of Start_Status_Enquiry: From CCBS_Monitoring_VLR + Start_Status_Enquiry --> CCBS_Not_Idle_Decision + state CCBS_Not_Idle_Decision <> + CCBS_Not_Idle_Decision --> Status_Not_Idle: Yes + CCBS_Not_Idle_Decision --> Status_Idle: No + state Status_Not_Idle: Status := CCBS Not idle + state Status_Idle: Status := CCBS Idle + Status_Not_Idle --> Status_Enquiry_Result + Status_Idle --> Status_Enquiry_Result + note right of Status_Enquiry_Result: To CCBS_Monitoring_VLR + Status_Enquiry_Result --> Monitoring + Monitoring --> Stop_Status_Enquiry + note left of Stop_Status_Enquiry: From CCBS_Monitoring_VLR + Stop_Status_Enquiry --> Idle + Monitoring --> Radio_Link_Failure + Radio_Link_Failure --> Radio_Failure + Radio_Failure --> Terminal_State + state Terminal_State: - + +``` + +Figure 11.3.2: Process CCBS\_Monitoring\_MSC + +![SDL diagram for Process CCBS_Coordinator_HLR showing state transitions from Idle and any state (*).](b02ba0b73e95416eb547976f6145b169_img.jpg) + +**Process CCBS\_Coordinator\_HLR** 1(6) + +Signals to / from left are to / from the VLR unless shown otherwise + +``` + + graph TD + Idle([Idle]) + AnyState(( * )) + + %% Top Section + Idle --> SR_A_In[/From HLRA_Monitoring/] + SR_A_In --> SR_A_Out[Start_Reporting] + SR_A_Out --> Mon_A([Monitoring A]) + + Idle --> SR_B_In[/From HLRB_Monitoring/] + SR_B_In --> SR_B_Out[Start_Reporting] + SR_B_Out --> Mon_B([Monitoring B]) + + Idle --> CCR_In[/CCBS_Call_Report +(Mode, Outcome, Status)/] + CCR_In --> CheckP[[Check_Parameters]] + CheckP --> Result{Result} + + Result -- Pass --> Mode{Mode} + Result -- Fail --> ErrorSet[Error:= Negative response] + ErrorSet --> CCR_Err_Out[/CCBS_Call_Report_Report_Error(Error)/] + CCR_Err_Out --> Dash1([ - ]) + + Mode -- A --> CCR_Rec_In[/To HLRA_Recall_Manager/] + CCR_Rec_In --> CCR_Out[/CCBS_Call_Report(Outcome)/] + CCR_Out --> CCR_Ack_Out[/CCBS_Call_Report_Ack/] + CCR_Ack_Out --> Dash2([ - ]) + + Mode -- B --> CCR_Ack_Out + + %% Bottom Section + AnyState --> LU_In[/From subscriber datahandling in HLR/] + LU_In --> LU_A[/To HLRA_Monitoring/] + LU_A --> LU_B[/To HLRB_Monitoring/] + LU_B --> Idle_Return([Idle]) + + AnyState --> CM_In[/From HLRB_Request_Manager/] + CM_In --> CM_Out[Continue_Monitoring] + CM_Out --> Dash3([ - ]) + + %% Notes + Note1[Note: CCBS_Call_Report can exist on A side without ongoing monitoring in the MSC] + Note2[See GSM 03.18] + +``` + +Note: CCBS\_Call\_Report can exist on A side without ongoing monitoring in the MSC + +See GSM 03.18 + +SDL diagram for Process CCBS\_Coordinator\_HLR showing state transitions from Idle and any state (\*). + +**Figure 11.3.3: Process CCBS\_Coordinator\_HLR (sheet 1 of 6)** + +![Flowchart for Process CCBS_Coordinator_HLR (sheet 2 of 6). The diagram shows two main monitoring processes. The first process starts with 'Monitoring A', leading to 'CCBS_Call_Report(Mode, Outcome, Status)'. A note indicates that 'CCBS_Call_Report can exist on A side without ongoing monitoring in the MSC'. This leads to 'Check_Parameters' (referencing GSM 03.18), which leads to a 'Result' decision. If 'Fail', it goes to 'Error := Negative response' and then 'CCBS_Call_Report_Error(Error)'. If 'Pass', it goes to a 'Mode' decision. From 'Mode', path 'A' leads to 'CCBS_Call_Report(Outcome)' (referencing 'To HLRA_Recall_Manager') and then 'CCBS_Call_Report_Ack'. Path 'B' leads directly to 'CCBS_Call_Report_Ack'. Both lead to an end connector. The second process also starts with 'Monitoring A', leading to 'Start_Reporting_Error(Error)' and 'Event_Report(Status)'. 'Start_Reporting_Error(Error)' leads to 'Error := Negative response' and then 'Event_Report_Error(Error)'. 'Event_Report(Status)' leads to 'Check_Parameters' (referencing GSM 03.18), which leads to a 'Result' decision. If 'Fail', it goes to 'Error := Negative response' and then 'Event_Report_Error(Error)'. If 'Pass', it goes to 'Event_Report_Ack' and then 'Store Status'. Both 'Event_Report_Error(Error)' and 'Store Status' lead to 'Event_Report(Status)' and then an end connector. A 'Stop_Reporting' process is also shown, starting from 'From HLRA_Monitoring', leading to 'Stop_Reporting', and then to an 'Idle' state. A note indicates that 'Signals to / from left are to / from the VLR unless shown otherwise'.](710ff83dc4a77abbe489fbf1a462845a_img.jpg) + +Process CCBS\_Coordinator\_HLR 2(6) + +``` +graph TD + subgraph Monitoring_A_1 [Monitoring A] + M1([Monitoring A]) --> CR1[CCBS_Call_Report(Mode, Outcome, Status)] + CR1 --> CP1[Check_Parameters] + CP1 --> R1{Result} + R1 -- Fail --> E1[Error := Negative response] + E1 --> CRE1[CCBS_Call_Report_Error(Error)] + R1 -- Pass --> MD1{Mode} + MD1 -- A --> CR2[CCBS_Call_Report(Outcome)] + CR2 --> CRA1[CCBS_Call_Report_Ack] + MD1 -- B --> CRA1 + CRA1 --> EN1[ ] + end + subgraph Monitoring_A_2 [Monitoring A] + M2([Monitoring A]) --> SR1[Start_Reporting_Error(Error)] + SR1 --> E2[Error := Negative response] + E2 --> ER1[Event_Report_Error(Error)] + M2 --> ES1[Event_Report(Status)] + ES1 --> CP2[Check_Parameters] + CP2 --> R2{Result} + R2 -- Fail --> E3[Error := Negative response] + E3 --> ER2[Event_Report_Error(Error)] + R2 -- Pass --> ER3[Event_Report_Ack] + ER3 --> SS[Store Status] + ER1 --> ES2[Event_Report(Status)] + SS --> ES2 + ES2 --> EN2[ ] + end + subgraph Stop_Reporting + SR[Stop_Reporting] --> ID[Idle] + end + Note1[Note: CCBS_Call_Report can exist on A side without ongoing monitoring in the MSC] -.-> CR1 + Note2[From HLRA_Monitoring] -.-> SR + Note3[Signals to / from left are to / from the VLR unless shown otherwise] -.-> EN1 + Note4[See GSM 03.18] -.-> CP1 + Note5[To HLRA_Recall_Manager] -.-> CR2 + Note6[See GSM 03.18] -.-> CP2 +``` + +Flowchart for Process CCBS\_Coordinator\_HLR (sheet 2 of 6). The diagram shows two main monitoring processes. The first process starts with 'Monitoring A', leading to 'CCBS\_Call\_Report(Mode, Outcome, Status)'. A note indicates that 'CCBS\_Call\_Report can exist on A side without ongoing monitoring in the MSC'. This leads to 'Check\_Parameters' (referencing GSM 03.18), which leads to a 'Result' decision. If 'Fail', it goes to 'Error := Negative response' and then 'CCBS\_Call\_Report\_Error(Error)'. If 'Pass', it goes to a 'Mode' decision. From 'Mode', path 'A' leads to 'CCBS\_Call\_Report(Outcome)' (referencing 'To HLRA\_Recall\_Manager') and then 'CCBS\_Call\_Report\_Ack'. Path 'B' leads directly to 'CCBS\_Call\_Report\_Ack'. Both lead to an end connector. The second process also starts with 'Monitoring A', leading to 'Start\_Reporting\_Error(Error)' and 'Event\_Report(Status)'. 'Start\_Reporting\_Error(Error)' leads to 'Error := Negative response' and then 'Event\_Report\_Error(Error)'. 'Event\_Report(Status)' leads to 'Check\_Parameters' (referencing GSM 03.18), which leads to a 'Result' decision. If 'Fail', it goes to 'Error := Negative response' and then 'Event\_Report\_Error(Error)'. If 'Pass', it goes to 'Event\_Report\_Ack' and then 'Store Status'. Both 'Event\_Report\_Error(Error)' and 'Store Status' lead to 'Event\_Report(Status)' and then an end connector. A 'Stop\_Reporting' process is also shown, starting from 'From HLRA\_Monitoring', leading to 'Stop\_Reporting', and then to an 'Idle' state. A note indicates that 'Signals to / from left are to / from the VLR unless shown otherwise'. + +Figure 11.3.3: Process CCBS\_Coordinator\_HLR (sheet 2 of 6) + +![Flowchart for Process CCBS_Coordinator_HLR, sheet 3 of 6. It shows state transitions and signal handling for Monitoring A and Monitoring B states in an HLR coordinator process.](1cd38e4f2ffcae2871964fa6313a9a27_img.jpg) + +Process CCBS\_Coordinator\_HLR + +3(6) + +Signals to / from left are to / from the VLR unless shown otherwise + +``` + +graph TD + subgraph Monitoring_A_Section [Monitoring A] + MA([Monitoring A]) + MA --- L1[ ] + L1 --- SRA[Start_Reporting_Ack +Status] + L1 --- SR[Start_Reporting] + L1 --- RD[Restore_Data] + + SRA --> SS[Store Status] + SS --> ER1[Event_Report +Status] + ER1 --> THLRA1[To HLRA_Monitoring] + ER1 --> THLRB1[To HLRB_Monitoring] + ER1 --> END1([ - ]) + + SR --- FHLRB[From HLRB_Monitoring] + SR --> SA1{Status +available} + SA1 -- No --> MAB1([Monitoring +A + B]) + SA1 -- Yes --> ER2[Event_Report +Status] + ER2 --> MAB1 + + RD --- FSD1[From subscriber +datahandling in +HLR] + RD --> SR2[Start_Reporting] + SR2 --> END2([ - ]) + end + + subgraph Monitoring_B_Section [Monitoring B] + MB([Monitoring B]) + MB --- L2[ ] + L2 --- SRB[Start_Reporting] + L2 --- RDB[Restore_Data] + + SRB --- FHLRA[From HLRA_Monitoring] + SRB --> SA2{Status +available} + SA2 -- No --> END3([ - ]) + SA2 -- Yes --> ER3[Event_Report +Status] + ER3 --> THLRA2[To HLRA_Monitoring] + ER3 --> MAB2([Monitoring +A + B]) + + RDB --- FSD2[From subscriber +datahandling in +HLR] + RDB --> SR3[Start_Reporting] + SR3 --> END4([ - ]) + end + +``` + +Flowchart for Process CCBS\_Coordinator\_HLR, sheet 3 of 6. It shows state transitions and signal handling for Monitoring A and Monitoring B states in an HLR coordinator process. + +**Figure 11.3.3: Process CCBS\_Coordinator\_HLR (sheet 3 of 6)** + +![State transition diagram for Process CCBS_Coordinator_HLR. The diagram shows two main states: 'Monitoring B' and 'Idle'. Transitions include 'Start_Reporting_Ack(Status)', 'Start_Reporting_Error', 'From HLRB_Monitoring', and 'Stop_Reporting'. The 'Monitoring B' state leads to 'Start_Reporting_Ack(Status)' which leads to 'Store Status' and then 'Event_Report (Status)' to 'To HLRB_Monitoring'. 'Start_Reporting_Error' leads to 'Status := Not_Reachable' and then 'Event_Report (Status)'. 'From HLRB_Monitoring' leads to 'Stop_Reporting' which leads to 'Idle'. 'Stop_Reporting' also leads to 'Monitoring B'. The 'Monitoring B' state also leads to 'Event_Report (Status)' which leads to 'Check_Parameters' (See GSM 03.18). 'Check_Parameters' leads to 'Result'. 'Result' leads to 'Pass' (Store Status, Event_Report_Ack, Event_Report (Status) to To HLRB_Monitoring) or 'Fail' (Error := Negative response, Event_Report_Error(Error), Status := Not_Reachable, Event_Report (Status) to To HLRB_Monitoring). 'CCBS_Call_Report (Mode, Outcome, Status)' leads to 'Check_Parameters' (See GSM 03.18). 'Check_Parameters' leads to 'Result'. 'Result' leads to 'Pass' (CCBS_Call_Report_Ack, Mode) or 'Fail' (Error := Negative response, CCBS_Call_Report_Error (Error), Outcome := Failure, Status := Not_Reachable). 'Mode' leads to 'A' (CCBS_Call_Report (Outcome) to To HLRA_Recall_Manager) or 'B' (CCBS_Call_Report (Outcome, Status) to To HLRB_Monitoring, Store Status). Both 'A' and 'B' lead to the end state.](884c44b6cb9fbe15347e0562a6085df2_img.jpg) + +Process CCBS\_Coordinator\_HLR 4(6) + +``` +stateDiagram-v2 + [*] --> Monitoring_B + state "Monitoring B" as Monitoring_B + Monitoring_B --> Start_Reporting_Ack + Start_Reporting_Ack --> Store_Status_1[Store Status] + Store_Status_1 --> Event_Report_Status_1[Event_Report (Status)] + Event_Report_Status_1 --> To_HLRB_Monitoring_1[To HLRB_Monitoring] + Event_Report_Status_1 --> End_1([ - ]) + Monitoring_B --> Start_Reporting_Error + Start_Reporting_Error --> Status_Not_Reachable_1[Status := Not_Reachable] + Status_Not_Reachable_1 --> Event_Report_Status_2[Event_Report (Status)] + Event_Report_Status_2 --> To_HLRB_Monitoring_2[To HLRB_Monitoring] + Event_Report_Status_2 --> End_2([ - ]) + Monitoring_B --> From_HLRB_Monitoring + From_HLRB_Monitoring --> Stop_Reporting_1[Stop_Reporting] + Stop_Reporting_1 --> Idle + Stop_Reporting_1 --> Monitoring_B + Monitoring_B --> Event_Report_Status_3[Event_Report (Status)] + Event_Report_Status_3 --> Check_Parameters_1[Check_Parameters] + Check_Parameters_1 --> Result_1[Result] + Result_1 --> Pass_1[Store Status] + Pass_1 --> Event_Report_Ack[Event_Report_Ack] + Event_Report_Ack --> Event_Report_Status_4[Event_Report (Status)] + Event_Report_Status_4 --> To_HLRB_Monitoring_3[To HLRB_Monitoring] + Event_Report_Status_4 --> End_3([ - ]) + Result_1 --> Fail_1[Error := Negative response] + Fail_1 --> Event_Report_Error[Event_Report_Error(Error)] + Event_Report_Error --> Status_Not_Reachable_2[Status := Not_Reachable] + Status_Not_Reachable_2 --> Event_Report_Status_5[Event_Report (Status)] + Event_Report_Status_5 --> To_HLRB_Monitoring_4[To HLRB_Monitoring] + Event_Report_Status_5 --> End_4([ - ]) + Monitoring_B --> CCBS_Call_Report + CCBS_Call_Report --> Check_Parameters_2[Check_Parameters] + Check_Parameters_2 --> Result_2[Result] + Result_2 --> Pass_2[CCBS_Call_Report_Ack] + Pass_2 --> Mode[Mode] + Mode --> A[CCBS_Call_Report (Outcome)] + A --> To_HLRA_Recall_Manager[To HLRA_Recall_Manager] + A --> End_5([ - ]) + Mode --> B[CCBS_Call_Report (Outcome, Status)] + B --> To_HLRB_Monitoring_5[To HLRB_Monitoring] + B --> Store_Status_2[Store Status] + Store_Status_2 --> End_6([ - ]) + Result_2 --> Fail_2[Error := Negative response] + Fail_2 --> CCBS_Call_Report_Error[CCBS_Call_Report_Error (Error)] + CCBS_Call_Report_Error --> Outcome_Failure[Outcome := Failure, Status := Not_Reachable] + Outcome_Failure --> End_7([ - ]) + Note right of Start_Reporting_Ack: Signals to / from left are to / from the VLR unless shown otherwise + Note right of Check_Parameters_1: See GSM 03.18 + Note right of Check_Parameters_2: See GSM 03.18 +``` + +State transition diagram for Process CCBS\_Coordinator\_HLR. The diagram shows two main states: 'Monitoring B' and 'Idle'. Transitions include 'Start\_Reporting\_Ack(Status)', 'Start\_Reporting\_Error', 'From HLRB\_Monitoring', and 'Stop\_Reporting'. The 'Monitoring B' state leads to 'Start\_Reporting\_Ack(Status)' which leads to 'Store Status' and then 'Event\_Report (Status)' to 'To HLRB\_Monitoring'. 'Start\_Reporting\_Error' leads to 'Status := Not\_Reachable' and then 'Event\_Report (Status)'. 'From HLRB\_Monitoring' leads to 'Stop\_Reporting' which leads to 'Idle'. 'Stop\_Reporting' also leads to 'Monitoring B'. The 'Monitoring B' state also leads to 'Event\_Report (Status)' which leads to 'Check\_Parameters' (See GSM 03.18). 'Check\_Parameters' leads to 'Result'. 'Result' leads to 'Pass' (Store Status, Event\_Report\_Ack, Event\_Report (Status) to To HLRB\_Monitoring) or 'Fail' (Error := Negative response, Event\_Report\_Error(Error), Status := Not\_Reachable, Event\_Report (Status) to To HLRB\_Monitoring). 'CCBS\_Call\_Report (Mode, Outcome, Status)' leads to 'Check\_Parameters' (See GSM 03.18). 'Check\_Parameters' leads to 'Result'. 'Result' leads to 'Pass' (CCBS\_Call\_Report\_Ack, Mode) or 'Fail' (Error := Negative response, CCBS\_Call\_Report\_Error (Error), Outcome := Failure, Status := Not\_Reachable). 'Mode' leads to 'A' (CCBS\_Call\_Report (Outcome) to To HLRA\_Recall\_Manager) or 'B' (CCBS\_Call\_Report (Outcome, Status) to To HLRB\_Monitoring, Store Status). Both 'A' and 'B' lead to the end state. + +Figure 11.3.3: Process CCBS\_Coordinator\_HLR (sheet 4 of 6) + +![SDL Flowchart for Process CCBS_Coordinator_HLR (sheet 5 of 6)](b0384c8e0ff826a8116ab2ff67dadc43_img.jpg) + +Process CCBS\_Coordinator\_HLR + +5(6) + +Signals to / from left are to / from the VLR unless shown otherwise + +``` + +graph TD + State1([Monitoring +A + B]) + + %% Path 1 + State1 --> In1[/Event_ +Report +(Status)/] + In1 --> Task1[Check_ +Parameters] + Task1 --> Dec1{Result} + Dec1 -- Fail --> Task2[Error := +Negative +response] + Task2 --> Out1[/Event_ +Report_ +Error(Error)/] + Out1 --> Task3[Status := +Not_Reachable] + Task3 --> In2[/Event_ +Report +(Status)/] + In2 --> Proc1(To HLRB_ +Monitoring) + Proc1 --> In3[/Event_ +Report +(Status)/] + In3 --> Proc2(To HLRA_ +Monitoring) + Proc2 --> State1 + + %% Path 2 + State1 --> In4[/Start_ +Reporting_ +Ack(Status)/] + In4 --> Join1 + + %% Path 3 + State1 --> In5[/Start_ +Reporting_ +Error/] + In5 --> Task4[Status := +Not_Reachable] + Task4 --> Join1 + + %% Path 4 + State1 --> In6[/CCBS_Call_ +Report(Mode, +Outcome, +Status)/] + In6 --> Task5[Check_ +Parameters] + Task5 --> Dec2{Result} + Dec2 -- Fail --> Task6[Error := +Negative +response] + Task6 --> Out2[/CCBS_Call_ +Report_ +Error(Error)/] + Out2 --> Task7[Outcome:=Failure +Status := +Not_Reachable] + Task7 --> Join2 + + Dec1 -- Pass --> Out3[/Event_ +Report_ +Ack/] + Out3 --> Join1 + + Dec2 -- Pass --> Out4[/CCBS_Call_ +Report_Ack/] + Out4 --> Join2 + + Join2 --> Dec3{Mode} + Dec3 -- B --> Out5[/CCBS_Call_ +Report +(Outcome, +Status)/] + Out5 --> Proc3(To HLRB_ +Monitoring) + Proc3 --> In7[/Event_ +Report +(Status)/] + + Dec3 -- A --> Out6[/CCBS_Call_ +Report +(Outcome)/] + Out6 --> Proc4(To HLRA_ +Monitoring) + Proc4 --> In8[/Event_ +Report +(Status)/] + + Join1 --> In7 + In7 --> Proc5(To HLRB_ +Monitoring) + Proc5 --> In8 + In8 --> Proc6(To HLRA_ +Monitoring) + Proc6 --> Task8[Store Status] + Task8 --> End([ - ]) + + %% Additional connections + Task8 --> Proc7(To HLRA_ +Recall_ +Manager) + Proc7 --> Out7[/CCBS_Call_ +Report +(Outcome)/] + +``` + +SDL Flowchart for Process CCBS\_Coordinator\_HLR (sheet 5 of 6) + +**Figure 11.3.3: Process CCBS\_Coordinator\_HLR (sheet 5 of 6)** + +![SDL diagram for Process CCBS_Coordinator_HLR showing transitions from state Monitoring A + B based on signals from HLRA, HLRB, and subscriber datahandling.](223792b3652794024244c277cc46394b_img.jpg) + +Process CCBS\_Coordinator\_HLR + +6(6) + +``` + +stateDiagram-v2 + state "Monitoring\nA + B" as MAB + state "Monitoring\nB" as MB + state "Monitoring\nA" as MA + state "-" as Dash + + MAB --> Stop_Reporting_A : From HLRA_\nMonitoring + Stop_Reporting_A --> MB : Stop_\nReporting + + MAB --> Stop_Reporting_B : From HLRB_\nMonitoring + Stop_Reporting_B --> MA : Stop_\nReporting + + MAB --> Restore_Data : From subscriber\ndatahandling in\nHLR + Restore_Data --> Start_Reporting : Restore_\nData + Start_Reporting --> Dash : Start_\nReporting + +``` + +Signals to / from left are to / from the VLR unless shown otherwise + +SDL diagram for Process CCBS\_Coordinator\_HLR showing transitions from state Monitoring A + B based on signals from HLRA, HLRB, and subscriber datahandling. + +**Figure 11.3.3: Process CCBS\_Coordinator\_HLR (sheet 6 of 6)** + +![Flowchart for Procedure CCBS_Set_Diagnostic_For_Release. It starts with a connector, followed by a decision 'CCBS Target'. If 'False', it goes to 'Diagnostic := CCBS Not Possible'. If 'True', it goes to another decision. The second decision has a 'No' path leading to 'Diagnostic := CCBS Possible' and a 'Yes' path leading to a decision 'Call Completion Treatment Indicator present in SII2?'. If 'Yes' to the second decision, it goes to a decision 'Call Completion Treatment Indicator set to Reject Call Completion Service Request?'. If 'Yes' to this third decision, it goes to 'Diagnostic := CCBS Not Possible'. If 'No' to the third decision, it goes to 'Diagnostic := CCBS Possible'. Both 'Diagnostic' boxes lead to an exit connector.](b55cd9b5721bd8aabc979c85316924e4_img.jpg) + +Procedure CCBS\_Set\_Diagnostic\_For\_Release 1(1) + +``` +graph TD; Start([ ]) --> CCBS_Target{CCBS Target}; CCBS_Target -- False --> NotPossible[Diagnostic := CCBS Not Possible]; CCBS_Target -- True --> Decision2{ }; Decision2 -- No --> Possible[Diagnostic := CCBS Possible]; Decision2 -- Yes --> SII2{Call Completion Treatment Indicator present in SII2?}; SII2 -- Yes --> Reject{Call Completion Treatment Indicator set to Reject Call Completion Service Request?}; Reject -- Yes --> NotPossible; Reject -- No --> Possible; NotPossible --> End(( )); Possible --> End +``` + +Flowchart for Procedure CCBS\_Set\_Diagnostic\_For\_Release. It starts with a connector, followed by a decision 'CCBS Target'. If 'False', it goes to 'Diagnostic := CCBS Not Possible'. If 'True', it goes to another decision. The second decision has a 'No' path leading to 'Diagnostic := CCBS Possible' and a 'Yes' path leading to a decision 'Call Completion Treatment Indicator present in SII2?'. If 'Yes' to the second decision, it goes to a decision 'Call Completion Treatment Indicator set to Reject Call Completion Service Request?'. If 'Yes' to this third decision, it goes to 'Diagnostic := CCBS Not Possible'. If 'No' to the third decision, it goes to 'Diagnostic := CCBS Possible'. Both 'Diagnostic' boxes lead to an exit connector. + +Figure 11.3.4: Procedure CCBS\_Set\_Diagnostic\_For\_Release + +![A flowchart diagram for Procedure CCBS_Report_Not_Idle. It starts with a dashed box (note) in the top left. The main flow consists of a vertical line connecting a rounded rectangle at the top to a 'Not_Idle' decision diamond. From the 'Not_Idle' diamond, a horizontal dashed line leads to a dashed box labeled 'To CCBS_Monitoring_VLR'. The vertical line continues from the bottom of the 'Not_Idle' diamond to a circle with an 'X' at the bottom.](2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg) + +Procedure CCBS\_Report\_Not\_Idle 1(1) + +``` +graph TD; A[ ] --- B{Not_Idle}; B --> C[To CCBS_Monitoring_VLR]; B --- D((X)); style A fill:none,stroke-dasharray: 5 5; style C fill:none,stroke-dasharray: 5 5; +``` + +A flowchart diagram for Procedure CCBS\_Report\_Not\_Idle. It starts with a dashed box (note) in the top left. The main flow consists of a vertical line connecting a rounded rectangle at the top to a 'Not\_Idle' decision diamond. From the 'Not\_Idle' diamond, a horizontal dashed line leads to a dashed box labeled 'To CCBS\_Monitoring\_VLR'. The vertical line continues from the bottom of the 'Not\_Idle' diamond to a circle with an 'X' at the bottom. + +Figure 11.3.5: Procedure CCBS\_Report\_Not\_Idle + +![Flowchart for Procedure CCBS_Report_MS_Activity. The flow starts with a connector symbol, followed by a process block 'Reason:= CM SERV TYPE'. This leads to a decision block 'MS Activity'. From 'MS Activity', one path goes to a dashed box 'To CCBS_Monitoring_VLR' and the other continues down to an end connector symbol. A dashed note box is in the top left corner.](6059b0a3a051cc20b414d51a4e412f3e_img.jpg) + +Procedure CCBS\_Report\_MS\_Activity 1(1) + +``` +graph TD; Start([ ]) --> Process[Reason:= CM SERV TYPE]; Process --> Decision{MS Activity}; Decision --> ToCCBS[To CCBS_Monitoring_VLR]; Decision --> End((X)); +``` + +Flowchart for Procedure CCBS\_Report\_MS\_Activity. The flow starts with a connector symbol, followed by a process block 'Reason:= CM SERV TYPE'. This leads to a decision block 'MS Activity'. From 'MS Activity', one path goes to a dashed box 'To CCBS\_Monitoring\_VLR' and the other continues down to an end connector symbol. A dashed note box is in the top left corner. + +Figure 11.3.6: Procedure CCBS\_Report\_MS\_Activity + +![Flowchart for Procedure CCBS_Check_Last_Call. It starts with a connector symbol, leading to a decision diamond 'Last CC connection'. If 'No', it goes to a circle with an 'X'. If 'Yes', it goes to a 'Call End' block, which then points to 'To CCBS_Monitoring_VLR' and also to the circle with an 'X'.](09797d4289ec96309d21a9a993153dab_img.jpg) + +Procedure CCBS\_Check\_Last\_Call 1(1) + +``` +graph TD; Start([ ]) --> Decision{Last CC connection}; Decision -- No --> End((X)); Decision -- Yes --> CallEnd{{Call End}}; CallEnd --> ToCCBS[To CCBS_Monitoring_VLR]; CallEnd --> End; +``` + +Flowchart for Procedure CCBS\_Check\_Last\_Call. It starts with a connector symbol, leading to a decision diamond 'Last CC connection'. If 'No', it goes to a circle with an 'X'. If 'Yes', it goes to a 'Call End' block, which then points to 'To CCBS\_Monitoring\_VLR' and also to the circle with an 'X'. + +Figure 11.3.7: Procedure CCBS\_Check\_Last\_Call + +# 12 Information stored in the HLRs + +Note that a given subscriber may be both the originator and the target of CCBS requests; a given HLR may therefore be required to store both the data for HLR A and the data for HLR B against a given subscriber. + +## 12.1 Originating Network Data + +The following logical states are applicable for the CCBS service in the originating network (refer to TS 23.011 for an explanation of the notation): + +| <b>Provisioning State</b> | <b>Registration State</b> | <b>Activation State</b> | <b>HLR Induction State</b> | +|---------------------------|---------------------------|-------------------------|----------------------------| +| (Not Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Active and Operative | Not Induced) | + +The logical state shall be on a per subscriber basis and hence the same for all basic service groups. + +The HLR shall store the logical state of the CCBS service (which shall be one of the valid states listed above) on a per subscriber basis. The HLR shall store the following information for each CCBS Request that is successfully activated by subscriber A: + +- AddressOfB; +- Basic Service Group; +- CCBS Call Information; +- Translated Number; +- Retention supported by destination network (if HLR A supports retention); +- CCBS Index; +- CAMEL Invoked. + +The HLR shall store for the served subscriber as the originator of CCBS requests: + +- The parameter “Max Queue Size”, +- This parameter takes a value in the range 1 to 5. + +## 12.2 Destination Network Data + +The following logical states are applicable for the CCBS service in the destination network (refer to TS 23.011 for an explanation of the notation): + +| <b>Provisioning State</b> | <b>Registration State</b> | <b>Activation State</b> | <b>HLR Induction State</b> | +|---------------------------|---------------------------|-------------------------|----------------------------| +| (Not Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Active and Operative, | Not Induced) | + +The logical state shall be on a per subscriber basis and hence the same for all basic service groups. + +The HLR shall store the logical state of the CCBS service (which shall be one of the valid states listed above) on a per subscriber basis. + +The HLR shall store the following information for each CCBS Request that is successfully activated against User B : + +- Basic Service Group; +- Retention supported by originating network (if HLR B supports retention). + +The HLR shall store on a per subscriber basis: + +The parameter "Number of terminating CCBS Requests" + +This parameter takes a value in the range 1 to 5. + +## 12.3 Transfer of information from HLR to VLR + +If the provisioning state for CCBS supplementary service is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of CCBS supplementary service. + +If the logical state of CCBS supplementary service is changed while a subscriber is registered on a VLR, then the HLR shall inform the VLR of the new logical state of CCBS supplementary service. + +Both originating and destination network CCBS supplementary service logical states are updated independently of each other to the VLR. + +# 13 State transition model + +## 13.1 State transition model for the CCBS service in the originating network + +Figure 13.1.1 shows the successful cases of transition between the applicable logical states of the CCBS service in the originating network. The state changes may be caused by actions of the service provider or the network. + +![State transition model for the CCBS service in the originating network](819f1d00e68b342a246b64fa888a97f9_img.jpg) + +``` +stateDiagram-v2 + [*] --> Not_Provisioned + state "Not Provisioned<br/>Not Applicable<br/>Not Active<br/>Not Induced" as Not_Provisioned + state "Provisioned<br/>Not Applicable<br/>Active and Operative<br/>Not Induced" as Provisioned + Not_Provisioned --> Provisioned : Provision + Provisioned --> Not_Provisioned : Withdrawal +``` + +The diagram illustrates the state transition model for the CCBS service in the originating network. It consists of two states represented by ovals. The left state is labeled "Not Provisioned" and contains the sub-states "Not Applicable", "Not Active", and "Not Induced". The right state is labeled "Provisioned" and contains the sub-states "Not Applicable", "Active and Operative", and "Not Induced". A curved arrow labeled "Provision" points from the left state to the right state. A curved arrow labeled "Withdrawal" points from the right state back to the left state. + +State transition model for the CCBS service in the originating network + +Figure 13.1.1: State Transition Model for CCBS Service in the originating network + +## 13.2 State transition model for the CCBS service in the destination network + +Figure 13.2.1 shows the successful cases of transition between the applicable logical states of the CCBS service in the destination network. The state changes may be caused by actions of the service provider or the network. + +![State transition model for the CCBS service in the destination network](c817f3df24c6107d07c517dce71ed086_img.jpg) + +``` +stateDiagram-v2 + [*] --> Not_Provisioned + state "Not Provisioned<br/>Not Applicable<br/>Not Active<br/>Not Induced" as Not_Provisioned + state "Provisioned<br/>Not Applicable<br/>Active and Operative<br/>Not Induced" as Provisioned + Not_Provisioned --> Provisioned : Provision + Provisioned --> Not_Provisioned : Withdrawal +``` + +The diagram illustrates the state transition model for the CCBS service in the destination network. It consists of two states represented by ovals. The left state is labeled "Not Provisioned" and contains the sub-states "Not Applicable", "Not Active", and "Not Induced". The right state is labeled "Provisioned" and contains the sub-states "Not Applicable", "Active and Operative", and "Not Induced". A curved arrow labeled "Provision" points from the left state to the right state. A curved arrow labeled "Withdrawal" points from the right state back to the left state. + +State transition model for the CCBS service in the destination network + +Figure 13.2.1: State Transition Model for CCBS Service in the destination network + +## 13.3 State transition model for a CCBS Request + +Figure 13.3.1 shows the successful cases of transition between the applicable logical states of a CCBS Request. The state changes may be caused by actions of the served subscriber or the network. + +Each subscriber can be considered to have a set of n requests, where n is the maximum number of CCBS requests allowed for a subscriber as an originator. + +![State transition diagram for a CCBS Request showing four states: Start, Active, Suspend, and Recall with various transitions between them.](5e022ae60ba810b1e6de0645671b9dd3_img.jpg) + +``` +stateDiagram-v2 + [*] --> Start + Start --> Active : CCBS Request + Active --> Start : CCBS Cancel + Active --> Recall : CCBS Recall + Recall --> Active : CCBS Resume + Recall --> Suspend : CCBS Suspend + Recall --> Start : CCBS Cancel, CCBS Complete + Suspend --> Start : CCBS Cancel +``` + +The diagram illustrates the state transitions for a CCBS Request. It consists of four states represented by ovals: 'Start' (top), 'Active' (left), 'Suspend' (right), and 'Recall' (bottom). Transitions are indicated by arrows with labels: 'CCBS Request' from Start to Active; 'CCBS Cancel' from Active to Start and from Suspend to Start; 'CCBS Recall' from Active to Recall; 'CCBS Resume' from Recall to Active; 'CCBS Suspend' from Recall to Suspend; and 'CCBS Cancel' and 'CCBS Complete' from Recall to Start. + +State transition diagram for a CCBS Request showing four states: Start, Active, Suspend, and Recall with various transitions between them. + +**Figure 13.3.1: State Transition Model for a CCBS Request in Originating Network** + +On provision of the CCBS service, all requests transit to the "Start" state + +![State transition diagram for a CCBS Request in Destination Network. States: Start, Active & Operative, Active & Quiescent, Suspend & Quiescent, Suspend, Recall. Transitions include CCBS Request, CCBS Cancel, SS Int, CCBS Resume, CCBS Suspend, CCBS Complete, and CCBS Recall.](511f9b05a4c458937dd12c30936fd7d6_img.jpg) + +``` +stateDiagram-v2 + [*] --> Start + Start --> Active & Operative: CCBS Request + Active & Operative --> Start: CCBS Cancel + Active & Operative --> Active & Quiescent: SS Int + Active & Operative --> Recall: CCBS Recall + Active & Quiescent --> Start: CCBS Cancel + Active & Quiescent --> Active & Operative: SS Int + Active & Quiescent --> Suspend & Quiescent: CCBS Resume + Suspend & Quiescent --> Start: CCBS Cancel + Suspend & Quiescent --> Suspend: SS Int + Suspend --> Start: CCBS Cancel + Suspend --> Active & Operative: CCBS Resume + Suspend --> Recall: CCBS Suspend + Recall --> Start: CCBS Complete + Recall --> Suspend: CCBS Cancel +``` + +State transition diagram for a CCBS Request in Destination Network. States: Start, Active & Operative, Active & Quiescent, Suspend & Quiescent, Suspend, Recall. Transitions include CCBS Request, CCBS Cancel, SS Int, CCBS Resume, CCBS Suspend, CCBS Complete, and CCBS Recall. + +Figure 13.3.2: State Transition Model for a CCBS Request in Destination Network + +## 13.4 Information stored in the VLRs + +### Originating Network Data + +For the CCBS service in the originating network the VLR shall store the service state information received from HLR. + +### Destination Network Data + +For the CCBS service in the destination network the VLR shall store the service state information received from HLR. + +# --- Annex A (informative): Message flow diagrams showing a successful CCBS request + +The following message flow diagrams show a successful CCBS request. Destination B busy when request activated, subscriber A free when destination B becomes free (mobile-to-mobile). + +![Sequence diagram for CCBS (Call Completion on Busy Subscriber) service logic showing interactions between MS, MSC, VLR, HLRA, GMSC, HLRB, and MSC/VLR entities.](649426750a89fa0e5d7c1736d5cf72c6_img.jpg) + +**Sequence Diagram: CCBS Service Logic** + +The diagram depicts the signaling flow for CCBS across multiple network entities. Key phases include: + +- Initial Call Attempt:** MS initiates a call via OCH\_MSC, which reaches MT\_GMSC and HLRB. The call is released with a 'CCBS Possible' indication. +- CCBS Activation:** MS sends a CCBS Request. This request is processed by HLRA and forwarded to HLRB. +- Monitoring:** HLRB starts monitoring the destination B-subscriber. States transition from IDLE to MONITORING. Event reports (e.g., CCBS\_Idle, CCBS Not Idle) are exchanged between the MSC/VLR and HLRB. +- Recall and Completion:** Once the B-subscriber becomes idle, HLRB initiates a recall. This involves Select\_Request, Send\_RUF (Remote User Free), and transitions to SELECTED and WAIT\_FOR\_CCBS\_CALL states. + +**Entities and Components:** + +- MS:** Mobile Station. +- MSC / VLR:** Mobile Switching Center and Visitor Location Register (OCH\_MSC, ICH\_MSC). +- HLRA / HLRB:** Home Location Registers for subscriber A and B, including Request Managers and Monitoring components. +- GMSC:** Gateway MSC (MT\_GMSC). + +Sequence diagram for CCBS (Call Completion on Busy Subscriber) service logic showing interactions between MS, MSC, VLR, HLRA, GMSC, HLRB, and MSC/VLR entities. + + + +![Sequence diagram for CCBS (Call Completion on Busy Subscriber) service. Lifelines include MSC_CCBS_Recall_Manager, VLR_CCBS_Recall_Manager, HLRA_Request_Manager, HLRA_Request, HLRA_Recall_Manager, MT_GMSC, HLRB_Request_Manager, HLRB_Request, HLRB_Recall_Manager, HLRB_Monitoring, HLRB_Blocking, CCBS_Coordinator_HLR, ICH_VLR, and ICH_MSC. The process involves setup, busy detection, request, recall, and completion phases.](9ef15a4afab1416db28b91184862a3a5_img.jpg) + +The sequence diagram illustrates the interaction for the CCBS service across several network entities: + +- MSC\_CCBS\_Recall\_Manager:** Handles the initial paging and connection establishment. Messages include *Page*, *MS Connection established*, *CM\_Service\_Prompt*, *Start CC*, *CCBS\_Call\_Info*, and *CCBS\_Call\_Info\_Ack*. It transitions to *CCBS\_Setup*. +- VLR\_CCBS\_Recall\_Manager:** Manages the recall process at the VLR. It sends *Page\_MS\_For\_Recall*, *ProcessAccessRequest*, and *CompleteRecall*. It handles *Recall* and *Recall\_Ack*. It also interacts with the *OG\_Call\_Setup\_MSC*. +- HLRA\_Request\_Manager:** Operates in the *OPERATIVE* state and handles *CCBS\_RUF*. +- HLRA\_Request:** Handles the *RECALL* message. +- HLRA\_Recall\_Manager:** Manages the recall state, transitioning to *CCBS\_BUSY*. +- MT\_GMSC:** Handles the *Initial Address Message* and transitions between *IDLE* and *WAIT\_FOR\_CLEAR*. +- HLRB\_Request\_Manager:** Operates in the *ACTIVE* state. +- HLRB\_Request:** Transitions to *SELECTED*. +- HLRB\_Recall\_Manager:** Manages the recall process at the B-party HLR, transitioning to *WAIT\_FOR\_CCBS\_CALL*. +- HLRB\_Monitoring:** Monitors the B-party status, transitioning from *B\_IDLE\_GUARDED NO\_B\_QUERY* to *Stop Blocking*. +- HLRB\_Blocking:** Manages blocking states like *RECALL\_BLOCKING*. +- CCBS\_Coordinator\_HLR:** Coordinates the CCBS process, managing *Monitoring B* and *CCBS\_Monitoring\_VLR/MSC*. +- ICH\_VLR & ICH\_MSC:** Handle the incoming call leg (*SIFOC*, *Complete Call*, *CCBS\_Call\_Delivery*). + +Key message flows and logic points: + +- CCBS\_RUF\_Ack (accept)* is sent from the MSC side back towards the HLR. +- Initial Address Message* triggers the call delivery sequence. +- Address Complete, Answer / Connect* signals successful call setup. +- Conditional logic: *If Q is empty* leads to *IDLE*; *Else: OPERATIVE* leads to *OPERATIVE RESUMING*. +- The process concludes with *Release* and return to *IDLE* states. + +Sequence diagram for CCBS (Call Completion on Busy Subscriber) service. Lifelines include MSC\_CCBS\_Recall\_Manager, VLR\_CCBS\_Recall\_Manager, HLRA\_Request\_Manager, HLRA\_Request, HLRA\_Recall\_Manager, MT\_GMSC, HLRB\_Request\_Manager, HLRB\_Request, HLRB\_Recall\_Manager, HLRB\_Monitoring, HLRB\_Blocking, CCBS\_Coordinator\_HLR, ICH\_VLR, and ICH\_MSC. The process involves setup, busy detection, request, recall, and completion phases. + +# Annex B (informative): Change history + +| Change history | | | | | | | +|----------------|-----------|---------|--------|---------|-------------|--------------------------------------------------------| +| TSG CN# | Spec | Version | CR | <Phase> | New Version | Subject/Comment | +| Apr 1999 | GSM 03.93 | 6.2.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.093 | | | | 3.0.0 | Approved at CN#03 | +| CN#06 | 23.093 | 3.0.0 | 001r3 | R99 | 3.1.0 | Approved at CN#06 | +| CN#06 | 23.093 | 3.0.0 | 002r3 | R99 | 3.1.0 | Approved at CN#06 | +| CN#09 | 23.093 | 3.1.0 | 003r1 | R99 | 3.2.0 | Handling of the Call Completion Treatment Indicator | +| CN#09 | 23.093 | 3.1.0 | 004 | R99 | 3.2.0 | Handling of the Call Diversion Treatment Indicator | +| CN#11 | 23.093 | 3.2.0 | | Rel-4 | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.093 | 4.0.0 | | Rel-5 | 5.0.0 | Release 5 after CN#16 | +| CN#26 | 23.093 | 5.0.0 | | Rel-6 | 6.0.0 | Release 6 after CN#26 | +| CT#36 | 23.093 | 6.0.0 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#37 | 23.093 | 7.0.0 | 0005 | Rel-7 | 7.1.0 | HLR procedure on Location Update from the current VLR | +| CT#37 | 23.093 | 7.0.0 | 0006 | Rel-7 | 7.1.0 | Incompatible terminal handling in VLR | +| CT#38 | 23.093 | 7.1.0 | 0007 | Rel-7 | 7.2.0 | Call forwarding on busy handling in HLR | +| CT#40 | 23.093 | 7.2.0 | 0008r1 | Rel-7 | 7.3.0 | Missing signal in process<br>VLR_CCBS_Recall_Manager | +| CT#42 | 23.093 | 7.3.0 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.093 | 8.0.0 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.093 | 9.0.0 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2011-11 | 23.093 | 10.0.0 | | Rel-10 | 10.0.1 | Editorial correction to previous line in history table | +| 2012-09 | 23.093 | 10.0.1 | - | Rel-11 | 11.0.0 | Update to Rel-11 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23094/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/23_series/23094/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc544b2cc6e4d0581a9e715c18df1f7b8b551550 --- /dev/null +++ b/marked/Rel-11/23_series/23094/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79f78eef74a00cac7a480d68096fb4d8a0ebf3802f53c09f2e63b4abde80a5d1 +size 124654 diff --git a/marked/Rel-11/23_series/23094/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23094/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a9370a9c2c1509c69210d63e1e7cf31c85e79dc --- /dev/null +++ b/marked/Rel-11/23_series/23094/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f4e3d08aa45bd96ae52bc9c8c393254c1797e1aa1da073d316c54f40fa77fd8 +size 166354 diff --git a/marked/Rel-11/23_series/23094/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-11/23_series/23094/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f748a93b2d4c8c581b168e6b2a5ba8e0bdf9830b --- /dev/null +++ b/marked/Rel-11/23_series/23094/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:714f1a77a93f0216e5fb96f188c15866d90833e0cb91299086184c24799946e6 +size 101586 diff --git a/marked/Rel-11/23_series/23094/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/23_series/23094/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c7b2f279272abe49da58317e0067b88ab8ee1c4 --- /dev/null +++ b/marked/Rel-11/23_series/23094/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdc6acd1a3b6cf762fbc03dfb31f7d7ab035328bd27759b54e43f40e9b1fd755 +size 53191 diff --git a/marked/Rel-11/23_series/23094/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23094/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e3d9f3e4bdba554956bfcd47d31e46bec24c904 --- /dev/null +++ b/marked/Rel-11/23_series/23094/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c673e510184058adc9257d370f73f4db65028655a651297d399dc13289dcbe52 +size 97215 diff --git a/marked/Rel-11/23_series/23094/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/23_series/23094/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c79a9f2087dda2505c85a4d964d54a5aae7a186c --- /dev/null +++ b/marked/Rel-11/23_series/23094/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5680c5aca530eabaa5a6c4bd77f79bb26824fe6438cf401623a9e2bac85ccced +size 71774 diff --git a/marked/Rel-11/23_series/23094/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/23_series/23094/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66d01c3cf7d476512208b6e98a609a0d123a2ece --- /dev/null +++ b/marked/Rel-11/23_series/23094/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:561db215fe936695ef7b05e26f1ef83f563af22ead6a6a15f45d6cab0a84a60f +size 73441 diff --git a/marked/Rel-11/23_series/23094/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/23_series/23094/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8ecfd733d13338624f65518180f7ce7f6dbb176 --- /dev/null +++ b/marked/Rel-11/23_series/23094/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db0652e17f03074952e986b5eacc44ad81bd8e426416d9ef315e52a6102ef635 +size 141104 diff --git a/marked/Rel-11/23_series/23094/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/23_series/23094/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c834e18e8fa0169514655036805f22e64abf4b5 --- /dev/null +++ b/marked/Rel-11/23_series/23094/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14f7b591a495efd7024d946fb97ad9fb95f995d111fcdc7db124159f23ea920c +size 52144 diff --git a/marked/Rel-11/23_series/23094/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23094/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f5a9a82000c8e379ca67466f50b304c63db7e84 --- /dev/null +++ b/marked/Rel-11/23_series/23094/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b279b02bbebf3719532c4d94586e319864110e238b871d468677d40d8f582b6 +size 189960 diff --git a/marked/Rel-11/23_series/23094/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/Rel-11/23_series/23094/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48863717fdf7bc4bdaff76e2803a0c25b26229c9 --- /dev/null +++ b/marked/Rel-11/23_series/23094/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e05ae9de964ba94d3f84614d0f282cb08552d2ef504f739abf1bfe113015c45f +size 45856 diff --git a/marked/Rel-11/23_series/23094/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/23_series/23094/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54e4f678bc7dfe6df1e645ef90da924045a872f6 --- /dev/null +++ b/marked/Rel-11/23_series/23094/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9e6aa6cc4ed45ad3e403fd7e6a2513962324efa21dacb1d8b2653a112850b6e +size 97591 diff --git a/marked/Rel-11/23_series/23094/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23094/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c65b9f5cd7756f0227b7bbb3b3b818e8dfb5628 --- /dev/null +++ b/marked/Rel-11/23_series/23094/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b79651f08b63ab374d9cf81510beb4b189c527abf0a091bfb9618800974b214a +size 87969 diff --git a/marked/Rel-11/23_series/23094/raw.md b/marked/Rel-11/23_series/23094/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..639223849c13691975a9fcffee41897fe3d165b0 --- /dev/null +++ b/marked/Rel-11/23_series/23094/raw.md @@ -0,0 +1,1042 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 Handling of Follow Me..... | 6 | +| 4.1 General ..... | 6 | +| 4.1.1 Provision..... | 7 | +| 4.1.2 Registration..... | 7 | +| 4.1.3 Erasure ..... | 7 | +| 4.1.4 Interrogation ..... | 7 | +| 4.2 Information Flows ..... | 7 | +| 4.2.1 Information Flow for the handling of FM by the initiating subscriber ..... | 7 | +| 4.2.2 Information Flow for the handling of FM by the remote party ..... | 10 | +| 4.3 Handling of FM control in HLRa and FFNb..... | 10 | +| 4.3.1 Handling of FM control in HLRa..... | 10 | +| 4.3.2 Handling of FM control in FFNb ..... | 13 | +| 4.4 USSD interworking and Cross-phase compatibility ..... | 22 | +| 5 Information stored in the network entities ..... | 23 | +| 5.1 Information stored in HLRa and FFNb ..... | 23 | +| 5.2 State transition model..... | 23 | +| 5.3 Information stored in the VLR ..... | 24 | +| 5.4 Transfer of information from HLR to VLR ..... | 24 | +| <b>Annex A (informative):      Checking matrix for FM-CFU interaction in FFNb .....</b> | <b>25</b> | +| <b>Annex B (normative):      FM control Messages and their contents.....</b> | <b>27</b> | +| B.1 General principles ..... | 27 | +| B.2 Information Elements used in the messages ..... | 27 | +| B.3 Messages Contents of the FM Request..... | 27 | +| B.4 Messages Contents of the HLR-FM-Request ..... | 28 | +| B.5 Contents and Format of the USSD String of the USSD-Notify..... | 30 | +| B.6 Inter-process Message Init-Notify ..... | 31 | +| Annex C (informative):      Change history..... | 32 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the stage 2 description for the Follow Me feature. + +The Follow Me feature enables a mobile subscriber A to manipulate the Follow Me data of a remote party B in such a way that subsequent calls directed to remote party B will be forwarded to subscriber A. + +# --- 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: "3G Vocabulary". +- [2] 3GPP TS 22.004: "General on Supplementary Services". +- [3] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)". +- [4] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". +- [5] 3GPP TS 22.094: "Follow Me (FM) feature - Stage 1". +- [6] 3GPP TS 23.011: "Technical realisation of Supplementary Services - General Aspects". +- [7] 3GPP TS 23.015: "Technical realisation of Operator Determined Barring (ODB)". +- [8] 3GPP TS 23.090: "Unstructured Supplementary Services Data (USSD)- Stage 2". +- [9] 3GPP TS 23.082: "Call Forwarding (CF) supplementary services - Stage 2". +- [10] 3GPP TS 22.090: "Unstructured Supplementary Services Data (USSD)- Stage 1". +- [11] 3GPP TS 24.090: "Unstructured Supplementary Services Data (USSD)- Stage 3". +- [12] 3GPP TS 29.002: "Mobile Application Part (MAP)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +**initiating subscriber:** mobile subscriber who modifies the Follow Me data of the remote party. + +**initiating number:** number (the MSISDN of the initiating subscriber) to which incoming calls, originally destined for the remote party, shall be forwarded. It is subsequently also referred to as **MSISDN<sub>A</sub>**. + +**remote party:** is characterised by the remote number which is defined in the numbering plan of a PLMN operator. The Follow Me feature enables the initiating subscriber to modify the Follow Me data of the remote party. In particular cases the remote party is a GSM subscriber of the PLMN and the remote number denotes her basic MSISDN. + +**Previously registered subscriber:** Is the initiating service subscriber who has registered Follow Me with respect to a remote party. Her Registration can be erased by herself or by an FM service supervisor via forced erasure procedure. + +**FM service supervisor:** is an initiating subscriber who is allowed to modify the Follow Me data of a remote party who has been registered to a previously registered subscriber for the Follow Me application. The FM service supervisor shall be authorised by her network operator. + +**remote number:** is a number in E.164 format which identifies a remote party. In general this number is not assigned to a subscriber and can be regarded as a "dummy MSISDN". In particular cases the remote party is a GSM subscriber of the PLMN and the remote number denotes her basic MSISDN. The remote number is entered by the initiating subscriber for registration, interrogation, forced erasure and erasure of the Follow Me feature with respect to the remote party. + +**Follow Me function node:** is a network node in the PLMN operator of the remote party. The FM data of the remote party are stored in this node. This node can be implemented in: + +- an HLR; +- any other operator specific network node e.g.: + - a gsmSCF; + - an SCP. + +## 3.2 Abbreviations + +| | | +|-----|-------------------------| +| FFN | Follow Me function node | +| FM | Follow Me | +| SCP | Service Control Part | + +Other abbreviations used in this ETS are listed in 3GPP TR 21.905. + +# --- 4 Handling of Follow Me + +## 4.1 General + +Follow Me enables an initiating mobile subscriber A to have control over the Follow Me data of a remote party B. The remote party B is characterised by the remote number which is defined in the numbering plan of a PLMN operator. Initiating Subscriber A shall be able to manipulate the Follow Me data of remote party B such that subsequent calls destined for remote party B are forwarded to initiating subscriber A. In the case of Forced Erasure by an FM service supervisor, the initiating subscriber is allowed to erase the Follow Me data of a remote party who has been registered to a different initiating subscriber for the Follow Me application. + +Follow Me is a PLMN specific feature and the control operations of FM are based on USSD. All messages between the MS and the mobile network and internal to the mobile network are USSD messages. + +The present document deals with the control operations of FM in HLRa and FFN. If the FFN is an HLR, the control of the requests for both FM and CFU services is specified (see subclause 4.3.2). + +The functionality of forwarding calls for remote party B to initiating subscriber A (after successful registration of FM) is out of the scope of the present document. This functionality is the same as the functionality of the Call Forwarding Unconditional Supplementary Service applied to all telecommunication services of remote party B for which CFU is applicable. + +NOTE 1: the "served mobile subscriber" in 3GPP TS 22.094 [5] corresponds to the "remote party" in the present document and the "forwarded-to subscriber" in 3GPP TS 22.094 [5] corresponds to the "initiating subscriber" in the present document. + +NOTE 2: The forwarding of calls for remote party B to initiating subscriber A can be achieved by invoking the Call Forwarding Unconditional Supplementary Service or by making use of an equivalent operator specific service (e.g. via CAMEL). + +The functionality of the control of Follow Me (registration, erasure, forced erasure and interrogation) is split between the HLR of the initiating subscriber A (HLRa) and the FFN of the remote party B (FFNb). + +### 4.1.1 Provision + +FM can be registered / erased / interrogated by an initiating subscriber A with respect to a remote party B if both parties are provisioned with FM. + +To enable forced erasure by an FM service supervisor, the FM service shall be provisioned to the FM service supervisor. Additionally, she needs the subscription entitlement to perform the forced erasure. + +NOTE: In general remote party B does not correspond to a GSM subscriber. In this case provisioning of FM for remote party B is operator specific. + +If remote party B is a GSM subscriber and if the forwarding of calls for remote party B to initiating subscriber A is achieved by invoking the Call Forwarding Unconditional Supplementary Service, provision of CFU for remote party B is required. + +### 4.1.2 Registration + +The initiating subscriber registers the FM feature with respect to a particular remote party. + +If an initiating subscriber A successfully registers FM with respect to a remote party B then FM becomes registered, active and operative for remote party B. + +As a result of the registration subsequent calls directed to remote party B are forwarded to initiating subscriber A. + +NOTE: The remote party cannot register FM with respect to herself. + +### 4.1.3 Erasure + +If an initiating subscriber A or the FM service supervisor successfully erases FM with respect to a remote party B then FM becomes not registered and not active for remote party B. + +For forced erasure by the FM service supervisor the previously registered subscriber shall be informed of the successful forced erasure via a network initiated USSD Notify message with appropriate contents. This message is sent by the FFN. + +If remote party B is a GSM subscriber and successfully erases FM then FM becomes not registered and not active for remote party B. + +### 4.1.4 Interrogation + +If an initiating subscriber A or the FM service supervisor successfully interrogates FM with respect to a remote party B then this procedure interrogates the FM data of subscriber B. + +If remote party B is a GSM subscriber and successfully interrogates FM then this procedure interrogates her own FM data. + +## 4.2 Information Flows + +### 4.2.1 Information Flow for the handling of FM by the initiating subscriber + +Figure 4.1 shows the Information Flow for the control of FM (registration, erasure, forced erasure and interrogation) by the initiating subscriber. + +For any control operation on FM, the initiating subscriber (MSa) enters a Follow Me Request (FM-Request). This is a USSD string containing the requested FM operation and the remote number. The Follow Me Request is routed via the MSC/VLR to the HLR of the initiating subscriber (HLRa). + +The HLRa performs a series of checks as described in the SDLs (subclause 4.3). If these checks fail, the MSa receives a response (FM-Response) indicating the error. + +If the checks pass, the HLRa forwards the operation request (HLR-FM-Request) to the FFN of the remote party (FFNb). + +FFNb carries out the appropriate control operation and checks as described in the SDLs (subclause 4.3) for the remote party. + +The result of this operation (success or error) is reported back in a USSD Response to the initiating subscriber. + +For successful forced erasure by a service supervisor, the FFN shall send a Network Initiated USSD notify message with the corresponding USSD string to the HLR of the previously registered subscriber who had registered the Follow Me data. The HLR shall forward the USSD notify to VLR which will relay the USSD Notify towards the MS. + +Upon receipt of the USSD Notify, the MS shall respond by sending a FACILITY message with empty return result component. + +An error response with corresponding reason can be returned from any entity, when error happens at the entity 3GPP TS 23.090 [8]. + +![Sequence diagrams showing information flow for FM and USSD control. The top diagram shows FM-Request and FM-Response messages between MSa, MSC, VLR, HLRA, and FFNb. The bottom diagram shows USSD-Notify and USSD-Response messages between MSP, MSC, VLR, HL Rp, and FFNb. A callout box on the right notes that in case of successful forced erasure, a USSD Notify is sent to the previously registered subscriber.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +**Top Sequence Diagram: Forced Erasure (FM)** + +``` + +sequenceDiagram + participant MSa + participant MSC + participant VLR + participant HLRA + participant FFNb + + Note right of FFNb: In case of successful forced erasure by a service supervisor, an USSD Notify with corresponding USSD string is sent to the previously registered subscriber. + + MSa->>MSC: FM-Request (OC,SC,RN,[(SI,PIM,)] [AI]) + MSC->>VLR: FM-Request (OC,SC,RN,[(SI,PIM,)] [AI]) + VLR->>HLRA: FM-Request (OC,SC,RN,[(SI,PIM,)] [AI]) + HLRA-->>VLR: FM-Response (Error) + Note right of HLRA: OR1: N + VLR->>MSC: FM-Response (Error) + MSC->>MSa: FM-Response (Error) + + HLRA-->>FFNb: HLR-FM-Request (OC,SC,RN,[(SI,PIM,)] [AI], MSISDN-A) + Note right of HLRA: OR1: Y + FFNb-->>HLRA: HLR-FM-Response (Result) + HLRA-->>VLR: FM-Response (Result) + VLR->>MSC: FM-Response (Result) + MSC->>MSa: FM-Response (Result) + +``` + +**Bottom Sequence Diagram: USSD Control** + +``` + +sequenceDiagram + participant MSP + participant MSC + participant VLR + participant HL Rp + participant FFNb + + MSP->>MSC: USSD-Notify (OC,SC,FN,SI, MSISDN-A,AI) + MSC->>VLR: USSD-Notify (OC,SC,FN,SI, MSISDN-A,AI) + VLR->>HL Rp: USSD-Notify (OC,SC,FN,SI, MSISDN-A,AI) + HL Rp-->>FFNb: USSD-Notify (OC,SC,FN,SI, MSISDN-A,AI) + FFNb-->>HL Rp: USSD-Response (error) + HL Rp-->>VLR: USSD-Response (error) + VLR-->>MSC: USSD-Response (error) + MSC-->>MSP: USSD-Response (error) + + MSP->>MSC: USSD-Response (error) + MSC->>VLR: USSD-Response (error) + VLR->>HL Rp: USSD-Response (error) + HL Rp-->>FFNb: USSD-Response (error) + + MSP->>MSC: USSD-Response (result) + MSC->>VLR: USSD-Response (result) + VLR->>HL Rp: USSD-Response (result) + HL Rp-->>FFNb: USSD-Response (result) + +``` + +Sequence diagrams showing information flow for FM and USSD control. The top diagram shows FM-Request and FM-Response messages between MSa, MSC, VLR, HLRA, and FFNb. The bottom diagram shows USSD-Notify and USSD-Response messages between MSP, MSC, VLR, HL Rp, and FFNb. A callout box on the right notes that in case of successful forced erasure, a USSD Notify is sent to the previously registered subscriber. + +Figure 4.1: Information flow for the control of FM by the initiating subscriber or service supervisor + +| | | | +|---------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | OR1:N: | The case where the checks in the HLR result in a negative outcome, e.g. FM is not provisioned for the initiating subscriber or the initiating subscriber is not allowed to operate FM for the remote party. | +| | OR1:Y: | The case where all the checks in the HLR are successful, e.g. FM is provisioned for the initiating subscriber and the initiating subscriber is allowed to operate FM for the remote party. | +| NOTE 2: | [...] | Optional parameter. | +| | (...)] | Conditional parameter. | +| | OC | Operation Code (Register, Erase or Interrogate). | +| | SC | Service Code for FM. | +| | RN | Remote Number. | +| | SI | Supervisor Indicator. This parameter is conditional and only used for forced erasure by a FM service supervisor. | +| | PIM | MSISDN of previously registered subscriber who has registered the FM to remote number. This parameter is conditional and only used for forced erasure by a FM service supervisor.. | +| | AI | Supplementary Information containing additional information. | +| | MSISDN-A | initiating number in international format. It is not a part of the USSD string, but is sent from HLRA to the FFNb together with the HLR-FM-Request within the MAP operation. For forced erasure, the MSISDN-A corresponds to the supervisor's MSISDN and will be part of the USSD-notify. | +| | MSP | MS of previously registered service subscriber. | +| | HLRp | HLR of the previously registered service subscriber. | + +### 4.2.2 Information Flow for the handling of FM by the remote party + +Control of FM by the remote party is possible if the remote party is a GSM subscriber. + +The information flow for control of FM by the remote party (erasure and interrogation of her own FM data) is the same as the information flow for control of FM by the initiating subscriber. + +If a remote party tries to register FM to herself the registration is rejected and an error is reported. + +## 4.3 Handling of FM control in HLRA and FFNb + +HLRA and FFNb can both receive FM control messages, based on USSD. The USSD handler in each entity analyses the Service Code contained in the USSD string and, recognising the Service Code for FM, invokes the FM USSD application. + +The FM control messages and their contents are given in Annex B (normative). + +### 4.3.1 Handling of FM control in HLRA + +The FM USSD application in HLRA is the process **FM\_initiating\_subscriber\_handling\_in\_HLR** (figure 4.2). It receives the FM-Request from the initiating subscriber. This FM-Request is an USSD-string containing: + +- the operation code (register, erase, interrogate); +- the remote number; +- an additional operator specific information field. + +The HLR checks: + +- the provisioning of FM to the initiating subscriber; +- whether the FFN can be deduced from the remote number; +- whether any operator specific restrictions to engage in FM activity with the remote party apply; +- if the initiating subscriber requires forced erasure, the HLR checks Whether the initiating subscriber is entitled to do it, i.e. Whether the initiating subscriber is a FM service supervisor. + +The basic MSISDN of the initiating subscriber is sent together with the original USSD string to the FFN of the remote party. + +The HLR forwards the response from the FFN to the initiating subscriber. + +For successful forced erasure by a service supervisor, the HLR of the previously registered subscriber (HLRp) shall relay the USSD Notify to the VLR when the USSD Notify from the FFN is received. The VLR will then forward the USSD Notify towards the MS of the previously registered service subscriber. + +On receipt of an USSD response from the MS of the previously registered subscriber, the HLRp shall relay it to the FFN. + +![Flowchart for Process FM_Initiating_Subscriber_Handling_in_HLR. The process starts at an 'Idle' state, receives an 'FM-Request', checks if the subscriber is provisioned, if the remote number is known, if a supervisor indicator is present, if forced erasure is allowed, and if the request is authorized. If any check fails, an error is returned. If all checks pass, an 'HLR-FM-Request' is sent to the FFN, and the process waits for a response before returning to 'Idle'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +**Process FM\_Initiating\_Subscriber\_Handling\_in\_HLR** 1(1) + +A process in the HLR to handle an FM-Request from an initiating subscriber. + +Signals to/from the left are to/from the VLR of the initiating subscriber; Signals to/from the right are to/from the FFN + +``` +graph TD; Idle1([Idle]) --> FM_Request{FM-Request +(Operation, Remote_Number, Additional_Info)}; FM_Request --> FM_Provisioned{FM provisioned?}; FM_Provisioned -- no --> Error1[Error := FM not subscribed]; FM_Provisioned -- yes --> Remote_Known{Remote Number known?}; Remote_Known -- no --> Error2[Error := unknown Remote Party]; Remote_Known -- yes --> Supervisor{Supervisor Indicator present?}; Supervisor -- no --> Error3[Error := unauthorised request]; Supervisor -- yes --> Forced_Erasure{Forced Erasure allowed?}; Forced_Erasure -- no --> Error3; Forced_Erasure -- yes --> FM_Allowed{FM allowed with remote_number?}; FM_Allowed -- no --> Error3; FM_Allowed -- yes --> HLR_FM_Request[HLR-FM-Request := FM-Request + initial MSISDN]; HLR_FM_Request --> HLR_FM_Request_Datagram{HLR-FM-Request +(Operation, Remote_Number, Additional_Info, Initial_MSISDN)}; HLR_FM_Request_Datagram --> Wait[wait_for_answer_from_FFN]; Wait --> HLR_FM_Response{HLR-FM-Response +(Result)}; HLR_FM_Response --> FM_Response{FM-Response +(Result)}; FM_Response --> Idle2([Idle]); Error1 --> FM_Response_Error{FM-Response +(Error)}; Error2 --> FM_Response_Error; Error3 --> FM_Response_Error; FM_Response_Error --> Idle2; +``` + +HLR receives USSD string from initiating subscriber + +check if initiating subscriber is FM provisioned + +check if address of FFN can be deduced from Remote\_Number + +Check if the forced erasure is allowed to the initiating subscriber. + +check operator specific restrictions on initiating subscriber to engage Remote Party in FM activity + +Basic MSISDN of initiating subscriber is sent to the FFN together with the FM-Request within the MAP operation. + +Flowchart for Process FM\_Initiating\_Subscriber\_Handling\_in\_HLR. The process starts at an 'Idle' state, receives an 'FM-Request', checks if the subscriber is provisioned, if the remote number is known, if a supervisor indicator is present, if forced erasure is allowed, and if the request is authorized. If any check fails, an error is returned. If all checks pass, an 'HLR-FM-Request' is sent to the FFN, and the process waits for a response before returning to 'Idle'. + +Figure 4.2: Process: FM\_Initiating\_Subscriber\_Handling\_in\_HLR + +![State transition diagram for Process Notification_for_previously_registered_subscriber_in_HLRp. The process starts in an 'Idle' state. It receives a 'USSD-Notify (OC,SC,FN,SI, MSISDN-A,Al)' signal from the FFN. A decision diamond 'any error occurred?' follows. If 'yes', it sends a 'USSD-Notify-Response(error)' to the VLR and returns to 'Idle'. If 'no', it sends the 'USSD-Notify' to the VLR, enters a 'wait for USSD-Response' state, receives a 'USSD-Notify-Response(/error)' from the VLR, sends a 'USSD-Notify-Response(/error)' to the FFN, and returns to 'Idle'. Callouts explain that the process handles forced erasure notifications from the FFN, signals are to/from the VLR or FFN, errors can occur in HLRp, and the final response to the FFN is 'FFN_Forced_Erasure_Notify'.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Process Notification\_for\_previously\_registered\_subscriber\_in\_HLRp 1(1) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> USSD_Notify_In: USSD-Notify (OC,SC,FN,SI, MSISDN-A,Al) from FFN + USSD_Notify_In --> any_error_occurred{any error occurred?} + any_error_occurred -- yes --> USSD_Notify_Response_Error: USSD-Notify-Response(error) to VLR + USSD_Notify_Response_Error --> Idle + any_error_occurred -- no --> USSD_Notify_Out: USSD-Notify (OC,SC,FN,SI, MSISDN-A,Al) to VLR + USSD_Notify_Out --> wait_for_response[wait for USSD-Response] + wait_for_response --> USSD_Notify_Response_In: USSD-Notify-Response(/error) from VLR + USSD_Notify_Response_In --> USSD_Notify_Response_Out: USSD-Notify-Response(/error) to FFN + USSD_Notify_Response_Out --> Idle + +``` + +Process in HLRp to handle the forced erasure notification sent from the FFN + +Signals to/from the left are to/from the VLR of the initiating subscriber; Signals to/from the right are to/from the FFN + +Idle + +USSD-Notify (OC,SC,FN,SI, MSISDN-A,Al) + +from the FFN process FFN\_Forced Erasure\_Notify + +any error occurred? + +Errors can occur in HLRp when handling USSD-Notify + +yes + +no + +USSD-Notify (OC,SC,FN,SI, MSISDN-A,Al) + +send to VLR + +wait for USSD-Response + +USSD-Notify-Response(/error) + +Response from VLR + +USSD-Notify-Response(error) + +USSD-Notify-Response(/error) + +send to the FFN process FFN\_Forced Erasure\_Notify + +Idle + +State transition diagram for Process Notification\_for\_previously\_registered\_subscriber\_in\_HLRp. The process starts in an 'Idle' state. It receives a 'USSD-Notify (OC,SC,FN,SI, MSISDN-A,Al)' signal from the FFN. A decision diamond 'any error occurred?' follows. If 'yes', it sends a 'USSD-Notify-Response(error)' to the VLR and returns to 'Idle'. If 'no', it sends the 'USSD-Notify' to the VLR, enters a 'wait for USSD-Response' state, receives a 'USSD-Notify-Response(/error)' from the VLR, sends a 'USSD-Notify-Response(/error)' to the FFN, and returns to 'Idle'. Callouts explain that the process handles forced erasure notifications from the FFN, signals are to/from the VLR or FFN, errors can occur in HLRp, and the final response to the FFN is 'FFN\_Forced\_Erasure\_Notify'. + +Figure 4.2a: Process Notification\_for\_previously\_registered\_subscriber\_in\_HLRp + +### 4.3.2 Handling of FM control in FFNb + +If the FFN is an HLR, the FFN is responsible for handling the interactions between FM and CFU. Two kinds of request may be received in an FFN which deals with forwarding services: + +- CFU requests sent by the VLR for CFU operations (only if the FFN is a HLR); +- FM-HLR-Requests which are USSD strings sent by HLRA for FM operations. + +When the control process in the FFN receives a CFU request, it shall either pass the CFU operation request directly to a CFU process or reject it depending on the registration and/or activation states of both FM and CFU services (see Table A.1 for permission checks). + +On receipt of an HLR-FM request, the control process in the FFN performs a series of FM specific checks and checks the states of both FM and CFU. If the checks are successful, a CFU operation request is sent to a CFU process. On receipt of an HLR-FM-Request from HLRA, the FFN performs a series of checks. e.g.: + +- if the remote party is a GSM subscriber: + - provisioning of FM to the remote party; + - provisioning of CFU to the remote party; + - illegal interaction with CFU registered or active to remote party. + +- if the remote number is registered in the FFN; +- if any operator specific restrictions to engage in FM activity with the initiating subscriber apply; +- specific checks for forced erasure. + +Depending on the requested operation, one of the following procedures is performed: + +- registration with implicit Activation (procedure Handle\_Remote\_Party\_Registration, figure 4.6); +- erasure with implicit Deactivation (procedure Handle\_Remote\_Party\_Erasure, figure 4.7); +- interrogation (procedure Handle\_Remote\_Party\_Interrogation, figure 4.8). + +For successful forced erasure by a service supervisor, the FFN shall generate an USSD-Notify message and send it to the HLRp, which will relay the USSD Notify towards the MS of the previously registered subscriber (MSp). On receipt of an error response that the USSD Notify message could not be transferred to the MS, the FFN shall check the error code of the response. Depending on the error types and the specific implementation the process shall decide to resend the USSD message after a predefined time. + +For the resend procedure the process shall start a timer. On timer expiry it shall send the message again. The FFN shall repeat the messages up to 5 times. + +The length of the timer is defined by operator and has the value in the range of 1 – 10 minutes. + +Figure 4.3 shows the message flow between the process Forwarding\_Service\_Control and the processes handling CFU operation requests, defined in 3GPP TS 23.082 [9]. + +![SDL Block Diagram for FFN_Processes showing message flows between process_forwarding_Service_control and process_CFU_handling, with external interfaces to HLRa and VLR.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +``` + +sequenceDiagram + participant HLRa + participant VLR + box Block FFN_Processes + participant FSC as process_forwarding_Service_control + participant CFU as process_CFU_handling + end + + Note over FSC: Process defined in 03.94 + Note over CFU: Processes defined in 03.82: CFU1, CFU2, CFU3 or CFU4 + + HLRa->>FSC: [FM-HLR-Request] + FSC-->>HLRa: [FM-HLR-Response] + VLR->>FSC: [CFU-Request] + FSC-->>VLR: [CFU acknowledge] + Note left of FSC: this is applicable if the FFN is a HLR + + FSC->>CFU: [CFU operation request] + CFU-->>FSC: [acknowledge] + +``` + +The diagram, titled 'Block FFN\_Processes 1(1)', illustrates the interaction between two internal processes: 'process\_forwarding\_Service\_control' and 'process\_CFU\_handling'. The 'process\_forwarding\_Service\_control' is defined in 03.94 and handles external signals: '[FM-HLR-Request]' and '[FM-HLR-Response]' from/to HLRa, and '[CFU-Request]' and '[CFU acknowledge]' from/to VLR. A note specifies that the VLR interaction is applicable if the FFN is a HLR. Internally, 'process\_forwarding\_Service\_control' sends a '[CFU operation request]' to 'process\_CFU\_handling' and receives an '[acknowledge]'. The 'process\_CFU\_handling' represents processes defined in 03.82 (CFU1, CFU2, CFU3, or CFU4). + +SDL Block Diagram for FFN\_Processes showing message flows between process\_forwarding\_Service\_control and process\_CFU\_handling, with external interfaces to HLRa and VLR. + +Figure 4.3: FFN\_processes + +![SDL Flowchart for Process Forwarding_Service_Control. The process starts at an 'Idle' state, receives an 'HLR-FM-Request', performs 'FM_remote_party_handling_in_FFN', and enters another 'Idle' state. It then checks if 'FM provisioned?'. If 'no', it proceeds to 'interrogate CFU'. If 'yes', it checks if 'FM registered & active?'. If 'no', it sends a 'CFU operation request', waits for a response, and then acknowledges. If 'yes', it proceeds to an 'acknowledge' step. The process concludes with a result assignment and a final 'Idle' state.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Process Forwarding\_Service\_Control 1(2) + +``` + +graph TD + Start([Idle]) --> Input1[/HLR-FM-Request +(Reg, erase, interr., +forced erasure)/] + Input1 --> Task1[FM_remote_party_handling_in_FFN] + Task1 --> State2([Idle]) + + %% Horizontal signal inputs + Register[/Register CFU/] --> FM_Prov + Activate[/activate CFU/] --> FM_Prov + Erase[/erase CFU/] --> FM_Prov + Deactivate[/deactivate CFU/] --> FM_Prov + Interrogate[/interrogate CFU/] --> FM_Prov + + State2 --> FM_Prov{FM provisioned?} + FM_Prov -- yes --> FM_Reg{FM registered +& active?} + FM_Prov -- no --> FM_Reg + + FM_Reg -- no --> Output1[/CFU operation +request/] + Output1 --> State3([wait_for_response]) + State3 --> Input2[/acknowledge/] + Input2 --> Task2[Result := +Conflicting +situation +with other SS] + Task2 --> Output2[/acknowledge/] + Output2 --> End([Idle]) + + FM_Reg -- yes --> Output2 + +``` + +This process describes the case where the FFN is a HLR. Camel or IN solution should have the similar behavior. + +Signals to/from the right are to/from the appropriate CFU process. Signals to/from the left are to/from the VLR unless otherwise stated. + +it's from the HLR of the initiating subscriber. + +it should contain the appropriate message, e.g. "register CFU" etc. + +if it's an FM-Request, the message is to the VLR of the initiating subscriber. + +SDL Flowchart for Process Forwarding\_Service\_Control. The process starts at an 'Idle' state, receives an 'HLR-FM-Request', performs 'FM\_remote\_party\_handling\_in\_FFN', and enters another 'Idle' state. It then checks if 'FM provisioned?'. If 'no', it proceeds to 'interrogate CFU'. If 'yes', it checks if 'FM registered & active?'. If 'no', it sends a 'CFU operation request', waits for a response, and then acknowledges. If 'yes', it proceeds to an 'acknowledge' step. The process concludes with a result assignment and a final 'Idle' state. + +## 4.4 Process Forwarding\_Service\_Control + +![Flowchart for Procedure FM_Remote_Party_Handling_in_FFN. It starts with a connector, then checks if FM is provisioned to the remote party. If no, it checks if CFU is provisioned. If CFU is also no, it sets Result := FM not subscribed. If CFU is yes, it checks if the remote number is handled here. If no, it sets Result := unknown remote party. If yes, it checks if FM is allowed with Initial_MSISDN. If no, it sets Result := remote party authorisation failed. If yes, it checks the operation: Register FM, Erase FM, or Remote Party Interrogation. All three lead to a merge connector. A callout for the Initial_MSISDN check says 'check operator specific restrictions on remote party to be engaged in FM activity with initiating subscriber'. All result boxes lead to an HLR-FM-Response (Result) box.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +### Procedure FM\_Remote\_Party\_Handling\_in\_FFN 1(1) + +This process describes the case where the FFN is an HLR. IN solutions should have similar behaviour. + +signals to/from the left are to/from the HLR of the initiating subscriber + +``` +graph TD; Start([ ]) --> D1{FM provisioned to remote party?}; D1 -- no --> D2{CFU provisioned to remote party?}; D1 -- yes --> D3{remote number handled here?}; D2 -- no --> R1[Result := FM not subscribed]; D2 -- yes --> D3; D3 -- no --> R2[Result := unknown remote party]; D3 -- yes --> D4{FM allowed with Initial_MSISDN?}; D4 -- no --> R3[Result := remote party authorisation failed]; D4 -- yes --> D5{Operation = Register FM?}; D5 -- yes --> Merge(( )); D5 -- no --> D6{Operation = Erase FM?}; D6 -- yes --> Merge; D6 -- no --> T1[handle Remote_party_Interrogation]; T1 --> Merge; T2[handle Remote_Party_Erasure] --> Merge; T3[handle Remote_Party_Registration] --> Merge; R1 --> HLR[HLR-FM-Response (Result)]; R2 --> HLR; R3 --> HLR; HLR --> Merge; Callout[check operator specific restrictions on remote party to be engaged in FM activity with initiating subscriber] -.-> D4; +``` + +Flowchart for Procedure FM\_Remote\_Party\_Handling\_in\_FFN. It starts with a connector, then checks if FM is provisioned to the remote party. If no, it checks if CFU is provisioned. If CFU is also no, it sets Result := FM not subscribed. If CFU is yes, it checks if the remote number is handled here. If no, it sets Result := unknown remote party. If yes, it checks if FM is allowed with Initial\_MSISDN. If no, it sets Result := remote party authorisation failed. If yes, it checks the operation: Register FM, Erase FM, or Remote Party Interrogation. All three lead to a merge connector. A callout for the Initial\_MSISDN check says 'check operator specific restrictions on remote party to be engaged in FM activity with initiating subscriber'. All result boxes lead to an HLR-FM-Response (Result) box. + +Figure 4.5: Procedure: FM\_Remote\_Party\_Handling\_in\_FFN + +![Flowchart for Handle_Remote_Party_Registration procedure. It starts with a connector, followed by a decision 'Initiating_MSISDN = Remote_Number?'. If 'yes', it goes to 'Result := request to own MSISDN not possible'. If 'no', it goes to 'Register_FM_for_remote_party', then to 'Result = pass?'. If 'yes', it goes to 'FM states := registered & active', then to 'Result := FM successful registered'. If 'no', it goes to 'result := corresponding unsuccessful outcome code'. All three result boxes merge into 'HLR-FM-Response (Result)', which ends at a connector.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Procedure Handle\_Remote\_Party\_Registration 1(1) + +This process describes the case where the FFN is an HLR. IN solutions should have similar behaviour. + +signals to/from the left are to/from the HLR of the initiating subscriber +signals to/from the right are to/from the CFU process as indicated + +initiating subscriber may not register FM of her own number + +``` +graph TD; Start([ ]) --> Decision1{Initiating_MSISDN = Remote_Number?}; Decision1 -- yes --> Result1[Result := request to own MSISDN not possible]; Decision1 -- no --> Process1[Register_FM_for_remote_party]; Process1 --> Decision2{Result = pass?}; Decision2 -- yes --> Process2[FM states := registered & active]; Process2 --> Result2[Result := FM successful registered]; Decision2 -- no --> Result3[result := corresponding unsuccessful outcome code]; Result1 --> Merge1(( )); Result2 --> Merge1; Result3 --> Merge1; Merge1 --> Process3{HLR-FM-Response (Result)}; Process3 --> End(( )) +``` + +Flowchart for Handle\_Remote\_Party\_Registration procedure. It starts with a connector, followed by a decision 'Initiating\_MSISDN = Remote\_Number?'. If 'yes', it goes to 'Result := request to own MSISDN not possible'. If 'no', it goes to 'Register\_FM\_for\_remote\_party', then to 'Result = pass?'. If 'yes', it goes to 'FM states := registered & active', then to 'Result := FM successful registered'. If 'no', it goes to 'result := corresponding unsuccessful outcome code'. All three result boxes merge into 'HLR-FM-Response (Result)', which ends at a connector. + +Figure 4.6: Procedure: Handle\_Remote\_Party\_Registration + +![Flowchart for Register_FM_for_Remote_Party procedure. It starts with a connector, then checks if FM is already registered. If yes, it checks if the initiating MSISDN equals FTN. If no, it sets Result to 'remote party already registered'. If yes, it sets Result to 'succ registered'. If FM is not already registered, it checks if CFU is active or registered. If yes, it sets Result to 'CFU active or registered'. If no, it calls Register_CFU (with ftn = initiating_MSISDN, BS = all BS), then waits for a response. The response can be an 'acknowledge (error)' leading to Result := (error), or an 'acknowledge (result)' leading to Result := pass. Both final results lead to an exit connector. External signals from process CFU1 (GSM 03.82) are shown entering the 'acknowledge' blocks.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Procedure Register\_FM\_for\_Remote\_Party 1(1) + +This process describes the case where the FFN is an HLR. IN solutions should have similar behaviour. + +signals to/from the right are to/from the CFU process as indicated. + +``` +graph TD; Start([ ]) --> D1{FM already registered?}; D1 -- yes --> D2{Initiating_MSISDN = FTN?}; D1 -- no --> D3{CFU active or registered?}; D2 -- no --> R1[Result := remote party already registered]; D2 -- yes --> R2[Result := succ registered]; D3 -- yes --> R3[Result := CFU active or registered]; D3 -- no --> P1[/Register_CFU (ftn = initiating_MSISDN, BS = all BS)/]; P1 --> P2((wait for response)); P2 --> A1{{acknowledge (error)}}; P2 --> A2{{acknowledge (result)}}; A1 --> R4[Result := (error)]; A2 --> R5[Result := pass]; R1 --> Exit1(( )); R2 --> Exit2(( )); R3 --> Exit3(( )); R4 --> Exit4(( )); R5 --> Exit4; CFU1_1[from process CFU1 (GSM 03.82)] --> A1; CFU1_2[from process CFU1 (GSM 03.82)] --> A2; CFU1_3[to process CFU1 (GSM 03.82)] --> P1; +``` + +Flowchart for Register\_FM\_for\_Remote\_Party procedure. It starts with a connector, then checks if FM is already registered. If yes, it checks if the initiating MSISDN equals FTN. If no, it sets Result to 'remote party already registered'. If yes, it sets Result to 'succ registered'. If FM is not already registered, it checks if CFU is active or registered. If yes, it sets Result to 'CFU active or registered'. If no, it calls Register\_CFU (with ftn = initiating\_MSISDN, BS = all BS), then waits for a response. The response can be an 'acknowledge (error)' leading to Result := (error), or an 'acknowledge (result)' leading to Result := pass. Both final results lead to an exit connector. External signals from process CFU1 (GSM 03.82) are shown entering the 'acknowledge' blocks. + +Figure 4.6a: Procedure Register\_FM\_for\_Remote\_Party + +![Flowchart for Procedure handle_Remote_Party_Erasure. The process starts with NotificationRequired := FALSE. It checks if FM is registered to remote party. If no, Result := FM not registered to remote party. If yes, it checks if Supervisor indicator is present. If yes, it checks if remote party is registered to given MSISDN. If no, Result := Remote party not registered to this MSISDN. If yes, NotificationRequired := TRUE. If Supervisor indicator is not present, it checks if remote party is registered to init_MSISDN. If no, it checks if initiating_MSISDN = remote_number. If yes, it proceeds to Erase_FM_for_Remote_party. If no, Result := remote party not registered to this MSISDN. If remote party is registered to init_MSISDN, it proceeds to Erase_FM_for_Remote_party. After Erase_FM_for_Remote_party, it checks if result = pass. If no, Result := corresponding unsuccessful outcome code. If yes, FM states := not registered & not active, then Result := FM successful deregistered. All result paths lead to HLR-FM-Response (Result). From there, it checks if NotificationRequired = TRUE. If yes, it calls Init-Notify (OC,SC,FN,SI, MSISDN-A,AI) to the FFN process FFN_Forced_erasure_Notify. Finally, it reaches an exit node.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +**Procedure handle\_Remote\_Party\_Erasure** 1(1) + +This procedure describes the case where the FFN is an HLR. IN Solutions should have similar behaviour, + +signals to/from the left are to/from the HLR of the initiating subscriber + signals to/from the right are to/from the CFU process as indicated + +``` + + graph TD + Start([ ]) --> Init[NotificationRequired := FALSE] + Init --> Dec1{FM registered to remote party?} + Dec1 -- no --> Res1[Result := FM not registered to remote party] + Dec1 -- yes --> Dec2{Supervisor indicator present?} + + Dec2 -- yes --> Dec3{Is remote party registered to given MSISDN?} + Dec2 -- no --> Dec4{remote party registered to init_MSISDN?} + + Dec3 -- no --> Res2[Result := Remote party not registered to this MSISDN] + Dec3 -- yes --> Res3[NotificationRequired := TRUE] + + Dec4 -- no --> Dec5{initiating_MSISDN = remote_number?} + Dec4 -- yes --> Proc1[Erase_FM_for_Remote_party] + + Dec5 -- no --> Res4[Result := remote party not registered to this MSISDN] + Dec5 -- yes --> Proc1 + + Res3 --> Proc1 + + Proc1 --> Dec6{result = pass?} + Dec6 -- no --> Res5[Result := corresponding unsuccessful outcome code] + Dec6 -- yes --> State1[FM states := not registered & not active] + State1 --> Res6[Result := FM successful deregistered] + + Res1 --> Join1(( )) + Res2 --> Join1 + Res4 --> Join1 + Res5 --> Join1 + Res6 --> Join1 + + Join1 --> ResOut[/HLR-FM-Response (Result)/] + ResOut --> Dec7{NotificationRequired = TRUE?} + + Dec7 -- yes --> Out1[/Init-Notify (OC,SC,FN,SI, MSISDN-A,AI)/] + Dec7 -- no --> Join2(( )) + Out1 --> Join2 + Join2 --> End([X]) + +``` + +*If yes, then FM service supervisor performs FM erasure* + +*If yes, remote party erases her own FM data* + +*to the FFN process FFN\_Forced\_erasure\_Notify* + +Flowchart for Procedure handle\_Remote\_Party\_Erasure. The process starts with NotificationRequired := FALSE. It checks if FM is registered to remote party. If no, Result := FM not registered to remote party. If yes, it checks if Supervisor indicator is present. If yes, it checks if remote party is registered to given MSISDN. If no, Result := Remote party not registered to this MSISDN. If yes, NotificationRequired := TRUE. If Supervisor indicator is not present, it checks if remote party is registered to init\_MSISDN. If no, it checks if initiating\_MSISDN = remote\_number. If yes, it proceeds to Erase\_FM\_for\_Remote\_party. If no, Result := remote party not registered to this MSISDN. If remote party is registered to init\_MSISDN, it proceeds to Erase\_FM\_for\_Remote\_party. After Erase\_FM\_for\_Remote\_party, it checks if result = pass. If no, Result := corresponding unsuccessful outcome code. If yes, FM states := not registered & not active, then Result := FM successful deregistered. All result paths lead to HLR-FM-Response (Result). From there, it checks if NotificationRequired = TRUE. If yes, it calls Init-Notify (OC,SC,FN,SI, MSISDN-A,AI) to the FFN process FFN\_Forced\_erasure\_Notify. Finally, it reaches an exit node. + +**Figure 4.7: Procedure: Handle\_Remote\_Party\_Erasure** + +![Flowchart for Procedure Erase_FM_for_Remote_Party. The flow starts with an oval connector, followed by a process block 'Erase_CFU (BS = all BS)' with an arrow pointing 'to process CFU2 (GSM 03.82)'. This is followed by a 'wait_for_response' block. Then, a decision block splits into 'acknowledge (result)' (receiving 'from process CFU2 (GSM 03.82)') leading to 'Result := pass', and 'acknowledge (error)' (receiving 'from process CFU2 (GSM 03.82)') leading to 'Result := (error)'. Both result blocks lead to a final circle connector.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +Procedure Erase\_FM\_for\_Remote\_Party 1(1) + +This procedure is called by the procedure handle\_Remote\_party\_Erase after the authorisation checks have been done. This procedure describes the case if the FFN is an HLR, Camel or IN solution should have the same behavior. + +signals to/from the left are to/from the HLR of the initiating subscriber +signals to/from the right are to/from the CFU process as indicated. + +``` +graph TD; Start([ ]) --> Process[Erase_CFU (BS = all BS)]; Process --> Wait((wait_for_response)); Wait --> AcknowledgeResult{acknowledge (result)}; Wait --> AcknowledgeError{acknowledge (error)}; AcknowledgeResult --> ResultPass[Result := pass]; AcknowledgeError --> ResultError[Result := (error)]; ResultPass --> End(( )); ResultError --> End; +``` + +Flowchart for Procedure Erase\_FM\_for\_Remote\_Party. The flow starts with an oval connector, followed by a process block 'Erase\_CFU (BS = all BS)' with an arrow pointing 'to process CFU2 (GSM 03.82)'. This is followed by a 'wait\_for\_response' block. Then, a decision block splits into 'acknowledge (result)' (receiving 'from process CFU2 (GSM 03.82)') leading to 'Result := pass', and 'acknowledge (error)' (receiving 'from process CFU2 (GSM 03.82)') leading to 'Result := (error)'. Both result blocks lead to a final circle connector. + +Figure 4.7a: Procedure Erase\_FM\_for\_Remote\_party + +![Flowchart for Procedure Handle_Remote_Party_Interrogation. It starts with an oval connector, leading to a decision diamond 'is FM registered?'. The 'no' path leads to a process box 'Result := FM not registered to remote party'. The 'yes' path leads to a process box 'Result := FM active to MSISDN', which has a note: 'The MSISDN digits are sent in the USSD response separated by a blank character from the outcome code'. Both process boxes lead to a decision diamond 'HLR-FM-Response (Result)', which then leads to a circle connector with an 'X'.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Procedure Handle\_Remote\_Party\_Interrogation 1(1) + +This procedure describes the case where the FFN is an HLR. IN solutions should have similar behaviour. + +signals to/from the left are to/from the HLR of the initiating subscriber + +``` +graph TD; Start([ ]) --> Decision{is FM registered?}; Decision -- no --> Process1[Result := FM not registered to remote party]; Decision -- yes --> Process2[Result := FM active to MSISDN]; Process2 -.-> Note[The MSISDN digits are sent in the USSD response separated by a blank character from the outcome code]; Process1 --> Decision2{HLR-FM-Response (Result)}; Process2 --> Decision2; Decision2 --> End((X)) +``` + +Flowchart for Procedure Handle\_Remote\_Party\_Interrogation. It starts with an oval connector, leading to a decision diamond 'is FM registered?'. The 'no' path leads to a process box 'Result := FM not registered to remote party'. The 'yes' path leads to a process box 'Result := FM active to MSISDN', which has a note: 'The MSISDN digits are sent in the USSD response separated by a blank character from the outcome code'. Both process boxes lead to a decision diamond 'HLR-FM-Response (Result)', which then leads to a circle connector with an 'X'. + +Figure 4.8: Procedure Handle\_Remote\_Party\_Interrogation + +![Flowchart for Process FFN_Forced_Erasure_Notify. The process starts at 'Idle', sends an 'Init-Notify' message, and sets 'NotifyCounter := 1'. It then enters a loop: 'start the Network initiated USSD' -> 'USSD-Notify (OC,SC,FN,SI, MSISDN-A,AI)' -> 'wait for USSD notify Response'. From the response, it branches into 'USSD-Notify-response (result)' which leads to 'Idle', or 'USSD-Notify-response (error)' which leads to a decision 'should the USSD-Notify be resent?'. If 'no', it leads to another decision 'NotifyCounter <= n (n<=5)'. If 'no' to this, it leads to 'Idle'. If 'yes', it leads to 'start Timer for resending Notify' -> 'NotifyCounter increment by 1' -> '1' (connector). If 'yes' to 'should the USSD-Notify be resent?', it leads to a note 'Depending on the error types and the specific implementation the process shall decide to resend the USSD message.' which then leads to the 'USSD-Notify' step. A note 'After Timer over, the process goes on.' is associated with the 'NotifyCounter increment by 1' step.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Process FFN\_Forced\_Erasure\_Notify 1(1) + +This process describes the case where the FFN is an HLR. Camel or IN solutions should have the similar behavior. + +Signals to/from the right are to/from the process Forwarding\_Service\_Control. Signals to/from the left are to/from the HLRp unless otherwise stated. + +``` + +graph TD + Idle1([Idle]) --> Init[Init-Notify +(OC,SC,FN,SI, +MSISDN-A,AI)] + Init --> Counter[NotifyCounter := 1] + Counter --> LoopStart(( )) + LoopStart --> USSDNotify{USSD-Notify +(OC,SC,FN,SI, +MSISDN-A,AI)} + StartUSSD[start the Network +initiated USSD] -.-> USSDNotify + USSDNotify --> Wait[wait for +USSD notify +Response] + Wait --> Result{USSD-Notify- +response +(result)} + Wait --> Error{USSD-Notify- +response +(error)} + Result --> Idle2([Idle]) + Error --> Resent{should the +USSD-Notify +be resent?} + Resent -- no --> CounterLimit{NotifyCounter +<= n (n<=5)} + Resent -- yes --> NoteResent[Depending on the +error types and the +specific +implementation the +process shall decide +to resend the USSD +message.] + NoteResent --> USSDNotify + CounterLimit -- no --> Idle3([Idle]) + CounterLimit -- yes --> Timer[start Timer for +resending Notify] + Timer --> CounterInc[NotifyCounter +increment by 1] + CounterInc --> Connector1((1)) + NoteTimer[After Timer over, +the process +goes on.] -.-> CounterInc + +``` + +Flowchart for Process FFN\_Forced\_Erasure\_Notify. The process starts at 'Idle', sends an 'Init-Notify' message, and sets 'NotifyCounter := 1'. It then enters a loop: 'start the Network initiated USSD' -> 'USSD-Notify (OC,SC,FN,SI, MSISDN-A,AI)' -> 'wait for USSD notify Response'. From the response, it branches into 'USSD-Notify-response (result)' which leads to 'Idle', or 'USSD-Notify-response (error)' which leads to a decision 'should the USSD-Notify be resent?'. If 'no', it leads to another decision 'NotifyCounter <= n (n<=5)'. If 'no' to this, it leads to 'Idle'. If 'yes', it leads to 'start Timer for resending Notify' -> 'NotifyCounter increment by 1' -> '1' (connector). If 'yes' to 'should the USSD-Notify be resent?', it leads to a note 'Depending on the error types and the specific implementation the process shall decide to resend the USSD message.' which then leads to the 'USSD-Notify' step. A note 'After Timer over, the process goes on.' is associated with the 'NotifyCounter increment by 1' step. + +Figure 4.9: Process FFN\_Forced\_Erasure\_Notify + +## 4.4 USSD interworking and Cross-phase compatibility + +All the messages between MS and the mobile network and internal to the mobile network, which are used for control of Follow Me, are USSD Phase 2 messages. + +A Cross-phase compatibility mechanism specified in 3GPP TS 23.011 [6] for networks or MS not supporting USSD Phase 2 is not required. + +Networks subject to the Interoperability Directive have to implement FM using USSD Phase 2. + +NOTE: As an option, these networks may also implement FM using USSD Phase 1. + +# 5 Information stored in the network entities + +## 5.1 Information stored in HLRA and FFNb + +The HLRA shall store: + +- the state of FM (which shall be one of the valid states listed below). + +The FFNb shall store: + +- the state of FM if the remote party is a GSM subscriber; +- the registration parameter: + - the initiating number (MSISDN<sub>A</sub>). + +The following logical states are applicable for FM (refer to TS 23.011 for an explanation of the notation): + +### **In HLRa (for the initiating subscriber)** + +| <b>Provisioning State</b> | <b>Registration State</b> | <b>Activation State</b> | <b>HLR Induction State</b> | +|---------------------------|---------------------------|-------------------------|----------------------------| +| (Not Provisioned, | Not Registered, | Not Active, | Not Induced) | +| (Provisioned, | Not Registered, | Not Active, | Not Induced) | + +The registration and activation state is the same for each applicable elementary basic service group. + +The provisioning state shall be per subscriber, and hence the same for all basic service groups. + +### **In FFNb (for the remote party).** + +| <b>Provisioning State</b> | <b>Registration State</b> | <b>Activation State</b> | <b>HLR Induction State</b> | +|---------------------------|---------------------------|-------------------------|----------------------------| +| (Not Provisioned, | Not Registered, | Not Active, | Not Induced) | +| (Provisioned, | Not Registered, | Not Active, | Not Induced) | +| (Provisioned, | Registered, | Active and Operative, | Not Induced) | + +The registration and activation state is the same for each applicable elementary basic service group. + +The provisioning state shall be per subscriber, and hence the same for all basic service groups. + +## 5.2 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of FM. The state changes are caused by actions of the service provider, the mobile user or the network. + +NOTE: Error cases are not shown in the diagram as they do not normally cause a state change. Successful requests that do not cause a state change are not shown in the diagram. + +The diagram only shows operations on an elementary basic service group. + +![State transition model for FM diagram](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` +stateDiagram-v2 + [*] --> S1 : Provision + S1 --> S2 : Withdrawal + S2 --> S1 : Registration + S2 --> S3 : Erasure + S3 --> S1 : Withdrawal +``` + +The diagram illustrates a state transition model for FM with three states represented by ovals: + +- Top State:** (Not Provisioned, Not Registered, Not Active, Not Induced) +- Bottom Left State:** (Provisioned, Not Registered, Not Active, Not Induced) +- Bottom Right State:** (Provisioned, Registered, Active and Operative, Not Induced) + +Transitions between states are as follows: + +- A transition labeled **Provision** leads from the initial state to the Bottom Left State. +- A transition labeled **Withdrawal** leads from the Bottom Left State back to the Top State. +- A transition labeled **Registration** leads from the Bottom Left State to the Bottom Right State. +- A transition labeled **Erasure** leads from the Bottom Right State back to the Bottom Left State. +- A transition labeled **Withdrawal** leads from the Bottom Right State back to the Top State. + +State transition model for FM diagram + +Figure 5.1: State transition model for FM + +## 5.3 Information stored in the VLR + +There is no FM information stored in the VLR. + +## 5.4 Transfer of information from HLR to VLR + +There is no FM information transferred from HLR to VLR. + +# Annex A (informative): Checking matrix for FM-CFU interaction in FFNb + +The following table is applicable under the assumption that FM and CFU are always provisioned to the remote party. + +If FM is not provisioned then there is no interaction between FM and CFU. + +If FM is Registered and Active, CFU must also be Registered and Active. + +Interrogation of both FM and CFU is allowed in any registration state. + +**Table A.1: Operation allowance check according registration states of FM and CFU (informative)** + +| Operation | Registration States | | Outcome | +|------------------|-----------------------|------------------------|-----------------------------------------------------------------| +| | FM | CFU | | +| Registration FM | Not registered | Not registered | FM: Registered and Active<br>CFU: Registered and Active | +| | | Registered, not active | operation not allowed | +| | | Registered, active | operation not allowed | +| | registered and active | Registered, active | see note 1 | +| Erasure FM | Not registered | Not registered | operation not allowed,<br>see note 2 | +| | | Registered, not active | operation not allowed | +| | | Registered, active | operation not allowed | +| | registered and active | Registered, active | FM: Not Registered<br>CFU: Not Registered | +| Registration CFU | Not registered | Not registered | FM: Not registered<br>CFU: Registered, active<br>see note 3 | +| | | Registered, not active | FM: Not registered<br>CFU: Registered, active<br>see note 3 | +| | | Registered, active | FM: Not registered<br>CFU: Registered, active<br>see note 3 | +| | registered and active | Registered, active | operation not allowed,<br>see note 4 | +| Erasure CFU | Not registered | Not registered | operation not allowed,<br>see note 3 | +| | | Registered, not active | FM: Not registered<br>CFU: Not registered<br>note 3 | +| | | Registered, active | FM: Not registered<br>CFU: Not registered<br>see note 3 | +| | registered and active | Registered, active | operation not allowed,<br>see note 4 | +| Activation CFU | Not registered | Not registered | operation not allowed,<br>see note 3 | +| | | Registered, not active | FM: Not registered<br>CFU: Registered, active<br>see note 3 | +| | | Registered, active | FM: Not registered<br>CFU: Registered, active<br>see note 3 | +| | registered and active | Registered, active | operation not allowed,<br>see note 4 | +| Deactivation CFU | Not registered | Not registered | operation not allowed,<br>see note 3 | +| | | Registered, not active | operation not allowed,<br>see note 3 | +| | | Registered, active | FM: Not registered<br>CFU: Registered, not active<br>see note 3 | + +| Operation | Registration States | | Outcome | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------|--------------------------------------| +| | FM | CFU | | +| | registered and active | Registered, active | operation not allowed,<br>see note 4 | +| NOTE 1: The operation is only allowed when the registration is made by the same initiating subscriber. The registration states of FM and CFU shall not be changed by the operation.<br>NOTE 2: The outcome code should be "Remote party not registered".<br>NOTE 3: Refer to TS 23.082 for CFU handling.<br>NOTE 4: Conflicting situation with other supplementary service (see TS 22.082: Exceptional procedures or unsuccessful outcome). | | | | + +# --- Annex B (normative): FM control Messages and their contents + +## B.1 General principles + +All messages used for the control of FM are based on mobile initiated USSD. The principles of USSD can be found in 3GPP TS 22.090, 3GPP TS 23.090, 3GPP TS 24.090 and 3GPP TS 29.002. + +The present document is only concerned with the contents of the USSD strings. + +## --- B.2 Information Elements used in the messages + +### The operation code + +The operation code is defined in 3GPP TS 22.030 for the control of Supplementary Services and consists of the two characters: + +- \*\* for Registration; +- ## for Erasure; +- \*# for Interrogation. + +### The Service Codes + +The Service Code is service specific for FM. + +### The remote number + +The remote number is the basic MSISDN of the remote party if the remote party is a GSM subscriber. It is entered by the initiating subscriber as part of the registration request. It is a number in international format. + +### Additional information field + +An additional information field which does not exceed 30 octets may be optionally included in all FM control messages to convey operator specific information to the FFNb. The content and use of this additional information is operator specific and out of scope of the present document. + +### The initiating number + +The initiating number is the basic MSISDN of the initiating subscriber. It is derived by HLRA from the IMSI of the initiating subscriber. + +This parameter is used in international format according to the scheme: + +- country code, national (significant) number. + +## --- B.3 Messages Contents of the FM Request + +Contents of the USSD string of FM-Request: + +- all parameters are entered by the initiating subscriber and transported transparently to HLRA. + +**Table B.1: Contents of the USSD string of FM-Request** + +| Parameter number | Value | Parameter mandatory (M) or optional (O) | Comment | +|------------------|------------------------------|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | OC | M | Operation Code:<br>OC = ** ... for Registration<br>OC = ## ... for Erasure<br>OC = *# ... for Interrogation | +| 2 | SC | M | Service Code for Follow Me. SMG1 Refer to 22.030 for the Service Code for Follow Me. | +| 3 | * | M | Delimiter | +| 4 | REMOTE NUMBER | M | remote number | +| 5 | * | M | Delimiter. | +| 6 | Supervisor Indicator | C | Supervisor Indicator = 88. Used for Forced Erasure by FM Service Supervisor. | +| 7 | * | M | Delimiter | +| 8 | MSISDN | C | MSISDN of previous initiating subscriber who has registered the FM to remote number. This parameter is conditional, only used for forced erasure. | +| 9 | * | M | Delimiter | +| 10 | Additional information field | O | For operator specific use | +| last | # | M | End of USSD string | + +## B.4 Messages Contents of the HLR-FM-Request + +Contents of the USSD string of HLR-FM- Request is the same of FM-Request described in clause B.3. Additionally, the MSISDNa is sent to the FFNb together with the FM-Request within the MAP operation. Contents of the FM-Response Messages. + +The FM-Response messages which are generated by the HLR, as well as the HLR-FM-Response messages which are received by the HLR from the FFN and are forwarded unchanged as FM-Response messages to the MS, contain the following two parts: + +- mandatory part: two digit outcome codes, which are interpreted in the MS according to operator specific requirements; +- optional part: the response texts. + +The optional part is separated by a space character as separator which occurs together with the optional part. + +These outcome codes indicating success or error of the requested FM operation are 2 USSD characters according to the following table (table B.2). + +#### **Table B.2 Outcome codes for FM-Response** + +| Scenario | Text examples for MS display | Reg | Era | Interro | Outcome Code | +|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|---------|---------------| +| <b>Outcome codes for successful cases</b> | | | | | 00 series | +| Success registration Case | Follow Me activated | X | | | 01 | +| Success erasure Case | Follow Me deactivated | | X | | 02 | +| Success interrogation Case | Follow Me active to <MSISDN><br>The MSISDN digits are sent in the USSD response separated by a <i>blank</i> character from the outcome code. | | | X | 03 | +| Operator Specific outcome codes | | | | | 04-06 | +| Reserved for future enhancement | | | | | 07-09 | +| <b>Spare outcome code</b> | | | | | 10 | +| Reserved for GSM-Railway | | | | | 11-12 | +| <b>Spare outcome codes</b> | | | | | 13-19 | +| | | | | | | +| <b>Outcome codes generated at the HLRa in non-successful cases</b> | | | | | 20, 30 series | +| Incoming barrings | Illegal interaction with incoming barring | X | X | X | 21 | +| Unauthorised request | Unauthorised request | X | X | X | 22 | +| Operator Specific outcome codes | | | | | 23-30 | +| Reserved for future enhancement | | | | | 31-39 | +| <b>Outcome codes generated at both the HLRa and the FM function node in non-successful cases</b> | | | | | 40 series | +| Unknown remote party | Unknown remote party | X | X | X | 41 | +| FM not subscribed | FM not subscribed | X | X | X | 42 | +| Operator Specific outcome codes | | | | | 43-45 | +| Reserved for future enhancement | | | | | 46-49 | +| | | | | | | +| <b>Spare unsuccessful outcome codes</b> | | | | | 50 series | +| | | | | | | +| <b>Outcome codes generated at the FM function node in non-successful cases</b> | | | | | 60, 70 series | +| Remote party already registered | Remote party already registered | X | | | 61 | +| FM not registered to remote party | FM not registered to remote party | | X | X | 62 | +| Remote party not registered to this MSISDN | Remote party not registered to this MSISDN | | X | | 63 | +| Remote Party Authorisation failed | Unauthorised changes to remote party | X | X | | 64 | + +| Scenario | Text examples for MS display | <u>Reg</u> | <u>Era</u> | <u>Interro</u> | Outcome Code | +|--------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|------------|------------|----------------|--------------| +| Call Forwarding active or registered | Illegal interaction with call forwarding | X | | | 65 | +| Incoming or outgoing barrings | Illegal interaction with call barrings | X | X | | 66 | +| Request to own MSISDN not possible | Request to own MSISDN not possible | X | | | 67 | +| Operator Specific outcome codes | | | | | 68-72 | +| Reserved for future enhancement | | | | | 73-79 | +| <b>Outcome codes could be sent back by CFU processes in unsuccessful cases</b> | | | | | | +| forwarded-to number is invalid directory number | forwarded-to number is invalid directory number | X | | | 80 | +| insufficient information | insufficient information | X | X | | 81 | +| forwarded-to number is a special service code | forwarded-to number is a special service code (e.g. police) | X | | | 82 | +| Conflicting situation with other supplementary services | Conflicting situation with other supplementary services (e.g. incoming call barring has been activated) | X | | X | 83 | +| Inconsistent with registration | Inconsistent with registration | | X | | 84 | +| <b>Spare unsuccessful outcome codes</b> | | | | | 85 - 99 | + +## B.5 Contents and Format of the USSD String of the USSD-Notify + +The Contents and the format of the USSD string of the USSD-Notify are described in the following table. + +**Table B.3: Contents of the USSD string of the USSD-Notify for forced de-registration** + +| Parameter number | Value | Parameter mandatory (M), optional (O) or conditional (C) | Comment | +|------------------|--------------------------------------------|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | OC | M | Operation Code:<br>OC = ## ... for Erasure | +| 2 | SC | M | Service Code for Follow Me. SMG1 Refer to 22.030 for the Service Code for Follow Me. | +| 3 | * | M | Delimiter | +| 4 | REMOTE NUMBER (forced deregistered number) | M | remote number | +| 5 | * | M | Delimiter. | +| 6 | Supervisor Indicator | C | Supervisor Indicator = 88. This parameter is mandatory used for Forced Erasure by FM Service Supervisor (see also parameter number 8). | +| 7 | * | M | Delimiter | +| 8 | MSISDN | C | <ul style="list-style-type: none"> <li>- This parameter is mandatory as MSISDN of supervisor who initiated the forced deregistration request.</li> <li>- This parameter shall not be included if initiated by an administrative terminal connected to the FFN.</li> </ul> | +| 9 | * | M | Delimiter | +| 10 | Additional information field | O | Additional information field | +| last | # | M | End of USSD string | + +Note: USSD Notification for Forced deregistration done by administrative terminal in general is optional. + +## B.6 Inter-process Message Init-Notify + +The Init-Notify message is an inter-process message in FFN. It is sent from the process Handle\_Remote\_Party\_Erasure to process FFN\_Forced\_Erasure\_Notify. + +This message consists of the parameter USSD String. On receipt of the Init-Notify message, the process FFN\_Forced\_Erasure\_Notify will pack the USSD String into the USSD-Notify message and send it to the HLRp. Refer to Table B.3 for the contents and format of the USSD String. + +This message is only required where the FFN is based on an HLR. If the FFN is based on an IN system it is not required. + +# Annex C (informative): Change history + +| Change history | | | | | | +|----------------|---------|-----|--------|-------------|------------------------------------------------------------------------------------| +| TSG CN# | Version | CR | Rel. | New Version | Subject/Comment | +| CN#06 | - | | R99 | 3.0.0 | Approved at TSG CN#06 and placed under Change Control | +| CN#07 | 3.0.0 | 001 | R99 | 3.1.0 | Some corrections and further clear formulations to FM stage 2 specification | +| CN#09 | 3.1.0 | 002 | R99 | 3.2.0 | Correction of the wrong Service Code | +| CN#11 | 3.2.0 | | Rel-4 | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 4.0.0 | | Rel-5 | 5.0.0 | Release 5 after CN#16 | +| Jun 2002 | 5.0.0 | | Rel-5 | 5.0.1 | Corrupted figure 5.1 fixed | +| Dec 2003 | 5.0.1 | 003 | Rel-6 | 6.0.0 | Notify of forced erasure to previously registered subscriber of his deregistration | +| Dec 2006 | 6.0.0 | 004 | Rel-7 | 7.0.0 | Reservation of outcome codes for GSM-Railway | +| Dec 2008 | 7.0.0 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| Dec 2009 | 8.0.0 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 9.0.0 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 10.0.0 | - | Rel-11 | 11.0.0 | Update to Rel-11 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23141/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-11/23_series/23141/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4fd144eb3abcd53cda626202ac55b0a468d693c --- /dev/null +++ b/marked/Rel-11/23_series/23141/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58d55f0b4d56a8fe5b34bb953c66d64eb1c43506850dc724a12feaf701079008 +size 69919 diff --git a/marked/Rel-11/23_series/23141/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/Rel-11/23_series/23141/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe36fc6a4c34a2d1475a741e448cf134b4fb34c2 --- /dev/null +++ b/marked/Rel-11/23_series/23141/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a79ae136f71c68658c2fd8712e251c7ba4acc8e63510f0eddbbb3bc6b9001d6 +size 85649 diff --git a/marked/Rel-11/23_series/23141/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/23_series/23141/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec53e60c92888c3fb8aa72858b847d280bcee61f --- /dev/null +++ b/marked/Rel-11/23_series/23141/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ebc2d5565535986f1602d17ee3ac50fe1b95066e9932bbb19d5c12d163010c8 +size 67902 diff --git a/marked/Rel-11/23_series/23141/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-11/23_series/23141/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cea328493a582857ff3ca72bfada7e71b9ec8a6f --- /dev/null +++ b/marked/Rel-11/23_series/23141/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:434fef5a1b1062531f674d4e893aec92728024e88e6de11662970dcedf05fe69 +size 73549 diff --git a/marked/Rel-11/23_series/23141/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/23_series/23141/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee1148b1606c75453e1df7b65962e55757b936ef --- /dev/null +++ b/marked/Rel-11/23_series/23141/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41934d6dd1c24887acafdbde13fe64a4f2bd6a5b48cdb8bf7891df7d9898513b +size 35120 diff --git a/marked/Rel-11/23_series/23141/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-11/23_series/23141/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ae7e89e89851ce6a7f39ff51c2dc3e157615169 --- /dev/null +++ b/marked/Rel-11/23_series/23141/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8461d5a582b8bb74045a104c8f09875d809610c2c7a6bf20c845e72dfc146886 +size 32089 diff --git a/marked/Rel-11/23_series/23141/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg b/marked/Rel-11/23_series/23141/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..078d59a69a42457917a8b799757d3c0774496852 --- /dev/null +++ b/marked/Rel-11/23_series/23141/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04baa64ea4f2c61095a3a433bdda749fb6977374bed3d178bda97f842e2a16c2 +size 49098 diff --git a/marked/Rel-11/23_series/23141/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/Rel-11/23_series/23141/4f148853ae68fdcf5e43f7604cab457d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..814e4299f38e00d4c45421816dc14266446e016f --- /dev/null +++ b/marked/Rel-11/23_series/23141/4f148853ae68fdcf5e43f7604cab457d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03470624585f6d1044e852105d13b7d401ff964bb115db56e134133055626356 +size 43835 diff --git a/marked/Rel-11/23_series/23141/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Rel-11/23_series/23141/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..066f7ff631ecdd749f0b6b6be8bfe40645463f7d --- /dev/null +++ b/marked/Rel-11/23_series/23141/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94086871f1a741bd7ddd6306f23e46ea838c0a9e56ee04fc4a3a6d06504a5432 +size 52669 diff --git a/marked/Rel-11/23_series/23141/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-11/23_series/23141/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43ac083dfe9fb39dd8f943e17a68f0317ee9719b --- /dev/null +++ b/marked/Rel-11/23_series/23141/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20501d773654d90112ad1f3906f7ba4e57898c0f717d45e5073ea1f131f99feb +size 44488 diff --git a/marked/Rel-11/23_series/23141/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23141/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c1649c62d3c64bd7a83c3be04cdfd48b9320b42 --- /dev/null +++ b/marked/Rel-11/23_series/23141/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cefb089ddf8991f9eb2337677fe821e580f3b8ef20e724a83d697d8e34ab0bb6 +size 25879 diff --git a/marked/Rel-11/23_series/23141/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/23_series/23141/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcc7aafb51bffc93722bffe208c65adaf1d0786b --- /dev/null +++ b/marked/Rel-11/23_series/23141/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ac52b0b61354dd30f8aec59a97908a2a7f5098b5bcf55003b810318316d8a7b +size 30252 diff --git a/marked/Rel-11/23_series/23141/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Rel-11/23_series/23141/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..917144db2c3ac3383d998dce1b6993092c715488 --- /dev/null +++ b/marked/Rel-11/23_series/23141/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4adcb43723fdd6af8edb17fed423f6b82128b361b073591aa7be44dd4734aa9a +size 50382 diff --git a/marked/Rel-11/23_series/23141/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23141/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82049ccc5bbbb4c99c228b66c3b984c72026273b --- /dev/null +++ b/marked/Rel-11/23_series/23141/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e14544be17643aacdec9ec9346de7de31857921c4e3495764130bfa459e1221 +size 106406 diff --git a/marked/Rel-11/23_series/23141/bd57a547bec253d4179e5c4491c53dbb_img.jpg b/marked/Rel-11/23_series/23141/bd57a547bec253d4179e5c4491c53dbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3561d5145f76e7d25ad4d87774c7d1b8b669494 --- /dev/null +++ b/marked/Rel-11/23_series/23141/bd57a547bec253d4179e5c4491c53dbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66306b7a14b585c1673998382556102a94ae413f7870318ada65d1298d0ebc85 +size 40018 diff --git a/marked/Rel-11/23_series/23141/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/Rel-11/23_series/23141/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfd126c2251a5e983e738367a86b6f3965cb767a --- /dev/null +++ b/marked/Rel-11/23_series/23141/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37abbc292434b4f6429eb1bc23f72043987a9da61c8af817e96e318424432b1c +size 42360 diff --git a/marked/Rel-11/23_series/23141/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-11/23_series/23141/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6e723208c55bbcd7984d0c1799b59d55886a98c --- /dev/null +++ b/marked/Rel-11/23_series/23141/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbe03da9ce4b9aece79f936102585275c20189ae115d38e7f0562dbdecf94aed +size 54177 diff --git a/marked/Rel-11/23_series/23141/raw.md b/marked/Rel-11/23_series/23141/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e08ec484b05e8904185ffddbfae81f59f8a4abc2 --- /dev/null +++ b/marked/Rel-11/23_series/23141/raw.md @@ -0,0 +1,1328 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Presence Architecture ..... | 8 | +| 4.1 Overview ..... | 8 | +| 4.2 Reference Architecture Model ..... | 8 | +| 4.3 Reference points..... | 9 | +| 4.3.1 Reference point Presence User Agent – Presence Server (Peu)..... | 9 | +| 4.3.2 Reference point Presence Network Agent – Presence Server (Pen) ..... | 9 | +| 4.3.3 Reference point Presence External Agent – Presence Server (Pex)..... | 10 | +| 4.3.4 Reference point Watcher applications – Presentity Presence Proxy (Pw) ..... | 10 | +| 4.3.5 Reference point HSS/HLR – Presence Network Agent (Ph) ..... | 10 | +| 4.3.6 Reference point S-CSCF – Presence Network Agent (Pi) ..... | 11 | +| 4.3.7 Reference point Presentity Presence Proxy – HSS (Px)..... | 11 | +| 4.3.8 Reference point Presence Network Agent – GMLC (Pl)..... | 11 | +| 4.3.9 Reference point Presence Network Agent – SGSN (Pg)..... | 11 | +| 4.3.10 Reference point Presence Network Agent –MSC Server/VLR (Pc)..... | 11 | +| 4.3.11 Reference point Presence Network Agent – GGSN (Pk)..... | 11 | +| 4.3.12 Reference point Presence Network Agent – 3GPP AAA Server (Pr) ..... | 12 | +| 4.3.13 Reference point Presence Network Agent – PDG (Pp)..... | 12 | +| 4.3.14 Reference point Presence User Agent – Presentity Presence Proxy (Pep)..... | 12 | +| 4.3.15 Reference point Presentity Presence Proxy – Presence Server (Pwp)..... | 12 | +| 4.3.16 Reference point Watcher Applications – Presence List Server (Pet) ..... | 12 | +| 4.4 Support of OSA Presence Service Capability Server in the Presence Architecture ..... | 12 | +| 5 Functional Entities To Support Presence Service ..... | 13 | +| 5.1 Presence Server ..... | 13 | +| 5.2 Presence Agent Elements..... | 14 | +| 5.2.1 Presence User Agent..... | 14 | +| 5.2.1.1 Relationship of Presence User Agent with IMS entities..... | 15 | +| 5.2.2 Presence Network Agent..... | 16 | +| 5.2.2.0 General..... | 16 | +| 5.2.2.1 Functions of the Presence Network Agent ..... | 16 | +| 5.2.2.2 Suppliers of Presence Information..... | 17 | +| 5.2.2.3 Relationship of Presence Network Agent with IMS entities ..... | 17 | +| 5.2.3 Presence External Agent..... | 18 | +| 5.3 Presence Proxies..... | 18 | +| 5.3.1 Presence Proxies introduction ..... | 18 | +| 5.3.2 Watcher Presence Proxy..... | 18 | +| 5.3.3 Presentity Presence Proxy ..... | 18 | +| 5.3.4 Relationship of Presence Proxies with IMS entities..... | 19 | +| 5.4 Watcher Applications..... | 20 | +| 5.4.1 Communication between Watcher and Presentity Proxy ..... | 20 | +| 5.4.2 Watcher application in an IMS UE..... | 20 | +| 5.4.3 Network based Watcher Application Server ..... | 20 | +| 5.4.4 Watcher application located in the external Internet..... | 20 | +| 5.4.5 Presence Server located in the external Internet, Watcher application located in the IMS ..... | 21 | +| 5.5 Presence List Server ..... | 21 | +| 6 Presence attributes..... | 21 | +| 6.1 Presence Attributes..... | 21 | +| 6.1.1 Subscriber Presence Attributes and Values ..... | 21 | +| 6.1.2 Presence Structure to Support Multiple Values for Attributes ..... | 22 | +| 6.2 Presence Information Model ..... | 22 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------------------------------|-----------| +| 7 | Subscription authorisation policies ..... | 23 | +| 8 | Charging requirement ..... | 24 | +| <b>Annex A (informative):</b> | <b>Information flows .....</b> | <b>25</b> | +| A.1 | General information flow ..... | 25 | +| A.2 | Detailed information flows ..... | 26 | +| A.2.1 | Overview of flows used..... | 26 | +| A.2.2 | Flows demonstrating how watchers subscribe to presence event notification ..... | 27 | +| A.2.2.1 | IMS Watcher and IMS Presentity in the same or different IM-CN ..... | 27 | +| A.2.3 | Flows demonstrating how presentities update Presence Information ..... | 28 | +| A.2.3.1 | Updating presence information by terminals without support of the Pep reference point ..... | 28 | +| A.2.3.2 | IMS Registration Notification process to the Presence Server within IMS ..... | 29 | +| A.2.3.3 | CS/PS Notification process of the Presence Server ..... | 30 | +| A.2.3.4 | Updating presence information by terminals with Pep interface support ..... | 31 | +| A.2.4 | Presence Server notifying watcher of updates to presence information ..... | 32 | +| A.2.4.1 | IMS based Watcher and presentity in the same or different IM-CN subsystem ..... | 32 | +| A.2.5 | Presence User Agent subscribing to watcher list and receiving notification of a new watcher subscription ..... | 33 | +| <b>Annex B (Informative):</b> | <b>Void.....</b> | <b>35</b> | +| Annex C (informative): | Change history..... | 36 | + +# --- 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 stage 2 description (architectural solution and functionalities) for the Presence Service, which includes the elements necessary to realise the stage 1 requirements in TS 22.141 [2]. + +The present document includes information applicable to network operators, service providers and manufacturers. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.141: "Presence service; Stage 1". +- [3] IETF RFC 3863: "Presence Information Data Format", August 2004. +- [4] IETF RFC 3856: "A Presence Event Package for the Session Initiation Protocol (SIP)", August 2004. +- [5] 3GPP TS 33.203: "3G security; Access security for IP-based services". +- [6] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles". +- [7] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging". +- [8] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security". +- [9] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [10] 3GPP TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2". +- [11] IETF RFC 3265: "Session Initiation Protocol (SIP) Event Notification". +- [12] Void. +- [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 23.271: "Location Services (LCS); Functional description; Stage 2". +- [15] 3GPP TS 23.198: "Open Service Access (OSA); Stage 2". +- [16] IETF RFC 2778: "A Model for Presence and Instant Messaging". +- [17] IETF RFC 2779: "Instant Messaging / Presence Protocol Requirements". +- [18] 3GPP TS 23.002: "Network architecture". +- [19] 3GPP TS 23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; System description". + +- [20] LIF TS 101: "Mobile Location Protocol Specification"(Location Interoperability Forum 2001) +[Available at <http://www.openmobilealliance.org>]. +- [21] 3GPP TR 23.981 "Interworking aspects and migration scenarios for IPv4 based IMS +implementations". +- [22] 3GPP2 X.S0027-004: "Network Presence". +- [23] 3GPP2 X.S0004: "Introduction to MAP". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions defined in TR 21.905 [1] and TS 22.141 [2] and the following apply: + +**Presence List Server:** functional entity that stores grouped lists of watched presentities and enables a Watcher Application to subscribe to the presence of multiple presentities using a single transaction. + +**Presence Network Agent:** network located element that collects and sends network related presence information on behalf of the presentity to a presence server. + +**Presentity Presence Proxy:** functional entity that provides presentity related functionality such as determining the presence server associated with a presentity. + +**Presence Server:** network entity responsible for managing presence information on behalf of a presence entity. + +**Presence User Agent:** a terminal or network located element that collects and sends user related presence information to a presence server on behalf of a Principal. + +**Watcher Presence Proxy:** a functional entity that provides watcher related function such as authentication of watchers. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations in TR 21.905 [1] and TS 22.141 [2] and the following apply: + +| | | +|--------|-----------------------------------------------------------| +| AAA | Authentication, Authorisation and Accounting | +| CAMEL | Customised Applications for Mobile network Enhanced Logic | +| CAP | CAMEL Application Part | +| CGI | Cell Global Identity | +| CS | Circuit Switched | +| CSCF | Call Session Control Function | +| GGSN | Gateway GPRS Support Node | +| GMLC | Gateway Mobile Location Centre | +| GPRS | General Packet Radio Service | +| HLR | Home Location Register | +| HSS | Home Subscriber Server | +| HTTP | Hyper Text Transport Protocol | +| I-CSCF | Interrogating CSCF | +| IETF | Internet Engineering Task Force | +| IMS | IP Multimedia Subsystem | +| ISDN | Integrated Service Digital Network | +| LIF | Location Interoperability Forum | +| MAP | Mobile Application Part | +| MSC | Mobile Switching Centre | +| MSISDN | Mobile Subscriber ISDN Number | +| P-CSCF | Proxy CSCF | +| PDG | Packet Data Gateway | +| PLMN | Public Land Mobile Network | +| PS | Packet Switched | + +| | | +|--------|-----------------------------| +| PUA | Presence User Agent | +| RFC | Request For Comments | +| SAI | Service Area Identity | +| S-CSCF | Serving CSCF | +| SGSN | Serving GPRS Support Node | +| SIP | Session Initiation Protocol | +| SMS | Short Message Service | +| UE | User Equipment | +| URL | Uniform Resource Locator | +| WAP | Wireless Access Protocol | +| WLAN | Wireless Local Area Network | +| WML | Wireless Markup Language | +| WV | Wireless Village | + +# --- 4 Presence Architecture + +## 4.1 Overview + +The Presence Service provides the ability for the home network to manage presence information of a user's device, service or service media even whilst roaming. A user's presence information may be obtained through input from the user, information supplied by network entities or information supplied by elements external to the home network. Consumers of presence information, watchers, may be internal or external to the home network. + +## 4.2 Reference Architecture Model + +The generic reference architectural model for providing presence service is depicted in Figure 4.2-1 below. The details of the elements in the figure (e.g. agents, proxies) are provided in clause 5. + +The mapping of the Presence Service functional elements and reference points to the functional elements and reference points in the 3GPP Network Architecture TS 23.002 [18] (and additionally IMS) is defined in clauses 4.3 and clause 5. + +![Figure 4.2-1: Reference architecture to support a presence service. The diagram shows two subscription authorisation lists on the left and five tuples on the right. The first list is for 'Friends' and includes Matt, Bob, and Bryan, with three tuples. The second list is for 'Public' and includes 'All watchers', with three tuples. The tuples on the right are: Tuple 1 (Attribute 1 = value A, Attribute 2 = value B), Tuple 2 (Attribute 3 = value C, Attribute 4 = value B), Tuple 3 (Attribute 5 = value D, Attribute 6 = value E), Tuple 4 (Attribute 1 = value E, Attribute 2 = value F), and Tuple 5 (Attribute 3 = value C, Attribute 7 = value G).](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +**Subscription authorisation list** +**"Friends":** +Matt +Bob +Bryan +**Tuples:** +Tuple 1 +Tuple 2 +Tuple 3 + +**Subscription authorisation list** +**"Public":** +'All watchers' +**Tuples:** +Tuple 3 +Tuple 4 +Tuple 5 + +**Tuple 1:** +Attribute 1 = value A +Attribute 2 = value B + +**Tuple 2:** +Attribute 3 = value C +Attribute 4 = value B + +**Tuple 3:** +Attribute 5 = value D +Attribute 6 = value E + +**Tuple 4:** +Attribute 1 = value E +Attribute 2 = value F + +**Tuple 5:** +Attribute 3 = value C +Attribute 7 = value G + +Figure 4.2-1: Reference architecture to support a presence service. The diagram shows two subscription authorisation lists on the left and five tuples on the right. The first list is for 'Friends' and includes Matt, Bob, and Bryan, with three tuples. The second list is for 'Public' and includes 'All watchers', with three tuples. The tuples on the right are: Tuple 1 (Attribute 1 = value A, Attribute 2 = value B), Tuple 2 (Attribute 3 = value C, Attribute 4 = value B), Tuple 3 (Attribute 5 = value D, Attribute 6 = value E), Tuple 4 (Attribute 1 = value E, Attribute 2 = value F), and Tuple 5 (Attribute 3 = value C, Attribute 7 = value G). + +Figure 4.2-1: Reference architecture to support a presence service + +## 4.3 Reference points + +### 4.3.1 Reference point Presence User Agent – Presence Server (Peu) + +This reference point shall allow the Presence User Agent to manage subscription authorization policies. + +IPv6 shall be supported for all functionalities required from a Presence User Agent that supports the Peu reference point. An IPv6 capable 3GPP UE shall use IPv6 when accessing Peu. However, early IMS implementations and deployments may use IPv4; if IPv4 is used, the guidelines and recommendations in TR 23.981 [21] should be followed. + +This reference point uses capabilities defined for the Ut reference point as defined in TS 23.002 [18]. + +### 4.3.2 Reference point Presence Network Agent – Presence Server (Pen) + +This reference point shall allow a presentity's presence information to be supplied to the Presence Server. The transport on this reference point shall not impose any limitations to the size of the presence information. + +Pen shall provide mechanisms for the Network Agent to manage subscription authorisation policies. + +Pen shall provide mechanisms for the Network Agent to supply or update only a certain subset of the presentity's presence information to the Presence Server. + +Pen shall provide mechanisms for activating or deactivating the reporting of Presence Information for a given presentity from the network entities within the PLMN. + +The Pen interface is an intra-operator interface. In order to provide the all the functionalities required on this reference point, a combination of multiple protocols may be used. In general the protocols used at the Pen reference point are not standardised. However, for 3GPP2 systems this reference point is defined in X.S0027-004 [x]. At least, this interface shall support the transport of presence information under the PIDF format as specified in IETF RFC 3863 [3]. + +### 4.3.3 Reference point Presence External Agent – Presence Server (Pex) + +This reference point shall allow a presentity's presence information to be supplied to the Presence Server. The transport on this reference point shall not impose any limitations on the size of the presence information. + +Pex shall provide mechanisms for the Presence External Agent to supply or update only a certain subset of the presentity's presence information to the Presence Server. + +In order to provide all the functionalities required on this reference point, a combination of multiple protocols may be used. Presence information obtained from an external network by the Presence External Agent is transferred across the Pex reference point to the Presence Server. This interface shall support the transport of presence information under the PIDF format as specified in IETF RFC 3863 [3]. + +### 4.3.4 Reference point Watcher applications – Presentity Presence Proxy (Pw) + +This reference point shall allow a Watcher application to request and obtain presence information. This interface shall support the transport of presence information under the PIDF format as specified in IETF RFC 3863 [3]. + +The transport shall not impose any limitations to the size of the presence information. + +In order to provide all the functionalities required on this interface, a combination of multiple protocols may be used. + +This reference point shall support both presence monitoring and fetching modes. In the fetching mode, it shall be possible for the watcher to once request all or only a subset of a presentity's presence information (e.g. one or more tuples). The subset of the presence information is defined by the filter that is carried in the presence information subscription. + +In the monitoring mode, it shall be possible for the watcher to request monitoring of all or a subset of a presentity's presence information (i.e. one or more tuples). Watcher shall be able to explicitly indicate the capability to process partial updates. The subset of the presence information is defined by the filter that is carried in the presence information subscription. It shall be possible for the watcher to request the presence server to filter out information when the watcher is equal to the publishing Presence User Agent. + +It shall be possible for the notifications containing the presentity's presence information to contain only information as defined by filters. It shall be possible for the notifications containing the presentity's presence information to contain only the modified tuples, i.e. only those tuples which have changed since the last notification. + +This reference point may allow a Watcher application to use presence lists in presence information subscriptions, and the Watcher Presence Proxy to interface to a server that provides the functionality of Presence List Server. + +IPv6 shall be supported for all functionalities required from a Watcher application that supports the Pw reference point. An IPv6 capable 3GPP UE shall use IPv6 when accessing Pw. However, early IMS implementations and deployments may use IPv4; if IPv4 is used, the guidelines and recommendations in TR 23.981 [21] should be followed. + +### 4.3.5 Reference point HSS/HLR – Presence Network Agent (Ph) + +This reference point shall allow the Presence Network Agent to query HSS/HLR about the state and status of a subscriber (associated with a presentity) from the serving network (for 3GPP this is the CS domain or GPRS) and IMS perspective. + +This reference point permits the Presence Network Agent to activate and deactivate the reporting of mobility management events from the serving network (for 3GPP this is the CS domain or GPRS) and/or the IMS-specific reports from the S-CSCF. + +This reference point uses capabilities defined for the Sh reference point as defined in TS 23.002 [18] as well as the MAP interface. + +### 4.3.6 Reference point S-CSCF – Presence Network Agent (Pi) + +The S-CSCF may provide IMS-specific presence information (e.g. about IMS registration state). This reference point shall use mechanisms defined for the ISC reference point as defined in TS 23.002 [18]. + +### 4.3.7 Reference point Presentity Presence Proxy – HSS (Px) + +The Px interface is an intra-operator interface. This interface shall assist locating the Presence Server of the presentity. This interface is implemented using the mechanisms defined for the Cx and Dx reference points as defined in TS 23.002 [18]. + +### 4.3.8 Reference point Presence Network Agent – GMLC (Pl) + +This reference point shall be used by the Presence Network Agent to retrieve location information related to a subscriber (associated with the presentity). This reference point is the interface to GMLC and it is an instance of the Le reference point (defined in TS 23.271 [14] and TS 23.002 [18]). In the case of Presence the LCS client (defined in TS 23.271 [14]) is the Presence Network Agent and so the protocol implementing Pl needs to be defined. Though normally a stage 3 responsibility in this case the protocol to be used is defined here since it is a reference to an existing protocol. Thus, Pl shall conform to OMA's LIF-MLP specification [20]. + +For 3GPP2 systems, the interface for this reference point is to the 3GPP2 Position Server and is not supported in the current release of the specification. + +### 4.3.9 Reference point Presence Network Agent – SGSN (Pg) + +This reference point shall allow the SGSN to report mobility management related events (such as attach/not reachable for paging/detach/routing area update) to the Presence Network Agent. + +This reference point may allow the SGSN to report Mobility States (such as Detached, Idle and Connected) and Session States (such as PDP context active and inactive). + +This reference point is implemented using the existing mechanisms of CAMEL phase 4, 3GPP Release 5. + +For 3GPP2 systems, this reference point is not supported. + +### 4.3.10 Reference point Presence Network Agent –MSC Server/VLR (Pc) + +This reference point shall allow the MSC Server/VLR to report the mobility management related events to the Network Agent (such as attach/detach/location area update) and may allow the MSC Server/VLR to report call related events (such as call setup with the bearer information and call release). + +This reference point may allow the MSC Server/ VLR to report Mobility States (such as Detached, Idle and Connected) and Call States (such as Busy with Bearer information and Idle). + +This reference point is implemented using the existing mechanisms of CAMEL phase 4, 3GPP Release 5. + +For 3GPP2 systems, the interface to this reference point is defined in 3GPP2 X.S0004 [23]. + +### 4.3.11 Reference point Presence Network Agent – GGSN (Pk) + +This reference point shall allow 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 of the RADIUS interface for reporting of access requests on Gi reference point as defined in TS 29.061 [13]. + +For 3GPP2 systems, this reference point is not supported. + +### 4.3.12 Reference point Presence Network Agent – 3GPP AAA Server (Pr) + +This reference point shall allow the 3GPP AAA Server to report IP-connectivity related events to the Presence Network Agent (such as WLAN UE attaching/detaching and tunnel establishment/removal). The Pr reference point shall be as much as possible based on mechanisms of existing interfaces. + +For 3GPP2 systems, the interface for this reference point is to the AAA server and is defined in X.S0027-004 [22]. + +### 4.3.13 Reference point Presence Network Agent – PDG (Pp) + +This reference point shall allow the PDG to report presence relevant events to the Presence Network Agent (such as tunnel establishment/removal, allocation of the remote IP address for the WLAN UE). This reference point is based on reusing of the Wi reference point. + +For 3GPP2 systems, this reference point is not supported. + +### 4.3.14 Reference point Presence User Agent – Presentity Presence Proxy (Pep) + +This reference point shall allow a presentity's presence information to be supplied to the Presence Server. The transport on this reference point shall not impose any limitations on the size of the presence information. This interface shall support the transport of presence information under the PIDF format as specified in IETF RFC 3863 [3]. + +Pep shall provide mechanisms for the Presence User Agent to obtain information on watcher subscriptions to the presentity's presence information. + +Pep shall provide mechanisms for the Presence User Agent to supply or update only a certain subset of the presentity's presence information to the Presence Server. It shall also be possible for the Presence User Agent to supply the complete presence document over Pep. + +Pep shall support SIP-based communications for publishing presence information. + +IPv6 shall be supported for all functionalities required from a Presence User Agent that supports the Pep reference point. An IPv6 capable 3GPP UE shall use IPv6 when accessing Pep. However, early IMS implementations and deployments may use IPv4; if IPv4 is used, the guidelines and recommendations in TR 23.981 [21] should be followed. + +### 4.3.15 Reference point Presentity Presence Proxy – Presence Server (Pwp) + +The Pwp interface is an intra-operator interface. This reference point shall allow all the functionalities provided by the Pw and Pep reference points. + +### 4.3.16 Reference point Watcher Applications – Presence List Server (Pet) + +This reference point shall allow a Watcher application to manage presence list information in the Presence List Server. + +This reference point uses capabilities defined for the Ut reference point as defined in TS 23.228 [9]. + +## 4.4 Support of OSA Presence Service Capability Server in the Presence Architecture + +An OSA API may be provided to allow external application to access presence service features, details of which are found in TS 23.198 [15]. + +The OSA Presence SCS may act like a presentity or a watcher. The application may then register as a presentity and/or watcher, to supply presence information, to request presence information, to be notified of subsequent changes, to request watcher information, and to manage subscription authorisation policies. + +# --- 5 Functional Entities To Support Presence Service + +## 5.1 Presence Server + +The Presence Server shall reside in the presentity's home network. + +The Presence Server shall be able to receive and manage presence information that is published by the Presence User/Network/External agents, and shall be responsible for composing the presence-related information for a certain presentity from the information it receives from multiple sources into a single presence document. The composing process to create the single presence document may involve complex transformations of presence information such as modifying the presence information from one presence source based on information from another presence source. In particular, the Presence server shall be able to receive and manage presence information that is published from multiple Presence User agents of the same presentity. The Presence Server shall be able to process partial publications of information from Presence User Agents. These partial publications contain the presence information of the presentity that has been modified since the latest publication sent to the Presence Server about this presentity. + +These Presence User agents may be updating the same parts of the presence information. + +The mechanisms for combining the presence related information shall be defined based on presence attributes, and according to certain policy defined in the Presence Server. The Presence Server shall be capable of receiving and composing the Presence information received in the standardized formats from authorized sources regardless of the source of the information or the ability to interpret the information contained in the presence tuples. The information that the Presence Server is not able to interpret shall be handled in a transparent manner. + +The Presence Server shall also allow watchers to request and subscribe to either the full set of presence information of a presentity, or only certain information within. Watcher defines the subset of the presence information, that he is interested in, by the filter that is carried in presence information subscription. The Presence Server shall be able to generate partial notifications to a watcher, which has indicated the capability to process them. These partial notifications contain the presence information of the presentity that has been modified since the latest notification sent to the watcher about this presentity, and required additional information to be able to link the partial notification to the information watcher has received earlier. In case the watcher does not indicate the capability to process partial notifications the presence server shall send only full updates. + +Before the subscription to presence information is accepted, the Presence Server should attempt to verify the identity of the watcher that subscribes to Presentity's Presence information, except if the watcher has indicated his desire to remain anonymous. The action taken by the Presence Server if the verification fails may include notifying the Presentity. + +The Presence Server shall support SIP-based communications for publishing presence information. + +The Presence Server shall support SIP-based communications with the Presentity Presence Proxy. The Presence Server is a SIP Application Server as defined by TS 23.228 [9], and is located using SIP URLs, standard SIP and existing IMS mechanisms (SIP routing, HSS query, ISC filtering, etc...). + +The Presence Server shall provide Subscription Authorization Policy. The Subscription Authorization Policy determines which Watchers are allowed to subscribe to a Presentity's Presence information. + +The Subscription Authorization Policy also determines which tuples of the Presentity's Presence information the watcher has access. It shall be possible for the Presentity's Presence User Agent to provide the Subscription Authorization Policy or it may be configured by the operator as part of the service provisioning. + +The Presence Server may provide a watcher configurable filtering function that is used to limit the information that is delivered to a watcher. After subscription the authorized watchers get notified of the actual Presence Information based on the Subscription Authorization Policy and the filters set by the watcher in the subscription. If the Presence Server does not support the filters as requested by the watcher, this is indicated to the watcher. In this case the notification shall contain the actual Presence information based on the Subscription Authorization Policy and local policy in the Presence Server. The Presence Server may support one or more of the following types of filters: Filters, which allow watchers to define: + +- the tuples that the watcher is interested in; +Watcher can define a criteria which allows the complete tuple and all the information within the tuple to be transmitted. E.g. watcher can define the filter to permit notifying all the tuples (and all the information within those tuples) which has "tel:+16305551212" as the contact address or "Instant Messaging" as a communication means. +- the attributes that the watcher is interested in; and +Watcher can define a criteria which result notifies to contain values only for defined attributes (attributes are defined by the filter and values for other attributes are not available in the notifications) +- the triggers when a notification should be sent. +Watcher can define a criteria which specifies when to send a notification. E.g. every time the communication means status attribute changes its value, a notification is sent to the watcher. Another example: filter out and do not send the notifications resulting from the publication of the Presence User agent that is equal to the watcher. + +The Presence Server shall collect watcher information to enable presentity to obtain information of the watchers that are or have been requesting, fetching or subscribing presentity's presence information. Service provider shall be able to define the maximum time period over which information is collected and stored. The watcher information list shall include: + +- identity of the watcher (unless anonymity was requested); +In case of anonymous watcher, the identity of the watcher shall not be provided to the presentity. The presentity shall be able to determine that an anonymous watcher has requested, fetched or subscribed presence information of the presentity including related information as specified in this list without revealing the watchers identity. + +- time of the request, fetch or subscription; +- length of the subscription; and +- state of the request or subscription. + +The Presence Server shall be able to support the presentity obtaining the above watcher information. The Presence Server shall be able to receive watcher information fetches and subscriptions from the presentity. These watcher information fetch and subscribe requests shall be able to contain filters which define: + +- what watchers the presentity is interested in; + +Possible categories are: + +- all watchers; + - defined watchers; + - new, unauthorised watchers; and + - defined and new, unauthorised watchers. +- what information the presentity is interested in; and +The information is all or part of the watcher information list as defined above. +- the length of the watcher information history collection period that the presentity is interested in. + +In response to watcher information fetches, the presence server shall be able to provide requested watcher information to the presentity. In response to watcher information subscriptions, the presence server shall provide notification to the presentity of the current state of the subscribed watcher information. When there are subsequent changes in the subscribed watcher information, notifications of the changes in watcher information are sent to the presentity. + +The Presence Server may support rate-limiting or filtering of the presence notifications based on local policy in order to minimize network load. + +## 5.2 Presence Agent Elements + +The Agent elements in the Presence Architecture are functionally distinct from the Presence Server functional element. The generic function of the Agent elements is to make presence information available to the Presence Server element in standardized formats across standardized interfaces. + +### 5.2.1 Presence User Agent + +The Presence User Agent element shall provide the following functionality: + +- The Presence User Agent shall collect Presence information associated with a Presentity representing a Principal. +- The Presence User Agent shall assemble the Presence information in the format defined for the Peu and Pep reference points. +- The Presence User Agent shall send the Presence information to the Presence Server element either via the Presentity Presence Proxy over the Pep reference point or over the Peu reference point.- The Presence User Agent shall be capable of managing the subscription authorisation policies. +- The Presence User Agent shall handle any necessary interworking required to support terminals that do not support the Peu and Pep reference points. +- Presence User Agent shall uniquely identify itself (among the Presence User Agents of the presentity) when publishing presence information. + +From a conceptual view, the Presence User Agent (PUA) element resides between the presence server and the user's equipment as illustrated in the reference architecture in figure 4.2-1. In reality, a Presence User Agent may be located in the user's terminal or within a network entity. + +Where the PUA is located in UE, the UE shall support Pep and the Peu reference point to the Presence Server as illustrated in Figure 5.2.1-1 below. + +![Flowchart of UE based Presence User Agent logic](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +graph LR + A[Presence subscription or fetch] --> B[On block subscription authorisation list] + B -- Yes --> C[No data available] + B -- No --> D[On personal subscription authorisation list] + D -- Yes --> E[Access tuples related to that list] + D -- No --> F[On general subscription authorisation list] + F -- Yes --> G[Access tuples related to that list] + F -- No --> H[Possible notification or without notification to the presentity of pending subscription] + +``` + +Flowchart of UE based Presence User Agent logic + +**Figure 5.2.1-1: UE based Presence User Agent** + +The Network based Presence User Agent shall reside in the presentity's home network. + +Where the PUA is located within the network, the particular network entity shall support the Pep and Peu reference point to the presence server as illustrated in Figure 5.2.1-2. In this case, additional functionality may be required to provide routing between UE and the Presence User Agent, and, for the Presence User Agent to "register" the user within the "Presence network". + +In this case, the interface between the terminal and the Presence User agent is outside of the scope of the present document. + +![Sequence diagram of Network based Presence User Agent](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +``` + +sequenceDiagram + participant A as A Party Network + participant WA_A as WA - A + participant WPP as Watcher Presence Proxy + participant IPP as Presentity Presence Proxy + participant PS_B as PS - B + participant HLR_HSS as HLR/HSS + + Note left of A: 1. Presence enquiry for B + WA_A->>WPP: 2. + WPP->>IPP: 3. Presence enquiry for B + Note right of WPP: 4. + IPP->>PS_B: 5. Presence enquiry for B + PS_B->>HLR_HSS: 6. Presentity Presence Proxy derives address of B's presence + HLR_HSS->>PS_B: 7. Presence enquiry for B + Note right of PS_B: 8, 9. + PS_B->>IPP: 10a. B party status sent to IPP + IPP->>WPP: 10b. B party status sent to Watcher Presence Proxy + WPP->>WA_A: 10c. B party status sent to WA-A + WA_A->>A: 11. B's presence status to A + +``` + +Sequence diagram of Network based Presence User Agent + +**Figure 5.2.1-2: Network based Presence User Agent** + +#### 5.2.1.1 Relationship of Presence User Agent with IMS entities + +When the Presence User Agent is located in an IMS UE the Pep reference point is implemented using the Gm, Mw and ISC reference points as defined in TS 23.002 [18]. + +- The Gm, Mw, and ISC reference points allow a presentity's presence information to be supplied to the Presence Server. These reference points also allow for the Presence User Agent to obtain information on watcher subscriptions to the Presentities Presence Information. +- The Peu reference point is implemented using the Ut reference point as defined in TS 23.002 [18]. The Ut reference point provides mechanisms for the Presence User Agent to manage subscription authorisation policies. + +![Sequence diagram of Presence User Agent in IMS architecture showing interactions between UE, Watcher Presence Proxy (P-CSCF, S-CSCF), Presentity Presence Proxy (I-CSCF, S-CSCF), HSS, and Presence Server.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant UE + subgraph Home Network of watcher + WPP[Watcher Presence Proxy] + P-CSCF[P-CSCF] + S-CSCF_W[S-CSCF] + end + subgraph Home Network of presentity + PPP[Presentity Presence Proxy] + I-CSCF[I-CSCF] + S-CSCF_P[S-CSCF] + end + HSS[HSS] + PS[Presence Server] + + UE->>P-CSCF: 1. SubscribePres + P-CSCF->>S-CSCF_W: 2. SubscribePres + S-CSCF_W->>I-CSCF: 3. SubscribePres + I-CSCF->>HSS: 4. Query + HSS-->>I-CSCF: 5. Resp + I-CSCF->>S-CSCF_P: 6. SubscribePres + S-CSCF_P->>PS: 7. SubscribePres + PS-->>S-CSCF_P: 8. MsgAck + S-CSCF_P-->>I-CSCF: 9. MsgAck + I-CSCF-->>S-CSCF_W: 10. MsgAck + S-CSCF_W-->>P-CSCF: 11. MsgAck + P-CSCF-->>UE: 12. MsgAck + PS->>HSS: 13. NotifyPresUp + HSS->>S-CSCF_P: 14. NotifyPresUp + S-CSCF_P->>I-CSCF: 15. NotifyPresUp + I-CSCF->>S-CSCF_W: 16. MsgAck + S-CSCF_W->>P-CSCF: 17. MsgAck + P-CSCF->>UE: 18. MsgAck + +``` + +Sequence diagram of Presence User Agent in IMS architecture showing interactions between UE, Watcher Presence Proxy (P-CSCF, S-CSCF), Presentity Presence Proxy (I-CSCF, S-CSCF), HSS, and Presence Server. + +Figure 5.2.1-3: Presence User Agent in IMS architecture + +### 5.2.2 Presence Network Agent + +#### 5.2.2.0 General + +The Presence Network Agent shall reside in the presentity's home network. + +#### 5.2.2.1 Functions of the Presence Network Agent + +The Presence Network Agent element shall provide the following functionality: + +- The Presence Network Agent shall receive Presence information from network elements within the HPLMN and VPLMN. +- The Presence Network Agent shall be able to send requests to the HSS/HLR to cause other network elements to send (or stop sending) Presence Information to the Presence Network Agent. Note that this only applies where the other network element has Presence Information subscriptions managed via the HSS/HLR. +- The Presence Network Agent shall associate Presence information with the appropriate Subscriber/Presentity combination. +- The Presence Network Agent shall convert the Presence information into the format standardized for the Pen interface. +- The Presence Network Agent shall publish the Presence information to the Presence Server across the Pen reference point. + +#### 5.2.2.2 Suppliers of Presence Information + +The Presence Network Agent may receive Presence information from one or more of the following 2G/3G network elements over the specified reference point: + +| Network Element supplying Presence Information | Reference Point | +|------------------------------------------------|-----------------| +| HSS/HLR | Ph | +| S-CSCF | Pi | +| MSC Server/VLR | Pc | +| SGSN | Pg | +| GGSN | Pk | +| GMLC | Pl | +| 3GPP AAA Server | Pr | +| PDG | Pp | + +It is a matter of implementation and operator choice which reference points the Presence Network Agent supports towards suppliers of Presence information. Where other reference points support such a capability, a Presence Network Agent can use the Ph reference point to activate and deactivate publishing of Presence information via those reference points. + +#### 5.2.2.3 Relationship of Presence Network Agent with IMS entities + +Figure 5.2.2.3-1 below presents the architecture for the S-CSCF and the HSS to provide presence related information to the Presence Server. + +NOTE: The architecture on Figure 5.2.2.3-1 is an IMS-specific simplification of some of the interfaces of the generic Presence reference architecture presented in clause 4. + +![Diagram showing IMS network elements supplying presence information. A dashed box labeled 'IMS network elements supplying Presence information' contains HSS and S-CSCF. The HSS connects to a 'Presence Network Agent' via an interface labeled 'Sh = Ph'. The S-CSCF connects to the 'Presence Network Agent' via an interface labeled 'Pi = ISC'. The 'Presence Network Agent' connects to a 'Presence server (home IMS network)' via an interface labeled 'Pen'.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg) + +``` + +graph LR + subgraph IMS_network_elements [IMS network elements supplying Presence information] + HSS[HSS] + S-CSCF[S-CSCF] + end + HSS -- "Sh = Ph" --> PNA[Presence Network Agent] + S-CSCF -- "Pi = ISC" --> PNA + PNA -- "Pen" --> PS[Presence server home IMS network] + +``` + +Diagram showing IMS network elements supplying presence information. A dashed box labeled 'IMS network elements supplying Presence information' contains HSS and S-CSCF. The HSS connects to a 'Presence Network Agent' via an interface labeled 'Sh = Ph'. The S-CSCF connects to the 'Presence Network Agent' via an interface labeled 'Pi = ISC'. The 'Presence Network Agent' connects to a 'Presence server (home IMS network)' via an interface labeled 'Pen'. + +**Figure 5.2.2.3-1: IMS network elements supplying presence information** + +The ISC interface is used to convey presence information from the S-CSCF to the Presence Network Agent. More specifically, the functions of the Pi interface are taken care of by the ISC interface. As an example, the S-CSCF can convey a user's IMS-registration status by generating and sending a 3<sup>rd</sup> party REGISTER request to the Presence server. + +The Sh interface is used to convey information from the HSS to the Presence Network Agent. More specifically, the functions of the Ph interface are taken care of by the Sh interface. + +Since the Network Agent is introduced as a functional entity, which models the abstraction from the different presence sources, the network agent and the presence server may be collocated. In case of an IMS-only network environment the Pen reference point is assumed to be realized by an internal interface. + +### 5.2.3 Presence External Agent + +The Presence External Agent element shall provide the following functionality: + +- The Presence External Agent shall supply Presence information from external networks; +- The Presence External Agent shall send the Presence information across the Pex reference point according to the format standardized for the Pex reference point; +- The Presence External Agent shall handle the interworking and security issues involved in interfacing to external networks; +- The Presence External Agent shall have functionality to resolve the location of the Presence Server associated with the Presentity. + +Examples of Presence Information that the Presence External Agent may supply, include: + +- Third party services (e.g. calendar applications, corporate systems); + +- Internet Presence Services; +- Other Presence Services. + +**Editor's Note: The mapping of Pex to IMS reference points is FFS.** + +## 5.3 Presence Proxies + +### 5.3.1 Presence Proxies introduction + +In order to support a presence service, in particular across PLMN borders, generic network functions are needed, e.g. routing and security. The presence proxies provide these functions. Presence proxies constitute the entry and exit point for presence requests between PLMNs. + +### 5.3.2 Watcher Presence Proxy + +When a Watcher application intends to access some presence information of a presentity, it first needs to contact its Watcher Presence Proxy which will contact the Presentity Presence Proxy to find the Presence Server containing this information. + +The Watcher Presence Proxy shall provide the following functionality: + +- Address resolution and identification of target networks associated with a presentity; +- Authentication of watchers; +- Interworking between presence protocols for watcher requests; +- Generation of accounting information for watcher requests. + +### 5.3.3 Presentity Presence Proxy + +The Presentity Presence Proxy shall provide the following functionality: + +- Determination of the identity of the presence server associated with a particular presentity; +- Authentication of Watcher Presence Proxy; +- Authentication of the Presence user Agent; +- Generation of accounting information for updates to presence information. + +### 5.3.4 Relationship of Presence Proxies with IMS entities + +The functionalities of the Watcher Presence Proxy are then taken care of by the P-CSCF and the S-CSCF: + +- The S-CSCF is responsible for authentication according to procedures described in TS 33.203 [5]. +- The charging and accounting procedures are conducted as per procedures defined by TS 32.240 [6], TS 32.260 [7]. +- The security mechanisms between the Watcher and the Presentity Presence proxy are defined by TS 33.210 [8]. + +The functionality of the Presentity Presence Proxy is taken care of by the P-CSCF, I-CSCF and the S-CSCF as defined in TS 23.228 [9]. + +The procedures for locating, routing to and accessing the Presence Server of the presentity are defined in TS 23.228 [9] and TS 23.218 [10]. These procedures also take care of routing and accessing the Presence Server of a presentity that is associated with an unregistered UE. + +The functionality of the Watcher Presence Proxy and the Presentity Presence Proxy are allocated to the functional element CSCF as defined in TS 23.002 [18]. + +Figure 5.3.4-1 below presents the mapping of the Watcher and Presentity Presence Proxy functionalities to IMS network elements when located within the IMS along with the Watcher application. This mapping is based on and + +restricted to reusing the existing IMS architecture mechanisms and can be clearly seen in the detailed information flows show in annex A. + +![Figure 5.3.4-1: Both the Watcher application and the Presence Server located within IMS. This is a complex architectural diagram showing the flow of SIP messages within an IMS network. At the top, a 'Pet = Ut' (User Terminal) is connected to a 'Watcher application' (Pw = Gm) and an 'Application Server (Presence List)' (ISC). The 'Watcher application' sends messages to a 'P-CSCF', which routes them to an 'S-CSCF'. The 'S-CSCF' is part of a 'Watcher Presence Proxy' (dashed box) and has interfaces Pw = ISC and Pw = Mw. It connects to an 'I-CSCF', which in turn connects to an 'HSS' (Px = Cx). The 'I-CSCF' also connects to another 'S-CSCF' (Pwp = ISC), which connects to a 'Presence Server'. This second 'S-CSCF' connects to a 'P-CSCF' (Pep = Gm), which connects to a 'UE based PUA' (Pep) and a 'Network based PUA'. The 'P-CSCF' is part of a 'Presentity Presence Proxy' (dashed box).](10781f43062bf3e9601a1e086710556c_img.jpg) + +Figure 5.3.4-1: Both the Watcher application and the Presence Server located within IMS. This is a complex architectural diagram showing the flow of SIP messages within an IMS network. At the top, a 'Pet = Ut' (User Terminal) is connected to a 'Watcher application' (Pw = Gm) and an 'Application Server (Presence List)' (ISC). The 'Watcher application' sends messages to a 'P-CSCF', which routes them to an 'S-CSCF'. The 'S-CSCF' is part of a 'Watcher Presence Proxy' (dashed box) and has interfaces Pw = ISC and Pw = Mw. It connects to an 'I-CSCF', which in turn connects to an 'HSS' (Px = Cx). The 'I-CSCF' also connects to another 'S-CSCF' (Pwp = ISC), which connects to a 'Presence Server'. This second 'S-CSCF' connects to a 'P-CSCF' (Pep = Gm), which connects to a 'UE based PUA' (Pep) and a 'Network based PUA'. The 'P-CSCF' is part of a 'Presentity Presence Proxy' (dashed box). + +**Figure 5.3.4-1: Both the Watcher application and the Presence Server located within IMS** + +**NOTE:** The standard IMS (SIP) routing mechanisms define whether a certain CSCF is indeed included in the path of a SUBSCRIBE or NOTIFY transaction. + +As described in IETF RFC 3856 [4], the Watcher Application sends a SIP SUBSCRIBE to Event: presence addressed to the presentity's SIP URL to subscribe or fetch presentity's presence information. This SUBSCRIBE transaction will be routed and handled by the IMS infrastructure according to standard IMS routing and ISC procedures defined in TS 23.228 [9] and TS 23.218 [10]. + +The Presentity's S-CSCF is not mandated to insert itself into the Record-Route header of the initial SUBSCRIBE request, in case the S-CSCF does not execute any functions for the subsequent requests and responses of the dialog. + +The presence document will be provided from the Presence Server to the Watcher Application using SIP NOTIFY along the dialogue setup by SUBSCRIBE either within the NOTIFY payload, or via a URL provided in the NOTIFY. The means to fetch the content can be seen as part of the Pw interface. + +## 5.4 Watcher Applications + +### 5.4.1 Communication between Watcher and Presentity Proxy + +Communications between the Presentity Presence Proxy and the Watcher Presence Proxy shall be based on SIP as shown in figure 5.4.1-1 below. Other IP-based mechanisms may also be needed to support the delivery of large amount of presence information. Support for non-SIP based Watchers may be provided by the use of an interworking functions co-located with the Watcher Presence Proxy. In this case the Watcher Presence Proxy interworking function needs to be able to support routing to the non-SIP based watcher. + +![Diagram showing communications between Non SIP watchers (e.g. SMS, WAP, WV) and SIP/IMS watchers, a Watcher Presence Proxy, a Presentity Presence Proxy, and a Presence server. The Watcher Presence Proxy is connected to the Presentity Presence Proxy via a SIP interface, and the Presentity Presence Proxy is connected to the Presence server via a SIP interface. Both types of watchers have bidirectional communication with the Watcher Presence Proxy.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +graph LR + subgraph Watchers + direction TB + W1[Non SIP watchers +(e.g. SMS,WAP,WV)] + W2[SIP/IMS watchers] + end + W1 <--> WPP[Watcher Presence Proxy] + W2 <--> WPP + WPP -- SIP --> PPP[Presentity Presence Proxy] + PPP -- SIP --> PS[Presence server] + +``` + +Diagram showing communications between Non SIP watchers (e.g. SMS, WAP, WV) and SIP/IMS watchers, a Watcher Presence Proxy, a Presentity Presence Proxy, and a Presence server. The Watcher Presence Proxy is connected to the Presentity Presence Proxy via a SIP interface, and the Presentity Presence Proxy is connected to the Presence server via a SIP interface. Both types of watchers have bidirectional communication with the Watcher Presence Proxy. + +**Figure 5.4.1-1: Communications between the Presentity Presence Proxy and the Watcher Presence Proxy for Watchers** + +### 5.4.2 Watcher application in an IMS UE + +The Watcher application can be located within a UE registered in the IMS network, it is registered to a S-CSCF via a P-CSCF according to standard IMS procedures as specified in TS 23.228 [9]. + +Watcher application shall be able to handle full and partial notifications. The capability to process partial notifications shall be indicated to the presence server when making a presence subscription. + +The Pet reference point is implemented using the Ut reference point. + +### 5.4.3 Network based Watcher Application Server + +The Watcher application can be located within an Application Server behind the ISC reference point. This entity is the Network Based Watcher Application Server. + +Watcher application shall be able to handle full and partial notifications. The capability to process partial notifications shall be indicated to the presence server when making a presence subscription. + +### 5.4.4 Watcher application located in the external Internet + +If a Watcher application is located in the external Internet, then the Watcher Presence Proxy shall reside in a network capable of executing security functionalities as per procedures defined in TS 33.210 [8]. + +The interworking with Watcher Applications located in the external Internet not supporting the standard Pw reference point is out of the scope of the present document. + +### 5.4.5 Presence Server located in the external Internet, Watcher application located in the IMS + +If a Watcher Application is located in the IMS, the functionalities of the Watcher Presence Proxy shall be as described in clause 5.3.2. Depending on the mechanisms and protocols supported by the external Presence Server, the Watcher Presence Proxy may implement additional functionalities, e.g. protocol mapping. + +The interworking with Presence Servers located in the external Internet not supporting the standard Pw reference point is out of the scope of the present document. + +## 5.5 Presence List Server + +The Presence List Server stores grouped lists of watched presentities and enables a Watcher Application to subscribe to the presence of multiple presentities using a single SUBSCRIBE transaction. Presence List Server also stores and enables the management of filters associated to presentities in the presence list. Presence list server shall attach associated filter to each individual SUBSCRIBE transaction. The Presence List Server is implemented as a SIP Application Server function as defined in TS 23.228 [9]. For the case where the Watcher Application resides in an IMS UE, the Presence List Server may support the Ut reference point to allow the user to manage his presence lists. + +# 6 Presence attributes + +## 6.1 Presence Attributes + +Presence attributes describe the presentity. As the type of the presentity can vary significantly the definition of generic attributes is practically impossible. Attributes can be defined by the service providers and manufacturers as part of the other presence markup as specified in IETF (e.g. RFC 2778 [16], RFC 2779 [17]). The values (and process of generating them) and value ranges for all attributes shall be kept relatively simple. It is necessary for the 3GPP subscriber to understand how the values are set/modified as it may have direct impact to whom the access to presence data is given (as defined by the subscription authorisation policies). + +### 6.1.1 Subscriber Presence Attributes and Values + +A subscriber is described by attributes: *subscriber's status*, *communication means status*, *one or more communication address(es)* (containing *communication means* and *contact address*), *location* (*subscriber provided location and/or network provided location*), *priority*, *text*. The attributes can be categorised as communication means and contact address specific information or generic information. Generic information attributes shall be: *subscriber's status*, *location* and *text*. Communication means and contact address specific information attributes shall be: *communication means status*, *communication means*, *contact address*, *priority* and *text*. + +- Generic information attributes, if these attributes are used as part of any tuple they shall use following values (values in parenthesis) to enable interoperability: + - Subscriber's status (willing, willing with limitations, not willing, not disclosed), + +NOTE 1: Attribute name *subscriber's status* has been defined in stage 1 and it does not imply any mapping to the IETF defined presence model e.g. IETF RFC 2778 [16], IETF RFC 2779 [17]. + +The *subscriber's status* attribute is not intended to be used when interworking with IM clients. Subscribers are able to provide more detailed willingness information as well as other information through the generic *Text* attribute, and the communication means and contact address specific *Text* attribute. + +- Location (e.g. Last known CGI/SAI and/or geographic co-ordinates and/or free format text and timestamp), +- Text (free format text). +- Communication means and contact address specific information attributes, if these attributes are used as part of any tuple they shall use following values (values in parenthesis) to enable interoperability: + - communication means status (online, offline), + - communication means (Service type (e.g. telephony, SMS, email, multimedia messaging service, instant messaging service)), + - contact address (E.164 (e.g. MSISDN), SIP URL, Email, Instant message address e.g. IM:name@domain name), + - Priority (Priority order for each of the defined communication means and contact address), + - Text (free format text). + +NOTE 2: The mapping of these attributes and values to the IETF defined presence model IETF RFC 2778 [16], IETF RFC 2779 [17] may result one or several of the following: + +- using existing IETF defined attributes and values (or subset of them) +- using existing IETF defined attributes but extending the value set +- Creating new attributes to the tuples. + +The mapping of these values for tuples and different fields of the tuple is defined in stage 3. Furthermore, mechanisms to allow extensibility of the presence information in order to ensure interoperability are defined in stage 3. + +All these attributes shall be able to contain value NULL to enable polite blocking. + +### 6.1.2 Presence Structure to Support Multiple Values for Attributes + +Attributes shall be mapped to separate tuples which have unique identifiers. If the presentity wants to show different presence information concerning one attribute to different watchers the presentity shall create more than one tuple that contain the same attribute with different value. The association of tuples to different watchers and watcher groups shall be based on the subscription authorisation policies. The presentity controls the value of the attribute by modifying the corresponding tuple. Figure 6.1.2-1 illustrates how different values for different watchers are provided utilising subscription authorisation policies. + +NOTE: The figure 6.1.2-1 is illustrative only and it shall not mandate or limit the server implementation options. + +![Figure 6.1.2-1: Illustration how subscription authorisation lists are utilised to present different values of the same attribute to different watchers. The diagram shows two subscription authorisation lists on the left and five corresponding tuples on the right. The first list is for 'Friends' (Matt, Bob, Bryan) and includes Tuples 1, 2, and 3. The second list is for 'Public' ('All watchers') and includes Tuples 3, 4, and 5. The tuples are: Tuple 1 (Attribute 1 = value A, Attribute 2 = value B), Tuple 2 (Attribute 3 = value C, Attribute 4 = value B), Tuple 3 (Attribute 5 = value D, Attribute 6 = value E), Tuple 4 (Attribute 1 = value E, Attribute 2 = value F), and Tuple 5 (Attribute 3 = value C, Attribute 7 = value G).](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +**Subscription authorisation list** +**"Friends":** + Matt + Bob + Bryan +**Tuples:** + Tuple 1 + Tuple 2 + Tuple 3 + +**Subscription authorisation list** +**"Public":** + 'All watchers' +**Tuples:** + Tuple 3 + Tuple 4 + Tuple 5 + +**Tuple 1:** + Attribute 1 = value A + Attribute 2 = value B + +**Tuple 2:** + Attribute 3 = value C + Attribute 4 = value B + +**Tuple 3:** + Attribute 5 = value D + Attribute 6 = value E + +**Tuple 4:** + Attribute 1 = value E + Attribute 2 = value F + +**Tuple 5:** + Attribute 3 = value C + Attribute 7 = value G + +Figure 6.1.2-1: Illustration how subscription authorisation lists are utilised to present different values of the same attribute to different watchers. The diagram shows two subscription authorisation lists on the left and five corresponding tuples on the right. The first list is for 'Friends' (Matt, Bob, Bryan) and includes Tuples 1, 2, and 3. The second list is for 'Public' ('All watchers') and includes Tuples 3, 4, and 5. The tuples are: Tuple 1 (Attribute 1 = value A, Attribute 2 = value B), Tuple 2 (Attribute 3 = value C, Attribute 4 = value B), Tuple 3 (Attribute 5 = value D, Attribute 6 = value E), Tuple 4 (Attribute 1 = value E, Attribute 2 = value F), and Tuple 5 (Attribute 3 = value C, Attribute 7 = value G). + +**Figure 6.1.2-1: Illustration how subscription authorisation lists are utilised to present different values of the same attribute to different watchers** + +## 6.2 Presence Information Model + +Presence information related to a particular communications means and contact address shall be carried in a presence tuple dedicated to that particular communications means and contact address. + +Generic presence information that is not directly applicable to a particular communications means and contact address shall be conveyed in a way that conforms to the IETF presence model e.g. IETF RFC 2778 [16], IETF RFC 2779 [17] (to ensure interoperability) and preferably does not require multiple instances of this information to be sent. + +Generic information may be mapped to the tuples specific to each communication means and contact address. In that case the information shall be equal in each tuple. The stage 3 description should use a mechanism which conforms to the IETF presence model. + +Application identifiers may be allocated to applications, which are using presence capabilities. The conventions and the allocation mechanism for application identifiers are subject to stage 3 specification. Application identifier(s) are carried as part of the presence information. Application identifier(s) may be added to published presence information on the presentity side. In this case, the presence server shall include this application identifier to the relevant tuple(s) in the presence document together with the published information. On the watcher side the received application identifier may be used e.g. for determining which application should receive and process the related presence information. Details of processing the application identifier(s) on the Presence User Agent and watcher side are out of scope of this specification. + +# 7 Subscription authorisation policies + +Subscription authorisation policies shall define the watchers who can access the presence information of the presentity. In addition to the watcher identities, the subscription authorisation policies shall contain the presence information or + +reference to the presence information that is allowed to be accessed by the listed watchers. The subscription authorisation lists can be logically arranged to be part of the presence server or a separate entity in the network. + +In case of presence information fetch or subscription from a watcher that has not been authorised by the subscription authorisation policies, the presence server shall put the fetch or subscription on hold until the watcher has been authorised, added to the subscription authorisation lists or until a preconfigured timer has expired. + +Subscription authorisation lists can be divided into three different categories: personal subscription authorisation lists, public subscription authorisation lists and blocking subscription authorisation lists. + +Personal and general subscription authorisation lists shall define which watchers can access which information. Personal subscription authorisation lists shall explicitly identify watchers, while general subscription authorisation lists relate to groups of watchers whose exact identities are not necessarily known by the presentity e.g. "all watchers". + +Blocking subscription authorisation lists shall define watchers that are not allowed to access any presence information related to the presentity. + +A presentity shall be able to manage several personal and general subscription authorisation lists as well as blocking subscription authorisation lists. + +The three subscription authorisation list categories shall be evaluated in the following order: blocking subscription authorisation lists, personal subscription authorisation lists and general subscription authorisation lists. + +The following shows an example where the presentity has defined a single subscription authorisation list for each category. + +In this particular example, once the hit is found the evaluation is halted and presence information according to access is delivered. + +1. Is the watcher on the blocking subscription authorisation list? +2. Is the watcher on the personal subscription authorisation list? +3. Is the watcher on the general subscription authorisation list (created e.g. by service provider containing all watchers)? +4. Send a notification to the presentity of pending subscription authorisation request. + +![Flowchart illustrating the subscription authorisation list evaluation order for presence service. The process starts with 'Presence subscription or fetch', which leads to 'On block subscription authorisation list'. If 'Yes', the result is 'No data available'. If 'No', it leads to 'On personal subscription authorisation list'. If 'Yes', the result is 'Access tuples related to that list'. If 'No', it leads to 'On general subscription authorisation list'. If 'Yes', the result is 'Access tuples related to that list'. If 'No', the result is 'Possible notification or without notification to the presentity of pending subscription'.](bd57a547bec253d4179e5c4491c53dbb_img.jpg) + +``` + +graph LR + A[Presence subscription or fetch] --> B[On block subscription authorisation list] + B -- Yes --> B1[No data available] + B -- No --> C[On personal subscription authorisation list] + C -- Yes --> C1[Access tuples related to that list] + C -- No --> D[On general subscription authorisation list] + D -- Yes --> D1[Access tuples related to that list] + D -- No --> E[Possible notification or without notification to the presentity of pending subscription] + +``` + +Flowchart illustrating the subscription authorisation list evaluation order for presence service. The process starts with 'Presence subscription or fetch', which leads to 'On block subscription authorisation list'. If 'Yes', the result is 'No data available'. If 'No', it leads to 'On personal subscription authorisation list'. If 'Yes', the result is 'Access tuples related to that list'. If 'No', it leads to 'On general subscription authorisation list'. If 'Yes', the result is 'Access tuples related to that list'. If 'No', the result is 'Possible notification or without notification to the presentity of pending subscription'. + +**Figure 7-1: Example of subscription authorisation list evaluation order for presence service** + +# 8 Charging requirement + +The following charging requirement for presence service is identified. The requirements shall be realized by enhancements of the IMS charging mechanism as specified in TS 32.240 [6] and TS 32.260 [7]. + +- 1) Watcher Presence Proxy shall be able to provide the charging information for watcher requests per watcher for presence enquiry or subscription and subsequent notifications. +- 2) Presentity Proxy shall be able to provide the charging information for updates to presence information per watcher. +- 3) The Presence Server shall be able to provide the charging information for notifying the watcher of updates to presence information. Presence Server shall be able to provide the charging information for subscription to + +Watcher Lists and receiving notification of Watcher Information. Presence Server shall be able to provide the charging information for collecting the record of watcher list information per presentity. The Presence Server shall be able to provide the charging information for publishing presence information per presentity. + +- 4) Presence List Server shall be able to provide the charging information for Watcher subscription to Presence Lists and receiving notification of Presence Information. +- 5) It shall be possible to apply specific tariffs (e.g. zero rating) to the bearer and/or signalling traffic associated with the above presence service "events". Differentiating in the IP Connectivity access network between the signalling traffic related to presence events and signalling traffic related to other IMS SIP communications is not a requirement. + +# Annex A (informative): Information flows + +## A.1 General information flow + +Figure A.1-1 illustrates the message flow for user A requesting presence information for user B in a different network. + +![Sequence diagram illustrating the presence enquiry message flow between two networks, A and B. The diagram shows the interaction between User A, Watcher Application A (WA-A), Watcher Presence Proxy, Presentity Presence Proxy, PS-B, and HLR/HSS. The flow starts with A sending a presence enquiry for B to WA-A, which then authenticates and checks credit status. WA-A sends a presence enquiry for B to the Watcher Presence Proxy, which derives B's network name and sends a presence enquiry for B to the Presentity Presence Proxy. The Presentity Presence Proxy derives the address of B's presence server and sends a presence enquiry for B to PS-B. PS-B sends a response to the Presentity Presence Proxy, which then sends the B party status to the Watcher Presence Proxy and the IPP. The Watcher Presence Proxy sends the B party status to WA-A, which finally sends the B's presence status to A.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +``` + +sequenceDiagram + participant A + participant WA-A as WA - A + participant WPP as Watcher Presence Proxy + participant PPP as Presentity Presence Proxy + participant PS-B + participant HLR/HSS + + Note left of A: A Party Network + Note right of HLR/HSS: B Party Network + + A->>WA-A: 1. Presence enquiry for B + WA-A-->>WA-A: 2. + WA-A->>WPP: 3. Presence enquiry for B + WPP-->>WPP: 4. + WPP->>PPP: 5. Presence enquiry for B + PPP->>HLR/HSS: 6. Presentity Presence Proxy derives address of B's presence + HLR/HSS-->>PPP: 7. Presence enquiry for B + PPP->>PS-B: 8, 9 + PS-B-->>PPP: 10a. B party status sent to IPP + PPP-->>WPP: 10b. B party status sent to Watcher Presence Proxy + WPP-->>WA-A: 10c. B party status sent to WA-A + WA-A-->>A: 11. B's presence status to A + +``` + +Sequence diagram illustrating the presence enquiry message flow between two networks, A and B. The diagram shows the interaction between User A, Watcher Application A (WA-A), Watcher Presence Proxy, Presentity Presence Proxy, PS-B, and HLR/HSS. The flow starts with A sending a presence enquiry for B to WA-A, which then authenticates and checks credit status. WA-A sends a presence enquiry for B to the Watcher Presence Proxy, which derives B's network name and sends a presence enquiry for B to the Presentity Presence Proxy. The Presentity Presence Proxy derives the address of B's presence server and sends a presence enquiry for B to PS-B. PS-B sends a response to the Presentity Presence Proxy, which then sends the B party status to the Watcher Presence Proxy and the IPP. The Watcher Presence Proxy sends the B party status to WA-A, which finally sends the B's presence status to A. + +**Figure A.1-1: Presence enquiry message flow** + +- The A party sends a presence enquiry to Watcher Application A (WA-A). The A party identifies B by B's address (e.g. MSISDN or URI). The enquiry can be of various types, e.g.: + - "tell me the current state of B" + - "tell me all state changes of user B for the next x hours" + - "tell me when B next changes state" + - "stop telling me about B" + - Watcher Application A 'authenticates' A and checks their credit status (details of authentication and credit status are outside scope of this message flow) + - Watcher Application A sends a "Presence enquiry for B" message to Watcher Presence Proxy. + - The Watcher Presence Proxy derives B's network name from B's address (details of how this is derived is outside the scope of this message flow). + - The Watcher Presence Proxy sends a "Presence enquiry for B" message to B's network's Presentity Presence Proxy. +- NOTE: Authentication may be necessary between A and B party networks in line with techniques used in other instances of inter operator message flow; precise details are outside the scope of this message flow. +- The Presentity Presence Proxy derives the address of B's Presence Server + - B's network Presentity Presence Proxy sends "Presence enquiry for B" message to B's Presence Server. + +8. B's Presence Server processes the presence enquiry request (e.g. check A is one of B's buddy's and B still wants A to watch him/her). +9. B's Presence Server raises charge record for A against A's network (precise details are for further study) +10. B's Presence Server sends B's status back to Watcher Application A in Originating PLMN (may be returned via Presentity Presence Proxy and Watcher Presence Proxy). +11. Watcher application returns B's presence to use A. + +NOTE 1: Steps 10 and 11 are repeated as necessary if B party has been requested to provide regular presence updates. + +NOTE 2: In the event that the presence enquiry message is "stop telling me about B" steps 8-11 are just an acknowledgement for watcher application A. + +## --- A.2 Detailed information flows + +### A.2.1 Overview of flows used + +The messages used in this clause are representative and are not meant to indicate any particular protocol as this is outside the scope of this document. In this clause the following messages have been used: + +*SubscribePres*: This is a request by a watcher to obtain presence information about a presentity. The message may be used to either request the current presence information or to subscribe to updates of presence information for a particular time period. This flow may also be used to un-subscribe to periodic updates. The request needs to convey the presence related events that that the watcher is interested in. A presence server may accept or deny such a request. + +*MsgAck*: This is a generic message acknowledgement for the message flows. It may be used to indicate a positive or negative acknowledgement. In the latter case, the message may convey an indication for the rejection. + +*Query*: This message is used by a Presentity presence proxy to request the HSS/HLR to provide the necessary information to locate a presence server that is associated with a presentity. + +*Resp*: This message is the reply by the HSS/HLR to provide the required information to the Query message above. + +*NotifyPresUp*: This message is used to notify a watcher of updates to a presentity's presence information. The watcher would have either requested the current presence information or had previously subscribed to periodic updates. The message may contain the presence information or a pointer to the information. + +*PresUpdateMsg*: This message is used by a Presence user agent, the Network agent, and the External agent to provide the presentity's presence information to the Presence Server. This message shall be capable of conveying the complete set of presence information associated with a presentity. This message shall also be capable of conveying a subset of the presence information associated with the presentity, to provide updates of a presentity's presence information to a presence server. This message needs to be able to convey the presence information associated with a presentity. The message may contain the presence information or a pointer to the information. (Note: there are similarities with the *NotifyPresUp* message listed above since they both convey presence information. However for simplicity, different message names are used). + +### A.2.2 Flows demonstrating how watchers subscribe to presence event notification + +The clause covers the flows that show how watchers can request presence information about a presentity. + +#### A.2.2.1 IMS Watcher and IMS Presentity in the same or different IM-CN + +![Sequence diagram showing the IMS Watcher registering for event notification. The diagram is split into two main sections: 'Home Network of watcher' and 'Home Network of presentity'. On the watcher's side, a UE sends a SubscribePres message to a Watcher Presence Proxy (containing P-CSCF and S-CSCF). The P-CSCF forwards it to the S-CSCF, which then forwards it to the I-CSCF in the presentity's network. The I-CSCF queries the HSS, receives a response, and forwards the SubscribePres to the Presence Server. The Presence Server returns a MsgAck, which is passed back through the I-CSCF, S-CSCF, and P-CSCF to the UE. The UE responds with a MsgAck. The Presence Server also sends a NotifyPresUp message to the S-CSCF, which is then passed to the P-CSCF and finally to the UE. The UE responds with another MsgAck.](088921fa3f5a44c8551815122517eefd_img.jpg) + +``` + +sequenceDiagram + participant UE + subgraph Home_Network_of_watcher [Home Network of watcher] + WPP[Watcher Presence Proxy: P-CSCF, S-CSCF] + end + subgraph Home_Network_of_presentity [Home Network of presentity] + PP[Presentity Presence Proxy: I-CSCF, S-CSCF] + end + participant HSS + participant PS[Presence Server] + + UE->>WPP: 1. SubscribePres + WPP->>PP: 3. SubscribePres + PP->>HSS: 4. Query + HSS-->>PP: 5. Resp + PP->>PS: 7. SubscribePres + PS-->>PP: 8. MsgAck + PP-->>WPP: 10. MsgAck + WPP-->>UE: 12. MsgAck + UE-->>WPP: 16. MsgAck + PS-->>PP: 13. NotifyPresUp + PP-->>WPP: 14. NotifyPresUp + WPP-->>UE: 15. NotifyPresUp + UE-->>WPP: 17. MsgAck + WPP-->>PS: 18. MsgAck + +``` + +Sequence diagram showing the IMS Watcher registering for event notification. The diagram is split into two main sections: 'Home Network of watcher' and 'Home Network of presentity'. On the watcher's side, a UE sends a SubscribePres message to a Watcher Presence Proxy (containing P-CSCF and S-CSCF). The P-CSCF forwards it to the S-CSCF, which then forwards it to the I-CSCF in the presentity's network. The I-CSCF queries the HSS, receives a response, and forwards the SubscribePres to the Presence Server. The Presence Server returns a MsgAck, which is passed back through the I-CSCF, S-CSCF, and P-CSCF to the UE. The UE responds with a MsgAck. The Presence Server also sends a NotifyPresUp message to the S-CSCF, which is then passed to the P-CSCF and finally to the UE. The UE responds with another MsgAck. + +Figure A.2.2.1-1: IMS Watcher registering for event notification + +Figure A.2.2.1-1 shows an IMS watcher subscribing to presence event notification about an IMS based presentity. The presentity may either be in the same IM-CN subsystem as the watcher or may be in a different IM-CN subsystem. The flows for both these cases are the same. + +*Note-i: The path of the SUBSCRIBE dialog may optionally include additional I-CSCF(THIGs) in networks where network topology hiding is applied.* + +*Note-ii: The flow shows the case that the S-CSCF of the Presentity does not remain in the path of the dialog.* + +The details of the flows as follows: + +1. A watcher agent in a UE wishes to watch a presentity's presence information, or certain parts of the presentity's presence information (defined by the filters included in *SubscribePres*). To initiate a subscription, the UE sends a *SubscribePres* message request containing the presence related events that it wishes to be notified of, together with an indication of the length of time this periodic subscription should last. The UE sends the *SubscribePres* information flow to the proxy (subscriber identity, home networks domain name). The *SubscribePres* may also include an indication of the watcher's capability to handle partial notifications. +2. The P-CSCF remembers (from the registration process) the next hop CSCF for this UE. In this case the *SubscribePres* is forwarded to the S-CSCF in the home network. In this case, the P-CSCF and the S-CSCF act as a Watcher Presence Proxy. +3. The S-CSCF is unable to resolve the presence server address of the presentity that the UE is requesting to watch, and as a result forwards the *SubscribePres* message to the an I-CSCF offering part of the Presentity Presence Proxy functionality. The S-CSCF shall examine the home domain of the presentity associated with the request and if the request is for a presentity outside the operator's domain, it determines the external I-CSCF. If the request is for a presentity in the same domain, the S-CSCF forwards the request to the local I-CSCF. + +4. The I-CSCF examines the presentity identity and the home domain identity and employs the services of a name-address resolution mechanism to determine the HSS address to contact. The I-CSCF shall query the HSS to obtain the address of the S-CSCF associated with the Presentity. It shall query the HSS via a Query message. + 5. The Query Resp message from the HSS provides the name of the S-CSCF associated with the presentity. + 6. The I-CSCF, using name of the Presence Server shall determine the address of the S-CSCF through a name-address resolution mechanism. The *SubscribePres* message is forwarded to the S-CSCF. + 7. The S-CSCF using any necessary filtering criteria forwards the *SubscribePres* message to the appropriate Presence Server. + 8. At this stage the presence server performs the necessary authorisation checks on the originator to ensure it is allowed to watch the presentity. Once all privacy conditions are met, the presence server issues a *MsgAck* to the S-CSCF. (In the case where the privacy/authorisation checks fail, then a negative acknowledgement is sent to the watcher). + 9. The S-CSCF forwards the to the I-CSCF. + 10. The I-CSCF forwards the *MsgAck* to the originating S-CSCF. + 11. The S-CSCF forwards the *MsgAck* message to the P-CSCF. + 12. The P-CSCF forwards the *MsgAck* to the watcher agent in the UE. + 13. As soon as the Presence Server sends a *MsgAck* to accept the subscription, it sends a *NotifyPresUp* message with the current full state of the presentity's tuples that the watcher has subscribed and been authorised to. The *NotifyPresUp* is sent along the path of the SUBSCRIBE dialog to the S-CSCF allocated to the Watcher. Further notifications sent by the Presence server may either contain the complete set of presence information, or only those tuples that have changed since the last notification if the watcher has indicated the capability to process partial notifications. +- NOTE: If charging for updates to presence information per watcher is enabled, then the presentity presence proxy will remain in the SUBSCRIBE dialogue path and the *NotifyPresUp* is routed through the presentity presence proxy. The presentity presence proxy (S-CSCF) will provide the charging update. +14. The S-CSCF forwards the *NotifyPresUp* to the P-CSCF. + 15. The P-CSCF forwards the *NotifyPresUp* to the watcher application in the UE. + 16. The UE acknowledges the receipt of the *NotifyPresUp* message with a *MsgAck* sending this to the P-CSCF. + 17. The P-CSCF forwards the *MsgAck* message to the S-CSCF. + 18. The S-CSCF allocated to the presentity forwards the *MsgAck* to the Presence Server. + +### A.2.3 Flows demonstrating how presentities update Presence Information + +#### A.2.3.1 Updating presence information by terminals without support of the Pep reference point + +For the case of terminals that do not support the Pep reference point presence information can be provided alternative mechanisms such as SMS, WAP etc. The Presence User Agent provides the necessary interworking with the presence server. As previously indicated, the PUA may be located with network entities such as a WAP WML/HTTP server or SMS-C, however this is an implementation issue and outside of the scope of technical report. This particular example is illustrative and shows the case where a user updates presence information through a WAP browser, where the Presence User Agent is located inside the WAP WML/HTTP server and is illustrated in figure A.2.3.1-1 below. It is acknowledged that other possibilities exist. + +![Sequence diagram for updating presence information via WAP WML/HTTP server. Lifelines: UE, WML/HTTP Server (containing Presence User Agent), and Presence Server. The sequence shows: 1. WAP session establishment between UE and WML/HTTP Server; 2. Update Presence Information from UE to WML/HTTP Server; 3. PresUpdateMsg [Presence Info] from WML/HTTP Server to Presence Server; 4. MsgAck from Presence Server to WML/HTTP Server. A note indicates the Presence server updates all authorised watchers with new presence information, with separate flows.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant WML/HTTP Server as WML/HTTP Server (Presence User Agent) + participant Presence Server + Note right of Presence Server: Presence server updates all authorised watchers with new presence information +See separate flows + + UE->>WML/HTTP Server: 1. WAP session establishment + WML/HTTP Server-->>UE: + UE->>WML/HTTP Server: 2. Update Presence Information + WML/HTTP Server->>Presence Server: 3. PresUpdateMsg [Presence Info] + Presence Server-->>WML/HTTP Server: 4. MsgAck + +``` + +Sequence diagram for updating presence information via WAP WML/HTTP server. Lifelines: UE, WML/HTTP Server (containing Presence User Agent), and Presence Server. The sequence shows: 1. WAP session establishment between UE and WML/HTTP Server; 2. Update Presence Information from UE to WML/HTTP Server; 3. PresUpdateMsg [Presence Info] from WML/HTTP Server to Presence Server; 4. MsgAck from Presence Server to WML/HTTP Server. A note indicates the Presence server updates all authorised watchers with new presence information, with separate flows. + +**Figure A.2.3.1-1: Updating presence information via WAP WML/HTTP server** + +1. The user opens a WAP session by requesting a WAP URL that is dedicated to updates of presence information. +2. Using a WAP browser, the user modifies aspects of 'user presence information'. +3. The WML/HTML server, which in this example hosts the Presence User Agent (although the PUA may be a separate entity, in which case the interface to the PUA will be proprietary), sends a PresUpdateMsg to the Presence Server. Additional functionality may be required to locate the presence server associated by the presentity. In this particular example, it is assumed that the PUA is configured with the appropriate address of the presence server. +4. The Presence Server acknowledges the PresUpdateMag with a MsgAck to the WAP WML/HTTP server. + +#### A.2.3.2 IMS Registration Notification process to the Presence Server within IMS + +The following flow describes how the presence server is notified of an IMS registration event by the network elements. + +![Sequence diagram for IMS Registration Notification procedure for the Presence Server. Lifelines: UE, HSS, S-CSCF, and a dashed box containing Presence Network Agent and Presence Server. The sequence shows: 1. Registration Process between UE and S-CSCF; 2. Filter Criteria download from HSS to S-CSCF; 3. Registration between S-CSCF and Presence Network Agent; 4. IMS Registration Event Notification from Presence Network Agent to Presence Server. A note indicates the Presence server updates all authorised watchers with new presence information, with separate flows.](f2ea0f64a770b22b902820457d262265_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HSS + participant S-CSCF + subgraph Presence Domain [ ] + participant Presence Network Agent + participant Presence Server + end + Note right of Presence Server: Presence server updates all authorised watchers with new presence information +See separate flows + + UE->>S-CSCF: 1. Registration Process + S-CSCF-->>UE: + HSS->>S-CSCF: Filter Criteria download + S-CSCF->>Presence Network Agent: 2. Registration + Presence Network Agent-->>S-CSCF: + Presence Network Agent->>Presence Server: 3. IMS Registration Event Notification + +``` + +Sequence diagram for IMS Registration Notification procedure for the Presence Server. Lifelines: UE, HSS, S-CSCF, and a dashed box containing Presence Network Agent and Presence Server. The sequence shows: 1. Registration Process between UE and S-CSCF; 2. Filter Criteria download from HSS to S-CSCF; 3. Registration between S-CSCF and Presence Network Agent; 4. IMS Registration Event Notification from Presence Network Agent to Presence Server. A note indicates the Presence server updates all authorised watchers with new presence information, with separate flows. + +**Figure A.2.3.2-1: IMS Registration Notification procedure for the Presence Server** + +1. UE registration takes place with the S-CSCF as detailed in TS 23.228 [9]. As part of this process, the filtering criteria are downloaded to the S-CSCF from the HSS. The filter criteria contains instructions that the registration be sent to the presence network agent (e.g. registration, de-registration). + +2. The S-CSCF sends the registration to the Presence Network Agent via the ISC interface. +3. When the Presence Network Agent receives the notification of the IMS registration event from the S-CSCF, it determines that this registration is an event that the Presence Server is interested in and informs the Presence Server. + +#### A.2.3.3 CS/PS Notification process of the Presence Server + +The following flow describes how the presence server is notified of an event by the network elements for a CS/PS subscriber. + +![Sequence diagram of CS/PS Notification procedure for the Presence Server](6470d350326789d5306eabcb76533951_img.jpg) + +The diagram illustrates the notification process between five entities: UE, HLR, MSC/SGSN, Network Agent, and Presence Server. The sequence of events is as follows: + +- 1. Off line trigger set-up:** A message is sent from the HLR to the MSC/SGSN. +- 2. Event Occurence:** An event occurs between the HLR and the MSC/SGSN. +- 3. NOTE\_MM\_EVENT:** The MSC/SGSN sends a notification message to the Network Agent. +- 4. Information Exchange:** The Network Agent and the Presence Server exchange information. A note indicates that the Presence server updates all authorised watchers with new presence information and refers to separate flows. +- 5. MM\_Event\_Ack:** The Network Agent sends an acknowledgment message back to the MSC/SGSN. + +Sequence diagram of CS/PS Notification procedure for the Presence Server + +**Figure A.2.3.3-1: CS/PS Notification procedure for the Presence Server** + +1. For network event to be reported on behalf of a CS/PS subscriber, the necessary triggers are armed in the MSC/SGSN. This takes place off-line and is outside the scope of this TS as to how it is achieved. +2. At the occurrence of an event between the HLR and the MSC/SGSN, (e.g. UE detach) a notification message is generated. +3. A MAP notification message (NOTE\_MM\_EVENT) is sent to the Network Agent via Pc/Pg interface on the occurrence of an event, details of this are outside the scope of this flow. There may be some address resolution needed by the network agent to locate the presence server but details of this is also outside the scope of this flow. +4. The Network Agent informs the Presence Server. The Presence Server notifies all authorised watchers and sends an acknowledgement to the Network Agent. +5. Network Agent sends an MM\_Event\_Ack to the MSC/SGSN. + +#### A.2.3.4 Updating presence information by terminals with Pep interface support + +![Sequence diagram showing the interaction for updating presence information via the Pep interface. The diagram is titled 'Home Network of presentity' and involves four lifelines: UE, P-CSCF, S-CSCF, and Presence Server. The sequence of messages is: 1. PressUpdateMsg from UE to P-CSCF; 2. PressUpdateMsg from P-CSCF to S-CSCF; 3. PressUpdateMsg from S-CSCF to Presence Server; 4. MsgAck from Presence Server to S-CSCF; 5. MsgAck from S-CSCF to P-CSCF; 6. MsgAck from P-CSCF to UE.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +``` +sequenceDiagram + participant UE + participant P-CSCF + participant S-CSCF + participant PS as Presence Server + Note over all: Home Network of presentity + UE->>P-CSCF: 1. PressUpdateMsg + P-CSCF->>S-CSCF: 2. PressUpdateMsg + S-CSCF->>PS: 3. PressUpdateMsg + PS-->>S-CSCF: 4. MsgAck + S-CSCF-->>P-CSCF: 5. MsgAck + P-CSCF-->>UE: 6. MsgAck +``` + +Sequence diagram showing the interaction for updating presence information via the Pep interface. The diagram is titled 'Home Network of presentity' and involves four lifelines: UE, P-CSCF, S-CSCF, and Presence Server. The sequence of messages is: 1. PressUpdateMsg from UE to P-CSCF; 2. PressUpdateMsg from P-CSCF to S-CSCF; 3. PressUpdateMsg from S-CSCF to Presence Server; 4. MsgAck from Presence Server to S-CSCF; 5. MsgAck from S-CSCF to P-CSCF; 6. MsgAck from P-CSCF to UE. + +**Figure A.2.3.4-1: Updating presence information via the Pep interface** + +1. The PUA residing in the UE generates a *PressUpdateMsg* message which contains the new presence information. The means for the PUA to compose this presence information is outside the scope of this specification. +2. P-CSCF forwards the message to the user's S-CSCF. +3. S-CSCF forwards message to the correct Presence Server based on ISC filtering rules. +4. Presence Server authorizes the presence update, and checks what information the message contains. The Presence Server then processes the updated presence information according to the client's request. The Presence Server sends a *MsgAck* response back to UE. +5. S-CSCF forwards the response back to the P-CSCF +6. P-CSCF forwards the response back to the UE. + +### A.2.4 Presence Server notifying watcher of updates to presence information + +#### A.2.4.1 IMS based Watcher and presentity in the same or different IM-CN subsystem + +![Sequence diagram showing the interaction between a Presence Server and a Watcher (UE) via various network elements (S-CSCF, I-CSCF, P-CSCF).](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +The diagram illustrates the sequence of messages for updating an IMS watcher's presence information. It is divided into two main network domains: 'Home Network of Presentity' and 'Home Network of Watcher'. + +- Home Network of Presentity:** Contains a **Presence Server** and a **Presentity Presence Proxy** (which includes an **S-CSCF**). +- Home Network of Watcher:** Contains a **Watcher Presence Proxy** (which includes an **I-CSCF** and an **S-CSCF**), a **P-CSCF**, and a **UE** (User Equipment). + +The sequence of messages is as follows: + +- The **Presence Server** sends a **1. NotifyPresUp** message to the **S-CSCF** in the **Presentity Presence Proxy**. +- The **S-CSCF** in the **Presentity Presence Proxy** forwards the message to the **S-CSCF** in the **Watcher Presence Proxy**. +- The **S-CSCF** in the **Watcher Presence Proxy** forwards the message to the **P-CSCF**. +- The **P-CSCF** forwards the message to the **UE**. +- The **UE** sends a **4. MsgAck** message back to the **P-CSCF**. +- The **P-CSCF** forwards the **MsgAck** message to the **S-CSCF** in the **Watcher Presence Proxy**. +- The **S-CSCF** in the **Watcher Presence Proxy** forwards the **MsgAck** message to the **Presence Server**. + +Sequence diagram showing the interaction between a Presence Server and a Watcher (UE) via various network elements (S-CSCF, I-CSCF, P-CSCF). + +**Figure A.2.4.1-1: Presence Server updating IMS watcher** + +Figure A.2.4.1-1 shows how an IMS based watcher is notified of updates to a presentity's presence information. The flows are applicable to the case where the Watcher and Presentity are in the same or in different IM-CN subsystems. + +*Note-i: The path of the SUBSCRIBE dialog (i.e. also the NOTIFY transaction) may optionally include additional I-CSCF(THIGs) in networks where network topology hiding is applied.* + +*Note-ii: The flow shows the case that the S-CSCF of the Presentity does not remain in the path of the dialog.* + +Details of the flows are as follows: + +1. The Presence Server determines which authorised watchers are entitled to receive the updates of the presence information for this presentity. For each appropriate watcher, the presence server sends a *NotifyPresUp* message that contains the full or partial updates to the presence information. This *NotifyPresUp* is sent along the path of the SUBSCRIBE dialog to the S-CSCF of the Watcher. +2. The S-CSCF forwards the *NotifyPresUp* message to the P-CSCF of the watcher. +3. The P-CSCF forwards the *NotifyPresUp* message to the UE. +4. The UE acknowledges the *NotifyPresUp* message with a *MsgAck* to the P-CSCF. +5. The P-CSCF forwards the *MsgAck* message to the S-CSCF. +6. The S-CSCF of the Watcher forwards the *MsgAck* to the Presence Server. + +### A.2.5 Presence User Agent subscribing to watcher list and receiving notification of a new watcher subscription + +![Sequence diagram showing the interaction between a Presence User Agent, Presence Server, Presentity Presence Proxy, and Watcher Presence Proxy for a new watcher subscription.](3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg) + +``` + +sequenceDiagram + participant PUA as Presence User Agent + participant PS as Presence Server + participant PPP as Presentity Presence Proxy + participant WP as Watcher Presence Proxy + + Note left of PUA: 1. SubscribePresence (Watcher List) + PUA->>PS: 1. SubscribePresence (Watcher List) + Note right of PS: 2. MsgAcks + PS-->>PUA: 2. MsgAcks + Note right of WP: 3. SubscribePres + WP->>PPP: 3. SubscribePres + Note right of PPP: 4. SubscribePres + PPP->>PS: 4. SubscribePres + Note left of PS: 5.. Watcher Request Notification + PS-->>PUA: 5.. Watcher Request Notification + Note right of PS: 6. MsgAck + PS->>PPP: 6. MsgAck + Note right of PPP: 7. MsgAck + PPP->>WP: 7. MsgAck + Note left of PUA: 8. UpdateSubscriptionAuthorisationPolicies + PUA->>PS: 8. UpdateSubscriptionAuthorisationPolicies + Note right of PS: 9. NotifyPresUp + PS->>PPP: 9. NotifyPresUp + Note right of PPP: 10. NotifyPresUp + PPP->>WP: 10. NotifyPresUp + +``` + +Sequence diagram showing the interaction between a Presence User Agent, Presence Server, Presentity Presence Proxy, and Watcher Presence Proxy for a new watcher subscription. + +**Figure A.2.5-1: Presence User Agent subscribing to watcher list and receiving notification of a new watcher subscription** + +Figure A.2.5-1 shows a Presence User Agent subscribing to watcher list and receiving notification of a new watcher subscription that is not contained in the current subscription authorisation policies. The details of the flows are as follows: + +- 1) The Presence User Agent initiates a subscription to the Presence Server requesting notification of any new watcher subscriptions. +- 2) The presence server issues a *MsgAck* to the Presence User Agent. +- 3) A watcher wishes to watch the Presentity. To initiate a subscription, the watcher sends a *SubscribePres* request containing the presence related events that it wishes to be notified of, together with an indication of the length of time this periodic subscription should last to the Watcher Presence Proxy. The Watcher Presence Proxy sends the *SubscribePres* information flow to the Presentity Presence Proxy. +- 4) The *SubscribePres* is forwarded by the Presentity Presence Proxy to the Presence Server. +- 5) The Presence Server checks the subscription authorisation policies and determines that this is a new watcher subscription not contained in the current subscription authorisation policies and so sends a notification to inform the Presence User Agent of the request from the new watcher. +- 6) The presence server issues a *MsgAck* to inform the watcher that the Presence Server has received the watcher's request for Presence information. The *MsgAck* is sent to the Presentity Presence Proxy. +- 7) The *MsgAck* is forwarded by the Presentity Presence Proxy to the watcher via the Watcher Presence Proxy. + +Steps 8 – 10 depend on the actions of the Principal. The Principal can ignore the notification sent in step 5 or can respond with an Update of the subscription authorisation policies to Accept, Accept with conditions or Deny the request. + +- 8) The Presence User Agent sends an *UpdateSubscriptionAuthorisationPolicies* to the Presence Server. (If the Presence User Agent decides to accept, block or accept with conditions the Presence Information requested by the watcher an appropriate *SubscriptionAccepted*, *SubscriptionBlocked* or *SubscriptionAcceptedWithConditions* is sent within the *UpdateSubscriptionAuthorisationPolicies* to the Presence Server). + +- 9) If the *UpdateSubscriptionAuthorisationPolicies* accepts the subscription then the Presence Server sends a *NotifyPresUp* message with the current state of the Presence User Agent to the Presentity Presence Proxy. If the *UpdateSubscriptionAuthorisationPolicies* indicates that the subscription is blocked then steps 9 and 10 are not performed. +- 10) The Presentity Presence Proxy forwards the *NotifyPresUp* message to the watcher via the Watcher Presence Proxy. + +# --- Annex B (Informative): Void + +# Annex C (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|------|-----|-----|----------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 2005-12 | SA#30 | SP-050665 | 0080 | 1 | A | Correction of some references to release 6 replacements | 7.0.0 | 7.1.0 | +| 2006-09 | SA#33 | SP-060582 | 0081 | 1 | F | Miscellaneous Corrections to Presence Specification | 7.1.0 | 7.2.0 | +| 2007-09 | SA#37 | SP-070532 | 0083 | - | A | Removal of obsolete reference and editor's note | 7.2.0 | 7.3.0 | +| 2008-03 | SA#39 | SP-080104 | 0773 | 2 | B | Update to the Presence Spec in support of the Common IMS | 7.3.0 | 8.0.0 | +| 2008-06 | SA#40 | SP-080363 | 0084 | 1 | F | Correction to Presence (Stage 2) for Common IMS | 8.0.0 | 8.1.0 | +| 2009-12 | SA#46 | - | - | - | - | Upgrade to Rel-9 version (MCC) | 8.1.0 | 9.0.0 | +| 2011-03 | SA#51 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | <b>11.0.0</b> | +| | | | | | | | | | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23146/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/23_series/23146/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bb3156d604b59455e597e4729583be0a4bf613f --- /dev/null +++ b/marked/Rel-11/23_series/23146/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3be6be3166943be73488737778a3d2cf22ba772a07a2233246aae55d67307f94 +size 87279 diff --git a/marked/Rel-11/23_series/23146/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/23_series/23146/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ba12e7bff151397a5adbef9de35d6854a1aa8c5 --- /dev/null +++ b/marked/Rel-11/23_series/23146/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d3c09a5573d7dc2ebe060b52621fbf4ba380c68daf1d2b8410db8161d9fbd5e +size 84276 diff --git a/marked/Rel-11/23_series/23146/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-11/23_series/23146/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c8dbbd9ae8f5f59ff0474f5e9eadc3bd84711a3 --- /dev/null +++ b/marked/Rel-11/23_series/23146/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96385cbb9491ce22bb76359c7e7bd6e4cbe5003c7ba49732ad0c6de95e7035d7 +size 73378 diff --git a/marked/Rel-11/23_series/23146/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-11/23_series/23146/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..979d13f17c9e0e8aa8c97ff499b1f722804f6131 --- /dev/null +++ b/marked/Rel-11/23_series/23146/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3486f31378dd470fbd8c45668910f00d8195fab424781610a237e91fe5032365 +size 115572 diff --git a/marked/Rel-11/23_series/23146/107da2e3495b2f24352c9e3b26ec4841_img.jpg b/marked/Rel-11/23_series/23146/107da2e3495b2f24352c9e3b26ec4841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de49e94da41d8cb9099303e228bca9b0b60d0aea --- /dev/null +++ b/marked/Rel-11/23_series/23146/107da2e3495b2f24352c9e3b26ec4841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea80cce1808b635a7612a7f47522c766886e4bd3a780af96a2bfb08d863a0c43 +size 63490 diff --git a/marked/Rel-11/23_series/23146/18442e4e239480f0c3c95b547aa8fde2_img.jpg b/marked/Rel-11/23_series/23146/18442e4e239480f0c3c95b547aa8fde2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..997e1650e7b25142badb4293b7b95d669a6818b4 --- /dev/null +++ b/marked/Rel-11/23_series/23146/18442e4e239480f0c3c95b547aa8fde2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d8e0d36a03979adca21c4bd379eca58b933655d5a3b11dafd47d215f11c1a6f +size 54233 diff --git a/marked/Rel-11/23_series/23146/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/23_series/23146/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33800e00ef0c4f9a2896802c7e82adeb7c08c3de --- /dev/null +++ b/marked/Rel-11/23_series/23146/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e51076a6f751249a3fdeac681233cf992000bc8fd8a1738e3355dc677990c68f +size 107189 diff --git a/marked/Rel-11/23_series/23146/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23146/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d4df34254f46a466411968cfd88634e3cf97e65 --- /dev/null +++ b/marked/Rel-11/23_series/23146/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b126f16ff5e2616abf038f6451d39a11549c53cbfec20ab4dcd687073a3073a +size 45487 diff --git a/marked/Rel-11/23_series/23146/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/23_series/23146/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5c56738a4a5474fc1e3b0f35583478eae8831b4 --- /dev/null +++ b/marked/Rel-11/23_series/23146/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88fbf87a72dc977bc75a4b77913fed3f3fd961650f4cf41d3262cdbde73dd68a +size 85932 diff --git a/marked/Rel-11/23_series/23146/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/23_series/23146/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3541d9547c35ba7b27936348e5f679c72968c33c --- /dev/null +++ b/marked/Rel-11/23_series/23146/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9518743bf858192bfe7be75caab5a3e08a294ea12a1322ff08c5e0345f355de1 +size 104804 diff --git a/marked/Rel-11/23_series/23146/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/23_series/23146/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e00b8a124011dc88d37424f1c3bd5000fd53651 --- /dev/null +++ b/marked/Rel-11/23_series/23146/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:786c26345eb314ef385922e5fe40dd89837a5b7f43f4f1c8acc67ddadbee0662 +size 47590 diff --git a/marked/Rel-11/23_series/23146/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/23_series/23146/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..850bde277d5bef2ef7f65e390366f62b7060cc55 --- /dev/null +++ b/marked/Rel-11/23_series/23146/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdc7197af4f4b8b5b70e1e26aca4df7ed6a0efb683c3d1eb5b9e4d14bea66ae6 +size 106791 diff --git a/marked/Rel-11/23_series/23146/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-11/23_series/23146/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6c284acb6dbf0249ab651c9061b9e4dcb6c51f0 --- /dev/null +++ b/marked/Rel-11/23_series/23146/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:118d4f4e06442cc8801c27f31945f085ec309e24d24986100bbb8e6e6eedf8d9 +size 84162 diff --git a/marked/Rel-11/23_series/23146/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-11/23_series/23146/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3db66c89c4d435d9c6c453a852f63e34c1d7088c --- /dev/null +++ b/marked/Rel-11/23_series/23146/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfa20b7483ed8b6b05e66fa75550dfe3a78e1088f0d2485e12bffbe0e7bec58d +size 102441 diff --git a/marked/Rel-11/23_series/23146/356eb99ab9489bbd647223390a913903_img.jpg b/marked/Rel-11/23_series/23146/356eb99ab9489bbd647223390a913903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13edff57673e64ed57c629f72177390be1a89834 --- /dev/null +++ b/marked/Rel-11/23_series/23146/356eb99ab9489bbd647223390a913903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c80a8334686977ab49671832e45223b0593526d087dd4cb098c594083e2fe97 +size 39670 diff --git a/marked/Rel-11/23_series/23146/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-11/23_series/23146/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f8fd1913b848a477ceac8b12ee1d936ffdae01e --- /dev/null +++ b/marked/Rel-11/23_series/23146/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7296183cfcfdeb1aba316b63673040e3b11a8029f547bee0d09248df9a89e349 +size 25624 diff --git a/marked/Rel-11/23_series/23146/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-11/23_series/23146/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c4789d14f489af43d9e4010de29a072f57d0056 --- /dev/null +++ b/marked/Rel-11/23_series/23146/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52efc0475e90031849abf6216b8eea20e034c17cf99fafda2d3535e8ff0c1a05 +size 57989 diff --git a/marked/Rel-11/23_series/23146/474a819357587e34949a3e110ff19b30_img.jpg b/marked/Rel-11/23_series/23146/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d84463ddddd5bd4661acf30ad78f9de500b38be --- /dev/null +++ b/marked/Rel-11/23_series/23146/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4cf23aa428c317bae6472df908c714906e63035ec21f610e8fed31276eb2386 +size 93467 diff --git a/marked/Rel-11/23_series/23146/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-11/23_series/23146/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a64ec5f15507710b8b725163f3c1d1d944ff9398 --- /dev/null +++ b/marked/Rel-11/23_series/23146/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f02f158abc37ef5b73ea07d03ccc2955228d551944e06951a6d94865e9592d4e +size 88986 diff --git a/marked/Rel-11/23_series/23146/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-11/23_series/23146/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7955804ce63951d0fef1bc8bfd065611b15a92c2 --- /dev/null +++ b/marked/Rel-11/23_series/23146/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a43b6f695e9346cd29336ade5540f7c92345eb19b2bef2d963e62832b6a380c +size 147626 diff --git a/marked/Rel-11/23_series/23146/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Rel-11/23_series/23146/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ee32370454ffe27bd20ee50c1aa8038ddf5a878 --- /dev/null +++ b/marked/Rel-11/23_series/23146/4ff00a489baaa34a0c01070de1d613db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb4135008d650cba6c39c0620baa4d0983ce7a2ecec08cb7779f9f661d1b3ee1 +size 65230 diff --git a/marked/Rel-11/23_series/23146/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/23_series/23146/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4117c7432446a16eccdf7b27fc47d59901526b37 --- /dev/null +++ b/marked/Rel-11/23_series/23146/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8068b69f83e69e650ca9815f3a43aaa442be456ba00f3c383913bce1da0fdabe +size 158223 diff --git a/marked/Rel-11/23_series/23146/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-11/23_series/23146/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..822a52b98328376b84242b87a7f2dd95f16ebd92 --- /dev/null +++ b/marked/Rel-11/23_series/23146/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae10e55bf262eea91dbea5d990ed4e9e0510c016f1d1db766f9283cb3bb03ada +size 178553 diff --git a/marked/Rel-11/23_series/23146/57939c16065211317c5442cf2a4009e0_img.jpg b/marked/Rel-11/23_series/23146/57939c16065211317c5442cf2a4009e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cb121c93fb33d65a2bcf80d9bfccf9df3315077 --- /dev/null +++ b/marked/Rel-11/23_series/23146/57939c16065211317c5442cf2a4009e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b241ee7e810560dc189cfc19f1d28d22353b17e497070e2a7098974dede0e812 +size 53520 diff --git a/marked/Rel-11/23_series/23146/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-11/23_series/23146/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26acf9398e23340e41da68f00616a29236dceb36 --- /dev/null +++ b/marked/Rel-11/23_series/23146/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:defafd19864b83832dc76cd38b7207e4419c1f979c692a07a2ca6a6d28bbf9c3 +size 131219 diff --git a/marked/Rel-11/23_series/23146/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-11/23_series/23146/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1afeb4c9598d10d0f270b7d4966d7d389d7623c6 --- /dev/null +++ b/marked/Rel-11/23_series/23146/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fc6a89eecc7b9e9e20b4a51f09db68255fbdd598e1ceb17cfd11ba1c8371f86 +size 42328 diff --git a/marked/Rel-11/23_series/23146/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-11/23_series/23146/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd5dd98d1f2137ee468cee92e54d4bace6b02cb1 --- /dev/null +++ b/marked/Rel-11/23_series/23146/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c485c1875ddacf1e1dc513189fcdb2f2c2fa946ce8e1cf21c254cd7e48ea094 +size 99409 diff --git a/marked/Rel-11/23_series/23146/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/23_series/23146/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb20cc65ed0ce0d28bd88b443f0f3181974fd063 --- /dev/null +++ b/marked/Rel-11/23_series/23146/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3246c03deb75a37b58179d0600a3e2c7735699379391cfffbb344c06c5739a3d +size 129878 diff --git a/marked/Rel-11/23_series/23146/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-11/23_series/23146/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50e7f8f0124a2eb4439b7ba53985b4e7b2653a29 --- /dev/null +++ b/marked/Rel-11/23_series/23146/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:665d077969b95ac598871c99d74e24ea29cca595246fb6cd2b42d7b25e455f3e +size 95554 diff --git a/marked/Rel-11/23_series/23146/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/23_series/23146/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e189113f1059c26928d9cec911ced5fa9384638a --- /dev/null +++ b/marked/Rel-11/23_series/23146/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7bf3a25aa2073409c6e27b821ee0726d9eb067f6cd04fcbc0098e5060b3a76e +size 98457 diff --git a/marked/Rel-11/23_series/23146/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/23_series/23146/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6070b8d53d41dd26488df0502d0465f0249d1298 --- /dev/null +++ b/marked/Rel-11/23_series/23146/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bf0f543ef59cb26fd98c3a72bc144696170f09111a91cb21ef157cb3e103edf +size 80515 diff --git a/marked/Rel-11/23_series/23146/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-11/23_series/23146/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..977a3ecef666c8ffa56326cd952fb9416ae6d061 --- /dev/null +++ b/marked/Rel-11/23_series/23146/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd4c6189f0478f68e15cf312e4a2ccfb408abbca6743e175b4ee870c9a7a0dfa +size 34219 diff --git a/marked/Rel-11/23_series/23146/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/23_series/23146/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c4f004eb880b38666e2d18bb47454ca69e1bb73 --- /dev/null +++ b/marked/Rel-11/23_series/23146/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd830f32ebbc507ad6cfa34ea0e974f9070e253cb4721c04c152feaf7e8c75c0 +size 85768 diff --git a/marked/Rel-11/23_series/23146/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-11/23_series/23146/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cf7638e1651735bff002a3a9dbc0da72bef8269 --- /dev/null +++ b/marked/Rel-11/23_series/23146/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:281952a6591345314382cdc4ab17a0f9fbe4882dde20a267f08b94b78d97c798 +size 113625 diff --git a/marked/Rel-11/23_series/23146/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-11/23_series/23146/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba6ea3b716bfa635cc5bff9f5dbe391adcc8ac8d --- /dev/null +++ b/marked/Rel-11/23_series/23146/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71e6043b405e30548ac36d8fc2651cbdf1d7591a4cf04349765d74bfa4b4f02f +size 148032 diff --git a/marked/Rel-11/23_series/23146/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-11/23_series/23146/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e8543a7b369a5606e08f2238e3235cee26c4de6 --- /dev/null +++ b/marked/Rel-11/23_series/23146/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d33db0d64a50c8e9facde5a561a000a509ae8556b81a955fbd374fe334a9a292 +size 91468 diff --git a/marked/Rel-11/23_series/23146/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-11/23_series/23146/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af24e42ae3d25ae822f631036eb70d53503e6260 --- /dev/null +++ b/marked/Rel-11/23_series/23146/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06c5f6f0b0d29ab25a4ef75ac56e1b92bba6f045769e9eb9c3a9463047d320ed +size 92513 diff --git a/marked/Rel-11/23_series/23146/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-11/23_series/23146/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57fd39fe2ffabbd9b8d63341c91daca75332bc7e --- /dev/null +++ b/marked/Rel-11/23_series/23146/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ec00af03a8e2a324c33bd6757e2a0447ffa1bc3cf524029a7bbb78c07cfebbe +size 42942 diff --git a/marked/Rel-11/23_series/23146/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Rel-11/23_series/23146/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2450412d183919edc06c067109848877fa637b9e --- /dev/null +++ b/marked/Rel-11/23_series/23146/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:253593ebe339ee69eea26d40f1a857f2a00bbc541e3914deda200a4d84c95d1b +size 26117 diff --git a/marked/Rel-11/23_series/23146/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-11/23_series/23146/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bb42d2f02544416df2c3b64743554105d63e5a4 --- /dev/null +++ b/marked/Rel-11/23_series/23146/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d827148e1011b4f089b8d583ee6b25dc98520bbc42a9a2876665d9d53fccb8d +size 61639 diff --git a/marked/Rel-11/23_series/23146/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/23_series/23146/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46cbc055f78e2a83e19602c58f4546674ad4b0ba --- /dev/null +++ b/marked/Rel-11/23_series/23146/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49127db97be72045a3958714357cb13a27f78a9f46fde7002499de494abc0bd3 +size 94428 diff --git a/marked/Rel-11/23_series/23146/9f50279046b74a4e66a1a0144c3b1d11_img.jpg b/marked/Rel-11/23_series/23146/9f50279046b74a4e66a1a0144c3b1d11_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bae1662a5ec289c1f4c76a7707f0d8f3009ceec8 --- /dev/null +++ b/marked/Rel-11/23_series/23146/9f50279046b74a4e66a1a0144c3b1d11_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d98dd97aa762fe3287e1e2c2560508d23f4d548fd029d22c87a15d59fd1efef6 +size 110223 diff --git a/marked/Rel-11/23_series/23146/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/23_series/23146/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53b1ee76d77004b640fc922778649846b915c3de --- /dev/null +++ b/marked/Rel-11/23_series/23146/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d8d448351666004b7bd2b08a9ac083dd1b85cbf3c1eeb4640324ebd9df15bd0 +size 43741 diff --git a/marked/Rel-11/23_series/23146/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-11/23_series/23146/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7fc052bfea6536e6ed295efa8f814d4425fd56b --- /dev/null +++ b/marked/Rel-11/23_series/23146/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe6116d5da57942619ebed9c34eb170cf21573a57eedcff043053bb556b23b1e +size 53400 diff --git a/marked/Rel-11/23_series/23146/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-11/23_series/23146/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e311902a1df10ab5c65c7e7d1091fca017f99afb --- /dev/null +++ b/marked/Rel-11/23_series/23146/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fad466074f2a82e31bfdc07f2f5031b8d040c1e4e5263c83743152549fe5ea47 +size 64284 diff --git a/marked/Rel-11/23_series/23146/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/23_series/23146/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d382b4bca9d2aa0d7e428d37cc1b5fe0cba68ba --- /dev/null +++ b/marked/Rel-11/23_series/23146/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0cdf507e4cb820880f150993903ea5bf2078b1297ed361635c980febbfb16c2 +size 102685 diff --git a/marked/Rel-11/23_series/23146/a634891d16b60b21df90a35c2af72c67_img.jpg b/marked/Rel-11/23_series/23146/a634891d16b60b21df90a35c2af72c67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21c03d4be4143e2f4e58976ecfa63bd4e81ed279 --- /dev/null +++ b/marked/Rel-11/23_series/23146/a634891d16b60b21df90a35c2af72c67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c81601868c3a500e0a534e581f74773ac422649d8aaafc54a45ab0772c86cdfc +size 91395 diff --git a/marked/Rel-11/23_series/23146/aa6e28822419dba9f22129fee66c9c4c_img.jpg b/marked/Rel-11/23_series/23146/aa6e28822419dba9f22129fee66c9c4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acc11044b69de2f708291316b346b66f39485bf4 --- /dev/null +++ b/marked/Rel-11/23_series/23146/aa6e28822419dba9f22129fee66c9c4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dab867a0ed84788c39d60cc8917619270c2276a3ce17910a555809975c21a3a +size 95986 diff --git a/marked/Rel-11/23_series/23146/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-11/23_series/23146/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42e47045eb55f295a5316c5a37f808a497ea5844 --- /dev/null +++ b/marked/Rel-11/23_series/23146/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:025fc4e665f6586e84f8f075c4a6501573aa4f089664ea64a08b98686e24ee58 +size 82873 diff --git a/marked/Rel-11/23_series/23146/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/23_series/23146/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6dcc20f0b80c740438ddf2a1a9e25e782011df33 --- /dev/null +++ b/marked/Rel-11/23_series/23146/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae54899b5137899ef8a87673cf071f3ac34283c4b96570c81a95fe720c2d1e32 +size 97024 diff --git a/marked/Rel-11/23_series/23146/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-11/23_series/23146/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad5e4b961858f41aa61c005fbe894b241c7befce --- /dev/null +++ b/marked/Rel-11/23_series/23146/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ada0ddf8153ac81f724a1825bccb729b416a8b9433f360a80dc28577498725e +size 20452 diff --git a/marked/Rel-11/23_series/23146/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-11/23_series/23146/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42dd825afdb51a7945540f11dfa6e1aa53381da8 --- /dev/null +++ b/marked/Rel-11/23_series/23146/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28d5b957b264a50bb0baf81af90634da5a90a43b641135441ab6d1d68cc51971 +size 127894 diff --git a/marked/Rel-11/23_series/23146/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-11/23_series/23146/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13051ba0b508f3c29b47a57450d0b15ffb8c3aec --- /dev/null +++ b/marked/Rel-11/23_series/23146/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e8b680649b1531dd608379eed92cdc0ecddcc9546475916d6d6168e215f1e65 +size 144801 diff --git a/marked/Rel-11/23_series/23146/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/marked/Rel-11/23_series/23146/db5ab5d386827a5d5f5fad0f45612b90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8bf8c51e563ce489854060f2e5babad12956614 --- /dev/null +++ b/marked/Rel-11/23_series/23146/db5ab5d386827a5d5f5fad0f45612b90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e6a901ff7002d8622aff022bbd16eaae106a986929868c555005c60b6421ca2 +size 28914 diff --git a/marked/Rel-11/23_series/23146/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/23_series/23146/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4abc4d55fb086306be774efe8d8dd5cc77f8337 --- /dev/null +++ b/marked/Rel-11/23_series/23146/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7506e9343dd31fc060969b29081897df2969ac6ccbf977cbff88045eeb7545b +size 95086 diff --git a/marked/Rel-11/23_series/23146/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/23_series/23146/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bb305d5960f9e4a033a30f61262f8d6d054dfe6 --- /dev/null +++ b/marked/Rel-11/23_series/23146/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62b6e0d841db9f03a8fb5a3224d9425eb5e84bf90165269dd55b6e3b49b647bb +size 93203 diff --git a/marked/Rel-11/23_series/23146/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-11/23_series/23146/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8d3bfdc4e44ba8365bc7f4876b58a8d7525c29d --- /dev/null +++ b/marked/Rel-11/23_series/23146/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4c17e50b133af4ae37a6a6ec16dc659354903bd251fc3c5997da8ef583cb8b2 +size 102574 diff --git a/marked/Rel-11/23_series/23146/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-11/23_series/23146/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbd0b1740cece145afdf5457643fa647ac93362c --- /dev/null +++ b/marked/Rel-11/23_series/23146/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16c7b087c2ad129bde77561632eba8ddf3bf73701ef8e74adc9add4c3b07cb11 +size 138701 diff --git a/marked/Rel-11/23_series/23146/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-11/23_series/23146/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bdcc89b71a986f6c7cb2803f56c22c891038a7a --- /dev/null +++ b/marked/Rel-11/23_series/23146/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddbf77cf739956ff7aaabd1c1229549db621d577b9227b2749a30287f674f62c +size 72500 diff --git a/marked/Rel-11/23_series/23146/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-11/23_series/23146/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ec99d108332083d4be0efcfed582ef9802f3b71 --- /dev/null +++ b/marked/Rel-11/23_series/23146/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e9086c0282ebbf1728ca3dfb122aa06d58972b30caaacdab8feacc7b75e6377 +size 53979 diff --git a/marked/Rel-11/23_series/23146/raw.md b/marked/Rel-11/23_series/23146/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ef029e5a7e6c44aab4cf83b3397f3eb61fbf8048 --- /dev/null +++ b/marked/Rel-11/23_series/23146/raw.md @@ -0,0 +1,2667 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definition and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Network architecture..... | 8 | +| 4.1 Service definition ..... | 8 | +| 4.2 Network architecture ..... | 9 | +| 5 Reference configuration at the mobile station ..... | 9 | +| 5.1 FA functionality ..... | 10 | +| 5.2 UMTS facsimile machine functionality ..... | 10 | +| 6 Connection types..... | 10 | +| 6.1 Protocol model ..... | 11 | +| 6.2 Mobile to mobile calls..... | 12 | +| 6.3 Procedure interrupts ..... | 12 | +| 6.4 Radio channel modification ..... | 12 | +| 7 Facsimile adaptor ..... | 12 | +| 7.1 Principles of the Facsimile Protocol Adaptation..... | 12 | +| 7.2 FA functionality ..... | 13 | +| 7.2.1 Packet elements between FAs ..... | 14 | +| 7.2.2 Interactions between and interventions within the FAs..... | 15 | +| 7.2.3 BCS phase ..... | 16 | +| 7.2.3.1 BCS command/response procedures ..... | 16 | +| 7.2.3.2 Compatibility checking..... | 17 | +| 7.2.3.3 Training Check ..... | 17 | +| 7.2.3.4 Control of transmission rate..... | 18 | +| 7.2.4 Message phase ..... | 18 | +| 7.2.4.1 Message Transcoding ..... | 18 | +| 7.2.4.2 Generation of the normal data packet..... | 19 | +| 7.2.4.3 Generation of the error correction data packet ..... | 19 | +| 7.2.4.4 Normal facsimile data..... | 19 | +| 7.2.4.5 Error correction facsimile data ..... | 19 | +| 7.2.4.6 Controlling of facsimile coded data..... | 20 | +| 7.2.4.6.1 Transmitting Fax Adapter ..... | 20 | +| 7.2.4.6.2 Receiving Fax Adapter..... | 20 | +| 7.2.5 Disconnect procedure ..... | 21 | +| 7.2.6 Timeouts ..... | 21 | +| 8 Use of terminal adaptation functions ..... | 21 | +| 8.1 Principles of terminal adaptation functions..... | 21 | +| 8.2 Specific TAFs for facsimile service..... | 22 | +| 9 Signalling aspects..... | 22 | +| 9.1 Handling of tonal signals..... | 22 | +| 9.2 Call establishment ..... | 22 | +| 9.2.1 Mobile terminated call..... | 22 | +| 9.2.1.1 Speech then facsimile ..... | 23 | +| 9.2.1.2 Auto answer ..... | 23 | +| 9.2.2 Mobile originated calls ..... | 23 | +| 9.2.2.1 Speech then facsimile ..... | 23 | +| 9.2.2.2 Auto calling..... | 24 | +| 9.2.2.3 Manual calling ..... | 24 | + +| | | | +|-------------------------------|-------------------------------------------------------------------|-----------| +| 10 | Interworking to fixed networks..... | 25 | +| 10.1 | Interworking to PSTN ..... | 25 | +| 10.2 | Interworking to ISDN..... | 25 | +| <b>Annex A (normative):</b> | <b>Structure and contents of the FA protocol elements.....</b> | <b>26</b> | +| A.1 | Internet Fax Protocol..... | 26 | +| A.2 | Facsimile UDP Transport Layer Protocol..... | 26 | +| A.3 | User Datagram Protocol..... | 26 | +| A.4 | Internet Protocol..... | 27 | +| A.5 | Point to Point Protocol ..... | 27 | +| A.6 | Mapping of FA frames..... | 27 | +| <b>Annex B (informative):</b> | <b>Abbreviations from ITU-T Recommendation T.30 and T.4 .....</b> | <b>28</b> | +| <b>Annex C (informative):</b> | <b>Procedure examples .....</b> | <b>29</b> | +| <b>Annex D (normative):</b> | <b>SDL Diagrams .....</b> | <b>41</b> | +| <b>Annex E (normative):</b> | <b>ASN.1 notation.....</b> | <b>79</b> | +| <b>Annex F (informative):</b> | <b>Change history.....</b> | <b>80</b> | + +# --- Foreword + +This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP). + +The present document defines the technical realization of facsimile group 3 using non-transparent network support 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 describes the procedures allowing the technical realization of the real time end-to-end facsimile group 3 service within the UMTS PLMN using non-transparent network support according to the definition of the Teleservices 61 and 62 specified in 3GPP TS 22.003. Within the present document particular attention is given to Teleservice "Alternate speech/facsimile group 3" (Teleservice 61). However, the definitions apply also to Teleservice "Automatic facsimile group 3" (Teleservice 62) with the exception of all actions concerned with the speech phase. Consequently, in the following descriptions the term "Teleservice" denotes both Teleservice 61 and Teleservice 62 as appropriate. + +NOTE: V.25bis is outdated. References to V.25bis procedures need to be replaced by corresponding procedures based on V.250 and 3GPP TS 27.007. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. + +- [1] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)". +- [2] 3GPP TR 23.910: "Circuit Switch Data Bearer Services". +- [3] 3GPP TS 24.008: "Mobile radio interface layer 3 specification". +- [4] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [5] 3GPP TS 27.002: "Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities". +- [6] 3GPP TS 27.007: "AT command set for 3GPP User Equipment(UE)". +- [7] 3GPP TS 29.007: "3GPP; TSG CN; General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [8] ITU-T Recommendation T.4: "Standardization of group 3 facsimile apparatus for document transmission". +- [9] ITU-T Recommendation T.30: "Procedures for document facsimile transmission in the general switched telephone network". +- [10] ITU-T Recommendation V.21: "300 bits per second duplex modem standardized for use in the general switched telephone network". +- [11] ITU-T Recommendation V.24: "List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)". +- [12] ITU-T Recommendation V.27 ter: "4 800/2 400 bits per second modem standardized for use in the general switched telephone network". +- [13] ITU-T Recommendation V.29: "9 600 bits per second modem standardized for use on point-to-point 4-wire leased telephone-type circuits". +- [14] ITU-T Recommendation V.17: "A 2-wire modem for facsimile applications with rates up to 14 400 bit/s". +- [15] ITU-T Recommendation V.250: "Serial asynchronous automatic dialling and control". + +- [16] ITU-T Recommendation X.300: "General principles and arrangements for interworking between public data networks, and between public data networks and other networks". +- [17] ITU-T Recommendation T.38: "Procedures for real-time Group 3 facsimile communication over IP networks". +- [18] ITU-T Recommendation X.680: "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [19] ITU-T Recommendation X.691: "Information technology – ASN.1 encoding rules – Specification of Packed Encoding Rules (PER)". +- [20] IETF RFC 1662: "PPP in HDLC-like Framing". +- [21] IETF RFC 1661: "The Point-to-Point Protocol (PPP)". +- [22] IETF RFC 1570: "PPP LCP Extensions". +- [23] IETF RFC 1332: "The PPP Internet Protocol Control Protocol (IPCP)". +- [24] IETF RFC 791: "Internet Protocol". +- [25] IETF RFC 768: "User Datagram Protocol". + +# --- 3 Definition and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**E-T.38:** to use E-T.38 between both the FAs across the radio interface. E-T.38 is based on ITU-T Recommendation T.38, but there are some differences with regards to the packet elements, transcoding methods, and the procedure of controlling signals. The same procedure as T.38 is used for the structure of the frame and the protocol stack (Refer to the following clause, annex A and T.38 for the details). + +**TAF:** TAF usually shows a function of the UE side, but when IWF has the function that is equal to the UE side TAF, TAF is used to express the function of the IWF in the present document. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|---------------------------------------------------| +| AAL2 | ATM Adaptation Layer type 2 | +| ARQ | Automatic Retransmission Request | +| BCS | Binary coded signalling | +| CCT | Circuit(s) | +| CD | Data Call Direction | +| CDMA | Code Division Multiple Access | +| CONT | Character Oriented Non-Transparent Protocol | +| DTCH | Dedicated Traffic Channel | +| E-T.38 | Enhanced T.38 | +| IE | Information element | +| IFP | Internet Fax Protocol | +| IP | Internet Protocol | +| IWF | Interworking Function | +| I/F | Interface | +| L2RCOP | Layer 2 Relay Character Oriented Protocol | +| MAC | Medium Access Control (protocol layering context) | +| MMI | Man-Machine Interface | +| MT | Mobile Terminal | +| PPP | Point to Point Protocol | +| PSTN | Public Switched Telephone Network | +| RCSD | Reverse Call Setup Direction | + +| | | +|-------|-----------------------------------------------------------------------| +| R-FA | Reception side facsimile adaptor that does not have TAF capability | +| R-FAX | Reception side facsimile | +| RLC | Radio Link Control | +| RLP | Radio Link Protocol | +| R-TAF | Reception side terminal adaptation function | +| SREJ | Selective reject | +| TAF | Terminal Adapter Function | +| TE | Terminal Equipment | +| T-FA | Transmission side facsimile adaptor that does not have TAF capability | +| T-FAX | Transmission side facsimile | +| T-TAF | Transmission side terminal adaptation function | +| UE | User Equipment | +| UDP | User Datagram Protocol | +| UDPTL | Facsimile UDP Transport Layer protocol | + +The abbreviations for the facsimile specific protocol elements and signals are listed in annex B. + +# --- 4 Network architecture + +## 4.1 Service definition + +The fixed network facsimile group 3 service is an international telematic service for document transmission between two facsimile group 3 terminals. + +The service specifications are comprised of two parts: + +- the control procedures described in ITU-T Recommendation T.30; +- the document transmission coding described in ITU-T Recommendation T.4. + +The UMTS facsimile group 3 Teleservice allows connections between facsimile group 3 terminals using: + +- a UMTS PLMN as stand-alone facility for mobile-to-mobile communication; +- a UMTS PLMN to have access to fixed networks PSTN and/or ISDN for mobile to/from fixed network communication. + +For this Teleservice, the coding of the facsimile document is as per ITU-T Recommendation T.4 and the protocol as per ITU-T Recommendation T.30 both modified within the PLMN as detailed in the present document. + +The interworking between different networks is based on ITU-T Recommendation X.300. + +The particular features of this Teleservice are: + +- it uses point-to-point communication; +- the information transfer mode is circuit, duplex, asynchronous; +- the information transfer capability is alternate speech/ facsimile group 3 or facsimile group 3 only; +- both mobile originated and mobile terminated calls are supported; +- different end-to-end message speeds as per ITU-T Recommendation T.30 may be used within the same connection to match the appropriate quality requirements; +- use of the standard asynchronous terminal adaptation function for non-transparent network support (as per 3GPP TS 27.002) within the UE is envisaged. + +## 4.2 Network architecture + +The network architecture applicable to this Teleservice is shown in figure 1. + +![Figure 1: Network architecture diagram showing a FAX terminal connected to an MT, which is connected to a RAN via a V interface. The RAN is connected to an MSC/IWF, which is connected to a vertical stack of PLMN, PSTN, and ISDN networks. A FAX terminal is also connected to the PSTN network.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +``` + +graph LR + FAX1[FAX] --- MT[MT] + MT -- V --- RAN[RAN] + RAN --- MSC_IWF[MSC/IWF] + MSC_IWF --- PLMN[PLMN] + MSC_IWF --- PSTN[PSTN] + MSC_IWF --- ISDN[ISDN] + PSTN --- FAX2[FAX] + +``` + +Figure 1: Network architecture diagram showing a FAX terminal connected to an MT, which is connected to a RAN via a V interface. The RAN is connected to an MSC/IWF, which is connected to a vertical stack of PLMN, PSTN, and ISDN networks. A FAX terminal is also connected to the PSTN network. + +Figure 1: Network architecture + +It shows the case of mobile to fixed network interworking. For mobile-to-mobile calls, there would effectively be a loop back within the PLMN using two IWFs. + +# 5 Reference configuration at the mobile station + +The user equipment reference configurations described in this clause are defined as per 3GPP TS 27.001. + +![Figure 2: Reference configurations diagram showing three options (a, b, c) for connecting a FAX terminal to an MT within a mobile station. Option a) shows FAX connected to FA, which is connected to MT via an R interface. Option b) shows FAX connected directly to MT via an R interface. Option c) shows FAX, FA, and MT as a single integrated unit connected to the MT interface.](99bae07626f60f9ede10e2e387ef7051_img.jpg) + +``` + +graph TD + subgraph Mobile_station [Mobile station] + direction LR + a) FAX_a[FAX] --- FA_a[FA] --- R_a((R)) --- MT_a[MT] + b) FAX_b[FAX] --- R_b((R)) --- MT_b[MT] + c) FAX_c[FAX] --- FA_c[FA] --- MT_c[MT] + end + +``` + +Figure 2: Reference configurations diagram showing three options (a, b, c) for connecting a FAX terminal to an MT within a mobile station. Option a) shows FAX connected to FA, which is connected to MT via an R interface. Option b) shows FAX connected directly to MT via an R interface. Option c) shows FAX, FA, and MT as a single integrated unit connected to the MT interface. + +Figure 2: Reference configurations + +The teleservice definitions in 3GPP TS 22.003 regard the facsimile group 3 terminal as a 2-wire analogue terminated equipment. In order to connect this to the MT a separate "FA" device is necessary. This configuration, shown in figure 2a, shall be considered as the standard configuration, so that all the existing facsimile group 3 terminals may be connected to the PLMN. + +An alternative realization would be to combine a facsimile group 3 terminal and the FA into a special "UMTS facsimile machine", directly providing a digital output. Although such a terminal shall appear to the MT as identical as the FA (i.e. with an identical interface and protocol), it would allow for a significantly smaller and simpler facsimile machine. This configuration is shown in figure 2b. + +In addition of course, it is always possible to realize a single device, as per figure 2c, where both the facsimile and mobile termination functions are considered to be part of one integrated unit. + +The particular terminal adaptation functions used are those detailed in 3GPP TS 27.002 for non-transparent bearer capability. The interface to the MT used is according to ITU-T Recommendation V.24 with an option for support of 3GPP TS 27.007 procedures for auto calling and auto answering. + +## 5.1 FA functionality + +The FA block, figure 3, is intended to specifically complement the facsimile group 3 terminal in order to be able to communicate over a UMTS PLMN. + +![Figure 3: FA scheme diagram. The diagram shows a rectangular block divided into two main sections. The left section is split horizontally into 'Composite Modem' (top) and 'Tone Handling' (bottom). The right section is labeled 'Control, Protocol Monitoring & Buffer'. An input line labeled '2-w' enters from the left, and an output line labeled 'R' exits to the right.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +Figure 3: FA scheme diagram. The diagram shows a rectangular block divided into two main sections. The left section is split horizontally into 'Composite Modem' (top) and 'Tone Handling' (bottom). The right section is labeled 'Control, Protocol Monitoring & Buffer'. An input line labeled '2-w' enters from the left, and an output line labeled 'R' exits to the right. + +**Figure 3: FA scheme** + +Whether it has to be a function internal to the UMTS PLMN, or an external accessory associated with the facsimile group 3 terminal, is beyond the scope of the present document, and in any case, does not affect the working of the procedure as described here. + +It may be functionally partitioned in two sections: + +- an analogue section, dealing with: + - the modulation and demodulation processes according to ITU-T Recommendation V.21, V.27ter, V.29 and V.17 as explained in ITU-T Recommendation T.4 and T.30; + - handling of the signalling on a 2-wire path to the associated facsimile terminal, including auto calling and auto answering functions where necessary (see clause 7). +- a digital section, dealing with: + - overall control of the FA; + - where necessary, manipulating the ITU-T Recommendation T.30 protocol as detailed in the present document; + - connection to the TAF using the interface according to ITU-T Recommendation V.24 as described in 3GPP TS 27.002; + - where necessary, auto calling and auto answering functions according to 3GPP TS 27.007. + +## 5.2 UMTS facsimile machine functionality + +The special UMTS facsimile machine shown in the UE configuration of figure 2b is similar to the digital part of the FA, but without any of the analogue portions. + +It appears at the ITU-T Recommendation V.24 interface as identical as the FA, i.e. the MT needs to have no knowledge of the particular configuration used. + +# 6 Connection types + +In UMTS, the following connection elements attributes are applicable to these Teleservices. + +| | | +|---------------------------|-------------------------| +| Connection element: | Non-transparent | +| Duplex Mode: | Full Duplex | +| Synchronous/Asynchronous: | Asynchronous | +| Fixed Network User Rate: | 14 400 or 9 600[bit/s] | +| Wanted Air User Rate: | 28 800 or 14 400[bit/s] | + +Layer 1 and Layer 2 at R reference point are specified in 3GPP TS 27.002, but not here. + +To support the ITU-T Recommendation T.30, requiring different transmission rates, the following strategy shall be implemented: + +- the channel on the radio interface in UMTS shall be a channel that is satisfied with a user rate of 28 800 bit/s or 14 400 bit/s; +- the transmission rate between the FA and the associated facsimile terminal at both ends shall be the same, i.e. there shall be only one common end-to-end transmission rate at any given time; +- the message speed shall be negotiated between T-FAX and R-FAX; this also allows for message speeds of 2 400, 4 800, 7 200, 9 600, or 12 000, 14 400 bit/s to be used; +- the connection between the fax terminals is divided into three logical sections (T-FAX -(1)- T-FA-(2)- -R-FA-(3)-R-FAX); +- flag stuffing is applied by the FA towards the associated facsimile terminal within the constraints of ITU-T Recommendation T.30, to keep the data link active whenever a procedure delay occurs; +- the BCS protocol elements and the facsimile coded data are buffered at both FAs , if necessary, to guarantee data integrity; +- a specific FA protocol (FA protocol) is provided between both FAs to cater for appropriate link control. + +## 6.1 Protocol model + +Figure 4 depicts the protocol stack for this Teleservice. + +Depending on the particular implementation, the R reference point may not explicitly exist. In this case, the Layer2 protocol between the FA and the TAF and consequently the Layer2 protocol between the FA and the TAF entities operating across this interface may be omitted. The protocol stack at the radio interface, however, is not affected by this consideration, i.e. RLP and L2RCOP always apply. + +All protocol modules specific for this Teleservice shall be confined in the FA functions at both the UE and MSC/IWF ends. The TAF shall comply with the specifications 3GPP TS 27.001 and 3GPP TS 27.002. + +![Figure 4: Protocol stack for non-transparent support in UMTS. The diagram shows the protocol layers for FAX, FA, TAF, RAN, MSC/IWF, PSTN, and TE. The FAX and FA layers are T.30/T.4 (or Atcomm and) and 2W (or RS-232C). The FA layer contains IFP, UDP, IP, PPP, CONT, and I/F CCT. The TAF layer contains CONT, L2RCOP, RLP, and CDM. The RAN layer contains RLC, MAC, Iu-UP, CDMA, and AAL2. The MSC/IWF layer contains IFP, UDP, IP, PPP, L2RCOP, RLP, Iu-UP, and AAL2. The PSTN and TE layers are T.30/T.4 and 2W. The Iu I/F is indicated between RAN and MSC/IWF.](18442e4e239480f0c3c95b547aa8fde2_img.jpg) + +The diagram illustrates the protocol stack for non-transparent support in UMTS. It shows the flow of data from a FAX terminal through various network elements: FA (Facsimile Adapter), TAF (Terminal Adapter Function), RAN (Radio Access Network), MSC/IWF (MSC/Interworking Function), PSTN (Packet Switched Network), and finally to a TE (Terminal Equipment). The protocol layers are stacked vertically for each element. At the FAX/FA end, layers include T.30/T.4 (or Atcomm and), 2W (or RS-232C), IFP, UDP, IP, PPP, CONT, and I/F CCT. The TAF layer adds CONT, L2RCOP, RLP, and CDM. The RAN layer includes RLC, MAC, Iu-UP, CDMA, and AAL2. The MSC/IWF layer contains IFP, UDP, IP, PPP, L2RCOP, RLP, Iu-UP, and AAL2. The PSTN and TE layers consist of T.30/T.4 and 2W. The Iu I/F interface is shown between the RAN and MSC/IWF. + +Figure 4: Protocol stack for non-transparent support in UMTS. The diagram shows the protocol layers for FAX, FA, TAF, RAN, MSC/IWF, PSTN, and TE. The FAX and FA layers are T.30/T.4 (or Atcomm and) and 2W (or RS-232C). The FA layer contains IFP, UDP, IP, PPP, CONT, and I/F CCT. The TAF layer contains CONT, L2RCOP, RLP, and CDM. The RAN layer contains RLC, MAC, Iu-UP, CDMA, and AAL2. The MSC/IWF layer contains IFP, UDP, IP, PPP, L2RCOP, RLP, Iu-UP, and AAL2. The PSTN and TE layers are T.30/T.4 and 2W. The Iu I/F is indicated between RAN and MSC/IWF. + +Figure 4: Protocol stack for non-transparent support in UMTS + +![Figure 5: Communication model diagram showing the flow of data between G3 FAX, FA, MT incl. TAF, RAN, MSC/IWF (FA), and G3 FAX. The diagram illustrates the use of ITU-T Recommendation T.30 and the Fax adaptor protocol (E-T.38) for communication. The flow is from left to right: G3 FAX to FA to MT incl. TAF, then through RAN to MSC/IWF (FA) to G3 FAX. Below the boxes, double-headed arrows indicate the protocols used: ITU-T Recommendation T.30 at the ends and Fax adaptor protocol (E-T.38) in the middle. Dashed lines with arrows indicate interactions and interventions between the components.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 5: Communication model diagram showing the flow of data between G3 FAX, FA, MT incl. TAF, RAN, MSC/IWF (FA), and G3 FAX. The diagram illustrates the use of ITU-T Recommendation T.30 and the Fax adaptor protocol (E-T.38) for communication. The flow is from left to right: G3 FAX to FA to MT incl. TAF, then through RAN to MSC/IWF (FA) to G3 FAX. Below the boxes, double-headed arrows indicate the protocols used: ITU-T Recommendation T.30 at the ends and Fax adaptor protocol (E-T.38) in the middle. Dashed lines with arrows indicate interactions and interventions between the components. + +**Figure 5: Communication model** + +## 6.2 Mobile to mobile calls + +Tandem operation shall be applied to mobile to mobile calls. + +## 6.3 Procedure interrupts + +Procedure interrupts shall be supported only in Teleservices 61. In the case of Teleservice 62 any attempt to invoke procedure interrupts by MMI on the MT (see subclause 6.4) shall have no effect. + +## 6.4 Radio channel modification + +This subclause applies to Teleservice 61 only, if a change of the radio channel during the call swapping from speech to facsimile or vice versa is required. For this purpose the in-call modification procedure (ICM) as detailed in 3GPP TS 24.008 is carried out. + +The change from speech to facsimile shall be initiated by MMI at the facsimile terminal starting the ICM procedure via MODIFY signalling. + +# 7 Facsimile adaptor + +## 7.1 Principles of the Facsimile Protocol Adaptation + +The basic approach of the present document for facsimile group 3 is: + +- to use the ITU-T Recommendation T.30 procedure at both ends of the connection between the FA and the associated facsimile terminal; +- to intervene within the FAs in order to avoid a T.30 timer timeout due to delays in the radio interface; +- to check the message speed; the R-FA selects the appropriate modem indicated by the DIS/DTC frames from the R-FAX. The T-FA switches the appropriate modem according to the TSI/DCS frames from the T-FAX after selecting the modem indicated by the DIS/DTC frames from the R-FA. + +Following this strategy, an interchange model is defined concentrating on the facsimile relevant components. According to this model, three connection sections may be distinguished: + +- a) between the T-FA and the T-FAX; +- b) between the FAs; +- c) between the R-FA and the R-FAX. + +The FAs shall cater for the correct establishment and control of these layers, including traffic channel synchronization and status information exchange, in particular, with respect to circuit 106 and circuit 109 (according to ITU-T Recommendation V.24). Once these circuits have been set to ON (traffic channel synchronization), they shall be kept in the ON condition during the entire facsimile phase of a connection. + +## 7.2 FA functionality + +Basically there are four problem areas: + +- support of facsimile group 3 with a digital connection type; +- unpredictable delays on the radio interface due to actual RLP working conditions (ARQ); +- the need to change the transmission rate "locally" in the FAs both in the UE and in the MSC/IWF and to adapt it to the constant user rate of the radio interface; +- the inability to support some ITU-T Recommendation T.30 features. + +To overcome these problems some particular functions within the FAs are necessary, such as: + +- buffering of BCS frames and facsimile coded data prior to transfer; +- autonomous interventions such as BCS frame inhibiting within the FAs; +- provision of a FA protocol (IFP/UDPTL/UDP/IP/PPP) as an interchange protocol between the FAs. + +The main features relevant to ITU-T Recommendation T.30 adaptation functions are detailed in the following. + +The proper configuration is settled on both network sides by detecting the DIS/DTC frame just at the beginning of the phase B in ITU-T Recommendation T.30 protocol procedure. + +The optional error correction mode, as defined in ITU-T Recommendation T.4-Annex A and ITU-T Recommendation T.30-Annex A, may be fully supported, provided some specific features are included in the FA procedure. ECM is optional for the FA. + +In order to support ECM: + +- additional BCS frames need to be detected; +- the handling of the message phase needs to be adjusted. + +The overall framework as described in the present document applies, i.e. it shall be the same mode, ECM or non-ECM, at the transmitting side and the receiving side, because the FA stores FAX signals but does not convert the format of ECM and non-ECM. + +The error correction mode is entered upon detection of the relevant bits in the DIS/DTC frame. + +The working principle of the present document is based on the detection, control, deletion, and generation of key messages between the: + +- the T-FAX and the T- FA; +- the T- FA and the R- FA; +- the R- FA and the R- FAX. + +While in BCS phases, the following frames shall be detected: + +- DIS/DTC, to monitor all operational parameters of the transmitting terminal; +- CSI, to monitor all operational parameters of the receiving terminal; +- DCS, to realize the actual operational parameters, e.g. message transmission speed accepted by the sender terminal and the relevant message transfer direction (see table 2/ITU-T Recommendation T.30); +- TSI, to indicate that the following FIF information is the identification of the transmitting terminal. It may be used to provide additional security to the facsimile procedures; +- TCF, to verify training and to give a first indication of the acceptability of the channel for this data rate; +- FTT, to reject the training signal and requesting a retrain; + +- CTC/EOR, to fix the retransmission strategy by the facsimile transmitting terminal (error correction mode); +- CTR/ERR, to act as the confirmation message and so closing a BCS phase before a new message phase; +- EOM, to indicate the end of a complete page of facsimile information and to return to the beginning of the phase B; +- MPS, to indicate the end of a complete page of facsimile information and to return to the beginning of the phase C upon receipt of a confirmation; +- EOP, to indicate the end of a complete page of facsimile information and to further indicate that no further documents are forthcoming and to proceed to phase E, upon receipt of a confirmation; +- PRI-Q, to indicate the same as EOM/MPS/EOP command with the additional optional capability of requesting operator intervention, therefore PRI-Q is treated as EOM/MPS/EOP; +- DCN, to initiate the call release procedure. + +While in BCS phases, the following frames shall additionally be detected. However, these following signals shall not be transmitted to the radio network: + +- NSF, to indicate the specific user requirements, which are not covered by ITU-T T-Series Recommendations; +- NSC, to indicate the response to NSF, however this signal is not transmitted to the radio network; +- CFR and MCF, to trigger the message phase; +- PPR, as above, but after the fourth consecutive PPR request, the BCS phase continues with either CTC or EOR (error correction mode); +- RR, to ask for the status of the receiver; +- RTP, to indicate that a complete message has been received and that an additional message may follow after retransmission of training and CFR; +- RTN, to indicate that the previous message has not been satisfactorily received. Several receptions may be possible, provided training is retransmitted; +- PIP/PIN, to indicate that further transmissions are not possible without operator intervention; +- RNR, to indicate that the receiver is not ready to receive more facsimile data; +- ERR, to indicate the response to EOR; +- CRP, to require the retransmission of the previous received signal in errors. + +Furthermore, all BCS command messages shall be monitored to eliminate repeated command messages at the FA towards the other FA and to initiate a repetition of those command messages, if necessary, at the FA towards the associated FAX. Additionally, all BCS response messages shall be monitored to be able to clear the former condition. + +### 7.2.1 Packet elements between FAs + +To cater for the appropriate facsimile transmission some protocol elements and the related procedures are defined. These protocol elements shall be exchanged between both FAs. They are based on E-T.38 and described as follows. They are structured as outlined in annex A: + +IFP packet (see clause A.1 in annex A): + +The IFP packet is used to relay ITU-T Recommendation T.30 BCS frames. It includes the possibility also to transmit parts of an entire BCS frame (segmentation). + +#### 1) T.30\_INDICATOR: + +- CNG packet; +- CED packet; + +- TCF error detection packet: The TCF error detection packet is used to notify the opposite FA of the TCF error; +- FA\_busy\_packet: The FA\_busy\_packet is used to notify the T-FA that the R-FA has received the image signal from T-FA; +- FA\_non\_busy\_packet: The FA\_non\_busy\_packet is used to notify the T-FA that the R-FA has received the MCF, RTP or PIP frame from R-FAX. + +#### 2) T.30\_DATA: + +- T.30\_DATA conforms to T.38; + +Packets defined in T.38 but not used in the present document: + +- Training packet; +- V.21 Preamble Flags packet. + +### 7.2.2 Interactions between and interventions within the FAs + +Interactions between the FAs and between FA and TAF are necessary: + +- where the content of the protocol packets, except NSF and NSC, shall be aligned with the capabilities of the supporting the UMTS PLMN (e.g. figure D.5); +- where the hardware flow control of V.24 shall be adopted for the flow control between the FA and the TAF (refer to 3GPP TS27.002); +- read the facsimile coded data from the buffer, for transmission across the radio interface using the appropriate FA protocol packets (see annex A); +- during the transmission of facsimile coded data where the document content is transcoded to save transmission capacity at the radio interface (see subclause 7.2.4.1); +- write the facsimile coded data received across the radio interface into a buffer at the R-FA; +- where the T-FA distinguishes the phase at the R-FA by using FA\_busy\_packet and FA\_non\_busy\_packet (see subclause 7.2.1). + +To perform the necessary interactions, the FAs at the UE side and at the MSC/IWF side shall monitor the BCS frames (commands/responses) and the facsimile coded data exchanged between the two facsimile terminals and perform the actions detailed below: + +- receive the BCS frames from the associated facsimile terminal discarding the BCS frames repetitively received due to time-out in the facsimile terminal; +- store the BCS frames completely received from the associated facsimile terminal; +- change information elements of the BCS frames indicating capabilities which may not be supported by the PLMN (e.g. figure D.5); +- change BCS frames received from the associate FAX into FA protocol packets, and transmit it to the opposite FA (see annex A and refer to ITU-T Recommendations T.38); +- change FA protocol packets received from the opposite FA into BCS frames, and transmit it to the associate FAX (see annex A and refer to ITU-T Recommendations T.38); +- transcode the normal facsimile coded data received from the T-FAX and store the data into a buffer in the T-FA (see subclause 7.2.4.1); + +Intervention with in the associated facsimile are necessary: + +- control the half duplex connections between the FA and the associated facsimile terminal (refer to ITU-T Recommendation T.30); +- perform phasing/training with the associated facsimile terminal (refer to ITU-T Recommendation T.30). + +- transmit the BCS frames to the associated facsimile terminal autonomously repeating the BCS frames towards the accepting facsimile terminal if necessary after time-out or on request by the CRP (e.g. figure D.4); +- where BCS frames shall be repeated autonomously by the FA after a time-out when no response has been received from the associated facsimile terminal (e.g. figure D.18); +- transmit/receive the ITU-T Recommendation T.30 training check frames (TCF) to/from the associated facsimile terminal (refer to ITU-T Recommendation T.30); +- read and reverse transcoding of the buffered normal facsimile coded data and transmitting them to the associated Facsimile terminal (see subclause 7.2.4.1); +- select a appropriate dummy signal (i.e. PPR, FTT, RTC, RTP) : For example, the dummy signal shall be sent to the T-FAX in order to avoid T.30 timer time-out at the turn of phases (e.g. figure D.7); +- adjust the time interval between the transmitted BCS frames (e.g. figure D.5); +- adjust the time interval between receiving a BCS frame and transmitting a response to it (e.g. figure D.14); + +The support of guard tones by the FA in the MSC/IWF is an implementation option. + +### 7.2.3 BCS phase + +#### 7.2.3.1 BCS command/response procedures + +The ITU-T Recommendation T.30 procedures are segmented in sections of associated BCS commands and responses. Any command sent by a facsimile terminal shall be answered by an appropriate BCS response (refer to Appendix III in ITU-T Recommendation T.30). To guarantee that the transmission and reception of responses have the correct timing, the response time after reception of a previous command shall be 75m seconds, when the opposite FA is not busy. When the opposite FA is busy the corresponding timer shall be extended to 2,4 seconds. + +According to the command/response relationship, the FA receiving a BCS command from its associated facsimile terminal is called the commanding FA. Similarly, the FA receiving a BCS response is called the responding FA. + +The FA shall not transmit the preamble from the associated FAX to the radio network. The opposite FA shall record the BCS frame received from the other FA and transmit the preamble and procedure signal to the associated facsimile within the proper timing. The procedures are as follows: + +- 1) BCS command procedures; A BCS command which has been received correctly from the associated facsimile terminal, is stored within the commanding FA. Any forwarding of BCS commands repetitively received from the facsimile terminal is further on inhibited. If an error occurs during the reception of the BCS command from the associated facsimile terminal, the commanding FA shall re-transmit the previously transmitted procedure signal to the associated FAX and request the proper procedure signal. The commanding FA transmits the received BCS frame using "IFP packets" to the radio network. The commanding FA shall not transmit the incorrect procedure signal received from the associated FAX to the radio network. + +Contiguously received parts of a BCS command packet received from the radio interface are stored in the responding FA. The stored complete BCS command is used for autonomous transmissions towards the associated facsimile terminal which may start at the earliest possible time according to ITU-T Recommendation T.30. + +The responding FA receiving "IFP packets" checks their correct sequence and starts reassembling the BCS command and transmits it when it has been completely received and no sequence error has been detected. All IFP packets except IFP packets for the next procedure are ignored. The sequence has to be reconstituted at the responding FA before sending it to the associated facsimile terminal. + +- 2) BCS response procedures; A BCS response which has been received correctly from the associated facsimile terminal, is stored within the responding FA. + +If an error occurs during the reception of the BCS response from the associated facsimile terminal, the responding FA shall re-transmit the previously transmitted procedure signal to the associated FAX and request the proper procedure signal. The responding FA shall not transmit the incorrect procedure signal received from the associated facsimile to the radio network. + +Contiguously received parts of a BCS response received from the radio interface are stored in the commanding FA. The stored complete BCS response is used for autonomous answering towards the associated facsimile terminal which may start at the earliest possible time according to ITU-T Recommendation T.30. + +After transmission of a response towards the FA/fax terminals by the FA function, after which the FA function waits for message data (CFR, CTR, MCF after MPS, PPS\_MPS, PPS\_NULL, ERR after EOR\_MPS, EOR\_NULL) a repeated BCS command shall be locally responded, without transferring a preamble element towards the radio link. + +The FA shall take care of the control of the local modem. The condition is derived from the reception of certain FA protocol elements. Additionally, there shall be a control of the half duplex transmission path towards the associated facsimile terminal. For that purpose, the receiver signal is monitored and the transmitter is activated, only if no receive signal is active. + +#### 7.2.3.2 Compatibility checking + +Some features shall not be supported in the UMTS PLMN environment. The FA is in charge of dealing with such compatibility checking which is carried out by monitoring certain BCS frames (DIS/DTC). + +- Group 1 and group 2 equipments shall not be supported by the Teleservice as described in the present document. +- Error limiting mode shall not be supported. +- Only standard 300 bit/s Binary Coded Signalling shall be supported. For this purpose, the FA shall ignore the 2400 bit/s capability within phase B of the ITU-T Recommendation T.30 procedure by looking for DIS frames from ITU-T Recommendation V.21 modem only. +- The following facsimile message speeds shall be supported: 2400, 4800, 7200, 9600, 12000 and 14400bit/s. For this purpose the FAs are responsible to carry out appropriate actions, e.g. to set the applicable fields in the DIS frame accordingly. +- It is not possible to support non-standard facilities since some of these contain proprietary methods of changing the modem speed that are un-interpretable to the IWF and hence impossible to track. + +#### 7.2.3.3 Training Check + +The training check sequence (TCF) as described in ITU-T Recommendation T.30 is exchanged only locally between the FA and the associated facsimile terminal. The training check sequence sent by the FA shall be transmitted at the earliest possible time, and shall have a duration that complies with the minimum duration requirement of ITU-T Recommendation T.30. Because CFR is not transmitted end to end the T- FA generates CFR or FTT, and sends it to the T-FAX. + +The T-FA shall send CFR to the T-FAX, 2.4s after it received TCF from the T-FAX. + +However in the following cases, the T-FA shall send FTT to the T-FAX instead of CFR (see figure D.7): + +- when it receives the TCF error detection packet from the R-FA; +- when it receives the FTT packet from the R-FA; +- when it recognizes the R-FA busy status by the FA\_busy\_packet. + +(The T-FA shall transmit FTT to avoid the phase difference between the transmitting and the receiving side when the phase is returned to phase B by EOM.) + +This is done by using the FA\_busy\_packet and the FA\_non\_busy\_packet to monitor the state of the R-FA. When the T-FA receives the FA\_busy\_packet it can deduce that the training has been successful on the receiving side. + +As a consequence of this local procedure, the T-FA shall check the received TCF to see whether the quality requirements are satisfied. Depending on the result of that check, the T-FA recognizing a corrupted line shall send FTT instead of CFR. If the T-FA receives corrupted TCF from the T-FAX, it shall transmit the TCF\_error\_detection\_packet to the R-FA. On the other hand, if the R-FA receives the TCF\_error\_detection\_packet from the radio network, it shall transmit a corrupted TCF to the R-FAX (see figure D.7). + +The message transfer phase in the R-FA shall be entered upon reception of CFR. The modem training at transmission speed shall start after the R-FA receives the facsimile coded data if it receives the data within 3 s after the receipt of CFR from the R-FAX (see figures D.5 and D.9). + +The R-FA shall transmit the TSI, DCS to the R-FAX, if it does not receive the facsimile coded data within 3,0 s after the receipt of the CFR from the R-FAX (see figures D.5 and D.9). + +#### 7.2.3.4 Control of transmission rate + +The controlling entity of the FA shall recognize a change of the transmission rate, and in conjunction with this a change of the modem function has to commence. The transmission rate shall be changed only locally, i.e. between the facsimile terminal and the FA at both the MSC/IWF and the UE ends. + +The actual message speed and the modem function are derived from the content of the related BCS frames (DIS/DTC, DCS, CTC). + +There are two methods to decide the transmission rate as follows: + +- Use DIS DCS signal between FAXs (see figures D.4 and D.5); +- Trigger Fallback by the TCF error detection. + +Fallback is triggered both on the transmitting and receiving sides. + +In the case that fallback occurs on the transmitting side, the R-FA shall be notified of the fact by the TCF error detection packet (see figure D.9). + +In the case that fallback occurs on the receiving side, the T-FA shall be notified of the fact by the FTT packet from the R-FA (see figure D.7). + +### 7.2.4 Message phase + +During the message phase (phase C of ITU-T Recommendation T.30) the EOL character shall be detected, (see subclause 4.1.2 of ITU-T Recommendation T.4). The EOL character is a unique code word that may never be found within a valid line of facsimile coded data, and is used: + +- to identify the start of the message phase; +- to control the transcoding procedure; +- to mark the end of the message phase (6 consecutive EOLs). + +If the R-FA has stored more than 0,28 kbyte of facsimile coded data and detected two or more EOLs in the data, then the R-FA shall send the FA\_busy\_packet to the T-FA. After the R-FA receives MCF from the R-FAX, the R-FA shall send the FA\_non\_busy\_packet to the T-FA. The R-FA shall notify the T-FA of the state of the reception side by sending the FA\_busy\_packet or the FA\_non\_busy\_packet to avoid that the phase at the T-FA proceeds the next phase (as a result of EOP, MPS, EOM, CTC, PPS-Q, EOR-Q, RR) while the R-FA is still busy in the current phase. + +#### 7.2.4.1 Message Transcoding + +To save transmission capacity at the radio interface the content of the document shall be transcoded. This applies only when using the normal facsimile data transfer. This does not apply when using the ITU-T Recommendation T.30 error correction mode. + +The facsimile coded data received by the T-FA from the T-FAX is transcoded and transmitted to the corresponding R-FA across the radio interface. Then it is transcoded and transmitted to the R-FAX by R-FA. + +The transcoding is based on the minimum line length capability of the T.30 protocol for the normal facsimile data transfer. According to this the transmitting facsimile terminal has to fill up each coded scan line with FILL information to conform to this requirement (refer to ITU-T Recommendation T.4). + +To do so, the FA associated with the T-FAX shall force this to use (at least) the standard value of 20 ms by replacing the applicable parameter value of the exchanged DIS/DTC messages. All FILL information of the facsimile coded data received from the FAX shall be deleted prior to forwarding the data across the radio interface. The FA associated with + +the R-FAX shall recognize and store the originally requested minimum line length to be able to regenerate to correct line length. + +It should be noted that ITU-T Recommendation T.4 document coding may be 1-dimensional or 2-dimensional and, in addition, uncompressed. The FAs shall take care of this when transcoding the document content. + +#### 7.2.4.2 Generation of the normal data packet + +This is specified in ITU-T Recommendations T.38 and X.691. X.691 provides details on octet alignment. + +#### 7.2.4.3 Generation of the error correction data packet + +This is specified in ITU-T Recommendations T.38 and X.691. X.691 provides details on octet alignment. + +#### 7.2.4.4 Normal facsimile data + +The T-FA starts the message phase by transmitting CFR or MCF to the T-FAX. The R-FA enters the message phase by receiving CFR or MCF from the R-FAX. + +- If the R- FA does not receive the facsimile coded data from the radio network within 3s of receiving CFR from the R-FAX, it shall re-transmit a preamble of 1.0s and the previously transmitted TSI, DCS to the R-FAX after changing the modem to V.21. +- If the R- FA does receive the facsimile coded data from radio network within 3s of receiving CFR from the R-FAX, it shall transmit the training to the R-FAX after changing the modem to V.17, V.27ter or V. 29. +- If the R-FA does not receive the facsimile coded data from the radio network within 3s of receiving MCF from the R-FAX, it shall re-transmit a preamble of 1.0s and the previously transmitted MPS to the R-FAX after changing the modem to V.21. +- If the R-FA does receive the facsimile coded data from the radio network within 3s of receiving MCF from the R-FAX, it shall transmit the training to the R-FAX after changing the modem to V.17, V.27ter or V. 29. + +Following the training sequence, the R-FA shall transmit FILL towards the R-FAX (see subclause 4.1.2 of ITU-T Recommendation T.4), disregarding all information received from the radio interface, until an EOL character is detected, which shall mark the beginning of the image data (see figure 1 of ITU-T Recommendation T.4). + +If due to a preceding error the message phase may not be entered, the training sequence shall be aborted when a new IFP packet is received by the T-FA. + +#### 7.2.4.5 Error correction facsimile data + +As the facsimile coded data between the FA and the facsimile terminal are structured in HDLC frames, the handling of this procedure segment shall exploit such formatting. The content of such an HDLC frame is called a block (refer to ITU-T Recommendation T.4 Annex A). + +Each such block is included in the information field of an Error\_Correction\_Data\_Packet of the FA protocol, which is processed for transmission across the radio interface as outlined in subclause 7.2.4.3. + +The message phase at both the PLMN ends is triggered by the transit of a confirmation frame (CFR, MCF, PPR, CTR or ERR) sent by the receiving terminal and marking the end of the BCS phase. + +The PPR that the T-FA sends to the T-FAX has two purposes: + +- PPR is used to request re-transmission of the facsimile coded data. When the T-FA receives corrupted facsimile coded data, it requests correct facsimile coded data to the T-FAX (refer to ITU-T Recommendation T.30). +- In addition to the T.30 purpose, PPR is used to avoid the timer timeout of the T.30 protocol. If the R-FA is busy, the T-FA shall transmit PPR to the T-FAX (see figure D.20). + +If four consecutive PPR are counted within the same "partial page", the BCS phase continues. + +The T-FA shall enter the message phase as described in ITU-T Recommendation T.30. + +- If the R-FA does not receive the facsimile coded data from the radio network within 3s of receiving CFR from the R-FAX, it shall re-transmit a preamble of 1.0s and the previously transmitted TSI, DCS to the R-FAX after changing the modem to V.21. +- If the R-FA does receive the facsimile coded data from radio network within 3s of receiving MCF from the R-FAX, it shall transmit the training to the R-FAX after changing the modem to V.17, V.27ter or V.29. +- If the R-FA does not receive the facsimile coded data from the radio network within 3s of receiving MCF from the R-FAX, it shall re-transmit a preamble of 1.0s and the previously transmitted MPS to the R-FAX after changing the modem to V.21. +- If the R-FA does receive the facsimile coded data from the radio network within 3s of receiving MCF from the R-FAX, it shall transmit the training to the R-FAX after changing the modem to V.17, V.27ter or V.29. + +Following the training sequence, HDLC flags shall be stuffed into the signal sent to the facsimile terminal until a FCD frame is detected, which shall mark the beginning of the image data. + +If due to a preceding error the message phase may not be entered, the training sequence shall be aborted when a new IFP packet is received by the T-FA. + +#### 7.2.4.6 Controlling of facsimile coded data + +The procedure for controlling the FAX data within the FA is described in the following two subclauses. + +It is recommended that the buffer size inside FA is more than 256 kbytes. + +##### 7.2.4.6.1 Transmitting Fax Adapter + +In the T-FA the facsimile coded data being received from the T-FAX are transcoded stripping of FILL information and written into the buffer. + +When data is read out from the buffer, an FA protocol element shall be generated and processed as described in Annex A or ITU-T Recommendation T.38. It is transferred to the R-FA using one of the standard FA protocol element. For that purpose the data shall be segmented into blocks. + +Due to the ARQ techniques of the RLP, the throughput across the radio interface may be less than the message speed between the T-FAX and the T-FA, i.e. the content of the buffer may increase. + +If the throughput at the radio interface is greater than the message speed between the T-FAX terminal and the T-FA (e.g. when the end to end speed is lower than 14400 bit/s), the buffer may be empty most of the time. + +##### 7.2.4.6.2 Receiving Fax Adapter + +In the R-FA, FILL information is transmitted to the R-FAX at the beginning of each page, if necessary, to bridge the gap between the training sequence and the reception of the image data. In case of normal fax data, the duration of the FILL 0's may be increased by only 4,5 s or less. + +The reverse transcoding consists of the insertion of FILL information before the facsimile coded data is forwarded to the facsimile terminal to comply with the recognized minimum line length as defined in ITU-T Recommendation T.4. + +At the beginning of each page, the facsimile coded data to be sent to the facsimile terminal is not read out from the buffer until either at least 2 instances of EOL have been received and the buffer size is at least 0,28 kbytes or, an RTC has been received, which does not depend on the end-to-end data transfer rate. + +###### 7.2.4.6.2.1 Fill insertion method for NON- ECM + +The R-FA controls FILL insertion according to the accumulation value of image signals (see figure D.11). + +The condition for starting FILL insertion: + +- when the pix memory accumulation value is 0,28 kbytes or less. + +The condition for stopping FILL insertion: + +- when the pix memory value is 0,9 kbytes or more; + +- when the pix memory value is not over 0,9 kbytes and the interval between EOLs (one line period) reaches 4,5 s. + +When the interval between EOL reaches 4,5 s, the R-FA shall stop FILL insertion, and shall transmit EOL and shall start to transmit the next facsimile coded line. If however the pix memory value is below "the forced RTC transmission value"(=7byte or less), the R-FA shall send RTC to the R-FAX to force end of Phase C. Then it shall wait for a post-message (EOP, EOM, MPS) to be received from the air interface. + +###### 7.2.4.6.2.2 Flag insertion method for ECM + +The R-FA controls Flag insertion according to the accumulation value of the image signals(see figure D.13). + +The condition for starting Flag insertion: + +- when pix memory accumulation value is 0,28 kbytes or less. + +The condition for stopping Flag insertion: + +- when the pix memory value is 0,9 kbytes or more. + +### 7.2.5 Disconnect procedure + +The T-FA sends the MCF frame to the T-FAX after receiving the FA\_non\_busy\_packet from the R-FA. The T- FAX sends the DCN frame (see ITU-T Recommendation T.30) to the T-FA after receiving the MCF frame. The T-FA, upon detection of the DCN frame sent by the T-FAX to indicate the end of the facsimile transmission, shall initiate the disconnect procedure. The T-FA transmits the DCN packet to the R-FA after receiving the DCN frame from the T-FAX, while the R-FA transmits the DCN frame to the R-FAX after receiving the DCN packet. + +### 7.2.6 Timeouts + +The T.30 timer between the T-FAX and the T-FA, and the T.30 timer between the R-FAX and the R-FA are independent of each other. Therefore, the overall fax adaptation function is in principle bound to the timing constraints associated with the associated FAX ITU-T Recommendation T.30 procedure. This means that, no matter of the reference configuration used at the mobile station, the progress of the call shall be mainly subject to the ITU-T Recommendation T.30 typical timing protections, settled externally. + +However, due to the specific conditions caused by the UMTS PLMN system, there is the need for a special support with respect to BCS command repetitions as explained above. For that purpose, the FAs shall provide means for local time-out. The timer shall be started and stopped as described in annex D (see table D.2). + +# --- 8 Use of terminal adaptation functions + +The protocol stack of the connection type is shown in figure 4. + +The TAFs described in 3GPP TS 27.002 for asynchronous bearer capabilities in the non-transparent mode. The interchange signalling mapping is in accordance with 3GPP TS 27.002. + +## 8.1 Principles of terminal adaptation functions + +The TAF, located at both PLMN ends, is in charge of: + +- call set-up, in particular the BC negotiation; +- establishment and maintenance of a Layer2 protocol link between the FA and the TAF according to 3GPP TS 27.002, where applicable; +- establishment and maintenance of an L2RCOP link between the TAFs according to 3GPP TS 27.002; +- initiation of the In-Call Modification (ICM) procedure. + +The basic approach of the present document for facsimile group 3 is: + +- to use the network support of BS 20 NT as defined in 3GPP TS 27.001, 3GPP TS 27.002 and 3GPP TS 29.007. + +## 8.2 Specific TAFs for facsimile service + +In order to perform the procedures described in the present document, the UE and the IWF environment shall be designed to transmit and receive facsimile data continuously with flow control. This specifically applies between RLP entities, L2RCOP (within TAF) entities, and between the FA and the TAF entities within the UE or the IWF. + +Furthermore, the RLP entity shall be able to make error recovery by using the SREJ command/response. + +# --- 9 Signalling aspects + +3GPP TS 27.002 identifies the bearer capability requirements to be supported by the terminal adaptation function in the MT (see 3GPP TS 27.001 for BC and HLC coding). The specific signalling requirements are those for "speech" and "facsimile group 3" or "facsimile group 3" only, respectively. The MT indicates in the call set up request the requirements, e.g. first speech, second facsimile by sending the bearer capability information element(s) in the appropriate order. For an "auto calling" facsimile request, the facsimile group 3 bearer capability is sent as the first or the only bearer capability for Teleservice 61 or 62, respectively. + +For interworking between Teleservice 61 and Teleservice 62, refer to 3GPP TS 22.003 and 3GPP TS 27.001. + +## 9.1 Handling of tonal signals + +Because the ITU-T defined service uses modems, there are some signals received from the analogue link at the MSC/IWF and (where used) the FA which do not have a direct binary representation. + +These signals are the modem called (CED) and calling (CNG) tones sent at the start of each fax data phase of the call. These tonal signals shall be used for the selection of ATD or ATA. No later than 3 sec after connecting the fax apparatus to the line the FA/UE is able to determine the AT command. If a CNG tone or nothing is detected by the FA/UE the mobile fax station is the calling station, if a CED tone or a BCS signal frame is detected by the FA/UE the mobile fax station is the called station. If the associate fax is the calling station, the FA shall transmit ATD toward the TAF. If the associate fax is the called station, the FA shall transmit ATA toward the TAF. + +After the link of the FA\_protocol is established, these tonal signals shall be sent to the opposite FA as the IFP\_packet(CNG,CED). The FA receiving the FA\_packet(CNG,CED) shall generate the tonal signal and transmit the signal toward the associated facsimile terminal.(see figure D.3) + +## 9.2 Call establishment + +### 9.2.1 Mobile terminated call + +The call may be set-up manually or automatically by the PSTN facsimile group 3. + +#### 9.2.1.1 Speech then facsimile + +Refer to the diagrams in figures C.1a and C.1b. In both of the figures, the initial call setup is mobile terminated. In figure C.1a, the DCD is also mobile terminated (MT), while the DCD in figure C.1b is mobile originated (MO). + +The connection of the FA to the TAF causes the initialization between the FA and the TAF. At this time, the setting of speech/facsimile call should be done in the FA. The operation of the FA for the speech/facsimile call setting is implementation dependent. + +At first, the FA at the UE shall turn on circuit 108/2 and circuit 105. After that, the TAF at the UE shall turn on circuit 106 and circuit 107 toward the FA. The FA which detected ON condition of circuit 106 and circuit 107 requires facsimile call of the TAF by appropriate AT command (e.g. AT+CMOD=1, AT+FCLASS=1, 2). If the AT command is recognized, the TAF shall transmit "OK" to the FA as a result code. + +In order to make the transition from the speech phase to the facsimile phase, the MODIFY message shall be initiated by the MMI at the facsimile terminal, which shall result in the establishment of RLP across the radio interface and connection to the line of the FA/IWF. + +When the facsimile machine is connected to the line by manual intervention, the facsimile machine should transmit tonal signal (CNG or CED) toward the FA. The FA shall select ATD or ATA according to the rules in subclause 9.1 and transmit ATD or ATA toward the TAF. + +On detecting ATD or ATA, the TAF shall transmit the MODIFY message that has G3FAX ability as a bearer capability. After that, RLP and L2RCOP shall be established across the radio interface. Once the connection is established, circuit 109 shall be clamped to the ON condition by the TAF at the IWF. Then, the FA protocol shall be started between the FAs. + +#### 9.2.1.2 Auto answer + +Refer to the diagram in figure C.2. The connection of the FA to the TAF causes the initialization between the FA and the TAF. At first, the FA at the UE shall turn on circuit 108/2 and circuit 105. After that, the TAF at the UE shall turn on circuit 106 and circuit 107 toward the FA. The FA which detected ON condition of circuit 106 and circuit 107 shall require facsimile call of the TAF by appropriate AT command (e.g. AT+FCLASS=1, 2). If the AT command is recognized, the TAF shall transmit "OK" to the FA as a result code. + +When the MT receives a call in the condition finished the above initialization, the TAF shall transmit the result code "RING" toward the FA. "RING" shall cause a ring current to be sent to the facsimile terminal. The FA shall transmit ATA toward the TAF when the FAX terminal connects to the line and begins behaviour of receiving. On receiving ATA, the FA shall transmit a signal that notifies the calling side that called facsimile terminal connected to the line. + +Once the connection is established, circuit 109 shall be clamped to the ON condition by the TAF at the IWF. Then, the FA protocol shall be started between the FAs. + +### 9.2.2 Mobile originated calls + +The PSTN facsimile group 3 terminal may manually or automatically answer the call originated by the mobile station. + +#### 9.2.2.1 Speech then facsimile + +Refer to the diagrams in figure C.3a and figure C.3b. In both of the figures, the initial call setup is mobile originated. In figure C.3a the DCD is also MO, while in figure C.3b the DCD is MT. + +The connection of the FA to the TAF causes the initialization between the FA and the TAF. At this time, the setting of speech/facsimile call should be done in the FA. The operation of the FA for the speech/facsimile call setting is implementation dependent. + +At first, the FA at the UE shall turn on circuit 108/2 and circuit 105. After that, the TAF at the UE shall turn on circuit 106 and circuit 107 toward the FA. The FA which detected ON condition of circuit 106 and circuit 107 requires facsimile call of the TAF by appropriate AT command (e.g. AT+CMOD=1, AT+FCLASS=1, 2). If the AT command is recognized, the TAF shall transmit "OK" to the FA as a result code. + +In order to make the transition from the speech phase to the facsimile phase, the MODIFY message shall be initiated by the MMI at the facsimile terminal, which shall result in the establishment of RLP across the radio interface and connection to line of the FA/IWF. + +When the facsimile machine is connected to the line by manual intervention, the facsimile machine should transmit tonal signal (CNG or CED) toward the FA. The FA shall select ATD or ATA according to the rules in subclause 9.1 and transmit ATD or ATA toward the TAF. On detecting ATD or ATA, the TAF shall transmit the MODIFY message that has G3FAX ability as a bearer capability. After that, RLP and L2RCOP shall be established across the radio interface. Once the connection is established, circuit 109 shall be clamped to the ON condition by the TAF at the IWF. Then, the FA protocol shall be started between the FAs. + +#### 9.2.2.2 Auto calling + +Refer to the diagram in figure C.4. The FA at the UE shall turn on circuit 108/2 and circuit 105 when the fax apparatus is connected to the line by manual intervention. After that, the TAF at the UE shall turn on circuit 106 and circuit 107 toward the FA. The FA which detected ON condition of circuit 106 and circuit 107 shall require facsimile call of the TAF by appropriate AT command (e.g. AT+FCLASS=1, 2). If the AT command is recognized, the TAF shall transmit "OK" to the FA as a result code. + +The FA shall make ATD [Dial signal] from DTMF dialling information and transmit ATD[Dial signal] toward the TAF. On detecting ATD [Dial signal], the TAF shall transmit the call set-up signal that has G3FAX ability as a bearer + +capability. When the call is answered, the synchronization process shall be started and the RLP shall be established across the radio interface. + +After that, RLP and L2RCOP are established across the radio interface. Once the connection is established, circuit 109 shall be clamped to the ON condition by the TAF at the IWF. Then, the FA protocol is started between the FAs. + +#### 9.2.2.3 Manual calling + +Refer to the diagram in figure C.5. The connection of the FA to the TAF causes the initialization between the FA and the TAF. At first, the FA shall turn on circuit 108/2 and circuit 105. After that, the TAF at the UE shall turn on circuit 106 and circuit 107 toward the FA. The FA which detected ON condition of circuit 106 and circuit 107 shall require facsimile call of the TAF by appropriate AT command (e.g. AT+FCLASS=1, 2). If the AT command is recognized, the TAF shall transmit "OK" to the FA as a result code. + +After the initialization of the FA and the TAF, the dialling operation shall be done at the MT. Then, the MT shall transmit the call set-up signal that has G3FAX ability as a bearer capability. + +After that, RLP and L2RCOP shall be established across the radio interface. Once the connection is established, circuit 109 shall be clamped to the ON condition by the TAF at the IWF. Then, the FA protocol shall be started between the FAs. And the fax apparatus is connected to the line by manual intervention. + +# 10 Interworking to fixed networks + +Only PSTN and ISDN are considered, and may be used as transit networks to complement the PLMN in the end-to-end connection between facsimile group 3 terminals (figure 6). + +![Figure 6: Network interworking diagram showing the connection between a FAX terminal and fixed networks (PSTN and ISDN) via a mobile network (RAN, MSC/IWF).](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +The diagram illustrates the network interworking architecture for facsimile group 3 terminals. On the left, a FAX terminal is connected to an FA (Facsimile Adapter). The FA is connected to an MT/TAF (Mobile Terminal/Transceiver and Facsimile Adapter). The MT/TAF is connected to a RAN (Radio Access Network), which is in turn connected to an MSC/IWF (Mobile Switching Center/Interworking Function). The MSC/IWF is connected to two fixed networks: PSTN and ISDN, with a Codec in between. Below the main components, a detailed view of the FA and MT/TAF is shown. The FA contains V.21, V.27ter, Tone handling, FA Protocol Control Monitor, Transcoding Buffers, and CONT P. The MT/TAF contains TAF Handling, RLP L2RCOP Mapping, and CONT P. A dashed box highlights the RLP L2RCOP Mapping function, which is labeled as 'Function corresponding to TAF'. + +Figure 6: Network interworking diagram showing the connection between a FAX terminal and fixed networks (PSTN and ISDN) via a mobile network (RAN, MSC/IWF). + +Figure 6: Network interworking + +## 10.1 Interworking to PSTN + +As the standard access of facsimile group 3 terminals for this Teleservice is a 2-wire analogue interface, all the technical requirements for network interworking to PSTN are identical in principle to those encountered for the terminal connection to the UE. The key functional block is the FA described in clause 7 of the present document. + +As far as network interworking is concerned, the main function to be performed by such a block is the correct managing of a composite modem, in accordance with the requirements of ITU-T Recommendation T.30: + +- ITU-T Recommendation V.21 synchronous mode, as standard facility for all BCS phases; +- ITU-T Recommendation V.27ter for message speeds of 4 800 and 2 400 bit/s; +- ITU-T Recommendation V.29 for message speeds of 9 600 and 7 200 bit/s; +- ITU-T Recommendation V.17 for message speeds of 14 400, 12 000, 9 600, 7 200 bit/s. + +The mechanism for selecting the correct modem is the following: + +- the actual message speed is obtained by detecting the DCS frame (see table 2/ITU-T Recommendation T.30) while in BCS phase; +- on entering the message phase, there is an interchange between the V.21 modem and the actual modem agreed upon between the terminals for message transmission; +- on exiting the message phase (RTC) the ITU-T Recommendation V.21 modem is selected again. + +Times for settling the modem shall be in accordance with the requirements of ITU-T Recommendation T.30. + +## 10.2 Interworking to ISDN + +The use of 3,1 kHz audio bearer capability of ISDN allows for an interworking of PLMN very similar in practice to the scheme for PSTN (figure 6). The FA function shall comply with the description given in clause 7 of the present document. + +# --- Annex A (normative): Structure and contents of the FA protocol elements + +## A.1 Internet Fax Protocol + +This ANNEX is related to the application of the T.38 protocol within the present document. + +Only the following packets are used: + +- T30\_INDICATOR + - CNG + - CED + - TCF error detection (not in T.38) + - FA\_busy\_packet (not in T.38) + - FA\_non\_busy\_packet (not in T.38) +- T30\_DATA + - V.21 channel 2 (except MCF, CFR, RTN, RTP, PIP, PIN, PRI, PPR, NSF, NSC, RR, RNR, ERR) + - V.27 ter 2400 + - V.27 ter 4800 + - V.29 7200 + - V.29 9600 + - V.17 7200 + - V.17 9600 + - V.17 12000 + - V.17 14400 + +In T30\_DATA the maximum length of T.4-Non-ECM/HDLC data is equal to 1 400 octets. + +Aligned Packet Encoding Rule is applied to ASN.1. + +## --- A.2 Facsimile UDP Transport Layer Protocol + +The FEC option and the redundant message option shall not be used. + +## --- A.3 User Datagram Protocol + +The port number at client side is ephemeral (assigned on a call by call basis). The port number at the server side is manually preassigned by the operator. + +## --- A.4 Internet Protocol + +The IP address is not required because a circuit switched connection is used between the UE and IWF. However, IP addresses shall be used in order to be consistent with IP. + +The IP address at UE side and IWF side are assigned by PPP. + +## A.5 Point to Point Protocol + +For the communication between the two FAs IP is provided on top of PPP. + +PPP shall conform to RFC 1662, 1661, 1570 and 1332. + +## A.6 Mapping of FA frames + +Refer also to 3GPP TS 27.002. + +![Figure A.1: Typical frame mapping within FA protocol. This diagram shows the encapsulation of IFP data into PPP frames. The layers from top to bottom are: IFP (Type of message, Field type, IFP-Payload), UDPTL (Header, UDPTL-Payload, No FEC), UDP (Header, UDP-Payload), IP (Header, IP-Payload), and PPP (Flag, Address, Control, Protocol, PPP-Payload, FCS, Flag). Lines connect the IFP payload to the UDPTL payload, UDPTL payload to UDP payload, IP payload to PPP payload, and finally to the PPP-Payload field.](356eb99ab9489bbd647223390a913903_img.jpg) + +Length of typical FAX data is much longer than 1400 Octets + +| | | | | | | | +|-----|-----------------|-------------|---------------------------------|----------|-------------|--------| +| IFP | Type of message | Field type | IFP-Payload<br>(max.1400?Octs?) | | | | +| | | | | | | | +| | UDPTL | Header | UDPTL-Payload | | | No FEC | +| | | | | | | | +| UDP | Header | UDP-Payload | | | | | +| | | | | | | | +| IP | Header | IP-Payload | | | | | +| | | | | | | | +| PPP | Flag | Address | Control | Protocol | PPP-Payload | | +| | FCS | Flag | | | | | + +Figure A.1: Typical frame mapping within FA protocol. This diagram shows the encapsulation of IFP data into PPP frames. The layers from top to bottom are: IFP (Type of message, Field type, IFP-Payload), UDPTL (Header, UDPTL-Payload, No FEC), UDP (Header, UDP-Payload), IP (Header, IP-Payload), and PPP (Flag, Address, Control, Protocol, PPP-Payload, FCS, Flag). Lines connect the IFP payload to the UDPTL payload, UDPTL payload to UDP payload, IP payload to PPP payload, and finally to the PPP-Payload field. + +Figure A.1: Typical frame mapping within FA protocol + +![Figure A.2: Typical frame mapping between FA Protocol and RLP. This diagram shows the mapping of FA Protocol-PDU into L2RCOP and then into RLP Ver.2 frames. The FA Protocol-PDU is split into multiple L2RCOP segments, each containing a status octet (S) and a payload (L2RCOP-Payload#1, #2, #3). These segments are then encapsulated into RLP Ver.2 frames, which have a Header, RLP-Payload, and FCS. A note indicates that 'S' means 'Status octet'.](db5ab5d386827a5d5f5fad0f45612b90_img.jpg) + +| | | | | | | | +|-------------|-----------------|------------------|--------------|------------------|--------------|------------------| +| FA Protocol | FA Protocol-PDU | | | | | | +| | | | | | | | +| L2RCOP | S | L2RCOP-Payload#1 | S or Nothing | L2RCOP-Payload#2 | S or Nothing | L2RCOP-Payload#3 | +| | | | | | | | +| RLP Ver.2 | Header | RLP-Payload | FCS | ... | | | +| | | | | | | | + +S means "Status octet" + +Figure A.2: Typical frame mapping between FA Protocol and RLP. This diagram shows the mapping of FA Protocol-PDU into L2RCOP and then into RLP Ver.2 frames. The FA Protocol-PDU is split into multiple L2RCOP segments, each containing a status octet (S) and a payload (L2RCOP-Payload#1, #2, #3). These segments are then encapsulated into RLP Ver.2 frames, which have a Header, RLP-Payload, and FCS. A note indicates that 'S' means 'Status octet'. + +Figure A.2: Typical frame mapping between FA Protocol and RLP + +# Annex B (informative): Abbreviations from ITU-T Recommendation T.30 and T.4 + +**Table B.1: Abbreviations from ITU-T Recommendation T.30** + +| Abbreviation | Function | Signal format | T.30 standard | T.30 err.corr. | +|--------------|----------------------------------------|---------------|---------------|----------------| +| CED | Called station identification | 2100 Hz | X | X | +| CFR | Confirmation to receive | X010 0001 | X | X | +| CRP | Command repeat | X101 1000 | X | X | +| CIG | Calling subscriber identification | 1000 1000 | X | X | +| CNG | Calling tone | 1100 Hz | X | X | +| CSI | Called subscriber identification | 0000 0010 | X | X | +| CTC | Continue to correct | X100 1000 | | X | +| CTR | Response to continue to correct | X010 0011 | | X | +| DCN | Disconnect | X101 1111 | X | X | +| DCS | Digital command signal | X100 0001 | X | X | +| DIS | Digital identification signal | 0000 0001 | X | X | +| DTC | Digital transmit command | 1000 0001 | X | X | +| EOM | End of message | X111 0001 | X | | +| EOP | End of procedure | X111 0100 | X | | +| EOR | End of retransmission | X111 0011 | | X | +| ERR | Response to end of retransmission | X011 1000 | | X | +| FCD | Facsimile coded data | 0110 0000 | | X | +| FCF | Facsimile control field | --- | X | X | +| FCS | Frame checking sequence | 16 bits | X | X | +| FIF | Facsimile information field | --- | X | X | +| FTT | Failure to train | X010 0010 | X | X | +| MCF | Message confirmation | X011 0001 | X | X | +| MPS | Multi-page signal | X111 0010 | X | | +| NSC | Non-standard facilities command | 1000 0100 | X | X | +| NSF | Non-standard facilities | 0000 0100 | X | X | +| NSS | Non-standard set-up | X100 0100 | X | X | +| PIN | Procedural interrupt negative | X011 0100 | X | X | +| PIP | Procedural interrupt positive | X011 0101 | X | X | +| PIS | Procedure interrupt signal | 462 Hz | X | X | +| PPR | Partial page request | X011 1101 | | X | +| PPS | Partial page signal | X111 1101 | | X | +| PRI | Procedure interrupt | X111 XXXX | X | | +| RCP | Return to control for partial page | 0110 0001 | | X | +| RNR | Receive not ready | X011 0111 | | X | +| RR | Receive ready | X111 0110 | | X | +| RTN | Retrain negative | X011 0010 | X | X | +| RTP | Retrain positive | X011 0011 | X | X | +| TCF | Training check frame | 0... 1.5s | X | X | +| TSI | Transmitting subscriber identification | X100 0010 | X | X | + +**Table B.2: Abbreviations from ITU-T Recommendation T.4** + +| Abbreviation | Function | Signal format | +|--------------|-------------------|----------------| +| EOL | End of line | 0000 0000 0001 | +| RTC | Return to control | 6 * EOL | + +# Annex C (informative): Procedure examples + +![Sequence diagram for Figure C.1a: Mobile terminated call - speech then facsimile DCD mobile terminated. The diagram shows the interaction between a Facsimile Group3 machine, FA, MT, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3 machine. The process involves call setup, speech phase, and facsimile protocol exchange.](474a819357587e34949a3e110ff19b30_img.jpg) + +The sequence diagram illustrates the following interaction: + +- Facsimile Group3 machine** (facsimile machine) sends an **R** signal to **FA**. +- FA** sends **CT 108/2, CT 105** (1) to **TAF**. +- TAF** responds with **CT 106, CT 107**. +- FA** sends **AT+C MOD=1** and **AT+FCLASS=X** to **TAF**. +- TAF** responds with **OK** and **RING**. +- TAF** sends **CALL SETUP** to **MSC/IWF**. +- MSC/IWF** sends **ANSWER** to **TAF**. +- Facsimile Group3 machine** (2) connects to the line. +- FA** sends **CED** to **Facsimile Group3 machine**. +- Facsimile Group3 machine** sends **ATA** to **FA**. +- FA** sends **MODIFY** to **MSC/IWF**. +- MSC/IWF** responds with **MODIFY COMPLETE**. +- MSC/IWF** sends **RLP** and **L2RCOP** to **FA**. +- Facsimile Group3 machine** (2) connects to the line. +- FA** sends **CNG** to **Facsimile Group3 machine**. +- Facsimile Group3 machine** sends **CED** to **FA**. +- FA** sends **CONNECT** and **CT 109** (4) to **TAF**. +- TAF** sends **CT 109** to **FA**. +- FA** sends **CNG** to **Facsimile Group3 machine**. +- FA** and **MSC/IWF** exchange **FA protocol**. + +Sequence diagram for Figure C.1a: Mobile terminated call - speech then facsimile DCD mobile terminated. The diagram shows the interaction between a Facsimile Group3 machine, FA, MT, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3 machine. The process involves call setup, speech phase, and facsimile protocol exchange. + +105, 106, 107, 108/2, 109: circuits according to ITU-T Recommendation V.24 + +(1) speech/fax call setting + +(2) manual intervention + +(3) triggered by ATA + +(4) locally generated by the IWF + +**Figure C.1a: Mobile terminated call - speech then facsimile DCD mobile terminated** + +![Sequence diagram for Mobile terminated call - speech then facsimile DCD mobile originated. The diagram shows the interaction between a Facsimile Group3 facsimile machine, FA, MT, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3. It details the call setup, speech phase, and facsimile data transfer phases.](dd5771673aececa53d42ece89218299d_img.jpg) + +The sequence diagram illustrates the following interaction: + +- Initial Setup:** The Facsimile Group3 facsimile machine sends (1) CT 108/2, CT 105 to the MT. The MT responds with CT 106, CT 107, AT+C MOD=1, AT+F CLASS=X, and OK. The MT then sends a RING to the FA. +- Call Setup:** The FA sends CALL SETUP to the RAN. The RAN sends ANSWER to the MSC/IWF. The MSC/IWF sends ANSWER to the PSTN. The PSTN sends ANSWER to the Facsimile Group3. +- Speech Phase:** A 'Speech phase' (highlighted in cyan) occurs between the MT and the Facsimile Group3. +- Facsimile Setup:** The Facsimile Group3 sends (2) Fax app. conn.to line to the PSTN. The PSTN sends CNG to the MT. The MT sends ATD to the FA. The FA sends (3) MODIFY to the MSC/IWF. The MSC/IWF responds with MODIFY COMPLETE. The MSC/IWF then sends RLP, L2RCOP, and (4) CT 109 to the MT. The MT sends CONNECT to the FA. The FA sends CT 109 to the MT. The MT sends CED to the Facsimile Group3. The Facsimile Group3 sends (2) Fax app. conn.to line to the PSTN. The PSTN sends CED to the MT. The MT sends CNG to the Facsimile Group3. +- FA Protocol:** A 'FA protocol' (highlighted in orange) occurs between the MT and the MSC/IWF. + +Sequence diagram for Mobile terminated call - speech then facsimile DCD mobile originated. The diagram shows the interaction between a Facsimile Group3 facsimile machine, FA, MT, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3. It details the call setup, speech phase, and facsimile data transfer phases. + +105, 106, 107, 108/2, 109: circuits according to ITU-T Recommendation V.24 + +(1) speech/fax call setting + +(2) manual intervention + +(3) triggered by ATD + +(4) locally generated by the IWF + +**Figure C.1b: Mobile terminated call - speech then facsimile DCD mobile originated** + +![Sequence diagram for mobile terminated call - auto answer. The diagram shows the interaction between a Facsimile Group3 facsimile machine, FA, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3. The process involves call setting, ringing, connection to line, and data transfer via RLP and L2RCOP protocols.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +The sequence diagram illustrates the interaction for a mobile terminated call with auto answer. The participants are: Facsimile Group3 facsimile machine (left), FA, TAF, RAN, MSC/IWF (containing TAF and FA), PSTN, and Facsimile Group3 (right). The sequence of messages is as follows: + +- (1) The FA sends CT 108/2, CT 105 to the TAF. The TAF responds with CT 106, CT 107. The FA then sends AT+FCLASS=X to the TAF, which responds with OK. +- The PSTN sends a CALL SETUP message to the MSC/IWF. +- The MSC/IWF sends a RING message to the FA. The FA sends a Ring current to the facsimile machine. +- (2) The facsimile machine sends a message to connect to line. The FA sends a CED signal to the TAF. +- (3) The TAF sends an ATA message to the MSC/IWF, which triggers the ANSWER message to the PSTN. The PSTN sends a CNG signal to the MSC/IWF. +- The MSC/IWF sends RLP and L2RCOP messages to the TAF. +- (4) The TAF sends a CONNECT message to the FA, which in turn sends CT 109 to the facsimile machine. The TAF also sends CT 109 to the MSC/IWF. +- The FA sends a CNG signal to the facsimile machine. +- The MSC/IWF sends a CED signal to the PSTN. +- Finally, a long orange bar labeled "FA protocol" spans across the interaction between the FA and the MSC/IWF. + +Sequence diagram for mobile terminated call - auto answer. The diagram shows the interaction between a Facsimile Group3 facsimile machine, FA, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3. The process involves call setting, ringing, connection to line, and data transfer via RLP and L2RCOP protocols. + +105, 106, 107, 108/2, 109: circuits according to ITU-T Recommendation V.24 + +- (1) fax call setting +- (2) manual or automatic operation +- (3) triggered by ATA +- (4) locally generated by the IWF + +**Figure C.2: Mobile terminated call - auto answer** + +![Sequence diagram for mobile originated call - speech then facsimile DCD mobile terminated. The diagram shows the interaction between a Facsimile Group3 machine, FA, TAF, MT, RAN, MSC/IWF, PSTN, and another Facsimile Group3 machine. It details the call setup, speech phase, and facsimile protocol exchange.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +The sequence diagram illustrates the following interaction: + +- Facsimile Group3 machine** (left) sends **(1) CT 108/2, CT 105** to **FA**. +- FA** responds with **CT 106, CT 107**. +- FA** sends **AT+CMOD=1** and **AT+FCLASS=X** to **TAF**. +- TAF** responds with **OK**. +- TAF** sends **CALL SETUP** to **MSC/IWF**. +- MSC/IWF** sends **ANSWER** to **TAF**. +- A **Speech phase** (cyan bar) occurs between **TAF** and **Facsimile Group3** (right). +- Facsimile Group3** (right) sends **(2) Fax app. conn.to line** to **PSTN**. +- PSTN** sends **CED** to **FA**. +- FA** sends **ATA** to **TAF**. +- TAF** sends **(3) MODIFY** to **MSC/IWF**. +- MSC/IWF** responds with **MODIFY COMPLETE**. +- MSC/IWF** sends **RLP** and **L2RCOP** to **TAF**. +- TAF** sends **CONNECT** and **CT 109 (4)** to **FA**. +- FA** sends **CNG** to **Facsimile Group3** (left). +- Facsimile Group3** (right) sends **CED** to **PSTN**. +- PSTN** sends **CNG** to **Facsimile Group3** (right). +- An **FA protocol** (orange bar) occurs between **FA** and **MSC/IWF**. + +Sequence diagram for mobile originated call - speech then facsimile DCD mobile terminated. The diagram shows the interaction between a Facsimile Group3 machine, FA, TAF, MT, RAN, MSC/IWF, PSTN, and another Facsimile Group3 machine. It details the call setup, speech phase, and facsimile protocol exchange. + +105, 106, 107, 108/2, 109: circuits according to ITU-T Recommendation V.24 + +(1) speech/fax call setting + +(2) manual intervention + +(3) triggered by ATA + +(4) locally generated by the IWF + +**Figure C.3a: Mobile originated call - speech then facsimile DCD mobile terminated** + +![Sequence diagram for mobile originated call - speech then facsimile DCD mobile originated. The diagram shows the interaction between a Facsimile Group3 facsimile machine, FA, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3. It details the call setup, speech phase, and facsimile protocol exchange.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +The sequence diagram illustrates the following interaction: + +- Initial Setup:** The Facsimile Group3 facsimile machine sends (1) CT 108/2, CT 105 to the FA. The FA responds with CT 106, CT 107. The FA then sends AT+CMOD=1 and AT+FCLASS=X to the TAF. The TAF responds with OK. +- Call Setup:** The FA sends (2) CALL SETUP to the RAN. The RAN sends ANSWER to the MSC/IWF. The MSC/IWF sends ANSWER to the PSTN. The PSTN sends ANSWER to the remote Facsimile Group3. +- Speech Phase:** The remote Facsimile Group3 sends (2) Fax app. conn.to line to the PSTN. The PSTN sends CNG to the FA. The FA sends ATD to the TAF. The TAF sends (3) MODIFY to the MSC/IWF. The MSC/IWF responds with MODIFY COMPLETE. The MSC/IWF then sends RLP and L2RCOP. The FA sends CONNECT to the TAF. The TAF sends (4) CT 109 to the FA. The FA sends CT 109 to the Facsimile Group3 facsimile machine. The Facsimile Group3 facsimile machine sends CED to the FA. +- Facsimile Protocol:** The FA sends (2) Fax app. conn.to line to the TAF. The TAF sends CED to the MSC/IWF. The MSC/IWF sends CNG to the FA. The FA sends the FA protocol to the Facsimile Group3 facsimile machine. + +Sequence diagram for mobile originated call - speech then facsimile DCD mobile originated. The diagram shows the interaction between a Facsimile Group3 facsimile machine, FA, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3. It details the call setup, speech phase, and facsimile protocol exchange. + +105, 106, 107, 108/2, 109: circuits according to ITU-T Recommendation V.24 + +(1) speech/fax call setting + +(2) manual intervention + +(3) triggered by ATD + +(4) locally generated by the IWF + +**Figure C.3b: Mobile originated call - speech then facsimile DCD mobile originated** + +![Sequence diagram for mobile originated call - auto calling. Lifelines: Facsimile Group3 (mobile), FA, TAF (MT), RAN, TAF (MSC/IWF), FA (MSC/IWF), PSTN, Facsimile Group3 (fixed). The process involves AT commands, call setup, RLP/L2RCOP negotiation, and the start of the FA protocol.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +The sequence diagram illustrates the interaction for a mobile originated call. It starts with the Facsimile Group3 (mobile) sending a 'connect to line' command (1) to the FA. The FA responds with 'CT 108/2, CT 105', followed by 'CT 106, CT 107', 'AT+FCLASS=X', and 'OK'. The mobile then sends 'Dial' and 'CNG' signals. The FA sends 'ATD(Dial)' to the TAF (MT). The TAF (MT) sends 'CALL SETUP' to the TAF (MSC/IWF), which receives an 'ANSWER' from the FA (MSC/IWF). The FA (MSC/IWF) sends 'CED' to the PSTN, which in turn sends 'CNG' to the Facsimile Group3 (fixed). The TAF (MSC/IWF) sends 'CT 109' (2) to the TAF (MT), which responds with 'CONNECT' and 'CT 109'. Finally, the mobile sends 'CED' to the FA, and the FA starts the 'FA protocol' block, which continues until the end of the diagram. + +Sequence diagram for mobile originated call - auto calling. Lifelines: Facsimile Group3 (mobile), FA, TAF (MT), RAN, TAF (MSC/IWF), FA (MSC/IWF), PSTN, Facsimile Group3 (fixed). The process involves AT commands, call setup, RLP/L2RCOP negotiation, and the start of the FA protocol. + +105, 106, 107, 108/2, 109: circuits according to ITU-T Recommendation V.24 + +(1) manual intervention + +(2) locally generated by the IWF + +Figure C.4: Mobile originated call - auto calling + +![Sequence diagram for mobile originated call - manual calling. Lifelines: Facsimile Group3 facsimile machine, FA, TAF (MT), RAN, TAF (MSC/IWF), FA (MSC/IWF), PSTN, Facsimile Group3 (2W). The process involves V.24 circuit exchanges (CT 108/2, 106, 107, 109), AT commands, and network signaling (CALL SETUP, ANSWER, RLP, L2RCOP, FA protocol).](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +The sequence diagram illustrates the interaction for a mobile originated call. It starts with the Facsimile Group3 facsimile machine sending a 'Connect to line' and 'CNG' signal to the FA. The FA then sends a series of messages to the TAF (MT): 'CT 108/2, CT 105' (1), 'CT 106, CT 107' (1), 'AT+FCLASS=X' (1), and 'OK' (1). The TAF (MT) sends 'CALL SETUP' to the TAF (MSC/IWF), which in turn sends 'ANSWER' to the Facsimile Group3 (2W). The Facsimile Group3 (2W) responds with 'CED' to the FA (MSC/IWF). The FA (MSC/IWF) sends 'RLP' and 'L2RCOP' messages to the TAF (MSC/IWF). The TAF (MSC/IWF) sends 'CT 109' (3) to the TAF (MT), which then sends 'CONNECT' and 'CT 109' (3) to the FA. The FA sends 'CED' to the Facsimile Group3 facsimile machine. Finally, a long 'FA protocol' message is exchanged between the FA and the Facsimile Group3 (2W), with a 'CNG' signal also shown. + +Sequence diagram for mobile originated call - manual calling. Lifelines: Facsimile Group3 facsimile machine, FA, TAF (MT), RAN, TAF (MSC/IWF), FA (MSC/IWF), PSTN, Facsimile Group3 (2W). The process involves V.24 circuit exchanges (CT 108/2, 106, 107, 109), AT commands, and network signaling (CALL SETUP, ANSWER, RLP, L2RCOP, FA protocol). + +105, 106, 107, 108/2, 109: circuits according to ITU-T Recommendation V.24 + +(1) fax call setting + +(2) manual intervention + +(3) locally generated by the IWF + +**Figure C.5: Mobile originated call - manual calling** + +![Sequence diagram of mobile originated facsimile transmission showing interactions between Facsimile Group3, FA, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +The diagram illustrates a mobile originated facsimile transmission sequence. On the left, a 'Facsimile Group3' (facsimile machine) sends a DIS message to an FA. The FA forwards it to a TAF, which then sends it to the RAN. The RAN passes it to the MSC/IWF, which then sends it to the PSTN. The PSTN delivers it to the receiving 'Facsimile Group3'. The receiving side responds with DCS, TCF, and CFR messages back through the chain. The sending side receives these and then begins the 'Training facsimile message' transmission. During this transmission, the sending FA sends a '<FA\_busy\_packet>' to the receiving FA via the TAF and MSC/IWF. The receiving FA responds with '<FA\_non\_busy\_packet>'. The transmission concludes with EOP, MCF, and DCN messages. + +Key elements of the sequence: + +- DIS / <DIS>:** Initial identification message from sender to receiver. +- DCS / <DCS>:** Digital Command Signal from receiver to sender. +- TCF / check ok:** Training and Confirmation Facsimile message. A bracket labeled (1) indicates it is triggered by a delayed DCS (75 ms). +- CFR / (2):** Cyclic Forward Response from receiver to sender. A bracket labeled (2) indicates it is triggered by a delayed TCF (2,4 s). +- Training facsimile message:** The main data transmission phase. A green shaded area represents the data flow. +- <FA\_busy\_packet>:** A packet sent from the sending FA to the receiving FA during the training phase. +- <FA\_non\_busy\_packet>:** A response packet sent from the receiving FA to the sending FA. +- EOP / <EOP>:** End of Page message. +- MCF / <MCF>:** Message Confirmation message. +- DCN / <DCN>:** Data Channel Notification message. + +Sequence diagram of mobile originated facsimile transmission showing interactions between Facsimile Group3, FA, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3. + +- (1) triggered by delayed DCS(75 ms) +- (2) triggered by delayed TCF(2,4 s) + +**Figure C.6: Mobile originated facsimile transmission** + +![Sequence diagram for mobile terminated facsimile transmission showing interactions between Facsimile Group3, FA, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +The diagram illustrates the sequence of messages for a mobile terminated facsimile transmission. The participants are: Facsimile Group3 (left), FA, TAF, RAN, MSC/IWF (containing TAF and FA), PSTN, and Facsimile Group3 (right). The sequence starts with DIS and DCS messages. The left Facsimile Group3 sends a DIS to its FA, which is relayed as <DIS> through TAF, RAN, and TAF in the MSC/IWF to the right Facsimile Group3's FA. The right FA responds with DCS, which is relayed back as <DCS> through the same path. The left FA receives the DCS and triggers the TCF message (1). The right FA receives the DCS, checks it (check ok), and then triggers its own TCF message (2). Both TCF messages are followed by CFR. The left Facsimile Group3 then sends a Training FILL facsimile message, which is relayed as <FA busy packet> through the TAF in the MSC/IWF to the right FA. The right FA sends a Training facsimile message. Both sides then send EOP. The left FA sends MCF, which is relayed as <FA non busy packet> through the TAF in the MSC/IWF to the right FA. Finally, both sides send DCN. + +Sequence diagram for mobile terminated facsimile transmission showing interactions between Facsimile Group3, FA, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3. + +- (1) triggered by delayed DCS(75 ms) +- (2) triggered by delayed TCF(2,4 s) + +Figure C.7: Mobile terminated facsimile transmission + +![Sequence diagram for mobile originated facsimile transmission in error correction mode. It shows the interaction between a Facsimile Group3 machine, FA, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3 machine. The process includes DIS, DCS, TCF, CFR, Training, FCD, RCP, PPS, MCF, and DCN signals. Red dashed arrows indicate error recovery packets: <FA_busy_packet> and <FA_non_busy_packet>.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +The diagram illustrates a mobile originated facsimile transmission in error correction mode. The sequence of events is as follows: + +- The Facsimile Group3 machine sends a DIS signal to the FA. +- The FA forwards the DIS signal via the TAF to the RAN, then to the MSC/IWF (TAF), then to the FA, then to the PSTN, and finally to the receiving Facsimile Group3 machine. +- The receiving Facsimile Group3 machine responds with a DCS signal, which is routed back through the PSTN, FA, MSC/IWF (FA), RAN, TAF, and FA to the originating machine. +- The originating machine receives the DCS signal and triggers a TCF (Training) sequence (labeled 1). +- The TCF sequence includes a 'check ok' response (labeled 2). +- Following the TCF, the CFR (Confirmation of Reception) and Training signals are exchanged. +- The actual data transmission begins with FCD (Fast Call Data) signals. If an error occurs, a red dashed arrow labeled <FA\_busy\_packet> is sent from the FA to the TAF. +- Subsequent FCD signals are transmitted, followed by RCP (Retransmission Control Protocol) and PPS (Pre-Transmission Protocol) signals. +- If another error occurs, a red dashed arrow labeled <FA\_non\_busy\_packet> is sent from the FA to the TAF. +- The transmission concludes with MCF (Message Confirmation) and DCN (Data Channel Network) signals. + +Sequence diagram for mobile originated facsimile transmission in error correction mode. It shows the interaction between a Facsimile Group3 machine, FA, TAF, RAN, MSC/IWF, PSTN, and another Facsimile Group3 machine. The process includes DIS, DCS, TCF, CFR, Training, FCD, RCP, PPS, MCF, and DCN signals. Red dashed arrows indicate error recovery packets: and . + +- (1) triggered by delayed DCS(75 ms) +- (2) triggered by delayed TCF(2,4 s) + +Figure C.8: Mobile originated facsimile transmission (error correction mode) + +![Sequence diagram for mobile originated facsimile transmission - error recovery. It shows the initial DIS and DCS exchange, followed by a timeout at the receiver, and then a retransmission of the DCS signal from the FA to the TAF.](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg) + +The diagram illustrates a mobile originated facsimile transmission with error recovery. The sequence of events is as follows: + +- The Facsimile Group3 machine sends a DIS signal to the FA. +- The FA forwards the DIS signal via the TAF to the RAN, then to the MSC/IWF (TAF), then to the FA, then to the PSTN, and finally to the receiving Facsimile Group3 machine. +- The receiving Facsimile Group3 machine responds with a DCS signal, which is routed back through the PSTN, FA, MSC/IWF (FA), RAN, TAF, and FA to the originating machine. +- The originating machine receives the DCS signal and triggers a TCF (Training) sequence. +- The TCF sequence includes a 'check ok' response. +- Following the TCF, the CFR (Confirmation of Reception) and Training signals are exchanged. +- The actual data transmission begins with FCD (Fast Call Data) signals. If an error occurs, a red dashed arrow labeled <FA\_busy\_packet> is sent from the FA to the TAF. +- Subsequent FCD signals are transmitted, followed by RCP (Retransmission Control Protocol) and PPS (Pre-Transmission Protocol) signals. +- If another error occurs, a red dashed arrow labeled <FA\_non\_busy\_packet> is sent from the FA to the TAF. +- The transmission concludes with MCF (Message Confirmation) and DCN (Data Channel Network) signals. + +Sequence diagram for mobile originated facsimile transmission - error recovery. It shows the initial DIS and DCS exchange, followed by a timeout at the receiver, and then a retransmission of the DCS signal from the FA to the TAF. + +Figure C.9: Mobile originated facsimile transmission - error recovery (example) + +![Figure C.10: Mobile terminated facsimile transmission - error recovery (example)](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +The diagram illustrates a sequence of messages for a mobile terminated facsimile transmission. The network elements involved are: Facsimile machine (containing Facsimile Group3), FA, TAF (forming the MT), RAN, MSC / IWF (containing TAF and FA), PSTN, and a remote Facsimile Group3 device. + +The sequence is as follows: +1. The remote Facsimile Group3 sends a DIS message through the PSTN and MSC/IWF. +2. The FA sends a DIS message to the local Facsimile machine. +3. A 'Time out' occurs at the local Facsimile machine. +4. The local Facsimile machine sends a DIS message back. +5. The MSC/IWF sends a <DIS> message across the RAN to the MT. +6. A 'Time out' occurs at the MSC/IWF. +7. The local Facsimile machine sends a DCS message. +8. The MT sends a <DCS> message across the RAN to the MSC/IWF. +9. The MSC/IWF sends a DCS message through the PSTN to the remote Facsimile Group3. + +Figure C.10: Mobile terminated facsimile transmission - error recovery (example) + +**Figure C.10: Mobile terminated facsimile transmission - error recovery (example)** + +![Figure C.11: Mobile originated facsimile transmission - error recovery (example)](4ff00a489baaa34a0c01070de1d613db_img.jpg) + +This sequence diagram illustrates a mobile originated facsimile transmission with error recovery. The lifelines are: Facsimile Group3 (facsimile machine), FA, TAF (MT), RAN, MSC / IWF (TAF and FA), PSTN, and Facsimile Group3. + +The sequence of messages is as follows: +1. The local Facsimile machine sends a DCS message to the FA. +2. The MT sends a <DCS> message across the RAN to the MSC/IWF. +3. The MSC/IWF sends a DCS message through the PSTN to the remote Facsimile Group3. +4. The local Facsimile machine sends a TCF signal, which the local FA marks as 'check ok'. +5. The remote Facsimile Group3 sends a TCF signal. The FA in the MSC/IWF marks this as 'check not ok'. This is marked as trigger (1). +6. The remote Facsimile Group3 sends an FTT message. +7. The MSC/IWF sends an <FTT> message across the RAN to the MT. +8. The local Facsimile machine sends a DCS message. +9. The MSC/IWF sends a DCS message through the PSTN to the remote Facsimile Group3. This is marked as trigger (2). +10. The local Facsimile machine sends a TCF signal, marked 'check ok' by the local FA. +11. The remote Facsimile Group3 sends a TCF signal, marked 'check ok' by the FA in the MSC/IWF. +12. The remote Facsimile Group3 sends a CFR message. +13. The MSC/IWF sends a <CFR> message across the RAN to the MT. +14. The local FA sends a CFR message to the local Facsimile machine. + +Figure C.11: Mobile originated facsimile transmission - error recovery (example) + +- (1) triggered by delayed DCS(75 ms) +- (2) triggered by delayed FTT(75 ms) + +**Figure C.11: Mobile originated facsimile transmission - error recovery (example)** + +![Figure C.12: Sequence diagram showing a mobile originated facsimile transmission error recovery during the training phase. The local side consists of a Facsimile Group 3 machine, FA, and TAF (MT). The network side includes RAN and MSC/IWF. The remote side has a PSTN and another Facsimile Group 3 machine. The local machine sends DCS and TCF. The TAF sends <DCS> to the MSC/IWF. The MSC/IWF detects an error in TCF and sends <TCF error detection > back to the TAF. The MSC/IWF also adds an error to the TCF sent to the remote machine, which responds with 'check not ok'. The local TAF sends FTT to the local machine after a delay marked as (1).](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Figure C.12: Sequence diagram showing a mobile originated facsimile transmission error recovery during the training phase. The local side consists of a Facsimile Group 3 machine, FA, and TAF (MT). The network side includes RAN and MSC/IWF. The remote side has a PSTN and another Facsimile Group 3 machine. The local machine sends DCS and TCF. The TAF sends to the MSC/IWF. The MSC/IWF detects an error in TCF and sends back to the TAF. The MSC/IWF also adds an error to the TCF sent to the remote machine, which responds with 'check not ok'. The local TAF sends FTT to the local machine after a delay marked as (1). + +- (1) triggered by delayed TCF error detection element (2,4 s) + +**Figure C.12: Mobile originated facsimile transmission - error recovery (example)** + +![Figure C.13: Sequence diagram showing mobile originated facsimile transmission error recovery during the message phase. It shows the flow of 'Training facsimile message' from the local machine through FA, TAF, RAN, MSC/IWF, and PSTN to the remote machine. Signals include EOP (End of Page) and MCF (Message Confirmation). A red dashed line indicates a <FA_non_busy_packet> sent from the MSC/IWF back towards the TAF. A 'Time out' is indicated on the local side during the EOP/MCF exchange.](107da2e3495b2f24352c9e3b26ec4841_img.jpg) + +Figure C.13: Sequence diagram showing mobile originated facsimile transmission error recovery during the message phase. It shows the flow of 'Training facsimile message' from the local machine through FA, TAF, RAN, MSC/IWF, and PSTN to the remote machine. Signals include EOP (End of Page) and MCF (Message Confirmation). A red dashed line indicates a sent from the MSC/IWF back towards the TAF. A 'Time out' is indicated on the local side during the EOP/MCF exchange. + +**Figure C.13: Mobile originated facsimile transmission - error recovery (example)** + +# Annex D (normative): SDL Diagrams + +The SDL specification within this Appendix shall be used as a reference model for implementation. The external behaviour of an implementation shall comply with the present document. However internal behaviour may be implementation dependent. + +**Table D.1: State symbols** + +| State symbol | Phase / Mode | | | +|--------------|--------------|----------------------------------|--------------| +| | Phase A | Transmission / Reception side FA | NONECM / ECM | +| A | | | | +| R-A1 | | Reception side FA | | +| T | Phase B | Transmission side FA | | +| T B1 | | | | +| T B2 | | | | +| T B4 | | | | +| T B5 | | | | +| R | | Reception side FA | | +| R B1 | | | | +| R B3 | | | | +| R B4 | | | | +| R B5 | | | | +| T C1 | Phase C | Transmission side FA | NONECM | +| T C2 | | | ECM | +| R C1 | | Reception side FA | NONECM | +| R C2 | | | ECM | +| T D1 | Phase D | Transmission side FA | NONECM | +| T D2 | | | ECM | +| T D2 res1 | | | | +| T D2 res2 | | | | +| R D1 | | Reception side FA | NONECM | +| R D2 | | | ECM | +| R D1 MPS | | | NONECM | +| R D1 EOM | | | | +| R D1 EOP | | | | +| R D2 NULL | | | ECM | +| R D2 MPS | | | | +| R D2 EOM | | | | +| R D2 EOP | | | | +| R D2 E NULL | | | | +| R D2 E MPS | | | | +| R D2 E EOM | | | | +| R D2 E EOP | | | | +| E1 | Phase E | Transmission / Reception side FA | NONECM / ECM | +| E2 | | | | +| E3 | | | | + +![System 23.146 - Overview diagram showing entities FAX_Entity, FA_UE_Entity, NW_Entity, LL_ADP_UE, LL_NW, and Lower_layer_Entity with their interactions.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +The diagram illustrates the system architecture for System 23.146. It features three main entities at the top: FAX\_Entity, FA\_UE\_Entity, and NW\_Entity. FAX\_Entity and FA\_UE\_Entity are connected via a bidirectional arrow labeled FAX\_protocol, with parameters (T.4) and (T.30) indicated on both sides. FA\_UE\_Entity and NW\_Entity are connected via a bidirectional arrow labeled FA\_protocol, with parameters (E\_T.38) indicated on both sides. Below FA\_UE\_Entity is LL\_ADP\_UE, connected by a vertical double-headed arrow with (LL\_Ind) on the upward arrow and (LL\_Req) on the downward arrow. Below NW\_Entity is LL\_NW, also connected by a vertical double-headed arrow with (LL\_Ind) on the upward arrow and (LL\_Req) on the downward arrow. Both LL\_ADP\_UE and LL\_NW are connected to a common Lower\_layer\_Entity at the bottom by vertical double-headed arrows. + +System 23.146 - Overview diagram showing entities FAX\_Entity, FA\_UE\_Entity, NW\_Entity, LL\_ADP\_UE, LL\_NW, and Lower\_layer\_Entity with their interactions. + +Figure D.1: System 23.146 - Overview + +![Block diagram of FA_UE_Entity showing internal components (FA_Process, FAX_interface, NW_interface) and their interactions with external protocols (FAX_protocol, FA_protocol, LL_FA_UE).](8269648391c59363ea61243864a2adf7_img.jpg) + +The diagram illustrates the internal structure and data flows of the FA\_UE\_Entity block. It contains three main components: FA\_Process, FAX\_interface, and NW\_interface. The FA\_Process is at the top, receiving [fax\_signal] from the FAX\_interface and [packet] from the NW\_interface. It sends [LL\_ind] to the FAX\_interface and [packet] to the NW\_interface. The FAX\_interface is on the left, receiving [fax\_signal] from the FA\_Process and sending [fax\_signal] to the FA\_Process. It has an external connection to FAX\_protocol via FAX\_protocol\_Rt, with data flow indicated by [(T.4), (T.30)]. The NW\_interface is on the right, receiving [packet] from the FA\_Process and sending [packet] to the FA\_Process. It has an external connection to FA\_protocol via FA\_protocol\_Rt, with data flow indicated by [(E\_T.38), (E\_T.38)]. A low\_layer\_signal\_Rt connects the FA\_Process to the NW\_interface. The entire block is labeled LL\_FA\_UE at the bottom. + +**signallist fax\_signal =** + +CED, +CFR, +CIG.DTC, +CNG, +CSI.DIS, +CSI.DIS.NSF, +CTC, +CTR, +EOM, +EOP, +EOR\_EOM, +EOR\_EOP, +EOR\_MPS, +EOR\_NULL, +ERR, +FCD, +FTT, +MCF, +MPS, +PIX, +PIX.RCP, +PIX.RTC, +PPR, +PPS\_EOM, +PPS\_EOP, +PPS\_MPS, +PPS\_NULL, +preamble, +RCP, +RNR, +RTC, +RTN, +RTP, +TCF, +TCF\_with\_error, +Carrier\_off; + +**signallist packet =** + +CED\_packet, +CIG.DTC\_packet, +CNG\_packet, +CSI.DIS\_packet, +CTC\_packet, +DCN\_packet, +DIS\_packet, +DTC\_packet, +EOL\_packet, +EOM\_packet, +EOP\_packet, +EOR\_Q\_packet, +FCD\_packet, +FTT\_packet, +MPS\_packet, +PPS\_EOM\_packet, +PPS\_EOP\_packet, +PPS\_MPS\_packet, +PPS\_NULL\_packet, +PPS\_Q\_packet, +TCF\_error\_detection\_packet, +TSI.DCS\_packet, +FA\_busy\_packet, +FA\_non\_busy\_packet; + +**signallist LL\_ind =** + +low\_layer\_established; + +**signallist LL\_req =** + +low\_layer\_Disconnect; + +Block diagram of FA\_UE\_Entity showing internal components (FA\_Process, FAX\_interface, NW\_interface) and their interactions with external protocols (FAX\_protocol, FA\_protocol, LL\_FA\_UE). + +Figure D.2a: Block FA\_UE Entity + +![Diagram showing four procedure references: Command_Reception, Response_Reception, RR_Response_Reception, and Wait, each with a description box.](32ff77da4286b58c4778033acaa10836_img.jpg) + +The diagram consists of four entries, each with a procedure name in a box on the left and a description box on the right, connected by a line. + +- Command\_Reception**: The routine searches for an error-free standard command, then returns 'F' and 'w', where 'F' is the most recent received standard command, and 'w' is the result word indicating the next action. +- Response\_Reception**: The routine searches for an error-free standard response, then returns 'F' and 'w', where F is the most recent received standard response, and 'w' is the result word indicating the next action. +- RR\_Response\_Reception**: The routine transmits the RR command and searches for an error-free standard response, then returns 'F' and 'w', where F is the most recent received standard response, and 'w' is the result word indicating the next action. +- Wait**: The routine searches for a packet, then returns 'w', where 'w' is the result word indicating the next action. + +Diagram showing four procedure references: Command\_Reception, Response\_Reception, RR\_Response\_Reception, and Wait, each with a description box. + +**Figure D.2b: Procedure Reference** + +![Flowchart showing the initial operation flow for a FA (Analogue). The process starts with a connector 'A', followed by 'wait_for_low_layer_protocol_link_establish', then 'low_layer_established'. A note indicates the 'Low layer protocol link establish' procedure details for NW and PSTN sides. The next step is 'Start to monitor DCN_packet', followed by 'wait_for_signal_in_phase_A'. A horizontal line branches into seven paths: 1) CNG leads to CNG_packet, which leads to a terminal '-'. 2) CED leads to CED_packet, which leads to a terminal '-'. 3) CSI.DIS.NSF leads to connector R_A1. 4) CNG_packet leads to CNG, which leads to connector R. 5) CED_packet leads to CED, which leads to a terminal '-'. 6) CSI.DIS_packet leads to a decision 'CED already transmitted to the FAX?'. If 'Yes', it leads to connector T. If 'else', it leads to CED, which leads to connector T. 7) An asterisk (*) leads to 'Discard the signal', which leads to a terminal '-'.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +Flowchart showing the initial operation flow for a FA (Analogue). The process starts with a connector 'A', followed by 'wait\_for\_low\_layer\_protocol\_link\_establish', then 'low\_layer\_established'. A note indicates the 'Low layer protocol link establish' procedure details for NW and PSTN sides. The next step is 'Start to monitor DCN\_packet', followed by 'wait\_for\_signal\_in\_phase\_A'. A horizontal line branches into seven paths: 1) CNG leads to CNG\_packet, which leads to a terminal '-'. 2) CED leads to CED\_packet, which leads to a terminal '-'. 3) CSI.DIS.NSF leads to connector R\_A1. 4) CNG\_packet leads to CNG, which leads to connector R. 5) CED\_packet leads to CED, which leads to a terminal '-'. 6) CSI.DIS\_packet leads to a decision 'CED already transmitted to the FAX?'. If 'Yes', it leads to connector T. If 'else', it leads to CED, which leads to connector T. 7) An asterisk (\*) leads to 'Discard the signal', which leads to a terminal '-'. + +Figure D.3: Initial operation flow for a FA (Analogue) + +![Flowchart for Transmission side FA, Phase B (Basic control flow).](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` + + graph TD + T((T)) --> set_T1[set (T1)] + set_T1 --> Wait_75ms['75ms Wait'] + Wait_75ms --> CSI_DIS{CSI.DIS} + CSI_DIS --> Response_Reception[Response Reception (F,w)] + Response_Reception --> w_resp{w} + w_resp -- Yes --> T_B5_counter_0_resp[T_B5_counter := 0] + w_resp -- No --> third_try{3rd try?} + third_try -- Yes --> Wait_2s['2s wait'] + third_try -- else --> T1_elapsed_resp{T1 elapsed?} + T1_elapsed_resp -- Yes --> E3_resp((E3)) + T1_elapsed_resp -- else --> Wait_75ms + T1_elapsed_resp -- No --> E1_resp((E1)) + E1_resp --> E1 + E3_resp --> E3 + T_B5_counter_0_resp --> F_resp{F} + F_resp -- DTC --> DTC_packet[DTC_packet] + F_resp -- DIS --> DIS_packet[DIS_packet] + F_resp -- DCS --> TSI_DCS_packet{TSI.DCS packet already transmitted?} + TSI_DCS_packet -- Yes --> EOM_already_received_resp{EOM already received?} + EOM_already_received_resp -- Yes --> TSI_DCS_packet + EOM_already_received_resp -- else --> TSI_DCS_packet + F_resp -- CRP --> reissue[reissue previous command] + reissue --> T_B5((T_B5)) + DTC_packet --> Reception_side_start[Reception side action starts] + DIS_packet --> Reception_side_start + TSI_DCS_packet -- else --> start_monitor[start to monitor FTT_packet] + start_monitor --> T_B1((T_B1)) + Reception_side_start --> R_B1((R_B1)) + set_T1 --> T_B5_counter_0[T_B5_counter := 0] + T_B5_counter_0 --> F{F} + F -- DTC --> DTC_packet + F -- DIS --> DIS_packet + F -- DCS --> TSI_DCS_packet + F -- CRP --> set_Twa[set (Twa)] + set_Twa --> ECM{ECM?} + ECM -- Yes --> T_D2((T_D2)) + ECM -- else --> T_D1((T_D1)) + T_B5((T_B5)) --> T_B5_counter_plus1[T_B5_counter := T_B5_counter + 1] + T_B5_counter_plus1 --> Command_Reception[Command Reception (F,w)] + Command_Reception --> w_cmd{w} + w_cmd -- Yes --> E3_cmd((E3)) + w_cmd -- No --> 66s_elapsed{66s elapsed?} + 66s_elapsed -- Yes --> E3_cmd + 66s_elapsed -- else --> T2_elapsed{2 elapsed?} + T2_elapsed -- Yes --> T_B4((T_B4)) + T2_elapsed -- else --> T_B5_counter_0_cmd[T_B5_counter := 0] + T_B5_counter_0_cmd --> T((T)) + T_B5_counter_0_cmd --> Discard[Discard the frame] + Discard --> E3_cmd + T_B5_counter_0_cmd --> NotDefined[The received frame is not defined in T.30] + T_B5_counter_0_cmd --> E1_cmd((E1)) + T_B5_counter_0_cmd --> T_B5((T_B5)) + T_B5_counter_plus1 --> Command_Reception + Command_Reception --> w_cmd + w_cmd -- No --> 66s_elapsed + 66s_elapsed -- else --> T2_elapsed + T2_elapsed -- else --> T_B5_counter_0_cmd + T_B5_counter_0_cmd --> T + T_B5_counter_0_cmd --> Discard + Discard --> E3_cmd + NotDefined --> E3_cmd + T_B5_counter_0_cmd --> E1_cmd + T_B5_counter_0_cmd --> T_B5 + +``` + +PRI\_MPS, + MPS, + PRI\_EOM, + EOM, + PRI\_EOP, + EOP, + CTC, + PPS\_PRI\_Q, + PPS\_Q, + EOR\_PRI\_Q, + EOR\_Q, + RR, + DCN + +Flowchart for Transmission side FA, Phase B (Basic control flow). + +Figure D.4: Transmission side FA, Phase B (Basic control flow) + +![Flowchart for Reception side FA, Phase B. The process starts at connector R, sets timer T1, and enters a loop for Command Reception (F,w). It checks flags 'w' and 'F'. If 'F' is 'Yes', it checks for CSI.DIS.NSF. If present, it resets T1, sets the DIS bit, and sends a CSI.DIS_packet. If 'F' is 'else', it checks if T1 has elapsed. If 'Yes', it resets T1 and ends at E1. If 'No', it checks if EOM is already received. If 'Yes', it goes to CNG. If 'else', it loops back to Command Reception. After sending CSI.DIS_packet, it waits for a packet. It then branches based on received packets: TSI.DCS_packet, CIG.DTC_packet, or CSI.DIS_packet. TSI.DCS_packet leads to a 75ms wait and then checks for TCF error detection. If 'Yes', it checks for TCF with error. If 'Yes', it ends at R_B5. If 'else', it increments the response received counter and checks if it's the 3rd try. If 'Yes', it resets the counter and ends at E2. If 'else', it loops back to wait for 75ms. If 'TCF with error' is 'No', it checks flag 'w'. If 'Yes', it resets the counter and ends at R_B4. If 'else', it ends at E1. CIG.DTC_packet leads to CIG.DTC and then to set (T2) and Transmission side action_starts, ending at T_B5. CSI.DIS_packet leads to CSI.DIS and then to set (T2) and Transmission side action_starts, ending at T_B5.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + +graph TD + R((R)) --> SetT1[Set (T1)] + SetT1 --> CommandReception[Command Reception (F,w)] + CommandReception --> w1{w} + w1 -- Yes --> F1{F} + F1 -- Yes --> CSI_DIS_NSF[CSI.DIS.NSF] + F1 -- else --> T1_elapsed{T1 elapsed?} + T1_elapsed -- Yes --> resetT1_1[reset (T1)] + resetT1_1 --> E1((E1)) + T1_elapsed -- No --> EOM_already[EOM already received?] + EOM_already -- Yes --> CNG{{CNG}} + EOM_already -- else --> CommandReception + CSI_DIS_NSF --> resetT1_2[reset (T1)] + resetT1_2 --> SetDIS[Set DIS bit] + SetDIS --> NSF_note[NSF frame is removed and no allowance bits of the DCS frame are masked.] + NSF_note --> CSI_DIS_packet1[CSI.DIS_packet] + CSI_DIS_packet1 --> wait_packet[wait_for_packet] + wait_packet --> TSI_DCS_packet[TSI.DCS_packet] + TSI_DCS_packet --> wait75ms[wait for 75ms] + wait75ms --> TSI_DCS1{{TSI.DCS}} + TSI_DCS1 --> TCF_error{TCF error detection packet received?} + TCF_error -- Yes --> TCF_error_with[TCF with error] + TCF_error_with -- Yes --> R_B5((R_B5)) + TCF_error_with -- else --> Response_received[Response received counter := Response_received_counter + 1] + Response_received --> 3rd_try{3rd try?} + 3rd_try -- Yes --> resetCounter0[Response received counter := 0] + resetCounter0 --> E2((E2)) + 3rd_try -- else --> wait75ms + TCF_error -- else --> Response_Reception[Response Reception (F,w)] + Response_Reception --> w2{w} + w2 -- Yes --> resetCounter1[Response received counter := 0] + resetCounter1 --> R_B4((R_B4)) + w2 -- else --> E1 + w2 -- E3 --> E3((E3)) + CIG_DTC_packet[CIG.DTC_packet] --> CIG_DTC{{CIG.DTC}} + CIG_DTC --> setT2[set (T2)] + setT2 --> Transmission[Transmission side action_starts] + Transmission --> T_B5((T_B5)) + CSI_DIS_packet2[CSI.DIS_packet] --> CSI_DIS2{{CSI.DIS}} + CSI_DIS2 --> setT2 + setT2 --> Transmission + Transmission --> T_B5 + +``` + +Flowchart for Reception side FA, Phase B. The process starts at connector R, sets timer T1, and enters a loop for Command Reception (F,w). It checks flags 'w' and 'F'. If 'F' is 'Yes', it checks for CSI.DIS.NSF. If present, it resets T1, sets the DIS bit, and sends a CSI.DIS\_packet. If 'F' is 'else', it checks if T1 has elapsed. If 'Yes', it resets T1 and ends at E1. If 'No', it checks if EOM is already received. If 'Yes', it goes to CNG. If 'else', it loops back to Command Reception. After sending CSI.DIS\_packet, it waits for a packet. It then branches based on received packets: TSI.DCS\_packet, CIG.DTC\_packet, or CSI.DIS\_packet. TSI.DCS\_packet leads to a 75ms wait and then checks for TCF error detection. If 'Yes', it checks for TCF with error. If 'Yes', it ends at R\_B5. If 'else', it increments the response received counter and checks if it's the 3rd try. If 'Yes', it resets the counter and ends at E2. If 'else', it loops back to wait for 75ms. If 'TCF with error' is 'No', it checks flag 'w'. If 'Yes', it resets the counter and ends at R\_B4. If 'else', it ends at E1. CIG.DTC\_packet leads to CIG.DTC and then to set (T2) and Transmission side action\_starts, ending at T\_B5. CSI.DIS\_packet leads to CSI.DIS and then to set (T2) and Transmission side action\_starts, ending at T\_B5. + +Figure D.5: Reception side FA, Phase B + +![Flowchart for TCF error detection. It starts at T_B1, checks if an error is detected. If 'Yes', it goes to a third decision diamond. If 'else', it checks if the radio interface quality is OK. If 'Yes', it goes to T_B2. If 'else', it goes to the third decision diamond. The third decision diamond checks if a TCF error detection packet is already transmitted. If 'Yes', it goes to T_B2. If 'else', it generates a TCF_error_detection_packet and sets the flag to ON, then goes to T_B2.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` +graph TD; T_B1((T_B1)) --> D1{'Error in TCF detected?'}; D1 -- Yes --> D3{"\"TCF error detection packet\" already transmitted to NW by DCS at the same speed?"}; D1 -- else --> D2{'Radio interface quality OK?'}; D2 -- Yes --> T_B2((T_B2)); D2 -- else --> D3; D3 -- Yes --> T_B2; D3 -- else --> P1{{TCF_error_detection_packet}}; P1 --> P2[TCF_error_detection_packet_flag := ON]; P2 --> T_B2; +``` + +Flowchart for TCF error detection. It starts at T\_B1, checks if an error is detected. If 'Yes', it goes to a third decision diamond. If 'else', it checks if the radio interface quality is OK. If 'Yes', it goes to T\_B2. If 'else', it goes to the third decision diamond. The third decision diamond checks if a TCF error detection packet is already transmitted. If 'Yes', it goes to T\_B2. If 'else', it generates a TCF\_error\_detection\_packet and sets the flag to ON, then goes to T\_B2. + +Figure D.6: Output conditions for "TCF error detection" for ECM&NONECM + +![Flowchart for selection algorithm for CFR/FTT for T-FA ECM & NONECM. It starts at T_B2, increments a counter, waits 2.4s, then checks TCF_error_detection_packet_flag, FTT_packet_flag, and Pre_message_response_counter. Depending on these checks, it leads to FTT, CFR, or another state.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` + +graph TD + T_B2((T_B2)) --> Counter["Pre_message_response_counter := +Pre_message_response_counter + 1"] + Counter --> Wait["'Wait for 2.4s'"] + Wait --> TCF_flag{TCF_error_detection_packet_flag} + + TCF_flag -- ON --> FTT_node{{FTT}} + TCF_flag -- else --> FTT_flag{FTT_packet_flag} + + FTT_flag -- ON --> FTT_node + FTT_flag -- else --> Pre_counter{Pre_message_response_counter} + + Pre_counter -- "=3" --> FTT_node + Pre_counter -- else --> R_FA_busy{"'R-FA busy?'"} + + R_FA_busy -- "'Yes'" --> Twa_elapsed{"'Twa elapsed?'"} + R_FA_busy -- else --> CFR_node{{CFR}} + + Twa_elapsed -- "'Yes'" --> E1((E1)) + Twa_elapsed -- else --> T_B5_1((T_B5)) + + CFR_node --> T_B4((T_B4)) + + FTT_node --> set_T2["set (T2)"] + set_T2 --> Reset["TCF_error_detection_packet_flag := OFF; +FTT_packet_flag := OFF; +Pre_message_response_counter := 0;"] + Reset --> T_B5_2((T_B5)) + +``` + +**Flowchart details:** + +- Start node:** T\_B2 +- Action:** Pre\_message\_response\_counter := Pre\_message\_response\_counter + 1 +- Action:** 'Wait for 2.4s' +- Decision:** TCF\_error\_detection\_packet\_flag + - ON:** Proceed to FTT + - else:** Proceed to FTT\_packet\_flag +- Decision:** FTT\_packet\_flag + - ON:** Proceed to FTT + - else:** Proceed to Pre\_message\_response\_counter +- Decision:** Pre\_message\_response\_counter + - =3:** Proceed to FTT + - else:** Proceed to 'R-FA busy?' +- Decision:** 'R-FA busy?' + - 'Yes':** Proceed to 'Twa elapsed?' + - else:** Proceed to CFR +- Decision:** 'Twa elapsed?' + - 'Yes':** End at E1 + - else:** End at T\_B5 +- Process FTT:** + - Action: set (T2) + - Action: TCF\_error\_detection\_packet\_flag := OFF; FTT\_packet\_flag := OFF; Pre\_message\_response\_counter := 0; + - End node: T\_B5 +- Process CFR:** + - End node: T\_B4 + +**Annotations:** + +- Next to **TCF\_error\_detection\_packet\_flag**: "If TCF\_error\_detection\_packet has been received, 'TCF\_error\_detection\_packet\_flag' was turned on." +- Next to **FTT\_packet\_flag**: "'FTT packet flag' shall be turned to 'ON' when 'FTT packet' is received to NW from 'T-B1' to 'just before C phase'." + +Flowchart for selection algorithm for CFR/FTT for T-FA ECM & NONECM. It starts at T\_B2, increments a counter, waits 2.4s, then checks TCF\_error\_detection\_packet\_flag, FTT\_packet\_flag, and Pre\_message\_response\_counter. Depending on these checks, it leads to FTT, CFR, or another state. + +Figure D.7: Selection algorithm for CFR /FTT for T-FA ECM & NONECM + +![Flowchart for Stand-by method for V.21/V.17/V.27ter/V.29 for T-FA. It starts at T_B4, goes through modem selection, a 3ms wait, carrier detection, PN detection, and counter logic to reach T_B5, T_C1, or T_C2.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +``` + +graph TD + T_B4((T_B4)) --> B1["'Select the relevant modem +in compliance with the DCS.'"] + B1 --> Join1(( )) + Join1 --> W1["'Wait for 3ms'"] + W1 --> CD{"'Carrier detection?'"} + CD -- else --> Init1["PN_detection_counter := 0; +PN_non_detection_counter := 0;"] + Init1 --> Join1 + CD -- Yes --> PD{"'PN detection?'"} + PD -- Yes --> Inc1["PN_detection_counter +:= +PN_detection_counter + 1"] + PD -- else --> Inc2["PN_non_detection_counter +:= +PN_non_detection_counter + 1"] + Inc1 --> C1{"PN_detection_counter"} + C1 -- else --> Init1 + C1 -- ">4" --> D1["'PN is detected.'"] + D1 --> Init2["PN_detection_counter := 0; +PN_non_detection_counter := 0;"] + Init2 --> ECM{"'ECM?'"} + ECM -- Yes --> T_C2((T_C2)) + ECM -- else --> T_C1((T_C1)) + Inc2 --> C2{"PN_non_detection_counter"} + C2 -- "<100" --> Init1 + C2 -- else --> B2["'Select V.21 modem'"] + B2 --> Init3["PN_detection_counter := 0; +PN_non_detection_counter := 0;"] + Init3 --> T_B5((T_B5)) + + subgraph Notes + direction LR + N1["Depend on OS +performance"] + end + N1 -.- Join1 + +``` + +Flowchart for Stand-by method for V.21/V.17/V.27ter/V.29 for T-FA. It starts at T\_B4, goes through modem selection, a 3ms wait, carrier detection, PN detection, and counter logic to reach T\_B5, T\_C1, or T\_C2. + +**Figure D.8: Stand-by method for V.21/V.17/V.27ter/V.29 for T-FA** + +![Flowchart for FTT and specified TX rate decision algorithm for DCS NONECM & ECM. It starts at R_B4, checks for T.30 HDLC frame, then TCF error detection packet, then ECM status, or FTT_packet contents, leading to various output states like R_C2, R_C1, or R_B5.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` +graph TD; R_B4((R_B4)) --> D1{'T.30 HDLC frame received?'}; D1 -- 'Yes' --> D2{'F'}; D1 -- 'else' --> D3{'TCF error detection packet received?'}; D2 --> D3; D3 -- 'CFR' --> D4{'TCF error detection packet received?'}; D3 -- 'else' --> D5{'Is TX rate specified for previously transmitted DCS 2.4kbps?'}; D4 -- 'Yes' --> D6{'TCF error detection packet received?'}; D4 -- 'else' --> D7{'ECM?'}; D6 -- 'Yes' --> D5; D6 -- 'else' --> R_B5_1((R_B5)); D7 -- 'Yes' --> R_C2((R_C2)); D7 -- 'else' --> R_C1((R_C1)); D5 -- 'Yes' --> DCS1[DCS]; D5 -- 'else' --> D8['Drop specified TX rate one rank']; D8 --> DCS1; DCS1 --> TCF1[TCF]; TCF1 --> R_B5_2((R_B5)); DCS1 --> DCS2[DCS]; DCS2 --> TCF2[TCF]; TCF2 --> R_B5_2; DCS2 --> Retransmit[Retransmit the last transmitted DCS,TCF]; +``` + +The flowchart illustrates the decision logic for FTT and specified TX rate. It begins at state R\_B4. The first decision is 'T.30 HDLC frame received?'. If 'Yes', it proceeds to decision 'F'. If 'else', it proceeds to decision 'TCF error detection packet received?'. From 'F', it proceeds to the same 'TCF error detection packet received?' decision. From this decision, if 'CFR' is received, it proceeds to another 'TCF error detection packet received?' decision. If 'else', it proceeds to 'Is TX rate specified for previously transmitted DCS 2.4kbps?'. From the second 'TCF error detection packet received?' decision, if 'Yes', it proceeds to 'Is TX rate specified for previously transmitted DCS 2.4kbps?'. If 'else', it proceeds to 'ECM?'. From 'ECM?', if 'Yes', it leads to state R\_C2. If 'else', it leads to state R\_C1. From 'Is TX rate specified for previously transmitted DCS 2.4kbps?', if 'Yes', it proceeds to DCS. If 'else', it proceeds to 'Drop specified TX rate one rank', which then leads to DCS. From DCS, it proceeds to TCF, which leads to state R\_B5. From DCS, it also proceeds to another DCS, which leads to TCF, which leads to state R\_B5. From this second DCS, it also proceeds to 'Retransmit the last transmitted DCS,TCF'. + +Flowchart for FTT and specified TX rate decision algorithm for DCS NONECM & ECM. It starts at R\_B4, checks for T.30 HDLC frame, then TCF error detection packet, then ECM status, or FTT\_packet contents, leading to various output states like R\_C2, R\_C1, or R\_B5. + +Figure D.9: Output conditions for FTT and specified TX rate decision algorithm for DCS NONECM & ECM + +![Flowchart for Transmission side FA, Phase C for NONECM. It starts at T_C1, goes through 'Stop to monitor FTT_packet', 'receiving facsimile message', then branches into Carrier_off, RTC, and PIX. The PIX path leads to 'Store the facsimile message (PIX) into the buffer while stripping FILL', then a decision 'one or more line received?'. If 'Yes', it goes to FCD_packet() and then to a connector '-'. If 'else', it bypasses FCD_packet() to the same connector '-'. The Carrier_off path leads to 'Stop receiving PIX then append RTC to received PIX', which then leads to FCD_packet (sig_end) and finally to T_B5. The RTC path also leads to FCD_packet (sig_end).](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` +graph TD; T_C1((T_C1)) --> S1["'Stop to monitor FTT_packet'"]; S1 --> R1[receiving facsimile message]; R1 --> Carrier_off[Carrier_off]; R1 --> RTC[RTC]; R1 --> PIX[PIX]; Carrier_off --> CO["Carrier off? (between FA and TE)"]; CO --> S2["'Stop receiving PIX then append RTC to received PIX'"]; S2 --> FCD_SE["FCD_packet (sig_end)"]; RTC --> FCD_SE; PIX --> S3["'Store the facsimile message (PIX) into the buffer while stripping FILL'"]; S3 --> D1{"'one or more line received?'"}; D1 -- Yes --> FCD_P["FCD_packet()"]; D1 -- else --> J1(( )); FCD_P --> J1; J1 --> FCD_SE; FCD_SE --> T_B5((T_B5)); +``` + +Flowchart for Transmission side FA, Phase C for NONECM. It starts at T\_C1, goes through 'Stop to monitor FTT\_packet', 'receiving facsimile message', then branches into Carrier\_off, RTC, and PIX. The PIX path leads to 'Store the facsimile message (PIX) into the buffer while stripping FILL', then a decision 'one or more line received?'. If 'Yes', it goes to FCD\_packet() and then to a connector '-'. If 'else', it bypasses FCD\_packet() to the same connector '-'. The Carrier\_off path leads to 'Stop receiving PIX then append RTC to received PIX', which then leads to FCD\_packet (sig\_end) and finally to T\_B5. The RTC path also leads to FCD\_packet (sig\_end). + +Figure D.10: Transmission side FA, Phase C for NONECM + +![Flowchart for Reception side FA, phase C for NONECM. It starts at R_C1, goes through receiving FCD_packet, checks for sig_end and EOL accumulation. If 'Yes', it sends FA_busy_packet and enters a PIX loop. If 'else', it loops back to receiving. The PIX loop checks accumulation size; if 'Yes' and sig_end is true, it goes to PIX,RTC and then R_D1. If 'else', it appends RTC and transmits data. The PIX,RTC loop checks accumulation size; if 'Yes', it sets Fill insertion timer, starts FILL insertion, and then checks accumulation size again. If 'Yes', it resets timer and stops FILL insertion, looping back. If 'else', it checks if Fill insertion timer timeout; if 'Yes', it checks if accumulation is within forced RTC transmission value; if 'Yes', it loops back to PIX,RTC, else it loops back to PIX. If 'else' at any point in the PIX,RTC loop, it loops back to PIX.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` +graph TD; R_C1((R_C1)) --> receiving[receiving FCD_packet]; receiving --> sig_end{FCD_packet (sig_end)}; sig_end --> EOL{2 EOL received & the accumulation is 0.28kbyte or more}; EOL -- Yes --> FA_busy_packet[FA_busy_packet]; EOL -- else --> receiving; FA_busy_packet --> PIX{PIX}; PIX --> Accumulation1{The accumulation is 0.28kbyte or less}; Accumulation1 -- Yes --> sig_end2{sig_end}; Accumulation1 -- else --> AppendRTC[Append RTC and transmit the rest of the accumulated facsimile data to FAX]; sig_end2 -- true --> PIX_RTC{PIX,RTC}; sig_end2 -- else --> set_timer[set Fill insertion_timer]; set_timer --> StartFILL['Start FILL insertion']; StartFILL --> Accumulation2{The accumulation is 0.9kbyte or more}; Accumulation2 -- Yes --> reset_timer[reset Fill insertion_timer]; reset_timer --> StopFILL['Stop FILL insertion']; StopFILL --> PIX_RTC; Accumulation2 -- else --> TimerTimeout{Fill insertion timer timeout?}; TimerTimeout -- Yes --> ForcedRTC{The accumulation is the forced RTC transmission value or less}; ForcedRTC -- Yes --> PIX_RTC; ForcedRTC -- else --> PIX; TimerTimeout -- else --> PIX; PIX_RTC --> R_D1((R_D1)); R_D1 --> Accumulation2; +``` + +Flowchart for Reception side FA, phase C for NONECM. It starts at R\_C1, goes through receiving FCD\_packet, checks for sig\_end and EOL accumulation. If 'Yes', it sends FA\_busy\_packet and enters a PIX loop. If 'else', it loops back to receiving. The PIX loop checks accumulation size; if 'Yes' and sig\_end is true, it goes to PIX,RTC and then R\_D1. If 'else', it appends RTC and transmits data. The PIX,RTC loop checks accumulation size; if 'Yes', it sets Fill insertion timer, starts FILL insertion, and then checks accumulation size again. If 'Yes', it resets timer and stops FILL insertion, looping back. If 'else', it checks if Fill insertion timer timeout; if 'Yes', it checks if accumulation is within forced RTC transmission value; if 'Yes', it loops back to PIX,RTC, else it loops back to PIX. If 'else' at any point in the PIX,RTC loop, it loops back to PIX. + +Figure D.11: Reception side FA, phase C for NONECM + +![Flowchart for Transmission side FA, Phase C. It starts at T_C2, goes to 'Stop to monitor FTT packet', then 'receiving fax_message_FCD'. A decision 'Carrier off? (between FA and TE)' leads to 'Carrier_off' (then 'Stop receiving FCD then append RCP') or 'RCP'. Both lead to 'FCD_packet (sig_end)' and then T_B5. The 'FCD' path leads to 'Store the fax message (FCD) into the buffer', then a decision 'one or more FCD frame received?'. If 'Yes', it checks 'frame error?'. If 'Yes', it goes to 'FCD_packet (sig_end)'. If 'else', it checks 'the FCD frame has been already received by PPR requesting?'. If 'Yes', it goes to 'FCD_packet (sig_end)'. If 'else', it goes to 'FCD_packet ()' and then to a connector '-'. The 'else' path from 'one or more FCD frame received?' also leads to the connector '-'.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +Flowchart for Transmission side FA, Phase C. It starts at T\_C2, goes to 'Stop to monitor FTT packet', then 'receiving fax\_message\_FCD'. A decision 'Carrier off? (between FA and TE)' leads to 'Carrier\_off' (then 'Stop receiving FCD then append RCP') or 'RCP'. Both lead to 'FCD\_packet (sig\_end)' and then T\_B5. The 'FCD' path leads to 'Store the fax message (FCD) into the buffer', then a decision 'one or more FCD frame received?'. If 'Yes', it checks 'frame error?'. If 'Yes', it goes to 'FCD\_packet (sig\_end)'. If 'else', it checks 'the FCD frame has been already received by PPR requesting?'. If 'Yes', it goes to 'FCD\_packet (sig\_end)'. If 'else', it goes to 'FCD\_packet ()' and then to a connector '-'. The 'else' path from 'one or more FCD frame received?' also leads to the connector '-'. + +Figure D.12: Transmission side FA, Phase C for + +![Flowchart for Reception side FA, phase C for ECM. The process starts at connector R_C2, proceeds to receiving FCD_packet_ECM, then checks if FCD_packet (sig_end) is present. It then starts accumulating facsimile data and checks if the accumulation is 0.28kbyte or more. If 'Yes', it sends FA_busy_packet and PIX. If 'else', it loops back to receiving. From PIX, it checks if the accumulation is 0.28kbyte or less. If 'Yes', it checks sig_end. If 'else', it loops back to PIX. If sig_end is 'true', it sends PIX.RCP to connector R_D2. If sig_end is 'else', it sets the Flag_insertion_timer, starts FLAG insertion, and checks if the accumulation is 0.9kbyte or more. If 'Yes', it resets the timer and stops FLAG insertion. If 'else', it checks if the Flag_insertion_timer has elapsed. If 'Yes', it checks if the accumulation is 'the forced RCP transmission value' or less. If 'Yes', it loops back to PIX.RCP. If 'else', it loops back to PIX. If the timer has not elapsed, it loops back to the accumulation check.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` +graph TD; R_C2((R_C2)) --> receiving[receiving FCD_packet_ECM]; receiving --> sig_end_in{FCD_packet (sig_end)}; sig_end_in --> start_accum[Start to accumulate the facsimile data]; start_accum --> acc_0_28{The accumulation is 0.28kbyte or more}; acc_0_28 -- Yes --> FA_busy[FA_busy_packet]; FA_busy --> PIX{PIX}; PIX --> acc_0_28_less{The accumulation is 0.28kbyte or less}; acc_0_28_less -- Yes --> sig_end_out{sig_end}; sig_end_out -- true --> PIX_RCP{PIX.RCP}; PIX_RCP --> R_D2((R_D2)); sig_end_out -- else --> set_timer[set (Flag_insertion_timer)]; set_timer --> start_flag[Start FLAG insertion]; start_flag --> acc_0_9{The accumulation is 0.9kbyte or more}; acc_0_9 -- Yes --> reset_timer[reset (Flag_insertion_timer)]; reset_timer --> stop_flag[Stop FLAG insertion]; stop_flag --> acc_0_28; acc_0_9 -- else --> timer_elapsed{Flag_insertion_timer elapsed?}; timer_elapsed -- Yes --> acc_forced{The accumulation is "the forced RCP transmission value" or less?}; acc_forced -- Yes --> PIX_RCP; acc_forced -- else --> PIX; timer_elapsed -- else --> acc_0_28; acc_0_28 -- else --> receiving; +``` + +Flowchart for Reception side FA, phase C for ECM. The process starts at connector R\_C2, proceeds to receiving FCD\_packet\_ECM, then checks if FCD\_packet (sig\_end) is present. It then starts accumulating facsimile data and checks if the accumulation is 0.28kbyte or more. If 'Yes', it sends FA\_busy\_packet and PIX. If 'else', it loops back to receiving. From PIX, it checks if the accumulation is 0.28kbyte or less. If 'Yes', it checks sig\_end. If 'else', it loops back to PIX. If sig\_end is 'true', it sends PIX.RCP to connector R\_D2. If sig\_end is 'else', it sets the Flag\_insertion\_timer, starts FLAG insertion, and checks if the accumulation is 0.9kbyte or more. If 'Yes', it resets the timer and stops FLAG insertion. If 'else', it checks if the Flag\_insertion\_timer has elapsed. If 'Yes', it checks if the accumulation is 'the forced RCP transmission value' or less. If 'Yes', it loops back to PIX.RCP. If 'else', it loops back to PIX. If the timer has not elapsed, it loops back to the accumulation check. + +Figure D.13: Reception side FA, phase C for ECM + +![Flowchart for Transmission side FA for NON ECM, Phase D (Basic control flow).](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +The flowchart illustrates the transmission side FA for NON ECM, Phase D (Basic control flow). It begins at connector T\_D1 and enters a decision diamond 'F'. From 'F', four main paths emerge based on the type of packet: PRI\_EOP, EOP; PRI\_EOM, EOM; PRI\_MPS, MPS; and DCN. The 'else' path from 'F' leads to a 'Discard the frame' block. The DCN path leads to connector E1. The PRI\_EOP, EOP path leads to an 'EOP\_packet' block, followed by a decision 'R\_FA busy?'. If 'Yes', it goes to 'Wait for 2.4s', then 'Twa elapsed?'. If 'Yes' to 'Twa elapsed?', it goes to connector E1. If 'else', it goes to 'PRI\_EOP or EQP has been received 3 times?'. If 'Yes', it goes to 'RTN'. If 'else', it goes to 'No response'. If 'else' to 'R\_FA busy?', it goes to 'Wait for 75ms', then to a common line. The PRI\_EOM, EOM path leads to an 'EOM\_packet' block, followed by a decision 'R-FA busy?'. If 'Yes', it goes to 'Wait for 2.4s', then 'Twa elapsed?'. If 'Yes' to 'Twa elapsed?', it goes to connector E1. If 'else', it goes to 'Wait for 75ms', then to a common line. If 'else' to 'R-FA busy?', it goes to 'PRI\_EOM or EQM has been received 3 times?'. If 'Yes', it loops back to the 'R-FA busy?' decision. If 'else', it goes to 'No response', then to a common line. The PRI\_MPS, MPS path leads to an 'MPS\_packet' block, followed by a decision 'R-FA busy?'. If 'Yes', it goes to 'Wait for 2.4s', then 'Twa elapsed?'. If 'Yes' to 'Twa elapsed?', it goes to connector E1. If 'else', it goes to 'PRI\_MPS or MPS has been received 3 times?'. If 'Yes', it goes to 'RTP'. If 'else', it goes to 'No response'. If 'else' to 'R-FA busy?', it goes to 'Wait for 75ms', then to a common line. All common lines from the wait and response blocks converge to a single line leading to connector T\_B5. + +Flowchart for Transmission side FA for NON ECM, Phase D (Basic control flow). + +Figure D.14: Transmission side FA for NON ECM, Phase D (Basic control flow) + +![Flowchart for Reception side FA for NON ECM, Phase D (Basic control flow).](7ed5d5770331f31ade15439a21c31425_img.jpg) + +``` +graph TD; R_D1((R_D1)) --> Init["3s_timer_counter := 0"]; Init --> Set["set (3s)"]; Set --> Recv[receiving_packet]; Recv --> MPS_packet{MPS_packet}; Recv --> EOM_packet{EOM_packet}; Recv --> EOP_packet{EOP_packet}; Recv --> DCN_packet{DCN_packet}; Recv --> Asterisk{*}; Recv --> ThreeS{3s}; MPS_packet --> ResetMPS["reset (3s)"]; EOM_packet --> ResetEOM["reset (3s)"]; EOP_packet --> ResetEOP["reset (3s)"]; DCN_packet --> ResetDCN["reset (3s)"]; Asterisk --> ResetAsterisk["reset (3s)"]; ThreeS --> ResetThreeS["reset (3s)"]; ResetMPS --> R_D1_MPS((R_D1_MPS)); ResetEOM --> FA_non_busy_EOM{FA_non_busy_packet}; ResetEOP --> R_D1_EOP((R_D1_EOP)); ResetDCN --> FA_non_busy_DCN{FA_non_busy_packet}; ResetAsterisk --> FA_non_busy_Asterisk{FA_non_busy_packet}; ResetThreeS --> Wait["'75ms wait'"]; FA_non_busy_Asterisk --> Discard["'Discard the signal'"]; Discard --> E2((E2)); Wait --> Preamble{preamble}; Preamble --> Increment["3s_timer_counter := 3s_timer_counter + 1"]; Increment --> Counter{3s_timer_counter}; Counter -- "= 3" --> FA_non_busy_Counter{FA_non_busy_packet}; Counter -- else --> Set; FA_non_busy_Counter --> E2; FA_non_busy_EOM --> E2; FA_non_busy_DCN --> E2; +``` + +The flowchart illustrates the reception side FA for NON ECM, Phase D (Basic control flow). It begins with the start node R\_D1, followed by the initialization of 3s\_timer\_counter to 0. The process then sets a 3s timer and enters the receiving\_packet state. From there, it branches based on the type of packet received: MPS\_packet, EOM\_packet, EOP\_packet, DCN\_packet, \*, or 3s. Each packet type leads to a reset (3s) operation. MPS\_packet, EOM\_packet, and EOP\_packet lead to their respective end nodes (R\_D1\_MPS, R\_D1\_EOM, R\_D1\_EOP). DCN\_packet, \*, and 3s lead to FA\_non\_busy\_packet states. The \* packet type also leads to a 'Discard the signal' state. The 3s packet type leads to a '75ms wait' state, followed by a preamble state, and then an increment of 3s\_timer\_counter. A decision node for 3s\_timer\_counter checks if it equals 3. If so, it leads to an FA\_non\_busy\_packet state. Otherwise, it loops back to the set (3s) state. All FA\_non\_busy\_packet states eventually lead to the end node E2. + +Flowchart for Reception side FA for NON ECM, Phase D (Basic control flow). + +Figure D.15: Reception side FA for NON ECM, Phase D (Basic control flow) + +![Flowchart for Reception FA, Phase D (MPS). The process starts at R_D1_MPS, goes through 'wait for 75ms', 'MPS', counter increment, and 'Response_Reception (F,w)'. It then enters a loop based on 'w' and 'MPS_transmission_counter'. If 'w' is No, it checks the counter; if =3, it resets to 0 and goes to E2, otherwise it loops back. If 'w' is Yes, it resets the counter and checks 'F'. If 'F' is MCF, it goes through 'FA_non_busy_packet' and 'Wait (w)'. If 'F' is RTP, RTN, PIP, PIN, it goes to R_B3. If 'F' is else, it discards the frame and goes to E3. Finally, it checks 'w' again for outcomes E1, E2, E3, R_C1, and R_D1.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` +graph TD; R_D1_MPS((R_D1_MPS)) --> W75ms[wait for 75ms]; W75ms --> MPS{{MPS}}; MPS --> CounterInc[MPS_transmission_counter := MPS_transmission_counter + 1]; CounterInc --> ResRec[Response_Reception (F,w)]; ResRec --> W{w}; W -- No --> CounterCheck{MPS_transmission_counter}; CounterCheck -- =3 --> CounterReset1[MPS_transmission_counter := 0]; CounterReset1 --> E2((E2)); CounterCheck -- else --> W75ms; W -- Yes --> CounterReset2[MPS_transmission_counter := 0]; CounterReset2 --> F{F}; F -- MCF --> FA_non_busy[FA_non_busy_packet]; FA_non_busy --> WaitW[Wait (w)]; WaitW --> W2{w}; W2 -- E1 --> E1_end((E1)); W2 -- E2 --> E2_end((E2)); W2 -- E3 --> E3_end((E3)); W2 -- W_pix --> R_C1((R_C1)); W2 -- W_packet --> R_D1((R_D1)); F -- RTP, RTN, PIP, PIN --> R_B3((R_B3)); F -- else --> Discard[Discard the frame]; Discard --> E3_end2((E3)); E1_end --> E1; E2_end --> E2; E3_end --> E3; E3_end2 --> E3; +``` + +Flowchart for Reception FA, Phase D (MPS). The process starts at R\_D1\_MPS, goes through 'wait for 75ms', 'MPS', counter increment, and 'Response\_Reception (F,w)'. It then enters a loop based on 'w' and 'MPS\_transmission\_counter'. If 'w' is No, it checks the counter; if =3, it resets to 0 and goes to E2, otherwise it loops back. If 'w' is Yes, it resets the counter and checks 'F'. If 'F' is MCF, it goes through 'FA\_non\_busy\_packet' and 'Wait (w)'. If 'F' is RTP, RTN, PIP, PIN, it goes to R\_B3. If 'F' is else, it discards the frame and goes to E3. Finally, it checks 'w' again for outcomes E1, E2, E3, R\_C1, and R\_D1. + +Figure D.16: Reception FA, Phase D (MPS) + +![Flowchart for Reception FA, Phase D (EOM). The process starts at R_D1_EOM, goes through 'wait for 75ms', 'EOM', and 'EOM_transmission_counter := EOM_transmission_counter + 1'. It then enters 'Response_Reception (F,w)'. A decision 'w' follows: 'No' leads to 'EOM_transmission_counter' decision; 'Yes' leads to 'EOM_transmission_counter := 0' and then 'F' decision. 'EOM_transmission_counter' decision: '=3' leads to 'EOM_transmission_counter := 0' and then 'E3'; 'else' loops back to start. 'F' decision: 'RTP, RTN, PIP, PIN, MCF' leads to 'R'; 'else' leads to 'Discard the frame' and then 'E3'. 'E1' and 'E3' are also terminal points from the 'w' decision.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` +graph TD; R_D1_EOM((R_D1_EOM)) --> W[wait for 75ms]; W --> EOM{{EOM}}; EOM --> C1[EOM_transmission_counter := EOM_transmission_counter + 1]; C1 --> RR[Response_Reception (F,w)]; RR --> W_dec{w}; W_dec -- No --> EC_dec{EOM_transmission_counter}; W_dec -- Yes --> C2[EOM_transmission_counter := 0]; W_dec -- E1 --> E1((E1)); W_dec -- E3 --> E3a((E3)); EC_dec -- else --> R_D1_EOM; EC_dec -- =3 --> C3[EOM_transmission_counter := 0]; C3 --> E3b((E3)); C2 --> F_dec{F}; F_dec -- "RTP, RTN, PIP, PIN, MCF" --> R((R)); F_dec -- else --> DF[Discard the frame]; DF --> E3c((E3)); +``` + +Flowchart for Reception FA, Phase D (EOM). The process starts at R\_D1\_EOM, goes through 'wait for 75ms', 'EOM', and 'EOM\_transmission\_counter := EOM\_transmission\_counter + 1'. It then enters 'Response\_Reception (F,w)'. A decision 'w' follows: 'No' leads to 'EOM\_transmission\_counter' decision; 'Yes' leads to 'EOM\_transmission\_counter := 0' and then 'F' decision. 'EOM\_transmission\_counter' decision: '=3' leads to 'EOM\_transmission\_counter := 0' and then 'E3'; 'else' loops back to start. 'F' decision: 'RTP, RTN, PIP, PIN, MCF' leads to 'R'; 'else' leads to 'Discard the frame' and then 'E3'. 'E1' and 'E3' are also terminal points from the 'w' decision. + +Figure D.17: Reception FA, Phase D (EOM) + +![Flowchart for Reception FA, Phase D (EOP). The process starts at R_D1_EOP, goes through 'wait for 75ms', EOP, increments EOP_transmission_counter, and then checks 'Response Reception (F,w)'. It branches based on 'w' and 'F' conditions, leading to various states like 'Discard the frame', 'FA_non_busy packet', or end states E1, E2, E3, E4.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` +graph TD; R_D1_EOP((R_D1_EOP)) --> W1[wait for 75ms]; W1 --> EOP{EOP}; EOP --> INC1[EOP_transmission_counter := EOP_transmission_counter + 1]; INC1 --> RR[Response Reception F,w]; RR --> W1st{w}; W1st -- No --> E1((E1)); W1st -- Yes --> INC2[EOP_transmission_counter := 0]; W1st -- E3((E3)) --> E3; INC2 --> F{F}; F -- else --> DISCARD['Discard the frame']; F -- RTN,PIN --> WAIT_W[wait w]; F -- MCF,RTP,PIP --> FA_NBP[FA_non_busy packet]; WAIT_W --> W2st{w}; W2st -- else --> DISCARD; W2st -- E1 --> E1; W2st -- E2 --> E2; W2st -- E3 --> E3; DISCARD --> E4((E4)); DISCARD --> INC3[EOP_transmission_counter := 0]; INC3 --> INC1; INC1 --> W1st; W1st -- else --> INC3; W1st -- =3 --> INC3; +``` + +Flowchart for Reception FA, Phase D (EOP). The process starts at R\_D1\_EOP, goes through 'wait for 75ms', EOP, increments EOP\_transmission\_counter, and then checks 'Response Reception (F,w)'. It branches based on 'w' and 'F' conditions, leading to various states like 'Discard the frame', 'FA\_non\_busy packet', or end states E1, E2, E3, E4. + +Figure D.18: Reception FA, Phase D (EOP) + +![Flowchart for Transmission side FA for ECM, Phase D (Basic control flow).](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +The flowchart illustrates the transmission side FA for ECM, Phase D. It begins with a start node **T\_D2** leading to a decision diamond **F**. From **F**, the flow branches into six main paths: **RR**, **EOR\_PRI\_Q, EOR\_Q**, **PPS\_PRI\_Q, PPS\_Q**, **CTC**, **DCN**, and **else**. + +- RR path:** Leads to a decision diamond **'Last post message command was PPS PRI-Q or PPS-Q?'**. + - 'Yes':** Leads to end node **T\_D2\_res1**. + - 'else':** Leads to a decision diamond **'Is used PPR to avoid the timer time out of T.30?'**. + - 'Yes':** Leads to end node **T\_D2\_res1**. + - 'else':** Leads to process block **EOR\_Q\_packet**, which then leads to end node **T\_D2\_res2**. +- EOR\_PRI\_Q, EOR\_Q path:** Leads directly to end node **T\_D2\_res1**. +- PPS\_PRI\_Q, PPS\_Q path:** Leads to a decision diamond **'PPS\_PRI\_Q/PPS\_Q received again despite the image quality OK?'**. + - 'Yes':** Leads to end node **T\_D2\_res1**. + - 'else':** Leads to process block **PPS\_Q\_packet**, which then leads to end node **T\_D2\_res1**. +- CTC path:** Leads to process block **CTC\_packet**, then to a decision diamond **'R-FA busy?'**. + - 'Yes':** Leads to end node **E1**. + - 'else':** Leads to process block **'Wait for 75ms'**, then to a decision diamond **'Twa elapsed?'**. + - 'Yes':** Leads to end node **E1**. + - 'else':** Leads to process block **'Wait for 2.4s'**, then to process block **CTR**, which leads to end node **T\_B5**. +- DCN path:** Leads directly to end node **E1**. +- else path:** Leads to process block **'Discard the frame'**, which leads to end node **T\_B5**. + +Flowchart for Transmission side FA for ECM, Phase D (Basic control flow). + +Figure D.19: Transmission side FA for ECM, Phase D (Basic control flow) + +![Flowchart of the selection algorithm for MCF/PPR/RNR. The process starts at T_D2_res1, checks if R-FA is busy, waits if necessary, then checks quality. If quality is OK, it checks if a 66s timer has started. If not, it sets the timer and proceeds to T_B5. If the timer has started, it checks if PPR has been transmitted 3 times. If yes, it goes to E3. If no, it sends an RNR and proceeds to T_B5. If quality is not OK, it checks if a 66s timer has started. If not, it resets the timer and proceeds to MCF. If the timer has started, it proceeds to PPR and then to T_B5. Various callouts explain the logic for retransmission and timer usage.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + +graph TD + T_D2_res1((T_D2_res1)) --> RFA_busy{R-FA busy?} + RFA_busy -- Yes --> Wait_2_4s[Wait for 2.4s] + RFA_busy -- else --> Wait_75ms[Wait for 75ms] + Wait_2_4s --> RFA_busy2{R-FA busy?} + RFA_busy2 -- else --> Wait_75ms + RFA_busy2 -- Yes --> Twa_elapsed{Twa elapsed?} + Twa_elapsed -- Yes --> E1((E1)) + Twa_elapsed -- else --> Quality_OK{Quality OK?} + Quality_OK -- Yes --> PPR_transmit_3{PPR transmit 3 times?} + PPR_transmit_3 -- Yes --> G66_elapsed{66s elapsed?} + G66_elapsed -- Yes --> E3((E3)) + G66_elapsed -- else --> RNR[RNR] + RNR --> Has_66s_started{Has 66s timer started?} + Has_66s_started -- Yes --> T_B5_1((T_B5)) + Has_66s_started -- else --> set_66s[set 66s] + set_66s --> T_B5_1 + PPR_transmit_3 -- else --> PPR_1[PPR] + PPR_1 --> T_B5_1 + Quality_OK -- else --> Quality_OK2{Quality OK?} + Quality_OK2 -- Yes --> Has_66s_started2{Has 66s timer started?} + Has_66s_started2 -- Yes --> PPR_2[PPR] + Has_66s_started2 -- else --> reset_66s[reset 66s] + reset_66s --> MCF[MCF] + MCF --> T_B5_1 + PPR_2 --> T_B5_1 + +``` + +Request re-transmission of the frames which includes errors. +If there are frames remaining in the FA buffer that need to be sent to the network, re-transmission may be requested in order to allow more time for data transmission. +Only the retransmitted error frames shall be transmitted to NW. +The frames received twice or more shall not be transmitted to NW. + +Datalinks with the FAX which do not use T5 timer can be disconnected by 66S timer. + +The number of the frames that are requested to be re-transmitted, is determined according to the quality of radio interface. The frames received twice or more shall not be transmitted to NW. + +The number of frames that are requested to be re-transmitted is the number of frames requested for retransmission for FA buffer management. + +Request re-transmission of the frames which includes errors. + +Flowchart of the selection algorithm for MCF/PPR/RNR. The process starts at T\_D2\_res1, checks if R-FA is busy, waits if necessary, then checks quality. If quality is OK, it checks if a 66s timer has started. If not, it sets the timer and proceeds to T\_B5. If the timer has started, it checks if PPR has been transmitted 3 times. If yes, it goes to E3. If no, it sends an RNR and proceeds to T\_B5. If quality is not OK, it checks if a 66s timer has started. If not, it resets the timer and proceeds to MCF. If the timer has started, it proceeds to PPR and then to T\_B5. Various callouts explain the logic for retransmission and timer usage. + +Figure D.20: Selection algorithm for MCF/PPR/RNR + +![State transition diagram for ERR / RNR ECM. It starts at T_D2_res2, checks if R-FA is busy. If yes, it waits for 2.4s and checks again. If still yes, it checks if Twa elapsed. If yes, it goes to E1. If no, it checks if 66s elapsed. If yes, it goes to E3. If no, it performs RNR and checks if the 66s timer started. If yes, it goes to T_B5. If no, it sets the 66s timer and goes to T_B5. If R-FA is not busy initially, it waits for 75ms and checks if the 66s timer started. If yes, it resets the 66s timer and goes to T_B5. If no, it goes to ERR and then to T_B5.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +``` +stateDiagram-v2 + [*] --> T_D2_res2 + T_D2_res2 --> R_FA_busy_1{R-FA busy} + R_FA_busy_1 --> Wait_2_4s[Wait for 2.4s] : Yes + R_FA_busy_1 --> Wait_75ms[Wait for 75ms] : else + Wait_2_4s --> R_FA_busy_2{R-FA busy} + R_FA_busy_2 --> Twa_elapsed{Twa elapsed?} : Yes + R_FA_busy_2 --> Wait_75ms : else + Twa_elapsed --> E1((E1)) : Yes + Twa_elapsed --> SixtySixs_elapsed{66s elapsed?} : else + SixtySixs_elapsed --> E3((E3)) : Yes + SixtySixs_elapsed --> RNR{{RNR}} : else + RNR --> Has_66s_timer_started_1{Has 66s timer_started?} + Has_66s_timer_started_1 --> T_B5((T_B5)) : Yes + Has_66s_timer_started_1 --> Set_66s[set (66s)] : else + Set_66s --> T_B5 + Wait_75ms --> Has_66s_timer_started_2{Has 66s timer_started?} + Has_66s_timer_started_2 --> Reset_66s[reset (66s)] : Yes + Has_66s_timer_started_2 --> ERR{{ERR}} : else + Reset_66s --> T_B5 + ERR --> T_B5 +``` + +State transition diagram for ERR / RNR ECM. It starts at T\_D2\_res2, checks if R-FA is busy. If yes, it waits for 2.4s and checks again. If still yes, it checks if Twa elapsed. If yes, it goes to E1. If no, it checks if 66s elapsed. If yes, it goes to E3. If no, it performs RNR and checks if the 66s timer started. If yes, it goes to T\_B5. If no, it sets the 66s timer and goes to T\_B5. If R-FA is not busy initially, it waits for 75ms and checks if the 66s timer started. If yes, it resets the 66s timer and goes to T\_B5. If no, it goes to ERR and then to T\_B5. + +Figure D.21: Selection for ERR / RNR ECM + +![Flowchart for Reception side FA for ECM, Phase D (Basic control flow).](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +``` + +graph TD + R_D2((R_D2)) --> set66[set (66s)] + set66 --> set3[set (3s)] + set3 --> wait_pkt([wait_for_packet_received_from_NW_in_ECM]) + + wait_pkt --> PPS_NULL{{PPS_NULL packet}} + wait_pkt --> PPS_MPS{{PPS_MPS packet}} + wait_pkt --> PPS_EOM{{PPS_EOM packet}} + wait_pkt --> PPS_EOP{{PPS_EOP packet}} + wait_pkt --> CTC_pkt{{CTC_packet}} + wait_pkt --> T3s{{3s}} + + PPS_NULL --> res1[reset (3s); +reset (66s);] + res1 --> RD2N((R_D2_NULL)) + + PPS_MPS --> res2[reset (3s); +reset (66s);] + res2 --> RD2M((R_D2_MPS)) + + PPS_EOM --> res3[reset (3s); +reset (66s);] + res3 --> RD2EOM((R_D2_EOM)) + + PPS_EOP --> res4[reset (3s); +reset (66s);] + res4 --> RD2EOP((R_D2_EOP)) + + CTC_pkt --> res5[reset (3s); +reset (66s);] + res5 --> wait75a[wait for 75ms] + wait75a --> CTC_node + + T3s --> wait75b[wait for 75ms] + wait75b --> preamble[preamble] + preamble --> CTC_node + + CTC_node{CTC} --> CTC_note["Regarding the data signalling rate specified with CTC, use the specified one with CTC_packet. If, however, the specified data signalling rate with CTC_packet is higher than the current one between the R-FA and R-FAX, use the current one instead of CTC_packet one."] + CTC_node --> inc_ctr[CTC_transmission_counter := +CTC_transmission_counter + 1] + inc_ctr --> resp_rec[Response_Reception +(F,w)] + resp_rec --> dec_w{w} + + dec_w -- Yes --> dec_ctr{CTC_transmission_counter} + dec_ctr -- "=3" --> res_ctr[CTC_transmission_counter := 0] + res_ctr --> E3_conn((E3)) + dec_ctr -- else --> E1_conn((E1)) + + dec_w -- No --> E3_conn + + resp_rec --> dec_F{F} + dec_F -- CTR --> FA_busy{{FA_non_busy_packet}} + FA_busy --> wait_w[Wait (w)] + wait_w --> dec_w2{w} + dec_w2 -- E3 --> E3_conn + dec_w2 -- E1 --> E1_conn2((E1)) + dec_w2 -- E2 --> E2_conn2((E2)) + dec_w2 -- W_packet --> RD2_loop((R_D2)) + dec_w2 -- W_pix --> RC2_conn((R_C2)) + + dec_F -- else --> res_ctr2[CTC_transmission_counter := 0] + res_ctr2 --> E3_conn + + EOR_Q{{EOR_Q_packet}} --> res6[reset (3s); +reset (66s);] + res6 --> EOR_FCF2{EOR_FCF2} + EOR_FCF2 -- "'EOR_NULL'" --> RD2EN((R_D2_E_NULL)) + EOR_FCF2 -- "'EOR_EOM'" --> RD2EEOM((R_D2_E_EOM)) + EOR_FCF2 -- "'EOR_MPS'" --> RD2EMPS((R_D2_E_MPS)) + EOR_FCF2 -- "'EOR_EOP'" --> RD2EEOP((R_D2_E_EOP)) + + DCN{{DCN_packet}} --> FA_busy2{{FA_non_busy_packet}} + FA_busy2 --> res7[reset (3s); +reset (66s);] + res7 --> E2_conn((E2)) + + star{{*}} --> FA_busy3{{FA_non_busy_packet}} + FA_busy3 --> res8[reset (3s); +reset (66s);] + res8 --> discard['Discard the signal'] + discard --> E2_conn + + T66s{{66s}} --> E3_conn + +``` + +The flowchart illustrates the state transitions for the R\_D2 state machine in the reception side FA for ECM, Phase D. It begins with state R\_D2, setting 66s and 3s timers, and waiting for a packet from the network. The logic branches based on the received packet type (PPS\_NULL, PPS\_MPS, PPS\_EOM, PPS\_EOP, CTC, or 3s timeout). PPS packets lead to timer resets and specific R\_D2 sub-states. CTC packets or 3s timeouts lead to CTC signal processing, which includes a transmission counter and response reception logic (F, w). Decisions based on 'w' and the counter lead to states E1, E3, or loops back to R\_D2/R\_C2. Other paths handle EOR\_Q, DCN, and wildcard packets, leading to EOR sub-states, E2, or signal discarding. + +Flowchart for Reception side FA for ECM, Phase D (Basic control flow). + +**Figure D.22: Reception side FA for ECM, Phase D (Basic control flow)** + +![Flowchart for Reception FA, Phase D (PPS-NULL). The process starts at R_D2_NULL, goes through 'wait for 75ms', then PPS_NULL. It checks if PPS_NULL_transmission_counter equals 3. If yes, it resets the counter to 0 and goes to E3. If no, it increments the counter and proceeds to Response_Reception (F,w). From there, it checks 'w'. If 'w' is No, it goes to E1. If 'w' is Yes, it resets the counter to 0 and proceeds to decision 'F'. Decision 'F' branches into RNR, else, and MCF. RNR leads to FA_busy_packet and then RR_Response_Reception (F,w). MCF leads to 'reset (66s)' and then 'FA non_busy packet'. The 'else' branch of 'F' leads to decision 'PPR' (Does an error frame exist in the FCD_packet?). If 'Yes', it goes to 'FA non_busy packet'. If 'else', it goes to 'FA_busy_packet'. Both 'FA_busy_packet' paths lead to decision '4th PPR?'. If 'Yes', it goes to R_D2_E_NULL. If 'else', it goes to 'requested frame' and then R_D2_NULL. 'requested frame' also leads to 'Transmit frames that is requested to retransmit'. 'FA non_busy packet' leads to 'Wait (w)' and then decision 'w'. If 'w' is Yes, it goes to E1. If 'w' is No, it goes to E3. 'RR_Response_Reception (F,w)' leads to decision 'w'. If 'w' is Yes, it goes to E1. If 'w' is No, it goes to E3. 'reset (66s)' leads to 'Discard the frame' and then E3. 'Discard the frame' also leads to E3. 'Wait (w)' leads to decision 'w'. If 'w' is Yes, it goes to E1. If 'w' is No, it goes to E3. 'W_packet' leads to R_D2 and then R_C2. 'W_pix' leads to R_C2. 'E1' leads to E2. 'E2' leads to E3.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` + +graph TD + R_D2_NULL((R_D2_NULL)) --> W75ms[wait for 75ms] + W75ms --> PPS_NULL{PPS_NULL} + PPS_NULL --> IncCounter[PPS_NULL_transmission_counter := PPS_NULL_transmission_counter + 1] + IncCounter --> RR[Response_Reception F,w] + RR --> w1{w} + w1 -- No --> E1((E1)) + w1 -- Yes --> ResetCounter1[PPS_NULL_transmission_counter := 0] + ResetCounter1 --> F{F} + F -- RNR --> FA_busy1[FA_busy_packet] + FA_busy1 --> RR_Fw1[Response_Reception F,w] + RR_Fw1 --> w2{w} + w2 -- Yes --> E1 + w2 -- No --> E3_1((E3)) + F -- else --> Reset66s1[reset 66s] + Reset66s1 --> Discard[Discard the frame] + Discard --> E3_2((E3)) + F -- MCF --> Reset66s2[reset 66s] + Reset66s2 --> FA_non_busy1[FA non_busy packet] + FA_non_busy1 --> WaitW1[Wait w] + WaitW1 --> w3{w} + w3 -- Yes --> E1 + w3 -- No --> E3_3((E3)) + F -- PPR --> ErrorFrame{Does an error frame exist in the FCD_packet?} + ErrorFrame -- Yes --> FA_non_busy2[FA non_busy packet] + ErrorFrame -- else --> FA_busy2[FA_busy_packet] + FA_busy2 --> 4thPPR{4th PPR?} + 4thPPR -- Yes --> R_D2_E_NULL((R_D2_E_NULL)) + 4thPPR -- else --> RequestedFrame[requested frame] + RequestedFrame --> R_D2_NULL + RequestedFrame --> Transmit[Transmit frames that is requested to retransmit] + RR_Fw1 --> w4{w} + w4 -- Yes --> E1 + w4 -- No --> E3_4((E3)) + Discard --> E3_5((E3)) + E1 --> E2((E2)) + E2 --> E3_6((E3)) + W_packet[W_packet] --> R_D2((R_D2)) + R_D2 --> R_C2((R_C2)) + W_pix[W_pix] --> R_C2 + +``` + +Flowchart for Reception FA, Phase D (PPS-NULL). The process starts at R\_D2\_NULL, goes through 'wait for 75ms', then PPS\_NULL. It checks if PPS\_NULL\_transmission\_counter equals 3. If yes, it resets the counter to 0 and goes to E3. If no, it increments the counter and proceeds to Response\_Reception (F,w). From there, it checks 'w'. If 'w' is No, it goes to E1. If 'w' is Yes, it resets the counter to 0 and proceeds to decision 'F'. Decision 'F' branches into RNR, else, and MCF. RNR leads to FA\_busy\_packet and then RR\_Response\_Reception (F,w). MCF leads to 'reset (66s)' and then 'FA non\_busy packet'. The 'else' branch of 'F' leads to decision 'PPR' (Does an error frame exist in the FCD\_packet?). If 'Yes', it goes to 'FA non\_busy packet'. If 'else', it goes to 'FA\_busy\_packet'. Both 'FA\_busy\_packet' paths lead to decision '4th PPR?'. If 'Yes', it goes to R\_D2\_E\_NULL. If 'else', it goes to 'requested frame' and then R\_D2\_NULL. 'requested frame' also leads to 'Transmit frames that is requested to retransmit'. 'FA non\_busy packet' leads to 'Wait (w)' and then decision 'w'. If 'w' is Yes, it goes to E1. If 'w' is No, it goes to E3. 'RR\_Response\_Reception (F,w)' leads to decision 'w'. If 'w' is Yes, it goes to E1. If 'w' is No, it goes to E3. 'reset (66s)' leads to 'Discard the frame' and then E3. 'Discard the frame' also leads to E3. 'Wait (w)' leads to decision 'w'. If 'w' is Yes, it goes to E1. If 'w' is No, it goes to E3. 'W\_packet' leads to R\_D2 and then R\_C2. 'W\_pix' leads to R\_C2. 'E1' leads to E2. 'E2' leads to E3. + +Figure D.23: Reception FA, Phase D (PPS-NULL) + +![Flowchart for Reception FA, Phase D (PPS-MPS)](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` + +graph TD + R_D2_MPS((R_D2_MPS)) --> W75ms[wait for 75ms] + W75ms --> PPS_MPS{PPS_MPS} + PPS_MPS --> TC_INC[PPS_MPS_transmission_counter := +PPS_MPS_transmission_counter + 1] + TC_INC --> RR[Response_Reception +(F,w)] + RR --> W_DEC{w} + W_DEC -- No --> F_DEC{F} + W_DEC -- Yes --> TC_RESET[PPS_MPS_transmission_counter := 0] + W_DEC -- E1 --> E1_CIRC((E1)) + W_DEC -- E3 --> E3_CIRC((E3)) + + PPS_MPS -- else --> TC_CHECK{PPS_MPS_transmission_counter} + TC_CHECK -- "=3" --> E3_TERM((E3)) + TC_CHECK -- else --> R_D2_MPS + + TC_RESET --> F_DEC + + F_DEC -- RNR --> FA_BUSY_P[FA_busy_ +packet] + FA_BUSY_P --> RR_REC[RR_Response_Reception +(F,w)] + RR_REC --> W_DEC2{w} + W_DEC2 -- Yes --> E1_TERM2((E1)) + W_DEC2 -- "No, E3" --> E3_TERM2((E3)) + + F_DEC -- else --> RESET1[reset (66s)] + RESET1 --> DISCARD['Discard +the frame'] + DISCARD --> E3_TERM3((E3)) + + F_DEC -- "PIP,PIN" --> RESET2[reset (66s)] + RESET2 --> FA_NON_BUSY1[FA_non_busy_ +packet] + FA_NON_BUSY1 --> R_B3_TERM((R_B3)) + + F_DEC -- MCF --> RESET3[reset (66s)] + RESET3 --> FA_NON_BUSY2[FA_non_busy_ +packet] + FA_NON_BUSY2 --> WAIT_W[Wait (w)] + + F_DEC -- PPR --> ERR_CHECK{Does an error +frame exist in the +radio-received +FCD block?} + ERR_CHECK -- Yes --> FA_NON_BUSY2 + ERR_CHECK -- else --> FA_BUSY2[FA_busy_ +packet] + FA_BUSY2 --> PPR4_CHECK{4th PPR?} + PPR4_CHECK -- Yes --> R_D2_E_MPS_TERM((R_D2_E_MPS)) + PPR4_CHECK -- else --> RETRANSMIT[retransmit +frame] + RETRANSMIT --> R_D2_MPS + + WAIT_W --> TRANS_REQ[Transmit frame +that is requested +to retransmit] + TRANS_REQ --> W_DEC3{w} + W_DEC3 -- E3 --> E3_TERM4((E3)) + W_DEC3 -- E2 --> E2_TERM((E2)) + W_DEC3 -- E1 --> E1_TERM3((E1)) + W_DEC3 -- W_packet --> R_D2_TERM((R_D2)) + W_DEC3 -- W_pix --> R_C2_TERM((R_C2)) + +``` + +Flowchart for Reception FA, Phase D (PPS-MPS) + +Figure D.24: Reception FA, Phase D (PPS-MPS) + +![Flowchart for Reception FA, Phase D (PPS-EOP). The process starts at R_D2_EOP, waits for 75ms, then checks PPS_EOP. It enters a loop for PPS_EOP transmission, incrementing a counter. If the counter reaches 3, it goes to E3. Otherwise, it performs Response_Reception (F,w). If 'w' is No, it goes to E1 or E3. If 'w' is Yes, it resets the counter and checks condition F. Condition F branches into RNR, else (reset 66s, discard signal), MCF/PIP/PIN (reset 66s, FA_non_busy packet, wait w), and PPR. PPR checks for an error frame in the FCD block. If 'Yes', it sends FA_non_busy packet and waits w. If 'else', it sends FA_busy packet and checks '4th PPR?'. If '4th PPR?' is Yes, it goes to R_D2_E_O_P and transmits the frame. If 'else', it goes to retransmit frame and then R_D2_E_O_P. Various other states E1, E2, E3, E4, R_D2, R_C2, and R_D2_E_O_P are shown as outcomes.](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` + +graph TD + Start((R_D2_EOP)) --> Wait75ms[wait for 75ms] + Wait75ms --> PPS_EOP{PPS_EOP} + PPS_EOP --> CounterInc[PPS_EOP_transmission_counter := PPS_EOP_transmission_counter + 1] + CounterInc --> ResponseRec[Response_Reception F,w] + ResponseRec --> W{w} + W -- No --> E1((E1)) + W -- No --> E3_1((E3)) + W -- Yes --> CounterReset[PPS_EOP_transmission_counter := 0] + CounterReset --> F{F} + F -- RNR --> FA_busy_1[FA_busy packet] + FA_busy_1 --> RR_ResponseRec[RR_Response_Reception F,w] + RR_ResponseRec -- Yes --> W_1{w} + W_1 -- No, E3 --> E3_2((E3)) + W_1 -- Yes --> E1_1((E1)) + F -- else --> Reset1[reset 66s] + Reset1 --> Discard[Discard the signal] + Discard --> E3_3((E3)) + F -- MCF, PIP, PIN --> Reset2[reset 66s] + Reset2 --> FA_non_busy_1[FA_non_busy packet] + FA_non_busy_1 --> WaitW_1[Wait w] + WaitW_1 --> W_2{w} + W_2 -- E1 --> E1_2((E1)) + W_2 -- E2 --> E2_1((E2)) + W_2 -- E3 --> E3_4((E3)) + F -- PPR --> ErrorFrame{Does an error frame exist in the radio-received FCD block?} + ErrorFrame -- Yes --> FA_non_busy_2[FA_non_busy packet] + FA_non_busy_2 --> WaitW_2[Wait w] + WaitW_2 --> W_3{w} + W_3 -- E1 --> E1_3((E1)) + W_3 -- E2 --> E2_2((E2)) + W_3 -- E3 --> E3_5((E3)) + W_3 -- W_packet --> R_D2((R_D2)) + W_3 -- W_pix --> R_C2((R_C2)) + ErrorFrame -- else --> FA_busy_2[FA_busy packet] + FA_busy_2 --> PPR4{4th PPR?} + PPR4 -- Yes --> R_D2_E_O_P_1((R_D2_E_O_P)) + PPR4 -- else --> Retransmit[retransmit frame] + Retransmit --> R_D2_E_O_P_2((R_D2_E_O_P)) + R_D2_E_O_P_1 --> TransmitFrame[Transmit frame that is requested to retransmit] + TransmitFrame --> R_D2_E_O_P_2 + F -- else --> CounterCheck[PPS_EOP_transmission_counter = 3] + CounterCheck --> CounterReset2[PPS_EOP_transmission_counter := 0] + CounterReset2 --> E3_6((E3)) + +``` + +Flowchart for Reception FA, Phase D (PPS-EOP). The process starts at R\_D2\_EOP, waits for 75ms, then checks PPS\_EOP. It enters a loop for PPS\_EOP transmission, incrementing a counter. If the counter reaches 3, it goes to E3. Otherwise, it performs Response\_Reception (F,w). If 'w' is No, it goes to E1 or E3. If 'w' is Yes, it resets the counter and checks condition F. Condition F branches into RNR, else (reset 66s, discard signal), MCF/PIP/PIN (reset 66s, FA\_non\_busy packet, wait w), and PPR. PPR checks for an error frame in the FCD block. If 'Yes', it sends FA\_non\_busy packet and waits w. If 'else', it sends FA\_busy packet and checks '4th PPR?'. If '4th PPR?' is Yes, it goes to R\_D2\_E\_O\_P and transmits the frame. If 'else', it goes to retransmit frame and then R\_D2\_E\_O\_P. Various other states E1, E2, E3, E4, R\_D2, R\_C2, and R\_D2\_E\_O\_P are shown as outcomes. + +Figure D.25: Reception FA, Phase D (PPS-EOP) + +![Flowchart for Reception FA, Phase D (PPS-EOM). The process starts at R_D2_EOM, goes through 'wait for 75ms', PPS_EOM, and increments the transmission counter. It then checks if the counter equals 3. If so, it resets the counter and ends at E2. Otherwise, it calls Response_Reception(F,w) and checks condition 'w'. If 'w' is No, it loops back to the start. If 'w' is Yes, it resets the counter and proceeds to decision 'F'. Decision 'F' branches into RNR, else, and MCF, PIP, PIN. The MCF, PIP, PIN branch leads to a decision 'Does an error frame exist in the radio-received FCD block?'. If Yes, it sends FA_non_busy_packet, waits 'w', and checks 'w' again. If 'w' is No, it ends at E3. If 'w' is Yes, it sends W_packet to R_D2 and W_pix to R_C2. If the error frame decision is else, it checks '4th PPR?'. If Yes, it ends at R_D2_E_EOM. If else, it retransmits the frame and ends at R_D2_E_EOM. The RNR branch leads to FA_busy_packet and RR_Response_Reception(F,w). If 'w' is Yes, it ends at E1. If else, it ends at E3. The 'else' branch of 'F' leads to reset (66s), Discard the frame, and ends at E3. The MCF, PIP, PIN branch also has a reset (66s) path leading to FA_non_busy_packet and then to R.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` + +graph TD + Start((R_D2_EOM)) --> Wait75ms[wait for 75ms] + Wait75ms --> PPS_EOM[PPS_EOM] + PPS_EOM --> CounterInc[PPS_EOM_transmission_counter := PPS_EOM_transmission_counter + 1] + CounterInc --> CounterCheck{PPS_EOM_transmission_counter} + CounterCheck -- "=3" --> CounterReset[PPS_EOM_transmission_counter := 0] + CounterReset --> E2((E2)) + CounterCheck -- else --> Start + CounterInc --> ResponseReception[Response_Reception F,w] + ResponseReception --> WCheck{w} + WCheck -- No --> Start + WCheck -- Yes --> CounterReset2[PPS_EOM_transmission_counter := 0] + CounterReset2 --> FCheck{F} + FCheck -- RNR --> FABusy1[FA_busy_packet] + FABusy1 --> RRResponseReception[RR_Response_Reception F,w] + RRResponseReception --> WCheck1{w} + WCheck1 -- Yes --> E1_1((E1)) + WCheck1 -- else --> E3_1((E3)) + FCheck -- else --> Reset1[reset 66s] + Reset1 --> Discard[Discard the frame] + Discard --> E3_2((E3)) + FCheck -- "MCF, PIP, PIN" --> Reset2[reset 66s] + Reset2 --> FANonBusy1[FA_non_busy_packet] + FANonBusy1 --> R((R)) + FCheck -- PPR --> ErrorFrame{Does an error frame exist in the radio-received FCD block?} + ErrorFrame -- Yes --> FANonBusy2[FA_non_busy_packet] + FANonBusy2 --> WaitW[Wait w] + WaitW --> WCheck2{w} + WCheck2 -- No --> E3_3((E3)) + WCheck2 -- Yes --> WPacket[R_D2 W_packet] + WCheck2 -- Yes --> WPix[R_C2 W_pix] + ErrorFrame -- else --> FABusy2[FA_busy_packet] + FABusy2 --> PPR4{4th PPR?} + PPR4 -- Yes --> RD2EOM((R_D2_E_EOM)) + PPR4 -- else --> Retransmit[retransmit frame] + Retransmit --> RD2EOM + Retransmit --> TransmitFrame[Transmit frame that is requested to retransmit] + TransmitFrame --> RD2EOM + +``` + +Flowchart for Reception FA, Phase D (PPS-EOM). The process starts at R\_D2\_EOM, goes through 'wait for 75ms', PPS\_EOM, and increments the transmission counter. It then checks if the counter equals 3. If so, it resets the counter and ends at E2. Otherwise, it calls Response\_Reception(F,w) and checks condition 'w'. If 'w' is No, it loops back to the start. If 'w' is Yes, it resets the counter and proceeds to decision 'F'. Decision 'F' branches into RNR, else, and MCF, PIP, PIN. The MCF, PIP, PIN branch leads to a decision 'Does an error frame exist in the radio-received FCD block?'. If Yes, it sends FA\_non\_busy\_packet, waits 'w', and checks 'w' again. If 'w' is No, it ends at E3. If 'w' is Yes, it sends W\_packet to R\_D2 and W\_pix to R\_C2. If the error frame decision is else, it checks '4th PPR?'. If Yes, it ends at R\_D2\_E\_EOM. If else, it retransmits the frame and ends at R\_D2\_E\_EOM. The RNR branch leads to FA\_busy\_packet and RR\_Response\_Reception(F,w). If 'w' is Yes, it ends at E1. If else, it ends at E3. The 'else' branch of 'F' leads to reset (66s), Discard the frame, and ends at E3. The MCF, PIP, PIN branch also has a reset (66s) path leading to FA\_non\_busy\_packet and then to R. + +Figure D.26: Reception FA, Phase D (PPS-EOM) + +![Flowchart for Reception FA, Phase D (EOR-NULL). The process starts at R_D2_E_NULL, goes through a 75ms wait, then checks EOR_NULL. If transmission counter reaches 3, it goes to E3. Otherwise, it increments the counter and checks for a response. If no response (w), it checks EOR_NULL transmission counter. If 3, it goes to E3. If not, it resets the counter and checks F. F can lead to RNR (busy packet), else (reset), or ERR (reset, non busy packet, wait). After RNR or ERR, it checks w. If Yes, it loops back. If No, it goes to E3. If w is Yes, it goes to E1. If w is No, it goes to E3. If w is W_packet, it goes to R_D2. If w is W_pix, it goes to R_C2.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` +graph TD; R_D2_E_NULL((R_D2_E_NULL)) --> W75ms['wait for 75ms']; W75ms --> EOR_NULL{EOR_NULL}; EOR_NULL --> TC[EOR_NULL transmission counter := EOR_NULL transmission counter + 1]; TC --> RR[Response Reception (F,w)]; RR --> W{w}; W -- No --> TC2{EOR_NULL transmission counter}; TC2 -- =3 --> E3_1((E3)); TC2 -- else --> TC3[EOR_NULL transmission counter := 0]; TC3 --> F{F}; W -- Yes --> TC4[EOR_NULL transmission counter := 0]; TC4 --> F; F -- RNR --> FB[FA_busy_packet]; FB --> RR2[RR_Response_Reception (F,w)]; RR2 --> W2{w}; W2 -- Yes --> F; W2 -- No --> E3_2((E3)); F -- else --> R1[reset (66s)]; R1 --> DF['Discard the frame']; DF --> E3_3((E3)); F -- ERR --> R2[reset (66s)]; R2 --> FNP[FA_non_busy_packet]; FNP --> W3[wait (w)]; W3 --> W4{w}; W4 -- E2 --> E2_1((E2)); W4 -- E3 --> E3_4((E3)); W4 -- W_packet --> R_D2((R_D2)); W4 -- W_pix --> R_C2((R_C2)); +``` + +Flowchart for Reception FA, Phase D (EOR-NULL). The process starts at R\_D2\_E\_NULL, goes through a 75ms wait, then checks EOR\_NULL. If transmission counter reaches 3, it goes to E3. Otherwise, it increments the counter and checks for a response. If no response (w), it checks EOR\_NULL transmission counter. If 3, it goes to E3. If not, it resets the counter and checks F. F can lead to RNR (busy packet), else (reset), or ERR (reset, non busy packet, wait). After RNR or ERR, it checks w. If Yes, it loops back. If No, it goes to E3. If w is Yes, it goes to E1. If w is No, it goes to E3. If w is W\_packet, it goes to R\_D2. If w is W\_pix, it goes to R\_C2. + +Figure D.27: Reception FA, Phase D (EOR-NULL) + +![Flowchart for Reception FA, Phase D (EOR-MPS). The process starts at R_D2_E_MPS, goes through a 75ms wait, then checks for EOR_MPS. It then increments a transmission counter and checks if it equals 3. If so, it resets the counter and ends at E3. Otherwise, it checks condition 'w'. If 'No', it ends at E1 or E3. If 'Yes', it resets the counter and proceeds to decision 'F'. Decision 'F' branches into RNR, else, PIP, PIN, and ERR. RNR leads to FA_busy_packet and then a 'w' condition. else leads to a 66s reset and 'Discard the frame'. PIP, PIN leads to a 66s reset and FA_non_busy_packet. ERR leads to a 66s reset and FA_non_busy_packet. The flowchart ends at various states including E1, E2, E3, R_D2, and R_C2.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` +graph TD + Start((R_D2_E_MPS)) --> Wait75ms[wait for 75ms] + Wait75ms --> EOR_MPS{EOR_MPS} + EOR_MPS --> CounterInc[EOR_MPS_transmission_counter := EOR_MPS_transmission_counter + 1] + CounterInc --> CounterCheck{EOR_MPS_transmission_counter} + CounterCheck -- "=3" --> CounterReset[EOR_MPS_transmission_counter := 0] + CounterReset --> E3_1((E3)) + CounterCheck -- "else" --> W_1{w} + W_1 -- "No" --> E1_1((E1)) + W_1 -- "Yes" --> CounterReset2[EOR_MPS_transmission_counter := 0] + CounterReset2 --> F{F} + F -- "RNR" --> FA_busy_packet[/FA_busy_packet/] + FA_busy_packet --> RR_Response_Reception[Response_Reception (F,w)] + RR_Response_Reception --> W_2{w} + W_2 -- "Yes" --> E1_2((E1)) + W_2 -- "No, E3" --> E3_2((E3)) + F -- "else" --> Reset1[reset (66s)] + Reset1 --> Discard[Discard the frame] + Discard --> E3_3((E3)) + F -- "PIP, PIN" --> Reset2[reset (66s)] + Reset2 --> FA_non_busy_packet1[/FA_non_busy_packet/] + FA_non_busy_packet1 --> R_B3((R_B3)) + F -- "ERR" --> Reset3[reset (66s)] + Reset3 --> FA_non_busy_packet2[/FA_non_busy_packet/] + FA_non_busy_packet2 --> WaitW[Wait (w)] + WaitW --> W_3{w} + W_3 -- "E1" --> E1_3((E1)) + W_3 -- "E2" --> E2_3((E2)) + W_3 -- "E3" --> E3_4((E3)) + W_3 -- "W_packet" --> R_D2((R_D2)) + W_3 -- "W_pix" --> R_C2((R_C2)) +``` + +Flowchart for Reception FA, Phase D (EOR-MPS). The process starts at R\_D2\_E\_MPS, goes through a 75ms wait, then checks for EOR\_MPS. It then increments a transmission counter and checks if it equals 3. If so, it resets the counter and ends at E3. Otherwise, it checks condition 'w'. If 'No', it ends at E1 or E3. If 'Yes', it resets the counter and proceeds to decision 'F'. Decision 'F' branches into RNR, else, PIP, PIN, and ERR. RNR leads to FA\_busy\_packet and then a 'w' condition. else leads to a 66s reset and 'Discard the frame'. PIP, PIN leads to a 66s reset and FA\_non\_busy\_packet. ERR leads to a 66s reset and FA\_non\_busy\_packet. The flowchart ends at various states including E1, E2, E3, R\_D2, and R\_C2. + +Figure D.28: Reception FA, Phase D (EOR-MPS) + +![Flowchart for Reception FA, Phase D (EOR-EOP).](5e9af8986a5845504f251d3079da8078_img.jpg) + +``` + +graph TD + Start((R_D2_E_EOP)) --> Wait75[wait for 75ms] + Wait75 --> EOR_EOP[/EOR_EOP/] + EOR_EOP --> IncCounter[EOR_EOP_transmission_counter := +EOR_EOP_transmission_counter + 1] + IncCounter --> RespRec[Response_Reception +(F,w)] + RespRec --> DecW{w} + + DecW -- No --> DecCount{EOR_EOP_transmission_counter} + DecCount -- "=3" --> ResetCount[EOR_EOP_transmission_counter := 0] + ResetCount --> E3_1((E3)) + DecCount -- else --> Wait75 + + DecW -- Yes --> ResetCount2[EOR_EOP_transmission_counter := 0] + ResetCount2 --> DecF{F} + + DecF -- RNR --> FABusy[/FA_busy_packet/] + FABusy --> RRRespRec[RR_Response_Reception +(F,w)] + RRRespRec --> DecW2{w} + DecW2 -- Yes --> E1_1((E1)) + DecW2 -- "No, E3" --> E3_2((E3)) + + DecF -- else --> Reset66_1[reset (66s)] + Reset66_1 --> Discard['Discard the frame'] + Discard --> E3_3((E3)) + + DecF -- "ERR, +PIP, +PIN" --> Reset66_2[reset (66s)] + Reset66_2 --> FANonBusy[/FA_non_busy_packet/] + FANonBusy --> WaitW[Wait (w)] + WaitW --> DecW3{w} + DecW3 -- E2 --> E2_1((E2)) + DecW3 -- else --> E1_2((E1)) + + DecW -- E1 --> E1_3((E1)) + DecW -- E3 --> E3_4((E3)) + +``` + +Flowchart for Reception FA, Phase D (EOR-EOP). + +**Figure D.29: Reception FA, Phase D (EOR-EOP)** + +![Flowchart for Reception FA, Phase D (EOR-EOM). The process starts at R_D2_E_EOM, goes through 'wait for 75ms', then checks EOR_EOM. If not EOR_EOM, it increments a counter and checks 'Response_Reception (F,w)'. If 'w' is No, it checks EOR_EOM_transmission_counter. If =3, it resets the counter to 0 and goes to E3. If else, it loops back. If 'w' is Yes, it resets the counter to 0 and checks 'F'. If 'F' is RNR, it sends 'FA_busy_packet' and checks 'RR_Response_Reception (F,w)'. If 'w' is Yes, it goes to E1. If 'w' is No, it goes to E3. If 'F' is else, it sends 'reset (66s)', 'Discard the frame', and goes to E3. If 'F' is ERR, PIP, PIN, it sends 'FA_non_busy_packet', 'reset (66s)', and goes to R.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` +graph TD; R_D2_E_EOM((R_D2_E_EOM)) --> W["'wait for 75ms'"]; W --> EOR_EOM{EOR_EOM}; EOR_EOM -- No --> INC["EOR_EOM_transmission_counter := EOR_EOM_transmission_counter + 1"]; INC --> RR["Response_Reception (F,w)"]; RR --> W_cond{w}; W_cond -- No --> COUNTER{EOR_EOM_transmission_counter}; COUNTER -- "=3" --> RESET_C["EOR_EOM_transmission_counter := 0"]; RESET_C --> E3_1((E3)); COUNTER -- else --> INC; W_cond -- Yes --> RESET_W["EOR_EOM_transmission_counter := 0"]; RESET_W --> F_cond{F}; F_cond -- RNR --> FA_BUSY[FA_busy_packet]; FA_BUSY --> RR_F["RR_Response_Reception (F,w)"]; RR_F --> W_F{w}; W_F -- Yes --> E1_1((E1)); W_F -- No --> E3_2((E3)); F_cond -- else --> RES1["reset (66s)"]; RES1 --> DISCARD["'Discard the frame'"]; DISCARD --> E3_3((E3)); F_cond -- "ERR, PIP, PIN" --> FA_NON_BUSY[FA_non_busy_packet]; FA_NON_BUSY --> RES2["reset (66s)"]; RES2 --> R((R)); +``` + +Flowchart for Reception FA, Phase D (EOR-EOM). The process starts at R\_D2\_E\_EOM, goes through 'wait for 75ms', then checks EOR\_EOM. If not EOR\_EOM, it increments a counter and checks 'Response\_Reception (F,w)'. If 'w' is No, it checks EOR\_EOM\_transmission\_counter. If =3, it resets the counter to 0 and goes to E3. If else, it loops back. If 'w' is Yes, it resets the counter to 0 and checks 'F'. If 'F' is RNR, it sends 'FA\_busy\_packet' and checks 'RR\_Response\_Reception (F,w)'. If 'w' is Yes, it goes to E1. If 'w' is No, it goes to E3. If 'F' is else, it sends 'reset (66s)', 'Discard the frame', and goes to E3. If 'F' is ERR, PIP, PIN, it sends 'FA\_non\_busy\_packet', 'reset (66s)', and goes to R. + +Figure D.30: Reception FA, Phase D (EOR-EOM) + +## Procedure Command\_Reception + +:fpar +IN/OUT F RECSIGNAL, +IN/OUT w RESULT; + +![Flowchart for Command_Reception subroutine. It starts with a connector 'Command_Reception', then checks 'Preamble flag?'. If 'Yes', it 'reset (T2)' and checks 'T.30 HDLC frame received?'. If 'Yes', it checks 'FCS Error'. If 'FCS Error' is 'Yes', it checks 'Signal gone?'. If 'Yes', it checks '3s delay?'. If 'Yes', it checks '200 ms delay?'. If 'Yes', it sets 'w:=No' and ends. If 'FCS Error' is 'else', it 'Set F from the received HDLC frame' and checks 'F'. If 'F' is 'RR', it 'reset (66s)' and sets 'w:=Yes'. If 'F' is 'DCN', it 'reset (66s)' and sets 'w:=E1'. If 'Preamble flag?' is 'else', it checks 'Signal gone?'. If 'Yes', it checks '3s delay?'. If 'Yes', it checks '200 ms delay?'. If 'Yes', it sets 'w:=No' and ends. If 'Signal gone?' is 'else', it loops back to 'Preamble flag?'.](aa6e28822419dba9f22129fee66c9c4c_img.jpg) + +``` +graph TD + Start([Command_Reception]) --> Preamble{Preamble flag?} + Preamble -- Yes --> resetT2[reset (T2)] + resetT2 --> T30{T.30 HDLC frame received?} + T30 -- Yes --> FCS{FCS Error} + FCS -- Yes --> SignalGone1{Signal gone?} + SignalGone1 -- Yes --> Delay3s1{3s delay?} + Delay3s1 -- Yes --> Delay200ms1{200 ms delay?} + Delay200ms1 -- Yes --> wNo1[w:=No] + wNo1 --> End1(( )) + FCS -- else --> SetF[Set F from the received HDLC frame] + SetF --> F{F} + F -- RR --> reset66s1[reset (66s)] + reset66s1 --> wYes[w:=Yes] + wYes --> End2(( )) + F -- DCN --> reset66s2[reset (66s)] + reset66s2 --> wE1[w:=E1] + wE1 --> End3(( )) + T30 -- else --> SignalGone2{Signal gone?} + SignalGone2 -- Yes --> Delay3s2{3s delay?} + Delay3s2 -- Yes --> Delay200ms2{200 ms delay?} + Delay200ms2 -- Yes --> wNo2[w:=No] + wNo2 --> End4(( )) + SignalGone2 -- else --> Preamble +``` + +Flowchart for Command\_Reception subroutine. It starts with a connector 'Command\_Reception', then checks 'Preamble flag?'. If 'Yes', it 'reset (T2)' and checks 'T.30 HDLC frame received?'. If 'Yes', it checks 'FCS Error'. If 'FCS Error' is 'Yes', it checks 'Signal gone?'. If 'Yes', it checks '3s delay?'. If 'Yes', it checks '200 ms delay?'. If 'Yes', it sets 'w:=No' and ends. If 'FCS Error' is 'else', it 'Set F from the received HDLC frame' and checks 'F'. If 'F' is 'RR', it 'reset (66s)' and sets 'w:=Yes'. If 'F' is 'DCN', it 'reset (66s)' and sets 'w:=E1'. If 'Preamble flag?' is 'else', it checks 'Signal gone?'. If 'Yes', it checks '3s delay?'. If 'Yes', it checks '200 ms delay?'. If 'Yes', it sets 'w:=No' and ends. If 'Signal gone?' is 'else', it loops back to 'Preamble flag?'. + +Figure D.31: Command reception subroutine + +## Procedure Wait + +; fpar IN/OUT w RESULT; + +![Flowchart for the Wait subroutine. It starts with a 'Wait' symbol, followed by 'set (66s)'. A loop begins with a 'Received packet' decision. If 'DCN_packet', 'other_packet', or 'FCD_packet', it performs 'reset (66s)' and sets 'w' to 'E2', 'W_packet', or 'W_pix' respectively, then exits. If 'else', it waits for 75ms and checks 'Received DCN packet already?'. If 'Yes', it resets (66s) and sets 'w:=E2' before exiting. If 'else', it calls 'reissue_previous_command' and 'Response_Reception (F,w)'. Both lead to a 'w' decision. If 'w' is 'Yes', it checks '66s elapsed?'. If 'Yes', it resets (66s) and sets 'w:=E3' before exiting. If 'else', it loops back. If 'w' is 'No', it checks '3rd try?'. If 'Yes', it resets (66s) and sets 'w:=E3' before exiting. If 'else', it branches to 'E1' (w:=E1) or 'E3' (w:=E3) and exits.](a634891d16b60b21df90a35c2af72c67_img.jpg) + +``` +graph TD; Start([Wait]) --> Set66s1[set (66s)]; Set66s1 --> RecPacket{Received packet}; RecPacket -- DCN_packet --> Reset66s1[reset (66s)]; Reset66s1 --> wE2_1[w:=E2]; wE2_1 --> Exit1(( )); RecPacket -- other_packet --> Reset66s2[reset (66s)]; Reset66s2 --> wW_packet[w:=W_packet]; wW_packet --> Exit2(( )); RecPacket -- FCD_packet --> Reset66s3[reset (66s)]; Reset66s3 --> wW_pix[w:=W_pix]; wW_pix --> Exit3(( )); RecPacket -- else --> Wait75ms[wait for 75ms]; Wait75ms --> RecDCN{Received DCN packet already?}; RecDCN -- Yes --> Reset66s4[reset (66s)]; Reset66s4 --> wE2_2[w:=E2]; wE2_2 --> Exit4(( )); RecDCN -- else --> Reissue[reissue_previous_command]; Reissue --> Response[Response_Reception F,w]; Response --> wDecision{w}; wDecision -- Yes --> Elapsed{66s elapsed?}; Elapsed -- Yes --> Reset66s5[reset (66s)]; Reset66s5 --> wE3_1[w:=E3]; wE3_1 --> Exit5(( )); Elapsed -- else --> RecPacket; wDecision -- No --> Try3{3rd try?}; Try3 -- Yes --> Reset66s6[reset (66s)]; Reset66s6 --> wE3_2[w:=E3]; wE3_2 --> Exit6(( )); Try3 -- else --> E1[w:=E1]; E1 --> Exit7(( )); Try3 -- else --> E3[w:=E3]; E3 --> Exit8(( )); +``` + +Flowchart for the Wait subroutine. It starts with a 'Wait' symbol, followed by 'set (66s)'. A loop begins with a 'Received packet' decision. If 'DCN\_packet', 'other\_packet', or 'FCD\_packet', it performs 'reset (66s)' and sets 'w' to 'E2', 'W\_packet', or 'W\_pix' respectively, then exits. If 'else', it waits for 75ms and checks 'Received DCN packet already?'. If 'Yes', it resets (66s) and sets 'w:=E2' before exiting. If 'else', it calls 'reissue\_previous\_command' and 'Response\_Reception (F,w)'. Both lead to a 'w' decision. If 'w' is 'Yes', it checks '66s elapsed?'. If 'Yes', it resets (66s) and sets 'w:=E3' before exiting. If 'else', it loops back. If 'w' is 'No', it checks '3rd try?'. If 'Yes', it resets (66s) and sets 'w:=E3' before exiting. If 'else', it branches to 'E1' (w:=E1) or 'E3' (w:=E3) and exits. + +Figure D.32: Wait subroutine + +## Procedure Response\_Reception + +![Flowchart for Response_Reception subroutine. It starts with a connector 'Response_Reception', followed by 'set (T4)'. A loop begins with decision 'preamble flag?'. If 'Yes', it goes to 'reset (T4)'. If 'else', it goes to 'T4 delayed?'. If 'Yes' to 'T4 delayed?', it sets 'w:=No' and exits. If 'else', it loops back. From 'reset (T4)', it goes to 'T.30 HDLC frame received?'. If 'Yes', it goes to 'FCS Error'. If 'else', it goes to 'Signal gone?'. If 'Yes' to 'Signal gone?', it goes to '3s delay?'. If 'Yes' to '3s delay?', it sets 'w:=E3' and exits. If 'else', it loops back. From 'FCS Error', if 'Yes', it goes to an exit connector. If 'else', it goes to 'Set F from the received HDLC frame', then to 'F'. From 'F', there are three branches: 'else' leads to 'w:=Yes' and exit; 'CRP' leads to 'w:=No' and exit; 'DCN' leads to 'w:=E1' and exit. From 'Signal gone?' (after 'FCS Error' else), if 'Yes', it goes to '200 ms delay?'. If 'Yes' to '200 ms delay?', it sets 'w:=No' and exits. If 'else', it loops back. From '200 ms delay?' (after 'FCS Error' else), if 'Yes', it sets 'w:=No' and exits. If 'else', it goes to '3s delay?'. If 'Yes' to '3s delay?', it sets 'w:=E3' and exits. If 'else', it loops back.](9f50279046b74a4e66a1a0144c3b1d11_img.jpg) + +: +fpar +IN/OUT F RECSIGNAL, +IN/OUT w RESULT; + +``` +graph TD + Start([Response_Reception]) --> SetT4[set (T4)] + SetT4 --> PreambleFlag{preamble flag?} + PreambleFlag -- Yes --> ResetT4[reset (T4)] + PreambleFlag -- else --> T4Delayed{T4 delayed?} + T4Delayed -- Yes --> WNo1[w:=No] + T4Delayed -- else --> PreambleFlag + WNo1 --> Exit1(( )) + ResetT4 --> HDLCFrame{T.30 HDLC frame received?} + HDLCFrame -- Yes --> FCSError{FCS Error} + HDLCFrame -- else --> SignalGone1{Signal gone?} + SignalGone1 -- Yes --> Delay3s1{3s delay?} + Delay3s1 -- Yes --> WE3_1[w:=E3] + Delay3s1 -- else --> PreambleFlag + WE3_1 --> Exit2(( )) + FCSError -- Yes --> Exit3(( )) + FCSError -- else --> SetF[Set F from the received HDLC frame] + SetF --> F{F} + F -- else --> WYes[w:=Yes] + F -- CRP --> WNo2[w:=No] + F -- DCN --> WE1[w:=E1] + WYes --> Exit4(( )) + WNo2 --> Exit5(( )) + WE1 --> Exit6(( )) + SignalGone1 -- else --> SignalGone2{Signal gone?} + SignalGone2 -- Yes --> Delay200ms{200 ms delay?} + Delay200ms -- Yes --> WNo3[w:=No] + Delay200ms -- else --> SignalGone2 + WNo3 --> Exit7(( )) + SignalGone2 -- else --> Delay3s2{3s delay?} + Delay3s2 -- Yes --> WE3_2[w:=E3] + Delay3s2 -- else --> SignalGone2 + WE3_2 --> Exit8(( )) +``` + +Flowchart for Response\_Reception subroutine. It starts with a connector 'Response\_Reception', followed by 'set (T4)'. A loop begins with decision 'preamble flag?'. If 'Yes', it goes to 'reset (T4)'. If 'else', it goes to 'T4 delayed?'. If 'Yes' to 'T4 delayed?', it sets 'w:=No' and exits. If 'else', it loops back. From 'reset (T4)', it goes to 'T.30 HDLC frame received?'. If 'Yes', it goes to 'FCS Error'. If 'else', it goes to 'Signal gone?'. If 'Yes' to 'Signal gone?', it goes to '3s delay?'. If 'Yes' to '3s delay?', it sets 'w:=E3' and exits. If 'else', it loops back. From 'FCS Error', if 'Yes', it goes to an exit connector. If 'else', it goes to 'Set F from the received HDLC frame', then to 'F'. From 'F', there are three branches: 'else' leads to 'w:=Yes' and exit; 'CRP' leads to 'w:=No' and exit; 'DCN' leads to 'w:=E1' and exit. From 'Signal gone?' (after 'FCS Error' else), if 'Yes', it goes to '200 ms delay?'. If 'Yes' to '200 ms delay?', it sets 'w:=No' and exits. If 'else', it loops back. From '200 ms delay?' (after 'FCS Error' else), if 'Yes', it sets 'w:=No' and exits. If 'else', it goes to '3s delay?'. If 'Yes' to '3s delay?', it sets 'w:=E3' and exits. If 'else', it loops back. + +Figure D.33: Response reception subroutine + +## Procedure RR\_Response\_Reception + +; fpar IN/OUT F RECSIGNAL, +IN/OUT w RESULT; + +![Flowchart for RR_Response_Reception subroutine. It starts with an entry connector, followed by a decision '1st RNR received ? (66s timer has not started)'. If 'Yes', it goes to 'set (66s)'. If 'else', it goes to a junction. From the junction, it goes to a decision '66s elapsed?'. If 'Yes', it goes to 'w:=No' and an exit connector. If 'else', it goes to 'Wait for 75ms', then 'RR', then 'Response_Reception (F,w)'. From 'Response_Reception (F,w)', it goes to a decision 'w'. If 'No', it loops back to the junction. If 'Yes', it goes to 'w:=Yes' and an exit connector. If 'E1', it goes to 'w:=E1' and an exit connector. If 'E3', it goes to 'w:=E3' and an exit connector.](57939c16065211317c5442cf2a4009e0_img.jpg) + +``` +graph TD + Entry([ ]) --> D1{1st RNR received ? +(66s timer has not started)} + D1 -- Yes --> P1[set (66s)] + D1 -- else --> J(( )) + P1 --> J + J --> D2{66s elapsed?} + D2 -- Yes --> P2[w:=No] + P2 --> Exit1(( )) + D2 -- else --> P3[Wait for 75ms] + P3 --> P4{{RR}} + P4 --> P5[Response_Reception +(F,w)] + P5 --> D3{w} + D3 -- No --> J + D3 -- Yes --> P6[w:=Yes] + P6 --> Exit2(( )) + D3 -- E1 --> P7[w:=E1] + P7 --> Exit3(( )) + D3 -- E3 --> P8[w:=E3] + P8 --> Exit4(( )) +``` + +Flowchart for RR\_Response\_Reception subroutine. It starts with an entry connector, followed by a decision '1st RNR received ? (66s timer has not started)'. If 'Yes', it goes to 'set (66s)'. If 'else', it goes to a junction. From the junction, it goes to a decision '66s elapsed?'. If 'Yes', it goes to 'w:=No' and an exit connector. If 'else', it goes to 'Wait for 75ms', then 'RR', then 'Response\_Reception (F,w)'. From 'Response\_Reception (F,w)', it goes to a decision 'w'. If 'No', it loops back to the junction. If 'Yes', it goes to 'w:=Yes' and an exit connector. If 'E1', it goes to 'w:=E1' and an exit connector. If 'E3', it goes to 'w:=E3' and an exit connector. + +Figure D.34: RR response reception subroutine + +![Flowchart of FA release flow (1)](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +``` + +graph TD + E4((E4)) --> DCN_E4{DCN} + E1((E1)) --> DCN_packet1{DCN_packet} + E3((E3)) --> DCN_E3{DCN} + DCN_E4 --> DCN_packet1 + DCN_E3 --> DCN_packet1 + DCN_packet1 --> reset_Twa[reset (Twa)] + reset_Twa --> set_3s[set (3s)] + set_3s --> wait_for_DCN([wait_for_DCN]) + wait_for_DCN --> DCN_packet2{DCN_packet} + wait_for_DCN --> timer_3s{{3s}} + DCN_packet2 --> reset_3s[reset (3s)] + timer_3s --> reset_3s + reset_3s --> stop_monitor["'Stop to monitor +DCN packet'"] + stop_monitor --> low_layer_Disconnect{low_layer_Disconnect} + low_layer_Disconnect --> A((A)) + low_layer_Disconnect -.- desc[Disconnection of +the low layer protocol link +procedure +NW side:FA or IWF is opposite] + +``` + +Flowchart of FA release flow (1) + +**Figure D.35: FA release flow (1)** + +![Flowchart of FA release flow (2). The flow starts at E2, goes to DCN, then 'wait for 1s', then 'Stop to monitor DCN packet'. A decision 'low_layer_Disconnect' follows, with a side note: '"Disconnection of the low layer protocol link" procedure NW side:FA or IWF is opposite"'. The flow ends at A.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` +graph TD; E2((E2)) --> DCN{DCN}; DCN --> W1[wait for 1s]; W1 --> S1[Stop to monitor DCN packet]; S1 --> LLD{low_layer_Disconnect}; LLD --> A((A)); Note["Disconnection of the low layer protocol link procedure NW side:FA or IWF is opposite"] -.-> LLD; +``` + +Flowchart of FA release flow (2). The flow starts at E2, goes to DCN, then 'wait for 1s', then 'Stop to monitor DCN packet'. A decision 'low\_layer\_Disconnect' follows, with a side note: '"Disconnection of the low layer protocol link" procedure NW side:FA or IWF is opposite"'. The flow ends at A. + +Figure D.36: FA release flow (2) + +Table D.2: Specified Timer values + +| Name of Timer | Timer Value | Refer to | +|----------------------|----------------|------------| +| T1 | 35 ± 5(sec) | ITU-T T.30 | +| T2 | 6 ± 1(sec) | ITU-T T.30 | +| T4 | 3,0(sec) ± 15% | ITU-T T.30 | +| Twa | 60(sec) | - | +| Fill insertion timer | 4,5(sec) | ITU-T T.30 | +| Flag insertion timer | 50(sec) | ITU-T T.30 | +| 66s | 66(sec) | ITU-T T.30 | +| 3s | 3(sec) | - | + +# Annex E (normative): ASN.1 notation + +``` + +ASN.1 notation +3GTS23146 DEFINITIONS AUTOMATIC TAGS ::= +BEGIN +IFPPacket ::= SEQUENCE +{ + type-of-msg Type-of-msg, + data-field Data-Field OPTIONAL +} +Type-of-msg ::= CHOICE +{ + t30-indicator ENUMERATED + { + no-signal, + cng, + ced, + tcf-error-detect, + fa-busy, + fa-non-busy, + }, + data ENUMERATED + { + v21, + v27-2400, + v27-4800, + v29-7200, + v29-9600, + v17-7200, + v17-9600, + v17-12000, + v17-14400, + ... + } +} +Data-Field ::= SEQUENCE OF SEQUENCE +{ + field-type ENUMERATED + { + hdlc-data, + hdlc-sig-end, + hdlc-fcs-OK, + hdlc-fcs-BAD, + hdlc-fcs-OK-sig-end, + hdlc-fcs-BAD-sig-end, + t4-non-ecm-data, + t4-non-ecm-sig-end + }, + field-data OCTET STRING (SIZE(1..65535)) OPTIONAL +} +UDPTLPacket ::= SEQUENCE +{ + seq-number INTEGER (0..65535), + primary-ifp-packet TYPE-IDENTIFIER.&Type(IFPPacket), + error-recovery CHOICE + { + secondary-ifp-packets SEQUENCE OF TYPE-IDENTIFIER.&Type(IFPPacket), + fec-info SEQUENCE + { + fec-npackets INTEGER, + fec-data SEQUENCE OF OCTET STRING + } + } +} +END + +``` + +# Annex F (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|----------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| July 2000 | CN#08 | NP-000222 | | | Approved to be made v4.0.0 and put under change control | 2.0.0 | 4.0.0 | +| 09-2000 | CN#09 | NP-000476 | 001 | | Correction of SDL Diagrams | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | NP-000552 | 002 | | Modification of V.25bis to V.250 | 4.0.0 | 4.1.0 | +| 06-2002 | CN#16 | | | | Upgraded to v5.0.0 | 4.1.0 | 5.0.0 | +| 12-2004 | CN#26 | | | | Upgraded to v6.0.0 | 5.0.0 | 6.0.0 | +| 06-2007 | CT#36 | | | | Upgraded to v7.0.0 | 6.0.0 | 7.0.0 | +| 12-2008 | CT#42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | 7.0.0 | 8.0.0 | +| 12-2009 | CT#46 | | | | Automatic upgrade from previous Release | 8.0.0 | 9.0.0 | +| 03-2011 | CT#51 | | | | Automatic upgrade from previous Release version 9.0.0 | 9.0.0 | 10.0.0 | +| 03-2011 | CT#51 | | | | Correction of heading and numbering made by MCC | 10.0.0 | 10.0.1 | +| 09-2012 | CT#57 | | | | Automatic upgrade from previous Release version 10.0.1 | 10.0.1 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23207/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-11/23_series/23207/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95e128955f0123880f8dfd0706d7825dddeb73b5 --- /dev/null +++ b/marked/Rel-11/23_series/23207/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4a636db35fa4afbd911a63247c7182547a04476ea3a91d8de2483d0dfbf1039 +size 106159 diff --git a/marked/Rel-11/23_series/23207/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Rel-11/23_series/23207/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..459bca9ea90d8980085071572221e3d7660ea246 --- /dev/null +++ b/marked/Rel-11/23_series/23207/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d97b4a6703e4abbef3e2d96577c923905aa3af386d88086e211ab412a5afc81 +size 103572 diff --git a/marked/Rel-11/23_series/23207/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg b/marked/Rel-11/23_series/23207/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f47870cfb119d57b202d4a639036a7c88f074095 --- /dev/null +++ b/marked/Rel-11/23_series/23207/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56b52d25aa714c96a3cc56dcff9c13d6419fb01e85c3c595ec9482bf4560fec8 +size 88384 diff --git a/marked/Rel-11/23_series/23207/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/23_series/23207/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00897acdf6993e47b8fb4939e898841bd473b067 --- /dev/null +++ b/marked/Rel-11/23_series/23207/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2259e97beea2715bf927a3a972d6b1d1b57c81a7a98d6f286774e9f7c0f14bba +size 142924 diff --git a/marked/Rel-11/23_series/23207/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23207/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c8095db866759730e9584203d670b72907a9697 --- /dev/null +++ b/marked/Rel-11/23_series/23207/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:279940c5f33e0f8eb334e91b6b63003ca340f7bba5bcf58e970d6f2641209587 +size 104303 diff --git a/marked/Rel-11/23_series/23207/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/Rel-11/23_series/23207/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..501de98b0c9a2eb3f521f7896dd86412f4353fe6 --- /dev/null +++ b/marked/Rel-11/23_series/23207/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c22b8e4f7ae93cb3919a336fb46a73085b59f475625130b36d94b669f8df6ae +size 127205 diff --git a/marked/Rel-11/23_series/23207/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/Rel-11/23_series/23207/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5e08ffd152bfb3e2b9fe1691504187e10183957 --- /dev/null +++ b/marked/Rel-11/23_series/23207/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abba434b6e67c10db3bfb96be1d58b72b8cfb039a7b92a6c0a7403a98d5162bd +size 50513 diff --git a/marked/Rel-11/23_series/23207/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg b/marked/Rel-11/23_series/23207/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8538215adc21c6be7d884040339055583e109137 --- /dev/null +++ b/marked/Rel-11/23_series/23207/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20b0d57828b8ca7b95f0d2543751182a8bbd4802b15fa279d81e3bc63bca10b3 +size 117439 diff --git a/marked/Rel-11/23_series/23207/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/23_series/23207/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cff0b200b51c60f9637efc9dab656938573db78d --- /dev/null +++ b/marked/Rel-11/23_series/23207/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c5c23c4c849adf266b6a3aac1042ee5e960ad9ea5683bf0ef36d08a27f9fefe +size 102012 diff --git a/marked/Rel-11/23_series/23207/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/23_series/23207/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e5aff98847ed68ef5eaaa8b3e822064c49a0e38 --- /dev/null +++ b/marked/Rel-11/23_series/23207/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e38640a21a6a37ed3f4282f10544bbb95c0c17594def34be4e492c8c26ef62eb +size 90766 diff --git a/marked/Rel-11/23_series/23207/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/23_series/23207/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e324832c70377e11ba5d778907f3d33eb8ce2bbf --- /dev/null +++ b/marked/Rel-11/23_series/23207/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bf57834c92c6532ec34028b50f44407ed3ac7ae4bfa9f73e2c0bcb72b624671 +size 94405 diff --git a/marked/Rel-11/23_series/23207/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/23_series/23207/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba7f8b9899b163baee21ea194cac2d44516ee961 --- /dev/null +++ b/marked/Rel-11/23_series/23207/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dac94f0b686e6363b85ffb3b171666667ed1e6edf7025840573b79f1cdbe3576 +size 143699 diff --git a/marked/Rel-11/23_series/23207/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/23_series/23207/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22dd40fc232cf9bbfe9d72ca73cff034d1663f91 --- /dev/null +++ b/marked/Rel-11/23_series/23207/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35a10b6170cf0d66eedb24098cc9b181f44a4b92a756251155f8fb28f938700f +size 97013 diff --git a/marked/Rel-11/23_series/23207/raw.md b/marked/Rel-11/23_series/23207/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0c75005c9145620a199cf153c80fa975be4366a1 --- /dev/null +++ b/marked/Rel-11/23_series/23207/raw.md @@ -0,0 +1,1190 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and Abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 High Level Requirements for End-to-End IP QoS ..... | 9 | +| 4.1 End-to-End QoS Negotiation Requirements ..... | 9 | +| 4.2 QoS Policy Requirements ..... | 9 | +| 5 End-to-End QoS Architecture..... | 9 | +| 5.1 QoS Management Functions in the Network ..... | 9 | +| 5.1.1 Description of functions ..... | 10 | +| 5.1.1.1 QoS management functions for end-to-end IP QoS in UMTS Network ..... | 10 | +| 5.1.1.2 (void)..... | 11 | +| 5.1.1.3 Interaction to External Networks..... | 11 | +| 5.1.1.4 Translation/mapping function in the GGSN and the UE ..... | 11 | +| 5.1.2 Allocation of QoS management functions ..... | 12 | +| 5.1.2.1 QoS management functions for end-to-end IP QoS ..... | 12 | +| 5.2 Capabilities of Functional Elements ..... | 12 | +| 5.2.1 GGSN ..... | 12 | +| 5.2.2 UE..... | 13 | +| 5.2.3 Void ..... | 13 | +| 5.2.3a PCRF ..... | 13 | +| 5.2.4 Application Function (AF) ..... | 14 | +| 5.3 Void..... | 14 | +| 5.3aVoid 14 | | +| 5.3b Gx reference point (PCRF – GGSN)..... | 14 | +| 5.3c Rx reference point (AF - PCRF) ..... | 14 | +| 5.4 QoS Parameters ..... | 15 | +| 5.5 QoS Parameter Mapping ..... | 15 | +| 6 End-to-End QoS Procedures ..... | 15 | +| 6.1 QoS Procedures in Functional Elements ..... | 15 | +| 6.1.1 Procedures in the GGSN ..... | 15 | +| 6.1.2 Procedures in the UE ..... | 15 | +| 6.1.3 Void ..... | 16 | +| 6.1.3a Procedures in the PCRF..... | 16 | +| 6.1.4 Procedures in the AF ..... | 16 | +| 6.2 IP Bearer Level / Application Level Binding Mechanism..... | 17 | +| 6.3 Session Flow: QoS Interaction Procedures ..... | 17 | +| 6.3.1 Void ..... | 17 | +| 6.3.2 Resource Reservation Message Flows ..... | 17 | +| 6.3.2.1 Void ..... | 17 | +| 6.3.2.2 Resource Reservation with IP QoS signalling..... | 17 | +| 6.3.2.3 Resource Reservation with IP QoS reservation signalling and Service-based Local Policy..... | 17 | +| 6.3.2.4 (void)..... | 17 | +| 6.3.3 Void ..... | 17 | +| 6.3.4 Void ..... | 17 | +| 6.3.5 Void ..... | 17 | +| 6.3.6 Void ..... | 18 | +| 6.3.6a Void ..... | 18 | +| 6.3.7 Void ..... | 18 | +| 6.3.8 Void ..... | 18 | +| 6.4 PDP Context Used for Application Level Signalling Transport..... | 18 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------|-----------| +| <b>Annex A (informative):</b> | <b>QoS Conceptual Models.....</b> | <b>19</b> | +| A.1 | Introduction..... | 19 | +| A.2 | Scenarios..... | 20 | +| A.2.1 | Scenario 1..... | 20 | +| A.2.2 | Scenario 2..... | 21 | +| A.2.3 | Scenario 3..... | 22 | +| A.2.4 | Scenario 4..... | 25 | +| A.2.5 | Scenario 5..... | 26 | +| <b>Annex B (informative):</b> | <b>(void).....</b> | <b>28</b> | +| <b>Annex C (informative):</b> | <b>Sample Mapping of SDP Descriptions Into QoS Authorization .....</b> | <b>29</b> | +| <b>Annex D (informative):</b> | <b>Resource reservation and end-to-end RSVP .....</b> | <b>32</b> | +| D.1 | Resource reservation with end-to-end RSVP..... | 32 | +| D.2 | Resource Reservation with End-to-End RSVP and Service-based Local Policy..... | 35 | +| <b>Annex E (informative):</b> | <b>Change history.....</b> | <b>39</b> | + +# --- Foreword + +This Technical Specification has been produced by the 3<sup>rd</sup> 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 framework for end-to-end Quality of Service involving GPRS and complements TS 23.107 [3] which describes the framework for Quality of Service within UMTS. The end-to-end QoS architecture is provided in Figure 1. The document describes the interaction between the TE/MT Local Bearer Service, the GPRS Bearer Service, and the External Bearer Service, and how these together provide Quality of Service for the End-to-End Service. The document also describes IP level mechanisms necessary in providing end-to-end Quality of Service involving GPRS networks, including possible interaction between the IP level and the GPRS level, as well as the application level and the IP level. + +This document covers different architectural aspects of the end-to-end Quality of Service concept and architecture with varying level of detail. In general, other specifications shall be referred to for further details; these other specifications enable the reader to acquire the full understanding of the end-to-end Quality of Service concept and architecture. In particular, the stage 2 specification for the PCC architecture is specified in TS 23.203 [21]. The present document does not contain any requirements for the PCC architecture. + +In contrast to the TS 23.107 [3], the present document is only applicable to GPRS packet switched access services, and includes aspects of interworking to the IM subsystem as well as PSTN and other networks. The document does not cover the circuit switched access services. + +![Figure 1: End-to-End QoS Architecture diagram showing the hierarchy of services from TE to TE through GPRS components.](1d27fed9c01eb99f6535283f35fe3bbf_img.jpg) + +The diagram illustrates the End-to-End QoS Architecture. At the top, a horizontal bar labeled "GPRS" spans across five components: MT, UTRAN/GERAN, CN Iu EDGE NODE, CN Gateway, and TE. Below this, a wide grey bar labeled "End-to-End Service" spans across all six components: TE, MT, UTRAN/GERAN, CN Iu EDGE NODE, CN Gateway, and TE. Below the "End-to-End Service" bar, three grey boxes are shown: "TE/MT Local Bearer Service" (under TE and MT), "GPRS Bearer Service" (under UTRAN/GERAN, CN Iu EDGE NODE, and CN Gateway), and "External Bearer Service" (under CN Gateway and TE). Below the "GPRS Bearer Service" box, three more grey boxes are shown: "Radio Access Bearer Service" (under UTRAN/GERAN and CN Iu EDGE NODE), "CN Bearer Service" (under CN Iu EDGE NODE and CN Gateway), and "Backbone Bearer Service" (under CN Gateway). Below the "Radio Access Bearer Service" box, two grey boxes are shown: "Radio Bearer Service" (under UTRAN/GERAN) and "Iu Bearer Service" (under CN Iu EDGE NODE). Below the "Iu Bearer Service" box, one grey box labeled "Physical Bearer Service" is shown (under CN Iu EDGE NODE). Below the "Radio Bearer Service" box, one grey box labeled "Physical Radio Service" is shown (under UTRAN/GERAN). Vertical lines connect the components at the top to the service boxes below, and further vertical lines connect the service boxes to the lower-level bearer and physical services. + +Figure 1: End-to-End QoS Architecture diagram showing the hierarchy of services from TE to TE through GPRS components. + +Figure 1: End-to-End QoS Architecture + +# 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 22.228: "Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1". +- [2] 3GPP TS 23.002: "Network Architecture". +- [3] 3GPP TS 23.107: "QoS Concept and Architecture". +- [4] 3GPP TS 23.228: "IP Multimedia (IM) Subsystem – stage 2". +- [4a] Void. +- [4b] Void. +- [4c] Void. +- [5] 3GPP TS 21.905: "Vocabulary for 3GPP Specifications". +- [6] RFC 2475: "An Architecture for Differentiated Services (DiffServ)". +- [7] RFC 2753: "A Framework for Policy-based Admission Control ". +- [8] RFC 2748: "Common Open Policy Service protocol (COPS)". +- [9] RFC 2205: "Resource ReSerVation Protocol (RSVP)". +- [10] RFC 2209: "Resource ReSerVation Protocol (RSVP) Message Processing Rules". +- [11] RFC 2210: "The use of RSVP with IETF integrated Services". +- [12] RFC 1633: "Integrated Services in the Internet Architecture: an Overview". +- [13] RFC 3261: "SIP: Session Initiation Protocol". +- [14] RFC 2327: "Session Description Protocol". +- [15] RFC 2998: "A Framework For Integrated Services Operation Over DiffServ Networks". +- [16] RFC 2750: "RSVP Extensions for Policy Control". +- [17] RFC 2474: "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [18] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [19] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2". +- [20] 3GPP TS 23.221: "Architecture requirements". +- [21] 3GPP TS 23.203: "Policy and Charging Control Architecture". +- [22] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [23] 3GPP TS 29.213: "Policy and Charging Control signalling flows and QoS parameter mapping". +- [24] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point". + +# 3 Definitions and Abbreviations + +## 3.1 Definitions + +**RSVP:** Resource ReSerVation Protocol: The RSVP protocol, RFC 2205 [9], is used by a host to request specific qualities of service from the network for particular application data streams or flows. The network responds by explicitly admitting or rejecting RSVP requests. + +**DiffServ:** DiffServ networks classify packets into one of a small number of aggregated flows or "classes", based on the DiffServ codepoint (DSCP) in the packet's IP header. This is known as behaviour aggregate (BA) classification (RFC 2475 [6]). At each DiffServ router, packets are subjected to a "per-hop behaviour" (PHB), which is invoked by the DSCP (RFC 2474 [17]). + +**IntServ:** The integrated services architecture RFC 1633 [12] defined a set of extensions to the traditional best effort model of the Internet with the goal of allowing end-to-end QOS to be provided to applications. One of the key components of the architecture is a set of service definitions; the current set of services consists of the controlled load and guaranteed services. The architecture assumes that some explicit setup mechanism is used to convey information to routers so that they can provide requested services to flows that require them. While RSVP is the most widely known example of such a setup mechanism, the IntServ architecture is designed to accommodate other mechanisms. + +**Application Function:** The Application Function (AF) is an element offering applications that require the control of IP bearer resources. The AF is capable of communicating with the PCRF to transfer dynamic QoS-related service information. One example of an AF is the P-CSCF of the IM CN subsystem. + +**AF session:** An AF session is 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. One example of an AF session is an IMS session. + +**AF session signalling:** AF session signalling is used to control the AF session. One example of AF session signalling is SIP/SDP. + +**Policy control:** The process whereby the Policy and Charging Rules Function (PCRF) indicates to the Policy and Charging Enforcement Function (PCEF) how to control the IP-CAN bearer. Policy control includes QoS control and/or gating control. + +## 3.2 Abbreviations + +For the purpose of the present document, the following abbreviations apply: + +| | | +|----------|--------------------------------------------| +| AF | Application Function | +| APN | Access Point Name (*) | +| DiffServ | Differentiated Services | +| DSCP | DiffServ Code Point | +| GERAN | GSM/EDGE Radio Access Network (*) | +| GGSN | Gateway GPRS Support Node (*) | +| HTTP | Hypertext Transfer Protocol (*) | +| IMS | IP Multimedia Subsystem | +| IntServ | Integrated Services | +| LAN | Local Area Network | +| LDP | Label Distribution Protocol | +| MPLS | Multiprotocol Label Switching Architecture | +| PCC | Policy and Charging Control | +| PCEF | Policy and Charging Enforcement Function | +| PHB | Per Hop Behaviour | +| PCRF | Policy and Charging Rules Function | +| RNC | Radio Network Controller (*) | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol (*) | +| SNMP | Simple Network Management Protocol (*) | +| TFT | Traffic Flow Template (*) | + +\* This abbreviation is covered in TR 21.905 [18], version 4.2.0. + +# --- 4 High Level Requirements for End-to-End IP QoS + +## 4.1 End-to-End QoS Negotiation Requirements + +- The UMTS QoS negotiation mechanisms used for providing end-to-end QoS shall be backward compatible with UMTS Release 1999. +- The UMTS QoS negotiation mechanisms used for providing end-to-end QoS shall not make any assumptions about the situation in external networks which are not within the scope of 3GPP specifications. +- The UMTS QoS negotiation mechanisms used for providing end-to-end QoS shall not make any assumptions about application layer signalling protocols. +- No changes to non-UMTS specific QoS negotiation mechanisms. +- The UMTS QoS negotiation mechanisms used for providing end-to-end QoS shall not make any assumptions about applications which may be used on terminal equipment attached to mobile terminals. +- Unnecessary signalling complexity and processing complexity in the network elements as well as the mobile terminal shall be avoided. +- Unnecessary signalling traffic due to end-to-end QoS negotiation shall be avoided. +- Methods for user authentication as well as billing and charging mechanisms related to the end-to-end QoS negotiation shall be kept as simple as possible. +- Minimum changes to network architecture and mechanisms due to introduction of end-to-end QoS negotiation. +- It shall be possible for an application on the external device to request end-to-end QoS. + +## 4.2 QoS Policy Requirements + +- The UMTS policy mechanisms described in TS 23.060 [19] shall be used for control of the UMTS bearers. +- Interaction between UMTS bearer services and IP bearer services shall only occur at the translation function in the UE and GGSN. + +# --- 5 End-to-End QoS Architecture + +## 5.1 QoS Management Functions in the Network + +To provide IP QoS end-to-end, it is necessary to manage the QoS within each domain. An IP BS Manager is used to control the external IP bearer service. Due to the different techniques used within the IP network, this communicates to the UMTS BS manager through the Translation function. + +At PDP context setup the user shall have access to one of the following alternatives: + +- Basic GPRS IP connectivity service: The bearer is established according to the user's subscription, local operator's IP bearer resource based policy, local operator's admission control function and GPRS roaming agreements. In this case, IP bearer resource based local policy decisions may be applied to the bearer. +- Enhanced GPRS based services: The bearer is used to support an enhanced application-layer service, such as IM. In this case, policy control decisions (e.g., authorization and policy based control) are also applied to the bearer. + +To enable coordination between events in the application layer and resource management in the IP bearer layer, a logical element, the Policy and Charging Rules Function (PCRF), is used as a logical policy decision element. It is also possible to implement a policy decision element internal to the IP BS Manager in the GGSN. The IP policy architecture does not mandate the policy decision point to be external to the GGSN. + +Whenever resources not owned or controlled by the UMTS network are required to provide QoS, it is necessary to interwork with the external network that controls those resources. Interworking may be realised in a number of ways, including: + +- signalling along the flow path (e.g. RSVP, LDP). +- packet marking or labelling along the flow path (e.g. DiffServ, MPLS) +- interaction between Policy Control and/or Resource Management elements. +- Service Level Agreements enforced by the border routers between networks. + +For the policy control the following should apply: + +- The IP policy framework employed in UMTS should, as far as possible, conform to IETF "Internet Standards". The IETF policy framework may be used for policy decision, authorization, and control of the IP level functionality, at both user and network level. +- There should be separation between the scope and roles of the UMTS policy mechanisms and the IP policy framework. This is to facilitate separate evolution of these functions. + +### 5.1.1 Description of functions + +#### 5.1.1.1 QoS management functions for end-to-end IP QoS in UMTS Network + +NOTE: The end-to-end QoS management functions do not cover the cases of a circuit switched service, or an IP service interworking with an ATM service at the gateway node. + +**IP BS Manager** uses standard IP mechanisms to manage the IP bearer services. These mechanisms may be different from mechanisms used within the UMTS, and may have different parameters controlling the service. When implemented, the IP BS Manager may include the support of DiffServ Edge Function and the RSVP function. The **Translation/mapping function** provides the inter-working between the mechanisms and parameters used within the UMTS bearer service and those used within the IP bearer service, and interacts with the IP BS Manager. In the GGSN, the IP QoS parameters are mapped into UMTS QoS parameters, where needed. In the UE, the QoS requirements determined from the application layer (e.g., SDP) are mapped to either the PDP context parameters or IP layer parameters (e.g., RSVP). + +If an IP BS Manager exists both in the UE and the Gateway node, it is possible that these IP BS Managers communicate directly with each other by using relevant signalling protocols. + +The required options in the table define the minimum functionality that shall be supported by the equipment in order to allow multiple network operators to provide interworking between their networks for end-to-end QoS. Use of the optional functions listed below, other mechanisms which are not listed (e.g. over-provisioning), or combinations of these mechanisms are not precluded from use between operators. + +The IP BS Managers in the UE and GGSN provide the set of capabilities for the IP bearer level as shown in table 1. Provision of the IP BS Manager is optional in the UE, and required in the GGSN. + +**Table 1: IP BS Manager capability in the UE and GGSN** + +| Capability | UE | GGSN | +|------------------------------------|----------|--------------| +| <b>DiffServ Edge Function</b> | Optional | Required | +| <b>RSVP/IntServ</b> | Optional | Optional | +| <b>IP Policy Enforcement Point</b> | Optional | Required (*) | + +(\*) Although the capability of IP policy enforcement is required within the GGSN, the control of IP policy through the GGSN is a network operator choice. + +Figure 2 shows the scenario for control of an IP service using IP BS Managers in both possible locations in the UE and Gateway node. The figure also indicates the optional communication path between the IP BS Managers in the UE and the Gateway node. + +**Policy and Charging Rules Function (PCRF)** encompasses policy control decision and flow based charging control functionalities. The PCRF provides network control regarding the service data flow detection, gating, and QoS towards the GGSN. The PCRF makes policy control decisions, and communicates these decisions to the IP BS Manager in the GGSN, which is the Policy and Charging Enforcement Point (PCEF). + +The interface between the PCRF and the Application Function (AF) is the Rx interface, and is included in the Reference Architecture depicted in TS 23.002 [2]. + +The interface between the PCRF and GGSN is specified within 3GPP, named Gx interface, and is included in the Reference Architecture depicted in TS 23.002 [2]. The interface between the PCRF and GGSN supports the transfer of information and policy decisions between the policy decision point and the IP BS Manager in the GGSN. + +The PCRF makes policy decisions based on input obtained from the AF as well as from other sources, e.g. operator configuration. The PCRF maps the policy set-up information received from the AF via the Rx interface into IP QoS parameters. The PCRF is in the same domain as the GGSN. The AF may either be in the same network as the PCRF or may be in a different network. In the particular case of IMS, the AF is the P-CSCF which is in the same network as the GGSN, as specified in TS 23.221 [20]. + +**Application Function (AF)** offers services that require the control of IP bearer resources. The AF maps QoS-related application level parameters (e.g. SDP) into policy set-up information, and sends this information to the PCRF via the Rx interface. + +#### 5.1.1.2 (void) + +#### 5.1.1.3 Interaction to External Networks + +Within the UMTS network, there is resource management performed by various nodes in the admission control decision. The resources considered here are under the direct control of the UMTS network. + +In IP Networks, it is also necessary to perform resource management to ensure that resources required for a service are available. Where the resources for the IP Bearer Service to be managed are not owned by the UMTS network, the resource management of those resources would be performed through an interaction between the UMTS network and that external network. + +In addition, where the UMTS network is also using external IP network resources as part of the UMTS bearer service (for example for the backbone bearer service), it may also be necessary to interwork with that network. + +The GGSN shall support DiffServ edge functionality. There are a number of other mechanisms provided to support interoperator interworking, some of which are given below. + +NOTE: This list is not exhaustive. Other options are possible. + +- Signalling along the flow path: In this scenario, resource requirements are explicitly requested and either granted or rejected through the exchange of signalling messages between network elements along the path of the IP packet flow. Signalling may be performed on a per-flow basis (e.g. using end to end RSVP) or it may be performed for an aggregate set of flows. In the latter case, it is expected that signalling exchanges would only be required when there are changes required in the resources allocated to an aggregate set of flows. +- Interaction between network management entities: In this scenario, resource requirements need to be explicitly negotiated and provisioned through network management entities. The results of this exchange are then enforced in the border nodes separating DiffServ administrative domains. +- Service Level Agreements enforced by the border routers between networks: In this scenario, resources are allocated along the path based on agreements between the network operators. The border routers along the path flow are provisioned with the characteristics of the aggregated traffic that is allowed to flow between systems. + +#### 5.1.1.4 Translation/mapping function in the GGSN and the UE + +Translation/mapping function interacts with the IP BS Manager and with the UMTS BS Manager in the GGSN and in the UE. It provides interworking between the mechanisms and parameters used within the UMTS bearer service and those used within the IP bearer service. + +For policy control, the translation/mapping function in the GGSN maps IP bearer based policy information into UMTS bearer based policy information. This mapping is used by the GGSN for policy control over the UMTS network. + +### 5.1.2 Allocation of QoS management functions + +#### 5.1.2.1 QoS management functions for end-to-end IP QoS + +The QoS management functions for controlling the external IP bearer services and how they relate to the UMTS bearer service QoS management functions are shown in Figure 2. + +![Figure 2: QoS management functions for UMTS bearer service in the control plane and QoS management functions for end-to-end IP QoS. The diagram shows a layered architecture across five domains: UE, UTRAN, CN EDGE, Gateway, and Ext. Netw. / Ext. Service Control. At the top, an Application Function connects to a Policy and Charging Rules Function via an Rx interface. The Policy and Charging Rules Function connects to the Gateway via a Gx interface. The Gateway contains an IP BS Manager, which connects to the Ext. Service Control. Below the IP BS Manager in the Gateway are Adm/Cap. Control, Transl, and UMTS BS Manager. The UMTS BS Manager connects to the CN EDGE. In the CN EDGE, there are Adm/Cap. Control, Subsc. Control, UMTS BS Manager, Radio BS Manager, Iu BS Manager, CN BS Manager, and BB NS Manager. The UMTS BS Manager connects to the UTRAN. In the UTRAN, there are Adm/Cap. Control, RAB Manager, Radio BS Manager, Iu BS Manager, UTRA ph. BS M, and Iu NS Manager. The RAB Manager connects to the CN EDGE. In the UE, there is an IP BS Manager, Transl, Adm/Cap. Control, UMTS BS Manager, Radio BS Manager, and UTRA ph. BS M. The IP BS Manager connects to the Transl and Adm/Cap. Control. The Transl connects to the UMTS BS Manager. The Adm/Cap. Control connects to the UMTS BS Manager. The UMTS BS Manager connects to the Radio BS Manager. The Radio BS Manager connects to the UTRA ph. BS M. A legend at the bottom indicates that double-headed arrows represent protocol interfaces and single-headed arrows represent service primitive interfaces.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 2: QoS management functions for UMTS bearer service in the control plane and QoS management functions for end-to-end IP QoS. The diagram shows a layered architecture across five domains: UE, UTRAN, CN EDGE, Gateway, and Ext. Netw. / Ext. Service Control. At the top, an Application Function connects to a Policy and Charging Rules Function via an Rx interface. The Policy and Charging Rules Function connects to the Gateway via a Gx interface. The Gateway contains an IP BS Manager, which connects to the Ext. Service Control. Below the IP BS Manager in the Gateway are Adm/Cap. Control, Transl, and UMTS BS Manager. The UMTS BS Manager connects to the CN EDGE. In the CN EDGE, there are Adm/Cap. Control, Subsc. Control, UMTS BS Manager, Radio BS Manager, Iu BS Manager, CN BS Manager, and BB NS Manager. The UMTS BS Manager connects to the UTRAN. In the UTRAN, there are Adm/Cap. Control, RAB Manager, Radio BS Manager, Iu BS Manager, UTRA ph. BS M, and Iu NS Manager. The RAB Manager connects to the CN EDGE. In the UE, there is an IP BS Manager, Transl, Adm/Cap. Control, UMTS BS Manager, Radio BS Manager, and UTRA ph. BS M. The IP BS Manager connects to the Transl and Adm/Cap. Control. The Transl connects to the UMTS BS Manager. The Adm/Cap. Control connects to the UMTS BS Manager. The UMTS BS Manager connects to the Radio BS Manager. The Radio BS Manager connects to the UTRA ph. BS M. A legend at the bottom indicates that double-headed arrows represent protocol interfaces and single-headed arrows represent service primitive interfaces. + +**Figure 2: QoS management functions for UMTS bearer service in the control plane and QoS management functions for end-to-end IP QoS** + +NOTE 1: The dimmed boxes in Figure 2 are clarified in TS 23.107 [3]. + +NOTE 2: The UE is only shown as a combined element, but it may also consist of a split TE/MT. Standardization of the interface and operation within a split UE is outside the scope of this TS. + +## 5.2 Capabilities of Functional Elements + +This section provides functional descriptions of capabilities in GGSN, UE, PCRF, and AF. + +### 5.2.1 GGSN + +This clause provides functional descriptions of capabilities in GGSN. The capabilities are part of IP BS Manager (see 5.1.1.1) or corresponding user plane functions. Determination of exactly which functions are required to support interoperator and multi-vendor aspects are not addressed in this clause. + +The **DiffServ Edge Function** shall be compliant to the IETF specifications for Differentiated Services (RFC 2475 [6]). The IETF Differentiated Services architecture will be used to provide QoS for the external bearer service. + +Parameters for the DiffServ Edge Function (i.e. classifiers, meters, packet handling actions) may be statically configured on the GGSN, derived from PDP Context parameters and/or derived from RSVP signalling. + +DiffServ functions configured on the basis of PDP Context parameters consist of marking user packets. The DSCP to be used is derived from the PDP Context parameters according to statically configured rules. + +Statically configured DiffServ functions may include classifiers, meters, markers, droppers and shapers acting on uplink traffic. + +**Policy and Charging Enforcement Function (PCEF)** controls the user plane quality of service that is provided including policy-based admission control that is applied to the bearer and gating control. Policy decisions are either pushed to or requested by the GGSN via the Gx interface. + +Policy-based admission control ensures that the resources that can be used by a particular set of IP flows are within the "authorized resources" specified via the Gx interface. The authorized resources provide an upper bound on the resources that can be reserved or allocated for the set of IP flows. + +The authorized resources are expressed as a maximum authorized bandwidth and QoS class. The QoS class identifies a bearer service (which has a set of bearer service characteristics associated with it). The PCRF generates a maximum authorized QoS class for the set of IP flows. This information is mapped by the translation/mapping function in the GGSN to give the authorized resources for UMTS bearer admission control. + +In the user plane, policy enforcement for an individual or a set of IP flows is defined in terms of a "gate" implemented in the GGSN. A gate is part of the policy enforcement functionality and is controlled by the PCRF through Gx interface signalling. A gate consists of a packet classifier, and a gate status (open/closed). When a gate is open, the packets matching the packet classifier are accepted, and are thus subject to the DiffServ edge treatment in uplink direction or forwarded in their corresponding PDP context in downlink direction. When a gate is closed, all of the packets matching the packet classifier are dropped. + +### 5.2.2 UE + +This clause provides functional descriptions of capabilities in UE. The capabilities are part of IP BS Manager (see 5.1.1.1) or corresponding user plane functions. Determination of exactly which functions are required to support interoperator and multi-vendor aspects are not addressed in this clause. + +**DiffServ Edge Function** acts as a DiffServ (DS) boundary for the traffic from applications running on the UE. As specified in RFC 2475 [6], DS boundary node must be able to apply the appropriate PHB to packets based on the DS code point. In addition, DS boundary nodes may be required to perform traffic conditioning functions. When GGSN DiffServ marking is used, the DiffServ edge function in the UE is not needed. + +**RSVP/IntServ Function** provides the capability for the UE to request end-to-end QoS using RSVP messages as defined in IETF standards. RSVP messages may also be used by the network to inform the DSCP to be used by the UE. RSVP messages shall include the authorization token and flow identifier(s) in a policy data object if the authorization token is available in the UE. RSVP may be used to trigger PDP context activation/modification. The inter-working between MT and TE is FFS. + +### 5.2.3 Void + +#### 5.2.3a PCRF + +This clause provides high level functional descriptions of PCRF capabilities. The PCRF makes policy decisions, e.g. based on policy set-up information obtained from the AF via the Rx interface. + +- The PCRF checks that if the policy set-up information received from the AF is consistent with operator policies defined in the PCRF. +- The PCRF authorizes QoS resources (bandwidth, etc.) for the AF session. The PCRF uses the policy set-up information received from the AF to calculate the proper authorization. The authorization includes the limits on QoS for the set of IP flows and restrictions on individual IP flows (e.g. destination address and port). +- The PCRF decides if new QoS authorization (bandwidth, etc.) is needed due to a mid-call media or codec change. The PCRF re-authorizes QoS resources when the resources requested by the UE for a flow exceeds previous authorization, or a new flow is added, or when elements of the packet classifier(s) for authorized flows change. +- The PCRF provides the policy decision information to the GGSN via the Gx interface. +- The PCRF provides gating control decisions controlling the gate for the authorized media stream. +- At AF session release, the PCRF revokes the QoS resource authorization for the AF session. + +For further details, see TS 23.203 [21]. + +### 5.2.4 Application Function (AF) + +The Application Function (AF) is an element offering applications that require the control of IP bearer resources (e.g. UMTS PS domain/GPRS domain resources). One example of an Application Function is the P-CSCF in the IMS architecture. + +Policy control related functions + +- The AF uses the Rx interface to exchange service based policy set-up information with the PCRF. This applies both during session establishment, as well as upon a mid-session modification affecting the media (e.g. addition of a new media in mid-session). +- The AF may give instructions to the PCRF defining how the PCRF shall interact with the PCEF for certain events related to policy control. The AF is able to give instructions to the PCRF to act on its own, i.e. based on the service information currently available, for the following events: + - The authorization of QoS resources for the AF session; + - The gate control (i.e. whether there is a common gate handling per AF session or an individual gate handling per AF session component required); + - The forwarding of transmission resource level events. + +For further details, see TS 23.203 [21]. + +## 5.3 Void + +### 5.3a Void + +### 5.3b Gx reference point (PCRF – GGSN) + +The Gx interface is the interface between the PCRF and the GGSN. The Gx interface allows policy control and QoS information to be "pushed" to or requested by the GGSN from the PCRF. The Gx interface provides information to support the policy enforcement functions in the GGSN: + +- Control of "gating" function in GGSN; +- UMTS bearer authorization. + +For further details, see TS 23.203 [21]. + +### 5.3c Rx reference point (AF - PCRF) + +The Rx interface is the interface between the AF and the PCRF. The Rx interface is used for policy set-up information exchange and event reporting. + +The Rx interface allows service based QoS information needed for QoS authorization to be exchanged between the AF and the PCRF. This information is used by the PCRF for policy control decisions. + +One PCRF is able to serve more than one AF and one given AF may interact with a number of PCRFs. On a per-AF-session basis, the AF interacts with only a single PCRF. + +For further details, see TS 23.203 [21]. + +## 5.4 QoS Parameters + +See stage 3 specification TS 29.212 [22]. + +## 5.5 QoS Parameter Mapping + +See stage 3 specification TS 29.213 [23]. + +# --- 6 End-to-End QoS Procedures + +## 6.1 QoS Procedures in Functional Elements + +This section describes the main procedures that are used for the end-to-end QoS management. These procedures are described in text description for each involved network elements. The procedures described in this document are meant to provide a high level description for further Stage 3 work and are not intended to be exhaustive. + +### 6.1.1 Procedures in the GGSN + +The QoS procedures in the GGSN are triggered by the QoS signalling messages from the UE or unsolicited provisioning of PCC rules from the PCRF. The exact QoS procedures in the GGSN depend on the GGSN and UE QoS capabilities. The GGSN is required to support DiffServ edge function. Other QoS capabilities that may be supported at the GGSN are RSVP functions and policy enforcement functions. + +For UEs that do not support RSVP, the GGSN may use the PDP context level information to configure the DiffServ edge functionality and provide internetworking between PDP context and backbone IP network. The authorization token is included in the PDP context activation/modification messages. + +For UEs that support RSVP, the GGSN may also support RSVP and use RSVP rather than the PDP context to control the QoS through the backbone IP network. The authorization token may be included in the RSVP signalling and the PDP context activation/modification messages. Alternatively, the RSVP messages may pass transparently through the GGSN. + +For details on PCC functionality in GGSN, see TS 23.203 [21]. + +### 6.1.2 Procedures in the UE + +The QoS procedures in the UE are triggered by the application layer (e.g., SIP/SDP) QoS requirements or initiated by the network. The exact QoS procedures in the UE depend on the UE QoS capabilities. + +For UEs that support only UMTS QoS mechanism, the network or the application QoS requirements will trigger a PDP Context Activation procedure with the corresponding UMTS QoS parameters. For UEs that support both IP (e.g., IP BS Manager) and UMTS QoS mechanism, the application QoS requirements are mapped down to the IP layer QoS parameters. The IP layer parameters are further mapped down to the PDP context parameters in the UE. For UEs that support RSVP, the application QoS requirements are mapped down to create an RSVP session. The UE shall establish a PDP context suitable for support of the RSVP session. + +At the AF session release, the UE shall release all QoS resources allocated for the AF session. + +For details on PCC functionality in the UE, see TS 23.203 [21]. + +### 6.1.3 Void + +#### 6.1.3a Procedures in the PCRF + +The QoS procedures at the PCRF are triggered by the IP-CAN session establishment as reported from a PCEF and, for an active IP-CAN session, IP-CAN session modification or service information from an AF. + +When the PCRF receives service information from the AF, the PCRF authorizes the QoS resources or rejects the service information received from the AF. If the PCRF rejects the authorization request, the PCRF may indicate in the response to the AF the service information that could be accepted by the PCRF. + +As part of the authorization, the PCRF shall perform the mapping from the service information conveyed over the Rx interface to the Authorized QoS sent over the Gx interface. + +The authorized QoS is either pushed to or requested by the GGSN via the Gx interface. + +The PCRF makes a final decision to enable the allocated QoS resource for the authorized IP flows. This may be triggered by an instruction from the AF. QoS resources may also be enabled at the time they are authorized by the PCRF. + +When the AF receives updated session description information, the AF may send an update for service information to the PCRF. The PCRF decides if a new QoS authorization is needed and updates the authorization for the session accordingly. If the PCRF does not accept the service information received from the AF, the PCRF rejects the update for service information. The PCRF may indicate in the response to the AF the service information that could be accepted by the PCRF. + +The PCRF revokes the resource authorization based on request from the AF. + +For details on the PCC functionality in the PCRF, see TS 23.203 [21]. + +### 6.1.4 Procedures in the AF + +The AF communicates with the PCRF to transfer dynamic session information, required for PCRF decisions as well as to receive information and notifications about IP transmission resource level events. + +The AF contacts the PCRF when it receives an AF session signalling message initiating a new AF session: + +- The AF contacts the PCRF that is responsible for the UE. + +**NOTE:** There is one PCRF responsible for the IP-CAN session of the UE. This implies that for all AF sessions to and from the same UE with the same UE IP address, the AF(s) interacts with the same PCRF. This also implies that if different AF sessions of a user are controlled by different AFs, then all these AFs will interact with the same PCRF. Hence, the bearer authorization of the PDP Context(s) carrying the media of these AF sessions will be performed by the same PCRF. + +- The AF generates the information (e.g. service information) conveyed over the Rx interface from the application specific media description (e.g. SDP media description). +- The PCRF uses the service information for the QoS policy set up for the AF session. During an AF session change, the AF sends an update for service information to the PCRF based on the new session description information exchanged within AF session signalling. + +The AF orders the PCRF to enable or disable a media to pass through the access network. The AF may instruct the PCRF to either wait for an explicit command or enable the media as part of the authorization of the QoS for the media. The AF may use an explicit command to disable the media e.g. when a media component of an AF session is put on hold. + +At AF session release, the AF revokes any granted resource authorization. + +For details on the PCC functionality in the AF, see TS 23.203 [21]. + +## 6.2 IP Bearer Level / Application Level Binding Mechanism + +See TS 23.203 [21]. + +## 6.3 Session Flow: QoS Interaction Procedures + +This section highlights possible additions to the GPRS bearer establishment procedures specified in TS 23.060 [19] for support of Policy and Charging Control (PCC). These additional procedures are utilized to provide Policy and Charging Control for session-based services, e.g. for IMS as described in Chapter 5: 'IP multimedia subsystem procedures' of TS 23.228 [4]. + +For IMS where PCC is not used, the related procedures defined in TS 23.228 [4] are not applied. + +Detailed specification of the additional procedures are given in TS 23.203 [21]. + +It shall be possible according to operator choice to use solely the GPRS bearer establishment procedures specified in TS 23.060 [19] without these additions. + +### 6.3.1 Void + +### 6.3.2 Resource Reservation Message Flows + +#### 6.3.2.1 Void + +#### 6.3.2.2 Resource Reservation with IP QoS signalling + +*Editor's note: There is still ongoing work in IETF on new IP QoS signalling techniques, hence it is not possible to include flows using those new techniques into this version of the specification. Procedures describing resource reservation with end-to-end RSVP are described in Annex X.* + +#### 6.3.2.3 Resource Reservation with IP QoS reservation signalling and Service-based Local Policy + +*Editor's note: There is still ongoing work in IETF on new IP QoS signalling techniques, hence it is not possible to include flows using those new techniques into this version of the specification. Procedures describing resource reservation with end-to-end RSVP and Service-based Local Policy are described in Annex X.* + +#### 6.3.2.4 (void) + +### 6.3.3 Void + +### 6.3.4 Void + +### 6.3.5 Void + +### 6.3.6 Void + +#### 6.3.6a Void + +### 6.3.7 Void + +### 6.3.8 Void + +## 6.4 PDP Context Used for Application Level Signalling Transport + +To establish a PDP context for application level signalling, the UE shall be able to include a signalling flag in PDP context activation procedure. This indicates to the network the intention of using the PDP context for application level signalling. The only defined application level signalling flag in this release is the IM CN subsystem signalling flag. However, the network may also support other mechanisms that cater for identifying application level signalling flows within a PDP context, as described in TS 23.228 [4] section 4.2.6. + +To establish a PDP context for application level signalling with prioritised handling over the radio interface, the UE shall be able to set the Signalling Indication in the QoS IE in the PDP context activation procedure. The Signalling indication in the QoS IE indicates to the radio and core networks the requirement for enhanced handling over the radio interface, once it has been negotiated with the networks. + +A request for a general purpose PDP context having the "signalling indication" within the QoS IE may be accepted or downgraded according to operator policy configured at the GGSN using the usual QoS negotiation mechanisms described in TS 23.060 [19]. + +In the case of IMS, the IM CN Signalling Flag in the PCO IE is used to reference rules and restrictions on the PDP context used for application level signalling, as described in TS 23.228 [4] section 4.2.6. + +The IM CN Signalling Flag and the Signalling indication in the QoS profile detailed in TS 23.107 [3] may be used independently of each other. + +Based on operator policy the "Signalling Indication" in the QoS IE may be allowed only if the "IM CN Subsystem Signalling" flag is present in the PCO IE. + +# Annex A (informative): QoS Conceptual Models + +## A.1 Introduction + +There are many different end-to-end scenarios that may occur from a UE connected to a UMTS network. The following examples depict how end-to-end QoS will be delivered for a number of scenarios that are considered to be significant. + +NOTE: Further consideration of scenarios 2 and 3 is not needed for Stage 3 work in the Release 5 timeframe. The normative aspects of scenarios 2 and 3 are considered to be already covered by scenario 1. + +In all the scenarios presented below, the network architecture is as shown in Figure A.1 below. + +![Figure A.1: Network Architecture for QoS Conceptual Models. The diagram shows a network architecture with the following components and layers: On the left, a 'Local UE' is connected to a 'GGSN' via an 'IP Bearer Service'. The 'Local UE' is also connected to an 'SGSN' via a 'Gn/Gp' interface. The 'SGSN' is connected to the 'GGSN'. The 'GGSN' is connected to a 'Backbone IP Network' (represented by a cloud). The 'Backbone IP Network' is connected to a 'Remote Access Point' (RAP). The 'RAP' is connected to a 'Remote Host'. The 'Remote Host' is connected to the 'Backbone IP Network'. The diagram is divided into three horizontal layers by dashed lines: the top layer is the 'IP Bearer Layer', the middle layer is the 'Access Bearer Layer (eg. UMTS Bearer)', and the bottom layer is the 'Scope of PDP Context'. The 'Scope of PDP Context' includes the 'Local UE', 'SGSN', 'GGSN', and 'Backbone IP Network'.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +Figure A.1: Network Architecture for QoS Conceptual Models. The diagram shows a network architecture with the following components and layers: On the left, a 'Local UE' is connected to a 'GGSN' via an 'IP Bearer Service'. The 'Local UE' is also connected to an 'SGSN' via a 'Gn/Gp' interface. The 'SGSN' is connected to the 'GGSN'. The 'GGSN' is connected to a 'Backbone IP Network' (represented by a cloud). The 'Backbone IP Network' is connected to a 'Remote Access Point' (RAP). The 'RAP' is connected to a 'Remote Host'. The 'Remote Host' is connected to the 'Backbone IP Network'. The diagram is divided into three horizontal layers by dashed lines: the top layer is the 'IP Bearer Layer', the middle layer is the 'Access Bearer Layer (eg. UMTS Bearer)', and the bottom layer is the 'Scope of PDP Context'. The 'Scope of PDP Context' includes the 'Local UE', 'SGSN', 'GGSN', and 'Backbone IP Network'. + +**Figure A.1: Network Architecture for QoS Conceptual Models** + +### NOTES: + +- Although the backbone IP network is shown as a single domain, it may consist of a number of separate domains. +- The structure of the Local UE is not specified. It includes cases from a simple host, to a gateway to a network such as a LAN. If the UE is acting as a gateway, it is responsible for providing the IP BS Management towards the extended network. +- The remote side is shown as a simple host. Other more complex cases on the remote side such as a private LAN with over-provisioning, or possibly LAN priority marking, and DiffServ and/or RSVP capable routing elements is not depicted. It is envisaged however that interworking between the QoS mechanisms in a more complex remote user side could also be performed with some similarities to the mechanisms shown at the local side. + +The reference point shown at the UE is at the interface to the UE. Within the UE, the QoS control could be derived from any of the mechanisms that occur across that reference point, or it could use a different mechanism internally. + +Although the scenarios currently identified are mainly using DiffServ in the backbone IP network (RSVP is indicated as an alternative in scenario 4), it is not mandated that DiffServ must be used in the backbone IP network. Other mechanisms, for example, over-provisioning and aggregated RSVP may be used. + +## A.2 Scenarios + +These scenarios give examples of concatenating QoS mechanisms in different parts of the network which together can deliver an end-to-end QoS. These scenarios are not intended to describe the details of the interworking between the QoS mechanisms. + +The different scenarios involve cases with and without service based local policy. Each scenario describes the applicable cases, possibly by referencing another scenario. In some scenarios, only one of the cases may be valid (e.g. scenario 5). Where both cases are covered, they may be described together identifying the optionality, or separately for clarity of the individual cases. + +The optional authorisation token is associated with the cases involving service based local policy, and is applicable for IM services. It is an operator decision whether or not to support service based local policy for IM services. If service based local policy is not supported, or not applicable (i.e. not IM service), then the optional authorisation token and application server at the P-CSCF are not used. + +IM services not using service based local policy will typically follow scenarios 1 to 4. IM services using service based local policy will typically follow scenarios 3 to 5. + +NOTE: Scenario 5 is reserved for the IP multimedia services involving, e.g., SIP signalling , IP policy control, and subscription checking. + +### A.2.1 Scenario 1 + +The UE does not provide an IP BS Manager. The end-to-end IP QoS bearer service towards the remote terminal is controlled from the GGSN. + +The scenario assumes that the GGSN supports DiffServ edge functions, and the backbone IP network is DiffServ enabled. + +NOTE: The UE may always include an authorisation token in establishment of the PDP context. Inclusion of the authorisation token in scenario 1 changes the QoS mechanisms to be the same as those described in scenario 5. Therefore, please refer to scenario 5 if the authorisation token is included. + +The application layer (e.g. SIP/SDP) between the end hosts identifies the QoS requirements. The QoS requirements determined from the application layer (e.g. TS 23.228 [4] describes interworking from SIP/SDP to QoS requirements) are mapped down to PDP context parameters in the UE. + +In this scenario, the control of the QoS over the UMTS access network (from the UE to the GGSN) may be performed either from the terminal using the PDP context signalling, or from the SGSN by subscription data. + +The IP QoS for the downlink direction is controlled by the remote terminal up to the GGSN. The GGSN will apply receiver control DiffServ edge functions and can reclassify the data (remarking the DiffServ Code Point (DSCP)). This may affect the QoS applied to the data over the UMTS access (the TFT may use the DSCP to identify the data to be allocated to the PDP context). + +The end-to-end QoS is provided by a local mechanism in the UE, the PDP context over the UMTS access network, DiffServ through the backbone IP network, and DiffServ in the remote access network in the scenario shown in the figure below. The GGSN provides the interworking between the PDP context and the DiffServ function. However, the interworking may use information about the PDP context which is established, or be controlled from static profiles, or dynamically through other means such as proprietary HTTP based mechanisms. The UE is expected to be responsible for the control of the PDP context, but this may instead be controlled from the SGSN by subscription. + +![Figure A.2: Local UE does not provide IP BS Manager. This sequence diagram illustrates the QoS mechanisms for uplink and downlink data flows across four entities: UE, GGSN, Remote AP, and Remote Host. The diagram is split into two horizontal sections by a solid line. The top section shows 'Uplink Data' flow from Remote Host to UE. The bottom section shows 'Downlink Data' flow from UE to Remote Host. Each section has four columns representing the entities. Above the diagram, text describes the QoS control mechanisms in each domain. Arrows indicate the flow of data and QoS control information.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +The diagram illustrates the QoS mechanisms for uplink and downlink data flows across four entities: UE, GGSN, Remote AP, and Remote Host. The diagram is split into two horizontal sections by a solid line. The top section shows 'Uplink Data' flow from Remote Host to UE. The bottom section shows 'Downlink Data' flow from UE to Remote Host. Each section has four columns representing the entities. Above the diagram, text describes the QoS control mechanisms in each domain. Arrows indicate the flow of data and QoS control information. + +**Uplink Data Flow:** + +- UE:** The UE controls the QoS mechanisms from the UE. A solid blue vertical line connects the UE to the PDP Flow. +- GGSN:** QoS in UMTS controlled by PDP context. A solid red horizontal line (PDP Flow) enters from the UE and exits to the Remote AP. A solid green horizontal line (DS) enters from the Remote AP and exits to the Remote Host. +- Remote AP:** QoS in backbone network controlled by DS. DS marking performed by GGSN. A solid green horizontal line (DS) enters from the GGSN and exits to the Remote Host. +- Remote Host:** QoS on remote access link controlled by DS. A solid green horizontal line (DS) enters from the Remote AP. + +**Downlink Data Flow:** + +- UE:** The UE may control the QoS mechanisms from received information. A solid blue vertical line connects the UE to the PDP Flow. +- GGSN:** QoS in UMTS controlled by PDP context selected by TFT. A solid red horizontal line (PDP Flow) enters from the Remote AP and exits to the UE. A solid green horizontal line (DS) enters from the Remote Host and exits to the Remote AP. +- Remote AP:** QoS in backbone network controlled by DS. DS marking performed by RUE, or remarking by RAP. A solid green horizontal line (DS) enters from the Remote Host and exits to the GGSN. +- Remote Host:** QoS on remote access link controlled by DS or other means. A solid green horizontal line (DS) enters from the Remote Host. + +**QoS Control Information:** + +- Application Layer (eg. SIP/SDP):** Represented by dashed green horizontal lines spanning across all entities in both uplink and downlink sections. + +Figure A.2: Local UE does not provide IP BS Manager. This sequence diagram illustrates the QoS mechanisms for uplink and downlink data flows across four entities: UE, GGSN, Remote AP, and Remote Host. The diagram is split into two horizontal sections by a solid line. The top section shows 'Uplink Data' flow from Remote Host to UE. The bottom section shows 'Downlink Data' flow from UE to Remote Host. Each section has four columns representing the entities. Above the diagram, text describes the QoS control mechanisms in each domain. Arrows indicate the flow of data and QoS control information. + +**Figure A.2: Local UE does not provide IP BS Manager** + +Notes: + +- The solid horizontal lines indicate the mechanism that is providing QoS for the flow of data in the direction indicated. +- The dashed horizontal lines indicate where QoS control information is passed that is not directly controlling the QoS in that link/domain. +- The arrows on the horizontal lines indicate nodes that receive information about QoS from that mechanism, even if that mechanism is not used to control the QoS over that link/domain. +- The solid vertical lines indicate interworking between the different mechanisms. +- In the figure, the term RAP refers to the Remote Access Point, and RUE is the Remote UE. + +No solid vertical line is shown from DiffServ to PDP flow on the downlink at the GGSN. The TFT determines the QoS applicable over the UMTS access. However, the configuration of the TFT may use the DiffServ to select the PDP context to be applied, so there may be interworking between DiffServ and the PDP Flow via the TFT filters. + +### A.2.2 Scenario 2 + +The UE performs an IP BS function which enables end-to-end QoS without IP layer signalling towards the IP BS function in the GGSN, or the remote terminal. + +The scenario assumes that the UE and GGSN support DiffServ edge functions, and that the backbone IP network is DiffServ enabled. + +NOTE: The UE may always include an authorisation token in establishment of the PDP context. Inclusion of the authorisation token in scenario 2 changes the QoS mechanisms to be the same as those described in scenario 5. Therefore, please refer to scenario 5 if the authorisation token is included. + +The application layer (e.g. SIP/SDP) between the end hosts identifies the QoS needs. The QoS requirements from application layer (e.g. TS 23.228 [4] describes interworking from SIP/SDP to QoS requirements) are mapped down to the IP layer. The IP layer service requirements are further mapped down to the PDP context parameters in the UE. + +In this scenario, the control of the QoS over the UMTS access network (from the UE to the GGSN) may be performed either from the terminal using the PDP context signalling. Alternatively, subscription data accessed by the SGSN may override the QoS requested via signalling from the UE (according to the procedures specified in TS 23.060 [19]). + +In this scenario, the terminal supports DiffServ to control the IP QoS through the backbone IP network. + +The IP QoS for the downlink direction is controlled by the remote terminal up to the GGSN. The PDP context controls the QoS between the GGSN and the UE. The UE may apply DiffServ edge functions to provide the DiffServ receiver control. Otherwise, the DiffServ marking from the GGSN will determine the IP QoS applicable at the UE. + +The end-to-end QoS is provided by a local mechanism in the UE, the PDP context over the UMTS access network, DiffServ through the backbone IP network, and DiffServ in the remote access network in the scenario shown in the figure below. The UE provides control of the DiffServ, and therefore determines the appropriate interworking between the PDP context and DiffServ. + +The GGSN DiffServ edge function may overwrite the DSCP received from the UE, possibly using information regarding the PDP context which is signalled between the UMTS BS managers and provided through the translation/mapping function to the IP BS Manager. + +Note that DiffServ control at the Remote Host is shown in this example. However, other mechanisms may be used at the remote end, as demonstrated in the other scenarios. + +![Figure A.3: Local UE supports DiffServ. A sequence diagram showing uplink and downlink data flows across four domains: UE, GGSN, Remote AP, and Remote Host. The diagram illustrates how QoS is managed at each stage for both directions, involving PDP contexts, DiffServ (DS) marking, and application layer protocols like SIP/SDP.](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +The diagram is divided into two horizontal sections: Uplink Data (top) and Downlink Data (bottom). Vertical dashed lines separate the four entities: UE, GGSN, Remote AP, and Remote Host. + +- Uplink Data:** + - UE to GGSN: A red arrow labeled "PDP Flow". Above it, a green dotted arrow labeled "Application Layer (eg. SIP/SDP)" points right. Text above the red arrow: "QoS in UMTS controlled by PDP context. UE DS marking carried transparently." + - GGSN to Remote AP: A solid green arrow labeled "DS". Text above it: "QoS in backbone network controlled by DS. DS marking performed by UE (or remarking by GGSN)." + - Remote AP to Remote Host: A solid green arrow. Text above it: "QoS on remote access link controlled by DS." + - UE text: "The UE controls the QoS mechanisms from the UE." +- Downlink Data:** + - Remote Host to Remote AP: A solid green arrow. Text above it: "QoS on remote access link controlled by DS or other means." + - Remote AP to GGSN: A solid green arrow labeled "DS". Text above it: "QoS in backbone network controlled by DS. DS marking performed by RUE, or remarking by RAP." + - GGSN to UE: A red arrow labeled "PDP Flow". Above it, a green dotted arrow labeled "Application Layer (eg. SIP/SDP)" points left. Text above the red arrow: "QoS in UMTS controlled by PDP context selected by TFT. Remote DS marking/GGSN remarking carried transparently." + - UE text: "The UE may control the QoS mechanisms from received information." + +A box at the bottom left of the diagram contains the text: "The UE performs DS edge functions." + +Figure A.3: Local UE supports DiffServ. A sequence diagram showing uplink and downlink data flows across four domains: UE, GGSN, Remote AP, and Remote Host. The diagram illustrates how QoS is managed at each stage for both directions, involving PDP contexts, DiffServ (DS) marking, and application layer protocols like SIP/SDP. + +Figure A.3: Local UE supports DiffServ + +### A.2.3 Scenario 3 + +The UE performs an IP BS function which enables end-to-end QoS using IP layer signalling towards the remote end. There is no IP layer signalling between the IP BS Managers in the UE and the GGSN. However, the GGSN may make use of information regarding the PDP context which is signalled between the UMTS BS managers and provided through the translation/mapping function. + +This scenario assumes that the UE and GGSN support DiffServ edge functions, and that the backbone IP network is DiffServ enabled. In addition, the UE supports RSVP signalling which interworks within the UE to control the DiffServ. + +The application layer (e.g. SIP/SDP) between the end hosts identifies the QoS requirements. The QoS requirements from application layer (e.g. TS 23.228 [4] describes interworking from SIP/SDP to QoS requirements) are mapped down to create an RSVP session. The UE shall establish the PDP context suitable for support of the RSVP session. The authorisation token from the application layer when included shall be mapped to the PDP context parameters, and may also be mapped to the RSVP signalling. + +In this scenario, the control of the QoS over the UMTS access network (from the UE to the GGSN) may be performed either from the terminal using the PDP context signalling. Alternatively, subscription data accessed by the SGSN may override the QoS requested via signalling from the UE (according to the procedures specified in TS 23.060 [19]). + +In this scenario, the terminal supports signalling via the RSVP protocol to control the QoS at the local and remote accesses, and DiffServ to control the IP QoS through the backbone IP network. The RSVP signalling protocol may be used for different services. It is expected that only RSVP using the Integrated Services (IntServ) semantics would be supported, although in the future, new service definitions and semantics may be introduced. The entities that are supporting the RSVP signalling should act according to the IETF specifications for IntServ and IntServ/DiffServ interwork. + +The QoS for the wireless access is provided by the PDP context. The UE may control the wireless QoS through signalling for the PDP context. The characteristics for the PDP context may be derived from the RSVP signalling information, or may use other information. + +QoS for the IP layer is performed at two levels. The end-to-end QoS is controlled by the RSVP signalling. Although RSVP signalling can be used end-to-end in the QoS model, it is not necessarily supported by all intermediate nodes. Instead, DiffServ is used to provide the QoS throughout the backbone IP network. + +At the UE, the data is also classified for DiffServ. Intermediate QoS domains may apply QoS according to either the RSVP signalling information or DiffServ mechanisms. In this scenario, the UE is providing interworking between the RSVP and DiffServ domains. The GGSN may override the DiffServ setting from the UE. This GGSN may use information regarding the PDP context in order to select the appropriate DiffServ setting to apply, as shown in the figure below. + +The end-to-end QoS is provided by a local mechanism in the UE, the PDP context over the UMTS access network, DiffServ through the backbone IP network, and DiffServ in the remote access network in the scenario shown in the figure below. The RSVP signalling may control the QoS at both the local and remote accesses. This function may be used to determine the characteristics for the PDP context, so the UE may perform the interwork between the RSVP signalling and PDP context. + +The UE provides control of the DiffServ (although this may be overwritten by the GGSN), and in effect, determines the appropriate interworking between the PDP context and DiffServ. + +![Sequence diagram showing Uplink and Downlink data flows between UE, GGSN, Remote AP, and Remote Host. It details QoS mechanisms like PDP context, DS marking, and RSVP signalling for both directions.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +The diagram is divided into two horizontal sections: Uplink Data (top) and Downlink Data (bottom). The vertical axis represents four entities: UE, GGSN, Remote AP, and Remote Host. + +**Uplink Data:** + +- UE:** The UE controls the QoS mechanisms from the UE. It sends 'Application Layer (eg. SIP/SDP)' (green dashed line), 'RSVP Signalling' (purple dashed line), 'DS' (green solid line), and 'PDP Flow' (red solid line) towards the GGSN. +- GGSN:** QoS in UMTS controlled by PDP context. UE DS marking and RSVP signalling carried transparently. It receives the flows from the UE and forwards them towards the Remote AP. +- Remote AP:** QoS in backbone network controlled by DS. DS marking performed by UE, or by GGSN based on PDP context signalling. RSVP signalling carried transparently. It receives the flows from the GGSN and forwards them towards the Remote Host. +- Remote Host:** QoS on remote access link controlled by either DS or RSVP. It receives the flows from the Remote AP. + +**Downlink Data:** + +- Remote Host:** QoS on remote access link controlled by either DS or RSVP. It sends 'Application Layer (eg. SIP/SDP)' (green dashed line), 'RSVP Signalling' (purple dashed line), 'DS' (green solid line), and 'PDP Flow' (red solid line) towards the Remote AP. +- Remote AP:** QoS in backbone network controlled by DS. DS marking performed by RUE (or remarking by RAP). RSVP signalling carried transparently. It receives the flows from the Remote Host and forwards them towards the GGSN. +- GGSN:** QoS in UMTS controlled by PDP context selected by TFT. Remote DS marking/GGSN remarking and RSVP signalling carried transparently. It receives the flows from the Remote AP and forwards them towards the UE. +- UE:** The UE may control the QoS mechanisms from received information. It receives the flows from the GGSN. + +A box at the bottom left indicates: 'The UE performs DS edge functions and RSVP'. + +Sequence diagram showing Uplink and Downlink data flows between UE, GGSN, Remote AP, and Remote Host. It details QoS mechanisms like PDP context, DS marking, and RSVP signalling for both directions. + +**Figure A.4: Local UE supports RSVP signalling with IntServ semantics, and DiffServ; without service based policy** + +The GGSN provides the interworking between the PDP context and the DiffServ function. The application layer signalling may be processed in the local network at an application server such as the P-CSCF in the case of SIP signalling. Interworking between the GGSN and the application layer is shown as a vertical line where applicable. This interworking is for policy control and is between the GGSN and the PDF policy function co-located in the P-CSCF, as shown in the figure below. + +![Figure A.5: Local UE supports RSVP signalling with IntServ semantics, and DiffServ; where service based policy is applied. The diagram illustrates two scenarios: Uplink Data and Downlink Data, showing the flow of QoS control signals and data across the UE, GGSN/P-CSCF, Remote AP, and Remote Host.](26d664119ad25250780f554633444e54_img.jpg) + +The diagram is divided into two horizontal sections: **Uplink Data** (top) and **Downlink Data** (bottom). Each section shows four vertical columns representing different network domains and their QoS control mechanisms: + +- UE (User Equipment):** + - Uplink:** The UE controls the QoS mechanisms from the UE. It sends **Application Layer (eg. SIP/SDP)** (green dashed line), **RSVP Signalling** (magenta dashed line), **DS** (green solid line), **Authorization token** (cyan dashed line), and **PDP Flow** (red solid line) to the GGSN/P-CSCF. + - Downlink:** The UE may control the QoS mechanisms from received information. It receives the same signals from the GGSN/P-CSCF. +- GGSN/P-CSCF(PDF):** + - Uplink:** QoS in UMTS controlled by PDP context. UE DS marking and RSVP signalling carried transparently. QoS in backbone network controlled by DS. DS marking performed by UE, or by GGSN based on PDP context signalling. RSVP signalling carried transparently. + - Downlink:** QoS in UMTS controlled by PDP context selected by TFT. Remote DS marking/GGSN remarking and RSVP signalling carried transparently. QoS in backbone network controlled by DS. DS marking performed by RUE (or remarking by RAP). RSVP signalling carried transparently. +- Remote AP:** QoS on remote access link controlled by either DS or RSVP. It acts as a relay for the signals between the GGSN and the Remote Host. +- Remote Host:** The endpoint for the data and signalling. + +A box at the bottom left indicates: **The UE performs DS edge functions and RSVP**. + +Figure A.5: Local UE supports RSVP signalling with IntServ semantics, and DiffServ; where service based policy is applied. The diagram illustrates two scenarios: Uplink Data and Downlink Data, showing the flow of QoS control signals and data across the UE, GGSN/P-CSCF, Remote AP, and Remote Host. + +**Figure A.5: Local UE supports RSVP signalling with IntServ semantics, and DiffServ; where service based policy is applied** + +### A.2.4 Scenario 4 + +The UE performs an IP BS function which enables end-to-end QoS using IP layer signalling towards the remote end. However, the UE relies on this end-to-end communication being utilised by at least the access point (GGSN) in order to provide the end-to-end QoS. + +This scenario assumes that the UE and GGSN support RSVP signalling which may control the QoS directly, or interwork with DiffServ. The backbone IP network is RSVP and/or DiffServ enabled. + +The application layer (e.g. SIP/SDP) between the end hosts identifies the QoS requirements. The QoS requirements from application layer (e.g. TS 23.228 [4] describes interworking from SIP/SDP to QoS requirements) are mapped down to create an RSVP session. The UE shall establish the PDP context suitable for support of the RSVP session. The authorisation token from the application layer shall be mapped to the PDP context parameters, and may also be mapped to the RSVP signalling. + +In this scenario, the terminal supports signalling via the RSVP protocol to control the QoS across the end-to-end path. The GGSN also supports the RSVP signalling, and uses this information rather than the PDP context to control the QoS through the backbone IP network. The control of the QoS through the core is expected to be supported through interworking with DiffServ at the GGSN, although it may optionally be supported by per flow resource reservation. The RSVP signalling protocol may be used for different services. It is only expected that only RSVP using the Integrated Services (IntServ) semantics would be supported, although in the future, new service definitions and semantics may be introduced. The entities that are supporting the RSVP signalling may fully support the specifications for IntServ and IntServ/DiffServ interwork. If not, they are expected to set the break bit. + +In this scenario, the control of the QoS over the UMTS access network (from the UE to the GGSN) may be performed either from the terminal using the PDP context signalling. Alternatively, subscription data accessed by the SGSN may override the QoS requested via signalling from the UE (according to the procedures specified in TS 23.060 [19]). + +QoS for the IP layer is performed at two levels. The end-to-end QoS is controlled by the RSVP signalling. Although RSVP signalling occurs end-to-end in the QoS model, it is not necessarily supported by all intermediate nodes. DiffServ is used to provide the QoS throughout the backbone IP network, although optionally each node may support RSVP signalling and allocation of resources per flow. An authorisation token may be included in the RSVP signalling and the PDP context establishment/modification. The GGSN may authorise the RSVP session and configure the DiffServ classifier functionality. + +The GGSN supports the RSVP signalling and acts as the interworking point between RSVP and DiffServ. Intermediate QoS domains may apply QoS according to either the RSVP or DiffServ mechanisms. + +The end-to-end QoS is provided by a local mechanism in the UE, the PDP context over the UMTS access network, DiffServ through the backbone IP network, and RSVP in the remote access network in the scenario shown in the figure below. The RSVP signalling may control the QoS at the local access. This function may be used to determine the characteristics for the PDP context, so the UE may perform the interwork between RSVP and the PDP context. + +![Figure A.6: Local UE supports RSVP signalling using IntServ Semantics. The diagram is split into two horizontal sections: Uplink Data (top) and Downlink Data (bottom). It shows four vertical domains: UE, GGSN/P-CSCF (PDF), Remote AP, and Remote Host. In the Uplink section, the UE controls QoS mechanisms from the UE. The PDP Flow (red) and (opt) Authorization token (dashed blue) go from UE to GGSN. RSVP Signalling (dashed green) goes from UE to Remote Host via GGSN. DS (solid green) goes from GGSN to Remote Host. In the Downlink section, the UE may control QoS mechanisms from received information. The PDP Flow (red) and (opt) Authorization token (dashed blue) go from GGSN to UE. RSVP Signalling (dashed green) goes from Remote Host to UE via GGSN. DS (solid green) goes from Remote Host to GGSN. A box at the bottom left indicates 'The UE performs RSVP signalling.'](392a79ccd95e682ccd08f35ab2e64144_img.jpg) + +The diagram illustrates the flow of QoS mechanisms and data across four domains: UE, GGSN/P-CSCF (PDF), Remote AP, and Remote Host. It is divided into two main sections: Uplink Data (top) and Downlink Data (bottom). + +**Uplink Data:** + +- UE:** The UE controls the QoS mechanisms from the UE. It sends the PDP Flow (red) and (opt) Authorization token (dashed blue) to the GGSN/P-CSCF (PDF). It also sends RSVP Signalling (dashed green) to the Remote Host via the GGSN/P-CSCF (PDF). +- GGSN/P-CSCF (PDF):** QoS in UMTS is controlled by PDP context. RSVP signalling is carried transparently. It receives the PDP Flow and (opt) Authorization token from the UE and forwards the DS (solid green) to the Remote Host. +- Remote AP:** QoS in backbone network is controlled by DS. DS marking is performed by GGSN based on RSVP. +- Remote Host:** QoS on remote access link is controlled by either DS or RSVP. It receives the DS (solid green) from the GGSN/P-CSCF (PDF) and the RSVP Signalling (dashed green) from the UE. + +**Downlink Data:** + +- UE:** The UE may control the QoS mechanisms from received information. It receives the PDP Flow (red) and (opt) Authorization token (dashed blue) from the GGSN/P-CSCF (PDF). It also receives RSVP Signalling (dashed green) from the Remote Host via the GGSN/P-CSCF (PDF). +- GGSN/P-CSCF (PDF):** QoS in UMTS is controlled by PDP context selected by TFT. RSVP signalling (and DS/CP) is carried transparently. It receives the DS (solid green) from the Remote Host and forwards the PDP Flow and (opt) Authorization token to the UE. +- Remote AP:** QoS in backbone network is controlled by DS. DS marking is performed by RUE (or remarking by RAP, possibly using RSVP information). +- Remote Host:** QoS on remote access link is controlled by either DS or RSVP. It sends the DS (solid green) to the GGSN/P-CSCF (PDF) and the RSVP Signalling (dashed green) to the UE. + +A box at the bottom left of the diagram states: "The UE performs RSVP signalling." + +Figure A.6: Local UE supports RSVP signalling using IntServ Semantics. The diagram is split into two horizontal sections: Uplink Data (top) and Downlink Data (bottom). It shows four vertical domains: UE, GGSN/P-CSCF (PDF), Remote AP, and Remote Host. In the Uplink section, the UE controls QoS mechanisms from the UE. The PDP Flow (red) and (opt) Authorization token (dashed blue) go from UE to GGSN. RSVP Signalling (dashed green) goes from UE to Remote Host via GGSN. DS (solid green) goes from GGSN to Remote Host. In the Downlink section, the UE may control QoS mechanisms from received information. The PDP Flow (red) and (opt) Authorization token (dashed blue) go from GGSN to UE. RSVP Signalling (dashed green) goes from Remote Host to UE via GGSN. DS (solid green) goes from Remote Host to GGSN. A box at the bottom left indicates 'The UE performs RSVP signalling.' + +Figure A.6: Local UE supports RSVP signalling using IntServ Semantics + +### A.2.5 Scenario 5 + +The UE performs an IP BS function which enables end-to-end QoS without IP layer signalling and negotiation towards the IP BS function in the GGSN, or the remote host. The P-CSCF provides the authorization token to the UE during the SIP session setup process, and the UE provides the authorization token to the GGSN in the PDP context activation/modification message. The GGSN uses the authorization token to obtain a policy decision from the P-CSCF(PDF). This is done via the standardized interface between the PDF and GGSN. Even if the interface is an open interface where all information elements are standardized, the actual usage of the information is operator specific. + +The scenario assumes that the GGSN support DiffServ edge functions, and that the backbone IP network is DiffServ enabled. + +The application layer (e.g. SIP/SDP) between the end hosts identifies the QoS needs. The QoS requirements from application layer (e.g. TS 23.228 [4] describes interworking from SIP/SDP to QoS requirements) are mapped down to the IP layer and further down to the PDP context parameters in the UE. The authorisation token from the application layer is included in the PDP context parameters by the UE. + +In this scenario, the control of the QoS over the UMTS access network (from the UE to the GGSN) may be performed from the terminal using the PDP context signalling. Alternatively, subscription data accessed by the SGSN may override the QoS requested via signalling from the UE (according to the procedures specified in TS 23.060 [19]). + +The QoS for the downlink direction is controlled by the remote host from the remote network to the GGSN. The PDP context controls the UMTS level QoS between the GGSN and the UE. The QoS in the uplink direction is controlled by the PDP context up to the GGSN. The GGSN configures the DiffServ Edge function to interwork with the backbone IP network and control the IP QoS bearer service towards the remote -host. + +The end-to-end QoS is provided by a local mechanism in the UE, the PDP context over the UMTS access network, DiffServ through the backbone IP network, and DiffServ in the remote access network. Note that DiffServ control at the Remote Host is shown in this example. However, other mechanisms may be used at the remote end, as demonstrated in the other scenarios. + +![Sequence diagram illustrating QoS control mechanisms for uplink and downlink data flows between a UE, GGSN/P-CSCF, Remote AP, and Remote Host.](088921fa3f5a44c8551815122517eefd_img.jpg) + +The diagram illustrates the interaction between four entities: UE, GGSN/P-CSCF (PDF), Remote AP, and Remote Host, showing QoS control for uplink and downlink data. + +**Uplink Data Flow:** + +- UE:** Controls QoS mechanisms from the UE. It sends an **Authorization token** (dashed blue arrow) and a **PDP Flow** (solid red arrow) to the GGSN/P-CSCF. It also has an **Application Layer (eg. SIP/SDP)** (dashed green arrow) connection to the Remote Host. +- GGSN/P-CSCF (PDF):** QoS in UMTS controlled by PDP context. It receives the Authorization token and PDP Flow. It performs **DS** (DiffServ) marking and forwards the data to the Remote AP. +- Remote AP:** QoS in backbone network controlled by DS. DS marking performed by GGSN. It receives the data from the GGSN and forwards it to the Remote Host. +- Remote Host:** QoS on remote access link controlled by DS. It receives the **Uplink Data** from the Remote AP. + +**Downlink Data Flow:** + +- Remote Host:** QoS on remote access link controlled by DS or other means. It sends **Downlink Data** to the Remote AP. +- Remote AP:** QoS in backbone network controlled by DS. DS marking performed by RUE, or remarking by RAP. It receives the data and forwards it to the GGSN/P-CSCF. +- GGSN/P-CSCF (PDF):** QoS in UMTS controlled by PDP context selected by TFT. Remote DS marking/GGSN remarking carried transparently. It receives the data and forwards it to the UE via the **PDP Flow** (solid red arrow) and **Authorization token** (dashed blue arrow). It also has an **Application Layer (eg. SIP/SDP)** (dashed green arrow) connection to the UE. +- UE:** The UE may control the QoS mechanisms from received information. It receives the **Downlink Data** from the GGSN/P-CSCF. + +**Legend:** + +- The UE supports PDP context signalling. + +Sequence diagram illustrating QoS control mechanisms for uplink and downlink data flows between a UE, GGSN/P-CSCF, Remote AP, and Remote Host. + +**Figure A.7: Local UE provides authorization token in PDP context activation/modification message and GGSN provides interworking with DiffServ** + +# --- Annex B (informative): (void) + +# Annex C (informative): Sample Mapping of SDP Descriptions Into QoS Authorization + +The QoS requirement for a session depends on the media and codec information for the session. Initial session establishment in the IM Subsystem must determine a common codec (or set of common codecs for multimedia sessions) that will be used for the session. This is done through an end-to-end message exchange to determine the complete set of common codecs, and then the session initiator makes the decision as to the initial set of codecs for the media flows. + +The session initiator includes an SDP in the SIP INVITE message that lists every codec that the originator is willing to support for this session. When the message arrives at the destination endpoint, it responds with the subset that it is also willing to support for the session by selectively accept or decline those media types in the original list. When multiple media codecs are listed, the caller and called party's media fields must be aligned—that is, there must be the same number, and they must be listed in the same order. QoS authorization is performed for this common subset. The P-CSCF(PDF) shall use the SDP contained in the SIP signalling to calculate the proper authorization. The authorization shall include limits on IP resources, and restrictions on IP packet flows, and may include restrictions on IP destinations. These restrictions are expressed as a data rate and QoS class for the combined set of IP flows, and a set of filter specs. + +The QoS authorization for a session shall include an Authorization-Token, which shall be assigned by the P-CSCF(PDF). The Authorization-Token shall contain information that identifies the P-CSCF(PDF) that generated the token. Each authorized session may include several flow authorizations. Each flow authorization may include an authorization for one or more flows. The authorization shall contain the following information: + +- Filter Specs (IP flow 5-tuples that identify the set of flows) +- Data rate and QoS class that describes the authorized resource for the set of flows +- The IP flow 5-tuples includes Source Address, Source Port, Destination Address, Destination Port and Protocol ID. Note that some fields may be wildcarded. + +A typical SDP description consists of a session-level description (details that apply to the whole session and all media flows) and the several media-level descriptions (details that apply to a single media flow). The four critical components for mapping an SDP description into a QoS authorization are the media announcements ("m="), the connection data ("c="), the attributes ("a=") and the bandwidth ("b="). + +The media announcements field contains information about the type of media session, and is of the form: + +m=<media> <port> <transport> <fmt list> + +The attributes field contains attributes of the preceding media session, and is of the form: + +a=<attribute><value> + +The connection data field contains information about the media connection, and is of the form: + +c=<network type> <address type> <connection address> + +The optional bandwidth field contains information about the bandwidth required, and is of the form: + +b=<modifier>:<bandwidth-value> + +An example SDP description from the session originator in the SIP INVITE message: + +v=0 + o=hshieh 2890844526 2890842807 IN IP4 saturn.attws.com + s=- + c=IN IP4 192.141.10.188 + t=0 0 + b=AS:64 + +m=audio 29170 RTP/AVP 3 96 97 + a=rtpmap:96 G726-32/8000 + a=rtpmap:97 AMR + a=fmtp:97 mode-set=0,2,5,7; maxframes=2 + m=video 51372 RTP/AVP 34 + a=fmtp 34 SQCIF=2/MaxBitRate=500/SAC AP + m=application 32416 udp text\_chat + +The called party answers the call and returns the following SDP description in the SIP 183 message: + +v=0 + o=johndoe 2890844526 2890842807 IN IP4 uranus.solar.com + s=- + c=IN IP4 204.142.180.111 + t=0 0 + b=AS:64 + m=audio 31160 RTP/AVP 3 97 + a=rtpmap:97 AMR + a=fmtp:97 mode-set=0,2,5,7; maxframes=2 + a=recvonly + m=video 61000 RTP/AVP 31 + a=fmtp 34 SQCIF=2/MaxBitRate=500/SAC AP + m=application 33020 udp text\_chat + a=sendonly + +Upon receiving the above SDP, the originator's P-CSCF will authorize QoS resource for the originator UE with the following media flows: + +## **A uplink audio flow:** + +The following IP 5-tuples identify the flow: + +| SrcAddress | SrcPort | DestAddress | DestPort | ProtocolID | +|----------------|---------|-----------------|----------|------------| +| 192.141.10.188 | * | 204.142.180.111 | 31160 | 17 | + +Since the conversational audio is very sensitive to delay, the maximum QoS class corresponding to conversational traffic class would be set. The b parameter is used to determine the maximum authorised data rate. + +## **An uplink video flow:** + +The following IP 5-tuples identify the flow: + +| <b>SrcAddress</b> | <b>SrcPort</b> | <b>DestAddress</b> | <b>DestPort</b> | <b>ProtocolID</b> | +|-----------------------|----------------|------------------------|-----------------|-------------------| +| <b>192.141.10.188</b> | * | <b>204.142.180.111</b> | <b>61000</b> | <b>17</b> | + +The video flow may be assigned a maximum QoS class corresponding to streaming traffic class. The b parameter is used to determine the data rate. + +## **A downlink video flow:** + +The following IP 5-tuples identify the flow: + +| <b>SrcAddress</b> | <b>SrcPort</b> | <b>DestAddress</b> | <b>DestPort</b> | <b>ProtocolID</b> | +|------------------------|----------------|-----------------------|-----------------|-------------------| +| <b>204.142.180.111</b> | * | <b>192.141.10.188</b> | <b>51372</b> | <b>17</b> | + +The video flow may be assigned a maximum QoS class corresponding to streaming traffic class. The b parameter is used to determine the maximum authorised data rate. + +## **A downlink udp flow:** + +The following IP 5-tuples identify the flow: + +| <b>SrcAddress</b> | <b>SrcPort</b> | <b>DestAddress</b> | <b>DestPort</b> | <b>ProtocolID</b> | +|------------------------|----------------|-----------------------|-----------------|-------------------| +| <b>204.142.180.111</b> | * | <b>192.141.10.188</b> | <b>32416</b> | <b>17</b> | + +The udp application flow may be assigned a maximum QoS class corresponding to interactive. The b parameter is used to determine the data rate. + +NOTE: The sample mappings in this section are for illustration purpose only. The actual mapping of media codec to QoS resource requirement is specified in TS 29.208. + +# --- Annex D (informative): Resource reservation and end-to-end RSVP + +## D.1 Resource reservation with end-to-end RSVP + +For this case, RSVP is added to the GPRS bearer establishment procedures specified in TS 23.060 [19], with no Service-based local policy. + +NOTE: The diagrams in this subsection depict one possible signalling sequence, however, the alternative signalling sequences below are possible: + +- to trigger the Create PDP Context Request message after the PATH message. +- to trigger the Create PDP Context Request message after the RESV message. +- to trigger only one PDP context after all RSVP exchanges have completed. + +NOTE: The diagrams in this subsection depict the case when the GGSN is not RSVP aware, however, the alternative of GGSN being RSVP aware is also possible. + +The following figure is applicable to the Mobile Originating (MO) side. + +![Sequence diagram titled 'MO Network' showing resource reservation steps between UE, SGSN, GGSN, and PDF. The diagram is split into uplink (above a dotted line) and downlink (below a dotted line) sections. Uplink steps: 1. UE to SGSN: Activate(Secondary) PDP Context; 2. SGSN to GGSN: Create PDP Context; 3. GGSN to SGSN: Create PDP Response; 4. SGSN to UE: RAB Setup; 5. SGSN to UE: Activate(Secondary) PDP Accept; 6. UE to PDF: RSVP-PATH. Downlink steps: 7. PDF to UE: RSVP-RESV; 8. PDF to GGSN: RSVP-RECV-CONF; 9. PDF to UE: RSVP-PATH; 10. UE to SGSN: Modify PDP Context; 11. SGSN to GGSN: Update PDP Context Request; 12. GGSN to SGSN: Update PDP Response; 13. SGSN to UE: RAB Modify; 14. SGSN to UE: Modify PDP Accept; 15. PDF to UE: RSVP-RESV; 16. PDF to GGSN: RSVP-RECV-CONF.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SGSN + participant GGSN + participant PDF + Note over all: MO Network + + Note over all: Uplink (above dotted line) + UE->>SGSN: 1. Activate(Secondary) PDP Context + SGSN->>GGSN: 2. Create PDP Context + GGSN-->>SGSN: 3. Create PDP Response + SGSN->>UE: 4. RAB Setup + SGSN->>UE: 5. Activate(Secondary) PDP Accept + UE->>PDF: 6. RSVP-PATH + + Note over all: Downlink (below dotted line) + PDF-->>UE: 7. RSVP-RESV + PDF->>GGSN: 8. RSVP-RECV-CONF + PDF-->>UE: 9. RSVP-PATH + UE->>SGSN: 10. Modify PDP Context + SGSN->>GGSN: 11. Update PDP Context Request + GGSN-->>SGSN: 12. Update PDP Response + SGSN->>UE: 13. RAB Modify + SGSN->>UE: 14. Modify PDP Accept + PDF-->>UE: 15. RSVP-RESV + PDF->>GGSN: 16. RSVP-RECV-CONF + +``` + +Sequence diagram titled 'MO Network' showing resource reservation steps between UE, SGSN, GGSN, and PDF. The diagram is split into uplink (above a dotted line) and downlink (below a dotted line) sections. Uplink steps: 1. UE to SGSN: Activate(Secondary) PDP Context; 2. SGSN to GGSN: Create PDP Context; 3. GGSN to SGSN: Create PDP Response; 4. SGSN to UE: RAB Setup; 5. SGSN to UE: Activate(Secondary) PDP Accept; 6. UE to PDF: RSVP-PATH. Downlink steps: 7. PDF to UE: RSVP-RESV; 8. PDF to GGSN: RSVP-RECV-CONF; 9. PDF to UE: RSVP-PATH; 10. UE to SGSN: Modify PDP Context; 11. SGSN to GGSN: Update PDP Context Request; 12. GGSN to SGSN: Update PDP Response; 13. SGSN to UE: RAB Modify; 14. SGSN to UE: Modify PDP Accept; 15. PDF to UE: RSVP-RESV; 16. PDF to GGSN: RSVP-RECV-CONF. + +**Figure D.1: MO Resource Reservation with End-to-End RSVP** + +NOTE: There is no timing relationship between the set of flows for the uplink (above the line) and the downlink (below the line). + +- 1) The UE sends an Activate (Secondary) PDP Context message to the SGSN with the UMTS QoS parameters. +- 2) The SGSN sends the corresponding Create PDP Context message to the GGSN. +- 3) The GGSN authorizes the PDP context activation request according to the local operator's IP bearer resource based policy, the local operator's admission control function and the GPRS roaming agreements and sends a Create PDP Context Response message back to the SGSN. +- 4) RAB setup is done by the RAB Assignment procedure. +- 5) The SGSN sends an Activate (Secondary) PDP Context Accept message to UE. +- 6) UE sends an RSVP PATH message to the next hop, through the GGSN. The GGSN does not process the RSVP PATH message. Alternatively, the GGSN may process the RSVP PATH message and forward it to the next hop. +- 7) The UE receives the RSVP RESV message in the downlink direction, through the GGSN. The GGSN does not process the RSVP RESV message. Alternatively, the GGSN may process the RSVP RESV message and forward it to the UE. + +- 8) The UE sends a RSVP RESV-CONF message to the next hop. The use of the RESV-CONF message is optional. +- 9) The UE receives a RSVP PATH message in the downlink direction, through the GGSN. The GGSN does not process the RSVP PATH message. Alternatively, the GGSN may process the incoming RSVP PATH message and forward it to the UE. +- 10) The UE may send a Modify PDP Context message to the SGSN with the necessary modification to UMTS QoS parameters according to the received RSVP PATH message. +- 11) The SGSN sends the corresponding Update PDP Context Request message to the GGSN. +- 12) The GGSN authorizes the PDP context modification according to the local operator's IP bearer resource based policy, the local operator's admission control function and the GPRS roaming agreements and sends an Update PDP Context Response message back to the SGSN. +- 13) The radio access bearer modification may be performed by the RAB Assignment procedure. +- 14) The SGSN sends a Modify PDP Context Accept message to UE. +- 15) UE sends the RSVP RESV message to the next hop, through the GGSN. The GGSN does not process the RSVP RESV message. Alternatively, the GGSN may process the RSVP RESV message and forward it to the next hop. +- 16) The UE receives the RSVP RESV-CONF message in the downlink direction. The use of the RESV-CONF message is optional. + +The following figure is applicable to the Mobile Terminating (MT) side. As the flow is the mirror of the Mobile Originating (MO) side, the step-by-step description is omitted. + +![Sequence diagram for MT Resource Reservation with End-to-End RSVP. The diagram shows interactions between PDF, GGSN, SGSN, and UE within an MT Network. The process is divided into uplink (above a dotted line) and downlink (below a dotted line) flows. Uplink: UE sends 1. Activate(Secondary) PDP Context to SGSN; SGSN sends 2. Create PDP Context to GGSN; GGSN sends 3. Create PDP Response to SGSN; SGSN sends 4. RAB Setup to UE; UE sends 5. Create(Secondary) PDP Accept to SGSN. Downlink: SGSN sends 6. RSVP-PATH to PDF; PDF sends 7. RSVP-RESV to UE; UE sends 8. RSVP-RECV-CONF to PDF. After the dotted line: UE sends 9. RSVP-PATH to SGSN; SGSN sends 10. Modify PDP Context to UE; UE sends 11. Update PDP Context to SGSN; SGSN sends 12. Update PDP Response to UE; UE sends 13. RAB Modify to SGSN; SGSN sends 14. Modify PDP Accept to UE. Finally, SGSN sends 15. RSVP-RESV to PDF; PDF sends 16. RSVP-RECV-CONF to UE.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +Sequence diagram for MT Resource Reservation with End-to-End RSVP. The diagram shows interactions between PDF, GGSN, SGSN, and UE within an MT Network. The process is divided into uplink (above a dotted line) and downlink (below a dotted line) flows. Uplink: UE sends 1. Activate(Secondary) PDP Context to SGSN; SGSN sends 2. Create PDP Context to GGSN; GGSN sends 3. Create PDP Response to SGSN; SGSN sends 4. RAB Setup to UE; UE sends 5. Create(Secondary) PDP Accept to SGSN. Downlink: SGSN sends 6. RSVP-PATH to PDF; PDF sends 7. RSVP-RESV to UE; UE sends 8. RSVP-RECV-CONF to PDF. After the dotted line: UE sends 9. RSVP-PATH to SGSN; SGSN sends 10. Modify PDP Context to UE; UE sends 11. Update PDP Context to SGSN; SGSN sends 12. Update PDP Response to UE; UE sends 13. RAB Modify to SGSN; SGSN sends 14. Modify PDP Accept to UE. Finally, SGSN sends 15. RSVP-RESV to PDF; PDF sends 16. RSVP-RECV-CONF to UE. + +**Figure D.2: MT Resource Reservation with End-to-End RSVP** + +NOTE: There is no timing relationship between the set of flows for the uplink (above the line) and the downlink (below the line). + +## D.2 Resource Reservation with End-to-End RSVP and Service-based Local Policy + +For this case, Service-based Local Policy and RSVP are added to the GPRS bearer establishment procedures specified in TS 23.060 [19]. + +NOTE: The diagrams in this subsection depict one possible signalling sequence, however, the alternative signalling sequences below are possible: + +- to trigger the Create PDP Context Request message after the PATH message. +- to trigger the Create PDP Context Request message after the RESV message. +- to trigger only one PDP context after all RSVP exchanges have completed. + +NOTE: The diagrams in this subsection depict the case when the GGSN is RSVP aware, however, the alternative of GGSN not being RSVP aware is also possible. + +This section provides the flows for bearer establishment, resource reservation and policy control with RSVP. + +The following figure is applicable to the Mobile Originating (MO) side. + +![Sequence diagram for MO Resource Reservation with End-to-End RSVP and Service-based Local Policy. The diagram shows interactions between UE, SGSN, GGSN, and PDF within the MO Network. It is divided into two parts by a dotted line: uplink (top) and downlink (bottom).](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SGSN + participant GGSN + participant PDF + Note over UE, PDF: MO Network + + Note over UE, PDF: Uplink (above the line) + UE->>SGSN: 1. Activate(Secondary) PDP Context + SGSN->>GGSN: 2. Create PDP Context + GGSN->>PDF: 3. Req + PDF-->>GGSN: 4. Dec + GGSN->>PDF: 5. Rpt + GGSN->>SGSN: 6. Create PDP Response + SGSN->>UE: 7. RAB Setup + UE->>SGSN: 8. Activate(Secondary) PDP Accept + UE->>GGSN: 9. RSVP-PATH + GGSN->>PDF: 10. RSVP-PATH + PDF-->>GGSN: 11. RSVP-RESV + GGSN->>UE: 12. RSVP-RESV + GGSN->>PDF: 13. RSVP-RECV-CONF + + Note over UE, PDF: Downlink (below the line) + PDF->>GGSN: 14. RSVP-PATH + GGSN->>UE: 15. RSVP-PATH + UE->>SGSN: 16. Modify PDP Context + SGSN->>GGSN: 17. Update PDP Context + GGSN->>SGSN: 18. Update PDP Response + SGSN->>UE: 19. RAB Modify + UE->>SGSN: 20. Modify PDP Accept + UE->>GGSN: 21. RSVP-RESV + GGSN->>PDF: 22. RSVP-RESV + GGSN->>UE: 23. RSVP-RECV-CONF + +``` + +Sequence diagram for MO Resource Reservation with End-to-End RSVP and Service-based Local Policy. The diagram shows interactions between UE, SGSN, GGSN, and PDF within the MO Network. It is divided into two parts by a dotted line: uplink (top) and downlink (bottom). + +**Figure D.3: MO Resource Reservation with End-to-End RSVP and Service-based Local Policy** + +NOTE: There is no timing relationship between the set of flows for the uplink (above the line) and the downlink (below the line). + +- 1) The UE sends an Activate (Secondary) PDP Context message to the SGSN with the UMTS QoS parameters. The UE includes the Binding Information in the Activate PDP Context message. +- 2) The SGSN sends the corresponding Create PDP Context message to the GGSN. +- 3) The GGSN sends a COPS REQ message with the Binding Information to the PDF in order to obtain relevant policy information. +- 4) The PDF sends a COPS DEC message back to the GGSN. +- 5) The GGSN sends a COPS RPT message back to the PDF. +- 6) The GGSN maps IP flow based policy information into PDP context based policy information and uses the PDP context based policy information to accept the PDP activation request, and sends a Create PDP Context Response message back to SGSN. The GGSN may cache the policy information. +- 7) RAB setup is done by the RAB Assignment procedure. + +8) The SGSN sends an Activate (Secondary) PDP Context Accept message to UE. + +9) UE sends a RSVP PATH message to GGSN. The UE includes the Binding Information. + +NOTE: If the decision was previously cached locally at the GGSN, it may not be necessary to query the PDF again. Otherwise the GGSN may have to query the PDF. + +10) The GGSN uses the policy information to accept the RSVP PATH message, and forwards the RSVP PATH message to the next hop. + +11) The GGSN receives the RSVP RESV message in the downlink direction. + +NOTE: If the decision was previously cached locally at the GGSN, it may not be necessary to query the PDF again. Otherwise the GGSN may have to query the PDF. + +12) The GGSN uses the policy information to accept the RSVP RESV message, and forwards the RSVP RESV message to the UE. + +13) The UE sends a RSVP RESV-CONF message to the next hop. The use of the RESV-CONF message is optional. + +14) The GGSN receives a RSVP PATH message in the downlink direction. + +15) The GGSN forwards the RSVP PATH message to the UE. + +16) The UE may send a Modify PDP Context message to the SGSN with the necessary modification to UMTS QoS parameters according to the received RSVP PATH message. The UE includes the Binding Information in the Modify PDP Context message. + +17) The SGSN sends the corresponding Update PDP Context message to the GGSN. + +NOTE: If the decision was previously cached locally at the GGSN, it may not be necessary to query the PDF again. Otherwise the GGSN may have to query the PDF. + +18) The GGSN uses the policy information to accept the PDP modification request, and sends a Update PDP Context Response message back to SGSN. + +19) The radio access bearer modification may be performed by the RAB Assignment procedure. + +20) The SGSN sends a Modify PDP Context Accept message to UE. + +NOTE: Steps 16 to 20 are optional if the existing PDP context already satisfies the QoS requirements. + +21) The UE sends a RSVP RESV message to the GGSN. The UE includes the Binding Information in the RSVP RESV message. + +NOTE: If the decision was previously cached locally at the GGSN, it may not be necessary to query the PDF again. Otherwise the GGSN may have to query the PDF. + +22) The GGSN uses the policy information to accept the RSVP RESV message, and forwards the RSVP RESV message to the next hop. + +23) The UE receives the RSVP RESV-CONF message in the downlink direction. The use of the RESV-CONF message is optional. + +The following figure is applicable to the Mobile Terminating (MT) side. As the flow is the mirror of the Mobile Originating (MO) side, the step-by-step description is omitted. + +![Sequence diagram for MT Resource Reservation with End-to-End RSVP and Service-based Local Policy](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +The diagram illustrates the interaction between four entities: PDF, GGSN, SGSN, and UE, all contained within an MT Network. The sequence of messages is as follows: + +1. Activate(Secondary) PDP Context: UE to SGSN +2. Create PDP Context: SGSN to GGSN +3. Req: GGSN to PDF +4. Dec: PDF to GGSN +5. Rpt: PDF to GGSN +6. Create PDP Response: GGSN to SGSN +7. RAB Setup: SGSN to UE +8. Activate(Secondary) PDP Accept: UE to SGSN +9. RSVP-PATH: UE to GGSN +10. RSVP-PATH: GGSN to PDF +11. RSVP-RESV: PDF to GGSN +12. RSVP-RESV: GGSN to UE +13. RSVP-RECV-CONF: UE to GGSN +- (Dotted line separating uplink and downlink flows) +14. RSVP-PATH: GGSN to PDF +15. RSVP-PATH: PDF to UE +16. Modify PDP Context: UE to SGSN +17. Update PDP Context: SGSN to GGSN +18. Update PDP Response: GGSN to SGSN +19. RAB Modify: SGSN to UE +20. Modify PDP Accept: UE to SGSN +21. RSVP-RESV: UE to GGSN +22. RSVP-RESV: GGSN to PDF +23. RSVP-RECV-CONF: UE to GGSN + +Sequence diagram for MT Resource Reservation with End-to-End RSVP and Service-based Local Policy + +**Figure D.4: MT Resource Reservation with End-to-End RSVP and Service-based Local Policy** + +NOTE: There is no timing relationship between the set of flows for the uplink (above the line) and the downlink (below the line). + +# Annex E (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|------|-----|-----|------------------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 2003-09 | SP-21 | SP-030378 | 0060 | 1 | B | Functional additions for the Gq interface | 5.8.0 | 6.0.0 | +| 2003-12 | SP-22 | SP-030656 | 0061 | 3 | B | Procedures in the AF | 6.0.0 | 6.1.0 | +| 2003-12 | SP-22 | SP-030656 | 0062 | 1 | B | Information exchanged via Gq interface | 6.0.0 | 6.1.0 | +| 2003-12 | SP-22 | SP-030656 | 0063 | 1 | B | Procedures in the PDF | 6.0.0 | 6.1.0 | +| 2003-12 | SP-22 | SP-030656 | 0064 | - | D | Editorial corrections to 23.207 | 6.0.0 | 6.1.0 | +| 2004-01 | SP-22 | SP-030656 | 0065 | 2 | B | Gq-related updates to the signalling flows | 6.0.0 | 6.1.0 | +| 2004-01 | SP-22 | SP-030656 | 0066 | 3 | B | Requirements for IM CN Subsystem signalling flag | 6.0.0 | 6.1.0 | +| 2004-01 | SP-22 | SP-030656 | 0067 | - | F | Definition of the Application Function | 6.0.0 | 6.1.0 | +| 2004-03 | SP-23 | SP-040035 | 0074 | 1 | B | Update of Authorization on Gq | 6.1.1 | 6.2.0 | +| 2004-03 | SP-23 | SP-040035 | 0068 | 1 | B | Mapping amendment to PDF procedures | 6.1.1 | 6.2.0 | +| 2004-03 | SP-23 | SP-040035 | 0069 | 2 | B | Mapping amendment to AF procedures | 6.1.1 | 6.2.0 | +| 2004-03 | SP-23 | SP-040035 | 0073 | 1 | B | SBLP implications of bundling different IMS sessions to the same PDP Context | 6.1.1 | 6.2.0 | +| 2004-03 | SP-23 | SP-040035 | 0075 | 1 | B | Service information | 6.1.1 | 6.2.0 | +| 2004-06 | SP-24 | SP-040317 | 0077 | 3 | B | Authorisation Reject Procedure by the PDF | 6.2.0 | 6.3.0 | +| 2004-06 | SP-24 | SP-040317 | 0079 | 1 | F | AF capabilities | 6.2.0 | 6.3.0 | +| 2004-06 | SP-24 | SP-040317 | 0080 | 2 | B | General corrections | 6.2.0 | 6.3.0 | +| 2004-06 | SP-24 | SP-040317 | 0081 | 1 | F | Intra-domain Gq for IMS | 6.2.0 | 6.3.0 | +| 2004-06 | SP-24 | SP-040317 | 0083 | - | B | Condition for update authorization procedure | 6.2.0 | 6.3.0 | +| 2004-09 | SP-25 | SP-040521 | 0084 | 1 | F | SBLP and non-realtime PDP Contexts | 6.3.0 | 6.4.0 | +| 2004-09 | SP-25 | SP-040521 | 0085 | - | F | Generation of multiple tokens | 6.3.0 | 6.4.0 | +| 2005-06 | SP-28 | SP-050337 | 0087 | - | F | Update of binding information handling | 6.4.0 | 6.5.0 | +| 2005-09 | SP-29 | SP-050337 | 0088 | 1 | A | Correction of reference to non-existent/obsolete document | 6.5.0 | 6.6.0 | +| 2007-06 | SP-36 | SP-070392 | 0092 | 5 | B | Rel-7 version of TS 23.207 main body | 6.6.0 | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | - | Update to Rel-8 version (MCC) | 7.0.0 | 8.0.0 | +| 2009-12 | SP-46 | - | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | +| 2011-03 | SP-51 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | SP-57 | SP-120627 | 0093 | 1 | F | Reference list correction to align with the corrected TS 29.212 title | 10.0.0 | <b>11.0.0</b> | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23221/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/23_series/23221/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfd4ad8461a828c2a00555fa15b8f36a2df425ab --- /dev/null +++ b/marked/Rel-11/23_series/23221/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4ea6d6ab755c90f08b788d73e359165d17d039f645eb3642f68ee95651c3f95 +size 36368 diff --git a/marked/Rel-11/23_series/23221/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg b/marked/Rel-11/23_series/23221/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..590d1d80324925e2b12fa916005bf611254afe52 --- /dev/null +++ b/marked/Rel-11/23_series/23221/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05a3ad13f533eb95de94a724b28ab757962b1b23fddeeaa3b1d416c4640ee941 +size 41017 diff --git a/marked/Rel-11/23_series/23221/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/23_series/23221/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acbc47929dee730e6098b3c78ad2fa6bca781e32 --- /dev/null +++ b/marked/Rel-11/23_series/23221/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e4fc9e30f8a2d131b5c898462f8dd1e49cadad0cccb42dc5f79822aae9d5308 +size 59405 diff --git a/marked/Rel-11/23_series/23221/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-11/23_series/23221/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d87fdc720affc0f13f7ef43dd7f98cf2d21f0327 --- /dev/null +++ b/marked/Rel-11/23_series/23221/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:689a0082afb43b9372ad9496f68155af3e43b58e9d0c3ac92d900231426e5d89 +size 36023 diff --git a/marked/Rel-11/23_series/23221/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-11/23_series/23221/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01fb32ec03de607f7f1b6d055554abb4a80c6a10 --- /dev/null +++ b/marked/Rel-11/23_series/23221/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71e5383e52a6deac863b2749952cda333ec5be5c7e400cd33a37de05f2913c28 +size 68788 diff --git a/marked/Rel-11/23_series/23221/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-11/23_series/23221/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25ce375a82b4de689f6348d6fa6245f794e96bf6 --- /dev/null +++ b/marked/Rel-11/23_series/23221/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9bbbcfdd5ef5292f0e483a2d4b4c9beeebc72bfe4e0fe28c836edad8ba7f661 +size 75529 diff --git a/marked/Rel-11/23_series/23221/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/Rel-11/23_series/23221/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dfbd93eebaa63a16cfe9ef64de5de04c025810b --- /dev/null +++ b/marked/Rel-11/23_series/23221/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a7d80584c37b448ebf75bbd8ea7aed4a24baca61a8e08d2c09317236443d0f3 +size 60468 diff --git a/marked/Rel-11/23_series/23221/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/marked/Rel-11/23_series/23221/5478f70a6cef3e5672b2b22d28830cfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ebf6980d808d658982603e173efe596b9ba8828 --- /dev/null +++ b/marked/Rel-11/23_series/23221/5478f70a6cef3e5672b2b22d28830cfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31280b7172aee08e0d1b2bd0e7ee578b8485e82c5c08e31a445f43b494a142dd +size 76641 diff --git a/marked/Rel-11/23_series/23221/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/Rel-11/23_series/23221/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4f9643994c971361d399a202c1b7d81c6df34c5 --- /dev/null +++ b/marked/Rel-11/23_series/23221/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2caba276c48aaf2836e03afad5f5cd92516b189a4985aebdc39d1b29dd8c0073 +size 79616 diff --git a/marked/Rel-11/23_series/23221/704082cc3e11776bda29595c76411362_img.jpg b/marked/Rel-11/23_series/23221/704082cc3e11776bda29595c76411362_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fcb3c8ac37d9f9ff4c4b8ee62d3c0bc98bc64e6 --- /dev/null +++ b/marked/Rel-11/23_series/23221/704082cc3e11776bda29595c76411362_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c596410e86abca1d0ffa3d3ef22bb612797bdcd653bdb12e54d3c18538c4a7e7 +size 69661 diff --git a/marked/Rel-11/23_series/23221/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-11/23_series/23221/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1685b7c08ce85690c722da26c02a433a55077369 --- /dev/null +++ b/marked/Rel-11/23_series/23221/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:106b5336b382f971ee64227edc8468c027cace4ff9a60fc271d7635cebb47eec +size 48146 diff --git a/marked/Rel-11/23_series/23221/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/23_series/23221/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75bd32f991c3d0d9650c441130bb91e1e05d2b77 --- /dev/null +++ b/marked/Rel-11/23_series/23221/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4de3612c145f6e9a35fa7dcbdaba33a262a01b2fc33317fe920cf3c2cd680e5 +size 68797 diff --git a/marked/Rel-11/23_series/23221/8d8c758885b4f754ff071bf3b572ab3c_img.jpg b/marked/Rel-11/23_series/23221/8d8c758885b4f754ff071bf3b572ab3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6f7fab3164cec6a1aafea4524fc4f5fe73a8655 --- /dev/null +++ b/marked/Rel-11/23_series/23221/8d8c758885b4f754ff071bf3b572ab3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29ba51cf2ba9a4dee69b35c9f6d3d88257d7be1c2c2d98979338c4305e595f2e +size 93598 diff --git a/marked/Rel-11/23_series/23221/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/23_series/23221/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d08299a5a8d5a893295620ea69f03fdd75f3432e --- /dev/null +++ b/marked/Rel-11/23_series/23221/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa5174f2cb7e3ab873b6812b84f26a2fed953db6544cc454bf9017910d9fe047 +size 103390 diff --git a/marked/Rel-11/23_series/23221/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-11/23_series/23221/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38d086613ac3977d96e129b61e6540642c4d8e91 --- /dev/null +++ b/marked/Rel-11/23_series/23221/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5dc3db1d755e0fba20a9751429306562083cbc5b3f7c93ebe1d66c0a8023370c +size 58318 diff --git a/marked/Rel-11/23_series/23221/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-11/23_series/23221/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b431bcfdb87ee08c4dcdd3cce79763f03f7b162c --- /dev/null +++ b/marked/Rel-11/23_series/23221/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:949344a34e7e0cde5b5444b5755e058db3fc25577fa946878dd38cbb4a4fbecd +size 51436 diff --git a/marked/Rel-11/23_series/23221/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-11/23_series/23221/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73352cebc17d0fdf01c218ed7e069cc5b3ba8ec0 --- /dev/null +++ b/marked/Rel-11/23_series/23221/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f503cc19999618546c3401a2d02cb7c5c64ba0e45a82d70fe8ebe302f27f9882 +size 33954 diff --git a/marked/Rel-11/23_series/23221/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-11/23_series/23221/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52a97c96666a4f43b469cdb31a6200f56ec54fd9 --- /dev/null +++ b/marked/Rel-11/23_series/23221/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26829739d9cc7b1c319f7877c66db101c606ed2923100285a2befd0b3bad181e +size 86513 diff --git a/marked/Rel-11/23_series/23221/a7c51c18111139f9aca2805114108565_img.jpg b/marked/Rel-11/23_series/23221/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a466f114420641f1de3ed36d6013eca96f8bc9c0 --- /dev/null +++ b/marked/Rel-11/23_series/23221/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17a6b29c2105423fcf5a6b994a998b50672aa8f21093c05da6c216e8ac1dbbc0 +size 54628 diff --git a/marked/Rel-11/23_series/23221/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-11/23_series/23221/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6499d43cec4c8e09095dec7e2578e28ff64da026 --- /dev/null +++ b/marked/Rel-11/23_series/23221/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:360c5a4202eceaf8bdf3d6ddc8f9939eec5eee756b96378b6c61ee74a3bc3a72 +size 61411 diff --git a/marked/Rel-11/23_series/23221/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Rel-11/23_series/23221/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bfe3fa61362d387ae0da66c916bb8320778872f --- /dev/null +++ b/marked/Rel-11/23_series/23221/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8480e252f3e0d7c96d98e8be468a05dd4c58b4c3225700246541462dbe85160c +size 44686 diff --git a/marked/Rel-11/23_series/23221/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-11/23_series/23221/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..926bd895042e905dacfddf92c353e2bc8da70de3 --- /dev/null +++ b/marked/Rel-11/23_series/23221/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9aee10abbb212244abdc99e95c7321dff054384b40b289996425d0e88ddd5b9d +size 77468 diff --git a/marked/Rel-11/23_series/23221/c0e369274e53b2e5364666be6f786c7a_img.jpg b/marked/Rel-11/23_series/23221/c0e369274e53b2e5364666be6f786c7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7718129d5e4cbb48b2f8e97379cb02e1b1be048b --- /dev/null +++ b/marked/Rel-11/23_series/23221/c0e369274e53b2e5364666be6f786c7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52888a3bc558d4f7d628e10aadaa5eeafc663d8607bd73784d073d028cb96757 +size 31074 diff --git a/marked/Rel-11/23_series/23221/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg b/marked/Rel-11/23_series/23221/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ea980065ee6f01243488bc219c714ce916a929f --- /dev/null +++ b/marked/Rel-11/23_series/23221/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db9f19c3e32698d9ac8a454a7a99c38574aabc581662533f7ae4b45be5907b8b +size 60831 diff --git a/marked/Rel-11/23_series/23221/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-11/23_series/23221/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a62ba02754e7beaf8c94516cfc7bd7f420e04867 --- /dev/null +++ b/marked/Rel-11/23_series/23221/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63130fb5b2bdaa2a2a6f860b0801c34a9b0bbca1da51fcd932727f6c75aadc09 +size 36743 diff --git a/marked/Rel-11/23_series/23221/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg b/marked/Rel-11/23_series/23221/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d4fd6aca124887bff823618eb4e1905ae31978f --- /dev/null +++ b/marked/Rel-11/23_series/23221/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:626e3d4d6596faf2e9caf30d0b366b0dfaac5b41a19614d71a8668af4165905b +size 56591 diff --git a/marked/Rel-11/23_series/23221/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/23_series/23221/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..289fc09b75188affbeffd7800f6daf5c863f1fc8 --- /dev/null +++ b/marked/Rel-11/23_series/23221/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86e3972a078d87499e84427c8bb8706325eb36fda40a597d6743ca6b60488828 +size 47562 diff --git a/marked/Rel-11/23_series/23221/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg b/marked/Rel-11/23_series/23221/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69054f3e73055c63d3f651b195a7548057b53c7a --- /dev/null +++ b/marked/Rel-11/23_series/23221/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8e1ca7035c87343cd8dd86c6cdee631b69ac6f6badb833e2f483942197fd99b +size 113876 diff --git a/marked/Rel-11/23_series/23221/f24f909d837b5476783e1bbea2dfc143_img.jpg b/marked/Rel-11/23_series/23221/f24f909d837b5476783e1bbea2dfc143_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..521e17a773a6befb98bc86f345b468e1566625ac --- /dev/null +++ b/marked/Rel-11/23_series/23221/f24f909d837b5476783e1bbea2dfc143_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63ba58cd8fc1b36ca370326ba122926eb077e6c9e907c3df0deb3695aec32b89 +size 66190 diff --git a/marked/Rel-11/23_series/23221/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23221/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efc0e12b957d27ea257f3fa75a03c68f93c5d6b7 --- /dev/null +++ b/marked/Rel-11/23_series/23221/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:126a464c5481702b33ad2a3804d9f2a1c9e8ba9a54809c7849e1ca31b440457a +size 47290 diff --git a/marked/Rel-11/23_series/23221/raw.md b/marked/Rel-11/23_series/23221/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..be39c1eb64615f815e703abc47d07c01b62b38bd --- /dev/null +++ b/marked/Rel-11/23_series/23221/raw.md @@ -0,0 +1,1620 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 3GPP system domains and subsystems..... | 10 | +| 4.1 Allowed network and terminal configurations..... | 10 | +| 4.2 Circuit switched (CS) core network domain..... | 10 | +| 4.2.1 Iu mode to Iu mode handover for circuit switched services..... | 10 | +| 4.2.2 A mode to Iu mode handover for CS services..... | 11 | +| 4.2.3 General principles for use of CS-MGW resources..... | 11 | +| 4.2.4 Transcoder location ..... | 11 | +| 4.3 Packet Switched (PS) core network domain ..... | 11 | +| 4.4 IP Multimedia subsystem (IMS) ..... | 11 | +| 4.5 Cross Core Network Domain Requirements..... | 11 | +| 4.6 UTRAN..... | 11 | +| 4.7 GERAN ..... | 12 | +| 4.8 E-UTRAN ..... | 12 | +| 5 IP addressing..... | 12 | +| 5.1 IP version issues..... | 12 | +| 5.2 Interoperability between IPv4 and IPv6 networks ..... | 12 | +| 5.2.1 IPv4/IPv6 Mobile connecting to IPv4 and IPv6 networks ..... | 12 | +| 5.2.2 IPv6 only Mobile connecting to IPv4 network..... | 13 | +| 5.2.3 IPv6 Mobile connected to an IPv6 Device via an IPv4 network..... | 14 | +| 5.3 Address management ..... | 14 | +| 5.4 IP addressing and routing for access to IM-subsystem services ..... | 15 | +| 5.5 Simultaneous access to multiple services..... | 16 | +| 5.6 UE support of IPv6..... | 17 | +| 5.7 IP addressing and routing for server/application..... | 18 | +| 6 Mobility management ..... | 18 | +| 6.1 Introduction ..... | 18 | +| 6.2 Location management and mobility management concept overview ..... | 18 | +| 6.2.1 Non-combined procedures..... | 18 | +| 6.2.2 Use of combined procedures ..... | 20 | +| 6.3 Description of the location management and mobility management concept - area concepts ..... | 21 | +| 6.3.1 Introduction ..... | 21 | +| 6.3.2 Location areas..... | 21 | +| 6.3.3 Tracking and Routing areas..... | 21 | +| 6.3.3a Support of Iu and A/Gb mode of operation in GERAN Cells..... | 21 | +| 6.3.3a.1 Overview..... | 21 | +| 6.3.3a.2 Interface selection in GERAN Cells..... | 22 | +| 6.3.3a.2.1 Basic principles for MS controlled Cell/Mode selection/re-selection ..... | 22 | +| 6.3.3a.2.2 Basic principles for network controlled Mode selection/re-selection..... | 22 | +| 6.3.4 RAN internal areas ..... | 22 | +| 6.3.5 Relationship between the different areas..... | 23 | +| 6.3.5a Restriction of subscribers' access..... | 24 | +| 6.3.6 Hierarchical tracking concept..... | 24 | +| 6.4 Relationship between MM and SM states for an UE..... | 25 | +| 6.5 Requirement in case of temporarily loss of coverage of packet UE ..... | 25 | +| 6.6 MM functionality in different UE service states..... | 25 | +| 6.7 The RRC state machine..... | 26 | +| 6.8 Relationship between CS and PS service states and RRC state for an UE ..... | 27 | +| 6.9 Service registration and location update ..... | 28 | + +| | | | +|-------------------------------|------------------------------------------------------------------------------|-----------| +| 6.9.1 | Introduction ..... | 28 | +| 6.9.2 | Location area update..... | 29 | +| 6.9.3 | Tracking and Routing area update..... | 29 | +| 6.9.4 | Combined updates ..... | 29 | +| 6.10 | Paging initiated by CN ..... | 29 | +| 6.11 | Signalling connection establishment..... | 29 | +| 6.11a | CS Domain Signalling Requirements (in particular relating to handover) ..... | 30 | +| 6.12 | Relations between SRNS relocation and location registration..... | 30 | +| 6.13 | Requirements on identifiers for UMTS and GSM ..... | 31 | +| 6.14 | Use of MM system information ..... | 32 | +| 6.15 | Signalling procedures..... | 32 | +| 6.15.1 | Idle mode procedures ..... | 32 | +| 6.15.1.1 | Location Area update..... | 33 | +| 6.15.1.2 | Routing Area Update ..... | 34 | +| 6.15.1.2A | Tracking Area Update..... | 34 | +| 6.15.1.3 | Periodic registration towards both CN nodes without use of Gs or SGs ..... | 34 | +| 6.15.1.4 | Periodic registration with use of Gs or SGs..... | 34 | +| 6.15.1.5 | UE initiated combined detach procedure when using Gs or SGs ..... | 34 | +| 6.15.1.6 | Forbidden LA/RA ..... | 34 | +| 6.15.2 | SRNS Relocation..... | 34 | +| 6.16 | RAN coordination ..... | 34 | +| 7 | Call control..... | 35 | +| 7.1 | General Aspects..... | 35 | +| 7.2 | Domain selection for mobile terminated calls from the PSTN/CS domain ..... | 36 | +| 7.2.1 | Introduction ..... | 36 | +| 7.2.2 | Calls directed to the CS domain ..... | 36 | +| 7.2.3 | Calls directed to the IMS..... | 36 | +| 7.2a | Domain selection for UE originating sessions / calls..... | 36 | +| 7.2b | Access Domain Selection for terminating sessions..... | 38 | +| 7.2c | Domain Selection for UE originating SMS..... | 39 | +| 7.2d | Domain selection decisions during ongoing sessions ..... | 39 | +| 7.3 | Routing sessions from the IMS to the CS Domain ..... | 40 | +| 8 | Support of IM CN Subsystem services ..... | 40 | +| 8.1 | Context activation and registration ..... | 40 | +| 8.2 | Location management ..... | 41 | +| 8.2.1 | Registration concepts for a subscriber roaming into CS domain ..... | 41 | +| 8.3 | IMS Emergency sessions ..... | 43 | +| 8.3.1 | GPRS/EPS considerations for UE recognized IMS Emergency Sessions ..... | 43 | +| 8.3.2 | Emergency Calls in absence of UICC for GPRS/EPS Access ..... | 43 | +| 9 | Efficient use of radio resource ..... | 43 | +| <b>Annex A (informative):</b> | <b>Guidance for CSFB and IMS enabled UE implementations in E-UTRAN.....</b> | <b>44</b> | +| A.1 | General..... | 44 | +| A.2 | IMS PS Voice preferred..... | 44 | +| A.2.1 | EPS Attach ..... | 44 | +| A.2.2 | Combined EPS/IMSI attach ..... | 45 | +| A.3 | CS Voice preferred..... | 46 | +| A.4 | IMS PS Voice only ..... | 47 | +| A.5 | CS Voice only ..... | 47 | +| <b>Annex B (informative):</b> | <b>Guidance related to IPv4 address usage .....</b> | <b>49</b> | +| B.1 | General..... | 49 | +| B.2 | Interworking aspects ..... | 49 | +| B.2.1 | Interworking scenario: UE assigned private IPv4 address..... | 49 | +| B.2.2 | Use of Device triggering ..... | 49 | + +B.2.3 Specific APN use .....50 + +Annex C (informative): Change history.....51 + +# --- Foreword + +This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +This document covers the architectural requirements for 3GPP systems based on UTRAN, E-UTRAN and Iu mode GERAN. In particular it details the high level requirements for the Circuit Switched (CS) Domain and the stage 2 procedures that span more than one domain/subsystem. The reference model to which these procedures apply can be found within TS 23.002 [1]. In addition, A mode to Iu mode handover for CS services is addressed. Detailed architectural requirements within the subsystems are contained within the remainder of the 23 series of specifications e.g. the requirements for the Packet Switched (PS) domain are contained within TS 23.060 [2], TS 23.401 [27] and the requirements for the Bearer Independent CS Core Network are contained in TS 23.205[14]. + +# --- 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.002: "Network Architecture". +- [2] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2". +- [3] 3GPP TS 23.012: "Location management procedures". +- [5] 3GPP TS 25.331: "Radio Resource Control (RRC) Protocol Specification". +- [6] 3GPP TS 25.301: "Radio interface protocol architecture". +- [7] 3GPP TS 25.303: "UE functions and inter-layer procedures in connected mode". +- [8] 3GPP TR 21.905: "3G Vocabulary". +- [9] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". +- [10] 3GPP TS 25.410: "UTRAN Iu Interface: General Aspects and Principles". +- [11] 3GPP TS 23.228: "IP Multimedia Subsystem – Stage 2". +- [12] 3GPP TS 43.051: "GERAN Overall Description". +- [13] 3GPP TS 23.153: "Out of Band Transcoder Control - Stage 2". +- [14] 3GPP TS 23.205: "Bearer Independent CS Core Network – Stage 2". +- [15] 3GPP TR 25.931: "UTRAN Functions, examples on signalling procedures". +- [16] RFC 2766: "Network Address Translation - Protocol Translation (NAT-PT)", G. Tsirtsis, P. Srisuresh. February 2000. +- [17] RFC 2893: "Transition Mechanisms for IPv6 Hosts and Routers", R. Gilligan, E. Nordmark, August 2000. +- [17a] RFC 4941: "Privacy Extensions for Stateless Address Autoconfiguration in IPv6", T. Narten, R. Daves, S. Krishnan, September 2007. +- [18] 3GPP TS 25.401 "UTRAN Overall Description". + +- [19] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode". +- [20] 3GPP TS 45.008: "Radio subsystem link control". +- [21] RFC3316: "IPv6 for Some Second and Third Generation Cellular Hosts", June 2002. +- [22] 3GPP TS 24.007: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3 General aspects". +- [23] 3GPP TS 24.229 "IP Multimedia Call Control Protocol based on SIP and SDP". +- [24] 3GPP TS 23.008: "Organisation of subscriber data". +- [25] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [26] 3GPP TR 23.981 "Interworking aspects and migration scenarios for IPv4 based IMS implementations". +- [27] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [28] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Overall description; Stage 2". +- [29] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [30] 3GPP TS 23.272: "Circuit Switched Fallback in Evolved Packet System; Stage 2". +- [31] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services". +- [32] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity". +- [33] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions". +- [34] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [35] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2". +- [36] 3GPP TR 23.975: "IPv6 Migration Guidelines". +- [37] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)". +- [38] 3GPP TS 23.682: "Architecture Enhancements to facilitate communications with Packet Data Networks and Applications". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms defined in TR 21.905 [8] apply, in addition, the following terms apply: + +**In Iu mode:** see TR 21.905 [8]. + +**In A/Gb mode:** see TR 21.905 [8]. + +**RAN:** within this document, the term RAN (Radio Access Network) is used to refer to UTRAN and/or GERAN in Iu mode and/or E-UTRAN. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|-----------------------------------------------| +| ATM | Asynchronous Transfer Mode | +| CM | Connection Management | +| CN | Core Network | +| CS | Circuit Switched | +| CSCF | Call/Session Control Function | +| CSFB | Circuit Switched Fallback | +| CS-MGW | Circuit Switched Media Gateway | +| DHCP | Dynamic Host Configuration Protocol | +| EPS | Evolved Packet System | +| E-UTRAN | Evolved UMTS Terrestrial Radio Access Network | +| GERAN | GSM/EDGE Radio Access Network | +| GGSN | Gateway GPRS Support Node | +| GPRS | General Packet Radio Service | +| GTP | GPRS Tunnelling Protocol | +| HLR | Home Location Register | +| IM | IP Multimedia | +| IMS | IP Multimedia Subsystem | +| IMSI | International Mobile Subscriber Identity | +| IP | Internet Protocol | +| IPSec | IP Security protocol | +| LA | Location Area | +| LAC | Location Area Code | +| LAN | Local Area Network | +| LLC | Logical Link Control | +| LM | Location Management | +| MAP | Mobile Application Part | +| MGCF | Media Gateway Control Function | +| MGW | Media Gateway | +| MM | Mobility Management | +| MME | Mobility Management Entity | +| MRF | Media Resource Function | +| MSC | Mobile Switching Centre | +| NAT | Network Address Translator | +| NGN | Next Generation Networks | +| OoBTC | Out of Band Transcoder Control | +| P-GW | PDN Gateway | +| PDA | Personal Digital Assistant | +| PDP | Packet Data Protocol | +| PLMN | Public Land Mobile Network | +| PS | Packet Switched | +| RA | Routing Area | +| RAC | Routing Area Code | +| RAI | Routing Area Identifier | +| RAN | Radio Access Network | +| RANAP | Radio Access Network Application Part | +| RLC | Radio Link Control | +| RNC | Radio Network Controller | +| RNTI | Radio Network Temporary Identifier | +| RRC | Radio Resource Control | +| S-GW | Serving Gateway | +| SGSN | Serving GPRS Support Node | +| SGW | Signalling gateway | +| SIP | Session Initiation Protocol | + +| | | +|-------|--------------------------------------------| +| SRNS | Serving Radio Network Subsystem | +| SS7 | Signalling System No. 7 | +| STM | Synchronous Transfer Mode | +| SRNS | Serving Radio Network Subsystem | +| TCP | Transmission Control Protocol | +| TMSI | Temporary Mobile Station Identifier | +| TrFO | Transcoder Free Operation | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| URA | UTRAN Registration Area | +| UTRAN | UMTS Terrestrial Radio Access Network | +| VHE | Virtual Home Environment | +| VLR | Visited Location Register | + +# --- 4 3GPP system domains and subsystems + +## 4.1 Allowed network and terminal configurations + +A 3GPP network is divided into a radio AN and a CN, which are connected via an open interface over the Iu or S1 or A/Gb reference point(s). The A/Gb mode is not further described in this specification. Furthermore, the core network is from a functional point of view divided into a PS Domain, IM Subsystem and a CS Domain (see TS 23.002 [1]). Any deployment of the IM subsystem requires a PS domain. + +The following network configurations shall be allowed: + +- networks which provide the functionality of CS Domain and PS Domain (and optionally IM Subsystem); +- networks which only provide the functionality of the CS Domain (only with GERAN or UTRAN access); +- networks which only provide the functionality of the PS Domain (and optionally IM Subsystem). + +The following terminal configurations shall be allowed: + +- terminals which are able to access both to the CS Domain and PS Domain (and optionally IM Subsystem); +- terminals which are only able to access to the PS Domain (and optionally IM Subsystem); +- terminals which are only able to access to the CS Domain. + +It shall be noted that a terminal which is only able to access to e.g. the PS Domain supports only mobility management, protocols etc. of that domain. The different configurations given above shall not prevent CS-type services from being delivered over the PS domain. + +## 4.2 Circuit switched (CS) core network domain + +### 4.2.1 Iu mode to Iu mode handover for circuit switched services + +For Iu mode to Iu mode Inter-MSC Hand-Over / SRNS relocation the MAP E interface transporting RANAP messages shall be used. Alternatively, in the case of intra-PLMN handover, the GSM to UMTS inter-system handover or SRNS relocation between two MSC-areas may be executed as intra-MSC inter-system handover or SRNS relocation respectively. In such a case this will be performed by utilising a direct SCCP connection between the target RNC located in the target MSC-area and the MSC server already involved in the call. + +For handover of circuit-switched services involving the change of CN equipment (only CS-MGW or CS-MGW and MSC-server) the anchor principle shall be applied. + +- The first MSC Server involved in a call will become the Anchor MSC Server for this call during and after handover, and will remain in the call until the call is released. Every subsequent handover (Intra and Inter) will be controlled by this MSC Server. + +- The first CS-MGW involved in a call will become the Anchor CS-MGW for this call during and after handover , and will remain in the call until the call is released. The Nc interface is anchored in the CS-MGW, the correlation between CS-MGW to PSTN and the CS-MGW to RAN remain fixed until the call is released. + +### 4.2.2 A mode to Iu mode handover for CS services + +For A mode to Iu mode inter-system Inter-MSC Hand-Over (GSM to UMTS) the MAP E interface transporting BSSMAP messages shall be used. As a network option, in the case of intra-PLMN inter-system handover from A mode to Iu mode, the handover between two MSC-areas may be executed as: + +- intra-MSC handover, if the serving BSS is connected to the Anchor MSC; or +- subsequent intra-MSC handover or subsequent inter-MSC handover back to the Anchor MSC Server, if the serving BSS is connected to an MSC-B. The decision between these two alternatives is implementation and network configuration dependent. + +The procedure will be performed by utilising a direct SCCP connection between the target RNC located in the target MSC-area and the Anchor MSC or MSC-B, respectively. + +### 4.2.3 General principles for use of CS-MGW resources + +The following principles for use of CS-MGW resources apply: + +1. it shall not be necessary to have the CS-MGW co-located with the MSC Server; +2. the CS-MGW resources need not be associated with any particular MSC Server (see note 1); +3. it shall be possible for any MSC Server to request resources of any CS-MGW in the network (see note 1); +4. it shall be possible for an RNC to connect to the CS-MGW indicated by the MSC server; + +Note 1: For points 2 and 3 above, issues related to O&M procedures such as where notification of restart of a CS-MGW should be sent to, need to be considered. Extensions to H.248 may be required. + +The specification of the Bearer Independent CS CN which uses the CS-MGW is in TS 23.205 [14]. + +### 4.2.4 Transcoder location + +The transcoders are located in the core network. They may be located in the CS-MGW at the border to the RAN (i.e. the CS-MGW at the Iu interface) or at the CS-MGW at the edge of the core network (e.g. at the edge towards the PSTN/ISDN), TS 23.153 [13]. + +## 4.3 Packet Switched (PS) core network domain + +The requirements for the GPRS PS domain are in TS 23.060 [2] and for the EPS PS domain in TS 23.401 [27]. + +## 4.4 IP Multimedia subsystem (IMS) + +The requirements for the IMS are in TS 23.228 [11]. + +## 4.5 Cross Core Network Domain Requirements + +The specifications shall support the option of IP transport for the MAP and CAP based interfaces + +## 4.6 UTRAN + +The requirements for the UTRAN are in the 3GPP 25-series of specifications. An overview can be found in TS 25.401 [18]. + +## 4.7 GERAN + +The requirements for the GERAN are in TS 43.051 [12] + +## 4.8 E-UTRAN + +The requirements for the E-UTRAN are in the 3GPP 36-series of specifications. An overview can be found in TS 36.300 [28]. + +# 5 IP addressing + +## 5.1 IP version issues + +The EPS/UMTS/GSM architecture shall support IPv4 / IPv6 based on the statements below. + +- IP transport between network elements of the IP Connectivity services (between RNC, SGSN, GGSN, eNodeB, MME, S-GW, and P-GW) and IP transport for the CS Domain: both IPv4 and IPv6 are options for IP Connectivity. +- For UEs used for Machine-Type Communications (MTC) IPv6 addressing as described in TS 23.401 [27] and TS 23.060 [2] should be the primary mechanism for IP addressing. IPv4 based addressing is considered a transition solution and is deprecated for MTC used over 3GPP accesses. + +For implementation guidelines related to transition and other aspects of IPv4 address usage see Annex B. + +- IM CN subsystem elements (UE to CSCF and the other elements e.g. MRF): + - The architecture should make optimum use of IPv6. + - 3GPP specifications design the IM CN subsystem elements and interfaces to support both IPv4 and IPv6. In the case the UE supports IPv4, the guidelines and recommendations in TR 23.981 [26] should be followed. + - The UE may support IPv4 only, IPv6 only or both for the connection to the IM CN subsystem. In the case the UE supports IPv4, the guidelines and recommendations in TR 23.981 [26] should be followed. + - According to the procedures defined in TS 23.060 [2] and/or TS 23.401 [27], when a UE is assigned an IPv6 prefix, it can change the global IPv6 address it is currently using via the mechanism defined in RFC 4941 [17a], or similar means. +- Access to existing data services (Intranet, Internet,...): +- The UE can access IPv4 and IPv6 based services. + +## 5.2 Interoperability between IPv4 and IPv6 networks + +Since the UE can access both IPv4 and IPv6 based services, situations may arise where interworking is needed to interoperate with IPv4 and IPv6 networks. This clause describes three different interworking scenarios: UE is IPv4 and IPv6 capable, IPv6 only UE, and IPv6 UE connected via IPv4 network to an IPv6 device. These scenarios are examples of IPv6 and IPv4 interworking. The scenarios presented below only considered cases of a Transition Gateway (TrGW) for generic services and specialist services may require additional functionality at the application level. + +In addition to the following subsections, Annex B describes additional guidelines for interoperability if such function is required (e.g. IMS, MTC). + +### 5.2.1 IPv4/IPv6 Mobile connecting to IPv4 and IPv6 networks + +An installation where the UE has both IPv4 and IPv6 stacks is shown in Figure 5-1. As depicted, the terminal connects to the IPv4 device directly using an IPv4 PDP or EPS Bearer Context. Hence, the UE appears to be a standard IPv4 node to the external IPv4 network. This scenario does not need any specific transition support from the network. However, it requires both versions of IP at the UE. The GGSN/P-GW in this scenario may be different for the IPv6 and the IPv4 connections unless IPv4/v6 PDP or EPS Bearer Contexts are used. With GGSN/P-GW is meant either a GGSN or a P-GW. + +![Figure 5-1: UE with IPv4 and IPv6 capability connecting to IPv4 and IPv6 networks. The diagram shows a UE with both IPv6 and IPv4 capabilities connected to a RAN. The RAN is connected to an (Evolved) Packet Core. From the Packet Core, a solid line (IPv6) connects to an IPv6 Network and an IPv6 Device, while a dashed line (IPv4) connects to an IPv4 Network and an IPv4 Device. A legend indicates that dashed lines represent IPv4 and solid lines represent IPv6.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 5-1: UE with IPv4 and IPv6 capability connecting to IPv4 and IPv6 networks. The diagram shows a UE with both IPv6 and IPv4 capabilities connected to a RAN. The RAN is connected to an (Evolved) Packet Core. From the Packet Core, a solid line (IPv6) connects to an IPv6 Network and an IPv6 Device, while a dashed line (IPv4) connects to an IPv4 Network and an IPv4 Device. A legend indicates that dashed lines represent IPv4 and solid lines represent IPv6. + +Figure 5-1: UE with IPv4 and IPv6 capability connecting to IPv4 and IPv6 networks + +### 5.2.2 IPv6 only Mobile connecting to IPv4 network + +![Figure 5-2: IPv6 only mobile connecting to IPv4 data services. The diagram shows an IPv6-only UE connected to a RAN, which is connected to an (Evolved) Packet Core. The Packet Core is connected to a TrGW (Transition Gateway). The TrGW is connected to an IPv4 Network and an IPv4 Device via a dashed line (IPv4). A legend indicates that dashed lines represent IPv4 and solid lines represent IPv6.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +Figure 5-2: IPv6 only mobile connecting to IPv4 data services. The diagram shows an IPv6-only UE connected to a RAN, which is connected to an (Evolved) Packet Core. The Packet Core is connected to a TrGW (Transition Gateway). The TrGW is connected to an IPv4 Network and an IPv4 Device via a dashed line (IPv4). A legend indicates that dashed lines represent IPv4 and solid lines represent IPv6. + +Figure 5-2: IPv6 only mobile connecting to IPv4 data services + +Figure 5-2 shows an IPv6 only terminal connected to an IPv4 device. The UE is using an IPv6 PDP or EPS Bearer Context for access to a Transition Gateway (TrGW) that translates the IPv6 packets to IPv4 and vice versa. The TrGW may be implemented as a Network Address Translation – Protocol Translation (NAT-PT) [16] to convert IPv6 traffic coming from the UE to IPv4 traffic and vice versa. + +NAT-PT is a combination of NAT-like address translation and IP header conversion as described in [16]. NAT-PT uses a pool of IPv4 addresses for assignment to IPv6 nodes on a dynamic basis as sessions are initiated across v4-v6 boundaries. NAT-PT binds addresses in the v6 network with addresses in the v4 network to provide transparent routing of packets traversing address realms. This requires no changes to end nodes and IP packet routing is completely transparent to them. It does, however, require NAT-PT to track the sessions it supports and mandates that inbound and outbound packets pertaining to a session traverse the same NAT-PT device. + +### 5.2.3 IPv6 Mobile connected to an IPv6 Device via an IPv4 network + +![Diagram of IPv6 mobile connected to an IPv6 device via an IPv4 network](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +The diagram illustrates a network architecture where an IPv6 mobile device (UE) is connected to an IPv6 network through an IPv4 network. On the left, a UE labeled 'IPv6' is connected to a 'RAN' (Radio Access Network), which is part of a larger 'Packet Core' labeled '(Evolved) Packet Core'. This core is connected to a 'TrGW' (Traffic Gateway). A dashed line representing an IPv4 network connects this 'TrGW' to another 'TrGW'. This second 'TrGW' is connected to an 'IPv6 Device', which is part of an 'IPv6 Network'. A legend box on the left indicates that dashed lines represent IPv4 and solid lines represent IPv6. + +Diagram of IPv6 mobile connected to an IPv6 device via an IPv4 network + +**Figure 5-3: IPv6 mobile connected to an IPv6 device via an IPv4 network** + +Figure 5-3 shows a case where an IPv4 network lies between two IPv6 domains. The IPv6 domains can be interconnected using IETF standard mechanisms such as automatic or configured tunnelling of IPv6 over IPv4 [17]. + +## 5.3 Address management + +A 3GPP network may be implemented as a number of logically separate IP networks which contain different parts of the overall system. Each of these elements is referred to as an "IP Addressing Domain". Within an "IP Addressing Domain" it is required that the nodes within the domain are part of a consistent non-overlapping IP-address space. It is also required that IP packets may be routed from any node in the domain to any other node in the domain using conventional IP routing. In a real implementation an IP Addressing Domain may be a physically separate IP network or an IP VPN. + +IP Addressing Domains may be interconnected at various points. At these points of interconnect gateways, firewalls or NATs may be present. It is not guaranteed that IP packets from one IP Addressing Domain can be directly routed to any interconnected IP Addressing Domain. Rather inter-Domain traffic may be handled via firewalls or tunnels. This implies that different IP Addressing Domains can have different (and possibly overlapping) address spaces. + +Figure 5-4 below shows an example of the IP Addressing Domains involved in PS-domain and IP-subsystem services. + +![Diagram of IP Addressing Domains involved in PS-Domain and IM Services](704082cc3e11776bda29595c76411362_img.jpg) + +This diagram shows the various IP Addressing Domains within a 3GPP network. A 'UE' (User Equipment) is connected to a 'Visited Network PS Domain Backbone' (containing 'S-GW/SGSN' and 'P-GW/GGSN'). This backbone is connected to an 'Inter-PLMN Backbone' (containing a 'BG' or Border Gateway) via an 'S8/Gp' interface. The 'Inter-PLMN Backbone' is connected to a 'Home Network PS Domain Backbone' (also containing 'S-GW/SGSN' and 'P-GW/GGSN') via another 'S8/Gp' interface and 'BG'. The 'Home Network PS Domain Backbone' is connected to a central 'SGi/Gi' interface. From this 'SGi/Gi' interface, traffic is distributed to several other domains: 'Home Network IM Subsystem' (containing a 'BG'), 'Inter-Network IM Backbone' (containing a 'BG'), 'Visited Network IM Subsystem', 'Internet', and 'Intranets'. A legend indicates that traffic tunneled over EPS/GPRS is shown with a double-headed arrow, and the 'SGi/Gi Implemented on VPN or dedicated resources' is also shown with a double-headed arrow. + +Diagram of IP Addressing Domains involved in PS-Domain and IM Services + +**Figure 5-4: IP Addressing Domains Involved In PS-Domain and IM Services** + +Though 3GPP networks can use different IP Addressing Domains as shown above, it is possible that several different IP Addressing Domains fall under a common co-operative management regime. In this case the different IP Addressing + +Domains may be implemented as a single administrative domain at the operator's discretion, thus using a common IP-address space. + +A UE accessing services in either an IM subsystem, the Internet, or an external Intranet, or a combination of these service domains within the same IP network, requires an IP address that is part of the target network's IP Addressing Domain. For each of these IP networks, the IP address is linked to a specific PDP or EPS Bearer context, or set of PDP or EPS Bearer contexts sharing this IP address via a single APN. + +When the UE establishes the PDP or EPS Bearer context to access an IP network, it may use an existing PDP or EPS Bearer context if it has an active context with a compatible IP addressing domain and quality of service profile. + +## 5.4 IP addressing and routing for access to IM-subsystem services + +This clause deals with a UE accessing IM CN subsystem services via EPS or GPRS. + +A UE accessing IM CN Subsystem services requires an IP address that is logically part of the IM CN subsystem IP Addressing Domain. This is established using an appropriate PDP or EPS Bearer context. It is possible to connect to a P-GW/GGSN either in the VPLMN or the HPLMN. For routing efficiency this context may benefit from being connected through a P-GW/GGSN in the visited network. The connection between the UE and the IM CN subsystem (where the P-GW/GGSN is either in the Home or the Visited network) is shown below: + +![Diagram illustrating UE Accessing IM Subsystem Services with P-GW/GGSN in the Visited network via Visited Network IM subsystem.](a7c51c18111139f9aca2805114108565_img.jpg) + +The diagram shows a UE connected to a Visited Network. Inside the Visited Network, the UE is connected to an S-GW/SGSN, which is connected to a P-GW/GGSN. A thick orange line labeled 'PDP/Bearer Context' runs from the UE through the S-GW/SGSN to the P-GW/GGSN. From the P-GW/GGSN, a line labeled 'SGi/Gi' connects to the Visited Network IM Subsystem. A callout box with the text 'Virtual presence of UE in Visited IM subsystem (UE's IP-address is here)' points to this connection. The Visited Network IM Subsystem is connected to an Inter-Network IM Backbone via a BG (Border Gateway). The Inter-Network IM Backbone is connected to the Home Network IM Subsystem via another BG. The Home Network IM Subsystem is also connected to the Internet and Intranets. + +Diagram illustrating UE Accessing IM Subsystem Services with P-GW/GGSN in the Visited network via Visited Network IM subsystem. + +**Figure 5-5: UE Accessing IM Subsystem Services with P-GW/GGSN in the Visited network via Visited Network IM subsystem** + +![Figure 5-5a.1: UE Accessing IM Subsystem Services with P-GW/GGSN in the Visited network](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +This diagram illustrates a network architecture where a User Equipment (UE) is connected to a Visited Network. The UE is connected to an S-GW/SGSN within the Visited Network, which is part of a Bearer/PDP Context. The S-GW/SGSN is connected to a P-GW/GGSN, also located within the Visited Network. The P-GW/GGSN is connected to an Inter Network Backbone. From the backbone, a dashed line labeled 'SGi/Gi' points towards the Internet and Intranets. Another path from the backbone leads to a Border Gateway (BG), which is connected to another BG. This second BG is connected to the IM CN SUBSYSTEM within the Home Network. A label 'Virtual presence of UE in Home network IM subsystem' points to this connection. Another label 'UE's IP-address is here' points to the P-GW/GGSN in the Visited Network. + +Figure 5-5a.1: UE Accessing IM Subsystem Services with P-GW/GGSN in the Visited network + +**Figure 5-5a.1: UE Accessing IM Subsystem Services with P-GW/GGSN in the Visited network** + +![Figure 5-5a: UE Accessing IM CN subsystem Services with P-GW/GGSN in the Home network](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +This diagram illustrates a network architecture where a User Equipment (UE) is connected to a Visited Network. The UE is connected to an S-GW/SGSN within the Visited Network, which is part of a Bearer/PDP Context. The S-GW/SGSN is connected to a Border Gateway (BG) within the Visited Network. This BG is connected to an Inter-Network Backbone. From the backbone, a path leads to another BG, which is connected to a P-GW/GGSN within the Home Network. The P-GW/GGSN is connected to the IM CN SUBSYSTEM within the Home Network via a dashed line labeled 'SGi/Gi'. A label 'Virtual presence of UE in Home network IM subsystem (UE's IP-address is here)' points to the connection between the P-GW/GGSN and the IM CN SUBSYSTEM. The P-GW/GGSN is also connected to the Internet and Intranets. + +Figure 5-5a: UE Accessing IM CN subsystem Services with P-GW/GGSN in the Home network + +**Figure 5-5a: UE Accessing IM CN subsystem Services with P-GW/GGSN in the Home network** + +The ability of the User plane and the Control Plane for a single IMS session being able to pass through different P-GWs/GGSNs is not defined in this release. + +## 5.5 Simultaneous access to multiple services + +A UE can have multiple services active simultaneously. When the services are part of different IP addressing domains, separate EPS Bearer or PDP contexts and IP addresses are required. The UE shall support multiple IP addresses when simultaneous EPS Bearer or PDP contexts are activated that require separate IP addresses for different addressing domains. + +Figure 5-6 shows an example of a connection between a UE and an Internet/Intranet service that is not available in the Visited Network with a simultaneous connection to the Visited Network's IM Subsystem. In this example, there may be two IPv6 addresses allocated, or one IPv4 address allocated for internet/Intranet access and one IPv6 address for IM subsystem access. + +![Diagram illustrating UE Accessing Home Internet/Intranet Services and Visited Network IM CN Subsystem Services. The diagram shows a User Equipment (UE) connected to a Visited Network (S-GW/SGSN, P-GW/GGSN) and a Home Network (S-GW/SGSN, P-GW/GGSN). The UE is connected to the Visited Network's S-GW/SGSN, which is connected to the Home Network's S-GW/SGSN via an S8/Gp interface. The Home Network's S-GW/SGSN is connected to the Home Network's P-GW/GGSN via a BG (PDN Gateway). The Home Network's P-GW/GGSN is connected to the Internet/Intranet via an SGi/Gi interface. The Visited Network's P-GW/GGSN is connected to the Visited Network's IM Subsystem via an S8/Gp interface. The UE is shown with two Bearer/PDP Contexts: one connecting to the Home Network's P-GW/GGSN and another connecting to the Visited Network's P-GW/GGSN.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Diagram illustrating UE Accessing Home Internet/Intranet Services and Visited Network IM CN Subsystem Services. The diagram shows a User Equipment (UE) connected to a Visited Network (S-GW/SGSN, P-GW/GGSN) and a Home Network (S-GW/SGSN, P-GW/GGSN). The UE is connected to the Visited Network's S-GW/SGSN, which is connected to the Home Network's S-GW/SGSN via an S8/Gp interface. The Home Network's S-GW/SGSN is connected to the Home Network's P-GW/GGSN via a BG (PDN Gateway). The Home Network's P-GW/GGSN is connected to the Internet/Intranet via an SGi/Gi interface. The Visited Network's P-GW/GGSN is connected to the Visited Network's IM Subsystem via an S8/Gp interface. The UE is shown with two Bearer/PDP Contexts: one connecting to the Home Network's P-GW/GGSN and another connecting to the Visited Network's P-GW/GGSN. + +**Figure 5-6: UE Accessing Home Internet/Intranet Services and Visited Network IM CN Subsystem Services** + +## 5.6 UE support of IPv6 + +The set of IPv6 functionality a 3GPP UE will require is dependent on the services (IMS, Packet Streaming etc.) it will use. + +As a minimum, a 3GPP UE shall comply with the Basic IP group of specifications as defined in RFC 3316 [21]. This IPv6 functionality is sufficient to provide compatibility towards IPv6 entities external to 3GPP. The 3GPP UE should support RFC 4941 [17a] and it should use RFC 4941 when choosing an interface identifier to generate the full IPv6 address for the initial generation process. + +A 3GPP UE shall follow the recommendations for the IP Security set of functions in RFC 3316 [21] when a specific service requires such functions. + +According to the procedures defined in TS 23.060 [2] and in TS 23.401 [27], when a UE is assigned an IPv6 prefix, it can change the global IPv6 address it is currently using via the mechanism defined in RFC 4941 [17a], or similar means, without updating the PS domain. Any application that requires full IP address knowledge shall provide a mechanism to get the latest IPv6 address when the IPv6 address in the UE has been changed. An example of such means is defined in TS 23.228 [11]. + +NOTE 1: RFC 3316 [21] does not make any recommendations on preferred transition and interoperability mechanisms between IPv4 and IPv6. + +NOTE 2: An application may inhibit the use of RFC 4941 mechanisms for privacy but the mechanism to do this is not specified. + +## 5.7 IP addressing and routing for server/application + +This clause deals with IP addressing for the UEs for communication between UEs and specific servers/applications (e.g. for servers/applications for MTC). + +![Diagram illustrating UE accessing server/application outside of the PLMN. A UE with an application (e.g., MTC) is connected via a PDP/PDN Connection to a P-GW/GGSN within a PLMN. The P-GW/GGSN is connected to an external network (Internet / Intranet) via an SGi/Gi interface. A Server / Application is connected to the external network. A callout box indicates that the UE's IP address is assigned at the P-GW/GGSN.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +The diagram shows a UE with an application (e.g., MTC) connected to a P-GW/GGSN within a PLMN. The P-GW/GGSN is connected to an external network (Internet / Intranet) via an SGi/Gi interface. A Server / Application is connected to the external network. A callout box indicates that the UE's IP address is assigned at the P-GW/GGSN. + +Diagram illustrating UE accessing server/application outside of the PLMN. A UE with an application (e.g., MTC) is connected via a PDP/PDN Connection to a P-GW/GGSN within a PLMN. The P-GW/GGSN is connected to an external network (Internet / Intranet) via an SGi/Gi interface. A Server / Application is connected to the external network. A callout box indicates that the UE's IP address is assigned at the P-GW/GGSN. + +**Figure 5.7-1: UE accessing server/application outside of the PLMN** + +UEs accessing services in either the Internet, or an external Intranet, or a combination of these service domains within the same IP network, require IP addresses that are routable between the P-GW/GGSN and the Server/Application. The mechanism for IP addressing scheme used for GPRS and EPS is described in TS 29.061 [37]. + +# 6 Mobility management + +## 6.1 Introduction + +From a Mobility Management point of view, the CN encompasses two domains, a CS domain and a PS domain. The UTRAN and the GERAN can be connected either to both these CN domains or to one of the CN domains. The E-UTRAN connects with the PS domain only. + +A single RRC connection (between RAN and UE) shall carry all user plane and signalling flows to/from a UE. This is regardless of where in the CN they originate/terminate. + +The 3GPP specifications for UTRAN and GSM in Iu mode shall support compatibility with GSM networks in A/Gb mode from the point of view of roaming and handover. The 3GPP specifications for EPS support compatibility with GSM networks and with UMTS from the point of view of roaming and handover. For the LM/MM functionality point of view this implies among other things the following: + +- IMSI shall be used as the common user identity in the two CN domains; +- common MAP signalling is applied to networks supporting either Iu or A/Gb mode or both. +- radio network parameters and radio resource management should be isolated in the RAN. + +The LM/MM techniques used should minimise radio resource usage of the RAN. + +## 6.2 Location management and mobility management concept overview + +### 6.2.1 Non-combined procedures + +From a LM/MM point of view, the CN consists of two domains, a CS domain and a PS domain or one of these domains. + +Each domain has its own service state machine. An UE, that is supporting both CS services and PS services, has a CS service state machine and a PS service state machine. The two peers of the service state machine are working independently to each other, although associated to the same UE. The UE-CN signalling aims to keep the peer entities synchronised. + +As an introduction, figure 6.1 gives an overview of the UE registration and connection principles for the CN consisting of two separate PS and CS service nodes. + +![Figure 6.1: Overview of the UE registration and connection principles. The diagram shows the interaction between the HSS, CS service domain (MSC/VLR), PS service domain (MME/SGSN), RAN, and UE. The HSS contains 'CS location' and 'PS location' and is labeled 'Common subscription data base' and 'Two CN service domains'. The CS service domain contains 'CS state' and the PS service domain contains 'PS state'. The RAN is labeled 'GERAN/UTRAN with distribution functionality' and 'E-UTRAN is PS only'. The UE contains 'CS state' and 'PS state'. Arrows indicate 'Two signaling connections in case of UTRAN/GERAN' between the RAN and both the MSC/VLR and MME/SGSN, and 'One RRC connection' between the RAN and the UE.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Figure 6.1: Overview of the UE registration and connection principles. The diagram shows the interaction between the HSS, CS service domain (MSC/VLR), PS service domain (MME/SGSN), RAN, and UE. The HSS contains 'CS location' and 'PS location' and is labeled 'Common subscription data base' and 'Two CN service domains'. The CS service domain contains 'CS state' and the PS service domain contains 'PS state'. The RAN is labeled 'GERAN/UTRAN with distribution functionality' and 'E-UTRAN is PS only'. The UE contains 'CS state' and 'PS state'. Arrows indicate 'Two signaling connections in case of UTRAN/GERAN' between the RAN and both the MSC/VLR and MME/SGSN, and 'One RRC connection' between the RAN and the UE. + +**Figure 6.1: Overview of the UE registration and connection principles** + +The CN consists of both a CS domain with MSC/VLR, 3G\_MSC/VLR, as the main serving node and an PS domain with SGSN/GGSN, 3G\_SGSN, 3G\_GGSN, MME, S-GW and P-GW as the main serving nodes. + +The main PS service states are PS-DETACHED, PS-IDLE and PS-CONNECTED. The main CS service states are CS-DETACHED, CS-IDLE and CS-CONNECTED. For the respective domain there are specific related MM system information controlling the MM functionality of the UE. + +When the UE is attached to PS it may be registered with SGSN and MME in parallel. + +The aim of the RAN is to offer one unified set of radio bearers which can be used for bursty packet traffic and for traditional telephony traffic. Therefore, only one logical control channel structure is used for all kind of traffic. The radio resource handling is RAN internal functionality and the CN does not define the type of radio resource allocated. + +The UTRAN and the E-UTRAN Radio Resource Control (RRC) has two modes, RRC Connected mode and RRC Idle mode. The RRC mode describes which identity is used to identify the UE. In RRC Idle mode the UE is identified by a CN associated identity. In RRC Connected mode the UE is assigned a Radio Network Temporary Identity to be used as UE identity on common transport channels. When the UE is allocated dedicated UTRAN transport channels, it uses the inherent addressing provided by these transport channels. + +In PS-CONNECTED state the UE is in RRC Connected mode. In CS-CONNECTED state the UE is in RRC Connected mode. + +For the mobility functionality, different area concepts are used. Tracking Areas (TAs), Location Areas (LAs) and Routing Areas (RAs) are used in the CN. UTRAN Registration Areas and Cell Areas are used in the Iu based RAN. LAs are related to CS services. TAs and RAs are related to PS services. + +When "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" is not used, one LA is handled by one CN node. With "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" one LA may be handled by multiple CN + +nodes. For an UE that is registered in a LA, this implies that the UE is registered in the specific CN node handling this specific LA. + +When "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" is not used, one RA is handled by one CN node. With "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" one RA may be handled by multiple CN nodes. One TA may be handled by multiple CN nodes. For an UE that is registered in a TA or RA, this implies that the UE is registered in the specific CN node handling this specific TA or RA. + +LA is used by the 3G\_MSC/VLR for paging the UE. RA is used by the SGSN for paging the UE. TA is used by the MME for paging the UE. UTRAN Registration Areas and Cell Areas are only visible in the UTRAN and used in RRC-Connected mode. The relations between LA, TA and RA are described in clause 4.3.2. + +In RRC Idle mode it is the broadcast MM system information (e.g. information about the present LA, present TA or present RA) that determines when the UE initiates a location registration procedure towards the CN. An UE crossing an LA border, in state CS-IDLE and RRC Idle mode, shall initiate LA update towards the MSC. An UE crossing an RA border, in state PS-IDLE and RRC Idle mode, shall initiate RA update towards the SGSN. An UE crossing a TA border to a TA that is not registered with the MME, in state ECM Idle or ECM Connected, shall initiate TA update towards the MME. + +In UTRAN RRC Connected mode, the UE receives the MM system information on the established RRC connection. (i.e. the broadcast MM system information is not used by the UE in the UTRAN RRC connected mode). In E-UTRAN RRC Connected mode, the UE receives the broadcast MM system information and uses it. An UE receiving information indicating a new LA, in state CS-IDLE and RRC Connected mode, shall initiate LA update towards the MSC. An UE receiving information indicating a new RA, in state PS-IDLE and RRC Connected mode, shall initiate RA update towards the SGSN. An UE receiving information indicating a new TA that is not registered with the MME shall initiate TA update towards the MME. An UE in state CS-CONNECTED and RRC Connected mode, shall not initiate LA update towards the CN. + +In CS-DETACHED mode the UE shall not initiate any LA update and this independent of the RRC mode. In PS-DETACHED mode the UE shall not initiate any TA or RA updates and this independent of the RRC mode. + +In addition to normal location registration when changing registration area, the UE may (network options) perform CS periodic registration when in CS-IDLE state and PS periodic registration when in PS-IDLE state. The respective periodic registration may be on/off on LA respective TA or RA level. + +On the MM level, IMSI and CS related TMSI are used as UE identities in the CS domain, and IMSI and PS related TMSI are used as UE identities in the PS domain. The IMSI is the common UE identity for the two CN domains (CS and PS). + +A signalling connection between the UE and the CN refers to a logical connection consisting of an RRC connection between UE and RAN and an Iu or S1 signalling connection between the RAN and the CN node. The CS domain related signalling between RAN and CN applies to UTRAN only. The CS domain related signalling and PS domain related signalling uses one common RRC connection and two Iu signalling connections ("two RANAP instances"), i.e. one Iu signalling connection for the CS domain and one Iu signalling connection for the PS domain. + +### 6.2.2 Use of combined procedures + +The use of separated PS and CS mobility mechanisms within the UE and within the CN can lead to non-optimal usage of the radio resource (for example a UE in PS idle and CS idle state would perform both LA updates (for the CS mechanism) and TA or RA updates (for PS mechanisms)). + +To offer flexibility in the provision of MM , combined mechanisms can be used for LM purposes as well as for attach/detach status purposes. + +A UE can perform combined update mechanisms. A CN should allow combined update operations (operator option). UEs should support the use of both combined and separate mechanisms. + +NOTE: The support of this feature by all UEs will also ease evolution of MM in the future. + +The RAN does not co-ordinate MM procedures that are logically between the CN and the MS. This includes: LM, authentication, temporary identity management and equipment identity check. + +## 6.3 Description of the location management and mobility management concept - area concepts + +### 6.3.1 Introduction + +For the mobility functionality five different area concepts are used. LA and RA in the CN as well as UTRAN Registration Area, GERAN Registration Area and Cell areas in the RAN. + +### 6.3.2 Location areas + +For CS services, the CN uses LA. LA is used e.g. at CN initiated paging related to CS services. A CS service related temporary identity, CS-TMSI, may be allocated to the UE. This temporary identity is then unique within a LA. + +### 6.3.3 Tracking and Routing areas + +For PS services, the CN uses TA or RA. TA or RA is used e.g. at CN initiated paging related to PS services. A PS service related temporary identity, P-TMSI or S-TMSI, may be allocated to the UE. The P-TMSI is then unique within an RA. The S-TMSI is then unique within one or multiple TAs. + +### 6.3.3a Support of Iu and A/Gb mode of operation in GERAN Cells + +#### 6.3.3a.1 Overview + +A GERAN capable cell may belong to the same LA/RA for both modes of operation (figure 6.2a). In the case of a combined CN node supporting both Iu and A/Gb mode MSs, a single LA/RA identity for MSs in either mode shall be broadcasted in the cell since the same LAI and RAI will be used in both modes of operation. + +![Diagram of a combined Iu/A/Gb cell with combined CN nodes. At the top, a box labeled 'CN' contains 'SGSN' and 'MSC'. Below it, a box labeled 'BSC' is connected via 'A/Gb' and 'Iu' interfaces. Below the BSC is a box labeled 'BTS'. At the bottom, an oval labeled 'LA/RA' contains three hexagonal shapes: 'A/Gb GSM', 'A/Gb/Iu GERAN' (shaded), and 'UTRAN'. A line connects the BTS to the 'A/Gb/Iu GERAN' hexagon.](c0e369274e53b2e5364666be6f786c7a_img.jpg) + +Diagram of a combined Iu/A/Gb cell with combined CN nodes. At the top, a box labeled 'CN' contains 'SGSN' and 'MSC'. Below it, a box labeled 'BSC' is connected via 'A/Gb' and 'Iu' interfaces. Below the BSC is a box labeled 'BTS'. At the bottom, an oval labeled 'LA/RA' contains three hexagonal shapes: 'A/Gb GSM', 'A/Gb/Iu GERAN' (shaded), and 'UTRAN'. A line connects the BTS to the 'A/Gb/Iu GERAN' hexagon. + +**Figure 6.2a: Combined Iu/A/Gb Cell with Combined CN nodes** + +It is also possible for GERAN capable cell to support both A/Gb and Iu mode of operation without any restriction on combined CN nodes (figure 6.2b). In order to support this GERAN capable cells need to support the possibility to broadcast both LA/RA identities for MSs in Iu mode and for MSs in A/Gb mode. The existing LAI/RAI will be used for mobiles operating in A/Gb mode while the LAI/RAI for Iu mode will be used for mobiles operating in Iu mode. The reason for this is that the LA and RA cannot in this case overlap the both CNs. + +![Diagram of a Combined A/Gb/Iu Cell. At the top, two CN (Core Network) blocks are shown, each containing an MSC (Mobile Switching Center) and an SGSN (Serving GPRS Support Node). The left CN is connected to a BSC (Base Station Controller) via an A/Gb interface. The right CN is connected to the same BSC via an Iu interface. The BSC is connected to a BTS (Base Transceiver Station). Below the BTS, a large oval represents the radio coverage area, which is divided into three regions: 'A/Gb LA/RA' on the left containing a 'GSM' hexagon, 'Iu LA/RA' on the right containing a 'UTRAN' hexagon, and a central shaded area labeled 'A/Gb/Iu GERAN'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Diagram of a Combined A/Gb/Iu Cell. At the top, two CN (Core Network) blocks are shown, each containing an MSC (Mobile Switching Center) and an SGSN (Serving GPRS Support Node). The left CN is connected to a BSC (Base Station Controller) via an A/Gb interface. The right CN is connected to the same BSC via an Iu interface. The BSC is connected to a BTS (Base Transceiver Station). Below the BTS, a large oval represents the radio coverage area, which is divided into three regions: 'A/Gb LA/RA' on the left containing a 'GSM' hexagon, 'Iu LA/RA' on the right containing a 'UTRAN' hexagon, and a central shaded area labeled 'A/Gb/Iu GERAN'. + +**Figure 6.2b: Combined A/Gb/Iu Cell** + +#### 6.3.3a.2 Interface selection in GERAN Cells + +The MS shall be able to derive the mode supported in cell from the information broadcasted. + +The support of different modes of operation in the MS shall be indicated in the MS Classmark and/or the MS Radio Access Capabilities. + +##### 6.3.3a.2.1 Basic principles for MS controlled Cell/Mode selection/re-selection + +The procedures for MS controlled cell selection/re-selection are done according to UMTS/GSM principles and procedures outlined in TS 25.304 [19] and TS 45.008 [20]. This means that a GERAN cell will be selected regardless which mode it supports. The cell selection is based on radio criteria and not service. + +If a GERAN cell is selected and it is both Iu and A/Gb capable, an Iu and A/Gb capable mobile station shall select Iu mode of operation by default. + +**NOTE:** The above text outlines the default mechanism of mode of operation selection and does not prohibit the introduction of a more flexible solution, which avoids unnecessary mode of operation changes, at a later stage + +##### 6.3.3a.2.2 Basic principles for network controlled Mode selection/re-selection + +The procedures for network-controlled cell selection/re-selection are done according to UMTS/GSM principles. When a cell/mode change is ordered by the network, the mode of operation to apply will be indicated by the network. + +### 6.3.4 RAN internal areas + +RAN internal areas are used by the UTRAN when the terminal is in RRC-Connected mode (see clause 6.7). The areas are used at e.g. RAN initiated paging. RAN internal area updating is a radio network procedure and the RAN internal area structure should not be visible outside the RAN. In RRC connected mode, the UE position is known on cell level or on URA/GRA level. RNTI is used as a temporary UE identifier used within the RAN and allocated at RRC connection establishment. + +### 6.3.5 Relationship between the different areas + +The following area relations exist (see figure 6.3): + +- there need not be any relation between URA/GRA and LA respectively between URA/GRA and RA. The URA concept is defined in TS 25.331 [5] and the GRA concept is defined in TS 43.051 [12]; +- one RA consists of a number of cells belonging to RNCs that are connected to the same CN node; +- one LA consists of a number of cells belonging to RNCs that are connected to the same CN node; +- one TA consists of a number of cells belonging to eNodeBs that are connected to the same CN node; +- one RA is handled by only one CN serving node, i.e. one combined MSC+SGSN or one 3G\_SGSN, unless "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" is used; +- one LA is handled by only one CN serving node, i.e. one combined MSC + SGSN or one 3G\_MSC/VLR, unless "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" is used. + +There is no relation between TAs and LA/RAs. However, related configurations may be useful for certain services, e.g. for CS Fallback. + +The GSM defined relations between LA and RA applies i.e. the following relations between LA and RA are possible: + +- RA and LA is equal; +- one RA is a subset of one, and only one, LA, meaning that a RA do not span more than one LA. + +The mapping between one LA and RNCs is handled within the MSC/VLR owning this LA. The mapping between one RA and RNCs is handled within the SGSN owning this RA. The mapping between LA and cells respective between RA and cells is handled within RNC. + +![Diagram showing the relationship between LA, RA, URA/GRA, and Cells. Top row shows three large ovals for LA1, LA2, and LA3. Inside LA1 are RA1 and RA2. Inside LA2 is RA3. Inside LA3 are RA4 and RA5. Small green ovals representing cells are distributed across the RAs. Below this, three large ovals represent URA/GRA1, URA/GRA2, and URA/GRA3, which overlap and contain cells. A legend at the bottom defines the shapes and arrow types.](f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg) + +**Legend:** + +LA    URA/GRA    RA    Cell + +◀-- -- -- --▶ RA(s) handled by one + +◀————▶ LA(s) handled by one + +◀-- · -- · --▶ LA(s) and RA(s) handled by one + +**The URA/GRAs does not need to have a one to one relation to the RNC/BSS or any CN nodes like the LA/RA.** + +Diagram showing the relationship between LA, RA, URA/GRA, and Cells. Top row shows three large ovals for LA1, LA2, and LA3. Inside LA1 are RA1 and RA2. Inside LA2 is RA3. Inside LA3 are RA4 and RA5. Small green ovals representing cells are distributed across the RAs. Below this, three large ovals represent URA/GRA1, URA/GRA2, and URA/GRA3, which overlap and contain cells. A legend at the bottom defines the shapes and arrow types. + +**Figure 6.3: Relationship between different areas** + +### 6.3.5a Restriction of subscribers' access + +Operators shall be able to restrict their subscriber's access between E-UTRAN, GERAN and UTRAN radio access, via administrative procedures based on subscription information. + +In order for the restriction to apply, the network cells shall be organized so that each LA and RA contains either UTRAN or GERAN cells only. TAs apply to E-UTRAN only. Based on the subscription information and the LA/RA/TA information available in the VLR/SGSN/MME, subscriber's access may be rejected during LA/RA/TA update procedure. + +NOTE: In order for this feature to work, both serving and home network operators need to have configured the feature. + +![Figure 6.3a: Example scenario between different areas for restriction. The diagram shows two rows of network areas. The top row consists of three Location Areas (LA1, LA2, LA3) represented by shaded ovals. LA1 contains two Radio Areas (RA1, RA2) represented by orange ovals. LA2 contains RA3 (orange oval). LA3 contains RA4 and RA5 (orange ovals). The bottom row consists of three UTRAN/RAN areas (URA1, GRA1, GRA2) represented by white ovals. Each of these areas contains a row of green ovals representing cells. A legend at the bottom identifies the shapes: a shaded oval for LA, a white oval for URA/ GRA, an orange oval for RA, and a green oval for Cell.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +Figure 6.3a: Example scenario between different areas for restriction. The diagram shows two rows of network areas. The top row consists of three Location Areas (LA1, LA2, LA3) represented by shaded ovals. LA1 contains two Radio Areas (RA1, RA2) represented by orange ovals. LA2 contains RA3 (orange oval). LA3 contains RA4 and RA5 (orange ovals). The bottom row consists of three UTRAN/RAN areas (URA1, GRA1, GRA2) represented by white ovals. Each of these areas contains a row of green ovals representing cells. A legend at the bottom identifies the shapes: a shaded oval for LA, a white oval for URA/ GRA, an orange oval for RA, and a green oval for Cell. + +**Access restriction can be applied for the above scenario** + +**Figure 6.3a: Example scenario between different areas for restriction** + +The HSS/HLR shall provide the MSC/MSC server/VLR, SGSN and MME with the following information about the subscriber's GERAN and UTRAN access restriction set by the operator, as specified in TS 23.008 [24]: + +- GERAN not allowed. +- UTRAN not allowed. + +In addition, the HSS/HLR shall provide SGSN and MME with the following information about the subscriber's E-UTRAN access restriction set by the operator, as specified in TS 23.008 [24]: + +- E-UTRAN not allowed. + +If roaming restriction to specific RATs needs to be enforced, SGSN and MME may be configured with a list of HPLMN IDs that are not allowed to access that RAT. + +The UE shall be notified of the access restriction using the existing procedures for rejection of Location Update, Routing Area Update, Tracking Area Update and Attachment, as defined in TS 24.008 [25] and TS 24.301 [34] and the existing cause values for these procedures. + +### 6.3.6 Hierarchical tracking concept + +This concept applies to UTRAN access only. A packet UE (in RRC connected mode) is tracked at the cell level by RNC during an active connection. + +A packet UE (in RRC connected mode) is tracked at the URA level by RNC when no data are actively transfer, and the probability of data transfer is quite high. + +A packet UE (in PS-Idle state) is tracked at the RA level by SGSN when no data is actively transferred and the probability of data transfer is quite low. The network operator can optimise paging and updating load by controlling the size of the different areas and the probability of data transfer (controlled by the RRC\_connection\_release timer). For example, one operator can decide that URA/GRA are small, and that RRC connection are released after a relatively short time of inactivity, so that most attached packet UE are tracked in the RA level (optimum for packet UE mainly using client-server type of service). + +Another operator can decide that URA/GRA are large, and that RRC connection are released only if RRC connection is lost, so that most attached packet UE are tracked at the URA level. + +The procedure for the releasing of the RRC connection can be found in TS 23.060 [2] under the Iu release procedure. The URA update procedures can be found in TS 25.331 [5] and GRA update procedures can be found in TS 43.051 [12]. + +## 6.4 Relationship between MM and SM states for an UE + +When a UE is attached to PS service, it may have, but need not have, some EPS Bearer/PDP context established with GERAN or UTRAN Access. With E-UTRAN access a PS attached UE has at least one EPS Bearer context established. + +If the UE has no EPS Bearer/PDP context established (SM-Inactive), no radio access bearer are established for PS service. The UE is in RRC connected mode, only if the state is CS-CONNECTED state or PS-CONNECTED state (i.e. only a PS signalling connection is established). + +If the UE has at least one EPS Bearer/PDP context established (SM-Active), the UE can be in PS-CONNECTED state or in PS-IDLE state. + +**NOTE:** The EPS Bearer/PDP context status is not modified by the release of the RRC connection, except if the release of the connection is due to an RRC failure which do not permit to maintain the negotiated QoS (e.g. a real time connection). + +## 6.5 Requirement in case of temporarily loss of coverage of packet UE + +A packet attached UE using non-real time bearer shall not lose its EPS Bearer/PDP context in case of temporarily loss of coverage. Within the network, it shall be possible to use timers to detect when a UE has been out of coverage for a long period of time and, dependent upon operator policy, to then remove unused EPS Bearer/PDP context(s). + +## 6.6 MM functionality in different UE service states + +CS service states and related MM functionality: + +- CS-DETACHED: The UE is not reachable by the network for CS services. The UE does not initiate LA updates at LA changes and no periodic CS service updates; +- CS-IDLE: The UE is reachable by paging for CS services. The UE initiates LA updates at LA changes. The UE may initiate periodic CS service updates and this depends on the CS periodic update state of the present LA; +- CS-CONNECTED: The UE has a signalling connection for CS services established between the UE and the CN. The UE does not initiate LA update (even not when the present LA changes) and no periodic CS service updates. + +PS service states and related MM functionality: + +- PS-DETACHED: The UE is not reachable by the network for PS services. The UE does not initiate TA/RA updates at TA/RA changes and no periodic PS service updates; +- PS-IDLE: The UE is reachable by paging for PS services. The UE initiates TA/RA updates at TA/RA changes. The UE may initiate periodic PS service updates and this depends on the PS periodic update state of the present TA/RA; +- PS-CONNECTED: The UE has a signalling connection for PS services established between the UE and the CN. The UE initiates TA/RA update when RAI in MM system information changes. No periodic PS service updates. + +There can also be a NULL state. In the UE, this state corresponds to power off or possibly a "no SIM" condition. In the CN, the NULL state correspond to CS-DETACHED and PS-DETACHED. + +For each state transition there can be several events that triggers the transition. Some of them are described below. + +NOTE: Some of these can coincide, e.g. moving from CS-IDLE to CS-DETACHED and moving from PS-IDLE to PS-DETACHED. + +### **Moving from CS-IDLE to CS-CONNECTED:** + +The state transition from CS-IDLE to CS-CONNECTED is performed when a signalling connection is established between UE and CN for CS services. In GSM this state transition is triggered by the message CM\_SERVICE\_REQUEST or PAGE\_RESPONSE. + +### **Moving from CS-CONNECTED to CS-IDLE:** + +The state transition from CS-CONNECTED to CS-IDLE is performed when the signalling connection for CS services is released, e.g. at call release and no other CS service is ongoing. A radio link failure can also trigger this state transition. + +### **Moving from CS-IDLE to CS-DETACHED:** + +The transition from CS-IDLE to CS-DETACHED can be triggered by some action from the user of the UE but an expiring timer in the network could also trigger it. The UE is marked as CS\_DETACHED in the CN and then as a consequence no CS service establishment is possible. + +### **Moving from PS-IDLE to PS-CONNECTED:** + +The state transition from PS-IDLE to PS-CONNECTED is performed when a signalling connection is established between UE and CN for PS services. + +### **Moving from PS-CONNECTED to PS-IDLE:** + +The state transition from PS-CONNECTED to PS-IDLE is performed when the signalling connection for PS services is released, e.g. at release of a PS service, no other PS service is ongoing and at release of the RRC connection in case of very low level of activity. A radio link failure can also trigger this state transition. + +### **Moving from PS-IDLE to PS-DETACHED:** + +The transition from PS-IDLE to PS-DETACHED can be triggered by some action from the user of the UE but an expiring timer in the network could also trigger it. The UE is marked as PS\_DETACHED in the CN and then as a consequence no PS service establishment is possible. + +## **6.7 The RRC state machine** + +The UTRAN RRC state machine is a description model of how the UE and the RAN co-operate regarding RRC functionality. The RRC state describes the state of the UE in the RAN. Here follows a brief description of the UTRAN RRC state machine, for more information see TS 25.301 [6] and TS 25.303 [7]. The E-UTRAN RRC state machine is described in TS 36.331 [29]. + +NOTE: RRC idle mode and RRC connected mode refer to the UE idle mode and UE connected mode respectively in TS 25.301 [6] and TS 25.303 [7]. + +The RRC state machine exists as peer entities, one in the UE and one in RAN. Apart from transient situations and error cases they are synchronised. Figure 6.4 illustrates the main modes/states of the RRC state machine. + +![Diagram of RRC modes and states. A large rounded rectangle labeled 'Connected mode' contains two oval states: 'Cell Connected' and 'URA Connected'. An arrow points from 'Cell Connected' to 'URA Connected' labeled 'Enter URA connected state'. Another arrow points from 'URA Connected' back to 'Cell Connected' labeled 'Enter cell connected state'. Below the 'Connected mode' box is a rectangular box labeled 'Idle mode'. An arrow points from 'Cell Connected' down to 'Idle mode' labeled 'RRC connection release'. Another arrow points from 'Idle mode' up to 'Cell Connected' labeled 'RRC connection establishment'.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +graph TD + subgraph Connected_mode [Connected mode] + CC([Cell Connected]) -- "Enter URA connected state" --> UC([URA Connected]) + UC -- "Enter cell connected state" --> CC + end + CC -- "RRC connection release" --> IM[Idle mode] + IM -- "RRC connection establishment" --> CC + +``` + +Diagram of RRC modes and states. A large rounded rectangle labeled 'Connected mode' contains two oval states: 'Cell Connected' and 'URA Connected'. An arrow points from 'Cell Connected' to 'URA Connected' labeled 'Enter URA connected state'. Another arrow points from 'URA Connected' back to 'Cell Connected' labeled 'Enter cell connected state'. Below the 'Connected mode' box is a rectangular box labeled 'Idle mode'. An arrow points from 'Cell Connected' down to 'Idle mode' labeled 'RRC connection release'. Another arrow points from 'Idle mode' up to 'Cell Connected' labeled 'RRC connection establishment'. + +**Figure 6.4: RRC modes, main RRC states and main mode/state transitions** + +### **RRC-Idle\_mode:** + +In the Idle mode there is no connection established between UE and RAN. There is no signalling between RAN and the UE except for system information that is sent from RAN down link on a Broadcast channel to the UE. The UE can also receive paging messages with a CN identity on the PCH. There is no information on the UE stored in RAN in this state. + +### **RRC-Connected\_mode:** + +In the Connected mode the main states are Cell Connected state and URA connected state. In this mode there is one RNC that is acting as Serving RNC (SRNC), and an RRC connection is established between the UE and this SRNC. + +- When the UE position is known on cell level, the UE is in the cell connected state. When in cell connected state, the RRC connection mobility is handled by handover procedures. +- When the UE position is known on URA level, the UE is in the URA connected state. The URA contains a set of cells. URA updating procedures provides the mobility functionality in this state. In URA connected state no dedicated radio resources are used. + +## **6.8 Relationship between CS and PS service states and RRC state for an UE** + +This clause describes the relationship for the UTRAN. In E-UTRAN the RRC operates for PS services only despite some extensions for supporting the provision of CS services via GERAN/UTRAN. + +During non-transient conditions the following relations are valid between service states and RRC modes for an UE: + +- when in either CS-CONNECTED state or PS-CONNECTED state, or in both CS-CONNECTED state and PS-CONNECTED state, then the UE is in RRC connected mode; +- when in neither CS-CONNECTED state nor PS-CONNECTED state, then the UE is in RRC idle mode. + +Figure 6.5 and figure 6.6 illustrate two examples on the relations between the UTRAN RRC states and CS/PS service states. + +![Figure 6.5: UE in CS-CONNECTED state and PS-IDLE state. The diagram shows a UE connected to an SRNC, which is connected to a 3G_MSC/VLR. The UE is in the CS-CONNECTED state (shaded oval) and the PS-IDLE state (shaded oval). The SRNC is in the RRC-CELL-CONNECTED state (dashed oval). The 3G_MSC/VLR is in the CS-CONNECTED state (shaded oval) and the PS-IDLE state (shaded oval). The 3G_SGSN is in the PS-IDLE state (shaded oval). The RNC is connected to the SRNC and the 3G_SGSN. A legend indicates that dashed ovals represent RRC states, light gray ovals represent CS states, and dark gray ovals represent PS states.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +Figure 6.5: UE in CS-CONNECTED state and PS-IDLE state. The diagram shows a UE connected to an SRNC, which is connected to a 3G\_MSC/VLR. The UE is in the CS-CONNECTED state (shaded oval) and the PS-IDLE state (shaded oval). The SRNC is in the RRC-CELL-CONNECTED state (dashed oval). The 3G\_MSC/VLR is in the CS-CONNECTED state (shaded oval) and the PS-IDLE state (shaded oval). The 3G\_SGSN is in the PS-IDLE state (shaded oval). The RNC is connected to the SRNC and the 3G\_SGSN. A legend indicates that dashed ovals represent RRC states, light gray ovals represent CS states, and dark gray ovals represent PS states. + +Figure 6.5: UE in CS-CONNECTED state and PS-IDLE state + +![Figure 6.6: UE in CS-IDLE state and PS-DETACHED state. The diagram shows a UE connected to an RNC, which is connected to a 3G_MSC/VLR. The UE is in the CS-IDLE state (light gray oval) and the PS-DETACHED state (dark gray oval). The RNC is in the RRC IDLE MODE state (dashed oval). The 3G_MSC/VLR is in the CS-IDLE state (light gray oval) and the PS-DETACHED state (dark gray oval). The 3G_SGSN is in the PS-DETACHED state (dark gray oval). Another RNC is connected to the first RNC and the 3G_SGSN. A legend indicates that dashed ovals represent RRC states, light gray ovals represent CS states, and dark gray ovals represent PS states.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +Figure 6.6: UE in CS-IDLE state and PS-DETACHED state. The diagram shows a UE connected to an RNC, which is connected to a 3G\_MSC/VLR. The UE is in the CS-IDLE state (light gray oval) and the PS-DETACHED state (dark gray oval). The RNC is in the RRC IDLE MODE state (dashed oval). The 3G\_MSC/VLR is in the CS-IDLE state (light gray oval) and the PS-DETACHED state (dark gray oval). The 3G\_SGSN is in the PS-DETACHED state (dark gray oval). Another RNC is connected to the first RNC and the 3G\_SGSN. A legend indicates that dashed ovals represent RRC states, light gray ovals represent CS states, and dark gray ovals represent PS states. + +Figure 6.6: UE in CS-IDLE state and PS-DETACHED state + +## 6.9 Service registration and location update + +### 6.9.1 Introduction + +Service registration (attach) in the respective CN domain is done initially (after UE being detached due to e.g. power off). When a registration area is changed a location update is performed. In addition, periodic registration can be performed. Here follows descriptions of when the respective CN registration area is changed. + +NOTE: It is not here defined which different registration procedures that are needed. + +### 6.9.2 Location area update + +LA update is initiated by the UE to inform the CS domain of the CN that the UE has entered a new LA. In case the new LA is in an area served by another CN node, the LA update also triggers the registration of the subscriber in the new CN node and a location update for CS services towards the HLR/HSS. + +LA update is only initiated by the UE when the UE is in state CS-IDLE, and this independently of the PS state. If the UE is CS-IDLE but RRC connected, which means that the UE is in PS-CONNECTED state, LA update is initiated by the UE when it receives information indicating a new LA. + +### 6.9.3 Tracking and Routing area update + +TA/RA update is initiated by the UE to inform the PS domain of the CN that the UE has entered a new TA/RA. In case the new TA/RA is in an area served by another CN node, the TA/RA update also triggers the registration of the subscriber in the new CN node and a location update for PS services towards the HSS. + +TA/RA update is initiated by the UE when the UE is in state PS-IDLE, and this independently of the CS state. If the UE is PS-IDLE but UTRAN RRC connected, which means that the UE is in CS-CONNECTED state, RA update is initiated by the UE when it receives information indicating a new RA. + +When the UE is in PS-CONNECTED state the UE initiates TA/RA update when TAI/RAI in MM system information changes. + +### 6.9.4 Combined updates + +The GSM radio interface combined procedures and their support via the Gs interface is the starting point for the support of combined updates. With E-UTRAN access combined update procedures may be used by MME and MSC. + +## 6.10 Paging initiated by CN + +A CN node requests paging only for UE in CS-IDLE state or PS IDLE state. Paging from a CN node is done independent of the service state of the UE in the other CN domain type. + +CS and PS paging is co-ordinated within the UTRAN. Details on how the co-ordination is achieved and the parameters to be provided by the CN are specified in TS 25.413 [9]. The procedures required between the UTRAN and UE are in TS 25.331 [5]. + +## 6.11 Signalling connection establishment + +A signalling connection between the UE and a CN node refers here to a logical connection consisting of an RRC connection between UE and the RAN and an S1 or Iu signalling connection between the RAN and the CN node. The signalling connection is used for transfer of higher layer (MM, CM) information between the UE and the CN node. + +At a service request to one of the CN domain types and when no such connection exists towards the applicable CN domain type, the UE shall request establishment of a new signalling connection. + +If no RRC connection exists, this is established in conjunction with (before) the transfer of the signalling establishment request. At the RRC connection establishment, an UE context is built up in the SRNC. + +If an RRC connection is already established, the UE shall send the signalling establishment request using that RRC connection. + +At reception of the signalling establishment request, the RAN will establish an S1 or Iu connection towards the CN node indicated by the CN service domain type received from UE. + +## 6.11a CS Domain Signalling Requirements (in particular relating to handover) + +Correct operation of the Call Control, Mobility Management and Call Independent Supplementary Service protocols requires that downlink messages from the MSC shall be delivered in the correct order and shall not be lost, duplicated or delivered in error. + +The RAN and Iu/A interfaces shall provide this functionality in all cases except for when the Iu/A interface SCCP connection is being changed, e.g. at SRNS relocation or inter-BSC (external) handover. + +When the SCCP connection is being changed, the MSC shall buffer downlink CC, MM and CISS messages. Specifically, the MSC shall buffer messages from these protocols after transmission of a (BSSMAP) Handover Command or RANAP-Relocation Command message and until receipt of a Handover Complete, Relocation Complete, Handover Failure or Relocation Cancel message. + +In the uplink, the UE is responsible for delivering the CS domain messages across the radio interface. Once the message has been received by part of the network, it is the network's responsibility to deliver the message to the MSC. This can result in duplicate message delivery to the CN. The RAN shall ensure that the protocol used between UE and RAN permits any duplicate messages that are delivered to the CN, to be correctly discarded by N(SD) mechanism specified in TS 24.007 [22] for the uplink CC, MM and CISS messages. + +## 6.12 Relations between SRNS relocation and location registration + +This clause clarifies the need for separate handling of MM registration area (LA and RA) information in RRC idle mode respective in RRC connected mode. The following example illustrates relations between SRNC relocation, registration area (LA/RA) change and LA/RA updates. As shown in the example, this is equally applicable for a combined MSC + SGSN as well as the 3G-MSC/VLR and 3G-SGSN. + +NOTE 1: The example is based on the assumptions that one RNC can set up Iu connections to only one 3G\_MSC/VLR (or combined MSC+SGSN) and only one 3G\_SGSN (or combined MSC+ SGSN), and that the CN node is configured to only send page to the RNC(s) that is controlling cells within the relevant LA/RA. + +Preconditions (see figure 6.7): + +- LA1 is handled by 3G\_MSC/VLR1 and LA2 is handled by 3G\_MSC/VLR2 ; +- RA1 is handled by 3G\_SGSN1 and RA2 is handled by 3G\_SGSN2 ; +- UE is registered in LA1 in 3G\_MSC/VLR1 and in RA1 in 3G\_SGSN1; +- the UE is in PS-CONNECTED state and a signalling connection exists between UE and 3G\_SGSN1; +- the UE is in CS-IDLE state and no signalling connection exists between UE and 3G\_MSC/VLR1; +- RNC1 is acting as SRNC and RNC2 is acting as DRNC; +- UE is in RRC cell connected state and with dedicated channels established to cells within both RNC1 and RNC2. UE does not listen to the PCH; +- the registration area information sent to the UE indicates LA1 and RA1. + +The UE can always (at least in normal working states) identify the present available registration area (LA respective RA) associated with the respective CN domain. The determination of the present area differs depending on the state of the UE. For UE in RRC idle mode (UE with no ongoing communication with the network) it is the cell selection mechanism in the UE that is used. For UE in RRC connected mode it is the RAN that determines the area (although a change can implicit be initiated by the UE). + +![Figure 6.7: Illustration of the preconditions in the described example. The diagram shows a network architecture with two RNCs (RNC1 and RNC2) connected to each other. RNC1 is connected to MSC1 and SGSN1, while RNC2 is connected to MSC2 and SGSN2. RNC1 is associated with LA1, RA1, and RNC2 is associated with LA2, RA2. A UE (User Equipment) is shown at the bottom, with arrows indicating movement from the coverage area of RNC1 towards RNC2.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +graph TD + subgraph LA1_RA1 [LA1, RA1] + RNC1((RNC1)) + C1_1(( )) + C1_2(( )) + C1_3(( )) + end + subgraph LA2_RA2 [LA2, RA2] + RNC2((RNC2)) + C2_1(( )) + C2_2(( )) + C2_3(( )) + C2_4(( )) + end + MSC1((MSC1)) + SGSN1((SGSN1)) + MSC2((MSC2)) + SGSN2((SGSN2)) + UE([UE]) + + RNC1 --- MSC1 + RNC1 --- SGSN1 + RNC2 --- MSC2 + RNC2 --- SGSN2 + RNC1 --- RNC2 + RNC1 --- C1_1 + RNC1 --- C1_2 + RNC1 --- C1_3 + RNC2 --- C2_1 + RNC2 --- C2_2 + RNC2 --- C2_3 + RNC2 --- C2_4 + UE --> RNC2 + +``` + +Figure 6.7: Illustration of the preconditions in the described example. The diagram shows a network architecture with two RNCs (RNC1 and RNC2) connected to each other. RNC1 is connected to MSC1 and SGSN1, while RNC2 is connected to MSC2 and SGSN2. RNC1 is associated with LA1, RA1, and RNC2 is associated with LA2, RA2. A UE (User Equipment) is shown at the bottom, with arrows indicating movement from the coverage area of RNC1 towards RNC2. + +**Figure 6.7: Illustration of the preconditions in the described example** + +In figure 6.7 MSC stands for 3G\_MSC/VLR and SGSN for 3G\_SGSN. + +The UE moves now further towards the right, leaving the coverage area of cells controlled by RNC1, and resulting in that the UE has dedicated channel(s) established to cell(s) within only RNC2. This can result in the following sequence of events: + +- the SRNC (RNC1) can decide to perform an SRNC relocation resulting in that the RNC2 becomes SRNC. In this example, the change of SRNC also implies a change of SGSN with an update of the UE location registration for the PS domain; +- after this SRNC relocation or combined with this procedure, the MM registration area information sent to the UE is changed and indicates now LA2 and RA2; + +NOTE 2: The MM registration area information need not be sent for every SRNS relocation, nor does it preclude MM registration area information being sent in other occasions. + +- the UE initiates a LA update, which results in a registration change from LA1 in 3G\_MSC/VLR1 to LA2 in 3G\_MSC/VLR2 and results in changed MM registration information. + +NOTE 3: The area information can not be changed to indicate LA2 unless SRNC relocation has been performed, because the LA update signalling is sent from the UE, by using the established RRC connection to SRNC, and then to the 3G\_MSC/VLR to which the SRNC belongs. + +## 6.13 Requirements on identifiers for UMTS and GSM + +- 1a) The format of the UMTS Location Area Identifier and UMTS TMSI shall not prevent a dual mode GSM-UMTS mobile which was last location updated over the GSM radio interface (i.e. has a GSM LAI and GSM TMSI), from performing a location update (or other signalling) over the UMTS radio interface to a UMTS MSC. + - 1b) The format of the UMTS Location Area Identifier and UMTS TMSI shall not prevent a dual mode GSM-UMTS mobile which was last location updated over the UMTS radio interface (i.e. has a UMTS LAI and UMTS TMSI), from performing a location update (or other signalling) over the GSM radio interface to a GSM MSC. + - 1c) The format of the UMTS Routing Area Identifier and UMTS P-TMSI shall not prevent a dual mode GSM-UMTS mobile which was last routing area updated over the GSM radio interface (i.e. has a GSM RAI and GSM P-TMSI), from performing a routing area update (or other signalling) over the UMTS radio interface to a UMTS SGSN. + - 1d) The format of the UMTS Routing Area Identifier and UMTS P-TMSI shall not prevent a dual mode GSM-UMTS mobile which was last routing area updated over the UMTS radio interface (i.e. has a UMTS RAI and UMTS P-TMSI), from performing a routing area update (or other signalling) over the GSM radio interface to a GSM SGSN. +- 2) The standard shall support means by which an operator can configure GSM and UMTS cells to be members of the same registration area (i.e. the mobile can receive paging from whichever cell it is camped on and does not need to location update (or routing update) just because the mobile has changed from a UMTS to a GSM cell). + +- 3a) The standard shall support means by which an operator can allocate GSM and UMTS LAIs which enable GSM MSCs to be able to contact UMTS MSCs and vice versa. +- 3b) The standard shall support means by which an operator can allocate GSM and UMTS RAIs which enable GSM SGSNs to be able to contact UMTS SGSNs and vice versa. +- 4) The standard shall support means by which an operator can ensure that the IMSI does not need to be sent over the radio interface when the mobile station moves from a GSM cell to a UMTS cell (and vice-versa). +- 5) The standard shall support means by which an operator can ensure that the IMSI does not need to be sent over the radio interface when a USIM is moved from a UMTS mobile station to a GSM mobile station (and vice-versa). +- 6) The standard need not support means by which an operator can ensure that the IMSI is not sent over the radio interface when a GSM SIM is moved from a GSM mobile station to a UMTS mobile station (and vice-versa). + +## 6.14 Use of MM system information + +In each cell the network broadcasts MM system information on the broadcast channel. . The "current MM system information" is used by the MM functionality in the UE respecting the rules for the UE service state of the respective MM state machine, see clause 6.6. The "current MM system information" is identified as follows: + +- In RRC idle mode, when the UE camps on one cell, it receives all MM system information valid for this cell on the broadcast channel of the cell. The received MM system information is then the "current MM system information"; +- In UTRAN RRC connected mode, the SRNS shall control the current MM system information valid for the UE. e.g. at SRNS relocation, the new SRNS may send applicable MM system information to the UE. The established RRC connection shall be used for transferring any new MM system information to the UE. The UE shall use any new MM system information received from the SRNC on the established RRC connection as the "current MM system information"; + +NOTE: The MM system information need not necessarily be sent for every SRNSs relocation, nor does it prelude MM system information being sent on other occasions. + +- In E-UTRAN RRC connected mode, the UE receives all MM system information valid for this cell on the broadcast channel of the cell. The received MM system information is then the "current MM system information"; +- At the RRC connection establishment, the UE uses the broadcasted MM system information of the cell where the establishment is made as the "current MM system information"; +- When the UE leaves the RRC connected mode and enters RRC idle mode, the UE uses the broadcasted MM system information of the chosen cell, which is determined by the UE idle mode cell selection/re-selection process that is then performed, as the "current MM system information". + +## 6.15 Signalling procedures + +### 6.15.1 Idle mode procedures + +The signalling procedures shown in the following clauses do not represent the complete set of possibilities, nor do they mandate this kind of operation. This document specifies a set of elementary procedures for each interface, which can be combined in different ways in an implementation. Therefore these sequences are merely examples of a typical implementation. By default the combined procedures as defined in TS 23.060 [2] or TS 23.272 [30] are also applicable when using Gs or SGs. + +The list of parameters should be regarded as examples of possible information carried by the messages and not as a complete list. + +#### 6.15.1.1 Location Area update + +Figure 6.8 shows location registration when changing LA including change of 3G-MSC/VLR and when the UE is in MM idle state towards the 3G\_MSC/VLR. + +The illustrated transfer of MM signalling to/from the UE uses an established RRC connection. This RRC connection can have been established beforehand due to ongoing interwork between UE and 3G-SGSN or be established only for this location registration procedure towards the 3G\_MSC/VLR. + +For each indicated MM message sent in this case to/from UE, the CN discriminator indicates 3G\_MSC/VLR. + +![Sequence diagram showing interface information transfer for location update when changing VLR area. Lifelines: UE, SRNS, New 3G_MSC/VLR, HLR, Old 3G_MSC/VLR. The sequence includes RRC connection establishment, LA Update Req., Send Identification Req./Ack., Security Functions, Update Location, Cancel Location/Ack., Insert Subscriber Data/Ack., Location Update Accept, TMSI reallocation, and RRC connection release.](5478f70a6cef3e5672b2b22d28830cfb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SRNS + participant New3G_MSC_VLR as New 3G_MSC/VLR + participant HLR + participant Old3G_MSC_VLR as Old 3G_MSC/VLR + + Note over UE, SRNS: 1. RRC connection establishment + UE->>New3G_MSC_VLR: 1. LA Update Req.(old LAI, old TMSI) + Note over SRNS: (Transfers message) + New3G_MSC_VLR->>Old3G_MSC_VLR: 2. Send Identification Req.(TMSI) + Old3G_MSC_VLR-->>New3G_MSC_VLR: 2. Send Identification Ack.(IMSI, triplets) + Note over UE, New3G_MSC_VLR: 3. Security Functions + New3G_MSC_VLR->>HLR: 4. Update Location + HLR->>Old3G_MSC_VLR: 5. Cancel Location + Old3G_MSC_VLR-->>HLR: 5. Cancel Location Ack + HLR->>New3G_MSC_VLR: 6. Insert Subscriber Data + New3G_MSC_VLR-->>HLR: 6. Insert SubscriberDataAck + HLR->>New3G_MSC_VLR: 7. Upd. Location Ack + New3G_MSC_VLR->>SRNS: 8. Location Update Accept (new LAI, new TMSI) + SRNS->>UE: 9. TMSI reallocation complete (new TMSI) + Note over UE, SRNS: 10. RRC connection release + SRNS->>New3G_MSC_VLR: 10. Release + +``` + +Sequence diagram showing interface information transfer for location update when changing VLR area. Lifelines: UE, SRNS, New 3G\_MSC/VLR, HLR, Old 3G\_MSC/VLR. The sequence includes RRC connection establishment, LA Update Req., Send Identification Req./Ack., Security Functions, Update Location, Cancel Location/Ack., Insert Subscriber Data/Ack., Location Update Accept, TMSI reallocation, and RRC connection release. + +**Figure 6.8: Interface information transfer for location update when changing VLR area** + +- 1 The RRC connection is established, if not already done. The UE sends the initial message LA Update Request (old TMSI, old LAI, etc.) to the new 3G\_MSC/VLR. The old TMSI and LAI are those that were assigned to the UE. The SRNS transfers the message to the 3G\_MSC/VLR. + +NOTE: The sending of this message to 3G\_MSC/VLR also implies establishment of a signalling connection between SRNS and 3G\_MSC/VLR for the concerned UE. + +The RAN shall add the RAC and the LAC of the cell where the message was received before passing the message to the MSC. + +2. The new 3G\_MSC/VLR sends an Send Identification Request (old TMSI) to the old 3G\_MSC/VLR to get the IMSI for the UE. (The old LAI received from UE is used to derive the old 3G\_MSC/VLR identity/address.) The old 3G\_MSC/VLR responds with Send Identification Ack. (IMSI and Authentication triplets). +3. Security functions may be executed. +4. The new 3G\_MSC/VLR inform the HLR of the change of 3G\_MSC/VLR by sending Update Location (IMSI, MSC address, VLR number) to the HLR. +5. The HLR cancels the context in the old 3G\_MSC/VLR by sending Cancel Location (IMSI). The old 3G\_MSC/VLR removes the context and acknowledges with Cancel Location Ack. + +6. The HLR sends Insert Subscriber Data (IMSI, subscription data) to the new 3G\_MSC/VLR. The new 3G\_MSC/VLR acknowledges with Insert Subscriber Data Ack. +7. The HLR acknowledges the Update Location by sending Update Location Ack. to the new 3G\_MSC/VLR. +8. The new 3G\_MSC/VLR validates the UE presence in the new LA. If due to regional, national or international restrictions the UE is not allowed to attach in the LA or subscription checking fails, then the new 3G\_MSC/VLR rejects the LA update with an appropriate cause. If all checks are successful, then the new 3G\_MSC/VLR responds to the UE with LA Update Accept (new TMSI, new LAI). +9. The UE acknowledges the new TMSI with a TMSI reallocation Complete. (TMSI can optionally be reallocated with the TMSI reallocation procedure). +10. When the location registration procedure is finished, the 3G\_MSC/VLR can release the signalling connection towards the SRNS for the concerned UE. The SRNS shall then release the RRC connection if there is no signalling connection between 3G\_SGSN and SRNS for the UE. + +#### 6.15.1.2 Routing Area Update + +The routing area update procedure is detailed in TS 23.060 [2]. + +#### 6.15.1.2A Tracking Area Update + +The tracking area update procedure is detailed in TS 23.401 [27]. + +#### 6.15.1.3 Periodic registration towards both CN nodes without use of Gs or SGs + +Periodic registration for the CS domain is specified in TS 23.012 [3]. Periodic registration for the PS domain is covered in TS 23.060 [2] and in TS 23.401 [27]. + +#### 6.15.1.4 Periodic registration with use of Gs or SGs + +Periodic registration for the PS domain with use of Gs or SGs is covered in TS 23.060 [2] or in TS 23.272 [30]. Only TA/RA Updates are required from the UE to the SGSN or MME. + +#### 6.15.1.5 UE initiated combined detach procedure when using Gs or SGs + +UE initiated Combined Detach Procedure when using Gs or SGs is specified in TS 23.060 [2] or in TS 23.272 [30]. The UE indicates which form of detach is required, i.e., PS Detach only, CS Detach only or combined Detach. + +#### 6.15.1.6 Forbidden LA/RA + +The CN (SGSN and MSC/VLR) shall not send the COMMON Id message with SNA information to the UTRAN when the attach request, LA update, or RA update are rejected. + +### 6.15.2 SRNS Relocation + +SRNS relocation is UTRAN related functionality covered in TS 25.413 [9] and TS 23.060 [2]. + +NOTE: Examples of RAN signalling are given in TR 25.931 [15]. + +## 6.16 RAN coordination + +This applies to UTRAN only. The RAN coordinates the resource allocation of an UE attached to both PS and CS services. The UTRAN shall reject or downgrade a connection which cannot be granted, see TS 23.060 [2]. The cause might be congestion on the radio interface, or the existence of other connections between this UE and the other CN. + +The RAN uses the IMSI to identify a UE. The IMSI is transferred from the CN to the RAN with the common ID procedure. When an Iu connection is established, the CN shall perform the RANAP common ID procedure toward RAN as soon as the UE is identified (IMSI). The IMSI is only stored in the RAN for the duration of the RRC Connection. + +There are two functions that are co-ordinated. + +- 1) Paging coordination is described in 5.9.1 of TS 25.410 [10]; and + +- 2) Relocation coordination that is described in 8.7.5 in TS 25.413 [9]. + +# 7 Call control + +## 7.1 General Aspects + +The following technical requirements are applied to support multimedia in GSM/UMTS. + +- 1) GSM/UMTS shall enable the provisioning of multimedia services and multivendor interworking between UE and network. +- 2) Handover and roaming to and from GSM shall be supported provided GSM is capable of supporting the ongoing media service. +- 3) For multimedia services the standardized multimedia protocol shall be run transparently via a PDP-context or a CS connection established using GSM SM/CC . This allows transparent hand-over and roaming between GSM and UMTS provided that GSM supports the QoS requirements. +- 4) SIP from the IETF shall be the multimedia call control supported over the PS domain, where the network functional entities for multimedia support are within the PLMN. + +NOTE: Other multimedia protocols can be supported e.g. H.323 transparently over the PS domain . In these cases, the multimedia functional entities shall be outside of the PLMN. Support of terminating calls for these protocols are outside the scope of these specifications. + +- 5) H.324M shall be supported within the CS domain. + +Figure 7.1 illustrates the realisation of the multimedia service based on requirement 3. 'Multimedia Protocol' indicates the functionality either inside the communicating user's terminal or a server (e.g. SIP server). It is essentially a control function both for user plane and control plane for the multimedia communication. + +![Figure 7.1: Support of multimedia making use of GSM SM/CC. The diagram shows a User Equipment (UE) connected to a Mobile Switching Center (MSC) and a Gateway GPRS Support Node (GSN). The UE contains a 'Multimedia Protocol' block connected to 'GSM CC' and 'GSM SM' blocks. The MSC contains a 'Multimedia Protocol' block connected to 'GSM CC'. The GSN contains a 'SIP Server' and a 'Multimedia Protocol' block connected to 'GSM SM'. Lines represent connections between these components: a blue line from UE 'GSM CC' to MSC 'GSM CC', a red line from UE 'GSM SM' to GSN 'GSM SM', and a black line from UE 'Multimedia Protocol' to MSC 'Multimedia Protocol' and GSN 'Multimedia Protocol'.](df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg) + +Figure 7.1: Support of multimedia making use of GSM SM/CC. The diagram shows a User Equipment (UE) connected to a Mobile Switching Center (MSC) and a Gateway GPRS Support Node (GSN). The UE contains a 'Multimedia Protocol' block connected to 'GSM CC' and 'GSM SM' blocks. The MSC contains a 'Multimedia Protocol' block connected to 'GSM CC'. The GSN contains a 'SIP Server' and a 'Multimedia Protocol' block connected to 'GSM SM'. Lines represent connections between these components: a blue line from UE 'GSM CC' to MSC 'GSM CC', a red line from UE 'GSM SM' to GSN 'GSM SM', and a black line from UE 'Multimedia Protocol' to MSC 'Multimedia Protocol' and GSN 'Multimedia Protocol'. + +Figure 7.1: Support of multimedia making use of GSM SM/CC + +## 7.2 Domain selection for mobile terminated calls from the PSTN/CS domain + +### 7.2.1 Introduction + +It is an operator's decision whether mobile terminated calls from the PSTN/CS domain are routed first to the CS domain, or to the IM subsystem. Both options may co-exist within one operator's network. + +The ability to select whether the CS domain or the IMS will provide the services is termed the Service Domain Selection (SDS) (see clause 7.2.2) and whether the CS domain or the IMS/IP-CAN is used to communicate call termination from the network and the UE is termed access domain selection (ADS) (see clauses 7.2a and 7.2b). + +NOTE: For a user subscribed to IMS Centralized Services as defined in TS 23.292 [31], the SDS routing procedure will always result in the call being routed to IMS. + +### 7.2.2 Calls directed to the CS domain + +When the mobile terminated call set-up arrives at a G-MSC server or G-MSC, then that call may be subject to service domain selection to determine whether the terminating call is to be delivered to the CS domain or the IMS is used to provide the services for the user. The G-MSC Server or G-MSC interrogates the HSS for routing information. The HSS decides on the way the call shall be treated next (e.g. IM CN subsystem, CS domain (e.g. the subscriber is roaming in a legacy network), service platform involvement). According to the decision, the HSS returns information that will make the G-MSC progress the call towards an MGCF (for onward handling in the IMS), a VMSC or to provide further processing (e.g. invoke CAMEL G-MSC processing). + +SDS may take into account for terminating calls whether the user is roaming or not, user preferences, service subscription and operator policy. In addition, for a mobile terminated call set-up towards a non IMS Centralized Services user (see TS 23.292 [31]), SDS may also take the following factors (but not limited to) into account for the selection decision: + +- The state of the UE in the circuit switched domain. The state information includes: Detached, Attached; +- The state of the UE in the IMS. The state information includes: Registered, Unregistered; +- The access network capabilities, including the information available in the HSS on whether IMS voice over PS Session is supported (as specified in TS 23.060 [2] and TS 23.401 [27]); +- The UE capabilities (e.g. SRVCC capability as defined in TS 23.216 [35]). + +NOTE: A non IMS Centralized Services user receiving services from either the CS domain or IMS depending on the above factors might experience issues with service consistency. + +### 7.2.3 Calls directed to the IMS + +When the mobile terminated call set-up arrives at a MGCF, then the MGCF passes the session to an I-CSCF which interrogates the HSS for routing information. The HSS returns information that will enable the I-CSCF to progress the call towards an S-CSCF. From the S-CSCF the session may be re-directed to the CS domain or may continue in the IMS upon instruction from the access domain selection functionality (see clause 7.2b). + +### 7.2a Domain selection for UE originating sessions / calls + +For UE originating calls, the UE performs access domain selection. The UE shall be able to take following factors into account for access domain selection decision: + +- The state of the UE in the circuit switched domain. This state information shall be included: Detached, Attached. +- The state of the UE in the IMS. The state information shall include: Registered, Unregistered. +- The domain used by an existing session / call for the same service (see the clause 7.2d). +- User preferences and any available operator policy. +- The "IMS voice over PS session supported indication" as defined in TS 23.060 [2] and TS 23.401 [27]. +- Whether the UE is expected to behave in a "Voice centric" or "Data Centric" way +- UE capability of supporting IMS PS voice. +- Indications the network may have provided to the UE in combined EPS/IMSI attach/TAU, e.g. "SMS-only" indication or "CSFB Not Preferred" indication as defined in TS 23.272 [30] + +The service domain selection functionality will decide whether the call is serviced in the CS domain or the IMS. Service domain selection functionality may take into account for originating calls whether the user is roaming or not, user preferences, service subscription and operator policy. If the UE is configured for Voice over IMS, the service domain selection functionality should take the "IMS voice over PS session supported indication" into account and should only initiate IMS voice calls (with the voice bearer in the PS domain) using the RAT where the "IMS voice over PS session supported indication" applies and indicates support. The "IMS voice over PS session supported indication" applies to E-UTRAN when received in E-UTRAN, and applies to UTRAN when either received in GERAN or UTRAN. + +NOTE 1: When a UE, which obtains voice and/or SMS services using an EPS/IMSI registration via E-UTRAN, selects a non-3GPP access network and it can neither remain EPS/IMSI registered via E-UTRAN nor obtain voice and/or SMS services using the non-3GPP access network, then the UE attempts to select also GERAN/UTRAN and performs IMSI registration to obtain voice and/or SMS services. + +To allow for appropriate domain selection for originating voice calls, a CSFB and/or IMS/CS-voice capable UE is set to behave as "Voice centric" or "Data centric" in E-UTRAN: + +- A UE set to "Voice centric" shall always try to ensure that Voice service is possible. A CSFB and an IMS/CS-voice capable UE set to "Voice centric" unable to obtain voice service in E-UTRAN (e.g. CSFB and IMS voice are not supported or the configured preferences on how to handle voice services prevent usage of any available voice services), shall disable the E-UTRAN capability, which results in re-selecting GERAN or UTRAN. The E-UTRAN capability is re-enabled by the UE under the conditions described in TS 24.301 [34]. A voice centric CSFB capable UE that receives "CSFB Not Preferred" or "SMS-only" indication as a result of combined EPS/IMSI attach or combined TA/LA Update procedures and unable to obtain voice services over IMS shall disable the E-UTRAN capability, which results in re-selecting GERAN or UTRAN. +- A UE set to "Data centric" does not disable the E-UTRAN capability if voice services cannot be obtained. Upon receiving combined EPS/IMSI attach accept or combined TA/LA Update accept with "SMS-only" indication, a data centric UE stays in the current RAT and is not allowed to use CSFB. Upon receiving combined EPS/IMSI attach accept or combined TA/LA Update accept with "CSFB Not Preferred" indication, a data centric UE stays in the current RAT and is allowed to use CSFB. + +As specified in TS 23.401 [27] and TS 23.060 [2], a CSFB and/or IMS capable UE indicates in Attach/RAU/TAU Request whether it is set to "Voice centric" or "Data centric" and it indicates its configured preferences on how the UE is supposed to handle voice services in E-UTRAN. Depending on operator's configuration, this information can be used by the network to choose the RFSP Index in use, see clause 4.3.6 in TS 23.401 [27] and clause 5.3.5 in TS 23.060 [2] for examples of how RFSP Index can be used for selective idle mode camping. + +To allow for appropriate domain selection for originating voice calls, the following applies for a CSFB and IMS capable UE in E-UTRAN: + +- It should be possible to provision UEs with the following HPLMN operator preferences on how a UE that is both CSFB and IMS capable is supposed to handle voice services (See Annex A for examples on UE behaviour for each configuration): + - CS Voice only: the UE will use only the CS domain (possibly using IMS signalling, see TS 23.292 [31]) to originate voice calls and it will not attempt to initiate voice sessions over IMS using a PS bearer. The UE attempts combined EPS/IMSI attach or combined TA/LA Update procedures. If combined EPS/IMSI attach or combined TA/LA Update fail to register the IMSI in the CS domain or succeed with an "SMS-only" indication or succeed with a "CSFB Not Preferred" indication, the UE behaves as described for "voice centric" or "data centric" according to its setting. + - CS Voice preferred, IMS PS Voice as secondary: if CS voice is available the UE will use the CS domain (possibly using IMS signalling, see TS 23.292 [31]) to originate and terminate voice calls. The UE attempts combined EPS/IMSI attach or combined TA/LA Update procedures (as defined in TS 23.272 [30]). If combined EPS/IMSI attach or combined TA/LA Update procedures fail to register the IMSI in the CS domain or succeed with an "SMS-only" indication or succeed with a "CSFB Not Preferred" indication, the UE attempts to use voice over IMS to originate voice calls. If the UE fails to use IMS for voice e.g. due to "IMS voice over PS session supported indication" indicates voice is not supported, the UE behaves as described for "voice centric" or "data centric" according to its setting. + - IMS PS Voice preferred, CS Voice as secondary: if IMS voice is available the UE will use IMS to originate and terminate voice sessions. The UE may attempt combined EPS/IMSI attach with or without "SMS only", combined TA/LA Update with or without "SMS only" or EPS attach/TAU procedures. If the UE fails to use IMS for voice, e.g. due to "IMS voice over PS session supported indication" indicates voice is not supported (in Attach accept or subsequent TAU accept), then the UE uses the CS domain (as defined in TS 23.272 [30]), possibly using IMS signalling (see TS 23.292 [31]). If not already performed, the UE attempts combined TA/LA Update procedures. If the combined TA/LA Update procedures fail to register the IMSI in the CS domain or succeed with an "SMS-only" indication or succeed with a "CSFB Not Preferred" indication and the UE has failed to use IMS for voice, the UE behaves as described for "voice centric" or "data centric" according to its setting. + +NOTE 2: Whether to perform combined EPS/IMSI attach/combined TA/LA Update or EPS attach/TAU for the case of "IMS PS Voice preferred" is to be evaluated in each release of the specifications. + +- IMS PS Voice only: the UE will use IMS to originate voice sessions and will not attempt CS Voice. The UE may attempt combined EPS/IMSI attach with "SMS only", combined TA/LA Update with "SMS only" or EPS attach/TAU. If the UE fails to use IMS for voice, e.g. due to "IMS voice over PS session supported indication" indicates voice is not supported on E-UTRAN, the UE behaves as described for "voice centric" or "data centric" according to its setting. + +To allow for appropriate domain selection for originating voice calls, the following CS/IMS voice preference setting applies for a CS and IMS capable UE in UTRAN: + +- It should be possible to provision UEs with the following HPLMN operator preferences on how a CS/IMS enabled UE is supposed to handle voice services: +- CS Voice only: the UE will not attempt to initiate voice sessions over IMS using a PS bearer. This does not preclude the use of IMS signalling to control a CS bearer (see TS 23.292 [31]); +- CS Voice preferred, IMS PS Voice as secondary: the UE will try to use the CS domain (possibly using IMS signalling, see TS 23.292 [31]) to originate voice calls; +- IMS PS Voice preferred, CS Voice as secondary: the UE will try to use IMS to originate voice sessions. If the UE fails to use IMS for voice e.g. due to "IMS voice over PS session supported indication" indicates voice is not supported (in Attach accept or subsequent RAU accept), then the UE will use the CS domain to originate voice calls, possibly using IMS signalling (see TS 23.292 [31]). + +NOTE 3: The above CS/IMS voice preference setting for UTRAN is only applicable for the selection of domain for the voice media i.e. the existing mobility procedure is not changed due to these settings. + +In limited service state, a UE should always camp on a RAT which is likely to support emergency calls. + +The TS 23.167 [33] describes when an emergency call is to be initiated in the CS domain or using IMS. When the CS domain is to be used the following applies: + +- A CSFB/IMS enabled UE which is registered in the CS domain, e.g. using CSFB procedures or using above-mentioned selection principles, shall initiate emergency call attempts in the CS domain by using available CS domain procedures. +- A CS Voice capable UE which is not registered in the CS domain shall initiate emergency calls in the CS domain by autonomously switching to a RAT which supports the CS domain (e.g. GERAN or UTRAN). + +### 7.2b Access Domain Selection for terminating sessions + +Terminating Access Domain Selection (T-ADS) selects CS access and/or one or more PS access network(s) to be used to deliver a terminating session to the UE. + +T-ADS functionality for call termination is performed in the terminating network, and can optionally be assisted by the UE procedures. + +NOTE: In case the service in the incoming request can only be supported by PS domain (e.g. file transfer, image share), PS domain is selected regardless of other criteria. + +For IMS Service Centralization and Continuity enabled networks, T-ADS is a functionality located in the IMS. The UE enhanced for IMS Service Centralization and Continuity is able to assist the T-ADS. + +For IMS Service Centralization and Continuity users, T-ADS is performed as specified in TS 23.292 [31] and TS 23.237 [32]. + +If the UE assisted T-ADS is used, then prior to responding to a session request requesting one or more media (i.e. bi-directional speech media) bearers in the PS domain, the UE shall determine, based on the PS domain's access network capabilities including the information whether IMS voice over PS Session is supported (as specified in TS 23.060 [2] and TS 23.401 [27]) (if indicated), user preferences and operator policy, whether the media bearers can be accepted on the PS domain. If the media bearers cannot be accepted, then the UE shall perform SDS. + +For terminating sessions: + +- T-ADS is always performed after the terminating services. + +The T-ADS may take the following factors (but not limited to) into account for the selection decision: + +- The service requested (e.g. voice call, file transfer, image share, etc.) in the incoming session. +- The state of the UE in the circuit switched domain. This state information shall be included: Detached, Attached. +- The state of the UE in the IMS. The state information shall include: Registered, Unregistered. +- The UE capabilities. +- The access network capabilities including the information whether IMS voice over PS Session is supported (as specified in TS 23.060 [2] and TS 23.401 [27]) by the 3GPP access network that had the most recent radio contact with the UE. +- The media components included in the incoming session. +- User preferences and operator policy. + +The T-ADS shall take into account the domains / access types used by an existing session. + +### 7.2c Domain Selection for UE originating SMS + +To allow for appropriate domain selection for SMS delivery, the following applies for an IMS capable UE which supports SMS over IP networks: + +- It should be possible to provision UEs with the following HPLMN operator preferences on how an IMS enabled UE is supposed to handle SMS services: + - SMS is not to be invoked over IP networks: the UE does not attempt to deliver SMS over IP networks. The UE attempts to deliver SMS over NAS signalling. + - SMS is preferred to be invoked over IP networks: the UE attempts to deliver SMS over IP networks. If delivery of SMS over IP networks is not available, the UE attempts to deliver SMS over NAS signalling. + +### 7.2d Domain selection decisions during ongoing sessions + +Ongoing IMS voice sessions are not impacted by a change of the IMS voice over PS session indicator (i.e. the UE performs a TAU or Combined TA/LA update in ECM-CONNECTED mode and receives IMS voice over PS session indicator indicating that IMS voice over PS sessions are not supported). + +If the UE has an ongoing IMS voice over PS session, then regardless of the value of the IMS voice over PS session indicator, the UE shall originate new calls in the same access domain as the ongoing IMS voice over PS session until the release of the ongoing IMS voice over PS session. + +## 7.3 Routing sessions from the IMS to the CS Domain + +If the IMS Service Centralization and Continuity is not used and if a subscriber is subscribed to both the CS domain and the IMS, then there may arise the need to route sessions that arrived in the IMS to the CS domain using a number related to the subscriber's MS-ISDN. All sessions which are forwarded from the IMS to the CS domain shall enter the CS domain through a G-MSC or G-MSC Server. The G-MSC or G-MSC Server will handle the session as a mobile terminating call. + +If the IMS Service Centralization and Continuity is used, the routing of the session from IMS to CS shall be done according to TS 23.292 [31]. + +# 8 Support of IM CN Subsystem services + +## 8.1 Context activation and registration + +The IP address is allocated to UE either by GPRS specific signalling when a PDP context is activated using the PDP Context Activation Procedure, or some other means e.g. by DHCP. The UE shall use IP addresses assigned to it for, but not limited to, the following: + +- the exchange of application level signalling (e.g., registration, CC) with the S-CSCF from the access network currently used, +- application level registration to IM CN subsystem as an address used to reach the UE +- an address used to reach the UE for multimedia sessions. + +The P-CSCF is located either in the Home network or in the Visited Network. + +In the following flow, a description of the order in which the registration procedure is executed and how the IP address is allocated is shown. Figure 8.1 shows the procedures performed during the GPRS and application level registration. + +![Sequence diagram showing the registration process between UE, GPRS, and IM CN Subsystem.](ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg) + +``` +sequenceDiagram + participant UE + participant GPRS + participant IM CN Subsystem + Note right of GPRS: 1. Bearer Level Registration: GPRS + Note right of GPRS: 2. PDP Context Activation + Note right of GPRS: 3. P-CSCF Discovery + Note right of GPRS: 4. Application Level Registration +``` + +The diagram illustrates a sequence of four steps for registration. At the top, three entities are shown in boxes: UE, GPRS, and IM CN Subsystem. Below them, four numbered steps are listed in separate boxes, each spanning the width of the GPRS and IM CN Subsystem columns. The steps are: 1. Bearer Level Registration: GPRS, 2. PDP Context Activation, 3. P-CSCF Discovery, and 4. Application Level Registration. Vertical lines connect the UE and GPRS boxes to the start of each step box. Horizontal lines connect the GPRS and IM CN Subsystem boxes to the start of steps 3 and 4. At the bottom of each step box, a vertical line descends to a short horizontal bar, indicating the completion of that step for the respective entity. + +Sequence diagram showing the registration process between UE, GPRS, and IM CN Subsystem. + +Figure 8.1: Registration + +The following steps are performed: + +1. the bearer level registration is performed (e.g. when the terminal is switched on or upon explicit indication from the user). +2. the PDP context activation is done. The UE has two options: + - activate a PDP context using the PDP Context Activation Procedure and obtain a new IP address (e.g. if the UE does not have any existing PDP context active or desires to use a different IP address) + - activate an additional PDP context using the Secondary PDP Context Activation Procedure and re-using the IP address of the linked already active PDP contexts. +3. UE performs the P-CSCF discovery procedure, where the UE discovers a P-CSCF, TS 23.228 [11]. + +There can be time gaps between these procedures and the following one. For instance, the UE may perform PDP context activation and the P-CSCF discovery, but not the application level registration. The UE may use the activated PDP context for other types of signalling, e.g. for P-CSCF discovery. + +4. UE performs application level registration by providing the IP address obtained at step 2 to the P-CSCF selected at step 3. The IP address used for signalling purposes is allocated in association with PDP context activation and not on an incoming call basis. + +The discovered P-CSCF forwards the registration on to the UE's home network where a S-CSCF, TS 23.228 [11] is assigned and the registration takes place. This registration associates the P-CSCF with the UE. + +From the S-CSCF point of view, the P-CSCF is where the UE is reachable for mobile-terminated session control signalling and any other type of mobile terminated IMS signalling. + +Whether the procedures are activated individually by the UE or some of them are performed automatically depends on implementation of the terminal and on the UE's configuration. For instance, the multimedia application in the UE could start the application level registration and steps 2-4 would have to be executed in response to support the operation initiated by the application. Interaction with the UE may happen during these steps. + +## 8.2 Location management + +### 8.2.1 Registration concepts for a subscriber roaming into CS domain + +Figure 8.2 shows the registration concept for a subscriber, who access IM services in the home network, roaming into a CS domain. + +![Figure 8.2: A roaming model for registration in a CS domain. The diagram shows a Home PS-IM/CS NW containing an HSS and an SGW. The SGW is connected to a Visited UMTS NW (containing an MSC/VLR and a UE) and a Visited GSM NW (containing an MSC/VLR and a UE). The HSS and SGW are connected by MAP (IP transport) messages. The SGW and the MSC/VLR in the Visited UMTS NW are connected by MAP (SS7 transport) messages. The SGW and the MSC/VLR in the Visited GSM NW are connected by MAP (SS7 transport) messages. The UE in the Visited UMTS NW sends an Update and Location (IMSI) message to the MSC/VLR. The UE in the Visited GSM NW sends an Update and Location (IMSI) message to the MSC/VLR. The legend indicates that solid lines represent UMTS (R99-CS, and PS-IM/CS -CS in case of non-IP transport) subscriber data download, and dashed lines represent GSM (CS) subscriber data download.](f24f909d837b5476783e1bbea2dfc143_img.jpg) + +Figure 8.2: A roaming model for registration in a CS domain. The diagram shows a Home PS-IM/CS NW containing an HSS and an SGW. The SGW is connected to a Visited UMTS NW (containing an MSC/VLR and a UE) and a Visited GSM NW (containing an MSC/VLR and a UE). The HSS and SGW are connected by MAP (IP transport) messages. The SGW and the MSC/VLR in the Visited UMTS NW are connected by MAP (SS7 transport) messages. The SGW and the MSC/VLR in the Visited GSM NW are connected by MAP (SS7 transport) messages. The UE in the Visited UMTS NW sends an Update and Location (IMSI) message to the MSC/VLR. The UE in the Visited GSM NW sends an Update and Location (IMSI) message to the MSC/VLR. The legend indicates that solid lines represent UMTS (R99-CS, and PS-IM/CS -CS in case of non-IP transport) subscriber data download, and dashed lines represent GSM (CS) subscriber data download. + +**Figure 8.2: A roaming model for registration in a CS domain** + +NOTE: The above figure shows one configuration where the Signalling Gateway (SGW) is needed. Other configurations are possible as well (see TS 23.002 [1]). + +The detailed message sequence chart for a subscriber roaming into a CS domain and accessing an IM application is shown in figure 8.3. + +![Sequence diagram for roaming into a CS domain. Lifelines: UE, MSC/VLR, SGW, HSS, Old MSC/VLR. The sequence shows 9 steps: 1. LU from UE to MSC/VLR; 2. UMTS/GSM Authentication between MSC/VLR and HSS; 3. LU from MSC/VLR to HSS via SGW; 4. Insert Subscriber Data Req from HSS to MSC/VLR via SGW; 5. Insert Subscriber Data Ack from MSC/VLR to HSS via SGW; 6. Update Location Ack from HSS to MSC/VLR via SGW; 7. LU Ack from MSC/VLR to UE; 8. Cancel Location Req from HSS to Old MSC/VLR; 9. Cancel Location Ack from Old MSC/VLR to HSS.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MSC/VLR + participant SGW + participant HSS + participant OldMSC/VLR as Old MSC/VLR + + Note right of UE: 1. LU + UE->>MSC/VLR: 1. LU + Note right of MSC/VLR: 2. UMTS/GSM Authentication + MSC/VLR->>HSS: 3. LU + Note right of HSS: 4. Insert Subscriber Data Req + HSS->>MSC/VLR: 4. Insert Subscriber Data Req + Note right of MSC/VLR: 5. Insert Subscriber Data Ack. + MSC/VLR->>HSS: 5. Insert Subscriber Data Ack. + Note right of HSS: 6. Update Location Ack. + HSS->>MSC/VLR: 6. Update Location Ack. + Note right of MSC/VLR: 7. LU Ack. + MSC/VLR->>UE: 7. LU Ack. + Note right of HSS: 8. Cancel Location Req. + HSS->>OldMSC/VLR: 8. Cancel Location Req. + Note right of OldMSC/VLR: 9. Cancel Location Ack. + OldMSC/VLR->>HSS: 9. Cancel Location Ack. + +``` + +Sequence diagram for roaming into a CS domain. Lifelines: UE, MSC/VLR, SGW, HSS, Old MSC/VLR. The sequence shows 9 steps: 1. LU from UE to MSC/VLR; 2. UMTS/GSM Authentication between MSC/VLR and HSS; 3. LU from MSC/VLR to HSS via SGW; 4. Insert Subscriber Data Req from HSS to MSC/VLR via SGW; 5. Insert Subscriber Data Ack from MSC/VLR to HSS via SGW; 6. Update Location Ack from HSS to MSC/VLR via SGW; 7. LU Ack from MSC/VLR to UE; 8. Cancel Location Req from HSS to Old MSC/VLR; 9. Cancel Location Ack from Old MSC/VLR to HSS. + +**Figure 8.3: Message sequence for roaming into a CS domain** + +1. The UE initiates the Location Update procedure with the MSC/VLR of the visited network. The LU message contains the IMSI of the subscriber. +2. The authentication is performed as per the existing 3GPP specifications for the CS domain. +3. The MSC/VLR initiates the MAP Location Update procedure towards the HSS of the user via SGW. The HSS stores the VLR address etc. The message contains IMSI and other parameters as defined in the 3GPP specifications for the CS domain. The SGW performs SS7 transport to/from IP conversion. +4. The HSS provides the subscriber data for the roaming user to VLR by sending MAP Insert Subscriber Data message via SGW. The message contains IMSI and other necessary parameters as defined in the 3GPP specification for both Iu and A/Gb mode. The message is passed through the SGW transparently while the SS7 to/from IP conversion is performed in SGW. +5. The serving VLR then acknowledges the receipt of the subscriber data to the HSS via SGW. +6. The HSS acknowledges the completion of location updating procedure to the MSC/VLR via SGW. +7. The MSC/VLR acknowledges the completion of location updating procedure to the UE. +8. The HSS sends the MAP Cancel Location message to the old MSC/VLR (optional procedure). +9. Location cancellation is acknowledged to the HSS by the old MSC/VLR. + +NOTE 1: The steps 8 and 9 above assume that the UE was previously registered to a CS domain . + +NOTE 2: The MAP messages between the MSC/VLR and HSS are passed transparently via SGW. The SGW does not interpret the MAP messages in anyway, but performs only the lower level conversion between SS7 and IP. This is in accordance with the TS 23.002 [1] for SGW. + +## 8.3 IMS Emergency sessions + +### 8.3.1 GPRS/EPS considerations for UE recognized IMS Emergency Sessions + +Requirements for GPRS and EPS functions for support of IMS emergency services are defined in TS 23.060 [2], TS 23.401 [27] and in TS 23.167 [33]. + +### 8.3.2 Emergency Calls in absence of UICC for GPRS/EPS Access + +Requirements for GPRS and EPS functions for support of IMS emergency services are defined in TS 23.060 [2], TS 23.401 [27] and in TS 23.167 [33]. + +# --- 9 Efficient use of radio resource + +This clause captures the technical requirements to ensure efficient use of the radio resource in the UMTS access network. The radio resource is considered to be a scarce resource and therefore every opportunity shall be taken to optimize its use. + +For UTRAN it shall be possible to re-apply PS domain pre-release 5 mechanisms for efficient use of radio resource. + +Additional requirements for efficient use of the radio spectrum for release 5 SIP signalling include the following: + +- UMTS shall support mechanisms to optimize transport of SIP signalling packets over the radio interface, typically by compressing the SIP signalling messages and by compressing the IP and transport layer protocol headers that carry these SIP messages. +- The chosen solution(s) shall be extensible to facilitate the incorporation of new and improved compression algorithms in a backward compatible way as they become available. +- The chosen solution(s) should work in roaming scenarios. +- Application specific compression shall minimize impacts on existing UMTS release e.g. it could be defined between the UE and associated application server, e.g. at the SIP Client and at the first SIP Proxy. + +Support of SIP signalling compression is mandatory in the UE and P-CSCF for IMS. The actual usage of compression is optional but highly preferable and is subject to operator policies. See TS 24.229 [23] for more details. + +# Annex A (informative): Guidance for CSFB and IMS enabled UE implementations in E-UTRAN + +## A.1 General + +This annex provides some examples on how the CSFB and IMS capable UE which supports E-UTRAN can make use of the following indications/settings prior to accessing E-UTRAN: + +- "CS Voice only", "IMS PS Voice only", "prefer CS Voice with IMS PS Voice as secondary", or "prefer IMS PS Voice with CS Voice as secondary", and +- "Voice centric" or "Data centric". + +## A.2 IMS PS Voice preferred + +### A.2.1 EPS Attach + +The following figure A.2.1-1 illustrates the UE behaviour when performing non-combined EPS/IMSI attach, with the setting of: "prefer IMS PS Voice with CS Voice as secondary". + +![Flowchart illustrating UE behaviour for IMS PS Voice preferred with CS Voice as secondary, non combined EPS/IMSI attach.](8d8c758885b4f754ff071bf3b572ab3c_img.jpg) + +``` +graph TD; A[UE is set to IMS voice preferred, CS voice secondary] --> B[UE initiates EPS attach procedure (non combined)]; B --> C[UE checks for IMS voice supported Indication from Network]; C -- Not supported --> D[UE performs combined TAU for CSFB as in TS 23.272]; D -- "Fail or Success with 'SMS only' indication or Success with 'CSFB Not Preferred' indication" --> E[UE checks for voice centric or data centric setting]; C -- Supported --> F[UE uses IMS Voice]; D -- "Success with no 'SMS-only' and no 'CSFB Not Preferred' indication" --> G[UE uses CSFB]; E -- Voice centric --> H[UE reselects to other RAT]; E -- Data centric --> I[UE stays in current RAT]; F -- TAU performed --> C; +``` + +The flowchart illustrates the UE behaviour for IMS PS Voice preferred with CS Voice as secondary, non combined EPS/IMSI attach. It starts with the UE being set to IMS voice preferred, CS voice secondary. The UE then initiates an EPS attach procedure (non combined). It checks for IMS voice supported Indication from Network. If not supported, it performs a combined TAU for CSFB as in TS 23.272. This TAU can result in a fail or success with "SMS only" indication or success with "CSFB Not Preferred" indication, leading to a check for voice centric or data centric setting. If supported, the UE uses IMS Voice, and a TAU performed loop back to the check. If the TAU is successful with no "SMS-only" and no "CSFB Not Preferred" indication, the UE uses CSFB. If the voice centric or data centric setting is voice centric, the UE reselects to other RAT. If data centric, the UE stays in current RAT. + +Flowchart illustrating UE behaviour for IMS PS Voice preferred with CS Voice as secondary, non combined EPS/IMSI attach. + +**Figure A.2.1-1: UE behaviour for IMS PS Voice preferred with CS Voice as secondary, non combined EPS/IMSI attach** + +### A.2.2 Combined EPS/IMSI attach + +The following figure A.2.2-1 illustrates the UE behaviour when performing combined EPS/IMSI attach, with the setting of: "prefer IMS PS Voice with CS Voice as secondary". + +![Flowchart illustrating UE behaviour for IMS PS Voice preferred with CS Voice as secondary, combined EPS/IMSI attach.](67d03c9e89620d73e3786c869e559752_img.jpg) + +``` + +graph TD + A[UE is set to prefer +IMS PS Voice with +CS Voice as +secondary] --> B[UE initiates a +combined EPS/ +IMSI attach +procedure] + + B -- "IMSI Attach Failed or +IMSI Attach accepted +with SMS only indication +or IMSI Attach accepted +with CSFB Not +Preferred indication" --> C[UE checks for IMS +Voice over PS +session supported +Indication from +Network] + + B -- "IMSI Attach +Accepted with no "SMS-only" +and no "CSFB Not +Preferred" indication" --> D[UE checks for IMS +Voice over PS +session supported +Indication from +Network] + + C -- "IMS PS Voice +NOT supported" --> E[UE checks for +voice centric or +data centric setting] + + C -- "IMS PS Voice supported" --> F[UE uses +IMS PS Voice] + + D -- "IMS PS Voice NOT supported" --> G[UE uses CSFB] + + D -- "IMS PS Voice supported" --> F + + E -- "Data centric" --> H[UE stays in +current RAT] + + E -- "Voice centric" --> I[UE reselects to +other RAT] + +``` + +The flowchart illustrates the UE behaviour for IMS PS Voice preferred with CS Voice as secondary, combined EPS/IMSI attach. It starts with the UE being set to prefer IMS PS Voice with CS Voice as secondary. The UE then initiates a combined EPS/IMSI attach procedure. If the IMSI Attach is failed or accepted with an SMS-only indication or CSFB Not Preferred indication, the UE checks for IMS Voice over PS session supported Indication from the Network. If IMS PS Voice is NOT supported, the UE checks for voice centric or data centric setting. If data centric, the UE stays in current RAT. If voice centric, the UE reselects to other RAT. If IMS PS Voice is supported, the UE uses IMS PS Voice. If the IMSI Attach is accepted with no "SMS-only" and no "CSFB Not Preferred" indication, the UE checks for IMS Voice over PS session supported Indication from the Network. If IMS PS Voice is NOT supported, the UE uses CSFB. If IMS PS Voice is supported, the UE uses IMS PS Voice. + +Flowchart illustrating UE behaviour for IMS PS Voice preferred with CS Voice as secondary, combined EPS/IMSI attach. + +**Figure A.2.2-1: UE behaviour for IMS PS Voice preferred with CS Voice as secondary, combined EPS/IMSI attach** + +## A.3 CS Voice preferred + +The following figure A.2.1-1 illustrates the UE behaviour with the setting of: "prefer CS Voice with IMS PS Voice as secondary". + +![Flowchart showing UE behavior for CS Voice preferred with IMS PS Voice as secondary. The process starts with UE settings, followed by EPS/IMSI attach, then checks for IMS voice support. If supported, IMS voice is used; if not, the UE checks for voice or data centric settings to decide whether to stay in the current RAT or reselect.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` +graph TD; A[UE is set to CS Voice preferred, IMS PS Voice secondary] --> B[UE initiates a combined EPS/IMSI attach procedure]; B -- "Success with no 'SMS only' indication and no 'CSFB Not Preferred' indication" --> C[UE uses CSFB]; B -- "Fail or Success with 'SMS only' indication or Success with 'CSFB Not Preferred' indication" --> D[UE checks for IMS voice supported Indication from Network]; D -- "Supported TAU performed" --> E[UE uses IMS Voice]; D -- "Not supported" --> F[UE checks for voice centric or data centric setting]; F -- "Voice centric" --> G[UE reselects to other RAT]; F -- "Data centric" --> H[UE stays in current RAT]; +``` + +Flowchart showing UE behavior for CS Voice preferred with IMS PS Voice as secondary. The process starts with UE settings, followed by EPS/IMSI attach, then checks for IMS voice support. If supported, IMS voice is used; if not, the UE checks for voice or data centric settings to decide whether to stay in the current RAT or reselect. + +Figure A.3-1: UE behaviour for CS Voice preferred with IMS PS Voice as secondary + +## A.4 IMS PS Voice only + +The following figure A.4.1-illustrates the UE behaviour with the setting of: "IMS PS Voice only". + +![Flowchart showing UE behavior for IMS PS Voice only. The process starts with 'UE is set to IMS voice only', followed by 'UE initiates EPS attach procedure (non combined)'. Then, 'UE checks for IMS voice supported Indication from Network'. If 'Not supported', it goes to 'UE checks for voice centric or data centric setting', which leads to either 'Data centric' (UE stays in current RAT) or 'Voice centric' (UE reselects to other RAT). If 'Supported TAU performed', it goes to 'UE uses IMS Voice'.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + +graph TD + A[UE is set to IMS voice only] --> B[UE initiates EPS attach procedure +(non combined)] + B --> C[UE checks for IMS voice supported +Indication from Network] + C -- "Not supported" --> D[UE checks for voice centric or +data centric setting] + D -- "Voice centric" --> E[UE reselects to +other RAT] + D -- "Data centric" --> F[UE stays in current +RAT] + C -- "Supported TAU performed" --> G[UE uses IMS +Voice] + G --> C + +``` + +Flowchart showing UE behavior for IMS PS Voice only. The process starts with 'UE is set to IMS voice only', followed by 'UE initiates EPS attach procedure (non combined)'. Then, 'UE checks for IMS voice supported Indication from Network'. If 'Not supported', it goes to 'UE checks for voice centric or data centric setting', which leads to either 'Data centric' (UE stays in current RAT) or 'Voice centric' (UE reselects to other RAT). If 'Supported TAU performed', it goes to 'UE uses IMS Voice'. + +Figure A.4-1: UE behaviour for IMS PS Voice only + +## A.5 CS Voice only + +The following figure A.5.1-1 illustrates the UE behaviour with the setting of: "CS Voice only". + +![Flowchart showing UE behavior for CS Voice only. It starts with 'UE is set to CS Voice only', leading to 'UE initiates a combined EPS/ IMSI attach procedure'. From there, if 'Success with no "SMS-only" indication and no "CSFB Not Preferred" indication', the UE uses CSFB. If 'Fail or Success with "SMS only" indication or Success with "CSFB Not Preferred" indication', the UE checks for voice centric or data centric setting. If 'Data centric', the UE stays in current RAT. If 'Voice centric', the UE reselects to other RAT.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` +graph TD; A[UE is set to CS Voice only] --> B[UE initiates a combined EPS/ IMSI attach procedure]; B -- "Success with no "SMS-only" indication and no "CSFB Not Preferred" indication" --> C[UE uses CSFB]; B -- "Fail or Success with "SMS only" indication or Success with "CSFB Not Preferred" indication" --> D[UE checks for voice centric or data centric setting]; D -- "Data centric" --> E[UE stays in current RAT]; D -- "Voice centric" --> F[UE reselects to other RAT]; +``` + +Flowchart showing UE behavior for CS Voice only. It starts with 'UE is set to CS Voice only', leading to 'UE initiates a combined EPS/ IMSI attach procedure'. From there, if 'Success with no "SMS-only" indication and no "CSFB Not Preferred" indication', the UE uses CSFB. If 'Fail or Success with "SMS only" indication or Success with "CSFB Not Preferred" indication', the UE checks for voice centric or data centric setting. If 'Data centric', the UE stays in current RAT. If 'Voice centric', the UE reselects to other RAT. + +Figure A.5-1: UE behaviour for CS Voice only + +# Annex B (informative): Guidance related to IPv4 address usage + +## B.1 General + +3GPP has investigated and documented various aspects of interworking as well as transition mechanisms related to IPv6 address usage and coexistence with IPv4 environment. These guidelines are as well applicable for usage in environment like MTC as deemed appropriate. + +- For general guidelines towards IPv6 migration aspects, TR 23.975 [36], "IPv6 migration Guidelines" should be followed as appropriate. +- For Session based applications similar to IMS, TR 23.981 [26], "Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations" may be used as appropriate. The report describes baseline guidelines and in conjunction with TS 23.228 [11] provides comprehensive details for coexistence/transition/migration for IPv6 and IPv4 addressing in 3GPP networks for IMS. + +## B.2 Interworking aspects + +### B.2.1 Interworking scenario: UE assigned private IPv4 address + +When IPv4 addressing is used, the UE, for example in case of MTC, is normally assigned a private IPv4 address due to the limitation of the public IPv4 address space. In case of MTC, the MTC Server may reside in the same private IPv4 address space as the UE, or the MTC Server may reside in public IPv4 address space. In the first case, the UE used for MTC and the MTC Server are in the same routable address space. In the latter case, the UE used for MTC and the MTC Server are located in different private IP address spaces. + +![Diagram illustrating the interworking scenario for MTC. It shows two main address spaces. The left space is a 'Private IPv4 Address Space' containing a 'UE used for MTC' and an 'MNO'. The right space is a 'Private or Public IPv4 Address space' containing an 'MTC Server / MTC Application'. Arrows indicate communication flow: from the MTC Server/Application to the MNO, and from the MNO to the UE.](1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg) + +``` +graph LR; subgraph RightSpace [Private or Public IPv4 Address space]; MTC[MTC Server / MTC Application]; end; subgraph LeftSpace [Private IPv4 Address Space]; MNO[MNO]; UE[UE used for MTC]; end; MTC --> MNO; MNO --> UE; +``` + +Diagram illustrating the interworking scenario for MTC. It shows two main address spaces. The left space is a 'Private IPv4 Address Space' containing a 'UE used for MTC' and an 'MNO'. The right space is a 'Private or Public IPv4 Address space' containing an 'MTC Server / MTC Application'. Arrows indicate communication flow: from the MTC Server/Application to the MNO, and from the MNO to the UE. + +**Figure B.2.1-1: Application Server (e.g. MTC) in a public or private address space and UE in private address space** + +### B.2.2 Use of Device triggering + +For indirect and hybrid model, use of device triggering as described in TS 23.682 [38] may be used to handle NAT traversal in situations where the Server (e.g. MTC Server) or Application is attempting to communicate with UEs in a private IP address space. In addition device triggering may be used to get the device to initiate the communication with the Server or Application. + +NOTE: The above mechanism can be applied to any application (e.g. MTC) which is able to use device triggering. + +### B.2.3 Specific APN use + +For indirect and direct model (as described in TS 23.682 [38]), use of separate explicit Access Point Names (APN), and IPv4 address allocation performed following procedures as described in 3GPP specifications in TS 23.401 [27] and TS 23.060 [2] and TS 29.061 [37] resolves private IPv4 address usage issues. + +![Diagram illustrating IP address assignment for multiple devices connected to different PDNs via GGSN/PGW units.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +The diagram shows a vertical stack of devices on the left: Device 1, an ellipsis, Device i, Device j, and Device k. Each device is connected to a corresponding GGSN/PGW unit labeled GGSN/PGW A, GGSN/PGW B, and GGSN/PGW C. Each GGSN/PGW unit is connected via a tunnel (labeled 'Tunneling') to a separate Packet Data Network (PDN) cloud: PDN A, PDN B, and PDN C. Inside each PDN cloud is a server: Server 1, Server 2, and Server 3. All three servers are connected to a common 'Overlapping private IP address pool e.g. (10.0.0.0)'. + +Diagram illustrating IP address assignment for multiple devices connected to different PDNs via GGSN/PGW units. + +**Figure B.2.3-1: Example IP address assignment when the Server is owned by the MNO or by Application Provider using specific APNs** + +In case of MTC, the Server is either deployed by the PLMN operator or by an application provider who owns an MTC Server and uses a specific APN assigned by the PLMN. In both cases a tunnelling mechanism is used between the GGSN/P-GW and the PDN of the Server to allow carrying the IP packets enabling assignment of private IP addresses to the UE used for MTC. The tunnelling allows for connecting the PLMN with the Server(s) using public IP networks. Furthermore that tunnelling allows for setting up private network with multiple GGSNs/P-GWs and multiple Servers where every GGSN, P-GW or the Server can be deployed at a different location. By using a separate APN per application (provider) the Servers from different applications can use the same overlapping private IP addresses as needed without the need for the network to implement a NAT function as the UE used for MTC and servers used for MTC belonging to one application share the same private IP address space. + +NOTE: The above mechanism can be applied to other applications using same scenario as described in Figure B.2.3-1. + +# Annex C (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|------|-----|-----|-----------------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 03/2011 | SA#51 | SP-110075 | 0122 | 2 | F | Restricting IPv6 interface identifier generation to protect usage patterns | 9.4.0 | 10.0.0 | +| 12/2011 | SA#54 | SP-110737 | 0134 | 2 | B | Update of Domain Selection | 10.0.0 | 10.1.0 | +| 12/2011 | SA#54 | SP-110742 | 0132 | 7 | B | Normative documentation for SIMTC and IP addressing | 10.1.0 | <b>11.0.0</b> | +| 12/2011 | SA#54 | SP-110748 | 0133 | 1 | C | Clarification on T-ADS behaviour | 10.1.0 | 11.0.0 | +| 12/2012 | SA#58 | SP-120710 | 0146 | - | A | Restriction of Inter RAT handover/release with redirection to E-UTRAN | 11.0.0 | 11.1.0 | +| 12/2012 | SA#58 | SP-120726 | 0149 | 1 | F | Clarification on SDS to ensure that the service can be performed correctly. | 11.0.0 | 11.1.0 | +| 06/2013 | SA#60 | SP-130223 | 0148 | 6 | F | Enabling CS services when UE gets IMSI detached | 11.1.0 | 11.2.0 | +| 06/2014 | SA#64 | SP-140251 | 0159 | 3 | A | Keeping ongoing IMS voice calls when IMSVoPS indication changes | 11.2.0 | 11.3.0 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23226/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-11/23_series/23226/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfe8ee9c52f3744eb7fe8de8e73dd1eec9b461e3 --- /dev/null +++ b/marked/Rel-11/23_series/23226/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:529294d77f646c233f3bdf7a02c8da83918f20cc31bee4bb056b9048e4e81bef +size 51449 diff --git a/marked/Rel-11/23_series/23226/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/Rel-11/23_series/23226/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..379dfe52d6dc0a02646f8a64570cdefda87181a9 --- /dev/null +++ b/marked/Rel-11/23_series/23226/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a0a259d933c7a843dd24000fe951800ca4e9e658cc2268b7400cb43780d06a4 +size 44375 diff --git a/marked/Rel-11/23_series/23226/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/marked/Rel-11/23_series/23226/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08ff76fa48204107eb7c1e30877da4baf139793b --- /dev/null +++ b/marked/Rel-11/23_series/23226/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53adb3dd2a36179e6f2a4ff0707e3de6b09c9e9cafc1bffaaecd6cd49538cb80 +size 44330 diff --git a/marked/Rel-11/23_series/23226/327ba94498e3381cf08eb41e3fd3d77f_img.jpg b/marked/Rel-11/23_series/23226/327ba94498e3381cf08eb41e3fd3d77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64622c899c6e2055dc637d80666af2560cf5aa15 --- /dev/null +++ b/marked/Rel-11/23_series/23226/327ba94498e3381cf08eb41e3fd3d77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5105d5f67688ca64f4f2fe8b353d06d714fe9cc7f2010522f5ff625e6dfad851 +size 26000 diff --git a/marked/Rel-11/23_series/23226/3b621c21b0af3a504a28d2547e87138f_img.jpg b/marked/Rel-11/23_series/23226/3b621c21b0af3a504a28d2547e87138f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a31c29b8c2bd3270690d767b95ec5be6dd038d6 --- /dev/null +++ b/marked/Rel-11/23_series/23226/3b621c21b0af3a504a28d2547e87138f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8588de65c59d032776c904c6359d501e5fe1707aad70447d5980b7f8bf80cba7 +size 51850 diff --git a/marked/Rel-11/23_series/23226/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-11/23_series/23226/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07dadf2c45d8e0b3440d2b21415df73e19b5e5e7 --- /dev/null +++ b/marked/Rel-11/23_series/23226/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2987a316ca7c3cd3e8627ec406d909edc67a1af3ba047504946cb59401c172e3 +size 58020 diff --git a/marked/Rel-11/23_series/23226/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Rel-11/23_series/23226/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b449041c01d43d1c7c2d290bc2f56f8e73a28bd7 --- /dev/null +++ b/marked/Rel-11/23_series/23226/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8374ec2d23d82b78eb06c6a392f8e2713e60d4112168e3ad97d8cae987f6b6c4 +size 44054 diff --git a/marked/Rel-11/23_series/23226/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-11/23_series/23226/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af4fdd5a90f4456c172f103db8dd909f6aa48ce5 --- /dev/null +++ b/marked/Rel-11/23_series/23226/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d2461b277b254d0041db09c96bd4f3df609f49c2f5f143b9fa9fa316fce22fd +size 32337 diff --git a/marked/Rel-11/23_series/23226/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/Rel-11/23_series/23226/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..505fb85b1b8ec666d488e85daec517ba0dd237b5 --- /dev/null +++ b/marked/Rel-11/23_series/23226/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad55a6e0b04b6193877d0ac950af021ec722a38694e5fa0c571965e906153ab1 +size 71066 diff --git a/marked/Rel-11/23_series/23226/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/Rel-11/23_series/23226/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4be61718e0081939a09b9480a9a447c5d38c5ca6 --- /dev/null +++ b/marked/Rel-11/23_series/23226/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b77ceb6fcbea7a06169c3fa92468e380a63f98ba2d91a68c2af5394e2a36423 +size 43851 diff --git a/marked/Rel-11/23_series/23226/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23226/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f703e0d814e39cfb55e2e8dc23c0a9d82c37afa --- /dev/null +++ b/marked/Rel-11/23_series/23226/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb2bad67fe440f05d787bf0f20492aba4f213447f729174fa1fce5b7793fe195 +size 58226 diff --git a/marked/Rel-11/23_series/23226/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/23_series/23226/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b8e7f65305d1649f72b9fcd1516d2922158d6f4 --- /dev/null +++ b/marked/Rel-11/23_series/23226/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26310c9eae274bd9294bab16c5bcf1e6d1ac3819b055e6c1e07ef960f9b27ad2 +size 60984 diff --git a/marked/Rel-11/23_series/23226/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23226/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb2b184db33a2944932c588a467d1d44d853eb19 --- /dev/null +++ b/marked/Rel-11/23_series/23226/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4ddf697625ac65524a8c058378a7da966d81b1be1a6b0330c1c00500560d362 +size 60297 diff --git a/marked/Rel-11/23_series/23226/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-11/23_series/23226/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4fd1d262b9349e011cceacb80ba2fe7963e8802 --- /dev/null +++ b/marked/Rel-11/23_series/23226/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b3e4b66a9f2629a38c17cd4ed81e352bcbb9b4387ab18e69ff29383b022a525 +size 63172 diff --git a/marked/Rel-11/23_series/23226/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-11/23_series/23226/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bd820f9098dfa6d8258e4c9e8215ee086247dbf --- /dev/null +++ b/marked/Rel-11/23_series/23226/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23c61d301e72e328f7b2bd0e0866b9b0f70a7f2701e2234bdad87381127da889 +size 24831 diff --git a/marked/Rel-11/23_series/23226/df1d0e45191302de72176e4390224c16_img.jpg b/marked/Rel-11/23_series/23226/df1d0e45191302de72176e4390224c16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04bdb1115415968eec3198c75fdc37ad076eba41 --- /dev/null +++ b/marked/Rel-11/23_series/23226/df1d0e45191302de72176e4390224c16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91037c0bd33af626b4966763a5655756740f0daad1c3e86988ba0ad3b57a9c72 +size 49716 diff --git a/marked/Rel-11/23_series/23226/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/23_series/23226/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e64f9df7200a0f7c833cbd4c97a1981b02cb5270 --- /dev/null +++ b/marked/Rel-11/23_series/23226/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a36138356557e961256bd07a87dcbf667b05dea90f94a02ce19c230fac02d29 +size 89150 diff --git a/marked/Rel-11/23_series/23226/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/23_series/23226/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3859c98d006dd86f0262d69c1e763bb57b45dfc5 --- /dev/null +++ b/marked/Rel-11/23_series/23226/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7a4f8d55e9e74759c04b041b256215d294638aa17845386209c6c9392c82684 +size 66784 diff --git a/marked/Rel-11/23_series/23226/raw.md b/marked/Rel-11/23_series/23226/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b02a9bc867b956ea230907e63db8337189ca48b4 --- /dev/null +++ b/marked/Rel-11/23_series/23226/raw.md @@ -0,0 +1,777 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 General Functions ..... | 8 | +| 4.1 Overview ..... | 8 | +| 4.1.1 General text transmission functions ..... | 8 | +| 4.1.2 Functions ..... | 9 | +| 4.1.2.1 Call Control and text media initiation..... | 9 | +| 4.1.2.2 Presentation coding..... | 9 | +| 4.1.2.3 Transport and transmission host environments ..... | 9 | +| 4.1.2.4 Multiplexing..... | 9 | +| 4.1.2.5 Conversion..... | 10 | +| 4.1.2.6 Text capable terminal..... | 10 | +| 4.1.2.7 Routing and location of CTM detection/conversion functions..... | 10 | +| 4.1.3 Emergency service considerations..... | 10 | +| 5 Considerations for each host environment..... | 11 | +| 5.1 GTT-IP: IP Multimedia..... | 11 | +| 5.1.0 GTT-IP ..... | 11 | +| 5.1.1 Interworking between Real-Time Text and PSTN Text Telephony..... | 11 | +| 5.1.2 Emergency call considerations for GTT-IP..... | 11 | +| 5.2 GTT-CS: Circuit switched Multimedia..... | 12 | +| 5.3 GTT-Voice: Circuit switched voice channel..... | 12 | +| 5.3.1 Interworking between GTT-Voice and PSTN Text Telephony ..... | 12 | +| 5.3.2 Functional details of fixed network interworking ..... | 13 | +| 5.3.3 Emergency call considerations for GTT-Voice..... | 13 | +| 5.3.4 Interworking aspects..... | 14 | +| <b>Annex A (informative): GTT-Voice specific information for CTM support in, or associated with, all transcoders .....</b> | <b>15</b> | +| A.1 GTT-Voice specific information for CTM support in, or associated with, all transcoders in the access network for GSM networks with A-interface ..... | 15 | +| A.2 GTT-Voice specific information for CTM support in or associated with all transcoders in the core network for networks supporting the Iu interface..... | 15 | +| <b>Annex B (informative): GTT-Voice support via selection of CTM detection / conversion function.....</b> | <b>17</b> | +| B.1 GTT-Voice specific information for CTM support in GSM networks with A-interface, via access network circuit pooling ..... | 17 | +| B.2 GTT-Voice specific information for CTM support via core network termination selection for networks using Iu interface..... | 18 | +| <b>Annex C (Informative): GTT-Voice specific information for the CTM-SRF core network node solution .....</b> | <b>20</b> | +| C.1 Emergency calls ..... | 20 | +| C.2 Routing of regular user calls ..... | 21 | +| C.2.1 Mobile Terminating calls ..... | 21 | +| C.2.2 Mobile originating calls ..... | 22 | + +| | | | +|------------------------|--------------------------------------------------------|----| +| C.2.3 | Mobile to Mobile Calls ..... | 23 | +| C.3 | Routing actions of the CTM-SCP ..... | 23 | +| C.4 | Routing actions of the CTM-SRF ..... | 25 | +| C.5 | Service interactions ..... | 26 | +| C.5.1 | Interaction with other CAMEL services ..... | 26 | +| C.5.2 | Interactions with Supplementary Services ..... | 26 | +| C.5.3 | Emergency Call interaction ..... | 26 | +| C.5.4 | Usage of Destination Routing Address ..... | 26 | +| C.5.5 | Inserting CTM/Text telephone conversion function ..... | 26 | +| C.5.6 | Lawful interception ..... | 27 | +| Annex D (informative): | Change history..... | 28 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +Real time, character by character text conversation is a component that can be of value in a distant conversation. Users may have an interest to use real time text conversation alone or in any combination with voice and video. + +Global Text Telephony is a feature that adds the capability to use a text conversation component in a session. It is called GTT here. + +GTT is defined in a set of host environments, circuit switched as well as packet switched. + +Interworking with corresponding features in other networks is an important part of Global Text Telephony. Specifically, the different kinds of PSTN text telephone systems supported by the international text telephone modem standard ITU-T Recommendation V.18 [4] are included in the modes for interworking consideration. + +One important reason to offer the Global Text feature is to enable emergency service access to people who are depending on a written dialogue. + +A more elaborated background is found in TS 22.226 [3], Global Text Telephony, Stage 1, Annex A. + +# --- 1 Scope + +This 3GPP Technical Specification defines the stage 2 description of the real time Text Conversation Feature called Global Text Telephony, GTT. GTT Stage 2 identifies the functional capabilities needed to support the service described in GTT Stage 1. + +This TS contains the core functions for a real time Text Conversation Feature GTT, to be used in combination with other media in conversational services. + +GTT offers real time conversation in text, to be used alone or in combination with other conversational media, and interworking with current and emerging text conversation features in the fixed networks and other mobile networks. + +GTT uses a number of functional entities to realise the requirements of the stage 1 description (TS 22.226 [3]). This TS describes how the service requirements are realised with these functional entities. As far as possible existing protocols shall be used for the realisation of the Global Text Telephony Feature. This may include e.g. , SIP, 3G.324, or Circuit Switched Voice service as protocol environments, and CTM, AL1 and RTP/text as transmission protocols. It also means usage of existing text presentation format ITU-T Recommendation T.140 [5], common to all GTT text conversation environments. + +# --- 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 22.101: "Service Principles". +- [2] 3GPP TS 22.121: "The Virtual home Environment". +- [3] 3GPP TS 22.226: "Global Text Telephony; Stage 1 service description". +- [4] ITU-T Recommendation V.18: "Operational procedures for modems in the text telephone mode". +- [5] ITU-T Recommendation T.140: "Text conversation presentation protocol". +- [6] 3GPP TS 26.110: "Codec for 3G CS Multimedia (2000)". +- [7] ITU-T Recommendation H.323 Annex G: "Text conversation and text SET (2000)". +- [8] ITU-T Recommendation H.224 (2000): "Very low bitrate multimedia system". +- [9] ITU-T Recommendation H.248.2: "Facsimile, Text Conversation and Call Discrimination Packages". +- [10] IETF RFC 4103: "RTP-Text. RTP Payload for Text Conversation". +- [11] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [12] 3GPP TS 26.226: "CTM Cellular Text telephony Modem, General description". +- [13] ITU-T Recommendation F.703: "Multimedia Conversation Service Description (2000)". +- [14] 3GPP TS 26.235: "Codec for packet switched conversation". +- [15] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". + +- [16] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols - Stage 3". +- [17] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [18] 3GPP TS 29.163: "Interworking between the IM CN subsystem and CS networks - Stage 3". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Total Conversation:** A service offering standardised simultaneous text, video and voice conversation or a subset thereof (see ITU-T Recommendation F.703 [13]). + +**Host environment:** The session environment where the text component is added. e.g. Circuit switched voice, IP Multimedia, etc. + +**Text Conversation:** A real time conversation in text with transmission character by character as entered. + +## 3.2 Abbreviations + +For the purposes of this document the following abbreviations apply in addition to those defined in TS 22.226 [3]: + +| | | +|-------|---------------------------------------------------------------| +| GTT | Global Text Telephony | +| CTM | Cellular Text telephone Modem, as specified in TS 26.226 [12] | +| BCSM | Basic Call State Model | +| CAMEL | Customised Application for Mobile Enhanced Logic | +| CAP | CAMEL Application Protocol | +| CLIP | Calling Line Presentation | +| CPC | Calling Party Category | +| GMSC | Gateway MSC | +| HPLMN | Home PLMN | +| ISUP | ISDN User Part | +| MSC | Mobile Switching Centre | +| MSRN | Mobile Station Roaming Number | +| NDC | National Destination Code | +| PLMN | Public Land Mobile Network | +| SK | Service Key | +| TRAU | Transcoder and Rate Adaption Unit | +| UMTS | Universal Mobile Telecommunication System | +| VLR | Visited Location Register | + +# 4 General Functions + +## 4.1 Overview + +![Figure 1: General view of GTT feature provision within the different networks. The diagram shows a central 'GTT Environment' (shaded oval) containing two 'Cellular Network' clouds. Inside this environment are 'Mobile, text capable terminals' (represented by a mobile phone and a laptop). Outside the environment, a 'Fixed Network' cloud connects to a 'Fixed textphone user' (represented by a desktop computer and a textphone icon) and a 'Fixed multimedia user' (represented by a desktop computer and a monitor icon). An 'IP network' cloud connects to an 'IP textphone or multimedia user' (represented by a desktop computer and a monitor icon). Arrows indicate connections between the users and the networks, and between the networks and the GTT Environment.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +Figure 1: General view of GTT feature provision within the different networks. The diagram shows a central 'GTT Environment' (shaded oval) containing two 'Cellular Network' clouds. Inside this environment are 'Mobile, text capable terminals' (represented by a mobile phone and a laptop). Outside the environment, a 'Fixed Network' cloud connects to a 'Fixed textphone user' (represented by a desktop computer and a textphone icon) and a 'Fixed multimedia user' (represented by a desktop computer and a monitor icon). An 'IP network' cloud connects to an 'IP textphone or multimedia user' (represented by a desktop computer and a monitor icon). Arrows indicate connections between the users and the networks, and between the networks and the GTT Environment. + +**Figure 1: General view of GTT feature provision within the different networks** + +Figure 1 shows a generalised view of the Global Text Telephony feature architecture for a third generation conversation service system. It shall combine different networks and network types and shall integrate text conversation systems already existent within these networks. + +Global Text Telephony is a 3GPP Feature that can be included in 3GPP conversation services such as circuit switched voice telephony, circuit switched multimedia and IP multimedia conversation. It makes use of the infrastructure of the host environment and includes elements necessary for GTT in these environments. + +The following description and figures describe the text specific parts and leave out many details of the host environment conversation service where text is included. + +### 4.1.1 General text transmission functions + +On the route from user to user, the text passes a set of functional elements. + +![Figure 2: Call flow for two mobile terminals with the same GTT transport method, using text conversation. The diagram shows a sequence of functional blocks for text transmission. The top row (User side) consists of: 'Text User Interface' ↔ 'Text presentation coding' ↔ 'Detection/Activation/Text Transport' (shaded) ↔ 'Multiplexing/Transmission'. The bottom row (Network side) consists of: 'Multiplexing/Transmission' ↔ 'Detection/Activation/Text Transport' (shaded) ↔ 'Text Presentation coding' ↔ 'Text User Interface'. A dashed line labeled 'Radio and network Interface' separates the two rows. Arrows show the flow of text from the top row, through the interface, into the bottom row, and finally to the user interface.](3b621c21b0af3a504a28d2547e87138f_img.jpg) + +Figure 2: Call flow for two mobile terminals with the same GTT transport method, using text conversation. The diagram shows a sequence of functional blocks for text transmission. The top row (User side) consists of: 'Text User Interface' ↔ 'Text presentation coding' ↔ 'Detection/Activation/Text Transport' (shaded) ↔ 'Multiplexing/Transmission'. The bottom row (Network side) consists of: 'Multiplexing/Transmission' ↔ 'Detection/Activation/Text Transport' (shaded) ↔ 'Text Presentation coding' ↔ 'Text User Interface'. A dashed line labeled 'Radio and network Interface' separates the two rows. Arrows show the flow of text from the top row, through the interface, into the bottom row, and finally to the user interface. + +**Figure 2: Call flow for two mobile terminals with the same GTT transport method, using text conversation** + +Figure 2 shows the function chain when communicating within the network, between terminals operating in the same mode. + +![Figure 3: GTT general text transmission functions showing interworking. The diagram illustrates the flow of text transmission functions. On the left, a 'Text User Interface' block is connected via a double-headed arrow to a 'Text presentation coding' block. This is followed by a 'Detection/Activation/Text Transport' block (shaded grey), which is connected to a 'Multiplexing/Transmission' block. A line labeled 'Radio and network Interface' connects this 'Multiplexing/Transmission' block to another 'Multiplexing/Transmission' block on the right. This second 'Multiplexing/Transmission' block is connected via a double-headed arrow to another 'Detection/Activation/Text Transport' block (shaded grey), which is then connected to a 'Text Interworking Conversion' block. From this block, an arrow points to a 'Text Capable Terminal' block, with labels 'PSTN', 'Other PLMN', and 'or other host environment' indicating the network types.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Figure 3: GTT general text transmission functions showing interworking. The diagram illustrates the flow of text transmission functions. On the left, a 'Text User Interface' block is connected via a double-headed arrow to a 'Text presentation coding' block. This is followed by a 'Detection/Activation/Text Transport' block (shaded grey), which is connected to a 'Multiplexing/Transmission' block. A line labeled 'Radio and network Interface' connects this 'Multiplexing/Transmission' block to another 'Multiplexing/Transmission' block on the right. This second 'Multiplexing/Transmission' block is connected via a double-headed arrow to another 'Detection/Activation/Text Transport' block (shaded grey), which is then connected to a 'Text Interworking Conversion' block. From this block, an arrow points to a 'Text Capable Terminal' block, with labels 'PSTN', 'Other PLMN', and 'or other host environment' indicating the network types. + +**Figure 3: GTT general text transmission functions showing interworking** + +The view in figure 3 is applicable to transport mechanisms and network environments when communicating in interworking mode between different environments. + +### 4.1.2 Functions + +#### 4.1.2.1 Call Control and text media initiation + +Before text conversation can begin, a call must be established. That is done with general call control functions of the host environment. GTT Elements detect the desire to establish a text channel, select a suitable transport mechanism, and activate transmission functions. + +#### 4.1.2.2 Presentation coding + +The text in GTT shall be coded in a common presentation protocol, ITU-T Recommendation T.140 [5]. If necessary this presentation protocol shall be converted to or from any legacy mode character code used in other networks. + +#### 4.1.2.3 Transport and transmission host environments + +When text transmission is activated, a suitable transmission method in the PLMN is selected. The appropriate method to use is selected according to the call environment. The environments valid for GTT are called GTT Host environments: + +1. IP Multimedia, according to IPMM subsystem with IETF RFC 3261 [11] (SIP). +2. Circuit Switched Multimedia according to 3G.324. +3. Circuit switched voice channel. + +Other methods to establish real time text conversation exist and may be used without further standardisation, using basic communication services of the PLMN. One example: + +Digital data transmission in a data channel can be used for real time text conversation. For cases when only text conversation is wanted, there are a multitude of ways to implement that kind of communication. It can for example be done through a HTML based server, with an already established mainstream mechanisms that do not require text conversation specific functions to be stored in the terminals. An alternative may be to use GSM circuit switched data functions for text telephones that are compatible with the modem characteristics provided. + +#### 4.1.2.4 Multiplexing + +The text transport is multiplexed in the network and radio interface according to normal procedures for the selected host environment. + +#### 4.1.2.5 Conversion + +For text conversation with text telephones and text capable terminals in different networks or using different transport mechanisms, conversion functions may be used. Functions and procedures suitable for the conversion functions are described in ITU-T Recommendation H.248.2, packages for Text telephony, Text Conversation and Call Type Discrimination [9]. + +#### 4.1.2.6 Text capable terminal + +By using the described GTT functions, a real time text conversation session can be conducted between GTT supported mobile Text Capable Terminals.. Different terminal function combinations and GTT host environments give different opportunities regarding combinations of text with voice and video. Valid combinations are: + +- text only, +- alternating text and voice, +- simultaneous text and voice, +- simultaneous text and video, +- simultaneous text, video and voice. + +#### 4.1.2.7 Routing and location of CTM detection/conversion functions + +There are three ways to include conversion functions between legacy text telephony and CTM. + +- The “All transcoder solution”. +The CTM detection/conversion can be carried out within the transcoder function or within a separate node associated with the transcoder function. This approach means that no specific routing is required since the CTM detection/conversion function will be present in every speech call. Further explanations are found in Annex A. +- The “CTM circuit pool solution”. +The CTM detection/conversion function can be located in a dedicated resource pool in the access network or can be associated with transcoders in the core network. In these cases, the MSC/MSC Server requires an indication from the terminal that this CTM detection/conversion function is required. See TS 24.008 [16] for the definition of this indication. This indication provides the necessary information to invoke the CTM detection/conversion function. TS 48.008 [15] defines mechanisms for pool identities and selection. Further explanations are found in Annex B. +- The “CTM-SRF core network node solution”. +The CTM detection/conversion function can be placed in the core network as a separate CTM Special Resource Function (CTM-SRF), in which case routing functions are required to make sure calls are routed via the CTM-SRF for CTM detection/conversion. Routing can for example be based on subscriber data or specific call conditions available for MSC routing, e.g. emergency calls. Further explanations are found in Annex C. + +### 4.1.3 Emergency service considerations + +If an operator implementing GTT selects to offer access to Emergency Services through this feature for a specific host environment, the following must be considered. + +If the emergency services only has limited types of text conversation devices, conversion from the users host environment to the one used by the emergency service may be configured. + +If the calling party address and location information are provided in voice emergency calls, this information must be preserved also in text emergency calls, and not changed by any conversion or routing mechanisms introduced. + +Other host environment specific considerations for emergency calls are described in sections below. + +# --- 5 Considerations for each host environment + +## 5.1 GTT-IP: IP Multimedia + +### 5.1.0 GTT-IP + +IP Multimedia, supported by the IPMM subsystem, is a suitable environment for real time text conversation. GTT-IP stands for the Text Telephony in IMS via the Real-Time Text protocol over RTP. It shall use IETF SIP [11] for the negotiation of the text media and IETF RFC 4103 [10] RTP-text for transport, with text coded according to ITU-T Recommendation T.140 [5] as indicated in TS 26.235 [14]. This allows conversation in a selection of simultaneous media, such as voice, text and potentially also video. + +Inclusion of the text conversation shall be done according to normal SIP and IPMM procedures, where the text media stream is handled as any other media. GTT-IP has no architecture influence on the 3G-PS network, only that the components must allow handling of the standardised text media stream. + +NOTE: This way of using mainstream procedures opens possibilities to utilize the flexibility of the SIP protocol for enhanced services. The user can interact in the service offering to optimise the stream handling. This may be used for flexible ways of invoking relay services for media conversion according to the desire of the users. + +### 5.1.1 Interworking between Real-Time Text and PSTN Text Telephony + +Interworking between Real-Time Text (RTT) and PSTN text telephony is provided by introducing conversion in the IMS-PLMN between IP-based Real-Time Text via RTP and modem based transmission of real-time text using ITU-T Recommendation V.18 [4] or any of its specific sub-modes. See TS 26.114 [17]. + +The conversion function can be seen as a context containing a Text/RTP termination plus a voice/RTP termination and an ITU-T Recommendation V.18 [4] text telephony termination with multiplexed V.18 and voice via PCM. + +It can be symbolically documented as follows. + +![Diagram illustrating the interworking between Real-Time Text (RTT) and PSTN Text Telephony. A PS-Client (containing Text/RTP and Voice/RTP) connects to a PS-Network. The PS-Network connects to an MGCF/IMS-MGW, which contains four conversion blocks: Text/RTP to Text/V18/PCM, Voice/RTP to Voice/PCM, Text/V18/PCM to Text/RTP, and Voice/PCM to Voice/RTP. The MGCF/IMS-MGW connects to a PSTN, which in turn connects to a legacy TTY phone (containing V18/PCM + Voice/PCM).](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +``` + +graph LR + subgraph PS_Client [PS-Client] + direction TB + TR[Text/RTP] + VR[Voice/RTP] + end + PS_Net((PS-Network)) + subgraph MGCF_IMS_MGW [MGCF/IMS-MGW] + direction LR + TR1[Text/RTP] <--> TV18P[Text/V18/PCM] + VR1[Voice/RTP] <--> VP[Voice/PCM] + TV18P <--> TR1 + VP <--> VR1 + end + PSTN((PSTN)) + subgraph Legacy_TTY [legacy TTY phone] + direction TB + V18P[V18/PCM + Voice/PCM] + end + + PS_Client <--> PS_Net + PS_Net <--> MGCF_IMS_MGW + MGCF_IMS_MGW <--> PSTN + PSTN <--> Legacy_TTY + +``` + +Diagram illustrating the interworking between Real-Time Text (RTT) and PSTN Text Telephony. A PS-Client (containing Text/RTP and Voice/RTP) connects to a PS-Network. The PS-Network connects to an MGCF/IMS-MGW, which contains four conversion blocks: Text/RTP to Text/V18/PCM, Voice/RTP to Voice/PCM, Text/V18/PCM to Text/RTP, and Voice/PCM to Voice/RTP. The MGCF/IMS-MGW connects to a PSTN, which in turn connects to a legacy TTY phone (containing V18/PCM + Voice/PCM). + +Figure 5.1.1.1: Interworking with PSTN + +If the mobile terminal requests Real-Time Text telephony, the call shall be setup with the RTT media type in parallel to the voice media, and the MGCF / IMS-MGW shall insert the Interworking function between RTT and V.18. On the contrary, if the mobile does not request RTT support, no Interworking function is necessary (which would represent majority of calls). + +Functional details of the interworking between Real-time text and PSTN Text telephony are specified in TS 29.163 [18]. + +### 5.1.2 Emergency call considerations for GTT-IP + +Regional regulatory rules may require the capability to let a user use any Real-time text capable mobile terminal for a text call to emergency services on the PSTN. This is an example of interworking from Real-time text to the PSTN. + +Depending on local regulation and operator's policy, it may also be required to support emergency calls originated by a SIM-less UE or a UE without a valid subscription. In these cases RTT / V.18 interworking shall be supported as in case of emergency calls for UE with a valid UICC. + +Call back from emergency services is handled as Mobile Terminating calls as specified in clause 5.1.1. + +## 5.2 GTT-CS: Circuit switched Multimedia + +Text conversation in Circuit Switched Multimedia is called GTT-CS. The host environment is 3G.324, according to TS 26.110 [6] Codec for circuit switched multimedia. GTT-CS Text is ITU-T Recommendation T.140 [5] coded and transported in an AL1 channel. Any combination of Video, Text and Voice can be supported and used simultaneously. + +GTT-CS has no architecture implications on the 3G network, only that the network components must allow the standardised handling of the text media channel as well as any other media channel. + +## 5.3 GTT-Voice: Circuit switched voice channel + +Voice channel transmission of text shall use CTM; Cellular Text telephone Modem, TS 26.226 [12]. It is possible to alternate between text and voice. Text shall be coded according to ITU-T Recommendation T.140 [5] on the presentation level. + +### 5.3.1 Interworking between GTT-Voice and PSTN Text Telephony + +If GTT-Voice is provided, interworking to PSTN text telephony can be provided by introducing conversion in the PLMN between CTM and PSTN based text telephony using ITU-T Recommendation V.18 [4] or any of its specific sub-modes. + +A simple extension can be made of the conversion functionality described in H.248.2 [9]. CTM is included among the transport mechanisms by an extension of package txc. + +For the CTM and PSTN text telephone case, a conversion function can be seen as a context containing a CTM termination and a ITU-T Recommendation V.18 [4] text telephony termination. This combination is called the CTM channel. It is foreseen that the CTM channel need control to be initiated to the proper state for each call etc. Such functions are here collected in an entity called interworking control. + +The CTM channels are normally transparent but monitoring for text telephone signals or CTM signals. When a signal is discovered, the audio path is stopped and character conversion and transmission performed. + +It can be symbolically documented as follows. + +![Figure 4: Interworking with PSTN. The diagram shows two network architectures for interworking. The top architecture shows a 'Wireless text capable terminal' connected to a 'Radio network' containing 'CTM' and 'V18 or subset' blocks, which is then connected to a 'Core network', 'PSTN', and finally a 'Land based text telephone'. The bottom architecture shows the same components but with the 'CTM' and 'V18 or subset' blocks located within the 'Core network' instead of the 'Radio network'.](63e0c22852c26699d0bd095a2d796bab_img.jpg) + +``` + +graph LR + subgraph Top_Arch [Top Architecture] + WTC[Wireless text capable terminal] <--> RN1((Radio network)) + subgraph RN1 + CTM1[CTM] <--> V18S1[V18 or subset] + end + RN1 <--> CN1((Core network)) + CN1 <--> PSTN1((PSTN)) + PSTN1 <--> LTT1[Land based text telephone] + end + subgraph Bottom_Arch [Bottom Architecture] + WTC2[Wireless text capable terminal] <--> RN2((Radio network)) + RN2 <--> CN2((Core network)) + subgraph CN2 + CTM2[CTM] <--> V18S2[V18 or subset] + end + CN2 <--> PSTN2((PSTN)) + PSTN2 <--> LTT2[Land based text telephone] + end + +``` + +Figure 4: Interworking with PSTN. The diagram shows two network architectures for interworking. The top architecture shows a 'Wireless text capable terminal' connected to a 'Radio network' containing 'CTM' and 'V18 or subset' blocks, which is then connected to a 'Core network', 'PSTN', and finally a 'Land based text telephone'. The bottom architecture shows the same components but with the 'CTM' and 'V18 or subset' blocks located within the 'Core network' instead of the 'Radio network'. + +**Figure 4: Interworking with PSTN** + +Since the PSTN text telephone protocols have states, resetting the state during the call should be avoided because it can cause loss or corruption of characters, loss of communication or a long ITU-T Recommendation V.18 [4] handshake before reestablishment. + +For the CTM-SRF core network node solution, already standardised routing and invocation mechanisms should be used to invoke CTM detection/conversion in the calls that may require text conversation. + +The mechanisms for invocation of the CTM channel act on both Mobile Originating calls and Mobile Terminated calls. + +### 5.3.2 Functional details of fixed network interworking + +The default action of the call path in the CTM-detection/conversion function is to transfer audio transparently while monitoring for text telephone signals. When valid text telephone signals are detected, the converting action of the channel takes effect. The path converts between the detected PSTN text telephone method and CTM. This mode of operation continues until text signalling ceases. Then transparent audio transport is re-established, again monitoring for + +text signals. This way of action allows alternating use of text and voice during the call according to established conventions in text telephony. + +TS 26.226 [3] describes the details of CTM and an indication of how CTM can be combined with a text telephone modem to compose a conversion function in the call path. + +ITU-T Recommendation H.248.2 [9] describes the principles of conversion between PSTN Text telephony as in the text telephone ITU-T Recommendation V.18 [4] and any general real time text conversation feature. So, even if CTM is not mentioned in that Recommendation, its general descriptions are valid for this case. On the PSTN end it is valid also for specific sub-modes of ITU-T Recommendation V.18 [4] (Including the US method Baudot 45). The handling is slightly different depending on if the selected ITU-T Recommendation V.18 [4] sub-mode is carrier-based or carrier-less, and if the call is known to be with a textphone or being general. + +The descriptions in ITU-T Recommendation H.248.2 [9] can be taken as functional descriptions of the call path without full implementation in a H.248 environment. + +### 5.3.3 Emergency call considerations for GTT-Voice + +It may be required to let a user use any CTM capable mobile terminal for a text call to the emergency service. If a terminal can support CTM and establishes a call with the CTM active then it will be expected to provide the network with an indication that a CTM detection/conversion function is required in the network. + +It may be required to handle emergency calls also when the call comes from a SIM-less phone or a phone with an invalid subscription. To meet this requirement, one configuration option, when the CTM-SRF is used, shall be to route emergency calls independent of subscription status through the CTM detection/conversion function. + +If the terminal supports CTM and is SIM-less, then it will be expected to indicate to the core network that CTM detection/conversion is required in the network. + +Call back from emergency services is handled as normal Mobile Terminating calls. + +### 5.3.4 Interworking aspects + +The following are known interworking issues between the different circuit switched voice solutions, and these should be considered carefully before deploying different approaches within one PLMN or regulatory area: + +- It is critical that all mobile terminals requiring CTM detection/conversion indicate to the network when CTM is required, otherwise a network that has adopted the CTM circuit pooling solution will not be able to allocate the appropriate CTM capable circuit. This CTM indication should therefore be considered a mandatory terminal requirement. +- An indication from a mobile terminal that CTM detection/conversion is required will not result in any interworking issues if the indication is received by a network where all the transcoders are CTM capable or where a core network CTM-SRF solution has been chosen. This is because the indication is redundant in this case. +- If a subscriber, from a network where all the transcoders are CTM capable or a CTM circuit pooling solution has been adopted, roams to a network where a core network CTM-SRF solution has been chosen, then the subscriber will only receive CTM conversion for emergency calls. The reason is that the subscriber lacks the necessary subscription to a CAMEL service, which would route this normal call via a core network CTM-SRF. +- In the case where inter-MSC handover occurs between an MSC where all the transcoders are CTM capable or a CTM circuit pooling approach is in operation, and an MSC which relies on a core network CTM-SRF, then the subscriber will lose CTM conversion for all calls. + +If a subscriber from a network where a core network CTM-SRF solution has been adopted roams to a network where all the transcoders are CTM capable or a CTM circuit pooling solution has been chosen, then the subscriber will receive CTM conversion for all calls. The presence of two CTM detection/conversion functions in tandem should not create any interworking issues. + +# Annex A (informative): GTT-Voice specific information for CTM support in, or associated with, all transcoders + +## A.1 GTT-Voice specific information for CTM support in, or associated with, all transcoders in the access network for GSM networks with A-interface + +The CTM detection/conversion function may be incorporated in all transcoders where CTM activity can realistically be expected. It is also an option to incorporate a CTM detection/conversion function in a separate entity associated with the Transcoder. + +The CTM adapter automatically detects the presence of CTM encoding and provides the necessary conversion to the appropriate ITU-T Recommendation V.18 [4] modem encoding. + +![Diagram illustrating the association of a CTM adapter with the transcoder in the access network. A CTM capable Mobile (represented by a mobile phone icon) is connected to a BSC/Transcoder (orange box) via a radio interface. The mobile sends CTM data (indicated by a speech bubble) to the BSC/Transcoder. The BSC/Transcoder is connected to a CTM adapter (yellow box) via a dashed line. The CTM adapter is connected to an MSC (orange box) via a solid line. The MSC is connected to a PSTN (blue cloud) via a solid line. The PSTN is connected to a terminal (represented by a fax machine icon) via a solid line. The mobile also sends V.18 data (indicated by a speech bubble) to the BSC/Transcoder. The BSC/Transcoder sends V.18 data (indicated by a speech bubble) to the CTM adapter. The CTM adapter sends V.18 data (indicated by a speech bubble) to the MSC. The MSC sends V.18 data (indicated by a speech bubble) to the PSTN. The PSTN sends V.18 data (indicated by a speech bubble) to the terminal.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +Diagram illustrating the association of a CTM adapter with the transcoder in the access network. A CTM capable Mobile (represented by a mobile phone icon) is connected to a BSC/Transcoder (orange box) via a radio interface. The mobile sends CTM data (indicated by a speech bubble) to the BSC/Transcoder. The BSC/Transcoder is connected to a CTM adapter (yellow box) via a dashed line. The CTM adapter is connected to an MSC (orange box) via a solid line. The MSC is connected to a PSTN (blue cloud) via a solid line. The PSTN is connected to a terminal (represented by a fax machine icon) via a solid line. The mobile also sends V.18 data (indicated by a speech bubble) to the BSC/Transcoder. The BSC/Transcoder sends V.18 data (indicated by a speech bubble) to the CTM adapter. The CTM adapter sends V.18 data (indicated by a speech bubble) to the MSC. The MSC sends V.18 data (indicated by a speech bubble) to the PSTN. The PSTN sends V.18 data (indicated by a speech bubble) to the terminal. + +Figure A.1: Association of a CTM adapter with the transcoder in the access network + +Due to the presence of the CTM detection/conversion function in all circuits, no CTM capability information needs to be signalled to the network by the mobile. + +## A.2 GTT-Voice specific information for CTM support in or associated with all transcoders in the core network for networks supporting the Iu interface + +For networks with GERAN and UTRAN radio access using the Iu interface, the CTM detection/conversion function may be incorporated in all transcoders where CTM activity can realistically be expected. It is also an option to incorporate a CTM detection/conversion function in separate entity associated with the Transcoder. + +The CTM adapter automatically detects the presence of CTM encoding and provides the necessary conversion to the appropriate ITU-T Recommendation V.18 [4] modem encoding. + +![Diagram showing the association of a CTM adapter with the transcoder in the core network. A CTM capable Mobile connects to a RAN server via CTM and V.18 protocols. The RAN server connects to an MGW/Transcoder, which is controlled by an MSC server. The MGW/Transcoder is associated with a CTM adapter. The CTM adapter connects to the PSTN via V.18 protocols, which then connects to a terminal via V.18.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The diagram illustrates a network architecture for CTM (Compression Type Management). On the left, a 'CTM capable Mobile' (represented by a mobile phone icon) is connected to a 'RAN server' (green box). The mobile has two connection paths: one labeled 'CTM' and another labeled 'V.18'. The 'RAN server' is connected to an 'MGW/Transcoder' (orange box) and is also labeled 'CTM'. The 'MGW/Transcoder' is connected to an 'MSC server' (orange box) and is associated with a 'CTM adapter' (yellow box) via a dashed line. The 'CTM adapter' is connected to the 'PSTN' (blue cloud). The 'PSTN' has two connection paths: one labeled 'V.18' leading to a terminal (represented by a fax machine icon) and another labeled 'V.18' leading to another terminal (represented by a fax machine icon). + +Diagram showing the association of a CTM adapter with the transcoder in the core network. A CTM capable Mobile connects to a RAN server via CTM and V.18 protocols. The RAN server connects to an MGW/Transcoder, which is controlled by an MSC server. The MGW/Transcoder is associated with a CTM adapter. The CTM adapter connects to the PSTN via V.18 protocols, which then connects to a terminal via V.18. + +**Figure A.2: Association of a CTM adapter with the transcoder in the core network** + +Due to the presence of the CTM detection/conversion function in all circuits, no CTM capability information needs to be signalled to the network by the mobile. + +# Annex B (informative): GTT-Voice support via selection of CTM detection / conversion function + +## B.1 GTT-Voice specific information for CTM support in GSM networks with A-interface, via access network circuit pooling + +A-interface pooling, and routing to a selected pool, is an intrinsic capability within current GSM Networks and is used to select transcoding for EFR, FR and in future AMR. It is an option to create circuit pools on the A-interface, which support the CTM detection/conversion. The circuit pools are defined in TS 48.008 [15]. These pools may be incorporated in the transcoder, in a separate entity associated with a transcoder or in a separate entity located in particular A-interface circuits but remote from the transcoder. + +The main steps of the process for a mobile originated call are: + +- Setup from terminal, including CTM indication. + +MSC detects CTM indication and allocates a circuit with CTM capabilities. + +The main steps of the process for a mobile terminated call are: + +- Setup from MSC. +- Call Confirm from terminal including CTM indication. + +MSC detects CTM indication and allocates a circuit with CTM capabilities. + +![Diagram illustrating the CTM adaptor contained within a transcoder pool. A CTM capable Mobile (represented by a mobile phone icon) is connected to a BSC (Base Station Controller). The BSC is connected to a Transcoder Circuit Pool, which contains a CTM adapter. The Transcoder Circuit Pool is connected to an MSC (Mobile Switching Center). The MSC is connected to a PSTN (Packet Switched Network). The CTM capable Mobile is also connected to a terminal (represented by a computer icon). The CTM capable Mobile and the terminal are both labeled with 'V.18'. The BSC is labeled with 'CTM'. The Transcoder Circuit Pool is labeled with 'V.18'. The MSC is labeled with 'V.18'. The PSTN is labeled with 'V.18'.](df1d0e45191302de72176e4390224c16_img.jpg) + +Diagram illustrating the CTM adaptor contained within a transcoder pool. A CTM capable Mobile (represented by a mobile phone icon) is connected to a BSC (Base Station Controller). The BSC is connected to a Transcoder Circuit Pool, which contains a CTM adapter. The Transcoder Circuit Pool is connected to an MSC (Mobile Switching Center). The MSC is connected to a PSTN (Packet Switched Network). The CTM capable Mobile is also connected to a terminal (represented by a computer icon). The CTM capable Mobile and the terminal are both labeled with 'V.18'. The BSC is labeled with 'CTM'. The Transcoder Circuit Pool is labeled with 'V.18'. The MSC is labeled with 'V.18'. The PSTN is labeled with 'V.18'. + +Figure B.1: CTM adaptor contained within a transcoder pool + +![Diagram illustrating the CTM adapter present on specific A-interface circuits. A CTM capable Mobile (represented by a mobile phone icon) is connected to a BSC/Transcoder (orange box) via an antenna. The mobile sends CTM and V.18 signals. The BSC/Transcoder is connected to a CTM adapter (yellow box) via a dashed line. The CTM adapter is connected to an MSC (orange box) via a solid line. The MSC is connected to a PSTN (blue cloud) via a solid line. The PSTN is connected to a fax machine (black icon) via a solid line. The fax machine sends V.18 signals. A callout box points to the connection between the CTM adapter and the MSC, stating 'Circuit where CTM detection/conversion is not available'.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Diagram illustrating the CTM adapter present on specific A-interface circuits. A CTM capable Mobile (represented by a mobile phone icon) is connected to a BSC/Transcoder (orange box) via an antenna. The mobile sends CTM and V.18 signals. The BSC/Transcoder is connected to a CTM adapter (yellow box) via a dashed line. The CTM adapter is connected to an MSC (orange box) via a solid line. The MSC is connected to a PSTN (blue cloud) via a solid line. The PSTN is connected to a fax machine (black icon) via a solid line. The fax machine sends V.18 signals. A callout box points to the connection between the CTM adapter and the MSC, stating 'Circuit where CTM detection/conversion is not available'. + +Figure B.2: CTM adapter present on specific A-interface circuits + +## B.2 GTT-Voice specific information for CTM support via core network termination selection for networks using Iu interface + +For networks with GERAN and UTRAN radio access using the Iu interface, a method to allocate the calls to terminations capable of handling CTM on audio channels can be provided in the core network. It can be based on the mechanisms for controlling Media Gateway functions through the control language specified on the Mc interface. The MSC Server has information on CTM indication issued by the mobile station and allocates terminations with proper CTM capabilities for the detection/conversion during the call. + +The main steps of the process for a mobile originated call are: + +- Setup from terminal, including CTM indication + +MSC server detects CTM indication and allocates a termination with CTM capabilities in the Media Gateway. + +The main steps of the process for a mobile terminated call are: + +- Setup from the MSC Server. +- Call Confirm from the terminal including CTM indication. +- The MSC server detects CTM indication and allocates a termination with CTM capabilities in the Media Gateway. + +![Diagram showing the association of a CTM capable termination within the Media Gateway. It includes components: CTM capable Mobile, RAN server, MSC server, MGW/Transcoder, CTM adapter, and PSTN. Callouts indicate CTM and V.18 capabilities at various points.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates a network architecture for CTM (Caption Transfer Mode) capable mobile communications. On the left, a 'CTM capable Mobile' device is shown with a 'V.18' callout, connected to a 'RAN server'. Above the mobile device, there are two 'CTM' callouts, one of which is associated with an 'H' (Home) symbol. The 'RAN server' is connected to an 'MSC server' and an 'MGW/Transcoder'. The 'MSC server' is also connected to the 'MGW/Transcoder'. The 'MGW/Transcoder' is connected to a 'CTM adapter'. The 'CTM adapter' is connected to the 'PSTN' (Packet Switched Network), which is represented by a cloud icon. Below the PSTN cloud, there is a 'V.18' callout and an icon of a fax machine. Another 'V.18' callout is shown between the 'CTM adapter' and the 'PSTN' cloud. The 'MGW/Transcoder' and 'CTM adapter' are enclosed in a dashed box. + +Diagram showing the association of a CTM capable termination within the Media Gateway. It includes components: CTM capable Mobile, RAN server, MSC server, MGW/Transcoder, CTM adapter, and PSTN. Callouts indicate CTM and V.18 capabilities at various points. + +Figure B.3: Association of a CTM capable termination within the Media Gateway + +# Annex C (Informative): GTT-Voice specific information for the CTM-SRF core network node solution + +This section describes a method how to route possible text calls via a core network node called the CTM-SRF. It should be taken as an informative example. It is based on CAMEL Phase 1 and call signalling with ISUP. Other call control environments and other IN service platforms can accomplish the same result. + +This section shows how emergency calls, terminating calls and originating calls can be routed through the CTM-SRF node without any modification to existing core network nodes. This covers also mobile-to-mobile calls. + +For cases where emergency call support for text calls is wanted, all emergency calls are routed to the CTM-SRF server. The CTM-SRF server routes the call to the emergency centre. This can be done, as the CTM/textphone conversion channel itself is transparent to speech. + +Originating and terminating calls, from and to possible text telephone users, are handled as CAMEL calls. A CAMEL service assures that the calls are routed through the CTM-SRF node by actions of a CAMEL application. + +## C.1 Emergency calls + +The network has no means to distinguish text emergency calls from voice emergency calls in areas where the same number is used for both types. It may also be desired that even a phone borrowed for the purpose of making a text emergency call shall get the text service without any specific text subscription. Therefore, in order to meet these requirements, it shall be possible to configure the network to route all emergency calls through CTM-SRF server nodes. + +![Diagram of emergency call routing showing a path from node A through an MSC/VLR, a CTM-SRF Server, and a Transit network to node B.](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) + +``` +graph TD; A[A] -- 1 --> MSC[MSC/VLR]; MSC -- 2 --> CTM[CTM-SRF Server]; CTM -- 3 --> Transit((Transit network)); Transit -- 4 --> B[B]; +``` + +The diagram illustrates the routing path for an emergency call. It starts at node A, which is connected to an MSC/VLR (step 1). The MSC/VLR then routes the call to a CTM-SRF Server (step 2). The CTM-SRF Server routes the call to a Transit network (step 3), which in turn routes the call to node B (step 4). + +Diagram of emergency call routing showing a path from node A through an MSC/VLR, a CTM-SRF Server, and a Transit network to node B. + +**Figure C.1: Emergency call routing** + +If the emergency service use the same number for emergency text calls as for emergency voice calls, routing of all calls, regardless of text or speech, to a CTM-SRF server can be accomplished by configuration in the MSC/VLRs. The MSC/VLR can be configured in a way that, depending on the Emergency Centre addresses, emergency calls are always routed via a CTM-SRF server. + +The CTM-SRF links in the CTM/textphone conversion function and routes the call further according to the received IAM. + +The CTM-SRF node could recognise emergency calls by knowing all numbers of the emergency centres in question. + +For US E-911-calls an additional method is given by looking at the CPC field. A special value is given. + +- CPC "H'E0" represents "emergency service call". + +In general, the CTM-SRF server handles emergency calls in the same way as normal Mobile originated calls. + +## C.2 Routing of regular user calls + +Regular user calls that may contain text are routed to the CTM-SRF by a CAMEL service. + +Text users are identified by a Text Telephony CAMEL Service Key (SK) and other CAMEL information stored in the HLR. The CTM part of this service modifies the Called Party Address (see following chapters). The call is routed through the CTM-SRF server and is then routed to the original destination. + +### C.2.1 Mobile Terminating calls + +![Diagram showing the routing paths for mobile terminating text calls. The diagram includes four main components: MSC/VLR (top left), HLR (top right), CTM-SCP (middle left, triangle), and GMSC (middle right, circle). A CTM-SRF Server (bottom left) is also shown. Arrows indicate signaling and data flow. Thick arrows represent the call path: from an external source to the GMSC, then to the CTM-SRF Server, then to the CTM-SCP, then to the MSC/VLR, and finally to the destination. Thin arrows represent other signaling: GMSC to HLR, HLR to GMSC, GMSC to MSC/VLR, MSC/VLR to HLR, CTM-SCP to GMSC, and CTM-SRF Server to GMSC.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +Diagram showing the routing paths for mobile terminating text calls. The diagram includes four main components: MSC/VLR (top left), HLR (top right), CTM-SCP (middle left, triangle), and GMSC (middle right, circle). A CTM-SRF Server (bottom left) is also shown. Arrows indicate signaling and data flow. Thick arrows represent the call path: from an external source to the GMSC, then to the CTM-SRF Server, then to the CTM-SCP, then to the MSC/VLR, and finally to the destination. Thin arrows represent other signaling: GMSC to HLR, HLR to GMSC, GMSC to MSC/VLR, MSC/VLR to HLR, CTM-SCP to GMSC, and CTM-SRF Server to GMSC. + +**Figure C.2: Paths for routing of mobile terminating text calls with call path shown in thick arrows** + +The GMSC discovers that the user is a subscriber of the text telephony service, by the Camel Subscription Information information received from the HLR. The text Service Key is present and the Detection Point = Terminating\_Attempt\_Authorized. + +The SCP with the text telephony service application is connected and the routing of the call through the CTM-SRF node is performed. + +To control the activation of CAMEL service invocations an indication is sent from the CAMEL service via the CTM-SRF server back to the CAMEL service. This information is used by the CAMEL CTM-SCP service (2<sup>nd</sup> invocation) to do nothing but just to continue the call. + +The indication is carried in the Calling Party Category parameter of ISUP. + +This ISUP parameter is supported in CAP V1. InitialDP, and Connect. The CTM-SRF node and the CAMEL CTM-SCP service form an integrated application, and this ISUP parameter handling is regarded internal application signalling. + +**Figure C.3: Mobile Terminating Text Call** + +For the support of text users, the CAMEL CTM-SCP service will return the textphone-number with a CTM-SRF server prefix in CAP\_CONNECT. The GMSC creates a new O-BCSM for this CAMEL based forwarding leg. It uses the Destination Routing Address in CAP\_CONNECT to do the routing and to send the ISUP\_IAM. The routing is based on the CTM-SRF server prefix part. + +The CTM-SRF server links in the CTM/textphone conversion function and extracts Text subscriber address, Nature of Address, and the Numbering Plan Indicator from the Destination Routing Address parameter. It stores the original CPC + +value in Additional Calling Party Number parameter. If Called Party's Category is not received, then this information as such is encoded. It writes this information to the appropriate IAM parameters and routes the call to a GMSC. It could be the same GMSC as before or a different one. + +The GMSC regards this incoming IAM as a new terminating call to a text subscriber. A second time a dialogue for the "same text call" to a CAMEL service is invoked. The service realises this fact and does nothing but connecting the call to the Text subscriber (Called Party Number, respectively Destination Routing Address has not been changed by the CTM-SRF server). + +### C.2.2 Mobile originating calls + +![Mobile originating call routing overview diagram](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +``` +graph LR; A[A] --> MSC_VLR[MSC/VLR]; MSC_VLR <--> CTM_SCP{CTM-SCP}; MSC_VLR --> CTM_SRF[CTM-SRF Server]; CTM_SRF --> Transit((Transit network)); Transit --> B[B]; +``` + +The diagram illustrates the mobile originating call routing process. It starts with a mobile station (A) sending a call to the MSC/VLR. The MSC/VLR has a bidirectional connection to the CTM-SCP and a unidirectional connection to the CTM-SRF Server. The CTM-SRF Server then routes the call to a Transit network, which in turn routes it to the destination (B). + +Mobile originating call routing overview diagram + +**Figure C.4: Mobile originating call routing overview** + +The following sequence chart shows the mobile originating traffic case. + +![Sequence diagram for Mobile Originating Text Call showing interactions between (V)MSC/VLR/SSF, SCP, and CTM.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant (V)MSC/VLR/SSF + participant SCP + participant CTM + + Note left of (V)MSC/VLR/SSF: DTAP_SETUP (Calling Party Address) = TTY-subscriber; Called Party Address = B-subscriber + (V)MSC/VLR/SSF->>SCP: DTAP_CALL_PROCEEDING + Note left of (V)MSC/VLR/SSF: VLR info: O-CSI, SK = CTM service, A-category + (V)MSC/VLR/SSF->>SCP: CAP_INITIAL_DP (SK, Called Party Number) = B-subscriber + Note right of (V)MSC/VLR/SSF: Calling Partys Category = A-category + SCP->>(V)MSC/VLR/SSF: CAP_CONNECT (Destination Routing Address = CTM server + B-subscriber) + Note right of (V)MSC/VLR/SSF: Calling Partys Category = A-category + (V)MSC/VLR/SSF->>CTM: ISUP_IAM (Calling Party Address = TTY-subscriber; Called Party Address = Destination Routing Addr) + Note right of (V)MSC/VLR/SSF: Calling Partys Category = A-category + CTM->>(V)MSC/VLR/SSF: ISUP_IAM (Calling Party Address = TTY-subscriber; Called Party Address = B-subscriber) + Note right of (V)MSC/VLR/SSF: Calling Partys Category = A-category + +``` + +Sequence diagram for Mobile Originating Text Call showing interactions between (V)MSC/VLR/SSF, SCP, and CTM. + +**Figure C.6: Mobile Originating Text Call** + +For normal originating calls the MSC finds the CAMEL text telephony Service Key in the VLR, together with information on the Detection Point = Collection of dialled digits. All non-emergency calls for the user will cause a connection to the text telephone service application in the CTM-SCP. The A-category value from the subscriber data in the VLR is used as CPC value. + +The CAMEL service knows that it is an originating call. In this case it just forwards the Calling Party's Category parameter untouched. + +The CTM-SRF removes its own address digits from the Called Party Address. The CTM/Text telephone conversion function is inserted before the call is routed towards the B-subscriber. + +### C.2.3 Mobile to Mobile Calls + +Two CTM-SRF servers are linked in, one on the originating leg and one on the terminating leg. The originating ISUP\_IAM sent from the CTM-SRF server on the outgoing side is received by the GMSC as normal ISUP\_IAM. + +## C.3 Routing actions of the CTM-SCP + +From the sections above, it can be derived that the following actions are performed in the CAMEL server CTM-SCP acting on the CAP Interface. + +![Flowchart for CTM-SCP Logic for Mobile Terminated case. Detection point = Terminating Attempt Authorized](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +graph TD + A[/CAP_INITIAL_DP/] --> B{Calling Party +Category = "CTM"} + B -- No --> C[Additional Calling Party +Number = Calling Party +Category = "CTM"] + B -- Yes --> D[Calling Party Category += Additional Calling +Party Number] + C --> E[Destination Routing Address = +CTM-SRF (V.18 side)+original +Called Party Number] + D --> F[Additional Calling +Party Number = Null] + E --> G[/CAP_CONNECT/] + F --> H[/CAP_CONNECT/] + +``` + +The flowchart starts with a detection point 'CAP\_INITIAL\_DP'. It then enters a decision diamond 'Calling Party Category = "CTM"'. If 'No', it proceeds to a process box 'Additional Calling Party Number = Calling Party Category = "CTM"', followed by 'Destination Routing Address = CTM-SRF (V.18 side)+original Called Party Number', and finally 'CAP\_CONNECT'. If 'Yes', it proceeds to a process box 'Calling Party Category = Additional Calling Party Number', followed by 'Additional Calling Party Number = Null', and finally 'CAP\_CONNECT'. + +Flowchart for CTM-SCP Logic for Mobile Terminated case. Detection point = Terminating Attempt Authorized + +**Figure C.7: CTM-SCP Logic for Mobile Terminated case. Detection point =Terminating Attempt Authorized** + +![Flowchart for CTM-SCP logic for Mobile Originated case at detection point=Collection of dialled digits](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +``` + +graph TD + A[/CAP_INITIAL_DP/] --> B[Destination Routing Address= +CTM-SRF(CTM side) + +original Called Party Number] + B --> C[/CAP_CONNECT/] + +``` + +The flowchart starts with a detection point 'CAP\_INITIAL\_DP', followed by a process box 'Destination Routing Address= CTM-SRF(CTM side) + original Called Party Number', and ends with 'CAP\_CONNECT'. + +Flowchart for CTM-SCP logic for Mobile Originated case at detection point=Collection of dialled digits + +**Figure C.8: CTM\_SCP logic for Mobile Originated case at detection point=Collection of dialled digits** + +## C.4 Routing actions of the CTM-SRF + +![Flowchart for Mobile terminated calls routing logic in CTM-SRF.](4b87467ad9642943235f48f7d4b59449_img.jpg) + +``` +graph TD; A[/ISUP_IAM/] --> B["Copy all IAM information to outgoing IAM, strip CTM-SRF number from Called Party Address in outgoing In IAM message"]; B --> C["Connect incoming to V.18 side of CTM Channel +Connect outgoing to CTM termination"]; C --> D[/ISUP-IAM/] +``` + +The flowchart illustrates the routing logic for mobile terminated calls in a CTM-SRF. It begins with an incoming ISUP\_IAM message, which is processed by copying all IAM information to the outgoing IAM and stripping the CTM-SRF number from the Called Party Address in the outgoing In IAM message. This is followed by connecting the incoming call to the V.18 side of the CTM Channel and connecting the outgoing call to the CTM termination. The process concludes with an outgoing ISUP-IAM message. + +Flowchart for Mobile terminated calls routing logic in CTM-SRF. + +Figure C.9: Routing logic in CTM-SRF for Mobile terminated calls + +![Flowchart for Mobile Originated calls routing logic in CTM-SRF.](171115f072e42b379238ed0dd438e9d7_img.jpg) + +``` +graph TD; A[/ISUP_IAM/] --> B["Copy all IAM information to outgoing IAM, strip CTM-SRF number from Called Party Address in outgoing IAM message"]; B --> C["Connect incoming to CTM side of CTM Channel +Connect outgoing to V.18 termination"]; C --> D[/ISUP-IAM/] +``` + +The flowchart illustrates the routing logic for mobile originated calls in a CTM-SRF. It begins with an incoming ISUP\_IAM message, which is processed by copying all IAM information to the outgoing IAM and stripping the CTM-SRF number from the Called Party Address in the outgoing IAM message. This is followed by connecting the incoming call to the CTM side of the CTM Channel and connecting the outgoing call to the V.18 termination. The process concludes with an outgoing ISUP-IAM message. + +Flowchart for Mobile Originated calls routing logic in CTM-SRF. + +Figure C.10: Routing logic in CTM-SRF, for Mobile Originated calls + +## --- C.5 Service interactions + +### C.5.1 Interaction with other CAMEL services + +The text users can use other CAMEL services. However, with other CAMEL services using the same Detection Point as the Text Telephone service, the other CAMEL services are impacted when using CAMEL Phase 1 as presented in this document. + +As for the impact on existing CAMEL services, some of the services may be impacted anyway to support text users, for example Prepaid for playing announcement in text telephone signals. + +Every CAMEL service, which is expected to be used by both voice and text users, and use the same CAMEL detection point as the GTT service, is assigned two SKs, one for non-text users and another for text users. For text users the other service logic has to integrate CTM-SCP routing logic. + +### C.5.2 Interactions with Supplementary Services + +In general, no other interactions are expected than described in the CAMEL standard. + +Call Forwarding in GMSC is invoked after terminating CAMEL service invocation. This means the CTM-SRF service node is already linked in the call path. A further invocation of a mobile originated CAMEL based service will cause an additional routing to a CTM-SRF service node. This is needed to convert the text back to text telephone coding, e.g. Baudot, which is required for the following routing towards the forwarded-to-party (C-party). + +### C.5.3 Emergency Call interaction + +New emergency call categories introduced in 3GPP Release 4 (introduced as emergency-call enhancement) have no impact on routing of emergency calls via CTM-SRF server. + +New categories may be specified in order to detect text emergency calls. + +### C.5.4 Usage of Destination Routing Address + +The Destination Routing Address CAMEL parameter is used by the service logic for two purposes. + +- It contains the CTM-SRF server address to let the MSC to route the call to the CTM-SRF server. +- It contains the original B-subscriber address, to let the CTM-SRF server to use it as Called Party Number on the outgoing side. + +When the service logic reconnects the CTM-SRF server, the service has to save the Nature of Address and the Numbering Plan Indicator of the original Called Party Number in the Destination Routing Address parameter. + +CAMEL Phase 1 Destination Routing Address has up to 12 octets. Two octets are needed to encode Nature of Address and the Numbering Plan Indicator. This means that 10 octets are left for CTM-SRF server address digits plus Called Party Address digits. All together 20 digits are given. + +An international one up to 15 digits according E.164. This results in having 5 digits left for CTM-SRF server addressing. + +### C.5.5 Inserting CTM/Text telephone conversion function + +The CTM/Text telephone conversion function is direction oriented. A CTM modem should be connected towards the radio side and a modem for ITU-T Recommendation V.18 [4] or any of its text telephone submodes towards the other direction. Therefore the CTM-SRF server has to distinguish between mobile terminating and mobile originating calls. + +This can be achieved by either allocating different channels for the directions or make decision based on the Called number to the CTM-SRF. + +### C.5.6 Lawful interception + +Depending on where on the route the intercept is made, and also depending on the support for CTM in the terminal, the coding in the intercept point will be transmitted in CTM modulation and coding, or native PSTN text telephone coding and modulation. Both are possible to decode, and a combined decoder can be designed. + +NOTE: In some countries it is required that all PLMN specific codings are decoded before the lawful interception. In this case operators must upgrade their lawful interception equipment. + +# Annex D (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|------|-----|-----|----------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 2004-12 | SP-29 | | - | | | Upgraded to Release 6 | 5.2.0 | 6.0.0 | +| 2006-03 | SP-31 | SP-060139 | 0003 | - | - | Update of three references on real time text | 6.0.0 | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | | Updated to Rel-8 version (MCC) | 7.0.0 | 8.0.0 | +| 2009-12 | SP-46 | SP-090795 | 0005 | 2 | F | Correction to introduce interworking and emergency aspects of GTT-IP | 8.0.0 | 9.0.0 | +| 2011-03 | SP-51 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | <b>11.0.0</b> | +| | | | | | | | | | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23231/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/23_series/23231/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86fe4210774cb76844a3d6cf2fdcdbd33ad2d49b --- /dev/null +++ b/marked/Rel-11/23_series/23231/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:809824bb44ffc68da6b8bda9e1515fbcb92fd93581148df2ce77ae5342c8ee70 +size 228587 diff --git a/marked/Rel-11/23_series/23231/04cfca33e3fc26513abe649d7474f733_img.jpg b/marked/Rel-11/23_series/23231/04cfca33e3fc26513abe649d7474f733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2e2c357a3db5df1843bb1d7064a0dda0bacec85 --- /dev/null +++ b/marked/Rel-11/23_series/23231/04cfca33e3fc26513abe649d7474f733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6204d0143fb1db056ed59da42b30fe0cbc86314df109e78c02da6c41468dc39 +size 92002 diff --git a/marked/Rel-11/23_series/23231/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/Rel-11/23_series/23231/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdb928bb8c2f9c6f071bad601af5ec255b2efcaa --- /dev/null +++ b/marked/Rel-11/23_series/23231/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d7fdceb724c31090923b6cb20b666873a3c6eb85a97970e85905e6502ddb1c1 +size 22188 diff --git a/marked/Rel-11/23_series/23231/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/23_series/23231/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a502d82f1b8c6d7893290421a2df1dafa360e28d --- /dev/null +++ b/marked/Rel-11/23_series/23231/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b566ea4c2b682314feeede2cbed6c6308be4699198fe7167fd67850daf88c3ca +size 119570 diff --git a/marked/Rel-11/23_series/23231/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/23_series/23231/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bc7b382954036d8b96555431041696f7b1cc58d --- /dev/null +++ b/marked/Rel-11/23_series/23231/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:964b2c6d6e1cfddb3aa6dc80dba0eba027c1d51a3568e8ff27ade3b79575b441 +size 121024 diff --git a/marked/Rel-11/23_series/23231/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/23_series/23231/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92bb927f7b4e10d1b7a476cbbd9230ee11225ebc --- /dev/null +++ b/marked/Rel-11/23_series/23231/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0337d8e0aef6cf643d4d4a78572c978e04b2474109d7a3f2dd0d32af00aee7a3 +size 178154 diff --git a/marked/Rel-11/23_series/23231/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/23_series/23231/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb3b30f2ca60a5073c774fd7f0dd2a015b5dbfee --- /dev/null +++ b/marked/Rel-11/23_series/23231/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e9b36e055e3d69ce84ee574e3ae8612eb452b4f36dc07c0922fc6c819ce8117 +size 87389 diff --git a/marked/Rel-11/23_series/23231/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-11/23_series/23231/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9251fa40fc03226b7535b79346be97f75ee0620 --- /dev/null +++ b/marked/Rel-11/23_series/23231/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68bd33671eedfc87929384d074c5c47b98e90ded4f436a31456043cb9ca77063 +size 103471 diff --git a/marked/Rel-11/23_series/23231/376f80eb8a41369e87da63a0210d173e_img.jpg b/marked/Rel-11/23_series/23231/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ffb52686063f5810222b2c9dbbdb51b67bd7d18 --- /dev/null +++ b/marked/Rel-11/23_series/23231/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cbe665d339a0b2d00aa79c29bdbce9957233908f534798ced01e622acdead60 +size 70091 diff --git a/marked/Rel-11/23_series/23231/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-11/23_series/23231/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb3427d9bff637daf9a04cb73e0bdf9951989f78 --- /dev/null +++ b/marked/Rel-11/23_series/23231/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d19e416cb92f35a2728193cc1b38f5e76404cae1e136f31fbdd6082888399dba +size 142949 diff --git a/marked/Rel-11/23_series/23231/4346261cc730a1eb683f35e4ce9deacf_img.jpg b/marked/Rel-11/23_series/23231/4346261cc730a1eb683f35e4ce9deacf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4b0bd2ac190802a72f16418f2b81e3862b08f40 --- /dev/null +++ b/marked/Rel-11/23_series/23231/4346261cc730a1eb683f35e4ce9deacf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f9d300930ee967c5629e9aa8188d36985db94d9f663c172f8999d0edb388fff +size 65952 diff --git a/marked/Rel-11/23_series/23231/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-11/23_series/23231/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7947a17f92d685a2582f7e7512bcdbee33b2036 --- /dev/null +++ b/marked/Rel-11/23_series/23231/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0aeb6abc50af1586d3d9f3f392d82c048e6a9fcc23cc85a3d275d4ba7846ddf2 +size 173662 diff --git a/marked/Rel-11/23_series/23231/54e4bda94c608845a162d52a75e67ce4_img.jpg b/marked/Rel-11/23_series/23231/54e4bda94c608845a162d52a75e67ce4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ccab75b7faeef1a98439a20175e013b6ce03e05 --- /dev/null +++ b/marked/Rel-11/23_series/23231/54e4bda94c608845a162d52a75e67ce4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77aaeabd0858018cb0e199fead706129b521f0211d672d3b975d882dfd8c650a +size 21549 diff --git a/marked/Rel-11/23_series/23231/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23231/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a7fd324af7522127308c19211ad32979eb88856 --- /dev/null +++ b/marked/Rel-11/23_series/23231/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a278a80a9a6d813758d399850c9cd2e20bdbb725239fadb455ba95c1920002a +size 103059 diff --git a/marked/Rel-11/23_series/23231/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/23_series/23231/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70f9c97b0c70b21c635881503c9f4fc45a924975 --- /dev/null +++ b/marked/Rel-11/23_series/23231/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c26f2721f337c24f14a34fe347f95f5de186ccacec7c220288e0e6be8b6bf015 +size 113970 diff --git a/marked/Rel-11/23_series/23231/8c880d6b715587bd710a9ba8414469b1_img.jpg b/marked/Rel-11/23_series/23231/8c880d6b715587bd710a9ba8414469b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d373f7705f375e02150d0cf40ef0b008e3b86f5 --- /dev/null +++ b/marked/Rel-11/23_series/23231/8c880d6b715587bd710a9ba8414469b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b39c3afe980c2352a8efffcd63b72da082a93cd33c5333d4f82363f13240ceac +size 95650 diff --git a/marked/Rel-11/23_series/23231/914919be6b64b1c8bb74e12616c85f71_img.jpg b/marked/Rel-11/23_series/23231/914919be6b64b1c8bb74e12616c85f71_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bc0832734a76888f54fae27683c944553991311 --- /dev/null +++ b/marked/Rel-11/23_series/23231/914919be6b64b1c8bb74e12616c85f71_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fa6e11393efdad92eb86842e632a88bc7c1e1738edb566650fe53dbef2de832 +size 56431 diff --git a/marked/Rel-11/23_series/23231/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-11/23_series/23231/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69b79f9413beae9092ca88971d08e8f7d7b54322 --- /dev/null +++ b/marked/Rel-11/23_series/23231/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fa563151425b7c61d8a7d458b347d4a9ecef2530a18b9d145a0ff744d1ff81d +size 21505 diff --git a/marked/Rel-11/23_series/23231/a4bfa2343d75076b79f7e33d93915e00_img.jpg b/marked/Rel-11/23_series/23231/a4bfa2343d75076b79f7e33d93915e00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58e9744b28ba2ad114d765f91dc1be6d7aace4f4 --- /dev/null +++ b/marked/Rel-11/23_series/23231/a4bfa2343d75076b79f7e33d93915e00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:815942b21c6264d341d10c8bef643f812b67b306d3333a0ea339c14ac4714dad +size 60152 diff --git a/marked/Rel-11/23_series/23231/a7c51c18111139f9aca2805114108565_img.jpg b/marked/Rel-11/23_series/23231/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92c035c93d47dbc73c83dca753b864203aea79e0 --- /dev/null +++ b/marked/Rel-11/23_series/23231/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b7ba3f022cd64ae6ff1fe6d3aa0bf974bacda09b340612ff01d198b0cab9c3c +size 61060 diff --git a/marked/Rel-11/23_series/23231/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/23_series/23231/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03f139c0a9fc319d9418bd7cc0b10256dd450e19 --- /dev/null +++ b/marked/Rel-11/23_series/23231/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:677e284cd7859346894996918ffbac4167bcb96456a97642241eb79c96bfcbf1 +size 133207 diff --git a/marked/Rel-11/23_series/23231/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/23_series/23231/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b3407a23f0b0ac8e41cf458b2b39ee573724722 --- /dev/null +++ b/marked/Rel-11/23_series/23231/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5d434395c0ac71d8efc380f6f14d79eafdad31217f573fdabe91f01233b1fa2 +size 99058 diff --git a/marked/Rel-11/23_series/23231/b58cedaf15ad4f0edee5621820865ccc_img.jpg b/marked/Rel-11/23_series/23231/b58cedaf15ad4f0edee5621820865ccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc01c9b51aab23129d927ba2dca1ad5aec0286ee --- /dev/null +++ b/marked/Rel-11/23_series/23231/b58cedaf15ad4f0edee5621820865ccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c35d4c44df96e8e4c6b6b7f81be74e1473c15e7c9b1acd02e557f5961d430d8 +size 22429 diff --git a/marked/Rel-11/23_series/23231/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Rel-11/23_series/23231/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f7857eecf1fda9ef4d439012c1bdcdb5be5b586 --- /dev/null +++ b/marked/Rel-11/23_series/23231/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67603e3cc12e608925dc515c8efaef4b266f0ace2367a6ab760ddd8314299f2f +size 45364 diff --git a/marked/Rel-11/23_series/23231/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/23_series/23231/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecec9de02482c22de05f73c08aa2512f8705db71 --- /dev/null +++ b/marked/Rel-11/23_series/23231/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03cfec97bbb2a2a2d912427e140eeec786fc35bde9cb8b126dceedf5a39d7314 +size 21296 diff --git a/marked/Rel-11/23_series/23231/cc542843836eecb036b99cb270b54a1e_img.jpg b/marked/Rel-11/23_series/23231/cc542843836eecb036b99cb270b54a1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ca221c826c3c4b88fcc6a34dc18c8647f21e2e0 --- /dev/null +++ b/marked/Rel-11/23_series/23231/cc542843836eecb036b99cb270b54a1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7d3fede74f5de6b00e4427994c2588178f25cd520cd9bc8494dd95a5e9b21e8 +size 58785 diff --git a/marked/Rel-11/23_series/23231/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/marked/Rel-11/23_series/23231/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..879227115207364ec72cd1a7c179d13c2b0672a7 --- /dev/null +++ b/marked/Rel-11/23_series/23231/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a80b0482757069c58e000cb195d8bbca08fda5bd3bf098ab66657c0ccd5add17 +size 57631 diff --git a/marked/Rel-11/23_series/23231/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/23_series/23231/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03dae5441d0772b4f31eb71d8d67d2e1534e4cba --- /dev/null +++ b/marked/Rel-11/23_series/23231/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:688e4236b4e9318f465710049db266946b128abf3c855608a64521569b49aef4 +size 166821 diff --git a/marked/Rel-11/23_series/23231/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/23_series/23231/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1f3e8e601786ac3105d679bdafbcede9d90c67f --- /dev/null +++ b/marked/Rel-11/23_series/23231/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8d4cacd9f5e4d2db77a2d0b3e100529c87bae8f86f1f86117297b5c706123ee +size 157462 diff --git a/marked/Rel-11/23_series/23231/e9b43ac020435f8121e8592f31afdc52_img.jpg b/marked/Rel-11/23_series/23231/e9b43ac020435f8121e8592f31afdc52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c32ef82128f285046c79a61402370033900bb3a --- /dev/null +++ b/marked/Rel-11/23_series/23231/e9b43ac020435f8121e8592f31afdc52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:102819671e5cab27ffd60f0a4f66fd5f08222cd9d22cbfd3be1e8999db82be3f +size 34222 diff --git a/marked/Rel-11/23_series/23231/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/23_series/23231/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fa5c11e9b9ba45ca6d341fb2702dace8921f900 --- /dev/null +++ b/marked/Rel-11/23_series/23231/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:550e5ded0e8f97ec5490c249ce98b2a3cf79ad8a0c8cc77bbc220731242b5f1d +size 69611 diff --git a/marked/Rel-11/23_series/23231/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/marked/Rel-11/23_series/23231/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f278ed9f3a3844f997cccc8b5a2053fb224971e0 --- /dev/null +++ b/marked/Rel-11/23_series/23231/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4cfc7292abe6c85006238e66a76a0a0266ee51f778396a827f92e07347c5e73 +size 110008 diff --git a/marked/Rel-11/23_series/23231/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23231/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8f6918ecd27abda5531a7832651764e0847c29b --- /dev/null +++ b/marked/Rel-11/23_series/23231/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bb1fe040b3e647ad61dcb99c4a7170425c293ef9fcd1a2a9225c6a7d82730ca +size 59748 diff --git a/marked/Rel-11/23_series/23231/raw.md b/marked/Rel-11/23_series/23231/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..729268489db4576a5fdc35fb9c362132831d9186 --- /dev/null +++ b/marked/Rel-11/23_series/23231/raw.md @@ -0,0 +1,2879 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions, symbols and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 10 | +| 3.3 Abbreviations ..... | 11 | +| 4 Main Concepts ..... | 11 | +| 4.1 General ..... | 11 | +| 4.2 Call Control..... | 12 | +| 4.3 H.248..... | 12 | +| 4.4 MGW Selection..... | 12 | +| 4.4.1 Principles ..... | 12 | +| 4.4.2 Optimised MGW Selection ..... | 12 | +| 4.4.3 Deferred MGW selection..... | 14 | +| 4.4.4 Mobile to Mobile Call ..... | 15 | +| 4.4.5 MGW bypass..... | 16 | +| 5 General Circuit Switched Core Network Domain Architecture ..... | 18 | +| 6 Call Establishment ..... | 19 | +| 6.1 Basic Mobile Originating Call ..... | 19 | +| 6.1.1 Basic Mobile Originating Call Establishment with immediate MGW selection..... | 19 | +| 6.1.1.1 General..... | 19 | +| 6.1.1.2 MGW selection ..... | 19 | +| 6.1.1.3 Initial INVITE message ..... | 19 | +| 6.1.1.4 Network side bearer establishment..... | 19 | +| 6.1.1.5 Access bearer assignment..... | 20 | +| 6.1.1.6 Framing protocol initialisation..... | 20 | +| 6.1.1.7 Through-Connection..... | 20 | +| 6.1.1.8 Confirmation of bearer establishment..... | 20 | +| 6.1.1.9 Interworking function ..... | 20 | +| 6.1.1.10 Codec handling ..... | 20 | +| 6.1.1.11 Voice Processing function ..... | 20 | +| 6.1.1.12 Failure handling in MSC server..... | 20 | +| 6.1.1.13 Example ..... | 21 | +| 6.1.2 Originating Call Establishment For Iu Interface on IP with immediate MGW selection ..... | 23 | +| 6.1.3 Originating Call Establishment For A Interface user plane over IP with immediate MGW selection ..... | 24 | +| 6.2 Basic Mobile Terminating Call..... | 25 | +| 6.2.1 Basic Mobile Terminating Call Establishment with immediate MGW selection ..... | 25 | +| 6.2.1.1 General..... | 25 | +| 6.2.1.2 GMSC server ..... | 26 | +| 6.2.1.2.1 MGW selection ..... | 26 | +| 6.2.1.2.2 Initial INVITE message ..... | 26 | +| 6.2.1.2.3 Outgoing side bearer termination configuration ..... | 26 | +| 6.2.1.2.4 Incoming side bearer termination configuration ..... | 26 | +| 6.2.1.2.5 Through-Connection ..... | 26 | +| 6.2.1.2.6 Indication of bearer establishment ..... | 26 | +| 6.2.1.2.7 Voice Processing function..... | 27 | +| 6.2.1.2.8 Failure handling in GMSC server ..... | 27 | +| 6.2.1.3 MSC server ..... | 27 | +| 6.2.1.3.1 Paging..... | 27 | +| 6.2.1.3.2 Call setup..... | 27 | +| 6.2.1.3.3 MGW selection ..... | 27 | +| 6.2.1.3.4 Network side bearer termination configuration ..... | 28 | +| 6.2.1.3.5 Access bearer assignment..... | 28 | +| 6.2.1.3.6 Framing protocol initialisation ..... | 28 | + +| | | | +|-------------|------------------------------------------------------------------------------------------------------|----| +| 6.2.1.3.7 | Called party alerting ..... | 28 | +| 6.2.1.3.8 | Called party answer ..... | 28 | +| 6.2.1.3.9 | Through-Connection ..... | 28 | +| 6.2.1.3.10 | Interworking function ..... | 29 | +| 6.2.1.3.11 | Codec handling ..... | 29 | +| 6.2.1.3.12 | Voice Processing function ..... | 29 | +| 6.2.1.3.13 | Failure handling in MSC server ..... | 29 | +| 6.2.1.3.14 | Example - the GMSC selects a MGW ..... | 29 | +| 6.2.2 | Terminating Call Establishment For Iu Interface on IP with immediate MGW selection ..... | 32 | +| 6.2.3 | Terminating Call Establishment For A Interface user plane over IP with immediate MGW selection ..... | 32 | +| 7 | Call Clearing ..... | 33 | +| 7.1 | General ..... | 33 | +| 7.2 | Visited MSC Server Procedures ..... | 34 | +| 7.2.1 | Call Clearing when Visited MSC Server has Forwarded/Deflected Call ..... | 34 | +| 7.2.2 | Call Clearing received from core network ..... | 34 | +| 7.2.2.1 | Procedures towards access side ..... | 34 | +| 7.2.2.2 | Procedures towards network side ..... | 34 | +| 7.2.2.2.1 | Call Clearing during establishment ..... | 34 | +| 7.2.2.2.1.1 | Originating MSC-S ..... | 34 | +| 7.2.2.2.1.2 | Terminating MSC-S ..... | 34 | +| 7.2.2.2.2 | Call Clearing after call established ..... | 35 | +| 7.2.2.2.2.1 | Originating MSC-S ..... | 35 | +| 7.2.2.2.2.2 | Terminating MSC-S ..... | 35 | +| 7.2.2.3 | Example Call Flow ..... | 35 | +| 7.2.3 | Call Clearing received from UE ..... | 36 | +| 7.2.3.1 | Procedures towards access side ..... | 36 | +| 7.2.3.2 | Procedures towards network side ..... | 37 | +| 7.2.3.2.1 | Call Clearing during call establishment ..... | 37 | +| 7.2.3.2.1.1 | Originating MSC-S ..... | 37 | +| 7.2.3.2.1.2 | Terminating MSC-S ..... | 37 | +| 7.2.3.2.2 | Call Clearing after call established ..... | 37 | +| 7.2.3.2.2.1 | Originating MSC-S ..... | 37 | +| 7.2.3.2.2.2 | Terminating MSC-S ..... | 37 | +| 7.2.3.3 | Example Call Flow ..... | 37 | +| 7.2.4 | Call Clearing initiated by V-MSC Server ..... | 39 | +| 7.2.4.1 | Call clearing towards access network ..... | 39 | +| 7.2.4.2 | Call clearing towards network side ..... | 39 | +| 7.2.4.3 | Example Call Flow ..... | 39 | +| 7.2.5 | Call clearing received from MGW ..... | 40 | +| 7.2.5.1 | Bearer released on the access side ..... | 40 | +| 7.2.5.2 | Bearer released on the network side ..... | 40 | +| 7.2.5.3 | Example Call Flow ..... | 40 | +| 7.2.6 | Call Clearing procedures towards MGW ..... | 42 | +| 7.2.7 | Call Clearing for Iu Interface on IP ..... | 42 | +| 7.3 | Gateway MSC Server Procedures ..... | 42 | +| 7.3.1 | Call Clearing received from peer SIP-I node ..... | 42 | +| 7.3.2 | Call Clearing initiated by G-MSC Server ..... | 43 | +| 7.3.2.1 | Call clearing to the destination side ..... | 43 | +| 7.3.2.2 | Call clearing to the originating side ..... | 43 | +| 7.3.3 | Call Clearing received from MGW ..... | 43 | +| 7.3.3.1 | Bearer released on the destination side ..... | 43 | +| 7.3.3.2 | Bearer released on the originating side ..... | 43 | +| 7.3.4 | Call Clearing procedures towards MGW ..... | 44 | +| 8 | Handover/Relocation ..... | 44 | +| 8.1 | UMTS to UMTS ..... | 44 | +| 8.1.1 | Intra-MSC SRNS/SBSS Relocation ..... | 44 | +| 8.1.1.1 | Intra-MGW Relocation ..... | 44 | +| 8.1.1.2 | Inter-MGW Relocation ..... | 44 | +| 8.1.2 | Basic Inter-MSC SRNS/SBSS Relocation ..... | 44 | +| 8.1.3 | Subsequent Inter-MSC SRNS/SBSS Relocation back to the Anchor MSC ..... | 44 | + +| | | | +|---------|------------------------------------------------------------------------------------------------|----| +| 8.1.4 | Subsequent Inter-MSC SRNS/SBSS Relocation to a third MSC..... | 44 | +| 8.1.5 | SRNS/SBSS Relocation with Iu on IP ..... | 45 | +| 8.2 | UMTS to GSM..... | 45 | +| 8.2.1 | Intra-MSC UMTS to GSM Handover ..... | 45 | +| 8.2.1.1 | Intra-MGW Relocation ..... | 45 | +| 8.2.1.2 | Inter-MGW Relocation ..... | 45 | +| 8.2.1.3 | Intra-MSC UMTS to GSM Handover for A interface over IP ..... | 45 | +| 8.2.2 | Basic Inter-MSC UMTS to GSM Handover ..... | 45 | +| 8.2.2.1 | Basic Inter-MSC UMTS to GSM Handover for A Interface over IP ..... | 45 | +| 8.2.3 | Subsequent Inter-MSC UMTS to GSM Handover back to the Anchor MSC..... | 45 | +| 8.2.3.1 | Subsequent Inter-MSC UMTS to GSM Handover back to the anchor MSC for A Interface over IP ..... | 45 | +| 8.2.4 | Subsequent Inter-MSC UMTS to GSM Handover to a third MSC..... | 46 | +| 8.3 | GSM to UMTS ..... | 46 | +| 8.3.1 | Intra-MSC GSM to UMTS Handover ..... | 46 | +| 8.3.1.1 | Intra-MGW Relocation ..... | 46 | +| 8.3.1.2 | Inter-MGW Relocation ..... | 46 | +| 8.3.2 | Basic Inter-MSC GSM to UMTS Handover ..... | 46 | +| 8.3.3 | Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC..... | 46 | +| 8.3.4 | Subsequent Inter-MSC GSM to UMTS Handover to a third MSC..... | 46 | +| 8.3.5 | GSM to UMTS Handover with Iu on IP ..... | 46 | +| 8.4 | GSM to GSM ..... | 47 | +| 8.4.1 | Intra-MSC Inter-BSS GSM to GSM Handover..... | 47 | +| 8.4.1.1 | Intra-MGW Relocation ..... | 47 | +| 8.4.1.2 | Inter-MGW Relocation ..... | 47 | +| 8.4.1.3 | Intra-MSC GSM to GSM Handover for A interface over IP..... | 47 | +| 8.4.2 | Basic Inter-MSC GSM to GSM Handover..... | 47 | +| 8.4.2.1 | Basic Inter-MSC GSM to GSM Handover for A Interface over IP..... | 47 | +| 8.4.3 | Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC ..... | 47 | +| 8.4.3.1 | Subsequent Inter-MSC GSM to GSM Handover back to the anchor MSC for A Interface over IP .... | 47 | +| 8.4.4 | Subsequent GSM to GSM Handover to a third MSC..... | 47 | +| 8.4.5 | BSS Internal Handover..... | 48 | +| 9 | Compatibility Issues..... | 48 | +| 9.1 | Compatibility Issues for Nc Interface ..... | 48 | +| 9.2 | Compatibility Issues for Mc Interface..... | 48 | +| 10 | General (G)MSC server-MGW Procedures..... | 48 | +| 10.1 | MGW Unavailable ..... | 48 | +| 10.2 | MGW Available ..... | 48 | +| 10.3 | MGW Recovery ..... | 48 | +| 10.4 | (G)MSC server Recovery..... | 48 | +| 10.5 | MGW Re-register..... | 48 | +| 10.6 | MGW Re-registration Ordered by (G)MSC server..... | 48 | +| 10.7 | Removal from Service of a Physical Termination ..... | 48 | +| 10.8 | Restoration to Service of a Physical Termination..... | 49 | +| 10.9 | Audit of MGW ..... | 49 | +| 10.10 | MGW Capability Change..... | 49 | +| 10.11 | (G)MSC Server Out of service..... | 49 | +| 10.12 | MGW Resource Congestion Handling - Activate..... | 49 | +| 10.13 | MGW Resource Congestion Handling -Indication ..... | 49 | +| 10.14 | Control association monitoring ..... | 49 | +| 10.15 | Hanging termination detection ..... | 49 | +| 11 | Identities..... | 49 | +| 11.1 | Telephone numbering schemes ..... | 49 | +| 11.2 | (G)MSC Server Identity ..... | 49 | +| 11.3 | Sub-addressing ..... | 49 | +| 12 | Operational Aspects..... | 50 | +| 12.1 | Charging..... | 50 | +| 12.2 | SIP session continuity ..... | 50 | +| 12.2.1 | Use of SIP session timer..... | 50 | + +| | | | +|------------|-------------------------------------------------------------------------|----| +| 12.2.2 | Example call flow ..... | 50 | +| 13 | Interactions with Other Services ..... | 51 | +| 13.1 | Enhanced Multi-Level Precedence and Pre-emption service (eMLPP) ..... | 51 | +| 13.2 | Call Deflection Service ..... | 51 | +| 13.3 | Line identification Services ..... | 51 | +| 13.3.1 | Calling Line Identification Presentation (CLIP) ..... | 51 | +| 13.3.2 | Calling Line Identification Restriction (CLIR) ..... | 51 | +| 13.3.3 | Connected Line Identification Presentation (COLP) ..... | 52 | +| 13.3.4 | Connected Line Identification Restriction (COLR) ..... | 52 | +| 13.4 | Call Forwarding Services ..... | 52 | +| 13.4.0 | Principles ..... | 52 | +| 13.4.1 | Call Forwarding Unconditional (CFU) ..... | 52 | +| 13.4.2 | Call Forwarding on mobile subscriber Busy (CFB) ..... | 52 | +| 13.4.2.1 | Network Determined User Busy (NDUB) ..... | 52 | +| 13.4.2.1.1 | Initial INVITE ..... | 52 | +| 13.4.2.1.2 | Confirmation of bearer establishment ..... | 52 | +| 13.4.2.2 | User Determined User Busy (UDUB) ..... | 53 | +| 13.4.2.2.1 | Initial INVITE ..... | 53 | +| 13.4.2.2.2 | Confirmation of bearer establishment ..... | 53 | +| 13.4.3 | Call Forwarding on No Reply (CFNRy) ..... | 53 | +| 13.4.3.1 | Initial INVITE ..... | 53 | +| 13.4.4 | Call Forwarding on mobile subscriber Not Reachable (CFNRc) ..... | 54 | +| 13.4.4.1 | Initial INVITE ..... | 54 | +| 13.4.4.2 | Confirmation of bearer establishment ..... | 54 | +| 13.5 | Call Waiting (CW) ..... | 54 | +| 13.6 | Call Hold (CH) ..... | 54 | +| 13.6.1 | Principles ..... | 54 | +| 13.6.2 | Hold Request ..... | 54 | +| 13.6.3 | Retrieval Request ..... | 55 | +| 13.7 | Multiparty (MPTY) ..... | 55 | +| 13.7.1 | Introduction ..... | 55 | +| 13.7.2 | Beginning the Multi Party call ..... | 55 | +| 13.7.3 | Managing an active Multi Party call ..... | 56 | +| 13.7.4 | Disconnect ..... | 56 | +| 13.7.5 | Failure handling in MSC server ..... | 56 | +| 13.7.6 | Example 1 ..... | 56 | +| 13.8 | Closed User Group (CUG) ..... | 58 | +| 13.9 | Advice of Charge (AoC) ..... | 58 | +| 13.10 | User-to-User Signalling (UUS) ..... | 59 | +| 13.11 | Call Barring Services ..... | 59 | +| 13.11.1 | Barring of outgoing calls ..... | 59 | +| 13.11.2 | Barring of incoming calls other than Anonymous Call Rejection ..... | 59 | +| 13.11.3 | Anonymous Call Rejection (ACR) ..... | 59 | +| 13.12 | Explicit Call Transfer (ECT) ..... | 59 | +| 13.12.1 | Example ..... | 59 | +| 13.13 | Completion of Calls to Busy Subscriber (CCBS) ..... | 60 | +| 13.14 | Multiple Subscriber Profile (MSP) ..... | 60 | +| 13.15 | Multicall ..... | 60 | +| 13.16 | Calling Name Presentation (CNAP) ..... | 60 | +| 13.17 | Alternate Speech/Fax ..... | 60 | +| 13.18 | Modification of the Access Bearer ..... | 61 | +| 13.18.1 | Modification of Bearer Characteristics ..... | 61 | +| 13.18.2 | IWF Protocol Change ..... | 61 | +| 13.19 | GSM Fax ..... | 61 | +| 13.20 | Voice group call service (VGCS), Voice broadcast service (VBS) ..... | 61 | +| 14 | Interactions with Other Network Features and Services ..... | 61 | +| 14.1 | Customised Applications for Mobile network Enhanced Logic (CAMEL) ..... | 61 | +| 14.1.1 | Play Announcement/Send Tone ..... | 61 | +| 14.1.2 | User Interaction ..... | 62 | +| 14.1.3 | Call Party Handling (CPH) ..... | 62 | + +| | | | +|------------------------|---------------------------------------------------------------------------------|----| +| 14.2 | IST ..... | 62 | +| 14.3 | Operator Determined Barring (ODB) ..... | 62 | +| 14.4 | DTMF..... | 62 | +| 14.4.1 | General ..... | 62 | +| 14.4.2 | DTMF handling in SIP-I Offer/Answer ..... | 63 | +| 14.4.3 | Server to MGW Procedures..... | 63 | +| 14.4.4 | RTP Telephony Event DTMF Digit Generation ..... | 64 | +| 14.4.4.1 | General..... | 64 | +| 14.4.4.2 | Start DTMF ..... | 64 | +| 14.4.4.3 | Stop DTMF ..... | 64 | +| 14.4.4.4 | Example ..... | 64 | +| 14.4.5 | DTMF Tone Generation ..... | 64 | +| 14.4.6 | RTP Telephony Event DTMF Digit Detection ..... | 65 | +| 14.4.6.1 | General..... | 65 | +| 14.4.6.2 | Detect DTMF Digit..... | 65 | +| 14.4.6.3 | Example – DTMF Notification..... | 65 | +| 14.4.7 | Inband DTMF Tone Detection ..... | 66 | +| 14.4.8 | Interworking between RTP Telephony Events and Inband DTMF Tones..... | 66 | +| 14.5 | OR ..... | 67 | +| 14.6 | Providing tones or announcements ..... | 67 | +| 14.6.1 | Introduction ..... | 67 | +| 14.6.2 | Preconditions when providing in-band information to the calling subscriber..... | 67 | +| 14.6.3 | Preconditions when providing in-band information to the called subscriber..... | 68 | +| 14.6.4 | Preconditions when providing in-band information to multiple subscribers ..... | 68 | +| 14.6.5 | Request to play an announcement/tone ..... | 68 | +| 14.6.6 | Stopping an announcement/tone..... | 68 | +| 14.6.7 | Announcement/tone completed..... | 68 | +| 14.7 | Global Text Telephony..... | 68 | +| 14.8 | Emergency Calls ..... | 68 | +| 14.9 | Subscriber and equipment trace ..... | 68 | +| 14.10 | Customized Alerting Tones..... | 68 | +| 14.10.1 | General ..... | 68 | +| 14.10.2 | Audio CAT ..... | 69 | +| 14.10.3 | Multimedia CAT ..... | 69 | +| 15 | Messages/Procedures and their contents ..... | 69 | +| 15.1 | Messages between (G)MSC servers..... | 69 | +| 15.2 | Procedures between (G)MSC server and MGW ..... | 69 | +| 15.2.1 | Generic Mc Interface Procedures ..... | 69 | +| 15.2.2 | SIP-I Specific Mc Interface Procedures ..... | 71 | +| 16 | Bearer Redirect ..... | 71 | +| 17 | (G)MSC MGW Tandeming ..... | 71 | +| 18 | Timers for SIP-I based CS core network ..... | 72 | +| 19 | Multiple IP Realms ..... | 72 | +| Annex A (informative): | Change history..... | 73 | + +# --- Foreword + +This Technical Specification has been produced by the 3<sup>rd</sup> 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 2 description for the SIP-I based CS core network. The logical architecture for the SIP-I based CS core network is defined in 3GPP TS 23.205 [7]. + +This stage 2 shall cover the information flows between the GMSC server, MSC server and media gateways that are required to support a SIP-I based Nc interface. Note that nothing in the present document shall preclude an implementation of a combined MSC Server and MGW. The present document shall show the CS core network termination of the Iu and A interfaces in order to cover the information flow stimulus to the core network and describe the interaction with the supplementary and value added services and capabilities. + +For the purposes of the present document, the Nc interface profile is based on ITU-T Q.1912.5 [9] SIP-I profile C and is specified in 3GPP TS 29.231 [4]. The Mc interface profile is based on ITU-T H.248.1 [5] and is specified in 3GPP TS 29.232 [8]. + +Local Call Local Switch (LCLS) functionality is further specified in 3GPP TS 23.284 [31]. + +The present document is applicable only for IP transport in the CS core network. + +Details of Transcoder-Free Operation/Out of Band Transcoder Control are outside the scope of the present document. See 3GPP TS 23.153 [3] for more information. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.002: "Network architecture". +- [3] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2". +- [4] 3GPP TS 29.231: "Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3". +- [5] ITU-T Recommendation H.248.1: "Gateway control protocol". +- [6] 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)". +- [7] 3GPP TS 23.205: "Bearer-independent circuit-switched core network; Stage 2". +- [8] 3GPP TS 29.232: "Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3". +- [9] ITU-T Recommendation Q.1912.5: "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part". +- [10] IETF RFC 3966: "The tel URI for Telephone Numbers". +- [11] 3GPP TS 23.108: "Mobile radio interface layer 3 specification core network protocols; Stage 2 (structured procedures)". + +- [12] 3GPP TS 48.008: "Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification". +- [13] 3GPP TS 23.009: "Handover procedures". +- [14] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [15] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [16] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)". +- [17] IETF RFC 2976: "The SIP INFO method". +- [18] IETF RFC 3311: "The Session Initiation Protocol (SIP) UPDATE Method". +- [19] IETF RFC 3262: "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)". +- [20] 3GPP TS 23.172: "Technical realization of Circuit Switched (CS); multimedia service UDI/RDI fallback and service modification; Stage 2". +- [21] 3GPP TS 29.235: "Interworking between SIP-I based circuit-switched core network and other networks". +- [22] 3GPP TS 25.415: "UTRAN Iu Interface User Plane Protocols". +- [23] 3GPP TS 29.414: "Core Network Nb Data Transport and Transport Signalling". +- [24] IETF RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". +- [25] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". +- [26] IETF RFC 3312: "Integration of Resource Management and Session Initiation Protocol (SIP)". +- [27] 3GPP TS 23.014: "Support of Dual Tone Multi Frequency (DTMF) signalling". +- [28] 3GPP TS 23.003: "Numbering, addressing and identification". +- [29] IETF RFC 4715: "The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI". +- [30] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application". +- [31] 3GPP TS 23.284: "Local Call Local Switch; Stage 2". +- [32] 3GPP TS 29.163: "Interworking between the IM CN subsystem and CS networks – Stage 3". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|---------------------------------------------------------------------------------------------| +| Iu | Interface between the RNS and the core network. It is also considered as a reference point. | +| Mc | Interface between the server and the media gateway. | +| Nb | Interface between media gateways. | +| Nc | The NNI call control interface between (G)MSC servers. | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|----------|----------------------------------------------------------------------------| +| BCF | Bearer Control Function | +| BICC | Bearer Independent Call Control | +| BICN | Bearer Independent Core Network | +| CS | Circuit Switched | +| DSP | Digital Signal Processing | +| GERAN | GSM/EDGE Radio Access Network | +| (G)MSC-S | (Gateway) MSC Server | +| IAM | Initial Address Message | +| IETF | Internet Engineering Task Force | +| IP | Internet Protocol | +| IPBCP | IP Bearer Control Protocol | +| IWF | Interworking Function | +| LCLS | Local Call Local Switch | +| MGCF | Media Gateway Control Function | +| MGW | Media Gateway | +| MSC-S | MSC Server | +| MSC/IWF | IWF at call control layer toward external network (see 3GPP TS 29.007 [6]) | +| NNI | Network-Network interface | +| OoBTC | Out of Band Transcoder Control | +| PRACK | Provisional Response Acknowledgement | +| RTO | Remote Transcoder Operation | +| RTP | Real-Time Transport Protocol | +| SCTP | Stream Control Transmission Protocol | +| SCUDIF | Service Change and UDI Fallback | +| SIP | Session Initiation Protocol | +| SDP | Session Description Protocol | +| TCP | Transmission Control Protocol | +| TDM | Time-Division Multiplexing | +| TFO | Tandem Free Operation | +| TrFO | Transcoder Free Operation | +| UDP | User Datagram Protocol | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# --- 4 Main Concepts + +## 4.1 General + +The SIP-I circuit switched core network supports the IP transport mechanism. The passage of compressed speech at variable bit rates is possible through the CS core network. + +The CS core network shall employ the MSC server, GMSC server and media gateways. The GMSC server and MSC server shall provide the call control and mobility management functions, and the media gateway shall provide the bearer control and transmission resource functions. The media gateway shall contain the stream manipulating functions. + +The GMSC server and MSC servers are connected to the media gateway via the Mc reference point. The MSC servers and GMSC servers are connected with the Nc reference point. There may be a number of call control transit nodes between the MSC server and GMSC server in the Nc reference point. The MGWs are connected with the Nb reference point. + +The users connected to the CS core network shall not be aware whether a MSC server – media gateway combination is used or a monolithic MSC is used. + +## 4.2 Call Control + +The protocol used on the Nc interface shall be a SIP-I call control profile supporting the IP transport mechanism for the ISDN service set, allowing the physical separation of the call control entities from the media transport entities. + +## 4.3 H.248 + +H.248 has been developed within the ITU-T, and supports a separation of call control entities from media transport entities. H.248 is used on the Mc interface between the (G)MSC servers and the media gateway. + +## 4.4 MGW Selection + +### 4.4.1 Principles + +A (G)MSC-Server may support one or several of the following optional MGW selection procedures: + +- "Optimised MGW selection" + +A (G)MSC Server may indicate at the initial SIP-I SDP offer the selected MGW identity in a SIP-I message to enable the receiver of the SIP-I message to select the same MGW, if it has a Mc H.248 gateway control protocol interface to this MGW. + +- "Deferred MGW selection" + +The deferred MGW selection procedure provides the opportunity for the receiver of a SIP-I message to select the MGW it prefers and to send back the identity of the MGW to the preceding node in order to enable that node to select the same MGW. + +Additionally the procedure allows the offerer to send a "proposed" MGW identity to the next SIP-I node, which may be taken into account when the succeeding node seizes a MGW. + +Additionally the procedure allows the offerer to send to the next SIP-I node a list of "additionally proposed" MGW identities that may be proposed in addition to the "proposed" MGW Identity, which may be taken into account when the succeeding node seizes a MGW. + +A GMSC-Server or Intermediate Node may support the following optional MGW selection procedures: + +- "MGW bypass" + +For call scenarios where there is no need for the GMSC server to manipulate the bearer, the GMSC Server may perform call control signalling without any associated MGW by transparently relaying bearer related information (e.g. connection addresses) from the preceding/succeeding nodes. If the (G)MSC server applies the MGW bypass this has the effect that if the succeeding node inserts a MGW this MGW performs the task of terminating the external bearer , i.e. it acts as point of ingress of the user plane from the external network. + +The general call establishment procedures to allow "Optimised MGW selection", "Deferred MGW selection", and "MGW bypass" are described in Clauses 4.4.2, 4.4.3 and 4.4.5, respectively. When applied these procedures shall be combined with the normal call establishment procedures as described in Clause 6. + +### 4.4.2 Optimised MGW Selection + +To initiate the optional "Optimised MGW Selection" procedure, a (G)MSC Server shall seize a MGW as for a normal call and indicate to the succeeding node the identity of the MGW in the initial SDP offer. + +If the succeeding node receiving the SDP offer supports the "Optimised MGW Selection" option and the SDP offer includes a MGW Identity, and the succeeding node has a Mc H.248 gateway control protocol interface to the indicated MGW, the succeeding node may connect to that MGW. The succeeding node may indicate the MGW Identity in the SDP answer to the preceding node. + +In the example sequence chart in Figure 4.4.2.2, which assumes the network model in Figure 4.4.2.1, the offerer is a GMSC Server, which has seized a MGW at the network border. The initial offer indicates that a MGW is connected and includes the MGW identity. The answerer is a terminating MSC Server, which is able to connect to the same MGW and seizes a bearer termination in this MGW and returns the user plane connection address in the answer. + +![Figure 4.4.2.1: Network model for Optimised and Deferred MGW Selection. This diagram shows the network architecture. On the left, a red cloud labeled 'UTRAN' is connected to a blue box 'MSC Server' via a 'RANAP / IP' interface. The 'MSC Server' is connected to a blue box 'GMSC Server' via a dashed green line labeled 'SIP-I / Nc'. The 'GMSC Server' is connected to a yellow box 'SGW' via a dashed line labeled 'N-ISUP'. Below the 'MSC Server' and 'GMSC Server' is a central yellow box labeled 'MGW (edge)'. The 'MSC Server' connects to the 'MGW (edge)' via a dashed line labeled 'GCP / IP'. The 'GMSC Server' also connects to the 'MGW (edge)' via a dashed line labeled 'GCP / IP'. The 'UTRAN' connects to the 'MGW (edge)' via a solid line labeled 'Iu UP'. The 'MGW (edge)' is connected to a blue cloud labeled 'PSTN/ISDN PLMN (TDM)' via a dashed line labeled 'N-ISUP'. Inside the 'MGW (edge)' box, there are two green boxes labeled 'CTX1' and 'CTX2'. 'CTX1' is connected to a red circle labeled 'TRA' and has interfaces 'T1' and 'T2'. 'CTX2' has interfaces 'T3' and 'T4'. Above the 'CTX' boxes, the text 'Nb UP/ IP (virtual)' is present. A large 'IP' label is positioned above the 'MGW (edge)' box.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 4.4.2.1: Network model for Optimised and Deferred MGW Selection. This diagram shows the network architecture. On the left, a red cloud labeled 'UTRAN' is connected to a blue box 'MSC Server' via a 'RANAP / IP' interface. The 'MSC Server' is connected to a blue box 'GMSC Server' via a dashed green line labeled 'SIP-I / Nc'. The 'GMSC Server' is connected to a yellow box 'SGW' via a dashed line labeled 'N-ISUP'. Below the 'MSC Server' and 'GMSC Server' is a central yellow box labeled 'MGW (edge)'. The 'MSC Server' connects to the 'MGW (edge)' via a dashed line labeled 'GCP / IP'. The 'GMSC Server' also connects to the 'MGW (edge)' via a dashed line labeled 'GCP / IP'. The 'UTRAN' connects to the 'MGW (edge)' via a solid line labeled 'Iu UP'. The 'MGW (edge)' is connected to a blue cloud labeled 'PSTN/ISDN PLMN (TDM)' via a dashed line labeled 'N-ISUP'. Inside the 'MGW (edge)' box, there are two green boxes labeled 'CTX1' and 'CTX2'. 'CTX1' is connected to a red circle labeled 'TRA' and has interfaces 'T1' and 'T2'. 'CTX2' has interfaces 'T3' and 'T4'. Above the 'CTX' boxes, the text 'Nb UP/ IP (virtual)' is present. A large 'IP' label is positioned above the 'MGW (edge)' box. + +Figure 4.4.2.1: Network model for Optimised and Deferred MGW Selection + +![Figure 4.4.2.2: Optimised MGW selection (message sequence chart). This sequence diagram shows the interaction between UE, RNC/BSC, MGWa', MSC-S, MGWa, and GMSC-S. The sequence starts with an INVITE [SDP, IAM] from GMSC-S to HLR Interrogation. HLR Interrogation sends a Context ($) and Context (C2) to MGWa. MGWa responds with Add.reply(T3). GMSC-S then sends a Reserve RTP Connection Point + Change Through Connection to MGWa. Next, an INVITE [IAM, SDP, MGW Id, Connection Address = T3] is sent from GMSC-S to MSC-S, which responds with 100 Trying. A Paging + Security message is sent from MSC-S to RNC/BSC. RNC/BSC sends a SETUP to UE, which responds with CALL CONFIRMED. MSC-S then sends an Add.request($) to MGWa', which responds with Add.reply(T2). A note indicates: 'If MSC-S can seize the same physical MGW identified by the MGWId then it seizes a new context in that MGW'. MSC-S sends a 183 Progress [SDP, MGW Id, Connection Address = T2] to GMSC-S, which responds with 183 Progress [SDP]. MSC-S sends a PRACK to GMSC-S, which responds with PRACK (200 OK). GMSC-S sends an UPDATE [SDP] to MSC-S, which responds with 200 OK (UPDATE [SDP]). Finally, GMSC-S sends a 200 OK (UPDATE [SDP]) to MGWa. A note indicates: 'Reserve RTP Connection Point and Configure Remote Resources + Change Through Connection'.](410562339ce067fdc6fa41940c118658_img.jpg) + +Figure 4.4.2.2: Optimised MGW selection (message sequence chart). This sequence diagram shows the interaction between UE, RNC/BSC, MGWa', MSC-S, MGWa, and GMSC-S. The sequence starts with an INVITE [SDP, IAM] from GMSC-S to HLR Interrogation. HLR Interrogation sends a Context (\$) and Context (C2) to MGWa. MGWa responds with Add.reply(T3). GMSC-S then sends a Reserve RTP Connection Point + Change Through Connection to MGWa. Next, an INVITE [IAM, SDP, MGW Id, Connection Address = T3] is sent from GMSC-S to MSC-S, which responds with 100 Trying. A Paging + Security message is sent from MSC-S to RNC/BSC. RNC/BSC sends a SETUP to UE, which responds with CALL CONFIRMED. MSC-S then sends an Add.request(\$) to MGWa', which responds with Add.reply(T2). A note indicates: 'If MSC-S can seize the same physical MGW identified by the MGWId then it seizes a new context in that MGW'. MSC-S sends a 183 Progress [SDP, MGW Id, Connection Address = T2] to GMSC-S, which responds with 183 Progress [SDP]. MSC-S sends a PRACK to GMSC-S, which responds with PRACK (200 OK). GMSC-S sends an UPDATE [SDP] to MSC-S, which responds with 200 OK (UPDATE [SDP]). Finally, GMSC-S sends a 200 OK (UPDATE [SDP]) to MGWa. A note indicates: 'Reserve RTP Connection Point and Configure Remote Resources + Change Through Connection'. + +Figure 4.4.2.2: Optimised MGW selection (message sequence chart) + +### 4.4.3 Deferred MGW selection + +To initiate the optional "Deferred MGW Selection", a (G)MSC Server shall indicate to the succeeding node in the initial SIP-I SDP offer that the MGW has not been seized by including an unspecified connection address and shall indicate that "preconditions are not met". The (G)MSC server may additionally include a "proposed" MGW identity within the SDP offer. The (G)MSC server may additionally include a list of "additionally proposed" MGW identities within the initial SDP offer. + +Upon reception of an INVITE with unspecified connection address, the succeeding node may seize a MGW (MGW Bypass may be supported in which case the MGW would not be selected, see Clause 4.4.4). + +NOTE: If the succeeding node applies MGW bypass, the next succeeding node will receive the forwarded unspecified connection address and will then apply the procedures in the present Clause. + +If the succeeding node seizes a MGW, it shall insert its own connection address in the SDP offer to the further succeeding 3GPP Node and in the subsequent SDP answer back to the preceding node. + +If the succeeding node supports the deferred MGW selection, and it received a "proposed" MGW Identity and a list of "additionally proposed" MGW identities, it may take this into account when selecting the MGW. If the succeeding node supports the deferred MGW selection, it should include the identity of the selected MGW in the SDP answer. + +Upon reception of the SDP answer, the (G)MSC Server that initiated the "deferred MGW" selection shall seize a MGW. It should use the received MGW identity to select the MGW, preferably using the same MGW to save resources, if it has a Mc H.248 gateway control protocol interface to that MGW. The (G)MSC Server shall then send a new SDP offer in a PRACK request or an UPDATE request including the connection address and an indication that preconditions are met (provided upstream continuity is also achieved). + +Upon reception of the new SDP offer, the succeeding node will update the MGW configuration with the new connection address. + +In the example sequence chart in Figure 4.4.3.1, which assumes the network model in Figure 4.4.2.1, the offerer is an originating MSC Server, which does not signal a MGW identity and at the same time indicates that the user plane is not connected. The answerer is an MSC-IW-Server, which seizes the MGW at the network border and returns the MGW identity to the originating MSC Server. The originating MSC Server is able to select the same MGW and seizes a bearer termination and indicates in the second SDP offer to the MSC-IW Server that the user plane is connected. + +![Sequence diagram for deferred MGW selection. Lifelines: UE, RNC/BSC, MGWa', MSC-S, MGWa, GMSC-S. The sequence starts with SETUP and CALL PROCEEDING messages. MSC-S indicates preconditions not met. The process involves INVITE, Add.request, Context, Add.reply, 183 Progress, PRACK or UPDATE, and 200 OK messages. A note indicates that if MSC-S can seize the same physical MGW identified by the MGWId, it seizes a new context in that MGW. The message sequence continues as for originating call flow Figure 6.1.2.1 step 4 and following.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +UE RNC/BSC MGWa' MSC-S MGWa GMSC-S +| | | | | | +|---SETUP-->| | | | | +| |---SETUP-->| | | | +|<--CALL PROCEEDING---| | | | +| | | | | | +| | | |---INVITE [IAM, SDP, Connection Address = 0]---> +| | | | |<--Add.request($)--| +| | | | |---Add.reply(T3)-->| +| | | |<--183 Progress [SDP, MGW Id, Connection Address = T3]--| +| | |<--Add.request($)--| | | +| | |---Add.reply(T2)-->| | | +| | | |---PRACK or UPDATE [SDP, Connection Address = T2]---> +| | | |<--200 OK (PRACK or UPDATE) [SDP]--| +| | | | | | +|----------------Message Sequence Continues as for Figure 6.1.2.1-----------------| + +``` + +Sequence diagram for deferred MGW selection. Lifelines: UE, RNC/BSC, MGWa', MSC-S, MGWa, GMSC-S. The sequence starts with SETUP and CALL PROCEEDING messages. MSC-S indicates preconditions not met. The process involves INVITE, Add.request, Context, Add.reply, 183 Progress, PRACK or UPDATE, and 200 OK messages. A note indicates that if MSC-S can seize the same physical MGW identified by the MGWId, it seizes a new context in that MGW. The message sequence continues as for originating call flow Figure 6.1.2.1 step 4 and following. + +NOTE: If an UPDATE is used to send the SDP, a PRACK without SDP will be sent before. This is not shown in the figure. + +Figure 4.4.3.1: Deferred MGW selection (message sequence chart) + +#### 4.4.4 Mobile to Mobile Call + +The mobile to mobile call may use either the deferred MGW selection or optimised MGW selection. The reason for choosing deferred MGW over optimised MGW would be to attempt to select the MGW at the edge as the originating MSC does not know where the call will finally terminate. + +An example of mobile to mobile call using optimised MGW selection is show in Figure 4.4.4.1. + +![Diagram of optimised MGW selection for mobile to mobile calls. It shows two UTRANs connected to an IP network via RANAP/IP and GCP/IP interfaces. The IP network contains an MGW with four ports (T1, T2, T3, T4) and a TRA. The MGW is connected to two MSC Server B units. The first MSC Server B sends a SIP-I Offer (IAM, full SDP, MGW Id) to the second MSC Server B, which responds with a SIP-I Answer (Connection address/port).](a7c51c18111139f9aca2805114108565_img.jpg) + +``` + + SIP-I Offer (IAM, full SDP, MGW Id) + ----------------------------------> +RANAP /IP [MSC Server B] SIP-I Answer [MSC Server B] RANAP /IP + ^ | (Connection address/port) | ^ + : | <------------------ | : + : | GCP /IP GCP /IP| : + : | IP | : + : v v : + : +-----------------------------------------+ : + : | Nb UP / | : + : | IP (virtual) | : + : Iu UP | +----+ +----+ +----+ +----+ | Iu UP : + +------->| | T1 |<-->| T2 | | T3 |<-->| T4 | |<-------+ + : | |TRA | +----+ +----+ +----+ | : + : +-----------------------------------------+ : +[UTRAN] [UTRAN] + +``` + +Diagram of optimised MGW selection for mobile to mobile calls. It shows two UTRANs connected to an IP network via RANAP/IP and GCP/IP interfaces. The IP network contains an MGW with four ports (T1, T2, T3, T4) and a TRA. The MGW is connected to two MSC Server B units. The first MSC Server B sends a SIP-I Offer (IAM, full SDP, MGW Id) to the second MSC Server B, which responds with a SIP-I Answer (Connection address/port). + +Figure 4.4.4.1: Optimised MGW Selection for mobile to mobile calls + +#### 4.4.5 MGW bypass + +In call scenarios without the need for the GMSC or Intermediate Node server to manipulate the bearer, the GMSC or Intermediate Node may perform call control signalling without any associated MGW by not inserting a MGW in the bearer path during the call establishment. In that case, the bearer related information of SDP offers/answers shall be passed transparently through the (G)MSC Server. + +Call scenarios where the GMSC or Intermediate Node needs to manipulate the bearer, e.g. scenarios with insertion of tones or announcements, lawful interception, CAMEL services do not allow this optimisation. + +MGW removal and MGW re-insertion scenarios once the call is answered are not supported. + +Figure 4.4.5.1 shows an example network model for a mobile terminating call with MGW bypass. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. + +![Figure 4.4.5.1: Terminating call establishment with MGW bypass (network model). The diagram shows a network architecture where a BSC/RNC (red cloud) is connected to an MSC Server (blue box) via a dotted green line (bearer control). The MSC Server is connected to a GMSC Server (blue box) via a solid blue line (SIP-I / Nc). The MSC Server is also connected to an MGW (yellow box) via a solid blue line (GCP / IP). The MGW has two interfaces, T1 and T2. T1 is connected to the BSC/RNC. T2 is connected to a PLMN / external network (purple cloud). A yellow box labeled 'MGW bypass' is shown with a dotted line pointing to the T2 interface, indicating that the MGW is bypassed for the bearer path.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +Figure 4.4.5.1: Terminating call establishment with MGW bypass (network model). The diagram shows a network architecture where a BSC/RNC (red cloud) is connected to an MSC Server (blue box) via a dotted green line (bearer control). The MSC Server is connected to a GMSC Server (blue box) via a solid blue line (SIP-I / Nc). The MSC Server is also connected to an MGW (yellow box) via a solid blue line (GCP / IP). The MGW has two interfaces, T1 and T2. T1 is connected to the BSC/RNC. T2 is connected to a PLMN / external network (purple cloud). A yellow box labeled 'MGW bypass' is shown with a dotted line pointing to the T2 interface, indicating that the MGW is bypassed for the bearer path. + +**Figure 4.4.5.1: Terminating call establishment with MGW bypass (network model)** + +NOTE: T<sub>2</sub> is the connection to the PLMN / external network i.e. it may not terminate Nb interface if to a Non-PLMN; in that case, the procedures associated to the MSC-S/MGW handling for T<sub>2</sub> (such as DTMF transmission/reception) are specified in 3GPP TS 29.235 [21]. + +Figure 4.4.5.2 shows the corresponding example message sequence. In the example, the GMSC determines that it does not need to include a MGW in the bearer path. SDP offer and SDP answer information is relayed between ingress and egress signalling paths. + +The option to support "MGW bypass" relies on the support of external user plane interworking at the succeeding MGW however the GMSC Server signalling to and from the succeeding 3GPP PLMN node in such a scenario shall comply with the SIP-I on Nc specification. + +![Sequence diagram for Basic Mobile Terminating Call, MGW bypass. Lifelines: GMSC-S, MGWa, MSCS, MGWb, RNC/BSC, UE. The diagram shows the call setup process from an external INVITE to the UE, with HLR interrogation, SDP relay, and resource reservation steps.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` +sequenceDiagram + participant External + participant GMSC-S + participant MGWa + participant MSCS + participant MGWb + participant RNC/BSC + participant UE + + Note left of GMSC-S: HLR Interrogation + External->>GMSC-S: INVITE [SDP, IAM] + GMSC-S->>MSCS: 1. G-MSC relays SDP offer to MSC-S + MSCS->>GMSC-S: 2. INVITE [IAM, SDP] + GMSC-S->>MSCS: 100 Trying + Note right of MSCS: Paging + Security + MSCS->>RNC/BSC: 3. SETUP + RNC/BSC->>UE: CALL CONFIRMED + Note right of MSCS: Context ($), Context (C1) + MSCS->>MGWb: 4. Add.request($), Add.reply(T2) + Note right of MGWb: Reserve RTP Connection Point and Configure Remote Resources + Change Through Connection + MGWb->>MSCS: 183 Progress [SDP] + MSCS->>GMSC-S: 5. 183 Progress [SDP] + GMSC-S->>External: PRACK + External->>GMSC-S: 200 OK(PRACK) + GMSC-S->>MSCS: 6. UPDATE [SDP] + MSCS->>GMSC-S: 200 OK (UPDATE [SDP]) + GMSC-S->>External: 7. 200 OK (UPDATE [SDP]) +``` + +Sequence diagram for Basic Mobile Terminating Call, MGW bypass. Lifelines: GMSC-S, MGWa, MSCS, MGWb, RNC/BSC, UE. The diagram shows the call setup process from an external INVITE to the UE, with HLR interrogation, SDP relay, and resource reservation steps. + +Figure 4.4.5.2/1: Basic Mobile Terminating Call, MGW bypass (message sequence chart) + +![Sequence diagram for Basic Mobile Terminating Call, MGW bypass. Lifelines: GMSC, MGWa, MSC, MGWb, RNC/BSC, UE. The diagram shows the interaction between these components for steps 9 through 15.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant MGWa + participant MSC + participant MGWb + participant RNC/BSC + participant UE + + Note over MSC, MGWb: UMTS: + Note right of MSC: 9 + MSC->>MGWb: Add.request($) (Context C1) + Note right of MGWb: Prepare Bearer + +Change Through Connection + MGWb-->>MSC: Add.reply(T1) (Context C1) + MSC->>RNC/BSC: RAB_ASSIGNMENT_REQ + Note right of RNC/BSC: Bearer Establishment +and Iu UP Initialization + RNC/BSC-->>MSC: RAB_ASSIGNMENT_COMPL + + Note over MSC, MGWb: GSM: + Note right of MSC: 10 + MSC->>MGWb: Add.request(T1) (Context C1) + Note right of MGWb: Reserve Circuit + +Change Through Connection + MGWb-->>MSC: Add.reply(T1) (Context C1) + MSC->>RNC/BSC: ASSIGNMENT_REQUEST + RNC/BSC-->>MSC: ASSIGNMENT_COMPL + + Note right of MSC: 11 + MSC->>MGWb: Mod.request(T2) (Context C1) + UE->>UE: ALERTING + Note right of MGWb: Send Tone (Start providing a +ringing tone for a speech call) + MGWb-->>MSC: Mod.reply(T2) (Context C1) + + Note right of MSC: 12 + MSC->>GMSC: 180 Ringing [ACM] + MSC->>MGWa: 180 Ringing [ACM] + GMSC->>MSC: PRACK + GMSC->>MGWa: PRACK + MSC->>GMSC: 200 OK [PRACK] + MSC->>MGWa: 200 OK [PRACK] + + Note right of MSC: 13 + UE->>MSC: CONNECT + MSC->>MGWb: Mod.request(T1) (Context C1) + Note right of MGWb: Change Through Connection + +Activate Inter Working Function +(when applicable) + +Activate Voice Processing Function +(when applicable) + MGWb-->>MSC: Mod.reply(T1) (Context C1) + MSC->>MGWb: Mod.request(T2) (Context C1) + Note right of MGWb: Activate InterWorking +Function (when applicable) + +Activate Voice Processing +Function (when applicable) + MGWb-->>MSC: Mod.reply(T2) (Context C1) + + Note right of MSC: 14 + MSC->>GMSC: 200 OK INVITE [ANM] + MSC->>MGWa: 200 OK INVITE [ANM] + + Note right of MSC: 15 + GMSC->>MSC: ACK + GMSC->>MGWa: ACK + +``` + +Sequence diagram for Basic Mobile Terminating Call, MGW bypass. Lifelines: GMSC, MGWa, MSC, MGWb, RNC/BSC, UE. The diagram shows the interaction between these components for steps 9 through 15. + +**Figure 4.4.5.2/2: Basic Mobile Terminating Call, MGW bypass (message sequence chart continue)** + +## 5 General Circuit Switched Core Network Domain Architecture + +The General CS core network domain architecture is specified in 3GPP TS 23.205 [7]. + +## 6 Call Establishment + +NOTE: All message sequence charts in this clause are examples. All valid call establishment message sequences can be derived from the example message sequences and associated message pre-conditions. + +### 6.1 Basic Mobile Originating Call + +#### 6.1.1 Basic Mobile Originating Call Establishment with immediate MGW selection + +##### 6.1.1.1 General + +The mobile originating call shall be established in accordance with 3GPP TS 23.108 [11]. The following clauses describe the additional requirements for the SIP-I based CS core network. The Offer/Answer Procedures of the Session Description Protocol (SDP) for media negotiation shall be applied as specified in 3GPP TS 29.231 [4]. + +If multiple speech codecs are offered, Out of Band Transcoder Control (OoBTC) procedures shall be applied by the Originating MSC server in accordance with 3GPP TS 23.153 [3]. Otherwise for speech calls only the default PCM speech codec shall be signalled in an SDP offer; auxiliary payload types such as the Telephony Event RTP payload type may be included in addition. The handling of such auxiliary payload types is described in specific clauses (e.g. DTMF is described in Clause 14.4). + +For data calls the procedures in 3GPP TS 29.007 [6] are applicable. + +##### 6.1.1.2 MGW selection + +The MSC server shall select an MGW for the bearer connection before it performs the access bearer assignment or the network side connection point reservation. This shall happen before sending the INVITE message. + +##### 6.1.1.3 Initial INVITE message + +The MSC server shall send the initial INVITE message before or after the access bearer assignment is completed. The MSC server shall provide the supported SDP (e.g. core network side user plane IP transport address and port, codec(s), RTP telephony event) to the succeeding node in the initial INVITE message. The initial INVITE message shall encapsulate the IAM message. If the access bearer assignment has not been completed, the MSC server shall indicate that the local precondition has not been met. + +##### 6.1.1.4 Network side bearer establishment + +The MSC server shall select the codec for this connection and request the MGW to select and provide the IP transport address and port for the network side bearer connection before sending the INVITE message. If OoBTC is supported, the selected codec may be the preferred codec for this connection. The MSC server shall use the Reserve RTP Connection Point procedure (bullet 1 in figure 6.1.1.13.2). Within this procedure, the MSC server shall indicate the codec and any additional payload types (e.g. RTP Telephony Event) and shall request a local IP address and UDP port from the MGW. The MSC server may indicate that the IP interface type is for Nb over IP with SIP-I based Nc. The local IP address and UDP port are used by the MGW to receive user plane data from the succeeding MGW. + +Support and selection of CS Data payload types is described in 3GPP TS 29.007 [6]. + +The MGW shall reply to the MSC server with the selected local IP address and UDP port. + +The MSC server shall send this information in the INVITE (bullet 2 in figure 6.1.1.13.2) to the succeeding node. + +After the succeeding node has provided the SDP answer, the MSC server shall use the Configure RTP Connection Point procedure to request the MGW to configure the remote address, codec and any additional negotiated payload types (e.g. RTP Telephony Event) (bullet 3 in figure 6.1.1.13.2) of the bearer termination. If OoBTC is supported, the Configure RTP Connection Point procedure may amend the selected codec for this connection if different from the codec sent in the previous Reserve RTP Connection Point procedure (bullet 1 in figure 6.1.1.13.2). The Configure RTP Connection Point procedure may indicate that the IP interface type is for Nb over IP with SIP-I based Nc. + +### 6.1.1.5 Access bearer assignment + +The access bearer assignment is defined in the clause 6.1.1.4 of 3GPP TS 23.205 [7]. + +### 6.1.1.6 Framing protocol initialisation + +There is no specific framing protocol initialisation in the SIP-I based CS network. The MGW terminates the Iu Framing Protocol towards the Iu interface and will receive an Iu UP Initialisation from an Iu-CS interface connected to the radio interface and shall process it according to the procedures in 3GPP TS 25.415 [22] and 3GPP TS 29.232 [8]. No information from the framing protocol initialisation needs to be interworked towards the Nb interface of a SIP-I based CS core network. Information within subsequent Iu UP payload PDUs and RTP PDUs shall be interworked according to the procedures in TS 29.414 [23]. + +### 6.1.1.7 Through-Connection + +In combination with the Prepare Bearer or Reserve Circuit procedures, and the Reserve RTP Connection Point or Configure RTP Connection Point procedure, the MSC server should use the Change Through-Connection procedure to request the MGW to configure the bearer terminations so that the bearer is through-connected in the backward direction (bullet 1 or 3 and bullet 4 or 5 in figure 6.1.1.13.2). + +For a multimedia call, the MSC may request the MGW to both-way through-connect the bearer using the Change Through-Connection procedure to generate a multimedia CAT (see subclause 14.10.1). + +Otherwise when the MSC server receives the answer indication (200 OK(INVITE)), it shall request the MGW to both-way through-connect the bearer using the Change Through-Connection procedure (bullet 8 in figure 6.1.1.13.2), unless the bearer has already been both way through-connected at an earlier stage. + +### 6.1.1.8 Confirmation of bearer establishment + +If the initial INVITE message which was sent to the succeeding node indicated that the local precondition has not been met, the MSC server shall send an UPDATE message indicating that the local preconditions are met when the access bearer assignment has been completed (bullet 6 in figure 6.1.1.13.2). + +### 6.1.1.9 Interworking function + +The MGW may use an interworking function that is based on the PLMN Bearer Capability, 3GPP TS 24.008 [14], of the bearer termination. The activation of the possible interworking function in both bearer terminations will be requested by the MSC server at reception of the SIP 200 OK (INVITE) response using the Activate Interworking Function procedure (bullet 8 in figure 6.1.1.13.2). + +### 6.1.1.10 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +### 6.1.1.11 Voice Processing function + +A voice processing function (i.e. echo cancellation) located on the MGW may be used to achieve desired acoustic quality on the bearer terminations. The MSC server shall request the activation of voice processing functions in the bearer terminations. For non-speech calls, the MSC server has the ability to instruct the MGW to disable the voice processing functions (bullet 8 in figure 6.1.1.13.2/2). + +### 6.1.1.12 Failure handling in MSC server + +If any procedure between the MSC server and the MGW has not completed successfully or the MSC server receives a Bearer Released procedure from the MGW, the call shall be cleared as described in clause 7.2.4, visited MSC server initiated call clearing or in clause 7.2.5, MGW initiated call clearing. Alternatively, the MSC server may only release the resources in the MGW that caused the failure, possibly select a new MGW for the bearer connection and continue the call establishment using new resources in the selected MGW. + +### 6.1.1.13 Example + +Figure 6.1.1.13.1 shows the network model for the mobile originating call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) + +and the bearer. The MSC server seizes one context with two terminations in the MGW. The bearer termination T1 is used for the bearer towards the RNC/BSC and the bearer termination T2 is used for the bearer towards the succeeding MGW. + +![Diagram of Basic Mobile Originating Call (network model)](a3472689858b068ef469213682965325_img.jpg) + +The diagram illustrates the network model for a Basic Mobile Originating Call. It features three main components: an RNC/BSC (Radio Network Controller/Base Station Controller) on the left, an MSC-S (Mobile Switching Center Server) at the top, and an MGW (Media Gateway) at the bottom. The RNC/BSC is connected to the MSC-S via a dashed green line. The MSC-S is connected to the MGW via a solid blue line. The MGW has two bearers: T1 (Termination 1) connected to the RNC/BSC via a dashed red line, and T2 (Termination 2) connected to a succeeding MGW via a dashed red line. The MGW is labeled with 'CTXI' and 'MGW'. + +Diagram of Basic Mobile Originating Call (network model) + +**Figure 6.1.1.13.1: Basic Mobile Originating Call (network model)** + +![Sequence diagram for Basic Mobile Originating Call with early originating access bearer assignment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the interaction between these entities to establish a call, including SETUP, CALL PROCEEDING, and various bearer assignment messages (Add.req, Add.resp, Mod.req, Mod.resp, RAB_ASSIGNMENT_REQ, RAB_ASSIGNMENT_COMPL, ASSIGNMENT_REQUEST, ASSIGNMENT_COMPL). It is divided into UMTS and GSM sections for bearer assignment. The final call state is ALERTING at the UE.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + Note left of UE: Error! No + Note right of MGW: Error! No text of specified style in + + UE->>MSC-S: SETUP + MSC-S-->>UE: CALL PROCEEDING + + Note right of MSC-S: 1 + MSC-S->>MGW: Add.req ($) + MGW-->>MSC-S: Add.resp (T2) + Note right of MGW: Reserve RTP Connection Point + Change Through-Connection + Note right of MSC-S: 2 + MSC-S->>MGW: INVITE [SDP, IAM] + MGW-->>MSC-S: 183 Progress [SDP] + MSC-S->>MGW: PRACK + Note right of MSC-S: 3 + MSC-S->>MGW: Mod.req (T2) + MGW-->>MSC-S: Mod.resp (T2) + Note right of MGW: Configure RTP Connection Point + Note right of MSC-S: 4 + MSC-S->>MGW: 200 OK (PRACK) + + Note right of RNC/BSC: UMTS: + Note right of MSC-S: 4 + MSC-S->>MGW: Add.req ($) + MGW-->>MSC-S: Add.resp (T1) + Note right of MGW: Prepare Bearer + Change Through-Connection + RNC/BSC->>MSC-S: RAB_ASSIGNMENT_REQ + Note right of RNC/BSC: Bearer Establishment and Iu UP Initialization + MSC-S->>RNC/BSC: RAB_ASSIGNMENT_COMPL + + Note right of RNC/BSC: GSM: + Note right of MSC-S: 5 + MSC-S->>MGW: Add.req (T1) + MGW-->>MSC-S: Add.resp (T1) + Note right of MGW: Reserve Circuit + Change Through-Connection + RNC/BSC->>MSC-S: ASSIGNMENT_REQUEST + MSC-S->>RNC/BSC: ASSIGNMENT_COMPL + + Note right of MSC-S: 6 + MSC-S->>MGW: UPDATE [SDP] + MGW-->>MSC-S: 200 OK (UPDATE [SDP]) + Note right of MSC-S: 7 + MSC-S->>MGW: 180 Ringing [ACM] + MGW-->>MSC-S: PRACK + MSC-S->>MGW: 200 OK (PRACK) + + MSC-S-->>RNC/BSC: ALERTING + RNC/BSC-->>UE: ALERTING + +``` + +Sequence diagram for Basic Mobile Originating Call with early originating access bearer assignment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the interaction between these entities to establish a call, including SETUP, CALL PROCEEDING, and various bearer assignment messages (Add.req, Add.resp, Mod.req, Mod.resp, RAB\_ASSIGNMENT\_REQ, RAB\_ASSIGNMENT\_COMPL, ASSIGNMENT\_REQUEST, ASSIGNMENT\_COMPL). It is divided into UMTS and GSM sections for bearer assignment. The final call state is ALERTING at the UE. + +Figure 6.1.1.13.2/1: Basic Mobile Originating Call with early originating access bearer assignment (message sequence chart). + +![Sequence diagram for Basic Mobile Originating Call with early originating access bearer assignment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The sequence starts with a 200 OK - INVITE [ANM] from MGW to MSC-S, followed by an ACK from MSC-S to MGW. Then, MSC-S sends a Mod.req (T1) to MGW, which responds with Mod.resp (T1). The response includes 'Change Through-Connection + Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'. Next, MSC-S sends a Mod.req (T2) to MGW, which responds with Mod.resp (T2). The response includes 'Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'. Finally, MSC-S sends a CONNECT message to RNC/BSC, which is then forwarded to UE. Context (C1) is indicated for the Mod.req and Mod.resp messages.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + Note right of MSC-S: 8 + MGW->>MSC-S: 200 OK - INVITE [ANM] + MSC-S->>MGW: ACK + MSC-S->>MGW: Mod.req (T1) Context (C1) + MGW-->>MSC-S: Mod.resp (T1) Context (C1) + Note right of MGW: Change Through-Connection + +Activate Inter-Working Function +(when applicable) + +Activate Voice Processing +Function (when applicable) + MSC-S->>MGW: Mod.req (T2) Context (C1) + MGW-->>MSC-S: Mod.resp (T2) Context (C1) + Note right of MGW: Activate Inter-Working +Function (when applicable) + +Activate Voice Processing +Function (when applicable) + MSC-S->>RNC/BSC: CONNECT + RNC/BSC->>UE: CONNECT + +``` + +Sequence diagram for Basic Mobile Originating Call with early originating access bearer assignment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The sequence starts with a 200 OK - INVITE [ANM] from MGW to MSC-S, followed by an ACK from MSC-S to MGW. Then, MSC-S sends a Mod.req (T1) to MGW, which responds with Mod.resp (T1). The response includes 'Change Through-Connection + Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'. Next, MSC-S sends a Mod.req (T2) to MGW, which responds with Mod.resp (T2). The response includes 'Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'. Finally, MSC-S sends a CONNECT message to RNC/BSC, which is then forwarded to UE. Context (C1) is indicated for the Mod.req and Mod.resp messages. + +**Figure 6.1.1.13.2/2: Basic Mobile Originating Call with early originating access bearer assignment (message sequence chart).** + +## 6.1.2 Originating Call Establishment For Iu Interface on IP with immediate MGW selection + +For IP transport over the IuCS interface the procedures in the present Clause shall apply in addition to the SIP-I based Core Network side procedures described in 6.1.1. + +For the access side termination, the exchange of IP addresses as defined in the clause 6.1.3 of 3GPP TS 23.205 [3] shall apply. + +If the bearer transport is IP and IuUP mode is Support, the MGW shall use the source IP address and UDP Port of the IuUP Init packet received from the radio access network as the destination address for subsequent downlink packets. + +The sequence is shown in Figure 6.1.2.1. + +![Sequence diagram for Originating Call Establishment for Iu on IP. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the interaction between these entities to establish a call. It includes steps for SIP signaling (SETUP, CALL PROCEEDING, INVITE, 183 Progress, PRACK, 200 OK), RTP connection point reservation (Add.req, Add.resp), and RAB assignment (RAB_ASSIGNMENT_REQ, RAB_ASSIGNMENT_COMPL). Two modes are shown: 'For IuUP in Support Mode' and 'For IuUP in Transparent Mode'.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + Note left of UE: Error! No + Note right of MGW: Error! No text of specified style in + + UE->>MSC-S: SETUP + MSC-S-->>UE: CALL PROCEEDING + + Note right of MSC-S: 1 + MSC-S->>MGW: Add.req ($) + MGW-->>MSC-S: Add.resp (T2) + Note right of MGW: Reserve RTP Connection Point + Change Through-Connection + + Note right of MSC-S: 2 + MSC-S->>MGW: INVITE [SDP, IAM] + MGW-->>MSC-S: 183 Progress [SDP] + MSC-S->>MGW: PRACK + + Note right of MSC-S: 3 + MSC-S->>MGW: Mod.req (T2) + MGW-->>MSC-S: Mod.resp (T2) + Note right of MGW: Configure RTP Connection Point + + MSC-S-->>MGW: 200 OK - PRACK + + Note right of MSC-S: 4 + MSC-S->>MGW: Add.req ($) + MGW-->>MSC-S: Add.resp (T1) + Note right of MGW: Prepare IP_Transport + Change Through-Connection + + MSC-S->>RNC/BSC: RAB_ASSIGNMENT_REQ + Note left of RNC/BSC: For IuUP in Support Mode + Note right of RNC/BSC: Bearer Establishment and Iu UP Initialization + RNC/BSC->>MSC-S: RAB_ASSIGNMENT_COMPL + + Note right of MSC-S: 5 + MSC-S->>MGW: Add.req (T1) + MGW-->>MSC-S: Add.resp (T1) + Note right of MGW: Modify IP Transport Address + + Note right of MSC-S: 6 + MSC-S->>MGW: UPDATE [SDP] + MGW-->>MSC-S: 200 OK - UPDATE [SDP] + +``` + +Sequence diagram for Originating Call Establishment for Iu on IP. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the interaction between these entities to establish a call. It includes steps for SIP signaling (SETUP, CALL PROCEEDING, INVITE, 183 Progress, PRACK, 200 OK), RTP connection point reservation (Add.req, Add.resp), and RAB assignment (RAB\_ASSIGNMENT\_REQ, RAB\_ASSIGNMENT\_COMPL). Two modes are shown: 'For IuUP in Support Mode' and 'For IuUP in Transparent Mode'. + +Figure 6.1.2.1: Originating Call Establishment for Iu on IP + +### 6.1.3 Originating Call Establishment For A Interface user plane over IP with immediate MGW selection + +For A interface user plane over IP, the procedures in the present Clause shall apply in addition to the SIP-I based Core Network side procedures described in 6.1.1. + +For the access side termination, the exchange of IP addresses as defined in the clause 6.1.5 of 3GPP TS 23.205 [7] shall apply. + +The sequence is shown in Figure 6.1.3.1. + +![Sequence diagram showing the originating call establishment for A interface user plane over IP. The diagram involves four entities: UE, BSC, MSC-S, and MGW. The process starts with a SETUP message from UE to BSC, followed by a CALL PROCEEDING message from BSC to UE. The main part of the diagram shows the interaction between MSC-S and MGW for context management, marked with numbered circles 1 through 6. Step 1: MSC-S sends Context ($) to MGW, MGW responds with Add.req ($), then MGW reserves RTP connection and changes through-connection, responding with Add.resp (T2). Step 2: MSC-S sends INVITE [SDP, IAM] to MGW, MGW responds with 183 Progress [SDP], then MSC-S sends PRACK. Step 3: MSC-S sends Context (C1) to MGW, MGW responds with Mod.req (T2), then MGW configures RTP connection point, responding with Mod.resp (T2), and finally 200 OK - PRACK. Step 4: MSC-S sends Context (C1) to MGW, MGW responds with Add.req ($), then MGW reserves RTP connection and changes through-connection, responding with Add.resp (T1). Step 5: BSC sends ASSIGNMENT_REQ to MSC-S, MSC-S responds with ASSIGNMENT_COMPL. Step 6: MSC-S sends Context (C1) to MGW, MGW responds with Mod.req (T1), then MGW configures RTP connection point, responding with Mod.resp (T1). Finally, MSC-S sends UPDATE [SDP] to MGW, MGW responds with 200 OK - UPDATE [SDP].](26d664119ad25250780f554633444e54_img.jpg) + +Sequence diagram showing the originating call establishment for A interface user plane over IP. The diagram involves four entities: UE, BSC, MSC-S, and MGW. The process starts with a SETUP message from UE to BSC, followed by a CALL PROCEEDING message from BSC to UE. The main part of the diagram shows the interaction between MSC-S and MGW for context management, marked with numbered circles 1 through 6. Step 1: MSC-S sends Context (\$) to MGW, MGW responds with Add.req (\$), then MGW reserves RTP connection and changes through-connection, responding with Add.resp (T2). Step 2: MSC-S sends INVITE [SDP, IAM] to MGW, MGW responds with 183 Progress [SDP], then MSC-S sends PRACK. Step 3: MSC-S sends Context (C1) to MGW, MGW responds with Mod.req (T2), then MGW configures RTP connection point, responding with Mod.resp (T2), and finally 200 OK - PRACK. Step 4: MSC-S sends Context (C1) to MGW, MGW responds with Add.req (\$), then MGW reserves RTP connection and changes through-connection, responding with Add.resp (T1). Step 5: BSC sends ASSIGNMENT\_REQ to MSC-S, MSC-S responds with ASSIGNMENT\_COMPL. Step 6: MSC-S sends Context (C1) to MGW, MGW responds with Mod.req (T1), then MGW configures RTP connection point, responding with Mod.resp (T1). Finally, MSC-S sends UPDATE [SDP] to MGW, MGW responds with 200 OK - UPDATE [SDP]. + +Figure 6.1.3.1: Originating Call Establishment for A interface user plane over IP + +## 6.2 Basic Mobile Terminating Call + +### 6.2.1 Basic Mobile Terminating Call Establishment with immediate MGW selection + +#### 6.2.1.1 General + +The mobile terminating call shall be established in accordance with 3GPP TS 23.108 [11]. The following clauses describe the additional requirements for the SIP-I based CS core network. The Offer/Answer Procedures of the Session Description Protocol (SDP) for media negotiation shall be applied as specified in 3GPP TS 29.231 [4]. + +If multiple speech codecs are supported by the Terminating MSC server then Out of Band Transcoder Control (OoBTC) procedures shall be applied by the Terminating MSC server in accordance with 3GPP TS 23.153 [3]. Otherwise for speech calls only the default PCM speech codec shall be supported and shall be selected from the SDP offer and included in the answer; auxiliary payload types such as the Telephony Event RTP payload type may be included in addition. The handling of such payload types is described in specific clauses (e.g. DTMF is described in Clause 14.4). + +For data calls the procedures in 3GPP TS 29.007 [6] are applicable. + +### 6.2.1.2 GMSC server + +#### 6.2.1.2.1 MGW selection + +The GMSC server shall select an MGW for the bearer connection before it performs the incoming side bearer establishment or the outgoing side bearer establishment. This shall happen before sending the initial INVITE message. + +#### 6.2.1.2.2 Initial INVITE message + +The GMSC server shall indicate in the initial INVITE message that the precondition has not been met if either of the following conditions is satisfied before sending the initial INVITE message: + +1. The incoming INVITE(IAM) indicated that remote preconditions had not been met, and no new SDP has been received indicating that preconditions have been met. +2. The incoming side RTP connection point has not been successfully reserved and configured in the MGW. + +The GMSC shall provide the supported SDP (e.g. core network side user plane IP transport address and port, codec(s), RTP telephony event) to the succeeding node in the initial INVITE message. + +#### 6.2.1.2.3 Outgoing side bearer termination configuration + +The GMSC server shall select the codec for the outgoing side bearer connection before it performs the Reserve RTP Connection Point procedure. If OoBTC is supported, the selected codec may be the preferred codec for this connection. + +After the succeeding node has provided a user plane IP transport address and port the GMSC server shall use the Configure RTP Connection Point procedure to request the MGW to configure the remote address and any additional negotiated payload types (e.g. RTP Telephony Event) of the bearer termination. If OoBTC is supported, the Configure RTP Connection Point procedure may amend the selected codec for this connection if different from the codec sent in the previous Reserve RTP Connection Point procedure. + +Both the Reserve RTP Connection Point procedure and the Configure RTP Connection Point procedure may indicate that the IP interface type is for Nb over IP with SIP-I based Nc. + +#### 6.2.1.2.4 Incoming side bearer termination configuration + +The GMSC server shall request the MGW to prepare for the incoming side bearer establishment using the Reserve and Configure RTP Connection Point procedure. The GMSC server shall select the codec for the incoming side bearer connection before it performs the Reserve and Configure RTP Connection Point procedure. Within this procedure, the GMSC server shall request the MGW to provide a local user plane IP address and UDP port and may indicate that the IP interface type is for Nb over IP with SIP-I based Nc. The GMSC server shall also provide the MGW with the selected codec, the remote user plane IP address and port information that was received from the preceding node in the INVITE message and any additional payload types (e.g. RTP Telephony Event). The GMSC server shall include in the SDP answer to the preceding node: the user plane IP address and UDP port received from the MGW, the selected codec and any additional accepted payload types. + +NOTE: The incoming side bearer establishment may take place either before or after HLR interrogation. + +#### 6.2.1.2.5 Through-Connection + +In combination with the Reserve RTP Connection Point or Configure RTP Connection Point procedures and with the Reserve and Configure RTP Connection Point procedure, the GMSC server should use the Change Through-Connection procedure to request the MGW to both-way through-connect the bearer termination. + +#### 6.2.1.2.6 Indication of bearer establishment + +The core network side bearer is established if the following conditions are satisfied: + +1. Either: + - a. The incoming INVITE(IAM) indicated that remote preconditions had not been met, and new SDP has been received indicating that preconditions have been met, or + - b. The incoming INVITE(IAM) did not include any preconditions information or indicated that remote preconditions had been met; + +and + +2. Either: + +- a. The incoming side RTP connection point has been successfully reserved and configured in the MGW, or +- b. MGW selection is not required for this call. + +If the initial INVITE message which was sent to the succeeding node indicated that the precondition has not been met, the GMSC server shall send an UPDATE message indicating that the preconditions are met when the core network side bearer is established (bullet 8 in figure 6.2.1.3.14.2). + +#### 6.2.1.2.7 Voice Processing function + +A voice processing function (i.e. echo cancellation) located on the MGW may be used to achieve desired acoustic quality on the bearer terminations. The GMSC server shall request the activation of the voice processing functions in the bearer terminations. For non-speech calls, the GMSC server has the ability to instruct the MGW to disable the voice processing functions (bullet 14 in figure 6.2.1.3.14.2/2). + +#### 6.2.1.2.8 Failure handling in GMSC server + +If any procedure between the GMSC server and the MGW has not completed successfully or the GMSC server receives a Bearer Released procedure from the MGW, the call shall be cleared as described in clause 7.3.2, GMSC server initiated call clearing or in clause 7.3.3, MGW initiated call clearing. Alternatively, the GMSC server may only release the resources in the MGW that caused the failure, possibly select a new MGW for the bearer connection and continue the call establishment using new resources in the selected MGW. + +#### 6.2.1.3 MSC server + +##### 6.2.1.3.1 Paging + +The Paging is defined in the clause 6.1.1.4 of 3GPP TS 23.205 [7]. + +##### 6.2.1.3.2 Call setup + +The MSC Server shall send a SETUP message towards the UE. + +According to TS 23.108 [11], the MSC server can either apply the early access bearer assignment procedure, i.e. the MSC does not include the signal IE in the SETUP to request that the user is alerted only after the setup of the access bearer as specified in 3GPP TS 24.008 [14], or the MSC server can apply the late access bearer assignment procedure, i.e. the MSC includes the signal IE in the SETUP to request that the user is immediately alerted. + +For basic call setup the MSC server should apply the early access bearer assignment procedure to ensure that the terminating UE is not alerted until the end to end bearer is established. + +NOTE: The late access bearer assignment procedure can result in clipping, alerting of the user if the core network side bearer or radio bearer establishment fails, and related charging of failed calls. + +##### 6.2.1.3.3 MGW selection + +The MSC server shall select an MGW for the bearer connection before it performs the network side bearer establishment or the access bearer assignment. This happens at latest after the UE has sent the Call Confirmed message. + +**Editor's Note: For GSM, if performing Service based handover (see 3GPP TS 48.008 [12]), the MSC Server may omit MGW selection at this time. This requires further study.** + +##### 6.2.1.3.4 Network side bearer termination configuration + +The MSC server requests the MGW to prepare for the network side bearer establishment using the Reserve and Configure RTP Connection Point procedure (bullet 4 in figure 6.2.1.3.14.2/1). The MSC server shall select the codec for the network side bearer connection before it performs the Reserve and Configure RTP Connection Point procedure. Within this procedure, the MSC server shall request the MGW to provide a local user plane IP address and UDP port and may indicate that the IP interface type is for Nb over IP with SIP-I based Nc. The MSC server shall also provide the MGW with the selected codec and with the remote user plane IP address and port information that was received from the preceding node in the SDP offer. The MSC server shall include in the SDP answer (e.g. 183 SESSION + +PROGRESS) to the preceding node: the user plane IP address and UDP port received from the MGW, the selected codec and any additional accepted payload types. + +#### 6.2.1.3.5 Access bearer assignment + +If the early access bearer assignment procedure is used (see 3GPP TS 23.108 [11]), the access bearer assignment shall be started only when the core network bearer is established, as described by the following conditions. + +1. Either: + - a. The incoming INVITE(IAM) indicated that remote preconditions had not been met, and new SDP has been received indicating that preconditions have been met, or + - b. The incoming INVITE(IAM) did not include any preconditions information or indicated that remote preconditions had been met; + +and + +2. The incoming side RTP connection point has been successfully reserved and configured in the MGW. + +The access bearer assignment is defined in the clause 6.2.1.2.5 of 3GPP TS 23.205 [7]. + +#### 6.2.1.3.6 Framing protocol initialisation + +There is no specific framing protocol initialisation requirement in SIP-I based CS network. The MGW terminates the Iu Framing Protocol towards the Iu interface and will receive an IuUP Initialisation from an Iu-CS interface towards the radio interface and shall process it according to the procedures in 3GPP TS 25.415 [22] and 3GPP TS 29.232 [8]. No information from the framing protocol initialisation needs to be interworked towards the Nb interface of a SIP-I based CS core network. Information within subsequent Iu UP payload PDUs and RTP PDUs shall be interworked according to the procedures in TS 29.414 [23]. + +#### 6.2.1.3.7 Called party alerting + +For a speech call, when the MSC server receives an Alerting message, it shall request the MGW to provide a ringing tone to the calling party using the Send Tone procedure (bullet 11 in figure 6.2.1.3.14.2/1). + +NOTE: Other kind of tones may be provided to the calling party at an earlier stage of the call establishment. + +#### 6.2.1.3.8 Called party answer + +For a speech call, when the MSC server receives a Connect message, it shall request the MGW to stop providing the ringing tone to the calling party using the Stop Tone procedure (bullet 13 in figure 6.2.1.3.14.2/2). + +#### 6.2.1.3.9 Through-Connection + +In combination with the Reserve and Configure RTP Connection Point procedure and with the Prepare Bearer procedure or Reserve Circuit procedure, the MSC server should use the Change Through-Connection procedure to request the MGW to through-connect the bearer terminations so that the bearer will be not through connected (bullet 4, and bullet 9 or 10 in figure 6.2.1.3.14.2). + +When the MSC server receives the Connect message, it shall request the MGW to both-way through-connect the bearer using the Change Through-Connection procedure (bullet 13 in figure 6.2.1.3.14.2/2). + +#### 6.2.1.3.10 Interworking function + +The MGW may use an interworking function that is based on the PLMN Bearer Capability, 3GPP TS 24.008 [14], of the bearer termination. The activation of the possible interworking function in both bearer terminations will be requested by the MSC server at reception of the Connect message using the Activate Interworking Function procedure (bullet 13 in figure 6.2.1.3.14.2). + +#### 6.2.1.3.11 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +#### 6.2.1.3.12 Voice Processing function + +A voice processing function (i.e. echo cancellation) located on the MGW may be used to achieve desired acoustic quality on the bearer terminations. The MSC server shall request the activation of the voice processing functions in the bearer terminations. For non-speech calls, the MSC server has the ability to instruct the MGW to disable the voice processing functions (bullet 13 in figure 6.2.1.3.14.2/2). + +#### 6.2.1.3.13 Failure handling in MSC server + +If any procedure between the MSC server and the MGW has not completed successfully or the MSC server receives a Bearer Released procedure from the MGW, the call shall be cleared as described in clause 7.2.4, visited MSC server initiated call clearing or in clause 7.2.5, MGW initiated call clearing. Alternatively, the MSC server may only release the resources in the MGW that caused the failure, possibly select a new MGW for the bearer connection and continue the call establishment using new resources in the selected MGW. + +#### 6.2.1.3.14 Example - the GMSC selects a MGW + +Figure 6.2.1.3.14.1 shows the network model for the basic mobile terminating call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in MGWb. The bearer termination T1 is used for the bearer towards the RNC/BSC and the bearer termination T2 is used for the bearer towards the GMSC server selected MGWa. The GMSC server seizes one context with two bearer terminations in MGWa. The bearer termination T3 is used for the bearer towards the MSC server selected MGWb and the bearer termination T4 is used for the bearer towards the preceding MGW. + +![Figure 6.2.1.3.14.1: Basic Mobile Terminating Call Forward Bearer Establishment (network model). The diagram shows a network model for a basic mobile terminating call. At the top, a GMSC-S (Gateway Mobile Switching Center Server) is connected to an MSC-S (Mobile Switching Center Server) via a green dashed line representing call control signalling. Below the GMSC-S is an MGWa (Media Gateway) with two bearer terminations, T3 and T4. Below the MSC-S is an MGWb (Media Gateway) with two bearer terminations, T1 and T2. Below the MGWb is an RNC/BSC (Radio Network Controller/Base Station Controller). A red dotted line represents the bearer control signalling path, connecting the GMSC-S to the MGWa, then to the MGWb, and finally to the RNC/BSC. The MGWa and MGWb are connected to the GMSC-S and MSC-S respectively via blue solid lines representing the bearer path. The MGWa has a context CTX2 and the MGWb has a context CTX1.](e9b43ac020435f8121e8592f31afdc52_img.jpg) + +Figure 6.2.1.3.14.1: Basic Mobile Terminating Call Forward Bearer Establishment (network model). The diagram shows a network model for a basic mobile terminating call. At the top, a GMSC-S (Gateway Mobile Switching Center Server) is connected to an MSC-S (Mobile Switching Center Server) via a green dashed line representing call control signalling. Below the GMSC-S is an MGWa (Media Gateway) with two bearer terminations, T3 and T4. Below the MSC-S is an MGWb (Media Gateway) with two bearer terminations, T1 and T2. Below the MGWb is an RNC/BSC (Radio Network Controller/Base Station Controller). A red dotted line represents the bearer control signalling path, connecting the GMSC-S to the MGWa, then to the MGWb, and finally to the RNC/BSC. The MGWa and MGWb are connected to the GMSC-S and MSC-S respectively via blue solid lines representing the bearer path. The MGWa has a context CTX2 and the MGWb has a context CTX1. + +**Figure 6.2.1.3.14.1: Basic Mobile Terminating Call Forward Bearer Establishment (network model)** + +Figure 6.2.1.3.14.2 shows the message sequence example for the basic mobile terminating call. In the example the GMSC server requests from MGWa the seizure of the outgoing side bearer termination before forwarding the INVITE to the MSC server. After the outgoing side bearer termination is seized the GMSC server sends the INVITE with supported SDP to the MSC server. The MSC server requests from MGWb the seizure of the network side bearer termination when Call Confirmed message is received from the UE. The MSC server sends the SDP answer (183 SESSION PROGRESS) to the GMSC. On receipt of the SDP answer, the GMSC requests from MGWa the through connection of the outgoing side bearer termination and the seizure of the incoming side bearer termination. The GMSC server sends the SDP answer (183 SESSION PROGRESS) to the external network. On receipt of the second SDP offer (UPDATE) from the external network, the GMSC server forwards this to the MSC server. The MSC server requests seizure of the access side bearer termination. For a speech call the MSC server requests MGWb to provide a ringing tone to the calling party at alerting. At answer the MSC server requests MGWb to both-way through-connect the bearer. For a speech call the MSC server requests MGWb to stop the ringing tone to the calling party at answer. When the MSC server receives an answer indication, for circuit switched data call it may request the activation of the interworking function in both bearer terminations. The (G)MSC server may request the activation of the voice processing functions for the bearer terminations. + +![Sequence diagram for Basic Mobile Terminating Call, GMSC selects a MGW. Lifelines: GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, UE. The diagram shows the flow of messages for call setup, including INVITE, HLR Interrogation, Add.request, Add.reply, 183 Progress, PRACK, 200 OK, Mod.request, Mod.reply, UPDATE, and CALL CONFIRMED messages.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant External + participant GMSC-S + participant MGWa + participant MSC-S + participant MGWb + participant RNC/BSC + participant UE + + Note left of GMSC-S: HLR Interrogation + External->>GMSC-S: INVITE [SDP, IAM] + GMSC-S->>MGWa: Add.request($), Context ($), Context (C2) + MGWa-->>GMSC-S: Add.reply(T3), Reserve RTP Connection Point + Change Through-Connection + GMSC-S->>MSC-S: INVITE [IAM, SDP] + MSC-S-->>GMSC-S: 100 Trying + Note right of MSC-S: Paging + Security + MSC-S->>UE: SETUP + UE-->>MSC-S: CALL CONFIRMED + MSC-S->>MGWb: Add.request($), Context ($), Context (C1) + MGWb-->>MSC-S: Add.reply(T2), Reserve and Configure RTP Connection Point + Change Through-Connection + MSC-S-->>GMSC-S: 183 Progress [SDP] + GMSC-S->>MSC-S: PRACK + MSC-S-->>GMSC-S: 200 OK (PRACK) + GMSC-S->>MGWa: Mod.request(T3), Context (C2) + MGWa-->>GMSC-S: Mod.reply(T3), Configure RTP Connection Point + Change Through-Connection + GMSC-S->>MGWb: Add.request($), Context (C2) + MGWb-->>GMSC-S: Add.reply(T4), Reserve and Configure RTP Connection Point + Change Through-Connection + GMSC-S-->>External: 183 Progress [SDP] + External->>GMSC-S: PRACK + GMSC-S-->>External: 200 OK (PRACK) + External->>GMSC-S: UPDATE [SDP] + GMSC-S->>MSC-S: UPDATE [SDP] + MSC-S-->>GMSC-S: 200 OK (UPDATE [SDP]) + GMSC-S-->>External: 200 OK (UPDATE) [SDP] + +``` + +Sequence diagram for Basic Mobile Terminating Call, GMSC selects a MGW. Lifelines: GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, UE. The diagram shows the flow of messages for call setup, including INVITE, HLR Interrogation, Add.request, Add.reply, 183 Progress, PRACK, 200 OK, Mod.request, Mod.reply, UPDATE, and CALL CONFIRMED messages. + +Figure 6.2.1.3.14.2/1: Basic Mobile Terminating Call, GMSC selects a MGW (message sequence chart) + +![Sequence diagram for Basic Mobile Terminating Call, GMSC selects a MGW. Lifelines: GMSC, MGWa, MSC, MGWb, RNC/BSC, UE. The diagram shows the interaction between these components to establish a call, including UMTS and GSM bearer setup, ringing, and connection phases.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant MGWa + participant MSC + participant MGWb + participant RNC/BSC + participant UE + + Note right of MSC: 9 UMTS: Context (C1) + MSC->>MGWb: Add.request(S) + MGWb-->>MSC: Add.reply(T1) + Note right of MGWb: Prepare Bearer + Change Through-Connection + MSC->>RNC/BSC: RAB_ASSIGNMENT_REQ + Note right of RNC/BSC: Bearer Establishment and Iu UP Initialization + RNC/BSC-->>MSC: RAB_ASSIGNMENT_COMPL + + Note right of MSC: 10 GSM: Context (C1) + MSC->>MGWb: Add.request(T1) + MGWb-->>MSC: Add.reply(T1) + Note right of MGWb: Reserve Circuit + Change Through-Connection + MSC->>RNC/BSC: ASSIGNMENT REQUEST + RNC/BSC-->>MSC: ASSIGNMENT COMPL + + Note right of MSC: 11 + MSC->>MGWb: Mod.request(T2) + Note right of MGWb: Send Tone (Start providing a ringing tone for a speech call) + MGWb-->>MSC: Mod.reply(T2) + + Note right of GMSC: 12 + GMSC->>MGWa: 180 Ringing [ACM] + MGWa-->>GMSC: 180 Ringing [ACM] + GMSC->>MGWa: PRACK + MGWa-->>GMSC: 200 OK (PRACK) + GMSC->>MSC: 200 OK (PRACK) + + Note right of MSC: 13 + MSC->>MGWb: CONNECT + Note right of MGWb: Change Through-Connection + Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable) + Note right of MSC: Context (C1) + MSC->>MGWb: Mod.request(T1) + MGWb-->>MSC: Mod.reply(T1) + Note right of MSC: Context (C1) + MSC->>MGWb: Mod.request(T2) + Note right of MGWb: Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable) + MGWb-->>MSC: Mod.reply(T2) + + Note right of GMSC: 14 + GMSC->>MGWa: 200 OK - INVITE [ANM] + Note right of MGWa: Context (C2) + MGWa->>MGWb: Mod.request(T3) + Note right of MGWb: Activate Voice Processing Function (when applicable) + MGWb-->>MGWa: Mod.reply(T3) + Note right of MGWa: Context (C2) + MGWa->>MGWb: Mod.request(T4) + Note right of MGWb: Activate Voice Processing Function (when applicable) + MGWb-->>MGWa: Mod.reply(T4) + GMSC->>MGWa: 200 OK (INVITE [ANM]) + + Note right of GMSC: 15 + GMSC->>MGWa: ACK + MGWa-->>GMSC: ACK + MGWa-->>MSC: ACK + +``` + +Sequence diagram for Basic Mobile Terminating Call, GMSC selects a MGW. Lifelines: GMSC, MGWa, MSC, MGWb, RNC/BSC, UE. The diagram shows the interaction between these components to establish a call, including UMTS and GSM bearer setup, ringing, and connection phases. + +Figure 6.2.1.3.14.2/2: Basic Mobile Terminating Call, GMSC selects a MGW (message sequence chart continue) + +## 6.2.2 Terminating Call Establishment For Iu Interface on IP with immediate MGW selection + +For IP transport over the IuCS the procedures in the present Clause shall apply in addition to the SIP-I based Core Network side procedures described in Clause 6.2.1. + +For the access side termination, the exchange of IP addresses as defined in the Clause 6.2.3 of 3GPP TS 23.205 [7] shall apply. + +If the bearer transport is IP and IuUP mode is Support, the MGW shall use the source IP address and UDP Port of the IuUP Init packet received from the radio access network as the destination address for subsequent downlink packets. + +The sequence is shown in Figure 6.2.2.1. + +![Sequence diagram for Terminating Call Establishment for Iu on IP. The diagram shows the interaction between GMSC, MGWa, MSC, MGWb, RNC/BSC, and UE. It details the signaling steps for UMTS context establishment and RAB assignment, with specific paths for IuUP Support Mode and Transparent Mode.](f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg) + +The diagram illustrates the signaling sequence for terminating call establishment over IP for the Iu interface. The participants are GMSC, MGWa, MSC, MGWb, RNC/BSC, and UE. The sequence is divided into two main parts by horizontal bars: "For preceding signalling sequences see Figures 6.2.1.3.14.2" at the top and "For succeeding signalling sequences see Figures 6.2.1.3.14.2" at the bottom. The main sequence of messages is as follows: + +- The MSC sends an **Add.request(\$)** to MGWb for Context (C1). +- MGWb responds with **Add.reply(T1)** containing "Prepare IP\_Transport + Change Through-Connection". +- The MSC then sends a **RAB\_ASSIGNMENT\_REQ** to RNC/BSC. +- A bracket labeled "For IuUP in Support Mode" encompasses the following steps: + - A box labeled "Bearer Establishment and Iu UP Initialization" is shown between MGWb and RNC/BSC. + - The RNC/BSC sends a **RAB\_ASSIGNMENT\_COMPL** back to the MSC. +- Another bracket labeled "For IuUP in Transparent Mode" encompasses: + - The MSC sends a **Mod.request(T1)** to MGWb for Context (C1). + - MGWb responds with **Mod.reply(T1)** containing "Modify IP Transport Address". + +Sequence diagram for Terminating Call Establishment for Iu on IP. The diagram shows the interaction between GMSC, MGWa, MSC, MGWb, RNC/BSC, and UE. It details the signaling steps for UMTS context establishment and RAB assignment, with specific paths for IuUP Support Mode and Transparent Mode. + +Figure 6.2.2.1: Terminating Call Establishment for Iu on IP + +## 6.2.3 Terminating Call Establishment For A Interface user plane over IP with immediate MGW selection + +For A interface user plane over IP, the procedures in the present Clause shall apply in addition to the SIP-I based Core Network side procedures described in Clause 6.2.1. + +For the access side termination, the exchange of IP addresses as defined in the Clause 6.2.4 of 3GPP TS 23.205 [7] shall apply. + +The sequence is shown in Figure 6.2.3.1. + +![Sequence diagram for Terminating Call Establishment for A interface user plane IP. The diagram shows interactions between GMSC, MGWa, MSC, MGWb, BSC, and UE. A bracket on the left labeled 'GSM:' groups the MSC, MGWb, and BSC. The sequence starts with MSC sending Add.request(S) to MGWb, which reserves an RTP connection point. MSC then sends ASSIGNMENT_REQ to BSC, which responds with ASSIGNMENT_COMPL. Finally, MSC sends Mod.request(T1) to MGWb to configure the RTP connection point, and MGWb responds with Mod.reply(T1). Context (C1) is indicated for the MSC and MGWb messages. A circled '8' is next to the first MSC message. Top and bottom boxes refer to preceding and succeeding signalling sequences in Figures 6.2.1.3.14.2.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant MGWa + participant MSC + participant MGWb + participant BSC + participant UE + + Note over GMSC, UE: For preceding signalling sequences see Figures 6.2.1.3.14.2 + + Note left of MGWa: GSM: + + MSC->>MGWb: Add.request(S) Context (C1) + Note right of MGWb: Reserve RTP Connection Point + Change Through-Connection + MGWb-->>MSC: Add.reply(T1) Context (C1) + MSC->>BSC: ASSIGNMENT_REQ + BSC-->>MSC: ASSIGNMENT_COMPL + MSC->>MGWb: Mod.request(T1) Context (C1) + Note right of MGWb: Configure RTP Connection Point + MGWb-->>MSC: Mod.reply(T1) Context (C1) + + Note over GMSC, UE: For succeeding signalling sequences see Figures 6.2.1.3.14.2 + +``` + +Sequence diagram for Terminating Call Establishment for A interface user plane IP. The diagram shows interactions between GMSC, MGWa, MSC, MGWb, BSC, and UE. A bracket on the left labeled 'GSM:' groups the MSC, MGWb, and BSC. The sequence starts with MSC sending Add.request(S) to MGWb, which reserves an RTP connection point. MSC then sends ASSIGNMENT\_REQ to BSC, which responds with ASSIGNMENT\_COMPL. Finally, MSC sends Mod.request(T1) to MGWb to configure the RTP connection point, and MGWb responds with Mod.reply(T1). Context (C1) is indicated for the MSC and MGWb messages. A circled '8' is next to the first MSC message. Top and bottom boxes refer to preceding and succeeding signalling sequences in Figures 6.2.1.3.14.2. + +Figure 6.2.3.1: Terminating Call Establishment for A interface user plane IP + +## 7 Call Clearing + +### 7.1 General + +The terms "incoming" and "outgoing" in the following text refers to the direction of propagation of the release indication, not to the direction of original call establishment. + +During call establishment, the call may be released by sending a BYE or CANCEL request in the direction of the original call establishment, or by a failure response in the opposite direction of the original call establishment. For an established call, the call may be released by BYE request in the direction of the original call establishment or in the opposite direction of the original call establishment. + +The term "release indication" in the following text refers to any message which is to release the call, i.e. it may be the BYE or CANCEL request, or the failure response to the initial INVITE request. + +In accordance with ITU-T Q.1912.5 [9] Profile C, the generation of: + +- a BYE request and a 4xx, 5xx, 6xx final response to initial INVITE should encapsulate an ISUP REL message. + +NOTE: there can be cases where it may not be possible to encapsulate an ISUP REL due to some specific error scenarios. Additionally it is possible that an IWU forwards a BYE or a 4xx, 5xx, 6xx final response without a REL. + +- a 200 OK final response to a BYE request shall encapsulate an ISUP RLC message if a BYE is received with an encapsulated REL. + +The user initiated call clearing shall be performed in accordance with 3GPP TS 23.108 [18]. + +NOTE: All message sequence charts in this clause are examples. All valid call clearing message sequences can be derived from the example message sequences and associated message pre-conditions. + +## 7.2 Visited MSC Server Procedures + +### 7.2.1 Call Clearing when Visited MSC Server has Forwarded/Deflected Call + +If the MSC server has forwarded/deflected the call to another terminating MSC server, call clearing is performed as described for the GMSC Server in clause 7.3. + +### 7.2.2 Call Clearing received from core network + +#### 7.2.2.1 Procedures towards access side + +The MSC server initiates call clearing towards the UE and requests release of the associated radio resources as described in 3GPP TS 23.108[18]. Once the call clearing and the release of the associated radio resources have been completed, the MSC server releases any MGW allocated resources for the access side. If any resources were seized in the MGW, the MSC server uses the Release Termination procedure to requests the MGW to remove the access side bearer termination. + +#### 7.2.2.2 Procedures towards network side + +##### 7.2.2.2.1 Call Clearing during establishment + +###### 7.2.2.2.1.1 Originating MSC-S + +If the release indication from the succeeding node is a failure response for the initial INVITE request, the MSC server shall send an ACK for the failure response to the succeeding node. + +The MSC server shall then perform the normal bearer release according to 7.2.6. + +NOTE: For early dialogue from O-MSC perspective, a BYE can only be received if it overtakes a 2xx response due to out-of-sequence packet delivery which should not be encountered with SCTP transport for SIP, as used on Nc + +###### 7.2.2.2.1.2 Terminating MSC-S + +If a CANCEL request to initial INVITE is received from the preceding node, the MSC server shall send a 200 OK response for the CANCEL request and the MSC server shall immediately send a 487 Request Terminated response for the initial INVITE request to the preceding node. + +NOTE: No final response for the initial INVITE request has previously been sent. + +If a BYE request is received from the preceding node, the MSC server shall send a 200 OK response for the BYE request, and immediately send a 487 Request Terminated response for the initial INVITE request to the preceding node. + +NOTE: A 487 final response is sent because of a reception of CANCEL/BYE request and does not contain encapsulated REL message. + +The MSC sever shall then perform the normal bearer release according to 7.2.6. + +##### 7.2.2.2.2 Call Clearing after call established + +###### 7.2.2.2.2.1 Originating MSC-S + +An MSC server that receives a BYE request from the succeeding node shall send a 200 OK response for the BYE request to the succeeding node. The MSC shall then perform the normal bearer release according to 7.2.6. + +###### 7.2.2.2.2.2 Terminating MSC-S + +If an MSC server receives a CANCEL request from the preceding node it shall send a 200 OK(CANCEL) final response for the CANCEL request but shall not take further action. + +If a BYE request is received from the preceding node, the MSC server shall send a 200 OK response for the BYE request to the preceding node. The MSC server shall then perform the normal bearer release according to 7.2.6. + +### 7.2.2.3 Example Call Flow + +Figure 7.2.2.3.1 shows the network model for a network initiated clearing of an established mobile call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. Bearer termination T1 is used for the bearer towards RNC/BSC and bearer termination T2 is used for the bearer towards succeeding MGW. + +![Figure 7.2.2.3.1: Network Initiated Call Clearing (Network model) diagram](0ee9d674085524d589646a6c3fb21ec3_img.jpg) + +The diagram illustrates the network model for call clearing. At the top is the MSC-S (Mobile Switching Center Server). Below it is the MGW (Media Gateway) with two bearer terminations labeled T1 and T2. To the left of the MGW is the RNC/BSC (Radio Network Controller/Base Station Controller). A green dashed line (call control signalling) connects the RNC/BSC to the MSC-S. A blue solid line (bearer control signalling) connects the MSC-S to the MGW. Red dotted lines (bearer) connect the RNC/BSC to the MGW (specifically to termination T1) and from the MGW (specifically from termination T2) to the right, representing a succeeding MGW. + +Figure 7.2.2.3.1: Network Initiated Call Clearing (Network model) diagram + +**Figure 7.2.2.3.1: Network Initiated Call Clearing (Network model)** + +Figure 7.2.2.3.2 shows the message sequence example for the network initiated clearing of an established mobile call. In the example when the call clearing indication is received from the preceding/succeeding node, the MSC server indicates to the preceding/succeeding node that call clearing has been completed and releases the network side bearer termination. The MSC server initiates call clearing towards the UE and requests release of the radio resource. After the response of the radio resource release is received then the MSC server requests release of the access side bearer termination. + +![Sequence diagram for Network Initiated Call Clearing showing interactions between UE, RNC/BSC, MSC-S, and MGW. It includes message flows for DISCONNECT, REL, RLC, IU RELEASE CMD, Bearer Release, IU RELEASE COMPLETE, CLEAR COMMAND, and CLEAR COMPLETE, with associated SUB.request and SUB.reply messages to the MGW for Release Termination.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +The sequence diagram illustrates the network-initiated call clearing process. It begins with the MSC-S sending a BYE message to the MGW, which responds with 200 OK (BYE). The MSC-S then sends a DISCONNECT message to the RNC/BSC, which in turn sends a REL message to the UE. The UE responds with an RLC message. The MSC-S sends a Context (C1) message to the RNC/BSC and a SUB.request(T2) to the MGW. The RNC/BSC sends an IU RELEASE CMD to the UE. A green bar labeled 'Bearer Release' indicates a period of activity. Following this, the RNC/BSC sends an IU RELEASE COMPLETE message to the MSC-S. The MSC-S sends Context (C1) and SUB.request(T1) to the MGW, receiving a SUB.reply(T1) in return. The MSC-S then sends Context(C1) to the RNC/BSC and a CLEAR COMMAND to the UE. The UE responds with a CLEAR COMPLETE message. Finally, the MSC-S sends Context (C1) and SUB.request(T1) to the MGW again, receiving a SUB.reply(T1). The MGW performs 'Release Termination' at several points in the process. + +Sequence diagram for Network Initiated Call Clearing showing interactions between UE, RNC/BSC, MSC-S, and MGW. It includes message flows for DISCONNECT, REL, RLC, IU RELEASE CMD, Bearer Release, IU RELEASE COMPLETE, CLEAR COMMAND, and CLEAR COMPLETE, with associated SUB.request and SUB.reply messages to the MGW for Release Termination. + +Figure 7.2.2.3.2: Network Initiated Call Clearing (message sequence chart) + +### 7.2.3 Call Clearing received from UE + +#### 7.2.3.1 Procedures towards access side + +Call clearing from the UE shall be performed in accordance with clause 7.2.2.1 in 3GPP TS 23.205 [7]. + +### 7.2.3.2 Procedures towards network side + +#### 7.2.3.2.1 Call Clearing during call establishment + +##### 7.2.3.2.1.1 Originating MSC-S + +If the MSC server has sent an initial INVITE request to the succeeding node, the MSC server shall apply SIP procedures detailed in IETF RFC 3261 [15] to terminate the corresponding SIP dialogue(s) and session(s), making use of CANCEL and/or BYE request(s). + +The MSC server shall then perform the normal bearer release according to 7.2.6. + +##### 7.2.3.2.1.2 Terminating MSC-S + +If the MSC server received an initial INVITE request from the preceding node and has not yet sent out a final response for the initial INVITE request, the MSC server shall send an appropriate failure response for the initial INVITE request to the preceding node. + +The MSC server shall then perform the normal bearer release according to 7.2.6. + +#### 7.2.3.2.2 Call Clearing after call established + +##### 7.2.3.2.2.1 Originating MSC-S + +If the MSC server has sent an initial INVITE request to the succeeding node and has received a final 200 OK (INVITE) response for the initial INVITE request, the MSC server shall send a BYE request to the succeeding node to release the call. + +The MSC server shall then perform the normal bearer release according to 7.2.6. + +If the call set-up fails and the MSC server plays an in-band tone or announcement to signal to the calling user the reason of the call failure, the MSC server shall initiate the call clearing with the SIP response code mapped from the ISUP cause No. 31 as specified in Table 9 of 3GPP TS 29.163 [32], and with encapsulated REL message with cause No. 31 "Normal, unspecified". + +##### 7.2.3.2.2.2 Terminating MSC-S + +If the MSC server received an initial INVITE request from the preceding node and a successful final response for the initial INVITE request has been sent out, the MSC server shall send a BYE request to release the call. + +The MSC server shall then perform the normal bearer release according to 7.2.6. + +### 7.2.3.3 Example Call Flow + +Figure 7.2.3.3.1 shows the network model for a user initiated clearing of an established mobile call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. Bearer termination T1 is used for the bearer towards RNC/BSC and bearer termination T2 is used for the bearer towards succeeding MGW. + +![Diagram of the network model for user initiated call clearing. It shows three main components: an RNC/BSC on the left, an MSC-S at the top, and an MGW at the bottom. A green dashed line (call control signalling) connects the RNC/BSC to the MSC-S. A blue solid line (bearer control signalling) connects the MSC-S to the MGW. A red dotted line (bearer) connects the RNC/BSC to the MGW. The MGW has two bearer terminations labeled T1 and T2. T1 is connected to the RNC/BSC via the red dotted line. T2 is connected to a succeeding MGW (represented by a red dotted line extending to the right).](54e4bda94c608845a162d52a75e67ce4_img.jpg) + +Diagram of the network model for user initiated call clearing. It shows three main components: an RNC/BSC on the left, an MSC-S at the top, and an MGW at the bottom. A green dashed line (call control signalling) connects the RNC/BSC to the MSC-S. A blue solid line (bearer control signalling) connects the MSC-S to the MGW. A red dotted line (bearer) connects the RNC/BSC to the MGW. The MGW has two bearer terminations labeled T1 and T2. T1 is connected to the RNC/BSC via the red dotted line. T2 is connected to a succeeding MGW (represented by a red dotted line extending to the right). + +Figure 7.2.3.3.1: User Initiated Call Clearing (Network model) + +Figure 7.2.3.3.2 shows the message sequence example for the user initiated clearing of an established mobile call. In the example the UE initiates call clearing towards the MSC server and the MSC server requests release of the radio resource. After the response of the radio resource release is received the MSC server requests the release of the access side bearer termination. The MSC server initiates call clearing towards the preceding/succeeding node. Once the preceding/succeeding node has indicated that call clearing has been completed, the MSC server releases the network side bearer termination. + +![Figure 7.2.3.3.2: User Initiated Call Clearing (message sequence chart). The diagram shows the interaction between UE, RNC/BSC, MSC-S, and MGW. The process starts with DISCONNECT from UE to MSC-S. MSC-S sends BYE to MGW. UE sends REL and RLC to MSC-S. MSC-S sends IU RELEASE CMD to RNC/BSC (marked with circled 1). A green 'Bearer Release' bar spans from RNC/BSC to MGW. RNC/BSC sends IU RELEASE COMPLETE (Context (C1)) to MSC-S. MSC-S sends SUB.request (T1) to MGW, which responds with SUB.reply (T1) and 'Release Termination'. MSC-S sends CLEAR COMMAND to RNC/BSC (marked with circled 2). RNC/BSC sends CLEAR COMPLETE (Context (C1)) to MSC-S. MSC-S sends SUB.request (T1) to MGW, which responds with SUB.reply (T1) and 'Release Termination'. MGW sends 200 OK (BYE) to MSC-S. MSC-S sends SUB.request (T2) to MGW (marked with circled 3), which responds with SUB.reply (T2) and 'Release Termination'. Brackets on the left indicate UMTS and GSM protocols. Brackets on the right indicate 'Release Termination' phases.](04cfca33e3fc26513abe649d7474f733_img.jpg) + +Figure 7.2.3.3.2: User Initiated Call Clearing (message sequence chart). The diagram shows the interaction between UE, RNC/BSC, MSC-S, and MGW. The process starts with DISCONNECT from UE to MSC-S. MSC-S sends BYE to MGW. UE sends REL and RLC to MSC-S. MSC-S sends IU RELEASE CMD to RNC/BSC (marked with circled 1). A green 'Bearer Release' bar spans from RNC/BSC to MGW. RNC/BSC sends IU RELEASE COMPLETE (Context (C1)) to MSC-S. MSC-S sends SUB.request (T1) to MGW, which responds with SUB.reply (T1) and 'Release Termination'. MSC-S sends CLEAR COMMAND to RNC/BSC (marked with circled 2). RNC/BSC sends CLEAR COMPLETE (Context (C1)) to MSC-S. MSC-S sends SUB.request (T1) to MGW, which responds with SUB.reply (T1) and 'Release Termination'. MGW sends 200 OK (BYE) to MSC-S. MSC-S sends SUB.request (T2) to MGW (marked with circled 3), which responds with SUB.reply (T2) and 'Release Termination'. Brackets on the left indicate UMTS and GSM protocols. Brackets on the right indicate 'Release Termination' phases. + +Figure 7.2.3.3.2: User Initiated Call Clearing (message sequence chart) + +## 7.2.4 Call Clearing initiated by V- MSC Server + +### 7.2.4.1 Call clearing towards access network + +Call clearing to the UE is performed as described in clause 7.2.2.1. + +### 7.2.4.2 Call clearing towards network side + +Call clearing to the network side is performed as described in clause 7.2.3.2 + +### 7.2.4.3 Example Call Flow + +Figure 7.2.4.3.1 shows the network model for a MSC server initiated clearing of an established mobile call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer + +terminations in the MGW. Bearer termination T1 is used for the bearer towards RNC/BSC and bearer termination T2 is used for the bearer towards succeeding MGW. + +![Diagram of MSC Server Initiated Call Clearing (Network model)](b58cedaf15ad4f0edee5621820865ccc_img.jpg) + +The diagram illustrates the network model for MSC server initiated call clearing. It features four main components: an RNC/BSC (Radio Network Controller/Base Station Controller) on the left, an MSC-S (MSC Server) at the top, and an MGW (Media Gateway) at the bottom. The RNC/BSC is connected to the MSC-S via a dashed green line. The MSC-S is connected to the MGW via a solid blue line. The MGW has two bearers: T1 (CTXI) connected to the RNC/BSC via a dashed red line, and T2 (CTXI) connected to a succeeding MGW via a dashed red line. The MGW is labeled with 'CTXI' and 'MGW'. + +Diagram of MSC Server Initiated Call Clearing (Network model) + +**Figure 7.2.4.3.1: MSC Server Initiated Call Clearing (Network model)** + +Figure 7.2.4.3.2 shows the message sequence example for the MSC server initiated clearing of an established mobile call. In the example the MSC server initiates call clearing of the network side and the access side. After the call clearing towards the UE and the release of the radio resource have been completed the MSC server requests release of the access side bearer termination. Once the preceding/succeeding node has indicated that call clearing has been completed, the MSC server requests the MGW to release the network side bearer termination. + +![Figure 7.2.4.3.1: MSC Server Initiated Call Clearing (message sequence chart). The diagram illustrates the signaling flow between UE, RNC/BSC, MSC-S, and MGW for call clearing. It shows two main branches: UMTS and GSM. In UMTS, an IU RELEASE CMD is sent from MSC-S to RNC/BSC, followed by a Bearer Release block and IU RELEASE COMPLETE. In GSM, a CLEAR COMMAND is sent from MSC-S to RNC/BSC, followed by CLEAR COMPLETE. Both branches involve SUB.request and SUB.reply messages between MSC-S and MGW for 'Release Termination' of Context (C1) at termination T1. Additionally, a BYE message is sent from MSC-S to an external network, and a 200 OK (BYE) is received, triggering another Release Termination for Context (C1) at termination T2. Initial signaling includes DISCONNECT, REL, and RLC between UE and MSC-S/RNC/BSC.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + participant Network + + MSC-S->>UE: DISCONNECT + UE->>MSC-S: REL + MSC-S->>UE: RLC + MSC-S->>Network: BYE + + Note over RNC/BSC, MSC-S: UMTS: + MSC-S->>RNC/BSC: IU RELEASE CMD (1) + rect rgb(200, 255, 200) + Note over RNC/BSC, MGW: Bearer Release + end + RNC/BSC->>MSC-S: IU RELEASE COMPLETE + MSC-S->>MGW: Context (C1) SUB.request (T1) + MGW->>MSC-S: SUB.reply (T1) + Note right of MGW: Release Termination + + Note over RNC/BSC, MSC-S: GSM: + MSC-S->>RNC/BSC: CLEAR COMMAND (2) + RNC/BSC->>MSC-S: CLEAR COMPLETE + MSC-S->>MGW: Context (C1) SUB.request (T1) + MGW->>MSC-S: SUB.reply (T1) + Note right of MGW: Release Termination + + Network-->>MSC-S: 200 OK (BYE) (3) + MSC-S->>MGW: Context (C1) SUB.request (T2) + MGW->>MSC-S: SUB.reply (T2) + Note right of MGW: Release Termination + +``` + +Figure 7.2.4.3.1: MSC Server Initiated Call Clearing (message sequence chart). The diagram illustrates the signaling flow between UE, RNC/BSC, MSC-S, and MGW for call clearing. It shows two main branches: UMTS and GSM. In UMTS, an IU RELEASE CMD is sent from MSC-S to RNC/BSC, followed by a Bearer Release block and IU RELEASE COMPLETE. In GSM, a CLEAR COMMAND is sent from MSC-S to RNC/BSC, followed by CLEAR COMPLETE. Both branches involve SUB.request and SUB.reply messages between MSC-S and MGW for 'Release Termination' of Context (C1) at termination T1. Additionally, a BYE message is sent from MSC-S to an external network, and a 200 OK (BYE) is received, triggering another Release Termination for Context (C1) at termination T2. Initial signaling includes DISCONNECT, REL, and RLC between UE and MSC-S/RNC/BSC. + +**Figure 7.2.4.3.1: MSC Server Initiated Call Clearing (message sequence chart)** + +## 7.2.5 Call clearing received from MGW + +### 7.2.5.1 Bearer released on the access side + +After the MSC server has received the Bearer Released procedure from the MGW on the access side, the MSC server shall release the access resources as described in clause 7.2.2.1. If the call is already established towards the network side, call clearing to the network side is performed as described in clause 7.2.3.2. + +### 7.2.5.2 Bearer released on the network side + +After the MSC server has received the Bearer Released procedure from the MGW on the network side, the MSC server shall clear the call to the network side as described in clause 7.2.3.2, and clear the call to the UE as described in clause 7.2.2.1. + +### 7.2.5.3 Example Call Flow + +Figure 7.2.5.3.1 shows the network model for an MGW initiated clearing of an established mobile call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. Bearer termination T1 is used for the bearer towards RNC/BSC and bearer termination T2 is used for the bearer towards succeeding MGW. + +![Figure 7.2.5.3.1: MGW Initiated Call Clearing (Network model) diagram showing MSC-S, RNC/BSC, and MGW components and their connections.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +The diagram shows three main components: MSC-S (top), RNC/BSC (bottom left), and MGW (bottom center). The MGW is connected to the MSC-S via a solid blue line. The MGW has two interfaces labeled T1 and T2. A red dotted line connects the RNC/BSC to the MGW's T1 interface. A green dashed line connects the RNC/BSC to the MSC-S. The MGW is also labeled CTX1. + +Figure 7.2.5.3.1: MGW Initiated Call Clearing (Network model) diagram showing MSC-S, RNC/BSC, and MGW components and their connections. + +Figure 7.2.5.3.1: MGW Initiated Call Clearing (Network model) + +Figure 7.2.5.3.2 shows the message sequence example for the MGW initiated clearing of an established mobile call. After the MSC server is notified that the MGW has released the network side bearer, the MSC server initiates call clearing of the network side and the access side. After the call clearing towards the UE and the radio resource release have been completed the MSC server requests release of the access side bearer termination. Once the preceding/succeeding node has indicated that call clearing has been completed, the MSC server requests the release of the network side bearer termination. + +![Figure 7.2.5.3.2: MGW Initiated Call Clearing (message sequence chart) showing the sequence of messages between UE, RNC/BSC, MSC-S, and MGW.](8c880d6b715587bd710a9ba8414469b1_img.jpg) + +The sequence chart shows the interaction between UE, RNC/BSC, MSC-S, and MGW. The sequence is as follows: + +- The MGW sends a **NOTIFY.request (T2)** to the MSC-S. The MSC-S responds with **Context (C1)** and **NOTIFY.reply (T2)**. The MGW then sends a **BYE** message to the UE. +- The MSC-S sends a **DISCONNECT** message to the RNC/BSC. The RNC/BSC responds with **REL** and **RLC** messages. The MSC-S then sends an **IU RELEASE CMD** to the RNC/BSC. +- A **Bearer Release** phase occurs between the RNC/BSC and the MGW. The RNC/BSC sends an **IU RELEASE COMPLETE** message to the MGW. The MGW then sends a **SUB.request (T1)** to the MSC-S, which responds with **Context (C1)** and **SUB.reply (T1)**. This is followed by a **Release Termination** message from the MGW to the MSC-S. +- The RNC/BSC sends a **CLEAR COMMAND** to the MSC-S. The MSC-S responds with **CLEAR COMPLETE**. The RNC/BSC then sends a **Context (C1)** message to the MGW. The MGW sends a **SUB.request (T1)** to the MSC-S, which responds with **Context (C1)** and **SUB.reply (T1)**. This is followed by a **Release Termination** message from the MGW to the MSC-S. +- The MGW sends a **200 OK (BYE)** message to the MSC-S. The MSC-S then sends a **SUB.request (T2)** to the MGW, which responds with **SUB.reply (T2)**. This is followed by a **Release Termination** message from the MGW to the MSC-S. + +The sequence is divided into two main sections: **UMTS:** (steps 1-3) and **GSM:** (steps 4-5). The MGW also sends a **Bearer Released** message to the MSC-S at the beginning of the sequence. + +Figure 7.2.5.3.2: MGW Initiated Call Clearing (message sequence chart) showing the sequence of messages between UE, RNC/BSC, MSC-S, and MGW. + +Figure 7.2.5.3.2: MGW Initiated Call Clearing (message sequence chart) + +## 7.2.6 Call Clearing procedures towards MGW + +The MSC server shall release any network side MGW allocated resources reserved for the call. If any resources were seized in the MGW the MSC server shall use the Release Termination procedure to indicate to the MGW to remove the bearer termination. + +## 7.2.7 Call Clearing for Iu Interface on IP + +Procedures for Call Clearing where the Iu Interface is on IP are as described in clauses through 7.2.2 to 7.2.6. + +For Iu Interface on IP, the Release Termination procedure for IP is used to clear the Access side bearer termination. + +# 7.3 Gateway MSC Server Procedures + +## 7.3.1 Call Clearing received from peer SIP-I node + +If a release indication (CANCEL, BYE, final error response (4xx, 5xx or 6xx) for the initial INVITE request) is received from the preceding or succeeding node, and the GMSC server decides to release the call, the GMSC server shall: + +- a. process those request according to SIP procedures for a user agent towards the preceding or succeeding side as specified in IETF RFC 3261 [15], and initiate a call release towards the succeeding or preceding node acting as user agent as specified in IETF RFC 3261 [15], or +- b. perform the following procedures: + 1. If the GMSC receives a CANCEL request from the preceding node, the GMSC shall send a 200 OK (CANCEL) response for the CANCEL request to the preceding node. If the GMSC did not yet receive a final response for the initial INVITE request from the succeeding node, the GMSC shall then initiate a CANCEL request to the succeeding node. + 2. If the GMSC server receives a BYE request from the preceding/succeeding node, the GMSC shall perform the procedure described in Clause 7.3.4 to release seized MGW resources, and forward the BYE request to the succeeding/preceding node. The GMSC server will then receive a 200 OK(BYE) response from the succeeding/preceding node and shall forward this 200 OK(BYE) response to the preceding/succeeding node. + 3. If the GMSC server receives a final error response (4xx, 5xx or 6xx) for the initial INVITE request from the succeeding node, the GMSC server shall perform the procedure described in Clause 7.3.4 to release seized MGW resources, and then forward a final error response (either the received response or an error response resulting from internal mapping procedures) to the preceding node. + +Note: The procedures under bullet b. are similar to SIP proxy procedures, as specified in IETF RFC 3261 [15], with the exception that the GMSC server sets SIP headers (e.g. contact, via) in forwarded SIP messages consistent with earlier settings during the dialogue. + +The GMSC shall also perform the procedure described in Clause 7.3.4 to release seized MGW resources + +## 7.3.2 Call Clearing initiated by G- MSC Server + +### 7.3.2.1 Call clearing to the destination side + +If the call is already established or under establishment towards the destination, call clearing to the destination side from the GMSC server is performed as described for the originating MSC server in clause 7.2.3.2. + +### 7.3.2.2 Call clearing to the originating side + +Call clearing to the originating side from the GMSC server is performed as described for the terminating MSC server in clause 7.2.3.2. + +### 7.3.3 Call Clearing received from MGW + +#### 7.3.3.1 Bearer released on the destination side + +After the GMSC server received the Bearer Released procedure from the MGW on the destination side, call clearing to the destination side and the originating side from the GMSC server is performed as described for the originating MSC server and for the terminating MSC server in clause 7.2.3.2 respectively. + +#### 7.3.3.2 Bearer released on the originating side + +After the GMSC server received the Bearer Released procedure from the MGW on the originating side, call clearing to the originating side from the GMSC server is performed as described for the terminating MSC server in clause 7.2.3.2. If the call is already established or under establishment towards the destination side, call clearing to the destination side is performed as described for the originating MSC server in clause 7.2.3.2. + +### 7.3.4 Call Clearing procedures towards MGW + +The (G)MSC server shall release any MGW allocated resources reserved for the call. If any resources were seized in the MGW the MSC server shall use the Release Termination procedure to indicate to the MGW to remove the bearer termination. + +--- + +## 8 Handover/Relocation + +NOTE: All message sequence charts in this clause are examples. All valid handover/relocation message sequences can be derived from the example message sequences and associated message pre-conditions. + +### 8.1 UMTS to UMTS + +In the context of the following clauses, the terms RNS or RNC refer also to a GERAN BSS or BSC (respectively) when serving an UE in Iu mode. + +#### 8.1.1 Intra-MSC SRNS/SBSS Relocation + +The procedures specified in 3GPP TS 23.009 [13] for "Intra-3G\_MSC SRNS Relocation" shall be followed. The following clauses describe the additional requirements for the SIP-I based CS core network. + +##### 8.1.1.1 Intra-MGW Relocation + +The handling of Intra-MSC Intra-MGW SRNS/SBSS Relocation shall be performed in accordance with clause 8.1.1 of 3GPP TS 23.205 [7]. + +##### 8.1.1.2 Inter-MGW Relocation + +Procedures used for the Intra-MSC Inter-MGW SRNS/SBSS Relocation are equivalent to those specified in accordance with 3GPP TS 23.205 [7], with the exception that the procedures for establishing the bearer between the MGW will be in accordance with normal procedures as defined within clause 15.2. + +#### 8.1.2 Basic Inter-MSC SRNS/SBSS Relocation + +Procedures used for the basic Inter-MSC SRNS/SBSS Relocation are equivalent to those specified in accordance to clause 8.1.2 of 3GPP TS 23.205 [7], with the exception that the call and bearer establishment procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +#### 8.1.3 Subsequent Inter-MSC SRNS/SBSS Relocation back to the Anchor MSC + +Procedures used for the subsequent Inter-MSC SRNS/SBSS Relocation back to the anchor MSC are equivalent to those specified in accordance to clause 8.1.3 of 3GPP TS 23.205 [7], with the exception that the call clearing and bearer release procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +## 8.1.4 Subsequent Inter-MSC SRNS/SBSS Relocation to a third MSC + +Procedures used for the subsequent Inter-MSC SRNS/SBSS Relocation to a third MSC are equivalent to those specified in accordance to clause 8.1.4 of 3GPP TS 23.205 [7], with the exception that the call establishment, call clearing, bearer establishment and bearer release procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +## 8.1.5 SRNS/SBSS Relocation with Iu on IP + +If IuCS on IP is supported by the MSC server, the Core Network side procedures described in clauses through 8.1.1 to 8.1.4 shall apply, and the Access Network side procedures described in clause 8.1.5 of 3GPP TS 23.205 [2] shall apply. + +# 8.2 UMTS to GSM + +In the context of the following clauses, the terms RNS or RNC refer also to a GERAN BSS or BSC (respectively) when serving an UE in Iu mode. + +## 8.2.1 Intra-MSC UMTS to GSM Handover + +The procedures specified in 3GPP TS 23.009 [13] for "Intra-3G\_MSC Handover from UMTS to GSM" shall be followed. The following clauses describe the additional requirements for the SIP-I based CS core network. + +### 8.2.1.1 Intra-MGW Relocation + +The handling of Intra-MSC Intra-MGW UMTS to GSM Handover shall be performed in accordance with clause 8.2.1 of 3GPP TS 23.205 [7]. + +### 8.2.1.2 Inter-MGW Relocation + +Procedures used for the Intra-MSC Inter-MGW UMTS to GSM Handover are equivalent to those specified in accordance with 3GPP TS 23.205 [7], with the exception that the procedures for establishing the bearer between the MGW will be in accordance with normal procedures as defined within clause 15.2. + +### 8.2.1.3 Intra-MSC UMTS to GSM Handover for A interface over IP + +The handling of Intra-MSC UMTS to GSM Handover for A interface over IP shall be performed in accordance with clause 8.2.1.10 of 3GPP TS 23.205 [7]. + +## 8.2.2 Basic Inter-MSC UMTS to GSM Handover + +Procedures used for the basic Inter-MSC UMTS to GSM Handover are equivalent to those specified in accordance to clause 8.2.2 of 3GPP TS 23.205 [7], with the exception that the call and bearer establishment procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +### 8.2.2.1 Basic Inter-MSC UMTS to GSM Handover for A Interface over IP + +The handling of Basic MSC UMTS to GSM Handover for A interface over IP shall be performed in accordance with clause 8.2.2.3 of 3GPP TS 23.205 [7]. + +## 8.2.3 Subsequent Inter-MSC UMTS to GSM Handover back to the Anchor MSC + +Procedures used for the subsequent Inter-MSC UMTS to GSM Handover back to the anchor MSC are equivalent to those specified in accordance to clause 8.2.3 of 3GPP TS 23.205 [7], with the exception that the call clearing and bearer release procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +### 8.2.3.1 Subsequent Inter-MSC UMTS to GSM Handover back to the anchor MSC for A Interface over IP + +The handling of Subsequent Inter-MSC UMTS to GSM Handover back to the anchor MSC for A Interface over IP shall be performed in accordance with clause 8.2.3.3 of 3GPP TS 23.205 [7]. + +## 8.2.4 Subsequent Inter-MSC UMTS to GSM Handover to a third MSC + +Procedures used for the subsequent Inter-MSC UMTS to GSM Handover to a third MSC are equivalent to those specified in accordance to clause 8.2.4 of 3GPP TS 23.205 [7], with the exception that the call establishment, call clearing, bearer establishment and bearer release procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +## 8.3 GSM to UMTS + +### 8.3.1 Intra-MSC GSM to UMTS Handover + +The procedures specified in 3GPP TS 23.009 [13] for "Intra-3G\_MSC GSM to UMTS Handover" shall be followed. The following clauses describe the additional requirements for the SIP-I based CS core network. + +#### 8.3.1.1 Intra-MGW Relocation + +The handling of Intra-MSC Intra-MGW GSM to UMTS Handover shall be performed in accordance with clause 8.2.1 of 3GPP TS 23.205 [7]. + +#### 8.3.1.2 Inter-MGW Relocation + +Procedures used for the Intra-MSC Inter-MGW GSM to UMTS Handover are equivalent to those specified in accordance with 3GPP TS 23.205 [7], with the exception that the procedures for establishing the bearer between the MGW will be in accordance with normal procedures as defined within clause 15.2. + +### 8.3.2 Basic Inter-MSC GSM to UMTS Handover + +Procedures used for the basic Inter-MSC GSM to UMTS Handover are equivalent to those specified in accordance to clause 8.3.2 of 3GPP TS 23.205 [7], with the exception that the call and bearer establishment procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +### 8.3.3 Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC + +Procedures used for the subsequent Inter-MSC GSM to UMTS Handover back to the anchor MSC are equivalent to those specified in accordance to clause 8.3.3 of 3GPP TS 23.205 [7], with the exception that the call clearing and bearer release procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +### 8.3.4 Subsequent Inter-MSC GSM to UMTS Handover to a third MSC + +Procedures used for the subsequent Inter-MSC GSM to UMTS Handover to a third MSC are equivalent to those specified in accordance to clause 8.3.4 of 3GPP TS 23.205 [7], with the exception that the call establishment, call clearing, bearer establishment and bearer release procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +### 8.3.5 GSM to UMTS Handover with Iu on IP + +If IuCS on IP is supported by the MSC server, the Core Network side procedures described in clauses through 8.3.1 to 8.3.4 shall apply, and the Access Network side procedures described in clause 8.3.5 of 3GPP TS 23.205 [2] shall apply. + +## 8.4 GSM to GSM + +### 8.4.1 Intra-MSC Inter-BSS GSM to GSM Handover + +The procedures specified in 3GPP TS 23.009 [13] for "Intra-MSC Handover" shall be followed. The following clauses describe the additional requirements for the SIP-I based CS core network. + +#### 8.4.1.1 Intra-MGW Relocation + +The handling of Intra-MSC Intra-MGW GSM to GSM Handover shall be performed in accordance with clause 8.4.1 of 3GPP TS 23.205 [7]. + +#### 8.4.1.2 Inter-MGW Relocation + +Procedures used for the Intra-MSC Inter-MGW GSM to GSM Handover are equivalent to those specified in accordance with 3GPP TS 23.205 [7], with the exception that the procedures for establishing the bearer between the MGW will be in accordance with normal procedures as defined within clause 15.2. + +#### 8.4.1.3 Intra-MSC GSM to GSM Handover for A interface over IP + +The handling of Intra-MSC GSM to GSM Handover for A interface over IP shall be performed in accordance with clause 8.4.1.9 of 3GPP TS 23.205 [7]. + +### 8.4.2 Basic Inter-MSC GSM to GSM Handover + +Procedures used for the basic Inter-MSC GSM to GSM Handover are equivalent to those specified in accordance to clause 8.4.2 of 3GPP TS 23.205 [7], with the exception that the call and bearer establishment procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +#### 8.4.2.1 Basic Inter-MSC GSM to GSM Handover for A Interface over IP + +The handling of Basic Inter-MSC GSM to GSM Handover for A Interface over IP shall be performed in accordance with clause 8.4.2.3 of 3GPP TS 23.205 [7]. + +### 8.4.3 Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC + +Procedures used for the subsequent Inter-MSC GSM to GSM Handover back to the anchor MSC are equivalent to those specified in accordance to clause 8.4.3 of 3GPP TS 23.205 [7], with the exception that the call clearing and bearer release procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +#### 8.4.3.1 Subsequent Inter-MSC GSM to GSM Handover back to the anchor MSC for A Interface over IP + +The handling of Subsequent Inter-MSC GSM to GSM Handover back to the anchor MSC for A Interface over IP shall be performed in accordance with clause 8.4.3.3 of 3GPP TS 23.205 [7]. + +### 8.4.4 Subsequent GSM to GSM Handover to a third MSC + +Procedures used for the subsequent Inter-MSC GSM to GSM Handover to a third MSC are equivalent to those specified in accordance to clause 8.4.4 of 3GPP TS 23.205 [7], with the exception that the call establishment, call clearing, bearer establishment and bearer release procedures between the MSCs and MGWs will be in accordance with normal procedures as defined within clause 15.2. + +### 8.4.5 BSS Internal Handover + +The handling of Intra-MSC BSS Internal Handover shall be performed in accordance with clause 8.4.5 of 3GPP TS 23.205 [7]. + +--- + +## 9 Compatibility Issues + +### 9.1 Compatibility Issues for Nc Interface + +A Release 8 (or later) (G)MSC-S implementing a SIP-I based Nc interface, according to 3GPP TS 23.231, is backward compatible with a Release 7 (or earlier) (G)MSC-S or (G)MSC by implementing the interworking procedures defined in 3GPP TS 29.235 [21]. + +## 9.2 Compatibility Issues for Mc Interface + +A Release 8 (or later) (G)MSC-S implementing a SIP-I based Nc interface, according to 3GPP TS 23.231, shall be deployed with a Release 8 (or later) MGW implementing at least Version 4 of the 3GPP Mc Profile Name "Threegbicsn" defined in 3GPP TS 29.232 [8]. + +--- + +## 10 General (G)MSC server-MGW Procedures + +### 10.1 MGW Unavailable + +See Clause 10.1 of 3GPP TS 23.205 [7]. + +### 10.2 MGW Available + +See Clause 10.2 of 3GPP TS 23.205 [7]. + +### 10.3 MGW Recovery + +See Clause 10.3 of 3GPP TS 23.205 [7]. + +### 10.4 (G)MSC server Recovery + +See Clause 10.4 of 3GPP TS 23.205 [7]. + +### 10.5 MGW Re-register + +See Clause 10.5 of 3GPP TS 23.205 [7]. + +### 10.6 MGW Re-registration Ordered by (G)MSC server + +See Clause 10.6 of 3GPP TS 23.205 [7]. + +### 10.7 Removal from Service of a Physical Termination + +See Clause 10.7 of 3GPP TS 23.205 [7]. + +### 10.8 Restoration to Service of a Physical Termination + +See Clause 10.8 of 3GPP TS 23.205 [7]. + +### 10.9 Audit of MGW + +See Clause 10.9 of 3GPP TS 23.205 [7]. + +### 10.10 MGW Capability Change + +See Clause 10.10 of 3GPP TS 23.205 [7]. + +### 10.11 (G)MSC Server Out of service + +See Clause 10.12 of 3GPP TS 23.205 [7]. + +### 10.12 MGW Resource Congestion Handling - Activate + +See Clause 10.13 of 3GPP TS 23.205 [7]. + +## 10.13 MGW Resource Congestion Handling -Indication + +See Clause 10.14 of 3GPP TS 23.205 [7]. + +## 10.14 Control association monitoring + +See Clause 10.15 of 3GPP TS 23.205 [7]. + +## 10.15 Hanging termination detection + +See Clause 10.16 of 3GPP TS 23.205 [7]. + +--- + +# 11 Identities + +## 11.1 Telephone numbering schemes + +(G)MSC-Servers shall support the receipt of Tel-URI and SIP URI (user=phone) and the sending of Tel-URI. The sending of SIP URI (user=phone) may be supported as an option. Both global and local telephone numbering formats shall be supported as per IETF RFC 3966 [10]. + +## 11.2 (G)MSC Server Identity + +**Editor's Note:** The (G)MSC Server Identity is FFS. + +## 11.3 Sub-addressing + +When using a Tel URI or a SIP-URI, the "isub" parameter defined within IETF RFC 3966 [10] may be used to include the ISDN sub-address as may be required within the MSISDN. See 3GPP TS 23.003 [28]. When the "isub" parameter is present, the "isub-encoding" parameter defined within IETF RFC 4715 [29] shall be used to define the ISDN subaddress encoding type. + +The procedures specified within ITU-T Q.1912.5 [9] Annex B.5 for profile C shall be applied for Sub-addressing. + +--- + +# 12 Operational Aspects + +## 12.1 Charging + +No impacts. + +## 12.2 SIP session continuity + +### 12.2.1 Use of SIP session timer + +The basic SIP as defined by IETF RFC 3261 [15] does not include a "keep alive" mechanism. As such, it is possible that one end of a session may fail and be unable to signal the release of the session. One possible scenario where this may occur is in the cases where an internal fault on a remote node results in the call instance being lost on the remote node. This would result in no further signalling from the remote node associated with that call instance. The local node would have no indication from the remote node should that party release the call. + +(G)MSC Servers may support the SIP Session Timer as specified in IETF RFC 4028 [16] as a means to determine whether a SIP session is still active by attempting to perform a session refresh, and therefore as a means to know when resources may be released if one end of the session fails. + +The procedure negotiates the rate at which the session refresh occurs. The procedure is compatible and still operational should the far end or other SIP entity not support the Session Timer procedure. + +## 12.2.2 Example call flow + +Figure 12.2.2.1 shows a message sequence example for the optional use of the SIP Session Timer procedures. During call origination each MSC Server may negotiate the use of the SIP Session Timer. This is accomplished through the exchange of the *Session-Expires* and *Min-SE* SIP header in the INVITE request and 2xx response. Support of the session timer extension procedure is indicated by placing the "timer" tag in the Supported header in the INVITE request. The use of session continuity and the session expiration timer value may be negotiated independently between each MSC Server pair. The session refresh request may be either an INVITE request or UPDATE request. The use of the UPDATE request does not require the exchange of SDP and is recommended by RFC 4028 [16]. + +When a failure of the session continuity is detected, the call will be cleared by the MSC servers independently on either side of the failure point according to the normal call clearing procedures (see sub-clause 7). + +![Sequence diagram illustrating SIP Session Timer procedures. The diagram shows two parallel call flows. The left flow involves UE, RNC/BSC, MGWa, and MSC-S. The right flow involves GMSC-S, MGWb, MSC-S, MGWc, RNC/BSC, and UE. The sequence of events is: 1. Basic mobile originating call procedures. 2. UPDATE request from MSC-S to GMSC-S, followed by 200 OK (UPDATE) response. 3. Failure occurs at the MSC-S on the left. 4. UPDATE request from MSC-S on the left is rejected (indicated by X). 6. Network initiated call clearing procedures on the left and GMSC-S initiated call clearing procedures on the right.](4346261cc730a1eb683f35e4ce9deacf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MGWa + participant MSC-S + participant GMSC-S + participant MGWb + participant MSC-S + participant MGWc + participant RNC/BSC + participant UE + + Note left of MSC-S: Basic mobile originating call procedures + Note right of MGWc: Basic mobile originating call procedures + + Note left of GMSC-S: 1 + Note right of MGWc: 1 + + Note left of MSC-S: 2 + Note right of GMSC-S: 2 + + Note left of GMSC-S: 3 + Note right of MGWc: 3 + + Note left of MSC-S: 4 + Note right of GMSC-S: 4 + + Note left of MSC-S: 6 + Note right of MGWc: 6 + + Note left of MSC-S: Network initiated call clearing procedures + Note right of MGWc: GMSC-S initiated call clearing procedures + +``` + +Sequence diagram illustrating SIP Session Timer procedures. The diagram shows two parallel call flows. The left flow involves UE, RNC/BSC, MGWa, and MSC-S. The right flow involves GMSC-S, MGWb, MSC-S, MGWc, RNC/BSC, and UE. The sequence of events is: 1. Basic mobile originating call procedures. 2. UPDATE request from MSC-S to GMSC-S, followed by 200 OK (UPDATE) response. 3. Failure occurs at the MSC-S on the left. 4. UPDATE request from MSC-S on the left is rejected (indicated by X). 6. Network initiated call clearing procedures on the left and GMSC-S initiated call clearing procedures on the right. + +Figure 12.2.2.1 SIP Session Timer + +## 13 Interactions with Other Services + +### 13.1 Enhanced Multi-Level Precedence and Pre-emption service (eMLPP) + +No impact. + +### 13.2 Call Deflection Service + +The procedures specified for the Call Deflection service in 3GPP TS 23.205 [7] sub-clause 13.2 shall be followed, with the following modifications: + +- The call establishment and call clearing procedures defined in clauses 6 and 7 shall be applied; +- The procedures for providing in-band information defined in sub-clause 14.6 shall be applied. +- Optimized or deferred MGW selection may apply for the establishment of the bearer towards the forwarded-to subscriber, as specified in sub-clauses 4.4.2 and 4.4.3. +- If there is no need for the (G)MSC server to manipulate the bearer, the (G)MSC server may apply MGW bypass as specified in sub-clause 4.4.5. Whilst this is true for CD prior to the assignment, after the assignment, the MSC behaviour should be the same as CFNRy. + +## 13.3 Line identification Services + +### 13.3.1 Calling Line Identification Presentation (CLIP) + +The procedures specified ITU-T Q.1912.5 [9] for profile C shall be applied. + +### 13.3.2 Calling Line Identification Restriction (CLIR) + +The procedures specified ITU-T Q.1912.5 [9] for profile C shall be applied. + +### 13.3.3 Connected Line Identification Presentation (COLP) + +No impact. + +### 13.3.4 Connected Line Identification Restriction (COLR) + +No impact. + +## 13.4 Call Forwarding Services + +### 13.4.0 Principles + +The procedures specified for Call Forwarding services in 3GPP TS 23.205 [7] sub-clause 13.4 shall be followed, with the following modifications: + +- The call establishment and call clearing procedures defined in clauses 6 and 7 shall be applied; +- The procedures for providing in-band information defined in sub-clause 14.6 shall be applied. +- Failure handling in GMSC and MSC Server shall be supported as specified for basic mobile originating and terminating calls. +- Optimized or Deferred MGW selection may apply for the incoming side bearer establishment and for the establishment of the bearer towards the forwarded-to subscriber, as specified in sub-clauses 4.4.2 and 4.4.3. +- MGW bypass may apply if there is no need for the (G)MSC server to manipulate the bearer or insert inband information and if the call forwarding condition is detected before the incoming side bearer is established. +- The modifications specified in the following sub-clauses shall be applied. + +The network model and message sequence specified in 3GPP TS 23.205 [7] sub-clause 13.4 also apply with the exception that the ISUP ACM/CPG messages are encapsulated within a SIP 183 Session Progress response. + +### 13.4.1 Call Forwarding Unconditional (CFU) + +See 3GPP TS 23.205 [7] sub-clause 13.4.1. + +### 13.4.2 Call Forwarding on mobile subscriber Busy (CFB) + +#### 13.4.2.1 Network Determined User Busy (NDUB) + +##### 13.4.2.1.1 Initial INVITE + +The MSC server shall indicate that preconditions have not been met if either of the following conditions is satisfied before sending the INVITE: + +- the incoming INVITE indicated that the remote preconditions had not been met and no new SDP indicating otherwise had since been received, or +- MGW selection is required for this call and the incoming side RTP connection point has not been yet successfully reserved and configured in the MGW. + +#### 13.4.2.1.2 Confirmation of bearer establishment + +If the outgoing INVITE indicated that preconditions are yet to be met, the new SDP indicating that the pre-conditions have now been satisfied will be sent when both following conditions are satisfied: + +1. Either: + +- a. The incoming INVITE indicated that the remote preconditions were yet to be satisfied, and new SDP indicating that these preconditions have been met has been received, or +- b. The incoming INVITE did not include any preconditions information or indicated that remote preconditions had been met + +and + +2. Either + +- a. The incoming side RTP connection point has been successfully reserved and configured in the MGW. +- b. MGW selection is not required for this call. + +#### 13.4.2.2 User Determined User Busy (UDUB) + +See 3GPP TS 23.205 [7] sub-clause 13.4.2.2. + +##### 13.4.2.2.1 Initial INVITE + +The MSC server shall indicate that preconditions have not been met if either of the following conditions is satisfied before sending the INVITE: + +- the incoming INVITE indicated that the remote preconditions had not been met and no new SDP message indicating otherwise had since been received, or +- MGW selection is required for this call and the incoming side RTP connection point has not been yet successfully reserved and configured in the MGW. + +NOTE: MGW selection may not be required for the call only if the UE is able to send the User Determined User Busy indication to the MSC Server before the subscriber is alerted. + +##### 13.4.2.2.2 Confirmation of bearer establishment + +If the outgoing INVITE indicated that preconditions are yet to be met, the new SDP indicating that the pre-conditions have now been satisfied will be sent when both following conditions are satisfied: + +1. Either: + +- a. The incoming INVITE indicated that the remote preconditions were yet to be satisfied, and new SDP indicating that these preconditions have been met has been received, or +- b. The incoming INVITE did not include any preconditions information or indicated that remote preconditions had been met + +and + +2. Either + +- a. The incoming side RTP connection point has been successfully reserved and configured in the MGW. +- b. MGW selection is not required for this call. + +### 13.4.3 Call Forwarding on No Reply (CFNRy) + +#### 13.4.3.1 Initial INVITE + +Following the possible generation of in-band information, the MSC server shall not include any preconditions in the INVITE message because the incoming side bearer has already been established. + +## 13.4.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc) + +### 13.4.4.1 Initial INVITE + +The MSC server shall indicate that preconditions have not been met if either of the following conditions is satisfied before sending the INVITE: + +- the incoming INVITE indicated that the remote preconditions had not been met and no new SDP message indicating otherwise had since been received, or +- MGW selection is required for this call and the incoming side RTP connection point has not been yet successfully reserved and configured in the MGW. + +### 13.4.4.2 Confirmation of bearer establishment + +If the outgoing INVITE indicated that preconditions are yet to be met, and new SDP indicating that the pre-conditions have now been satisfied will be sent when both following conditions are satisfied: + +1. Either: + +- a. The incoming INVITE indicated that the remote preconditions were yet to be satisfied, and new SDP indicating that these preconditions have been met has been received, or +- b. The incoming INVITE did not include any preconditions information or indicated that remote preconditions had been met + +and + +2. Either + +- a. The incoming side RTP connection point has been successfully reserved and configured in the MGW. +- b. MGW selection is not required for this call. + +## 13.5 Call Waiting (CW) + +The procedures specified for Call Waiting services in 3GPP TS 23.205 [7] sub-clause 13.5 shall be followed with the modifications: + +- The procedures of "Hold request" for the Call Hold service in clause 13.6 applies for Existing call on hold. +- The call establishment and call clearing procedures defined in clauses 6 and 7 shall be applied. + +## 13.6 Call Hold (CH) + +### 13.6.1 Principles + +The procedures specified for the Call Hold supplementary service in 3GPP TS 23.205 [7] sub-clause 13.6 shall be followed, with the following modifications: + +- The call establishment and call clearing procedures defined in clauses 6 and 7 shall be applied; +- If an announcement is to be applied to the held party the procedures defined in sub-clause 14.6 shall be applied. +- The Call Hold service shall be supported through ISUP encapsulation and generation of SDP offer as specified by ITU-T Q.1912.5 [9] for profile C. + +### 13.6.2 Hold Request + +The SDP offer and encapsulated ISUP CPG message shall be sent within: + +- UPDATE message if Hold request occurred before answer (200 OK final response with encapsulated ANM); +- re-INVITE message if Hold request occurred after answer (200 OK final response with encapsulated ANM or CON). + +The hold procedure shall be performed by changing the SDP attribute: + +- "a=sendonly", if the stream was previously a sendrecv media stream; +- "a=inactive", if the stream was previously a recvonly media stream. + +### 13.6.3 Retrieval Request + +The SDP offer and encapsulated ISUP CPG message shall be sent within: + +- UPDATE message if Retrieval request occurred before answer (200 OK final response with encapsulated ANM); +- re-INVITE message if Retrieval request occurred after answer (200 OK final response with encapsulated ANM or CON). + +The retrieval procedure shall be performed by changing the SDP attribute: + +- "a=sendrecv", if the stream was previously a sendonly media stream, or the attribute can be omitted, since sendrecv is the default; +- "a=recvonly", if the stream was previously an inactive media stream. + +## 13.7 Multiparty (MPTY) + +### 13.7.1 Introduction + +The procedures specified for the Multi Party supplementary service in 3GPP TS 23.205 [7] sub-clause 13.7 shall be followed, with the following modifications: + +- If the MGW only supports SIP-I associated Nb, the procedures for establishing the internal Nb bearer between the peripheral context and the Multiparty bridge context shall be in accordance with the standard SIP-I based Nc external bearer setup procedures. The Establish Bearer, Prepare Bearer, Tunnel Information Up and Tunnel Information Down procedures shall be replaced by the Reserve RTP Connection Point, Reserve and Configure RTP Connection Point, Configure RTP connection point. +- If the MGW supports combinations of SIP-I and BICC associated Nb, the MSC-S may establish the internal Nb bearer between the peripheral context and the Multiparty bridge following the standard SIP-I based Nc or BICC based Nc external bearer setup procedures. +- The MSC-S knows whether the MGW supports SIP-I and/or BICC associated Nb through local configuration data. +- The hold and retrieval of users shall be encoded as described in Clause 13.6, with further clarifications in Clause 13.7.2. + +NOTE1: If the MGW only supports BICC associated Nb, the procedures for establishing the internal Nb bearer between the peripheral context and the Multiparty bridge context are defined in 3GPP TS 23.205 [7]. + +NOTE2: Sub-clause 13.7.5 of 3GPP TS 23.205 [7] gives an example where the procedures for establishing the internal Nb bearer between the peripheral context and the Multiparty bridge context are in accordance with the standard external bearer setup procedures specified in BICC based Nc. + +### 13.7.2 Beginning the Multi Party call + +See 3GPP TS 23.205 [7] sub-clause 13.7.1. + +The CPG to inform an active user of the conference establishment shall be encoded in a SIP INFO. + +For a user on hold, the following applies: + +- A CPG to inform the user on hold of the conference establishment shall be sent. +- A CPG to retrieve the user on hold may be sent. The retrieval of the user on hold may also be combined with the conference call establishment in a single CPG. + +- a re-INVITE to activate the held media shall be sent. +- If only a CPG to inform the user on hold of the conference establishment is sent, the re-INVITE shall encapsulate this CPG. +- If only a single CPG to inform the user on hold of the conference establishment and to retrieve the user on hold is sent, the re-INVITE shall encapsulate this CPG. +- If separate CPGs to inform the user on hold of the conference establishment and to retrieve the user on hold are sent, the re-INVITE shall encapsulate the CPG to retrieve the user on hold. The CPG to inform the user on hold of the conference establishment shall be encapsulated in a SIP INFO. + +### 13.7.3 Managing an active Multi Party call + +See 3GPP TS 23.205 [7] sub-clause 13.7.2. + +### 13.7.4 Disconnect + +See 3GPP TS 23.205 [7] sub-clause 13.7.3. + +### 13.7.5 Failure handling in MSC server + +See 3GPP TS 23.205 [7] sub-clause 13.7.4. + +### 13.7.6 Example 1 + +In this example, the procedures for establishing the internal Nb bearer between the peripheral context and the Multiparty bridge context are in accordance with the standard external bearer setup procedures specified for SIP-I based Nc. + +Figure 13.7.6.1 shows the network model for multi party call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. Note that for a TDM access there is no separation between the call and bearer control signalling. In the following example it is assumed that each party participating in the Multi Party conference is handled in a separate context representing the call leg between the Multi Party bridge and the Multi Party participant. The Multi Party bridge itself is handled in a separate context. This separation to several contexts is done in order to simplify interactions with other functionality, such as handover, even though other implementation options are not excluded. + +![Figure 13.7.6.1: Multi Party call (Network model). The diagram shows a network architecture for a multi-party call. At the top is an MSC-S (Mobile Switching Center - Server). Below it is a large box containing several components: an RNC/BSC (Radio Network Controller/Base Station Controller) on the left, a central CTX_MPTY (Multiparty Context) box, and two other context boxes labeled CTX_A and CTX_AB. Below the central box is an MGW (Media Gateway) with a CTX_AC context. Solid blue lines represent call control signalling, connecting the MSC-S to the central CTX_MPTY box, and from the central box to the CTX_A and CTX_AB boxes. Dotted green lines represent bearer control signalling and the bearer path, originating from the MSC-S and extending to the right, labeled 'B-party' and 'C party'.](914919be6b64b1c8bb74e12616c85f71_img.jpg) + +Figure 13.7.6.1: Multi Party call (Network model). The diagram shows a network architecture for a multi-party call. At the top is an MSC-S (Mobile Switching Center - Server). Below it is a large box containing several components: an RNC/BSC (Radio Network Controller/Base Station Controller) on the left, a central CTX\_MPTY (Multiparty Context) box, and two other context boxes labeled CTX\_A and CTX\_AB. Below the central box is an MGW (Media Gateway) with a CTX\_AC context. Solid blue lines represent call control signalling, connecting the MSC-S to the central CTX\_MPTY box, and from the central box to the CTX\_A and CTX\_AB boxes. Dotted green lines represent bearer control signalling and the bearer path, originating from the MSC-S and extending to the right, labeled 'B-party' and 'C party'. + +**Figure 13.7.6.1: Multi Party call (Network model)** + +For the purposes of the information flow diagrams it is assumed that there are only two remote parties. Party A is the subscriber controlling the Multi Party service (served mobile subscriber). Party B is the held party and party C is the active party. + +It is assumed that the Multi Party bridge is located in the MGW that has been selected for the served mobile subscriber. + +Figure 13.7.6.2 shows the message sequence example for the beginning of multi party call. When the served mobile subscriber invokes a Multi Party service the MSC server requests the MGW to create a separate context for the Multi Party bridge. The MSC server seizes a bearer termination for each party in that context. In addition, each call leg is represented by a separate context. Therefore the parties in the active call will be split in separate contexts. The MSC server requests the MGW to create a new context and to move the bearer termination for the served mobile subscriber from the active call context to the new context. To connect the parties to the Multi Party bridge the MSC server requests the MGW to establish internal Nb connections with the PCM codec between the bearer terminations in the Multi Party bridge context and the call leg contexts, using the standard external bearer setup procedures of SIP-I based Nc. The held party is informed about the retrieval of the held call, and the both remote parties are informed about the multi party call establishment. + +![Sequence diagram showing information flow for a multi-party call, internal IP bearer. Lifelines: UE, RNC/BSC, MSC-S, and MGW. The process involves context exchange, MOV, ADD, and MOD requests/replies, and final INFO messages for call establishment.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + UE->>MSC-S: Multi Party req + Note over MSC-S: Context ($) + MSC-S->>MGW: MOV.request (TA) + MGW-->>MSC-S: MOV.reply (TA) + Note over MSC-S: Context (CA) + Note over MSC-S: Context ($) + MSC-S->>MGW: ADD.request ($) + Note right of MGW: Reserve RTP Connection Point + MSC-S->>MGW: ADD.request ($) + Note right of MGW: Reserve RTP Connection Point + MSC-S->>MGW: ADD.request ($) + Note right of MGW: Reserve RTP Connection Point + Note over MSC-S: Context (CMPTY) + MGW-->>MSC-S: ADD.reply (TA0) + MGW-->>MSC-S: ADD.reply (TB0) + MGW-->>MSC-S: ADD.reply (TC0) + Note over MSC-S: Context (CA) + MSC-S->>MGW: ADD.request ($) + Note over MSC-S: Context (CA) + MGW-->>MSC-S: ADD.reply (TA1) + Note right of MGW: Reserve and Configure RTP Connection Point + Note over MSC-S: Context (CAB) + MSC-S->>MGW: ADD.request ($) + Note over MSC-S: Context (CAB) + MGW-->>MSC-S: ADD.reply (TB1) + Note right of MGW: Reserve and Configure RTP Connection Point + Note over MSC-S: Context (CAC) + MSC-S->>MGW: ADD.request ($) + Note over MSC-S: Context (CAC) + MGW-->>MSC-S: ADD.reply (TC1) + Note right of MGW: Reserve and Configure RTP Connection Point + Note over MSC-S: Context (CMPTY) + MSC-S->>MGW: MOD.request (TA0) + MSC-S->>MGW: MOD.request (TB0) + MSC-S->>MGW: MOD.request (TC0) + Note right of MGW: Configure RTP Connection Point + Note right of MGW: Configure RTP Connection Point + Note right of MGW: Configure RTP Connection Point + Note over MSC-S: Context (CMPTY) + MGW-->>MSC-S: MOD.reply (TA0) + MGW-->>MSC-S: MOD.reply (TB0) + MGW-->>MSC-S: MOD.reply (TC0) + MSC-S->>MSC-S: Re-INVITE (a=sendrecv, CPG ConfCallEstablished + retrieval) (to B) (Note) + MSC-S->>MSC-S: INFO (CPG(ConfCallEstablished) (to B) (Note) + MSC-S->>MSC-S: INFO (CPG(ConfCallEstablished) (to C) + MSC-S->>UE: Multi Party acknowledge + +``` + +Sequence diagram showing information flow for a multi-party call, internal IP bearer. Lifelines: UE, RNC/BSC, MSC-S, and MGW. The process involves context exchange, MOV, ADD, and MOD requests/replies, and final INFO messages for call establishment. + +Note: See Clause 13.7.2. + +**Figure 13.7.6.2: Information flow for multi party call, internal IP bearer (message sequence chart)** + +## 13.8 Closed User Group (CUG) + +No impact. + +## 13.9 Advice of Charge (AoC) + +No impact. + +## 13.10 User-to-User Signalling (UUS) + +User to User signalling is supported through ISUP encapsulation, as specified by ITU-T Q.1912.5 [9]. + +## 13.11 Call Barring Services + +### 13.11.1 Barring of outgoing calls + +No impact. + +### 13.11.2 Barring of incoming calls other than Anonymous Call Rejection + +No impact. + +### 13.11.3 Anonymous Call Rejection (ACR) + +The call shall be handled as for other call barring procedures, with the additions as specified for the Anonymous Call Rejection service in 3GPP TS 23.205 [7] sub-clause 13.11.3 shall be followed, and with the following modifications: + +- the procedures for providing in-band information defined in sub-clause 14.6 shall be applied; +- the GMSC Server shall send a 183 message with encapsulated ACM or CPG including cause no. 24 before applying the announcement; +- after the announcement has been completed, the GMSC server shall initiate the call clearing according to clause 7. + +## 13.12 Explicit Call Transfer (ECT) + +The procedures specified in Clause 13.12 of 3GPP TS 23.205[7] shall be applied. The example service flow is as shown in the following sub-clause. + +### 13.12.1 Example + +Party A is the subscriber controlling the Explicit Call Transfer Call (served mobile subscriber). Party B is the first remote called party (held party). Party C is the second remote called party. MSC-A, MSC-B and MSC-C is the MSC server served for Party A, Party B and Party C respectively. + +After a call between Party A with Party B has been established successfully and Party B is held, a new call between party A with Party C is established successfully. After getting the ECT request, MSC-A initiates the ECT service procedure by changing through the connection between Party B with Party C. + +After receiving an ECT request from Party A UE, MSC-A shall retrieve Party B from hold by using a re-INVITE request and through-connection the bearer terminations between Party B and Party C. Additionally, MSC-A sends ECT notifications to MSC-B and MSC-C using INFO requests. Figure 13.12.1 is an example service flow diagram for the ECT service. + +![Sequence diagram of ECT service flow between MSC-B, GMSC/AB, MSC-A, GMSC/BC, and MSC-C.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant MSC-B + participant GMSC/AB + participant MSC-A + participant GMSC/BC + participant MSC-C + + Note left of MSC-B: A call between Party A and Party B has been established + MSC-B->>MSC-A: Party B is held + Note right of MSC-A: A call between Party A and Party C is established + MSC-A->>GMSC/AB: ECT request from Party A UE + GMSC/AB->>MSC-B: re-INVITE [CPG, SDP] + MSC-B->>GMSC/AB: 200 OK [SDP] + GMSC/AB->>MSC-A: 200 OK [SDP] + MSC-A->>GMSC/BC: INFO [FAC] + GMSC/BC->>MSC-C: INFO [FAC] + MSC-A->>GMSC/BC: 200 OK + GMSC/BC->>MSC-C: 200 OK + MSC-B->>GMSC/AB: ACK + GMSC/AB->>MSC-A: ACK + MSC-A->>GMSC/AB: INFO [FAC] + GMSC/AB->>MSC-B: INFO [FAC] + MSC-B->>GMSC/AB: 200 OK + GMSC/AB->>MSC-A: 200 OK + Note right of MSC-A: MSC-A orders the MGW to through-connect the bearer terminations to Party B and to Party C + GMSC/AB->>MSC-A: ECT Acknowledge to Party A UE + Note right of MSC-A: Call and bearer release to Party A + +``` + +Sequence diagram of ECT service flow between MSC-B, GMSC/AB, MSC-A, GMSC/BC, and MSC-C. + +Figure 13.12.1: ECT service flow + +## 13.13 Completion of Calls to Busy Subscriber (CCBS) + +The procedures specified for the Completion of Calls to Busy Subscriber service in 3GPP TS 23.205 [7] sub-clause 13.13 shall be followed, with the following modifications: + +- The call establishment and call clearing procedures defined in clauses 6 and 7 shall be applied; +- The procedures for providing in-band information defined in sub-clause 14.6 shall be applied. + +## 13.14 Multiple Subscriber Profile (MSP) + +No impact. + +## 13.15 Multicall + +See 3GPP TS 23.205 [7] sub-clause 13.15. + +## 13.16 Calling Name Presentation (CNAP) + +No impact. + +## 13.17 Alternate Speech/Fax + +See 3GPP TS 23.205 [7] sub-clause 13.17. + +## 13.18 Modification of the Access Bearer + +### 13.18.1 Modification of Bearer Characteristics + +See 3GPP TS 23.205 [7] sub-clause 13.18.1. + +## 13.18.2 IWF Protocol Change + +See 3GPP TS 23.205 [7] sub-clause 13.18.2. + +## 13.19 GSM Fax + +See 3GPP TS 23.205 [7] sub-clause 13.19. + +## 13.20 Voice group call service (VGCS), Voice broadcast service (VBS) + +The procedures specified for the VGCS/VBS supplementary service in 3GPP TS 23.205 [7] sub-clause 13.20 shall be followed, with the following modifications: + +- If the MGW only supports SIP-I associated Nb, the procedures for establishing the internal Nb bearer between the peripheral context and the VGCS Multiparty Bridge context shall be in accordance with the standard SIP-I based Nc external bearer setup procedures. The Establish Bearer and Prepare Bearer procedures shall be replaced by the Reserve RTP Connection Point, Reserve and Configure RTP Connection Point, Configure RTP connection point. +- If the MGW supports combinations of SIP-I and BICC associated Nb, the MSC-S may establish the internal Nb bearer between the peripheral context and the VGCS Multiparty Bridge context following the standard SIP-I based Nc or BICC based Nc external bearer setup procedures. +- The MSC-S knows whether the MGW supports SIP-I and/or BICC associated Nb through local configuration data. + +NOTE: If the MGW only supports BICC associated Nb, the procedures for establishing the internal Nb bearer between the peripheral context and the VGCS Multiparty Bridge context are defined in 3GPP TS 23.205 [7]. + +--- + +## 14 Interactions with Other Network Features and Services + +### 14.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) + +The procedures specified for Customised Applications for Mobile network Enhanced Logic (CAMEL) in 3GPP TS 23.205 [7] sub-clause 14.1 shall be followed, with the clarifications given in the following sub-clauses. The examples specified in 3GPP TS 23.205 [7] sub-clauses 14.6 also apply. + +#### 14.1.1 Play Announcement/Send Tone + +The procedures specified for the Play Announcement/Send Tone in 3GPP TS 23.205 [7] sub-clause 14.1.1 shall be followed, with the following modifications: + +- the procedures for providing tones or announcements and the procedures for stopping providing tones or announcements defined in sub-clause 14.6 shall be applied. + +#### 14.1.2 User Interaction + +The procedures specified for the User Interaction in 3GPP TS 23.205 [7] sub-clause 14.1.2 shall be followed, with the following modifications: + +- the procedures for providing tones or announcements and the procedures for stopping providing tones or announcements defined in sub-clause 14.6 shall be applied. +- the procedures for detecting and reporting DTMF tones defined in sub-clause 14.4 shall be applied. + +### 14.1.3 Call Party Handling (CPH) + +See 3GPP TS 23.205 [7] sub-clause 14.1.3. + +## 14.2 IST + +See 3GPP TS 23.205 [7] sub-clause 14.2 with the following modification: + +- the (G)MSC server initiated call clearing procedures defined in clause 7 shall be applied. + +## 14.3 Operator Determined Barring (ODB) + +The procedures specified for the Operator Determined Barring service in 3GPP TS 23.205 [7] sub-clause 14.3 shall be followed, with the following modifications: + +- the call establishment and call clearing procedures defined in clauses 6 and 7 shall be applied; +- the procedures for providing in-band information defined in sub-clause 14.6 shall be applied. +- Optimized or deferred MGW selection may apply for the establishment of the incoming side bearer, as specified in sub-clauses 4.4.2 and 4.4.3. + +## 14.4 DTMF + +### 14.4.1 General + +This clause only specifies the requirements to be supported for DTMF signalling on SIP-I based Nc. Interworking of DTMF between BICC and SIP-I on Nc and interworking between DTMF in external networks and SIP-I is specified in 3GPP TS 29.235 [21]. + +DTMF signalling via the RTP telephony-event according to IETF RFC 4733 [24] on Nb Interface shall be supported in SIP-I based Circuit Switched Core Network [y]. + +Inband DTMF signalling (generation, detection) shall also be supported in SIP-I based Nc to ensure open interoperability between two MSC servers from different vendors, when terminating MSC server selects PCM and does not offer RTP telephony-event in the answer. + +When the negotiation for telephone events via the SDP offer-answer mechanism is complete and the needed preconditions defined in IETF RFC 3312 [26] are fulfilled, if RTP telephony-event has been successfully negotiated then telephone events can be sent in RTP payload. If a speech codec other than the default PCM codec has been selected (via the 3GPP SIP-I codec negotiation procedures, see 3GPP TS 23.153 [3]), DTMF shall be sent as an RTP Telephony Event. If the default PCM speech codec is selected, DTMF transport in the RTP telephony-event is optional. However, if the RTP telephony-event is included in the SDP answer, it shall be used to transport DTMF (rather than inband transport in the default PCM speech codec). + +Interworking Procedures to external networks at the G-MSC server are specified in 3GPP TS 29.235 [21]. + +### 14.4.2 DTMF handling in SIP-I Offer/Answer + +(G)MSC Servers and MGWs shall support the reception and transmission of the RTP MIME type "telephone event" as defined in IETF RFC 4733 [24] and as per the following requirements: + +- An MSC Server initiating an SDP offer shall include the MIME type "telephone events" with default events in the first SDP offer, if it offers any codecs other than the default PCM codec. An MSC Server initiating an SDP offer with only the default PCM codec as speech codec may include the MIME type "telephone events" in the first SDP offer, +- An MSC Server terminating an SDP offer shall accept the MIME type "telephone events" with default events in any SDP answer, if it selects any codec other than the default PCM codec. An MSC Server terminating an SDP offer that selects the default PCM codec as speech codec may include the MIME type "telephone events" in the SDP answer, if present in the SDP offer, + +- A 3GPP SIP-I intermediate node receiving an SDP offer with the MIME type "telephone events" shall forward the MIME type "telephone-events" in the offer to the succeeding node. + +### 14.4.3 Server to MGW Procedures + +The (G)MSC Server indicates the transport mode of DTMF to the MGW as follows in the "Configure RTP Connection Point" procedure or "Reserve and Configure RTP Connection Point" procedure: + +- The (G)MSC Server shall configure the RTP telephony event payload at the MGW if successfully negotiated in the SDP Offer/Answer. +- If the (G)MSC Server configures the RTP telephony event payload at the MGW for a given termination and applies the Detect DTMF procedure to request the detection of DTMF, the MGW shall detect DTMF within the RTP telephony event payload according to IETF RFC 4733 [24] and shall not detect inband DTMF within a speech codec. +- If the (G)MSC Server does not configure the RTP telephony event payload at the MGW for a given termination and applies the "Detect DTMF" procedure to request the detection of DTMF, the MGW shall detect inband DTMF within the speech codec; the (G)MSC Server shall not request "Detect DTMF" without RTP Telephony Event in combination with any codec other than the default PCM codec. +- If the (G)MSC Server configures the RTP telephony event payload at the MGW for a given termination and applies the Send DTMF procedure to request the sending of DTMF, the MGW shall send DTMF within the RTP telephony event payload according to IETF RFC 4733 [24]. +- If the (G)MSC Server does not configure the RTP telephony event payload at the MGW for a given termination and applies the "Send DTMF" procedure to request the sending of DTMF, the MGW shall send inband DTMF within the speech codec; the (G)MSC Server shall not request "Send DTMF" without RTP Telephony Event in combination with any codec other than the default PCM codec. +- If the (G)MSC Server requests reporting of DTMF via "Detect DTMF" Procedure then when the MGW has reported a DTMF Digit Event the MGW shall not forward the DTMF to the succeeding interface as this could result in double detection of the same digit. +- If the (G)MSC Server has requested support of RTP Telephony Event via the "Configure RTP Connection Point" procedure or "Reserve and Configure RTP Connection Point" procedure but has not requested reporting of DTMF digits via the "Detect DTMF" procedure the MGW shall forward received RTP Telephony Events to succeeding/preceding interface for a connection that is configured to support RTP Telephony Event. +- If the (G)MSC Server does not wish to receive DTMF (has not configured "DTMF Detect") but has requested support of RTP Telephony Event via the "Configure RTP Connection Point" procedure or "Reserve and Configure RTP Connection Point" procedure at one bearer termination but not at the other bearer termination, if the other termination is default PCM MGW shall then relay DTMF (see clauses 14.4.8 and 14.4.9). + +### 14.4.4 RTP Telephony Event DTMF Digit Generation + +#### 14.4.4.1 General + +The RTP Telephony Event DTMF digit generation shall be performed in accordance with IETF RFC 4733 [24]. The following clauses describe the additional requirements for the bearer independent CS core network. + +#### 14.4.4.2 Start DTMF + +When the MSC server receives the Start DTMF message from the UE, it shall use the Send DTMF procedure to request the MGW to modify the bearer termination to transmit the requested digit. + +#### 14.4.4.3 Stop DTMF + +When the MSC server receives the Stop DTMF message from the UE, it shall use the Stop DTMF procedure to request the MGW to modify the bearer termination to stop digit transmission. + +Upon reception of the Stop DTMF procedure, the MGW shall ensure the minimum digit duration is kept, in accordance with 3GPP TS 23.014 [27] and then terminate the digit transmission by sending RTP Telephony Event with "End-bit" set to YES. + +If implicit DTMF timing is deployed (as shown in example figure 14.4.4.3.1) and the MGW has already completed the digit transmission it shall not take any action upon the reception of the Stop DTMF procedure. + +#### 14.4.4.4 Example + +When the UE sends Start DTMF and Stop DTMF messages, the MSC server uses resources in the MGW to transmit a digit by modifying the bearer termination. + +![Sequence diagram illustrating DTMF Digit generation with implicit timing over RTP Telephony Event. The diagram shows three participants: Ue, MSC-S, and MGW. The process involves two main steps: 1. Start DTMF: Ue sends 'Start DTMF(Digit)' to MSC-S. MSC-S sends 'MOD. Request [RTP Tel Event, signal = Digit] (Tx)' to MGW, which then sends the 'RTP Telephony Event [Digit=digit, Ebit=0]'. MSC-S receives 'MOD. Reply (Tx)' from MGW and sends 'Start DTMF Ack' to Ue. 2. Stop DTMF: Ue sends 'Stop DTMF(Digit)' to MSC-S. MSC-S sends 'MOD. Request [RTP Tel Event, stop signal] (Tx)' to MGW, which then sends a 'Stop DTMF Procedure'. MSC-S receives 'MOD. Reply (Tx)' from MGW and sends 'Stop DTMF Ack' to Ue. Context (Cx) is maintained throughout the interaction.](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +``` + +sequenceDiagram + participant Ue + participant MSC-S + participant MGW + + Note right of MSC-S: 1 + Ue->>MSC-S: Start DTMF(Digit) + MSC-S->>MGW: MOD. Request [RTP Tel Event, signal = Digit] (Tx) + MGW->>External: RTP Telephony Event [Digit=digit, Ebit=0] + MGW-->>MSC-S: MOD. Reply (Tx) + MSC-S-->>Ue: Start DTMF Ack + Note right of MSC-S: 2 + Ue->>MSC-S: Stop DTMF(Digit) + MSC-S->>MGW: MOD. Request [RTP Tel Event, stop signal] (Tx) + MGW->>External: Stop DTMF Procedure + MGW-->>MSC-S: MOD. Reply (Tx) + MSC-S-->>Ue: Stop DTMF Ack + +``` + +Sequence diagram illustrating DTMF Digit generation with implicit timing over RTP Telephony Event. The diagram shows three participants: Ue, MSC-S, and MGW. The process involves two main steps: 1. Start DTMF: Ue sends 'Start DTMF(Digit)' to MSC-S. MSC-S sends 'MOD. Request [RTP Tel Event, signal = Digit] (Tx)' to MGW, which then sends the 'RTP Telephony Event [Digit=digit, Ebit=0]'. MSC-S receives 'MOD. Reply (Tx)' from MGW and sends 'Start DTMF Ack' to Ue. 2. Stop DTMF: Ue sends 'Stop DTMF(Digit)' to MSC-S. MSC-S sends 'MOD. Request [RTP Tel Event, stop signal] (Tx)' to MGW, which then sends a 'Stop DTMF Procedure'. MSC-S receives 'MOD. Reply (Tx)' from MGW and sends 'Stop DTMF Ack' to Ue. Context (Cx) is maintained throughout the interaction. + +**Figure 14.4.4.4.1: DTMF Digit generation - implicit timing over RTP Telephony Event (message sequence chart)** + +### 14.4.5 DTMF Tone Generation + +DTMF Tone Generation shall only occur if the RTP Telephony Event has not been negotiated and the default PCM codec is selected for the user plane. The MSC Server shall apply the "Send DTMF" procedure to the core network side termination (PCM) in accordance with 3GPP TS 23.205 [7] Clause 14.4.1.1 + +### 14.4.6 RTP Telephony Event DTMF Digit Detection + +#### 14.4.6.1 General + +The RTP Telephony Event DTMF digit detection shall be performed in accordance with IETF RFC 4733 [24]. The following clauses describe the additional requirements for the bearer independent CS core network. + +#### 14.4.6.2 Detect DTMF Digit + +An MSC server uses the Detect DTMF procedure to request a MGW to report DTMF Digits. If a MGW receives the Detect DTMF procedure, it shall configure the bearer termination to receive DTMF digits. The result of the digit detection shall be reported within Notify DTMF Digit procedure. + +The Detect DTMF procedure permits the MSC Server to request reporting either of Start and End of DTMF detection, or only of End of DTMF Detection. The support of "start of DTMF detection" is optional for the MGW; if not supported the MGW shall indicate the appropriate error code. + +If the MSC Server does not request DTMF notification then the MGW shall relay the DTMF to the succeeding interface. + +### 14.4.6.3 Example – DTMF Notification + +![Sequence diagram for DTMF Notification with both start and end events. It shows three steps: 1. MSC-S sends a MOD. Request for StartTone to MGW, which detects the start of the DTMF digit via RTP Tel Event. 2. MGW sends an RTP Telephony Event with E-bit=0 to MSC-S, which then sends a Notify.Request for the start tone to the other MGW. 3. MGW sends an RTP Telephony Event with E-bit=1 to MSC-S, which then sends a Notify.Request for the end tone to the other MGW.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +``` + +sequenceDiagram + participant MGW1 as MGW + participant MSC-S + participant MGW2 as MGW + Note right of MGW2: Detect DTMF Digit via RTP Tel Event, (start DTMF and StopDTMF) + MSC-S->>MGW2: MOD. Request [RTP Tel Event, Event = StartTone, EndTone] (Tx) + Note left of MGW2: Context (Cx) + MGW2-->>MSC-S: MOD. Reply (Tx) + Note left of MGW2: Context (Cx) + MGW1->>MSC-S: RTP Telephony Event [(Digit), E-bit = 0, Duration = x] + Note left of MGW2: Context (Cx) + MSC-S->>MGW2: Notify.Request [Report DTMF, start tone, Digit] (Tx) + Note left of MGW2: Context (Cx) + MGW2-->>MSC-S: Notify. Reply (Tx) + MGW1->>MSC-S: RTP Telephony Event [(Digit), E-bit = 1, Duration = y] + Note left of MGW2: Context (Cx) + MSC-S->>MGW2: Notify.Request [Report DTMF, end tone, Digit] (Tx) + Note left of MGW2: Context (Cx) + MGW2-->>MSC-S: Notify. Reply (Tx) + Note right of MGW2: Report start of DTMF Digit + Note right of MGW2: Report end of DTMF Digit + +``` + +Sequence diagram for DTMF Notification with both start and end events. It shows three steps: 1. MSC-S sends a MOD. Request for StartTone to MGW, which detects the start of the DTMF digit via RTP Tel Event. 2. MGW sends an RTP Telephony Event with E-bit=0 to MSC-S, which then sends a Notify.Request for the start tone to the other MGW. 3. MGW sends an RTP Telephony Event with E-bit=1 to MSC-S, which then sends a Notify.Request for the end tone to the other MGW. + +Figure 14.4.6.3.1: DTMF Notification with both start and end events + +![Sequence diagram for DTMF Notification with only end DTMF event. It shows two steps: 1. MSC-S sends a MOD. Request for EndTone to MGW, which detects the DTMF digit via RTP Tel Event. 2. MGW sends RTP Telephony Events with E-bit=0 and E-bit=1 to MSC-S. Upon receiving E-bit=1, MSC-S sends a Notify.Request for the end tone to the other MGW.](a4bfa2343d75076b79f7e33d93915e00_img.jpg) + +``` + +sequenceDiagram + participant MGW1 as MGW + participant MSC-S + participant MGW2 as MGW + Note right of MGW2: Detect DTMF Digit via RTP Tel Event, (End DTMF only) + MSC-S->>MGW2: MOD. Request [RTP Tel Event, Event = EndTone] (Tx) + Note left of MGW2: Context (Cx) + MGW2-->>MSC-S: MOD. Reply (Tx) + Note left of MGW2: Context (Cx) + MGW1->>MSC-S: RTP Telephony Event [(Digit), E-bit = 0, Duration = x] + Note right of MGW2: start of DTMF Digit received, waits for E-bit=1 + MGW1->>MSC-S: RTP Telephony Event [(Digit), E-bit = 1, Duration = y] + Note left of MGW2: Context (Cx) + MSC-S->>MGW2: Notify.Request [Report DTMF, end tone, Digit] (Tx) + Note left of MGW2: Context (Cx) + MGW2-->>MSC-S: Notify. Reply (Tx) + Note right of MGW2: Report end of DTMF Digit + +``` + +Sequence diagram for DTMF Notification with only end DTMF event. It shows two steps: 1. MSC-S sends a MOD. Request for EndTone to MGW, which detects the DTMF digit via RTP Tel Event. 2. MGW sends RTP Telephony Events with E-bit=0 and E-bit=1 to MSC-S. Upon receiving E-bit=1, MSC-S sends a Notify.Request for the end tone to the other MGW. + +Figure 14.4.6.3.2: DTMF Notification with only end DTMF event + +### 14.4.7 Inband DTMF Tone Detection + +DTMF tone detection within the PCM speech codec as specified by Clause 14.4.2.1 of 3GPP TS 23.205 [7] shall only be required by applications making use of the DTMF information within the (G)MSC server, and only if the RTP telephony event is not negotiated with SDP offer/answer. + +A server controlling a MGW requests detection of inband DTMF by applying the Detect DTMF procedure but not configuring the RTP Telephony Event payload at the corresponding termination. + +### 14.4.8 Interworking between RTP Telephony Events and Inband DTMF Tones + +A (G)MSC Server or Interworking Node may need to interwork a SIP-I associated bearer where the usage of RTP Telephony Event has been negotiated with a bearer where PCM encoded speech but no RTP Telephony Event has been negotiated. The MGW shall relay the DTMF between the terminations of a context if the following conditions apply: + +- the (G)MSC Server or Interworking Node configures a MGW with SIP-I associated bearer termination to support RTP Telephony Event from/to the preceding node and; +- the (G)MSC Server has not requested DTMF detection to be reported and; +- the selected codec to the succeeding node is default PCM and; +- the succeeding SIP-I node has not selected RTP Telephony Event. + +RTP Telephony events received on SIP-I associated bearer are inserted into the PCM stream (bullet 2 in Figure 14.4.8.1). Inband DTMF received from the preceding node shall be inserted as RTP Telephony events on succeeding bearer termination (bullet 3 in Figure 14.4.8.1). + +When detecting inband DTMF the MGW shall ensure the minimum duration for valid DTMF validation is detected in accordance with 3GPP TS 23.014 [27] before signalling an RTP telephony Event. + +![Sequence diagram illustrating DTMF Relay between RTP Telephony Event and inband DTMF. The diagram shows five nodes: MGW, MSC-S, MGW, MSC-S, and MGW. The first MGW sends an RTP Telephony Event [(Digit), Duration = x] to the first MSC-S. The first MSC-S sends a MOD. Request [RTP Tel Event payload Type] (Tx) to the second MGW. The second MGW responds with a MOD. Reply (Tx) to the first MSC-S. The second MGW then inserts the DTMF tone into the payload (bullet 2) and detects it (bullet 3). Finally, the second MGW sends an RTP Telephony Event [(Digit), Duration = y] to the first MGW. A label 'SIP-I node that does not support RTP Telephony Event' is present above the second MGW.](cc542843836eecb036b99cb270b54a1e_img.jpg) + +``` + +sequenceDiagram + participant MGW1 as MGW + participant MSCS1 as MSC-S + participant MGW2 as MGW + participant MSCS2 as MSC-S + participant MGW3 as MGW + + Note right of MGW2: SIP-I node that does not support RTP Telephony Event + + MGW1->>MSCS1: Context (Cx) + MSCS1->>MGW2: MOD. Request [RTP Tel Event payload Type] (Tx) + MGW2-->>MSCS1: MOD. Reply (Tx) + MSCS1->>MGW1: Context (Cx) + MGW1->>MGW2: RTP Telephony Event [(Digit), Duration = x] + Note right of MGW2: 2 Insert DTMF Tone into payload + Note right of MGW2: 3 Detect DTMF Tone in payload + MGW2->>MGW1: RTP Telephony Event [(Digit), Duration = y] + +``` + +Sequence diagram illustrating DTMF Relay between RTP Telephony Event and inband DTMF. The diagram shows five nodes: MGW, MSC-S, MGW, MSC-S, and MGW. The first MGW sends an RTP Telephony Event [(Digit), Duration = x] to the first MSC-S. The first MSC-S sends a MOD. Request [RTP Tel Event payload Type] (Tx) to the second MGW. The second MGW responds with a MOD. Reply (Tx) to the first MSC-S. The second MGW then inserts the DTMF tone into the payload (bullet 2) and detects it (bullet 3). Finally, the second MGW sends an RTP Telephony Event [(Digit), Duration = y] to the first MGW. A label 'SIP-I node that does not support RTP Telephony Event' is present above the second MGW. + +**Figure 14.4.8.1: DTMF Relay between RTP Telephony Event and inband DTMF** + +## 14.5 OR + +The procedures specified for Optimal Routing network service in 3GPP TS 23.205 [7] sub-clause 14.5 shall be followed with the following modification: + +- the procedures for call clearing defined in sub-clause 7 shall be applied. + +## 14.6 Providing tones or announcements + +### 14.6.1 Introduction + +The procedures specified for providing tones or announcements in 3GPP TS 23.205 [7] sub-clause 14.6 shall be followed, with the clarifications given in the following sub-clauses. The examples specified in 3GPP TS 23.205 [7] sub-clauses 14.6 also apply. + +### 14.6.2 Preconditions when providing in-band information to the calling subscriber + +For a mobile terminating/forwarded call, announcements/tones may be provided to the calling subscriber only when the following conditions are satisfied: + +1. Either: + - a. The incoming INVITE(IAM) indicated that remote preconditions had not been met, and new SDP has been received indicating that preconditions have been met, or + - b. The incoming INVITE(IAM) did not include any preconditions information or indicated that remote preconditions had been met; + +and + +2. The incoming side RTP connection point has been successfully reserved and configured in the MGW. + +For a mobile originating call, the traffic channel assignment shall be completed before providing the in-band information to the calling subscriber. + +### 14.6.3 Preconditions when providing in-band information to the called subscriber + +The called party is selected by the calling party, or a supplementary service (call forwarding, call deflection, CAMEL redirection etc), or a call is initiated by the gsmSCF using the Initiate Call Attempt procedure. The called party may also be in the PSTN. + +Announcements/tones may be provided to the called subscriber only when the following conditions are satisfied: + +1. The called party has answered and is still active in the call, and +2. The outgoing side RTP Connection point has been successfully reserved and configured in the MGW. + +### 14.6.4 Preconditions when providing in-band information to multiple subscribers + +See 3GPP TS 23.205 [7] sub-clause 14.6.3. + +### 14.6.5 Request to play an announcement/tone + +See 3GPP TS 23.205 [7] sub-clause 14.6.4. + +### 14.6.6 Stopping an announcement/tone + +See 3GPP TS 23.205 [7] sub-clause 14.6.5. + +### 14.6.7 Announcement/tone completed + +See 3GPP TS 23.205 [7] sub-clause 14.6.6. + +## 14.7 Global Text Telephony + +Global Text Telephony shall be supported as described in 3GPP TS 23.205 [7] Clause 14.7 where the CTM package properties are included in the "Reserve RTP Connection Point" and "Configure RTP Connection Point" for Access side terminations and default PCM codec selected for the Core Network side terminations. + +## 14.8 Emergency Calls + +Emergency Calls shall be handled as in clause 6.1 Basic Mobile Originating Call and clause 6.2 Basic Mobile Terminating Call. The Procedure Emergency Call Indication may be used for informing the MGW about the emergency call. + +## 14.9 Subscriber and equipment trace + +See 3GPP TS 23.205 [7] sub-clause 14.9. + +## 14.10 Customized Alerting Tones + +### 14.10.1 General + +See 3GPP TS 23.205 [7] sub-clause 14.10.1. + +### 14.10.2 Audio CAT + +See 3GPP TS 23.205 [7] sub-clause 14.10.2. + +### 14.10.3 Multimedia CAT + +See 3GPP TS 23.205 [7] sub-clause 14.10.3. + +--- + +## 15 Messages/Procedures and their contents + +### 15.1 Messages between (G)MSC servers + +Table 15.1.1 lists the SIP methods that shall be supported between (G)MSC servers on Nc interface. Amendments and Endorsements to the referenced specifications are specified in 3GPP TS 29.231[4]. + +**Table 15.1.1: Messages between (G)MSC servers** + +| SIP method | Reference | +|------------|---------------| +| INVITE | RFC 3261 [15] | +| ACK | RFC 3261 [15] | +| BYE | RFC 3261 [15] | +| CANCEL | RFC 3261 [15] | +| OPTIONS | RFC 3261 [15] | +| INFO | RFC 2976 [17] | +| UPDATE | RFC 3311 [18] | +| PRACK | RFC 3262 [19] | + +### 15.2 Procedures between (G)MSC server and MGW + +#### 15.2.1 Generic Mc Interface Procedures + +Table 15.2.1.1 below indicates the procedures used between the (G)MSC server and the MGW in the Mc interface. These procedures are defined in Clause 16.2 of 3GPP TS 23.205 [7]. + +**Table 15.2.1.1: Required procedures defined in 3GPP TS 23.205 [7]** + +| Procedure defined in 3GPP TS 23.205 [7] | Remarks | +|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Change Flow Direction | NOTE 1 in that Clause is replaced by the following Note:<br><br>NOTE 1: This procedure may be combined with the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure, the "Reserve and Configure RTP Connection Point" procedure, the "Prepare Bearer" procedure, the "Reserve Circuit" procedure, the "Join Bearer Termination" procedure, or the "Isolate Bearer Termination" procedure. | +| Join Bearer Termination | | +| Isolate Bearer Termination | | +| Prepare Bearer | This procedure is not applicable for terminations towards a 3GPP SIP-I based circuit-switched core network, but it is applicable for terminations toward an Iu-CS interface with ATM transport, or to seize internal terminations in a MGW, e.g. for conferencing scenarios or for VGCS.<br><br>The optional "Tunnel Support" Information element is not applicable. | +| Reserve Circuit | | +| Change Through-Connection | The NOTE in that Clause is replaced by the following Note:<br><br>NOTE: This procedure may be combined with the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure, the "Reserve and Configure RTP Connection Point" procedure, the "Prepare Bearer" procedure, the "Reserve Circuit" procedure, the "Join Bearer Termination" procedure, or the "Isolate Bearer Termination" procedure. | +| Activate Interworking Function | | +| Bearer Released | | +| Release Termination | | +| Send Tone | | +| Stop Tone | | +| Play Announcement | | +| Stop Announcement | | +| Announcement Completed | | +| Tone Completed | | +| Detect DTMF | The NOTE in that Clause is replaced by the following Note:<br><br>NOTE: This procedure may be combined with the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure, the "Reserve and Configure RTP Connection Point" procedure, the "Prepare Bearer" procedure, the "Reserve Circuit" procedure. | +| Stop DTMF Detection | | +| Report DTMF | | +| Send DTMF | | +| Stop DTMF | | +| MGW Out-of-Service/ Maintenance locking | | +| MGW Communication Up | | +| MGW Restoration | | +| MGW Register | | +| MGW Re-register | | +| (G)MSC Server Ordered Re-register | | +| (G)MSC Server Restoration | | +| (G)MSC Server Out of Service | | +| Termination Out-of-Service | | +| Termination Restoration | | +| Audit Value | | +| Audit Capability | | +| Capability Update | | +| Command Reject | | +| Activate Voice Processing Function | | +| Modify Bearer Characteristics | This procedure is not applicable for terminations towards a 3GPP SIP-I based circuit-switched core network, but it is applicable for terminations toward an Iu-CS or A interface. | +| IWF Protocol Indication | | + +| | | +|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MGW Resource Congestion Handling – Activate | | +| MGW Resource Congestion Handling – Indication | | +| Bearer Modification Support | This procedure is not applicable for terminations towards a 3GPP SIP-I based circuit-switched core network, but it is applicable for terminations toward an Iu-CS interface. | +| CTM report | | +| Prepare IP Transport | | +| Modify IP Transport Address | | +| Emergency Call Indication | | +| Trace Activation | | +| Trace Deactivation | | +| Trace Activation result notification | | +| Continuity Check Tone | | +| Continuity Check Verify | | +| Continuity Check Response | | +| Rate Change | | +| Bearer Modified | This procedure is not applicable for terminations towards a 3GPP SIP-I based circuit-switched core network, but it is applicable for terminations toward an Iu-CS interface with ATM transport. | +| Bearer Modification Failed | This procedure is not applicable for terminations towards a 3GPP SIP-I based circuit-switched core network, but it is applicable for terminations toward an Iu-CS interface with ATM transport. | +| Termination heartbeat indication | | +| Inactivity timeout activation | | +| Inactivity timeout indication | | +| Reserve RTP Connection Point | | +| Configure RTP Connection Point | | +| Reserve and Configure RTP Connection Point | | + +## 15.2.2 SIP-I Specific Mc Interface Procedures + +The clauses below indicate the procedures used between the (G)MSC server and the MGW in the Mc interface that are specific for a SIP-I based Nc network. + +The procedures are logical, i.e. message identifiers are not part of the protocol. Several logical procedures can be combined into one H.248 command in order to perform required transactions. If several logical procedures are combined into one H.248 command, only one context/context request and only one bearer termination/bearer termination request is sent in the H.248 command. + +All the procedures below describe a successful operation. If the procedure is rejected, a Command Reject is sent back to the entity that sent the command request. + +Each Information Element, IE, is marked as (M) Mandatory, (C) Conditional or (O) Optional. A mandatory information element shall always be present. A conditional information shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional information element may be present or absent, at the discretion of the application at the sending entity. This categorisation is a functional classification, i.e., stage 2 information and not a stage 3 classification to be used for the protocol. + +The stage 2 and stage 3 message and information element names are not necessarily identical. + +--- + +## 16 Bearer Redirect + +Bearer Redirect is not supported within this 3GPP Release. + +--- + +## 17 (G)MSC MGW Tandeming + +For (G)MSC MGW Tandeming, the procedures specified in the clause 18 of 3GPP TS 23.205 [7] shall apply. + +--- + +## 18 Timers for SIP-I based CS core network + +The Start\_Bearer\_Establishment Timer, as defined in 3GPP TS 23.205 [7], shall apply to a SIP-I based CS core network. + +Timer functionality and procedures defined within ITU-T Q.1912.5 [9] Profile C shall apply to a SIP-I based CS core network. + +--- + +## 19 Multiple IP Realms + +Multiple IP realms are supported as specified in 3GPP TS 23.205 [7]. + +## Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|---------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2008-06 | CT#40 | CP-080245 | | | V2.0.0 approved in CT#40 | 2.0.0 | 8.0.0 | +| 2008-09 | CT#41 | CP-080464 | 0005 | 1 | MGW selection procedures impacts on Call Forwarding services | 8.0.0 | 8.1.0 | +| | | | 0006 | | MGW selection procedures impacts on Call Deflection service | | | +| | | | 0007 | | MGW selection procedures impacts on ODB | | | +| | | | 0008 | 1 | Global Text Telephony for SIP-I on Nc | | | +| | | | 0009 | 1 | IP interface type indicator | | | +| | | | 0010 | 1 | Call Hold Service | | | +| | | | 0011 | 1 | Bearer Establishment for Multiparty Bearers | | | +| | | | 0012 | | CS Data and Facsimile Updates | | | +| 2008-12 | CT#42 | CP-080697 | 0014 | | Clarifications for Multiparty service | 8.1.0 | 8.2.0 | +| | | | 0019 | | Call Clearing for A Interface on IP | | | +| | | | 0020 | 1 | BSS Internal Handover procedure | | | +| | | | 0021 | 1 | Multimedia CAT in the CS domain | | | +| | | | 0024 | | AoIP Impacts for Handover/Relocation | | | +| | | | 0025 | 1 | Telephone Numbering Schemes for a SIP-I based Nc Network | | | +| | | | 0027 | | Usage of SIP Resource-Priority header for eMLPP service | | | +| | | | 0028 | | Usage of re-INVITE without SDP for ECT Service | | | +| | | | 0029 | 1 | Impacts for MSP, VGCS, VBS within a SIP-I based Nc network | | | +| | | | 0030 | | Usage of IP Interface Type within a SIP-I based Nc Network | | | +| | | | 0031 | | Support of Bearer Redirect within a SIP-I based Nc network | | | +| | | | 0018 | 3 | Call Release | | | +| | | | 0032 | 1 | Data Calls | | | +| | | | 0033 | 2 | Call Clearing procedures at G-MSC | | | +| 2009-03 | CT#43 | CP-090029 | 0035 | 1 | G-MSC Procedures for Call Release- long variant | 8.2.0 | 8.3.0 | +| 2009-06 | CT#44 | CP-090307 | 0036 | | Customised Alerting Tones | 8.3.0 | 8.4.0 | +| | | CP-090306 | 0039 | 1 | MGW selection Context and Termination correction | | | +| | | | 0040 | 1 | Corrections to Deferred MGW Selection | | | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 8.4.0 | 9.0.0 | +| 2011-03 | CT#51 | CP-110069 | 0041 | 1 | Deferred MGW selection | 9.0.0 | 10.0.0 | +| | | | 0042 | 1 | Introduction of LCLS | | | +| 2011-09 | CT#53 | CP-110585 | 0044 | 1 | Addition of Anonymous Call Rejection in the CS layered architecture | 10.0.0 | 11.0.0 | +| 2011-12 | CT#53 | CP-110814 | 0045 | 1 | | 11.0.0 | 11.1.0 | +| 2012-11 | | | | | Change history table corrected. | 11.1.0 | 11.1.1 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23236/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/23_series/23236/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f05ee6241babe0925ea6be6cf513aeb6b132a19b --- /dev/null +++ b/marked/Rel-11/23_series/23236/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e08bf66886be290b3805e0c541f66d8777d6eef6f1448c8c1b2cc70515dec68 +size 26478 diff --git a/marked/Rel-11/23_series/23236/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/Rel-11/23_series/23236/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3430e513a09516c8655a78f187ae42d6ec156497 --- /dev/null +++ b/marked/Rel-11/23_series/23236/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7254b9f42838a1f2d34cb2077061222602ab51bf40147636298b3ffa9f5df5f2 +size 82936 diff --git a/marked/Rel-11/23_series/23236/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/23_series/23236/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88ccf449d7b6219517d836f3bcaa5187c8b013a0 --- /dev/null +++ b/marked/Rel-11/23_series/23236/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c50da004968a319caef4aa9120b305da700abeb54dbb7e1ca25d91881586701f +size 36306 diff --git a/marked/Rel-11/23_series/23236/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-11/23_series/23236/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bfecd5bda383c5ad7496bebf2aafe3c32b0e410 --- /dev/null +++ b/marked/Rel-11/23_series/23236/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dae06937662c3554687f3e83f8b180a60fed96e1b7b2f6353e7ac8cb7db7155a +size 205320 diff --git a/marked/Rel-11/23_series/23236/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/Rel-11/23_series/23236/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..886bb3c1185f9af55b6993bfd5c101c4836e5c61 --- /dev/null +++ b/marked/Rel-11/23_series/23236/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95164e8e5065bad1f4f0143700c3b0e762691cf86bac3554bf5c1dce291d2b69 +size 44317 diff --git a/marked/Rel-11/23_series/23236/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-11/23_series/23236/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96dfbf04e484706877a53e63c6dd3574be8d5724 --- /dev/null +++ b/marked/Rel-11/23_series/23236/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd6e8c9b0357dbdafb19ebb8bcdcc9c68a1873ded6d6b2dcaff4a7143c58a00b +size 143859 diff --git a/marked/Rel-11/23_series/23236/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/23_series/23236/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba3e3f950c4c9618330b232dec8cf668344a386e --- /dev/null +++ b/marked/Rel-11/23_series/23236/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c418679ba93df853cb21f7ec94c8719edd1f6cc86a5d0364210c9ff74f29843 +size 37361 diff --git a/marked/Rel-11/23_series/23236/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/23_series/23236/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6ef6c21fbaee0610f202062d7df0e1e72a6588c --- /dev/null +++ b/marked/Rel-11/23_series/23236/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4de6d978dc4c749a6ba4e739da3ddff22e5472cf1e6453aadb130f891d931ecf +size 74375 diff --git a/marked/Rel-11/23_series/23236/80ec3bf791fd8eb41f73a420c2122529_img.jpg b/marked/Rel-11/23_series/23236/80ec3bf791fd8eb41f73a420c2122529_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dcd3e5d00e5a915e2e2b3bb605393b56ef811c6 --- /dev/null +++ b/marked/Rel-11/23_series/23236/80ec3bf791fd8eb41f73a420c2122529_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2705963602b15b21c9021dcbf8030ebf77141cf9ae83980d7568838883e4eceb +size 42619 diff --git a/marked/Rel-11/23_series/23236/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-11/23_series/23236/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0934e04d4436012d18fb77ffcd28fc60df5e3eec --- /dev/null +++ b/marked/Rel-11/23_series/23236/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d5be23cc0fd6823998eed636bc812d2a7e4b6dc2305266ecfa5424cbff5fdec +size 95576 diff --git a/marked/Rel-11/23_series/23236/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/23_series/23236/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da24eec5ebf987ca448c4e8b8cfa7b2d5585c944 --- /dev/null +++ b/marked/Rel-11/23_series/23236/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73ed0e42863ec94700b49382e3d7a38c81e664fd6be1828ff66e8fa2ceba85a7 +size 92499 diff --git a/marked/Rel-11/23_series/23236/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/23_series/23236/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0841fa024a5ccd072bf1de1e72a3cce96db02258 --- /dev/null +++ b/marked/Rel-11/23_series/23236/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca24d9b12c5d9ffd82e770966b1eb9c8993111b593e1f590d67eedfb787c1de1 +size 168166 diff --git a/marked/Rel-11/23_series/23236/raw.md b/marked/Rel-11/23_series/23236/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8ed741ead91f223121ca0fa297a0bfcb45671743 --- /dev/null +++ b/marked/Rel-11/23_series/23236/raw.md @@ -0,0 +1,1158 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 General Description ..... | 8 | +| 4.1 Iu Flex Technical Requirements ..... | 8 | +| 4.2 Overview ..... | 8 | +| 4.3 Pool-Area and Network Resource Identification ..... | 10 | +| 4.4 NAS Node Selection Function ..... | 10 | +| 4.5 Load Balancing ..... | 11 | +| 4.5a Load Re-Distribution..... | 12 | +| 4.5a.1 General ..... | 12 | +| 4.5a.2 Network Mode of Operation = 1 ..... | 12 | +| 4.6 Mobility Management..... | 13 | +| 4.7 Default CN node and Backwards Compatibility..... | 13 | +| 4.8 Support of combined mobility management procedures..... | 14 | +| 4.8.1 Attach ..... | 14 | +| 4.8.2 Routing area update..... | 14 | +| 4.9 VGCS/VBS Compatibility Issues ..... | 14 | +| 4.10 Interactions with E-UTRAN ..... | 14 | +| 5 Functional Description..... | 15 | +| 5.1 MS Functions ..... | 15 | +| 5.2 RNC Functions..... | 15 | +| 5.2.1 Load Re-Distribution function in RNC ..... | 16 | +| 5.3 BSC Functions..... | 16 | +| 5.3.1 A interface mode ..... | 16 | +| 5.3.2 Gb mode ..... | 16 | +| 5.3.3 Iu mode..... | 17 | +| 5.3.4 Load Re-Distribution function in BSC..... | 17 | +| 5.4 MSC Functions..... | 17 | +| 5.4.1 TMSI Allocation..... | 17 | +| 5.4.2 Mobility Management and Handover/Relocation ..... | 17 | +| 5.4.3 Backward Compatibility and Default MSC ..... | 18 | +| 5.4.4 Support of Combined Procedures..... | 18 | +| 5.4.5 Load Re-Distribution function in MSC ..... | 18 | +| 5.5 SGSN Functions..... | 18 | +| 5.5.1 P-TMSI Allocation ..... | 18 | +| 5.5.2 Mobility Management and Handover/Relocation ..... | 18 | +| 5.5.3 Backward Compatibility and Default SGSN..... | 19 | +| 5.5.4 Support of Combined Procedures..... | 19 | +| 5.5.5 CS Paging ..... | 19 | +| 5.5.6 Load Re-Distribution function in SGSN ..... | 19 | +| 6 Application Examples..... | 19 | +| 6.1 Network configuration example 1 ..... | 19 | +| 6.2 Network configuration example 2..... | 20 | +| 7 Specific Examples..... | 21 | +| 7.1 Building blocks for signalling flows ..... | 21 | +| 7.1.1 RAN node selecting CN node in A interface mode..... | 21 | +| 7.1.2 RAN node selecting CN node in Gb interface mode..... | 21 | +| 7.1.3 RAN node selecting CN node in Iu interface mode ..... | 21 | + +| | | | +|-------------------------------|-------------------------------------------------------------------|-----------| +| 7.1.4 | New CN node selecting old CN node..... | 21 | +| 7.1.5 | Old CN node selecting new CN node..... | 21 | +| 7.1.6 | SGSN selecting MSC ..... | 22 | +| 7.2 | Signalling flow for Attach (Iu interface mode)..... | 22 | +| 7.3 | Signalling flows for Service Request (Iu interface mode) ..... | 24 | +| 7.3.1 | Service Request initiated by MS ..... | 24 | +| 7.3.2 | Service Request initiated by network ..... | 25 | +| 7.4 | Signalling flow for Routing Area Update (Iu interface mode) ..... | 27 | +| 7.5 | IMSI attach procedure / Location area update with IMSI..... | 30 | +| <b>Annex A (informative):</b> | <b>Network configuration examples .....</b> | <b>33</b> | +| A.1 | One city centre surrounded by residential areas ..... | 33 | +| A.1.1 | Assumptions..... | 33 | +| A.1.2 | TMSI calculation..... | 34 | +| A.2 | 3 Neighbouring large city centres ..... | 34 | +| <b>Annex B (informative):</b> | <b>Change history.....</b> | <b>40</b> | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +UMTS will build on the success of GSM and is likely to become even more widespread, increasing the importance of a flexible network structure to permit the different operational configurations in which these networks will be deployed. The requirements to have a RNC or BSC controlled by a single MSC server or SGSN lead to certain limitations. Allowing the BSCs and RNCs to connect to a number of MSC servers or SGSNs increases the networks performance in terms of scalability, distributing the network load amongst the serving entities, and reducing the required signalling as the user roams. + +# --- 1 Scope + +This document covers the details for the Intra Domain Connection of RAN Nodes to Multiple CN Nodes for GERAN and UTRAN based systems. In particular, it details the impacts to GSM and UMTS systems and the stage 2 procedures for the support of connecting a RNC or BSC to multiple MSC servers or SGSNs. The overall solution is described, and the detailed impacts on the existing specifications are identified. The description of a broadly similar concept for E-UTRAN based systems is not described in the document: instead, it is described in TS 23.401 [22]. + +NOTE: The specified solution impacts RAN nodes. In case an upgrade of radio networks is not performed, the solutions for deploying NNSF functionality above RAN nodes described in TR 23.924 [23] may be used as a guideline for connecting RAN nodes to multiple MSC servers. + +The reference model to which these procedures apply can be found within TS 23.002 [1]. Detailed architectural requirements within the subsystems are contained within the remainder of the 23 series of specifications e.g. the requirements for the Packet Switched (PS) domain are contained within TS 23.060 [2] and the requirements for the Bearer Independent CS Core Network are contained in TS 23.205 [14]. + +# --- 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.002: "Network Architecture". +- [2] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2". +- [3] 3GPP TS 23.012: "Location management procedures". +- [5] 3GPP TS 25.331: "Radio Resource Control (RRC) Protocol Specification". +- [6] 3GPP TS 25.301: "Radio interface protocol architecture". +- [7] 3GPP TS 25.303: "UE functions and inter-layer procedures in connected mode". +- [8] 3GPP TR 21.905: "3G Vocabulary". +- [9] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". +- [10] 3GPP TS 25.410: "UTRAN Iu Interface: General Aspects and Principles". +- [11] 3GPP TS 23.228: "IP Multimedia Subsystem – Stage 2". +- [12] 3GPP TS 43.051: "GSM/EDGE Radio Access Network (GERAN) overall description (Stage 2)". +- [13] 3GPP TS 23.153: "Out of Band Transcoder Control - Stage 2". +- [14] 3GPP TS 23.205: "Bearer Independent CS Core Network – Stage 2". +- [15] 3GPP TR 25.931: "UTRAN Functions, examples on signalling procedures". +- [16] GSM 08.18: "General Packet Radio Service (GPRS);Base Station System (BSS) -Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [17] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". + +- [18] 3GPP TS 23.003: "Numbering, addressing and identification". + - [19] 3GPP TS 43.068: "Voice Group Call Service (VGCS); Stage 2". + - [20] 3GPP TS 43.069: "Voice Broadcast Service (VBS); Stage 2". + - [21] 3GPP TS 23.251: "Network Sharing; Architecture and functional description". + - [22] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". + - [23] 3GPP TS 924: "Feasibility Study on NAS Node Selection Function above BSC/RNC". +- + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms defined in TR 21.905 [8] apply: + +**CN node:** for the purpose of this specification, and unless otherwise stated, a CN node is either an MSC or an SGSN. + +**NAS node selection Function:** The function used to assign specific network resources (i.e. MSC or SGSN) to serve a mobile station and subsequently route the traffic to the assigned network resource. + +**Network Resource Identifier:** A specific parameter used to identify the CN node assigned to serve a mobile station. + +**Non-broadcast LAI/RAI:** Each CN node in a pool have to be assigned one unique non-broadcast LAI/RAI that it use in case it want to be offloaded. Each CN node in the pool has to be aware of the non-broadcast LAI/RAI assigned to the other CN nodes in the pool, because in case of re-distribution the 'target CN node' will retrieve data (e.g. IMSI, security context, MM & PDP contexts) from the 'offloaded CN node' based on non-broadcast LAI/RAI. + +**Null-NRI:** A 'null-NRI' indicates to a radio node (BSC/RNC) that the NAS Node Selection Function shall be used for selecting a CN node to receive a message. There is one unique 'null-NRI' in a PLMN supporting pool functionality. In MOCN shared networks (see TS 23.251 [21]) with multiple CN Operators, there is one unique 'null-NRI' per CN operator. That is, in MOCN networks the RAN Operator handles multiple 'null-NRIs'. + +**Pool-area:** A pool area is an area within which a MS may roam without need to change the serving CN node. A pool area is served by one or more CN nodes in parallel. All the cells controlled by a RNC or BSC belong to the same one (or more) pool area(s). + +**RAN node:** for the purpose of this specification, and unless otherwise stated, a RAN node is either an RNC or a BSC. + +**RAN node service area:** This area contains all the cells controlled by the RNC or BSC. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [8] 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 [8]. + +| | | +|--------|-------------------------------------| +| AS | Access Stratum | +| BSC | Base Station Controller | +| BVCI | BSSGP Virtual Connection Identifier | +| CN | Core Network | +| CS | Circuit Switched | +| CS-MGW | Circuit Switched Media Gateway | +| DNS | Directory Name Server | +| IDNNS | Intra Domain NAS Node Selector | +| LA | Location Area | + +| | | +|------|-----------------------------------| +| LAI | Location Area Identity | +| MOCN | Multi-Operator Core Network | +| MS | Mobile Station | +| MSC | Mobile Switching Centre | +| NAS | Non Access Stratum | +| NRI | Network Resource Identifier | +| O&M | Operation and Maintenance | +| PS | Packet Switched | +| RA | Routing Area | +| RAI | Routing Area Identity | +| RAN | Radio Access Network | +| RNC | Radio Network Controller | +| SRNS | Serving Radio Network Subsystem | +| TMSI | Temporary Mobile Station Identity | +| TLLI | Temporary Logical Link Identifier | +| UE | User Equipment | + +# --- 4 General Description + +## 4.1 Iu Flex Technical Requirements + +This provides a (non-exhaustive) set of technical requirements: + +1. Iu Flex capable RAN nodes such as the RNC/BSC shall be able to select any CN node such as the SGSN/MSC-Server within a pool area +2. Iu Flex capable RAN nodes and CN nodes shall be able to co-exist with pre Release 5 RAN nodes and pre Release 5 CN nodes. +3. The network shall provide the CN node routing information to the UE and the UE shall store it. +4. The UE shall provide the routing information received from the serving CN node to the RAN node. In some cases, this serving CN node may be an Evolved Packet Core MME. +5. The solution shall enable the reduction of signalling within the core network (e.g. reduction of the HLR signalling traffic). +6. The solution shall enable an improved scaling between radio access nodes and the core network nodes. + +## 4.2 Overview + +**Editor's Note: Clarification is required in order to remove RAN nodes and CN node terminology and to capture that this is referring to the control signalling aspects.** + +The Intra Domain Connection of RAN Nodes to Multiple CN Nodes overcomes the strict hierarchy, which restricts the connection of a RAN node to just one CN node. This restriction results from routing mechanisms in the RAN nodes which differentiate only between information to be sent to the PS or to the CS domain CN nodes and which do not differentiate between multiple CN nodes in each domain. The Intra Domain Connection of RAN Nodes to Multiple CN Nodes introduces a routing mechanism (and other related functionality), which enables the RAN nodes to route information to different CN nodes within the CS or PS domain, respectively. + +The Intra Domain Connection of RAN Nodes to Multiple CN Nodes introduces further the concept of “pool-areas” which is enabled by the routing mechanism in the RAN nodes. A pool-area is comparable to an MSC or SGSN service area as a collection of one or more RAN node service areas. In difference to an MSC or SGSN service area a pool-area is served by multiple CN nodes (MSCs or SGSNs) in parallel which share the traffic of this area between each other. Furthermore, pool-areas may overlap which is not possible for MSC or SGSN service areas. From a RAN perspective a pool-area comprises all LA(s)/RA(s) of one or more RNC/BSC that are served by a certain group of CN nodes in parallel. One or more of the CN nodes in this group may in addition serve LAs/RAs outside this pool-area or may also serve other pool-areas. This group of CN nodes is also referred to as MSC pool or SGSN pool respectively. + +The Intra Domain Connection of RAN Nodes to Multiple CN Nodes enables a few different application scenarios with certain characteristics. The service provision by multiple CN nodes within a pool-area enlarges the served area compared to the service area of one CN node. This results in reduced inter CN node updates, handovers and relocations and it reduces the HLR update traffic. The configuration of overlapping pool-areas allows to separate the overall traffic into different MS moving pattern, e.g. pool-areas where each covers a separate residential area and all the same city centre. Other advantages of multiple CN nodes in a pool-area are the possibility of capacity upgrades by additional CN nodes in the pool-area or the increased service availability as other CN nodes may provide services in case one CN node in the pool-area fails. + +An MS is served by one dedicated CN node of a pool-area as long as it is in radio coverage of the pool-area. Figure 1 shows most of the possible pool-area configurations. It contains CS pool-area 1 (RAN area 1, 2, 5, 6 served by MSCs 1, 2, 3), CS pool-areas 2 (RAN area 2, 3, 6, 7 served by MSCs 4, 5, 6), PS pool-area 1 (RAN area 1, 5 served by SGSNs 1, 2) and PS pool-area 2 (RAN area 2, 3, 6, 7 served by SGSNs 3, 4, 5). In addition the RAN areas 4 and 8 are served by MSC 7 and SGSN 6 without any usage of the Intra Domain Connection of RAN Nodes to Multiple CN Nodes. The possibility to configure overlapping pool-areas is shown by the CS pool-areas 1 and 2. The PS pool-areas 1 and 2 are configured non-overlapping. The pool-areas of the CS and the PS domain may be configured identical as CS pool-area 2 and PS pool-area 2 or they may be configured differently as shown by CS pool-area 1 and PS pool-area 1. The number or capacity of CN nodes is configured independently for each pool-area. The usage of the Intra Domain Connection of RAN Nodes to Multiple CN Nodes may be configured in parts of the network only. It co-exists with other areas not using this feature as shown in the figure with RAN areas 4 and 8 which are served by MSC 7 and SGSN 6. + +![Figure 1: Pool-area configuration example. The diagram illustrates various pool-area configurations for RAN nodes. At the top, MSC 1, 2, and 3 are shown, with MSC 1 connected to RAN nodes in Area 1 and Area 5. MSC 4, 5, and 6 are shown, with MSC 4 connected to RAN nodes in Area 2, 3, 6, and 7. MSC 7 is shown connected to RAN nodes in Area 4 and Area 8. At the bottom, SGSN 1 and 2 are shown connected to RAN nodes in Area 1 and Area 5. SGSN 3, 4, and 5 are shown connected to RAN nodes in Area 2, 3, 6, and 7. SGSN 6 is shown connected to RAN nodes in Area 4 and Area 8. Dashed lines indicate pool areas: CS pool-area 1 (Areas 1, 2, 5, 6), CS pool-area 2 (Areas 2, 3, 6, 7), PS pool-area 1 (Areas 1, 5), and PS pool-area 2 (Areas 2, 3, 6, 7).](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +Figure 1: Pool-area configuration example. The diagram illustrates various pool-area configurations for RAN nodes. At the top, MSC 1, 2, and 3 are shown, with MSC 1 connected to RAN nodes in Area 1 and Area 5. MSC 4, 5, and 6 are shown, with MSC 4 connected to RAN nodes in Area 2, 3, 6, and 7. MSC 7 is shown connected to RAN nodes in Area 4 and Area 8. At the bottom, SGSN 1 and 2 are shown connected to RAN nodes in Area 1 and Area 5. SGSN 3, 4, and 5 are shown connected to RAN nodes in Area 2, 3, 6, and 7. SGSN 6 is shown connected to RAN nodes in Area 4 and Area 8. Dashed lines indicate pool areas: CS pool-area 1 (Areas 1, 2, 5, 6), CS pool-area 2 (Areas 2, 3, 6, 7), PS pool-area 1 (Areas 1, 5), and PS pool-area 2 (Areas 2, 3, 6, 7). + +**Figure 1: Pool-area configuration example** + +## 4.3 Pool-Area and Network Resource Identification + +A pool-area is an area within which an MS may roam without a need to change the serving CN node. A pool-area is served by one or more CN nodes in parallel. The complete service area of a RAN node (RNC or BSC) belongs to the same one or more pool-area(s). A RAN node service area may belong to multiple pool-areas, which is the case when multiple overlapping pool-areas include this RAN node service area. The pool-areas of the CS and of the PS domain are configured independently with the granularity of RAN node service areas. Therefore, all uniqueness statements below + +apply to each of the domains (CS/PS) separately. If LAs or RAs span over multiple RAN node service areas then all these RAN node service areas have to belong to the same pool-area. + +The Network Resource Identifier (NRI) identifies uniquely an individual CN node out of all CN nodes, which serve in parallel a pool-area. The length of the NRI shall be the same in all nodes of a domain in one pool-area. In areas where pool-areas overlap the NRI identifies uniquely a CN node out of all CN nodes, which serve all these overlapping pool-areas, i.e. an NRI identifies uniquely a CN node within a RAN node. In case of overlapping pool-areas the NRI length shall be configured to be the same in all the nodes of a specific domain serving these pool-areas. Note again, that the NRIs of the CS and the PS domain are independent of each other as the PS and the CS domain CN nodes are addressed independently. More than one NRI may be assigned to a CN node. + +The NRI is part of the temporary identity TMSI (CS domain) or P-TMSI (PS domain), which is assigned by the serving CN node to the MS. Each CN node which supports the "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" is configured with its specific one or more NRI(s). The (P-)TMSI allocation mechanism in the CN node generates (P-)TMSIs which contain a configured NRI in the relevant bit positions. The NRI has a flexible length between 10 and 0 bits (0 bits means the NRI is not used and the feature is not applied). + +In Iu mode the MS provides an Intra Domain NAS Node Selector (IDNNS) TS 25.331 [5] in the AS part of the RRC-Initial-direct-transfer message to the RAN node (RNC or BSC). The IDNNS contains a routing parameter with a fixed length of 10 bits. This routing parameter transports the NRI value. In addition the IDNNS contains an indication from which identity (TMSI, IMSI, IMEI, ...) the routing parameter is derived. The RAN node masks the significant bits out of the routing parameter part of the IDNNS to determine the NRI which is relevant to identify the CN node. The most significant bit of the NRI shall correspond with the most significant bit of the routing parameter in the IDNNS. When the IDNNS is derived from the IMSI, the IDNNS has a value (V) from the range 0 to 999 as defined in TS 25.331 [5]. The RAN node shall be configured to use the value (V) to select a CN node. Each value (V) corresponds a single CN node. Typically many values of (V) may point to the same CN node. In A/Gb mode. + +In A/Gb-mode for the A interface the RAN node derives the NRI from any initial NAS signalling message. The RAN node masks the significant bits out of the TMSI to determine the NRI, which identifies the CN node. In A/Gb-mode for the Gb interface the RAN node derives the NRI from the TLLI. The RAN node masks the significant bits out of the TLLI to determine the NRI, which identifies the CN node. + +For all three cases, Iu, A interface and Gb mode, it is configured in the RAN node which bits out of the information elements provided by the MS are significant for the NRI. The NRI is coded in bits 23 to 14 of TMSI or P-TMSI. Regardless of the NRI length the most significant bit of the NRI is always in bit 23 of TMSI or P-TMSI (examples of NRI position are given in annex A.2), see also TS 23.003 [18]. + +The whole network may be configured as one pool-area, a network may configure multiple pool-areas and the configuration of pool-areas may be combined with MSC or SGSN service areas which are not belonging to pool-areas. The change of a pool-area is not visible to the MS. In general there is no need to detect a pool-area change. It may be advantageous for load balancing purposes to detect pool-area changes in the network to distribute MSs entering a pool-area to CN nodes with an appropriate load status. MSs changing a pool-area may be detected by configuration of different NRI values for adjacent pool-areas. The pool-area change information potentially provided in the IDNNS by an MS in Iu mode is ignored by the network. + +## 4.4 NAS Node Selection Function + +This function is used in RAN nodes and potentially in CN nodes. In the RAN node the function selects the specific CN node (i.e. MSC or SGSN) to which initial NAS signalling messages or LLC frames are routed. The NRI identifies the specific CN node. If the NAS Node Selection Function has a CN node address configured for the NRI derived from the initial NAS signalling message or from the LLC frame then this message or frame is routed to this address. If no CN node address is configured for the derived NRI or if no NRI can be derived (e.g. the MS indicated an identity which contains no NRI) then the NAS Node Selection Function selects an available CN node (e.g. according to load balancing) and routes the message or LLC frame to the selected CN node. + +The pool-area has no influence on the decisions of the NAS Node Selection Function as pool-areas may overlap. The NAS Node Selection Function in the RAN node derives the NRI from the IDNNS when the MS is supported in Iu mode. When the MS is supported in Gb mode the NRI is derived from the TLLI and for A interface mode the NRI is derived from the TMSI. + +NOTE: A routing-area update after SRNS relocation is not an initial NAS signalling message, thus it is routed along the existing Iu-connection to the SGSN. + +In A/Gb mode in case a MSC/VLR sends a paging-request/paging with IMSI (i.e. the paging message does not contain a TMSI), the NAS node selection function in the BSC shall upon reception temporarily store the Global-CN- ID of the node that issued the paging-request/paging message. If the NAS node selection function in A/Gb mode receives a paging-response with an IMSI then it should check the temporarily stored Global-CN-ID on entries matching this IMSI and forward the paging-response to the node identified by this Global-CN-ID. + +In Iu mode in case a MSC/VLR sends a paging-request/paging with IMSI (i.e. the paging message does not contain a TMSI), the NAS node selection function in the BSC/RNC may upon reception temporarily store the Global-CN-ID of the node that issued the paging-request/paging message. If the NAS node selection function in Iu mode receives an Initial Direct Transfer message with an IDNNS derived from IMSI as a result of IMSI paging: + +- and if BSC/RNC has temporarily stored the Global-CN-ID then it should check the temporarily stored Global-CN-ID on entries matching this IDNNS and forward the paging-response to the node identified by this Global-CN-ID or +- the BSC/RNC shall use the IDNNS derived from IMSI to select a CN node. In this case the IDNNS has a value (V) from the range 0 to 999 as defined in TS 25.331 [5]. The RAN node shall be configured to use the value (V) to select a CN node. Each value (V) corresponds a single CN node. Typically many values of (V) may point to the same CN node. + +In UMTS, an MS answering a paging with IMSI includes in its response an IDNNS derived from its TMSI, if the MS has a valid TMSI. Temporarily storing the IMSI in the RNC increases the success rate to reach the MS that have both lost their TMSI and are paged with IMSI. In GSM, an MS paged with IMSI always answers with IMSI. + +If the MSC/VLR initiates the paging procedure via Gs-interface the SGSN has to add the MSC/VLR-identity to the paging-request/paging message. + +An MS will return an Attach Request containing the IMSI parameter as a response to a PS IMSI paging. Also, a PS IMSI paging is not time supervised from the SGSN sending the message. Therefore the RAN node receiving such a paging request does not have to buffer the associated SGSN identity. This again means that the NAS Node Selection Function in the RAN node selects an available SGSN (e.g. according to load balancing) when it receives an Attach Request containing the IMSI parameter. + +## 4.5 Load Balancing + +Preferably, the NAS Node Selection Function in the RAN node balances the load between the available CN nodes. This is performed by an appropriate selection of the CN node for an MS which was not yet assigned to a CN node, i.e. when there is no CN node configured for the NRI indicated by the MS, when a 'random TLLI' is received (Gb-mode BSC), when no NRI can be derived or in exceptional cases, e.g. when the CN node corresponding to an NRI cannot be reached. + +The load-balancing algorithm is implementation specific. + +When the NAS Node Selection Function in the RAN (or, if using Network Mode of Operation I, the SGSN) receives an indication that the MS is configured for low access priority (e.g. because it is used for Machine Type Communication), the NAS Node Selection Function may take this indication into account when selecting the CN node (e.g. to select an MSC that has a particularly large VLR capacity). + +In case of handover/relocation into a pool-area a load balancing between all the target CN nodes serving this pool-area is gained by configuration. Source CN nodes which support Intra Domain Connection of RAN Nodes to Multiple CN Nodes may be configured with all possible target CN nodes for each handover/relocation target. Source CN nodes which do not support the Intra Domain Connection of RAN Nodes to Multiple CN Nodes can configure only one target CN node per handover/relocation target. In this case each of source CN nodes which handover/relocate to the same pool-area may be configured with another target CN node out of all target CN nodes serving the same handover/relocation target. The mechanism for distribution of the traffic between the handover/relocation target CN nodes is implementation specific. This load balancing is complemented by the NAS Node selection Function in the RAN, which distributes MSs between the CN nodes when these MSs enter the pool-area in idle mode. + +As more than one SGSN may send downlink data at the same time for a cell or a BVCI the total possible downlink traffic has to shared between the SGSNs as described in clause 5.3.2. + +In case of CS domain subsequent handover/relocation, if the controlling MSC supports Intra Domain Connection of RAN Nodes to Multiple CN Nodes then it should check the target indicated by the serving MSC. If it is in its own pool area then the handover/relocation is handled as one back to the controlling MSC (the target MSC indicated by the + +serving MSC is not taken into account). If the target location is not in its own pool area then the target MSC indicated by the serving MSC is taken into account as normal (handover/relocation to a third MSC). + +If the controlling (anchor) MSC is not in the same pool as target third MSC and if the controlling MSC does not support Intra Domain Connection of RAN Nodes to Multiple CN nodes, because the serving MSC can select any third MSC in the target pool area, the operator should configure the addresses of all possible third MSCs within the controlling MSC. + +## 4.5a Load Re-Distribution + +### 4.5a.1 General + +There are situations where a network operator will wish to remove load from one CN node in an orderly manner (e.g. to perform scheduled maintenance, or, to perform load re-distribution to avoid overload) with minimal impact to end users and/or additional load on other entities. The re-distribution procedure does not require any new functionality in the terminal, that is, all terminals can be moved. + +Re-distribution of UEs is initiated via an O&M command in the CN node, which needs to be off-loaded. In a first phase (a couple of Periodic LU/RAU periods long), UEs doing LU/RAU or Attach are moved to other CN nodes in the pool. When the CN node receives the Location Update, Routing Area Update or Attach request, it returns a new TMSI/P-TMSI with a null-NRI, and a non-broadcast LAI/RAI in the accept message. + +In CS domain the non-broadcast LAI will cause the terminal to immediately send a new Location Update, which the RAN node then will route to a new MSC due to the null-NRI. In the PS domain, a new Routing Area Update is triggered by setting the periodic routing area update timer to a sufficiently low value (recommended value is 4 seconds) in the accept message. The UE will shortly after send a new Routing Area Update that the RAN node then will route to a new SGSN due to the presence of a null-NRI. + +In a second phase (PS domain specific), the SGSN requests all UEs trying to set up PDP Contexts to detach & reattach. When they reattach, the SGSN moves them as in the first phase described above. + +A third phase includes scanning through remaining UEs and initiating a move of them to other CN nodes. In the PS domain UEs are requested to detach and reattach, which will cause them to be moved. In case of CS domain a new TMSI is allocated to these UEs using the TMSI re-allocation procedure (with null-NRI and non-broadcast LAI) so that a Location Update is triggered when the ongoing CM transaction ends, which will cause them to be moved. + +UEs being moved from one CN node are stopped from registering to the same CN node again by an O&M command in BSCs and RNCs connected to the pool. UEs moving into a pool area may also be stopped from registering into a CN node being off-loaded in the same manner. + +In network configurations using MOCN network sharing, re-distribution is always done between CN nodes within the same CN Operator. This is ensured by each CN Operator using his own unique null-NRI. The RAN node is preconfigured with the null-NRIs for the different CN Operators, and it uses the null-NRI to select a CN node within the same CN Operator. + +A CN node should ensure that move operations does not overload the network. BSCs and RNCs shall be able to handle situations where several CN nodes are off-loaded simultaneously. + +### 4.5a.2 Network Mode of Operation = 1 + +If an operator is using Network Mode of Operation = 1 (i.e. using combined MM and GMM procedures and the Gs interface), then redistribution of MSC load needs to be handled in a special way. + +Redistribution of UEs is initiated by O&M command in the SGSN providing the Gs interface to the MSC to be off-loaded. The corresponding NRI distribution or IMSI Hash table is reconfigured to reflect the redistribution. If the SGSNs are also configured in a pool, this is repeated for any SGSN connected to that MSC. The NRI distribution or IMSI Hash table shall have a consistent configuration in all SGSNs in the pool (to ensure that a redistribution of SGSN load doesn't affect the MSC registration of UEs). + +The redistribution is done in two phases. During the first phase, the UEs that are performing combined RA/LA updates are moved to a new MSC. When the SGSN receives a Routing Area Update Request (combined RA/LA updating), it checks if the particular UE shall be moved (i.e. it has a Gs association with the MSC being off-loaded). If the UE shall be moved, the SGSN invokes the MSC selection function (NRI distribution or IMSI Hash) to decide where the UE should be distributed. SGSN sends the (BSSAP+) Location-Update-Request (IMSI attach) to the new selected MSC + +where the UE is registered. Stationary UEs (i.e. UEs not performing RA/LA updates) are not moved during this first phase. + +During the second phase, the SGSN scans its Gs associations to find out which UEs shall be moved. For each UE with an association to the MSC being off-loaded, the SGSN sends a Detach Request (indicating IMSI detach). The UE is forced to re-attach to non-GPRS service (note that there is no impact on PDP contexts in this case). The UE sends a RAU request (combined RA/LA updating with IMSI Attach). SGSN checks if the UE shall be moved. If the UE shall be moved, the SGSN invokes the MSC selection function (NRI distribution or IMSI Hash) to select another MSC. SGSN sends the (BSSAP+) Location-Update-Request (IMSI attach) to the new MSC where the UE is registered. + +During the redistribution, incoming IMSI Detach messages are (as during normal operation) routed to respective existing associated MSC. That is, the reconfigured NRI distribution or IMSI Hash doesn't affect the routing of IMSI Detach messages. + +## 4.6 Mobility Management + +An MS performs LA or RA Updates and Attachments, which may result in a change of the serving CN node. In these procedures the new CN node requests from the old CN node MS specific parameters. If multiple CN nodes are configured in the new CN node for the old RA or LA indicated by the MS then the new CN node derives the NRI from the old (P-)TMSI indicated by the MS. The new CN node uses the old RA or LA together with the NRI to derive the signalling address of the old CN node from its configuration data. If the network contains nodes that cannot derive the old CN node from LAI/RAI and NRI a default CN node for each RA or LA (as described below) shall be used to resolve the ambiguity of the multiple CN nodes serving the same area. + +## 4.7 Default CN node and Backwards Compatibility + +CN nodes that can only derive one CN node from the LAI or RAI (e.g. because they do not support the Intra Domain Connection of RAN Nodes to Multiple CN Nodes, or no detailed knowledge of the NRIs is configured) are not aware, that multiple CN nodes may serve a LA or RA. These nodes can therefore contact only one CN node per LA or RA, respectively. This node will further on be referred to as default node. + +A default node resolves the ambiguity of the multiple CN nodes per LA or RA by deriving the NRI from the TMSI and P-TMSI. The default node relays the signalling between the new CN node and the old CN node. + +Note that the default node is configured per LA or RA. So different CN nodes in a network might have configured different default nodes for a LA or RA. With this approach more than one of the CN nodes that serve a pool-area can be used as default-node, so load concentration on one node and a single point of failure can be avoided. + +Note further, that it may be required to keep information on ongoing MAP/GTP dialogues in the default nodes. + +The handover/relocation from CN nodes which do support the Intra Domain Connection of RAN Nodes to Multiple CN Nodes to CN nodes not supporting this features does not need a NAS Node Selection Function in the originating CN node as there is only one target CN node. The originating CN node discovers from its configuration data, that there is only one target CN node for the requested handover/relocation target ID. See clause 4.5 for handling of subsequent handover/relocation in the controlling CN node. + +## 4.8 Support of combined mobility management procedures + +### 4.8.1 Attach + +In case of 'combined GPRS/IMSI attach' or 'GPRS attach when already IMSI attached', the SGSN sends the Location Update Request message to the MSC/VLR. The SGSN selects an MSC/VLR from the available MSC/VLRs which serve the current LA of the MS. The selection is based on the TMSI based NRI as provided by the UE or a hash value derived from the IMSI. It is configured in the SGSN which NRI values and range of the hash values relates to which MSC/VLR. This selection mechanism avoids a random change of the MSC/VLR for MSs using combined procedures when an SGSN fails. The new SGSN will select the same MSC/VLR. + +In some networks, the SGSN may be configured to select the MSC/VLR for "MSs configured for low access priority" with a different load balance to that used for MSC/VLR selection for other UEs. In this case the SGSN maintains a separate NRI and hash value function for "MSs configured for low access priority". + +### 4.8.2 Routing area update + +The CN node changes in the following considerations result from pool-area changes (when pool-areas are configured) or from CN node service area changes (when no pool-areas are configured). For each domain (PS or CS) it is configured independently whether pool-areas are used or not. + +When neither the MSC nor the SGSN are changed, the association for an MS between both CN nodes will also not change. + +When the MSC changes but the SGSN does not change, the SGSN selects a new MSC because the new LA is not served by the old MSC/VLR. The selection mechanism is as described for the attach above. + +When the SGSN changes but the MSC does not change, the new SGSN selects the old MSC to establish a Gs association because the new SGSN uses the same selection mechanism as described above for the attach with the same parameters as configured in the old SGSN. + +When both the MSC and the SGSN change, the new SGSN selects a new MSC to establish a Gs association. The selection mechanism is as described for the attach above. + +## 4.9 VGCS/VBS Compatibility Issues + +Voice Group Call Services, TS 43.068 [19], as well as Voice Broadcast Service, TS 43.069 [20], are specified for A-interface only. Architectural enhancements and procedures needed to support these services in an area where Intra Domain Connection of RAN Nodes to Multiple CN Nodes is applied on the A-interface are specified in TS 43.068 [19] and TS 43.069 [20]. + +## 4.10 Interactions with E-UTRAN + +The MS has separate core network temporary identities for GERAN/UTRAN (the RAI plus P-TMSI in the packet domain) and E-UTRAN (the GUTI). + +Following movement between GERAN/UTRAN and E-UTRAN the MS will have both a P-TMSI and a GUTI. Independent of whether the Idle mode Signalling Reduction (ISR) feature is active, one or both of the P-TMSI and GUTI may be valid. If the MS is E UTRAN capable, then TS 23.401 [22], TS 23.060 [2] and TS 23.003 [18] define rules as to how the MS shall select and encode the identity to place in the P-TMSI/TLLI parameters used in the Routing Area Update procedure. + +NOTE: ISR is specified and described in TS 23.401 [22]. + +In some network deployments the MME and SGSN may be combined in the same physical platform (while in other deployments they may be separated). + +TS 23.003 [18] specifies a mapping from the E-UTRAN core network temporary identity (the GUTI) to the TLLI that facilitates the BSC to route an RA update caused by movement from E-UTRAN to GERAN to an SGSN that is on the same physical platform as the MME. + +TS 23.003 [18] and TS 25.331 [5] specify a mapping from the E-UTRAN core network temporary identity (the GUTI) to the IDNNS that facilitates the RNC to route an RA update caused by movement from E-UTRAN to UTRAN to an SGSN that is on the same physical platform as the MME. + +TS 23.003 [18] also specifies a mapping from the RAI and P-TMSI to the GUTI that facilitates the E-UTRAN to route to an MME that is on the same physical platform as the SGSN. For this mapping function to work correctly when using combined MME/SGSNs, the effective maximum length of the NRI is reduced from 10 bits to 8 bits. + +# --- 5 Functional Description + +## 5.1 MS Functions + +In Iu mode the MS provides the IDNNS to the RNC in the access stratum part of the *RRC\_initial\_DT* message as described in TS 25.331 [5]. + +If the MS is E-UTRAN capable, then TS 23.401 [22], TS 23.060 [2] and TS 23.003 [18] define rules as to how the MS shall select and encode the identity to place in the P-TMSI/TLLI parameters used in the Routing Area Update procedure. For the PS domain, the E-UTRAN capable MS shall use this P-TMSI parameter to derive the UTRAN IDNNS parameter. For the CS domain, the E-UTRAN temporary identities shall not be used to derive the IDNNS: instead the MS shall use its (MSC supplied) TMSI, if that TMSI is valid, to derive the IDNNS. + +NOTE: movement of an E-UTRAN capable MS between GERAN/UTRAN and E-UTRAN accesses does not cause the TMSI to be marked as invalid or deleted. + +When the MS in Iu mode replies to IMSI paging, it shall derive IDNNS from (P)TMSI if a valid one is available. If (P)TMSI is not available, the MS shall derive IDNNS from IMSI. + +No further changes are expected in the MS for Gb or A interface mode. + +## 5.2 RNC Functions + +The RNC provides the NAS Node Selection Function. It masks the significant number of bits out of the IDNNS provided by the MS together with the initial NAS signalling message. The significant number of bits is configured in the RNC. The NAS Node Selection Function derives from the NRI the address of the specific CN node for the relevant domain (CS or PS). The association between NRI values and CN node addresses is configured in the RNC (O&M). + +The RNC routes the initial NAS signalling messages according to the NRI and the "domain indicator" (CS or PS) to the relevant CN node if a CN node address is configured in the RNC for the specific NRI and the requested domain (CS or PS). + +When IDNNS is derived from the IMSI, the IDNNS has a value (V) from the range 0 to 999 as defined in TS 25.331 [5]. The RAN node shall be configured to use the value (V) to select a CN node. Each value (V) corresponds a single CN node. Typically many values of (V) may point to the same CN node. In some networks, the RAN node may be configured to select the MSC/VLR for "UEs configured for low access priority" with a different load balance to that used for MSC/VLR selection for other UEs. In this case the RAN node maintains a second, separate mapping table between value (V) and CN node for "UEs configured for low access priority". + +If the selected CN node is not available or if no CN node address is configured in the RNC for the requested NRI or if the provided identity contains no NRI then the RNC routes the initial NAS signalling message to a CN node selected from the available CN nodes which serve the related domain (CS or PS). The selection mechanism is implementation dependent and should enable load balancing between the available CN nodes. In some networks, the RNC may be configured to select the MSC/VLR for "UEs configured for low access priority" with a different load balance to that used for MSC/VLR selection for other UEs. + +NOTE 1: A routing-area update after SRNS relocation is not an initial NAS signalling message, thus it is routed along the existing Iu-connection to the SGSN. + +NOTE 2: The RAN can determine whether or not the "MS is configured for low access priority" from information received in the RRC establishment signalling. + +In case a MSC sends a paging with IMSI (i.e. the paging message does not contain a TMSI), the RNC may, for purposes to increase the paging success rate, upon reception temporarily store the Global-CN-ID of the node that issued the paging message. If the MSC/VLR initiates the paging procedure via Gs-interface the SGSN has to add the Global-CN-ID to the paging message. + +### 5.2.1 Load Re-Distribution function in RNC + +When the RNC receives a message with a 'null-NRI' it uses the NAS Node Selection Function for selecting a CN node where to forward the message. CN node(s) with re-distribution in progress should be excluded from the NAS Node Selection algorithm in the RNC. This is done by O&M configuration in the RNC. + +In network configurations using MOCN network sharing, the RNC is preconfigured with a null-NRI for each CN Operator in the MOCN. The RNC selects a CN node belonging to a CN Operator based on what 'null-NRI' is received. + +## 5.3 BSC Functions + +### 5.3.1 A interface mode + +The BSC provides the NAS Node Selection Function. It is aware whenever a new RR connection is established. In particular, the BSC always examines the content of the Initial Layer 3 message sent by the MS in order to determine the position of the MS Classmark and to extract its contents. The examination of the Initial Layer 3 message content allows the BSC to observe the TMSI+LAI or IMSI or IMEI. + +The BSC derives from Initial Layer 3 messages the NRI from the TMSI. It is configured in the BSC (O&M) which bits of the TMSI are significant for the NRI. The BSC routes the Initial Layer 3 message according to the NRI to the relevant MSC if an MSC address is configured in the BSC for the specific NRI. The association between NRI values and MSC addresses is configured in the BSC (O&M). + +If no MSC address is configured in the BSC for the requested NRI, or if no TMSI is sent by the MS (e.g. an IMSI or IMEI), then the BSC routes the initial NAS signalling message to an MSC selected from the available MSCs. In addition, the BSC may route the initial NAS signalling message to an MSC selected from the available MSCs if this message is a Location Update Request messages and the PLMN ID in the LAI is not one of the PLMN IDs served by the BSC (FFS). The selection mechanism is implementation dependent and should enable load balancing between the available MSCs. In some networks, the BSC may be configured to select the MSC/VLR for "MSs configured for low access priority" with a different load balance to that used for MSC/VLR selection for other MSs. + +NOTE: The BSC can determine whether or not the "MS is configured for low access priority" from information contained in the Initial Layer 3 message. Using a different load balance for "MSs configured for low access priority" might be useful if some MSCs have a particularly large VLR capacity compared to their relative processing power. + +In case a MSC sends a paging-request with IMSI, the NAS node selection function in the BSC shall upon reception temporarily store the MSC/VLR-identity of the node that issued the paging-request message. + +### 5.3.2 Gb mode + +The BSC provides the NAS Node Selection Function. The MS sends the TLLI to the BSC. The NRI is part of the P-TMSI and therefore also contained in the 'local TLLI' or in the 'foreign TLLI'. The number of bits out of the TLLI which are significant for the NRI is configured in the BSC (O&M). + +A 'local TLLI' indicates to the BSC that the TLLI is derived from a P-TMSI which was assigned for the current RA, i.e. the 'local TLLI' contains an NRI which is valid for routing to an SGSN. A 'foreign TLLI' indicates to the BSC that the TLLI is derived from a P-TMSI which was assigned for another RA than the current RA. The BSC does not know whether the other RA and therefore the related P-TMSI belongs to the same pool-area or not unless this is configured in the BSC (which is not intended). Consequently, the BSC assumes, that the 'foreign TLLI' contains a NRI which is valid for routing to an SGSN. + +For 'local TLLIs' and for 'foreign TLLIs' the BSC masks the NRI out of the TLLI. The BSC routes the uplink LLC frame to the relevant SGSN if an SGSN address is configured in the BSC for the specific NRI. The association between NRI values and SGSN addresses is configured in the BSC (O&M). + +If no SGSN address is configured in the BSC for the requested NRI, which may happen for NRIs masked out of a 'foreign TLLI', or if the BSC received a 'random TLLI' which contains no NRI at all then the RNC routes the uplink LLC frame to an SGSN selected from the available SGSNs. The selection mechanism is implementation dependent and should enable load balancing between the available SGSNs. In some networks, the BSC may be configured to select the SGSN for "MSs configured for low access priority" with a different load balance to that used for SGSN selection for other MSs. In this case, until TLLI re-allocation occurs, the BSC shall remember which TLLIs are from "MSs configured for low access priority" and which are not. + +NOTE 1: For the selection mechanism in the BSC it is probably sufficient, that the algorithm is 'slow moving'. If the selection algorithm changes the SGSN to be assigned for 'random TLLIs' or for 'foreign TLLIs' whose NRI value is not used in the current SGSN pool area during a MS's Attach procedure or RA update procedure, then the Attach procedure or RA update procedure is likely to fail, but the MS will reattempt the procedure at T3310/T3330 expiry (=15 seconds). + +NOTE 2: The BSC can determine whether or not the "MS is configured for low access priority" from information contained in the RR Channel Request message. + +NOTE 3: When performing special SGSN selection for "MSs configured for low access priority", it is necessary to ensure that all the Mobility Management signalling for that MS is routed to that special SGSN and not routed to any other SGSN. Hence the requirement for the BSC to remember the "TLLI to SGSN" relationship until the new SGSN has reallocated the TLLI. + +As more than one SGSN may send downlink data at the same time for a cell or a BVCI, the BSC has to share the total possible downlink traffic between the SGSNs that can access a cell. The BSC should use the existing flow control procedure on cell level to control each of the SGSNs in a way not to violate the total possible traffic for the cell. How the BSC decides to share the downlink traffic between each of the SGSNs is an implementation specific issue; e.g. the possible downlink traffic can be equally shared between the SGSNs, or the share of each SGSN can be proportional to the capacity of the SGSN. In case a MSC sends a paging-request with IMSI via Gs-interface the SGSN has to add the MSC/VLR-identity to the paging-request message. The NAS node selection function in the BSC/RNC shall upon reception temporarily store the MSC/VLR-identity. + +### 5.3.3 Iu mode + +To support MSs in Iu mode the BSC provides the same functionality as described under "RNC Functions". + +### 5.3.4 Load Re-Distribution function in BSC + +When the BSC receives a message with a 'null-NRI' it uses the NAS Node Selection Function for selecting a CN node where to forward the message. This is also done for all messages with 'random TLLIs' (Gb-mode). CN node(s) with re-distribution in progress should be excluded from the NAS Node Selection algorithm in the BSC. This is done by O&M configuration in the BSC. + +## 5.4 MSC Functions + +### 5.4.1 TMSI Allocation + +Every MSC is configured with its one or more specific NRI (O&M). One of these specific NRIs is part of every temporary identity (TMSI) which the MSC assigns to an MS. The TMSI allocation mechanism in the MSC generates TMSIs which contain one of the specific NRIs in the relevant bit positions. An NRI has a flexible length between 10 and 0 bits (0 bits means the NRI is not used and the feature is not applied). The use of the bits not used to encode the NRI is implementation dependent (e.g. to extent the TMSI space). An MSC applying "Intra Domain Connection of RAN nodes to multiple CN nodes" shall allocate TMSIs to the served MSs. + +### 5.4.2 Mobility Management and Handover/Relocation + +For MAP signalling between two MSCs which both support the Intra Domain Connection of RAN Nodes to Multiple CN Nodes the new MSC derives the address of the old MSC from the old LAI and the NRI contained in the old TMSI. The MSC addresses for each LAI and NRI combination are configured in the MSC (O&M). If the network contains MSCs that cannot derive the old MSC from LAI and NRI the default MSC per LAI as described below shall be used (e.g. to reduce the configuration effort). Some redundancy may be required as the default MSC is a single point of failure. + +The load balancing between multiple target MSCs at handover/relocation into a pool area is described in "4.5 Load Balancing". The handover/relocation from an MSC that supports the Intra Domain Connection of RAN Nodes to Multiple CN Nodes to an MSC not supporting the feature needs no new functionality, as there is only one MSC that serves the handover/relocation target. + +### 5.4.3 Backward Compatibility and Default MSC + +If a default MSC that is serving a pool-area receives MAP signalling (e.g. to fetch the IMSI or to get unused cipher parameters) it has to resolve the ambiguity of the multiple MSCs per LAI by deriving the NRI from the TMSI. The MSC relays the MAP signalling to the old MSC identified by the NRI in the old TMSI unless the default MSC itself is the old MSC. For every NRI value that is used in the pool-area an MSC address is configured in the default MSC (O&M). + +NOTE: It might be required to keep information on ongoing MAP dialogues in the default MSC. + +### 5.4.4 Support of Combined Procedures + +If the SGSN does not support the Intra Domain Connection of RAN Nodes to Multiple CN Nodes then only one default out of the MSCs serving the related LA can be used for the combined procedures. A relaying or diverting from the default MSC to another is FFS. Distributing the associations of the combined procedures according to the LAs would result in MSC changes when the MS is still in the old MSC service area. + +### 5.4.5 Load Re-Distribution function in MSC + +The MSC needs to ensure that the RR-connection is released immediately after the Location Update response message is returned to the UE, i.e. the follow-on proceed flag shall be cleared. + +For the special case when an MSC in a pool also serves a BSC or RNC that is not part of the pool (e.g. a BSC or RNC that does not support pool functionality), an MSC should not try to re-distribute UEs connected to that BSC or RNC. + +## 5.5 SGSN Functions + +### 5.5.1 P-TMSI Allocation + +Every SGSN is configured with its specific one or more NRI (O&M). One of these specific NRIs is part of every temporary identity (P-TMSI) which the SGSN assigns to an MS. The P-TMSI allocation mechanism in the SGSN generates P-TMSIs which contain one of the specific NRIs in the relevant bit positions. An NRI has a flexible length between 10 and 0 bits (0 bits means the NRI is not used and the feature is not applied). The use of the bits not used to encode the NRI is implementation dependent (e.g. to extent the TMSI space). An SGSN applying “Intra Domain Connection of RAN nodes to multiple CN nodes” shall allocate P-TMSIs to the served MSs. + +### 5.5.2 Mobility Management and Handover/Relocation + +For the GTP signalling between two SGSNs supporting the Intra Domain Connection of RAN Nodes to Multiple CN Nodes the new SGSN derives the address of the old SGSN from the old RAI and the NRI contained in the old P-TMSI/TLTI. The SGSN addresses are configured in the SGSN (O&M) or in DNS for each RAI and NRI combination. If the network contains SGSNs that cannot derive the old SGSN from RAI and NRI the default SGSN per RAI as described below shall be used (e.g. to reduce the configuration effort). + +The load balancing between multiple target SGSNs at handover/relocation into a pool area is described in "4.5: Load Balancing". The handover/relocation from an SGSN that supports the Intra Domain Connection of RAN Nodes to Multiple CN Nodes to an SGSN not supporting the feature needs no new functionality, as there is only one SGSN that serves the handover/relocation target. + +### 5.5.3 Backward Compatibility and Default SGSN + +If a default SGSN that is serving a pool-area receives GTP signalling (e.g. to fetch the IMSI or to get unused cipher parameters) it has to resolve the ambiguity of the multiple SGSNs per RAI by deriving the NRI from the P-TMSI. The SGSN relays the GTP signalling to the old SGSN identified by the NRI in the old P-TMSI unless the default SGSN itself is the old SGSN. For every NRI value that is used in the pool-area an SGSN address is configured in the relaying SGSN (O&M) or in DNS. + +NOTE: It might be required to keep information on ongoing GTP dialogues in the default SGSN. + +### 5.5.4 Support of Combined Procedures + +The SGSN has to select an MSC at the Gs interface for the combined procedures if multiple MSCs are configured for the relevant LAI. The MSC out of the available MSCs is selected based on the TMSI based NRI as provided by the UE or on the IMSI, and optionally, whether the "MS is configured for low access priority". Use of the TMSI based NRI as provided by the UE prevents an MSC change for UEs when UEs register first via normal procedures, and later by combined procedures. Use of the TMSI based NRI as provided by the UE or IMSI hash prevents an MSC change for many MSs if an SGSN fails and the re-attaching MSs would get assigned another MSC by the new SGSN. Two HLR updates instead of one would be the result. + +From the LAI and the TMSI based NRI as provided by the UE, the SGSN can select a VLR from the available VLRs. The NRI length and the selected VLR per NRI value shall be the same as for the CN Node selection for the CS Domain in the RNC and BSC nodes. + +From the IMSI the SGSN derives a value (V) using algorithm [(IMSI div 10) modulo 1000]. Every value (V) from the range 0 to 999 corresponds to a single MSC node. Typically many values of (V) may point to the same MSC node. The configuration of the MSC node should be the same in the same RNC area. + +In some networks, the SGSN may be configured to select the MSC/VLR for "MSs configured for low access priority" with a different load balance to that used for MSC/VLR selection for other UEs. In this case the SGSN maintains a second set of tables of NRI to MSC mappings, and of value (V) to MSC mappings. + +### 5.5.5 CS Paging + +If a CS paging is received via the Gs interface from MSC with mobile identity type IMSI then the SGSN should include the MSC/VLR-id in the paging / paging-request message to RNC/BSC. + +### 5.5.6 Load Re-Distribution function in SGSN + +On the Iu-ps interface the SGSN needs to ensure that the Iu-connection is released immediately after the Routing Area Update response message is returned to the UE, i.e. the follow-on flag shall be cleared. + +On the Gb interface the SGSN needs to force the UE to standby after the Routing Area Update response message is returned to the UE, i.e. the force to standby indication shall be set. This ensures the Periodic Routing Area Update timer to start as quickly as possible. + +For the special case when an SGSN in a pool also serves a BSC or RNC that is not part of the pool (e.g. a BSC or RNC that does not support pool functionality), an SGSN should not try to re-distribute UEs connected to that BSC or RNC. + +# 6 Application Examples + +This clause describes some application examples for networks using the intra domain NAS node selection. In these examples, pool-areas are depicted by boxes or ellipses, while the core network elements which serve the pool-areas are depicted by the NRIs they have been assigned. + +## 6.1 Network configuration example 1 + +This example configures 9 pool-areas each with 3 CN nodes serving within a pool-area. When a MS moves from one (NRI:1,2,3) to another pool-area (NRI:4,5,6). It indicates the old NRI (3) derived from its old TMSI to the RNC in the new pool-area (NRI:4,5,6). This NRI 3 is not configured in the RNC of the pool-area (NRI:4,5,6). The RNC selects a CN node out of the available NRIs 4,5,6 and establishes the signalling connection for the MS with the selected CN node. This new CN node allocates a new TMSI to the MS and thereby the new NRI for the new pool-area. + +In this example, the NRIs can be re-used in a pattern where adjacent pool areas do not use the same NRI. Every pool area change will initiate a new selection of a new CN node. + +| | | | +|--------------------|--------------------|--------------------| +| NRI:<br>19, 20, 21 | NRI:<br>22, 23, 24 | NRI:<br>25, 26, 27 | +| NRI:<br>16, 17, 18 | NRI:<br>1, 2, 3 | NRI:<br>4, 5, 6 | +| NRI:<br>13, 14, 15 | NRI:<br>10, 11, 12 | NRI:<br>7, 8, 9 | + +Figure 2: Network configuration example 1 + +## 6.2 Network configuration example 2 + +This example shows a network covering one city centre surrounded by residential areas. The city centre is covered by all 4 pool-areas while each of the residential areas is covered by one pool-area only. Once a MS „found" its pool-area, it will not change the pool-area while commuting between the city centre and its residential area. Each of the pool-areas is served by 5 MSCs, indicated by the 5 NRI values in the figure below, which share the load within the pool-area. Only distinct NRI values are used for the overlapping pool-areas. Therefore, a MS changing between these pool-areas will always be allocated to a new MSC by the NAS node selection function. In addition it is shown, that the NRIs can be re-used in other pool-areas as indicated in the figure by the smaller areas with only one NRI. Also at a change to these areas the MSs will always be allocated to a new MSC by the NAS node selection function as adjacent areas do not use the same NRI values. + +A calculation for the possible number of subscribers in this scenario is in Annex A.1: One city centre surrounded by residential areas + +![Diagram of network configuration example 3 showing overlapping pool areas and their NRI values.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +The diagram illustrates a network configuration with a central 'city centre' area surrounded by several pool areas. The pool areas are represented by overlapping circles, and the 'city centre' is a small circle in the center. The NRI values for each pool area are as follows: + +- Top pool area: NRI: 16,17,18,19,20 +- Left pool area: NRI: 1,2,3,4,5 +- Right pool area: NRI: 11,12,13,14,15 +- Bottom pool area: NRI: 6,7,8,9,10 +- Top-left small pool area: Reuse NRI: 11 +- Bottom-right small pool area: Reuse NRI: 1 + +The 'city centre' circle is located at the intersection of the four main pool areas (top, left, right, and bottom). + +Diagram of network configuration example 3 showing overlapping pool areas and their NRI values. + +Figure 3: Network configuration example 3 + +# 7 Specific Examples + +This chapter describes specific examples of Iu Flex. First, building blocks of Iu Flex are described in 7.1. These building blocks are then used in signalling flows starting from 7.2. + +The changes to the signalling flows are indicated in *italic*. + +## 7.1 Building blocks for signalling flows + +### 7.1.1 RAN node selecting CN node in A interface mode + +### 7.1.2 RAN node selecting CN node in Gb interface mode + +### 7.1.3 RAN node selecting CN node in Iu interface mode + +### 7.1.4 New CN node selecting old CN node + +This building block describes how a new CN node selects the old CN node which was previously serving the MS. The new CN node has been allocated to serve the MS, and it may have to communicate with the old CN node e.g. in order to get IMSI of the MS or to get MM and PDP contexts of the MS. + +### 7.1.5 Old CN node selecting new CN node + +This building block describes how the old CN node selects a new CN node which starts to serve the MS. The old CN node has to select a new CN node e.g. when performing handover. + +### 7.1.6 SGSN selecting MSC + +## 7.2 Signalling flow for Attach (Iu interface mode) + +At attach, the RNC selects an SGSN to serve the MS. The attach procedure is shown in the figure below. + +![Sequence diagram showing the signalling flow for Attach (Iu interface mode) between MS, UTRAN, new SGSN, old SGSN, GGSN, EIR, new MSC/VLR, HLR, and old MSC/VLR.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant MS + participant UTRAN + participant new_SGSN as new SGSN + participant old_SGSN as old SGSN + participant GGSN + participant EIR + participant new_MSC_VLR as new MSC/VLR + participant HLR + participant old_MSC_VLR as old MSC/VLR + + Note left of MS: INITIAL_DT + MS->>UTRAN: 1. Attach Request + Note right of UTRAN: RANAP-INITIAL_UE + UTRAN->>new_SGSN: 1. Attach Request + new_SGSN->>old_SGSN: 2. Identification Request + old_SGSN-->>new_SGSN: 2. Identification Response + new_SGSN->>MS: 3. Identity Request + MS-->>new_SGSN: 3. Identity Response + new_SGSN->>MS: 4. Authentication + MS-->>new_SGSN: 4. Authentication + new_SGSN->>EIR: 5. IMEI Check + EIR-->>new_SGSN: 5. IMEI Check + new_SGSN->>HLR: 6a. Update Location + HLR-->>old_SGSN: 6b. Cancel Location + old_SGSN-->>HLR: 6c. Cancel Location Ack + HLR-->>new_SGSN: 6d. Insert Subscriber Data + new_SGSN-->>HLR: 6e. Insert Subscriber Data Ack + HLR-->>new_SGSN: 6f. Update Location Ack + new_SGSN->>new_MSC_VLR: 7a. Location Update Request + new_MSC_VLR->>HLR: 7b. Update Location + HLR-->>old_MSC_VLR: 7c. Cancel Location + old_MSC_VLR-->>HLR: 7d. Cancel Location Ack + HLR-->>new_MSC_VLR: 7e. Insert Subscriber Data + new_MSC_VLR-->>HLR: 7f. Insert Subscriber Data Ack + HLR-->>new_MSC_VLR: 7g. Update Location Ack + new_MSC_VLR-->>new_SGSN: 7h. Location Update Accept + Note right of new_SGSN: C1 + new_SGSN->>MS: 8. Attach Accept + MS-->>UTRAN: 9. Attach Complete + UTRAN->>new_SGSN: 9. Attach Complete + new_SGSN->>new_MSC_VLR: 10. TMSI Reallocation Complete + +``` + +Sequence diagram showing the signalling flow for Attach (Iu interface mode) between MS, UTRAN, new SGSN, old SGSN, GGSN, EIR, new MSC/VLR, HLR, and old MSC/VLR. + +**Figure 4: Signalling flow for Attach (Iu interface mode)** + +- 1) The Attach Request (old P-TMSI, old RAI, old P-TMSI Signature) is carried in the Initial Direct Transfer message (RRC) from the MS to the RNC. The RNC selects an SGSN to serve the MS as described in clause 7.1.3 and relays the Attach Request to the SGSN in the Initial UE message (RANAP). +- 2) If the MS identifies itself with P-TMSI and the SGSN has changed since detach, the new SGSN sends an Identification Request (P-TMSI, old RAI, old P-TMSI Signature) to the old SGSN to request the IMSI. The new SGSN selects the old SGSN as described in clause 7.1.4. The old SGSN responds with Identification Response (IMSI, Authentication Triplets (for GPRS) or Authentication Vectors (for UMTS)). If the MS is not known in the old SGSN, the old SGSN responds with an appropriate error cause. The old SGSN also validates the old P-TMSI Signature and responds with an appropriate error cause if it does not match the value stored in the old SGSN. + +- 3) If the MS is unknown in both the old and new SGSN, the SGSN sends an Identity Request (Identity Type = IMSI) to the MS. The MS responds with Identity Response (IMSI). +- 4) The authentication functions are defined in the clause "Security Function" of TS 23.060 [2]. If no MM context for the MS exists anywhere in the network, then authentication is mandatory. Ciphering procedures are described in clause "Security Function" of TS 23.060 [2]. If P-TMSI allocation is going to be done and the network supports ciphering, the network shall set the ciphering mode. +- 5) The equipment checking functions are defined in the clause "Identity Check Procedures" of TS 23.060 [2]. Equipment checking is optional. +- 6) If the SGSN number has changed since the GPRS detach, or if it is the very first attach, then the SGSN informs the HLR: + - a) The SGSN sends an Update Location (SGSN Number, SGSN Address, IMSI) to the HLR. + - b) The HLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. + - c) The old SGSN acknowledges with Cancel Location Ack (IMSI). If there are any ongoing procedures for that MS, the old SGSN shall wait until these procedures are finished before removing the MM and PDP contexts. + - d) The HLR sends Insert Subscriber Data (IMSI, GPRS Subscription Data) to the new SGSN. + - e) The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to attach in the RA, the SGSN rejects the Attach Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the HLR. If subscription checking fails for other reasons, the SGSN rejects the Attach Request with an appropriate cause and returns an Insert Subscriber Data Ack (IMSI, Cause) message to the HLR. If all checks are successful then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the HLR. + - f) The HLR acknowledges the Update Location message by sending an Update Location Ack to the SGSN after the cancelling of old MM context and insertion of new MM context are finished. If the Update Location is rejected by the HLR, the SGSN rejects the Attach Request from the MS with an appropriate cause. +- 7) If Attach Type in step 1 indicated GPRS Attach while already IMSI attached, or combined GPRS / IMSI attached, then the VLR shall be updated if the Gs interface is installed. The VLR number is determined as described in 7.1.6. The SGSN starts the location update procedure towards the new MSC/VLR upon receipt of the first Insert Subscriber Data message from the HLR in step 6d). This operation marks the MS as GPRS-attached in the VLR. + - a) The SGSN sends a Location Update Request (new LAI, IMSI, SGSN Number, Location Update Type) message to the VLR. Location Update Type shall indicate IMSI attach if Attach Type indicated combined GPRS / IMSI attach. Otherwise, Location Update Type shall indicate normal location update. The VLR creates an association with the SGSN by storing SGSN Number. + - b) If the LA update is inter-MSC, the new VLR sends Update Location (IMSI, new VLR) to the HLR. + - c) If the LA update is inter-MSC, the HLR sends a Cancel Location (IMSI) to the old VLR. + - d) The old VLR acknowledges with Cancel Location Ack (IMSI). + - e) If the LA update is inter-MSC, the HLR sends Insert Subscriber Data (IMSI, GSM subscriber data) to the new VLR. + - f) The VLR acknowledges with Insert Subscriber Data Ack (IMSI). + - g) After finishing the inter-MSC location update procedures, the HLR responds with Update Location Ack (IMSI) to the new VLR. + - h) The VLR responds with Location Update Accept (VLR TMSI) to the SGSN. An Iu Flex aware VLR includes one of its (CS-)NRIs as part of VLR TMSI. The SGSN creates an association with the VLR by storing VLR number. + +- 8) The SGSN selects Radio Priority SMS, and sends an Attach Accept (P-TMSI, VLR TMSI, P-TMSI Signature, Radio Priority SMS) message to the MS. P-TMSI is included if the SGSN allocates a new P-TMSI. An Iu Flex aware SGSN includes one of its (PS-)NRIs as part of P-TMSI. +- 9) If P-TMSI or VLR TMSI was changed, the MS acknowledges the received TMSI(s) by returning an Attach Complete message to the SGSN. +- 10) If VLR TMSI was changed, the SGSN confirms the VLR TMSI re-allocation by sending a TMSI Reallocation Complete message to the VLR. + +## 7.3 Signalling flows for Service Request (Iu interface mode) + +When performing service request, the signalling connection between the MS and the SGSN is re-established. + +### 7.3.1 Service Request initiated by MS + +The service request procedure initiated by the MS is shown in the figure below. + +![Sequence diagram showing signalling flows for Service Request initiated by MS (Iu interface mode). The diagram involves five entities: MS, RNC, SGSN, HLR, and GGSN. The sequence of messages is: 1. MS to RNC: RRC Connection Request; 2. RNC to MS: RRC Connection Setup; 3. MS to RNC: Initial_DT; 4. RNC to SGSN: RANAP INITIAL_UE; 5. RNC to SGSN: Service Request; 6. SGSN to RNC: Security Functions; 7. RNC to HLR: Security Functions; 8. HLR to SGSN: Security Functions; 9. SGSN to RNC: Radio Access Bearer Assignment Request; 10. RNC to MS: Radio Bearer Setup; 11. MS to RNC: Radio Bearer Setup Complete; 12. RNC to SGSN: Radio Access Bearer Assignment Response; 13. SGSN to GGSN: SGSN-Initiated PDP Context Modification; 14. GGSN to SGSN: SGSN-Initiated PDP Context Modification; 15. SGSN to MS: Uplink PDU.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +``` + +sequenceDiagram + participant MS + participant RNC + participant SGSN + participant HLR + participant GGSN + + Note left of MS: 1. RRC Connection Request + MS->>RNC: 1. RRC Connection Request + Note right of RNC: 1. RRC Connection Setup + RNC-->>MS: 1. RRC Connection Setup + Note left of MS: Initial_DT + MS-->>RNC: Initial_DT + Note right of RNC: RANAP INITIAL_UE + RNC-->>SGSN: RANAP INITIAL_UE + Note left of RNC: 2. Service Request + RNC->>SGSN: 2. Service Request + Note left of SGSN: 3. Security Functions + SGSN-->>RNC: 3. Security Functions + Note right of RNC: 3. Security Functions + RNC-->>HLR: 3. Security Functions + Note left of HLR: 3. Security Functions + HLR-->>SGSN: 3. Security Functions + Note left of SGSN: 4. Radio Access Bearer Assignment Request + SGSN-->>RNC: 4. Radio Access Bearer Assignment Request + Note left of RNC: 5. Radio Bearer Setup + RNC-->>MS: 5. Radio Bearer Setup + Note left of MS: 6. Radio Bearer Setup Complete + MS-->>RNC: 6. Radio Bearer Setup Complete + Note right of RNC: 6. Radio Access Bearer Assignment Response + RNC-->>SGSN: 6. Radio Access Bearer Assignment Response + Note left of SGSN: 7. SGSN-Initiated PDP Context Modification + SGSN-->>GGSN: 7. SGSN-Initiated PDP Context Modification + Note left of GGSN: 7. SGSN-Initiated PDP Context Modification + GGSN-->>SGSN: 7. SGSN-Initiated PDP Context Modification + Note left of SGSN: 8. Uplink PDU + SGSN-->>MS: 8. Uplink PDU + +``` + +Sequence diagram showing signalling flows for Service Request initiated by MS (Iu interface mode). The diagram involves five entities: MS, RNC, SGSN, HLR, and GGSN. The sequence of messages is: 1. MS to RNC: RRC Connection Request; 2. RNC to MS: RRC Connection Setup; 3. MS to RNC: Initial\_DT; 4. RNC to SGSN: RANAP INITIAL\_UE; 5. RNC to SGSN: Service Request; 6. SGSN to RNC: Security Functions; 7. RNC to HLR: Security Functions; 8. HLR to SGSN: Security Functions; 9. SGSN to RNC: Radio Access Bearer Assignment Request; 10. RNC to MS: Radio Bearer Setup; 11. MS to RNC: Radio Bearer Setup Complete; 12. RNC to SGSN: Radio Access Bearer Assignment Response; 13. SGSN to GGSN: SGSN-Initiated PDP Context Modification; 14. GGSN to SGSN: SGSN-Initiated PDP Context Modification; 15. SGSN to MS: Uplink PDU. + +**Figure 5: Signalling flows for Service Request initiated by MS (Iu interface mode)** + +- 1) The MS establishes an RRC connection, if none exists for CS traffic. +- 2) The MS sends a Service Request (P-TMSI, RAI, CKSN, Service Type) message to the SGSN. Service Type specifies the requested service. Service Type shall indicate one of the following: Data or Signalling. The Service Request is carried in the Initial Direct Transfer message (RRC) from the MS to the RNC. The RNC selects an SGSN to serve the MS as described in 7.1.3 and relays the Service Request to the SGSN in the Initial UE message (RANAP). At this point, the SGSN may perform the authentication procedure. + - If Service Type indicates Data, a signalling connection is established between the MS and the SGSN, and resources for active PDP context(s) are allocated, i.e., RAB establishment for the activated PDP context(s). + - If Service Type indicates Signalling, the signalling connection is established between the MS and the SGSN for sending upper-layer signalling messages, e.g., Activate PDP Context Request. The resources for active PDP context(s) are not allocated. +- 3) The SGSN shall perform the security functions if the MS in PMM-IDLE state initiated the service request. +- 4) If the network is in PMM-CONNECTED state and the Service Type indicates Data, the SGSN shall respond with a Service Accept message towards the MS, in case the service request can be accepted. In case Service Type indicates Data, the SGSN sends a Radio Access Bearer Assignment Request (NSAPIRAB ID(s), TEID(s), + +QoS Profile(s), SGSN IP Address(es)) message to re-establish radio access bearer for every activated PDP context. + +- 5) The RNC indicates to the MS the new Radio Bearer Identity established and the corresponding RAB ID with the RRC radio bearer setup procedure. +- 6) SRNC responds with the Radio Access Bearer Assignment Response (RAB ID(s), TEID(s), QoS Profile(s), RNC IP Address(es)) message. The GTP tunnel(s) are established on the Iu interface. If the RNC returns a Radio Access Bearer Assignment Response message with a cause indicating that the requested QoS profile(s) can not be provided, e.g., "Requested Maximum Bit Rate not Available", the SGSN may send a new Radio Access Bearer Assignment Request message with different QoS profile(s). The number of re-attempts, if any, as well as how the new QoS profile(s) values are determined is implementation dependent. +- 7) For each RAB re-established with a modified QoS profile, the SGSN initiates a PDP Context Modification procedure to inform the MS and the GGSN of the new negotiated QoS profile for the corresponding PDP context. +- 8) The MS sends the uplink packet. + +### 7.3.2 Service Request initiated by network + +The service request procedure initiated by the network is shown in the figure below. + +![Sequence diagram showing signalling flows for Service Request initiated by network (Iu interface mode). The diagram involves five entities: MS, RNC, SGSN, HLR, and GGSN. The sequence starts with a Downlink PDU from GGSN to SGSN, followed by Paging from SGSN to RNC and then to MS. The MS sends an RRC Connection Request to RNC, which responds with RRC Connection Setup. The RNC then sends an INITIAL_UE message to SGSN, followed by a Service Request. The SGSN initiates Security Functions, which involve the HLR. The SGSN then sends a Radio Access Bearer Assignment Request to the RNC, which responds with a Radio Bearer Setup message to the MS. The MS completes the setup and sends a response to the RNC, which in turn sends a Radio Access Bearer Assignment Response to the SGSN. Finally, the SGSN initiates a PDP Context Modification Procedure with the GGSN, and a Downlink PDU is sent from the SGSN to the MS.](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +``` + +sequenceDiagram + participant MS + participant RNC + participant SGSN + participant HLR + participant GGSN + + Note left of GGSN: 1. Downlink PDU + GGSN->>SGSN: + Note right of SGSN: 2. Paging + SGSN->>RNC: + Note left of RNC: 2. Paging + RNC->>MS: + Note left of MS: 3. RRC Connection Request + MS-->>RNC: + Note right of RNC: 3. RRC Connection Setup + RNC-->>MS: + Note left of MS: Initial_UE + MS-->>RNC: + Note right of RNC: 4. Service Request + RNC->>SGSN: + Note left of SGSN: 5. Security Functions + SGSN-->>HLR: + Note right of HLR: 6. Radio Access Bearer Assignment Request + HLR-->>SGSN: + Note left of SGSN: 6. Radio Bearer Setup + SGSN->>RNC: + Note left of RNC: 6. Radio Bearer Setup Complete + RNC-->>MS: + Note right of MS: 6. Radio Access Bearer Assignment Response + MS-->>RNC: + Note right of RNC: 7. SGSN-Initiated PDP Context Modification Procedure + RNC->>SGSN: + Note left of SGSN: 8. Downlink PDU + SGSN->>MS: + +``` + +Sequence diagram showing signalling flows for Service Request initiated by network (Iu interface mode). The diagram involves five entities: MS, RNC, SGSN, HLR, and GGSN. The sequence starts with a Downlink PDU from GGSN to SGSN, followed by Paging from SGSN to RNC and then to MS. The MS sends an RRC Connection Request to RNC, which responds with RRC Connection Setup. The RNC then sends an INITIAL\_UE message to SGSN, followed by a Service Request. The SGSN initiates Security Functions, which involve the HLR. The SGSN then sends a Radio Access Bearer Assignment Request to the RNC, which responds with a Radio Bearer Setup message to the MS. The MS completes the setup and sends a response to the RNC, which in turn sends a Radio Access Bearer Assignment Response to the SGSN. Finally, the SGSN initiates a PDP Context Modification Procedure with the GGSN, and a Downlink PDU is sent from the SGSN to the MS. + +**Figure 6: Signalling flows for Service Request initiated by network (Iu interface mode)** + +- 1) The SGSN receives a downlink PDP PDU for an MS in PMM-IDLE state. +- 2) The SGSN sends a Paging message to the RNC. The RNC pages the MS by sending a Paging message to the MS. See clause "PS Paging Initiated by 3G-SGSN without RRC Connection for CS" of TS 23.060 [2] for details. +- 3) The MS establishes an RRC connection if none exists for CS traffic. + +- 4) The MS sends a Service Request (P-TMSI, RAI, CKSN, Service Type) message to the SGSN. Service Type specifies Paging Response. The Service Request is carried over the radio in an RRC Direct Transfer message. The RNC selects an SGSN to serve the MS as described in 7.1.3 and relays the Service Request to the SGSN in the Initial UE message (RANAP). At this point, the SGSN may perform the authentication procedure. The SGSN knows whether the downlink packet requires RAB establishment (e.g., downlink PDU) or not (e.g., Request PDP Context Activation or MT SMS). +- 5) The SGSN shall perform the security mode procedure. +- 6) If resources for the PDP contexts are re-established, the SGSN sends a Radio Access Bearer Assignment Request (RAB ID(s), TEID(s), QoS Profile(s), SGSN IP Address(es)) message to the RNC. The RNC sends a Radio Bearer Setup (RAB ID(s)) to the MS. The MS responds by returning a Radio Bearer Setup Complete message to the RNC. The RNC sends a Radio Access Bearer Assignment Response (RAB ID(s), TEID(s), RNC IP Address(es)) message to the SGSN in order to indicate that GTP tunnels are established on the Iu interface and radio access bearers are established between the RNC and the MS. If the RNC returns a Radio Access Bearer Assignment Response message with a cause indicating that the requested QoS profile(s) can not be provided, e.g., "Requested Maximum Bit Rate not Available", the SGSN may send a new Radio Access Bearer Assignment Request message with different QoS profile(s). The number of re-attempts, if any, as well as how the new QoS profile(s) values are determined is implementation dependent. +- 7) For each RAB re-established with a modified QoS profile, the SGSN initiates a PDP Context Modification procedure to inform the MS and the GGSN of the new negotiated QoS profile for the corresponding PDP context. +- 8) The SGSN sends the downlink packet. + +## 7.4 Signalling flow for Routing Area Update (Iu interface mode) + +The routing area update procedure is shown in the figure below. + +![Sequence diagram showing the signalling flow for a Routing Area Update (Iu interface mode).](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +The sequence diagram illustrates the signalling flow for a Routing Area Update (Iu interface mode) involving the following entities: MS, UTRAN, new 3G-SGSN, old 3G-SGSN, GGSN, new MSC/VLR, HLR, and old MSC/VLR. + +The process begins with the MS sending an *INITIAL- DT RANAP- INITIAL\_UE* message to the UTRAN. The UTRAN then sends a **1. Routeing Area Update Request** to the new 3G-SGSN. The new 3G-SGSN sends a **2. SGSN Context Request** to the old 3G-SGSN. The old 3G-SGSN responds with **2a. SRNS Context Request** to the new 3G-SGSN, which in turn sends a **2a. SRNS Context Response** back to the old 3G-SGSN. The old 3G-SGSN then sends a **2. SGSN Context Response** to the new 3G-SGSN. The new 3G-SGSN performs **3. Security Functions** with the MS. The new 3G-SGSN sends a **4. SGSN Context Ack** to the old 3G-SGSN. The old 3G-SGSN sends a **5. Update PDP Context Request** to the GGSN, which responds with a **5. Update PDP Context Response**. The new 3G-SGSN sends a **6. Update Location** message to the HLR. The HLR sends a **7. Cancel Location** message to the old 3G-SGSN. The old 3G-SGSN sends a **7a. Iu Release Command** to the UTRAN, which responds with a **7a. Iu Release Complete**. The old 3G-SGSN sends a **7. Cancel Location Ack** to the HLR. The new 3G-SGSN sends an **8. Insert Subscriber Data** message to the HLR, which responds with an **8. Insert Subscriber Data Ack**. The new 3G-SGSN sends a **9. Update Location Ack** to the HLR. The HLR sends a **10. Location Update Request** to the new MSC/VLR. The new MSC/VLR performs a series of actions: **11a. Update Location** to the HLR, **11b. Cancel Location** to the old MSC/VLR, **11c. Cancel Location Ack** from the old MSC/VLR, **11d. Insert Subscriber Data** to the HLR, **11e. Insert Subscriber Data Ack** from the HLR, and **11f. Update Location Ack** to the HLR. The new MSC/VLR sends a **12. Location Update Accept** message to the new 3G-SGSN. The new 3G-SGSN sends a **13. Routeing Area Update Accept** message to the MS. The new 3G-SGSN sends a **14. Routeing Area Update Complete** message to the UTRAN. Finally, the new 3G-SGSN sends a **15. TMSI Reallocation Complete** message to the new MSC/VLR. + +Sequence diagram showing the signalling flow for a Routing Area Update (Iu interface mode). + +Figure 7: Signalling flow for Routing Area Update (Iu interface mode) + +- 1) The RRC connection is established, if not already done. The Routeing Area Update Request (old P-TMSI, old RAI, old P-TMSI Signature) is carried in the Initial Direct Transfer message (RRC) from the MS to the RNC. The RNC selects an SGSN to serve the MS as described in 7.1.3 and relays the Routeing Area Update Request to the SGSN in the Initial UE message (RANAP). +- 2) If the RA update is an Inter-SGSN Routeing area update and if the MS was in PMM-IDLE state, the new SGSN sends an SGSN Context Request message (old P-TMSI, old RAI, old P-TMSI Signature) to the old SGSN to get the MM and PDP contexts for the MS. The new SGSN selects the old SGSN as described in 7.1.4. The old SGSN validates the old P-TMSI Signature and responds with an appropriate error cause if it does not match the value stored in the old SGSN. This should initiate the security functions in the new SGSN. If the security functions authenticate the MS correctly, the new SGSN shall send an SGSN Context Request (IMSI, old RAI, MS Validated) message to the old SGSN. MS Validated indicates that the new SGSN has authenticated the MS. If the old P-TMSI Signature was valid or if the new SGSN indicates that it has authenticated the MS, the old SGSN responds with SGSN Context Response (Cause, IMSI, MM Context, PDP contexts). If the MS is not known in the old SGSN, the old SGSN responds with an appropriate error cause. The old SGSN starts a timer. The new SGSN shall ignore the MS Network Capability contained in MM Context of SGSN Context Response only when it has previously received an MS Network Capability in the Routeing Area Request. + - a) If the MS is PMM-CONNECTED in the old 3G-SGSN, the old SGSN shall send an SRNS Context Request (IMSI) message to the old SRNS to retrieve the sequence numbers for the PDP context for inclusion in the SGSN Context Response message from the SRNS. Upon reception of this message, the SRNS buffers and stops sending downlink PDUs to the MS and returns an SRNS Context Response (IMSI, GTP-SNDs, GTP-SNUs, PDCP-SNUs) message. The SRNS shall include for each PDP context the next in-sequence GTP sequence number to be sent to the MS and the GTP sequence number of the next uplink PDU to be tunnelled to the GGSN. For each active PDP context using acknowledged mode, the SRNS also includes the uplink PDCP sequence number (PDCP-SNU). PDCP-SNU shall be the next in-sequence PDCP sequence number expected from the MS (per each active radio bearer). +- 3) Security functions may be executed. These procedures are defined in clause "Security Function" of TS 23.060 [2]. If the security functions do not authenticate the MS correctly, the routeing area update shall be rejected, and the new SGSN shall send a reject indication to the old SGSN. The old SGSN shall continue as if the SGSN Context Request was never received. +- 4) If the RA update is an Inter-SGSN Routeing area update, the new SGSN sends an SGSN Context Acknowledge message to the old SGSN. The old SGSN marks in its context that the MSC/VLR association and the information in the GGSNs and the HLR are invalid. This triggers the MSC/VLR, the GGSNs, and the HLR to be updated if the MS initiates a routeing area update procedure back to the old SGSN before completing the ongoing routeing area update procedure. +- 5) If the RA update is an Inter-SGSN RA Update and if the MS was in PMM-IDLE state, the new SGSN sends Update PDP Context Request (new SGSN Address, QoS Negotiated, Tunnel Endpoint Identifier) to the GGSNs concerned. The GGSNs update their PDP context fields and return an Update PDP Context Response (Tunnel Endpoint Identifier). Note: If the RA update is an Inter-SGSN routeing area update initiated by an MS in PMM-CONNECTED state, the Update PDP Context Request message is sent as described in clause "Serving RNS Relocation Procedures" of TS 23.060 [2]. +- 6) If the RA update is an Inter-SGSN RA Update, the new SGSN informs the HLR of the change of SGSN by sending Update Location (SGSN Number, SGSN Address, IMSI) to the HLR. +- 7) If the RA update is an inter-SGSN RA Update, the HLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. If the timer described in step 2 is not running, the old SGSN removes the MM context. Otherwise, the contexts are removed only when the timer expires. It also ensures that the MM context is kept in the old SGSN in case the MS initiates another inter SGSN routeing area update before completing the ongoing routeing area update to the new SGSN. The old SGSN acknowledges with Cancel Location Ack (IMSI). + - a) If the MS is PMM-CONNECTED in the old 3G-SGSN, the old 3G-SGSN sends an Iu Release Command message to the old SRNC. The SRNC responds with an Iu Release Complete message. +- 8) If the RA update is an inter-SGSN RA Update, the HLR sends Insert Subscriber Data (IMSI, subscription data) to the new SGSN. The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to be attached in the RA, the SGSN rejects the Routeing Area Update Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message + +to the HLR. If all checks are successful, the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the HLR. + +- 9) If the RA update is an Inter-SGSN RA Update, the HLR acknowledges the Update Location by sending Update Location Ack (IMSI) to the new SGSN. +- 10) If Update Type indicates combined RA / LA update with IMSI attach requested, or if the LA changed with the routing area update, the association has to be established. *The VLR number is determined as described in 7.1.6. The new SGSN sends a Location Update Request (new LAI, IMSI, SGSN Number, Location Update Type) to the VLR.* Location Update Type shall indicate IMSI attach if Update Type in step 1 indicated combined RA / LA update with ISI attach requested. Otherwise, Location Update Type shall indicate normal location update. The SGSN starts the location update procedure towards the new MSC/VLR upon receipt of the first Insert Subscriber Data message from the HLR in step 8). The VLR creates or updates the association with the SGSN by storing SGSN Number. +- 11) If the subscriber data in the VLR is marked as not confirmed by the HLR, the new VLR informs the HLR. The HLR cancels the old VLR and inserts subscriber data in the new VLR (this signalling is not modified from existing GSM signalling and is included here for illustrative purposes): + - a) The new VLR sends an Update Location (new VLR) to the HLR. + - b) The HLR cancels the data in the old VLR by sending Cancel Location (IMSI) to the old VLR. + - c) The old VLR acknowledges with Cancel Location Ack (IMSI). + - d) The HLR sends Insert Subscriber Data (IMSI, GSM subscriber data) to the new VLR. + - e) The new VLR acknowledges with Insert Subscriber Data Ack (IMSI). + - f) The HLR responds with Update Location Ack (IMSI) to the new VLR. +- 12) The new VLR allocates a new TMSI and responds with Location Update Accept (VLR TMSI) to the SGSN. VLR TMSI is optional if the VLR has not changed. An Iu Flex aware VLR includes one of its (CS-)NRIs as part of VLR TMSI. The SGSN creates an association with the VLR by storing VLR number. +- 13) The new SGSN validates the MS's presence in the new RA. If due to roaming restrictions the MS is not allowed to be attached in the SGSN, or if subscription checking fails, the SGSN rejects the routing area update with an appropriate cause. If all checks are successful, the new SGSN establishes MM context for the MS. The new SGSN responds to the MS with Routing Area Update Accept (P-TMSI, VLR TMSI, P-TMSI Signature). An Iu Flex aware SGSN includes one of its (PS-)NRIs as part of P-TMSI. +- 14) The MS confirms the reallocation of the TMSIs by returning a Routing Area Update Complete message to the SGSN. +- 15) The new SGSN sends a TMSI Reallocation Complete message to the new VLR if the MS confirms the VLR TMSI. + +## 7.5 IMSI attach procedure / Location area update with IMSI + +This signalling flow shows the basic IMSI attach or location update procedure when a UMTS UE registers to a pool-area by mobile identity type IMSI. + +![Sequence diagram of IMSI attach procedure / Location area update with IMSI. Lifelines: UE, RNC, New MSC, old MSC, HLR. The sequence shows the UE sending an Initial_DT to the RNC, which then sends an Initial_UE to the New MSC. Security functions are performed between the New MSC and HLR. The New MSC sends an Update Location to the HLR, which responds with Cancel Location to the old MSC, Cancel Location Ack to the HLR, Insert Subscriber Data to the New MSC, Insert Subscriber Data Ack to the HLR, and Update Location Ack to the New MSC. Finally, the New MSC sends a Direct_Transfer(NAS_PDU(TMSI(NRI))) to the RNC, which sends a Downlink_DT(NAS_PDU(TMSI(NRI))) to the UE. The UE sends an Uplink_DT(NAS_PDU) to the RNC, which sends a Direct_Transfer(NAS_PDU) to the New MSC.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC + participant New MSC + participant old MSC + participant HLR + + Note right of UE: 1. Initial_DT( IDNNS = "routing parameter derived from IMSI") + UE->>RNC: + Note right of RNC: 2. Initial_UE + RNC->>New MSC: + Note right of New MSC: 3. Security Functions + New MSC->>HLR: + Note right of HLR: 4a. Update Location + HLR->>old MSC: 4b. Cancel Location + old MSC->>HLR: 4c. Cancel Location Ack + HLR->>New MSC: 4d. Insert Subscriber Data + New MSC->>HLR: 4e. Insert Subscriber Data Ack + HLR->>New MSC: 4f. Update Location Ack + Note right of New MSC: 5. Direct_Transfer(NAS_PDU(TMSI(NRI))) + New MSC->>RNC: + Note right of RNC: 6. Downlink_DT (NAS_PDU(TMSI(NRI))) + RNC->>UE: + Note right of UE: 7. Uplink_DT(NAS_PDU) + UE->>RNC: + Note right of RNC: 8. Direct_Transfer(NAS_PDU) + RNC->>New MSC: + +``` + +Sequence diagram of IMSI attach procedure / Location area update with IMSI. Lifelines: UE, RNC, New MSC, old MSC, HLR. The sequence shows the UE sending an Initial\_DT to the RNC, which then sends an Initial\_UE to the New MSC. Security functions are performed between the New MSC and HLR. The New MSC sends an Update Location to the HLR, which responds with Cancel Location to the old MSC, Cancel Location Ack to the HLR, Insert Subscriber Data to the New MSC, Insert Subscriber Data Ack to the HLR, and Update Location Ack to the New MSC. Finally, the New MSC sends a Direct\_Transfer(NAS\_PDU(TMSI(NRI))) to the RNC, which sends a Downlink\_DT(NAS\_PDU(TMSI(NRI))) to the UE. The UE sends an Uplink\_DT(NAS\_PDU) to the RNC, which sends a Direct\_Transfer(NAS\_PDU) to the New MSC. + +**Figure 8: IMSI attach procedure / Location area update with IMSI** + +- 1) UE requests the setup of the RRC connection and sends the Initial\_DT including the Intra Domain NAS Node Selector (IDNNS). The IDNNS indicates that the routing parameter is derived from IMSI. +- 2) The RNC selects the MSC as described in 7.1.3. The Initial-UE message is generated on RANAP and sent via Iu-CS to the selected MSC/VLR. +- 3) The optional security functions can be executed. +- 4) Since the UE wasn't registered in the MSC before the Map Update-location procedure to HLR is invoked by the MSC: + - a) The update-location is sent to HLR; + - b) In case the UE was registered in another VLR the HLR sends cancel location procedure to old VLR; + - c) The old VLR acknowledges with Cancel location Ack; + - d) The HLR sends insert-subscriber data to the new VLR; + - e) The new VLR acknowledges with insert-subscriber data Ack; + - f) After finishing the location update procedure the HLR responds with Update-location to the new VLR. +- 5) The MSC/VLR assigns a new TMSI to the UE and sends this TMSI value in the location-update accept to the UE. The TMSI contains the NRI of the VLR. The location update accept is carried in the NAS-PDU of the RANAP direct-transfer over Iu interface. + +- 6) The RNC transparently forwards the NAS-PDU to the UE in the RRC downlink-DT message. +- 7) In the UE the new TMSI (including the NRI) and the LA are stored on SIM and the TMSI-reallocation complete is generated. This NAS message is returned to CN in the Uplink-DT via RRC. The mobile shall use this new TMSI next time it performs a mobile originating procedure. +- 8) The RNC forwards the NAS-PDU transparently to the MSC/VLR in the NAS-PDU of a Direct-transfer on Iu interface. If the TMSI-reallocation complete is received in the MSC/VLR the TMSI is considered as valid for the UE. From then on the UE will be addressed using this TMSI value. + +# Annex A (informative): Network configuration examples + +Editor's note: This annex contains the examples for network configurations that have been discussed during the drafting meetings. + +## A.1 One city centre surrounded by residential areas + +### A.1.1 Assumptions + +This example shows a network covering one city centre surrounded by residential areas. The city centre is covered by all 4 pool-areas while the residential areas are covered by one pool-area only. Once a subscriber „found" its pool-area, he will not change the pool-area while commuting between the city centre and his residential area. Each of the pool-areas is served by 5 MSCs, indicated by the 5 NRI values in the figure below. + +The example in the figure configures 4 overlapping pool-areas: + +- City centre with 12 Mio subscribers (with context in VLR, attached or detached); +- One switch office/building with 5 MSCs (5 NRIs) per pool-area; +- Capacity of one MSC/VLR up to 1 Mio subscribers in VLR; +- 4 bits are assumed for the VLR-restart counter; +- Only distinct NRI values are used, so a UE changing between pool-areas will always be allocated to a new MSC by the NAS node selection function. + +![Diagram illustrating network configuration with overlapping pool-areas. A central circle represents the city centre, surrounded by four circles representing residential areas. The central circle is labeled 'NRI: 16,17,18,19,20'. The top-left residential area is labeled 'Reuse NRI: 11'. The bottom-left residential area is labeled 'NRI: 1,2,3,4,5'. The bottom-right residential area is labeled 'NRI: 6,7,8,9,10'. The right residential area is labeled 'NRI: 11,12,13,14,15'. The bottom-right residential area is also labeled 'Reuse NRI: 1'.](80ec3bf791fd8eb41f73a420c2122529_img.jpg) + +The diagram shows five overlapping circles representing pool-areas. A central circle is labeled 'NRI: 16,17,18,19,20'. Four other circles overlap with this central circle: + + +- Top-left: labeled 'Reuse NRI: 11'. +- Bottom-left: labeled 'NRI: 1,2,3,4,5'. +- Bottom: labeled 'NRI: 6,7,8,9,10'. +- Right: labeled 'NRI: 11,12,13,14,15'. + + Additionally, a separate circle at the bottom right is labeled 'Reuse NRI: 1'. + +Diagram illustrating network configuration with overlapping pool-areas. A central circle represents the city centre, surrounded by four circles representing residential areas. The central circle is labeled 'NRI: 16,17,18,19,20'. The top-left residential area is labeled 'Reuse NRI: 11'. The bottom-left residential area is labeled 'NRI: 1,2,3,4,5'. The bottom-right residential area is labeled 'NRI: 6,7,8,9,10'. The right residential area is labeled 'NRI: 11,12,13,14,15'. The bottom-right residential area is also labeled 'Reuse NRI: 1'. + +Figure 9: One city centre surrounded by residential areas + +### A.1.2.TMSI calculation + +For addressing in the CS domain 30 bits for can be used (Bit 30&31 are reserved): + +- The assumption is that 4 bits are used for the restart counter; + +- To differentiate the 20 MSC in the city area 5 bits are needed for the NRI (12 NRI values remain unused; these 12 NRIs are left for additional MSCs in the whole area, NRIs can also be re-used as indicated in the figure); +- This leaves $30 - 4 - 5 = 21$ bits for every MSC to address the subscriber data records in the VLR. (This give address space for 2 Mio TMSIs unique over all LAs of the MSC); +- The 4 pool-areas sum up to 20 Mio subscriber, allowing for some unbalanced load distribution. + +## A.2 3 Neighbouring large city centres + +This documents provides some calculations for 'pool-identification alternative B' in case that 3 huge city centres are covered by pool-areas with direct contacts. + +### Assumptions: + +The calculations are based on the following assumptions: + +- 3 neighbouring pools with capacity of 32 M non-purged subscribers each. +- Maximum capacity of a paging channel is 1 M pagings/hour per LA. +- 0.25 pagings / hour are assumed per subscriber $\rightarrow$ 2M TMSI/LA can be realized. +- For the 'VLR-restart' counters a number of bits need to be reserved. Working assumption is that 5 bit should be sufficient for any implementation, in the examples these 5 bits are reserved on the upper part of the TMSI. (This is of course implementation specific and not part of Iu Flex). +- The calculations are based on a node capacity of up to 1M ( $2^{20}$ ) non-purged subscribers this results in: + - Minimum 32 nodes are needed per pool-area (5-bit NRI). + - Minimum is 16 LA's per pool-area. + +### Basic configuration needed for 1 pool: + +- To address the 32M TMSI per pool the total number of 25 bits are needed in the TMSI. +- For a node capacity of 1M non-purged TMSIs 20 Bits have to be reserved for TMSI per NRI and 5 bit for the NRI value. +- The NRI is located bit 14-23 (configurable). It is assumed that the bits 19-23 are used for the NRI. + +| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-----|----|---------------|----|----|----|----|----------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|---|---|---|---|---|---|---|---|---|---| +| CS/ | PS | 'VLR-restart' | | | | | used NRI range | | | | | | | | | | | | | | | | | | | | | | | | | + +Figure 10: Example of a TMSI structure with 5 bit 'VLR-restart counter' and 5 bits NRI-length + +#### '3 pool configuration' – no sharing of NRI values: + +- This example assumes that the 3 pool-areas have independent NRI values, so the available TMSI range has to be shared between the pools. All TMSI's from other pool-areas can be detected - best load distribution in the pools. +- So $3 \cdot 32 = 96$ NRI values are needed for all 3 pools. The NRI-length has to be increased to 7 bit. (not an optimum configuration since 32 NRI values are unused). In the example the NRI now uses bits 23-17. +- Since still for each NRI value 20 bits are needed to address 1M TMSIs there is a conflict with the assumed VLR-restart field length of 5 bit. The VLR-restart field has to be reduced to a 3 bit field in order to free sufficient addressing space in the TMSI structure! + +![Diagram showing three pools of NRI and TMSI values. Pool 1 (NRI: 0..31, TMSI: x0000000xx - x0011111xx) is on the left. Pool 2 (NRI: 32..63, TMSI: x0100000xx - x0111111xx) is on the top right. Pool 3 (NRI: 64..95, TMSI: x1000000xx - x1011111xx) is on the bottom right.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +Diagram showing three pools of NRI and TMSI values. Pool 1 (NRI: 0..31, TMSI: x0000000xx - x0011111xx) is on the left. Pool 2 (NRI: 32..63, TMSI: x0100000xx - x0111111xx) is on the top right. Pool 3 (NRI: 64..95, TMSI: x1000000xx - x1011111xx) is on the bottom right. + +*NRI: 96..127 +TMSI: x1100000xx - x1111111xx +are unused* + +| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-------|---------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|---|---|---|---|---|---|---|---|---|---| +| CS/PS | 'VLR-restart' | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Figure 11: Modified TMSI structure 7 bits NRI-length; VLR-restart field must be reduced to 3 bit** + +- In this example configuration 32M TMSI values are wasted! So it would be more efficient to assign these TMSI ranges to the 3 pools rather than leave them unused. Alternatively these values could be used for sharing with nodes in the 'outside world'. +- The major drawback of this solution is the reduction of the VLR-restart field to 3 bits only! + +#### **'3 pool configuration' – 25% of NRI values shared between the pools:** + +- Now the pool configurations are changed in a way that 25% of the NRI values are the same in all the 3 pools. This means that for 1/4 of subscribers pool-changes cannot be detected. The traffic generated by these subscribers will not be distributed, but is routed by the NAS node selection function to the specific node with this NRI value in the new pool. +- The total range of needed NRI values is reduced by this to: +8 (the shared NRI's) + 3 \* 24 = 80 +- To code this NRI's still 7 bit are needed. So there is no gain in terms of addressing space in this example. +- In the example the NRI values 0..7 are shared and so are the TMSI ranges x0000000xx .. x0000111x + +![Diagram showing three pools (Pool 1, Pool 2, Pool 3) with their respective NRI and TMSI ranges. Pool 1 is on the left, Pool 2 is on top right, and Pool 3 is on bottom right. Pool 1 has NRI 0..31 and TMSI x0000000xx - x0011111xx. Pool 2 has NRI 0..7 & 32..55 and TMSI x0000000xx - x0000111xx & x0100000xx - x0110111xx. Pool 3 has NRI 0..7 & 56..79 and TMSI x0000000xx - x0000111xx & x0111000xx - x1001111xx.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +**Pool 1** +NRI: 0..31 +TMSI: x0000000xx +- +x0011111xx + +**Pool 2** +NRI: 0..7 & 32..55 +TMSI: x0000000xx - +x0000111xx & +x0100000xx +- +x0110111xx + +**Pool 3** +NRI: 0..7 & 56..79 +TMSI: x0000000xx - +x0000111xx & +x0111000xx +- +x1001111xx + +Diagram showing three pools (Pool 1, Pool 2, Pool 3) with their respective NRI and TMSI ranges. Pool 1 is on the left, Pool 2 is on top right, and Pool 3 is on bottom right. Pool 1 has NRI 0..31 and TMSI x0000000xx - x0011111xx. Pool 2 has NRI 0..7 & 32..55 and TMSI x0000000xx - x0000111xx & x0100000xx - x0110111xx. Pool 3 has NRI 0..7 & 56..79 and TMSI x0000000xx - x0000111xx & x0111000xx - x1001111xx. + +*NRI: 80..127* + +*TMSI: x1010000xx - x1111111xx* + +*are unused* + +| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-------|---------------|----|----|----------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|---|---|---|---|---|---|---|---|---|---| +| CS/PS | 'VLR-restart' | | | used NRI range | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Figure 12: Modified TMSI structure 7 bits NRI-length; VLR-restart field must remain 3 bit.** + +#### **'3 pool configuration' – 50% of NRI values shared between the pools:** + +- The percentage of the shared NRIs is now increased to 50%. So ½ of the NRI values are the same in all the 3 pools. This means that for ½ of subscribers pool-changes cannot be detected. The traffic generated by these subscribers will not be distributed, but is routed by the NAS node selection function to the specific node with this NRI value in the new pool. +- The total range of needed NRI values is reduced by this to: 16 (the shared NRI's) + 3 \* 16 = 64. +- This reduction of NRI saves 1 bit in NRI length. So the VLR-restart can be slightly increased to 4 bit (still 1 bit less than in the original assumption). +- In the example the NRI values 0..15 are shared and so are the TMSI ranges x0000000xx .. x0011111x + +![Diagram showing three pools of NRI and TMSI values. Pool 1 is on the left, containing NRI: 0..31 and TMSI: x000000xx - x011111xx. Pool 2 is on the top right, containing NRI: 0..15 & 32..47 and TMSI: x000000xx - x001111xx & x010000xx - x101111xx. Pool 3 is on the bottom right, containing NRI: 0..15 & 48..63 and TMSI: x000000xx - x001111xx & x110000xx - x111111xx.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +**Pool 1** +NRI: 0..31 +TMSI: x000000xx +- +x011111xx + +**Pool 2** +NRI: 0..15 & 32..47 +TMSI: x000000xx - +x001111xx & +x010000xx +- +x101111xx + +**Pool 3** +NRI: 0..15 & 48..63 +TMSI: x000000xx - +x001111xx & +x110000xx +- +x111111xx + +Diagram showing three pools of NRI and TMSI values. Pool 1 is on the left, containing NRI: 0..31 and TMSI: x000000xx - x011111xx. Pool 2 is on the top right, containing NRI: 0..15 & 32..47 and TMSI: x000000xx - x001111xx & x010000xx - x101111xx. Pool 3 is on the bottom right, containing NRI: 0..15 & 48..63 and TMSI: x000000xx - x001111xx & x110000xx - x111111xx. + +| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-------|---------------|----|----|----|----------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|---|---|---|---|---|---|---|---|---|---| +| CS/PS | 'VLR-restart' | | | | used NRI range | | | | | | | | | | | | | | | | | | | | | | | | | | | + +**Figure 13: NRI-length can be reduced by 1 bit; VLR-restart field can increase to 4 bit.** + +**'3 pool configuration' – 75% of NRI values shared between the pools:** + +- Next step is to even increase the shared part of the NRI to $\frac{3}{4}$ . This means that only 25% of the incoming traffic in a pool-area is distributed. +- The total range of needed NRI values is reduced by this to: +24 (the shared NRI's) + 3 \* 8 = 48. +- Like the first step this doesn't free any addressing space in the TMSI. But some NRI values are now available in case it is wanted to share them with other nodes outside the '3 pool area'. +- In the example the NRI values 0..23 are shared and so are the TMSI ranges x000000xx .. x010111x + +![Diagram showing three pools (Pool 1, Pool 2, Pool 3) with their respective NRI and TMSI ranges. Pool 1: NRI: 0..31, TMSI: x000000xx - x011111xx. Pool 2: NRI: 0..23 & 32..39, TMSI: x000000xx - x010111xx & x100000xx - x101001xx. Pool 3: NRI: 0..23 & 40..47, TMSI: x000000xx - x010111xx & x101010xx - x101111xx. Below the diagram is a 32-bit bit map showing CS/PS, VLR-restart, and used NRI range fields.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------|---------------|----|----|----------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|---|---|---|---|---|---|---|---|---|---|--|--|--|--| +| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | +| CS/PS | 'VLR-restart' | | | used NRI range | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +Diagram showing three pools (Pool 1, Pool 2, Pool 3) with their respective NRI and TMSI ranges. Pool 1: NRI: 0..31, TMSI: x000000xx - x011111xx. Pool 2: NRI: 0..23 & 32..39, TMSI: x000000xx - x010111xx & x100000xx - x101001xx. Pool 3: NRI: 0..23 & 40..47, TMSI: x000000xx - x010111xx & x101010xx - x101111xx. Below the diagram is a 32-bit bit map showing CS/PS, VLR-restart, and used NRI range fields. + +**Figure 14: NRI-length can be reduced by 1 bit; VLR-restart field can increase to 4 bit.** + +#### **'3 pool configuration' – full sharing of NRIs between the pools:** + +- The last variant of these configurations is a full sharing of all NRI values between all neighbouring pools. In this case no detection of pool area changes is possible. Consequently no distribution of load can be achieved. This results necessarily in the need to have a 'forced redistribution' mechanism to resolve heavy unbalance of load. +- The NRI and TMSI ranges will then be the same as in the 'single pool' example in the beginning. + +### **Result:** + +The examples above show that it is basically not possible to configure the example configuration (32M non-purged subscribers; 1M per MSC) with a VLR-restart field as put in the assumptions, except that the full range of NRI is shared between the pools. + +Taking it literally it could be possible with 3 pools when sharing the remaining quarter of the NRI (the part that would be unused otherwise), but latest if 4 pool-areas with this capacity have to be supported this reaches the limit. + +An alternative to overcome this could be to apply the TMSI's on a per LA basis as it is already foreseen on the A/Iu interface specifications. + +#### **TMSI per LA:** + +Taking the example configuration mentioned above but changing the TMSI allocation per LA would result in an increase of the addressing space. Then the same TMSI value can be used multiple times in the same VLR. A specific subscriber data record can then only be addressed by LA&TMSI. + +For the 32 MSCs this means that each of them supports an equal share of TMSI of a LA. So each MSC handles $2M/32 = 32k$ TMSI of a specific LA. + +The required TMSI addressing space is thereby reduced to 15 bit per MSC. + +If, like before, 96 NRI values are needed to address all nodes in the 3 pools then 7 bit are needed for this. This leaves 5 bit for the VLR-restart counters (plus 3 unused bits). + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------|---------------|----|----|----|----|----|----|----|----|----|----|----------------|----|----|----|----|----|----|----|----|----|---|---|---|---|---|---|---|---|---|---| +| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| CS/<br>PS | 'VLR-restart' | | | | | | | | | | | used NRI range | | | | | | | | | | | | | | | | | | | | + +**Figure 15: TMSI example for TMSI allocation per VLR; 32M TMSI/pool;** + +Without sharing NRI values the pool size can even be increased (Factor 8 – since 3 bit spare). + +A number of aspects however remain to be looked at with this TMSI per LA approach: + +- It requires an equal distribution of UE's of a certain LA over all nodes in the pool. This contradicts the wish for a flexible routing where e.g. a new attach should be routed to the closest node in order to save transmission resources. +- Attach requests in a LA may be rejected by one node because this node has already a fully booked TMSI table for this LA. At the same time the node may have in total still capacity left to serve subscribers. +- The total load of TMSI re-allocations may increase since every change of LA must result in a TMSI reallocation. +- MAP on VLR-VLR I/F must be updated, otherwise subscriber confidentiality decreases because for every change to other MSCs the IMSI has to be fetched via the air I/F. (At the same time node changes should only occur when changing the pool-area – so maybe never?). +- Can it happen that if NRI are shared there are several subscribers with the same TMSI in a certain LA? FFS +If yes then a paging-request there will trigger several page-response messages per LA. + +# Annex B (informative): Change history + +| Change history | | | | | | | | | | +|----------------|-------|-----------|------|-----|-----|------------------------------------------------------------|--------|---------------|-----| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | | Old | New | +| 2010-03 | SA#47 | SP-100162 | 0039 | 1 | F | Inclusion of informative reference to FS IDC study work | 9.0.0 | 10.0.0 | | +| 2010-09 | SA#49 | SP-100553 | 0041 | 1 | B | M2M related updates | 10.0.0 | 10.1.0 | | +| 2010-12 | SA#50 | SP-100688 | 0042 | 1 | F | Extra text on NNSF for MTC | 10.1.0 | 10.2.0 | | +| 2010-12 | SA#50 | SP-100691 | 0046 | 2 | F | Iu/A Flex - Subsequent Inter- MSC Handover Interactions | 10.1.0 | 10.2.0 | | +| 2011-01 | - | - | - | - | - | Update of LTE logo to LTE-Advanced logo | 10.2.0 | 10.2.1 | | +| 2012-03 | SA#55 | SP-120074 | 0048 | 2 | F | Corrected MTC terminology | 10.2.1 | 10.3.0 | | +| 2012-06 | SA#57 | SP-120486 | 0049 | 3 | F | Gs Support for MSC in Pool to avoid dual VLR registration. | 10.3.0 | <b>11.0.0</b> | | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23327/164d1b48231be457522b31965610ea3b_img.jpg b/marked/Rel-11/23_series/23327/164d1b48231be457522b31965610ea3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a50d9ec78ec81ac607d483b094cba86472023962 --- /dev/null +++ b/marked/Rel-11/23_series/23327/164d1b48231be457522b31965610ea3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:258d492ae031ad3e51ae76a490ced05751979e6fd3032e48e989415f3d6810cd +size 128351 diff --git a/marked/Rel-11/23_series/23327/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg b/marked/Rel-11/23_series/23327/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa678e55efd749b396ade90835c437a88ca28087 --- /dev/null +++ b/marked/Rel-11/23_series/23327/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db7df10e66b3d0d9a72a9be52e992397f87f62d8fab4e180cb3905e959de697c +size 63698 diff --git a/marked/Rel-11/23_series/23327/72bc1a2b64dd6bac8285f560440c1218_img.jpg b/marked/Rel-11/23_series/23327/72bc1a2b64dd6bac8285f560440c1218_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56fac0af496b29fd5d9e14fbae65ef614f44893b --- /dev/null +++ b/marked/Rel-11/23_series/23327/72bc1a2b64dd6bac8285f560440c1218_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23c8ea4a9f68a4c5f8ae0eb2870b1890454fa1501db538fb810b5a59f9da4f17 +size 54054 diff --git a/marked/Rel-11/23_series/23327/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Rel-11/23_series/23327/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e504117ac5f6ce4251daf5d66a81848b903cea4 --- /dev/null +++ b/marked/Rel-11/23_series/23327/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:704e0883868b259d679ecfd9e2e4d80660e04dc4cee8c87d2e3a342ccc800256 +size 57751 diff --git a/marked/Rel-11/23_series/23327/d793cf7c174b89eb024d132f00679787_img.jpg b/marked/Rel-11/23_series/23327/d793cf7c174b89eb024d132f00679787_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f403b57ed3e9a630e12987e926dbb7275eb12b7f --- /dev/null +++ b/marked/Rel-11/23_series/23327/d793cf7c174b89eb024d132f00679787_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb3a55fac3c16b813de7b7080a24fdaa73634a29cd0c6570154abc69ec341055 +size 17117 diff --git a/marked/Rel-11/23_series/23327/raw.md b/marked/Rel-11/23_series/23327/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a7d24c9ea4d7dfb848951b0df2c156652b71e822 --- /dev/null +++ b/marked/Rel-11/23_series/23327/raw.md @@ -0,0 +1,898 @@ +# Contents + +| | | +|-------------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and Abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 High-Level Requirements and Principles ..... | 7 | +| 4.1 General Requirements ..... | 7 | +| 4.2 Architecture Requirements..... | 7 | +| 4.3 Mobility Requirements..... | 8 | +| 4.4 Roaming Requirements ..... | 8 | +| 4.5 Charging Requirements..... | 8 | +| 4.6 Security Requirements ..... | 8 | +| 5 Concepts and Architecture Model..... | 8 | +| 5.1 General Concepts ..... | 8 | +| 5.2 Architecture Reference Model ..... | 8 | +| 5.2.1 Home Mobility Service Architecture ..... | 8 | +| 5.2.2 Visited Mobility Service Architecture..... | 9 | +| 5.3 High Level Functions ..... | 10 | +| 5.3.1 General ..... | 10 | +| 5.3.2 Home Agent Discovery ..... | 10 | +| 5.3.3 Home Link Detection ..... | 10 | +| 5.4 Network Elements ..... | 11 | +| 5.5 Reference Points..... | 11 | +| 6 Functional Description and Information Flows ..... | 12 | +| 6.1 H1 PDN Attach ..... | 12 | +| 6.2 H1 PDN Detach..... | 13 | +| 6.2.1 UE Initiated Detach ..... | 13 | +| 6.2.2 HA Initiated Detach..... | 14 | +| 6.2.3 AAA Initiated Detach..... | 14 | +| 6.3 Handover ..... | 15 | +| 6.3.1 H1 Reference Point Procedure ..... | 15 | +| 6.3.2 Handover Signalling Flows ..... | 16 | +| 6.3.2.1 Handover from 3GPP I-WLAN to 3GPP access ..... | 16 | +| 6.3.2.2 Handover from 3GPP access to 3GPP I-WLAN access ..... | 16 | +| 6.4 Accounting ..... | 17 | +| 6.5 Interactions with Other Services ..... | 17 | +| 6.6 IPv4 Home Address Release Procedure..... | 18 | +| <b>Annex A (Normative): EPS Migration Considerations .....</b> | <b>19</b> | +| <b>Annex B (Normative): Information on implementation options .....</b> | <b>20</b> | +| B.1 Co-located HA and GGSN functions..... | 20 | +| B.1.1 I-WLAN Mobility System Architecture with Co-located HA-GGSN..... | 20 | +| B.1.2 Home Link Discovery for the Co-located HA and GGSN..... | 20 | +| B.1.3 3GPP Attachment..... | 21 | +| B.1.4 I-WLAN Attachment..... | 22 | +| B.1.5 Handover from 3GPP access to I-WLAN..... | 24 | +| B.1.6 Handover from I-WLAN to 3GPP Access..... | 25 | +| B.2 Co-located HA and PDG functions..... | 26 | +| B.2.1 H1 PDN Attach ..... | 26 | +| Annex C (Informative): Change History ..... | 27 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +This document specifies the stage 2 system description for providing mobility between 3GPP Wireless Local Area Network Interworking (I-WLAN) and 3GPP Systems. It is to define a technical solution based on the working principles of DSMIPv6 (see RFC 5555 [7]) with necessary enhancement of the I-WLAN architecture for supporting mobility and roaming between 3GPP-WLAN Interworking system and 3GPP Systems so that ongoing 3GPP PS based services can be maintained with minimal impact on the end-user's perceived quality on the services at a change of the access network (between I-WLAN and 3GPP Access Systems). + +The specification includes both non-roaming and roaming scenarios and covers all aspects, including mobility between 3GPP Systems and I-WLAN with access authentication and charging. + +# --- 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.234: "3GPP Systems to Wireless Local Area Network (WLAN) Interworking; System Description". +- [3] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2". +- [4] 3GPP TS 23.203: "Policy and Charging Control Architecture". +- [5] 3GPP TS 33.234: "3G security; Wireless Local Area Network (WLAN) interworking security". +- [6] 3GPP TS23.402: "Architecture Enhancements for non-3GPP accesses". +- [7] IETF RFC 5555: "Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)". +- [8] IETF RFC 6275: "Mobility Support in IPv6". +- [9] IETF RFC 5996, "Internet Key Exchange Protocol Version 2 (IKEv2)". +- [10] IETF RFC 3748: "Extensible Authentication Protocol (EAP)". +- [11] IETF RFC 4877: "Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture". +- [12] IETF RFC 4739: "Multiple Authentication Exchanges in the Internet Key Exchange (IKEv2) Protocol". +- [13] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based Services and Packet Data Networks (PDN)". + +# --- 3 Definitions and Abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the definition given in TR 21.905 [1] and the following apply. A definition given in the present document takes precedence over the same definition, if any, in TR 21.905 [1]. + +**Home Agent Access Point Name (HA-APN):** Is used to identify a specific PDN and a point of interconnection to that network (Home Agent). + +## 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]. + +| | | +|---------|-------------------------------------| +| APN | Access Point Name | +| CoA | Care-of-address | +| DHCP | Dynamic Host Configuration Protocol | +| DNS | Domain Name System | +| DSMIPv6 | Dual-Stack MIPv6 | +| EPS | Evolved Packet Systems | +| GGSN | Gateway GPRS Support Node | +| GTP | GPRS Tunnelling Protocol | +| HA | Home Agent | +| I-WLAN | Interworking WLAN | +| MIP | Mobile IP | +| MIPv6 | Mobile IP version 6 | +| MN | Mobile Node | +| PDP | Packet Data Protocol, e.g. IP | +| SGSN | Serving GPRS Support Node | +| UE | User Equipment | + +# --- 4 High-Level Requirements and Principles + +## 4.1 General Requirements + +- Access to 3GPP and internet services shall be supported. +- Smooth migration from legacy network with minimal impacts on dual mode UEs, I-WLAN and 3GPP systems shall be possible. +- Architecture, functions and procedures described in I-WLAN interworking TS 23.234 [2] and GPRS TS 23.060 [3] shall be re-used as basis. + +## 4.2 Architecture Requirements + +- Mobility for PDG based I-WLAN architecture shall be supported. +- Both IPv4 and IPv6 addresses shall be supported +- Quality of service shall be supported when the UE moves between I-WLAN and 3GPP systems +- I-WLAN and 3GPP QoS mechanisms defined in TS 23.234 [2] TS 23.060 [3] and TS 23.203 [4] shall be re-used. Additionally, the Home Agent shall be able to provide transport IP QoS e.g. DiffServ support similarly as defined for PDG in TS 23.234 [2]. + +## 4.3 Mobility Requirements + +- Service continuity between 3GPP packet switched network and I-WLAN with IP address (es) preservation shall be supported. +- Multiple parallel sessions under the same APN shall be maintained when the UE moves between 3GPP PS network and I-WLAN. Also the mobility for the UE with multiple PDN connectivity should be supported. +- Interruption time of the operators' services or applications being provided to the end user shall be minimized. +- It shall be possible to notify to the user the change of the access networks, 3GPP PS system or I-WLAN. + +- It shall be possible to disable the mobility function where applicable to the operators' needs. + +## 4.4 Roaming Requirements + +- Mobility with re-use of roaming architecture interface(s) and protocol(s) in a visited PLMN shall be possible. + +## 4.5 Charging Requirements + +- It shall be possible to re-use existing policy control and charging (PCC) rules and mechanisms as defined in TS 23.203 [4]. +- Charging differentiation capability based on radio access type shall be enabled. +- Use of common billing system for 3GPP PS system and the I-WLAN access shall be possible. + +## 4.6 Security Requirements + +- Existing security measures taken by the end users and the operators shall not be compromised. +- It shall be possible for operators to apply common access control based on TS 33.234 [5] regardless of the change of the accesses by the UEs. +- The operators shall be able to apply legal interception. + +# --- 5 Concepts and Architecture Model + +This specification is based on the architectural/functional/procedural definitions described in (WLAN Interworking) TS 23.234 [2] and (GPRS) TS 23.060 [3]. + +I-WLAN Mobility solution shall allow the operator to configure a type of access (e.g. 3GPP access) as the "home link" for DSMIPv6 purposes. + +## 5.1 General Concepts + +## 5.2 Architecture Reference Model + +### 5.2.1 Home Mobility Service Architecture + +The *Home Mobility Service architecture* refers to the case where the Home Agent function locates at HPLMN. Whether the user is roaming or not roaming in the underlying access system and/or whether the illustrated H3 reference point spans across different administrative domains is not relevant for this specification. + +![Home Mobility Service Architecture for I-WLAN Mobility diagram](4792a2ccd62226861fadc22117edb7b1_img.jpg) + +``` + +graph TD + subgraph WLAN_AN [WLAN Access Network] + end + style WLAN_AN stroke-dasharray: 5 5 + + subgraph GERAN_UTRAN [GERAN/UTRAN] + end + style GERAN_UTRAN stroke-dasharray: 5 5 + + subgraph EXT_PDN [External PDN] + end + style EXT_PDN stroke-dasharray: 5 5 + + WAG[WAG] + PDG_AR[PDG/AR] + UE[UE] + HA[HA] + SGSN[SGSN] + GGSN_AR[GGSN/AR] + AAA[3GPP AAA Server] + HSS[HSS] + + WLAN_AN -- Wn --- WAG + WAG -- Wp --- PDG_AR + WLAN_AN -- Ww --- UE + UE -- Wu --- PDG_AR + UE -- H1 --- HA + UE -- Uu/Um --- GERAN_UTRAN + GERAN_UTRAN -- Iu_ps/Gb --- SGSN + SGSN -- Gn --- GGSN_AR + GGSN_AR -- H3 --- HA + PDG_AR -- H3 --- HA + PDG_AR -- H2 --- AAA + AAA -- Wx --- HSS + HA -- HGi --- EXT_PDN + +``` + +The diagram illustrates the Home Mobility Service Architecture for I-WLAN Mobility. It features a central User Equipment (UE) connected to various network components. The UE is connected to a WLAN Access Network via a Ww interface, to a GERAN/UTRAN via a Uu/Um interface, and to a PDG/AR via a Wu interface. The WLAN Access Network is connected to a WAG via a Wn interface, which in turn connects to the PDG/AR via a Wp interface. The GERAN/UTRAN is connected to an SGSN via an Iu\_ps/Gb interface, which connects to a GGSN/AR via a Gn interface. The PDG/AR is connected to a HA via an H3 interface. The HA is connected to the UE via an H1 interface, to the PDG/AR via an H2 interface, to the GGSN/AR via an H3 interface, and to an External PDN via an HGi interface. The PDG/AR is also connected to a 3GPP AAA Server via an H2 interface. The 3GPP AAA Server is connected to an HSS via a Wx interface. The WLAN Access Network, GERAN/UTRAN, and External PDN are represented by dashed boxes. + +Home Mobility Service Architecture for I-WLAN Mobility diagram + +**Figure 5.2.1-1: Home Mobility Service Architecture for I-WLAN Mobility** + +NOTE: The architecture is compatible with pre-Release 8 PDG and GGSN. + +### 5.2.2 Visited Mobility Service Architecture + +The Visited Mobility service *architecture* refers to the case where the Home Agent function locates outside of the HPLMN. Whether the user is roaming or not roaming in the underlying access system and/or whether the illustrated H3 reference point spans across different administrative domains is not relevant for this specification. + + + +## 5.3 High Level Functions + +### 5.3.1 General + +The WLAN Interworking Mobility solution described in this TS provides a DSMIPv6 (see RFC 5555 [7]) based inter-system mobility solution on top of 3GPP I-WLAN, TS 23.234 [2] and 3GPP PS domain, TS 23.060 [3]. The inter-system mobility solution is compatible with pre-Release 8 TS 23.060 [3] systems and with pre-Release 8 TS 23.234 [2] systems. + +The inter-system mobility solution provides the following functions: + +- HA discovery. + +- Security association establishment between UE and HA, including the required AAA interactions. +- DSMIPv6 signalling and user data transfer between UE and HA. + +The inter-system mobility solution has the following limitations: + +- No support for Network Initiated Service Request procedures. +- No support for PCRF -HA interactions. +- No updates to the existing PCRFs. +- No updates to the existing PCC signalling. +- No updates to the existing PCEF functionality in GGSN and PDG. + +NOTE: This means that the PCEF in GGSN and PDG can not operate on service data flows inside the tunnel between UE and HA. + +Extending DSMIPv6 based inter-system mobility, to avoid the above limitations, requires deployment of EPS PDN GW. EPS PDN GW and its interactions with other 3GPP system nodes are specified in TS 23.402 [6]. + +Further EPS migration aspects are described in Annex A of this specification. + +### 5.3.2 Home Agent Discovery + +DSMIPv6 requires that the UE knows the HA IP address in order to establish the security association with home agent and then, to proceed to binding updates. This address is made known to the UE with one of the following ways: + +- 1) The IP address of the home agent is statically configured in UE, typically through a manual method, and is permanent until manually changed. +- 2) The IP address of the home agent can be retrieved from DNS. +- 3) The IP address of the home agent can be delivered to the UE via PCO. +- 4) The PDG may return the IP address of the home agent in IKEv2 configuration payload to the UE. + +NOTE: The underlying IP access network may support other ways of configuring the HA IP address to the UE, but this is out of the scope of this specification. + +### 5.3.3 Home Link Detection + +The DSMIPv6 Home Link Detection Function is used by the UE to detect, if for a specific PDN, an access interface is the Home Link from DSMIPv6 perspective. + +It is up to the UE's configuration to decide when to trigger the home link detection function for a specific PDN connection. Before performing DSMIPv6 registration over any PDN connection, the UE must determine that it is not on its home link. + +The home link detection function compares: + +- IPv6 prefix associated with a specific access interface of the UE; and +- Home Network Prefix (HNP) allocated to the PDN connection. + +If the two prefixes match, the UE detects it is in the home link for this specific PDN over the access interface. Otherwise, the UE detects it is not in the home link for this specific PDN over the access interface. + +NOTE 1: The UE knows the IPv6 prefix associated with a specific access system interface via IP address allocation mechanisms applied in that access system. + +The UE knows the HNP allocated to the PDN connection from: + +- the IPsec security association bootstrap with the HA; or +- the PCO delivered to UE at 3GPP attach during the PDP context creation procedure to the GGSN in 2G/3G; or +- from the IKEv2 sent to the UE during the IPsec tunnel establishment to the PDG in I-WLAN. + +The GGSN and PDG can get the HNP of the UE by means such as DHCP or AAA. + +NOTE 2: The HNP may also be pre-configured in the UE. + +## 5.4 Network Elements + +### Home Agent (HA): + +The Home Agent communicates with the UE and exchanges DSMIPv6 related signalling to keep track of the access network the UE is recently camping on. This signalling is transparent to the Access Routers (AR) (GGSN and PDG). + +HA functionality may be implemented as a stand-alone HA entity, or co-located with GGSN or PDG. The special considerations of the HA-GGSN and HA-PDG co-location are described in Annex B of this specification. Configuring the GPRS system as the home link also for a standalone HA is not precluded. The home link is the link on which the UE's home subnet prefix is defined (see RFC 6275 [8]). + +### **UE:** + +The UE contains a DSMIPv6 Client to enable the DSMIPv6 based signalling and user data transfer towards the Home Agent. + +## 5.5 Reference Points + +**HGi:** This reference point defines the interface from the HA to external PDN + +**H1:** This is the reference point for signalling and user data transfer between UE and HA. + +NOTE: H1 may be transported over IP connectivity provided by I-WLAN or 3GPP access system. + +**H2:** This reference point defines the interface between HA and 3GPP AAA infrastructure (3GPP AAA server or 3GPP AAA proxy) and is used to transport authentication, authorization and charging-related information in a secure manner. + +**H3:** This is the IP transport reference point to carry the end-to-end UE-HA signalling and user data between Access Router and HA. Since there is no direct signalling messages between these two entities this is simple IP transport reference point, which does not require additional specification. + +# --- 6 Functional Description and Information Flows + +## 6.1 H1 PDN Attach + +H1 PDN Attach is triggered by the UE to initialize the I-WLAN Mobility service towards a specific PDN. For each PDN connection, the H1 PDN Attach has to be performed separately. + +NOTE 1: The H1 PDN Attach is creating a PDN specific H1 instance between a UE and a HA. + +NOTE 2: To execute H1 PDN Attach via GPRS, the UE shall have Primary PDP context to GGSN from which the discovered HA can be reached via H3. + +When connected over the UE home link (e.g. 3GPP access), the UE may be configured not to trigger the establishment of IKEv2 SA. In this case, H1 PDN Attach is triggered when the UE moves to I-WLAN. During the Handover the UE keeps using the source 2G/3G access (i.e. make-before-break). + +![Sequence diagram for H1 PDN Attach showing interactions between UE, HA, 3GPP AAA Proxy, and 3GPP AAA Server.](68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HA + participant 3GPP_AAA_Proxy as 3GPP AAA Proxy + participant 3GPP_AAA_Server as 3GPP AAA Server + + Note over UE: 1. HA discovery + UE->>HA: 2. IKEv2 Security Association establishment & IPv6 HoA allocation + HA->>3GPP_AAA_Proxy: 2. Auth. & Authorization + 3GPP_AAA_Proxy->>3GPP_AAA_Server: + UE->>HA: 3. Binding Update + HA->>UE: 4. Binding Acknowledgement + rect rgb(255, 255, 255) + Note over UE, HA: 5. Child SA establishment for enhanced security + end + +``` + +The diagram illustrates the H1 PDN Attach process. It begins with the UE performing HA discovery. The UE then initiates IKEv2 Security Association establishment and IPv6 HoA allocation with the HA. The HA communicates with the 3GPP AAA infrastructure (Proxy and Server) for authentication and authorization. The UE sends a Binding Update to the HA, which responds with a Binding Acknowledgement. Finally, a child IPsec Security Association may be established for enhanced security. + +Sequence diagram for H1 PDN Attach showing interactions between UE, HA, 3GPP AAA Proxy, and 3GPP AAA Server. + +**Figure 6.1: H1 PDN Attach** + +1. The UE discovers the Home Agent as defined in the clause 5.3.2, *Home Agent Discovery*. +2. A security association is established between UE and HA to secure the DSMIPv6 messages related to this PDN connection between the UE and the HA. The UE initiates the establishment of the security association using IKEv2, RFC 5996 [9]; EAP, RFC 3748 [10] is used over IKEv2 for authentication purposes. The HA communicates with the AAA infrastructure in order to complete the authentication. + + +During this step an IPv6 home network prefix is assigned by the HA to the UE as defined in RFC 4877 [11] and RFC 5996 [9]. During this step the UE may include the APN of the PDN it wants to access (in the IKE AUTH message using the IDr payload in similar manner as specified for I-WLAN in TS 23.234 [2]) and it can also request a specific IPv6 home network prefix as defined in RFC 4877 [11] in order to influence the IP network prefix assignment procedure. After the IPv6 home network prefix is assigned, UE constructs a home address from it via auto-configuration. + +In this step, the HA may be either in the HPLMN or in the VPLMN. When the HA is in the VPLMN, the interaction between the HA in the VPLMN with the AAA/HSS in the HPLMN may involve a 3GPP AAA Proxy in the VPLMN as specified in TS 23.234 [2]. + +If the PDN requires an additional authentication and authorization with an external AAA Server additional authentication is executed in this step. Details on these multiple authentications are specified in RFC 4739 [12] and in TS 23.234 [2] for I-WLAN (Private Network Access (PNA)). +3. In case a Binding Update is required to establish the desired PDN connectivity (e.g. UE is not at it's home link), the UE sends the DSMIPv6 Binding Update message to the HA as specified in RFC 5555 [7]. The UE shall inform the HA that IP address preservation shall be maintained for the whole home network prefix. + + +The HA processes the Binding Update. During the processing the HA performs local authentication and authorization of the message using the IPsec security association established in step 2. If the UE does not have an IPv4 HoA already, it may request for the IPv4 home address from the HA as defined in RFC 5555 [7] in this step. This request for the IPv4 home address may alternatively be done in any subsequent Binding Update. +4. The HA sends the DSMIPv6 Binding Ack to the UE. In this step the HA may include an IPv4 home address as specified in RFC 5555 [7] if requested by the UE in step 3. In case GPRS is configured to act as the home link for the PDN connection, the HA should also include an APN through which it is possible for the UE to gain GPRS home link connectivity. +5. The HA may additionally trigger the creation of a child IPsec Security Association for protecting the traffic sent via the H1 reference point. The child SA is created as specified in RFC 4877 [22]. Child SA can be used for H1 IP flow integrity protection and may be used also for H1 IP flow encryption. + +NOTE 1: The child SA can be established and/or released by HA at any time after the IKEv2 bootstrap and not only just after step 4. + +NOTE 2: In a roaming scenario, the usage of the child SA for H1 IP flow encryption by HPLMN HA may be restricted by the policies in the roaming agreement between the VPLMN and the HPLMN. + +## 6.2 H1 PDN Detach + +The H1 PDN Detach is clearing the PDN specific H1 instance between a UE and a HA. This H1 PDN detach has no impact to the status of possibly existing other H1 based PDN connections nor to the underlying IP access connectivity state e.g. within GPRS system. + +### 6.2.1 UE Initiated Detach + +The Detach procedure when initiated by the UE is illustrated below. + +![Sequence diagram of UE Initiated Detach Procedure](22b2fd4b8672ad8b02cf6cd4de5809cd_img.jpg) + +``` +sequenceDiagram + participant UE + participant HA + participant 3GPP_AAA_Proxy as 3GPP AAA Proxy + participant 3GPP_AAA_Server as 3GPP AAA Server + Note left of UE: + UE->>HA: 1. Binding Update + HA-->>UE: 2. Binding Acknowledgement + Note left of HA: + UE->>HA: 3. IKEv2 Security Association tear down + HA-->>UE: + Note right of HA: + HA->>3GPP_AAA_Proxy: + 3GPP_AAA_Proxy->>3GPP_AAA_Server: + Note right of 3GPP_AAA_Server: + 3GPP_AAA_Server-->>3GPP_AAA_Proxy: + 3GPP_AAA_Proxy-->>HA: 4. H2 session termination + HA-->>UE: +``` + +The diagram illustrates the UE Initiated Detach Procedure. It involves four main steps: 1. Binding Update (UE to HA), 2. Binding Acknowledgement (HA to UE), 3. IKEv2 Security Association tear down (UE to HA), and 4. H2 session termination (HA to 3GPP AAA Proxy, then to 3GPP AAA Server, and back to HA). The HA interacts with the 3GPP AAA infrastructure to tear down the H2 session. + +Sequence diagram of UE Initiated Detach Procedure + +Figure 6.2-1: UE Initiated Detach Procedure + +1. If a Binding exists, the UE sends the DSMIPv6 Binding Update message to the HA as specified in RFC 5555 [7]. UE indicates Binding Lifetime as 0. The HA processes the Binding Update. During the processing the HA performs local authentication and authorization of the message using the existing IPsec security association. +2. The HA sends the DSMIPv6 Binding Ack to the UE. +3. UE triggers the tear down of the security association between UE and HA using IKEv2, RFC 5996 [9]. The HA acknowledges the security association removal. +4. The HA communicates with the AAA infrastructure in order to tear down the H2 session (unless needed to be maintained for other purposes). + +In this step, the HA may be either in the HPLMN or in the VPLMN. When the HA is in the VPLMN, the interaction between the HA in the VPLMN with the AAA/HSS in the HPLMN may involve a 3GPP AAA Proxy in the VPLMN as specified in TS 23.234 [2]. + +### 6.2.2 HA Initiated Detach + +The detach procedure when initiated by the HA is illustrated below. + +![Sequence diagram for HA Initiated Detach Procedure](69edc2887e907309499ac95b47ab6905_img.jpg) + +A sequence diagram illustrating the HA Initiated Detach Procedure. The participants are UE, HA, 3GPP AAA proxy, and 3GPP AAA server. The sequence of messages is as follows: 1. Detach Request (HA to UE), 2. Detach Acknowledgement (UE to HA), 3. IKEv2 Security Association tear down (UE to HA), and 4. H2 session termination (HA to 3GPP AAA server via the 3GPP AAA proxy). + +``` +sequenceDiagram + participant UE + participant HA + participant 3GPP AAA proxy + participant 3GPP AAA server + Note left of UE: + HA->>UE: 1. Detach Request + UE-->>HA: 2. Detach Acknowledgement + Note right of HA: + UE->>HA: 3. IKEv2 Security Association tear down + HA->>3GPP AAA server: 4. H2 session termination + Note right of 3GPP AAA server: +``` + +Sequence diagram for HA Initiated Detach Procedure + +**Figure 6.2-2: HA Initiated Detach Procedure** + +1. In the explicit detach procedure the HA shall send a detach request message as specified. In the implicit detach procedure this step is omitted. +2. In the explicit detach procedure, the UE shall acknowledge the detach request. In the implicit detach procedure this step is omitted. + +NOTE: How the detach request and acknowledge messages are implemented is a stage 3 detail. + +3. UE triggers the tear down of the security association between UE and HA using IKEv2, RFC 5996 [9]. The HA acknowledges the security association removal. +4. The HA communicates with the AAA infrastructure in order to tear down the H2 session (unless needed to be maintained for other purposes). + +In this step, the HA may be either in the HPLMN or in the VPLMN. When the HA is in the VPLMN, the interaction between the HA in the VPLMN with the AAA/HSS in the HPLMN may involve a 3GPP AAA Proxy in the VPLMN as specified in TS 23.234 [2]. + +### 6.2.3 AAA Initiated Detach + +The Detach procedure when initiated by the AAA is illustrated below. + +![Sequence diagram for AAA Initiated Detach Procedure](062ad684575a714449a7e040c0e1ec00_img.jpg) + +A sequence diagram illustrating the AAA Initiated Detach Procedure. The participants are UE, HA, 3GPP AAA proxy, and 3GPP AAA server. The sequence of messages is as follows: 1. Session termination (3GPP AAA server to HA via the 3GPP AAA proxy), followed by a large block labeled '2. HA Initiated Detach Procedure as in Figure 6.2-2' which encompasses the remaining steps of the procedure. + +``` +sequenceDiagram + participant UE + participant HA + participant 3GPP AAA proxy + participant 3GPP AAA server + Note left of UE: + 3GPP AAA server->>HA: 1. Session termination + Note right of HA: + Note right of UE: 2. HA Initiated Detach Procedure as in Figure 6.2-2 + Note right of 3GPP AAA server: +``` + +Sequence diagram for AAA Initiated Detach Procedure + +**Figure 6.2-3: AAA Initiated Detach Procedure** + +1. If the AAA wants to request the immediate termination of an H1 session for a given UE, it shall send a Session Termination message to the HA. In the roaming case signalling may be routed via a 3GPP AAA Proxy in the VPLMN. +2. The HA initiated detach procedure is performed as defined in clause 6.2.2, Figure 6.2-2. + +## 6.3 Handover + +### 6.3.1 H1 Reference Point Procedure + +This procedure is used to bind access specific Care-of Address with the Home Address. This procedure is performed to either refresh an existing binding or to change the binding from one Care-of Address to another when the Care-of Address changes e.g., due to movement between GPRS and I-WLAN. When this procedure is triggered it is assumed that the UE already has an IP address from the underlying IP access system. + +In this procedure it is assumed that the UE is already H1 PDN Attached. + +![Sequence diagram of the Binding Update Procedure between UE and HA.](6324b252294c0f5d4e34dad4a1202075_img.jpg) + +``` +sequenceDiagram + participant UE + participant HA + Note left of UE: + UE->>HA: 1. Binding Update + HA-->>UE: 2. Binding Acknowledgement + Note right of HA: +``` + +The diagram illustrates the interaction between a User Equipment (UE) and a Home Agent (HA). The UE sends a '1. Binding Update' message to the HA. The HA responds with a '2. Binding Acknowledgement' message back to the UE. Both entities are represented by rectangular boxes with vertical lines extending downwards, and there are small rectangular blocks at the bottom of these lines. + +Sequence diagram of the Binding Update Procedure between UE and HA. + +**Figure 6.3.1-1: Binding Update Procedure** + +1. The UE sends the DSMIPv6 Binding Update message to the HA as specified in RFC 5555 [7]. HA performs local authentication and authorization of the Binding Update message using the existing IPsec security association. The UE shall inform the HA that IP address preservation shall be maintained for the whole home network prefix. +2. The HA sends the DSMIPv6 Binding Ack to the UE as specified in RFC 5555 [7]. + +### 6.3.2 Handover Signalling Flows + +#### 6.3.2.1 Handover from 3GPP I-WLAN to 3GPP access + +The information flow represents a handover scenario from 3GPP I-WLAN access to 3GPP access for both the home mobility service and the visited mobility service cases (HSS and 3GPP AAA server are left out for simplicity). + +![Sequence diagram illustrating the handover process from 3GPP I-WLAN access to 3GPP access. The diagram shows five lifelines: UE, SGS N, PDG, GGSN, and HA. The process involves four steps: 1. UE discovers 3GPP access and initiates HO; 2. GPRS Attach/PDP context activation, establishing a GTP Tunnel between UE and GGSN; 3. UE sends a Binding Update to the HA; 4. HA sends a Binding Acknowledgement back to the UE.](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SGS_N as SGS N + participant PDG + participant GGSN + participant HA + + Note left of UE: 1. UE Discovers 3GPP access and initiates HO + Note over UE, GGSN: 2. GPRS Attach/PDP context activation + Note right of PDG: GTP Tunnel + UE->>HA: 3. Binding Update + HA-->>UE: 4. Binding Acknowledgement + +``` + +Sequence diagram illustrating the handover process from 3GPP I-WLAN access to 3GPP access. The diagram shows five lifelines: UE, SGS N, PDG, GGSN, and HA. The process involves four steps: 1. UE discovers 3GPP access and initiates HO; 2. GPRS Attach/PDP context activation, establishing a GTP Tunnel between UE and GGSN; 3. UE sends a Binding Update to the HA; 4. HA sends a Binding Acknowledgement back to the UE. + +**Figure 6.3.2.1-1: Handover from 3GPP I-WLAN access to 3GPP access** + +1. While connected over I-WLAN, the UE discovers the 3GPP GPRS coverage and determines to transfer its current sessions from the currently used 3GPP I-WLAN access to the discovered 3GPP access system. +2. The GPRS attach procedure including GGSN selection, IP address assignment to the UE, etc., is involved as specified in TS 23.060 [3]. The GTP tunnel between UE and GGSN is finally established and the UE can transfer data via 3GPP access. +3. The UE sends the DSMIPv6 Binding Update message to the HA as specified in RFC 5555 [7]. + - A. If the UE is on the home link, the UE sends a BU with LIFETIME==0. The UE shall inform the HA that IP address preservation shall be maintained for the whole home network prefix. + - B. If the UE is not on the home link, the UE sends a regular BU. The UE shall inform the HA that IP address preservation shall be maintained for the whole home network prefix. +4. The HA sends the DSMIPv6 Binding Ack to the UE as specified in RFC 5555 [7]. The DSMIPv6 tunnelling is modified accordingly. + +#### 6.3.2.2 Handover from 3GPP access to 3GPP I-WLAN access + +The information flow represents a handover scenario from 3GPP access to 3GPP I-WLAN access for both the home mobility service and the visited mobility service cases (HSS and 3GPP AAA server are left out for simplicity). + +![Sequence diagram illustrating the handover from 3GPP access to 3GPP I-WLAN access. The diagram shows four main entities: UE, PDG, GGSN, and HA. The sequence of events is: 1. UE discovers 3GPP I-WLAN access and initiates HO; 2. IPsec tunnel establishment between UE and PDG; 3. H1 PDN Attach or BU/BA between UE and HA, resulting in a DSMIPv6 tunnel between UE and HA.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PDG + participant GGSN + participant HA + Note left of UE: 1. UE Discovers 3GPP I-WLAN access and initiates HO + UE->>PDG: 2. IPsec tunnel establishment + Note over UE, PDG: IPsec Tunnel + Note right of HA: 3. H1 PDN Attach or BU/BA + Note over UE, HA: DSMIPv6 tunnel + +``` + +Sequence diagram illustrating the handover from 3GPP access to 3GPP I-WLAN access. The diagram shows four main entities: UE, PDG, GGSN, and HA. The sequence of events is: 1. UE discovers 3GPP I-WLAN access and initiates HO; 2. IPsec tunnel establishment between UE and PDG; 3. H1 PDN Attach or BU/BA between UE and HA, resulting in a DSMIPv6 tunnel between UE and HA. + +**Figure 6.3.2.2-1: Handover from 3GPP access to 3GPP I-WLAN access** + +1. The UE discovers the 3GPP I-WLAN coverage and determines to transfer its current sessions from the currently used 3GPP GPRS access to the discovered 3GPP I-WLAN access system. +2. The UE establishes an IPsec tunnel with PDG according to TS 23.234 [2]. +3. If H1 PDN attach is not already executed, UE triggers H1 PDN attach via I-WLAN. If H1 PDN attach is already executed the UE triggers a Binding Update via I-WLAN. The UE shall inform the HA that IP address preservation shall be maintained for the whole home network prefix. +4. As the result of H1 PDN attach or Binding Update, DSMIPv6 tunnel is established/re-established between UE and HA, and UE can transfer data via 3GPP I-WLAN access. + +## 6.4 Accounting + +H2 reference point supports transfer of accounting related information between the HA and 3GPP AAA infrastructure. The accounting related functionality in H2 reference point is based on accounting functionality for the Wa reference point specified in TS 23.234 [2]. + +As stated in the requirement section, It should be possible to perform charging differentiation based on radio access type the user is connected for collocated GGSN/HA and for separate GGSN and HA based architecture. The charging system may use the UE IP address to correlate the IP session between GPRS and I-WLAN and the NAS ID / NAS-IP address which correspond either to the GGSN or PDG or HA to derive the radio access type the user is connected to. + +NOTE: How the charging differentiation based on radio access type the user is implemented is a stage 3 detail. + +## 6.5 Interactions with Other Services + +When the UE moves between I-WLAN and GPRS network, as the same IP address is kept, there is no need to re-register with the IMS network. There is no impact to the IMS services. + +NOTE 1: A new registration to inform the network of changes of the access radio link (e.g. different capability) may be needed. In this case, because the P-CSCF has already been discovered in source access system, the re-registration in from the target access system is according to standard IMS registration. + +NOTE 2: Current P-CSCF discovery mechanisms described in TS 23.228 are re-used. + +## 6.6 IPv4 Home Address Release Procedure + +This procedure is initiated by the UE to release an IPv4 Home Address previously registered at the HA. + +![Sequence diagram of IPv4 Home Address Release Procedure between UE and HA.](d793cf7c174b89eb024d132f00679787_img.jpg) + +``` +sequenceDiagram + participant UE + participant HA + Note left of UE: + UE->>HA: 1. BU Lifetime=0, <Indication to delete IPv4 address only> + HA-->>UE: 2. Binding Acknowledgement + Note right of HA: +``` + +The diagram illustrates the IPv4 Home Address Release Procedure. It features two vertical lifelines: UE (User Equipment) on the left and HA (Home Agent) on the right. The interaction consists of two messages: 1. A Binding Update (BU) message from the UE to the HA, labeled "1. BU Lifetime=0, <Indication to delete IPv4 address only>". 2. A Binding Acknowledgement message from the HA back to the UE, labeled "2. Binding Acknowledgement". + +Sequence diagram of IPv4 Home Address Release Procedure between UE and HA. + +**Figure 6.6-1: IPv4 Home Address Release Procedure** + +1. The UE sends a Binding Update (IPv6 HoA, IPv4 HoA, lifetime=0, IPv4 only indication) message to the HA with lifetime value set to zero, indicating de-registration for the IPv4 Home Address only. The indication for IPv4 only informs the UE that only the IPv4 address from BCE is to be deleted. + +2. The PDN GW modifies the existing entry to delete the IPv4 home address implied in the Binding Update message from its Binding Cache and releases all associated resources, and then sends a Binding Ack (lifetime=0, IPv4 only indicator) message to the UE. + +# --- Annex A (Normative): EPS Migration Considerations + +Extension of the DSMIPv6 based inter-system mobility with additional functionality, such as PCRF interactions, requires deployment of EPS PDNGW, containing the HA functionality. EPS PDN GW and its interactions with other 3GPP system nodes are specified in TS 23.402 [6]. + +The intention is not to extend the introduced HA entity to support these additional release 8 functions of PDN GW. Thus enabling these additional functions requires migration to EPS. + +Figure A-1. illustrates a possible migration path to EPS. + + + +###### **Figure A-1: A possible migration to EPS** + +Reference point considerations: + +- The H1 should be a subset of S2c. +- The HGi should be a subset of SGi. + +- The H2 should be a subset of S6b. + +# Annex B (Normative): Information on implementation options + +## B.1 Co-located HA and GGSN functions + +It shall be possible to configure the GPRS access system as the DSMIPv6 "home link". In this case the IP address allocated to the UE by the GPRS system (as specified in TS 23.060 [3]) is used as the Home Address for DSMIPv6 and so, DSMIPv6 user plane encapsulation is not used over the GPRS system. + +### B.1.1 I-WLAN Mobility System Architecture with Co-located HA-GGSN + +The *I-WLAN mobility architecture* in integrated scenario refers to the case where the Home Agent function logically locates within the GGSN. + +The UE access the operator's PS Services via the radio interface labelled Um in A/Gb mode and Uu in Iu mode for mobile access. + +The UE access the operator PS Services via the radio interface labelled Ww for I-WLAN access. + +*PDP contexts each of them using one unique PDP address are independent to each other. The terminating access points of these different primary PDP contexts could be located in the same or in different GGSN/HA's.* + +![Diagram of I-WLAN Mobility System Architecture with Co-located HA-GGSN functions. The diagram shows a UE connected to a WLAN AN, UTRAN, and GERAN. The WLAN AN connects to a WAG via Wn, which then connects to a PDG via Wp. The UE also connects to the WAG via Ww and to the PDG via Wu. The PDG connects to a Packet Data Network via Gi. The PDG also connects to a HA/GGSN via H3. The HA/GGSN connects to a SGSN via Gn and to a Packet Data Network via Gi. The SGSN connects to the UE via Uu (UTRAN) and Um (GERAN). The SGSN also connects to a AAA Server via Gr, which in turn connects to an HSS via Wx. The HSS connects to the PDG via H2. The PDG also connects to the HSS via Wm.](72bc1a2b64dd6bac8285f560440c1218_img.jpg) + +``` + +graph TD + UE[UE] --- Wn[Wn] --- WLAN_AN((WLAN AN)) + UE --- Ww[Ww] --- WAG[WAG] + UE --- Wu[Wu] --- PDG[PDG] + WLAN_AN --- Wn + WAG --- Wp[Wp] --- PDG + PDG --- H3[H3] --- HA_GGSN[HA GGSN] + HA_GGSN --- Gn[Gn] --- SGSN[SGSN] + HA_GGSN --- Gi[Gi] --- PDN((Packet Data Network)) + SGSN --- Uu[Uu] --- UTRAN((UTRAN)) + SGSN --- Um[Um] --- GERAN((GERAN)) + SGSN --- Gr[Gr] --- AAA_Server[AAA Server] + AAA_Server --- Wx[Wx] --- HSS[HSS] + HSS --- H2[H2] --- PDG + PDG --- Wm[Wm] --- HSS + +``` + +Diagram of I-WLAN Mobility System Architecture with Co-located HA-GGSN functions. The diagram shows a UE connected to a WLAN AN, UTRAN, and GERAN. The WLAN AN connects to a WAG via Wn, which then connects to a PDG via Wp. The UE also connects to the WAG via Ww and to the PDG via Wu. The PDG connects to a Packet Data Network via Gi. The PDG also connects to a HA/GGSN via H3. The HA/GGSN connects to a SGSN via Gn and to a Packet Data Network via Gi. The SGSN connects to the UE via Uu (UTRAN) and Um (GERAN). The SGSN also connects to a AAA Server via Gr, which in turn connects to an HSS via Wx. The HSS connects to the PDG via H2. The PDG also connects to the HSS via Wm. + +**Figure B-1: Co-located HA and GGSN architecture** + +### B.1.2 Home Link Discovery for the Co-located HA and GGSN + +This section introduces the usage of Protocol Configuration Options (PCO) for the home link discovery when UE attaches to GPRS which is configured as UE's home link. If the home link information is available in the GGSN, the GGSN shall send the home link information to the UE in the PCO. The home link information includes the HA IP address and the HNP. + +### B.1.3 3GPP Attachment + +In the collocated GGSN/HA I-WLAN mobility architecture, the Mobile Node is in the home link in 2G/3G. In this case, it does not need to use mobile IP signalling and encapsulation and it will use the PDP Address as the Home Address (HoA). + +The 3GPP attachment procedure is unchanged. The 2G/3G network is assumed to be the home link therefore H1 PDN-Attach is not performed. + +The following procedure describes the attach procedure over 2G/3G for the GGSN and HA collocated scenario. + +![Sequence diagram showing PDP Context Activation with mobility. Lifelines: UE, SGSN, GGSN/HA, HLR/HSS, AAA DHCP. The process involves GPRS Attach, Authentication, Update Location, PDP Context Request, GGSN selection, and final activation response.](17b9d89b91e10c3efc38193baedee268_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SGSN + participant GGSN/HA + participant HLR/HSS + participant AAA_DHCP as AAA DHCP + + Note left of UE: 3. Activate PDP Context Request (APN) + UE->>SGSN: 1. GPRS Attach Request/Accept + SGSN->>HLR/HSS: 1. Authentication + SGSN->>HLR/HSS: 2. Update Location and Insert Subscriber Data + Note right of SGSN: 4. GGSN selection + SGSN->>GGSN/HA: 5. Create PDP Context Request (APN) + GGSN/HA->>AAA_DHCP: 6. AAA/DHCP Query/Response (PDP address) + AAA_DHCP-->>GGSN/HA: 7. Create PDP Context Response (PDP address == HoA) + GGSN/HA->>SGSN: 8. Activate PDP Context Response + Note left of UE: 3GPP access-specific data transmission + Note right of GGSN/HA: GTP tunnel + +``` + +Sequence diagram showing PDP Context Activation with mobility. Lifelines: UE, SGSN, GGSN/HA, HLR/HSS, AAA DHCP. The process involves GPRS Attach, Authentication, Update Location, PDP Context Request, GGSN selection, and final activation response. + +**Figure B-2: PDP Context Activation with mobility** + +1. The UE initiates the attach procedure at power on. The UE is authenticated and authorized to access the 2G/3G network according to TS 23.060 [3]. SGSN may interact with the HLR for Authentication. +2. The SGSN interacts with the HLR and updates the mobile node's location area as it is specified in TS 23.060 [3]. SGSN receives the Subscriber Data from HLR. + +3. The UE initiates the PDP context activation procedure as it is specified in TS 23.060 [3] to obtain the IP address. The Access Point Name (APN) specified by the service provider may be passed as a parameter. The UE shall leave the PDP Address empty to request a dynamic PDP address. +4. The SGSN performs the GGSN selection as it is specified in TS 23.060 [3]. +5. The SGSN requests the selected GGSN to set up a PDP context for the UE as it is specified in TS 23.060 [3]. +6. If the GGSN can assign an address for the UE locally, it assigns the address and the GGSN creates a TEID for the requested PDP context. Otherwise the GGSN uses External PDN Address Allocation mechanism as it is specified in TS 23.060 [3] and in TS 29.061 [13]. The GGSN obtain a PDP address from the PDN by means of protocols such as DHCP or RADIUS and creates a TEID for the requested PDP context. +7. The GGSN responds back to the SGSN, indicating completion of the PDP context activation procedure as it is specified in TS 23.060 [3]. The PDP address, which is sent back to the UE, is the Home Address. In addition to the GPRS specification TS 23.060 [3], if the Home Link information is available, the GGSN shall return the HA IP address and the HNP via the PCO to the UE. +8. The SGSN replies back to the UE as it is specified in TS 23.060 [3]. This signals completion of the PDP context activation and the IP address allocated corresponds also to its HoA. The UE stores the information for future use. + +NOTE 1: As the UE is on the home link, H1 PDN-Attach is not performed. How the UE detects that it is on the home link is described in Home link discovery section. + +NOTE 2: The HA address may be returned to the UE in PCO. + +### B.1.4 I-WLAN Attachment + +The UE powers on over I-WLAN and performs I-WLAN attach procedure according to TS 23.234 [2] and H1 PDN Attach to the HA according to this specification. The DSMIPv6 BU/BA to the Home Agent is triggered by the UE. + +**NOTE: How the UE discovers the HA is defined in HA discovery section (see clause 5.3.2 Home Agent Discovery).** + +![Sequence diagram for I-WLAN Attach with mobility service](54a53f959bb7758332532c1cd5f0ad75_img.jpg) + +The diagram shows a sequence of interactions between five entities: UE, WLAN AN, PDG, 3GPP AAA Server, and GGSN/HA. + 1. A 'WLAN connection' is established between UE and WLAN AN. + 2. 'I-WLAN Attach Tunnel establishment' occurs between UE and PDG, while 'Authentication Authorization' happens between PDG and 3GPP AAA Server. + An 'IPsec Tunnel' (yellow cylinder) is established between UE and PDG. + 3. 'HA Discovery' is performed by the UE (indicated by a dashed box). + 4. 'H1-PDN-Attach Procedure' occurs between UE and GGSN/HA. + Finally, data is routed by HA to UE's CoA via I-WLAN, represented by a 'Mobile IP tunnel inside an IPsec tunnel' (a light blue cylinder inside a larger grey/yellow structure) spanning from the UE to the GGSN/HA. + +Sequence diagram for I-WLAN Attach with mobility service + +**Figure B-3: I-WLAN Attach with mobility service** + +1. The WLAN UE selects a WLAN Access Network and establishes the WLAN connection with a WLAN technology specific procedure. The UE gets allocated a local IP address and optionally WLAN Access Authentication and Authorization which may depend on the home operator policy as well as the policy of the provider of the WLAN AN according to TS 23.234 [2]. +2. I-WLAN attachment and IPsec tunnel setup is executed according to TS 23.234 [2]. In addition to the procedure defined in TS 23.234 [2]. The PDG may return the HA address in IKEv2 configuration payload to the UE. +3. The method by which HA is known to the UE is defined in HA discovery clause 5.3.2 The UE must know the HA in order to perform BU/BA. This step is required only if HA address was not discovered via IKEv2 configuration payload in the previous steps. +4. H1 PDN-Attach procedure is performed as it is specified in clause 6.1. +5. The UE can send and receive packet. + +### B.1.5 Handover from 3GPP access to I-WLAN + +![Sequence diagram illustrating the handover from 3GPP access to I-WLAN. The diagram shows the interaction between UE, SGSN, PDG, GGSN/HA, and 3GPP AAA Server. The process involves: 1. GTP tunnel establishment between SGSN and GGSN/HA; 2. HO decision by the UE; 3. I-WLAN Attach, Tunnel establishment, CoA allocation by the UE to the PDG, and Authentication and Authorization by the UE to the 3GPP AAA Server; 4. IKEv2 Bootstrap between the UE and the GGSN/HA; 5. Binding Update from the UE to the GGSN/HA; 6. Binding Acknowledgement from the GGSN/HA to the UE; 7. Mobile IP tunnel inside an IPsec tunnel between the UE and the PDG; 8. Bearer Resource Release by the UE.](164d1b48231be457522b31965610ea3b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SGSN + participant PDG + participant GGSN/HA + participant 3GPP AAA Server + + Note right of SGSN: 3GPP access-specific data transmission + Note right of SGSN: 1. GTP tunnel + + Note left of UE: 2. HO decision + + UE->>PDG: 3. I-WLAN Attach, Tunnel establishment, CoA allocation + UE->>3GPP AAA Server: 3. Authentication and Authorization + Note right of UE: IPsec Tunnel + Note right of UE: 4. IKEv2 Bootstrap + UE->>GGSN/HA: 5. Binding Update + GGSN/HA->>UE: 6. Binding Acknowledgement + Note right of PDG: Data routed by HA to UE's CoA via I-WLAN + Note right of UE: 7. Mobile IP tunnel inside an IPsec tunnel + Note left of UE: 8. Bearer Resource Release + +``` + +Sequence diagram illustrating the handover from 3GPP access to I-WLAN. The diagram shows the interaction between UE, SGSN, PDG, GGSN/HA, and 3GPP AAA Server. The process involves: 1. GTP tunnel establishment between SGSN and GGSN/HA; 2. HO decision by the UE; 3. I-WLAN Attach, Tunnel establishment, CoA allocation by the UE to the PDG, and Authentication and Authorization by the UE to the 3GPP AAA Server; 4. IKEv2 Bootstrap between the UE and the GGSN/HA; 5. Binding Update from the UE to the GGSN/HA; 6. Binding Acknowledgement from the GGSN/HA to the UE; 7. Mobile IP tunnel inside an IPsec tunnel between the UE and the PDG; 8. Bearer Resource Release by the UE. + +**Figure B-4: Handover from 3GPP access to I-WLAN** + +1. The precondition of this flow is that the UE is attached to a 3GPP access and has active PDP context(s) with a GGSN/HA node. There is a GTP tunnel between the SGSN and the GGSN. +2. The UE needs to handover to a WLAN access network. The HO decision mechanism could be based on local policy in the UE. +3. I-WLAN attachment and IPsec tunnel setup is executed according to TS 23.234 [2]. In addition to the procedure defined in TS 23.234 [2] the UE may also obtain the Home Agent information via IKEv2 configuration payload if not already available in the UE. +4. The UE perform IKEv2/IPsec security association setup procedure with the Home Agent for DSMIPv6. +5. The UE sends a binding update to its home agent to update the binding cache entry at the home agent. The UE will use its IP address used in 3GPP access as its Home Address. This address will be preserved unless further indication from the 3GPP access. The UE uses the address configured from the PDG as the care-of address. The care-of address may be an IPv4 or IPv6 address. + +6. The Home Agent responds with a binding acknowledgement if the binding update process was successful. The Home Agent also creates the binding cache entry with the new care-of address of the UE. In this message, the HA also includes the APN corresponding to the home link for the UE to store. +7. The successful exchange of binding update and binding acknowledgement results in a Mobile IP tunnel between the UE and the home agent over the IPsec tunnel between the UE and the PDG. Data packets are now routed by Home Agent to UE's Care-of-Address via I-WLAN. +8. During this procedure, bearer resources reserved for the UE are released. + +### B.1.6 Handover from I-WLAN to 3GPP Access + +The handover may take place when the source network is no longer able to provide the required user-to-PDN connection service or based on operator policies. + +![Sequence diagram illustrating the handover from I-WLAN to 3GPP Access. The diagram shows the interaction between UE, SGSN, PDG, GGSN/H A, and 3GPP AAA Server. It details the steps from data routing over I-WLAN to the activation of a GTP tunnel over 3GPP access.](2df09d249c38abee55dbf0526dd6da0a_img.jpg) + +The diagram illustrates the sequence of events for a handover from I-WLAN to 3GPP Access. The participants are UE, SGSN, PDG, GGSN/H A, and 3GPP AAA Server. The process starts with data being routed by the Home Agent (HA) to the UE's Care-of Address (CoA) via I-WLAN. A Mobile IP tunnel inside an IPsec tunnel is established between the UE and the PDG. The UE then makes a handover decision and attaches to the 3GPP Access. This triggers a PDP Context Activation Service Request from the SGSN to the GGSN/H A. The GGSN/H A performs AAA interactions with the 3GPP AAA Server. The UE sends a Binding Update (Lifetime = 0) to the GGSN/H A, which responds with a Binding Acknowledgement. This is followed by 3GPP access-specific data transmission and a GTP tunnel is established between the SGSN and the GGSN/H A. Finally, a Bearer Resource Release is initiated by the UE. + +``` + +sequenceDiagram + participant UE + participant SGSN + participant PDG + participant GGSN/H A + participant 3GPP AAA Server + + Note over UE, GGSN/H A: Data routed by HA to UE's CoA via I-WLAN + Note over UE, PDG: 1. Mobile IP tunnel inside an IPsec tunnel + Note left of UE: 2. HO Decision. Attach to 3GPP Access + Note over SGSN, GGSN/H A: 3. PDP Context Activation Service Request + Note over GGSN/H A, 3GPP AAA Server: 4. AAA interactions + Note over UE, GGSN/H A: 5. Binding Update (Lifetime = 0) + Note over GGSN/H A, UE: 6. Binding Acknowledgement + Note over UE, GGSN/H A: 3GPP access-specific data transmission + Note over SGSN, GGSN/H A: 7. GTP tunnel + Note left of UE: 8. Bearer Resource Release + +``` + +Sequence diagram illustrating the handover from I-WLAN to 3GPP Access. The diagram shows the interaction between UE, SGSN, PDG, GGSN/H A, and 3GPP AAA Server. It details the steps from data routing over I-WLAN to the activation of a GTP tunnel over 3GPP access. + +**Figure B-5: Handover from I-WLAN to 3GPP Access** + +1. The precondition of this flow is that the UE is attached over I-WLAN with mobility support. There is a Mobile IP tunnel between the UE and the Home Agent over an IPsec tunnel between the UE and the PDG. +2. The UE may need to handover to 3GPP access network because I-WLAN is no longer able to provide the required user-to-PDN connection service or based on operator policies. The UE attaches to 3GPP access according to TS 23.060 [3]. + +In order to generate an APN to be used when activating a PDP context in the GPRS access, the UE uses the APN information received in the BA during H1 PDN attach as described in clause 1.6. If no APN is received in the + +Binding Acknowledgement message during H1 PDN attach, the UE shall use the pre-configured APN, if available + +3. The UE initiates PDP context setup according to TS 23.060 [3]. The UE provides an APN corresponding to the combined GGSN/HA used in the source access. This results in a PDP context setup with a GTP tunnel between the SGSN and the GGSN. GGSN returns a PDP address to the UE which is same as the HoA the UE used in WLAN access in step 1. In case of IPv6, the prefix associated with the PDP context is the same as the one for HoA (i.e. HNP). +4. The GGSN/HA interacts with the AAA server for mobility service authentication and authorization according to TS 29.061 [13]. +5. The UE detects that the HoA and the PDP address are same, so the UE considers itself in home link. The UE sends a Binding Update to its home agent with lifetime=0, and CoA=HoA to delete the binding cache entry at the home agent. +6. The Home Agent responds with a Binding Acknowledgement if the binding update process (binding deletion) was successful. +7. With the Binding Update and binding acknowledgement exchange the HA recognizes that the UE has returned home and deletes the binding cache. There is no Mobile IP tunnel between the UE and the home agent however a GTP tunnel is established between the SGSN and the GGSN. +8. Bearer Resources on the I-WLAN access system are released according to TS 23.234 [2]. For that the UE detaches from I-WLAN if it has not happened before. + +## --- B.2 Co-located HA and PDG functions + +It shall be possible to co-locate the HA and PDG. The GERAN/UTRAN may still acts as the home link. In this case the IP address allocated to the UE by the GPRS system is used as HoA for DSMIPv6. + +### B.2.1 H1 PDN Attach + +The H1- PDN Attach procedure for co-located PDG and HA is based on the attach procedure described in clause 6.1. When attached to the co-located PDG+HA, the UE may be on the home link. How the UE finds it's in the home link is described in clause 5.3.3 Home Link Detection. + +# Annex C (Informative): Change History + +| Change history | | | | | | | | | +|----------------|-------|-----------|------|-----|-----|------------------------------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 2008-06 | SP-40 | SP-080358 | - | - | - | Approved at TSG SA#40 and updated to version 8.0.0 | 1.0.0 | 8.0.0 | +| 2008-09 | SP-41 | SP-080577 | 0001 | 1 | F | Essential corrections for TS 23.327 | 8.0.0 | 8.1.0 | +| 2008-09 | SP-41 | SP-080577 | 0002 | 1 | F | Correction and Cleanup to IWLan Mobility TS 23.327 | 8.0.0 | 8.1.0 | +| 2008-09 | SP-41 | SP-080577 | 0003 | - | F | Correction and Cleanup of Annex A – IWLan Mobility TS 23.327 | 8.0.0 | 8.1.0 | +| 2008-09 | SP-41 | SP-080577 | 0004 | 1 | F | Correction and Cleanup of Annex B – IWLan Mob | 8.0.0 | 8.1.0 | +| 2008-12 | SP-42 | SP-080810 | 0005 | - | F | APN in IDr payload | 8.1.0 | 8.2.0 | +| 2008-12 | SP-42 | SP-080810 | 0006 | 1 | F | APN discovery for HO to GPRS | 8.1.0 | 8.2.0 | +| 2008-12 | SP-42 | SP-080810 | 0007 | 1 | F | Alignment of PDN address handling for H1 | 8.1.0 | 8.2.0 | +| 2008-12 | SP-42 | SP-080810 | 0008 | 1 | F | IPv4 Home Address release procedure for H1 | 8.1.0 | 8.2.0 | +| 2008-12 | SP-42 | SP-080810 | 0010 | 3 | F | I-WLAN Mobility- cleanups | 8.1.0 | 8.2.0 | +| 2009-01 | | | | | | LTE logo and keyword removed | 8.2.0 | 8.2.1 | +| 2009-01 | | | | | | Typo in previous entry of history box corrected | 8.2.1 | 8.2.2 | +| 2009-03 | SP-43 | SP-090125 | 0011 | 1 | F | Cleanup for using PCO to obtain the homelink information when GGSN and HA are co-located | 8.2.2 | 8.3.0 | +| 2009-09 | SP-45 | SP-090581 | 0015 | 1 | F | Reference correction for S2c | 8.3.0 | 8.4.0 | +| 2009-12 | SP-46 | - | - | - | - | Update to Rel-9 version (MCC) | 8.4.0 | 9.0.0 | +| 2011-03 | SP-51 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-03 | SP-55 | SP-120088 | 0022 | - | C | Update of reference to obsolete IETF RFCs | 10.0.0 | <b>11.0.0</b> | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23380/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Rel-11/23_series/23380/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14da12e15a420197c7c99d2356d76f0b2d04a997 --- /dev/null +++ b/marked/Rel-11/23_series/23380/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaebd23e69ce49dedbc176ee08fb1627956514814215ec08ebed4653b03e876d +size 41839 diff --git a/marked/Rel-11/23_series/23380/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-11/23_series/23380/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fddf2986c8a1c6e0adc04d883ce1d058eb9744d6 --- /dev/null +++ b/marked/Rel-11/23_series/23380/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c42a801f56730ab5cc299f82bf8aeac725fba08b07b331e93ac8b8be3cca4593 +size 99593 diff --git a/marked/Rel-11/23_series/23380/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-11/23_series/23380/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3acc240d81b0b131c7057e7bd84c8fbd0c47181 --- /dev/null +++ b/marked/Rel-11/23_series/23380/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ae28510b11a04e47315a8d0c28944025bdb43ce1f3efdb83b1e08abbb384f9e +size 95888 diff --git a/marked/Rel-11/23_series/23380/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-11/23_series/23380/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c5d1b499b2fde5f7b2b7bf2f110f153b956cdda --- /dev/null +++ b/marked/Rel-11/23_series/23380/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1ba7c7ae17727e6148c48dca97b2b6b291d2c571977ca57b6fbed9b8d456fd3 +size 89696 diff --git a/marked/Rel-11/23_series/23380/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/23_series/23380/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7cb3a6282150ec674a509c067e023357fb020a5 --- /dev/null +++ b/marked/Rel-11/23_series/23380/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62efb7572e9b0bad23673f2d64481dea5d30d3f02bcac2ab6b3d012a0c57deec +size 123748 diff --git a/marked/Rel-11/23_series/23380/raw.md b/marked/Rel-11/23_series/23380/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2c3b8018e02d8a6d0baf07f208e8b97b764bf398 --- /dev/null +++ b/marked/Rel-11/23_series/23380/raw.md @@ -0,0 +1,532 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Restoration of Data in the S-CSCF ..... | 6 | +| 4.1 General ..... | 6 | +| 4.2 Registration Procedure ..... | 6 | +| 4.2.1 Introduction ..... | 6 | +| 4.2.2 S-CSCF Restoration after Failure..... | 6 | +| 4.2.3 S-CSCF Restoration during Registration Process ..... | 7 | +| 4.3 UE Terminating Procedure..... | 7 | +| 4.3.1 Introduction ..... | 7 | +| 4.3.2 S-CSCF Restoration after Restart..... | 7 | +| 4.3.3 S-CSCF Restoration after Failure..... | 8 | +| 4.4 UE Originating Procedure ..... | 8 | +| 4.4.1 Introduction ..... | 8 | +| 4.4.2 S-CSCF Restoration after Restart..... | 8 | +| 4.4.3 S-CSCF Restoration after Failure..... | 9 | +| 4.5 SIP-AS Originating Procedure ..... | 9 | +| 4.5.1 Introduction ..... | 9 | +| 4.5.2 S-CSCF Restoration after Restart..... | 9 | +| 4.5.3 S-CSCF Restoration after Failure..... | 9 | +| 4.6 S-CSCF Data Restoration Information Backup and Update Procedures ..... | 10 | +| 4.6.1 Introduction ..... | 10 | +| 4.6.2 Backup and Update of S-CSCF Restoration Information during Registration Process ..... | 10 | +| 4.6.3 Backup and Update of S-CSCF Restoration Information after UE's Subscription..... | 10 | +| 5 Recovery after P-CSCF failure ..... | 11 | +| 5.0 General ..... | 11 | +| 5.1 Update PDP context/Bearer at P-CSCF failure..... | 11 | +| 5.1.1 General requirements..... | 11 | +| 5.1.2 Network recovery information flow - Update PDP context / Bearer ..... | 11 | +| 5.1.3 Network recovery information flow with S5 PMIP ..... | 13 | +| 5.2 Inform UE about P-CSCF failure..... | 14 | +| 5.2.1 General requirements..... | 14 | +| 5.2.2 Network recovery information flow – Inform UE at P-CSCF failure..... | 14 | +| 5.2.3 Network recovery information flow – Inform UE at P-CSCF failure with S5 PMIP ..... | 16 | +| 5.3 Network recovery information flow – UE uses keep alive mechanism ..... | 17 | +| Annex A (informative): Change history..... | 18 | + +# --- Foreword + +This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +Although network nodes in the IMS Core Network should have a very high availability, some maintenance downtime and occasional failures are unavoidable. Communication links although designed with robust protocols between the network elements are also subject to failures. This document specifies a set of standardized procedures for automatic restoration after loss or corruption of data reducing the impact of these problems in order to improve service to the users. The scenarios covered here for the IMS Domain are similar to those covered in 3GPP TS 23.007 [2] for the CS and PS Domains. + +# --- 1 Scope + +The present document specifies the procedures required in 3GPP IMS to handle a S-CSCF service interruption scenario with minimum impact to the service to the end user. + +NOTE: IMS Restoration Procedures covering service interruption of other network elements are not defined in this version of the specification. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.007: "Restoration procedures". +- [3] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and message contents". +- [4] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification". +- [5] 3GPP TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping". +- [6] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [7] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point". +- [8] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface". +- [9] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)". +- [10] 3GPP TS 29.274: "3GPP Evolved Packet System. Evolved GPRS Tunnelling Protocol for EPS (GTPv2)". +- [11] IETF RFC 3361: "Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers". +- [12] IETF RFC 1034: "Session Initiation Protocol (SIP): Locating SIP Servers". +- [13] IETF RFC 3319: "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers". +- [14] IETF RFC 6223: "Indication of Support for Keep-Alive". +- [15] 3GPP TS 29.275: "Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3". +- [16] IETF RFC 7077: "Update Notifications for Proxy Mobile IPv6". +- [17] 3GPP TS 23.401: "GPRS Enhancements for E-UTRAN Access". + +# --- 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]. + +**Service Interruption:** A period of time in which one or more network elements do not respond to requests and do not send any requests to the rest of the system. + +**S-CSCF Restoration Information:** Information required for the S-CSCF to handle traffic for a registered user. This information is stored in HSS and if lost, retrieved by the S-CSCF. + +## 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]. + +| | | +|-----|------------------------------| +| LIR | Location Information Request | +| LIA | Location Information Answer | +| SAR | Server Assignment Request | +| SAA | Server Assignment Answer | +| UAR | User Authorization Request | +| UAA | User Authorization Answer | + +# --- 4 Restoration of Data in the S-CSCF + +## 4.1 General + +The following clauses describe the IMS Restoration Procedures for the S-CSCF service interruption in each of the scenarios where they apply. + +## 4.2 Registration Procedure + +### 4.2.1 Introduction + +The following clauses specify the behaviour of HSS and S-CSCF if they support the IMS restoration feature. + +### 4.2.2 S-CSCF Restoration after Failure + +If the UE initiates a SIP REGISTER and the S-CSCF returned by the HSS during user registration status query procedure fails, the I-CSCF is unable to contact the S-CSCF. In this case, regardless of this registration is an initial registration, a re-registration or a de-registration, the I-CSCF shall send UAR with Authorization Type set to REGISTRATION\_AND\_CAPABILITIES to the HSS to explicitly request S-CSCF capabilities. After re-assignment of another S-CSCF according to the S-CSCF capabilities, the I-CSCF shall forward the REGISTER to the new S-CSCF. For registrations and re-registrations, S-CSCF shall proceed with the registration procedure as for initial registration, except for the clauses specified in 4.2.3. + +For de-registrations, S-CSCF shall proceed as for user-initiated de-registration. + +### 4.2.3 S-CSCF Restoration during Registration Process + +During the registration procedure, the HSS shall send all the registered Private User Identities sharing the same Public User Identity which is being registered in the SAA, in addition to the basic user data to the S-CSCF. Then the S-CSCF compares the registered Private User Identities received from the HSS with the ones it stores. If there are any registered Private User Identities the S-CSCF does not have their registration data, the S-CSCF shall send SAR with Server Assignment Type set to NO\_ASSIGNMENT to the HSS to retrieve the S-CSCF restoration information for the registered Public User Identity. If there are S-CSCF restoration information related to the Public User Identity stored in + +the HSS, the HSS shall send the S-CSCF restoration information together with the user profile in the SAA to the S-CSCF. The result code shall be set to DIAMETER\_SUCCESS. + +If there are more than one group of S-CSCF restoration information related to the Public User Identity stored in the HSS, which may happen if the Public User Identity is shared by multiple Private User Identities, the HSS shall include all of the S-CSCF restoration information in the SAA. One group of S-CSCF restoration information corresponds to one Private User Identity. + +If the S-CSCF receives an initial registration request for a Public User Identity that does not match any Public User Identity currently registered with the same Private User Identity as in the request at this S-CSCF, the S-CSCF shall check whether there is a reg-id parameter in the Contact header in the SIP REGISTER message and whether there is an "sos" SIP URI parameter in the SIP REGISTER message. Only when a reg-id parameter exists and an "sos" SIP URI parameter does not exist, the S-CSCF shall indicate to the HSS that the registration is related to a multiple registration. + +If the HSS receives an SAR request with multiple registration indication, and the Public User Identity is stored as registered in the HSS, and there is restoration information related to the Private User Identity, the HSS shall not overwrite stored restoration information, instead, it shall send the stored S-CSCF restoration information together with the user profile in the SAA. The result code shall be set to DIAMETER\_ERROR\_IN\_ASSIGNMENT\_TYPE. The S-CSCF shall send a new SAR with Server-Assignment-Type set to RE\_REGISTRATION and the User Data Already Available parameter set to USER\_DATA\_ALREADY\_AVAILABLE to update the restoration information in the HSS in accordance to the current registration event. + +If the S-CSCF receives a user-initiated deregistration request for a Public User Identity that does not match any Public User Identity currently registered with the same Private User Identity as in the request at this S-CSCF, the S-CSCF shall check whether there is a reg-id parameter in the Contact header in the received SIP REGISTER message, + +- if a reg-id parameter exists, the S-CSCF shall: + 1. Send SAR with Server-Assignment-Type set to NO\_ASSIGNMENT to retrieve the S-CSCF restoration information associated with the Public User Identity. The Result-Code shall be set to DIAMETER\_SUCCESS. + 2. Compare the contact address(es) received in SAA with the contact address(es) in REGISTER request: + - If they are not the same, the S-CSCF shall send SAR with Server-Assignment-Type set to RE\_REGISTRATION to update the S-CSCF restoration information in HSS with the Contact address(es) still associated with the Public User Identity after the deregistration event. + +Otherwise, the S-CSCF shall send SAR with Server-Assignment-Type set to USER\_DEREGISTRATION. + +## 4.3 UE Terminating Procedure + +### 4.3.1 Introduction + +The following clauses specify the behaviour of HSS, I-CSCF and S-CSCF if they support the IMS Restoration feature. + +### 4.3.2 S-CSCF Restoration after Restart + +The S-CSCF lost all user data if it restarts after a failure or it is unable to trust any data after it resumes operation, due to the fact that it may have lost profile updates from the HSS in the service interruption period. If such a S-CSCF receives a terminating service request from the I-CSCF, it sends an SAR to the HSS for unregistered service data. In this case, HSS and S-CSCF proceed as indicated in 3GPP TS 29.228 [3], except that + +- if the Public User Identity is stored as registered in the HSS, and there are S-CSCF restoration information related to the Public User Identity stored in the HSS, the HSS shall send the S-CSCF restoration information together with the user profile in the SAA. The result code shall be set to DIAMETER\_ERROR\_IN\_ASSIGNMENT\_TYPE. The S-CSCF shall trigger matched registered services for the Public User Identity. + +If there are more than one group of S-CSCF restoration information related to the Public User Identity, which may happen if the Public User Identity is shared by multiple Private User Identities, the HSS shall include all of the S-CSCF restoration information in the SAA. One group of S-CSCF restoration information corresponds to one Private User Identity. + +If the S-CSCF restoration information received includes the UE's subscription information, the S-CSCF shall construct a NOTIFY message according to the information and send it to the UE (or UEs if the IMPU is shared between several IMPIs) to trigger a new registration at anytime after normal processing of the terminating request. + +### 4.3.3 S-CSCF Restoration after Failure + +If the S-CSCF returned by the HSS during location query procedure fails, the I-CSCF is unable to contact the S-CSCF during terminating procedure. In this case, the I-CSCF shall send LIR to the HSS to explicitly request S-CSCF capabilities. If the HSS returns the S-CSCF capabilities to the I-CSCF, after re-selection of another S-CSCF according to the S-CSCF capabilities, the I-CSCF shall forward the service request to the new S-CSCF. The HSS and this new S-CSCF shall behave as described in clause 4.3.2, except that the HSS shall overwrite the S-CSCF name when receiving the SAR request, only if there is a previous explicit LIR request for S-CSCF capabilities. + +NOTE: If the HSS indicates during location query procedure that the server name returned corresponds to an AS, then the service request is for PSI direct routing. In this case, IMS Restoration Procedures will not be executed and I-CSCF will reject the service request. + +## 4.4 UE Originating Procedure + +### 4.4.1 Introduction + +The following clauses specify the behaviour of HSS, S-CSCF and P-CSCF if they support the IMS Restoration feature. + +### 4.4.2 S-CSCF Restoration after Restart + +The S-CSCF lost all user data if it restarts after a failure or it is unable to trust any data after it resumes operation, due to the fact that it may have lost profile updates from the HSS in the service interruption period. If such a S-CSCF receives an originating request different from SIP REGISTER coming from the UE, the S-CSCF shall send SAR to the HSS with Server Assignment Type set to NO\_ASSIGNMENT to restore the user data. If the S-CSCF name sent in the Server-Assignment-Request command and the previously assigned S-CSCF name stored in the HSS are different, which may happen if S-CSCF reassignment occurred during a terminating restoration before, the HSS shall not overwrite the S-CSCF name; instead it shall send a response to the S-CSCF with result code set to DIAMETER\_UNABLE\_TO\_COMPLY, as specified in the 3GPP TS 29.228 [3]. If there are S-CSCF restoration information related to the Public User Identity stored in the HSS, the HSS shall send the S-CSCF restoration information together with the user profile in the SAA to the S-CSCF. If the HSS returns an error DIAMETER\_UNABLE\_TO\_COMPLY to the S-CSCF, the S-CSCF shall then return a specific error response to the UE to trigger a new registration. + +If there are more than one group of S-CSCF restoration information related to the Public User Identity stored in the HSS, which may happen if the Public User Identity is shared by multiple Private User Identities, the HSS shall include all of the S-CSCF restoration information in the SAA. One group of S-CSCF restoration information corresponds to one Private User Identity. + +If authentication of SIP request methods initiated by the UE excluding REGISTER is desired according to operator's policy, for other authentication schemes different from IMS-AKA, the S-CSCF requires authentication information (e.g. authentication vectors). If this information is not stored in the S-CSCF, the S-CSCF shall fetch that information from the HSS by means of the authentication procedures (Cx-MAR/MAA). + +NOTE 1: The S-CSCF restoration information includes authentication scheme information (SIP-Authentication-Scheme). It allows the S-CSCF to identify the corresponding scheme for authentication when multiple schemes are supported. + +NOTE 2: The authentication information (e.g. authentication vectors) was retrieved by the S-CSCF from the HSS for the authentication of REGISTER requests and it can be stored locally. This data may be lost after the S-CSCF restart. + +If the S-CSCF receives SAA with the service profile of the user, the S-CSCF shall continue the originating service as normal. + +If the S-CSCF receives SAA with S-CSCF restoration information and the S-CSCF restoration information includes the UE's subscription information, the S-CSCF shall construct a NOTIFY message according to the information and send it to the UE (or UEs if the IMPU is shared between several IMPIs) to trigger a new registration at anytime after normal processing of the originating request. + +### 4.4.3 S-CSCF Restoration after Failure + +If the UE initiates an originating service request different from SIP REGISTER and the P-CSCF is unable to contact the S-CSCF in the Route, the P-CSCF shall return a specific error response to the UE to trigger a new registration. + +## 4.5 SIP-AS Originating Procedure + +### 4.5.1 Introduction + +The following clauses specify the behaviour of HSS, I-CSCF and S-CSCF if they support the IMS Restoration feature. + +### 4.5.2 S-CSCF Restoration after Restart + +The S-CSCF lost all user data if it restarts after a failure or it is unable to trust any data after it resumes operation, due to the fact that it may have lost profile updates from the HSS in the service interruption period. If such S-CSCF receives an originating request on behalf of a user (i.e. top-most route header in request contains "orig" parameter) coming from an AS, the S-CSCF shall send SAR to the HSS with Server Assignment Type set to UNREGISTERED\_USER to inform the HSS that the user is unregistered. HSS and S-CSCF proceed as indicated in 3GPP TS 29.228 [3], except that: + +- if the Public User Identity is stored as registered in the HSS, and there is S-CSCF restoration information related to the Public User Identity stored in the HSS, the HSS shall send the S-CSCF restoration information together with the user profile in the SAA. The result code shall be set to DIAMETER\_ERROR\_IN\_ASSIGNMENT\_TYPE. The S-CSCF shall trigger matched originating services for the Public User Identity. if the Public User Identity is stored as registered in the HSS, and there is no S-CSCF restoration information related to the Public User Identity stored in the HSS, the HSS shall send the user profile in the SAA and set the registration state for the Public Identity to unregistered. The result code shall be set to DIAMETER\_SUCCESS. The S-CSCF shall trigger matched originating unregistered services for the Public User Identity. +- if the S-CSCF name sent in the Server-Assignment-Request command and the previously assigned S-CSCF name stored in the HSS are different, the HSS shall not overwrite the S-CSCF name. Result Code will be DIAMETER\_IDENTITY\_ALREADY\_REGISTERED. The S-CSCF shall return a specific error response to AS. The AS shall resend the request to the I-CSCF. + +NOTE: The address of the S-CSCF can be obtained by AS either by querying the HSS on the Sh interface or during third-party registration. It may happen that if AS is using third party registration and a reassignment occurred during a terminating request, AS will have the wrong S-CSCF name. + +### 4.5.3 S-CSCF Restoration after Failure + +If the application server sends the originating service request on behalf of the user to the S-CSCF, and the S-CSCF can not be contacted, after timeout, the application server shall resend the originating service request to the I-CSCF. + +If the application server sends the originating service request directly to the I-CSCF, or resends the originating service request to the I-CSCF due to the S-CSCF can not be contacted, the I-CSCF shall behave as in section 4.3.3. The S-CSCF and HSS shall behave as in section 4.5.2, except that the HSS shall overwrite the S-CSCF name when receiving the SAR request, only if there is a previous explicit LIR request for S-CSCF capabilities. + +## 4.6 S-CSCF Data Restoration Information Backup and Update Procedures + +### 4.6.1 Introduction + +The following clauses specify the behaviour of HSS and S-CSCF if they support the IMS Restoration feature. + +### 4.6.2 Backup and Update of S-CSCF Restoration Information during Registration Process + +The S-CSCF shall backup the following data in the HSS during the initial registration process. + +- the list of SIP proxies in the path (normally it would be just the P-CSCF address) + +- the Contact Information (Contact Addresses and Contact Header parameters) +- the Authentication Information (SIP-Authentication-Scheme) + +This is done with an additional information element in the SAR requesting user information, in addition to the basic set of information required to handle traffic, as specified in the 3GPP TS 29.228 [3]. The information is associated with the Private User Identity and the Implicit Registration Set that is affected by the SAR request. The HSS shall store this information. + +If any of the above data is changed, the S-CSCF shall update it in the HSS using SAR request with Server-Assignment-Type set to RE\_REGISTRATION and the User Data Already Available parameter set to USER\_DATA\_ALREADY\_AVAILABLE, as specified in the 3GPP TS 29.228 [3]. + +### 4.6.3 Backup and Update of S-CSCF Restoration Information after UE's Subscription + +If the S-CSCF receives the UE's subscription to notification of the reg-event for the first time, the S-CSCF shall send an SAR to the HSS to store the following UE's subscription information. + +- Call-ID, From, To, Record-Route, Contact + +To avoid frequent storing of the subscription information in the HSS, the CSeq should not be included in the S-CSCF restoration information. Instead, the CSCF shall ensure that subsequent notification after retrieving this data includes a sufficiently large Cseq value so that the UE is able to accept it. + +This is done with Server Assignment Type set to RE\_REGISTRATION and the User Data Already Available parameter set to USER\_DATA\_ALREADY\_AVAILABLE in the SAR, as specified in the 3GPP TS 29.228 [3]. The information is associated with the Private User Identity affected by the SAR request. The HSS shall store this information. + +If any of the above data is changed, the S-CSCF shall update it in the HSS using SAR request with Server-Assignment-Type set to RE\_REGISTRATION and the User Data Already Available parameter set to USER\_DATA\_ALREADY\_AVAILABLE, as specified in the 3GPP TS 29.228 [3]. + +The S-CSCF shall send the registration data together with the subscription data as one S-CSCF restoration information. Each time the HSS receives the S-CSCF restoration information related to the same Private User Identity in the SAR with Server-Assignment-Type set to RE\_REGISTRATION, the HSS shall overwrite the previous S-CSCF restoration information. + +# --- 5 Recovery after P-CSCF failure + +## 5.0 General + +The following clauses show the requirements and information flows of IMS Restoration Procedures for the P-CSCF service interruption in each of the scenarios where they apply. + +Procedures over S9 between V-PCRF and H-PCRF are not supported in this release of the specification. + +## 5.1 Update PDP context/Bearer at P-CSCF failure + +These flows show the procedures performed by the network at P-CSCF failure after user initiated registration.. + +### 5.1.1 General requirements + +The following points are considered as requirements for the purpose of these procedures. + +1. P-CSCF discovery is performed by requesting and provisioning P-CSCF address(es) within Protocol Configuration Options (PCO), as specified in 3GPP TS 29.061 [9], subclause 13a.2.1 +2. The UE supports PCO IE, as specified in 3GPP TS 24.008 [4], subclause 10.5.6.3. +3. For the GTP based S5 interface, GTPv1, as specified in 3GPP TS 29.060 [8] or GTPv2, as specified in 3GPP TS 29.274 [10] are supported by the GGSN/PDN-GW. + +4. For the PMIP based S5 interface, PMIPv6, as specified in 3GPP TS 29.275 [15] is supported by the PDN-GW. + +### 5.1.2 Network recovery information flow - Update PDP context / Bearer + +![Sequence diagram illustrating the network recovery information flow for a P-CSCF failure. The diagram shows the interaction between UE, GGSN/PDN-GW, P-CSCF, and PCRF. The process starts with the UE sending a CreatePDPContextRequest to the GGSN/PDN-GW, which responds with a list of P-CSCF addresses. The GGSN/PDN-GW then sends a Diameter CCR to the PCRF, which responds with a Diameter CCA. The UE sends a SIP REGISTER to the P-CSCF, which responds with a Rx Push (P-CSCF address). The P-CSCF then sends a Gx Push (P-CSCF address) to the PCRF, which responds with a Gx Push Rsp. The GGSN/PDN-GW starts monitoring the P-CSCF. A failure is detected by the GGSN/PDN-GW. The GGSN/PDN-GW then sends an UpdatePDPContextRequest / UpdateBearerRequest (new list of P-CSCF addresses) to the UE, which responds with an UpdatePDPContextResponse / UpdateBearerResponse. Finally, the UE sends a SIP REGISTER to the GGSN/PDN-GW.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +``` +sequenceDiagram + participant UE + participant GGSN/PDN-GW + participant P-CSCF + participant PCRF + + Note left of GGSN/PDN-GW: Start monitoring of P-CSCF + + UE->>GGSN/PDN-GW: 1. CreatePDPContextRequest / CreateSessionRequest + GGSN/PDN-GW-->>UE: 2. CreatePDPContextResponse / CreateSessionResponse (list of P-CSCF addresses) + GGSN/PDN-GW->>PCRF: 3. Diameter CCR + PCRF-->>GGSN/PDN-GW: 4. Diameter CCA + UE->>P-CSCF: 5. SIP REGISTER + P-CSCF->>PCRF: 6. Rx Push (P-CSCF address) + PCRF-->>P-CSCF: 7. Rx Push Rsp + P-CSCF->>PCRF: 8. Gx Push (P-CSCF address) + PCRF-->>GGSN/PDN-GW: 9. Gx Push Rsp + GGSN/PDN-GW-->>UE: 10. 200 OK + Note right of GGSN/PDN-GW: Failure detected + GGSN/PDN-GW->>UE: 11. UpdatePDPContextRequest / UpdateBearerRequest (new list of P-CSCF addresses) + UE-->>GGSN/PDN-GW: 12. UpdatePDPContextResponse / UpdateBearerResponse + UE->>GGSN/PDN-GW: 13. SIP REGISTER +``` + +Sequence diagram illustrating the network recovery information flow for a P-CSCF failure. The diagram shows the interaction between UE, GGSN/PDN-GW, P-CSCF, and PCRF. The process starts with the UE sending a CreatePDPContextRequest to the GGSN/PDN-GW, which responds with a list of P-CSCF addresses. The GGSN/PDN-GW then sends a Diameter CCR to the PCRF, which responds with a Diameter CCA. The UE sends a SIP REGISTER to the P-CSCF, which responds with a Rx Push (P-CSCF address). The P-CSCF then sends a Gx Push (P-CSCF address) to the PCRF, which responds with a Gx Push Rsp. The GGSN/PDN-GW starts monitoring the P-CSCF. A failure is detected by the GGSN/PDN-GW. The GGSN/PDN-GW then sends an UpdatePDPContextRequest / UpdateBearerRequest (new list of P-CSCF addresses) to the UE, which responds with an UpdatePDPContextResponse / UpdateBearerResponse. Finally, the UE sends a SIP REGISTER to the GGSN/PDN-GW. + +**Figure 5.1.2a: P-CSCF failure (new list of P-CSCFs in PCO)** + +1. The UE initiates an IP-CAN session. +2. P-CSCF discovery is performed. A list of P-CSCF addresses is received in CreatePDPContextResponse / CreateBearerResponse within the PCO IE. +3. The GGSN/PDN-GW sends CCR to request for PCC rules, as specified in 3GPP TS 29.212 [6]. +4. The PCRF provides PCC rules to be applied in CCA. +5. The UE performs an initial registration towards a P-CSCF from the received list. + +6. The P-CSCF sends Rx Push (see 3GPP TS 29.214 [7]) to provide the PCRF with the P-CSCF selected by the UE. +7. The PCRF sends Rx Push response. +8. The PCRF uses a Gx push procedure to provide the GGSN/PDN-GW with the P-CSCF address. +9. The GGSN/PDN-GW stores this address for the UE and sends Gx Push Rsp. Also, the GGSN/PDN-GW starts monitoring the health of the P-CSCF if not already done. +10. The P-CSCF sends 200 OK to the UE. +11. A failure in P-CSCF is detected via Gi/sGi by the GGSN/PDN-GW. The GGSN/PDN-GW sends a new PCO IE with a new list of P-CSCF addresses (which does not include the failed P-CSCF) to all UEs associated to the failed P-CSCF address. +12. The UEs acknowledge the request. +13. Upon receiving the new list of P-CSCFs, if the P-CSCF in use is missing, each UE performs an initial registration towards a new P-CSCF. + +### 5.1.3 Network recovery information flow with S5 PMIP + +![Sequence diagram illustrating network recovery information flow with S5 PMIP. The diagram shows interactions between UE, S-GW, PDN-GW, P-CSCF, and PCRF. It details the initial setup (steps 1-10), a P-CSCF failure detection and notification (steps 11-12), a fallback procedure if PMIP Update Notification is not supported (step 13), and final UE registration to a new P-CSCF (step 14).](7f17c430b9598e4d748a8041457810b3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant S-GW + participant PDN-GW + participant P-CSCF + participant PCRF + + Note right of S-GW: 1. PBU (PCO) + S-GW->>PDN-GW: 1. PBU (PCO) + Note right of PDN-GW: 2. PBA (list of P-CSCF address in PCO) + PDN-GW-->>S-GW: 2. PBA (list of P-CSCF address in PCO) + + Note left of PDN-GW: Same as Step 3 ~ 10 Figure 5.1.2a: P-CSCF failure + Note right of P-CSCF: Failure + + Note right of PDN-GW: 11. UPN (New list of P-CSCF address) + PDN-GW->>S-GW: 11. UPN (New list of P-CSCF address) + Note right of S-GW: 12. UPA + S-GW-->>PDN-GW: 12. UPA + + Note left of PDN-GW: 13. If the PGW knows the SGW does not support the PMIP Update Notification procedure, the PGW shall release the PMIP binding with cause code "Reactivation Requested". + + Note right of UE: 14. Upon receiving the new list of P-CSCFs, each UE performs an initial registration towards a new P-CSCF. + +``` + +Sequence diagram illustrating network recovery information flow with S5 PMIP. The diagram shows interactions between UE, S-GW, PDN-GW, P-CSCF, and PCRF. It details the initial setup (steps 1-10), a P-CSCF failure detection and notification (steps 11-12), a fallback procedure if PMIP Update Notification is not supported (step 13), and final UE registration to a new P-CSCF (step 14). + +**Figure 5.1.3: P-CSCF failure with S5 PMIP** + +- 1 ~ 10. The IMS session is setup as described in subclause 5.1.2 except S5 PMIP procedure is used between SGW and PGW. +11. Once a P-CSCF failure is detected via Gi/sGi by the PDN-GW, the PDN-GW shall send a PMIP UPN message (MN ID, APN, PDN connection ID, PCO, and Additional parameters) as specified in 3GPP TS 29.275 [15] and IETF draft-ietf-netext-update-notifications-12 [16]. The PCO contains a new list of P-CSCF address. The Notification reason shall indicate that update Bearer Context at P-CSCF failure is needed. + +12. If the SGW supports the PMIP Update Notification message, it shall send Update Bearer Request message with the new list of P-CSCF address in the PCO to the MME/SGSN as part of the PGW initiated bearer modification without QoS update procedure as specified in 3GPP TS 23.401[17]. + +Once the Update Bearer Response message is received, the SGW shall response with a PMIP UPA message (MN ID, APN, PDN connection ID, PCO, and Additional parameters) as specified in 3GPP TS 29.275 [15] and IETF RFC 7077 [16]. + +13. If the PGW knows the SGW does not support the PMIP Update Notification procedure, the PGW shall skip step 11 and release the PMIP binding with cause code "Reactivation Requested". +14. Upon receiving the new list of P-CSCFs, the UE may perform an initial registration towards a new P-CSCF. + +## 5.2 Inform UE about P-CSCF failure + +These flows show the procedures performed by the network at P-CSCF failure after user initiated registration.. + +### 5.2.1 General requirements + +The following points are considered as requirements for the purpose of these procedures. + +1. P-CSCF discovery is performed by requesting P-CSCF address(es) via DHCP method, as specified in 3GPP TS 29.061 [9], subclause 13a.2.1 +2. The UE supports PCO IE, as specified in 3GPP TS 24.008 [4], subclause 10.5.6.3. +3. For the GTP based S5 interface, GTPv1, as specified in 3GPP TS 29.060 [8] or GTPv2, as specified in 3GPP TS 29.274 [10] are supported by the GGSN/PDN-GW +4. For the PMIPv6 based S5 interface, PMIPv6, as specified in 3GPP TS 29.275 [15] is supported by the PDN-GW. + +### 5.2.2 Network recovery information flow – Inform UE at P-CSCF failure + +![Sequence diagram illustrating P-CSCF failure for DHCP based scenarios. The diagram shows interactions between UE, GGSN/PDN-GW, DHCP server, P-CSCF, and PCRF. The sequence starts with UE sending a CreatePDPContextRequest to GGSN/PDN-GW. GGSN/PDN-GW responds with CreatePDPContextResponse. UE then sends a DHCP request to GGSN/PDN-GW, which relays it to the DHCP server. DHCP server responds with DHCP response (P-CSCF address). GGSN/PDN-GW sends a Diameter CCR to PCRF. PCRF responds with Diameter CCA. GGSN/PDN-GW sends a SIP REGISTER to P-CSCF. P-CSCF responds with Rx Push (P-CSCF address). PCRF responds with Rx Push Rsp. GGSN/PDN-GW sends a Gx Push (P-CSCF address) to P-CSCF. P-CSCF responds with Gx Push Rsp. GGSN/PDN-GW starts monitoring P-CSCF. P-CSCF sends a 200 OK to GGSN/PDN-GW. A failure is detected at GGSN/PDN-GW. GGSN/PDN-GW sends a P-CSCF failure indication to UE. UE responds with P-CSCF failure indication ack. UE then sends a DHCP request to GGSN/PDN-GW, which relays it to the DHCP server. DHCP server responds with DHCP response (P-CSCF address). GGSN/PDN-GW sends a SIP REGISTER to PCRF.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant GGSN/PDN-GW + participant DHCP server + participant P-CSCF + participant PCRF + + Note left of GGSN/PDN-GW: Start monitoring of P-CSCF + + UE->>GGSN/PDN-GW: 1. CreatePDPContextRequest/ CreateSessionRequest + GGSN/PDN-GW-->>UE: 2. CreatePDPContextResponse/ CreateSessionResponse + UE->>GGSN/PDN-GW: 3. DHCP request / Response (P-CSCF address) + GGSN/PDN-GW->>PCRF: 4. Diameter CCR + PCRF-->>GGSN/PDN-GW: 5. Diameter CCA + GGSN/PDN-GW->>P-CSCF: 6. SIP REGISTER + P-CSCF->>PCRF: 7. Rx Push (P-CSCF address) + PCRF-->>P-CSCF: 8. Rx Push Rsp + GGSN/PDN-GW->>P-CSCF: 9. Gx Push (P-CSCF address) + P-CSCF-->>GGSN/PDN-GW: 10. Gx Push Rsp + P-CSCF-->>GGSN/PDN-GW: 11. 200 OK + Note right of GGSN/PDN-GW: Failure detected + GGSN/PDN-GW->>UE: 12. P-CSCF failure indication + UE-->>GGSN/PDN-GW: 13. P-CSCF failure indication ack + UE->>GGSN/PDN-GW: 14. DHCP request / Response (P-CSCF address) + GGSN/PDN-GW->>PCRF: 15. SIP REGISTER + +``` + +Sequence diagram illustrating P-CSCF failure for DHCP based scenarios. The diagram shows interactions between UE, GGSN/PDN-GW, DHCP server, P-CSCF, and PCRF. The sequence starts with UE sending a CreatePDPContextRequest to GGSN/PDN-GW. GGSN/PDN-GW responds with CreatePDPContextResponse. UE then sends a DHCP request to GGSN/PDN-GW, which relays it to the DHCP server. DHCP server responds with DHCP response (P-CSCF address). GGSN/PDN-GW sends a Diameter CCR to PCRF. PCRF responds with Diameter CCA. GGSN/PDN-GW sends a SIP REGISTER to P-CSCF. P-CSCF responds with Rx Push (P-CSCF address). PCRF responds with Rx Push Rsp. GGSN/PDN-GW sends a Gx Push (P-CSCF address) to P-CSCF. P-CSCF responds with Gx Push Rsp. GGSN/PDN-GW starts monitoring P-CSCF. P-CSCF sends a 200 OK to GGSN/PDN-GW. A failure is detected at GGSN/PDN-GW. GGSN/PDN-GW sends a P-CSCF failure indication to UE. UE responds with P-CSCF failure indication ack. UE then sends a DHCP request to GGSN/PDN-GW, which relays it to the DHCP server. DHCP server responds with DHCP response (P-CSCF address). GGSN/PDN-GW sends a SIP REGISTER to PCRF. + +**Figure 5.2.2a: P-CSCF failure for DHCP based scenarios** + +1-2. The UE initiates an IP-CAN session. + +3. P-CSCF discovery is performed using DHCP based method. The GGSN/PDN-GW relays/sends the list of P-CSCF addresses in DHCP response. + +NOTE: The DHCP response can include either a list of P-CSCF IPv4/IPv6 addresses or a list of FQDNs (see IETF RFC 3361 [11] and IETF RFC 3319 [13]). If P-CSCF FQDNs were provided, the UE uses DNS SIP server resolution mechanism (see IETF RFC 3263 [12]) + +4. The GGSN/PDN-GW sends CCR to request for PCC rules, as specified in 3GPP TS 29.212 [6]. + +5. The PCRF provides PCC rules to be applied in CCA. +6. The UE performs an initial registration towards the P-CSCF received. +7. The P-CSCF sends Rx Push (see 3GPP TS 29.214 [7]) to provide the PCRF with the P-CSCF selected by the UE, +8. The PCRF sends Rx Push response. +9. The PCRF uses a Gx push procedure to provide the GGSN/PDN-GW with the P-CSCF address. +10. The GGSN/PDN-GW stores this address for the UE and sends Gx Push Rsp. Also, the GGSN/PDN-GW starts monitoring the health of the P-CSCF if not already done. +11. The P-CSCF sends 200 OK to the UE. +12. A failure in P-CSCF is detected via Gi/sGi by the GGSN/PDN-GW. The GGSN/PDN-GW informs to all UEs associated to the failed P-CSCF address that the P-CSCF is not available. +13. The UEs acknowledge the request. +14. The UE requests P-CSCF addresses (if needed) via new DHCP request. +15. The UE selects a new P-CSCF and initiates an initial IMS registration. + +### 5.2.3 Network recovery information flow – Inform UE at P-CSCF failure with S5 PMIP + +![Sequence diagram illustrating the network recovery information flow for P-CSCF failure with S5 PMIP. The diagram shows five entities: UE, S-GW, PDN-GW, P-CSCF, and PCRF. A dashed box labeled 'Same as Step 1 ~ 11 Figure 5.2.2a: P-CSCF failure for DHCP based scenarios' covers the initial setup. A starburst labeled '12 Failure' occurs at the PDN-GW. Arrows 12.1 (UPN (P-CSCF failure indicator)) and 12.2 (UPA) point from the PDN-GW to the S-GW. A dashed box labeled '12.3 If the PGW knows the SGW does not support the PMIP Update Notification procedure, the PGW shall skip step 12.1 and may release the PMIP binding with cause code "Reactivation Requested".' is shown. A final dashed box labeled 'Same as Step 13 ~ 15 Figure 5.2.2a: P-CSCF failure for DHCP based scenarios' covers the final steps.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +The diagram illustrates the sequence of messages for network recovery when the P-CSCF fails in a DHCP-based scenario with S5 PMIP. The entities involved are UE, S-GW, PDN-GW, P-CSCF, and PCRF. The process starts with a setup phase (steps 1-11) identical to the DHCP-based scenario. At step 12, a failure is detected at the PDN-GW. The PDN-GW sends a PMIP UPN message (12.1) and a UPA message (12.2) to the S-GW. A note indicates that if the PDN-GW knows the S-GW does not support PMIP Update Notification, it may skip step 12.1 and release the PMIP binding. The process then continues with steps 13-15, which are also identical to the DHCP-based scenario. + +Sequence diagram illustrating the network recovery information flow for P-CSCF failure with S5 PMIP. The diagram shows five entities: UE, S-GW, PDN-GW, P-CSCF, and PCRF. A dashed box labeled 'Same as Step 1 ~ 11 Figure 5.2.2a: P-CSCF failure for DHCP based scenarios' covers the initial setup. A starburst labeled '12 Failure' occurs at the PDN-GW. Arrows 12.1 (UPN (P-CSCF failure indicator)) and 12.2 (UPA) point from the PDN-GW to the S-GW. A dashed box labeled '12.3 If the PGW knows the SGW does not support the PMIP Update Notification procedure, the PGW shall skip step 12.1 and may release the PMIP binding with cause code "Reactivation Requested".' is shown. A final dashed box labeled 'Same as Step 13 ~ 15 Figure 5.2.2a: P-CSCF failure for DHCP based scenarios' covers the final steps. + +**Figure 5.2.3-1: P-CSCF failure for DHCP based scenarios with S5 PMIP** + +1 ~ 11. Same as figure 5.2.2a step 1 ~ 11 + +12. A failure in P-CSCF is detected via Gi/sGi by the GGSN/PDN-GW. The GGSN/PDN-GW informs to all UEs associated to the failed P-CSCF address that the P-CSCF is not available. + +- The PDN-GW shall send a PMIP UPN message (MN ID, APN, PDN connection ID, PCO, and Additional parameters) as specified in 3GPP TS 29.275 [15] and IETF RFC 7077 [16]. The PCO contains a P-CSCF failure Indicator. The Notification reason shall indicate that there is a P-CSCF failure. + +- If the SGW supports the PMIP Update Notification message, it shall send Update Bearer Request message with the P-CSCF failure Indicator in the PCO to the MME as part of the PGW initiated bearer modification without QoS update procedure as specified in 3GPP TS 23.401 [17]. Once the Update Bearer Response message is received, the SGW shall response with a PMIP UPA message (MN ID, APN, PDN connection ID, PCO, and Additional parameters) as specified in 3GPP TS 29.275 [15] and IETF RFC 7077 [16]. +- If the PGW knows the SGW does not support the PMIP Update Notification procedure, the PGW may release the PMIP binding with cause code "Reactivation Requested". + +13 ~ 15. Same as figure 5.2.2a step 13 ~15. + +## 5.3 Network recovery information flow – UE uses keep alive mechanism + +![Sequence diagram illustrating P-CSCF failure detection by UE. The diagram shows three lifelines: UE, P-CSCF, and P-CSCF. The UE sends a SIP REGISTER to the first P-CSCF, which responds with 200 OK. The UE then starts monitoring the P-CSCF. A failure is detected (indicated by a starburst). The UE then sends a SIP REGISTER to the second P-CSCF.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +``` +sequenceDiagram + participant UE + participant P-CSCF1 as P-CSCF + participant P-CSCF2 as P-CSCF + Note left of UE: Start monitoring of P-CSCF + UE->>P-CSCF1: 1. SIP REGISTER + P-CSCF1-->>UE: 2. 200 OK + Note right of P-CSCF1: Failure + UE->>P-CSCF2: 3. SIP REGISTER +``` + +Sequence diagram illustrating P-CSCF failure detection by UE. The diagram shows three lifelines: UE, P-CSCF, and P-CSCF. The UE sends a SIP REGISTER to the first P-CSCF, which responds with 200 OK. The UE then starts monitoring the P-CSCF. A failure is detected (indicated by a starburst). The UE then sends a SIP REGISTER to the second P-CSCF. + +**Figure 5.3a: P-CSCF failure detected by UE** + +1. After establishment of an IP-CAN session and acquiring P-CSCF addresses, the UE performs initial registration towards a P-CSCF. +2. If registration is successful, the UE monitors the P-CSCF health according to IETF RFC 6223 [14] +3. When a failure is detected, the UE acquires new P-CSCF addresses (if needed) and performs an initial registration. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|-------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | CT#41 | | | | V1.0.0 was approved in CT#41 | 1.0.0 | 8.0.0 | +| 2008-12 | CT#42 | CP-080698 | 0003 | - | Re-selection of S-CSCF at de-registration | 8.0.0 | 8.1.0 | +| | | CP-080698 | 0004 | 1 | Subscription to registration information recover | | | +| | | CP-080963 | 0007 | 3 | AS originating procedures | | | +| | | CP-080698 | 0008 | - | Multiple contacts restoration at re-registration | | | +| | | CP-080698 | 0009 | 1 | Multiple contacts restoration at de-registration | | | +| 2009-03 | CT#43 | CP-090026 | 0010 | - | Multiple Registrations in De-Registration | 8.1.0 | 8.2.0 | +| | | | 0011 | - | Multiple Registrations in Registration | | | +| 2009-06 | CT#44 | CP-090303 | 0019 | - | Contact storage in reg event subscription | 8.2.0 | 8.3.0 | +| 2009-12 | CT#46 | CP-090796 | 0020 | 1 | P-CSCF restoration procedures: stage 2 | 8.3.0 | 9.0.0 | +| 2010-03 | CT#47 | CP-100045 | 0022 | 1 | P-CSCF failure indication removal | 9.0.0 | 9.1.0 | +| | | | 0023 | 1 | P-CSCF failure handling for DHCP based scenarios | | | +| | | | 0024 | 1 | P-CSCF monitoring performed by UE | | | +| | | | 0025 | 1 | S9 interface procedures | | | +| 2010-06 | CT#48 | CP-100285 | 0027 | - | Notification is to be sent to all UEs sharing the IMPU | 9.1.0 | 9.2.0 | +| 2010-09 | CT#49 | CP-100462 | 0030 | 1 | Restoration Data Backup | 9.2.0 | 9.3.0 | +| 2011-03 | | | | - | Update to Rel-10 version (MCC) | 9.3.0 | 10.0.0 | +| 2011-06 | CT#52 | CP-110356 | 0033 | - | Emergency Restoration | 10.0.0 | 10.1.0 | +| 2012-09 | CT#57 | CP-120440 | 0040 | 1 | Emergency registrations do not affect registration status | 10.1.0 | 10.2.0 | +| 2012-09 | CT#57 | CP-120458 | 0037 | 1 | P-CSCF failure procedure with S5 PMIP | 10.2.0 | 11.0.0 | +| | | CP-120458 | 0041 | 1 | Reference list correction to align with the corrected TS 29.212 title | | | +| 2012-12 | CT#58 | CP-120745 | 0042 | 1 | Alignment on the Network recovery procedure at P-CSCF failure | 11.0.0 | 11.1.0 | +| | | CP-120743 | 0046 | 1 | PSI direct routing with restoration procedures | | | +| 2013-12 | CT#62 | CP-130609 | 0047 | 1 | Correction of reference to Update Notifications for Proxy Mobile IPv6 | 11.1.0 | 11.2.0 | +| 2014-03 | CT#63 | CP-140017 | 0051 | 1 | Update the reference of draft-ietf-sipcore-keep-01 to RFC 6223 | 11.2.0 | 11.3.0 | +| 2014-03 | CT#63 | CP-140020 | 0048 | 1 | Update the reference of IETF draft Update Notifications for Proxy Mobile IPv6 to RFC 7077 | 11.2.0 | 11.3.0 | +| 2016-09 | CT#73 | CP-160415 | 0089 | - | Non REGISTER authentication after S-CSCF restart | 11.3.0 | 11.4.0 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23852/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/23_series/23852/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ecdc8cd86cd896fbc6ed8cab4875c728369bfff --- /dev/null +++ b/marked/Rel-11/23_series/23852/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c85f8ed36b42312c5f95cf1741c8b86243995e25b4e887445a3ce876b0191b7d +size 60597 diff --git a/marked/Rel-11/23_series/23852/007fefafb4fcbdb7d388209f63a0ba5d_img.jpg b/marked/Rel-11/23_series/23852/007fefafb4fcbdb7d388209f63a0ba5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88009db457fcb134b61e7007a2840f17db6e49f7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/007fefafb4fcbdb7d388209f63a0ba5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68393a3814edf63c13df592c74c2e1ce6330c09596d12b2bdefb82fa18b2409d +size 73424 diff --git a/marked/Rel-11/23_series/23852/01141eb99b707de5aead56f84afe3b1f_img.jpg b/marked/Rel-11/23_series/23852/01141eb99b707de5aead56f84afe3b1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e551bf6443ce98161105ac48fed4fb608f3236ad --- /dev/null +++ b/marked/Rel-11/23_series/23852/01141eb99b707de5aead56f84afe3b1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67398274e4f682ee44bbe872d0d3241b96a79b01cba5bef1a9b8548280d598af +size 58914 diff --git a/marked/Rel-11/23_series/23852/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/Rel-11/23_series/23852/030c758fd425016b03290c8f11bef69d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4658ff46f4f1a65baab380029415fb743175b2e --- /dev/null +++ b/marked/Rel-11/23_series/23852/030c758fd425016b03290c8f11bef69d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b1020da1d008efebbb225d764568d572e085c243114f94a948201ead9048a0a +size 59526 diff --git a/marked/Rel-11/23_series/23852/036ceaf207a7b289ca76e160892eb724_img.jpg b/marked/Rel-11/23_series/23852/036ceaf207a7b289ca76e160892eb724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6d97c74b29a413019cca0902bc81f229f350c25 --- /dev/null +++ b/marked/Rel-11/23_series/23852/036ceaf207a7b289ca76e160892eb724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dfc9818530f99e179d84dc9d9b094cbe3ace7ab2490abb9b8ddaf5b1a668844 +size 10014 diff --git a/marked/Rel-11/23_series/23852/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg b/marked/Rel-11/23_series/23852/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15ad619f813f4dd13777f73e1820d6842e92581a --- /dev/null +++ b/marked/Rel-11/23_series/23852/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afde777d30510a6db8ee7756ab6aab3f2cfa673e4015b204880a50d1c7415cf7 +size 222675 diff --git a/marked/Rel-11/23_series/23852/04cfca33e3fc26513abe649d7474f733_img.jpg b/marked/Rel-11/23_series/23852/04cfca33e3fc26513abe649d7474f733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..703607a4465c923575819142e75662f4addadb77 --- /dev/null +++ b/marked/Rel-11/23_series/23852/04cfca33e3fc26513abe649d7474f733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a0fb7fed6800fe10047ea4b5f5e6e387e8e61046e348e7c83a6d00da8736805 +size 86621 diff --git a/marked/Rel-11/23_series/23852/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/23_series/23852/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4baf22a641bb75c7eb6369095a0ef64287e0db7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ec9636d187a4338ffe7e15e0fa415edf85a0deed2e7b61d0bafcdb253a38d17 +size 79727 diff --git a/marked/Rel-11/23_series/23852/077f85b82901283b4657fd2b45fc0294_img.jpg b/marked/Rel-11/23_series/23852/077f85b82901283b4657fd2b45fc0294_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..605b13a7b42a1867165b1d132582ccbd88b4366e --- /dev/null +++ b/marked/Rel-11/23_series/23852/077f85b82901283b4657fd2b45fc0294_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a68ec56568314c33e09ec245c779385b5bddea618f4c6d49d4e1b78dd2e72054 +size 82467 diff --git a/marked/Rel-11/23_series/23852/0b452c5334567cbdc22ee9817e1246f5_img.jpg b/marked/Rel-11/23_series/23852/0b452c5334567cbdc22ee9817e1246f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf59a13690b607aeff5df9fadd31c79e725bcb62 --- /dev/null +++ b/marked/Rel-11/23_series/23852/0b452c5334567cbdc22ee9817e1246f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b198e5ba01594ed43ef4ffd0ab5772e9d13dc7147ae6a118837d6a0b5999e46 +size 36474 diff --git a/marked/Rel-11/23_series/23852/0f26e70157bd4c45f825795cdcd20fbd_img.jpg b/marked/Rel-11/23_series/23852/0f26e70157bd4c45f825795cdcd20fbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ca8e9608d00ec2a6be9f299e08544f8a0cded1d --- /dev/null +++ b/marked/Rel-11/23_series/23852/0f26e70157bd4c45f825795cdcd20fbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ac090a3e5a7262a80f09947d65f76dd632774ad895b409125dda54308c8b9ca +size 59002 diff --git a/marked/Rel-11/23_series/23852/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-11/23_series/23852/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4fff4a6c2954f18369ac55535e1e12e3be481ae --- /dev/null +++ b/marked/Rel-11/23_series/23852/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad63781bc050a0c3465000ace21a3fd91d3990d8a91e01cbee1316604f5f0b5d +size 107155 diff --git a/marked/Rel-11/23_series/23852/1033dc9fde75540d224c907681b1b7aa_img.jpg b/marked/Rel-11/23_series/23852/1033dc9fde75540d224c907681b1b7aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58607753c0954956b1e49b807947db1cba4611ef --- /dev/null +++ b/marked/Rel-11/23_series/23852/1033dc9fde75540d224c907681b1b7aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc547701f176b0625e66d4706e615f1f1cbd804172aec48a90f6c05a0ad3ec0e +size 68745 diff --git a/marked/Rel-11/23_series/23852/142bb586c6d72f1be78c75cea40ff7de_img.jpg b/marked/Rel-11/23_series/23852/142bb586c6d72f1be78c75cea40ff7de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e32662c5cfdcae55708984da4a59a94aba6555e5 --- /dev/null +++ b/marked/Rel-11/23_series/23852/142bb586c6d72f1be78c75cea40ff7de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d52a25bf28b519b3253ea5d86cddddab093e58102cdddbd58f82a4353284c527 +size 6704 diff --git a/marked/Rel-11/23_series/23852/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-11/23_series/23852/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdab4b652fe7ca78150270733f9174280abc54d3 --- /dev/null +++ b/marked/Rel-11/23_series/23852/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97018dccdd132334457d88b063fcc149cd63b083c6ed7cafe9b1007c8a881aca +size 117365 diff --git a/marked/Rel-11/23_series/23852/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/23_series/23852/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abe7a2a98643546085b44d46158ce5805f36e79a --- /dev/null +++ b/marked/Rel-11/23_series/23852/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af973027e6a6a986ee24b2ffe5660fc29c4f4f4470394818983424f805a4629b +size 94378 diff --git a/marked/Rel-11/23_series/23852/195611c20b2dc7ed0fa3033392e22908_img.jpg b/marked/Rel-11/23_series/23852/195611c20b2dc7ed0fa3033392e22908_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15ad619f813f4dd13777f73e1820d6842e92581a --- /dev/null +++ b/marked/Rel-11/23_series/23852/195611c20b2dc7ed0fa3033392e22908_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afde777d30510a6db8ee7756ab6aab3f2cfa673e4015b204880a50d1c7415cf7 +size 222675 diff --git a/marked/Rel-11/23_series/23852/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/Rel-11/23_series/23852/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bb5db2b3950de649db069464245e50e901a9c04 --- /dev/null +++ b/marked/Rel-11/23_series/23852/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10650711bb9b1fa9821de0c0609d06bb8d3e3946a9347ebed0e29f3f8ce1e481 +size 22955 diff --git a/marked/Rel-11/23_series/23852/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg b/marked/Rel-11/23_series/23852/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7aa04f925fc24bf8b3024b9a958f6d16d68abc5 --- /dev/null +++ b/marked/Rel-11/23_series/23852/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a2a58f96e1faa0d05d1ac7c1cfa4c7b36a94968ba2e9a70014847ff319286ad +size 48780 diff --git a/marked/Rel-11/23_series/23852/1c94fd3cebf58af136144f14160d128e_img.jpg b/marked/Rel-11/23_series/23852/1c94fd3cebf58af136144f14160d128e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4d65e31859c49f7679eed8e78881820d64af2af --- /dev/null +++ b/marked/Rel-11/23_series/23852/1c94fd3cebf58af136144f14160d128e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:543e242a88b46d982db0db05b5f6ba0eeea9ca062e175e6d244a272cad65afd7 +size 61516 diff --git a/marked/Rel-11/23_series/23852/1cd762800fb629a48ed907cf73d794f4_img.jpg b/marked/Rel-11/23_series/23852/1cd762800fb629a48ed907cf73d794f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b33747de95cfdfc5600532756e41c4d311caf13 --- /dev/null +++ b/marked/Rel-11/23_series/23852/1cd762800fb629a48ed907cf73d794f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60cd87342efe3161275aae13387c8068b824361e91575f690b8715f2ff3bd96f +size 36062 diff --git a/marked/Rel-11/23_series/23852/1dbb1d90b2022a3a765c85929a515cc6_img.jpg b/marked/Rel-11/23_series/23852/1dbb1d90b2022a3a765c85929a515cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fa91293bbc748f9ca6b1cca7c7dc0ff7b2050dd --- /dev/null +++ b/marked/Rel-11/23_series/23852/1dbb1d90b2022a3a765c85929a515cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23b89b1003acd2665bf78dc4adf12cc62503b184cf2a5eec2f949f24b9c87b3a +size 5073 diff --git a/marked/Rel-11/23_series/23852/1f1614411edea7edfc86c839a608e1fc_img.jpg b/marked/Rel-11/23_series/23852/1f1614411edea7edfc86c839a608e1fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ad993fc5074b6a9d525201698a9bfd9da6631e6 --- /dev/null +++ b/marked/Rel-11/23_series/23852/1f1614411edea7edfc86c839a608e1fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7da91de5e9f6a442a479041bf580dd82d4242b078a4dd6262f751390b3882e7f +size 99104 diff --git a/marked/Rel-11/23_series/23852/212c50c4e3d043c989037a01e13c1a98_img.jpg b/marked/Rel-11/23_series/23852/212c50c4e3d043c989037a01e13c1a98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb48fa92bf7760a1ced518de0df59d729f2c6b00 --- /dev/null +++ b/marked/Rel-11/23_series/23852/212c50c4e3d043c989037a01e13c1a98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd51fd7ca0f2a07a5c7c7eefb8f78c3ce48aa72c9a6cad8349522eff608e5d5a +size 39827 diff --git a/marked/Rel-11/23_series/23852/21327313f7b18a481da0c87a6472a80d_img.jpg b/marked/Rel-11/23_series/23852/21327313f7b18a481da0c87a6472a80d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..600cd67a943b2da06a065fe5cd145f744a033c8a --- /dev/null +++ b/marked/Rel-11/23_series/23852/21327313f7b18a481da0c87a6472a80d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00401fe5fa421f9f9dfe5d677ea41784a54b376eb2d043e7022028347a87e6a7 +size 91208 diff --git a/marked/Rel-11/23_series/23852/237b76118be454462fc9b4e96adaa6c7_img.jpg b/marked/Rel-11/23_series/23852/237b76118be454462fc9b4e96adaa6c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55db8e40afe1fa29eda0544b04cfb0e0009fe889 --- /dev/null +++ b/marked/Rel-11/23_series/23852/237b76118be454462fc9b4e96adaa6c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26a39da4394bb15b29578a5dc0e9853b12abc3bddfa8335d6d020a30d004f683 +size 26654 diff --git a/marked/Rel-11/23_series/23852/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg b/marked/Rel-11/23_series/23852/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e6adeb0b17ecf07e848110ddd207686db01d7b0 --- /dev/null +++ b/marked/Rel-11/23_series/23852/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53a3c576e2ea08540fdc8477e64028127333e2dfaf6d25eb1b2cf4c6b63799e4 +size 6758 diff --git a/marked/Rel-11/23_series/23852/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/23_series/23852/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f10bb9596d7bd4a1264ba46e304954cb3f2b1772 --- /dev/null +++ b/marked/Rel-11/23_series/23852/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb5faa280f64007d9ca06d9bf037c9ca6464e5b92f4b4b476ac2b3528a96683d +size 85854 diff --git a/marked/Rel-11/23_series/23852/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-11/23_series/23852/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12a1b3bcc6e5c81b7edc40a69dd571b35434384c --- /dev/null +++ b/marked/Rel-11/23_series/23852/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:097dd5f5dd8354ed5918af02ac055a477b3c9cd4a4500187f95d4de3920799ed +size 111007 diff --git a/marked/Rel-11/23_series/23852/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Rel-11/23_series/23852/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7f7e8b6d826321333e75b9aecd2bf88de06861d --- /dev/null +++ b/marked/Rel-11/23_series/23852/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f238bea83b771e855583128cceefa1b0a910769bad7c67b9dd8722a43a8cf520 +size 82964 diff --git a/marked/Rel-11/23_series/23852/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/23_series/23852/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7eaf7dac2e9b96834bb99fc1804aa76543a68052 --- /dev/null +++ b/marked/Rel-11/23_series/23852/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:257e23bfcb94b1e295a918d312c1991bddf9710aabf998a8bd9aa9dac38611dc +size 43635 diff --git a/marked/Rel-11/23_series/23852/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-11/23_series/23852/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d23982f72e9f9116ee911cdb85ecba950d6207a --- /dev/null +++ b/marked/Rel-11/23_series/23852/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f8287f97efb8bf3d3b5af091b936bc042a41c41d980c1ec9cdcdd4b55cf0542 +size 153372 diff --git a/marked/Rel-11/23_series/23852/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/23_series/23852/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e721a1155be313f08ae092bad91a98b4223d4a1e --- /dev/null +++ b/marked/Rel-11/23_series/23852/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5283c5662bf1f5634da21ee6af14645c8f912db3c703b79fc3429461b03ff37 +size 76471 diff --git a/marked/Rel-11/23_series/23852/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/23_series/23852/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2222c907cdd7311d5763f4005bd706b1436772dd --- /dev/null +++ b/marked/Rel-11/23_series/23852/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:972c29b8171b37ca7788ba3446e12c5a746a39dc21266e4228254a22be389bba +size 71141 diff --git a/marked/Rel-11/23_series/23852/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-11/23_series/23852/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9179ddd0046beece05368338997fb6329978ff5 --- /dev/null +++ b/marked/Rel-11/23_series/23852/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e32adc8d1e850ee2c864bbbdaf0d0bd3925458090f582e325bc92b93e843b3a0 +size 71174 diff --git a/marked/Rel-11/23_series/23852/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-11/23_series/23852/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..603e67ed0447849299fcf60841a9489fffa4b137 --- /dev/null +++ b/marked/Rel-11/23_series/23852/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a7788af9a5e11ed703fb5d4ecb37812cbf3ac98de6735b6275062b37675672e +size 113855 diff --git a/marked/Rel-11/23_series/23852/367378559e35017a5e1a6f5c30798c5a_img.jpg b/marked/Rel-11/23_series/23852/367378559e35017a5e1a6f5c30798c5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0b630315a51f7b07d98400a38f2a08405498268 --- /dev/null +++ b/marked/Rel-11/23_series/23852/367378559e35017a5e1a6f5c30798c5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1e024e225e5f4b143324af37a9d23c600181bdeed3c7c2ef34c5a92c104df78 +size 84408 diff --git a/marked/Rel-11/23_series/23852/376f80eb8a41369e87da63a0210d173e_img.jpg b/marked/Rel-11/23_series/23852/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb48fa92bf7760a1ced518de0df59d729f2c6b00 --- /dev/null +++ b/marked/Rel-11/23_series/23852/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd51fd7ca0f2a07a5c7c7eefb8f78c3ce48aa72c9a6cad8349522eff608e5d5a +size 39827 diff --git a/marked/Rel-11/23_series/23852/3b00a61116faef21d3a6009fd350b46a_img.jpg b/marked/Rel-11/23_series/23852/3b00a61116faef21d3a6009fd350b46a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b6adef7ae020782904545b550988869fc80f9f7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/3b00a61116faef21d3a6009fd350b46a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d98a0d809ba10301501bdf7db3a79c2bb7e73e3a1c63fbb51ce909452be10715 +size 52086 diff --git a/marked/Rel-11/23_series/23852/3c04b14104f95eb8f7100f6d497d956e_img.jpg b/marked/Rel-11/23_series/23852/3c04b14104f95eb8f7100f6d497d956e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bf50a8b3ed19f0f40bae464a1dec339cdb128b5 --- /dev/null +++ b/marked/Rel-11/23_series/23852/3c04b14104f95eb8f7100f6d497d956e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9737322c2e07ca5bd84f7e5c61cfc3019250cb089de327be49632ec42e483ace +size 19506 diff --git a/marked/Rel-11/23_series/23852/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-11/23_series/23852/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf50fb812e001241a982145045d6100338c47713 --- /dev/null +++ b/marked/Rel-11/23_series/23852/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77908be5402df2fbf4a6f67b25617d8a6aecea30c179adfdfa40e792ae3b7854 +size 48069 diff --git a/marked/Rel-11/23_series/23852/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg b/marked/Rel-11/23_series/23852/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..600cd67a943b2da06a065fe5cd145f744a033c8a --- /dev/null +++ b/marked/Rel-11/23_series/23852/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00401fe5fa421f9f9dfe5d677ea41784a54b376eb2d043e7022028347a87e6a7 +size 91208 diff --git a/marked/Rel-11/23_series/23852/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/Rel-11/23_series/23852/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e6d691d07233327e25d96cf2beae5cc311232f1 --- /dev/null +++ b/marked/Rel-11/23_series/23852/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f37b274f70d1c59f4b3522a6532a8ca04c26e5ba29ba8fafd00993202a89df43 +size 49689 diff --git a/marked/Rel-11/23_series/23852/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-11/23_series/23852/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0329f2fd06a71d212cdd4c45c7de2a0213a6bff --- /dev/null +++ b/marked/Rel-11/23_series/23852/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f48ae532317008b221abff30e306a36e2019594e910d34ec1d08c3f9ffb88e32 +size 73352 diff --git a/marked/Rel-11/23_series/23852/42e18c25bfd455a5a57f207bacfcb970_img.jpg b/marked/Rel-11/23_series/23852/42e18c25bfd455a5a57f207bacfcb970_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f0ed5cb44eb00a8cbb9040480ba547f9c983364 --- /dev/null +++ b/marked/Rel-11/23_series/23852/42e18c25bfd455a5a57f207bacfcb970_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:646b2838da65cad63bbfae6452f8b1286a49795c6626cc738009ca9b14dc60d2 +size 91531 diff --git a/marked/Rel-11/23_series/23852/4346261cc730a1eb683f35e4ce9deacf_img.jpg b/marked/Rel-11/23_series/23852/4346261cc730a1eb683f35e4ce9deacf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3a02442da63346c9560152f908749ef0013eeee --- /dev/null +++ b/marked/Rel-11/23_series/23852/4346261cc730a1eb683f35e4ce9deacf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ceccf7474a9cd542963b653e31d4f2cb1eb3a49dbb33a4be4db43133fdddf191 +size 165029 diff --git a/marked/Rel-11/23_series/23852/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg b/marked/Rel-11/23_series/23852/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05a47c710374091b48fb93f98f8cfa20ab2764d8 --- /dev/null +++ b/marked/Rel-11/23_series/23852/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33f546f0e52bd622065d1ec91f1053064d557909aceeac8839685ba8f743876c +size 44212 diff --git a/marked/Rel-11/23_series/23852/45578bd3ed11d45af63ce00e28bab2f8_img.jpg b/marked/Rel-11/23_series/23852/45578bd3ed11d45af63ce00e28bab2f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88009db457fcb134b61e7007a2840f17db6e49f7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/45578bd3ed11d45af63ce00e28bab2f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68393a3814edf63c13df592c74c2e1ce6330c09596d12b2bdefb82fa18b2409d +size 73424 diff --git a/marked/Rel-11/23_series/23852/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-11/23_series/23852/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fafc854cc013cc425ad3b64c509778c488ebef85 --- /dev/null +++ b/marked/Rel-11/23_series/23852/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3fb2c4c1e12ef3b87e7c3aaf2b3aee4c6fdf12283ab1503ea88d578700cfbe3 +size 109390 diff --git a/marked/Rel-11/23_series/23852/4b82c57bac9f5800baee15745b212963_img.jpg b/marked/Rel-11/23_series/23852/4b82c57bac9f5800baee15745b212963_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4da8f54a21d70275078d3377c840cff84b79cd2f --- /dev/null +++ b/marked/Rel-11/23_series/23852/4b82c57bac9f5800baee15745b212963_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a24501fac789e251fc9643b7b5fad42b636460e1b2a967dfc84c094e22cc4332 +size 55713 diff --git a/marked/Rel-11/23_series/23852/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg b/marked/Rel-11/23_series/23852/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad67348a3f955e72bb6d09211f6793b9dc3846fd --- /dev/null +++ b/marked/Rel-11/23_series/23852/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccc5103a8799eac6e41eca41a7259dcd3dca06a1836c9e3a72a040e43ef0076b +size 68290 diff --git a/marked/Rel-11/23_series/23852/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-11/23_series/23852/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3d60ca376fc71f5c2e230225e632df8b25d3549 --- /dev/null +++ b/marked/Rel-11/23_series/23852/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1df8eeafa7e56ce29f8e8b6c5830d9294f539f5b9ecbc5f6e0858da8bbf53674 +size 133074 diff --git a/marked/Rel-11/23_series/23852/50214d232017279410e9c9db8eb75119_img.jpg b/marked/Rel-11/23_series/23852/50214d232017279410e9c9db8eb75119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfc571787a1b61f2353a5c8135eb18b3d9fdbb2b --- /dev/null +++ b/marked/Rel-11/23_series/23852/50214d232017279410e9c9db8eb75119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e8afe1e1aa1c538c510cf3f186856be2102138b4364d9b83ea0e5e3656d5380 +size 65959 diff --git a/marked/Rel-11/23_series/23852/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/23_series/23852/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c194d2ebdc12d2d89d9e8bb9b366600e95bf9aea --- /dev/null +++ b/marked/Rel-11/23_series/23852/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15b97b82bfdd2c19ef2ec995f632f4cd9891e70019718bde1d92732238de391a +size 87385 diff --git a/marked/Rel-11/23_series/23852/573c8f9e728e343b6864e1070c14b8cf_img.jpg b/marked/Rel-11/23_series/23852/573c8f9e728e343b6864e1070c14b8cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..961e1b98931bde573b6be30288ed451b998d5f48 --- /dev/null +++ b/marked/Rel-11/23_series/23852/573c8f9e728e343b6864e1070c14b8cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:668ee0291efe2f41ae024b7aecb9043cc2663d8f7046b4914634488610962a1e +size 60789 diff --git a/marked/Rel-11/23_series/23852/58bbc570572758132ea39938e4f03b5b_img.jpg b/marked/Rel-11/23_series/23852/58bbc570572758132ea39938e4f03b5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9df8c2d946d87ebbdfbaf26e966655bf7be0135 --- /dev/null +++ b/marked/Rel-11/23_series/23852/58bbc570572758132ea39938e4f03b5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:435225094a6c7ba91308e825d2bef224a7bb68f3f2ad324871385caede0f1140 +size 90829 diff --git a/marked/Rel-11/23_series/23852/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-11/23_series/23852/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7f0d673db39b7982ef3c23504087eba99e20f0b --- /dev/null +++ b/marked/Rel-11/23_series/23852/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd9f892d3677062cc3f978bdd618ed49edbdaee6f8c0ff98ad5aa177ad35a91a +size 143016 diff --git a/marked/Rel-11/23_series/23852/5cb74e3ca5034698d7eab12de06f8763_img.jpg b/marked/Rel-11/23_series/23852/5cb74e3ca5034698d7eab12de06f8763_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2406b0187ee53e818a0ce269632e6b3caa12dd67 --- /dev/null +++ b/marked/Rel-11/23_series/23852/5cb74e3ca5034698d7eab12de06f8763_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72ec38209d9288b2320d4bc87aa26c81443a0c2ac974facd0d305ff64363ba5f +size 7731 diff --git a/marked/Rel-11/23_series/23852/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/Rel-11/23_series/23852/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12062e1eff8fcd3e3e252003bce01b8be97bded2 --- /dev/null +++ b/marked/Rel-11/23_series/23852/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62ae3766cb95af4ac83c3398f4cc5ee2e5f500dcb5c53d88e293fe8249889976 +size 115422 diff --git a/marked/Rel-11/23_series/23852/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-11/23_series/23852/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef6279be81270247baffebd9da69d86e3ff03b3d --- /dev/null +++ b/marked/Rel-11/23_series/23852/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42b7f9ab4b0a82ad2a0d8c4d8993dbe4a3fb41ab3f0efb39f6ffd97a55786fe0 +size 105827 diff --git a/marked/Rel-11/23_series/23852/62ee64afa2d368d732de66628cf2c841_img.jpg b/marked/Rel-11/23_series/23852/62ee64afa2d368d732de66628cf2c841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf59a13690b607aeff5df9fadd31c79e725bcb62 --- /dev/null +++ b/marked/Rel-11/23_series/23852/62ee64afa2d368d732de66628cf2c841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b198e5ba01594ed43ef4ffd0ab5772e9d13dc7147ae6a118837d6a0b5999e46 +size 36474 diff --git a/marked/Rel-11/23_series/23852/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-11/23_series/23852/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12a1b3bcc6e5c81b7edc40a69dd571b35434384c --- /dev/null +++ b/marked/Rel-11/23_series/23852/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:097dd5f5dd8354ed5918af02ac055a477b3c9cd4a4500187f95d4de3920799ed +size 111007 diff --git a/marked/Rel-11/23_series/23852/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-11/23_series/23852/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c194d2ebdc12d2d89d9e8bb9b366600e95bf9aea --- /dev/null +++ b/marked/Rel-11/23_series/23852/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15b97b82bfdd2c19ef2ec995f632f4cd9891e70019718bde1d92732238de391a +size 87385 diff --git a/marked/Rel-11/23_series/23852/683f755e8456c884716de4fce48c7e63_img.jpg b/marked/Rel-11/23_series/23852/683f755e8456c884716de4fce48c7e63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cc83cadf0f8fdb6edfdf3f1aedd0e01c8fbbb68 --- /dev/null +++ b/marked/Rel-11/23_series/23852/683f755e8456c884716de4fce48c7e63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a78168e638e9553a5f81765d58092b01b03cb0f1efb3e4825de9c1075ee254eb +size 111357 diff --git a/marked/Rel-11/23_series/23852/68dad113f9a15ab01945110cb50cdcfb_img.jpg b/marked/Rel-11/23_series/23852/68dad113f9a15ab01945110cb50cdcfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baaaec6bfd21ee71fb0809ee84ff7e1cfbd97ad3 --- /dev/null +++ b/marked/Rel-11/23_series/23852/68dad113f9a15ab01945110cb50cdcfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:581c9e6a5140fb970eb1e38ca95a38493876df44a1a5453ddba6fc09baad7fdd +size 38186 diff --git a/marked/Rel-11/23_series/23852/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Rel-11/23_series/23852/69edc2887e907309499ac95b47ab6905_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c69f7ef55116c4934c33939b6130e726e1e7a634 --- /dev/null +++ b/marked/Rel-11/23_series/23852/69edc2887e907309499ac95b47ab6905_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:771852c43b91200bab6f6c3e5e3fb8af01781a4062d1d535d35a6ea5af433df9 +size 61226 diff --git a/marked/Rel-11/23_series/23852/6b9ee906d502aece4a2becf5895db07a_img.jpg b/marked/Rel-11/23_series/23852/6b9ee906d502aece4a2becf5895db07a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c0d9439642b3d4dfade0be6d9f9a22c5ecd3466 --- /dev/null +++ b/marked/Rel-11/23_series/23852/6b9ee906d502aece4a2becf5895db07a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba94f183ecd89f4a67f4e08e369cff66ada9fd6791ef76fb69e2a61bfc05bea5 +size 81816 diff --git a/marked/Rel-11/23_series/23852/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Rel-11/23_series/23852/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c49ea40a30278dc044f39f7b118ad5ab6e5ad52 --- /dev/null +++ b/marked/Rel-11/23_series/23852/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4edf5989c15b361b4b037ac49a6aa638fbd594ae9bd65e2d23332c6f1cac3068 +size 53168 diff --git a/marked/Rel-11/23_series/23852/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-11/23_series/23852/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26fc121e2f52f4f35ec0b1f389c354b6d9f10ef9 --- /dev/null +++ b/marked/Rel-11/23_series/23852/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07c8e342dc26d468c6b2a08ed4bcda27484f9e40cde0226479756a6d5d5e627b +size 4866 diff --git a/marked/Rel-11/23_series/23852/7156cf400ef0e19f9d06a5d0549834a3_img.jpg b/marked/Rel-11/23_series/23852/7156cf400ef0e19f9d06a5d0549834a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a81949eda4d0b9e53d7c7999f172322c1aeb3d1b --- /dev/null +++ b/marked/Rel-11/23_series/23852/7156cf400ef0e19f9d06a5d0549834a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:434aac36eb176b475d9a338342225ad0934d342530d7a22b117c869fd2e9910c +size 82740 diff --git a/marked/Rel-11/23_series/23852/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-11/23_series/23852/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59a1acbbbd818fb80b200afdcc3b90e69ad980c4 --- /dev/null +++ b/marked/Rel-11/23_series/23852/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb0bb2b0d2e86c94f1e8dd135a4515383cb0c811817a4f4965fa6187939cab09 +size 88327 diff --git a/marked/Rel-11/23_series/23852/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-11/23_series/23852/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5df5ff9c365fd445c41ccee3fd83c08240bfa3d9 --- /dev/null +++ b/marked/Rel-11/23_series/23852/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14ed4fdb23b5318236875879e45e220fd23c7d676461008c7aafc62ae008888f +size 51839 diff --git a/marked/Rel-11/23_series/23852/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-11/23_series/23852/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94fc1848747cbde09510359e0664969ca4b22743 --- /dev/null +++ b/marked/Rel-11/23_series/23852/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55c5b4d5e487cbc5f588ce6efa8c08febafa3d69aa3730353dcf2f82bcc290b7 +size 63700 diff --git a/marked/Rel-11/23_series/23852/762a17cd79880dbca172bcbbe9375223_img.jpg b/marked/Rel-11/23_series/23852/762a17cd79880dbca172bcbbe9375223_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36d06231987e006364252576dda3e75efe06d660 --- /dev/null +++ b/marked/Rel-11/23_series/23852/762a17cd79880dbca172bcbbe9375223_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9b2587d11cefb699e9922e5afb8472881787d829d5cbaae454f8e84c38647f7 +size 55836 diff --git a/marked/Rel-11/23_series/23852/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/23_series/23852/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c07a371497f2d68d9e082bd9b15e136e9e633f1 --- /dev/null +++ b/marked/Rel-11/23_series/23852/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36fecb84f853d2dd0a4cfbc57e0de6af46edb9e145def4c5ebbbcd0b2033465d +size 65322 diff --git a/marked/Rel-11/23_series/23852/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Rel-11/23_series/23852/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7de26c21c55749ac0554f0e3a22d68a61b5f9cae --- /dev/null +++ b/marked/Rel-11/23_series/23852/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2db3340304d48ba236e7c9b79fe51ecaa6f10d3e8cc93547b63e81592929d56b +size 63268 diff --git a/marked/Rel-11/23_series/23852/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-11/23_series/23852/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..019f3fee94e03bcac218a8f9234441f6a5201ca4 --- /dev/null +++ b/marked/Rel-11/23_series/23852/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce12210fd1eebb36b667edd26d2307a70cca8ce63e2ec7f90ac196046896dbd3 +size 51872 diff --git a/marked/Rel-11/23_series/23852/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg b/marked/Rel-11/23_series/23852/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d1bdd980780e651dbbc50b13a6d178851505a8c --- /dev/null +++ b/marked/Rel-11/23_series/23852/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:225f7d3d60f9ab4ceaee91d396e9b03bf66ca4799af44adbceec44f74494dd4e +size 92038 diff --git a/marked/Rel-11/23_series/23852/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-11/23_series/23852/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4854bc8a630866651b0761084fdeb526b3eb6115 --- /dev/null +++ b/marked/Rel-11/23_series/23852/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a81d5b8716ed49839e94d21ada814ad5b4fca0a0a39f293434f23c96f757560e +size 59903 diff --git a/marked/Rel-11/23_series/23852/805c475f0859e607af0530ba43194bf1_img.jpg b/marked/Rel-11/23_series/23852/805c475f0859e607af0530ba43194bf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9f2314d65a6b328808393829c61ee1217d1ef32 --- /dev/null +++ b/marked/Rel-11/23_series/23852/805c475f0859e607af0530ba43194bf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2867d0ade7c317d775ce8e4ec569db41b20d4c14956e1037d7777ee660cc994 +size 51810 diff --git a/marked/Rel-11/23_series/23852/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-11/23_series/23852/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36513c03a4af088a3d5dd85268204cba57e8c883 --- /dev/null +++ b/marked/Rel-11/23_series/23852/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc5532f4b91d55bc23152421668678747849c744d1ea8617b6f9a5877917d9d5 +size 13340 diff --git a/marked/Rel-11/23_series/23852/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/Rel-11/23_series/23852/848073118eebfdbfdb9a60e3923fe0b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f88454dff08f600909971467ff8076aa17f1e46 --- /dev/null +++ b/marked/Rel-11/23_series/23852/848073118eebfdbfdb9a60e3923fe0b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48182e1a945978dc62c2a9dd58da7573ea1518e3a37b3f3ccbd80ca905a092b7 +size 83042 diff --git a/marked/Rel-11/23_series/23852/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-11/23_series/23852/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4acdd690f6aac91e02b3510b3c4cf4d8eaf222b --- /dev/null +++ b/marked/Rel-11/23_series/23852/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:195faff66e850957947189383517613021af9dbe13f084d6e9fc4774483fa130 +size 66434 diff --git a/marked/Rel-11/23_series/23852/879d68959f0c0ba370ef82447298ba17_img.jpg b/marked/Rel-11/23_series/23852/879d68959f0c0ba370ef82447298ba17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e62db7df565c20306db5ad510e186028a8ea1b09 --- /dev/null +++ b/marked/Rel-11/23_series/23852/879d68959f0c0ba370ef82447298ba17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:026e8bb755a9408c1af70e5591017b17184db554b0f000520ea27b07aee4f320 +size 65246 diff --git a/marked/Rel-11/23_series/23852/896e86ed12aff206d302c64f2e3091fa_img.jpg b/marked/Rel-11/23_series/23852/896e86ed12aff206d302c64f2e3091fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b6adef7ae020782904545b550988869fc80f9f7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/896e86ed12aff206d302c64f2e3091fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d98a0d809ba10301501bdf7db3a79c2bb7e73e3a1c63fbb51ce909452be10715 +size 52086 diff --git a/marked/Rel-11/23_series/23852/8bd7adf738ea4b7e65e0d6f67e122d55_img.jpg b/marked/Rel-11/23_series/23852/8bd7adf738ea4b7e65e0d6f67e122d55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4deead5c3e56cb93090fc6487cd7cb8dc6df1153 --- /dev/null +++ b/marked/Rel-11/23_series/23852/8bd7adf738ea4b7e65e0d6f67e122d55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee347c869c49eb1424d5ca058fad0c275d091dacbd54d833f581232deb4a61c1 +size 84753 diff --git a/marked/Rel-11/23_series/23852/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-11/23_series/23852/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2222c907cdd7311d5763f4005bd706b1436772dd --- /dev/null +++ b/marked/Rel-11/23_series/23852/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:972c29b8171b37ca7788ba3446e12c5a746a39dc21266e4228254a22be389bba +size 71141 diff --git a/marked/Rel-11/23_series/23852/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-11/23_series/23852/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9179ddd0046beece05368338997fb6329978ff5 --- /dev/null +++ b/marked/Rel-11/23_series/23852/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e32adc8d1e850ee2c864bbbdaf0d0bd3925458090f582e325bc92b93e843b3a0 +size 71174 diff --git a/marked/Rel-11/23_series/23852/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/23_series/23852/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f90498fb7ec498e4826941eff17fba7295bfc2a --- /dev/null +++ b/marked/Rel-11/23_series/23852/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08a017ea88facce9ba346d6058d6cdb01eae8c90cee19e2eb3b9011b7ec0e8a8 +size 84972 diff --git a/marked/Rel-11/23_series/23852/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/23_series/23852/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2851ddf9245c32e4279caeec4a2c17e09d37432 --- /dev/null +++ b/marked/Rel-11/23_series/23852/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a2751be13b9c233e07200de36526873ed25f141a84854a854edde1d8b9a587c +size 60615 diff --git a/marked/Rel-11/23_series/23852/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/Rel-11/23_series/23852/90ddf538ef276510e2b631f7b96654e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..182673c6bf7b95fb450584630ed14a978c8adace --- /dev/null +++ b/marked/Rel-11/23_series/23852/90ddf538ef276510e2b631f7b96654e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ecb337bdd1cd6d4a7394f67bc270b2bcc833890af07cb35b8980c90e9701d06 +size 82303 diff --git a/marked/Rel-11/23_series/23852/90ee16ccc0ad16aeca48087797d7b07f_img.jpg b/marked/Rel-11/23_series/23852/90ee16ccc0ad16aeca48087797d7b07f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d450a1433c31b111b83de85218dc885f6e3572c --- /dev/null +++ b/marked/Rel-11/23_series/23852/90ee16ccc0ad16aeca48087797d7b07f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf4807c76651275cac032b7e7606e4a805cc95755a0a20cfab82f60b2e263227 +size 81652 diff --git a/marked/Rel-11/23_series/23852/94acd33fcad85bb6f207a308f9b63191_img.jpg b/marked/Rel-11/23_series/23852/94acd33fcad85bb6f207a308f9b63191_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a06f2cf268b74cc100d433b87685f5efd9b3a22 --- /dev/null +++ b/marked/Rel-11/23_series/23852/94acd33fcad85bb6f207a308f9b63191_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a346a85756c949cfcf2d1c14fccec6d83256bb046c3116091d69d24201c4355d +size 56952 diff --git a/marked/Rel-11/23_series/23852/94d3fdcc244924326f02533aeb2d93fc_img.jpg b/marked/Rel-11/23_series/23852/94d3fdcc244924326f02533aeb2d93fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e14b3950bdb6721b0291e9a6e3db1d52e711fc31 --- /dev/null +++ b/marked/Rel-11/23_series/23852/94d3fdcc244924326f02533aeb2d93fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efa7a81e57446362903ba9e9b34ae17e638fc7271480bd6a142466aa0a3a5030 +size 162079 diff --git a/marked/Rel-11/23_series/23852/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/Rel-11/23_series/23852/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f9691f1a59eff783e8e2c63fa391043e1c3b0a4 --- /dev/null +++ b/marked/Rel-11/23_series/23852/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bc22456f7c7f1a04cececb57d210bdaab1899da9d7fc5408b16adad03e278c3 +size 63799 diff --git a/marked/Rel-11/23_series/23852/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-11/23_series/23852/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d36bf35533cd1f928b46a9b1f5cae1457acb5af --- /dev/null +++ b/marked/Rel-11/23_series/23852/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef7386484398b5f9e6aef2fa953e8b51ffee49be4ab47beffa1322bbdaee0efc +size 82965 diff --git a/marked/Rel-11/23_series/23852/9b25cfd1657391070da4ca3e922b82b1_img.jpg b/marked/Rel-11/23_series/23852/9b25cfd1657391070da4ca3e922b82b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10022e9d019ae83a9fbade5c6d2eb27d56c55fd2 --- /dev/null +++ b/marked/Rel-11/23_series/23852/9b25cfd1657391070da4ca3e922b82b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53e2820c7cc62ee153c8d2f5710f70412f9fd4e1dfbe2a495e2cbde9860b0a8f +size 54278 diff --git a/marked/Rel-11/23_series/23852/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-11/23_series/23852/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c79aadb7e0d6077fa281fce04fa86f85ff2f2797 --- /dev/null +++ b/marked/Rel-11/23_series/23852/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:193c3a3218b20ab171e969385611a01a2bb4480c6550c3349e235deade90c7b9 +size 50855 diff --git a/marked/Rel-11/23_series/23852/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-11/23_series/23852/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78f065663bfed1aae971cc1603f6cd7b89555630 --- /dev/null +++ b/marked/Rel-11/23_series/23852/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:682759b908574d3d2283894b1900ef10b3c5d8443fc458cedd7306a6c57878f4 +size 85433 diff --git a/marked/Rel-11/23_series/23852/9dc9f41d7d76c1add4b190d348cb1533_img.jpg b/marked/Rel-11/23_series/23852/9dc9f41d7d76c1add4b190d348cb1533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16244a35d79d65a617161d137bc23023f4ba87c7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/9dc9f41d7d76c1add4b190d348cb1533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbeb67a580c152fa698f82ceae571ec2e8effeda66a1e7b234de32bc791c2a18 +size 60148 diff --git a/marked/Rel-11/23_series/23852/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg b/marked/Rel-11/23_series/23852/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c9d7cc0db33fe66f4180936ddf7a7497e962aa8 --- /dev/null +++ b/marked/Rel-11/23_series/23852/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8ecf23bb24ebc1cc74ce18ec981a3ecd4e96e6d3cb9590e16071fe4bb628642 +size 91257 diff --git a/marked/Rel-11/23_series/23852/9edb407536d4d4d4a6ac391527af047c_img.jpg b/marked/Rel-11/23_series/23852/9edb407536d4d4d4a6ac391527af047c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e55d040e059002d1208cfa9a8e879d0cf80def5 --- /dev/null +++ b/marked/Rel-11/23_series/23852/9edb407536d4d4d4a6ac391527af047c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7e3e259444b7587f3839d2e5ea46eed0f3411074d6506092c86793394dd9165 +size 124425 diff --git a/marked/Rel-11/23_series/23852/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/23_series/23852/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f60a4cf84f0b7ba207caeb28130256b8ad0069ed --- /dev/null +++ b/marked/Rel-11/23_series/23852/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2f4aca1b41441d53aacd10fd633383b4b70841a1f4f2022a4c439cdec0c62de +size 86832 diff --git a/marked/Rel-11/23_series/23852/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-11/23_series/23852/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7c30b7469b52ee6771af136718d1369fd176c72 --- /dev/null +++ b/marked/Rel-11/23_series/23852/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2042668732309bff7c746bbc0f017d3827fb86317f323262c74af63dac83e112 +size 173333 diff --git a/marked/Rel-11/23_series/23852/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/Rel-11/23_series/23852/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e523f78e5df6fe1366b4a3d1372fa19ebcb96805 --- /dev/null +++ b/marked/Rel-11/23_series/23852/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46ca486718bd1a9202d6a3811e8953570165350a8708172702ea2337f846f555 +size 67399 diff --git a/marked/Rel-11/23_series/23852/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-11/23_series/23852/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e110fa2dbcb0763a74f5961da3988abb57aa6e4 --- /dev/null +++ b/marked/Rel-11/23_series/23852/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:533544a3fb05a883d4b0a5d5dce5d6cc0fc4c77957a9c282630a74c290b9731c +size 52655 diff --git a/marked/Rel-11/23_series/23852/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/23_series/23852/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecee9e3b9e71ab7b8a09fa4167f81ac901f0f524 --- /dev/null +++ b/marked/Rel-11/23_series/23852/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df561aa9469fb864bb8f073bfee4989869256d509c2cc420a5f444c39ce31d3f +size 172578 diff --git a/marked/Rel-11/23_series/23852/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-11/23_series/23852/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52b4c16c94faf25a0782e3ae2d2d04ca8f65fd7b --- /dev/null +++ b/marked/Rel-11/23_series/23852/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e89f73b617d3ba1ee58ecb31d54fbf9e0bc295d1fedd670e40c9b225371734be +size 45042 diff --git a/marked/Rel-11/23_series/23852/a3083eec2a883ee8327b3c24174df6a9_img.jpg b/marked/Rel-11/23_series/23852/a3083eec2a883ee8327b3c24174df6a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efa37ffb52933e9a22087b0dc53abab64d6edce6 --- /dev/null +++ b/marked/Rel-11/23_series/23852/a3083eec2a883ee8327b3c24174df6a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dd1c2c77e774103a600c8081e06f10b6061ef6790a1d33ff6473fbd382b0c67 +size 65944 diff --git a/marked/Rel-11/23_series/23852/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/23_series/23852/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf68b18e5d9b69bc977146b2b3ecb04a10a2ebd7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35ad648bfaea13244e5902fc77840024f7a7def31fdd6f93e6f53120e78beaad +size 103069 diff --git a/marked/Rel-11/23_series/23852/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-11/23_series/23852/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e76c3e5ecb3dde849ec2b35720a7f1fad2e4003 --- /dev/null +++ b/marked/Rel-11/23_series/23852/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d82a0fc992e20d6b3433aabec9e81fbf359bcc9df0623b4664e695b506a58531 +size 142989 diff --git a/marked/Rel-11/23_series/23852/a47713c2491e6ce619259ed2f196fd24_img.jpg b/marked/Rel-11/23_series/23852/a47713c2491e6ce619259ed2f196fd24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30d56fee419f8d70fe5a266bbcf91924f5dc7517 --- /dev/null +++ b/marked/Rel-11/23_series/23852/a47713c2491e6ce619259ed2f196fd24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65daa7bc5f7df480d374774b60b33daa27ba4f7c9014feeff9312c2780d24863 +size 20467 diff --git a/marked/Rel-11/23_series/23852/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Rel-11/23_series/23852/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25dc73b8e635f4ecd0099dbdb8c87441ef389756 --- /dev/null +++ b/marked/Rel-11/23_series/23852/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0074d93f0123c59f24f8ee2802d4e34739a38ec909593277353555270a8cd52a +size 74335 diff --git a/marked/Rel-11/23_series/23852/a4bfa2343d75076b79f7e33d93915e00_img.jpg b/marked/Rel-11/23_series/23852/a4bfa2343d75076b79f7e33d93915e00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83abd9a99131a285211150a9f7fa7098b210beda --- /dev/null +++ b/marked/Rel-11/23_series/23852/a4bfa2343d75076b79f7e33d93915e00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70df23eb1c61539312f0f4a3c1d8f8566028626495a5f3bb0a263d900bc597f8 +size 39628 diff --git a/marked/Rel-11/23_series/23852/a6f9ef297168667527ab18da412f917d_img.jpg b/marked/Rel-11/23_series/23852/a6f9ef297168667527ab18da412f917d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02fa4bdf776bb6ca9fecf48debe74045f402c927 --- /dev/null +++ b/marked/Rel-11/23_series/23852/a6f9ef297168667527ab18da412f917d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac07b0f3cd9a22d2c948818819b7cf26343adac28c2e26c8d8f4bd3fea087c8d +size 65709 diff --git a/marked/Rel-11/23_series/23852/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-11/23_series/23852/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b83ab1a5f76d69964818b6e56eb6c4b63713d88 --- /dev/null +++ b/marked/Rel-11/23_series/23852/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ceacf154c8669e1b89cfbb27924d4baea3883c7a603cfd3902cd5ce680a670a4 +size 118593 diff --git a/marked/Rel-11/23_series/23852/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/Rel-11/23_series/23852/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67b488493cab332703d7253d8bbec6b11779a963 --- /dev/null +++ b/marked/Rel-11/23_series/23852/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c62b3cdd94b16d86199bd28daa8cd7dec1d6930afa31755ffe7a462386801526 +size 4905 diff --git a/marked/Rel-11/23_series/23852/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/23_series/23852/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7a17f094baba0900c0ccbe50ce0aa18afbda27a --- /dev/null +++ b/marked/Rel-11/23_series/23852/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:776a372e9bbde794c857f53d1419ac60e64155d868e855a3add1b302560d9f96 +size 84953 diff --git a/marked/Rel-11/23_series/23852/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-11/23_series/23852/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc99b062b74b121cf213183c01415104a8177a6a --- /dev/null +++ b/marked/Rel-11/23_series/23852/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f5aed83a5106298e575c9f9bc5b64bc6a9ec07695bdc74115473bd76440edfd +size 222910 diff --git a/marked/Rel-11/23_series/23852/b0211cee4b20034939d883ac0d70f696_img.jpg b/marked/Rel-11/23_series/23852/b0211cee4b20034939d883ac0d70f696_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e551bf6443ce98161105ac48fed4fb608f3236ad --- /dev/null +++ b/marked/Rel-11/23_series/23852/b0211cee4b20034939d883ac0d70f696_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67398274e4f682ee44bbe872d0d3241b96a79b01cba5bef1a9b8548280d598af +size 58914 diff --git a/marked/Rel-11/23_series/23852/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-11/23_series/23852/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb47440bb0b78b9755ee32c02bc763c36a463d79 --- /dev/null +++ b/marked/Rel-11/23_series/23852/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7602eccfbba4b87de8b69725c34f318d10020dd03b9c06944d435cccac84713a +size 80592 diff --git a/marked/Rel-11/23_series/23852/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23852/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01e1dbf78a70446a2609a1540e5d160e78df3444 --- /dev/null +++ b/marked/Rel-11/23_series/23852/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2898b291a46fb4d7a119a849845b110a02d0369936692fa18ecdcfe2d10ca8c6 +size 115039 diff --git a/marked/Rel-11/23_series/23852/b3c108e7145f2017957569d06ea359cb_img.jpg b/marked/Rel-11/23_series/23852/b3c108e7145f2017957569d06ea359cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..645a36ef9f3a3a5d71fbcc70056aa4d13164e329 --- /dev/null +++ b/marked/Rel-11/23_series/23852/b3c108e7145f2017957569d06ea359cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39e93599046ededf305ec249716447dbabf5d6e194d5463007d584707cb202b3 +size 44400 diff --git a/marked/Rel-11/23_series/23852/b6ad8b32179842fca5ad086cf22b03eb_img.jpg b/marked/Rel-11/23_series/23852/b6ad8b32179842fca5ad086cf22b03eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5be9843e11403a590b1c2107c58fa3dcb18e8de --- /dev/null +++ b/marked/Rel-11/23_series/23852/b6ad8b32179842fca5ad086cf22b03eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:117a885c1bbf7385bd966bfc3ee9ed2f56756b0c9f817cb78572d33fe6cc662c +size 63151 diff --git a/marked/Rel-11/23_series/23852/b6e90f8ae3109449704b9b5c7951f631_img.jpg b/marked/Rel-11/23_series/23852/b6e90f8ae3109449704b9b5c7951f631_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba843fb0b01813ea78f919b44eecb3e576a184c7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/b6e90f8ae3109449704b9b5c7951f631_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d0dfcd7a6d123cd608a59a6c15f97428a1921e3273d06bae4ca73020b6c816a +size 45592 diff --git a/marked/Rel-11/23_series/23852/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg b/marked/Rel-11/23_series/23852/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..744a2d5d868fef6d6749e4f649819dded03bf366 --- /dev/null +++ b/marked/Rel-11/23_series/23852/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d34208bce397098a92ea7a0812cb0b7e7c06ebb17846776edb3a82fb4be8bb28 +size 103947 diff --git a/marked/Rel-11/23_series/23852/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-11/23_series/23852/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..430d674c1106fbc92cc659dcaf6e68f52d24d974 --- /dev/null +++ b/marked/Rel-11/23_series/23852/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e53943f432dd80d4b15db3544ebb4cf061029af04f3b3d507896aa5f06801305 +size 50083 diff --git a/marked/Rel-11/23_series/23852/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-11/23_series/23852/b904ac2472cab80892d1e783e6230d6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9f2314d65a6b328808393829c61ee1217d1ef32 --- /dev/null +++ b/marked/Rel-11/23_series/23852/b904ac2472cab80892d1e783e6230d6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2867d0ade7c317d775ce8e4ec569db41b20d4c14956e1037d7777ee660cc994 +size 51810 diff --git a/marked/Rel-11/23_series/23852/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/Rel-11/23_series/23852/c036e2540a94b31357ceb0002f0cacab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d05ca494839bec1cefa25a013220ced2f6f7f2f5 --- /dev/null +++ b/marked/Rel-11/23_series/23852/c036e2540a94b31357ceb0002f0cacab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:779aef52840f5be68d64838293fff23c74c2015130bf26ee290d9698d2420055 +size 36140 diff --git a/marked/Rel-11/23_series/23852/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-11/23_series/23852/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f98dbe9139d89a202a75980832681e4fa0ba92a7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb7af620d950c70ee6399db4bfd88f34e45984b8e08a9ab56ea35a02dcb1ac75 +size 73351 diff --git a/marked/Rel-11/23_series/23852/c419b566d720267c499087add1506018_img.jpg b/marked/Rel-11/23_series/23852/c419b566d720267c499087add1506018_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9974156107fda8367565bd8f1123614629314744 --- /dev/null +++ b/marked/Rel-11/23_series/23852/c419b566d720267c499087add1506018_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08db846d76280a77e82197f1a56a2a8b1497a3ead56402e50367dccbee6c70bc +size 26692 diff --git a/marked/Rel-11/23_series/23852/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/Rel-11/23_series/23852/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b40bf365eb67d1fbfd04cc85612ff81cbd6e9254 --- /dev/null +++ b/marked/Rel-11/23_series/23852/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f12cef8ffef8487a54b6b044b75ccc41416aa8dd4d54625ba3df81340fe1849 +size 89842 diff --git a/marked/Rel-11/23_series/23852/c79b9212cfc136d4191e637cd9437ffb_img.jpg b/marked/Rel-11/23_series/23852/c79b9212cfc136d4191e637cd9437ffb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2774de424817316c7f45386464f562c8ac6f1ac5 --- /dev/null +++ b/marked/Rel-11/23_series/23852/c79b9212cfc136d4191e637cd9437ffb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb583aa9643da4fcb2453da14fa73420709f86a0d5b816a7af885de4bee1fdb8 +size 7370 diff --git a/marked/Rel-11/23_series/23852/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/23_series/23852/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3d60ca376fc71f5c2e230225e632df8b25d3549 --- /dev/null +++ b/marked/Rel-11/23_series/23852/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1df8eeafa7e56ce29f8e8b6c5830d9294f539f5b9ecbc5f6e0858da8bbf53674 +size 133074 diff --git a/marked/Rel-11/23_series/23852/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Rel-11/23_series/23852/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95094c3f0417bf415cd722d30e01cd377461af3f --- /dev/null +++ b/marked/Rel-11/23_series/23852/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecff0dad2458176397a640366b3e7fe375acbc06150d9d4269d74f406bafa498 +size 57282 diff --git a/marked/Rel-11/23_series/23852/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg b/marked/Rel-11/23_series/23852/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35afb4bcac1cafeadff9f5e68d525336557221d0 --- /dev/null +++ b/marked/Rel-11/23_series/23852/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92b9d4d1355158c572766ec10d322b20d7dfa33d16872c9b90c2e9218a516b7c +size 108347 diff --git a/marked/Rel-11/23_series/23852/cf018d13814389b0bd7f94a2f9bb812a_img.jpg b/marked/Rel-11/23_series/23852/cf018d13814389b0bd7f94a2f9bb812a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50be084cdf20ed9c2160067501a48ac28d24ecd6 --- /dev/null +++ b/marked/Rel-11/23_series/23852/cf018d13814389b0bd7f94a2f9bb812a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5422e6293866fe8d96cced451d76140c48cf8aaf5c9a1b479b8fef5175cf0ed +size 78896 diff --git a/marked/Rel-11/23_series/23852/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/marked/Rel-11/23_series/23852/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83abd9a99131a285211150a9f7fa7098b210beda --- /dev/null +++ b/marked/Rel-11/23_series/23852/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70df23eb1c61539312f0f4a3c1d8f8566028626495a5f3bb0a263d900bc597f8 +size 39628 diff --git a/marked/Rel-11/23_series/23852/d116934392360da963e91d840d1e45a8_img.jpg b/marked/Rel-11/23_series/23852/d116934392360da963e91d840d1e45a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb779f3fef13ccd1a5c4e1e56a5fb3c7f1fbba17 --- /dev/null +++ b/marked/Rel-11/23_series/23852/d116934392360da963e91d840d1e45a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f47248c463566d7411f37cbdcc76a679854d5e08841417ac4bf012ff4d3de853 +size 12795 diff --git a/marked/Rel-11/23_series/23852/d244183a8ff3d94b0dcf30140f51020d_img.jpg b/marked/Rel-11/23_series/23852/d244183a8ff3d94b0dcf30140f51020d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f21c8039bf14674ca5290d69895875c68936340a --- /dev/null +++ b/marked/Rel-11/23_series/23852/d244183a8ff3d94b0dcf30140f51020d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c23ff921078abcb5de32b3844205163e726925d3c45590c6e5e8236b9b2aaf65 +size 77879 diff --git a/marked/Rel-11/23_series/23852/d793cf7c174b89eb024d132f00679787_img.jpg b/marked/Rel-11/23_series/23852/d793cf7c174b89eb024d132f00679787_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cea941d8fae303d190824077061d57931d239b7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/d793cf7c174b89eb024d132f00679787_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5557a890cfd6c2470e6b145899d1537573c13d1034dce46781c1f01b7b9d5de5 +size 38471 diff --git a/marked/Rel-11/23_series/23852/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-11/23_series/23852/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30cadd80d9ba9b9386f7455978bbc89089e93c9a --- /dev/null +++ b/marked/Rel-11/23_series/23852/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe7a7c7448416cef26ebe7342baeecb17c17c87b21b072c6e9db8c5ce7bc8900 +size 84186 diff --git a/marked/Rel-11/23_series/23852/daf05db9f13b34fb12da52f007bbfe5b_img.jpg b/marked/Rel-11/23_series/23852/daf05db9f13b34fb12da52f007bbfe5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..744a2d5d868fef6d6749e4f649819dded03bf366 --- /dev/null +++ b/marked/Rel-11/23_series/23852/daf05db9f13b34fb12da52f007bbfe5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d34208bce397098a92ea7a0812cb0b7e7c06ebb17846776edb3a82fb4be8bb28 +size 103947 diff --git a/marked/Rel-11/23_series/23852/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-11/23_series/23852/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a192f12613d40ed450d2c777d1f8e7578d89a4bd --- /dev/null +++ b/marked/Rel-11/23_series/23852/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e73970293981703a6760a4e2975b299d71c2efa9c6d7034972f6c5b2c06230ee +size 74649 diff --git a/marked/Rel-11/23_series/23852/df1966d80c74bc127f159a48f38b13ee_img.jpg b/marked/Rel-11/23_series/23852/df1966d80c74bc127f159a48f38b13ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15ad619f813f4dd13777f73e1820d6842e92581a --- /dev/null +++ b/marked/Rel-11/23_series/23852/df1966d80c74bc127f159a48f38b13ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afde777d30510a6db8ee7756ab6aab3f2cfa673e4015b204880a50d1c7415cf7 +size 222675 diff --git a/marked/Rel-11/23_series/23852/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/23_series/23852/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c07a371497f2d68d9e082bd9b15e136e9e633f1 --- /dev/null +++ b/marked/Rel-11/23_series/23852/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36fecb84f853d2dd0a4cfbc57e0de6af46edb9e145def4c5ebbbcd0b2033465d +size 65322 diff --git a/marked/Rel-11/23_series/23852/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-11/23_series/23852/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daeee6adbc6e11db2b48e2ce788e0ee4883f99e7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:538fafb6627b71e810113448bb3db8934ae0c1423836cad74129ba6cec402d07 +size 103176 diff --git a/marked/Rel-11/23_series/23852/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-11/23_series/23852/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d61eba0cb127b315e1a853dc605bcf237e1faba3 --- /dev/null +++ b/marked/Rel-11/23_series/23852/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b788e18f3946bdf9fdb9e2cd16464d3965680677589609f0eab2dae4f4c60795 +size 79521 diff --git a/marked/Rel-11/23_series/23852/e90b25c8d90cadc3f76c376701cf27ed_img.jpg b/marked/Rel-11/23_series/23852/e90b25c8d90cadc3f76c376701cf27ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0db5811ad343de8b5e11424eb06a13cbe473712 --- /dev/null +++ b/marked/Rel-11/23_series/23852/e90b25c8d90cadc3f76c376701cf27ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1c9b2f04a1bd7bb8ca78e53983c513b6755f037821807a439f2c9ea951d2165 +size 86591 diff --git a/marked/Rel-11/23_series/23852/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/marked/Rel-11/23_series/23852/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9e3e8475ea924b1d7371d6426b65aeab1b08b22 --- /dev/null +++ b/marked/Rel-11/23_series/23852/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:850dbecae1725b4be53a67dbbef914301bf5b8115f16dc561f1ea0992aad37a3 +size 13400 diff --git a/marked/Rel-11/23_series/23852/ef5f5c6665b6ae13660ede412333ba45_img.jpg b/marked/Rel-11/23_series/23852/ef5f5c6665b6ae13660ede412333ba45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e3104adcfd908d9915cb5883a92e3a3fa2322da --- /dev/null +++ b/marked/Rel-11/23_series/23852/ef5f5c6665b6ae13660ede412333ba45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fdbbd97cb7c079661f48490da78a3ecab309f01895ef140de824d193be985c4 +size 108104 diff --git a/marked/Rel-11/23_series/23852/efb282bed9f06eef1987a14fb27bc599_img.jpg b/marked/Rel-11/23_series/23852/efb282bed9f06eef1987a14fb27bc599_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..887c8466dcaaf347ba4f73b7f4368b7d57f78bf8 --- /dev/null +++ b/marked/Rel-11/23_series/23852/efb282bed9f06eef1987a14fb27bc599_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3499f133899cdb7b0c08bbc82f8efcf4ea842c1a2bf970c2f3f979926965fa50 +size 49143 diff --git a/marked/Rel-11/23_series/23852/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-11/23_series/23852/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de5f9774c9bbb81c340e5dd2a040d54b1756592e --- /dev/null +++ b/marked/Rel-11/23_series/23852/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36d8f3386f61058bec0857bce8de673f851de031f5e9a4059f4c99b58068de80 +size 23257 diff --git a/marked/Rel-11/23_series/23852/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/marked/Rel-11/23_series/23852/f5deee2f3301ee351c4008283ffafbb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01af477a44fdbcd12220f4bfe67fc68f1fb84f49 --- /dev/null +++ b/marked/Rel-11/23_series/23852/f5deee2f3301ee351c4008283ffafbb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54de2104210cebb8b8ed7d189770ed4a1681b6d2a606b295145a9ee348300e78 +size 52578 diff --git a/marked/Rel-11/23_series/23852/f76f0f5dfff2511b51f6b875867c029f_img.jpg b/marked/Rel-11/23_series/23852/f76f0f5dfff2511b51f6b875867c029f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..430d674c1106fbc92cc659dcaf6e68f52d24d974 --- /dev/null +++ b/marked/Rel-11/23_series/23852/f76f0f5dfff2511b51f6b875867c029f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e53943f432dd80d4b15db3544ebb4cf061029af04f3b3d507896aa5f06801305 +size 50083 diff --git a/marked/Rel-11/23_series/23852/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/Rel-11/23_series/23852/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8dba9b93919c4bc5bd31ff61cea4cfcf5c791d7 --- /dev/null +++ b/marked/Rel-11/23_series/23852/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c49d82ff612f9d4926d3c5011104414b438d7dfa9a417407677382c8495e732 +size 71191 diff --git a/marked/Rel-11/23_series/23852/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-11/23_series/23852/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1878eecf0ffacaa645c2d559eacf9995f8263b9 --- /dev/null +++ b/marked/Rel-11/23_series/23852/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2054e6fb087cd070c634e82ea406a528264633f6436fa9197ff2973b00e53350 +size 92027 diff --git a/marked/Rel-11/23_series/23852/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-11/23_series/23852/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd61bb2eac51e6da1dbab833558f2a629b3224c5 --- /dev/null +++ b/marked/Rel-11/23_series/23852/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cab96a12796be4f752eedccd6cc51344300c1c2cbf4b9353c8569dc3e6a1a1be +size 77831 diff --git a/marked/Rel-11/23_series/23852/raw.md b/marked/Rel-11/23_series/23852/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7ec6663cb29aadefb4464a80b660c2cda981d5b3 --- /dev/null +++ b/marked/Rel-11/23_series/23852/raw.md @@ -0,0 +1,10009 @@ +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Abbreviations ..... | 10 | +| 4 Scenarios..... | 11 | +| 5 Architectural assumptions..... | 11 | +| 5.1 Architectural assumptions for GTP based S2a..... | 11 | +| 5.2 Architectural assumptions for WLAN access to EPC through S2a ..... | 11 | +| 5.2.1 Assumptions for solutions with no Impact to the UE..... | 12 | +| 6 Solutions for GTP based S2a ..... | 12 | +| 6.1 Solution 1 ..... | 13 | +| 6.1.1 Architecture ..... | 13 | +| 6.1.2 Functional description ..... | 15 | +| 6.1.2.1 Bearer model for a PDN connection..... | 15 | +| 6.1.3 Information flows ..... | 15 | +| 6.1.3.1 Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW ..... | 15 | +| 6.1.3.2 Detach and PDN Disconnection with GTP on S2a..... | 18 | +| 6.1.3.2.1 UE/Trusted Non-3GPP IP Access Network Initiated Detach and UE/Trusted Non-3GPP IP Access requested PDN Disconnection Procedure with GTP on S2a ..... | 18 | +| 6.1.3.2.2 HSS/AAA Initiated Detach Procedure with GTP on S2a ..... | 19 | +| 6.1.3.3 UE-initiated Connectivity to Additional PDN with GTP on S2a ..... | 19 | +| 6.1.3.4 Dedicated bearer activation with GTP on S2a..... | 21 | +| 6.1.3.5 Network-initiated S2a bearer modification with GTP on S2a ..... | 22 | +| 6.1.3.5.1 PDN GW Initiated Bearer Modification ..... | 22 | +| 6.1.3.5.2 HSS Initiated Subscribed QoS Modification ..... | 23 | +| 6.1.3.6 PDN GW initiated Resource Allocation Deactivation with GTP on S2a..... | 24 | +| 6.1.3.7 Handovers without Optimizations Between 3GPP Accesses and Non-3GPP IP Accesses with S2a GTP..... | 25 | +| 6.1.3.7.1 Handover from a trusted non-3GPP IP access with S2a GTP to 3GPP Access..... | 25 | +| 6.1.3.7.2 Handover from 3GPP Access to a trusted non-3GPP IP access with S2a GTP..... | 26 | +| 7 Additional considerations for WLAN access to EPC through S2a for Phase 1 ..... | 28 | +| 7.1 Solutions without UE Impact ..... | 28 | +| 7.1.0 General ..... | 28 | +| 7.1.1 Solution 1 ..... | 28 | +| 7.1.1.1 Reference model ..... | 28 | +| 7.1.1.2 Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW ..... | 31 | +| 7.1.1.3 Without-UE-impact procedures except Initial Attach ..... | 33 | +| 7.1.1.4 SaMOG deployment ..... | 33 | +| 7.1.1.5 PMIP based S2a considerations..... | 33 | +| 7.1.2 Solution 2..... | 34 | +| 7.1.2.0 General..... | 34 | +| 7.1.2.1 Reference Model..... | 34 | +| 7.1.2.2 Network elements ..... | 36 | +| 7.1.2.2.1 UE..... | 36 | +| 7.1.2.2.2 Trusted WLAN AAA Proxy ..... | 36 | +| 7.1.2.2.3 Trusted WLAN Access Gateway ..... | 36 | +| 7.1.2.3 Reference Points ..... | 37 | +| 7.1.2.3.1 Ta reference point..... | 37 | +| 7.1.2.3.2 Tg reference point ..... | 37 | +| 7.1.2.3.3 Tn reference point ..... | 37 | +| 7.1.2.3.4 Tw reference point ..... | 38 | +| 7.1.2.3.5 Tu reference point ..... | 38 | + +| | | | +|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 7.1.2.4 | Procedures..... | 38 | +| 7.1.2.4.1 | Initial Attach to Trusted Non-3GPP WLAN Access procedure ..... | 39 | +| 7.1.2.4.2 | UE/Trusted Non-3GPP WLAN Access Network Initiated Detach procedure..... | 40 | +| 7.1.2.4.3 | HSS/AAA Initiated Detach procedure ..... | 41 | +| 7.1.2.4.4 | Other procedures ..... | 41 | +| 7.1.3 | Handovers with or without TNSP/TWAG relocation with unmodified UEs..... | 41 | +| 8 | Additional considerations for WLAN access to EPC through S2a for Phase 2..... | 41 | +| 8.1 | Requirements..... | 41 | +| 8.1A | Key issues..... | 42 | +| 8.2 | Solutions..... | 43 | +| 8.2.1 | Solution 1: Tunnelled approach with dedicated UE-TWAG control protocol..... | 43 | +| 8.2.1.1 | Functional Description..... | 43 | +| 8.2.1.1.1 | Overview ..... | 43 | +| 8.2.1.1.2 | User plane..... | 43 | +| 8.2.1.1.2.1 | Alternative 1: XYZ = GRE..... | 44 | +| 8.2.1.1.1.2.2 | Alternative 2: XYZ = VLAN ..... | 44 | +| 8.2.1.1.3 | Control plane ..... | 44 | +| 8.2.1.1.3.1 | Alternative 1: L2.5-based control protocol..... | 44 | +| 8.2.1.1.3.2 | Alternative 2: L3-based control protocol..... | 45 | +| 8.2.1.1.4 | Protocol Stacks ..... | 45 | +| 8.2.1.2 | Procedures..... | 46 | +| 8.2.1.2.1 | Initial Attach in WLAN on S2a..... | 46 | +| 8.2.1.2.2 | Initial Attach in single-connection scenario in WLAN on S2a (continuation) ..... | 47 | +| 8.2.1.2.2.1 | Initial Attach in single-connection scenario in WLAN on GTP S2a (continuation)..... | 47 | +| 8.2.1.2.2.2 | Initial Attach in single-connection scenario in WLAN on PMIP S2a (continuation) ..... | 47 | +| 8.2.1.2.3 | Initial Attach in multi-connection scenario in WLAN on S2a (continuation) ..... | 48 | +| 8.2.1.2.4 | UE-Initiated Connectivity to PDN in WLAN on S2a..... | 48 | +| 8.2.1.2.4.1 | UE-Initiated Connectivity to PDN in WLAN on GTP S2a..... | 48 | +| 8.2.1.2.4.2 | UE-Initiated Connectivity to PDN in WLAN on PMIP S2a ..... | 49 | +| 8.2.1.2.5 | Handover procedure in single-connection scenario from 3GPP access to WLAN on S2a..... | 50 | +| 8.2.1.2.5.1 | Handover in single-connection scenario from 3GPP access to WLAN on GTP S2a ..... | 50 | +| 8.2.1.2.5.2 | Handover in single-connection scenario from 3GPP access to WLAN on PMIP S2a..... | 51 | +| 8.2.1.2.6 | Handover procedure in multi-connection scenario from 3GPP access to WLAN on S2a..... | 51 | +| 8.2.1.2.6.1 | Handover in multi-connection scenario from 3GPP access to WLAN on GTP S2a..... | 51 | +| 8.2.1.2.6.2 | Handover from 3GPP access to WLAN on PMIP S2a..... | 53 | +| 8.2.1.2.7 | Handover procedure from WLAN on S2a to 3GPP access..... | 54 | +| 8.2.1.2.8 | Detach and PDN disconnection in WLAN on S2a ..... | 55 | +| 8.2.1.2.8.1 | Detach and PDN disconnection in WLAN on GTP S2a ..... | 55 | +| 8.2.1.2.8.1.1 | UE/TWAN Initiated Detach and UE/TWAN requested PDN Disconnection Procedure<br>in WLAN on GTP S2a..... | 55 | +| 8.2.1.2.8.1.2 | HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a..... | 56 | +| 8.2.1.2.8.2 | Detach and PDN disconnection in WLAN on PMIP S2a ..... | 56 | +| 8.2.1.2.9 | PDN GW initiated Resource Allocation Deactivation..... | 56 | +| 8.2.1.2.9.1 | PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a ..... | 56 | +| 8.2.1.2.9.2 | PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a..... | 56 | +| 8.2.1.3 | Impacts on existing nodes or functionality ..... | 56 | +| 8.2.1.4 | Evaluation ..... | 56 | +| 8.2.2 | Solution 2: Layer 2 solution based on Stateful Address Configuration of Per-PDN<br>Connection/NSWO Point-to-Point Link Multiplexed at Layer 2..... | 57 | +| 8.2.2.1 | Functional Description..... | 57 | +| 8.2.2.1.1 | User Plane Multiplexing for Per-PDN Connection / NSWO Point-to-Point Link..... | 57 | +| 8.2.2.1.1.0 | General ..... | 57 | +| 8.2.2.1.1.1 | Per-PDN Connection/NSWO Virtual Point-to-Point Link Model based on distinct VLAN<br>ID..... | 57 | +| 8.2.2.1.1.2 | Per-PDN Connection/NSWO Virtual Point-to-Point Link Model based on distinct layer 2<br>TWAG MAC addresses..... | 58 | +| 8.2.2.1.2 | Initial Attach in WLAN..... | 59 | +| 8.2.2.1.3 | UE Requested PDN or NSWO connectivity ..... | 60 | +| 8.2.2.1.4 | UE Requested PDN or NSWO disconnection..... | 62 | +| 8.2.2.1.5 | HSS/AAA Initiated PDN or NSWO Disconnection procedure in WLAN ..... | 64 | +| 8.2.2.1.6 | HSS/AAA Initiated Detach procedure in WLAN ..... | 64 | + +| | | | +|---------------|-------------------------------------------------------------------------------------------------------------|-----| +| 8.2.2.1.7 | Handover from 3GPP Access to Trusted WLAN Access ..... | 65 | +| 8.2.2.1.8 | Handover from Trusted WLAN Access to 3GPP Access ..... | 66 | +| 8.2.2.2 | Impacts on existing nodes or functionality ..... | 66 | +| 8.2.2.3 | Evaluation ..... | 67 | +| 8.2.3 | Solution 3: Stateful DHCP-based Solution ..... | 68 | +| 8.2.3.1 | Functional Description..... | 68 | +| 8.2.3.1.1 | Functional Overview and Overall System Impacts..... | 68 | +| 8.2.3.1.1.1 | Overview ..... | 68 | +| 8.2.3.1.1.2 | UE Impacts ..... | 68 | +| 8.2.3.1.1.3 | Trusted WLAN Access Gateway Impacts..... | 69 | +| 8.2.3.1.1.4 | Trusted WLAN Access Point Impacts ..... | 69 | +| 8.2.3.1.1.5 | Trusted WLAN Backhaul Impacts ..... | 69 | +| 8.2.3.1.2 | Control Plane Management..... | 69 | +| 8.2.3.1.2.1 | UE-Network Capability Negotiation ..... | 69 | +| 8.2.3.1.2.2 | Connection related control plan interface..... | 69 | +| 8.2.3.1.3 | User plane management ..... | 70 | +| 8.2.3.1.3.1 | Alternative 1: GRE over IP ..... | 70 | +| 8.2.3.1.3.1.2 | GRE over IP tunneling establishment..... | 71 | +| 8.2.3.1.3.2 | Alternative 2: TWAG virtual MAC Address ..... | 72 | +| 8.2.3.1.4 | Protocol stack ..... | 73 | +| 8.2.3.1.5 | IP addressing support for SaMOG phase-2..... | 74 | +| 8.2.3.1.5.1 | IP address assignment for NSWO ..... | 74 | +| 8.2.3.1.5.2 | IP address assignment for GRE over IP tunnel ..... | 74 | +| 8.2.3.1.5.3 | IP address assignment for EPC-routed ..... | 74 | +| 8.2.3.2 | Procedures..... | 75 | +| 8.2.3.2.1 | Initial Attach in WLAN on S2a..... | 75 | +| 8.2.3.2.1.1 | Initial Attach in WLAN on GTP/PMIP S2a..... | 75 | +| 8.2.3.2.2 | UE-initiated Connectivity to Additional PDN ..... | 78 | +| 8.2.3.2.2.1 | UE-initiated Connectivity to Additional PDN on GTP S2a ..... | 78 | +| 8.2.3.2.2.2 | UE-initiated Connectivity to Additional PDN on PMIP S2a ..... | 80 | +| 8.2.3.2.3 | Detach and PDN disconnection in WLAN on S2a ..... | 81 | +| 8.2.3.2.3.1 | Detach and PDN disconnection in WLAN on GTP S2a ..... | 81 | +| 8.2.3.2.3.1.1 | UE/TWAN requested single PDN Disconnection Procedure in WLAN on GTP S2a ..... | 81 | +| 8.2.3.2.3.1.2 | UE/TWAN requested one IPv4 Address or one IPv6 address release for a dual stack PDN in WLAN on GTP S2a..... | 82 | +| 8.2.3.2.3.1.3 | UE/TWAN requested Detach Procedure in WLAN on GTP S2a ..... | 83 | +| 8.2.3.2.3.1.4 | HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a ..... | 84 | +| 8.2.3.2.3.2 | Detach and PDN disconnection in WLAN on PMIP S2a..... | 86 | +| 8.2.3.2.3.2.1 | UE/TWAN requested single PDN Disconnection Procedure in WLAN on PMIP S2a ..... | 86 | +| 8.2.3.2.3.2.2 | UE/TWAN requested multiple PDN Disconnection Procedure in WLAN on PMIP S2a..... | 86 | +| 8.2.3.2.3.2.3 | UE/TWAN requested Detach Procedure in WLAN on PMIP S2a..... | 87 | +| 8.2.3.2.3.2.4 | HSS/AAA Initiated Detach Procedure in WLAN on PMIP S2a ..... | 87 | +| 8.2.3.2.4 | PDN GW initiated Resource Allocation Deactivation in WLAN on S2a..... | 88 | +| 8.2.3.2.4.1 | PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a..... | 88 | +| 8.2.3.2.4.2 | PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a..... | 89 | +| 8.2.3.2.5 | Dedicated bearer activation in WLAN on GTP S2a ..... | 90 | +| 8.2.3.2.6 | Network-initiated bearer modification in WLAN on GTP S2a ..... | 90 | +| 8.2.3.2.7 | Handover from 3GPP Access to Trusted WLAN Access..... | 90 | +| 8.2.3.2.7.1 | Handover from 3GPP Access to Trusted WLAN Access on GTP S2a..... | 90 | +| 8.2.3.2.7.2 | Handover from 3GPP Access to Trusted WLAN Access on PMIP S2a ..... | 93 | +| 8.2.3.3 | Impacts on existing nodes or functionality ..... | 93 | +| 8.2.3.4 | Evaluation ..... | 93 | +| 8.2.4 | Solution 4..... | 95 | +| 8.2.4.1 | Functional Description..... | 95 | +| 8.2.4.1.1 | P2P link ..... | 95 | +| 8.2.5 | Solution 5: Associating APN/PDN with Virtual IP Interface ..... | 95 | +| 8.2.5.1 | Functional Description..... | 95 | +| 8.2.5.1.1 | General ..... | 95 | +| 8.2.5.2 | Procedures..... | 97 | +| 8.2.5.2.2 | Connection Establishment Procedure..... | 97 | +| 8.2.5.2.3 | UE Initiated Disconnection Procedure ..... | 100 | +| 8.2.5.2.4 | HSS/AAA Initiated Disconnection Procedure ..... | 101 | + +| | | | +|--------------|-------------------------------------------------------------------------------------------|-----| +| 8.2.5.2.5 | Handover procedure between 3GPP access and WLAN on GTP S2a..... | 103 | +| 8.2.5.3 | Impacts on existing nodes or functionality ..... | 104 | +| 8.2.5.4 | Evaluation ..... | 104 | +| 8.2.6 | Solution 6: X..... | 104 | +| 8.2.7 | Solution 7: PPP over Ethernet (PPPoE) ..... | 104 | +| 8.2.7.1 | Functional Description..... | 104 | +| 8.2.7.1.1 | Overview ..... | 105 | +| 8.2.7.2 | Procedures..... | 107 | +| 8.2.7.2.1 | PDN Connectivity Parameter Negotiation ..... | 107 | +| 8.2.7.2.1.1 | Option 1: PDN connectivity parameters negotiated during PPP session establishment ..... | 107 | +| 8.2.7.2.1.2 | Option 2: PDN connectivity parameters negotiated during PPPoE session establishment..... | 107 | +| 8.2.7.2.2 | Initial Attach and UE-initiated Connectivity to PDN ..... | 108 | +| 8.2.7.2.3 | PDN Connection Release ..... | 110 | +| 8.2.7.2.4 | Handover from 3GPP access to WLAN..... | 111 | +| 8.2.7.3 | Impacts on existing nodes or functionality ..... | 111 | +| 8.2.7.4 | Evaluation ..... | 111 | +| 8.2.8 | Solution 8: Solution using new 3GPP specific LLC/SNAP header settings ..... | 112 | +| 8.2.8.1 | Functional Description..... | 113 | +| 8.2.8.1.1 | General ..... | 113 | +| 8.2.8.1.2 | Protocol stack ..... | 113 | +| 8.2.8.1.3 | Protocol header..... | 114 | +| 8.2.8.2 | Procedures..... | 115 | +| 8.2.8.3 | Impacts on existing nodes or functionality ..... | 118 | +| 8.2.8.4 | Evaluation ..... | 118 | +| 8.2.9 | Solution 9: EAP based signaling solution ..... | 119 | +| 8.2.9.1 | Functional Description..... | 119 | +| 8.2.9.1.1 | General ..... | 119 | +| 8.2.9.1.2 | Protocol stack ..... | 120 | +| 8.2.9.1.3 | Signaling information from UE to the network ..... | 120 | +| 8.2.9.1.4 | Signaling information from the network to the UE..... | 121 | +| 8.2.9.2 | Procedures..... | 122 | +| 8.2.9.2.1 | Initial Attach in WLAN on S2a..... | 122 | +| 8.2.9.2.2 | UE-Initiated Connectivity to Additional PDN in WLAN on S2a ..... | 123 | +| 8.2.9.2.2.1 | UE-Initiated Connectivity to Additional PDN in WLAN on GTP S2a..... | 123 | +| 8.2.9.2.2.2 | UE-Initiated Connectivity to Additional PDN in WLAN on PMIP S2a..... | 124 | +| 8.2.9.2.3 | Handover procedure between 3GPP access and WLAN on S2a ..... | 124 | +| 8.2.9.2.3.1 | Handover from 3GPP access to WLAN on GTP S2a ..... | 124 | +| 8.2.9.2.3.2 | Handover from 3GPP access to WLAN on PMIP S2a..... | 124 | +| 8.2.9.2.3.3 | Handover from TWAN to 3GPP access ..... | 125 | +| 8.2.9.2.4 | PDN GW initiated Resource Allocation Deactivation..... | 125 | +| 8.2.9.2.4.1 | PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a ..... | 125 | +| 8.2.9.2.4.2 | PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a..... | 125 | +| 8.2.9.2.5 | TWAN requested PDN Disconnection Procedures..... | 125 | +| 8.2.9.2.5.1 | TWAN requested PDN Disconnection Procedure in WLAN on GTP S2a..... | 125 | +| 8.2.9.2.5.2 | TWAN Initiated Detach and requested PDN Disconnection Procedure in WLAN on PMIP S2a ..... | 126 | +| 8.2.9.2.6 | UE requested PDN Disconnection Procedures ..... | 126 | +| 8.2.9.2.6.1 | UE requested PDN Disconnection Procedure in WLAN on GTP S2a..... | 126 | +| 8.2.9.2.6.2 | UE requested PDN Disconnection Procedure in WLAN on GTP S2a on PMIP S2a ..... | 127 | +| 8.2.9.2.7 | Detach Procedures..... | 127 | +| 8.2.9.3 | Impacts on existing nodes or functionality ..... | 127 | +| 8.2.9.4 | Evaluation ..... | 128 | +| 8.2.10 | Solution 10 : WCS Solution ..... | 128 | +| 8.2.10.1 | Functional Description..... | 128 | +| 8.2.10.1.1 | Overview ..... | 128 | +| 8.2.10.1.2 | User plane..... | 128 | +| 8.2.10.1.3 | Control plane ..... | 128 | +| 8.2.10.1.3.1 | Alternative 1: Virtual MAC-based control protocol transport ..... | 129 | +| 8.2.10.1.3.2 | Alternative 2: VLAN-based control protocol transport..... | 129 | +| 8.2.10.1.3.3 | Alternative 3: L3-based control protocol transport ..... | 129 | +| 8.2.10.1.3.4 | p2p link ID negotiation in EAP-AKA' procedure..... | 129 | +| 8.2.10.1.4 | Protocol Stacks ..... | 131 | + +| | | | +|------------------------------------------------------------|---------------------------------------------------------------------------------------|------------| +| 8.2.10.2 | Procedures..... | 131 | +| 8.2.10.2.1 | Initial Attach procedure..... | 131 | +| 8.2.10.2.1.1 | Initial Attach in WLAN on S2a – network capability negotiation..... | 131 | +| 8.2.10.2.1.2 | Initial Attach continuation for GTP based S2a ..... | 132 | +| 8.2.10.2.1.2 | Initial Attach in WLAN on PMIP S2a ..... | 133 | +| 8.2.10.2.2 | UE-initiated Connectivity to Additional PDN ..... | 133 | +| 8.2.10.2.2.1 | UE-Initiated Connectivity to PDN in WLAN on GTP S2a..... | 133 | +| 8.2.10.2.2.2 | UE-Initiated Connectivity to PDN in WLAN on PMIP S2a..... | 134 | +| 8.2.10.2.3 | Handover procedure in multi-connection scenario from 3GPP access to WLAN on S2a ..... | 134 | +| 8.2.10.2.5 | Handover procedure from WLAN on S2a to 3GPP access..... | 136 | +| 8.2.10.2.6 | UE/TWAN RequestedPDN disconnection in WLAN on S2a ..... | 137 | +| 8.2.10.2.6.1 | UE/TWAN requested PDN disconnection in WLAN on GTP S2a ..... | 137 | +| 8.2.10.2.6.2 | UE TWAN request ed PDN disconnection in WLAN on PMIP S2a..... | 138 | +| 8.2.10.2.7 | UE initiated Detach in WLAN on S2a..... | 138 | +| 8.2.10.2.7.1 | UE initiated Detach in WLAN on GTP S2a..... | 138 | +| 8.2.10.2.7.2 | UE initiated Detach in WLAN on PMIP S2a..... | 139 | +| 8.2.10.2.8 | HSS/AAA Initiated Detach Procedure in WLAN ..... | 139 | +| 8.2.10.2.8.1 | HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a..... | 139 | +| 8.2.10.2.8.2 | HSS/AAA Initiated Detach Procedure in WLAN on on PMIP S2a..... | 140 | +| 8.2.10.2.9 | PDN GW initiated Resource Allocation Deactivation..... | 140 | +| 8.2.10.2.9.1 | PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a ..... | 140 | +| 8.2.10.2.9.2 | PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a..... | 140 | +| 8.2.10.3 | Impacts on existing nodes or functionality ..... | 140 | +| 8.2.10.4 | Evaluation ..... | 140 | +| 8.3 | Evaluation..... | 141 | +| 8.2.x | Solution x..... | 141 | +| 8.2.x.1 | Functional Description..... | 141 | +| 8.2.x.2 | Procedures..... | 142 | +| 8.2.x.3 | Impacts on existing nodes or functionality ..... | 142 | +| 8.2.x.4 | Evaluation ..... | 142 | +| 8.3 | Evaluation..... | 142 | +| 9 | Conclusion ..... | 142 | +| 9.1 | Conclusion on SaMOG Phase 1 ..... | 142 | +| 9.1.1 | Conclusion on attach trigger solution..... | 143 | +| 9.2 | Conclusion on SaMOG Phase 2 ..... | 143 | +| <b>Annex A: Example of WLAN integrated with Femto.....</b> | | <b>144</b> | +| Annex B: Change History ..... | | 145 | + +--- + +## Foreword + +This Technical Report has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +This Study item is to study: + +1. The addition of a S2a based on GTP option. In particular this SID will develop the necessary stage 2 message flows to support S2a based on GTP and mobility between GTP-S5/S8 and GTP-S2a. +2. Supporting WLAN access to EPC through S2a via mechanisms: + - 2.1 with no impact to the UE; + - 2.2 with impact to the UE. + +Solutions requiring modifications to non 3GPP link-layers will not be considered. It is expected that the result of this Study Item may be used by 3GPP-BBF interworking activities (BBAI). + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 41.001: "GSM Release specifications". +- [3] 3GPP TS 23.402: "Architecture enhancements for Non-3GPP Accesses". +- [4] 3GPP TS 23.203: "Policy and charging control architecture". +- [5] IEEE Std 802.11-2007: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications". +- [6] 3GPP TS 23.401: "GPRS Enhancements for E-UTRAN Access". +- [7] 3GPP TS 29.273: "3GPP EPS AAA interfaces". +- [8] IETF RFC 791: "Internet Protocol". +- [9] IETF RFC 2131: "Dynamic Host Configuration Protocol". +- [10] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification". +- [11] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)". +- [12] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration". +- [13] IETF RFC 4436: "Detecting Network Attachment in IPv4 (DNAv4)". +- [14] IETF RFC 6059: "Simple Procedures for Detecting Network Attachment in IPv6". +- [15] IEEE Std 802.11n-2009: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. Enhancements for Higher Throughput (Amendment 5)". + +- [16] IETF RFC 6085: " Address Mapping of IPv6 Multicast Packets on Ethernet". +- [17] IETF RFC 5213: "Proxy Mobile IPv6". +- [18] IETF RFC 5844: "IPv4 Support for Proxy Mobile IPv6". +- [19] IETF RFC 3736: "Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6". +- [20] IEEE Std 802.1Q-2011: "IEEE Standard for Local and metropolitan area networks--Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks". +- [21] IEEE Std 802.11u-2011: " IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Amendment 9: Interworking with External Networks". +- [22] IETF RFC 4187: "Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)". +- [23] IETF RFC 3315: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". +- [24] IETF RFC 3203: "DHCP reconfigure extension". +- [25] IETF RFC 6085: “Address Mapping of IPv6 Multicast Packets on Ethernet”. +- [26] IEEE Std 802-2001: “IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture”. +- [27] IETF RFC 5448: "Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)". +- [28] 3GPP TS 33 402: "Security aspects of non-3GPP accesses" +- [29] IETF RFC 6704: "Forcerenew Nonce 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]. + +<Definition: Explanation.> + +### 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [x] 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]. + +<ACRONYM> <Explanation> + +--- + +## 4 Scenarios + +The decision on whether a non 3GPP access is considered trusted or un trusted is made by the HPLMN operator and is not a characteristic of the non 3GPP access network. More details on it are provided in clause 4.3.1.2 of TS 23.402 [3]. The HPMN operator however while making a decision on trust worthiness of a non 3GPP access can also take into consideration security aspects of the access network. + +WLAN security was considered poor in both strength and ease of use, compared with that taken for granted in 3G networks and devices (UICC plus HSS, and GPRS encryption of data). Hence it made sense for the mobile network operators (MNOs) to use their core network to add overlay security layers, i.e. the IKEv2 for Authentication and Authorization of the UE, and the IPSec between the UE and ePDG for the security of the user data. + +Now, with the deployment of 802.1x, 802.11u, 802.11i and Hotspot 2.0, it may be considered by some operators that the security strength and ease of use (discovery and set up) is as acceptable as 3G/LTE security. For example, for the radio air link, the operator controlled hotspot with 802.11i could be treated as a secure Non-3GPP Access. As 802.11i (or WPA2 called by WFA) has been released for several years, many AP-s support it as a basic feature and lots of smart phones also have supported it. + +WLAN can also be deployed integrated in a residential/enterprise device (e.g. femto). In such a scenario, protection mechanism for the traffic on the backhaul link between the residential/enterprise device and the EPC may be used. This protection of the backhaul may be leveraged to consider the WLAN security in terms of connectivity to the EPC. + +The impact on the support of the following scenarios shall be used to evaluate the solutions that will be proposed in the study: + +- Access to EPC resources/services with access control by the operator; +- Seamless mobility between 3GPP and WLAN for EPS services with IP address preservation; +- Non-seamless mobility services between 3GPP and WLAN for EPS services: no IP address preservation; +- Support of UEs with single PDN connection; support of UEs with multiple PDN connections; +- Access to EPC via WLAN simultaneously with non-seamless WLAN offload. + +--- + +## 5 Architectural assumptions + +**Editor's note: This clause will identify the architectural assumptions.** + +### 5.1 Architectural assumptions for GTP based S2a + +From a UE perspective, using S2a-GTP or S2a-PMIP shall be transparent. + +The impacts to the existing functionalities and to the EPC shall be minimized. The protocol design on S2a should aim at keeping S2a GTP operations similar to those supported on GTP-based S5/S8 and GTP-based S2b as much as possible. + +All functions of the existing PMIP-S2a option should also be supported by GTP-S2a, except for optimized handover. + +### 5.2 Architectural assumptions for WLAN access to EPC through S2a + +In order to support the scenarios described in section 4, the following assumptions for WLAN access to EPC through S2a are taken and need to be investigated as part of the study: + +- The UE and the EPC are assumed to mutually authenticate through the WLAN Access as defined in TS 23.402 [3], clause 4.9.1. +- It is assumed that UE traffic over the WLAN air link may be confidentiality and integrity protected as defined by IEEE 802.11 [5]. +- It is assumed that there is a point-to-point link between UE and non-3GPP access GTP peer for the solutions with no impact to UE. + +The backhaul, through which WLAN accesses to EPC, may be secured, e.g. through IPSec, to build a secure access to the EPC. + +#### 5.2.1 Assumptions for solutions with no Impact to the UE + +The solutions that enable trusted WLAN access to EPC over S2a without any UE impact shall comply with the following architectural assumptions: + +- There shall be no functionality added to a R11 UE with respect to a R10 or pre-R10 UE specifically for the support of trusted WLAN access to EPC over S2a. +- No additional 3GPP mechanisms (other than those already specified), layer 2 protocol modifications or layer 3 protocol modifications shall be required on the UE to allow a UE capable of WLAN connectivity to a trusted WLAN network to gain WLAN access to EPC through S2a. +- There shall be no impact to the UE for the indication of the APN of the PDN to be established upon attach or upon handover of a PDN connection from a 3GPP access to trusted WLAN through S2a. The network shall be capable of selecting the APN to be used for the PDN establishment upon attach, independently of whether one or more PDN connections with such APNs are active over a 3GPP access. +- There shall be no impact to the UE for the support of IP address preservation in case of mobility between a 3GPP access and WLAN. +- There shall be no impact to the UE for the establishment of more than one PDN connections over WLAN when attaching to WLAN access or when handing over PDN connections from a 3GPP access. +- There shall be no impact to the UE for the simultaneous support of IP connectivity to the EPC over WLAN and with non-seamless WLAN offload. +- SaMOG solution should co-exist with Release 11 and earlier UEs which may implement WLAN interworking related features including ANDSF and its extensions, SWu, S2c. +- Since an unmodified UE may support the Detecting Network Attachment (DNA) functions, solutions claiming no impacts to the UE shall work in presence of the following protocols: + - For IPv4: IETF RFC 4436 [13] + - For IPv6: IETF RFC 6059 [14] + +The above list is non-exhaustive. + +Only the following functions can be considered supported by an unmodified UE, i.e. solutions with no impacts to UE shall only expect the following functions in the UE: + +- WLAN spec only restricted to PHY/MAC aspects in IEEE 802.11 [5] and IEEE 802.11n [15] +- 3GPP-based authentication as defined in TS 23.402 [3] over WLAN (i.e. access authentication towards EPC) +- IPv4 and/or IPv6 support: + - For IPv4: IETF RFC791 [8], IETF RFC 2131 [9] + - For IPv6: IETF RFC 2460 [10], IETF RFC 4861 [11], and IETF RFC 4862 [12] + +--- + +## 6 Solutions for GTP based S2a + +**Editor's note:** This clause will describe the solution(s) for the "access agnostic" GTP-S2a, which is basically similar to PMIPv6-S2a in TS 23.402 [3]. For WLAN Access, the additional considerations including the potential UE impacts are studied in clause 7. + +### 6.1 Solution 1 + +#### 6.1.1 Architecture + +The same architecture reference models as those defined in TS 23.402 [3] can be applied to GTP based S2a, with the following differences: + +- BBERF is not required with GTP based S2a; +- Gxa interface is not required between the PCRF (or vPCRF) and the Trusted Non-3GPP Access; +- vPCRF (and S9 interface) is not required for roaming with Home Routed traffic (i.e. non-LBO traffic). + +NOTE 1: The Chained case is not proposed to be supported in this release. Figures 6.1.1-1 to 6.1.1-3 show the baseline architecture reference model for GTP based S2a in the non roaming and roaming cases. + +![Figure 6.1.1-1: Non-Roaming Architecture within EPS using GTP based S5, S2a. This diagram shows the network architecture for a non-roaming scenario. It includes an HSS connected to a Serving Gateway (via S6a) and a PDN Gateway (via S5). The PDN Gateway is connected to a PCRF (via Gx) and Operator's IP Services (via SGi). The PCRF is also connected to the Operator's IP Services (via Rx). The PDN Gateway is connected to a Trusted Non-3GPP IP Access (via S2a). The Trusted Non-3GPP IP Access is connected to a 3GPP AAA Server (via STa). The 3GPP AAA Server is connected to the HSS (via SWx). The architecture is divided into HPLMN and Non-3GPP Networks by a dashed red line.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +Figure 6.1.1-1: Non-Roaming Architecture within EPS using GTP based S5, S2a. This diagram shows the network architecture for a non-roaming scenario. It includes an HSS connected to a Serving Gateway (via S6a) and a PDN Gateway (via S5). The PDN Gateway is connected to a PCRF (via Gx) and Operator's IP Services (via SGi). The PCRF is also connected to the Operator's IP Services (via Rx). The PDN Gateway is connected to a Trusted Non-3GPP IP Access (via S2a). The Trusted Non-3GPP IP Access is connected to a 3GPP AAA Server (via STa). The 3GPP AAA Server is connected to the HSS (via SWx). The architecture is divided into HPLMN and Non-3GPP Networks by a dashed red line. + +Figure 6.1.1-1: Non-Roaming Architecture within EPS using GTP based S5, S2a + +![Figure 6.1.1-2: Roaming Architecture for EPS using GTP based S8, S2a - Home Routed. This diagram shows the network architecture for a roaming scenario. It includes an HSS connected to a PDN Gateway (via S6a) and a 3GPP AAA Server (via SWx). The PDN Gateway is connected to an hPCRF (via Gx) and Operator's IP Services (via SGi). The hPCRF is also connected to the Operator's IP Services (via Rx). The PDN Gateway is connected to a Serving Gateway (via S8). The Serving Gateway is connected to a 3GPP Access (via S2a). The 3GPP Access is connected to a 3GPP AAA Proxy (via SWd). The 3GPP AAA Proxy is connected to the 3GPP AAA Server (via STa). The 3GPP AAA Server is connected to the HSS (via SWx). The architecture is divided into HPLMN, VPLMN, and Non-3GPP Networks by dashed red lines.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +Figure 6.1.1-2: Roaming Architecture for EPS using GTP based S8, S2a - Home Routed. This diagram shows the network architecture for a roaming scenario. It includes an HSS connected to a PDN Gateway (via S6a) and a 3GPP AAA Server (via SWx). The PDN Gateway is connected to an hPCRF (via Gx) and Operator's IP Services (via SGi). The hPCRF is also connected to the Operator's IP Services (via Rx). The PDN Gateway is connected to a Serving Gateway (via S8). The Serving Gateway is connected to a 3GPP Access (via S2a). The 3GPP Access is connected to a 3GPP AAA Proxy (via SWd). The 3GPP AAA Proxy is connected to the 3GPP AAA Server (via STa). The 3GPP AAA Server is connected to the HSS (via SWx). The architecture is divided into HPLMN, VPLMN, and Non-3GPP Networks by dashed red lines. + +Figure 6.1.1-2: Roaming Architecture for EPS using GTP based S8, S2a - Home Routed + +![Figure 6.1.1-3: Roaming Architecture for EPS using GTP based S5, S2a – Local Breakout. The diagram shows a roaming architecture across three network domains: HPLMN (Home PLMN), VPLMN (Visited PLMN), and Non-3GPP Networks. In the HPLMN, the HSS is connected to the hPCRF via the S6a interface. The hPCRF is connected to the Operator's IP Services (e.g., IMS, PSS etc.) via the Rx interface and to the vPCRF via the S9 interface. The vPCRF is connected to the Visited network IP services or proxies to home network services or PDN via the Rx interface and to the PDN Gateway via the Gx interface. The PDN Gateway is connected to the Serving Gateway via the S5 interface and to the 3GPP AAA Proxy via the S6b interface. The Serving Gateway is connected to the 3GPP Access via the S1 interface. The 3GPP AAA Proxy is connected to the 3GPP AAA Server via the SWd interface and to the Trusted Non-3GPP IP Access via the STa interface. The 3GPP AAA Server is connected to the hPCRF via the SWx interface. The PDN Gateway is also connected to the Trusted Non-3GPP IP Access via the S2a interface. The S2a interface is highlighted in red in the original document.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Figure 6.1.1-3: Roaming Architecture for EPS using GTP based S5, S2a – Local Breakout. The diagram shows a roaming architecture across three network domains: HPLMN (Home PLMN), VPLMN (Visited PLMN), and Non-3GPP Networks. In the HPLMN, the HSS is connected to the hPCRF via the S6a interface. The hPCRF is connected to the Operator's IP Services (e.g., IMS, PSS etc.) via the Rx interface and to the vPCRF via the S9 interface. The vPCRF is connected to the Visited network IP services or proxies to home network services or PDN via the Rx interface and to the PDN Gateway via the Gx interface. The PDN Gateway is connected to the Serving Gateway via the S5 interface and to the 3GPP AAA Proxy via the S6b interface. The Serving Gateway is connected to the 3GPP Access via the S1 interface. The 3GPP AAA Proxy is connected to the 3GPP AAA Server via the SWd interface and to the Trusted Non-3GPP IP Access via the STa interface. The 3GPP AAA Server is connected to the hPCRF via the SWx interface. The PDN Gateway is also connected to the Trusted Non-3GPP IP Access via the S2a interface. The S2a interface is highlighted in red in the original document. + +**Figure 6.1.1-3: Roaming Architecture for EPS using GTP based S5, S2a – Local Breakout** + +NOTE 2: A GTP peer is assumed in the Trusted Non-3GPP IP Access for this GTP based S2a. Moreover it is assumed that the GTP peer acts as first hop router in a similar way as the MAG when PMIP is used over S2a. When deferred IPv4 address allocation is supported, it is assumed that the GTP peer supports DHCPv4 relay functionality. + +## 6.1.2 Functional description + +*Editor's note: This clause will contain the functional description for S2a mobility based on GTP.* + +### 6.1.2.1 Bearer model for a PDN connection + +![Figure 6.1.2.1-1: Bearer model on GTP based S2a. The diagram shows a UE connected to a Trusted Non-3GPP IP Access via a Non-3GPP connectivity link. The Trusted Non-3GPP IP Access contains a UL TFT (Upstream Traffic Flow Template) that maps the Non-3GPP connectivity to multiple GTP tunnels over the S2a interface. The GTP tunnels are then mapped to a PGW via a DL TFT (Downstream Traffic Flow Template). A callout box indicates that the mapping between Non-3GPP connectivity and multiple GTP bearers (Default and dedicated bearers) is out of 3GPP scope.](c036e2540a94b31357ceb0002f0cacab_img.jpg) + +Figure 6.1.2.1-1: Bearer model on GTP based S2a. The diagram shows a UE connected to a Trusted Non-3GPP IP Access via a Non-3GPP connectivity link. The Trusted Non-3GPP IP Access contains a UL TFT (Upstream Traffic Flow Template) that maps the Non-3GPP connectivity to multiple GTP tunnels over the S2a interface. The GTP tunnels are then mapped to a PGW via a DL TFT (Downstream Traffic Flow Template). A callout box indicates that the mapping between Non-3GPP connectivity and multiple GTP bearers (Default and dedicated bearers) is out of 3GPP scope. + +**Figure 6.1.2.1-1: Bearer model on GTP based S2a** + +NOTE: The mapping between Non-3GPP connectivity and multiple GTP bearers in the Trusted Non-3GPP IP Access is out of 3GPP scope. + +For Trusted non-3GPP access to the EPC, the PDN connectivity is made up of the concatenation of Non-3GPP connectivity (between the UE and the Trusted Non-3GPP access) and of GTP bearer(s) over S2a. + +The GTP based S2a interface is similar to GTP-S5/S8 and GTP-S2b. The Trusted Non 3GPP access handles the UL TFT received from the PGW over GTP with the same way as an ePDG terminating GTP based S2b handles the UL TFT received from the PGW. + +Whether GTP or PMIP is used in the network for S2a is transparent to the UE. + +### 6.1.3 Information flows + +#### 6.1.3.1 Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW + +NOTE 1: The exact list of parameters signalled in GTP S2a information flows will be defined during normative work. + +![Sequence diagram of the Initial Attach Procedure with GTP on S2a. Lifelines: UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps 1 through 11, with a shaded 'Roaming Scenarios' area for steps 2, 6, and 7. Step 9 is highlighted as a green bar labeled 'GTP Tunnel'.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TrustedNon3GPP as Trusted Non-3GPP IP Access + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note left of UE: 1. Non-3GPP Specific Procedures + UE->>TrustedNon3GPP: 2. EAP Authentication + TrustedNon3GPP->>HSS_AAA: 2. Authentication & Authorization + Note left of UE: 3. L3 Attach Trigger + TrustedNon3GPP->>PDN_GW: 5. Create Session Request + Note right of PDN_GW: 6. IP-CAN Session Establishment Procedure + PDN_GW->>HSS_AAA: 7. Update PDN GW Address + PDN_GW->>TrustedNon3GPP: 8. Create Session Response + Note right of PDN_GW: 9. GTP Tunnel + Note left of UE: 11. L3 Attach Completion + +``` + +Sequence diagram of the Initial Attach Procedure with GTP on S2a. Lifelines: UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps 1 through 11, with a shaded 'Roaming Scenarios' area for steps 2, 6, and 7. Step 9 is highlighted as a green bar labeled 'GTP Tunnel'. + +**Figure 6.1.3.1-1: Initial attachment with Network-based MM mechanism over S2a for roaming, LBO and non-roaming scenarios** + +Principles are similar to those specified for the PMIPv6 S2a call flow in clause 6.2.1 of TS 23.402 [3], but with GTP signalling and following differences: + +The home routed roaming, LBO and non-roaming scenarios are depicted in the figure 6.1.3.1-1. + +- In the LBO case, the 3GPP AAA Proxy acts as an intermediary, forwarding messages from the 3GPP AAA Server in the HPLMN to the PDN GW in the VPLMN and vice versa. Messages between the PDN GW in the VPLMN and the hPCRF in the HPLMN are forwarded by the vPCRF in the VPLMN. +- In the home routed roaming and non-roaming cases, the vPCRF and the 3GPP AAA Proxy are not involved, except for the authentication and authorization in step 2. + +- 1) as for step 1 of clause 6.2.1 of TS 23.402 [3]. +- 2) as for step 2 of clause 6.2.1 of TS 23.402 [3], with the following additions: + +- Upon successful authorization, the 3GPP AAA server downloads authorization (subscription) data to the Trusted non-3GPP Access. This information is used at step 5. +- The Trusted non 3GPP IP Access selects the S2a protocol variant (GTP vs PMIP). The Trusted non 3GPP IP Access may be configured with the S2a protocol variant(s) on a per HPLMN granularity, or may retrieve information regarding the S2a protocol variants supported by the PDN GW (PMIP or/and GTP) from the Domain Name Service function. +- The Trusted non-3GPP IP Access selects the PGW as per the existing PGW selection procedure; if the Trusted non-3GPP IP Access receives a PGW Identity under the form of a FQDN, it shall derive it to an IP address according to the selected mobility management protocol (here GTP). + +NOTE 2: As per existing principles, to support separate PDN GW addresses at a PDN GW for different mobility protocols (e.g. PMIP, MIPv4 or GTPv2), the PDN GW Selection function takes mobility protocol type into account when deriving PDN GW address by using the Domain Name Service function. + +3) as for step 3 of clause 6.2.1 of TS 23.402 [3]. + +NOTE 3: Only when IPv4, the L3 trigger may be relayed to the PDN GW after the GTP tunnel has been setup in step 9 using deferred IPv4 address mechanism. + +4) step 4 of clause 6.2.1 of TS 23.402 [3] is skipped. + +5) The Trusted non-3GPP IP Access sends a Create Session Request (IMSI, APN, RAT type, Trusted non-3GPP IP Access TEID of the control plane, PDN Type, PDN Address, EPS Bearer Identity, Default EPS Bearer QoS, Trusted non-3GPP IP Access Address for the user plane, Trusted non-3GPP IP Access TEID of the user plane, APN-AMBR, Selection Mode, Dual Address Bearer Flag, Trace Information, Charging Characteristics, Protocol Configuration Options) message to the PGW. The RAT type indicates the non-3GPP IP access technology type. The PDN Type shall be set based on the requested IP address types and subscription profile in the same way as the PDN type is selected during the E-UTRAN Initial Attach in TS 23.401 [6]. The Trusted non-3GPP IP Access Network shall set the Dual Address Bearer Flag when the PDN type is set to IPv4v6 and all SGSNs which the UE may be handed over to are Release 8 or above supporting dual addressing, which is determined based on node pre-configuration by the operator. The Trusted non-3GPP IP Access Network shall include Trace Information if PDN GW trace is activated. + +The PGW creates a new entry in its bearer context table and generates a Charging Id. The new entry allows the PGW to route user plane PDUs between the Trusted non-3GPP IP Access Network and the packet data network and to start charging. + +NOTE 4: The EPS Bearer Identity and Default EPS Bearer QoS parameters convey the S2a bearer identity and the default S2a bearer QoS. + +NOTE 5: As part of the access specific study it will be clarified whether step 5 (Create Session Request) is triggered by the completion of the authentication procedure (step 2) either/or by the reception of the L3 Attach trigger (step 3). + +6) as for step 6 of clause 6.2.1 of TS 23.402 [3] except that there is no associated Gateway Control Sessions. + +7) as for step 7 of clause 6.2.1 of TS 23.402 [3], with the following addition: + +- when informing the 3GPP AAA Server of the PDN GW identity, the selected PDN GW also indicates the selected S2a protocol variant (here GTP); this allows the option for the 3GPP AAA Server or 3GPP AAA Proxy not to return to the PDN GW PMIP specific parameters (e.g. static QoS Profile, Trace Information, APN-AMBR) if GTP is used over S2a; the PDN GW shall ignore those parameters if received from the 3GPP AAA Server or 3GPP AAA Proxy. + +8) The PDN GW returns a Create Session Response (PDN GW Address for the user plane, PDN GW TEID of the user plane, PDN GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, Protocol Configuration Options, Cause) message to the Trusted non-3GPP IP Access, including the IP address(es) allocated for the UE. + +NOTE 6: If the L3 attach trigger is relayed to the PDN GW, the IP address will not be returned in the Create Session Response. + +The PGW may initiate the creation of dedicated bearers on GTP based S2a (like it may do it on GTP based S5/S8 for an Attach on 3GPP access). + +9) The GTP tunnel is set up between the Trusted Non-3GPP IP Access and the PDN GW. + +NOTE 7: If the L3 Attach trigger is relayed to the PDN GW, the DHCP request is sent to the PDN GW in the established GTP tunnel. + +10) step 10 of clause 6.2.1 of TS 23.402 [3] is skipped. + +11) as for step 11 of clause 6.2.1 of TS 23.402 [3]. + +### 6.1.3.2 Detach and PDN Disconnection with GTP on S2a + +#### 6.1.3.2.1 UE/Trusted Non-3GPP IP Access Network Initiated Detach and UE/Trusted Non-3GPP IP Access requested PDN Disconnection Procedure with GTP on S2a + +![Sequence diagram for UE/Trusted Non-3GPP IP Access Network initiated detach procedure or PDN-disconnection with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, AAA Proxv, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box covers the AAA Proxv, hPCRF, and HSS/AAA components. The sequence starts with a '1. Access technology specific detach trigger' from UE to Trusted Non-3GPP IP Access. Then, '3. Delete Session Request' is sent from Trusted Non-3GPP IP Access to PDN GW. PDN GW sends '4. Update PDN GW Address' to AAA Proxv, which then forwards it to HSS/AAA. A '5. PCEF-Initiated IP-CAN Session Termination Procedure' is shown as a dashed box between AAA Proxv and hPCRF. PDN GW sends '6. Delete Session Response' back to Trusted Non-3GPP IP Access. Finally, '7. Non-3GPP specific resource release procedure' is shown as a dashed box between UE and Trusted Non-3GPP IP Access.](90ee16ccc0ad16aeca48087797d7b07f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TrustedNon3GPP as Trusted Non-3GPP IP Access + participant PDN_GW as PDN GW + participant AAA_Proxv as AAA Proxv + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note left of UE: 1. Access technology specific detach trigger + TrustedNon3GPP->>PDN_GW: 3. Delete Session Request + PDN_GW->>AAA_Proxv: 4. Update PDN GW Address + AAA_Proxv->>HSS_AAA: + Note right of AAA_Proxv: 5. PCEF-Initiated IP-CAN Session Termination Procedure + PDN_GW->>TrustedNon3GPP: 6. Delete Session Response + Note left of UE: 7. Non-3GPP specific resource release procedure + +``` + +Sequence diagram for UE/Trusted Non-3GPP IP Access Network initiated detach procedure or PDN-disconnection with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, AAA Proxv, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box covers the AAA Proxv, hPCRF, and HSS/AAA components. The sequence starts with a '1. Access technology specific detach trigger' from UE to Trusted Non-3GPP IP Access. Then, '3. Delete Session Request' is sent from Trusted Non-3GPP IP Access to PDN GW. PDN GW sends '4. Update PDN GW Address' to AAA Proxv, which then forwards it to HSS/AAA. A '5. PCEF-Initiated IP-CAN Session Termination Procedure' is shown as a dashed box between AAA Proxv and hPCRF. PDN GW sends '6. Delete Session Response' back to Trusted Non-3GPP IP Access. Finally, '7. Non-3GPP specific resource release procedure' is shown as a dashed box between UE and Trusted Non-3GPP IP Access. + +**Figure 6.1.3.2.1-1: UE/Trusted Non-3GPP Access Network initiated detach procedure or PDN-disconnection with GTP on S2a** + +Principles are similar to those specified for the PMIP S2a call flow in clause 6.4.1.1 of TS 23.402 [3], but with GTP signalling: + +1) as for step 1 of clause 6.4.1.1 of TS 23.402 [3]. + +2) step 2 of clause 6.4.1.1 of TS 23.402 [3] is skipped. + +3) The active Bearer(s) Trusted non-3GPP IP Access regarding this particular UE and PDN connection are deactivated by the Trusted non-3GPP IP Access sending a Delete Session Request (Linked EPS Bearer ID) to the PGW for the related PDN connection. + +4 to 5) as for steps 4 to 5 of clause 6.4.1.1 of TS 23.402 [3]. + +6) The PDN GW acknowledges with Delete Session Response (Cause). + +7) as for step 7 of clause 6.4.1.1 of TS 23.402 [3]. + +#### 6.1.3.2.2 HSS/AAA Initiated Detach Procedure with GTP on S2a + +![Sequence diagram for HSS/AAA-initiated detach procedure with GTP on S2a. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access, PDN GW, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' covers the PDN GW, AAA Proxy, and hPCRF. Step 1: UE De-registration Request is sent from HSS/AAA to Trusted Non-3GPP IP Access. Step 2: A block labeled 'The procedures as figure 6.1.3.2.1-1, after Step 1' is shown. Step 3: UE De-Registration Ack is sent from AAA Proxy to HSS/AAA.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TNA as Trusted Non-3GPP IP Access + participant PDN_GW as PDN GW + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + rect rgb(240, 240, 240) + Note over PDN_GW, hPCRF: Roaming Scenarios + end + + HSS_AAA->>TNA: 1. UE De-registration Request + Note over UE, HSS_AAA: 2. The procedures as figure 6.1.3.2.1-1, after Step 1 + AAA_Proxy->>HSS_AAA: 3. UE De-Registration Ack + +``` + +Sequence diagram for HSS/AAA-initiated detach procedure with GTP on S2a. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access, PDN GW, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' covers the PDN GW, AAA Proxy, and hPCRF. Step 1: UE De-registration Request is sent from HSS/AAA to Trusted Non-3GPP IP Access. Step 2: A block labeled 'The procedures as figure 6.1.3.2.1-1, after Step 1' is shown. Step 3: UE De-Registration Ack is sent from AAA Proxy to HSS/AAA. + +**Figure 6.1.3.2.2-1: HSS/AAA-initiated detach procedure with GTP on S2a** + +Principles are similar to those specified for the PMIP S2a call flow in clause 6.4.2.1 of TS 23.402 [3], but with GTP signalling: + +- 1) as for step 1 of clause 6.4.2.1 of TS 23.402 [3]. +- 2) This includes the procedures after step 1 as for Figure 6.1.3.2.1-1. + +For multiple PDN connectivity, this step shall be repeated for each PDN connected. + +- 3) as for step 3 of clause 6.4.2.1 of TS 23.402 [3]. + +**NOTE:** The HSS/AAA may also send a detach indication message to the PDN GW. The PDN GW does not remove the GTP tunnels on S2a, since the Trusted non-3GPP IP Access is responsible for removing those tunnels on S2a. The PDN GW acknowledges the receipt of the detach indication message to the HSS/AAA. + +#### 6.1.3.3 UE-initiated Connectivity to Additional PDN with GTP on S2a + +Establishment of connectivity to an additional PDN over Trusted Non-3GPP IP Access with S2a is supported only for the accesses that support such feature and the UEs that have such capability. + +During the establishment of a new PDN connection, the Trusted Non-3GPP IP Access allocates and sends a default EPS bearer ID to the PDN GW. The default EPS bearer ID is unique in the scope of the UE within an Trusted Non-3GPP IP Access, i.e. the IMSI and the default EPS bearer ID together identify a PDN connection within an Trusted Non-3GPP IP Access. In order to be able to identify a specific established PDN connection, both the Trusted Non-3GPP IP Access and the PDN GW shall store the default EPS bearer ID. + +For network supporting multiple mobility protocols, the AAA/HSS enforces the same IPMS decision for each additional PDN connection as for initial attach. + +![Sequence diagram illustrating Additional PDN connectivity with GTP on S2a for non-roaming and roaming scenarios. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access (MAG), PDN GW, PDN GW 2, vPCRF, AAA Proxv, hPCRF, and HSS/AAA. The process involves triggering new PDN connectivity, performing steps 5-9 of initial attach, replying with new PDN connectivity information, and establishing a new GTP tunnel.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The diagram is a sequence diagram showing the interaction between several network entities for establishing additional PDN connectivity. The entities are: UE, Trusted Non-3GPP IP Access (MAG), PDN GW, PDN GW 2, vPCRF, AAA Proxv, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxv, and hPCRF. The sequence of messages is as follows: + +- The UE sends a message '1. Trigger new PDN Connectivity' to the Trusted Non-3GPP IP Access (MAG). +- The Trusted Non-3GPP IP Access (MAG) initiates '2. Steps 5-9 of Initial Attach' with the PDN GW. +- The Trusted Non-3GPP IP Access (MAG) sends a message '3. Reply(new PDN connectivity information)' to the UE. +- A '4. New GTP Tunnel' is established between the Trusted Non-3GPP IP Access (MAG) and the PDN GW 2. + +Existing GTP Tunnels are shown between the UE and the Trusted Non-3GPP IP Access (MAG), and between the Trusted Non-3GPP IP Access (MAG) and the PDN GW. + +Sequence diagram illustrating Additional PDN connectivity with GTP on S2a for non-roaming and roaming scenarios. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access (MAG), PDN GW, PDN GW 2, vPCRF, AAA Proxv, hPCRF, and HSS/AAA. The process involves triggering new PDN connectivity, performing steps 5-9 of initial attach, replying with new PDN connectivity information, and establishing a new GTP tunnel. + +**Figure 6.1.3.3-1: Additional PDN connectivity with GTP on S2a for non-roaming and roaming** + +The steps in the procedure which are marked as optional occur only if dynamic policy provisioning has been deployed. + +The home routed roaming, LBO and non-roaming scenarios are depicted in the figure 6.1.3.3-1. + +- In the LBO case, the 3GPP AAA Proxy acts as an intermediary, forwarding messages from the 3GPP AAA Server in the HPLMN to the PDN GW in the VPLMN and vice versa. Messages between the PDN GW in the VPLMN and the hPCRF in the HPLMN are forwarded by the vPCRF in the VPLMN. + - In the home routed roaming and non-roaming cases, the vPCRF and the 3GPP AAA Proxy are not involved. +- 1) When the UE wishes to connect to an additional PDN, it sends a trigger indicating that connectivity with that specific PDN is desired. The UE provides information about the new PDN by using an APN. When multiple PDN connections to a single APN are supported then some additional access specific mechanism is needed between the UE and the Trusted Non-3GPP IP Access to differentiate the PDN connections towards the same APN. If supported by the non-3GPP access, the UE may send Protocol Configuration Options in this step using access specific mechanisms. The Protocol Configuration Options provided by the UE may include the user credentials for PDN access authorization. The UE triggers the re-establishment of existing PDN connectivity after the handover by providing a Request Type indicating "Handover" on accesses that support the indication. + +NOTE 1: The definition of the trigger that the UE provides to the access network is out of scope of 3GPP. + +- 2) At this step the Trusted non-3GPP IP Access performs PDN GW selection as described in Steps 5 to 9 of Initial Attach procedure, while PDN GW2 is selected. +- 3) The Trusted non-3GPP IP Access sends the reply message to the UE with the allocated IP address from the PDN that the UE indicated at step 1. If supported by the non-3GPP access, the Protocol Configuration Options provided by the PDN GW2 in step 2 are returned to the UE in this step using access specific mechanisms. Since UE requested for additional PDN connectivity, the UE configures the IP address received from the Trusted Non-3GPP IP Access without deleting its configuration for connectivity with any other previously established PDN. + +NOTE 2: The definition of the message used to carry the new connectivity information to the UE is out of scope of 3GPP. + +- 4) The GTP tunnel is thus set up between the Trusted Non-3GPP IP Access and the PDN GW corresponding to the requested additional PDN while maintaining tunnels previously established for other PDNs. + +#### 6.1.3.4 Dedicated bearer activation with GTP on S2a + +The dedicated bearer activation procedure for GTP based S2a is depicted in figure 6.1.3.4-1. + +![Sequence diagram of Dedicated S2a Bearer Activation Procedure with GTP on S2a. The diagram shows interactions between UE, Trusted non-3GPP access, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxv, vPCRF, and hPCRF. The sequence is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Create Bearer Request (PDN GW to Trusted non-3GPP access), 3. Trusted non-3GPP access specific mechanism for resource allocation or modification (dashed box), 4. Create Bearer Response (Trusted non-3GPP access to PDN GW), 5. IP-CAN Session Modification (PDN GW to vPCRF).](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TNA as Trusted non-3GPP access + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + AAA_Proxv as AAA Proxv + vPCRF + hPCRF + end + PDN_GW-->>vPCRF: 1. IP-CAN Session Modification + PDN_GW->>TNA: 2. Create Bearer Request + Note right of TNA: 3. Trusted non-3GPP access specific mechanism for resource allocation or modification + TNA->>PDN_GW: 4. Create Bearer Response + PDN_GW-->>vPCRF: 5. IP-CAN Session Modification + +``` + +Sequence diagram of Dedicated S2a Bearer Activation Procedure with GTP on S2a. The diagram shows interactions between UE, Trusted non-3GPP access, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxv, vPCRF, and hPCRF. The sequence is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Create Bearer Request (PDN GW to Trusted non-3GPP access), 3. Trusted non-3GPP access specific mechanism for resource allocation or modification (dashed box), 4. Create Bearer Response (Trusted non-3GPP access to PDN GW), 5. IP-CAN Session Modification (PDN GW to vPCRF). + +**Figure 6.1.3.4-1: Dedicated S2a Bearer Activation Procedure with GTP on S2a** + +1. If dynamic PCC is deployed, the PCRF sends a PCC decision provision (QoS policy) message to the PDN GW. This corresponds to the initial steps of the PCRF-Initiated IP CAN Session Modification procedure or to the PCRF response in the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203 [4], up to the point that the PDN GW requests IP CAN Bearer Signalling. If dynamic PCC is not deployed, the PDN GW may apply local QoS policy. +2. The PDN GW uses this QoS policy to assign the S2a bearer QoS, i.e., it assigns the values to the bearer level QoS parameters QCI, ARP, GBR and MBR. The PDN GW sends a Create Bearer Request message (IMSI, EPS bearer QoS, TFT, PDN GW Address for the user plane, PDN GW TEID of the user plane, Charging Id, LBI) to the trusted non-3GPP access. The Linked EPS bearer Identity (LBI) is the EPS bearer Identity of the default S2a bearer. +3. If supported by the trusted non-3GPP access, a trusted non-3GPP access specific resource allocation/modification procedure may be executed in this step. The details of this step are out of the scope of 3GPP. +4. The trusted non-3GPP access selects an EPS bearer Identity, which has not yet been assigned to the UE. The trusted non-3GPP access then stores the EPS bearer Identity and links the dedicated S2a bearer to the default S2a bearer indicated by the Linked Bearer Identity (LBI). The trusted non-3GPP access uses the uplink packet filter (UL TFT) to determine the mapping of uplink traffic flows to the S2a bearer. The trusted non-3GPP access then acknowledges the S2a bearer activation to the PDN GW by sending a Create Bearer Response (EPS bearer Identity, trusted non-3GPP access Address for the user plane, trusted non-3GPP access TEID of the user plane) message. + +- If the dedicated bearer activation procedure was triggered by a PCC Decision Provision message from the PCRF, the PDN GW indicates to the PCRF whether the requested PCC decision (QoS policy) could be enforced or not, allowing the completion of the PCRF-Initiated IP CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203 [4], after the completion of IP CAN bearer signalling. + +NOTE 1: The exact signalling of step 1 and 5 (e.g. for local break-out) is outside the scope of this TR. This signalling and its interaction with the dedicated bearer activation procedure are to be specified in TS 23.203 [4]. Steps 1 and 5 are included here only for completeness. + +### 6.1.3.5 Network-initiated S2a bearer modification with GTP on S2a + +#### 6.1.3.5.1 PDN GW Initiated Bearer Modification + +The PDN GW initiated bearer modification procedure for a GTP based S2a is depicted in figure 6.1.3.5.1-1. This procedure is used to update the TFT for an active default or dedicated S2a bearer, or in cases when one or several of the S2a bearer QoS parameters QCI, GBR, MBR or ARP are modified (including the QCI or the ARP of the default S2a bearer e.g. due to the HSS Initiated Subscribed QoS Modification procedure, as described in clause 6.1.3.5.2). + +![Sequence diagram of PDN GW-initiated S2a Bearer Modification Procedure with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP access, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxy, vPCRF, and hPCRF. The sequence is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Update Bearer Request (PDN GW to Trusted Non-3GPP IP access), 3. Access specific mechanism to enforce the policy (Trusted Non-3GPP IP access), 4. Update Bearer Response (Trusted Non-3GPP IP access to PDN GW), 5. IP-CAN Session Modification (PDN GW to vPCRF).](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TrustedNon3GPP as Trusted Non-3GPP IP access + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant AAA_Proxy as AAA Proxy + participant vPCRF + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + PDN_GW->>vPCRF: 1. IP-CAN Session Modification + PDN_GW->>TrustedNon3GPP: 2. Update Bearer Request + Note left of TrustedNon3GPP: 3. Access specific mechanism to enforce the policy + TrustedNon3GPP->>PDN_GW: 4. Update Bearer Response + PDN_GW->>vPCRF: 5. IP-CAN Session Modification + +``` + +Sequence diagram of PDN GW-initiated S2a Bearer Modification Procedure with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP access, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxy, vPCRF, and hPCRF. The sequence is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Update Bearer Request (PDN GW to Trusted Non-3GPP IP access), 3. Access specific mechanism to enforce the policy (Trusted Non-3GPP IP access), 4. Update Bearer Response (Trusted Non-3GPP IP access to PDN GW), 5. IP-CAN Session Modification (PDN GW to vPCRF). + +**Figure 6.1.3.5.1-1: PDN GW-initiated S2a Bearer Modification Procedure with GTP on S2a** + +- If dynamic PCC is deployed, the PCRF sends a PCC decision provision (QoS policy) message to the PDN GW. This corresponds to the initial steps of the PCRF-Initiated IP CAN Session Modification procedure or to the PCRF response in the PCEF initiated IP-CAN Session Modification procedure as defined in 3GPP TS 23.203 [4], up to the point that the PDN GW requests IP-CAN Bearer Signalling. If dynamic PCC is not deployed, the PDN GW may apply local QoS policy. +- The PDN GW uses this QoS policy to determine that a service data flow shall be aggregated to or removed from an active S2a bearer or that the authorized QoS of a service data flow has changed. The PDN GW generates the TFT and updates the S2a bearer QoS to match the traffic flow aggregate. The PDN GW then sends the Update Bearer Request (EPS bearer Identity, EPS bearer QoS, TFT) message to the trusted non-3GPP IP access. +- If supported by the trusted non-3GPP access, an IP-CAN specific resource allocation or resource release procedure may be triggered by the enforcement of the received policy rules. The details of this step are out of the scope of 3GPP. +- The trusted non-3GPP IP access uses the uplink packet filter (UL TFT) to determine the mapping of traffic flows to the S2a bearer and acknowledges the S2a bearer modification to the PGW by sending an Update Bearer Response (EPS bearer Identity) message. +- If the Bearer modification procedure was triggered by a PCC Decision Provision message from the PCRF, the PDN GW indicates to the PCRF whether the requested PCC decision (QoS policy) could be enforced or not by + +sending a Provision Ack message allowing the completion of the PCRF-Initiated IP CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203 [4], after the completion of IP CAN bearer signalling. + +NOTE: The exact signalling of step 1 and 5 (e.g. for local break-out) is outside the scope of this TR. This signalling and its interaction with the bearer activation procedure are to be specified in TS 23.203 [4]. Step 1 and 5 are included here only for completeness. + +#### 6.1.3.5.2 HSS Initiated Subscribed QoS Modification + +The HSS Initiated Subscribed QoS Modification for a GTP-based S2a is depicted in figure 6.1.3.5.2-1. + +![Sequence diagram for HSS Initiated Subscribed QoS Modification showing interactions between UE, Trusted non-3GPP IP access, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Trusted as Trusted non-3GPP IP access + participant PDN GW + participant AAA Proxy + participant vPCRF + participant hPCRF + participant HSS/AAA + + Note over AAA Proxy, hPCRF: Roaming Scenarios + + rect rgb(255, 255, 255) + Note over PDN GW, HSS/AAA: 1. HSS-initiated User Profile Update procedure as in TS 23.402 + end + + PDN GW->>Trusted: 2. Modify Bearer Command + + Note over PDN GW, vPCRF: 3. PCEF Initiated IP-CAN Session Modification + PDN GW-->vPCRF: + vPCRF-->PDN GW: + + Trusted->>PDN GW: 4. Update Bearer Request + + rect rgb(255, 255, 255) + Note over UE, Trusted: 5. Access specific mechanism to enforce the policy + end + + PDN GW->>Trusted: 6. Update Bearer Response + + Note over PDN GW, vPCRF: 7. Provision Ack + PDN GW-->vPCRF: + vPCRF-->PDN GW: + +``` + +Detailed description: The diagram shows a sequence of 7 steps. Step 1 is a broad box spanning PDN GW to HSS/AAA representing the User Profile Update. Step 2 is a message from PDN GW to Trusted non-3GPP IP access. Step 3 is a bi-directional interaction between PDN GW and vPCRF (labeled PCEF Initiated IP-CAN Session Modification). Step 4 is a message from Trusted non-3GPP IP access to PDN GW. Step 5 is a dashed box between UE and Trusted non-3GPP IP access for policy enforcement. Step 6 is a message from PDN GW to Trusted non-3GPP IP access. Step 7 is a bi-directional interaction between PDN GW and vPCRF (labeled Provision Ack). + +Sequence diagram for HSS Initiated Subscribed QoS Modification showing interactions between UE, Trusted non-3GPP IP access, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. + +**Figure 6.1.3.5.2-1: HSS Initiated Subscribed QoS Modification** + +1. The HSS updates the User Profile as specified in clause 12.2.1 of TS 23.402 [3]. +2. If the QCI and/or ARP and/or subscribed APN-AMBR has been modified and there is a related active PDN connection with the modified QoS Profile, the trusted non-3GPP IP access sends the Modify Bearer Command (EPS bearer Identity, EPS bearer QoS, APN AMBR) message to the PDN GW. The EPS bearer Identity identifies the default bearer of the affected PDN connection. The EPS bearer QoS contains the EPS subscribed QoS profile to be updated. +3. If PCC infrastructure is deployed, the PDN GW informs the PCRF about the updated EPS bearer QoS. The PCRF sends the new updated PCC decision to the PDN GW. This corresponds to the PCEF-initiated IP CAN Session Modification procedure as defined in TS 23.203 [4]. + +The PCRF may modify the APN-AMBR and the QoS parameters (QCI and ARP) associated with the default bearer in the response to the PDN GW as defined in TS 23.203 [4]. + +4. The PDN GW modifies the default bearer of each PDN connection corresponding to the APN for which subscribed QoS has been modified. If the subscribed ARP parameter has been changed, the PDN GW shall also modify all dedicated S2a bearers having the previously subscribed ARP value unless superseded by PCRF decision. The PDN GW then sends the Update Bearer Request (EPS bearer Identity, EPS bearer QoS, TFT, APN AMBR) message to the trusted non-3GPP IP access. +5. If supported by the trusted non-3GPP access, an IP-CAN specific procedure may be triggered by the enforcement of the received policy rules. The details of this step are out of the scope of 3GPP. + +6. The trusted non-3GPP IP access acknowledges the bearer modification to the PDN GW by sending an Update Bearer Response (EPS bearer Identity) message. If the bearer modification fails the PDN GW deletes the concerned S2a Bearer. +7. The PDN GW indicates to the PCRF whether the requested PCC decision was enforced or not by sending a Provision Ack message. + +### 6.1.3.6 PDN GW initiated Resource Allocation Deactivation with GTP on S2a + +This procedure depicted in figure 6.1.3.6-1 can be used to deactivate a dedicated bearer or deactivate all bearers belonging to a PDN address, for e.g., due to IP CAN session modification requests from the PCRF or due to handover from Non-3GPP to 3GPP access. If the default bearer belonging to a PDN connection is deactivated, the PDN GW deactivates all bearers belonging to the PDN connection. + +When it is performed for a handover, the connections associated with the PDN address are released, but the PDN address is kept in the PDN GW. + +![Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Delete Bearer Request (PDN GW to Trusted Non-3GPP IP Access), 3. Non-3GPP specific resource Release Procedure (Trusted Non-3GPP IP Access to UE), 4. Delete Bearer Response (Trusted Non-3GPP IP Access to PDN GW), 5. Update PDN GW Address (PDN GW to AAA/HSS), 6. IP-CAN Session Modification (PDN GW to vPCRF).](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Delete Bearer Request (PDN GW to Trusted Non-3GPP IP Access), 3. Non-3GPP specific resource Release Procedure (Trusted Non-3GPP IP Access to UE), 4. Delete Bearer Response (Trusted Non-3GPP IP Access to PDN GW), 5. Update PDN GW Address (PDN GW to AAA/HSS), 6. IP-CAN Session Modification (PDN GW to vPCRF). + +**Figure 6.1.3.6-1: PDN GW Initiated Bearer Deactivation with GTP on S2a** + +This procedure applies to the Non-Roaming, Roaming and Local Breakout cases. In the Local Breakout case, the vPCRF forwards messages between the PDN GW and the hPCRF. In the non-roaming and home routed roaming cases, the vPCRF is not involved at all. + +The optional interaction steps between the PDN GW and the PCRF in the procedures in figure 6.1.3.6-1 only occur if dynamic policy provisioning is deployed. Otherwise policy may be statically configured within the PDN GW. + +1. If dynamic PCC is deployed, the PDN GW initiated Bearer Deactivation procedure may for example be triggered due to 'IP CAN session Modification procedure', as defined in 3GPP TS 23.203 [4]. In this case, the resources associated with the PDN connection in the PDN GW are released. + +The PDN GW initiated Resource Allocation Deactivation can also be triggered during handovers from Non-3GPP to 3GPP. + +2. The PDN GW sends a Delete Bearer Request message (EPS Bearer Identity, Cause) to the trusted non-3GPP IP access. +3. If supported by the trusted non-3GPP access, the Non 3GPP specific resources may be released in the non-3GPP IP access. The details of this step are out of the scope of 3GPP. + +4. The trusted non-3GPP IP access deletes the bearer contexts related to the Delete Bearer Request, and acknowledges the bearer deactivation to the PDN GW by sending a Delete Bearer Response (EPS Bearer Identity) message. +5. In the case where the resources corresponding to the PDN connection are released in PDN GW, the PDN GW informs the 3GPP AAA Server/HSS of the PDN disconnection. If this is the last PDN connection for the given APN, the PDN GW identity information and APN corresponding to the UE's PDN Connection is removed from the AAA Server/HSS. This information is de-registered from the HSS as described in TS 23.402 [3]. +6. The PDN GW deletes the bearer context related to the deactivated EPS bearer. If the dedicated bearer deactivation procedure was triggered by receiving a PCC decision message from the PCRF, the PDN GW indicates to the PCRF whether the requested PCC decision was successfully enforced by completing the PCRF-initiated IP CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203 [4], proceeding after the completion of IP CAN bearer signalling. + +### 6.1.3.7 Handovers without Optimizations Between 3GPP Accesses and Non-3GPP IP Accesses with S2a GTP + +#### 6.1.3.7.1 Handover from a trusted non-3GPP IP access with S2a GTP to 3GPP Access + +The handover procedure from a trusted non-3GPP IP access using GTP S2a to E-UTRAN access using GTP S5/S8 connected to EPC is similar to the procedure specified in TS 23.402 [3], clause 8.2.1.1, except that: + +- at step 1, the tunnel between trusted non-3GPP access and the PGW is a GTP tunnel; +- at step 7, the PDN GW may create dedicated bearers during this procedure. +- at step 18, the PDN GW shall initiate resource allocation deactivation procedure in the trusted non-3GPP IP access as defined in clause 6.1.3.6 PDN GW initiated Resource Allocation Deactivation with GTP on S2a. + +![Sequence diagram for handover from Trusted Non-3GPP IP Access with GTP on S2a to E-UTRAN. The diagram shows the interaction between UE, Trusted non-3GPP Access, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A green bar at the top indicates the initial GTP tunnel between the UE and the PDN GW. A dashed box labeled (C) encloses the core network elements (MME, Serving GW, Old MME/SGSN, PDN GW). Below this, two messages labeled '18.NON-3GPP EPS Bearer Release' are shown, one from the PDN GW to the Trusted non-3GPP Access and another from the PDN GW to the HSS/AAA. The 'Roaming Scenarios' section includes the AAA Proxy, vPCRF, hPCRF, and HSS/AAA.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +Sequence diagram for handover from Trusted Non-3GPP IP Access with GTP on S2a to E-UTRAN. The diagram shows the interaction between UE, Trusted non-3GPP Access, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A green bar at the top indicates the initial GTP tunnel between the UE and the PDN GW. A dashed box labeled (C) encloses the core network elements (MME, Serving GW, Old MME/SGSN, PDN GW). Below this, two messages labeled '18.NON-3GPP EPS Bearer Release' are shown, one from the PDN GW to the Trusted non-3GPP Access and another from the PDN GW to the HSS/AAA. The 'Roaming Scenarios' section includes the AAA Proxy, vPCRF, hPCRF, and HSS/AAA. + +**Figure 6.1.3.7.1-1: Handover from Trusted Non-3GPP IP Access with GTP on S2a to E-UTRAN** + +The handover procedure from a trusted non-3GPP IP access using GTP S2a to UTRAN/GERAN access using GTP S5/S8 connected to EPC is similar to the procedure specified in TS 23.402 [3], clause 8.2.1.3, except that: + +- at step 1, the tunnel between trusted non-3GPP access and the PGW is a GTP tunnel; +- at step 10, the PDN GW may create dedicated bearers during this procedure. +- at step 17, the PDN GW shall initiate resource allocation deactivation procedure in the trusted non-3GPP IP access as defined in clause 6.1.3.6 PDN GW initiated Resource Allocation Deactivation with GTP on S2a. + +![Sequence diagram for handover from Trusted Non-3GPP IP Access with GTP on S2a to UTRAN/GERAN. Lifelines: UE, Trusted Non-3GPP IP Access, 3GPP Access, SGSN, Serving GW, Old SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, HSS/AAA. The diagram shows the flow of data and signaling during the handover process.](26d664119ad25250780f554633444e54_img.jpg) + +The diagram illustrates the sequence of operations for a handover from a Trusted Non-3GPP IP Access to a 3GPP Access (UTRAN/GERAN). The lifelines involved are: UE, Trusted Non-3GPP IP Access, 3GPP Access, SGSN, Serving GW, Old SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A green bar at the top indicates the initial GTP tunnel(s) between the UE and the PDN GW. A dashed box labeled (D) encloses the 'Procedure per 8.2.1.3 steps 2 to 16'. Step 17, 'Non-3GPP EPS Bearer Release', is shown as a message from the PDN GW to the 3GPP Access and from the PDN GW to the AAA Proxy. The AAA Proxy, vPCRF, and hPCRF are grouped under 'Roaming Scenarios'. + +Sequence diagram for handover from Trusted Non-3GPP IP Access with GTP on S2a to UTRAN/GERAN. Lifelines: UE, Trusted Non-3GPP IP Access, 3GPP Access, SGSN, Serving GW, Old SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, HSS/AAA. The diagram shows the flow of data and signaling during the handover process. + +Figure 6.1.3.7.1-2: Handover from Trusted Non-3GPP IP Access with GTP on S2a to UTRAN/GERAN + +6.1.3.7.2 Handover from 3GPP Access to a trusted non-3GPP IP access with S2a GTP + +NOTE 1: This procedure is based on TS 23.402 [3], clause 8.2.2. Only the differences are described below. + +![Sequence diagram illustrating the handover from 3GPP Access to Trusted Non-3GPP IP Access with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, 3GPP Access, MME/SGSN, Serving GW, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. Key steps include: 1. GTP/PMIP tunnel establishment; 2. UE discovers Trusted Non-3GPP Access and initiates HO; 3. Access Authentication and Authorization (PDN GW); 4. L3 Attach Trigger; 5. Create Session Request (IMSI, PDN GW); 6A. PCEF-Initiated IP-CAN Session Modification Procedure; 6B. Update AAA Server/HSS; 7. Create Session Response (IP Addr); 8. L3 Attach Completion; 9. GTP tunnel establishment; 10. UE-initiated Connectivity to Additional PDN; 11. 3GPP EPS Bearer Release. A 'Roaming Scenarios' box covers the AAA Proxy, vPCRF, hPCRF, and HSS/AAA components.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Sequence diagram illustrating the handover from 3GPP Access to Trusted Non-3GPP IP Access with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, 3GPP Access, MME/SGSN, Serving GW, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. Key steps include: 1. GTP/PMIP tunnel establishment; 2. UE discovers Trusted Non-3GPP Access and initiates HO; 3. Access Authentication and Authorization (PDN GW); 4. L3 Attach Trigger; 5. Create Session Request (IMSI, PDN GW); 6A. PCEF-Initiated IP-CAN Session Modification Procedure; 6B. Update AAA Server/HSS; 7. Create Session Response (IP Addr); 8. L3 Attach Completion; 9. GTP tunnel establishment; 10. UE-initiated Connectivity to Additional PDN; 11. 3GPP EPS Bearer Release. A 'Roaming Scenarios' box covers the AAA Proxy, vPCRF, hPCRF, and HSS/AAA components. + +**Figure 6.1.3.7.2-1: Handover from 3GPP Access to Trusted Non-3GPP IP Access with GTP on S2a** + +1-4) Same as step 1-4 in TS 23.402 [3] clause 8.2.2 except that at step 1, the tunnel between Serving GW and the PGW may be both a GTP or a PMIP tunnel. + +5) The entity in the Trusted non-3GPP IP Access sends Create Session Request (IMSI, APN, Handover Indication, RAT type, Trusted non-3GPP IP Access TEID of the control plane, Trusted non-3GPP IP Access Address for the user plane, Trusted non-3GPP IP Access TEID of the user plane, EPS Bearer Identity) message to the PDN GW. The RAT type indicates the non-3GPP IP access technology type. If the UE supports IP address preservation and included the address in early steps, the Trusted non-3GPP IP Access sets the 'Handover Indication' in the Creation Session Request to allow the PDN GW to re-allocate the same IP address or prefix that was assigned to the UE while it was connected to the 3GPP IP access and to initiate a PCEF-Initiated IP CAN Session Modification Procedure with the PCRF. + +NOTE 2: With GTP on S2a, APN, IMSI and EPS Bearer ID identifies a PDN connection over GTP based S2a. + +NOTE 3: With GTP on S2a, there is no relation between the values of the EPS bearer identities used within 3GPP networks and non-3GPP networks. + +NOTE 4: In a non-3GPP to 3GPP access handover, the 'Handover Indication' leads the PDN GW to delay switching the DL user plane traffic from non-3GPP to 3GPP until a subsequent Modify Bearer Request is received. In a 3GPP to non-3GPP handover scenario with GTP based S2a, the 'Handover Indication' should not delay the switching of DL user plane traffic from 3GPP to non-3GPP access. + +6A-6B) Same as steps 7A and 7B in TS 23.402 [3] clause 8.2.2 with following additions: + +- at step 8, the PDN GW may create dedicated bearers during this procedure. + +7) The PDN GW responds with a Create Session Response (PDN GW Address for the user plane, PDN GW TEID of the user plane, PDN GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, Charging ID, Cause) message to the Trusted non-3GPP IP Access. The Create Session Response contains the IP address and/or the prefix that was assigned to the UE while it was connected to the 3GPP IP access. + +8-11) Same as step 9-12 in TS 23.402 [3] clause 8.2.2, except that at step 12, the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401 [6], clause 5.4.4.1. + +--- + +## 7 Additional considerations for WLAN access to EPC through S2a for Phase 1 + +### 7.1 Solutions without UE Impact + +#### 7.1.0 General + +1) Multiple PDN connections in the WLAN access + +Since the support of multiple PDN connections in the WLAN access would require the UE to signal the APN, a solution without UE impact only considers a single PDN connection in WLAN. This does not preclude multiple PDN connections through 3GPP and WLAN as long as there is only one PDN connection using WLAN access. + +2) Mobility aspects + +A solution without any impact to the UE only considers mobility without IP address preservation: the preservation on WLAN of the IP address the UE used on the 3GPP access would require changes in existing UEs as it is not specified in current 3GPP specifications. + +NOTE: The security considerations of the internal WLAN-based trusted non-3GPP access network architecture are outside the scope of this study item. + +#### 7.1.1 Solution 1 + +##### 7.1.1.1 Reference model + +When the WLAN is considered as trusted by the operator, the WLAN AN is interfaced as any trusted non-3GPP access i.e. via STa to the 3GPP AAA Server and via S2a to a PDN-GW. EPC access via Trusted WLAN is supported through S2a interface. A single SSID offering simultaneous access for a UE to EPC through S2a and non-seamless offload is not supported. Non-seamless offload may however be supported in some deployments (e.g. with separate SSIDs for non-seamless offload and access to EPC through S2a via Wireless LAN, see clause 7.1.1.4). + +The reference model is depicted in the following figure. + +![Non-roaming Trusted WLAN Inter-working reference model diagram](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +This diagram illustrates the non-roaming Trusted WLAN Inter-working reference model. On the left, a 'WLAN UE' is connected to a 'Trusted WLAN Access Network' via the 'SWw' interface. The 'Trusted WLAN Access Network' is connected to an 'Intranet / Internet' cloud and has two interfaces on the right: 'STa' connecting to a '3GPP AAA Server' and 'S2a' connecting to a 'PDN GW'. The '3GPP AAA Server' is connected to an 'HSS' via the 'SWx' interface. The 'PDN GW' is connected to an 'hPCRF' via the 'Gx' interface and has an 'SGi/Gi' interface on the far right. All components of the '3GPP Home Network' (HSS, 3GPP AAA Server, PDN GW, and hPCRF) are contained within a single boundary. + +Non-roaming Trusted WLAN Inter-working reference model diagram + +Figure 7.1.1.1-1: Non-roaming Trusted WLAN Inter-working reference model + +![Home Routed Roaming Trusted WLAN Inter-working reference model diagram](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +This diagram illustrates the Home Routed Roaming Trusted WLAN Inter-working reference model. A 'WLAN UE' connects to a 'Trusted WLAN Access Network' via 'SWw'. The 'Trusted WLAN Access Network' connects to an 'Intranet / Internet' cloud and has two interfaces on the right: 'STa' connecting to a '3GPP AAA Proxy' and 'S2a' connecting to a 'PDN GW'. The '3GPP AAA Proxy' connects to a '3GPP AAA Server' via the 'SWd' interface. The '3GPP AAA Server' connects to an 'HSS' via the 'SWx' interface. The 'PDN GW' connects to an 'hPCRF' via the 'Gx' interface and has an 'SGi/Gi' interface on the far right. The '3GPP AAA Proxy' is located outside the '3GPP Home Network' boundary, which contains the 'HSS', '3GPP AAA Server', 'PDN GW', and 'hPCRF'. + +Home Routed Roaming Trusted WLAN Inter-working reference model diagram + +Figure 7.1.1.1-2: Home Routed Roaming Trusted WLAN Inter-working reference model + +![Local Breakout Roaming Trusted WLAN Inter-working reference model diagram](805c475f0859e607af0530ba43194bf1_img.jpg) + +This diagram illustrates the Local Breakout Roaming Trusted WLAN Inter-working reference model. A 'WLAN UE' connects to a 'Trusted WLAN Access Network' via 'SWw'. The 'Trusted WLAN Access Network' connects to an 'Intranet / Internet' cloud and has two interfaces on the right: 'STa' connecting to a '3GPP AAA Proxy' and 'S2a' connecting to a 'PDN GW'. The '3GPP AAA Proxy' connects to a '3GPP AAA Server' via the 'SWd' interface. The '3GPP AAA Server' connects to an 'HSS' via the 'SWx' interface. The 'PDN GW' connects to a 'vPCRF' via the 'Gx' interface and has an 'SGi/Gi' interface on the far right. The 'vPCRF' connects to an 'hPCRF' via the 'S9' interface. The '3GPP AAA Proxy', 'PDN GW', and 'vPCRF' are located outside the '3GPP Home Network' boundary, which contains the 'HSS', '3GPP AAA Server', and 'hPCRF'. + +Local Breakout Roaming Trusted WLAN Inter-working reference model diagram + +Figure 7.1.1.1-3: Local Breakout Roaming Trusted WLAN Inter-working reference model + +Within the trusted non-3GPP IP access network (TNAN) we distinguish three functions: + +- A WLAN Access Network (WLAN AN). This function terminates the UE's WiFi air link defined in IEEE 802.11 [5]. +- A Trusted non-3GPP access's S2a peer (TNSP). This function terminates S2a. +- A Trusted non-3GPP access's STa peer (TNAP). This function terminates STa. + +NOTE 1: Policy and QoS aspects are studied as part of BBAI. + +NOTE 2: Whether multiple TNAN functions are mapped to a single non-3GPP access entity, or a single TNAN function is distributed among multiple non-3GPP access entities is out-of-scope of 3GPP. + +#### **STa reference point** + +The STa reference point is defined in TS 23.402 [3] and specified in TS 29.273 [7]. It connects the Trusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and transports access authentication, authorization, mobility parameters and charging-related information in a secure manner. + +STa might need to be enhanced to support: + +- A way for the Trusted WLAN Access Network to provide the AAA server with following information: + - An indication on whether the Trusted WLAN AN supports S2a, non-seamless offload or both; + +NOTE 3: Stage 3 discussions will determine whether existing "Mobility Capabilities" over STa may be reused for that purpose. + +- The SSID selected by the UE to access the Trusted WLAN AN. +- A way for the AAA server to provide the Trusted WLAN Access Network with following information: + - The APN the user is to be associated with for EPC access; this is required for the Trusted WLAN Access Network to establish the PDN connection with the PDN GW. Based on the HPLMN operator configuration the HSS may provide the 3GPP AAA server with a default APN for Trusted WLAN Access Network. + +NOTE 4: Stage 3 discussions will determine whether existing "Default APN" over STa may be reused for that purpose. + +- Whether access to EPC is allowed for the UE. + +NOTE 5: Stage 3 discussions will determine whether existing "Mobility Capabilities" over STa may be reused for that purpose. + +- The UE IMSI; this is required for the Trusted WLAN Access Network to build the S2a messages towards the PDN-GW. + +NOTE 6: Stage 3 discussions will determine whether existing "Permanent User Identity" over STa may be reused for that purpose. + +#### **SWw reference point** + +The SWw reference point connects the WLAN UE to the WLAN Access Network according to IEEE 802.11 [5]. This includes the support of: + +- the security that was defined as part of 802.11-2007 [5] and thus the transport of EAP signalling messages for authentication signalling between the 3GPP AAA Server and the WLAN UE; +- parameters for identification of the operator networks for roaming purposes (i.e. PLMN list). + +#### **SWx reference point** + +The SWx reference point is defined for EPC in TS 23.402 [3]. It is specified at stage 3 level respectively in TS 29.273 [7]. + +### 7.1.1.2 Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW + +![Sequence diagram of the Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes the PDN GW, vPCRF, AAA Proxy, and hPCRF. The process involves Non-3GPP specific procedures, EAP authentication, L3 attach trigger, session request, IP-CAN session establishment, PDN GW address update, GTP tunnel creation, and L3 attach completion.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TNSP as Trusted Non-3GPP IP Access + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note left of UE: 1. Non-3GPP Specific Procedures + Note left of UE: 2. EAP Authentication + Note left of UE: 3. L3 Attach Trigger + Note right of PDN_GW: Roaming Scenarios + + TNSP->>HSS_AAA: 2. Authentication & Authorization + HSS_AAA-->>TNSP: + TNSP->>PDN_GW: 5. Create Session Request + Note right of PDN_GW: 6. IP-CAN Session Establishment Procedure + PDN_GW->>HSS_AAA: 7. Update PDN GW Address + HSS_AAA-->>PDN_GW: + PDN_GW-->>TNSP: 8. Create Session Response + Note right of PDN_GW: 9. GTP Tunnel + Note left of UE: 11. L3 Attach Completion + +``` + +Sequence diagram of the Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes the PDN GW, vPCRF, AAA Proxy, and hPCRF. The process involves Non-3GPP specific procedures, EAP authentication, L3 attach trigger, session request, IP-CAN session establishment, PDN GW address update, GTP tunnel creation, and L3 attach completion. + +**Figure 7.1.1.2-1: Initial attachment with Network-based MM mechanism over S2a for roaming, LBO and non-roaming scenarios** + +A per-UE point-to-point link between UE and TNSP is assumed. In particular, it is assumed that the trusted non-3GPP access does not do any routing of UE traffic between WLAN AN and TNSP. It is assumed that the WLAN AN applies upstream and downstream forced-forwarding between the UE's WiFi air link and the WLAN AN -TNSP link. The aspects of point-to-point link described in IETF RFC 5213 [17] and IETF RFC 5844 [18] also applies to the point-to-point link between UE and TNSP. The implementation of the point-to-point link is out-of-scope for 3GPP. + +In this specific solution, it is assumed that TNSP is the first hop router and the DHCP server. + +NOTE 1: The link model is different from GTP based S5/S8 and GTP based S2b. + +No specific mechanisms are defined to support AP-to-AP handover. + +Refer to clause 6.1.3.1. Based on assumptions for solutions with no impact to UE, UE cannot provide APN and PCO to TNSP. So, there are following differences than clause 6.1.3.1: + +- At step 2, the following additions apply: + - The HSS provide APN information to the Trusted Non-3GPP IP Access in the subscription data. HSS provides a default APN for WLAN. PDN type is indicated from HSS in this step. Based on the HPLMN operator configuration the HSS may provide the 3GPP AAA server with a default APN for Trusted WLAN Access Network. + +NOTE 2: If the APN used in 3GPP side is the same as the default APN for Trusted WLAN the network may select the same or different PDN GWs for the PDN connections when PDN connections to this APN are activated via 3GPP access network and Trusted WLAN in the same time. If the same PDN GW is selected then the APN-AMBR is enforced for the PDN connections. If different PDN GWs are selected then the APN-AMBR is enforced separately in the PDN GWs for the PDN connections, i.e. the UE will receive double amount of bandwidth for the APN. Therefore it is recommended that the default APN for Trusted WLAN access be different from any APN that the UE may use on the 3GPP side. + +- The UE and the EPC are mutually authenticated through the WLAN Access as defined in TS 23.402 [3] clause 4.9.1. +- IEEE 802.1X as defined by IEEE 802.11 [5] is used over the WLAN air link to carry EAP. +- After EAP authentication, UE traffic over the WLAN air link may be confidentiality and integrity protected as defined by IEEE 802.11 [5]. +- The TNAN may indicate to the AAA server via STa whether it supports S2a, non-seamless offload or both. The HSS/AAA may indicate via STa whether access to EPC via S2a is or is not allowed for this subscriber. The HSS/AAA decision to allow EPC access or not could be based on information elements such as subscriber profile, access network, SSID selected. +- At step 3, For IPv4 address configuration, the use of DHCPv4 as in IETF RFC 5844 [18] is the L3 attach trigger. +- At step 3, For IPv6 address configuration, the use of RS as in IETF RFC 5213 [17] or LL-DAD NS is the L3 attach trigger. The TNSP does not send RAs until an L3 attach trigger is received. + +NOTE 3: It is assumed that, to identify the UE, the L3 triggers are transported in an L2 frame that contains the UE L2 address (MAC address). + +- The TNAN determines based on HSS/AAA indication or pre-configured information whether or not to establish S2a. +- If the TNAN determined that S2a shall not be used steps 5-9 are skipped. Instead, the TNAN assigns an IPv4 address and/or IPv6 prefix to the UE (depending on the trigger received in step 3) and offloads the traffic. +- At step 5, when TNSP receives L3 attach trigger message, the TNSP selects default APN according the subscription data received in step 2. If the L3 attach trigger is of an IP version not supported by the subscription PDN Type, the TNSP does not send Create Session Request. Otherwise, the TNSP sends a Create Session Request with the PDN Type of the subscription data: + - If the L3 attach trigger is IPv4 and step 2 indicates that PDN type IPv4v6 is supported for the default APN, then PDN type in the Create Session Request is set to IPv4v6. If the UE also performs an IPv6 L3 attach trigger, then the TNSP will correlate both requests to the same PDN connection. + - If the L3 attach trigger is IPv6, and step 2 indicates that PDN type IPv4v6 is supported for the default APN, then PDN type in the Create Session Request is set to IPv4v6. If the UE also performs an IPv4 L3 attach trigger, then the TNSP will correlate both requests to the same PDN connection. + - If the L3 attach trigger is IPv4, and step 2 indicates that PDN type is IPv4-only, then PDN type in the Create Session Request is set to IPv4. + - If the L3 attach trigger is IPv6, and step 2 indicates that PDN type is IPv6-only, then PDN type in the Create Session Request is set to IPv6. +- At step 8, PDN GW sends Create Session Response to the TNSP. +- At step 11, for IPv4, a DHCPv4 message with allocated IPv4 address is sent. For IPv6, the TNSP starts sending RAs with the allocated prefix and sets "autonomous address configuration" flag and "O" flag [RFC 4861]. + +NOTE 4: A UE might request to get some IP configuration parameters (e.g. DNS server) by means of DHCP. These parameters sent by TNSP(acting as a DHCP server) to the UE in a DHCP reply. These parameters are retrieved by the TNSP(acting as a DHCP client) from the PGW by means of DHCP. + +### 7.1.1.3 Without-UE-impact procedures except Initial Attach + +Based on the GTP-S2a procedures in Section 6, for the solution without UE impact the following procedures are considered: + +- Detach and PDN Disconnection with GTP on S2a: + - Trusted WLAN AN and HSS/AAA may disconnect the PDN Connection and detach the UE, and the PDN GW may initiate Resource Allocation Deactivation for the default bearer as the PDN disconnection. If there is no traffic received from the UE for a configurable duration and the WLAN AN detects the UE has left based on unanswered probes (e.g. ARP Request, Neighbour Solicitation message), it disconnects the PDN Connection. In these cases the UE IP address(es) are released in the network. When disconnecting the PDN Connection, the TNAN needs to locally remove the UE context and de-authenticate and disconnect the UE at Layer 2 according to IEEE Std. 802.11-2007 [5]. When UE connects to the network next time, the L2 disconnection serves as an indication to the UE that the previous IPv4 address/IPv6 prefix might no longer be valid. The UE can then proceed with re-validation or re-acquisition of its IPv4 address / IPv6 prefix. +- The UE can send an explicit DHCPv4 message to release the IPv4 address, then the PDN connection is disconnected when the PDN type is IPv4. +- PDN GW Initiated Bearer Modification and HSS Initiated Subscribed QoS Modification procedures may be used to modify the default and dedicated bearer but correspond to no signalling over Trusted WLAN's airlink. +- The dedicated bearer activation procedure may be used to activate the dedicate bearer in S2a but correspond to no signalling over Trusted WLAN's airlink. + +In addition, the following procedures in clause 6 are not supported: + +- UE-initiated Connectivity to Additional PDN connection. +- The handover between Trusted WLAN and 3GPP Access with IP address preservation. + +### 7.1.1.4 SaMOG deployment + +WLAN networks may be deployed such that separate SSIDs are used for EPC-routed and non-seamless WLAN offload, e.g. SSID\_EPC and SSID\_NSO. + +WLAN networks may also be deployed such that the same SSID in a WLAN Access Point provides different type of network access to different users attached to this Access Point. For example, SSIDX may provide EPC-routed access for subscriber A, but non-seamless WLAN offload for subscriber B. In such a deployment it would be up to the operator to provide network configuration that supports different user access preferences, subscriptions and UE configurations. + +It is recommended that the UE can be configured to apply different behavior when connected to different SSIDs, e.g. allow or prevent the usage of certain applications on specific SSIDs. For example, for the SSIDs used for SaMOG the UE can be configured to disable applications that require local connectivity (e.g. DLNA applications) and enable applications that require EPC connectivity to the default APN used for SaMOG. Such kind of special behavior for SSIDs used for SaMOG can improve the user experience and prolong the UE battery life. + +NOTE: An unmodified UE can be configured to apply different behaviour when connected to different SSIDs by means which are outside the scope of this document. For example, the UE can be configured over-the-air, by means of a downloadable application, or by means of manual configuration. + +### 7.1.1.5 PMIP based S2a considerations + +The solution described above can also work when PMIP is used over S2a with the following considerations: + +- To support PMIP, the TNSP shall implement the MAG function as it is specified in TS 23.402 [3], clause 6 for S2a. Instead of GTP messages the relevant PMIP messages are used as it is specified in TS 23.402 [3], clause 6 for S2a. +- The considerations described on APN and PDN type selection in clause 7.1.1.2 are also valid when PMIP based S2a is used. + +- The link model, IPv4 address and IPv6 prefix allocation considerations of the sections describing the solution with GTP S2a (e.g. TNSP is the first hop router and DHCPv4 server shall be located in the TNSP) are also valid when PMIP based S2a is used. + +## 7.1.2 Solution 2 + +### 7.1.2.0 General + +This solution is based on the S2a bearer creation and deletion between a Trusted Non-3GPP WLAN Access and the 3GPP Home Network be driven by the AAA signalling between these two. A key difference to the solution described in clause 7.1.1 is that this solution uses EAP and AAA signalling to trigger establishment of the S2a session, while the solution in clause 7.1.1 uses L3 messages to trigger the S2a session. The interfaces towards EPC (STa and S2a) do not differ between the solutions. + +NOTE: Although the solution is described for a GTP-based S2a, it would equally apply to a PMIP-based system were the GTP signalling be replaced by the corresponding PMIP signalling (i.e. Create Session Request replaced by Proxy Binding Update, and Create Session Reply replaced by Proxy Binding Acknowledgement, as well as the corresponding BBERF procedures between Trusted WLAN Access Gateway and PCRF). + +### 7.1.2.1 Reference Model + +NOTE: The shaded area in Figures 7.1.2.1-1, 7.1.2.1-2, and 7.1.2.1-3 refers to Trusted Non-3GPP WLAN functionality. + +![Figure 7.1.2.1-1: Non-roaming reference model diagram. The diagram shows a UE connected to a WLAN Access Network (part of a Trusted Non-3GPP WLAN). The WLAN Access Network connects to a TWAP via the Ta interface and to a TWA via the Tn interface. The TWAP and TWA are connected via the Tg interface. The TWAP connects to the 3GPP Home Network via the STa interface, which is connected to a 3GPP AAA server. The 3GPP AAA server is connected to an HSS via the SWx interface. The TWA connects to the 3GPP Home Network via the S2a interface, which is connected to a PDN GW. The PDN GW is connected to the SGi interface. The UE is also connected to the WLAN Access Network via the Tw interface and has a Tu interface.](94acd33fcad85bb6f207a308f9b63191_img.jpg) + +``` + +graph LR + UE[UE] -- Tw --> WLAN[WLAN Access Network] + WLAN -- Ta --> TWAP[TWAP] + WLAN -- Tn --> TWA[TWA] + TWAP -- Tg --> TWA + TWAP -- STa --> AAA[3GPP AAA] + AAA -- SWx --> HSS[HSS] + TWA -- S2a --> PDN[PDN GW] + PDN -- SGi --> SGi[SGi] + subgraph TrustedNon3GPPWLAN [Trusted Non-3GPP WLAN] + WLAN + TWAP + TWA + end + subgraph 3GPPHomeNetwork [3GPP Home Network] + HSS + AAA + PDN + end + UE --- Tu + +``` + +Figure 7.1.2.1-1: Non-roaming reference model diagram. The diagram shows a UE connected to a WLAN Access Network (part of a Trusted Non-3GPP WLAN). The WLAN Access Network connects to a TWAP via the Ta interface and to a TWA via the Tn interface. The TWAP and TWA are connected via the Tg interface. The TWAP connects to the 3GPP Home Network via the STa interface, which is connected to a 3GPP AAA server. The 3GPP AAA server is connected to an HSS via the SWx interface. The TWA connects to the 3GPP Home Network via the S2a interface, which is connected to a PDN GW. The PDN GW is connected to the SGi interface. The UE is also connected to the WLAN Access Network via the Tw interface and has a Tu interface. + +Figure 7.1.2.1-1: Non-roaming reference model + +![Roaming reference model Trusted Non-3GPP WLAN Access - Home Routed](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +This diagram illustrates the 'Home Routed' roaming model for a Trusted Non-3GPP WLAN Access. On the left, a 'UE' (User Equipment) is connected to a 'WLAN Access Network' via a 'TW' (TWAP) interface. The 'WLAN Access Network' is part of a 'Trusted Non-3GPP WLAN Access' area. It connects to a 'TWAG' (TWAG) via 'Tn' and 'Tu' interfaces. The 'TWAG' is connected to a 'PDN GW' (PDN GW) via an 'S2a' interface. The 'PDN GW' is connected to the '3GPP Home Network' via an 'SGi' interface. The '3GPP Home Network' contains an 'HSS' (HSS) and a '3GPP AAA Server' (3GPP AAA Server) connected by an 'SWx' interface. The '3GPP AAA Server' is connected to a '3GPP AAA Proxy' (3GPP AAA Proxy) in the '3GPP Visited Network' via an 'SWd' interface. The '3GPP Visited Network' also contains a 'TWAP' (TWAP) connected to the 'WLAN Access Network' via a 'Ta' interface. The 'TWAP' is connected to the '3GPP AAA Proxy' via an 'STa' interface. The 'TWAG' is also connected to the '3GPP AAA Proxy' via a 'Tg' interface. + +Roaming reference model Trusted Non-3GPP WLAN Access - Home Routed + +Figure 7.1.2.1-2: Roaming reference model Trusted Non-3GPP WLAN Access - Home Routed + +![Roaming reference model Trusted Non-3GPP WLAN Access - Local Break-Out](a4b963a07cc368283154762c4b156fe7_img.jpg) + +This diagram illustrates the 'Local Break-Out' roaming model for a Trusted Non-3GPP WLAN Access. On the left, a 'UE' (User Equipment) is connected to a 'WLAN Access Network' via a 'TW' (TWAP) interface. The 'WLAN Access Network' is part of a 'Trusted Non-3GPP WLAN Access' area. It connects to a 'TWAG' (TWAG) via 'Tn' and 'Tu' interfaces. The 'TWAG' is connected to a 'PDN GW' (PDN GW) via an 'S2a' interface. The 'PDN GW' is connected to the '3GPP Visited Network' via an 'SGi' interface. The '3GPP Visited Network' contains a '3GPP AAA Proxy' (3GPP AAA Proxy) connected to the 'PDN GW' via an 'STa' interface. The '3GPP AAA Proxy' is connected to a '3GPP AAA Server' (3GPP AAA Server) in the '3GPP Home Network' via an 'SWd' interface. The '3GPP Home Network' also contains an 'HSS' (HSS) connected to the '3GPP AAA Server' by an 'SWx' interface. The 'TWAG' is also connected to the '3GPP AAA Proxy' via a 'Tg' interface. The 'TWAP' (TWAP) is connected to the 'WLAN Access Network' via a 'Ta' interface and to the '3GPP AAA Proxy' via an 'STa' interface. + +Roaming reference model Trusted Non-3GPP WLAN Access - Local Break-Out + +Figure 7.1.2.1-3: Roaming reference model Trusted Non-3GPP WLAN Access - Local Break-Out + +## 7.1.2.2 Network elements + +### 7.1.2.2.1 UE + +For the purpose of accessing a Trusted Non-3GPP WLAN Access the UE is assumed to be unmodified and has the following standard functions: + +- WLAN Access Network authentication based on EAP methods. +- Configure an IP address on the WLAN using the relevant IETF standards, depending on the specific WLAN deployment: + - For IP version 4: DHCP as per IETF RFC 2131. Optionally, Detecting Network Attachment in IPv4 (DNAv4) according to IETF RFC 4436. + - For IP version 6: Stateless Address Autoconfiguration (SLAAC) as per IETF RFC 4861 [11], and optionally stateless DHCPv6 as per IETF RFC 3736 [19]. Optionally, Detecting Network Attachment in IPv6 (DNAv6) according to IETF RFC 6059 [14]. + +### 7.1.2.2.2 Trusted WLAN AAA Proxy + +The Trusted WLAN AAA Proxy (TWAP) function includes: + +- Relaying the AAA information between the WLAN Access Network and the 3GPP AAA Server or Proxy in case of roaming. +- Establishing Binding of UE IMSI with UE MAC address on the WLAN Access Network into (IMSI, MAC) tuple via snooping on the AAA protocol carrying EAP-AKA exchange. +- Detecting L2 Attach of UE to the WLAN Access Network via snooping on the AAA protocol for EAP-Success message. +- Detecting L2 Detach of UE from the WLAN Access Network via snooping on the AAA protocol for Accounting-Request STOP message. +- Informing the Trusted WLAN Access Gateway of WLAN Attach and Detach events for UE with (MAC, IMSI) tuple. +- Protocol conversion when the Ta and STa reference points do not use the same protocol (e.g. Ta based on RADIUS) +- Transfer necessary information for suitable per-UE L2 encapsulation (e.g. 802.1Q VLAN tag or MPLS label) between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway. + +The Trusted WLAN AAA Proxy functionality can reside in a separate physical network node, it may reside in the Trusted WLAN Access Gateway or any other physical network node. + +### 7.1.2.2.3 Trusted WLAN Access Gateway + +The Trusted WLAN Access Gateway function includes: + +- For IP version 4: + - Default IPv4 Router. + - DHCP server according to IETF RFC 2131 [9]. The TWAG allocates to the UE the IPv4 address that is allocated to the UE by the PDN GW. +- For IP version 6: + - Default IPv6 Router according to IETF RFC 4861 [11]. +- Enforces routing of packets between the UE MAC address and the GTP tunnel for that UE. +- Enforce per-UE L2 encapsulation of traffic to/from the UE. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between + +the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. + +NOTE 1: There is a per-UE subnet point-to-point link and subnet between the UE and the Trusted WLAN Access Gateway that acts as the default router. This link model is the same as the one used for PMIP-based S5/S8 and differs from that of GTP-based S5/S8. + +NOTE 2: Whether multiple TNAN functions are mapped to a single non-3GPP access entity, or a single TNAN function is distributed among multiple non-3GPP access entities is out-of-scope of 3GPP. + +### 7.1.2.3 Reference Points + +#### 7.1.2.3.1 Ta reference point + +The Ta reference point applies to Trusted Non-3GPP WLAN Access. + +The Ta reference point connects the WLAN Access Network to the Trusted WLAN AAA Proxy. The prime purpose of the protocols crossing this reference point is to transport authentication, authorization and accounting related information. The reference point has to accommodate also legacy WLAN Access Networks. + +EAP authentication shall be transported over the Ta reference point. + +The functionality of the reference point is to transport AAA frames: + +- Carrying data for authentication signalling between UE and 3GPP Network; As a side effect, allowing the Trusted WLAN AAA Proxy to detect L2 attach of the UE. +- Carrying data for authorization (including the authorization information update) signalling between WLAN Access Network and 3GPP Network. +- Carrying accounting signalling per WLAN user, e.g. for charging purposes; As a side effect, allowing the Trusted WLAN AAA Proxy to detect L2 detach of the UE. +- Carrying keying data for the purpose of radio interface integrity protection and encryption; +- Informs WLAN Access Network of per-UE L2 encapsulation information to be used with the Trusted WLAN Access Gateway. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. +- Purging a user from the WLAN Access Network for immediate service termination. + +#### 7.1.2.3.2 Tg reference point + +The Tg reference point applies to Trusted Non-3GPP WLAN Access. + +The Tg reference point connects the Trusted WLAN AAA Proxy to the Trusted WLAN Access Gateway. This is a AAA interface used to: + +- Trusted WLAN AAA Proxy notify Trusted WLAN Access Gateway of WLAN attach and detach events. +- Trusted WLAN Access Gateway Informs Trusted WLAN AAA Proxy of per-UE L2 encapsulation information to be used between the WLAN Access Network and the Trusted WLAN Access Gateway. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. + +#### 7.1.2.3.3 Tn reference point + +The Tn reference point applies to Trusted Non-3GPP WLAN Access. + +The Tn reference point connects the WLAN Access Network and the Trusted WLAN Access Gateway and provides the following functionality: + +- Per-UE encapsulation between the WLAN Access Network and the Trusted WLAN Access Gateway. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. + +#### 7.1.2.3.4 Tw reference point + +The Tw reference point applies to Trusted Non-3GPP WLAN Access. + +The Tw reference point connects the UE to the WLAN Access Network per IEEE 802.11 [5] specifications. The definition of IEEE Physical and Medium Access Control layers protocols (e.g. Layer 1 and Layer 2 defined by IEEE 802.11 [5] standards) is out of the scope of 3GPP. + +The functionality of the reference point is based on IEEE 802.11 [5] specifications and it is intended to transport signalling messages including: + +- Attach and Detach request from the UE to the WLAN Access Network. +- Detach signal from the WLAN Access Network to the UE. +- Parameters for authentication signalling between the 3GPP AAA Server and the UE; +- Per-UE encapsulation of data frames between the UE and the WLAN Access Network as per IEEE 802.11 [5] specifications. + +#### 7.1.2.3.5 Tu reference point + +The Tu reference point applies to Trusted Non-3GPP WLAN Access. + +The Tu reference point represents the point-to-point link and per-UE subnet between the UE and the Trusted WLAN Access Gateway. Transport for the Tu reference point is provided by a combination of: + +- The Tw reference point provides an IEEE 802.11 association between the UE and a BSSID/ESSID in the WLAN Access Network, as per IEEE 802.11 specifications. +- The WLAN Access Network internally provides per-UE encapsulation between the BSSID/ESSID and the Tn endpoint. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. +- The Tn reference point provides per-UE encapsulation between the WLAN Access Network and the Trusted WLAN Access Gateway. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. + +#### 7.1.2.4 Procedures + +For the steps that already exist in the generic Trusted Non-3GPP Access procedure and are re-used in the Trusted Non-3GPP WLAN Access procedure, identical numbering is used, and the differences are outlined, if any. For the steps that are specific to the Trusted Non-3GPP WLAN Access procedure and do not exist in the generic Trusted Non-3GPP WLAN Access procedure, the steps are indexed with the number of the generic preceding step and a letter, and a description of the step is provided. + +#### 7.1.2.4.1 Initial Attach to Trusted Non-3GPP WLAN Access procedure + +![Sequence diagram of the Initial Attach to Trusted Non-3GPP WLAN Access procedure. The diagram shows interactions between UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, and hPCRF. The procedure includes steps: 1. WLAN Specific Procedures (dashed box), 2. EAP Authentication, 2b. WLAN Attach Request, 5. Create Session Request, 6. IP-CAN Session Establishment Procedure (dashed box), 7. Update PDN GW Address, 8. Create Session Response, 9. GTP Tunnel (highlighted), 9b. WLAN Attach Accept, 9c. EAP Success, and 11. L3 Attach Completion (dashed box).](04cfca33e3fc26513abe649d7474f733_img.jpg) + +``` + +sequenceDiagram + participant UE + participant WLAN as WLAN Access Network + participant TWAG + participant TWAP + participant PDN + participant vPCRF + participant AAA + participant hPCRF + participant HSS + + Note left of WLAN: 1. WLAN Specific Procedures + Note right of AAA: Roaming Scenarios + + UE->>WLAN: 2. EAP Authentication + WLAN->>AAA: 2. Authentication & Authorization + AAA->>HSS: + HSS-->>AAA: + AAA->>TWAG: 2b. WLAN Attach Request + TWAG->>PDN: 5. Create Session Request + Note right of PDN: 6. IP-CAN Session Establishment Procedure + PDN->>AAA: 7. Update PDN GW Address + AAA->>PDN: 8. Create Session Response + PDN->>TWAG: 9. GTP Tunnel + TWAG->>WLAN: 9b. WLAN Attach Accept + WLAN->>AAA: 9c. EAP Success + Note left of WLAN: 11. L3 Attach Completion + +``` + +Sequence diagram of the Initial Attach to Trusted Non-3GPP WLAN Access procedure. The diagram shows interactions between UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, and hPCRF. The procedure includes steps: 1. WLAN Specific Procedures (dashed box), 2. EAP Authentication, 2b. WLAN Attach Request, 5. Create Session Request, 6. IP-CAN Session Establishment Procedure (dashed box), 7. Update PDN GW Address, 8. Create Session Response, 9. GTP Tunnel (highlighted), 9b. WLAN Attach Accept, 9c. EAP Success, and 11. L3 Attach Completion (dashed box). + +**Figure 7.1.2.4.1-1: Initial attach to Trusted Non-3GPP WLAN Access** + +The procedure for Initial Attach to Trusted Non-3GPP WLAN Access is represented in Figure 7.1.2.4.1-1 and described below. It is based on the generic Initial Attach to Trusted Non-3GPP Access procedure described in clause 6.1.3.1. with the following differences: + +- At step 2, the following additions apply: + - The HSS/AAA provides to the Trusted Non-3GPP WLAN Access the APN to which the UE will be attached. in the subscription data. PDN type is indicated from HSS in this step. + - The mutual authentication between the UE and the EPC as defined in TS 23.402 [3], clause 4.9.1 is carried according to IEEE 802.11 [5] specifications through the Trusted Non-3GPP WLAN Access. + - At reception of the EAP Success, the Trusted WLAN AAA Proxy buffers it and notifies the Trusted WLAN Access Gateway of the layer 2 attach of the UE and provides MAC address and IMSI of the UE as depicted in step 2b. +- At step 5, after the Trusted WLAN AAA Proxy informs of layer 2 attach of the UE, the Trusted WLAN Access Gateway selects the APN as per the subscription data received in step 2 and send Create Session Request to the PDN GW with the PDN type. +- At step 8, After allocating an IPv6 prefix and/or an IPv4 address to the UE, the PDN GW sends Create Session Response to the Trusted WLAN Access Gateway. Deferred IPv4 address allocation may be used. +- At step 9b, the Trusted WLAN Access Gateway notifies the Trusted Non-3GPP Access AAA Proxy of successful GTP tunnel establishment, and provides the necessary parameters for establishment of a point-to-point link towards the UE through the WLAN Access Network. +- At step 9c, the Trusted WLAN AAA Proxy delivers the buffered EAP success to the WLAN Access Network together with the necessary parameters for establishment of a point-to-point link between the UE and the Trusted WLAN Access Gateway. On receiving this, the WLAN Access Network configures the point-to-point link adequately and informs the UE of EAP success. + +- At step 11, after the UE is associated and authenticated with the WLAN Access Network, the UE performs IP layer configuration with the Trusted WLAN Access Gateway acting as the default router according to standard IETF procedures [9] [12] [13] [14] [19]. + +NOTE: The WLAN Access Gateway can send unsolicited IP layer configuration signalling, e.g. DHCPv4 or RA, over the point-to-point link towards the UE. + +#### 7.1.2.4.2 UE/Trusted Non-3GPP WLAN Access Network Initiated Detach procedure + +![Sequence diagram for UE/Trusted Non-3GPP WLAN Access Network Initiated Detach procedure. The diagram shows interactions between UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box groups the vPCRF, AAA Proxy, and hPCRF. The procedure starts with a dashed box '1. UE or WLAN Access Network initiated detach'. Step 2b 'Session Termination' is a message from the WLAN Access Network to the HSS/AAA. Step 2c 'WLAN Detach Request' is from the AAA Proxy to the TWAG. Step 3 'Delete Session Request' is from the TWAG to the PDN GW. Step 4 'Update PDN GW Address' is from the PDN GW to the HSS/AAA. Step 5 is a dashed box 'PCEF-initiated IP-CAN Session Termination Procedure' between the PDN GW and the vPCRF. Step 6 'Delete Session Response' is from the PDN GW to the TWAG. Step 6b 'WLAN Detach Accept' is from the TWAG to the WLAN Access Network.](b6ad8b32179842fca5ad086cf22b03eb_img.jpg) + +Sequence diagram for UE/Trusted Non-3GPP WLAN Access Network Initiated Detach procedure. The diagram shows interactions between UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box groups the vPCRF, AAA Proxy, and hPCRF. The procedure starts with a dashed box '1. UE or WLAN Access Network initiated detach'. Step 2b 'Session Termination' is a message from the WLAN Access Network to the HSS/AAA. Step 2c 'WLAN Detach Request' is from the AAA Proxy to the TWAG. Step 3 'Delete Session Request' is from the TWAG to the PDN GW. Step 4 'Update PDN GW Address' is from the PDN GW to the HSS/AAA. Step 5 is a dashed box 'PCEF-initiated IP-CAN Session Termination Procedure' between the PDN GW and the vPCRF. Step 6 'Delete Session Response' is from the PDN GW to the TWAG. Step 6b 'WLAN Detach Accept' is from the TWAG to the WLAN Access Network. + +**Figure 7.1.2.4.2-1: UE/Trusted Non-3GPP WLAN Access Network Initiated Detach** + +The procedure for UE/Trusted Non-3GPP WLAN Access Network Initiated Detach is represented in Figure 7.1.2.4.2-1 and described below. It is based on the generic UE/Trusted Non-3GPP IP Access Network Initiated Detach procedure described in clause 6.1.3.2.1. with the following differences: + +- At step 2, the following additions apply: + - In step 2b, the UE/Trusted Non-3GPP WLAN Access Network Initiated Detach triggers AAA signalling between the WLAN Access Network and the home HSS/AAA server to terminate the session. + - Based on the AAA signalling for session termination, the Trusted WLAN AAA Proxy sends a WLAN Detach Request to the Trusted WLAN Access Gateway. +- Step 3 is initiated by the Trusted WLAN Access Gateway based on the WLAN Detach Request received from the Trusted WLAN AAA Proxy. +- At step 6, the following addition applies: + - In step 6b, the Trusted WLAN Access Gateway confirms session deletion by sending to the Trusted WLAN AAA Proxy a WLAN detach accept. + +### 7.1.2.4.3 HSS/AAA Initiated Detach procedure + +![Sequence diagram for HSS/AAA Initiated Detach procedure. Lifelines: UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. A 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF. Step 1: HSS/AAA sends a Session Termination Request to the PDN GW. Step 2: A block labeled 'The procedures as figure 7.1.2.4.2-1, Step 2c to 6b.' spans from the PDN GW to the WLAN Access Network. Step 3: The PDN GW sends a Session Termination Response to the HSS/AAA.](f5deee2f3301ee351c4008283ffafbb3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant WLAN as WLAN Access Network + participant TWAG + participant TWAP + participant PDN as PDN GW + participant vPCRF + participant AAA as AAA Proxy + participant hPCRF + participant HSS as HSS/AAA + + Note right of AAA: Roaming Scenarios + HSS->>PDN: 1. Session Termination Request + PDN->>WLAN: 2. The procedures as figure 7.1.2.4.2-1, Step 2c to 6b. + PDN->>HSS: 3. Session Termination Response + +``` + +Sequence diagram for HSS/AAA Initiated Detach procedure. Lifelines: UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. A 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF. Step 1: HSS/AAA sends a Session Termination Request to the PDN GW. Step 2: A block labeled 'The procedures as figure 7.1.2.4.2-1, Step 2c to 6b.' spans from the PDN GW to the WLAN Access Network. Step 3: The PDN GW sends a Session Termination Response to the HSS/AAA. + +Figure 7.1.2.4.3-1: HSS/AAA Initiated Detach + +The procedure for HSS/AAA Initiated Detach from Trusted Non-3GPP WLAN Access Network is represented in Figure 7.1.2.4.3-1 and described below. As for the UE/Trusted Non-3GPP WLAN Access Network Initiated Detach, it is based on the generic HSS/AAA Initiated Detach procedure described in clause 6.1.3.2.2 with the following differences: + +- At step 2, the step 2c to 6b of the UE/Trusted Non-3GPP WLAN Access Network Initiated Detach procedure described in clause 7.1.2.4.2 are followed. + +### 7.1.2.4.4 Other procedures + +Other procedures defined for the generic Trusted Non-3GPP IP Access refer to clause 7.1.1.3 descriptions. + +## 7.1.3 Handovers with or without TNSP/TWAG relocation with unmodified UEs + +No specific mechanisms are defined to support AP-to-AP handover with and without TNSP/TWAG relocation. However, this does not preclude the support of IP address preservation in handovers without TNSP/TWAG relocation when supported by procedures out of 3GPP scope. + +# 8 Additional considerations for WLAN access to EPC through S2a for Phase 2 + +**Editor's Note:** Phase 2 of the study is aiming at studying enhancements to the Rel-11 solution to avoid those limitations (except emergency attach). In this phase it is expected that there will be some impacts to the UE. + +## 8.1 Requirements + +**Editor's Note:** This sub-clause will contain the requirement(s) related to SaMOG Phase 2 study. + +The solutions shall comply with the following Requirements: + +- The SaMOG phase 2 solution (e.g. possibly with impact to the UE) shall be able to co-exist with the SaMOG Release 11 solution. + +The solutions shall comply with one or more of the following requirements: + +- For a UE, multiple simultaneous PDN connections over Trusted WLAN are supported, including the support for establishment of concurrent PDN Connections via 3GPP access and over WLAN. +- For a UE, PDN Connectivity to EPC over Trusted WLAN concurrent with non-seamless WLAN offload is supported. +- The UE is capable of IP address preservation in case of mobility between a 3GPP access and a Trusted WLAN. The UE is capable to request IP address preservation per PDN connection in case of mobility between a 3GPP access and a Trusted WLAN. +- The UE is capable of signalling the requested APN over Trusted WLAN, and the UE is capable of receiving the selected APN over Trusted WLAN (e.g. in case the UE did not indicate an APN). +- The UE is capable of indicating whether it requests a PDN connection or a NSWO connectivity service over Trusted WLAN, and the UE is capable of receiving an indication of whether the granted service is a PDN connection or NSWO connectivity (e.g. in case the UE did not indicate the kind of service it was requesting). A solution may also enable NSWO connectivity establishment only as the first connection. It is not required to release the NSWO connection without releasing the other connections. +- The solution should minimize the UE functional changes. + +## 8.1A Key issues + +- Regarding the feature of handover with IP address preservation. S2a already supports the hand-over indication that can be used by the TWAG to tell the PGW that the IP address is to be preserved. A solution is needed to enable the UE to provide to the TWAN an indication of whether the access to the TWAN corresponds to a “handover” (with IP address preservation) or “initial attach”. +- Regarding the feature of connecting to a non-default APN. Also here, S2a already supports this. The TWAN will also get all relevant APN profile information for this UE from the 3GPP AAA/HSS as part of the STa authentication and authorization process. A solution is needed to enable the UE to explicitly indicate which APN to connect to, and for the UE to be informed about the APN that the TWAN connected the UE to. +- Regarding the feature of the UE choosing between access to EPC and NSWO. Also here, the TWAN will also get all relevant APN profile information for this UE from the 3GPP AAA/HSS as part of the STa authentication and authorization process. A solution is needed for enabling the UE to indicate to the network whether an IP session is requested for EPC access or for non-seamless WLAN offload, and the network to respond whether the access request has been granted. +- Regarding the feature of the UE requesting a connection to an additional PDN. Also here, a solution is needed for the UE to request an additional PDN connection. Besides this, additional logic may be needed to correlate an individual user plane IP packet to an individual PDN connection. The solution shall take into account all situations and in particular when: + - 1) Two or more PDN connections from one UE might have the same IP address. This is in particular possible if these PDN connections are towards different PDN(s) using IPv4 private addressing. + - 2) Downlink (link layer) broadcasts do not include a specific UE target IP address (associated with a PDN connection). + - 3) Downlink IP multicast does not include a specific UE target IP address, and the sources of multicast services would have also the same IPv4 private address. + +The UE, the TWAG and/or the link between them, may need to implement means to cope with these situations. + +- Regarding the support for the same UE of simultaneous access to EPC through S2a and of non-seamless offload, similar considerations than for the support of simultaneous PDN connections apply. + +## 8.2 Solutions + +*Editor's Note: This clause will describe the solution(s) for SaMOG Phase 2 study.* + +### 8.2.1 Solution 1: Tunnelled approach with dedicated UE-TWAG control protocol + +#### 8.2.1.1 Functional Description + +*Editor's Note: It should be described whether and how the solution fulfils the requirements in subclause 8.1.* + +##### 8.2.1.1.1 Overview + +This solution uses a two-scenario approach to support handover, non-default APN and multiple PDN connections: + +1. Single-connection scenario: In this scenario, the network or the UE only supports a single IP connection over WLAN. An IP connection is either a PDN connection or a NSWO connection. EAP signaling between UE and network is enhanced to carry attach parameters (e.g. handover indicator or APN or a request for NSWO). +2. Multi-connection scenario: In this scenario, the network and the UE both support multiple connections over WLAN. In the multi-connection scenario, a signaling protocol to manage PDN connections is needed. Also, a user-plane separation mechanism is needed to separate user-plane traffic between the different active PDN connections. A NSWO IP address or prefix is obtained through standard IETF procedures (i.e. DHCP or IPv6 Stateless Address Auto-configuration). + +Negotiation of which scenario to choose is done once as part of the attachment EAP signaling between UE and network. + +##### 8.2.1.1.2 User plane + +In the single-connection scenario, the PDN connection over WLAN uses the per-UE point-to-point link as defined in TS 23.402 clause 16. Such point-to-point link carries MAC frames. The MAC frame would typically carry an IP packet. IP is indicated by means of the “EtherType” field in the MAC header as defined in IEEE 802.1 (e.g. IPv4 is indicated by the Ethertype 0x0800). + +![](1dbb1d90b2022a3a765c85929a515cc6_img.jpg) + +| | | | +|-----|----|---------| +| MAC | IP | payload | +|-----|----|---------| + +**Figure 8.2.1.1.2-1 Frame format for the single-connection scenario** + +For the multi-connection scenario, there is at most one NSWO connection. For all PDN connections over WLAN, an additional layer between MAC and IP is used when carrying IP packets belonging to these connections. The MAC “Ethertype” field would in this case instead indicate “XYZ”, where “XYZ” is an identifier for the protocol that is used to include: 1) A key to differentiate the PDN connections from each other; 2) A next header indicator, which will be typically IP. The key is unique within the scope of a single UE. The key combined with the MAC address of the UE provides a globally unique identification for a PDN connection. The TWAG and the UE can use this identification to correlate a packet to the correct PDN connection. In the following two subsections, two alternatives are proposed for “XYZ”. + +*Editor's Notes: One of these two alternatives needs to be chosen. Which one is still FFS.* + +![](265d5cb06b401cf460a20fd2c93fd6d5_img.jpg) + +| | | | | +|-----|-------|----|---------| +| MAC | “XYZ” | IP | Payload | +|-----|-------|----|---------| + +**Figure 8.2.1.1.2-2 Frame format for PDN connections in the multi-connection scenario** + +##### 8.2.1.1.2.1 Alternative 1: XYZ = GRE + +In this alternative, XYZ is the GRE header as defined in IETF RFC 2890. The GRE key is used to differentiate the PDN connections from each other. This requires that GRE is defined by IEEE as new EtherType. + +As the access point is functioning like a layer-2 bridge, it forwards frames between its WiFi interface and its wired interface without checking the EtherType value. If the access point implements a mapping between IEEE 802.11e priorities and DSCP, then the DSCP will be found on a different offset for frames with EtherType GRE compared to frames with EtherType IPv4 or IPv6. + +#### 8.2.1.1.1.2.2 Alternative 2: XYZ = VLAN + +In this alternative, XYZ is an extension of the MAC header, forming a VLAN-tagged MAC header. The VLAN ID is used as key to differentiate the PDN connections from each other. + +The AP performs translation between the IEEE Std 802.11 air link and the IEEE 802 AP-TWAG segment e.g. using IEEE 802.11 integration service per IEEE 802.11-2007 appendix M. The solution relies on the VLAN ID to be carried un-modified to the TWAG. + +The VLAN ID used to distinguish PDN connections is encapsulated over the air in LLC SNAP and thus cannot be used for any other (non-3GPP) service differentiation over the air. + +As described in TS 23.402 clause 16, the WLAN AN enforces upstream and downstream forced-forwarding between the UE's WLAN IEEE 802.11 association and the TWAG. The way this forced-forwarding is enforced ensures that the VLAN ID used to multiplex TWAN connectivity services is in a different protocol stack layer than VLAN ID potentially used on the transport interface between the UE and the TWAG. + +The VLAN ID used to multiplex TWAN connectivity services is not used to route traffic on the path between the AP and the TWAG. + +If the access point implements a mapping between IEEE 802.11e priorities and DSCP, then the DSCP will be found on a different offset for VLAN-tagged frames compared to frames without VLAN tagging. + +#### 8.2.1.1.3 Control plane + +A UE-TWAG protocol is needed to control (i.e. setup and teardown) the per-PDN point-to-point link. This protocol is denoted as TSM (TWAN Session Management). TSM is a new protocol defined by 3GPP. The functions that WLCP supports include: Establishment of a per-UE-and-PDN point-to-point link; Tear down of a per-UE-and-PDN point-to-point link. + +As described in clause 8.2.1.1.1, a User Plane Connection ID (GRE key or VLAN ID) value is needed to differentiate PDN connections. When establishing a new per-UE-and-PDN point-to-point link using TSM, the network decides upon this User Plane Connection ID value and returns it to the UE. + +In the following two subsections, two alternatives to support the control protocol are proposed. + +**Editor's Notes: One of these two alternatives needs to be chosen. Which one is still FFS.** + +##### 8.2.1.1.3.1 Alternative 1: L2.5-based control protocol + +In this alternative, the following frame format is used for control plane messages. + +![](142bb586c6d72f1be78c75cea40ff7de_img.jpg) + +| | | | +|-----|-------|---------| +| MAC | "XYZ" | Payload | +|-----|-------|---------| + +**Figure 8.2.1.1.3.1-1 Frame format for PDN** + +##### **for L2.5-based control protocol** + +Just as for the user plane frames, the EtherType in MAC is set to "XYZ" (i.e. GRE or VLAN). As described in section 8.2.1.1.2, "XYZ" contains both a next header field (i.e. EtherType) and a key field (i.e. GRE key or VLAN ID). The EtherType field in "XYZ" is set to a new value for control plane signalling. It is required that IEEE defines such new value. The key field is set to a dedicated value. The payload contains the control protocol message. + +Alternatively, the EtherType in MAC is not set to "XYZ" but to a new value for control plane signalling. The "XYZ" part of the frame can then be omitted for control signalling. In that case, the frame for the control protocol would be as follows. + +![](32ff77da4286b58c4778033acaa10836_img.jpg) + +| | | +|-----|---------| +| MAC | Payload | +|-----|---------| + +Figure 8.2.1.1.3.1-2 Alternative frame format for PDN for + +### L2.5-based control protocol + +Editor's Notes: One of these two alternatives needs to be chosen. Which one is still FFS. + +If the UE is unaware of the TWAG MAC address, the first TSM message is sent in MAC broadcast to the TWAG. From the TWAG reply, the UE learns the TWAG MAC address. Alternatively, the TWAG MAC address is sent to the UE as part of the EAP-AKA' signalling. + +Editor's Notes: One of these two alternatives needs to be chosen. Which one is still FFS. + +### 8.2.1.1.3.2 Alternative 2: L3-based control protocol + +In this alternative, the following frame format is used for control plane messages. + +![](c79b9212cfc136d4191e637cd9437ffb_img.jpg) + +| | | | | +|-----|----|------------|---------| +| MAC | IP | TCP or UDP | Payload | +|-----|----|------------|---------| + +Figure 8.2.1.1.3.2-1 + +### Frame format for PDN for L3-based control protocol + +The payload contains the control protocol message. The IP address used is either the NSWO address, or a link-local address in case NSWO is not possible. A dedicated TCP or UDP port is used for control plane signalling. + +Editor's Notes: It is FFS if TCP or UDP is to be used. + +If the UE is unaware of the TWAG MAC address, the first TSM message is sent in MAC broadcast to the TWAG. If the UE is unaware of the TWAG IP address, the first TSM message is sent in IPv4 broadcast / IPv6 multicast to the TWAG. From the TWAG reply, the UE learns the TWAG MAC and IP address. Alternatively, the TWAG MAC and IP address is sent to the UE as part of the EAP-AKA' signalling. + +Editor's Notes: One of these two alternatives needs to be chosen. Which one is still FFS. + +## 8.2.1.1.4 Protocol Stacks + +Editor's Notes: Impact on link model due to handover support is FFS. + +## 8.2.1.2 Procedures + +### 8.2.1.2.1 Initial Attach in WLAN on S2a + +![Sequence diagram for Initial Attach in WLAN on S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with '1. Non-3GPP Specific Procedures' between UE and TWAN, followed by '2. EAP Authentication' between UE and TWAN. A large arrow labeled '2. Authentication & Authorization' spans from the UE/TWAN pair to the HSS/AAA, passing through the PDN GW and a 'Roaming Scenarios' box containing vPCRF, AAA Proxy, and hPCRF.](1cd762800fb629a48ed907cf73d794f4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note left of UE: 1. Non-3GPP Specific Procedures + UE->>TWAN: 2. EAP Authentication + Note right of TWAN: 2. Authentication & Authorization + TWAN->>PDN_GW: + PDN_GW->>vPCRF: + vPCRF->>AAA_Proxy: + AAA_Proxy->>hPCRF: + hPCRF->>HSS_AAA: + HSS_AAA-->>PDN_GW: + PDN_GW-->>TWAN: + TWAN-->>UE: + +``` + +Sequence diagram for Initial Attach in WLAN on S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with '1. Non-3GPP Specific Procedures' between UE and TWAN, followed by '2. EAP Authentication' between UE and TWAN. A large arrow labeled '2. Authentication & Authorization' spans from the UE/TWAN pair to the HSS/AAA, passing through the PDN GW and a 'Roaming Scenarios' box containing vPCRF, AAA Proxy, and hPCRF. + +Figure 8.2.1.2.1.1-1: Initial attachment in WLAN on GTP S2a for roaming and non-roaming scenarios + +The procedure is as TS 23.402 clause 16.2.1 with the following additions: + +- Step 2. As part of this step, the UE shall send an indication to the network whether it supports single-connection or multi-connection or both. If the UE supports the single-connection scenario, the UE also indicates whether it requests EPC access or non-seamless WLAN offload. If the UE requests EPC access, it may indicate APN. + +These indicators are sent in EAP-AKA to the 3GPP AAA. The 3GPP AAA sends these indicators to the TWAN. Depending on the capabilities of the network and the request of the UE, the network informs the UE as part of step 2 whether the single-connection scenario or the multi-connection scenario is selected. If both network and UE support both single-connection and multi-connection, then the network selects the multi-connection scenario. + +In case the single-connection scenario is selected, the procedure continues as described in clause 8.2.1.2.2. In case the multi-connection scenario is selected, the procedure continues as described in clause 8.2.1.2.3. + +#### 8.2.1.2.2 Initial Attach in single-connection scenario in WLAN on S2a (continuation) + +##### 8.2.1.2.2.1 Initial Attach in single-connection scenario in WLAN on GTP S2a (continuation) + +![Sequence diagram for Initial Attach in single-connection scenario in WLAN on GTP S2a for roaming and non-roaming scenarios. The diagram shows two scenarios, (A) and (B), involving the UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Scenario (A) is for non-roaming and Scenario (B) is for roaming. Both scenarios follow Step 1-2 from clause 8.2.1.2.1. In (A), the TWAN sends a Create Session Request to the PDN GW, which initiates the IP-CAN Session Establishment Procedure with the vPCRF and HSS/AAA, resulting in an Update PDN GW Address to the AAA Proxy and a Create Session Response back to the TWAN, which then establishes a GTP Tunnel with the UE. This is followed by EAP authentication completion and L3 Attach. In (B), the process is similar but includes an additional step for the AAA Proxy to send an Update PDN GW Address to the hPCRF. The diagram concludes with L3 Attach Completion for both scenarios.](9edb407536d4d4d4a6ac391527af047c_img.jpg) + +The diagram illustrates the sequence of messages for the initial attachment in a single-connection scenario in WLAN on GTP S2a. It is divided into two parts: (A) for non-roaming and (B) for roaming. Both parts start with 'Step 1-2 as in clause 8.2.1.2.1'. In part (A), the TWAN sends a '3. Create Session Request' to the PDN GW. The PDN GW then initiates the '4. IP-CAN Session Establishment Procedure' with the vPCRF and HSS/AAA. The vPCRF sends an '5. Update PDN GW Address' to the AAA Proxy. The HSS/AAA sends a '6. Create Session Response' back to the PDN GW. The PDN GW then establishes a '7. GTP Tunnel' with the TWAN. The TWAN sends an '8. EAP authentication Completion' to the UE, followed by a '9. L3 Attach'. In part (B), the TWAN sends a '10. Create Session Request' to the PDN GW. The PDN GW initiates the '11. IP-CAN Session Establishment Procedure' with the vPCRF and HSS/AAA. The vPCRF sends an '12. Update PDN GW Address' to the AAA Proxy, which then sends an 'Update PDN GW Address' to the hPCRF. The HSS/AAA sends a '13. Create Session Response' back to the PDN GW. The PDN GW then establishes a '14. GTP Tunnel' with the TWAN. The TWAN sends a '15. L3 Attach Completion' to the UE. + +Sequence diagram for Initial Attach in single-connection scenario in WLAN on GTP S2a for roaming and non-roaming scenarios. The diagram shows two scenarios, (A) and (B), involving the UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Scenario (A) is for non-roaming and Scenario (B) is for roaming. Both scenarios follow Step 1-2 from clause 8.2.1.2.1. In (A), the TWAN sends a Create Session Request to the PDN GW, which initiates the IP-CAN Session Establishment Procedure with the vPCRF and HSS/AAA, resulting in an Update PDN GW Address to the AAA Proxy and a Create Session Response back to the TWAN, which then establishes a GTP Tunnel with the UE. This is followed by EAP authentication completion and L3 Attach. In (B), the process is similar but includes an additional step for the AAA Proxy to send an Update PDN GW Address to the hPCRF. The diagram concludes with L3 Attach Completion for both scenarios. + +**Figure 8.2.1.2.2.1-1: Initial attachment in single-connection scenario in WLAN on GTP S2a for roaming and non-roaming scenarios** + +The procedure continues from step 2 in clause 8.2.1.2.1: + +- Step 2. As part of this step, the UE is made aware of the network support of SAMOG phase 2 features and if the requested connectivity feature (attach to non-default APN, non-seamless WLAN offload, EPC-routed traffic) is accepted by the network. Also, if the UE requested EPC access without indicating APN, then the network indicates the selected (default) APN. If the UE requested EPC access and indicated an APN, then the network verifies that it is allowed by subscription. If the UE requested NSWO and it was accepted by the network, steps + +3-7 and 10-14 are skipped. If the requested connectivity feature is not possible, the request is rejected with a relevant authorization failure. + +- Step 3 and step 10. The TWAN selects the PDN GW for the APN, and includes the APN in the Create Session Request. The APN is determined by the TWAN based on the UE request and on the subscription data received from the AAA server. + +NOTE: In the single-connection scenario, if a UE using NSWO wants to establish a PDN Connection, or if the UE has a PDN Connection but wants to use NSWO, the UE needs to detach from TWAN and make a new Initial Attach. + +#### 8.2.1.2.2.2 Initial Attach in single-connection scenario in WLAN on PMIP S2a (continuation) + +**Editor's Notes: This procedure is still to be added.** + +#### 8.2.1.2.3 Initial Attach in multi-connection scenario in WLAN on S2a (continuation) + +![Sequence diagram for Initial Attach in multi-connection scenario in WLAN on S2a (continuation). The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF. The sequence starts with 'Steps 1-2 as in clause 8.2.1.2.1', followed by '8. EAP authentication Completion', '9. L3 Attach', and '15. L3 Attach Completion'. A dashed box at the bottom indicates '16. Procedure "UE-Initiated Connectivity to PDN in WLAN on S2a" in clause 8.2.x.2.41'.](9dc9f41d7d76c1add4b190d348cb1533_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note over UE, TWAN: Steps 1-2 as in clause 8.2.1.2.1 + UE->>TWAN: 8. EAP authentication Completion + TWAN->>PDN_GW: 9. L3 Attach + PDN_GW->>TWAN: 15. L3 Attach Completion + Note over UE, TWAN: 16. Procedure "UE-Initiated Connectivity to PDN in WLAN on S2a" in clause 8.2.x.2.41 + +``` + +Sequence diagram for Initial Attach in multi-connection scenario in WLAN on S2a (continuation). The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF. The sequence starts with 'Steps 1-2 as in clause 8.2.1.2.1', followed by '8. EAP authentication Completion', '9. L3 Attach', and '15. L3 Attach Completion'. A dashed box at the bottom indicates '16. Procedure "UE-Initiated Connectivity to PDN in WLAN on S2a" in clause 8.2.x.2.41'. + +**Figure 8.2.1.2.3-1: Initial attachment in multi-connection scenario in WLAN on GTP S2a for roaming, and non-roaming scenarios** + +The procedure continues from step 2 in clause 8.2.1.2.1: + +- Step 2. As part of this step, the UE is made aware of the network support of SAMOG phase 2 features. Non-seamless WLAN offload is possible if the network supports this and the UE is entitled to use this. As part of step 2, the UE is made aware whether or not non-seamless WLAN offload is possible. If non-seamless WLAN offload is possible, then the UE receives the address or prefix of the non-seamless WLAN offload connection as part of steps 9 and 15. If non-seamless WLAN offload is not possible, and the control protocol is L2.5-based, then step 9 and 15 are not performed. If non-seamless WLAN offload is not possible, and the control protocol is L3-based, then step 9 is not performed and in step 15 only a link-local IP address is configured. +- Step 16. The procedure “UE-Initiated Connectivity to PDN in WLAN on S2a” in clause 8.2.1.2.4 may be performed to establish a PDN connection. + +After the attach procedure, the UE has at least one IP connection (either a NSWO connection or a PDN connection). + +#### 8.2.1.2.4 UE-Initiated Connectivity to PDN in WLAN on S2a + +##### 8.2.1.2.4.1 UE-Initiated Connectivity to PDN in WLAN on GTP S2a + +This procedure can only be performed if the multi-connection scenario was selected during authentication. + +This procedure is used when the UE has previously attached to WLAN and the UE wishes to establish one or more PDN connections over WLAN. This procedure is also used when the UE already has one or more PDN connections over WLAN and wishes to establish one or more additional PDN connections over WLAN. This procedure is also used to request for connectivity to an additional PDN connection over WLAN when the UE is simultaneously connected to + +WLAN and a 3GPP access, and the UE already has active PDN connections over both the accesses. The UE establishes a separate point-to-point link to the TWAG for each PDN connection. + +There can be more than one PDN connection per APN when GTP is used between the TWAN and the PDN GW. During the establishment of a new PDN connection, the TWAN allocates and sends a default S2a bearer ID to the PDN GW. The default S2a bearer ID is unique in the scope of the UE within a TWAG, i.e. the IMSI and the default S2a bearer ID together identify a PDN connection within a TWAG. In order to be able to identify a specific established PDN connection, both the TWAG and the PDN GW shall store the default S2a bearer ID. + +NOTE: The establishment of a connection to a PDN connection does not impact the NSWO connection if that was previously setup. As a separate point-to-point link is used for each PDN connection, traffic separation can be achieved between all connections including the NSWO connection. + +![Sequence diagram illustrating UE-Initiated Connectivity to PDN in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW 1, PDN GW 2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It details the steps for establishing a new PDN connection while maintaining an existing one.](683f755e8456c884716de4fce48c7e63_img.jpg) + +The sequence diagram illustrates the following steps for UE-Initiated Connectivity to PDN in WLAN on GTP S2a: + +- The UE sends a "1. Establishment new per-UE-and-PDN point-to-point link Request" to the TWAN. +- The TWAN sends a "2. Create Session Request" to PDN GW 2. +- PDN GW 2 initiates the "3. IP-CAN Session Establishment Procedure" (indicated by a dashed box). +- PDN GW 2 sends an "4. Update PDN GW Address" message to the AAA Proxy. +- The AAA Proxy sends a "5. Create Session Response" back to the TWAN. +- A "6. GTP Tunnel" is established between the TWAN and PDN GW 2 (highlighted in green). +- The TWAN sends a "7. Establishment new per-UE-and-PDN point-to-point link Response" to the UE. +- The UE performs an "8. L3 Attach" to the TWAN. +- The UE receives a "9. L3 Attach Completion" from the TWAN. + +The diagram also shows the state of PDN connections: + +- An "Existing PDN connection" is shown between the UE and PDN GW 1 at the top. +- Another "Existing PDN connection" is shown between the UE and PDN GW 1 after step 9. +- A "New PDN connection" is established between the UE and PDN GW 2 after step 9. + +Sequence diagram illustrating UE-Initiated Connectivity to PDN in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW 1, PDN GW 2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It details the steps for establishing a new PDN connection while maintaining an existing one. + +**Figure 8.2.1.4.2.1-1: UE-Initiated Connectivity to PDN in WLAN on GTP S2a** + +- Step 1. The UE triggers the establishment of a new per-UE-and-PDN point-to-point link by means of TSM. This step establishes the setup of a new per-UE-and-PDN-connection point-to-point link to the TWAG. The UE may indicate the requested APN. The UE triggers the re-establishment of an existing PDN connectivity by providing a handover indicator. In that case, it shall provide an APN. +- Step 2-6. Same as step 3-7 in clause 8.2.1.2.2.1. As part of these steps, the TWAN verifies that the APN requested by the UE is allowed by subscription. Upon handover, the TWAN selects the PDN GW handling this PDN connection; otherwise, the TWAN performs PDN GW selection as described in TS 23.402. Steps 2-6 are executed with the selected PDN GW. +- Step 7. By means of TSM, the TWAN returns a response to the establishment of a new per-UE-and-PDN point-to-point link. This response contains a User Plane Connection ID. If the UE did not indicate the APN in the request, then the response indicates the selected default APN. If the UE does not receive an IPv4 address in this step, it may negotiate the IPv4 address with DHCPv4 in step 8, + +- Step 8. As step 9 in clause 8.2.1.2.2.1. +- Step 9. As step 15 in clause 8.2.1.2.2.1. + +#### 8.2.1.2.4.2 UE-Initiated Connectivity to PDN in WLAN on PMIP S2a + +**Editor's Notes: This procedure is still to be added.** + +#### 8.2.1.2.5 Handover procedure in single-connection scenario from 3GPP access to WLAN on S2a + +##### 8.2.1.2.5.1 Handover in single-connection scenario from 3GPP access to WLAN on GTP S2a + +This procedure is used in the single-connection scenario to hand over a single PDN Connection from 3GPP access to WLAN. The decision to use the single-connection scenario is made during authentication as described in clause 8.2.1.2.1. + +![Sequence diagram for Handover procedure in single-connection scenario from 3GPP access to WLAN on GTP S2a.](94d3fdcc244924326f02533aeb2d93fc_img.jpg) + +The sequence diagram illustrates the handover procedure from 3GPP access to WLAN on GTP S2a. The participants are UE, TWAN, S-GW, PDN GW, and a 'Roaming Scenarios' group containing vPCRF, AAA Proxy, hPCRF, and HSS/AAA. + +The flow is as follows: + +- 0. GTP/PMIPv6 tunnel exists between S-GW and PDN GW. +- 1. Non-3GPP Specific Procedures between UE and TWAN. +- 2. EAP Authentication between UE and HSS/AAA via TWAN and AAA Proxy. +- Section (A):** + - 3. Create Session Request from TWAN to PDN GW. + - 4. PCEF-initiated IP-CAN Session Modification Procedure between PDN GW and hPCRF (via vPCRF). + - 5. Update PDN GW Address between PDN GW and HSS/AAA. + - 6. Create Session Response from PDN GW to TWAN. + - 7. GTP Tunnel established between TWAN and PDN GW. +- 8. EAP authentication Completion between UE and TWAN. +- 9. L3 Attach (dashed box) between UE and TWAN. +- Section (B):** + - 10. Create Session Request from TWAN to PDN GW. + - 11. PCEF-initiated IP-CAN Session Modification Procedure between PDN GW and hPCRF (via vPCRF). + - 12. Update PDN GW Address between PDN GW and HSS/AAA. + - 13. Create Session Response from PDN GW to TWAN. + - 14. GTP Tunnel established between TWAN and PDN GW. +- 15. L3 Attach Completion between UE and TWAN. +- 16. 3GPP EPS bearer release between UE/TWAN and S-GW/PDN GW. + +Sequence diagram for Handover procedure in single-connection scenario from 3GPP access to WLAN on GTP S2a. + +### **Figure 8.2.1.2.5.1-1: Handover in single-connection scenario from 3GPP access to Trusted WLAN on GTP S2a for roaming and non-roaming scenarios** + +The home routed roaming, LBO and non-roaming scenarios are depicted in the figure 8.2.1.2.5.1-1: + +- In the LBO case, the 3GPP AAA Proxy acts as an intermediary, forwarding messages from the 3GPP AAA Server in the HPLMN to the PDN GW in the VPLMN and vice versa. Messages between the PDN GW in the VPLMN and the hPCRF in the HPLMN are forwarded by the vPCRF in the VPLMN. +- In the home routed roaming and non-roaming cases, the vPCRF and the 3GPP AAA Proxy are not involved, except for the authentication and authorization in step 2. + +The steps in figure 8.2.1.2.5.1-1 are based on figure 8.2.1.2.2.1-1, with the following changes: + +- Step 0. The UE is connected in the 3GPP Access and has a PMIPv6 or GTP tunnel on the S5/S8 interface. +- Step 2. As step 2 in 8.2.1.2.1.1 with the following addition: If the UE supports single-connection, then the UE indicates handover via EAP-AKA to 3GPP AAA. +- Step 3 and 10. As step 3 and 10 in 8.2.1.2.2.1 with the following addition: The handover indication is set in the Create Session Request to allow the PDN GW to re-allocate the same IP address or prefix that was assigned to the UE while it was connected to the 3GPP access and to initiate a PCEF-Initiated IP CAN Session Modification Procedure with the PCRF. +- Step 4 and 11. The PDN GW executes a PCEF-Initiated IP-CAN Session Modification Procedure with the PCRF as specified in TS 23.203 [4]. The Event Report indicates the change in Access Type. + +If the PDN GW decides to allocate a new IP address/prefix instead of preserving the old IP address/prefix, as described in TS 23.402 clause 4.1.3.2.3, the PDN GW executes an IP-CAN session Establishment Procedure with the PCRF instead of a PCEF-Initiated IP-CAN Session Modification Procedure. + +- Step 6 and 13. The PDN GW responds with a Create Session Response (PDN GW Address for the user plane, PDN GW TEID of the user plane, PDN GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, Charging ID, Cause). The Create Session Response contains the IP address and/or the prefix that was assigned to the UE while it was connected to the 3GPP IP access. The Charging Id provided by the PGW is the Charging Id previously assigned to the default bearer of the PDN connection in the 3GPP access. +- Step 16. The PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure in 3GPP access as defined in TS 23.402 clause 5.6.2.2 or the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401 [xx], clause 5.4.4.1. + +#### **8.2.1.2.5.2 Handover in single-connection scenario from 3GPP access to WLAN on PMIP S2a** + +**Editor's Notes: This procedure is still to be added.** + +#### **8.2.1.2.6 Handover procedure in multi-connection scenario from 3GPP access to WLAN on S2a** + +##### **8.2.1.2.6.1 Handover in multi-connection scenario from 3GPP access to WLAN on GTP S2a** + +This procedure is used in the multi-connection scenario to hand over a one or more PDN Connection from 3GPP access to WLAN. The decision to use the multi-connection scenario is made during authentication as described in clause 8.2.1.2.1. + +![Sequence diagram for handover from 3GPP access to Trusted WLAN on GTP S2a for roaming and non-roaming scenarios. The diagram shows interactions between UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, and hPCRF. Step 0 shows a GTP/PMIPv6 tunnel between S-GW and PDN GW. Steps 1-15 are grouped for non-roaming, while step 16 is for UE-initiated connectivity. Step 17 shows 3GPP EPS bearer release for both scenarios.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +The diagram illustrates the sequence of messages for a handover from 3GPP access to a Trusted WLAN using GTP S2a. The participants are UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded region labeled 'Roaming Scenarios' encompasses the vPCRF, AAA Proxy, and hPCRF. The sequence starts with Step 0, where a GTP/PMIPv6 tunnel is established between the S-GW and PDN GW. Steps 1 through 15 are specific to non-roaming scenarios and include Non-3GPP Specific Procedures, EAP Authentication, EAP authentication Completion, L3 Attach, and L3 Attach Completion. Step 16, UE-initiated Connectivity to PDN, is shown with dashed lines. Step 17, 3GPP EPS bearer release, is performed in both roaming and non-roaming scenarios. + +Sequence diagram for handover from 3GPP access to Trusted WLAN on GTP S2a for roaming and non-roaming scenarios. The diagram shows interactions between UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, and hPCRF. Step 0 shows a GTP/PMIPv6 tunnel between S-GW and PDN GW. Steps 1-15 are grouped for non-roaming, while step 16 is for UE-initiated connectivity. Step 17 shows 3GPP EPS bearer release for both scenarios. + +**Figure 8.2.1.2.6.1-1: Handover from 3GPP access to Trusted WLAN on GTP S2a for roaming and non-roaming scenarios** + +The home routed roaming, LBO and non-roaming scenarios are depicted in the figure 8.2.1.2.6.1-1: + +- In the LBO case, the 3GPP AAA Proxy acts as an intermediary, forwarding messages from the 3GPP AAA Server in the HPLMN to the PDN GW in the VPLMN and vice versa. Messages between the PDN GW in the VPLMN and the hPCRF in the HPLMN are forwarded by the vPCRF in the VPLMN. +- In the home routed roaming and non-roaming cases, the vPCRF and the 3GPP AAA Proxy are not involved, except for the authentication and authorization in step 2. + +If the UE is connected to both 3GPP access and non-3GPP access before the handover of PDN connections to non-3GPP access is triggered, steps 1 to 15 shall be skipped and the UE shall only perform step 16 for each PDN connection that is being transferred from 3GPP access. + +If the UE is connected only to 3GPP access before the handover of PDN connections to non-3GPP access is triggered, steps 2 to 15 shall be performed. As described in clause 8.2.1.2.3, these steps result in the UE receiving the address or prefix of the non-seamless WLAN offload connection, if supported by the network for this UE. The UE shall then perform step 16 for each PDN connection that is being transferred from 3GPP access. + +Step 17 shall be repeated for each PDN connection that is being transferred from 3GPP access. Step 16 can occur in parallel for each PDN. Other aspects related to the handover for multiple PDNs are described in TS 23.402 clause 8.1. + +The steps in figure 8.2.1.2.6.1-1 are based on figure 8.2.1.2.3-1, with the following changes: + +- Step 0. The UE is connected in the 3GPP Access and has a PMIPv6 or GTP tunnel on the S5/S8 interface. +- Step 2. As step 2 in 8.2.1.2.1 with the following addition: The UE indicates handover via EAP to 3GPP AAA. + +- Step 16. For connectivity to multiple PDN connections, the UE establishes connectivity to each PDN that is being transferred from 3GPP access, by executing the UE-initiated Connectivity to PDN procedure specified in clause 8.2.1.2.4. +- Step 17. The PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure in 3GPP access as defined in TS 23.402 clause 5.6.2.2 or the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401 [6], clause 5.4.4.1. + +#### 8.2.1.2.6.2 Handover from 3GPP access to WLAN on PMIP S2a + +**Editor's Notes: This procedure is still to be added.** + +## 8.2.1.2.7 + +## Handover procedure from WLAN on S2a to 3GPP access + +![Sequence diagram of handover procedure from Trusted WLAN on S2a to 3GPP access. It shows 18 steps involving UE, ePDG, E-UTRAN, MME, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. The diagram is split into two scenarios: (A) Roaming and (B) Non-Roaming.](aeb2a26a07219661191294dba528067a_img.jpg) + +Sequence diagram illustrating the Handover procedure from Trusted WLAN on S2a to 3GPP access for roaming and non-roaming scenarios. + +Participants: UE, Trusted Non-3GPP IP Access/ePDG, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, HSS/AAA. + +The diagram is divided into two main sections: (A) Roaming Scenarios and (B) Non-Roaming Scenarios. + +**Sequence of Messages:** + +1. PMIPv6 or GTP Tunnel (Established between Trusted Non-3GPP IP Access/ePDG and PDN GW) +2. UE discovers 3GPP access system and initiates HO +3. Attach (UE to E-UTRAN) +4. Access Authentication (E-UTRAN to HSS/AAA via MME) +5. Location Update and Subscriber Data Retrieval (MME to HSS/AAA) +6. Create Session Request (MN-NAI, PDN GW) (MME to PDN GW) +7. Create Session Request (PDN GW to Old MME/SGSN) +8. PCEF-Initiated IP-CAN Session Modification Procedure (Old MME/SGSN to PDN GW) +9. Create Session Response (Old MME/SGSN to PDN GW) +10. Create Session Response (IP Addr) (PDN GW to MME) +11. Radio and Access Bearer Establishment (MME to E-UTRAN) +12. Modify Bearer Request (MME to PDN GW) +13. Modify Bearer Request (PDN GW to Old MME/SGSN) +14. Modify Bearer Response (Old MME/SGSN to PDN GW) +15. Modify Bearer Response (PDN GW to MME) +16. Radio and Access Bearer / GTP Tunnel (Established between E-UTRAN and PDN GW) +17. UE Requested PDN Connectivity (MME to HSS/AAA) +18. Non-3GPP EPS Bearer Release (PDN GW to Trusted Non-3GPP IP Access/ePDG) + +**Scenarios:** + +- (A) Roaming Scenarios: Includes steps 7, 8, and 9. +- (B) Non-Roaming Scenarios: Includes steps 13 and 14. + +Sequence diagram of handover procedure from Trusted WLAN on S2a to 3GPP access. It shows 18 steps involving UE, ePDG, E-UTRAN, MME, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. The diagram is split into two scenarios: (A) Roaming and (B) Non-Roaming. + +Figure 8.2.1.2.7-1: Handover from Trusted WLAN on GTP S2a to 3GPP access for roaming and non-roaming scenarios + +This procedure is as in TS 23.402 clause 8.2.1.1/8.2.1.2 with the following differences: + +- Step 1. There is a GTP or PMIP tunnel between TWAN and PGW +- Step 18. The PDN GW shall initiate resource allocation deactivation procedure in the TWAN as defined in clause 8.2.1.2.9. + +### 8.2.1.2.8 Detach and PDN disconnection in WLAN on S2a + +#### 8.2.1.2.8.1 Detach and PDN disconnection in WLAN on GTP S2a + +##### 8.2.1.2.8.1.1 UE/TWAN Initiated Detach and UE/TWAN requested PDN Disconnection Procedure in WLAN on GTP S2a + +For UE/TWAN initiated detach, this procedure is the same as TS 23.402 clause 16.3.1.1. + +If the single-connection scenario was selected during authentication, then the UE/TWAN requested PDN disconnection procedure is the same as TS 23.402 clause 16.3.1.1. + +If the multi-connection scenario was selected during authentication, then this clause applies to UE/TWAN-requested PDN disconnection procedure. For multiple PDN connections, this disconnection procedure shall be repeated for each PDN connection that needs to be released. + +![Sequence diagram of UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN. The diagram shows interactions between UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxv, vPCRF, and hPCRF. The procedure involves a PDN Disconnect Request from UE to TWAN, a Delete Session Request from TWAN to PDN GW, an Update PDN GW Address from AAA Proxv to HSS/AAA, a PCEF-Initiated IP-CAN Session Termination Procedure between PDN GW and vPCRF, a Delete Session Response from PDN GW to TWAN, a PDN Disconnect Response from TWAN to UE, a PDN Disconnection Request from UE to TWAN, a PDN Disconnection Response from TWAN to UE, and finally a TWAN specific resource Release Procedure between UE and TWAN.](42e18c25bfd455a5a57f207bacfcb970_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant AAA_Proxv as AAA Proxv + participant vPCRF + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of AAA_Proxv: Roaming Scenarios + Note right of AAA_Proxv: (AAA Proxv, vPCRF, hPCRF) + + UE-->>TWAN: 1. PDN Disconnect Request + TWAN->>PDN_GW: 2. Delete Session Request + AAA_Proxv->>HSS_AAA: 3. Update PDN GW Address + PDN_GW-->>vPCRF: 4. PCEF-Initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Delete Session Response + TWAN-->>UE: 6. PDN Disconnect Response + UE-->>TWAN: 7. PDN Disconnection Request + TWAN-->>UE: 8. PDN Disconnection Response + Note left of PDN_GW: 9. TWAN specific resource Release Procedure + UE-->>TWAN: + +``` + +Sequence diagram of UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN. The diagram shows interactions between UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxv, vPCRF, and hPCRF. The procedure involves a PDN Disconnect Request from UE to TWAN, a Delete Session Request from TWAN to PDN GW, an Update PDN GW Address from AAA Proxv to HSS/AAA, a PCEF-Initiated IP-CAN Session Termination Procedure between PDN GW and vPCRF, a Delete Session Response from PDN GW to TWAN, a PDN Disconnect Response from TWAN to UE, a PDN Disconnection Request from UE to TWAN, a PDN Disconnection Response from TWAN to UE, and finally a TWAN specific resource Release Procedure between UE and TWAN. + +**Figure 8.2.1.2.8.1.1-1: UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN** + +This procedure applies to the Non-Roaming, Home Routed Roaming and Local Breakout cases. In the Local Breakout case, the vPCRF forwards messages between the PDN GW and the hPCRF. In the LBO cases, the 3GPP AAA Proxy serves as an intermediary between the Trusted Non-3GPP IP Access and the 3GPP AAA Server in the HPLMN. In the non-roaming and Home Routed Roaming case, the vPCRF is not involved at all. + +If dynamic policy provisioning is not deployed, the optional steps of interaction between the PDN GW and PCRF do not occur. Instead, the PDN GW may employ static configured policies. + +- Step 1. If the PDN disconnection is initiated by the UE, the UE sends a PDN Disconnection Request (User Plane Connection ID) to the TWAG by means of TSM. + +- Step 2. The TWAN releases the PDN connection and sends a Delete Session Request (Linked EPS Bearer ID) message for this PDN connection to the PDN GW. +- Step 3. The PDN GW informs the 3GPP AAA Server of the PDN disconnection. +- Step 4. The PDN GW deletes the IP CAN session associated with the UE and executes a PCEF-Initiated IP-CAN Session Termination Procedure with the PCRF as specified in TS 23.203 [4]. +- Step 5. The PDN GW acknowledges with a Delete Session Response (Cause) message. +- Step 6. If the PDN disconnection was initiated by the UE in step 1, then the UE is informed of the disconnection by means of a TSM PDN Disconnection Response. +- Step 7. If the PDN disconnection was initiated by the TWAG, then the UE is informed of the disconnection by means of a TSM PDN Disconnection Request (User Plane Connection ID). +- Step 8. The UE acknowledges the disconnection request received in step 7. + +NOTE: Either step 1 and 6, or step 7 and 8, are performed + +#### 8.2.1.2.8.1.2 HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a + +This procedure is the same as TS 23.402 clause 16.3.1.2. + +#### 8.2.1.2.8.2 Detach and PDN disconnection in WLAN on PMIP S2a + +**Editor's Notes: This procedure is still to be added.** + +#### 8.2.1.2.9 PDN GW initiated Resource Allocation Deactivation + +##### 8.2.1.2.9.1 PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a + +If the single-connection scenario was selected during authentication, then this procedure is the same as TS 23.402 clause 16.4.1. + +If the network selected the multi-connection scenario during authentication, then this procedure is as in TS 23.402 clause 16.4.1 with the following difference: If all TWAN resources related to a PDN connection are released, then in step 3 the UE is informed of the PDN connection release using WLCP. + +##### 8.2.1.2.9.2 PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a + +**Editor's Notes: This procedure is still to be added.** + +#### 8.2.1.3 Impacts on existing nodes or functionality + +**Editor's Note: Impact on existing nodes or functionality is still to be added.** + +#### 8.2.1.4 Evaluation + +**Editor's Note: The fulfilment to the requirements in subclause 8.1 should be evaluated.** + +## 8.2.2 Solution 2: Layer 2 solution based on Stateful Address Configuration of Per-PDN Connection/NSWO Point-to-Point Link Multiplexed at Layer 2 + +### 8.2.2.1 Functional Description + +#### 8.2.2.1.1 User Plane Multiplexing for Per-PDN Connection / NSWO Point-to-Point Link + +##### 8.2.2.1.1.0 General + +The solution relies on the use of Stateful Address Configuration of Per-PDN Connection / NSWO Point-to-Point Link Multiplexed at Layer 2. + +In addition to the two mechanisms described as part of this solution in subclause 8.2.2.1.1.1 (Per PDN/NSWO VLAN Id), and subclause 8.2.2.1.1.2 (Per PDN/NSWO TWAG MAC Address), any type of per-PDN/NSWO packet marking mechanism layered directly over L2 but below IPv4/IPv6 could be used with this solution, including, but not limited to, keyed GRE over Ethernet as described as part of Solution 1 in subclause 8.2.1, or a new 3GPP specific LLC/SNAP header as described as part of Solution 8 in subclause 8.2.8. + +Multiple PDN Connections to the same APN are supported via allocation of multiple identifiers (e.g. VLAN Ids) for multiple point-to-point links. + +##### 8.2.2.1.1.1 Per-PDN Connection/NSWO Virtual Point-to-Point Link Model based on distinct VLAN ID + +![Diagram illustrating the Point-to-point link model for PDN connection and NSWO access based on distinct VLAN ID. The diagram shows traffic flow from an Application / Service Layer through UL and DL Traffic Flow Aggregates into a UE and PDN GW. The UE connects to an AP/WLC, which connects to a TWAG, which in turn connects to an NSWO. The PDN GW also connects to the TWAG. VLAN IDs are used to distinguish between different PDN connections and the NSWO access. The diagram includes labels for APN/NSWO, APN/NSWO -> VLAN ID, DL-TFT -> S2a - TEID, VLAN-ID <-> S2a-TEID, and S2a Bearer.](daf05db9f13b34fb12da52f007bbfe5b_img.jpg) + +The diagram illustrates the network architecture for the point-to-point link model. At the top, an 'Application / Service Layer' is shown. Below it, 'UL Traffic Flow Aggregates' and 'DL Traffic Flow Aggregates' are depicted. On the left, a 'UE' (User Equipment) is connected to an 'AP/WLC' (Access Point/Wireless LAN Controller). The 'AP/WLC' is connected to a 'TWAG' (Traffic Gateway). The 'TWAG' is connected to an 'NSWO' (Non-Seamless WLAN Offload) and a 'PDN GW' (PDN Gateway). The 'PDN GW' is also connected to the 'TWAG'. The 'UE' has multiple virtual interfaces, each associated with a specific 'VLAN ID'. The 'AP/WLC' and 'TWAG' are also associated with specific 'VLAN IDs'. The 'NSWO' is connected to the 'TWAG' via an 'S2a Bearer'. The 'PDN GW' is connected to the 'TWAG' via an 'S2a - TEID'. The 'TWAG' is connected to the 'NSWO' via an 'S2a - TEID'. The 'VLAN-ID' and 'S2a-TEID' are shown as being linked on the 'TWAG' interface. The 'APN/NSWO' and 'APN/NSWO -> VLAN ID' are shown on the 'UE' side, indicating the mapping of traffic to specific VLANs. The 'DL-TFT -> S2a - TEID' and 'VLAN-ID <-> S2a-TEID' are shown on the 'PDN GW' and 'TWAG' side, indicating the mapping of traffic to specific bearers and VLANs. + +Diagram illustrating the Point-to-point link model for PDN connection and NSWO access based on distinct VLAN ID. The diagram shows traffic flow from an Application / Service Layer through UL and DL Traffic Flow Aggregates into a UE and PDN GW. The UE connects to an AP/WLC, which connects to a TWAG, which in turn connects to an NSWO. The PDN GW also connects to the TWAG. VLAN IDs are used to distinguish between different PDN connections and the NSWO access. The diagram includes labels for APN/NSWO, APN/NSWO -> VLAN ID, DL-TFT -> S2a - TEID, VLAN-ID <-> S2a-TEID, and S2a Bearer. + +Figure 8.2.2.1.1.1-1: Point-to-point link model for PDN connection and NSWO access based on distinct VLAN ID + +In this link model the virtual point-to-point link required to transport traffic for a given PDN connection, or for Non-Seamless WLAN Offload (NSWO) is realized via the TWAG reserving a distinct VLAN ID that uniquely (on a per-UE basis) corresponds to an APN or NSWO. These distinct VLAN ID are configured on the TWAG interface, i.e., the TWAG can receive and send layer 2 frames from and to each of these VLAN ID. + +As depicted in Figure 8.2.2.1.1.1-1, the virtual point-to-point link is realized via enforcing forwarding of uplink and downlink IP packets between distinct PDN connections and NSWO access into their corresponding VLANs via marking layer 2 frame contacting these IP packets with the appropriate VLAN ID. VLAN marking over the IEEE Std 802.11 air link is performed as per Annex P of IEEE Std 802.11 [5]. + +On the UE, each of the virtual point-to-point link is modelled as a virtual interface that is exposed to the IP layer with a fixed IPv4 and/or IPv6 address(es). Applications can bind sockets to a specific virtual interface thus in effect binding the socket to a specific PDN connection or to NSWO access. Packet transmission occurs as follow: + +- In the uplink direction, all IP packets transmitted via the virtual interface, including IP multicast packets, are encapsulated in layer 2 frames marked with the VLAN ID that corresponds to the PDN connection or NSWO access the socket/interface is bound to. On the receiving side, the TWAG is able to demultiplex incoming packets towards the appropriate PDN connection or NSWO access via looking up the VLAN ID of the layer 2 data frame. +- In the downlink direction, the TWAG transmits all IP packets, including IP multicast packets, encapsulated in layer 2 frames marked with the VLAN ID that corresponds to the PDN connection or NSWO access the packet originated from. On the receiving side, the UE is able to demultiplex incoming packets towards the appropriate PDN connection or NSWO access via looking up the VLAN ID of the layer 2 data frame, and passes the IP packets contained in these frames to the IP layer via the corresponding virtual interface. + +#### 8.2.2.1.1.2 Per-PDN Connection/NSWO Virtual Point-to-Point Link Model based on distinct layer 2 TWAG MAC addresses + +![Diagram of the Point-to-point link model for PDN connection and NSWO access based on distinct layer 2 TWAG MAC addresses. The diagram shows the flow of traffic from the Application / Service Layer through UL and DL Traffic Flow Aggregates to the UE, AP/WLC, TWAG, and PDN GW. It details the mapping of APN/NSWO and DL-TFT to specific MAC and TEID addresses at the TWAG.](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +The diagram illustrates the network architecture for the Point-to-point link model. At the top, the **Application / Service Layer** is shown. Below it, **UL Traffic Flow Aggregates** and **DL Traffic Flow Aggregates** are depicted. The **UE** (User Equipment) is on the left, connected to an **AP/WLC** (Access Point/Wireless LAN Controller). The **AP/WLC** is connected to a **TWAG** (Traffic Offload Gateway). The **TWAG** is connected to a **PDN GW** (PDN Gateway) on the right. The **PDN GW** is connected to an **NSWO** (Non-Seamless WLAN Offload) and an **S2a Bearer**. The diagram shows the mapping of traffic flows to specific MAC and TEID addresses at the TWAG. For uplink traffic, the mapping is **APN/NSWO → TWAG-MAC** and **DL-TFT → S2a-TEID**. For downlink traffic, the mapping is **TWAG-MAC → S2a-TEID**. The **802 Flow UE-MAC ↔ TWAG-MAC** is also shown at the bottom. + +Diagram of the Point-to-point link model for PDN connection and NSWO access based on distinct layer 2 TWAG MAC addresses. The diagram shows the flow of traffic from the Application / Service Layer through UL and DL Traffic Flow Aggregates to the UE, AP/WLC, TWAG, and PDN GW. It details the mapping of APN/NSWO and DL-TFT to specific MAC and TEID addresses at the TWAG. + +**Figure 8.2.2.1.1.2-1: Point-to-point link model for PDN connection and NSWO access based on distinct layer 2 TWAG MAC addresses** + +In this link model the virtual point-to-point link required to transport traffic for a given PDN connection, or for Non-Seamless WLAN Offload (NSWO) is realized via the TWAG reserving a distinct MAC address that uniquely (on a per-UE basis) corresponds to an APN or NSWO. These distinct layer 2 MAC addresses are configured on the TWAG interface, i.e., the TWAG can receive and send layer 2 frames from each of these MAC addresses. + +As depicted in Figure 8.2.2.1.1.2-1, the virtual point-to-point link is realized via enforcing a forced forwarding of uplink and downlink IP packets respectively to and from the corresponding layer 2 TWAG MAC address located in the layer 2 header of the frame containing the IP packets. + +On the UE, each of the virtual point-to-point link is modelled as a virtual interface that is exposed to the IP layer with a fixed IPv4 and/or IPv6 address(es). Applications can bind sockets to a specific virtual interface thus in effect binding the socket to a specific PDN connection or to NSWO access. Packet transmission occurs as follow: + +- In the uplink direction, all IP packets transmitted via the virtual interface, including IP multicast packets, are encapsulated in layer 2 frames with destination layer 2 address set to the layer 2 unicast MAC address of the TWAG that corresponds to the PDN connection or NSWO access the socket/interface is bound to. On the receiving side, after identifying the associated UE using the source MAC address of the data frame, the TWAG is able to demultiplex incoming packets towards the appropriate PDN connection or NSWO access via looking up the layer 2 destination address TWAG-MAC of the data frame. + +- In the downlink direction, the TWAG transmits all IP packets, including IP multicast packets, encapsulated in layer 2 frames with source layer 2 address set to the layer 2 unicast MAC address of the TWAG that corresponds to the PDN connection or NSWO access the packet originated from. On the receiving side, the UE is able to demultiplex incoming packets towards the appropriate PDN connection or NSWO access via looking up the layer 2 source unicast MAC address of the data frame, and passes the IP packets contained in these frames to the IP layer via the corresponding virtual interface. + +#### 8.2.2.1.2 Initial Attach in WLAN + +![Sequence diagram of Initial Attach in WLAN. Lifelines: UE, TWAN, PDN GW, Roaming Scenarios (vPCRF, AAA Proxy), hPCRF, HSS/AAA. Step 1: Non-3GPP Specific Procedures (UE to TWAN). Step 2: EAP authentication (UE to TWAN). Step 3: Authentication & Authorization (TWAN to PDN GW via Roaming Scenarios).](c419b566d720267c499087add1506018_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy + end + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note left of UE: 1. Non-3GPP Specific Procedures + UE->>TWAN: 2. EAP authentication + TWAN->>PDN_GW: 3. Authentication & Authorization + +``` + +Sequence diagram of Initial Attach in WLAN. Lifelines: UE, TWAN, PDN GW, Roaming Scenarios (vPCRF, AAA Proxy), hPCRF, HSS/AAA. Step 1: Non-3GPP Specific Procedures (UE to TWAN). Step 2: EAP authentication (UE to TWAN). Step 3: Authentication & Authorization (TWAN to PDN GW via Roaming Scenarios). + +**Figure 8.2.2.1.2-1: Initial Attach in WLAN on GTP or PMIP S2a for roaming, LBO and non-roaming scenarios** + +As depicted in Figure 8.2.2.1.2-1, the initial attach procedure occurs with the following steps: + +The first step of the proposal is for both the UE, the Trusted WLAN Access, and the 3GPP AAA Server in the HPLMN to discover whether all of them do support fully fledged Trusted WLAN Access to the EPC (i.e., as per the requirements, concurrent multiple PDN connections, IP address preservation, and concurrent NSWO and EPC access). This is done in the following way: + +1. The UE discovers the TWAN and associates with it. +2. The TWAN begins the EAP exchange by sending an EAP Request message as part of the IEEE 802.1X authentication procedure [5]. As part of the EAP exchange, the UE, the Trusted WLAN Access, and the 3GPP AAA Server in the HPLMN to discover whether all of them do support fully fledged Trusted WLAN Access to the EPC (i.e., as per the requirements, concurrent multiple PDN connections, IP address preservation, and concurrent NSWO and EPC access): + - a) The UE indicates support to the 3GPP AAA server in the HPLMN via including an indication EAP-AKA attribute in the EAP-AKA Response messages it sends. + - b) The Trusted WLAN Access indicates support to the 3GPP AAA server in the HPLMN via including an indication AAA attribute in the Diameter EAP-Request message it sends. + - c) The 3GPP AAA server in the HPLMN indicates to the Trusted WLAN Access that both itself and the UE have support via inclusion of the same indication AAA attribute in the Diameter EAP-Answer message it sends. + - d) The 3GPP AAA server in the HPLMN indicates to UE that both itself and the Trusted WLAN Access have support via inclusion of a similar indication attribute within the EAP-AKA Request message. + - e) If either of the UE, the Trusted WLAN Access Network, or the 3GPP AAA Server in the HPLMN support fully fledged Trusted WLAN Access to the EPC, fallback to single PDN connection to a default per-subscription APN ensues (phase 1 SaMOG) as per steps 3-15 of subclause 16.2.1 of 3GPP TS 23.402 [3] in case of GTP S2a or subclause 16.2.2 of 3GPP TS 23.402 [3] in case of PMIP S2a. If on the other hand all of the UE, the Trusted WLAN Access Network, and the HPMLN support fully fledged Trusted WLAN Access to the EPC, neither PDN connections nor Non-Seamless WLAN Offload (NSWO) is offered automatically by the Trusted WLAN Access without explicit request from the UE as described in subclause 8.2.2.1.3. + +### 8.2.2.1.3 UE Requested PDN or NSWO connectivity + +The UE explicitly requests establishment of PDN connections and/or NSWO in two steps: preparation and execution. + +In a first preparation step, the UE queries from the network the values of the VLAN or TWAG MAC address to use to reach a list of APNs it might want to establish a PDN connection to in the future, including the unspecified *'default'* APN that will be selected by the network (similar to the default APN that exists in phase 1 of SaMOG), as well as NSWO. The UE also indicates to the network the PDN Type of the PDN connection it will desire to establish. The signalling to carry on with this query from the UE to the network based on the use of EAP-AKA [22] extensions attributes during the authentication phase. As a result of this query, the network indicates to the UE a list of VLAN identifiers (first variant of the virtual point-to-point link model), TWAG MAC addresses (second variant of the virtual point-to-point link model), or any other point-to-point link multiplexing identifier (e.g., for keyed GRE or new 3GPP SNAP protocol) that corresponds to each of the APN in which it has expressed interest in connecting to (as well as the value that was selected by the network as the *'default'* APN) on one hand, and to NSWO on the other hand. Again, the signalling to carry on with this indication from the network to the UE is based on the use of EAP-AKA extension attributes that are populated by the 3GPP AAA Server based on information received from the Trusted WLAN Access. A list of L2 identifiers for multiplexing of the point-to-point links is chosen locally by the TWAN based on configuration, and sent to the AAA server over STa. The AAA server extracts from this list as many L2 identifiers as there are PDN connections requested by the UE in the EAP Response/Identity, and includes it together with the authorized PDN types for those APN as per the subscription in the EAP Request/AKA-Challenge or AKA-Reauthentication message sent back to the UE, while the list of APNs for the PDN connections requested by UE is sent to the TWAN over STa. + +**Editor's note:** It is FFS how a UE that requests a dual IP version PDN Type IPv4v6 is informed that the established PDN connection has a single IP version PDN Type (i.e., IPv4, or IPv6) in cases where the selected PDN GW only allows single IP version PDN Type for this APN. + +If a UE expects to need multiple PDN connections to a single APN, it needs to requests multiple point-to-point link multiplexing identifiers for that same APN. The network may decide to respond fully to the request, or with a lesser number of point-to-point link multiplexing identifiers. + +- NOTE:** Because the values of the point-to-point link identifiers for the various APNs the UE wishes to connect to are negotiated during the EAP-AKA exchange, APNs need to be known prior to authentication with the Trusted WLAN Access. In the unlikely event that the UE needs to connect to an *unforeseen* APN, the UE would be required to disconnect, then reconnect, to the Trusted WLAN Access. +- NOTE:** Because the values of the point-to-point link identifiers for the various APNs the UE wishes to connect to are negotiated during the EAP-AKA exchange, all this information needs to fit in a single EAP-AKA message. This places a limit on the number of the point-to-point links and APNs that can be negotiated. However given that on a 3GPP access a UE is also limited to a maximum of 12 simultaneous bearers, and hence PDN connections, it is deemed reasonable that for Trusted WLAN Access a limitation also exists. +- NOTE:** In case where the subscription profile list the wildcard APN, the TWAN would need to send all APNs supported by an HPLMN (with corresponding VLAN IDs or TWAG MAC addresses) to the UE via EAP-AKA’ or ANQP. + +![Sequence diagram for UE requested PDN or NSWO connectivity for GTP-based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps for Virtual Point-to-Point Link Creation, L3 Address Request, Create Session Request, IP-CAN Session Establishment Procedure, Update PDN GW Address, Create Session Response, GTP Tunnel, NSWO Activation, and L3 Address Reply. It is divided into GTP S2a and NSWO scenarios.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +The sequence diagram illustrates the interaction for GTP-based S2a. It begins with '1. Virtual Point-to-Point Link Creation' between UE and TWAN. The UE sends an '2. L3 Address Request' to the TWAN. The TWAN then sends a '3. Create Session Request' to the PDN GW. A dashed box labeled '4. IP-CAN Session Establishment Procedure' involves the PDN GW, vPCRF, AAA Proxy, and hPCRF. The AAA Proxy sends a '5. Update PDN GW Address' to the HSS/AAA. The PDN GW returns a '6. Create Session Response' to the TWAN. A green bar labeled '7. GTP Tunnel' is shown between the TWAN and PDN GW. A separate dashed box labeled '3b. NSWO Activation' is shown between the TWAN and PDN GW. Finally, the TWAN sends an '8. L3 Address Reply' to the UE. The diagram is categorized into '(GTP S2a)' and '(NSWO)' scenarios. + +Sequence diagram for UE requested PDN or NSWO connectivity for GTP-based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps for Virtual Point-to-Point Link Creation, L3 Address Request, Create Session Request, IP-CAN Session Establishment Procedure, Update PDN GW Address, Create Session Response, GTP Tunnel, NSWO Activation, and L3 Address Reply. It is divided into GTP S2a and NSWO scenarios. + +Figure 8.2.2.1.3-1: UE requested PDN or NSWO connectivity for GTP-based S2a + +![Sequence diagram for UE requested PDN or NSWO connectivity for PMIP-based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps for Virtual Point-to-Point Link Creation, L3 Address Request, Proxy Binding Update, IP-CAN Session Establishment Procedure, Update PDN GW Address, Proxy Binding Ack, PMIP Tunnel, NSWO Activation, and L3 Address Reply. It is divided into PMIP S2a and NSWO scenarios.](28085f681b9fff76a53c5b8b32338ee1_img.jpg) + +The sequence diagram illustrates the interaction for PMIP-based S2a. It begins with '1. Virtual Point-to-Point Link Creation' between UE and TWAN. The UE sends an '2. L3 Address Request' to the TWAN. The TWAN then sends a '3. Proxy Binding Update' to the PDN GW. A dashed box labeled '4. IP-CAN Session Establishment Procedure' involves the PDN GW, vPCRF, AAA Proxy, and hPCRF. The AAA Proxy sends a '5. Update PDN GW Address' to the HSS/AAA. The PDN GW returns a '6. Proxy Binding Ack' to the TWAN. A green bar labeled '7. PMIP Tunnel' is shown between the TWAN and PDN GW. A separate dashed box labeled '3b. NSWO Activation' is shown between the TWAN and PDN GW. Finally, the TWAN sends an '8. L3 Address Reply' to the UE. The diagram is categorized into '(PMIP S2a)' and '(NSWO)' scenarios. + +Sequence diagram for UE requested PDN or NSWO connectivity for PMIP-based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps for Virtual Point-to-Point Link Creation, L3 Address Request, Proxy Binding Update, IP-CAN Session Establishment Procedure, Update PDN GW Address, Proxy Binding Ack, PMIP Tunnel, NSWO Activation, and L3 Address Reply. It is divided into PMIP S2a and NSWO scenarios. + +Figure 8.2.2.1.3-2: UE requested PDN or NSWO connectivity for PMIP-based S2a + +In a second execution step, the UE explicitly requests establishment of a PDN connection to a specific APN or activation and deactivation of NSWO as per the following steps depicted in Figure 8.2.2.1.3-1 for GTP-based S2a and Figure 8.2.2.1.3-2 for PMIP-based S2a: + +1. The UE creates a virtual IP interface corresponding to the APN towards which it desires to establish a PDN connection, or to NSWO. +2. The UE requests allocation of an IPv4 and/or IPv6 address for this virtual interface by sending a DHCP or DHCPv6 request message from this virtual interface. In the first variant of the virtual point-to-point link model, the layer 2 frame carrying the DHCP is marked with the corresponding VLAN Id. In the second variant of the virtual point-to-point link model, the layer 2 frame carrying the DHCP message will be unicasted to the corresponding TWAG MAC address. + +NOTE: The UE may requests allocation of an IPv4 address via DHCP but still perform IPv6 Stateless Address Auto-Configuration (SLAAC) for configuration of its IPv6 address. In this case, the UE or the network signal the will to tear down a PDN connection and/or NSWO access based solely on DHCP signaling for the IPv4 address. + +- 3-7. When the TWAG receives the DHCP IPv4 and/or IPv6 address allocation request over the virtual interface corresponding to a specific VLAN (first variant of the virtual point-to-point link model) or TWAG MAC address (second variant of the virtual point-to-point link model), that corresponds to an APN it requests to the PDN GW creation of a GTP or PMIP tunnel for the APN as per steps 3-7 of respectively subclause 16.2.1 or 16.2.2 of 3GPP TS 23.402 [5] in case of GTP-based S2a or PMIP-based S2a, otherwise it activates NSWO if the virtual interface corresponds to NSWO access (step 3b). +8. The TWAG then sends a DHCP reply to the UE with an IPv4 address and/or IPv6 address as allocated by the PDN GW or by the NSWO access. The UE can then use the PDN connection via the virtual interface. Within the Trusted WLAN Access, the different virtual point-to-point links ensure separation of user plane traffic belonging to separate APNs and NSWO. The TWAG enforces forwarding between specific virtual point-to-point links and the GTP or PMIP tunnels towards the specific APNs, or NSWO access. + +#### 8.2.2.1.4 UE Requested PDN or NSWO disconnection + +![Sequence diagram for UE requested PDN or NSWO disconnection for GTP-based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves L3 Address Release, Delete Session Request, Update PDN GW Address, PCEF-initiated IP-CAN Session Termination Procedure, Delete Session Response, L3 Address Release Confirmation, and Virtual Point-to-Point Link Deletion. Two scenarios are highlighted: (GTP S2a) and (NSWO).](e90b25c8d90cadc3f76c376701cf27ed_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of HSS_AAA: Roaming Scenarios + + UE->>TWAN: 1. L3 Address Release + TWAN->>PDN_GW: 2. Delete Session Request + PDN_GW->>HSS_AAA: 3. Update PDN GW Address + Note right of HSS_AAA: (GTP S2a) + PDN_GW-->>AAA_Proxy: 4. PCEF-initiated IP-CAN Session Termination Procedure + AAA_Proxy-->>PDN_GW: 5. Delete Session Response + PDN_GW-->>TWAN: 6. L3 Address Release Confirmation + Note right of HSS_AAA: (NSWO) + TWAN->>UE: 2b. NSWO Disconnect + TWAN->>UE: 7. Virtual Point-to-Point Link Deletion + +``` + +Sequence diagram for UE requested PDN or NSWO disconnection for GTP-based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves L3 Address Release, Delete Session Request, Update PDN GW Address, PCEF-initiated IP-CAN Session Termination Procedure, Delete Session Response, L3 Address Release Confirmation, and Virtual Point-to-Point Link Deletion. Two scenarios are highlighted: (GTP S2a) and (NSWO). + +Figure 8.2.2.1.4-1: UE requested PDN or NSWO disconnection for GTP-based S2a + +![Sequence diagram for UE requested PDN or NSWO disconnection for PMIP-based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves L3 Address Release, Proxy Binding Update, Update PDN GW Address, PCEF-initiated IP-CAN Session Termination Procedure, Proxy Binding Ack, NSWO Disconnect, L3 Address Release Confirmation, and Virtual Point-to-Point Link Deletion. The diagram is divided into two main sections: (GTP S2a) and (NSWO).](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN GW + participant vPCRF + participant AAA Proxy + participant hPCRF + participant HSS/AAA + + Note right of PDN GW: Roaming Scenarios + + Note right of HSS/AAA: (GTP S2a) + + UE->>TWAN: 1. L3 Address Release + TWAN->>PDN GW: 2. Proxy Binding Update (lifetime=0) + PDN GW->>HSS/AAA: 3. Update PDN GW Address + Note right of PDN GW: 4. PCEF-initiated IP-CAN Session Termination Procedure + PDN GW->>TWAN: 5. Proxy Binding Ack + Note right of HSS/AAA: (NSWO) + TWAN->>TWAN: 2b. NSWO Disconnect + TWAN->>UE: 6. L3 Address Release Confirmation + Note left of UE: 7. Virtual Point-to-Point Link Deletion + +``` + +Sequence diagram for UE requested PDN or NSWO disconnection for PMIP-based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves L3 Address Release, Proxy Binding Update, Update PDN GW Address, PCEF-initiated IP-CAN Session Termination Procedure, Proxy Binding Ack, NSWO Disconnect, L3 Address Release Confirmation, and Virtual Point-to-Point Link Deletion. The diagram is divided into two main sections: (GTP S2a) and (NSWO). + +**Figure 8.2.2.1.4-2: UE requested PDN or NSWO disconnection for PMIP-based S2a** + +The UE explicitly requests disconnection of a PDN disconnection to a specific APN or deactivation of NSWO and deactivation of NSWO as per the following steps: + +1. The UE releases the IPv4 and/or IPv6 address allocated for the virtual interface by sending a DHCP or DHCPv6 release from this virtual interface. In the first variant of the virtual point-to-point link model, the layer 2 frame carrying the DHCP message is marked with the corresponding VLAN Id. In the second variant of the virtual point-to-point link model, the layer 2 frame carrying the DHCP message will be unicasted to the corresponding TWAG MAC address. +2. When the TWAG receives the DHCP IPv4 and/or IPv6 address release message over the virtual interface corresponding that corresponds to an APN, it requests to the PDN GW deletion of the GTP tunnel, or the PMIP tunnel for this APN as per steps 2-5 of respectively subclause 16.3.1.1 of 3GPP TS 23.402 [5] in case of GTP-based S2a, or subclause 16.3.2.1 of 3GPP TS 23.402 [5] in case of PMIP-based S2a, or disconnects NSWO if the virtual interface corresponds to NSWO (step 2b). +6. The TWAG then sends a DHCP reply to the UE to confirm release of the IPv4 address and/or IPv6 address for the PDN connection or the NSWO access. +7. The UE then deletes the virtual IP interface for the virtual point-to-point link corresponding the PDN connection, or to NSWO. + +### 8.2.2.1.5 HSS/AAA Initiated PDN or NSWO Disconnection procedure in WLAN + +![Sequence diagram for HSS/AAA Initiated Detach on GTP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a session termination request from HSS/AAA to TWAN, followed by a block of procedures (steps 2-5) from another figure, then an L3 Address Force Renew/Reconfigure from TWAN to UE, and finally a Session Termination Response from AAA Proxy to HSS/AAA. A 'Roaming Scenarios' box covers the PDN GW, vPCRF, and AAA Proxy lifelines.](212c50c4e3d043c989037a01e13c1a98_img.jpg) + +Sequence diagram for HSS/AAA Initiated Detach on GTP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a session termination request from HSS/AAA to TWAN, followed by a block of procedures (steps 2-5) from another figure, then an L3 Address Force Renew/Reconfigure from TWAN to UE, and finally a Session Termination Response from AAA Proxy to HSS/AAA. A 'Roaming Scenarios' box covers the PDN GW, vPCRF, and AAA Proxy lifelines. + +Figure 8.2.2.1.5-1: HSS/AAA Initiated Detach on GTP S2a + +![Sequence diagram for HSS/AAA Initiated Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a session termination request from HSS/AAA to TWAN, followed by a block of procedures (steps 2-5) from another figure, then an L3 Address Force Renew/Reconfigure from TWAN to UE, and finally a Session Termination Response from AAA Proxy to HSS/AAA. A 'Roaming Scenarios' box covers the PDN GW, vPCRF, and AAA Proxy lifelines.](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +Sequence diagram for HSS/AAA Initiated Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a session termination request from HSS/AAA to TWAN, followed by a block of procedures (steps 2-5) from another figure, then an L3 Address Force Renew/Reconfigure from TWAN to UE, and finally a Session Termination Response from AAA Proxy to HSS/AAA. A 'Roaming Scenarios' box covers the PDN GW, vPCRF, and AAA Proxy lifelines. + +Figure 8.2.2.1.5-2: HSS/AAA Initiated Detach on PMIP S2a + +The procedure for HSS/AAA Initiated Detach from TWAN is represented in Figure 8.2.2.1.5-1 in case of GTP-based S2a and Figure 8.2.2.1.5-2 in case of PMIP-based S2a and described below: + +- 1) The HSS/AAA sends a Session Termination Request message to the TWAN to detach a specific UE. +- 2) The step 2 to 5 of the UE/TWAN Initiated PDN or NSWO Disconnection procedure described in clause 8.2.2.1.4 are followed. +- 3) The TWAG force the UE to renew its IPv4 and/or IPv6 address(es) by sending a DHCP FORCERENEW message as per IETF RFC 3203 [24] or DHCPv6 Reconfigure message as per IETF RFC 3315 [23]. The DHCP FORCERENEW message is secured via Forcerenew Nonce Authentication as per RFC 6704 [29]. When the UE proceeds with renewing the address lease for the APN or NSWO, the TWAG can in turn refuse to do so, notifying to the UE that the PDN or NSWO has been disconnected. +- 4) TWAN sends a Session Termination Response message to 3GPP AAA Server. If the detach procedure was initiated from the 3GPP AAA Server and if the UE no longer has any context in the 3GPP AAA Server, the 3GPP AAA Server communicates this to the HSS as described in clause 12.1.2 of 3GPP TS 23.402 [5]. If the detach procedure was initiated by HSS, the 3GPP AAA Server replies to the HSS as described in clause 12.1.3 of 3GPP TS 23.402 [5]. + +### 8.2.2.1.6 HSS/AAA Initiated Detach procedure in WLAN + +This procedure is similar as per subclause 16.3.2.2.2 of 3GPP TS 23.402 [5]. + +### 8.2.2.1.7 Handover from 3GPP Access to Trusted WLAN Access + +![Sequence diagram illustrating the handover from 3GPP Access to Trusted WLAN Access. The diagram shows the interaction between UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with the UE connected via a Radio Bearer & S1/S4 bearer (GTP/PMIP tunnel). The handover steps are: 1. Virtual Point-to-Point Link Creation; 2. Handover Request; 3. Create Session Request / Proxy Binding Update; 4. IP-CAN Session Establishment Procedure (repeated for each PDN connection to same APN); 5. Update PDN GW Address; 6. Create Session Response / Proxy Binding Ack; 7. GTP/PMIP Tunnel; 8. Handover Reply; 9. 3GPP EPS Bearer Release.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +The diagram illustrates the sequence of messages for a handover from 3GPP Access to Trusted WLAN Access. The participants are UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process begins with the UE connected via a Radio Bearer & S1/S4 bearer (GTP/PMIP tunnel). The steps are: 1. Virtual Point-to-Point Link Creation; 2. Handover Request; 3. Create Session Request / Proxy Binding Update; 4. IP-CAN Session Establishment Procedure (repeated for each PDN connection to same APN); 5. Update PDN GW Address; 6. Create Session Response / Proxy Binding Ack; 7. GTP/PMIP Tunnel; 8. Handover Reply; 9. 3GPP EPS Bearer Release. + +Sequence diagram illustrating the handover from 3GPP Access to Trusted WLAN Access. The diagram shows the interaction between UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with the UE connected via a Radio Bearer & S1/S4 bearer (GTP/PMIP tunnel). The handover steps are: 1. Virtual Point-to-Point Link Creation; 2. Handover Request; 3. Create Session Request / Proxy Binding Update; 4. IP-CAN Session Establishment Procedure (repeated for each PDN connection to same APN); 5. Update PDN GW Address; 6. Create Session Response / Proxy Binding Ack; 7. GTP/PMIP Tunnel; 8. Handover Reply; 9. 3GPP EPS Bearer Release. + +**Figure 8.2.2.1.7-1: Handover from 3GPP Access to Trusted WLAN Access** + +In a second execution step, the UE explicitly requests handover of a PDN connection to a specific APN as per the following steps depicted in Figure 8.2.2.1.7-1 for GTP-based S2a and Figure 8.2.2.1.7-2 for PMIP-based S2a: + +0. The UE is connected in the 3GPP Access and has a GTP or PMIP tunnel on the S5/S8 interface. +1. The UE creates a WLAN virtual IP interface corresponding to the APN towards which it desires to handover a PDN connection. +2. The UE requests handover of the PDN connection from the 3GPP access to this WLAN virtual interface by sending a DHCP and/or DHCPv6 request message from this WLAN virtual interface that contains a handover indication for the PDN connection. The handover indication consists of requesting allocation of the same IPv4 address than previously allocated for the PDN connection over the 3GPP access, or of an IPv6 address within the same IPv6 prefix than previously allocated for the PDN connection over the 3GPP access. The DHCP requests are transmitted over the virtual point-to-point link negotiated during authentication phase, i.e., the layer 2 frame carrying the DHCP is marked with the corresponding VLAN Id, or unicasted to the corresponding TWAG MAC address, or encapsulated with the corresponding GRE key. + +**NOTE:** The UE is not required to request re-allocation of all addresses it had previously been allocated over the 3GPP access; a single request for one of the addresses that were used over the 3GPP access is enough to signal a handover indication to the TWAG. The UE may however request allocation for as many addresses as it wishes. Hence for an IPv4v6 PDN connection the handover indication signalling may be based entirely on DHCPv4 with no use of DHCPv6. If that is the case the UE may configure with Stateless Address Autoconfiguration the same IPv6 address than previously allocated with Stateless Address Autoconfiguration for the PDN connection over the 3GPP access based on receiving from the TWAG the same IPv6 prefix in a router advertisement. + +3. When the TWAG receives the first DHCP IPv4 and/or IPv6 address allocation request with a handover indication over the virtual point-to-point link corresponding to a specific APN, it request the PDN GW handover of the corresponding GTP or PMIP tunnel for the PDN connection to that APN. This is done by sending a Create Session Request or Proxy Binding Update with the handover indication for each of the PDN connections to the same APN. In case of multiple PDN connections to a same APN, the steps 3-5 in + +(A) shall be repeated for each PDN connection to the same APN that is being transferred from 3GPP access to Trusted WLAN access. The steps in (A) can occur in parallel for each PDN connection.. + +4. The PDN GW initiates the IP-CAN Session Modification Procedure with the PCRF, as specified in TS 23.203 [19]. +5. The selected PDN GW informs the 3GPP AAA Server of its PDN GW identity and the APN corresponding to the UE's PDN Connection. The message includes information that identifies the PLMN in which the PDN GW is located. This information is registered in the HSS as described in clause 12. +6. The PDN GW returns a Create Session Response or a Proxy Binding Update message to the TWAG, including the IPv4 and/or IPv6 address(es) allocated for the UE. +7. The GTP or PMIP tunnel is set up between the TWAN and the PDN GW. +8. The TWAG then sends a DHCP reply to the UE with the IPv4 address and/or IPv6 address as re-allocated by the PDN GW. The UE can then continue to use the PDN connection via the WLAN virtual interface. + +#### 8.2.2.1.8 Handover from Trusted WLAN Access to 3GPP Access + +This procedure is as described in subclause 8.2.1.3 of TS 23.402 for GTP-based S5/S8, with the difference that there is a GTP tunnel instead of a PMIP tunnel in step 1 in case of GTP-based S2a, and that the resource allocation deactivation procedure initiated by the PDN GW in step 17 is as defined in clause 16.4 of TS 23.402, followed by the additional step of the UE then deleting the virtual IP interface for the virtual point-to-point link corresponding the PDN connection. + +#### 8.2.2.2 Impacts on existing nodes or functionality + +The UE shall support: + +- Creation and deletion of per-PDN/NSWO WLAN virtual interfaces for the chosen user plane multiplexing scheme (VLAN, or unicast L2) +- For IPv4 PDN connections: stateful address configuration mechanisms DHCP, DHCP Forcerenew, DHCP Forcerenew Nonce Authentication. +- For IPv4v6 PDN connections: stateful address configuration mechanisms DHCP, DHCP Forcerenew, DHCP Forcerenew Nonce Authentication, and/or DHCPv6. +- For IPv6 PDN connections: stateful address configuration mechanism DHCPv6 +- Enhanced EAP-AKA' method for negotiation of SaMOG phase 2 capabilities with the UE, and discovery of per-PDN user plane multiplexing identifier (VLAN Id, or TWAG MAC address) + +The TWAN shall support: + +- Creation and deletion of per-PDN/NSWO WLAN virtual interfaces for the chosen user plane multiplexing scheme (VLAN Id, or TWAG MAC address) +- For IPv4 PDN connections: stateful address configuration mechanisms DHCP, DHCP Forcerenew, DHCP Forcerenew Nonce Authentication. +- For IPv4v6 PDN connections: stateful address configuration mechanisms DHCP, DHCP Forcerenew, DHCP Forcerenew Nonce Authentication, and/or DHCPv6. +- For IPv6 PDN connections: stateful address configuration mechanism DHCPv6 +- Additional AVP for negotiation of SaMOG phase 2 capabilities with the AAA server, and discovery of per-PDN user plane multiplexing identifier (VLAN Id, or TWAG MAC address) + +The AAA server shall support: + +- Additional AVP for negotiation of SaMOG phase 2 capabilities with the TWAN, and discovery of per-PDN user plane multiplexing identifier (VLAN Id, or TWAG MAC address) +- Enhanced EAP-AKA' method for negotiation of SaMOG phase 2 capabilities with the UE, and discovery of per-PDN user plane multiplexing identifier (VLAN Id, or TWAG MAC address) + +### 8.2.2.3 Evaluation + +The following aspects are considered and evaluated for the solution: + +- i) Impacts to existing network deployment: + - a) There is no requirement for WLAN APs compared to Rel-11. + - b) The TWAG shall support the point-to-point link multiplexing, the EAP-AKA enhancements, and the binding of an IPv4 and/or IPv6 session(s) for stateful address configuration with a PDN connection. +- ii) Impacts to UE: + - a) The UE shall support the point-to-point link multiplexing, the AAA enhancements, and the binding of an IPv4 and/or IPv6 session(s) for stateful address configuration with a PDN connection. +- iii) Impacts to 3GPP protocols/extensions (e.g. EAP AKA'): + +The following protocols are extended: + + - a) EAP-AKA is extended with UE network capability negotiation and PDN point-to-point link management (APN, PDN type, point-to-point link identifiers) + - b) STa protocol is extended with UE network capability negotiation and PDN point-to-point link management (APN, PDN type, point-to-point link identifiers). +- iv) Impacts to protocols defined by other SDOs (e.g. DHCP): + +No impact on other SDOs. +- v) Control plane + - a) The latency/load of first PDN connection is as for phase 1 SaMOG, i.e., EAP-AKA based authentication and IP layer address configuration. The latency/load of additional PDN connections is less as it only requires IP layer configuration. + - b) There is impact on the AAA server as it needs to be enhanced with the EAP-AKA extensions and the STa extensions. +- vi) Compliance to clause 8.1 SaMOG phase-2 system requirements: + - a) Co-existence with Rel-11 SaMOG + - b) Support for IP address preservation during handover + - c) Simultaneous support for S2a EPC-routed and NSWO; support of simultaneous multiple PDN connections +- vii) Other functional limitations: + - a) Limitation on the number of point-to-point links to specific APNs that can be negotiated – but no different from limit on number of bearers on 3GPP access. + - b) Limitation that APNs the UE will connect to have to be known prior to WLAN authentication phase. Were it not the case, connection to an unforeseen APN when the UE is already authenticated to WLAN would + +require UE to disconnect and reconnect to the WLAN such that the new APN can be negotiated in EAP-AKA authentication. The UE disconnecting and reconnecting from WLAN may cause the UE to release existing PDN connections anchored over the TWAN. + +## 8.2.3 Solution 3: Stateful DHCP-based Solution + +### 8.2.3.1 Functional Description + +Editor's Notes: It should be described whether and how the solution fulfils the requirements in Subclause 8.1. + +NOTE: The solution does not support stateless auto-configuration DHCPv6. + +#### 8.2.3.1.1 Functional Overview and Overall System Impacts + +##### 8.2.3.1.1.1 Overview + +The following table summarizes the proposed solution with respect to the Rel-12 SaMOG system requirements. + +| Table | Requirements | | Solution | +|-----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Co-exist with the SaMOG Release 11 solution | <ul style="list-style-type: none"> <li>• R12 UE interworks with Rel-11 TWAN and vice versa</li> <li>• R12 TWAN supports both R11 and R12 UEs attaching to the same TWAG</li> <li>• 3GPP AAA updates PDN GW identification to support HO operation for Rel-12 UE</li> </ul> | <p>Supports UE Rel-12 capability Indication obtained from EAP-AKA'</p> <p>Based on prior detection of the UE's release version during the capability negotiation, 3GPP AAA determines whether to update PDN GW identification to support HO operation for Rel-12 UE</p> | +| Multiple simultaneous PDN connections over Trusted WLAN including the simultaneous support Non-seamless WLAN offload (NSWO) | Control Plane | | Via DHCP request message to trigger additional PDN connection establishment. | +| | User Plane compatible with existing PDN connections | | <ul style="list-style-type: none"> <li>• User data for Multiple EPC-routed PDN connections can be separated by GRE tunnel.</li> <li>• Differentiate NSWO traffic from EPC-routed connection(s) without GRE tunnel</li> <li>- Supporting NSWO, IPv4, IPv6 and dual-stack as specified in DHCP request and permitted by the 3GPP UE's subscription policy</li> </ul> | +| IP address preservation | Signalling handover indication for IP address preservation to TWAN and the IP address | | TWAN determines UE requirement of IP address preservation by special indication in DHCP request message | +| Signalling the requested APN over Trusted WLAN | | | UE signals APN using DHCP request message | + +##### 8.2.3.1.1.1 - : Solution overview + +#### 8.2.3.1.1.2 UE Impacts + +For the purpose of accessing a Trusted Non-3GPP WLAN Access, the UE will be modified with the following enhancements with respect to Rel-11 UE: + +- Control Plane: + - Incorporate the requested APN, uplink GRE key, and HO indication in DHCP request message to communicate with TWAN/EPC. + - Support SAMOG phase 2 capabilities exchange and negotiation with TWAN during the EAP Authentication and Authorization operation. + - Indicate the desired connectivity service (NSWO access/ PDN connection), and receive the indication via DHCP response message. + +- Support IPv4, IPv6 and dual-stack PDN connection corresponding to the UE's subscription policy with its operator + - Support hand-over and release specific PDN connection or multiple PDN connections. + - Set-up and release the NSWO access. + - Support multiple simultaneous (TWAN) connectivity services i.e. both EPC-routed and NSWO simultaneously. + - Decide on the unique downlink GRE key for the EPC-routed traffic across all the PDN connections and sent it to TWAN, and also track the uplink GRE key that is assigned by the TWAN +- User Plane: +- Encapsulate and decapsulate GRE-over-IP tunnel for its EPC-routed PDN connection + - Simultaneous support for EPC-routed and NSWO traffic + +#### 8.2.3.1.1.3 Trusted WLAN Access Gateway Impacts + +The Trusted WLAN Access Gateway is enhanced with respect to Rel-11 TWAG with the following functions: + +- Control Plane: +- Support the TWAN side of the operations corresponding to UE's operation as described in clause 8.2.3.1.1.2 above. + - Binding the PDN connection for S2a GTP/PMIP tunnel. +- User Plane: +- Enforces routing of packets between the PDN connection and the GTP/PMIP tunnel for that UE. + - Encapsulate and decapsulate GRE-over-IP tunnel for its EPC-routed PDN connection + - Simultaneous support for EPC-routed and NSWO traffic + +#### 8.2.3.1.1.4 Trusted WLAN Access Point Impacts + +None + +#### 8.2.3.1.1.5 Trusted WLAN Backhaul Impacts + +Same as SaMOG Rel-11 + +### 8.2.3.1.2 Control Plane Management + +#### 8.2.3.1.2.1 UE-Network Capability Negotiation + +The UE negotiates SaMOG phase 2 capabilities with its serving TWAN during its EAP Authentication and Authorization operation. The TWAN sends UE requested SaMOG phase 2 capabilities and local TWAN configuration policies (i.e. whether supporting NSWO and/or EPC-routed) to the 3GPP AAA server over STa interface. The 3GPP AAA server takes a decision on whether or not the capabilities may apply to the UE session on the TWAN based on UE's subscription policy and local TWAN policies. + +#### 8.2.3.1.2.2 Connection related control plan interface + +DHCP protocol is used as the connection related control plane interface between the UE and the TWAG. It is the control plane protocol for UE to trigger the setup/maintain and release of any PDN or NSWO access among multiple connections: + +- Allows the UE to set-up (or Handover) and release a specific PDN or multiple PDNs. +- Allows the UE to set-up and release the NSWO access. + +NOTE 1: For DHCPv4 Forcerenew message used for releasing an individual PDN, RFC6704 [27] “DHCP Forcerenew nonce authentication” shall be used to provide secure client/server signaling exchange . + +NOTE 2: For DHCPv6, RFC 3315 [23] specifies security mechanism to protect client/server signaling exchange . + +- Allows the UE to have multiple simultaneous (TWAN) connectivity services. +- Allows the UE to indicate the desired connectivity service (NSWO access/PDN), whether an initial attach or a handover is required, the PDN type, etc. + +NOTE 3: 3GPP Vendor-specific Information that has been assigned by IETF for 3GPP for DHCPv4 and DHCPv6 can be used to provide DHCP enhancement as required by this solution. Hence, there is no impact to IETF. + +### 8.2.3.1.3 User plane management + +Basic assumption of SaMOG is to have point-to-point underlying transport between the UE and TWAG within the TWAN. However, when emulating multiple S2a PDNs support over TWAN, it is possible that several UE's serving PDN GWs could allocate the same private IP(v4) address to an UE. Hence, a user plane connection identifier is required to support multiplexing multiple PDNs over the point-to-point link between the UE and the TWAG to support TWAN connectivity service i.e. EPC-routed traffic. + +In the following two subsections, two alternatives are proposed for the user plane connection identifier. + +**Editor's Notes: For which of these two alternatives needs to be chosen is FFS.** + +#### 8.2.3.1.3.1 Alternative 1: GRE over IP + +##### 8.2.3.1.3.1.1 Point-to-point link model and multiple PDN connections support + +In this alternative, a unique pair of per-UE based GRE Keys in the uplink and in downlink direction is required for differentiating individual PDN. + +As there is no need to manage bearers over the WLAN access, a GRE Key at the user plane interface between the UE and the TWAG, corresponds to an entire PDN. When different GTP-u bearers are used on S2a for a given PDN, it is the same mechanism used in Rel-11 SaMOG to determine the GTP-u bearer to be used to carry a given packet i.e. the usage of UL-TFT at the UE and DL-TFT at the PGW. + +NOTE 1: The figures in the following sections depict the case of a PDN using a single bearer over S2a. + +![Diagram of point-to-point link model for PDN and NSWO access based on distinct GRE Key. It shows traffic flow from Application/Service Layer through PDN to GRE Keys, then to UE and PDN GW via AP/WLC and TWAG components, with NSWO access.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +The diagram illustrates a network architecture for point-to-point links. At the top, an oval labeled 'Application / Service Layer' is connected to 'UL Traffic Flow Aggregates' and 'DL Traffic Flow Aggregates'. These aggregates lead to 'PDN --> GRE Key' labels. Below this, a 'PDN' label is present. The main part of the diagram shows a sequence of components: 'UE' (User Equipment) on the left, 'AP/WLC' (Access Point/Wireless LAN Controller) in the middle-left, 'TWAG' (TWAN Access Gateway) in the middle-right, and 'PDN GW' (PDN Gateway) on the right. Arrows indicate traffic flow from the UE through the AP/WLC and TWAG to the PDN GW. A dashed oval labeled 'NSWO' is shown below the TWAG. A label '802 Flow UE-MAC ↔ TWAG-MAC' is positioned between the UE and TWAG. Another label 'GRE Key ↔ S2a-TEID' is shown above the TWAG. A label 'S2a Bearer' is at the bottom right. The diagram uses various colored boxes and arrows to represent different types of traffic and connections. + +Diagram of point-to-point link model for PDN and NSWO access based on distinct GRE Key. It shows traffic flow from Application/Service Layer through PDN to GRE Keys, then to UE and PDN GW via AP/WLC and TWAG components, with NSWO access. + +**Figure 8.2.3.1.3.1.1-1: Point-to-point link model for PDN and NSWO access based on distinct GRE Key** + +As depicted in the Figure 8.2.3.1.3.1.1-1 above, there are separate uplink and downlink GRE Keys. The virtual point-to-point link corresponding to a given connectivity service is realized as enforcing the packet forwarding of uplink and downlink traffic from different PDNs of which the IP packets are identified by specific GRE Key. + +The solution described above supports one or multiple PDN(s) corresponding with one or more APN(s). + +**8.2.3.1.3.1.2 GRE over IP tunneling establishment** + +It is assumed that a given 3GPP UE is always hosted by only one TWAG within the TWAN. Both the UE and the TWAG guarantees the uniqueness of GRE Key across all the 3GPP UE's PDNs. Each PDN is identified by both uplink GRE Key and downlink GRE Key. + +Figure 8.2.3.1.3.1.2 -1 shows the user data encapsulated in GRE tunnel. + +![Sequence diagram showing encapsulation of UE EPC-routed traffic in GRE tunnels. The diagram illustrates four traffic paths: Tunnel A (EPC-routed) for UE1, Tunnel C (EPC-routed) for UE2, NSWO for UE2, and a native local IP addressing path for UE2. Each path shows the flow of traffic from the UE through the TWAG to the PDN GW, with specific GRE keys assigned for each tunnel.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +The diagram illustrates the encapsulation of UE EPC-routed traffic in GRE tunnels across four scenarios: + +- Tunnel A EPC-routed:** UE1 sends traffic with local IP A@UE1, served by TWAG1 with IP A@TWAG1. The traffic is encapsulated in a GRE tunnel with key-i for uplink and key-i for downlink, passing through TWAG2 to PDN GW1 (APN1). +- Tunnel C EPC-routed:** UE2 sends traffic with local IP C@UE2, served by TWAG2 with IP C@TWAG2. The traffic is encapsulated in a GRE tunnel with key-k for uplink and key-k for downlink, passing through PDN GW2 (APN2). +- NSWO:** UE2 sends traffic with local IP D@UE2, served by TWAG2 with IP D@TWAG2. This traffic uses no GRE key and native local IP addressing, passing through PDN GW2 (APN2). + +Key components and labels in the diagram: + +- UE1, UE2:** User Equipment. +- TWAG1, TWAG2:** Traffic Offloading and Aggregation Gateways. +- PDN GW1 (APN1), PDN GW2 (APN2):** PDN Gateways. +- Tunnel A EPC-routed:** Blue shaded area representing the tunnel for UE1. +- Tunnel C EPC-routed:** Yellow shaded area representing the tunnel for UE2. +- GRE Keys:** [uplink GRE key-i, down GRE key-i], [uplink GRE key-j, down GRE key-j], [uplink GRE key-k, down GRE key-k], [uplink GRE key-l, down GRE key-l]. +- IP Addresses:** [UE local IP-A@UE1, Serving UE TWAG's IP-A@TWAG1], [UE local IP-C@UE2, Serving UE TWAG's IP-C@TWAG2], [UE local IP-D@UE2, Serving UE TWAG's IP-D@TWAG2]. + +Sequence diagram showing encapsulation of UE EPC-routed traffic in GRE tunnels. The diagram illustrates four traffic paths: Tunnel A (EPC-routed) for UE1, Tunnel C (EPC-routed) for UE2, NSWO for UE2, and a native local IP addressing path for UE2. Each path shows the flow of traffic from the UE through the TWAG to the PDN GW, with specific GRE keys assigned for each tunnel. + +**Figure 8.2.3.1.3.1.2-1: Encapsulation of UE EPC-routed Traffic in GRE Tunnel** + +#### 8.2.3.1.3.2 Alternative 2: TWAG virtual MAC Address + +In this alternative, a TWAG virtual MAC address in the uplink and in downlink direction is required for differentiating individual PDN. + +As there is no need to manage bearers over the WLAN access, a TWAG virtual MAC address at the user plane interface between the UE and the TWAG, corresponds to an entire PDN. When different GTP-u bearers are used on S2a for a given PDN, it is the same mechanism used in Rel-11 SaMOG to determine the GTP-u bearer to be used to carry a given packet i.e. the usage of UL-TFT at the UE and DL-TFT at the PGW. On the UL direction, the TWAG uses both the source MAC address and the TWAG virtual MAC address to identify the S2a bearer on which the packet is to be forwarded. Two different UEs served by the same TWAG can share the same TWAG virtual MAC address. + +![Figure 8.2.3.1.3.2-1: Point-to-point link model for PDN and NSWO access based on TWAG VMAC. The diagram illustrates the traffic flow between a User Equipment (UE), an Access Point/Wireless LAN Controller (AP/WLC), a Trusted WLAN Access Gateway (TWAG), and a Packet Data Network Gateway (PDN GW). Uplink (UL) traffic flows from the Application/Service Layer through the UE, AP/WLC, and TWAG. Downlink (DL) traffic flows from the PDN GW through the TWAG, AP/WLC, and UE. Key mapping functions include APN/NSWO to VMAC and Source_MAC, TWAG VMAC for UL, and DL-TFT to S2a-TEID for DL. An S2a Bearer connects the TWAG and PDN GW. Non-Seamless WLAN Offload (NSWO) is also indicated.](5e9af8986a5845504f251d3079da8078_img.jpg) + +Figure 8.2.3.1.3.2-1: Point-to-point link model for PDN and NSWO access based on TWAG VMAC. The diagram illustrates the traffic flow between a User Equipment (UE), an Access Point/Wireless LAN Controller (AP/WLC), a Trusted WLAN Access Gateway (TWAG), and a Packet Data Network Gateway (PDN GW). Uplink (UL) traffic flows from the Application/Service Layer through the UE, AP/WLC, and TWAG. Downlink (DL) traffic flows from the PDN GW through the TWAG, AP/WLC, and UE. Key mapping functions include APN/NSWO to VMAC and Source\_MAC, TWAG VMAC for UL, and DL-TFT to S2a-TEID for DL. An S2a Bearer connects the TWAG and PDN GW. Non-Seamless WLAN Offload (NSWO) is also indicated. + +Figure 8.2.3.1.3.2-1: Point-to-point link model for PDN and NSWO access based on TWAG VMAC + +### 8.2.3.1.4 Protocol stack + +The following mobility protocols are supported over S2a: + +- GTP. +- PMIPv6. + +The link model as well as IPv4 address and IPv6 prefix allocation considerations are equally valid for GTP and PMIPv6 S2a options. + +The figure below illustrates the control plane for Tunnel Management and the user plane for GTP option. + +![Diagram showing the Control Plane and User Plane protocol stacks for Tunnel Management. The Control Plane stack includes L3 trigger, 802.11, GTP-C, UDP, IP, and L2/L1 across UE, TWAN, and PDN GW. The User Plane stack includes IPv4/IPv6, GRE, GTP-U, UDP, IP, MAC/L1, and L2/L1 across UE, TWAN, and PDN GW.](879d68959f0c0ba370ef82447298ba17_img.jpg) + +| | | | | +|------------|--|-------|--| +| L3 trigger | | GTP-C | | +| 802.11 | | UDP | | +| | | IP | | +| | | L2/L1 | | + +UE     TWAN     PDN GW + +**Control Plane for Tunnel Management** + +| | | | +|-----------|--------|-----------| +| IPv4/IPv6 | | IPv4/IPv6 | +| | GRE | GTP-U | +| | IP | UDP | +| | MAC/L1 | IP | +| | | L2/L1 | + +UE     TWAN     PDN GW + +**User Plane for Tunnel Management** + +Diagram showing the Control Plane and User Plane protocol stacks for Tunnel Management. The Control Plane stack includes L3 trigger, 802.11, GTP-C, UDP, IP, and L2/L1 across UE, TWAN, and PDN GW. The User Plane stack includes IPv4/IPv6, GRE, GTP-U, UDP, IP, MAC/L1, and L2/L1 across UE, TWAN, and PDN GW. + +**Legend:** + +**802.11:** This refers to Layer 1 and Layer 2 defined by IEEE Std 802.11-2007 [5]. + +**L3 trigger:** This refers to DHCPv4/DHCPv6 which is used as mandatory attach trigger. + +**GRE:** The GRE tunnels user data between UE and the Trusted WLAN Access Gateway over the SWw interface, which identifies specific the data per PDN connection by different GRE key. + +**GTP-C:** The GPRS Tunnelling Protocol control plane consists of signalling messages between the Trusted WLAN Access Gateway and the PDN- GW over the S2a interface. It is defined in TS 29.274 [25]. + +**GTP-U:** The GPRS Tunnelling Protocol user plane tunnels user data between the Trusted WLAN Access Gateway and the PDN GW over the S2a interface. It is defined in TS 29.281 [26]. + +**UDP:** This is the transport layer protocol onto which both GTP-C and GTP-U are layered. + +#### Figure 8.2.3.1.4-1: Link Model for GTP-based S2a + +When PMIP based S2a is used with Trusted WLAN, the PMIPv6 protocol stacks described in TS 23.402 clause 6.1.1 apply. + +##### 8.2.3.1.5 IP addressing support for SaMOG phase-2 + +This clause describes the IP addressing support for SaMOG phase-2 based on the stateful DHCP-based solution. The main scenarios for IP address/prefix assignment to UE are: + +- The IP address allocated by TWAN which is used for NSWO access +- The IP address allocated by TWAN for GRE over IP tunnelling the EPC routed traffic, +- The IPv4 address/IPv6 prefix allocated by PGW which is used for EPC routed. + +###### 8.2.3.1.5.1 IP address assignment for NSWO + +If the requested connectivity is for NSWO and the NSWO connectivity is allowed by the user subscription, the TWAN shall assign a NSWO IP address or prefix via DHCPv4 or DHCPv6 procedures. + +###### 8.2.3.1.5.2 IP address assignment for GRE over IP tunnel + +In the case when additional PDN connection is requested, and the multiple PDN connectivity is allowed, the TWAN shall assign the tunnel IP address via DHCPv4 if TWAN support IPv4; otherwise, the TWAN supports IPv6, the UE may generate link local address to be used for GRE over IP tunnelling. + +###### 8.2.3.1.5.3 IP address assignment for EPC-routed + +The IPv4 address and/or IPv6 prefix is allocated to the UE by PDN GW or external PDN when a new PDN connection is established. In order to enable IPv4 or IPv6 connectivity, the TWAN shall support DHCPv4 and DHCPv6 server functionality for IP parameter configuration and IPv4 address and/or IPv6 prefix allocation as specified in IETF RFC 2131 [9] and IETF RFC 3315 [23]. + +The way that the UE sets the requested PDN type is as specified in sub-clause 5.3.1.1 of 3GPP TS 23.401 [6]. + +The following IP address allocation procedure applies to the following conditions accordingly: + +- If the requested PDN type is allowed by the user subscription, the TWAN requests the PDN connectivity towards EPC as requested. +- If the requested PDN type is IPv4v6, but the subscription data allows only PDN type IPv4 or only PDN type IPv6, the TWAN requests IPv4 address or IPv6 prefix in the Proxy Binding Update or GTP Create Session Request from the PDN GW according to the subscribed value. The TWAN shall return the assigned PDN type to the UE. In this case the UE shall not request another PDN connection to the same APN for the other IP version. The IPv4 address or IPv6 prefix is delivered to the TWAN during the PMIPv6 or GTP tunnel establishment. + - When the UE requests the IPv4 address via DHCPv4, and if the subscription data allows PDN type IPv4, the TWAN delivers the received IPv4 address to the UE within DHCPv4 signalling after the PMIPv6 or GTP tunnel is established between the TWAN and the PDN GW. Otherwise, the subscription data allows only PDN type IPv6, TWAN will reject the request with a cause value that PDN type IPv6 only. + +- b). When the UE requests the IPv6 prefix via DHCPv6, and if the subscription data allows PDN type IPv6, the TWAN delivers the received IPv6 address to the UE within DHCPv6 signalling after the PMIPv6 or GTP tunnel is established between the TWAN and the PDN GW. Otherwise, the subscription data allows only PDN type IPv4, TWAN will reject the request with a cause value that PDN type IPv4 only. +- If the requested PDN type is IPv4 or IPv6, and if either the requested PDN type or PDN type IPv4v6 are subscribed, the TWAN requested the PDN connectivity from the PDN GW as requested. Otherwise the requested PDN connection request is rejected with the appropriate cause value. + - If the requested PDN type is IPv4v6, and both IPv4 and IPv6 PDN types are allowed by subscription but not IPv4v6, the TWAN shall decide for which the PDN type that it will request and such decision is operator's implementation decision. + +### 8.2.3.2 Procedures + +*Editor's Note: The call flows are described in this subclause.* + +#### 8.2.3.2.1 Initial Attach in WLAN on S2a + +##### 8.2.3.2.1.1 Initial Attach in WLAN on GTP/PMIP S2a + +![Sequence diagram for Initial Attach in WLAN on GTP/PMIP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The sequence starts with '1. Non-3GPP Specific Procedures' between UE and TWAN. Step 2 shows EAP Authentication between UE and TWAN, and Authentication & Authorization between TWAN and HSS/AAA. Step 3 is DHCP Discover/ Solicit from UE to TWAN. Step 4 is Create Session Request/PBU from TWAN to PDN GW. Step 5 is a dashed box for 'IP-CAN Session Establishment Procedure' between PDN GW and AAA Proxy. Step 6 is Update PDN GW Address from AAA Proxy to PDN GW. Step 7 is Create Session Response/PBA from PDN GW to TWAN. Step 8 is a green bar labeled 'GTP Tunnel' between TWAN and PDN GW. Steps 9a, 9b, 10a, and 10b show DHCP Offer, Advertise, Request/DHCP Ack, and Request/ Reply between UE and TWAN.](007fefafb4fcbdb7d388209f63a0ba5d_img.jpg) + +Sequence diagram for Initial Attach in WLAN on GTP/PMIP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The sequence starts with '1. Non-3GPP Specific Procedures' between UE and TWAN. Step 2 shows EAP Authentication between UE and TWAN, and Authentication & Authorization between TWAN and HSS/AAA. Step 3 is DHCP Discover/ Solicit from UE to TWAN. Step 4 is Create Session Request/PBU from TWAN to PDN GW. Step 5 is a dashed box for 'IP-CAN Session Establishment Procedure' between PDN GW and AAA Proxy. Step 6 is Update PDN GW Address from AAA Proxy to PDN GW. Step 7 is Create Session Response/PBA from PDN GW to TWAN. Step 8 is a green bar labeled 'GTP Tunnel' between TWAN and PDN GW. Steps 9a, 9b, 10a, and 10b show DHCP Offer, Advertise, Request/DHCP Ack, and Request/ Reply between UE and TWAN. + +**Figure 8.2.3.2.1.1-1: Initial attachment in WLAN on GTP/PMIP S2a for roaming, LBO and non-roaming scenarios** + +The scenario is defined as the TWAN using the layer 3 attach request, including a DHCPv4 or DHCPv6 message, sent by the UE as the attach trigger. + +1. The step is same as step 1 in TS 23.402 [3] clause 16.2.1. + +2. In this step, the UE indicates its capability (i.e. Rel-12 SaMOG capability) to the AAA server during the authentication procedure. Based on the UE capability provided by AAA server, the TWAN decides to use L3 trigger. +3. The UE shall send a DHCPv4 Discover as per IETF RFC 2131 [9], or DHCPv6 Solicit as per IETF RFC 3315[23] to TWAN, including the following information, + - The requested APN + +- An indication on the requested access (EPC via S2a access or the use of NSWO access) +- And in the former case, an APN optionally. +- For alternative 1, downlink GRE key may be inserted in 3GPP Vendor Specific information for IPv4, IPv6 or IPv4v6 connection. +- Requested PDN type – one of IPv4, IPv6 or IPv4v6 + +Based on HSS/AAA authorization and the received UE EPC/NSWO access indication whether or not to establish S2a, TWAN can decide to allow EPC access or not. All the UE traffic through the TWAG is blocked unless the UE is granted NSWO/PDN access. The following steps 4-8 proceed according to the considerations below. + +If UE doesn't provide an APN to TWAN, then: + +- A. If the TWAN decides NSWO access, steps 4-8 below are skipped. Instead, the TWAN assigns an IPv4 address and/or IPv6 address from its local address pool to the UE (depending on the L3 attach request in step 3) and the NSWO traffic will be forwarded/received without traversing EPC. +- B. If the TWAN decides S2a access, the TWAN assigns an IPv4 address and/or IPv6 address from its local address pool to the UE (depending on the L3 attach request in step 3). The TWAN shall request to PDN GW for an IPv4 address and/or IPv6 address and PDN GW shall return an IPv4 address and/or IPv6 address to the TWAN during steps 4-8. + +If UE provides its requested APN to TWAN, and the TWAN determines that S2a shall be established, the TWAN assigns an IPv4 address and/or IPv6 address from its local address pool to the UE (depending on the L3 attach request in step 3). The TWAN proceeds according to steps 4-8 below. + +4. TWAN decides PDN type according to requested PDN type and subscribed PDN type from HSS, and sets the Dual Address Bearer Flag when the PDN type is set to IPv4v6. The TWAN sends a Create Session Request/PBU message to the PDN GW, including PDN type, Dual Address Bearer Flag. +5. The step is same as step 10 in TS 23.402[3] clause 16.2.1. +6. The 3GPP AAA Server decides whether or not to update PDN GW identification according to the UE capability, which has been provided at the authentication phase. If the UE supports IP address preservation, the 3GPP AAA Server shall update PDN GW identity towards the HSS. +- 7-8. These steps are the same as steps 6-7 in TS 23.402[3] clause 16.2.1. If Dual Address Bearer Flag is set, the PDN GW shall return IPv4 address and IPv6 address to TWAN. +- 9a. For DHCPv4, TWAN returns DHCP offer message to UE, TWAG virtual MAC address is included if alternative 2 is used. +- 9b. For DHCPv6, TWAN returns Advertise message to UE, TWAG virtual MAC address is included if alternative 2 is used. +- 10a. UE sends DHCP Request (for DHCPv4) to TWAN, and TWAN returns DHCP Ack message to the UE, including the indication on whether EPC access or NSWO access has been granted to the UE and UE IP allocated by PDN GW. + - (a) Alternative 1: For EPC access, GRE tunnelling information is included to UE, where GRE tunnel information includes uplink GRE key and UE's local IP address which are allocated by TWAN for tunnelling data for the given PDN. For NSWO, GRE tunnelling information isn't required. + - (b) Alternative 2: Both UE and TWAN maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address. For NSWO, no dedicated virtual MAC address is needed. + +All NSWO traffic and control messages between UE and TWAG use TWAG's MAC address. 10b. UE sends Request (for DHCPv6) to TWAN, and TWAN returns Reply message to the UE, including the indication on whether EPC access or NSWO access has been granted to the UE and UE IP allocated by PDN GW. + +- (a) Alternative 1: For EPC access, GRE tunnelling information is included to UE where GRE tunnel information includes uplink GRE key and UE's local IP address which are allocated by TWAN for tunnelling data for the given PDN. For NSWO, GRE tunnelling information isn't required.. +- (b) Alternative 2: Both UE and TWAN will maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address. For NSWO, no dedicated virtual MAC address is needed. + +All NSWO traffic and control messages between UE and TWAG are using TWAG's MAC address. When PDN type is IPv4, steps 9a and 10a apply. + +When PDN type is IPv6, steps 9b and 10b apply. + +When PDN type is IPv4v6, there are two subsequent cases: + +- Alternative 1: + - 1) If UE requests IPv4 address first, TWAN shall implement steps 9a and 10a and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send solicit message encapsulated by the GRE key which is allocated in step 10a to TWAN, TWAN and UE shall implement steps 9b and 10b which are encapsulated by the GRE key which is allocated in step 10a. + - 2) If UE requests IPv6 address first, TWAN shall implement steps 9b and 10b and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message encapsulated by the GRE key which is allocated in step 10b to TWAN, TWAN and UE shall implement steps 9a and 10a which are encapsulated by the GRE key which is allocated in step 10b. +- Alternative 2: + - 1) If UE requests IPv4 address first, TWAN shall implement steps 9a and 10a and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send solicit message with TWAG virtual MAC address which is allocated in step 9a to TWAN, TWAN and UE shall implement steps 9b and 10b. + - 2) If UE requests IPv6 address first, TWAN shall implement steps 9b and 10b and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message with TWAG virtual MAC address which is allocated in step 9b to TWAN, TWAN and UE shall implement steps 9a and 10a. + +##### 8.2.3.2.2 UE-initiated Connectivity to Additional PDN + +##### 8.2.3.2.2.1 UE-initiated Connectivity to Additional PDN on GTP S2a + +![Sequence diagram illustrating UE-initiated connectivity to additional PDN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with a DHCP Discover/Solicit (APN) from UE to TWAN, followed by a Create Session Request from TWAN to PDN GW. The PDN GW then initiates the IP-CAN Session Establishment Procedure (dashed box) involving vPCRF, AAA Proxy, and hPCRF. The PDN GW sends an Update PDN GW Address to HSS/AAA. The PDN GW then sends a Create Session Response to TWAN, which establishes a GTP Tunnel (highlighted in green). Finally, the UE sends a DHCP Request/DHCP Ack to TWAN, and the TWAN sends a Request/Reply to the UE.](d244183a8ff3d94b0dcf30140f51020d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW: Roaming Scenarios + + UE->>TWAN: 1. DHCP Discover/ Solicit (APN) + TWAN->>PDN_GW: 2. Create Session Request + PDN_GW-->>vPCRF: 3. IP-CAN Session Establishment Procedure + PDN_GW-->>AAA_Proxy: 3. IP-CAN Session Establishment Procedure + PDN_GW-->>hPCRF: 3. IP-CAN Session Establishment Procedure + PDN_GW->>HSS_AAA: 4. Update PDN GW Address + PDN_GW-->>TWAN: 5. Create Session Response + Note right of TWAN: 6. GTP Tunnel + TWAN-->>UE: 7a. DHCP Offer + TWAN-->>UE: 7b. Advertise + UE->>TWAN: 8a. DHCP Request/DHCP Ack + TWAN-->>UE: 8b. Request/ Reply + +``` + +Sequence diagram illustrating UE-initiated connectivity to additional PDN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with a DHCP Discover/Solicit (APN) from UE to TWAN, followed by a Create Session Request from TWAN to PDN GW. The PDN GW then initiates the IP-CAN Session Establishment Procedure (dashed box) involving vPCRF, AAA Proxy, and hPCRF. The PDN GW sends an Update PDN GW Address to HSS/AAA. The PDN GW then sends a Create Session Response to TWAN, which establishes a GTP Tunnel (highlighted in green). Finally, the UE sends a DHCP Request/DHCP Ack to TWAN, and the TWAN sends a Request/Reply to the UE. + +**Figure 8.2.3.2.2.1-1: UE-initiated connectivity to additional PDN from Trusted WLAN Access with GTP** + +The scenario is defined as the TWAN using the layer 3 attach request, including DHCPv4 or DHCPv6 message, sent by the UE as the PDN trigger. NSWO is a special PDN. + +For DHCPv4 messaging and security handling, RFC 6704 shall be applied. + +1. The UE shall send layer 3 attach request to the TWAN, (e.g. a DHCPv4 discover as per IETF RFC 2131 [9], DHCPv6 Solicit as per IETF RFC3315 [23]), including requested APN, requested PDN type and an indication on the requested access (EPC via S2a access or the use of NSWO access), and for alternative 1, the downlink GRE key if EPC via S2a access. + +If UE doesn't send UE requested APN to TWAN, the TWAN determines whether or not to grant NSWO connectivity based on the authorization result during initial attach: + +- If TWAN determines NSWO and there isn't a existing NSWO access, TWAN forwards the traffic without traversing EPC. Otherwise, the NSWO access isn't allowed. +- If UE provides its requested APN to TWAN, and the TWAN determines that S2a shall be established, the TWAN proceeds according to steps 2-6 below. + +2. TWAN decides PDN type according to requested PDN type and subscribed PDN type from HSS, and sets the Dual Address Bearer Flag when the PDN type is set to IPv4v6. The TWAN sends a Create Session Request message to the PDN GW, including PDN type, Dual Address Bearer Flag. +3. The step is same as step 10 in TS 23.402[3] clause 16.2.1. +4. The 3GPP AAA Server decides whether or not to update PDN GW identification according to the UE capability, which has been provided at the authentication phase. If the UE supports IP address preservation, the 3GPP AAA Server shall update PDN GW identity towards the HSS. +- 5-6. These steps are the same as steps 6-7 in TS 23.402[3] clause 16.2.1. If Dual Address Bearer Flag is set, the PDN GW shall return both IPv4 address and IPv6 address to TWAN. +- 7a. For DHCPv4, TWAN returns DHCP offer message to UE, TWAG virtual MAC address is included if alternative 2 is used. +- 7b. For DHCPv6, TWAG returns Advertise message to UE, TWAG virtual MAC address is included if alternative 2 is used. +- 8a. UE sends DHCP Request (for DHCPv4) to TWAN, and TWAN returns DHCP Ack message to the UE, including the indication on whether EPC access or NSWO access has been granted to the UE and UE's IP allocated by its serving PDN GW. + - 1) Alternative 1: For EPC access, GRE tunnelling information included to UE where GRE tunnel information includes uplink GRE key allocated by TWAN for tunnelling data for the given PDN. For NSWO, GRE tunnelling information isn't required. + - 2) Alternative 2: Both UE and TWAN maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address. For NSWO, no dedicated virtual MAC is needed. + +All NSWO traffic and control messages between UE and TWAG are using TWAG's MAC address. + +- 8b. UE sends Request (for DHCPv6) to TWAN, and TWAN returns Reply message to the UE, including the indication on whether EPC access or NSWO access has been granted to the UE and UE's IP address allocated by its serving PDN GW. + - 1) Alternative 1: For EPC access, GRE tunnelling information and UE's IP address allocated by its serving PDN GW are included to UE where GRE tunnel information includes uplink GRE key which is allocated by TWAN for tunnelling support in the case of multiple PDNs. For NSWO, GRE tunnelling information isn't required. + - 2) Alternative 2: Both UE and TWAN maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address etc.. For NSWO, no dedicated virtual MAC address is needed. + +All NSWO traffic and control messages between UE and TWAG are using TWAG's MAC address. + +When PDN type is IPv4, steps 7a and 8a apply. + +When PDN type is IPv6, steps 7b and 8b apply. + +When PDN type is IPv4v6, there are two following cases: + +- Alternative 1: + - 1) If UE requests IPv4 address first, TWAN shall implement steps 7a and 8a and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send solicit message encapsulated by the GRE key which is allocated in step 8a to TWAN, TWAN and UE shall implement steps 7b and 8b which are encapsulated by the GRE key which is allocated in step 8a. + - 2) If UE requests IPv6 address first, TWAN shall implement steps 7b and 8b and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message encapsulated by the GRE key which is allocated in step 8b to TWAN, TWAN and UE shall implement steps 7a and 8a which are encapsulated by the GRE key which is allocated in step 8b. +- Alternative 2: + +- 1) If UE requests IPv4 address first, TWAN shall implement steps 9a and 10a and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send solicit message with TWAG virtual MAC address which is allocated in step 9a to TWAN, TWAN and UE shall implement steps 9b and 10b. +- 2) If UE requests IPv6 address first, TWAN shall implement steps 9b and 10b and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message with TWAG virtual MAC address which is allocated in step 9b to TWAN, TWAN and UE shall implement steps 9a and 10a. + +##### 8.2.3.2.2.2 UE-initiated Connectivity to Additional PDN on PMIP S2a + +![Sequence diagram for UE-initiated connectivity to additional PDN on PMIP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains vPCRF, AAA Proxy, and hPCRF. The sequence starts with UE sending a DHCP Discover/Solicit (APN) to TWAN. TWAN sends a Proxy Binding Update to PDN GW. PDN GW initiates the IP-CAN Session Establishment Procedure (dashed box) involving vPCRF, AAA Proxy, and hPCRF. PDN GW sends an Update PDN GW Address to HSS/AAA. PDN GW sends a Proxy Binding Acknowledgement to TWAN. TWAN and UE establish a PMIP Tunnel (highlighted in green). Finally, UE sends DHCP messages (Offer, Advertise, Request/Ack, Reply) to TWAN.](f76f0f5dfff2511b51f6b875867c029f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW: Roaming Scenarios + + UE->>TWAN: 1. DHCP Discover/ Solicit (APN) + TWAN->>PDN_GW: 2. Proxy Binding Update + PDN_GW-->>vPCRF: 3. IP-CAN Session Establishment Procedure + PDN_GW-->>AAA_Proxy: 3. IP-CAN Session Establishment Procedure + PDN_GW-->>hPCRF: 3. IP-CAN Session Establishment Procedure + PDN_GW->>HSS_AAA: 4. Update PDN GW Address + PDN_GW->>TWAN: 5. Proxy Binding Acknowledgement + Note right of TWAN: 6. PMIP Tunnel + UE->>TWAN: 7a. DHCP Offer + UE->>TWAN: 7b. Advertise + UE->>TWAN: 8a. DHCP Request/DHCP Ack + UE->>TWAN: 8b. Request/ Reply + +``` + +Sequence diagram for UE-initiated connectivity to additional PDN on PMIP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains vPCRF, AAA Proxy, and hPCRF. The sequence starts with UE sending a DHCP Discover/Solicit (APN) to TWAN. TWAN sends a Proxy Binding Update to PDN GW. PDN GW initiates the IP-CAN Session Establishment Procedure (dashed box) involving vPCRF, AAA Proxy, and hPCRF. PDN GW sends an Update PDN GW Address to HSS/AAA. PDN GW sends a Proxy Binding Acknowledgement to TWAN. TWAN and UE establish a PMIP Tunnel (highlighted in green). Finally, UE sends DHCP messages (Offer, Advertise, Request/Ack, Reply) to TWAN. + +**Figure 8.2.3.2.2.2-1: UE-initiated connectivity to additional PDN from Trusted WLAN Access with PMIP** + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.2.1 above, with the following differences: + +- Step 2 is a Proxy Binding Update. The parameters in the Proxy Binding Update message are same as step 5 in clause 8.2.3.2.2.1. +- Step 5 is a Proxy Binding Acknowledgement. The parameters in the Proxy Binding Acknowledgement message are same as step 6 in clause 8.2.3.2.2.1. + +##### 8.2.3.2.3 Detach and PDN disconnection in WLAN on S2a + +##### 8.2.3.2.3.1 Detach and PDN disconnection in WLAN on GTP S2a + +###### 8.2.3.2.3.1.1 UE/TWAN requested single PDN Disconnection Procedure in WLAN on GTP S2a + +![Sequence diagram illustrating the UE/TWAN requested single PDN Disconnection Procedure in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains vPCRF, AAA Proxy, and hPCRF. The sequence of messages is: 1. DHCP release (UE to TWAN), 2. Delete Session Request (TWAN to PDN GW), 3. Update PDN GW Address (PDN GW to HSS/AAA), 4. PCEF-initiated IP-CAN Session Termination Procedure (PDN GW to AAA Proxy), 5. Delete Session Response (PDN GW to TWAN), 6. DHCP Reply (TWAN to UE), and 7. TWAN Specific resource release (TWAN internal process).](1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note left of UE: 7. TWAN Specific resource release + UE-->>TWAN: 1. DHCP release + TWAN->>PDN_GW: 2. Delete Session Request + PDN_GW->>HSS_AAA: 3. Update PDN GW Address + PDN_GW-->>AAA_Proxy: 4. PCEF-initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Delete Session Response + TWAN-->>UE: 6. DHCP Reply + +``` + +Sequence diagram illustrating the UE/TWAN requested single PDN Disconnection Procedure in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains vPCRF, AAA Proxy, and hPCRF. The sequence of messages is: 1. DHCP release (UE to TWAN), 2. Delete Session Request (TWAN to PDN GW), 3. Update PDN GW Address (PDN GW to HSS/AAA), 4. PCEF-initiated IP-CAN Session Termination Procedure (PDN GW to AAA Proxy), 5. Delete Session Response (PDN GW to TWAN), 6. DHCP Reply (TWAN to UE), and 7. TWAN Specific resource release (TWAN internal process). + +**Figure 8.2.3.2.3.1.1-1: UE/ TWAN requested single PDN Disconnection on GTP S2a** + +- If the PDN Type is IPv4, UE releases the IPv4 address using DHCPv4 release message or IPv4 address lease time expires in TS23.402 [3] clause 16.3. And if the PDN Type is IPv6, UE releases the IPv6 address using DHCPv6 release message or IPv6 address lease time expires. If the PDN Type is IPv4v6, UE shall releases the IPv4 address and IPv6 address by the first DHCP release session, i.e. DHCPv4 release message or DHCPv6 release message, with PDN Type for IPv4v6 is included in the message. + +###### - Alternative 1: + +For DHCPv4 release message, a specific GRE key or a client id is used for identifying specific PDN. + +For DHCPv6 release message, a specific GRE key or IAID is used for identifying specific PDN. + +###### - Alternative 2: + +For DHCPv4 release message, TWAG virtual MAC address is used for identifying specific PDN. + +For DHCPv6 release message, TWAG virtual MAC address is used for identifying specific PDN. + +If there is no traffic received from the UE for a configurable duration and the TWAN detects the UE has left based on unanswered probes (e.g., ARP Request, Neighbour Solicitation message), the TWAN triggers PDN disconnection. + +- After TWAN receives DHCP release message, it shall detect if the PDN supports IPv4v6 dual stack and PDN type for IPv4v6 is included in the message. If so, TWAN shall send delete session request message to PDN GW, in order to indicate PDN GW for deleting the PDN. Steps 3-5 are same as the steps 2-5 in TS23.402 [3] clause 16.3.1.1. + +- TWAN shall remove the associated contexts corresponding to specific PDN, and send Reply message to inform UE of removing associated contexts in the case of DHCPv6. + +- If TWAN requested Single PDN Disconnection, TWAN shall send a DHCPv4 FORCERENEW message as per IETF RFC 3203 [24] and RFC6704[27], and/or DHCPv6 Reconfigure message as per IETF RFC 3315 [23]. When the UE proceeds with renewing the address lease for single PDN, the TWAN shall in turn refuse the request and notify to the UE that the PDN has been disconnected. + +NOTE: For PDN type is IPv4v6, it is FFS. + +###### 8.2.3.2.3.1.2 UE/TWAN requested one IPv4 Address or one IPv6 address release for a dual stack PDN in WLAN on GTP S2a + +![Sequence diagram for UE/TWAN initiated release for one IPv4 Address or one IPv6 Address for dual stack PDN in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves a DHCP release from UE to TWAN, a Modify Bearer Request from TWAN to PDN GW1, a PCEF-initiated IP CAN Session Modification Procedure from PDN GW1 to PDN GW2, a Modify Bearer Response from PDN GW2 to PDN GW1, a DHCP Reply from PDN GW1 to TWAN, and a TWAN Specific resource release from TWAN to UE. The vPCRF, AAA Proxy, and hPCRF are grouped under 'Roaming Scenarios'.](d793cf7c174b89eb024d132f00679787_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW1 as PDN GW1 + participant PDN_GW2 as PDN GW2 + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note right of UE: 1. DHCP release + UE-->>TWAN: 1. DHCP release + Note right of TWAN: 2. Modify Bearer Request + TWAN->>PDN_GW1: 2. Modify Bearer Request + Note right of PDN_GW1: 3. PCEF-initiated IP CAN Session Modification Procedure + PDN_GW1->>PDN_GW2: 3. PCEF-initiated IP CAN Session Modification Procedure + Note right of PDN_GW2: 4. Modify Bearer Response + PDN_GW2->>PDN_GW1: 4. Modify Bearer Response + Note right of PDN_GW1: 5. DHCP Reply + PDN_GW1->>TWAN: 5. DHCP Reply + Note right of TWAN: 6. TWAN Specific resource release + TWAN->>UE: 6. TWAN Specific resource release + +``` + +Sequence diagram for UE/TWAN initiated release for one IPv4 Address or one IPv6 Address for dual stack PDN in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves a DHCP release from UE to TWAN, a Modify Bearer Request from TWAN to PDN GW1, a PCEF-initiated IP CAN Session Modification Procedure from PDN GW1 to PDN GW2, a Modify Bearer Response from PDN GW2 to PDN GW1, a DHCP Reply from PDN GW1 to TWAN, and a TWAN Specific resource release from TWAN to UE. The vPCRF, AAA Proxy, and hPCRF are grouped under 'Roaming Scenarios'. + +**Figure 8.2.3.2.3.1.2-1: UE/ TWAN initiated release for one IPv4 Address or one IPv6 Address for dual stack PDN in WLAN on GTP S2a** + +When the PDN Type is IPv4v6, UE shall release the IPv4 address using DHCPv4 release message or IPv4 address lease time expires in TS23.402 [3] clause 16.3, and release the IPv6 address using DHCPv6 release message or IPv6 address lease time expires separately. + +The scenario applies that UE/TWAN deletes one IPv4 address or one IPv6 address for a Dual Stack PDN first, and subsequently, UE/TWAN deletes the PDN. + +1. UE sends DHCPv4 release message to TWAN if UE releases IPv4 address first, including PDN Type for IPv4. + +- Alternative 1: + +Specific GRE key or client id is used for identifying specific PDN to be deleted, and TWAN can detect that only IPv4 address shall be deleted according to PDN Type for IPv4 in DHCPv4 release message. + +UE sends DHCPv6 release message to TWAN, specific GRE key or IAID is used for identifying specific PDN to be deleted, if UE releases IPv6 address first. + +- Alternative 2: + +TWAG virtual MAC address is used for identifying specific PDN to be deleted, and TWAN can detect that only IPv4 address shall be deleted according to PDN Type for IPv4 in DHCPv4 release message. + +UE sends DHCPv6 release message to TWAN, TWAG virtual MAC address is used for identifying specific PDN to be deleted, if UE releases IPv6 address first. + +2. In case that TWAN receives DHCPv4 release message, then, IP type is IPv4 and TWAN indicates PDN GW for deleting IPv4 address from the PDN. In case that TWAN receives DHCPv6 release message, then, IP type is IPv6 and TWAN indicates PDN GW for deleting IPv6 address from the PDN. + +If TWAN requested IP release, TWAN decides the order of deleting IPv4 address and IPv6 address, If TWAN decides to delete IPv4 first, TWAN sets the IP type to be IPv4 and indicates PDN GW for deleting IPv4 address from the PDN. If TWAN decides to delete IPv6 address first, TWAN sets the IP type to be IPv6 and indicates PDN GW for deleting IPv6 address from the PDN. + +TWAN checks there are two associated IPv4 address and IPv6 address for the PDN, and sends modify Bearer Request to PDN GW, including the indication for IP type to be deleted, in order to indicate PDN GW for deleting this type of IP from the PDN. + +3. PDN GW initiates the IP-CAN Session Modification Procedure with the PCRF. + +4. PDN GW sends modify Bearer response to TWAN. + +If there are multiple bearers corresponding to the PDN, then steps 2-4 are repeated. + +5. TWAN shall remove the associated contexts corresponding to specific PDN, send Reply message in the case of DHCPv6, and inform UE of removing associated contexts. + +6. If TWAN requested IP release, TWAN shall send a DHCPv4 FORCERENEW message as per IETF RFC 3203 [24] and RFC6704 [27], or DHCPv6 Reconfigure message as per IETF RFC 3315 [23]. When the UE proceeds with renewing the IPv4 address or IPv6 address lease, the TWAN shall in turn refuse to do so, notifying to the UE that the IPv4 address or IPv6 address has been released. + +Subsequently, when UE sends DHCPv6 release (if DHCPv4 release is sent in step 1) or DHCPv4 release (if DHCPv6 release is sent in step 1) message, TWAN shall disconnect the PDN. If TWAN requested IP release, then TWAN shall send delete session request message to PDN GW, in order to disconnect the PDN. + +###### 8.2.3.2.3.1.3 UE/TWAN requested Detach Procedure in WLAN on GTP S2a + +![Sequence diagram of UE/TWAN requested Detach Procedure in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with a DHCP release from UE to TWAN, followed by a Delete Session Request from TWAN to PDN GW1. PDN GW1 then interacts with vPCRF and AAA Proxy to update PDN GW Address. A PCEF-initiated IP-CAN Session Termination Procedure is initiated between PDN GW1 and PDN GW2. PDN GW1 sends a Delete Session Response to TWAN. A loop for steps 2-5 is shown if additional PDN connections exist. Finally, TWAN sends a DHCP Reply to UE, and a TWAN Specific resource release is performed.](1c94fd3cebf58af136144f14160d128e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW1 as PDN GW1 + participant PDN_GW2 as PDN GW2 + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + end + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW2: Roaming Scenarios + + UE->>TWAN: 1. DHCP release + TWAN->>PDN_GW1: 2. Delete Session Request + PDN_GW1->>vPCRF: 3. Update PDN GW Address + PDN_GW1->>AAA_Proxy: + PDN_GW1->>PDN_GW2: 4. PCEF-Initiated IP-CAN Session Termination Procedure + PDN_GW2-->>PDN_GW1: + PDN_GW1->>TWAN: 5. Delete Session Response + Note right of PDN_GW2: 6. steps 2-5 above are implemented if additional PDN connections exist + TWAN->>UE: 7. DHCP Reply + Note left of TWAN: 8. TWAN Specific resource release + +``` + +Sequence diagram of UE/TWAN requested Detach Procedure in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with a DHCP release from UE to TWAN, followed by a Delete Session Request from TWAN to PDN GW1. PDN GW1 then interacts with vPCRF and AAA Proxy to update PDN GW Address. A PCEF-initiated IP-CAN Session Termination Procedure is initiated between PDN GW1 and PDN GW2. PDN GW1 sends a Delete Session Response to TWAN. A loop for steps 2-5 is shown if additional PDN connections exist. Finally, TWAN sends a DHCP Reply to UE, and a TWAN Specific resource release is performed. + +Figure 8.2.3.2.3.1.3-1: UE/ TWAN requested Detach on GTP S2a + +1. If the PDN Type is IPv4, UE releases the IPv4 address using DHCPv4 release message or IPv4 address lease time expires in TS23.402 [3] clause 16.3. And if the PDN Type is IPv6, UE releases the IPv6 address using DHCPv6 release message or IPv6 address lease time expires. If the PDN Type is IPv4v6, UE shall releases the IPv4 address and IPv6 address by the first DHCP release session, i.e. DHCPv4 release message or DHCPv6 release message. + +For DHCPv4 release message, the UE MAC address is included in the option of “chaddr”. By the option, UE indicates detach to TWAN. + +For DHCPv6 release message, the UE MAC address is included in the option of “client id”. By the option, UE indicates detach to TWAN. + +2-5. TWAN sends delete Session Request to PDN GW, in order to indicate PDN GW for deleting one PDN. The steps 2-5 are same as steps 2-5 in TS23.402 [3] clause 16.3.1.1. + +6. Repeat steps 2-5 above for remainder PDNs if multiple PDNs are established. + +7. TWAN shall de-authenticate and de-associate the UE at layer 2 according to IEEE STD 802.11-2007 [5], send Reply message to UE in the case of DHCPv6 and informing UE of removing associated contexts. + +8. If TWAN requested Detach, the TWAN locally removes the UE contexts and de-authenticates and disassociates the UE at Layer 2 according to IEEE Std. 802.11-2007 [5]. + +###### 8.2.3.2.3.1.4 HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a + +![Sequence diagram for HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with HSS/AAA sending a Session Termination Request to TWAN. Step 2 involves procedures from figure 8.2.3.2.3.1.3-1, step 2 to 5. Step 3 is a dashed box indicating step 2 is implemented if additional PDN connections exist. Step 4 is TWAN Specific resource release. Step 5 is Session Termination Response from TWAN to HSS/AAA. A shaded 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN GW + participant vPCRF + participant AAA Proxy + participant hPCRF + participant HSS/AAA + + Note right of PDN GW: Roaming Scenarios (vPCRF, AAA Proxy, hPCRF) + + HSS/AAA->>TWAN: 1. Session Termination Request + Note over UE, PDN GW: 2. The procedures as figure 8.2.3.2.3.1.3-1, step 2 to 5 + Note over UE, PDN GW: 3. step 2 is implemented if additional PDN connections exist + TWAN->>UE: 4. TWAN Specific resource release + TWAN->>HSS/AAA: 5. Session Termination Response + +``` + +Sequence diagram for HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with HSS/AAA sending a Session Termination Request to TWAN. Step 2 involves procedures from figure 8.2.3.2.3.1.3-1, step 2 to 5. Step 3 is a dashed box indicating step 2 is implemented if additional PDN connections exist. Step 4 is TWAN Specific resource release. Step 5 is Session Termination Response from TWAN to HSS/AAA. A shaded 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF. + +**Figure 8.2.3.2.3.1.4-1: HSS/AAA Initiated Detach on GTP S2a** + +The procedure for HSS/AAA Initiated Detach from TWAN is represented in Figure 8.2.3.2.3.1.4-1 and described below. + +This procedure applies to the Non-Roaming, Home Routed Roaming and Local Breakout cases. In the Local Breakout case, the vPCRF forwards messages between the PDN GW and the hPCRF. In the Home Routed Roaming and LBO cases, the 3GPP AAA Proxy serves as an intermediary between the Trusted Non-3GPP IP Access and the 3GPP AAA Server in the HPLMN. In the non-roaming and Home Routed Roaming case, the vPCRF is not involved at all. + +- 1) The HSS/AAA sends a Session Termination Request message to the TWAN to detach a specific UE. +- 2) The step 2 to 5 of the UE/TWAN Initiated Detach procedure described in clause 8.2.3.2.3.1.3 above are followed. +- 3) If additional PDNs exist, step 2 is implemented for each PDN. +- 4) During the step, TWAN shall de-authenticate and de-associate the UE at layer 2 according to IEEE STD 802.11-2007 [5], and inform UE to remove the associated contexts. +- 5) TWAN sends a Session Termination Response message to 3GPP AAA Server, respectively. If the detach procedure was initiated from the 3GPP AAA Server and if the UE no longer has any context in the 3GPP AAA Server, the 3GPP AAA Server communicates the HSS as described in clause 12.1.2 TS23.402. If the detach procedure was initiated by HSS, the 3GPP AAA Server replies to the HSS as described in clause 12.1.3 TS23.402. + +**NOTE:** The HSS/AAA may also send a detach indication message to the PDN GW. The PDN GW does not remove the GTP tunnels on S2a, since the TWAN is responsible for removing the GTP tunnels on S2a. The PDN GW acknowledges the receipt of the detach indication message to the 3GPP AAA Server. + +###### 8.2.3.2.3.2 Detach and PDN disconnection in WLAN on PMIP S2a + +###### 8.2.3.2.3.2.1 UE/TWAN requested single PDN Disconnection Procedure in WLAN on PMIP S2a + +![Sequence diagram for UE/TWAN requested single PDN Disconnection Procedure in WLAN on PMIP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with a DHCP release from UE to TWAN, followed by a Proxy Binding Update (lifetime=0) from TWAN to PDN GW. The PDN GW then sends an Update PDN GW Address to the AAA Proxy, which in turn sends it to the HSS/AAA. The AAA Proxy initiates an IP-CAN Session Termination Procedure with the PDN GW. The PDN GW sends a Proxy Binding Ack to the TWAN, which then sends a DHCP Reply to the UE. Finally, TWAN-specific resources are released.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of AAA_Proxy: Roaming Scenarios + + UE-->>TWAN: 1. DHCP release + TWAN->>PDN_GW: 2. Proxy Binding Update(lifetime=0) + PDN_GW->>AAA_Proxy: 3. Update PDN GW Address + AAA_Proxy->>HSS_AAA: 3. Update PDN GW Address + AAA_Proxy->>PDN_GW: 4. PCEF-Initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Proxy Binding Ack + TWAN-->>UE: 6. DHCP Reply + Note left of UE: 7. TWAN Specific resource release + +``` + +Sequence diagram for UE/TWAN requested single PDN Disconnection Procedure in WLAN on PMIP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with a DHCP release from UE to TWAN, followed by a Proxy Binding Update (lifetime=0) from TWAN to PDN GW. The PDN GW then sends an Update PDN GW Address to the AAA Proxy, which in turn sends it to the HSS/AAA. The AAA Proxy initiates an IP-CAN Session Termination Procedure with the PDN GW. The PDN GW sends a Proxy Binding Ack to the TWAN, which then sends a DHCP Reply to the UE. Finally, TWAN-specific resources are released. + +Figure 8.2.3.2.3.2.1-1: UE/ TWAN requested single PDN Disconnection on PMIP S2a + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.3.1.1, with the following differences: + +- Step 2 is a Proxy Binding Update. The parameters in the Proxy Binding Update message are same as step 2 in clause 8.2.3.2.3.1.1. +- Step 5 is a Proxy Binding Acknowledgement. The parameters in the Proxy Binding Acknowledgement message are same as step 5 in clause 8.2.3.2.3.1.1. + +###### 8.2.3.2.3.2.2 UE/TWAN requested multiple PDN Disconnection Procedure in WLAN on PMIP S2a + +![Sequence diagram for UE/TWAN requested multiple PDN Disconnection Procedure in WLAN on PMIP S2a. The diagram shows the interaction between UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with a DHCP release from UE to TWAN, followed by a Proxy Binding Update (lifetime=0) from TWAN to PDN GW1. PDN GW1 sends an Update PDN GW Address to the AAA Proxy, which in turn sends it to the HSS/AAA. The AAA Proxy initiates an IP-CAN Session Termination Procedure with PDN GW1. PDN GW1 sends a Proxy Binding Ack to the TWAN, which then sends a DHCP Reply to the UE. Finally, TWAN-specific resources are released. A note indicates that steps 2-5 are implemented if additional PDN connections exist.](b0211cee4b20034939d883ac0d70f696_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW1 as PDN GW1 + participant PDN_GW2 as PDN GW2 + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of AAA_Proxy: Roaming Scenarios + + UE-->>TWAN: 1. DHCP release + TWAN->>PDN_GW1: 2. Proxy Binding Update(lifetime=0) + PDN_GW1->>AAA_Proxy: 3. Update PDN GW Address + AAA_Proxy->>HSS_AAA: 3. Update PDN GW Address + AAA_Proxy->>PDN_GW1: 4. PCEF-Initiated IP-CAN Session Termination Procedure + PDN_GW1->>TWAN: 5. Proxy Binding Ack + Note right of AAA_Proxy: 6. steps 2-5 are implemented if additional PDN connections exist + TWAN-->>UE: 7. DHCP Reply + Note left of UE: 8. TWAN Specific resource release + +``` + +Sequence diagram for UE/TWAN requested multiple PDN Disconnection Procedure in WLAN on PMIP S2a. The diagram shows the interaction between UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with a DHCP release from UE to TWAN, followed by a Proxy Binding Update (lifetime=0) from TWAN to PDN GW1. PDN GW1 sends an Update PDN GW Address to the AAA Proxy, which in turn sends it to the HSS/AAA. The AAA Proxy initiates an IP-CAN Session Termination Procedure with PDN GW1. PDN GW1 sends a Proxy Binding Ack to the TWAN, which then sends a DHCP Reply to the UE. Finally, TWAN-specific resources are released. A note indicates that steps 2-5 are implemented if additional PDN connections exist. + +Figure 8.2.3.2.3.2.2-1: UE/ TWAN requested multiple PDN Disconnection on PMIP S2a + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.3.1.2, with the following differences: + +- Step 2 is a Proxy Binding Update. The parameters in the Proxy Binding Update message are same as step 2 in clause 8.2.3.2.3.1.2. + +- Step 5 is a Proxy Binding Acknowledgement. The parameters in the Proxy Binding Acknowledgement message are same as step 5 in clause 8.2.3.2.3.1.2. + +###### 8.2.3.2.3.2.3 UE/TWAN requested Detach Procedure in WLAN on PMIP S2a + +![Sequence diagram for UE/TWAN requested Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a sequence of messages starting with a DHCP release from UE to TWAN, followed by a Proxy Binding Update from TWAN to PDN GW1. PDN GW1 then sends an Update PDN GW Address to AAA Proxy. A dashed box labeled 'Roaming Scenarios' contains steps 3 and 4. Step 4 is a PCEF-initiated IP-CAN Session Termination Procedure. Step 5 is a Proxy Binding Ack from PDN GW1 to TWAN. A dashed box labeled '6.steps 2-5 are implemented if additional PDN connections exist' surrounds steps 2-5. Step 7 is a DHCP Reply from TWAN to UE. Step 8 is a TWAN Specific resource release from TWAN to UE.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Sequence diagram for UE/TWAN requested Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a sequence of messages starting with a DHCP release from UE to TWAN, followed by a Proxy Binding Update from TWAN to PDN GW1. PDN GW1 then sends an Update PDN GW Address to AAA Proxy. A dashed box labeled 'Roaming Scenarios' contains steps 3 and 4. Step 4 is a PCEF-initiated IP-CAN Session Termination Procedure. Step 5 is a Proxy Binding Ack from PDN GW1 to TWAN. A dashed box labeled '6.steps 2-5 are implemented if additional PDN connections exist' surrounds steps 2-5. Step 7 is a DHCP Reply from TWAN to UE. Step 8 is a TWAN Specific resource release from TWAN to UE. + +Figure 8.2.3.2.3.2.3-1: UE/ TWAN requested Detach on PMIP S2a + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.3.1.3, with the following differences: + +- Step 2 is a Proxy Binding Update. The parameters in the Proxy Binding Update message are same as step 2 in clause 8.2.3.2.3.1.3. +- Step 5 is a Proxy Binding Acknowledgement. The parameters in the Proxy Binding Acknowledgement message are same as step 5 in clause 8.2.3.2.3.1.3. + +###### 8.2.3.2.3.2.4 HSS/AAA Initiated Detach Procedure in WLAN on PMIP S2a + +Same as the procedure for SaMOG R11, refer to TS23.402 [3] clause 16.3.1.2. + +![Sequence diagram for HSS/AAA Initiated Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a sequence of messages starting with a Session Termination Request from HSS/AAA to AAA Proxy. Step 2 is a dashed box labeled 'The procedures as figure 8.2.3.2.3.2.1-1, step 2 to 5'. Step 3 is a dashed box labeled 'step 2 is implemented if additional PDN connections exist'. Step 4 is a TWAN Specific resource release from TWAN to UE. Step 5 is a Session Termination Response from AAA Proxy to HSS/AAA.](b3c108e7145f2017957569d06ea359cb_img.jpg) + +Sequence diagram for HSS/AAA Initiated Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a sequence of messages starting with a Session Termination Request from HSS/AAA to AAA Proxy. Step 2 is a dashed box labeled 'The procedures as figure 8.2.3.2.3.2.1-1, step 2 to 5'. Step 3 is a dashed box labeled 'step 2 is implemented if additional PDN connections exist'. Step 4 is a TWAN Specific resource release from TWAN to UE. Step 5 is a Session Termination Response from AAA Proxy to HSS/AAA. + +Figure 8.2.3.2.3.2.4-1: HSS/AAA Initiated Detach on PMIP S2a + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.3.1.4, the difference is that steps 2 and 3 refer to figure 8.2.3.2.3.2.3-1. + +##### 8.2.3.2.4 PDN GW initiated Resource Allocation Deactivation in WLAN on S2a + +Same as the procedure for SaMOG R11, refer to TS23.402 [3] clause 16.4. + +###### 8.2.3.2.4.1 PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a + +This procedure can be used to deactivate an S2a dedicated bearer or deactivate all S2a bearers belonging to a PDN address, e.g., due to IP-CAN session modification requests from the PCRF. If the default S2a bearer belonging to a PDN is deactivated, the PDN GW deactivates all S2a bearers belonging to the PDN. + +![Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Delete Bearer Request (PDN GW to TWAN), 3. TWAN specific resource Release Procedure (TWAN to UE), 4. Delete Bearer Response (TWAN to PDN GW), 5. Update PDN GW Address (PDN GW to 3GPP AAA proxy), and 6. IP-CAN Session Modification (PDN GW to vPCRF).](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Delete Bearer Request (PDN GW to TWAN), 3. TWAN specific resource Release Procedure (TWAN to UE), 4. Delete Bearer Response (TWAN to PDN GW), 5. Update PDN GW Address (PDN GW to 3GPP AAA proxy), and 6. IP-CAN Session Modification (PDN GW to vPCRF). + +**Figure 8.2.3.2.4.1-1: PDN GW Initiated Bearer Deactivation with GTP on S2a** + +This procedure applies to the Non-Roaming, Roaming and Local Breakout cases. In the Local Breakout case, the vPCRF forwards messages between the PDN GW and the hPCRF. In the non-roaming and home routed roaming cases, the vPCRF is not involved at all. + +The optional interaction steps between the PDN GW and the PCRF in the procedures in figure 16.4.1-1 occur only if dynamic policy provisioning is deployed. Otherwise policy may be statically configured within the PDN GW. + +1. If dynamic PCC is deployed, the PDN GW initiated Bearer Deactivation procedure may be triggered, for example, due to 'IP-CAN session Modification procedure', as defined in TS 23.203 [19]. In this case, the resources associated with the PDN in the PDN GW are released. +2. The PDN GW sends a Delete Bearer Request message (EPS Bearer Identity, Cause) to the TWAN. This message can include an indication that all bearers belonging to that PDN shall be released. +3. If supported by the TWAN, the TWAN shall remove the associated contexts corresponding to specific PDNs, and inform UE to remove the associated contexts. +4. The TWAN deletes the bearer contexts related to the Delete Bearer Request message, and acknowledges the bearer deactivation to the PDN GW by sending a Delete Bearer Response (EPS Bearer Identity) message. +5. In the case of the resources corresponding to the PDN are released in PDN GW, the PDN GW informs the 3GPP AAA Server/HSS of the PDN disconnection. +6. The PDN GW deletes the bearer context related to the deactivated S2a bearer. If the dedicated bearer deactivation procedure was triggered by receiving a PCC decision message from the PCRF, the PDN GW + +indicates to the PCRF whether the requested PCC decision was successfully enforced by completing the PCRF-initiated IP-CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203 [19], proceeding after the completion of IP-CAN bearer signalling. + +###### 8.2.3.2.4.2 PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a + +![Sequence diagram for PDN GW Initiated Bearer Deactivation with PMIP on S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Binding Revocation Indication (PDN GW to TWAN), 3. TWAN specific resource Release Procedure (TWAN internal), 4. Gateway Control Session Termination Procedure (TWAN to hPCRF), 5. Binding Revocation Ack (TWAN to PDN GW), 6. Update PDN GW Address (hPCRF to AAA/HSS), 7. IP-CAN Session Modification (hPCRF to vPCRF).](410562339ce067fdc6fa41940c118658_img.jpg) + +Sequence diagram for PDN GW Initiated Bearer Deactivation with PMIP on S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Binding Revocation Indication (PDN GW to TWAN), 3. TWAN specific resource Release Procedure (TWAN internal), 4. Gateway Control Session Termination Procedure (TWAN to hPCRF), 5. Binding Revocation Ack (TWAN to PDN GW), 6. Update PDN GW Address (hPCRF to AAA/HSS), 7. IP-CAN Session Modification (hPCRF to vPCRF). + +**Figure 8.2.3.2.4.2-1: PDN GW Initiated Bearer Deactivation with PMIP on S2a** + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.4.1, with the following differences: + +- Step 2 is a Binding Revocation Indication message. The parameters in the Binding Revocation Indication message are same as step 2 in clause 8.2.3.2.4.1. +- Step 4. If the resources are released in the TWAN, the TWAN initiates a Gateway Control Session Termination Procedure with the PCRF as specified in TS 23.203 [4]. +- Step 5 is a Binding Revocation Acknowledgement message. The parameters in the Binding Revocation Acknowledgement message are same as step 4 in clause 8.2.3.2.4.1. + +##### 8.2.3.2.5 Dedicated bearer activation in WLAN on GTP S2a + +Same as the procedure for SaMOG R11, refer to TS23.402 [3] clause 16.5. + +##### 8.2.3.2.6 Network-initiated bearer modification in WLAN on GTP S2a + +Same as the procedure for SaMOG R11, refer to TS23.402 [3] clause 16.6. + +##### 8.2.3.2.7 Handover from 3GPP Access to Trusted WLAN Access + +##### 8.2.3.2.7.1 Handover from 3GPP Access to Trusted WLAN Access on GTP S2a + +![Sequence diagram illustrating the handover from 3GPP Access to Trusted WLAN Access on GTP S2a. The diagram shows interactions between UE, TWAN, MME, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves radio bearer setup, WLAN discovery, authentication, DHCP exchange, session creation, IP-CAN modification, and bearer release.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates the sequence of messages for a handover from 3GPP Access to Trusted WLAN Access on GTP S2a. The participants are UE, TWAN, MME, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process is as follows: + +- Radio bearer and S1 bearer (UE to PDN GW via MME and S-GW). +- UE discovers WLAN Access and initiates HO (UE to TWAN). +- EAP Authentication (UE to TWAN) and Authentication & Authorization (TWAN to AAA Proxy to HSS/AAA). +- DHCP Discover/ Confirm (UE to TWAN). +- Create Session Request (TWAN to PDN GW). +- IP-CAN Session Modification Procedure (PDN GW to vPCRF). +- Update PDN GW Address (PDN GW to AAA Proxy). +- Create Session Response (PDN GW to TWAN). +- GTP Tunnel (TWAN to PDN GW). +- DHCP Offer (TWAN to UE). +- DHCP Request/DHCP Ack (UE to TWAN). +- Reply (TWAN to UE). +- UE-initiated Connectivity to Additional PDN (UE to PDN GW). +- 3GPP EPS Bearer Release (UE to MME and PDN GW). + +Sequence diagram illustrating the handover from 3GPP Access to Trusted WLAN Access on GTP S2a. The diagram shows interactions between UE, TWAN, MME, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves radio bearer setup, WLAN discovery, authentication, DHCP exchange, session creation, IP-CAN modification, and bearer release. + +**Figure 8.2.3.2.7.1-1: Handover from 3GPP Access to Trusted WLAN Access on GTP S2a** + +1-2) These steps are the same as steps 1-3 in TS 23.402 [3], clause 8.2.2. + +- In this step, indication on whether the UE indicates its capability (i.e. Rel-12 SaMOG capability) to the AAA server during the authentication procedure. Based on the UE capability provided by AAA server, the TWAN decides to use L3 trigger. +- The UE shall send a DHCPv4 Discover as per IETF RFC 2131 [9], or DHCPv6 confirm as per IETF RFC3315[23] to TWAN with “requested IP address” included in DHCPv4 Discover message (option 50)/ DHCPv6 Confirm message (option IA\_NA) with all previously assigned UE IP addresses prior to its handover. TWAN determines IP address preservation by the presence of the “requested IP address” option. APN, PDN Type and downlink GRE key (for alternative 1) shall also be included. +- The TWAN sends a Create Session Request (APN PDN address, Handover Indication) message to the PDN GW. The PDN Address shall be set according to requested IP address for DHCP request message in step 4, and sent to the PDN GW. The TWAN sets the 'Handover Indication' to allow the PDN GW to re-allocate the same IPv4 address and/or IPv6 address that was assigned to the UE while it was connected to 3GPP IP access and to initiate an IP CAN Session Modification Procedure with the PCRF. Both the APN and PDN Address are used by the PDN GW to determine which PDN to establish connectivity for, in the case that the PDN GW supports multiple PDN connectivity. +- This steps is same as steps 7A-7B in TS 23.402 [3], clause 8.2.2. +- The PDN GW informs the 3GPP AAA Server of its PDN GW identity and the APN corresponding to the UE's PDN and obtains authorization information from the 3GPP AAA Server. The 3GPP AAA Server decides whether or not to update PDN GW identification according to the UE capability, which has been provided at the + +authentication phase. If the UE supports IP address preservation, the 3GPP AAA Server shall update PDN GW identity towards the HSS. + +8. The PDN GW responds with a Create Session Response to the TWAN. The Create Session Response contains the IPv4 address and/or the IPv6 address that were assigned to the UE while it was connected to the 3GPP IP access. +9. GTP tunnel is setup between TWAN and PDN GW. +10. For DHCPv4, TWAN returns DHCP offer message to UE, TWAG virtual MAC address is included if alternative 2 is used. +11. UE sends DHCP Request (for DHCPv4) to TWAN, and TWAN returns DHCP Ack message to the UE and UE IP allocated by PDN GW. + - a) Alternative 1: GRE tunnelling information is included to UE, where GRE tunnel information includes uplink GRE key and UE's local IP address which are allocated by TWAN for tunnelling support in the case of one or multiple PDNs. + - b) Alternative 2: Both UE and TWAN maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address. +12. TWAN returns Reply message to the UE, and UE IP allocated by PDN GW. + - a) Alternative 1: GRE tunnelling information is included to UE, where GRE tunnel information includes uplink GRE key and UE's local IP address which are allocated by TWAN for tunnelling support in the case of one or multiple PDNs. + - b) Alternative 2: Both UE and TWAN maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address. + +When PDN type is IPv4, steps 10-11 apply. + +When PDN type is IPv6, step 12 apply. + +When PDN type is IPv4v6, there are two following cases: + +- Alternative 1: + - (a) If UE requests IPv4 address first, TWAN shall implement steps 10-11 and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send confirm message encapsulated by the GRE key which is allocated in step 11 to TWAN, TWAN shall implement steps 12 which are encapsulated by the GRE key which is allocated in step 11. + - (b) If UE requests IPv6 address first, TWAN shall implement steps 12 and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message encapsulated by the GRE key which is allocated in step 12 to TWAN, TWAN and UE shall implement steps 10-11 which are encapsulated by the GRE key which is allocated in step 12. +- Alternative 2: + - (a) If UE requests IPv4 address first, TWAN shall implement steps 10-11 and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send confirm message with TWAG virtual MAC address which is allocated in step 10 to TWAN, TWAN shall implement steps 12. + - (b) If UE requests IPv6 address first, TWAN shall implement steps 12 and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message with TWAG virtual MAC address which is allocated in step 12 to TWAN, TWAN and UE shall implement steps 10-11. + +Both uplink and downlink GRE key corresponds to the specific PDN. And subsequently, user data for the PDN shall be encapsulated by corresponding GRE tunnel. + +13. For connectivity to multiple PDNs, the UE establishes connectivity to all the remain PDNs that are being transferred from 3GPP access besides the PDN, and steps 3 to 12 are repeated for per PDN, with the following exception: + - Handover indication isn't included in step 5. +14. The PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure in 3GPP access as defined in clause 5.6.2.2 in TS 23.402 [3] for PMIP S5/S8 or the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401 [6], clause 5.4.4.1 for GTP-S5/S8. + +##### 8.2.3.2.7.2 Handover from 3GPP Access to Trusted WLAN Access on PMIP S2a + +![Sequence diagram for Handover from 3GPP Access to Trusted WLAN Access on PMIP S2a. The diagram shows the interaction between UE, TWAN, MME, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves radio bearer establishment, WLAN discovery, EAP authentication, DHCP negotiation, Proxy Binding updates, IP-CAN session modification, and 3GPP EPS bearer release.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +The sequence diagram illustrates the handover process from 3GPP Access to Trusted WLAN Access on PMIP S2a. The participants are UE, TWAN, MME, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process is as follows: + +1. Radio bearer and S1 bearer (UE to PDN GW) +2. UE discovers WLAN Access and initiates HO (UE to TWAN) +3. EAP Authentication (UE to AAA Proxy) and 3. Authentication & Authorization (AAA Proxy to HSS/AAA) +4. DHCP Discover/ Confirm (UE to TWAN) +5. Proxy Binding Update (TWAN to PDN GW) +6. IP-CAN Session Modification Procedure (PDN GW to vPCRF and hPCRF) +7. Update PDN GW Address (PDN GW to AAA Proxy) +8. Proxy Binding Acknowledgement (PDN GW to TWAN) +9. GTP Tunnel (TWAN to PDN GW) +10. DHCP Offer (TWAN to UE) +11. DHCP Request/DHCP Ack (UE to TWAN) +12. Reply (TWAN to UE) +13. UE-initiated Connectivity to Additional PDN (UE to PDN GW) +14. 3GPP EPS Bearer Release (MME to PDN GW and PDN GW to vPCRF) + +Sequence diagram for Handover from 3GPP Access to Trusted WLAN Access on PMIP S2a. The diagram shows the interaction between UE, TWAN, MME, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves radio bearer establishment, WLAN discovery, EAP authentication, DHCP negotiation, Proxy Binding updates, IP-CAN session modification, and 3GPP EPS bearer release. + +**Figure 8.2.3.2.7.2-1: Handover from 3GPP Access to Trusted WLAN Access on PMIP S2a** + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.7.1, with the following differences: + +- Step 5 is a Proxy Binding Update. The parameters in the Proxy Binding Update message are same as step 5 in clause 8.2.3.2.7.1. +- Step 8 is a Proxy Binding Acknowledgement. The parameters in the Proxy Binding Acknowledgement message are same as step 8 in clause 8.2.3.2.7.1. + +#### 8.2.3.3 Impacts on existing nodes or functionality + +#### 8.2.3.4 Evaluation + +**Editor's Notes: The fulfilment to the requirements in Subclause 8.1 as well as simplicity of implementation in the UE should be evaluated.** + +The following aspects are considered and evaluated for the solution: + +- i) Impacts to existing network deployment: + - a) There is no requirement for WLAN APs compared to Rel-11. + - b) For TWAG, it shall support DHCP enhancement, EAP enhancement, and the association of IPv4 session and IPv6 session for same PDN for dual stack scenario. +- ii) Impacts to UE: + - a) For UE, it shall support DHCP enhancement, EAP enhancement, and the association of IPv4 session and IPv6 session for same PDN for dual stack scenario. + +NOTE 1: Required the support of Stateful DHCP as described in RFC 3315 with also the 3GPP vendor specific extensions + +NOTE 2: Required additional security support for DHCP Force renew as described in RFCs 3203 and 6704 + +NOTE 3: The IPv4 and IPv6 sessions association for dual-stack support is common to all SaMOG proposed solutions and is not specific to Solution 3. + - b) UE is required to support GRE-over-IP encapsulation if alternative 1 is used. +- iii) Impacts to 3GPP protocols/extensions (e.g. EAP AKA'): + +The following protocols are extended: + + - a) UE network capability negotiation is enhanced for EAP protocol. + - b) Session Management (APN, PDN type, GRE tunnel information(for alternative 1), UE IP), is enhanced for DHCP protocol. + - c) 3GPP Vendor-specific Information can be used for enhanced information in DHCP protocol +- iv) Impacts to protocols defined by other SDOs (e.g. DHCP): + +No impact on other SDOs. +- v) Control plane + - a) The latency/load can increase in the following procedures: + - 1) For first PDN and handover procedures, EAP (once for first PDN) and DHCP messages are implemented. + - 2) For additional PDN, DHCP messages are implemented. + - b) There is no impact on other network element, e.g. AAA signaling etc. +- vi) Compliance to clause 8.1 SaMOG phase-2 system requirements: + - a) Co-existence with Rel-11 SaMOG + - b) Support for IP address preservation during handover + - c) Simultaneous support for S2a EPC-routed and NSWO; support of simultaneous multiple PDNs +- vii) Other functional limitations: + +There is no other functional limitation. + +## 8.2.4 Solution 4 + +#### 8.2.4.1 Functional Description + +#### 8.2.4.1.1 P2P link + +A per UE point-to-point link between the UE and the TWAG is assumed. + +The TWAG performs unicast layer 2 forwarding even when layer 3 is multicast address (e.g. Router Advertisement, RFC 6085). + +**Editor's Note:** Handling of unsolicited IPv6 Router Advertisement for PDN connections is FFS. + +**Editor's Note:** How to support multiple IPv4 PDN connections when same private IPv4 addresses are allocated from different PDN connections with per UE point-to-point link is FFS. + +In IPv4 case, the multiple PDN may use the same IP multicast address for different services, the source IP address in general could be used to disambiguate the multicast services. + +**Editor's Note:** If the source IP address is same, how to distinguish the services are FFS. + +## 8.2.5 Solution 5: Associating APN/PDN with Virtual IP Interface + +#### 8.2.5.1 Functional Description + +**Editor's Notes:** It should be described whether and how the solution fulfils the requirements in Subclause 8.1. + +#### 8.2.5.1.1 General + +This section describes in general the point-to-point link/IP forwarding and the control sequence for associating an APN/NSWO to a point-to-point link. The session control protocol carries the APN/PDN signalling attributes and uses distinct Gateway interface (gateway IP address, MAC address) for the connection to associate the APN in IP configuration signalling (DHCP for IPv4, stateless autoconfiguration for IPv6). + +##### **Point-to-Point Link** + +The point-to-point link in this solution uses the distinct MAC address per APN/NSWO at the gateway as described in subclause 8.2.2.1.1.2 for packet forwarding. In addition to a distinct MAC address, this solution has a distinct TWAG Gateway Interface per APN/NSWO connection. A TWAG Gateway Interface for a connection consists of an IP address and a MAC address – each of which is distinct for connections to a UE. + +![Diagram of a Point-to-Point Link architecture showing traffic flow aggregates and network components.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The diagram illustrates a network architecture for a Point-to-Point Link. At the top, an oval labeled 'Application / Service Layer' is connected to 'UL Traffic Flow Aggregates' on the left and 'DL Traffic Flow Aggregates' on the right. Below this, a 'UE' (User Equipment) box on the left contains three stacked trapezoidal icons representing traffic flows. Arrows from these flows point to an 'APN/NSWO' label, which in turn points to 'APN/NSWO → TWAG-GW-If'. This interface connects to a central 'AP/WLC' (Access Point/Wireless LAN Controller) box. From the 'AP/WLC', three arrows point to a 'TWAG' (Traffic Flow Aggregation) box. Below the 'AP/WLC' and 'TWAG' is a dashed oval labeled 'NSWO'. An arrow labeled 'L2 Flow: UE-MAC ↔ TWAG-VMAC' connects the 'UE' to the 'NSWO'. The 'TWAG' box has an interface labeled 'TWAG-GW-If ↔ S2a-TEID' connecting it to a 'PDN GW' (PDN Gateway) box on the right. The 'PDN GW' box contains three stacked trapezoidal icons representing traffic flows. Arrows from these flows point to a 'DL-TFT' label, which points to 'DL-TFT → S2a-TEID'. This interface connects back to the 'TWAG'. Below the 'PDN GW' is a label 'S2a Bearer'. The entire central section is enclosed in a large dashed oval. + +Diagram of a Point-to-Point Link architecture showing traffic flow aggregates and network components. + +**Figure 8.2.5.1.1-1: Point-to-Point Link** + +**PDN Control Protocol** The PDN control protocol is used to signal APN/PDN information between UE TWAN. This protocol also associates the APN/NSWO connection request to a distinct gateway IP address/MAC address prior to IP configuration using DHCP, RS/RA. The gateway IP address is derived from the MAC address and there is a 1:1 association between the distinct gateway MAC address and the gateway IP address. For IP configuration signalling using DHCP or RS/RA, the TWAG can uniquely associate a UE's PDN connection using UE MAC address (or IPv6 link layer address) and this gateway interface (IP address, virtual MAC address) that is distinct for each PDN connection of the UE. + +For IPv4 stateful address configuration, the UE provides a PDN connection request and the TWAG returns this distinct gateway IP address as input for server-identity in DHCP request. In the subsequent DHCP Request from UE, the server-identity is populated with this distinct gateway IP address as a means for the TWAG to identify the PDN connection. + +For IPv6 stateless address configuration, the UE provides an PDN connection request and the TWAG returns this distinct gateway IP address and also populates the same gateway IP address in a Router Advertisement that follows. For cases where the UE needs to send a Router Solicitation (optional), the TWAG also returns a transient multicast address corresponding to this PDN connection that the TWAG listens to. The UE may send a Router Solicitation with destination address set to this transient multicast address that is distinct for this PDN connection. + +If UE request handover from 3GPP to WLAN access, it indicates handover attach in the control protocol. + +If the UE needs to setup a second PDN connection, this can be signalled in a subsequent connection setup request. For disconnection of a PDN connection, either the UE or the TWAN may notify the other about an IP address/prefix that is released. The notified entity can then release the local connection resources. + +The PDN Control Protocol described above consists of requests / responses or notification messages and requires a transport for these messages. Two alternative transport protocols are considered here: + +###### - **Alternative A: ICMP Echo Payload** + +ICMP Echo [RFC 792] is typically used to verify if another host is active. However, it is possible to add an arbitrary data payload following the ICMP header as long as it is echoed back, and this solution uses the data payload to carry binary encoded connection control messages each of which is an ICMP Echo Request and Response. The PDN Control Protocol is identified by a unique sequence identifier (e.g. 0xFCFCFC) that follows the ICMP Echo message and precedes the PDN control protocol frame. The data payload of the ICMP Echo messages maybe authenticated (message authentication) using a hashed key each for UE and TWAG (established during EAP-AKA). Only one set of keys are established between UE – TWAG and either the link local address or the NSWO IP + +connection may be used for this signalling. + +Reliability of this control sequence is provided by virtue of receiving the echoed message. For re-transmission, this method re-uses the DHCP re-transmission timer value. No support for fragmentation is provided and is not necessary for the control protocol. + +The ICMP Echo payload mechanism uses existing ICMP protocol semantics and does not violate IETF RFC 792. Only the control messages need to be standardized (in 3GPP). The mechanism is basic and is efficient enough even if messages are echoed back since only a limited amount of control signalling required and is always across one IP hop. + +###### - **Alternative B: 802.11 GAS frame** + +802.11 GAS frames can be used to carry the PDN control protocol frames similar to the transport of ANQP/GAS between UE – WLAN Access Point. These control frames could then be carried to the TWAG over RADIUS or other similar protocol. The control protocol semantics are the same as in Alternative A above. + +Reliability of this control sequence is provided using 802.11 GAS and the backhaul protocol (e.g. RADIUS). Re-transmission timers re-use the DHCP re-transmission timer value. No fragmentation is expected as the signalling is expected to be well below the size of an Ethernet frame. + +The PDN Control protocol would be defined as a new GAS protocol in WFA as part of HS2.0 Rel-3 specifications. The protocol would use the WMM Notification Action frames as a L2 transport over the 802.11 air interface. In addition, RADIUS protocol messages Accept-Request/Response (for PDN Request/Response) and Change-of-Authorization (for Notification) should carry this protocol from AP – TWAN controllers. This underlying mechanism provides a reliable control protocol transport. As in the case above, DHCP re-transmission timer values may be used. + +**Editor's Note:** Selection of one of the control transport protocols is FFS. + +**Editor's Notes:** For uplink broadcasts signalling (e.g. IPv6 RS, IPv6 ND, ARP, and service discovery requests (e.g. DLNA) generally sent using a L2 (MAC) broadcast address: + +- when the destination MAC address used over WLAN is a broadcast address and not the TWAG MAC address associated with a TWAN connectivity service, a specific handling would be required at the TWAN to handle such traffic or +- the UE uses a unicast MAC addressing for such traffic as described in RFC 6085 “Address Mapping of IPv6 Multicast Packets on Ethernet “ for the IPv6 case. Using such technique for IPv4 is FFS. + +#### 8.2.5.2 Procedures + +**Editor's Notes:** The call flows are described in this subclause. + +#### 8.2.5.2.2 Connection Establishment Procedure + +The connection establishment procedures below support both PDN connection establishment and NSWO connections. In the case of PDN connections, the signalling from UE to TWAN explicitly provides the APN that the UE wishes to connect to. For NSWO connections, the UE indicates NSWO request or signal that it wants a local IP address. + +The figures below outline GTP S2a, PMIP S2a and NSWO connection setup. + +![Sequence diagram titled 'Roaming Scenarios' showing the attach procedure for PDN and NSWO for GTP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram is divided into sections for GTP S2a and NSWO. Steps include: 1. Non-3GPP Specific Procedures; 2. EAP Authentication; 2b. Initialize Control Interface; 3. Request to associate APN/PDN to virtual IP interface; 4. Response to associate APN/PDN to virtual IP interface; 5a. Create Session Request; 6. IP-CAN Session Establishment Procedure; 7. Update PDN GW Address; 8. Create Session Response; 9. GTP Tunnel; 5b. Create NSWO connection context; 10. L3 Address Request; 11. L3 Address Ack.](a3472689858b068ef469213682965325_img.jpg) + +Sequence diagram titled 'Roaming Scenarios' showing the attach procedure for PDN and NSWO for GTP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram is divided into sections for GTP S2a and NSWO. Steps include: 1. Non-3GPP Specific Procedures; 2. EAP Authentication; 2b. Initialize Control Interface; 3. Request to associate APN/PDN to virtual IP interface; 4. Response to associate APN/PDN to virtual IP interface; 5a. Create Session Request; 6. IP-CAN Session Establishment Procedure; 7. Update PDN GW Address; 8. Create Session Response; 9. GTP Tunnel; 5b. Create NSWO connection context; 10. L3 Address Request; 11. L3 Address Ack. + +**Figure 8.2.5.2.2-1: Attach Procedure for PDN and NSWO for GTP based S2a** + +The procedure to attach PDN or NSWO for a trusted WLAN access is represented in Figure 8.2.5.2.2-1 and described below: + +1. The initial TWAN specific L2 procedures are performed. These procedures are TWAN specific and outside the scope of 3GPP. +2. EAP authentication procedures are performed. During this sequence, support of Phase 2 by the UE and TWAG are conveyed using EAP-AKA [RFC 4187] extensions. If the UE, TWAG are Phase 2 compliant, the UE and TWAG setup and exchange keys to be used to provide integrity protection (e.g. checksum hash) for the subsequent signalling setup messages. +After successful authentication, in step 2b, for ICMP Payload transport of PDN signalling protocol, the UE sets up a link-local address for IPv4 (RFC 3927), or follows the procedure in RFC 4861 to setup an IPv6 link local address. The TWAG replies with a control-initialize message with source router IP, MAC address that UE can use in subsequent requests. +3. The UE sends a request with APN, other PDN signalling parameters (e.g. initial attach) to the TWAN to setup a PDN/NSWO connection. The signalling may be transported using ICMP Echo Payload (alternative 1) or 802.11 GAS (alternative 2). +4. The TWAN assigns a distinct IPv4 gateway address corresponding to the APN/NSWO and responds with this address in server-identity and router address for IPv4. For IPv6, the TWAN assigns a distinct IPv6 gateway address (source address in Router Advertisement) and transient multicast address for router solicitation if needed. + +**Editor's Note: The choice of a control protocol transport in steps 3-4 is FFS.** + +Steps 5 – 9 are performed as specified in TS 23.402, subclause 16.2.1, steps 3 – 7 for PDN connection establishment for GTP S2a. + +For NSWO connection, step 5b, the TWAG assigns local connection resources (gateway IP address, subnet, etc.) for the connection. + +10. The UE sends a layer 3 attach request. + + +For IPv4, the UE sends a DHCP Request with server-identity option set to the distinct gateway IP address obtained in step 4. + +For IPv6, the UE may optionally send a Router Solicitation with destination address set to the transient multicast address obtained in step 4. +11. The TWAN responds to the layer 3 attach. + + +For IPv4, the TWAG sends a DHCP Ack with server-identity, router option set to the distinct gateway IP address for the APN/NSWO. The IP address in the message is in *yiaddr*. + +For IPv6, the TWAG sends a Router Advertisement when a Create Session Response (step 8) is received for this PDN connection or it receives Router Solicitation in step 10. The Router Advertisement is sent with source address set to the distinct gateway IP address configured for this APN/NSWO in step 4. + +The UE can determine the L2 address of the router interface by sending an ARP Request (IPv4) or Neighbor Solicitation (IPv6) + +For subsequent PDN / NSWO connections, steps 3 – 11 are repeated. + +Establishing a second connection (IP address/interface) corresponding to an already signalled/established APN/NSWO session is straightforward using this method. In step 3 above, the explicit parameters that are conveyed between UE and TWAG can include the means to indicate if a second connection is being requested. + +![Sequence diagram for Attach Procedure for PDN and NSWO for PMIP based S2a. It shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Steps include EAP Authentication, Control Interface initialization, APN/PDN association, Proxy Binding Update/Ack, IP-CAN Session Establishment, PMIP Tunneling, and L3 Address Request/Ack.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN GW + box "Roaming Scenarios" + participant vPCRF + participant AAA Proxy + participant hPCRF + end + participant HSS/AAA + + Note over UE, TWAN: 1. Non-3GPP Specific Procedures + UE->>HSS/AAA: 2. EAP Authentication / Authentication & Authorization + Note over UE, TWAN: 2b. Initialize Control Interface + UE->>TWAN: 3. Request to associate APN/PDN to virtual IP interface + TWAN->>UE: 4. Response to associate APN/PDN to virtual IP interface + + rect rgb(240, 240, 240) + Note right of TWAN: (PMIP S2a) + TWAN->>PDN GW: 5a. Proxy Binding Update + PDN GW->>AAA Proxy: 6. IP-CAN Session Establishment Procedure + PDN GW->>HSS/AAA: 7. Update PDN GW Address + PDN GW->>TWAN: 8. Proxy Binding Ack + Note over TWAN, PDN GW: 9.. PMIP Tunnel + end + + rect rgb(240, 240, 240) + Note right of TWAN: (NSWO) + Note over TWAN: 5b. Create NSWO connection context + end + + UE->>TWAN: 10. L3 Address Request + TWAN->>UE: 11. L3 Address Ack + +``` + +Sequence diagram for Attach Procedure for PDN and NSWO for PMIP based S2a. It shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Steps include EAP Authentication, Control Interface initialization, APN/PDN association, Proxy Binding Update/Ack, IP-CAN Session Establishment, PMIP Tunneling, and L3 Address Request/Ack. + +**Figure 8.2.5.2.2-2: Attach Procedure for PDN and NSWO for PMIP based S2a** + +The procedure for attach using PMIP based S2a is similar to the sequence for GTP. However, steps 5a and 8 for PMIP consist of Proxy Binding Update (5a) and Proxy Binding Ack (8). + +#### 8.2.5.2.3 UE Initiated Disconnection Procedure + +The disconnection sequence in the figure below supports UE triggered disconnection of one connection (while the rest of the session remains unchanged). If the last connection (or all connections) is being released, all session resources are cleaned up also. + +![Sequence diagram for UE Initiated Disconnection Procedure for PDN and NSWO for GTP based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The UE sends a Delete Connection notification to the TWAN. The TWAN then sends a Delete Session Request to the PDN GW. The PDN GW sends an Update PDN GW Address to the HSS/AAA. The PDN GW then initiates a PCEF-initiated IP-CAN Session Termination Procedure. The PDN GW sends a Delete Session Response to the TWAN. The TWAN then releases local resources. Finally, the TWAN releases specific resources.](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + rect rgb(230, 230, 230) + Note over vPCRF, AAA_Proxy: Roaming Scenarios + end + + UE->>TWAN: 1. Delete Connection (notification) + + rect dashed + TWAN->>PDN_GW: 2a. Delete Session Request + PDN_GW->>HSS_AAA: 3. Update PDN GW Address + Note over PDN_GW, hPCRF: 4. PCEF-initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Delete Session Response + Note right of HSS_AAA: (GTP S2a) + end + + rect dashed + Note over TWAN: 2b. NSWO release +local resources + Note right of HSS_AAA: (NSWO) + end + + Note over UE, TWAN: 6. TWAN specific +resource release + +``` + +Sequence diagram for UE Initiated Disconnection Procedure for PDN and NSWO for GTP based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The UE sends a Delete Connection notification to the TWAN. The TWAN then sends a Delete Session Request to the PDN GW. The PDN GW sends an Update PDN GW Address to the HSS/AAA. The PDN GW then initiates a PCEF-initiated IP-CAN Session Termination Procedure. The PDN GW sends a Delete Session Response to the TWAN. The TWAN then releases local resources. Finally, the TWAN releases specific resources. + +**Figure 8.2.5.2.3-1: Disconnection Procedure for PDN and NSWO for GTP based S2a** + +The procedure to disconnect a PDN /NSWO session for GTP based S2a is shown in the figure above. + +1. The UE sends a delete connection notification with the IP address and gateway IP address for the connection to trigger disconnection. +2. If the IP address to be released is not an NSWO connection, the TWAG initiates a Delete Session Request with the IP address of the PDN connection. (2a). +For NSWO, the TWAN releases local connection resources (2b). + +Steps 3, 4 are as defined in TS 23.402 [3], subclause 16.3.1.1, steps 3, 4. + +5. The PDN GW acknowledges with Delete Session Response (cause). +6. Connection resources in TWAG and UE are released. + +![Sequence diagram for Disconnection Procedure for PDN and NSWO for PMIP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a disconnection procedure initiated by the UE. The UE sends a 'Delete Connection (notification)' to the TWAN. The TWAN sends a 'Proxy Binding Update (lifetime = 0)' to the PDN GW. The PDN GW sends an 'Update PDN GW Address' to the HSS/AAA. A dashed box labeled '(PMIP S2a)' contains the interaction between the PDN GW and the AAA Proxy, which includes a 'PCEF-initiated IP-CAN Session Termination Procedure'. The PDN GW sends a 'Proxy Binding Ack' to the TWAN. A dashed box labeled '(NSWO)' contains the TWAN sending 'NSWO release local resources' to the PDN GW. Finally, the TWAN sends a 'TWAN specific resource release' to the UE.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW: Roaming Scenarios + + UE->>TWAN: 1. Delete Connection(notification) + Note right of TWAN: (PMIP S2a) + TWAN->>PDN_GW: 2a. Proxy Binding Update (lifetime = 0) + PDN_GW->>HSS_AAA: 3. Update PDN GW Address + Note right of AAA_Proxy: (NSWO) + Note right of AAA_Proxy: 4. PCEF-initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Proxy Binding Ack + Note right of TWAN: 2b. NSWO release local resources + TWAN->>UE: 6. TWAN specific resource release + +``` + +Sequence diagram for Disconnection Procedure for PDN and NSWO for PMIP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a disconnection procedure initiated by the UE. The UE sends a 'Delete Connection (notification)' to the TWAN. The TWAN sends a 'Proxy Binding Update (lifetime = 0)' to the PDN GW. The PDN GW sends an 'Update PDN GW Address' to the HSS/AAA. A dashed box labeled '(PMIP S2a)' contains the interaction between the PDN GW and the AAA Proxy, which includes a 'PCEF-initiated IP-CAN Session Termination Procedure'. The PDN GW sends a 'Proxy Binding Ack' to the TWAN. A dashed box labeled '(NSWO)' contains the TWAN sending 'NSWO release local resources' to the PDN GW. Finally, the TWAN sends a 'TWAN specific resource release' to the UE. + +Figure 8.2.5.2.3-2: Disconnection Procedure for PDN and NSWO for PMIP based S2a + +The procedure for disconnection using PMIP based S2a is similar to the sequence for GTP. However, steps 2a and 5 for PMIP consist of Proxy Binding Update with lifetime set to zero (2a) and Proxy Binding Ack (5). + +##### 8.2.5.2.4 HSS/AAA Initiated Disconnection Procedure + +The disconnection sequence in the figure below supports disconnection of one connection triggered by the HSS/AAA (while the rest of the session remains unchanged). If the last connection (or all connections) is being released, all session resources are cleaned up also. + +![Sequence diagram for Disconnection Procedure for GTP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a disconnection procedure initiated by the HSS/AAA. The HSS/AAA sends a 'Session Termination Request' to the AAA Proxy. The AAA Proxy sends a 'Delete Connection (notification)' to the TWAN. A dashed box labeled 'The procedures as figure 8.2.x.2.3-1, step 2 to 6' contains the subsequent interactions between the TWAN, PDN GW, vPCRF, AAA Proxy, and hPCRF. Finally, the AAA Proxy sends a 'Session Termination Response' to the HSS/AAA.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW: Roaming Scenarios + + HSS_AAA->>AAA_Proxy: 1. Session Termination Request + AAA_Proxy->>TWAN: 1b. Delete Connection(notification) + Note right of TWAN: The procedures as figure 8.2.x.2.3-1, step 2 to 6 + AAA_Proxy->>HSS_AAA: 3. Session Termination Response + +``` + +Sequence diagram for Disconnection Procedure for GTP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a disconnection procedure initiated by the HSS/AAA. The HSS/AAA sends a 'Session Termination Request' to the AAA Proxy. The AAA Proxy sends a 'Delete Connection (notification)' to the TWAN. A dashed box labeled 'The procedures as figure 8.2.x.2.3-1, step 2 to 6' contains the subsequent interactions between the TWAN, PDN GW, vPCRF, AAA Proxy, and hPCRF. Finally, the AAA Proxy sends a 'Session Termination Response' to the HSS/AAA. + +Figure 8.2.5.2.4-1: Disconnection Procedure for GTP based S2a + +The procedure to disconnect a PDN /NSWO session for GTP based S2a when triggered by HSS/AAA is shown in the figure above. + +1. The HSS/AAA sends a Session Termination Request message to the TWAN to detach a specific UE. +In (1b), the TWAG sends a delete connection notification message with the IP address and gateway IP address of the connection to trigger release of connection resources at UE. +2. The procedures in 8.2.5.2.3, steps 2 – 6 are followed. +3. Step 3 defined in TS 23.402 [6], subclause 16.3.1.2 is followed. + +![Sequence diagram for Disconnection Procedure for PMIP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. A shaded area labeled 'Roaming Scenarios' covers vPCRF, AAA Proxy, and hPCRF. Step 1: HSS/AAA sends Session Termination Request to TWAN. Step 1b: TWAN sends Delete Connection (notification) to UE. Step 2: A block labeled 'The procedures as figure 8.2.x.2.3-2, step 2 to 6' spans across the diagram. Step 3: TWAN sends Session Termination Response to HSS/AAA.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +Sequence diagram for Disconnection Procedure for PMIP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. A shaded area labeled 'Roaming Scenarios' covers vPCRF, AAA Proxy, and hPCRF. Step 1: HSS/AAA sends Session Termination Request to TWAN. Step 1b: TWAN sends Delete Connection (notification) to UE. Step 2: A block labeled 'The procedures as figure 8.2.x.2.3-2, step 2 to 6' spans across the diagram. Step 3: TWAN sends Session Termination Response to HSS/AAA. + +**Figure 8.2.5.2.4-2: Disconnection Procedure for PMIP based S2a** + +The procedure for disconnection using PMIP based S2a is similar to the sequence for GTP. Step 2 in the figure is based on 8.2.5.2.3 for PMIP. + +#### 8.2.5.2.5 Handover procedure between 3GPP access and WLAN on GTP S2a + +![Sequence diagram of the handover procedure between 3GPP access and WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, Serving GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It is divided into 'Roaming Scenarios' and 'Non-Roaming Scenarios'. The process includes steps like EAP Authentication, IP-CAN Session Establishment, and 3GPP EPS bearer release.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +The diagram illustrates the handover procedure from 3GPP access to Trusted WLAN on GTP S2a. It features the following components and steps: + +- UE**: User Equipment +- TWAN**: Trusted WLAN Access Node +- Serving GW**: Serving Gateway +- PDN GW**: PDN Gateway +- vPCRF**: Virtual PDN Connection Request Function +- AAA Proxy**: AAA Proxy +- hPCRF**: Home PDN Connection Request Function +- HSS/AAA**: Home Subscriber Server / AAA + +**Sequence of Events:** + +- 0. GTP Tunnel**: Initial GTP tunnel between UE and PDN GW. +- 1. Non-3GPP Specific Procedures**: TWAN specific L2 procedures. +- 2. EAP Authentication**: UE performs EAP authentication with TWAN. +- 2. Authentication & Authorization**: TWAN sends authentication request to HSS/AAA via AAA Proxy. +- 3. Request to associate APN/PDN to virtual IP interface**: UE sends request to TWAN. +- 4. Response to associate APN/PDN to virtual IP interface**: TWAN responds to UE. +- 5a. Create Session Request**: TWAN sends request to Serving GW. +- 6. IP-CAN Session Establishment Procedure**: Serving GW initiates procedure with PDN GW and vPCRF. +- 7. Update PDN GW Address**: PDN GW updates address in HSS/AAA. +- 8. Create Session Response**: PDN GW sends response to Serving GW. +- 9. GTP Tunnel**: New GTP tunnel established between UE and PDN GW. +- 5b. Create NSWO connection context**: Serving GW creates context in TWAN. +- 10. L3 Address Request**: UE sends request to TWAN. +- 11. L3 Address Ack**: TWAN responds to UE. +- 12. 3GPP EPS bearer release**: Serving GW and PDN GW release the 3GPP EPS bearer. + +**Scenarios:** + +- Roaming Scenarios**: Involves vPCRF, AAA Proxy, and hPCRF. +- (GTP S2a)**: Path between PDN GW and HSS/AAA. +- (NSWO)**: Path between Serving GW and TWAN. + +Sequence diagram of the handover procedure between 3GPP access and WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, Serving GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It is divided into 'Roaming Scenarios' and 'Non-Roaming Scenarios'. The process includes steps like EAP Authentication, IP-CAN Session Establishment, and 3GPP EPS bearer release. + +Figure 8.2.5.2.6-1: Handover from 3GPP access to Trusted WLAN on GTP S2a + +The handover procedure is based on the Connection Establishment Procedure in 8.2.5.2.2 with the following additions: + +0. The UE is connected in the 3GPP Access and has a PMIPv6 or GTP tunnel on the S5/S8 interface. +1. The initial TWAN specific L2 procedures are performed. These procedures are TWAN specific and outside the scope of 3GPP. +2. If the handover establishes the first PDN connection in WLAN of the UE, EAP procedure is performed in this step. +3. The UE sets up an IP interface to perform initial PDN signalling with the TWAN. During this sequence, if UE and TWAG are Phase 2 compliant, i.e. supporting EPC-routed, handover and multiple PDN connections, the UE sends a request with APN and handover indication, to setup a PDN connection. +4. The TWAN assigns a distinct IPv4 gateway address corresponding to the APN and responds with this address in server-identity and router address for IPv4. For IPv6, the TWAN assigns a distinct IPv6 gateway address (source address in Router Advertisement) and transient multicast address for router solicitation if needed. + +5. The TWAN sends a Create Session Request (APN, handover indication) message to the PDN GW. The APN and handover indication is set in the Create Session Request to allow the PDN GW to re-allocate the same IP address or prefix that was assigned to the UE while it was connected to the 3GPP IP access and to initiate a PCEF-Initiated IP CAN Session Modification Procedure with the PCRF. The APN is used by the PDN GW to determine which PDN connection(s) to handover, in the case that the UE has established multiple PDN connections to different APNs. + +Steps 6 – 11 are performed as Connection Establishment Procedure in 8.2.5.2.2. + +12. The PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure in 3GPP access as defined in TS 23.402 clause 5.6.2.2 or the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401 [6], clause 5.4.4.1. + +### 8.2.5.3 Impacts on existing nodes or functionality + +**Editor's Notes:** Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause. + +This solution minimizes the impact to existing IP configuration procedures – both DHCP, stateless IPv6 auto-configuration by moving all PDN connection signalling to a new protocol that only handles PDN connection aspects. + +For transporting the new PDN connection signalling, ICMP Echo payload proposed here has low impact in terms of implementation on the UE and TWAG. The ICMP messages are echoed back to be compliant with RFC 792 and this adds a response (echo) by definition. Echoing the message takes additional network capacity for the echo message, but does not require significant processing in the TWAN/UE. Two such echoes are needed for each PDN connection setup. A full implementation of L3 control protocol would be more flexible and complete if the time and effort to develop it is acceptable – including its support on UE and TWAG. + +If GAS frames are the chosen method to transport PDN connection signalling, it requires UEs that support WFA/HS2.0 and standards extensions in WFA/HS2.0. This method also requires APs to map the PDN signalling over GAS to backhaul protocol (e.g. RADIUS). + +**Editor's Note:** The implications of using RADIUS to transport the control protocol between AP – TWAN is FFS. + +#### 8.2.5.4 Evaluation + +**Editor's Notes:** The fulfilment to the requirements in Subclause 8.1 as well as simplicity of implementation in the UE should be evaluated. + +### 8.2.6 Solution 6: X + +This solution has been merged with the solution in section 8.2.1 + +### 8.2.7 Solution 7: PPP over Ethernet (PPPoE) + +#### 8.2.7.1 Functional Description + +**Editor's Notes:** It should be described whether and how the solution fulfils the requirements in Subclause 8.1. + +#### 8.2.7.1.1 Overview + +The solution described in this section does not require any new protocols. It is based on the well-known PPP and PPP over Ethernet (PPPoE) protocols, specified in RFC1661 and RFC2516, respectively. These protocols are used to implement both the control plane and the user plane. + +In summary, the solution is characterized by the following: + +1. A PDN Connection over a trusted WLAN (TWAN) is created by establishing a PPPoE/PPP session between the UE and TWAG (Trusted WLAN Access Gateway). +2. The PPPoE protocol is used to create a virtual point-to-point link between the UE and TWAG. +3. The UE encapsulates all traffic pertaining to a PDN connection into PPPoE frames (as shown below). These frames include a PPPoE session ID, which differentiates traffic between different PDN connections. + +![](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +| | | | | +|-------------|---------------------------------------|-------------------------------|-------------| +| WLAN header | PPPoE header<br>(Session ID = 0x065d) | PPP header<br>(Protocol = IP) | IP Datagram | +| | 6 bytes | 2 bytes | | + +4. The TWAG binds a PPPoE session ID with a PDN connection. Traffic arrived from a certain PPPoE session ID is forwarded to the linked PDN connection and vice versa. +5. The TWAG behaves as an Access Concentrator that terminates both PPP and PPPoE protocols. It is very similar to a Broadband Remote Access Server (BRAS) function used in fixed broadband networks. +6. The UE needs to implement the PPP and PPPoE protocols. Both of them are already available in most smartphone platforms. Note that there are already applications available which enable the user to establish PPPoE connections on a smartphone. +7. A Non-Seamless WLAN Offload (NSWO) connection does not use PPP or PPPoE. So, NSWO traffic is transmitted directly over WLAN without any PPPoE encapsulation (as shown below). + +![](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +| | | +|-------------|-------------| +| WLAN header | IP Datagram | +|-------------|-------------| + +8. Since NSWO traffic does not use PPPoE, it does not necessarily need to be routed through TWAG. Instead, it can be optimally routed without going through TWAG. This allows TWAG to be offloaded from NSWO traffic. It also allows the WLAN network and the UE to support NSWO traffic with the currently deployed means (i.e. without any changes). However, the solution allows the AP to tunnel NSWO traffic to TWAG, if this is required. +9. There is no impact on the WLAN AP and on other legacy WLAN components. If the AP supports QoS on the WLAN air interface, it is assumed that the AP can still map between DSCP and WLAN QoS parameters. + +The solution requires the following protocol extensions: + +1. The EAP-AKA protocol is enhanced (as proposed by other solutions too) so that during initial connection to TWAN, the UE becomes aware of the supported capabilities, e.g. whether NSWO is supported, whether single or multiple concurrent PDN connections are supported, etc. This can be easily supported by defining new 3GPP-specific EAP-AKA attributes as already done for other attributes (see e.g. AT\_TRUST\_IND, AT\_IPMS\_IND, AT\_IPMS\_RES). +2. The PPP or PPPoE protocol should be enhanced in order to enable the UE and TWAG to negotiate PDN connectivity parameters (such as APN, attach type) when a new PPPoE/PPP session is created. Such enhancements can be supported by either of the following two options: + - a. Option 1: PDN connectivity parameters are negotiated during PPP session establishment. A new configuration option is specified for PPP, e.g. LCP (Link Control Protocol) or for IPCP and for IPV6CP (IP Configuration Protocol) protocols. This configuration option is used to negotiate specific PDN connectivity parameters (such as APN, attach type, etc.) between the UE and TWAG when a new PPP session is created. For this purpose the PPP Vendor Extensions as specified in RFC2153 could be used. + - b. Option 2: PDN connectivity parameters are negotiated during PPPoE session establishment. The Service-Name Tag within PPPoE could be used to transfer APN information and Vendor-Specific tag could be specified for other parameters. This way the UE can also indicate the requested PDN type (IPv4/IPv6/IPv4v6). + +The details for the above two options are further discussed in clause 8.2.7.2.1. The choice between these two options could be made during the normative work. The figure below illustrates the user-plane operation for a UE that concurrently has a NSWO connection and two PDN connections. Note that traffic for PDN connections is encapsulated + +in PPPoE frames while NSWO traffic does not require such encapsulation. Note also that each PPPoE frame carries a Session ID which is associated with a PDN connection. + +There is no requirement for NSWO traffic (i.e. traffic which does not traverse EPC) to be routed to TWAG. This enables TWAG offload and a single TWAG could support a larger number of UEs. + +![Figure 8.2.7.1.1-1: User plane operation when the UE has a NSWO connection and two PDN connections.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +This diagram illustrates the user plane operation for a UE with a NSWO connection and two PDN connections. The UE contains three traffic paths: PDN-2, PDN-1, and NSWO. PDN-2 and PDN-1 traffic is encapsulated in PPPoE frames with a Session ID (Y and X respectively) and then in IP Datagrams. These are further encapsulated in WLAN headers with DestMAC=TWAG and SrcMAC=UE. NSWO traffic consists only of an IP Datagram encapsulated in a WLAN header. All three types of traffic are sent to an Access Point (AP). The AP forwards traffic based on the DestMAC address. PDN-1 and PDN-2 traffic is forwarded through intermediate WLAN components to a TWAG, where session binding occurs, and then to the EPC via PDN connection 1 and PDN connection 2. NSWO traffic is bypassed from the TWAG. + +Figure 8.2.7.1.1-1: User plane operation when the UE has a NSWO connection and two PDN connections. + +**Figure 8.2.7.1.1-1: User plane operation when the UE has a NSWO connection and two PDN connections.** + +The figure below shows a simplified UE protocol architecture for a UE that concurrently has a NSWO connection and two PDN connections. Each PDN connection requires a PPPoE/PPP instance. NSWO traffic in the UE can be supported without the need for any new protocols. + +![Figure 8.2.7.1.1-2: Simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and two concurrent PDN connections.](f2ea0f64a770b22b902820457d262265_img.jpg) + +This diagram shows the simplified UE architecture. Traffic from upper layers enters a 'Policy based routing' block. From there, it is split into three paths: NSWO, APN-1, and APN-2. The NSWO path goes directly to the WLAN interface. The APN-1 and APN-2 paths each pass through a PPP layer and then a PPPoE layer, resulting in PPPoE Session IDs 'x' and 'y' respectively, before reaching the WLAN interface. + +Figure 8.2.7.1.1-2: Simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and two concurrent PDN connections. + +**Figure 8.2.7.1.1-2: Simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and two concurrent PDN connections.** + +#### 8.2.7.2 Procedures + +##### 8.2.7.2.1.1 PDN Connectivity Parameter Negotiation + +###### 8.2.7.2.1.1 Option 1: PDN connectivity parameters negotiated during PPP session establishment + +The figure below shows how a PDN connection can be established when the PDN connectivity parameters are negotiated with the PPP protocol. + +![Figure 8.2.7.2.1.1-1: PDN connection establishment with Option 1. The diagram shows two cases: Case A (IPv4) and Case B (IPv6). Both cases show the UE and TWAN performing EAP-AKA authentication and PDN connectivity negotiation. In Case A, the UE decides to activate a PDN connection with Type = IPv4. The PPP session establishment (TWAG discovered) is followed by PPPoE Session Data / PPP LCP Configuration Request, PPPoE Session Data / PPP LCP Configuration Ack, PPPoE Session Data / PPP IPCP Configuration Request (Existing Options: IP Address, DNS Server, etc. New Configuration Option includes the requested APN, Attach Type, etc. (NOTE1)), PPPoE Session Data / PPP IPCP Configuration Ack (Existing Options: IPv4 Address, DNS Server, etc. New Configuration Option includes the offered APN (NOTE1)). The result is Case A: PDN establishment with PDP Type = IPv4. In Case B, the UE decides to activate a PDN connection with Type = IPv6. The PPP session establishment (TWAG discovered) is followed by PPPoE Session Data / PPP LCP Configuration Request, PPPoE Session Data / PPP LCP Configuration Ack, PPPoE Session Data / PPP IPV6CP Configuration Request (Existing Options: Interface-Identifier New Configuration Option includes the requested APN, Attach Type, etc. (NOTE1)), PPPoE Session Data / PPP IPV6CP Configuration Ack (Existing Options: Interface-Identifier New Configuration Option includes the offered APN (NOTE1)). The result is Case B: PDN establishment with PDP Type = IPv6, which then leads to Stateless or Stateful Autoconfiguration.](6470d350326789d5306eabcb76533951_img.jpg) + +Figure 8.2.7.2.1.1-1: PDN connection establishment with Option 1. The diagram shows two cases: Case A (IPv4) and Case B (IPv6). Both cases show the UE and TWAN performing EAP-AKA authentication and PDN connectivity negotiation. In Case A, the UE decides to activate a PDN connection with Type = IPv4. The PPP session establishment (TWAG discovered) is followed by PPPoE Session Data / PPP LCP Configuration Request, PPPoE Session Data / PPP LCP Configuration Ack, PPPoE Session Data / PPP IPCP Configuration Request (Existing Options: IP Address, DNS Server, etc. New Configuration Option includes the requested APN, Attach Type, etc. (NOTE1)), PPPoE Session Data / PPP IPCP Configuration Ack (Existing Options: IPv4 Address, DNS Server, etc. New Configuration Option includes the offered APN (NOTE1)). The result is Case A: PDN establishment with PDP Type = IPv4. In Case B, the UE decides to activate a PDN connection with Type = IPv6. The PPP session establishment (TWAG discovered) is followed by PPPoE Session Data / PPP LCP Configuration Request, PPPoE Session Data / PPP LCP Configuration Ack, PPPoE Session Data / PPP IPV6CP Configuration Request (Existing Options: Interface-Identifier New Configuration Option includes the requested APN, Attach Type, etc. (NOTE1)), PPPoE Session Data / PPP IPV6CP Configuration Ack (Existing Options: Interface-Identifier New Configuration Option includes the offered APN (NOTE1)). The result is Case B: PDN establishment with PDP Type = IPv6, which then leads to Stateless or Stateful Autoconfiguration. + +**Figure 8.2.7.2.1.1-1: PDN connection establishment with Option 1.** + +NOTE 1: Although the figure above shows new configuration options for the IPCP and IPV6CP protocols, those new configuration options could be specified for the LCP protocol instead. + +For establishing a PDN connection with type IPv4, the UE uses the IP Control Protocol (IPCP), as specified in RFC 1332, “The PPP Internet Protocol Control Protocol”. With IPCP, the UE receives IPv4 configuration parameters, such as an IPv4 address, DNS servers, etc. + +For establishing a PDN connection with type IPv6, the UE uses the IPv6 Control Protocol (IPv6CP), as specified in RFC 5072, “IPv6 over PPP”. With IPv6CP, the UE negotiates an “Interface-Identifier” (a 64-bit interface identifier) to be used for address autoconfiguration. On the established PPP session the UE receives a Router Advertisement and, based on its content, the UE uses either stateless or stateful autoconfiguration. Since the Router Advertisement is sent to UE over a point-to-point link, it is possible to use stateless autoconfiguration in a similar manner as used over 3GPP RAN, i.e. the UE can receive the /64 IPv6 prefix in the RA message. Moreover it is also possible to use stateful autoconfiguration for some UEs (although this is not typically needed). + +To support PDN connections with type IPv4v6, the UE can establish two PPP connections over the same PPPoE session: one for IPv4 (using IPCP) and another for IPv6 (using IPv6CP). Traffic on both PPP connections is transported on the same PPPoE session and is thus mapped to the same PDN connection. + +Editor’s Note: It is FFS if the UE needs to explicitly indicate the requested PDN type within the new configuration options. + +###### 8.2.7.2.1.2 Option 2: PDN connectivity parameters negotiated during PPPoE session establishment + +The figure below shows how a PDN connection can be established when the PDN connectivity parameters are negotiated with the PPPoE protocol. + +![Sequence diagram showing PDN connection establishment with Option 2 between UE and TWAN. The process starts with EAP-AKA Authentication and PDN Connectivity Supported. The UE decides to activate a PDN connection with Type = IPv4. The sequence includes PPPoE Discovery Initiation (Broadcast), PPPoE Discovery Offer (from TWAG) with AC-name: TWAG-1, PPPoE Discovery Request (to TWAG) with AC-name: TWAG-1, Service-Name: APN, and Vendor-Specific: Attach-Type, PDN-Type = IPv4. The TWAG responds with PPPoE Discovery Session-Confirmation (from TWAG) with AC-name: TWAG-1, Session ID = 0x065d. The UE then sends PPPoE Session Data / PPP LCP Configuration Request, which the TWAG responds with PPPoE Session Data / PPP LCP Configuration Ack. The UE then sends PPPoE Session Data / PPP IPCP Configuration Request with Existing Options: IPv4 Address, DNS Server, etc., which the TWAG responds with PPPoE Session Data / PPP IPCP Configuration Ack with Existing Options: IPv4 Address, DNS Server, etc. The entire process is labeled Case C: PDN establishment with PDP Type = IPv4.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Case C: PDN establishment with +PDP Type = IPv4 + +Sequence diagram showing PDN connection establishment with Option 2 between UE and TWAN. The process starts with EAP-AKA Authentication and PDN Connectivity Supported. The UE decides to activate a PDN connection with Type = IPv4. The sequence includes PPPoE Discovery Initiation (Broadcast), PPPoE Discovery Offer (from TWAG) with AC-name: TWAG-1, PPPoE Discovery Request (to TWAG) with AC-name: TWAG-1, Service-Name: APN, and Vendor-Specific: Attach-Type, PDN-Type = IPv4. The TWAG responds with PPPoE Discovery Session-Confirmation (from TWAG) with AC-name: TWAG-1, Session ID = 0x065d. The UE then sends PPPoE Session Data / PPP LCP Configuration Request, which the TWAG responds with PPPoE Session Data / PPP LCP Configuration Ack. The UE then sends PPPoE Session Data / PPP IPCP Configuration Request with Existing Options: IPv4 Address, DNS Server, etc., which the TWAG responds with PPPoE Session Data / PPP IPCP Configuration Ack with Existing Options: IPv4 Address, DNS Server, etc. The entire process is labeled Case C: PDN establishment with PDP Type = IPv4. + +**Figure 8.2.7.2.1.2-1: PDN connection establishment with Option 2.** + +In the PPPoE Discovery Request message the UE includes in the existing *Service-Name* tag (see RFC2516) the requested APN. Also, in a *Vendor-Specific* tag (the details of which should be specified by 3GPP) the UE includes the Attach-Type and the requested PDN-Type. After the PPPoE session is established, the TWAG may start the GTP/PMIP tunnel over S2a establishment, which can result in faster PDN connection creation. + +After the PPPoE session is established the UE requests configuration data with the IPCP and/or IPV6CP (see RFC5072) protocol. If the negotiated PDN Type is IPv4v6, the UE establishes two PPP sessions, one with IPCP and another with IPV6CP. The allocation of IPv6 prefix and address can happen in the same way as in option 1. + +The main advantages of the Option 2 are the following: + +- No modifications to existing IPCP and IPV6CP are needed +- Avoids potential protocol ambiguities when providing both IPv4 and IPv6 on the same APN. IPV6CP for IPv6 is different to IPCP for IPv4. The PDN type is indicated within the PPPoE message. +- The network can learn sooner which APN the UE intend to use and thus the network can start creating the GTP/PMIP tunnel over S2a interface earlier (during PPPoE discovery), which can result in faster PDN connection creation. + +#### 8.2.7.2.2 Initial Attach and UE-initiated Connectivity to PDN + +The signaling flow below shows the steps carried out when a UE connects to a trusted WLAN (TWAN) and establishes a NSWO connection along with a PDN connection. The figure is generic and applies to both GTP S2a and PMIP S2a. + +![Sequence diagram illustrating the simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and a concurrent PDN connection. The diagram shows interactions between UE, TWAN, P-GW, PCRF, and HSS/AAA. It details the process from WLAN discovery and EAP-AKA authentication to PPPoE session establishment and PDN connection setup.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +The diagram illustrates the following sequence of events: + +- WLAN discovery and selection:** The UE performs WLAN discovery and selection within the TWAN. +- EAP-AKA Authentication:** The UE sends an EAP-AKA Authentication request to the HSS/AAA via the TWAN. The message indicates that NSWO and Multi-PDN Connectivity are supported. +- DHCPv4 or SLAAC:** The UE receives an IP configuration for NSWO from the TWAN via DHCPv4 or SLAAC. +- NSWO traffic:** NSWO traffic is shown being transmitted between the UE and the TWAN. +- UE decides to activate a PDN Connection:** The UE makes a decision to activate a PDN connection. At this point, the data packet structure is a **WLAN header** followed by an **IP Datagram**. +- PPPoE Discovery:** The UE initiates PPPoE Discovery (Broadcast). The TWAN responds with a PPPoE Discovery Offer (from TWAG). The UE sends a PPPoE Discovery Request (to TWAG). The TWAG responds with a PPPoE Discovery Session-Confirmation (from TWAG), assigning a **Session ID = 0x065d**. A note indicates: "TWAG discovery and PPPoE session establishment. All subsequent frames include the allocated Session ID." +- PPPoE Session Data / PPP LCP Configuration:** The UE sends a PPPoE Session Data / PPP LCP Configuration Request. The TWAG responds with a PPPoE Session Data / PPP LCP Configuration Ack. A note indicates: "PPP session establishment (PPP authentication not required)". +- PDN Connection establishment:** The UE sends a PPPoE Session Data / PPP IPCP Configuration Request. The TWAG responds with a PPPoE Session Data / PPP IPCP Configuration Ack. This request includes "Existing Options: IP Address, DNS Server, etc." and a "New Configuration Option includes the requested APN, Attach Type, etc.". The TWAG also sends a PDN Connection establishment message to the P-GW. The P-GW sends an IP-CAN Session Establishment/Modification message to the PCRF. +- PDN traffic:** PDN traffic is shown being transmitted between the UE and the P-GW. +- UE may decide to activate another PDN Connection:** The UE may decide to activate another PDN connection. At this point, the data packet structure is a **WLAN header**, followed by a **PPPoE header (Session ID = 0x065d)** (6 bytes), a **PPP header (Protocol = IP)** (2 bytes), and an **IP Datagram**. + +Sequence diagram illustrating the simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and a concurrent PDN connection. The diagram shows interactions between UE, TWAN, P-GW, PCRF, and HSS/AAA. It details the process from WLAN discovery and EAP-AKA authentication to PPPoE session establishment and PDN connection setup. + +**Figure 8.2.7.2.2-2: Simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and a concurrent PDN connection.** + +NOTE 1: The above figure assumes that Option 1 is used for PDN Connectivity parameter negotiation (see clause 8.2.7.2.1). However, Option 2 is equally applicable. + +During the EAP-AKA authentication the UE becomes aware of the services offered by the trusted WLAN network, e.g. whether NSWO is supported, whether a single and/or multiple concurrent PDN connections are supported, etc. This can be accomplished by defining 3GPP-specific EAP-AKA attributes. + +When the UE decides to activate a PDN connection (with type IPv4) over the TWAN, it uses the normal PPPoE procedures to discover the TWAG and to establish a new PPPoE session with the TWAG. A new session ID is allocated by TWAG to this PPPoE session (for example: Session ID=0x065d, as shown in the figure). + +Subsequently, the UE initiates the establishment of a PPP session according to the normal PPP procedures. Note that after the LCP negotiation: + +- The standard PPP authentication could be used if the requested PDN connection is needed for “Non-Transparent access to an Intranet or ISP” (see TS 29.061); or +- The standard PPP authentication could be skipped, if the requested PDN connection is needed for “Transparent access to the Internet” (see TS 29.061). In this case, even when the UE sends a PPP authentication request the TWAG may always accept it. + +In the figure above, it is assumed that during the IPCP configuration a new IPCP configuration option is used. This allows the UE to request a specific APN, attach type, etc. and allows the TWAG to respond with an offered APN and possibly other parameters. Although the figure above shows new configuration options for the IPCP protocol, those new configuration options could be specified for the LCP protocol instead. PPP Vendor Extensions should be specified by 3GPP to support these new configuration options. + +Note that the signaling flow shown in the figure above is based on known steps already used in practice. The only extension required is (a) the new EAP-AKA attribute(s) and (b) the new PPP configuration option(s) that allows the negotiation of PDN connectivity parameters between the UE and TWAG. + +#### 8.2.7.2.3 PDN Connection Release + +The figure below illustrates the control-plane signaling flow when the UE initiates a PDN connection release. The UE simply terminates the corresponding PPP session and subsequently terminates the associated PPPoE session too. + +![Sequence diagram of PDN connection release initiated by UE](b904ac2472cab80892d1e783e6230d6e_img.jpg) + +The diagram illustrates the control-plane signaling flow for a PDN connection release initiated by the UE. The entities involved are UE, TWAN, P-GW, PCRF, and HSS/AAA. The sequence of messages is as follows: + +- The UE decides to deactivate a PDN Connection. +- The UE sends a PPPoE Session Data / PPP LCP Terminate Request to the TWAN. The Session ID is 0x065d. +- The TWAN maps the PPPoE Session ID to an EPS Bearer Identity. +- The TWAN sends a PDN Connection Release Request to the P-GW. +- The P-GW sends an Update PGW Address message to the PCRF. +- The P-GW sends a PDN Connection Release Response to the TWAN. A dashed double-headed arrow between the P-GW and PCRF indicates an IP-CAN Session Termination. +- The TWAN sends a PPPoE Session Data / PPP LCP Terminate Ack to the UE. +- The UE sends a PPPoE Discovery Terminate to the TWAN. The Session ID is 0x065d. + +Sequence diagram of PDN connection release initiated by UE + +**Figure 8.2.7.2.3-1: PDN connection release initiated by UE.** + +The figure below illustrates the control-plane signaling flow when the P-GW initiates a PDN connection release. Note that the TWAN could also initiate the PDN connection release. In this case, the TWAN terminates the PPP session with the UE and sends the Delete Session Request to P-GW. + +The TWAG may use the standard LCP Echo Request/Reply procedure (or other link management facilities provided by PPPoE) to determine when a UE becomes unreachable. In this case, the TWAG may detach the UE from EPC by releasing all its PDN connections. + +![Sequence diagram showing PDN connection release initiated by P-GW. The diagram involves five entities: UE, TWAN, P-GW, PCRF, and HSS/AAA. The sequence starts with a PDN Connection Release Request from P-GW to TWAN. TWAN maps the EPS Bearer Identity to a PPPoE Session. TWAN sends a PPPoE Session Data / PPP LCP Terminate Request to UE with Session ID = 0x065d. UE responds with a PPPoE Session Data / PPP LCP Terminate Ack. TWAN sends a PDN Connection Release Response to P-GW. P-GW sends an Update PGW Address to PCRF. A dashed double-headed arrow labeled 'IP-CAN Session Termination' is shown between P-GW and PCRF. Finally, UE sends a PPPoE Discovery Terminate with Session ID = 0x065d to TWAN.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant P-GW + participant PCRF + participant HSS/AAA + + P-GW->>TWAN: PDN Connection Release Request + Note right of TWAN: TWAG maps the EPS Bearer Identity to a PPPoE Session + TWAN->>UE: PPPoE Session Data / PPP LCP Terminate Request +Session ID = 0x065d + UE->>TWAN: PPPoE Session Data / PPP LCP Terminate Ack + TWAN->>P-GW: PDN Connection Release Response + P-GW->>PCRF: Update PGW Address + Note right of P-GW: IP-CAN Session Termination + UE->>TWAN: PPPoE Discovery Terminate +Session ID = 0x065d + +``` + +Sequence diagram showing PDN connection release initiated by P-GW. The diagram involves five entities: UE, TWAN, P-GW, PCRF, and HSS/AAA. The sequence starts with a PDN Connection Release Request from P-GW to TWAN. TWAN maps the EPS Bearer Identity to a PPPoE Session. TWAN sends a PPPoE Session Data / PPP LCP Terminate Request to UE with Session ID = 0x065d. UE responds with a PPPoE Session Data / PPP LCP Terminate Ack. TWAN sends a PDN Connection Release Response to P-GW. P-GW sends an Update PGW Address to PCRF. A dashed double-headed arrow labeled 'IP-CAN Session Termination' is shown between P-GW and PCRF. Finally, UE sends a PPPoE Discovery Terminate with Session ID = 0x065d to TWAN. + +**Figure 8.2.7.2.3-2: PDN connection release initiated by P-GW.** + +#### 8.2.7.2.4 Handover from 3GPP access to WLAN + +The UE can handover a first PDN connection from 3GPP access to WLAN by re-using the “Initial Attach and UE-Initiated Connectivity to PDN” procedure described above. In the handover scenario, during the PPP session establishment the UE provides the associated APN and indicates “Attach Type = Handover”. Existing procedures can then be used (e.g. procedures specified in TS 23.402 for IP address preservation) to make sure that the PDN connection over the trusted WLAN uses the same PGW and the same IP address. If the UE wants to handover additional PDN connections from 3GPP access to WLAN, it should establish additional PPP connections over WLAN by providing the associated APNs and “Attach Type = Handover”. + +#### 8.2.7.3 Impacts on existing nodes or functionality + +**Editor's Notes: Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause.** + +#### 8.2.7.4 Evaluation + +The solution supports the following capabilities: + +1. Supports one or more concurrent PDN connections. Each PDN connection requires a PPP/PPPoE protocol instance in the UE and in the TWAG. +2. Supports NSWO traffic and concurrently EPC traffic (via one or more PDN connections). +3. Supports IPv4, IPv6 and IPv4v6 PDN connections. +4. Supports IPv6 stateless autoconfiguration. It does not mandate stateful DHCPv6, thus simplifies UE implementation. +5. Supports PDN connection handover from 3GPP to TWAN with IP address preservation. +6. Supports TWAG discovery by means of standard PPPoE procedures. +7. Supports PDN connections for “Non-Transparent access to an Intranet or ISP” and for “Transparent access to the Internet” (see TS 29.061). Standard PPP authentication can be used to authenticate PDN connections for “Non-Transparent access to an Intranet or ISP”. +8. Supports SaMOG phase-2 capable UEs and “legacy” (pre-Rel-12) UEs on the same TWAN (and on the same SSID). + +The solution is also characterized by the following features: + +1. NSWO traffic does not need to go through TWAG. This enables TWAG offload and can lead to deployments with reduced cost. +2. NSWO traffic is transmitted without any encapsulation. This improves air-interface utilization and reduces complexity. +3. There is no need for special signaling to establish tunnels / point-to-point connections for NSWO traffic. This improves efficiency and reduces complexity. +4. It is based on the well-known PPP/PPPoE protocols. Thus avoids the effort to standardize and implement new protocols in the UE and in the network. In addition, it minimizes the need for new conformance specifications; only conformance testing against the new PPP configuration options and EAP-AKA attributes is required. +5. The PPP/PPPoE protocols are already supported by many smartphones (typically as build-in or loadable kernel modules). Thus, UE modifications are minimized. +6. Standard PPP/PPPoE procedures can be used to monitor the link between the UE and TWAG. For example, the TWAG may use the standard LCP Echo Request/Reply procedure to determine when a UE becomes unreachable and then trigger Detach procedures. +7. The standard PPP LCP protocol can be used to negotiate an MTU for each PDN connection. +8. The standard PPP Compression Control Protocol (CCP) can be used to enable data compression between the UE and TWAG. Although CCP is not considered necessary over WLAN, it is a readily available option for deployment. +9. The PDN connection establishment can be expedited when Option 2 (as per clause 8.2.7.2.1) is applied. +10. It is supported by existing WLAN APs. PPPoE frames can traverse existing WLAN APs without any modification. When the AP supports QoS on the WLAN air interface, it is expected that the AP can still map between DSCP and WLAN QoS parameters. + +The solution requires the following protocol extensions: + +1. The EAP-AKA protocol should be enhanced so that during initial connection to TWAN, the UE becomes aware of the supported capabilities, e.g. whether NSWO is supported, whether single or multiple concurrent PDN connections are supported, etc. This can be easily supported by defining new 3GPP-specific EAP-AKA attributes as already done for other attributes (see e.g. AT\_TRUST\_IND, AT\_IPMS\_IND, AT\_IPMS\_RES). +2. The PPP or PPPoE protocol should be enhanced in order to enable the UE and TWAG to negotiate PDN connectivity parameters (such as APN, attach type) when a new PPPoE or PPP session is created. Such enhancements can be supported by either of the following two options presented in clause 8.2.7.2.1. + +### 8.2.8 Solution 8: Solution using new 3GPP specific LLC/SNAP header settings + +#### 8.2.8.1 Functional Description + +#### 8.2.8.1.1 General + +This solution addresses the user plane problem of supporting multiple PDN connections between the UE and the TWAG. + +The solution has the following aspects: + +- a) Works both for the case where an AP only supports 802.11 $\leftrightarrow$ Ethernet II bridging or where it supports 802.3 $\leftrightarrow$ 802.11 bridging. +- b) The LLC Address field on the wireless link (and optionally on the 802.3 LAN, if 802.3 is used) is always set to indicate that a SNAP header is present. +- c) The OUI (Organisationally Unique Identifier) of the SNAP header on the wireless link (and optionally on the 802.3 LAN, if 802.3 is used) is set to the value used in RFC 1042 (00 00 00). +- d) 3GPP requests $x$ (tbd) new EtherType values from the IEEE Registration Authority (note that: a request to IEEE RA for 12 EtherType values would be sufficient for supporting up to the maximum of 11 PDN connections per UE with one spare for support of a 3GPP control plane protocol if needed). These EtherTypes will be sufficient in number to provide differentiation between PDN connections as well as differentiation of any 3GPP control plane protocol that needs to be supported. +- e) These new EtherType values are directly mapped onto the SNAP Protocol Type field on the 802.11 network. On an Ethernet II network these new EtherType values are used to populate the EtherType field (and there is a one to one mapping between 802.11 Protocol Type and Ethernet II EtherType). On an 802.3 fixed network the EtherType values are used to populate the Protocol Type field (and there is a one to one mapping between SNAP Protocol Type on 802.11 and SNAP Protocol Type on 802.3 in the bridging function). +- f) In the uplink, the combination of source (device) MAC address and EtherType value can be used by the TWAG to bind the traffic to the appropriate GTP tunnel. In the downlink the TWAG binds the GTP tunnel to the appropriate Ethernet II 'link' by appropriate setting of the destination (device) MAC address and EtherType value. +- g) The allocation of a particular EtherType/Protocol Type value to a particular user plane PDN connection can be established dynamically via signalling. +- h) Since conventionally EtherType is used to indicate the higher layer protocol type that is associated with the payload, a method is needed by which the UE or TWAG can differentiate between IPv4 and IPv6 in the case of a dual stack PDN connection. This issue is solved at the IP layer since the UE or TWAG can inspect the first 4 bits of the payload to determine the IP type of the packet. In both IPv4 and IPv6 the first 4 bits of the payload convey 'version' of the IP packet. In IPv4 'version' takes the value '4' and in IPv6 it takes the value '6'. Note that an assumption here is that the only types of packet which need to be carried on the PDN connection are packets of type IPv4 and IPv6. + +##### 8.2.8.1.2 Protocol stack + +Figure 8.2.8.1.2-1 shows an example user plane protocol stack for this solution where the AP and TWAG are implemented separately and the AP provides a bridging function to an 802.3 LAN. + +![Figure 8.2.8.1.2-1: Example user plane protocol stack where 802.11 ↔ 802.3 bridging is used. The diagram shows five vertical protocol stacks. From left to right: Device (STA/UE) with layers App, TCP, IP, SNAP, LLC, 802.11 MAC, 802.11 PHY; AP with layers 802.11 MAC, 802.11 PHY on the left and 802.3 MAC, 802.3 PHY on the right; Router/AG with layers GTP-U, UDP, IP, L2, L1 on the right and SNAP, LLC, 802.3 MAC, 802.3 PHY on the left; P-GW with layers IP, L2, L1 on the right and GTP-U, UDP, IP, L2, L1 on the left; App server with layers App, TCP, IP, L2, L1. Horizontal lines connect corresponding layers across the stacks.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +Figure 8.2.8.1.2-1: Example user plane protocol stack where 802.11 ↔ 802.3 bridging is used. The diagram shows five vertical protocol stacks. From left to right: Device (STA/UE) with layers App, TCP, IP, SNAP, LLC, 802.11 MAC, 802.11 PHY; AP with layers 802.11 MAC, 802.11 PHY on the left and 802.3 MAC, 802.3 PHY on the right; Router/AG with layers GTP-U, UDP, IP, L2, L1 on the right and SNAP, LLC, 802.3 MAC, 802.3 PHY on the left; P-GW with layers IP, L2, L1 on the right and GTP-U, UDP, IP, L2, L1 on the left; App server with layers App, TCP, IP, L2, L1. Horizontal lines connect corresponding layers across the stacks. + +**Figure 8.2.8.1.2-1: Example user plane protocol stack where 802.11 ↔ 802.3 bridging is used** + +Figure 8.2.8.1.2-2 shows an example user plane protocol stack where the AP and TWAG are implemented separately and the AP provides a bridging function to an Ethernet II LAN. + +![Figure 8.2.8.1.2-2: Example user plane protocol stack where 802.11 ↔ Ethernet II bridging is used. The diagram shows five vertical protocol stacks. From left to right: Device (STA/UE) with layers App, TCP, IP, SNAP, LLC, 802.11 MAC, 802.11 PHY; AP with layers SNAP, LLC, 802.11 MAC, 802.11 PHY on the left and Ethernet II MAC, 802.3 PHY on the right; Router/AG with layers GTP-U, UDP, IP, L2, L1 on the right and Ethernet II MAC, 802.3 PHY on the left; P-GW with layers IP, L2, L1 on the right and GTP-U, UDP, IP, L2, L1 on the left; App server with layers App, TCP, IP, L2, L1. Horizontal lines connect corresponding layers across the stacks.](fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg) + +Figure 8.2.8.1.2-2: Example user plane protocol stack where 802.11 ↔ Ethernet II bridging is used. The diagram shows five vertical protocol stacks. From left to right: Device (STA/UE) with layers App, TCP, IP, SNAP, LLC, 802.11 MAC, 802.11 PHY; AP with layers SNAP, LLC, 802.11 MAC, 802.11 PHY on the left and Ethernet II MAC, 802.3 PHY on the right; Router/AG with layers GTP-U, UDP, IP, L2, L1 on the right and Ethernet II MAC, 802.3 PHY on the left; P-GW with layers IP, L2, L1 on the right and GTP-U, UDP, IP, L2, L1 on the left; App server with layers App, TCP, IP, L2, L1. Horizontal lines connect corresponding layers across the stacks. + +**Figure 8.2.8.1.2-2: Example user plane protocol stack where 802.11 ↔ Ethernet II bridging is used** + +##### **8.2.8.1.3 Protocol header** + +Figure 8.2.8.1.3-1 shows the population of LLC and SNAP fields on 802 (W)LAN's. + +| | | | | | | | +|------------|----------------------------------|-----------------------------|--------------------------------------|---------------------------|--------------------------|-----| +| MAC header | LLC<br>Destination<br>SAP = 0xAA | LLC<br>Source<br>SAP = 0xAA | SNAP OUI<br>= 00 00 00<br>(RFC 1042) | SNAP Protocol<br>Type = Y | IP header and<br>payload | FCS | +| MAC | LLC | | SNAP | | IP | | + +Y is an EtherType value that has been allocated to 3GPP by the IEEE Registration Authority and which may correspond to a specific PDN connection. The mapping between a given value Y and a given PDN connection is established via signalling. + +**Figure 8.2.8.1.3-1: User plane packet as seen on an 802 (W)LAN** + +Figure 8.2.8.1.3-2 shows the population of the MAC header on an Ethernet II packet. + +| | | | | | +|--------------------|---------------|-----------|------------|-----| +| Destination<br>MAC | Source<br>MAC | EtherType | Frame Body | FCS | +|--------------------|---------------|-----------|------------|-----| + +The EtherType value would be one that has been allocated to 3GPP by the IEEE Registration Authority and which may correspond to a specific PDN connection. The mapping between a given EtherType value and a given PDN connection is established via signalling. The EtherType value is the same as that which is used in the Protocol Type field across the wireless 802.11 interface + +**Figure 8.2.8.1.3-2: User plane packet as seen on an Ethernet II wired interface** + +#### 8.2.8.2 Procedures + +An LLC/SNAP user plane solution can be used in conjunction with a variety of the signaling solutions which are described as part of other solutions in this TR. These signaling possibilities are now discussed and any modifications to those proposals which are required in order to support the LLC/SNAP based user plane solution are described. + +It is worth noting that some of the signaling options presented within other solutions make use of new signaling protocols which would be defined by 3GPP. The LLC/SNAP solution can provide support for such protocols. This is achieved simply by reserving one of the 3GPP specific EtherType values for this purpose. For example an EtherType value *p* could correspond to a 3GPP specified control plane protocol that runs between the UE and the TWAG. If either the UE or the TWAG receives a frame with an EtherType value set to *p* then it would process the frame contents as a 3GPP control plane frame. Note that this reserved value *p* would be defined in a 3GPP specification and would not be dynamically changeable. + +Non Seamless Wireless Offload (NSWO) could be supported by the device in the way that the device would typically use today when directly accessing the internet over WLAN (eg SNAP OUI set to 00 00 00 (RFC 1042) and SNAP Protocol Type set to the EtherType value corresponding to the appropriate higher layer protocol (IP=0x0800, ARP=0x0806), and with IP address locally allocated by the TWAN). + +From a signaling point of view the UE needs to learn both the MAC address of the TWAG and the EtherType value that it should use for a given PDN connection. Regards the former issue, an approach which will be common to many if not all of the signaling solutions will be for the UE to determine the MAC address of the TWAG through DHCP/ARP messaging using a broadcast 802.11 MAC address. The TWAG also needs to learn the MAC address of the device and the EtherType values that should be bound with given GTP tunnels. + +Note: Because with this proposal EtherType is encapsulated in a Protocol Type field on an 802.3 LAN or on an 802.11 WLAN, and since EtherType is always used on Ethernet II, in the remainder of this section we will in general just use the term ‘EtherType’ as opposed to ‘Protocol Type’. + +| <b>Solution</b> | <b>Signalling aspects of solution compatible with SNAP/LLC user plane solution?</b> | <b>Comment</b> | +|-----------------------------------------------------------------|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution 1: Two Scenario Approach | Yes | <p>The proposed UE-TWAG Wireless LAN Control Protocol (WLCP) can be supported by defining, in a 3GPP specification, one of the 3GPP specific EtherType values for use in carrying WLCP frames.</p> <p>As part of the ‘UE initiated Connectivity to PDN in WLAN GTP S2a’ procedure the TWAG allocates an EtherType value for each PDN connection which is being established and indicates this EtherType assignment and its association with a specific PDN connection to the UE using WLCP.</p> <p>Other procedures such as handover and PDN disconnection procedures make use of WLCP in the same way.</p> <ul style="list-style-type: none"> <li>• UE learns TWAG MAC address: DHCP/ARP on broadcast MAC addr</li> <li>• UE learns EtherType/PDN connection binding: WLCP</li> <li>• TWAG learns device MAC address: WLCP</li> <li>• TWAG learns GTP/EtherType binding: TWAG configures it</li> </ul> | +| Solution 2: Layer 2 solution based on per-APN/NSWO VLAN marking | Yes | <p>The first preparation step within the ‘UE requested PDN or NSWO connectivity’ (Section 8.2.2.1.3) procedure would be modified so that the UE can be informed, for each APN, of one EtherType value to be used for conveying user plane traffic and a second value to be used for conveying DHCP traffic that is associated with that APN. This request and response signaling takes place via extensions to EAP-AKA or ANQP.</p> <p>In the second execution step of this procedure the UE sends a DHCP request message using the EtherType value which has been allocated for carrying DHCP messages that is associated with the particular APN for which the IP address is being requested. When the TWAG receives this message it can determine, using the source (device) MAC address and the EtherType setting for which PDN the session is to be set up. The DHCP signaling from TWAG to the UE which carries the allocated IP address also makes use of this APN and DHCP specific EtherType header value when building the Layer 2 frame, so that the UE can associate the allocated IP address with the correct PDN connection.</p> <p>Similarly, PDN disconnection makes use of the same EtherType values at Layer 2 for conveying the DHCP signaling to release the IP address.</p> <p>If this signaling approach were to be adopted and if up to 11 APN’s per device are to be supported then 3GPP would need to request 22 EtherType values from the IEEE RA.</p> | + +| | | | +|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | <ul style="list-style-type: none"> <li>UE learns TWAG MAC address: DHCP/ARP on broadcast MAC addr</li> <li>UE learns EtherType/PDN connection binding: EAP-AKA / ANQP</li> <li>TWAG learns device MAC address: During second DHCP execution step</li> <li>TWAG learns GTP/EtherType binding: TWAG configures it</li> </ul> | +| Solution 3: Stateful DHCP based solution | Yes | <p>The DHCP messaging is modified so that instead of the UE / TWAG indicating GRE keys the UE /TWAG indicates the EtherType value that will be used by certain PDN connections.</p> <ul style="list-style-type: none"> <li>UE learns TWAG MAC address: DHCP/ARP on broadcast MAC addr</li> <li>UE learns EtherType/PDN connection binding: modifications to DHCP</li> <li>TWAG learns device MAC address: DHCP procedure</li> <li>TWAG learns GTP/EtherType binding: TWAG configures it</li> </ul> | +| Solution 4 | N/A | No signalling solution provided. | +| Solution 5: Associating APN/PDN with virtual IP interface | Partially (some aspects of the solution may be used in conjunction with SNAP/LLC based approach) | <p>Solution 8 (SNAP/LLC based user plane) does support the use of a new 3GPP defined 'PDN Control protocol' as is defined as part of this solution. However, the methods described in Solution 5 for transporting the 'PDN Control Protocol', eg use of ICMP Echo payload or 802.11 GAS frame are competing methods to the approach proposed in Solution 8 (which instead would support such a 'PDN Control protocol' through the use of a specific EtherType value).</p> <p>(See for example comments under solution 1)</p> | +| Solution 6: X | Yes | <p>This approach proposes the use of a new 3GPP specified TSM (TWAN Session Management) control plane protocol to run between the UE and the TWAG. Solution 8 provides support for a new control plane protocol as discussed above.</p> <p>Instead of delineating PDN connections through VLAN ID or TWAG MAC address, if this signaling solution were to be combined with Solution 8 then Ethertype would be used to distinguish between PDN connections. These settings would be conveyed between UE and TWAG within the TSM protocol.</p> <ul style="list-style-type: none"> <li>UE learns TWAG MAC address: DHCP/ARP on broadcast MAC addr</li> <li>UE learns EtherType/PDN connection binding: TSM</li> <li>TWAG learns device MAC address: TSM</li> <li>TWAG learns GTP/EtherType binding: TWAG configures it</li> </ul> | +| Solution 7: PPP over Ethernet (PPPoE) | No | If a PPPoE approach is adopted for signaling then it would seem logical to use it in conjunction with the PPPoE user plane solution. | +| Solution 8 – Solution using new 3GPP specific LLC/SNAP header | N/A | | +| Solution 9 – EAP based signaling solution | Yes | EAP based signaling can be used for conveying the association between a specific PDN connection and an EtherType value. | + +| | | | +|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | <ul style="list-style-type: none"> <li>• UE learns TWAG MAC address: DHCP/ARP on broadcast MAC addr or EAP</li> <li>• UE learns EtherType/PDN connection binding: EAP modification.</li> <li>• TWAG learns device MAC address: May require TWAN internal signaling to communicate this setting to the TWAG from the entity terminating EAP.</li> <li>• TWAG learns GTP/EtherType binding: TWAN sets it. May require TWAN internal signaling to communicate this setting to the TWAG.</li> </ul> | +|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### 8.2.8.3 Impacts on existing nodes or functionality + +Editor's Notes: Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause. + +#### 8.2.8.4 Evaluation + +The evaluation of this user plane solution against relevant evaluation criteria is provided below: + +- i) Impacts to existing network deployment + - a. New requirements on WLAN APs compared to Rel-11 + - i. No new requirements + - b. Additional assumptions on AP-TWAG link + - i. No additional assumptions +- ii) Impacts to UE + - a. UE needs to populate EtherType value appropriately for the given PDN connection / control plane protocol. +- iii) Impacts to 3GPP protocols/extensions (e.g. EAP AKA') + - a. N/A (Solution 8 defines user plane solution between UE and TWAG) +- iv) Impacts to protocols defined by other SDOs (e.g. DHCP) + - a. No impact to protocols. + - i. 3GPP would need to ask the IEEE Registration Authority for multiple (eg 12) new EtherType values to be allocated for use by 3GPP. +- v) Control plane + - a. Latency/load of first/additional PDN connections setup and handover procedures + - i. N/A (Solution 8 is a user plane solution) + - b. Network element impacts (e.g. AAA signaling etc.) + - i. N/A (Solution 8 is a user plane solution) +- vi) Compliance to clause 8.1 SaMOG phase-2 system requirements + - a. Co-existence with Rel-11 SaMOG + +- i. This solution can coexist with Rel 11 SaMOG on the user plane. + - b. Support for IP address preservation during handover + - i. N/A (Solution 8 is a user plane solution) + - c. Simultaneous support for S2a EPC-routed and NSWO; support of simultaneous multiple PDN connections + - i. This is supported. +- vii) Others functional limitations + - i. None + +### 8.2.9 Solution 9: EAP based signaling solution + +#### 8.2.9.1 Functional Description + +**Editor's Notes: It should be described whether and how the solution fulfils the requirements in Subclause 8.1.** + +#### 8.2.9.1.1 General + +In this solution all 3GPP specification signaling between the UE and the network is carried within EAP signaling. This solution is based on defining a new attribute for EAP to transfer 3GPP specific information (e.g. APN, handover indication) between the UE and the network. This type of new attribute for EAP is also needed if EAP is used to create the first PDN connection at initial attach, but other mechanisms are used for creating additional PDN connections as it is described e.g. in solution 1 (section 8.2.1). The solution works in the following way. + +1) How the UE triggers the creation of the new PDN Connections: + +The assumption is that the UE has already been authenticated to the TWAN. When a new PDN Connection needs to be created the UE sends an IEEE 802.1X EAPoL Start message to the authenticator. The authenticator responds, as it must, with EAP-Request/Identity. The UE responds to this as expected for a re-authentication. The UE indicates the APN and other 3GPP specific parameters within the EAP-Response/AKA'-Reauthentication and EAP-Response/AKA'-Challenge messages in a new EAP attribute. + +2) How the EAP-Server indicates the support for the functionality described in this solution: + +The network can indicate the support for the functionality described in this solution within EAP-Request/AKA'-Reauthentication and EAP-Request/AKA'-Challenge messages in a new EAP attribute. + +3) How the network indicates to the UE that the creation of the new PDN Connection failed: + +A new AT\_NOTIFICATION notification code has to be defined. This code is sent by the EAP-server in EAP-Request/AKA'-Notification to the UE. The general rule is that both S and P bits must be set to 0, i.e. indicating an error after a successful authentication, because the APN & PDN specific authorization failed. + +4) How the network indicates to the UE that the creation of the PDN succeeded: + +A network specific information prior to or during the PDN Connection establishment is sent to the UE using a success-indicating EAP-Request/AKA'-Notification (such as VLAN tags, selected APN). + +5) How the UE or the network initiates a deletion of the PDN Connection. + +A UE can also trigger the release of a PDN connection using the (fast) re-authentication mechanism. The UE acts like in case 1) but sends different values within the messages to the network. The network initiated PDN Connection release is done by the network requesting a (fast) re-authentication. The indication that the PDN connection is released is included in the EAP-Response/AKA' Reauthentication or EAP-Response/AKA'-Challenge messages. + +The mechanism proposed does not depend on the selected user plane mechanism selected for SaMOG phase 2 as transporting EAP messages is possible in all anticipated solutions. + +As the capability indication from the network side is possible, the implementation of supporting additional PDN connection establishment in the network can also be optional. As there might be deployments where the additional PDN connection support is not needed, it is proposed to make this feature optional in the specification, however the proposed solution can also be specified in a way that the support of additional PDN creation in the network is mandatory. + +##### 8.2.9.1.2 Protocol stack + +The authentication procedure used in this solution follows the Authentication and key agreement procedures specified in section 6 of TS 33.402 [28]. Beyond the proposed additional parameters no other change is needed. + +Figure 8.2.9.1.2-1 shows the protocol stack that can be used together for authentication, capability negotiation and signaling for PDN connection management. + +![Figure 8.2.9.1.2-1: Protocol stack for authentication related signalling. The diagram shows the protocol stack across five entities: UE, SWw, TWAN (authenticator), STa, and 3GPP AAA Proxy/Server. The stack layers from top to bottom are: 3GPP ext., EAP-AKA', EAPoL (IEEE 802.1X), and L1/L2. Between the TWAN and the 3GPP AAA Proxy/Server, the stack includes DIAMETER, Transport, and L1/L2 layers. The 3GPP AAA Proxy and 3GPP AAA Server share the same stack layers.](3b00a61116faef21d3a6009fd350b46a_img.jpg) + +| | | | | | | | +|----|---------------------|--|---------------------|----------------|-----------------|---------------------| +| UE | 3GPP ext. | | | | | 3GPP ext. | +| | EAP-AKA' | | | | | EAP-AKA' | +| | EAPoL (IEEE 802.1X) | | EAPoL (IEEE 802.1X) | DIAMETER | DIAMETER | EAPoL (IEEE 802.1X) | +| | L1/L2 | | L1/L2 | Transport | Transport | L1/L2 | +| | | | | L1/L2 | | | +| | | | | 3GPP AAA Proxy | | | +| | | | | | 3GPP AAA Server | | + +Figure 8.2.9.1.2-1: Protocol stack for authentication related signalling. The diagram shows the protocol stack across five entities: UE, SWw, TWAN (authenticator), STa, and 3GPP AAA Proxy/Server. The stack layers from top to bottom are: 3GPP ext., EAP-AKA', EAPoL (IEEE 802.1X), and L1/L2. Between the TWAN and the 3GPP AAA Proxy/Server, the stack includes DIAMETER, Transport, and L1/L2 layers. The 3GPP AAA Proxy and 3GPP AAA Server share the same stack layers. + +**Figure 8.2.9.1.2-1: Protocol stack for authentication related signalling** + +3GPP access authentication based on EAP-AKA' as defined in IEEE RFC 5448 [27] (together with still necessary, 3GPP defined extensions) is performed end-to-end between UE and 3GPP AAA Server. Between UE and the TWAN/authenticator the information is transported over EAPoL (see IEEE 802.1X [5]). Between TWAN/authenticator and 3GPP AAA Server the EAP-AKA' payload is transported within Diameter messages. The following information is assumed to be exchanged newly, i.e. in addition to Rel. 11: + +- handover indication (from UE to NW); +- APN (requested one from UE to NW, selected one from NW to UE); +- success/failure of PDN connection request (from NW to UE); +- PDN connection identifier (from NW to UE at PDN connection establishment or teardown, from UE to NW at PDN connection teardown) +- User plane connection identifier (e.g. VLAN tag) + +However the solution is not limited in transferring the above listed parameters, other parameters could also be sent. + +Some examples how EAP procedures can be used for sending session management information between the UE and TWAN are presented. The principle is that the TWAN can read the parameters sent by the UE from EAP messages, but cannot modify them. This is possible as during EAP-AKA' the EAP messages are integrity protected, but not encrypted. When the TWAN needs to send a parameter to the UE, it inserts it in the Diameter message sent to the 3GPP AAA server and then the 3GPP AAA server moves the received parameter from the Diameter message to the consecutive EAP message. + +#### 8.2.9.1.3 Signaling information from UE to the network + +In Figure 8.2.9.1.3-1 an example is presented how the UE can send the requested APN to the TWAN during a fast re-authentication when a new PDN connection is established and how the network can send back the selected APN to the UE. Other session management parameters (e.g. handover indication, VLAN tags) can be sent in a similar manner + +![Sequence diagram showing the interaction between UE, TWAN, and 3GPP AAA server for sending the requested APN to the TWAN. The sequence starts with an Authentication Trigger from UE to TWAN. The TWAN sends an EAP REQ/Identity to the UE. The UE responds with an EAP RSP/Identity. The TWAN then sends a Diameter (EAP RSP/Identity) to the 3GPP AAA server. The 3GPP AAA server responds with a Diameter (EAP REQ/AKA'-ReAuth) to the TWAN. The TWAN sends an EAP REQ/AKA'-ReAuth to the UE. The UE responds with an EAP RSP/AKA'-ReAuth (R-APN). The TWAN then reads the Requested APN from the EAP message and adds the Selected APN into the Diameter message. The TWAN sends a Diameter (EAP RSP/AKA'-ReAuth, S-APN) to the 3GPP AAA server. The 3GPP AAA server moves the S-APN into the EAP message and sends a Diameter (EAP REQ/AKA'-Notif, (S-APN)) to the TWAN. The TWAN sends an EAP REQ/AKA'-Notif (S-APN) to the UE. The UE responds with an EAP RSP/AKA'-Notif. The TWAN sends a Diameter (EAP RSP/AKA'-Notif) to the 3GPP AAA server. The 3GPP AAA server sends a Diameter (EAP Success) to the TWAN. The TWAN sends an EAP Success to the UE.](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant AAA as 3GPP AAA server + + Note left of UE: 0. Authentication Trigger + UE->>TWAN: 1. EAP REQ/Identity + TWAN->>UE: 2a. EAP RSP/Identity + TWAN->>AAA: 2b. Diameter (EAP RSP/Identity) + AAA->>TWAN: 3a. Diameter (EAP REQ/AKA'-ReAuth) + TWAN->>UE: 3b. EAP REQ/AKA'-ReAuth + UE->>TWAN: 4a. EAP RSP/AKA'-ReAuth (R-APN) + Note right of TWAN: 4b. Reading Requested APN from EAP message + Note right of TWAN: 4c. Adding Selected APN into Diameter message + TWAN->>AAA: 4d. Diameter (EAP RSP/AKA'-ReAuth, S-APN) + Note right of AAA: 5a. Moving S-APN into EAP message + AAA->>TWAN: 5b. Diameter (EAP REQ/AKA'-Notif, (S-APN)) + TWAN->>UE: 5v. EAP REQ/AKA'-Notif (S-APN) + UE->>TWAN: 6a. EAP RSP/AKA'-Notif + TWAN->>AAA: 6b. Diameter (EAP RSP/AKA'-Notif) + AAA->>TWAN: 7a. Diameter (EAP Success) + TWAN->>UE: 7b. EAP Success + +``` + +Sequence diagram showing the interaction between UE, TWAN, and 3GPP AAA server for sending the requested APN to the TWAN. The sequence starts with an Authentication Trigger from UE to TWAN. The TWAN sends an EAP REQ/Identity to the UE. The UE responds with an EAP RSP/Identity. The TWAN then sends a Diameter (EAP RSP/Identity) to the 3GPP AAA server. The 3GPP AAA server responds with a Diameter (EAP REQ/AKA'-ReAuth) to the TWAN. The TWAN sends an EAP REQ/AKA'-ReAuth to the UE. The UE responds with an EAP RSP/AKA'-ReAuth (R-APN). The TWAN then reads the Requested APN from the EAP message and adds the Selected APN into the Diameter message. The TWAN sends a Diameter (EAP RSP/AKA'-ReAuth, S-APN) to the 3GPP AAA server. The 3GPP AAA server moves the S-APN into the EAP message and sends a Diameter (EAP REQ/AKA'-Notif, (S-APN)) to the TWAN. The TWAN sends an EAP REQ/AKA'-Notif (S-APN) to the UE. The UE responds with an EAP RSP/AKA'-Notif. The TWAN sends a Diameter (EAP RSP/AKA'-Notif) to the 3GPP AAA server. The 3GPP AAA server sends a Diameter (EAP Success) to the TWAN. The TWAN sends an EAP Success to the UE. + +**Figure 8.2.9.1.3-1: Sending the requested APN to the TWAN** + +- Step 0. The UE triggers a new EAP authentication. + +*.Editor's Note: It is FFS how the UE can trigger a new authentication, especially if IEEE 802.1X EAPoL Start message can trigger a new EAP authentication.* + +- Step 1-3: These steps are performed as in 3GPP TS 33 402 [28]. +- Step 4: The UE adds the requested APN (and other session management parameters) into the EAP message into a new EAP information element. The TWAN reads the requested APN from the EAP message and adds the selected APN (and other session management parameters including the indication of success or failure of the PDN connection establishment) as a Diameter information element to the Diameter message sent to the 3GPP AAA server. Note that the requested APN is not removed from the EAP message as the TWAN cannot modify the EAP message. +- Step 5: The 3GPP AAA server extracts the selected APN from the Diameter message and inserts it into the EAP message in a new information element. Note that the 3GPP AAA server ignores the requested APN received in the EAP message and does not interpret the selected APN received in Diameter, it just copies the Selected APN value from the received Diameter message into the EAP message to be sent. The UE receives the selected APN (and other session management parameters) within the EAP message. +- Step 6-7: these steps are performed as in 3GPP TS 33 402 [28]. + +#### 8.2.9.1.4 Signaling information from the network to the UE + +In Figure 8.2.9.1.4-1 an example is presented how the network can send an indication to the UE that a PDN connection is released during a fast re-authentication. Other parameters (e.g. handover indication) can be sent in a similar manner. + +![Sequence diagram showing the PDN connection release procedure between UE, TWAN, and 3GPP AAA server. The diagram illustrates the exchange of EAP and Diameter messages, with specific steps for adding and moving the Release Indication (Rel-Ind).](8e80de0cac529b2c3775d677c5203133_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant AAA as 3GPP AAA server + + Note right of TWAN: 2b. Adding Release Indication into Diameter + Note right of AAA: 3a. Moving Rel-Ind into EAP message + + UE->>TWAN: 1. EAP REQ/Identity + TWAN-->>UE: 2a. EAP RSP/Identity + TWAN->>AAA: 2b. Diameter (EAP RSP/Identity, Rel-Ind) + AAA-->>TWAN: 3b. Diameter (EAP REQ/AKA'-ReAuth (Rel-Ind)) + Note right of AAA: 3a. Moving Rel-Ind into EAP message + AAA-->>UE: 3c. EAP REQ/AKA'-ReAuth (Rel-Ind) + UE-->>TWAN: 4a. EAP RSP/AKA'-ReAuth + TWAN->>AAA: 4b. Diameter (EAP RSP/AKA'-ReAuth) + AAA-->>TWAN: 5a. Diameter (EAP REQ/AKA'-Notif) + TWAN-->>UE: 5b. EAP REQ/AKA'-Notif + AAA-->>TWAN: 6b. Diameter (EAP RSP/AKA'-Notif) + TWAN-->>UE: 6a. EAP RSP/AKA'-Notif + AAA-->>TWAN: 7a. Diameter (EAP Success) + TWAN-->>UE: 7b. EAP Success + +``` + +Sequence diagram showing the PDN connection release procedure between UE, TWAN, and 3GPP AAA server. The diagram illustrates the exchange of EAP and Diameter messages, with specific steps for adding and moving the Release Indication (Rel-Ind). + +**Figure 8.2.9.1.4-1: Sending the PDN connection release to the UE** + +- Step 1-2a: These steps are performed as in 3GPP TS 33 402 [28]. +- Step 2b-2c: The TWAN adds the indication of the PDN connection release into the Diameter message within a Diameter information element. This indication shall contain an identifier of the release PDN connection to be released. +- Step 3a: The 3GPP AAA server extracts the Release Indication from the Diameter message and inserts it into the EAP message in a new information element. Note that the 3GPP AAA server does not interpret the Release Indication, it just copies it from the received Diameter message into the EAP message. +- Step 3b-3c: The UE receives the Release Indication within the EAP message. +- Step 4-8: These steps are performed as in 3GPP TS 33 402 [28]. After the successful EAP procedure the UE shall consider the PDN connection released. + +In the procedures described below the principles presented in this section are used to carry session management information within EAP signaling, but for the sake of simplicity the details are not presented within the procedures. + +#### 8.2.9.2 Procedures + +**Editor's Notes: The call flows are described in this subclause.** + +#### 8.2.9.2.1 Initial Attach in WLAN on S2a + +The initial attach procedure is the same as (or similar to) the initial attach procedure described in section 8.2.1.2 with the following addition: + +In step 2 of Figure 8.2.1.2.1.1-1 during the EAP authentication within the capability indication the TWAN shall also indicate if it supports the creation of additional PDN connections or a simultaneous NSWO connection. This additional capability indication is only needed if the support of additional PDN connections or simultaneous NSWO connection creation is optional. + +#### 8.2.9.2.2 UE-Initiated Connectivity to Additional PDN in WLAN on S2a + +##### 8.2.9.2.2.1 UE-Initiated Connectivity to Additional PDN in WLAN on GTP S2a + +This procedure is used to create additional PDN connections or when the UE is authenticated to the network (via EAP-AKA') and has a NSWO session. + +![Sequence diagram titled 'Roaming Scenarios' showing UE-initiated connectivity to an additional PDN in WLAN on GTP S2a. The diagram is divided into two parts, (A) and (B). Part (A) shows the initial session establishment, and Part (B) shows a subsequent session establishment. Lifelines include UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS / 3GPP AAA Server. Steps include authentication triggers, EAP authentication, session requests, IP-CAN session establishment, and GTP tunnel creation.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +The diagram illustrates the sequence of messages for UE-initiated connectivity to an additional PDN in WLAN on GTP S2a. It is divided into two main parts, (A) and (B), under the heading 'Roaming Scenarios'. + +**Part (A): Initial Session Establishment** + +- 0. Existing authentication:** A box indicating the precondition. +- 1. Authentication trigger:** UE sends a message to TWAN. +- 2. EAP Authentication:** UE and TWAN exchange messages. +- 3. Create Session Request:** TWAN sends a request to PDN GW. +- 4. IP-CAN Session Establishment Procedure:** A dashed box representing a procedure between PDN GW and HSS / 3GPP AAA Server. +- 5. Update PDN GW Address:** HSS / 3GPP AAA Server sends an update to PDN GW. +- 6. Create Session Response:** PDN GW sends a response to TWAN. +- 7. GTP Tunnel:** A green cylinder representing the established tunnel between TWAN and PDN GW. + +**Part (B): Subsequent Session Establishment** + +- 8. EAP authentication Completion:** TWAN sends a completion message to UE. +- 9. L3 Attach:** A dashed box representing an attachment procedure between UE and TWAN. +- 10. Create Session Request:** TWAN sends a request to PDN GW. +- 11. IP-CAN Session Establishment Procedure:** A dashed box representing a procedure between PDN GW and HSS / 3GPP AAA Server. +- 12. Update PDN GW Address:** HSS / 3GPP AAA Server sends an update to PDN GW. +- 13. Create Session Response:** PDN GW sends a response to TWAN. +- 14. GTP Tunnel:** A green cylinder representing the established tunnel between TWAN and PDN GW. +- 15. L3 Attach Completion:** TWAN sends a completion message to UE. + +Sequence diagram titled 'Roaming Scenarios' showing UE-initiated connectivity to an additional PDN in WLAN on GTP S2a. The diagram is divided into two parts, (A) and (B). Part (A) shows the initial session establishment, and Part (B) shows a subsequent session establishment. Lifelines include UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS / 3GPP AAA Server. Steps include authentication triggers, EAP authentication, session requests, IP-CAN session establishment, and GTP tunnel creation. + +**Figure 8.2.9.2.2.1-1: UE-Initiated Connectivity to Additional PDN in WLAN on GTP S2a** + +The procedure is as in section 8.2.1.2.1.1 (Initial Attach in WLAN on GTP S2a for solution 1) with the following additions: + +- Step 0: The precondition of this procedure is that the UE has valid authentication with the TWAN. The UE might have an existing PDN connection or might use NSWO capability of the TWAN. +- Step 1: The UE triggers a new EAP authentication by sending an IEEE 802.1X EAPoL Start message to the authenticator. +- Step 2: An EAP authentication using Fast Reauthentication is performed if possible, otherwise a full authentication is performed. The UE indicates the APN and other 3GPP specific parameters within the EAP-Response/AKA'-Reauthentication and EAP-Response/AKA'-Challenge messages in a new EAP attribute in a similar way as it is indicated during initial attach. +- Step 8: After the successful PDN connection establishment the EAP procedure is completed. Within this step the TWAN sends back information about the established PDN connection (e.g. success indication, necessary user plane parameters, such as VLAN tag). +- During the procedure a new virtual point-to-point between the UE and the TWAG is created for the new PDN connection (on NSWO session). When and how this is performed depends on the mechanism used for point-to-point link creation. + +##### 8.2.9.2.2.2 UE-Initiated Connectivity to Additional PDN in WLAN on PMIP S2a + +The required additions to the procedure are the same as the ones described for GTP S2a (see previous section) as the proposed additions to the EAP procedures do not depend on the protocol used over S2a. + +##### 8.2.9.2.3 Handover procedure between 3GPP access and WLAN on S2a + +##### 8.2.9.2.3.1 Handover from 3GPP access to WLAN on GTP S2a + +This procedure is used to hand over a PDN connection from 3GPP access to WLAN on GTP S2a. If multiple PDN connections are handed over then this procedure is invoked for each PDN connections separately. + +![Sequence diagram for Handover from 3GPP access to WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/3GPP AAA Server. The process starts with an existing PDN connection over 3GPP. Step 1 involves authentication with the TWAN. Step 2 involves EAP Authentication between the UE and the AAA Proxy. Step 3 involves steps 3-15 from Figure 8.2.x.2.2.1-1. Step 4 involves resource release in the 3GPP RAN and CN. A 'Roaming Scenarios' box groups the vPCRF, AAA Proxy, and hPCRF.](a3083eec2a883ee8327b3c24174df6a9_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_3GPP_AAA_Server as HSS / 3GPP AAA Server + + Note over UE, PDN_GW: 0. Existing PDN connection over 3GPP + Note over UE, PDN_GW: 1. Step 2 of Figure 8.2.1.2.1.1-1 or Step 2 of Figure 8.2.9.2.2.1-1 + Note over UE, AAA_Proxy: 2. EAP Authentication + Note over AAA_Proxy, HSS_3GPP_AAA_Server: 2. Authentication & Authorization + Note over UE, PDN_GW: 3. Steps 3-15 in Figure 8.2.x.2.2.1-1 + Note over UE, PDN_GW: 4. Resource release in 3GPP RAN and CN + +``` + +Sequence diagram for Handover from 3GPP access to WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/3GPP AAA Server. The process starts with an existing PDN connection over 3GPP. Step 1 involves authentication with the TWAN. Step 2 involves EAP Authentication between the UE and the AAA Proxy. Step 3 involves steps 3-15 from Figure 8.2.x.2.2.1-1. Step 4 involves resource release in the 3GPP RAN and CN. A 'Roaming Scenarios' box groups the vPCRF, AAA Proxy, and hPCRF. + +**Figure 8.2.9.2.3.1-1: Handover from 3GPP access to WLAN on GTP S2a** + +During the steps of Figure 8.2.9.2.3.1-1 the following should be taken into account: + +- Step 0: The UE is connected in the 3GPP Access and has a PMIPv6 or GTP tunnel on the S5/S8 interface. +- Step 1: If the UE has no valid authentication with the TWAN, i.e. the UE has neither a PDN connection nor a NSWO connection then this step is the same as step 2 of 8.2.1.2.1.1-1. If the UE has a valid authentication with the TWAN either due to the UE having an existing PDN connection or using NSWO capability of the TWAN, then this step is the same as step 2 of 8.2.9.2.2.1-1. +- Step 2: As step 2 in 8.2.9.2.2.1-1 with the following addition: the UE indicates handover via EAP to the 3GPP AAA Server. +- Step 3: The same as step 3-15 in 8.2.9.2.2.1-1 with the addition that handover is performed: the handover indication is set in the Create Session Request to allow the PDN GW to re-allocate the same IP address or prefix that was assigned to the UE while it was connected to the 3GPP IP access and to initiate a PCEF-Initiated IP CAN Session Modification Procedure with the PCRF. +- Step 4: The PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure in 3GPP access as defined in TS 23.402 subclause 5.6.2.2 or the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401, subclause 5.4.4.1. + +##### 8.2.9.2.3.2 Handover from 3GPP access to WLAN on PMIP S2a + +The required additions to the procedure are the same as the ones described for GTP S2a (see previous section) as the proposed additions to the EAP procedures do not depend on the protocol used over S2a. + +##### 8.2.9.2.3.3 Handover from TWAN to 3GPP access + +This procedure can be performed as specified in 3GPP TS 23.402 [3]. Solution specific changes are needed when after the handover the PGW initiates the removal of the resources in the TWAN. These changes can be found in section 8.2.9.2.4. + +##### 8.2.9.2.4 PDN GW initiated Resource Allocation Deactivation + +##### 8.2.9.2.4.1 PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a + +This procedure applies when the PDN GW would like to release a PDN connection. + +![Sequence diagram for PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS / 3GPP AAA Server. A 'Roaming Scenarios' box groups the PCRF, AAA Proxy, and hPCRF. The sequence of messages is: 1. IP-CAN sessions Modification (PDN GW to vPCRF), 2. Delete Session Response (PDN GW to TWAN), 3. EAP Authentication (TWAN to UE) and 3. Authentication & Authorization (TWAN to HSS), 4. Delete Session Request (TWAN to PDN GW), 5. Update PDN GW Address (PDN GW to HSS), and 6. TWAN specific Resource Release Procedure (TWAN to UE).](0f26e70157bd4c45f825795cdcd20fbd_img.jpg) + +Sequence diagram for PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS / 3GPP AAA Server. A 'Roaming Scenarios' box groups the PCRF, AAA Proxy, and hPCRF. The sequence of messages is: 1. IP-CAN sessions Modification (PDN GW to vPCRF), 2. Delete Session Response (PDN GW to TWAN), 3. EAP Authentication (TWAN to UE) and 3. Authentication & Authorization (TWAN to HSS), 4. Delete Session Request (TWAN to PDN GW), 5. Update PDN GW Address (PDN GW to HSS), and 6. TWAN specific Resource Release Procedure (TWAN to UE). + +**Figure 8.2.9.2.4.1-1: PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a** + +During the steps of Figure 8.2.9.2.4.1-1 the following should be taken into account: + +- Step 3: An EAP authentication is triggered by the TWAN. Preferably a Fast Reauthentication is performed, but if it is not possible due to any reason then a full authentication is performed. The TWAN indicates that it requests a release of an existing PDN connection within the EAP-Request/AKA'-Reauthentication and EAP-Request/AKA'-Challenge messages in a new EAP attribute. + +NOTE: Step 3 and steps 4 and 5 can be performed simultaneously. + +##### 8.2.9.2.4.2 PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a + +The required additions to the procedure are the same as the ones described for GTP S2a (see previous section) as the proposed additions to the EAP procedures do not depend on the protocol used over S2a. + +##### 8.2.9.2.5 TWAN requested PDN Disconnection Procedures + +##### 8.2.9.2.5.1 TWAN requested PDN Disconnection Procedure in WLAN on GTP S2a + +This procedure applies when multiple PDN connections have been established or when the UE has at least one PDN connection and simultaneously uses NSWO. + +![Sequence diagram for TWAN initiated Resource Allocation Deactivation in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS / 3GPP AAA Server. A 'Roaming Scenarios' box covers the vPCRF, AAA Proxy, and hPCRF. The sequence of messages is: 1. PDN connection release trigger (TWAN to PDN GW); 2. EAP Authentication (TWAN to UE) and 2. Authentication & Authorization (TWAN to HSS/AAA Server); 3. Delete Session Request (TWAN to PDN GW); 4. IP-CAN Session Establishment Procedure (dashed box between PDN GW and vPCRF); 5. Update PDN GW Address (PDN GW to HSS/AAA Server); 6. Delete Session Response (PDN GW to TWAN); 7. TWAN specific Resource Release Procedure (TWAN to UE).](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +Sequence diagram for TWAN initiated Resource Allocation Deactivation in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS / 3GPP AAA Server. A 'Roaming Scenarios' box covers the vPCRF, AAA Proxy, and hPCRF. The sequence of messages is: 1. PDN connection release trigger (TWAN to PDN GW); 2. EAP Authentication (TWAN to UE) and 2. Authentication & Authorization (TWAN to HSS/AAA Server); 3. Delete Session Request (TWAN to PDN GW); 4. IP-CAN Session Establishment Procedure (dashed box between PDN GW and vPCRF); 5. Update PDN GW Address (PDN GW to HSS/AAA Server); 6. Delete Session Response (PDN GW to TWAN); 7. TWAN specific Resource Release Procedure (TWAN to UE). + +**Figure 8.2.9.2.5.1-1: TWAN initiated Resource Allocation Deactivation in WLAN on GTP S2a** + +During the steps of Figure 8.2.9.2.3.1-1 the following should be taken into account: + +- Step 2. An EAP authentication is triggered by the TWAN. Preferably a Fast Reauthentication is performed, but if it is not possible due to any reason then a full authentication is performed. The TWAN indicates that it requests a release of an existing PDN connection within the EAP-Request/AKA'-Reauthentication and EAP-Request/AKA'-Challenge messages in a new EAP attribute. + +NOTE: An NSWO session that is simultaneously used with PDN connection(s) can also be terminated in this way. If the NSWO offload session is terminated then steps 3-6 are not performed. + +##### 8.2.9.2.5.2 TWAN Initiated Detach and requested PDN Disconnection Procedure in WLAN on PMIP S2a + +The required additions to the procedure are the same as the ones described for GTP S2a (see previous section) as the proposed additions to the EAP procedures do not depend on the protocol used over S2a. + +##### 8.2.9.2.6 UE requested PDN Disconnection Procedures + +##### 8.2.9.2.6.1 UE requested PDN Disconnection Procedure in WLAN on GTP S2a + +This procedure applies when multiple PDN connections have been established or when the UE has at least one PDN connection and simultaneously uses NSWO. + +![Sequence diagram of UE requested PDN Disconnection Procedure in WLAN on GTP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS / 3GPP AAA Server. The diagram shows 7 steps: 1. Authentication trigger (UE to TWAN), 2. EAP Authentication (UE <-> TWAN), 2. Authentication & Authorization (TWAN <-> HSS), 3. Delete Session Request (TWAN to PDN GW), 4. IP-CAN Session Establishment Procedure (PDN GW <-> AAA Proxy), 5. Update PDN GW Address (AAA Proxy to HSS), 6. Delete Session Response (PDN GW to TWAN), 7. TWAN specific Resource Release Procedure (TWAN internal). A 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +Sequence diagram of UE requested PDN Disconnection Procedure in WLAN on GTP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS / 3GPP AAA Server. The diagram shows 7 steps: 1. Authentication trigger (UE to TWAN), 2. EAP Authentication (UE <-> TWAN), 2. Authentication & Authorization (TWAN <-> HSS), 3. Delete Session Request (TWAN to PDN GW), 4. IP-CAN Session Establishment Procedure (PDN GW <-> AAA Proxy), 5. Update PDN GW Address (AAA Proxy to HSS), 6. Delete Session Response (PDN GW to TWAN), 7. TWAN specific Resource Release Procedure (TWAN internal). A 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF. + +**Figure 8.2.9.2.6.1-1: UE requested PDN Disconnection Procedure in WLAN on GTP S2a** + +During the steps of Figure 8.2.9.2.3.1-1 the following should be taken into account: + +- Step 1. The UE triggers a new EAP authentication. + +**.Editor's Note:** It is FFS how the UE can trigger a new authentication, especially if IEEE 802.1X EAPoL Start message can trigger a new EAP authentication. + +- Step 2. An EAP authentication is performed. Preferably a Fast Reauthentication is performed, but if it is not possible due to any reason then a full authentication is performed. The UE indicates that it requests a release of an existing PDN connection within the EAP-Response/AKA' Reauthentication and EAP-Response/AKA'-Challenge messages in a new EAP attribute. + +**NOTE:** An NSWO session that is simultaneously used with PDN connection(s) can also be terminated in this way. If the NSWO offload session is terminated then steps 3-6 are not performed. + +- Step 3-6: Step 3 is triggered by the PDN connection release request indication received in step 2. + +##### 8.2.9.2.6.2 UE requested PDN Disconnection Procedure in WLAN on GTP S2a on PMIP S2a + +The required additions to the procedure are the same as the ones described for GTP S2a (see previous section) as the proposed additions to the EAP procedures do not depend on the protocol used over S2a. + +##### 8.2.9.2.7 Detach Procedures + +There is nothing special in the detach procedures, they are in principle the same as specified in TS 23.402 [3] for Trusted Non-3GPP Access Networks. If the detach procedure requires to perform PDN connection release procedures then the procedures described above are applicable. + +#### 8.2.9.3 Impacts on existing nodes or functionality + +**Editor's Notes:** Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause. + +The UE shall support an enhanced EAP-AKA' scheme with new attributes in EAP messages. + +The 3GPP AAA server shall support: + +- an enhanced EAP-AKA' scheme with new attributes in EAP messages; +- additional Diameter AVP for parameters sent from TWAN to the UE. + +NOTE: The 3GPP AAA server does not process the new parameters, their values are simply ignored or copied between messages. + +#### 8.2.9.4 Evaluation + +**Editor's Notes:** The fulfilment to the requirements in Subclause 8.1 as well as simplicity of implementation in the UE should be evaluated. + +### 8.2.10 Solution 10 : WCS Solution + +#### 8.2.10.1 Functional Description + +**Editor's Notes:** It should be described whether and how the solution fulfils the requirements in Subclause 8.1. + +##### 8.2.10.1.1 Overview + +This solution proposes a control plane protocol between the UE and the TWAG for mobility management PDN connections. + +This solution supports simultaneous NSWO and PDN connections. + +For the user plane, a virtual MAC address or VLAN is used to differentiate multiple connections (including PDN connections and NSWO connection). + +UE and network capability is negotiated during EAP-AKA' procedure to decide whether the Rel-11 or the Rel-12 SaMOG procedure is performed. + +##### 8.2.10.1.2 User plane + +The point-to-point link required to transport traffic for a given PDN connection, or for Non-Seamless WLAN Offload (NSWO) is realized via the TWAN reserving a distinct VLAN ID or virtual MAC address that uniquely (on a per-UE basis) corresponds to an PDN connection or NSWO. + +The link model for VLAN based user plane is described in 8.2.2.1.1.1, and the link model for virtual MAC based user plane is described in 8.2.2.1.1.2. + +**Editor's Notes:** Whether VLAN or Virtual MAC address is chosen is FFS. + +##### 8.2.10.1.3 Control plane + +A UE-TWAG protocol is used to control (i.e. setup and teardown) the per-PDN point-to-point link. This protocol is denoted as WCS (WLAN Control Signaling) and should be defined by 3GPP. The functions that WCS supports include: Establishment of a per-UE-and-PDN point-to-point link; Tear down of a per-UE-and-PDN point-to-point link; IP address allocation for PDN connections connection. An NSWO connection is established using DHCP or IPv6 stateless autoconfiguration after authentication in the per UE p2p link. + +Reliability of the WCS protocol uses RFC 3315 reliability mechanisms and depends on the reception of a reply message in response to a request message. If no response is received, re-transmission of the request message can use the DHCP re-transmission timer value. No support for fragmentation is provided and is not necessary for the control protocol. + +Three alternatives for the transport of WCS are outlined below. + +**Editor's Notes:** One of these alternatives for protocol transport needs to be chosen. The selection would depend on the choice of user plane. + +##### 8.2.10.1.3.1 Alternative 1: Virtual MAC-based control protocol transport + +The frame format of the control plane is as shown in Figure 8.2.10.1.3-1. + +A new Ethertype is used to identify the WCS protocol. If the virtual MAC address is used by TWAG to differentiate the user plane PDN connections, a dedicated virtual MAC address may also be used to differentiate the control plane. + +The new Ethertype for WCS needs to be defined in IEEE. + +| | | | +|---------|---------------|--------------| +| MAC/LLC | WCS Ethertype | Payload(WCS) | +|---------|---------------|--------------| + +**Figure 8.2.10.1.3-1 Frame format for PDN for Virtual MAC-based control protocol** + +A dedicated p2p Link ID (i.e. (Virtual MAC address) allocated by TWAG is used for WCS signalling. The Virtual MAC address is unique per UE. + +This MAC address is sent to the UE during EAP-AKA' authentication as described in clause 8.2.10.1.3.4. In this case, the p2p link ID in clause 8.2.10.1.3.4 is a Virtual MAC address of the TWAG. + +##### 8.2.10.1.3.2 Alternative 2: VLAN-based control protocol transport + +The frame format of the control plane is as shown in Figure 8.2.10.1.3.2-1. + +| | | | | +|---------|------|---------------|---------------| +| MAC/LLC | VLAN | New Ethertype | Payload (WCS) | +|---------|------|---------------|---------------| + +**Figure 8.2.10.1.3.2-1 Frame format for PDN for L2.5-based control protocol** + +The VLAN ID is used to differentiate the tunnel between the control plane and the user plane protocol. In the corresponding user plane, the VLAN ID used to distinguish PDN connections. + +As in the case of Alternative 1 (clause 8.2.10.1.3.1), a new Ethertype is needed to indicate that payload is WCS. + +The dedicated p2p link ID (i.e. VLAN ID) used for control plane signalling on top of per UE p2p link is negotiated during the EAP-AKA' procedure. Details of provisioning the p2p link ID (i.e. VLAN ID) are described in clause 8.2.10.1.3.4. The TWAG MAC address is also sent to the UE during EAP-AKA' authentication sequence, along with the VLAN ID. + +##### 8.2.10.1.3.3 Alternative 3: L3-based control protocol transport + +In this alternative, the frame format of the control plane message is as shown in Figure 8.2.10.1.3.3-1. + +| | | | +|---------|--------|---------------| +| MAC/LLC | UDP/IP | Payload (WCS) | +|---------|--------|---------------| + +**Figure 8.2.10.1.3.3-1 Frame format for L3-based control protocol** + +The payload contains the WCS control protocol message. The UE gets a link-local address or NSWO address before using L3 based control protocol. The IP address of the TWAG is sent to the UE during the EAP-AKA' procedure in the same as how the TWAG MAC address is delivered in alternative2. + +###### 8.2.10.1.3.4 p2p link ID negotiation in EAP-AKA' procedure. + +This procedure describes the p2p link ID is negotiation during EAP-AKA'. The p2p link ID is used to establish tunnel to transport the control plane protocol (WCS). + +![Sequence diagram for p2p link ID negotiation between UE, Non-3GPP Access, Proxy AAA (optional), 3GPP AAA Server, and HSS. The diagram shows the flow of EAP and AAA messages, including optional AKA' authentication and conditional notification steps.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Non-3GPP Access + participant Proxy AAA (optional) + participant 3GPP AAA Server + participant HSS + + Note over UE, Non-3GPP Access: 1. Connection Established + Non-3GPP Access->>UE: 2. EAP-REQ / Identity + UE->>Non-3GPP Access: 3. EAP-RSP / Identity + Non-3GPP Access->>Proxy AAA (optional): 4. AAA (EAP-RSP/Identity, P2P link ID) + Proxy AAA (optional)->>3GPP AAA Server: 5. AAA (EAP-RSP/Identity, P2P link ID) + + rect rgb(240, 240, 240) + Note over UE, 3GPP AAA Server: Optional Messages + 3GPP AAA Server->>Proxy AAA (optional): 6a. AAA (EAP-REQ / AKA'-Identity) + Proxy AAA (optional)->>Non-3GPP Access: 6b. AAA (EAP-REQ / AKA'-Identity) + Non-3GPP Access->>UE: 7. EAP-REQ / AKA'-Identity + UE->>Non-3GPP Access: 8. EAP-RSP / AKA'-Identity + Non-3GPP Access->>Proxy AAA (optional): 9a. AAA (EAP-RSP / AKA'-Identity) + Proxy AAA (optional)->>3GPP AAA Server: 9b. AAA (EAP-RSP / AKA'-Identity) + end + + 3GPP AAA Server->>HSS: 10a. Request AKA vector + Note right of HSS: 10b. AKA Algorithm executed, outputs AK Vector: AKA-RAND, AUTN, XRES + HSS->>3GPP AAA Server: 10c. Return AKA vector + 3GPP AAA Server->>HSS: 11a. Request Profile + HSS->>3GPP AAA Server: 11b. Return Profile + Note right of 3GPP AAA Server: 12. Derive Keying Material + 3GPP AAA Server->>Proxy AAA (optional): 13a. AAA (EAP-REQ / AKA'-Challenge, P2P link ID) + Proxy AAA (optional)->>Non-3GPP Access: 13b. AAA (EAP-REQ / AKA'-Challenge, P2P link ID) + Non-3GPP Access->>UE: 14. EAP-REQ / AKA'-Challenge, P2P link ID + Note left of UE: 15. UE runs AKA algorithms, verifies AUTN, generates RES, and MSK + UE->>Non-3GPP Access: 16. EAP-RSP / AKA'-Challenge + Non-3GPP Access->>Proxy AAA (optional): 17a. AAA (EAP-RSP / AKA'-Challenge) + Proxy AAA (optional)->>3GPP AAA Server: 17b. AAA (EAP-RSP / AKA'-Challenge) + Note right of 3GPP AAA Server: 18. 3GPP AAA Verifies that AT-RES = XRES + + rect rgb(240, 240, 240) + Note over UE, 3GPP AAA Server: Conditional Messages + 3GPP AAA Server->>Proxy AAA (optional): 19a. AAA (EAP-REQ / AKA'-Notification) + Proxy AAA (optional)->>Non-3GPP Access: 19b. AAA (EAP-REQ / AKA'-Notification) + Non-3GPP Access->>UE: 20. EAP-REQ / AKA'-Notification + UE->>Non-3GPP Access: 21. EAP-RSP / AKA'-Notification + Non-3GPP Access->>Proxy AAA (optional): 22a. AAA (EAP-RSP / AKA'-Notification) + Proxy AAA (optional)->>3GPP AAA Server: 22b. AAA (EAP-RSP / AKA'-Notification) + end + + 3GPP AAA Server->>Proxy AAA (optional): 23a. AAA (EAP-Success) + Proxy AAA (optional)->>Non-3GPP Access: 23b. AAA (EAP-Success) + Non-3GPP Access->>UE: 24. EAP-Success + Note over 3GPP AAA Server, HSS: 25. Registration + +``` + +Sequence diagram for p2p link ID negotiation between UE, Non-3GPP Access, Proxy AAA (optional), 3GPP AAA Server, and HSS. The diagram shows the flow of EAP and AAA messages, including optional AKA' authentication and conditional notification steps. + +**Figure 8.2.10.1.3.4-1 p2p link ID negotiation** + +Step4-Step5 TWAG sends the p2p link ID via TWAN to the 3GPP AAA. + +Step 13a,b-14, the p2p link ID is sent in EAP-REQ message to the UE. + +The p2p link ID could be the virtual MAC address or VLAN ID provisioned in the TWAN. + +##### 8.2.10.1.4 Protocol Stacks + +*Editor's Notes: Impact on link model due to handover support is FFS.* + +#### 8.2.10.2 Procedures + +*Editor's Notes: The call flows are described in this subclause.* + +##### 8.2.10.2.1 Initial Attach procedure + +##### 8.2.10.2.1.1 Initial Attach in WLAN on S2a – network capability negotiation + +![Sequence diagram for Initial Attach in WLAN on S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' contains vPCRF, AAA Proxy, and hPCRF. Step 1, 'Non-3GPP Specific Procedures', occurs between UE and TWAN. Step 2, 'EAP Authentication', is a bidirectional exchange between UE and HSS/AAA, passing through TWAN, PDN GW, and AAA Proxy. A circle on the AAA Proxy lifeline indicates a processing point.](62ee64afa2d368d732de66628cf2c841_img.jpg) + +``` +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note left of UE: 1. Non-3GPP Specific Procedures + UE->>TWAN: + TWAN->>UE: + Note left of UE: 2. EAP Authentication + UE->>HSS_AAA: + HSS_AAA->>UE: + Note right of AAA_Proxy: (Processing point) +``` + +Sequence diagram for Initial Attach in WLAN on S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' contains vPCRF, AAA Proxy, and hPCRF. Step 1, 'Non-3GPP Specific Procedures', occurs between UE and TWAN. Step 2, 'EAP Authentication', is a bidirectional exchange between UE and HSS/AAA, passing through TWAN, PDN GW, and AAA Proxy. A circle on the AAA Proxy lifeline indicates a processing point. + +**Figure 8.2.10.2.1-1: Initial attachment in WLAN on S2a for roaming and non-roaming scenarios** + +The procedure is as in TS 23.402 clause 16.2 with the following additions: + +- Step 2. As part of this step, the UE shall send an indication to the network as to whether it supports Rel-12 SaMOG. Depending on the capabilities of the network and the indication of the UE, the network informs the UE as part of step 2 whether the Rel-12 SaMOG procedures should be performed. + +##### 8.2.10.2.1.2 Initial Attach continuation for GTP based S2a + +![Sequence diagram for Initial Attach continuation for GTP based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' covers the vPCRF, AAA Proxy, and hPCRF. Step 1-2 is referenced as being in clause 8.2.10.2.1. The sequence includes: 3.1 UE obtains link local IP address; 3.2 attach request (WCS) from UE to TWAN; 4. Create Session Request from TWAN to PDN GW; 5. IP-CAN Session Establishment Procedure (dashed box); 6. Update PDN GW Address from PDN GW to HSS/AAA; 7. Create Session Response from PDN GW to TWAN; 8. GTP Tunnel (highlighted in green); 9. attach accept (WCS) from TWAN to UE.](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +Sequence diagram for Initial Attach continuation for GTP based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' covers the vPCRF, AAA Proxy, and hPCRF. Step 1-2 is referenced as being in clause 8.2.10.2.1. The sequence includes: 3.1 UE obtains link local IP address; 3.2 attach request (WCS) from UE to TWAN; 4. Create Session Request from TWAN to PDN GW; 5. IP-CAN Session Establishment Procedure (dashed box); 6. Update PDN GW Address from PDN GW to HSS/AAA; 7. Create Session Response from PDN GW to TWAN; 8. GTP Tunnel (highlighted in green); 9. attach accept (WCS) from TWAN to UE. + +Figure 8.2.10.2.1-2: Initial attachment in WLAN on S2a for roaming and non-roaming scenarios + +The procedure continues from step 2 in clause 8.2.10.2.1: + +- Step 2, as part of the authentication procedure, the p2p link ID for WCS signalling is negotiated between the UE and the TWAG. There are following alternatives to establish the p2p link for WCS: + +- If Alternative 1 (clause 8.2.10.1.3.1) based mechanism is used for WCS, then a (virtual) MAC address of TWAG is sent to the UE. +- If Alternative 2 (clause 8.2.10.1.3.2) based mechanism is used for WCS, then the VLAN ID is negotiated between the UE and the TWAG. Also the MAC address of the TWAG should be sent to the UE. +- If Alternative 3 (clause 8.2.10.1.3.3) based mechanism is used for WCS, the TWAG IP address is sent to the UE. + +- Step 3.1, The UE will get a link local address or NSWO Address from TWAN using RFC 4861 for IPv6, or RFC 3927 for IPv4. The UE can use this IP address for the transport of the control plane protocol to TWAG. If the UE wants to setup an NSWO connection, the UE sends a DHCP Request (and optionally an IPv6 Router Solicitation Request) in this step. + +- Step 3.2: If the UE wants to set up a PDN connection, the UE sends a WCS Attach Request to the TWAN. This message includes AttachType, APN, , PDN type, PCO. The Attach Type field indicates initial attach and the APN field indicates the APN that the UE requests. The PDN type field indicates the IP address type the UE request. The PCO field + +may indicate that the UE wants deferred IP address allocation and if so, the UE will send DHCP/RS after the attach procedures. + +There are two options for user plane p2p link ID. 1) virtual MAC address 2) VLAN ID allocated by the UE + +-Step 4-8 refers to step-3 –step7 in clause 16.2.1 of TS 23.402. Additionally, if the PDN GW receives the PCO which indicates deferred IPv4 address allocation, then the PDN GW will not allocate IP address to the UE at this step. + +Step 9 the TWAN sends a WCS attach accept message to the UE. If the UE does not indicate an APN in the attach request, the TWAN should send the selected APN to the UE. The IP address(es) is also sent to the UE if the PDN GW has allocated the IP address to the UE (i.e., not deferred address for IPv4). . This response contains a User Plane p2p link ID to be used in further signalling associated with this PDN connection. + +If the user plane p2p link is VLAN based, the VLAN ID allocated by the TWAN is included in the p2p link field of the attach accept message. Alternatively, if the user plane p2p link is virtual MAC based, the virtual MAC allocated by the TWAN is included in the p2p link field. + +If the UE requests a deferred IPv4 address allocation, the UE may request for an IP address using DHCP after the attach procedure. DHCP signalling is performed over the established p2p link. In IPv6, prefix assignment takes place using RFC 4861 over the established p2p link. + +##### 8.2.10.2.1.2 Initial Attach in WLAN on PMIP S2a + +Editor's Notes: The procedure is FFS. + +##### 8.2.10.2.2 UE-initiated Connectivity to Additional PDN + +This procedure is used when the UE requests additional PDN connections. + +This procedure is also used when the UE requests more PDN connections in the same APN. + +The p2p link is established between UE and TWAG per each PDN connection. + +##### 8.2.10.2.2.1 UE-Initiated Connectivity to PDN in WLAN on GTP S2a + +![Sequence diagram for UE-initiated connectivity to PDN in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains vPCRF, AAA Proxy, and hPCRF. The sequence includes: 1. PDN Connectivity Request (UE to TWAN), 2. S2a Create Session Request (TWAN to PDN GW), 3. IP-CAN Session Establishment Procedure (PDN GW to AAA Proxy), 4. Update PDN GW Address (AAA Proxy to HSS/AAA), 5. S2a Create Session Response (PDN GW to TWAN), 6. GTP Tunnel (established between TWAN and PDN GW), 7. PDN connectivity accepted (TWAN to UE).](9b25cfd1657391070da4ca3e922b82b1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW: Roaming Scenarios + + UE->>TWAN: 1. PDN Connectivity Request + TWAN->>PDN_GW: 2. S2a Create Session Request + PDN_GW->>AAA_Proxy: 3. IP-CAN Session Establishment Procedure + AAA_Proxy->>HSS_AAA: 4. Update PDN GW Address + PDN_GW->>TWAN: 5. S2a Create Session Response + Note over TWAN,PDN_GW: 6. GTP Tunnel + TWAN->>UE: 7. PDN connectivity accepted + +``` + +Sequence diagram for UE-initiated connectivity to PDN in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains vPCRF, AAA Proxy, and hPCRF. The sequence includes: 1. PDN Connectivity Request (UE to TWAN), 2. S2a Create Session Request (TWAN to PDN GW), 3. IP-CAN Session Establishment Procedure (PDN GW to AAA Proxy), 4. Update PDN GW Address (AAA Proxy to HSS/AAA), 5. S2a Create Session Response (PDN GW to TWAN), 6. GTP Tunnel (established between TWAN and PDN GW), 7. PDN connectivity accepted (TWAN to UE). + +Figure 8.2.10.2.2.1-1: UE initiated connectivity to PDN/NSWO + +- Step 1. The UE triggers the establishment of a new per-UE and per-PDN point-to-point link. The UE sends WCS PDN Connectivity Request (APN, PDN Type, Protocol Configuration Options, Request Type). The Request Type indicates "initial request" if the UE requests new additional PDN connectivity over the 3GPP access network for multiple PDN connections, the Request Type indicates "handover" when the UE is performing a handover from 3GPP access and the UE has already established connectivity with the PDN over the 3GPP access. +- Step 2-6. Same as step 3-7 in clause 8.2.10.2.2.1. As part of these steps, the TWAN verifies that the APN requested by the UE is allowed by subscription. Upon handover, the TWAN selects the PDN GW handling this PDN connection; otherwise, the TWAN performs PDN GW selection as described in TS 23.402. Steps 2-6 are executed with the selected PDN GW. +- Step 7. The TWAN replies with WCS PDN connectivity accept to the UE. This response contains a p2p link id to be used in further signalling associated with this PDN connection. +- If the UE requests deferred IPv4 address allocation, it may negotiate the IPv4 address with DHCPv4 after step7. + +###### 8.2.10.2.2.2 UE-Initiated Connectivity to PDN in WLAN on PMIP S2a + +Editor's Notes: The procedure is FFS. + +##### 8.2.10.2.3 Handover procedure in multi-connection scenario from 3GPP access to WLAN on S2a + +##### 8.2.10.2.3.1 Handover in multi-connection scenario from 3GPP access to WLAN on GTP S2a + +![Sequence diagram for handover from 3GPP access to WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process includes Non-3GPP Specific Procedures, EAP Authentication, Handover attach, a block for steps 4-8 (referenced to Figure 8.2.10.2.1.2), attach accept, and 3GPP EPS bearer release.](367378559e35017a5e1a6f5c30798c5a_img.jpg) + +The diagram illustrates the sequence of messages for a handover from 3GPP access to WLAN on GTP S2a. The participants are UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A green cylinder labeled "0. GTP/PMIPv6 tunnel" connects the S-GW and PDN GW. A shaded area labeled "Roaming Scenarios" contains the vPCRF, AAA Proxy, and hPCRF. The sequence of steps is as follows: + +1. Non-3GPP Specific Procedures (UE to TWAN) +2. EAP Authentication (UE to TWAN) and 2. Authentication & Authorization (TWAN to HSS/AAA via AAA Proxy) +3. Handover attach (UE to TWAN) +- 4-8. Step4-step8 in Figure 8.2.10.2.1.2 (TWAN to PDN GW via S-GW, involving vPCRF, AAA Proxy, and hPCRF) +9. attach accept (PDN GW to S-GW to TWAN to UE) +10. 3GPP EPS bearer release (PDN GW to S-GW and TWAN to S-GW) + +Sequence diagram for handover from 3GPP access to WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process includes Non-3GPP Specific Procedures, EAP Authentication, Handover attach, a block for steps 4-8 (referenced to Figure 8.2.10.2.1.2), attach accept, and 3GPP EPS bearer release. + +Figure 8.2.10.3.1-1: Handover from 3GPP access to WLAN + +Step1- Step2, same as in clause 8.2.10.2.1-1 + +Step3- Refer to Step3.2 of attach procedure in clause 8.2.10.2.1.2. Attach type indicates handover attach. + +If L3 based WCS is used, then the UE should get a link local IP address or NSWO address before step3 as described in step3.1 of attach procedure in clause 8.2.10.2.1.2. + +Step4-step8: Since these steps represent handover attach, IP address preservation is handled by the PDN GW. + +Step9: same as Step9 of attach procedure in clause 8.2.10.2.1.2. + +8.2.10.2.3.2 Handover in multi-connection scenario from 3GPP access to WLAN on PMIP S2a + +**Editor's Notes: The procedure is FFS.** + +8.2.10.2.4 Handover procedure in multi-connection scenario from WLAN on S2a to 3GPP access + +**Editor's Notes: The procedure is FFS.** + +##### 8.2.10.2.5 Handover procedure from WLAN on S2a to 3GPP access + +![](03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg) + +Sequence diagram illustrating the handover procedure from Trusted WLAN on S2a to 3GPP access for roaming, LBO and non-roaming scenarios. + +Participants: UE, Trusted Non-3GPP IP Access/ePDG, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, HSS/AAA. + +The diagram is divided into two main sections: (C) and (B). + +**Sequence of Messages:** + +1. PMIPv6 or GTP Tunnel (Established between Trusted Non-3GPP IP Access/ePDG and PDN GW) +2. UE discovers 3GPP access system and initiates HO +3. Attach (UE to E-UTRAN) +4. Access Authentication (E-UTRAN to MME, then MME to AAA Proxy, then AAA Proxy to HSS/AAA) +5. Location Update and Subscriber Data Retrieval (MME to PDN GW) +6. Create Session Request (MN-NAI, PDN GW) (PDN GW to MME) +7. Create Session Request (MME to PDN GW) +8. PCEF-Initiated IP-CAN Session Modification Procedure (PDN GW to vPCRF) +9. Create Session Response (PDN GW to MME) +10. Create Session Response (IP Addr) (MME to PDN GW) +11. Radio and Access Bearer Establishment (MME to E-UTRAN) +12. Modify Bearer Request (MME to PDN GW) +13. Modify Bearer Request (PDN GW to vPCRF) +14. Modify Bearer Response (vPCRF to PDN GW) +15. Modify Bearer Response (PDN GW to MME) +16. Radio and Access Bearer (Established between E-UTRAN and MME) / 16. GTP Tunnel (Established between PDN GW and vPCRF) +17. UE Requested PDN Connectivity (MME to PDN GW) +18. Non-3GPP EPS Bearer Release (PDN GW to Trusted Non-3GPP IP Access/ePDG) + +**Notes:** + +- (C) indicates the main sequence of messages for the handover. +- (A) indicates a sub-sequence of messages (7, 8, 9) related to the PCEF-Initiated IP-CAN Session Modification Procedure. +- (B) indicates a sub-sequence of messages (13, 14) related to the Modify Bearer Request/Response procedure. + +Figure 8.2.10.2.5-1: Handover from Trusted WLAN on S2a to 3GPP access for roaming, LBO and non-roaming scenarios + +This procedure is as in TS 23.402 clause 8.2.1.1/8.2.1.2 with the following differences: + +- Step 1. There is a GTP or PMIP tunnel between TWAN and PGW. +- Step 18. The PDN GW shall initiate resource allocation deactivation procedure in the TWAN as defined in clause 8.2.10.2.9. + +##### 8.2.10.2.6 UE/TWAN Requested PDN disconnection in WLAN on S2a + +###### 8.2.10.2.6.1 UE/TWAN requested PDN disconnection in WLAN on GTP S2a + +For multiple PDN connections, this disconnection procedure shall be repeated for each PDN connection that needs to be released. + +![Sequence diagram of UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN. The diagram shows interactions between UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxv, vPCRF, and hPCRF. Step 1: UE sends PDN Disconnect Request to TWAN. Step 2: TWAN sends Delete Session Request to PDN GW. Step 3: PDN GW sends Update PDN GW Address to AAA Proxv. Step 4: PDN GW initiates PCEF-Initiated IP-CAN Session Termination Procedure with vPCRF. Step 5: PDN GW sends Delete Session Response to TWAN. Step 6: TWAN sends PDN Disconnect Response to UE. Step 7: TWAN sends PDN Disconnection Request to UE. Step 8: UE sends PDN Disconnection Response to TWAN. Step 9: TWAN specific resource Release Procedure (dashed box).](3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant AAA_Proxv as AAA Proxv + participant vPCRF + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of AAA_Proxv: Roaming Scenarios + + UE-->>TWAN: 1. PDN Disconnect Request + TWAN->>PDN_GW: 2. Delete Session Request + PDN_GW->>AAA_Proxv: 3. Update PDN GW Address + Note right of AAA_Proxv: 4. PCEF-Initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Delete Session Response + TWAN-->>UE: 6. PDN Disconnect Response + TWAN->>UE: 7. PDN Disconnection Request + UE-->>TWAN: 8. PDN Disconnection Response + Note left of PDN_GW: 9. TWAN specific resource Release Procedure + +``` + +Sequence diagram of UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN. The diagram shows interactions between UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxv, vPCRF, and hPCRF. Step 1: UE sends PDN Disconnect Request to TWAN. Step 2: TWAN sends Delete Session Request to PDN GW. Step 3: PDN GW sends Update PDN GW Address to AAA Proxv. Step 4: PDN GW initiates PCEF-Initiated IP-CAN Session Termination Procedure with vPCRF. Step 5: PDN GW sends Delete Session Response to TWAN. Step 6: TWAN sends PDN Disconnect Response to UE. Step 7: TWAN sends PDN Disconnection Request to UE. Step 8: UE sends PDN Disconnection Response to TWAN. Step 9: TWAN specific resource Release Procedure (dashed box). + +**Figure 8.2.10.2.6.1-1: UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN** + +This procedure applies to the Non-Roaming, Home Routed Roaming and Local Breakout cases. In the Local Breakout case, the vPCRF forwards messages between the PDN GW and the hPCRF. In the LBO cases, the 3GPP AAA Proxy serves as an intermediary between the Trusted Non-3GPP IP Access and the 3GPP AAA Server in the HPLMN. In the non-roaming and Home Routed Roaming case, the vPCRF is not involved at all. + +If dynamic policy provisioning is not deployed, the optional steps of interaction between the PDN GW and PCRF do not occur. Instead, the PDN GW may employ static configured policies. + +- Step 1. If the PDN disconnection is initiated by the UE, the UE sends a WCS PDN Disconnection Request (p2p link ID) to the TWAG. The p2p link ID identifies a PDN connection uniquely. Step 2. The TWAN releases the PDN connection and sends a Delete Session Request (Linked EPS Bearer ID) message for this PDN connection to the PDN GW. +- Step 3. The PDN GW informs the 3GPP AAA Server of the PDN disconnection. +- Step 4. The PDN GW deletes the IP CAN session associated with the UE and executes a PCEF-Initiated IP-CAN Session Termination Procedure with the PCRF as specified in TS 23.203 [4]. +- Step 5. The PDN GW acknowledges with a Delete Session Response (Cause) message. +- Step 6. TWAN sends WCS PDN disconnection response to the UE. + +- Step 7. If the PDN disconnection was initiated by the TWAG, then the UE is informed of the disconnection by means of a WCS PDN Disconnection Request (User Plane Connection ID). +- Step 8. The UE acknowledges the disconnection request received in step 7. + +NOTE: Either step 1 and 6, or step 7 and 8, are performed. Step 1 and 6 is used for UE initiated disconnection procedure, step 7 and 8 is for TWAN initiated disconnection procedure. + +NOTE: If NSWO disconnection is performed steps from 2 to 5 are skipped. + +##### 8.2.10.2.6.2 UE TWAN requested PDN disconnection in WLAN on PMIP S2a + +Editor's Notes: The procedure is FFS. + +##### 8.2.10.2.7 UE initiated Detach in WLAN on S2a + +###### 8.2.10.2.7.1 UE initiated Detach in WLAN on GTP S2a + +![Sequence diagram for UE-initiated Detach procedure with GTP S2a in WLAN. Lifelines: UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, HSS/AAA. The diagram shows a sequence of messages: 1. Detach Request (UE to TWAN), 2. Delete Session Request (TWAN to PDN GW), 3. Update PDN GW Address (PDN GW to HSS/AAA), 4. PCEF-Initiated IP-CAN Session Termination Procedure (PDN GW to vPCRF), 5. Delete Session Response (PDN GW to TWAN), 6. Detach Response (TWAN to UE), and 7. TWAN specific resource Release Procedure (UE to TWAN). A 'Roaming Scenarios' box covers the AAA Proxv, vPCRF, and hPCRF lifelines.](6b9ee906d502aece4a2becf5895db07a_img.jpg) + +Sequence diagram for UE-initiated Detach procedure with GTP S2a in WLAN. Lifelines: UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, HSS/AAA. The diagram shows a sequence of messages: 1. Detach Request (UE to TWAN), 2. Delete Session Request (TWAN to PDN GW), 3. Update PDN GW Address (PDN GW to HSS/AAA), 4. PCEF-Initiated IP-CAN Session Termination Procedure (PDN GW to vPCRF), 5. Delete Session Response (PDN GW to TWAN), 6. Detach Response (TWAN to UE), and 7. TWAN specific resource Release Procedure (UE to TWAN). A 'Roaming Scenarios' box covers the AAA Proxv, vPCRF, and hPCRF lifelines. + +Figure 8.2.10.2.7.1-1: UE -initiated Detach procedure with GTP S2a in WLAN + +- Step 1 The UE sends a WCS Detach Request to the TWAN. +- Step 2 - Step 5. Same as step 2-5 in clause 8.2.10.2.6.1 The TWAN deleted all the S2a bearers. - Step 6. TWAN send Detach Response to the UE. + +For NSWO connection, the release procedure is the same as TS 23.402 clause 16.3.1.1. + +##### 8.2.10.2.7.2 UE initiated Detach in WLAN on PMIP S2a + +**Editor's Notes:** This procedure is FFS. + +##### 8.2.10.2.8 HSS/AAA Initiated Detach Procedure in WLAN + +##### 8.2.10.2.8.1 HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a + +![Sequence diagram for HSS/AAA Initiated Detach Procedure with GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box covers AAA Proxv, vPCRF, and hPCRF. The steps are: 1. Detach Request (HSS/AAA to TWAN), 2. Delete Session Request (TWAN to PDN GW), 3. Update PDN GW Address (PDN GW to HSS/AAA), 4. PCEF-Initiated IP-CAN Session Termination Procedure (PDN GW to vPCRF), 5. Delete Session Response (PDN GW to TWAN), 6. Detach Request (TWAN to UE), 7. TWAN specific resource Release Procedure (TWAN to UE).](8bd7adf738ea4b7e65e0d6f67e122d55_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN GW + participant AAA Proxv + participant vPCRF + participant hPCRF + participant HSS/AAA + + Note right of AAA Proxv: Roaming Scenarios + + HSS/AAA->>TWAN: 1. Detach Request + TWAN->>PDN GW: 2. Delete Session Request + PDN GW->>HSS/AAA: 3. Update PDN GW Address + PDN GW-->>vPCRF: 4. PCEF-Initiated IP-CAN Session Termination Procedure + PDN GW->>TWAN: 5. Delete Session Response + TWAN->>UE: 6. Detach Request + Note left of UE: 7. TWAN specific resource Release Procedure + +``` + +Sequence diagram for HSS/AAA Initiated Detach Procedure with GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box covers AAA Proxv, vPCRF, and hPCRF. The steps are: 1. Detach Request (HSS/AAA to TWAN), 2. Delete Session Request (TWAN to PDN GW), 3. Update PDN GW Address (PDN GW to HSS/AAA), 4. PCEF-Initiated IP-CAN Session Termination Procedure (PDN GW to vPCRF), 5. Delete Session Response (PDN GW to TWAN), 6. Detach Request (TWAN to UE), 7. TWAN specific resource Release Procedure (TWAN to UE). + +**Figure 8.2.10.2.8.1-1: HSS/AAA Initiated Detach Procedure with GTP S2a** + +-Step-1 HSS/AAA send Detach Request to the TWAN + +-Step-2-step5 is same as procedure in 8.2.10.2.6.1. + +For NSWO connection, the release procedure is the same as TS 23.402 clause 16.3.1.1. + +###### 8.2.10.2.8.2 HSS/AAA Initiated Detach Procedure in WLAN on PMIP S2a + +**Editor's Notes:** This procedure is still to be added. + +##### 8.2.10.2.9 PDN GW initiated Resource Allocation Deactivation + +###### 8.2.10.2.9.1 PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a + +![Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. The process involves IP-CAN Session Modification, Delete Bearer Request, TWAN specific resource Release Procedure, Delete Bearer Response, and Update PDN GW Address. A 'Roaming Scenarios' box groups the vPCRF, 3GPP AAA proxy, and hPCRF. Steps 7-8 are referenced as being in clause 8.2.10.2.6.1.](4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant 3GPP_AAA_proxy as 3GPP AAA proxy + participant hPCRF + participant AAA_HSS as AAA/HSS + + Note right of vPCRF: Roaming Scenarios + PDN_GW->>vPCRF: 1. IP-CAN Session Modification + PDN_GW->>TWAN: 2. Delete Bearer Request + Note left of TWAN: Steps 7-8 as in clause 8.2.10.2.6.1 + Note left of TWAN: 3. TWAN specific resource Release Procedure + TWAN->>PDN_GW: 4. Delete Bearer Response + PDN_GW->>AAA_HSS: 5. Update PDN GW Address + PDN_GW->>vPCRF: 6. IP-CAN Session Modification + +``` + +Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. The process involves IP-CAN Session Modification, Delete Bearer Request, TWAN specific resource Release Procedure, Delete Bearer Response, and Update PDN GW Address. A 'Roaming Scenarios' box groups the vPCRF, 3GPP AAA proxy, and hPCRF. Steps 7-8 are referenced as being in clause 8.2.10.2.6.1. + +**Figure 8.2.10.2.9.1-1: PDN GW Initiated Bearer Deactivation with GTP on S2a** + +The step 1,-6 is same as step 1,2,4,5,6 in Clause 16.4.1 in TS23.402 + +If all TWAN resources related to a PDN connection are released, then step 7 and 8 of Figure 8.2.10.2.6.1-1: (UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN) are carried out to inform the UE of the PDN connection release. + +##### 8.2.10.2.9.2 PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a + +*Editor's Notes: This procedure is FFS.* + +#### 8.2.10.3 Impacts on existing nodes or functionality + +*Editor's Notes: Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause.* + +#### 8.2.10.4 Evaluation + +*Editor's Notes: The fulfilment to the requirements in Subclause 8.1 as well as simplicity of implementation in the UE should be evaluated.* + +## 8.3 Evaluation + +*Editor's Note: This clause will include solution(s) assessment.* + +The following aspects are considered and evaluated for the solution: + +- i) Impacts to existing network deployment: + - a) There is no additional requirement for WLAN APs compared to Rel-11. + - b) For TWAG, it shall support EAP enhancement for UE and network capability negotiation, and support the new control plane protocol, support p2p link for each PDN connections. +- ii) Impacts to UE: + +The UE should be capable of supporting enhanced EAP procedures. + +It should support the new control plane protocol and user plane p2p link using virtual MAC or VLAN. +- iii) Impacts to 3GPP protocols/extensions (e.g. EAP AKA'): + +The following protocols are extended: + + - a) UE network capability negotiation is enhanced for EAP protocol. + - b) Defining a new control plane protocol for mobility management (e.g. APN, PDN type, user plane p2p link delivery etc). +- iv) Impacts to protocols defined by other SDOs (e.g. DHCP): + +For VLAN based/Virtual MAC based control plane protocol, we need to define a new Ethertype in IEEE. +- v) Control plane + - a) The latency/load can be affected by the messages in the following procedures: + - b) A new control plane protocol is used for all the PDN connections/ NSWO connection. + - c) For L3 based control plane protocol, the NSWO connection may also established by DHCP/RS/RA after authentication procedure. +- vi) Compliance to clause 8.1 SaMOG phase-2 system requirements: + - a) Co-existence with Rel-11 SaMOG + - b) Support for IP address preservation during handover + - c) Simultaneous support for S2a EPC-routed and NSWO; support of simultaneous multiple PDN connections +- vii) Other functional limitations: + +There is no other functional limitation. + +### 8.2.x Solution x + +#### 8.2.x.1 Functional Description + +**Editor's Notes:** It should be described whether and how the solution fulfils the requirements in Subclause 8.1. + +#### 8.2.x.2 Procedures + +**Editor's Notes:** The call flows are described in this subclause. + +#### 8.2.x.3 Impacts on existing nodes or functionality + +**Editor's Notes:** Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause. + +#### 8.2.x.4 Evaluation + +**Editor's Notes:** The fulfilment to the requirements in Subclause 8.1 as well as simplicity of implementation in the UE should be evaluated. + +## 8.3 Evaluation + +**Editor's Note:** This clause will include solution(s) assessment. + +# --- 9 Conclusion + +**Editor's note:** This clause will provide conclusions with respect to what further specification work is required in order to provide the feature of S2a mobility based on GTP and WLAN access to EPC. + +## 9.1 Conclusion on SaMOG Phase 1 + +For the support of SaMOG without UE impact, it has been concluded that Solution 2 (described in clause 7.1.2) is selected as the basis for normative specifications: + +- The style of the reference model and call flows of Solution 1 (described in clause 7.1.1.1, 7.1.1.2 and 7.1.1.3) will be used for documentation of the normative specification, i.e., the internal structure of the WLAN Access Network will not be exposed. +- The L2 attach/detach triggers for solution 2 (described in clause 7.1.2.4) will be used in the work of normative specifications. Only L2 attach triggers are used for PDN type IPv6 and IPv4v6; L2 or L3 attach triggers may be used for PDN type IPv4 as described in clause 9.1.1. +- Enhancements on STa reference point in clause 7.1.1.1 will be used in the work of normative specifications. +- Simultaneous access for a UE to EPC through S2a and non-seamless offload using a single SSID is not supported. For a network deployment, behaviour described in clause 7.1.1.4 will be used in the work of normative specifications. +- Whether multiple TNAN functions are mapped to a single non-3GPP access entity, or a single TNAN function is distributed among multiple non-3GPP access entities is out-of-scope of 3GPP. + +### 9.1.1 Conclusion on attach trigger solution + +Two solutions are proposed in chapter 7.1. The main difference between the two solutions is how the TNSP/TWAG is triggered to setup the S2a tunnel towards the PGW. For the support of SaMOG without UE impact, it has been concluded that: + +After the successful authentication, the AAA in the TNAN (TNAP/TWAP) knows from the UE profile the PDN type for the default APN. There are two possibilities: + +1. PDN type = IPv6 or IPv4v6. In that case, TNAP/TWAP shall send a trigger signal to the TNSP/TWAG. TNSP/TWAG establishes the S2a tunnel. +2. PDN type = IPv4. In that case, S2a tunnel setup by the TNSP/TWAG is triggered either by a signal from the TNAP/TWAP, or by a L3 trigger from the UE. A trigger from the TNAP/TWAP is the recommended way. + +In all cases, there shall be no difference on STa and S2a signaling. + +NOTE: That this conclusion applies even though the call flows in clause 7.1 have not been updated to reflect this conclusion. + +## 9.2 Conclusion on SaMOG Phase 2 + +# Annex A: Example of WLAN integrated with Femto + +For the Femto, the network will perform authentication and integrity checking through AAA before the femto can be connect to the EPC. In addition, the IPSec function in Femto can be used to build a secure transmission tunnel through the backhaul to the EPC. Therefore, the WLAN module integrated with the Femto box can leverage the authentication, integrity checking and the IPSec function to build a trusted WLAN access for connectivity to the EPC. + +![Diagram showing the connection path from a Femto integrated with WLAN, through an IPSec tunnel, to an IPSec termination function, and then via an S2a interface to a PGW.](a47713c2491e6ce619259ed2f196fd24_img.jpg) + +``` +graph LR; A[Femto integrated with WLAN] -- IPSec --> B[IPSec termination function]; B -- S2a --> C[PGW]; +``` + +Diagram showing the connection path from a Femto integrated with WLAN, through an IPSec tunnel, to an IPSec termination function, and then via an S2a interface to a PGW. + +**Figure A-1: WLAN integrated with Femto accessing EPC through S2a** + +Editor's note: Figure A-1 is illustrative and does not imply the location of the non-3GPP GTP peer. + +# Annex B: Change History + +| Change history | | | | | | | | | +|----------------|--------|-----------|----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 2011-04 | SA2#84 | | | | Initial draft | | 0.0.0 | | +| 2011-04 | SA2#84 | | | | Inclusion of P-CRs approved during SA2#84: S2-111940, S2-111941, S2-112138, S2-111943 | 0.0.0 | 0.1.0 | | +| 2011-05 | | | | | Add the TR number (Rapporteur) | 0.1.0 | 0.1.1 | | +| 2011-05 | SA2#85 | | | | Inclusion of P-CRs approved during SA2#85: S2-112731, S2-112733, S2-112836, S2-112837, S2-112905, S2-112906, S2-112907, S2-112908 | 0.1.1 | 0.2.0 | | +| 2011-07 | SA2#86 | | | | Inclusion of P-CRs approved during SA2#86: S2-113828, S2-113829, S2-113779 | 0.2.0 | 0.3.0 | | +| 2011-10 | SA2#87 | | | | Inclusion of P-CRs approved during SA2#87: S2-114542, S2-114543, S2-114697, S2-114648, S2-114681, S2-114682, S2-114683, S2-114626 | 0.3.0 | 0.4.0 | | +| 2011-11 | SA2#88 | | | | Inclusion of P-CRs approved during SA2#88: S2-114800, S2-114857, S2-114987, S2-115319, S2-115332, S2-115361, S2-115364, S2-115433, S2-115434, S2-115456 | 0.4.0 | 0.5.0 | | +| 2011-12 | SP#54 | SP-110758 | - | - | MCC Update to version 1.0.0 for presentation to TSG SA for information | 0.5.0 | 1.0.0 | | +| 2012-05 | SA2#91 | | | | Inclusion of P-CRs approved during SA2#91: S2-122490, S2-122491 | 1.0.0 | 1.1.0 | | +| 2012-07 | SA2#92 | | | | Inclusion of P-CRs approved during SA2#92: S2-123190, S2-123191, S2-123193, S2-123194, S2-123195, S2-123196, S2-123365, | 1.1.0 | 1.2.0 | | +| 2012-12 | SA2#94 | | | | Inclusion of P-CRs approved during SA2#94: S2-124845, S2-124768, S2-124846, S2-124770, S2-124771, S2-124772, S2-124847 | 1.2.0 | 1.3.0 | | +| 2013-02 | SA2#95 | | | | Inclusion of P-CRs approved during SA2#95: S2-130562, S2-130675, S2-130565, S2-130677, S2-130566, S2-130625, S2-130624 | 1.3.0 | 1.4.0 | | + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Abbreviations ..... | 10 | +| 4 Scenarios..... | 11 | +| 5 Architectural assumptions..... | 11 | +| 5.1 Architectural assumptions for GTP based S2a..... | 11 | +| 5.2 Architectural assumptions for WLAN access to EPC through S2a ..... | 11 | +| 5.2.1 Assumptions for solutions with no Impact to the UE..... | 12 | +| 6 Solutions for GTP based S2a ..... | 12 | +| 6.1 Solution 1 ..... | 13 | +| 6.1.1 Architecture ..... | 13 | +| 6.1.2 Functional description ..... | 15 | +| 6.1.2.1 Bearer model for a PDN connection..... | 15 | +| 6.1.3 Information flows ..... | 15 | +| 6.1.3.1 Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW ..... | 15 | +| 6.1.3.2 Detach and PDN Disconnection with GTP on S2a..... | 18 | +| 6.1.3.2.1 UE/Trusted Non-3GPP IP Access Network Initiated Detach and UE/Trusted Non-3GPP IP Access requested PDN Disconnection Procedure with GTP on S2a ..... | 18 | +| 6.1.3.2.2 HSS/AAA Initiated Detach Procedure with GTP on S2a ..... | 19 | +| 6.1.3.3 UE-initiated Connectivity to Additional PDN with GTP on S2a ..... | 19 | +| 6.1.3.4 Dedicated bearer activation with GTP on S2a..... | 21 | +| 6.1.3.5 Network-initiated S2a bearer modification with GTP on S2a ..... | 22 | +| 6.1.3.5.1 PDN GW Initiated Bearer Modification ..... | 22 | +| 6.1.3.5.2 HSS Initiated Subscribed QoS Modification ..... | 23 | +| 6.1.3.6 PDN GW initiated Resource Allocation Deactivation with GTP on S2a..... | 24 | +| 6.1.3.7 Handovers without Optimizations Between 3GPP Accesses and Non-3GPP IP Accesses with S2a GTP..... | 25 | +| 6.1.3.7.1 Handover from a trusted non-3GPP IP access with S2a GTP to 3GPP Access..... | 25 | +| 6.1.3.7.2 Handover from 3GPP Access to a trusted non-3GPP IP access with S2a GTP..... | 26 | +| 7 Additional considerations for WLAN access to EPC through S2a for Phase 1 ..... | 28 | +| 7.1 Solutions without UE Impact ..... | 28 | +| 7.1.0 General ..... | 28 | +| 7.1.1 Solution 1 ..... | 28 | +| 7.1.1.1 Reference model ..... | 28 | +| 7.1.1.2 Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW ..... | 31 | +| 7.1.1.3 Without-UE-impact procedures except Initial Attach ..... | 33 | +| 7.1.1.4 SaMOG deployment ..... | 33 | +| 7.1.1.5 PMIP based S2a considerations..... | 33 | +| 7.1.2 Solution 2..... | 34 | +| 7.1.2.0 General..... | 34 | +| 7.1.2.1 Reference Model..... | 34 | +| 7.1.2.2 Network elements ..... | 36 | +| 7.1.2.2.1 UE..... | 36 | +| 7.1.2.2.2 Trusted WLAN AAA Proxy ..... | 36 | +| 7.1.2.2.3 Trusted WLAN Access Gateway ..... | 36 | +| 7.1.2.3 Reference Points ..... | 37 | +| 7.1.2.3.1 Ta reference point..... | 37 | +| 7.1.2.3.2 Tg reference point ..... | 37 | +| 7.1.2.3.3 Tn reference point ..... | 37 | +| 7.1.2.3.4 Tw reference point ..... | 38 | +| 7.1.2.3.5 Tu reference point ..... | 38 | + +| | | | +|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 7.1.2.4 | Procedures..... | 38 | +| 7.1.2.4.1 | Initial Attach to Trusted Non-3GPP WLAN Access procedure ..... | 39 | +| 7.1.2.4.2 | UE/Trusted Non-3GPP WLAN Access Network Initiated Detach procedure..... | 40 | +| 7.1.2.4.3 | HSS/AAA Initiated Detach procedure ..... | 41 | +| 7.1.2.4.4 | Other procedures ..... | 41 | +| 7.1.3 | Handovers with or without TNSP/TWAG relocation with unmodified UEs..... | 41 | +| 8 | Additional considerations for WLAN access to EPC through S2a for Phase 2..... | 41 | +| 8.1 | Requirements..... | 41 | +| 8.1A | Key issues..... | 42 | +| 8.2 | Solutions..... | 43 | +| 8.2.1 | Solution 1: Tunnelled approach with dedicated UE-TWAG control protocol..... | 43 | +| 8.2.1.1 | Functional Description..... | 43 | +| 8.2.1.1.1 | Overview ..... | 43 | +| 8.2.1.1.2 | User plane..... | 43 | +| 8.2.1.1.2.1 | Alternative 1: XYZ = GRE..... | 44 | +| 8.2.1.1.1.2.2 | Alternative 2: XYZ = VLAN ..... | 44 | +| 8.2.1.1.3 | Control plane ..... | 44 | +| 8.2.1.1.3.1 | Alternative 1: L2.5-based control protocol..... | 44 | +| 8.2.1.1.3.2 | Alternative 2: L3-based control protocol..... | 45 | +| 8.2.1.1.4 | Protocol Stacks ..... | 45 | +| 8.2.1.2 | Procedures..... | 46 | +| 8.2.1.2.1 | Initial Attach in WLAN on S2a..... | 46 | +| 8.2.1.2.2 | Initial Attach in single-connection scenario in WLAN on S2a (continuation) ..... | 47 | +| 8.2.1.2.2.1 | Initial Attach in single-connection scenario in WLAN on GTP S2a (continuation)..... | 47 | +| 8.2.1.2.2.2 | Initial Attach in single-connection scenario in WLAN on PMIP S2a (continuation) ..... | 47 | +| 8.2.1.2.3 | Initial Attach in multi-connection scenario in WLAN on S2a (continuation) ..... | 48 | +| 8.2.1.2.4 | UE-Initiated Connectivity to PDN in WLAN on S2a..... | 48 | +| 8.2.1.2.4.1 | UE-Initiated Connectivity to PDN in WLAN on GTP S2a..... | 48 | +| 8.2.1.2.4.2 | UE-Initiated Connectivity to PDN in WLAN on PMIP S2a ..... | 49 | +| 8.2.1.2.5 | Handover procedure in single-connection scenario from 3GPP access to WLAN on S2a..... | 50 | +| 8.2.1.2.5.1 | Handover in single-connection scenario from 3GPP access to WLAN on GTP S2a ..... | 50 | +| 8.2.1.2.5.2 | Handover in single-connection scenario from 3GPP access to WLAN on PMIP S2a..... | 51 | +| 8.2.1.2.6 | Handover procedure in multi-connection scenario from 3GPP access to WLAN on S2a..... | 51 | +| 8.2.1.2.6.1 | Handover in multi-connection scenario from 3GPP access to WLAN on GTP S2a..... | 51 | +| 8.2.1.2.6.2 | Handover from 3GPP access to WLAN on PMIP S2a..... | 53 | +| 8.2.1.2.7 | Handover procedure from WLAN on S2a to 3GPP access..... | 54 | +| 8.2.1.2.8 | Detach and PDN disconnection in WLAN on S2a ..... | 55 | +| 8.2.1.2.8.1 | Detach and PDN disconnection in WLAN on GTP S2a ..... | 55 | +| 8.2.1.2.8.1.1 | UE/TWAN Initiated Detach and UE/TWAN requested PDN Disconnection Procedure<br>in WLAN on GTP S2a..... | 55 | +| 8.2.1.2.8.1.2 | HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a..... | 56 | +| 8.2.1.2.8.2 | Detach and PDN disconnection in WLAN on PMIP S2a ..... | 56 | +| 8.2.1.2.9 | PDN GW initiated Resource Allocation Deactivation..... | 56 | +| 8.2.1.2.9.1 | PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a ..... | 56 | +| 8.2.1.2.9.2 | PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a..... | 56 | +| 8.2.1.3 | Impacts on existing nodes or functionality ..... | 56 | +| 8.2.1.4 | Evaluation ..... | 56 | +| 8.2.2 | Solution 2: Layer 2 solution based on Stateful Address Configuration of Per-PDN<br>Connection/NSWO Point-to-Point Link Multiplexed at Layer 2..... | 57 | +| 8.2.2.1 | Functional Description..... | 57 | +| 8.2.2.1.1 | User Plane Multiplexing for Per-PDN Connection / NSWO Point-to-Point Link..... | 57 | +| 8.2.2.1.1.0 | General ..... | 57 | +| 8.2.2.1.1.1 | Per-PDN Connection/NSWO Virtual Point-to-Point Link Model based on distinct VLAN<br>ID..... | 57 | +| 8.2.2.1.1.2 | Per-PDN Connection/NSWO Virtual Point-to-Point Link Model based on distinct layer 2<br>TWAG MAC addresses..... | 58 | +| 8.2.2.1.2 | Initial Attach in WLAN..... | 59 | +| 8.2.2.1.3 | UE Requested PDN or NSWO connectivity ..... | 60 | +| 8.2.2.1.4 | UE Requested PDN or NSWO disconnection..... | 62 | +| 8.2.2.1.5 | HSS/AAA Initiated PDN or NSWO Disconnection procedure in WLAN ..... | 64 | +| 8.2.2.1.6 | HSS/AAA Initiated Detach procedure in WLAN ..... | 64 | + +| | | | +|---------------|-------------------------------------------------------------------------------------------------------------|-----| +| 8.2.2.1.7 | Handover from 3GPP Access to Trusted WLAN Access ..... | 65 | +| 8.2.2.1.8 | Handover from Trusted WLAN Access to 3GPP Access ..... | 66 | +| 8.2.2.2 | Impacts on existing nodes or functionality ..... | 66 | +| 8.2.2.3 | Evaluation ..... | 67 | +| 8.2.3 | Solution 3: Stateful DHCP-based Solution ..... | 68 | +| 8.2.3.1 | Functional Description..... | 68 | +| 8.2.3.1.1 | Functional Overview and Overall System Impacts..... | 68 | +| 8.2.3.1.1.1 | Overview ..... | 68 | +| 8.2.3.1.1.2 | UE Impacts ..... | 68 | +| 8.2.3.1.1.3 | Trusted WLAN Access Gateway Impacts..... | 69 | +| 8.2.3.1.1.4 | Trusted WLAN Access Point Impacts ..... | 69 | +| 8.2.3.1.1.5 | Trusted WLAN Backhaul Impacts ..... | 69 | +| 8.2.3.1.2 | Control Plane Management..... | 69 | +| 8.2.3.1.2.1 | UE-Network Capability Negotiation ..... | 69 | +| 8.2.3.1.2.2 | Connection related control plan interface..... | 69 | +| 8.2.3.1.3 | User plane management ..... | 70 | +| 8.2.3.1.3.1 | Alternative 1: GRE over IP ..... | 70 | +| 8.2.3.1.3.1.2 | GRE over IP tunneling establishment..... | 71 | +| 8.2.3.1.3.2 | Alternative 2: TWAG virtual MAC Address ..... | 72 | +| 8.2.3.1.4 | Protocol stack ..... | 73 | +| 8.2.3.1.5 | IP addressing support for SaMOG phase-2..... | 74 | +| 8.2.3.1.5.1 | IP address assignment for NSWO ..... | 74 | +| 8.2.3.1.5.2 | IP address assignment for GRE over IP tunnel ..... | 74 | +| 8.2.3.1.5.3 | IP address assignment for EPC-routed ..... | 74 | +| 8.2.3.2 | Procedures..... | 75 | +| 8.2.3.2.1 | Initial Attach in WLAN on S2a..... | 75 | +| 8.2.3.2.1.1 | Initial Attach in WLAN on GTP/PMIP S2a..... | 75 | +| 8.2.3.2.2 | UE-initiated Connectivity to Additional PDN ..... | 78 | +| 8.2.3.2.2.1 | UE-initiated Connectivity to Additional PDN on GTP S2a ..... | 78 | +| 8.2.3.2.2.2 | UE-initiated Connectivity to Additional PDN on PMIP S2a ..... | 80 | +| 8.2.3.2.3 | Detach and PDN disconnection in WLAN on S2a ..... | 81 | +| 8.2.3.2.3.1 | Detach and PDN disconnection in WLAN on GTP S2a ..... | 81 | +| 8.2.3.2.3.1.1 | UE/TWAN requested single PDN Disconnection Procedure in WLAN on GTP S2a ..... | 81 | +| 8.2.3.2.3.1.2 | UE/TWAN requested one IPv4 Address or one IPv6 address release for a dual stack PDN in WLAN on GTP S2a..... | 82 | +| 8.2.3.2.3.1.3 | UE/TWAN requested Detach Procedure in WLAN on GTP S2a ..... | 83 | +| 8.2.3.2.3.1.4 | HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a ..... | 84 | +| 8.2.3.2.3.2 | Detach and PDN disconnection in WLAN on PMIP S2a..... | 86 | +| 8.2.3.2.3.2.1 | UE/TWAN requested single PDN Disconnection Procedure in WLAN on PMIP S2a ..... | 86 | +| 8.2.3.2.3.2.2 | UE/TWAN requested multiple PDN Disconnection Procedure in WLAN on PMIP S2a..... | 86 | +| 8.2.3.2.3.2.3 | UE/TWAN requested Detach Procedure in WLAN on PMIP S2a..... | 87 | +| 8.2.3.2.3.2.4 | HSS/AAA Initiated Detach Procedure in WLAN on PMIP S2a ..... | 87 | +| 8.2.3.2.4 | PDN GW initiated Resource Allocation Deactivation in WLAN on S2a..... | 88 | +| 8.2.3.2.4.1 | PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a..... | 88 | +| 8.2.3.2.4.2 | PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a..... | 89 | +| 8.2.3.2.5 | Dedicated bearer activation in WLAN on GTP S2a ..... | 90 | +| 8.2.3.2.6 | Network-initiated bearer modification in WLAN on GTP S2a ..... | 90 | +| 8.2.3.2.7 | Handover from 3GPP Access to Trusted WLAN Access..... | 90 | +| 8.2.3.2.7.1 | Handover from 3GPP Access to Trusted WLAN Access on GTP S2a..... | 90 | +| 8.2.3.2.7.2 | Handover from 3GPP Access to Trusted WLAN Access on PMIP S2a ..... | 93 | +| 8.2.3.3 | Impacts on existing nodes or functionality ..... | 93 | +| 8.2.3.4 | Evaluation ..... | 93 | +| 8.2.4 | Solution 4..... | 95 | +| 8.2.4.1 | Functional Description..... | 95 | +| 8.2.4.1.1 | P2P link ..... | 95 | +| 8.2.5 | Solution 5: Associating APN/PDN with Virtual IP Interface ..... | 95 | +| 8.2.5.1 | Functional Description..... | 95 | +| 8.2.5.1.1 | General ..... | 95 | +| 8.2.5.2 | Procedures..... | 97 | +| 8.2.5.2.2 | Connection Establishment Procedure..... | 97 | +| 8.2.5.2.3 | UE Initiated Disconnection Procedure ..... | 100 | +| 8.2.5.2.4 | HSS/AAA Initiated Disconnection Procedure ..... | 101 | + +| | | | +|--------------|-------------------------------------------------------------------------------------------|-----| +| 8.2.5.2.5 | Handover procedure between 3GPP access and WLAN on GTP S2a..... | 103 | +| 8.2.5.3 | Impacts on existing nodes or functionality ..... | 104 | +| 8.2.5.4 | Evaluation ..... | 104 | +| 8.2.6 | Solution 6: X..... | 104 | +| 8.2.7 | Solution 7: PPP over Ethernet (PPPoE) ..... | 104 | +| 8.2.7.1 | Functional Description..... | 104 | +| 8.2.7.1.1 | Overview ..... | 105 | +| 8.2.7.2 | Procedures..... | 107 | +| 8.2.7.2.1 | PDN Connectivity Parameter Negotiation ..... | 107 | +| 8.2.7.2.1.1 | Option 1: PDN connectivity parameters negotiated during PPP session establishment ..... | 107 | +| 8.2.7.2.1.2 | Option 2: PDN connectivity parameters negotiated during PPPoE session establishment..... | 107 | +| 8.2.7.2.2 | Initial Attach and UE-initiated Connectivity to PDN ..... | 108 | +| 8.2.7.2.3 | PDN Connection Release ..... | 110 | +| 8.2.7.2.4 | Handover from 3GPP access to WLAN..... | 111 | +| 8.2.7.3 | Impacts on existing nodes or functionality ..... | 111 | +| 8.2.7.4 | Evaluation ..... | 111 | +| 8.2.8 | Solution 8: Solution using new 3GPP specific LLC/SNAP header settings ..... | 112 | +| 8.2.8.1 | Functional Description..... | 113 | +| 8.2.8.1.1 | General ..... | 113 | +| 8.2.8.1.2 | Protocol stack ..... | 113 | +| 8.2.8.1.3 | Protocol header..... | 114 | +| 8.2.8.2 | Procedures..... | 115 | +| 8.2.8.3 | Impacts on existing nodes or functionality ..... | 118 | +| 8.2.8.4 | Evaluation ..... | 118 | +| 8.2.9 | Solution 9: EAP based signaling solution ..... | 119 | +| 8.2.9.1 | Functional Description..... | 119 | +| 8.2.9.1.1 | General ..... | 119 | +| 8.2.9.1.2 | Protocol stack ..... | 120 | +| 8.2.9.1.3 | Signaling information from UE to the network ..... | 120 | +| 8.2.9.1.4 | Signaling information from the network to the UE..... | 121 | +| 8.2.9.2 | Procedures..... | 122 | +| 8.2.9.2.1 | Initial Attach in WLAN on S2a..... | 122 | +| 8.2.9.2.2 | UE-Initiated Connectivity to Additional PDN in WLAN on S2a ..... | 123 | +| 8.2.9.2.2.1 | UE-Initiated Connectivity to Additional PDN in WLAN on GTP S2a..... | 123 | +| 8.2.9.2.2.2 | UE-Initiated Connectivity to Additional PDN in WLAN on PMIP S2a..... | 124 | +| 8.2.9.2.3 | Handover procedure between 3GPP access and WLAN on S2a ..... | 124 | +| 8.2.9.2.3.1 | Handover from 3GPP access to WLAN on GTP S2a ..... | 124 | +| 8.2.9.2.3.2 | Handover from 3GPP access to WLAN on PMIP S2a..... | 124 | +| 8.2.9.2.3.3 | Handover from TWAN to 3GPP access ..... | 125 | +| 8.2.9.2.4 | PDN GW initiated Resource Allocation Deactivation..... | 125 | +| 8.2.9.2.4.1 | PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a ..... | 125 | +| 8.2.9.2.4.2 | PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a..... | 125 | +| 8.2.9.2.5 | TWAN requested PDN Disconnection Procedures..... | 125 | +| 8.2.9.2.5.1 | TWAN requested PDN Disconnection Procedure in WLAN on GTP S2a..... | 125 | +| 8.2.9.2.5.2 | TWAN Initiated Detach and requested PDN Disconnection Procedure in WLAN on PMIP S2a ..... | 126 | +| 8.2.9.2.6 | UE requested PDN Disconnection Procedures ..... | 126 | +| 8.2.9.2.6.1 | UE requested PDN Disconnection Procedure in WLAN on GTP S2a..... | 126 | +| 8.2.9.2.6.2 | UE requested PDN Disconnection Procedure in WLAN on GTP S2a on PMIP S2a ..... | 127 | +| 8.2.9.2.7 | Detach Procedures..... | 127 | +| 8.2.9.3 | Impacts on existing nodes or functionality ..... | 127 | +| 8.2.9.4 | Evaluation ..... | 128 | +| 8.2.10 | Solution 10 : WCS Solution ..... | 128 | +| 8.2.10.1 | Functional Description..... | 128 | +| 8.2.10.1.1 | Overview ..... | 128 | +| 8.2.10.1.2 | User plane..... | 128 | +| 8.2.10.1.3 | Control plane ..... | 128 | +| 8.2.10.1.3.1 | Alternative 1: Virtual MAC-based control protocol transport ..... | 129 | +| 8.2.10.1.3.2 | Alternative 2: VLAN-based control protocol transport..... | 129 | +| 8.2.10.1.3.3 | Alternative 3: L3-based control protocol transport ..... | 129 | +| 8.2.10.1.3.4 | p2p link ID negotiation in EAP-AKA' procedure..... | 129 | +| 8.2.10.1.4 | Protocol Stacks ..... | 131 | + +| | | | +|-----------------|---------------------------------------------------------------------------------------|------------| +| 8.2.10.2 | Procedures..... | 131 | +| 8.2.10.2.1 | Initial Attach procedure..... | 131 | +| 8.2.10.2.1.1 | Initial Attach in WLAN on S2a – network capability negotiation..... | 131 | +| 8.2.10.2.1.2 | Initial Attach continuation for GTP based S2a ..... | 132 | +| 8.2.10.2.1.2 | Initial Attach in WLAN on PMIP S2a ..... | 133 | +| 8.2.10.2.2 | UE-initiated Connectivity to Additional PDN ..... | 133 | +| 8.2.10.2.2.1 | UE-Initiated Connectivity to PDN in WLAN on GTP S2a..... | 133 | +| 8.2.10.2.2.2 | UE-Initiated Connectivity to PDN in WLAN on PMIP S2a..... | 134 | +| 8.2.10.2.3 | Handover procedure in multi-connection scenario from 3GPP access to WLAN on S2a ..... | 134 | +| 8.2.10.2.5 | Handover procedure from WLAN on S2a to 3GPP access..... | 136 | +| 8.2.10.2.6 | UE/TWAN RequestedPDN disconnection in WLAN on S2a ..... | 137 | +| 8.2.10.2.6.1 | UE/TWAN requested PDN disconnection in WLAN on GTP S2a ..... | 137 | +| 8.2.10.2.6.2 | UE TWAN request ed PDN disconnection in WLAN on PMIP S2a..... | 138 | +| 8.2.10.2.7 | UE initiated Detach in WLAN on S2a..... | 138 | +| 8.2.10.2.7.1 | UE initiated Detach in WLAN on GTP S2a..... | 138 | +| 8.2.10.2.7.2 | UE initiated Detach in WLAN on PMIP S2a..... | 139 | +| 8.2.10.2.8 | HSS/AAA Initiated Detach Procedure in WLAN ..... | 139 | +| 8.2.10.2.8.1 | HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a..... | 139 | +| 8.2.10.2.8.2 | HSS/AAA Initiated Detach Procedure in WLAN on on PMIP S2a..... | 140 | +| 8.2.10.2.9 | PDN GW initiated Resource Allocation Deactivation..... | 140 | +| 8.2.10.2.9.1 | PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a ..... | 140 | +| 8.2.10.2.9.2 | PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a..... | 140 | +| 8.2.10.3 | Impacts on existing nodes or functionality ..... | 140 | +| 8.2.10.4 | Evaluation ..... | 140 | +| 8.3 | Evaluation..... | 141 | +| 8.2.x | Solution x..... | 141 | +| 8.2.x.1 | Functional Description..... | 141 | +| 8.2.x.2 | Procedures..... | 142 | +| 8.2.x.3 | Impacts on existing nodes or functionality ..... | 142 | +| 8.2.x.4 | Evaluation ..... | 142 | +| 8.3 | Evaluation..... | 142 | +| 9 | Conclusion ..... | 142 | +| 9.1 | Conclusion on SaMOG Phase 1 ..... | 142 | +| 9.1.1 | Conclusion on attach trigger solution..... | 143 | +| 9.2 | Conclusion on SaMOG Phase 2 ..... | 143 | +| <b>Annex A:</b> | <b>Example of WLAN integrated with Femto.....</b> | <b>144</b> | +| <b>Annex B:</b> | <b>Change History.....</b> | <b>145</b> | + +--- + +## Foreword + +This Technical Report has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +This Study item is to study: + +1. The addition of a S2a based on GTP option. In particular this SID will develop the necessary stage 2 message flows to support S2a based on GTP and mobility between GTP-S5/S8 and GTP-S2a. +2. Supporting WLAN access to EPC through S2a via mechanisms: + - 2.1 with no impact to the UE; + - 2.2 with impact to the UE. + +Solutions requiring modifications to non 3GPP link-layers will not be considered. It is expected that the result of this Study Item may be used by 3GPP-BBF interworking activities (BBAI). + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 41.001: "GSM Release specifications". +- [3] 3GPP TS 23.402: "Architecture enhancements for Non-3GPP Accesses". +- [4] 3GPP TS 23.203: "Policy and charging control architecture". +- [5] IEEE Std 802.11-2007: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications". +- [6] 3GPP TS 23.401: "GPRS Enhancements for E-UTRAN Access". +- [7] 3GPP TS 29.273: "3GPP EPS AAA interfaces". +- [8] IETF RFC 791: "Internet Protocol". +- [9] IETF RFC 2131: "Dynamic Host Configuration Protocol". +- [10] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification". +- [11] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)". +- [12] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration". +- [13] IETF RFC 4436: "Detecting Network Attachment in IPv4 (DNAv4)". +- [14] IETF RFC 6059: "Simple Procedures for Detecting Network Attachment in IPv6". +- [15] IEEE Std 802.11n-2009: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. Enhancements for Higher Throughput (Amendment 5)". + +- [16] IETF RFC 6085: " Address Mapping of IPv6 Multicast Packets on Ethernet". +- [17] IETF RFC 5213: "Proxy Mobile IPv6". +- [18] IETF RFC 5844: "IPv4 Support for Proxy Mobile IPv6". +- [19] IETF RFC 3736: "Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6". +- [20] IEEE Std 802.1Q-2011: "IEEE Standard for Local and metropolitan area networks--Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks". +- [21] IEEE Std 802.11u-2011: " IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Amendment 9: Interworking with External Networks". +- [22] IETF RFC 4187: "Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)". +- [23] IETF RFC 3315: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". +- [24] IETF RFC 3203: "DHCP reconfigure extension". +- [25] IETF RFC 6085: “Address Mapping of IPv6 Multicast Packets on Ethernet”. +- [26] IEEE Std 802-2001: “IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture”. +- [27] IETF RFC 5448: "Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA')". +- [28] 3GPP TS 33 402: "Security aspects of non-3GPP accesses” +- [29] IETF RFC 6704: "Forcerenew Nonce 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]. + +<Definition: Explanation.> + +### 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [x] 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]. + +<ACRONYM> <Explanation> + +--- + +## 4 Scenarios + +The decision on whether a non 3GPP access is considered trusted or un trusted is made by the HPLMN operator and is not a characteristic of the non 3GPP access network. More details on it are provided in clause 4.3.1.2 of TS 23.402 [3]. The HPMN operator however while making a decision on trust worthiness of a non 3GPP access can also take into consideration security aspects of the access network. + +WLAN security was considered poor in both strength and ease of use, compared with that taken for granted in 3G networks and devices (UICC plus HSS, and GPRS encryption of data). Hence it made sense for the mobile network operators (MNOs) to use their core network to add overlay security layers, i.e. the IKEv2 for Authentication and Authorization of the UE, and the IPSec between the UE and ePDG for the security of the user data. + +Now, with the deployment of 802.1x, 802.11u, 802.11i and Hotspot 2.0, it may be considered by some operators that the security strength and ease of use (discovery and set up) is as acceptable as 3G/LTE security. For example, for the radio air link, the operator controlled hotspot with 802.11i could be treated as a secure Non-3GPP Access. As 802.11i (or WPA2 called by WFA) has been released for several years, many AP-s support it as a basic feature and lots of smart phones also have supported it. + +WLAN can also be deployed integrated in a residential/enterprise device (e.g. femto). In such a scenario, protection mechanism for the traffic on the backhaul link between the residential/enterprise device and the EPC may be used. This protection of the backhaul may be leveraged to consider the WLAN security in terms of connectivity to the EPC. + +The impact on the support of the following scenarios shall be used to evaluate the solutions that will be proposed in the study: + +- Access to EPC resources/services with access control by the operator; +- Seamless mobility between 3GPP and WLAN for EPS services with IP address preservation; +- Non-seamless mobility services between 3GPP and WLAN for EPS services: no IP address preservation; +- Support of UEs with single PDN connection; support of UEs with multiple PDN connections; +- Access to EPC via WLAN simultaneously with non-seamless WLAN offload. + +--- + +## 5 Architectural assumptions + +**Editor's note:** This clause will identify the architectural assumptions. + +### 5.1 Architectural assumptions for GTP based S2a + +From a UE perspective, using S2a-GTP or S2a-PMIP shall be transparent. + +The impacts to the existing functionalities and to the EPC shall be minimized. The protocol design on S2a should aim at keeping S2a GTP operations similar to those supported on GTP-based S5/S8 and GTP-based S2b as much as possible. + +All functions of the existing PMIP-S2a option should also be supported by GTP-S2a, except for optimized handover. + +### 5.2 Architectural assumptions for WLAN access to EPC through S2a + +In order to support the scenarios described in section 4, the following assumptions for WLAN access to EPC through S2a are taken and need to be investigated as part of the study: + +- The UE and the EPC are assumed to mutually authenticate through the WLAN Access as defined in TS 23.402 [3], clause 4.9.1. +- It is assumed that UE traffic over the WLAN air link may be confidentiality and integrity protected as defined by IEEE 802.11 [5]. +- It is assumed that there is a point-to-point link between UE and non-3GPP access GTP peer for the solutions with no impact to UE. + +The backhaul, through which WLAN accesses to EPC, may be secured, e.g. through IPSec, to build a secure access to the EPC. + +#### 5.2.1 Assumptions for solutions with no Impact to the UE + +The solutions that enable trusted WLAN access to EPC over S2a without any UE impact shall comply with the following architectural assumptions: + +- There shall be no functionality added to a R11 UE with respect to a R10 or pre-R10 UE specifically for the support of trusted WLAN access to EPC over S2a. +- No additional 3GPP mechanisms (other than those already specified), layer 2 protocol modifications or layer 3 protocol modifications shall be required on the UE to allow a UE capable of WLAN connectivity to a trusted WLAN network to gain WLAN access to EPC through S2a. +- There shall be no impact to the UE for the indication of the APN of the PDN to be established upon attach or upon handover of a PDN connection from a 3GPP access to trusted WLAN through S2a. The network shall be capable of selecting the APN to be used for the PDN establishment upon attach, independently of whether one or more PDN connections with such APNs are active over a 3GPP access. +- There shall be no impact to the UE for the support of IP address preservation in case of mobility between a 3GPP access and WLAN. +- There shall be no impact to the UE for the establishment of more than one PDN connections over WLAN when attaching to WLAN access or when handing over PDN connections from a 3GPP access. +- There shall be no impact to the UE for the simultaneous support of IP connectivity to the EPC over WLAN and with non-seamless WLAN offload. +- SaMOG solution should co-exist with Release 11 and earlier UEs which may implement WLAN interworking related features including ANDSF and its extensions, SWu, S2c. +- Since an unmodified UE may support the Detecting Network Attachment (DNA) functions, solutions claiming no impacts to the UE shall work in presence of the following protocols: + - For IPv4: IETF RFC 4436 [13] + - For IPv6: IETF RFC 6059 [14] + +The above list is non-exhaustive. + +Only the following functions can be considered supported by an unmodified UE, i.e. solutions with no impacts to UE shall only expect the following functions in the UE: + +- WLAN spec only restricted to PHY/MAC aspects in IEEE 802.11 [5] and IEEE 802.11n [15] +- 3GPP-based authentication as defined in TS 23.402 [3] over WLAN (i.e. access authentication towards EPC) +- IPv4 and/or IPv6 support: + - For IPv4: IETF RFC791 [8], IETF RFC 2131 [9] + - For IPv6: IETF RFC 2460 [10], IETF RFC 4861 [11], and IETF RFC 4862 [12] + +--- + +## 6 Solutions for GTP based S2a + +**Editor's note:** This clause will describe the solution(s) for the "access agnostic" GTP-S2a, which is basically similar to PMIPv6-S2a in TS 23.402 [3]. For WLAN Access, the additional considerations including the potential UE impacts are studied in clause 7. + +### 6.1 Solution 1 + +#### 6.1.1 Architecture + +The same architecture reference models as those defined in TS 23.402 [3] can be applied to GTP based S2a, with the following differences: + +- BBERF is not required with GTP based S2a; +- Gxa interface is not required between the PCRF (or vPCRF) and the Trusted Non-3GPP Access; +- vPCRF (and S9 interface) is not required for roaming with Home Routed traffic (i.e. non-LBO traffic). + +NOTE 1: The Chained case is not proposed to be supported in this release. Figures 6.1.1-1 to 6.1.1-3 show the baseline architecture reference model for GTP based S2a in the non roaming and roaming cases. + +![Figure 6.1.1-1: Non-Roaming Architecture within EPS using GTP based S5, S2a](cab0834804fb031b43865554cc8d06ab_img.jpg) + +This diagram illustrates the non-roaming architecture within an EPS. It features a 3GPP Access unit connected to a Serving Gateway, which is linked to a PDN Gateway via an S5 interface. The PDN Gateway connects to Operator's IP Services (e.g., IMS, PSS, etc.) through an SGi interface. A PCRF is connected to the PDN Gateway via a Gx interface and to the Operator's IP Services via an Rx interface. The HSS is connected to the Serving Gateway via an S6a interface and to the PDN Gateway via an S2a interface. A 3GPP AAA Server is connected to the PDN Gateway via an S6b interface and to the Operator's IP Services via an SWx interface. A Trusted Non-3GPP IP Access unit is connected to the PDN Gateway via an S2a interface and to the 3GPP AAA Server via an STa interface. The architecture is divided into two sections by a dashed red line: the top section is labeled HPLMN and the bottom section is labeled Non-3GPP Networks. + +Figure 6.1.1-1: Non-Roaming Architecture within EPS using GTP based S5, S2a + +Figure 6.1.1-1: Non-Roaming Architecture within EPS using GTP based S5, S2a + +![Figure 6.1.1-2: Roaming Architecture for EPS using GTP based S8, S2a - Home Routed](ddc7460821484f1ae2835c67955c554c_img.jpg) + +This diagram illustrates the roaming architecture for EPS using GTP based S8, S2a - Home Routed. It shows a 3GPP Access unit connected to a Serving Gateway, which is connected to a PDN Gateway via an S8 interface. The PDN Gateway is connected to the HSS via an S6a interface and to the PDN Gateway via an S2a interface. The PDN Gateway connects to Operator's IP Services (e.g., IMS, PSS, etc.) through an SGi interface. A hPCRF is connected to the PDN Gateway via a Gx interface and to the Operator's IP Services via an Rx interface. The HSS is connected to the PDN Gateway via an S2a interface. A 3GPP AAA Server is connected to the PDN Gateway via an S6b interface and to the Operator's IP Services via an SWx interface. A 3GPP AAA Proxy is connected to the 3GPP AAA Server via an SWd interface and to the PDN Gateway via an STa interface. A Trusted Non-3GPP IP Access unit is connected to the PDN Gateway via an S2a interface and to the 3GPP AAA Proxy via an STa interface. The architecture is divided into three sections by dashed red lines: the top section is labeled HPLMN, the middle section is labeled VPLMN, and the bottom section is labeled Non-3GPP Networks. + +Figure 6.1.1-2: Roaming Architecture for EPS using GTP based S8, S2a - Home Routed + +Figure 6.1.1-2: Roaming Architecture for EPS using GTP based S8, S2a - Home Routed + +![Figure 6.1.1-3: Roaming Architecture for EPS using GTP based S5, S2a – Local Breakout. The diagram shows a roaming architecture across three network domains: HPLMN (Home PLMN), VPLMN (Visited PLMN), and Non-3GPP Networks. In the HPLMN, the HSS is connected to the 3GPP AAA Server via SWx and to the Serving Gateway via S6a. The hPCRF is connected to the HSS via Rx and to the vPCRF via S9. The Operator's IP Services (e.g., IMS, PSS etc.) are connected to the hPCRF via Rx. In the VPLMN, the 3GPP Access (Serving Gateway) is connected to the PDN Gateway via S5. The vPCRF is connected to the PDN Gateway via Gx and to the Visited network IP services or proxies to home network services or PDN via Rx. The 3GPP AAA Proxy is connected to the PDN Gateway via S6b and to the 3GPP AAA Server via SWd. In the Non-3GPP Networks, the Trusted Non-3GPP IP Access is connected to the PDN Gateway via S2a and to the 3GPP AAA Proxy via STa. The PDN Gateway is also connected to the Visited network IP services or proxies to home network services or PDN via SGi.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Figure 6.1.1-3: Roaming Architecture for EPS using GTP based S5, S2a – Local Breakout. The diagram shows a roaming architecture across three network domains: HPLMN (Home PLMN), VPLMN (Visited PLMN), and Non-3GPP Networks. In the HPLMN, the HSS is connected to the 3GPP AAA Server via SWx and to the Serving Gateway via S6a. The hPCRF is connected to the HSS via Rx and to the vPCRF via S9. The Operator's IP Services (e.g., IMS, PSS etc.) are connected to the hPCRF via Rx. In the VPLMN, the 3GPP Access (Serving Gateway) is connected to the PDN Gateway via S5. The vPCRF is connected to the PDN Gateway via Gx and to the Visited network IP services or proxies to home network services or PDN via Rx. The 3GPP AAA Proxy is connected to the PDN Gateway via S6b and to the 3GPP AAA Server via SWd. In the Non-3GPP Networks, the Trusted Non-3GPP IP Access is connected to the PDN Gateway via S2a and to the 3GPP AAA Proxy via STa. The PDN Gateway is also connected to the Visited network IP services or proxies to home network services or PDN via SGi. + +**Figure 6.1.1-3: Roaming Architecture for EPS using GTP based S5, S2a – Local Breakout** + +NOTE 2: A GTP peer is assumed in the Trusted Non-3GPP IP Access for this GTP based S2a. Moreover it is assumed that the GTP peer acts as first hop router in a similar way as the MAG when PMIP is used over S2a. When deferred IPv4 address allocation is supported, it is assumed that the GTP peer supports DHCPv4 relay functionality. + +## 6.1.2 Functional description + +Editor's note: This clause will contain the functional description for S2a mobility based on GTP. + +### 6.1.2.1 Bearer model for a PDN connection + +![Figure 6.1.2.1-1: Bearer model on GTP based S2a. The diagram shows a UE connected to a Trusted Non-3GPP IP Access via Non-3GPP connectivity. The Trusted Non-3GPP IP Access is connected to a PGW via S2a. The connection between the Trusted Non-3GPP IP Access and the PGW is shown as three parallel GTP Tunnels. The Trusted Non-3GPP IP Access contains a UL TFT (Upstream Traffic Flow Template) and the PGW contains a DL TFT (Downstream Traffic Flow Template). A callout box indicates that the mapping between Non-3GPP connectivity and multiple GTP bearers (Default and dedicated bearers) is out of 3GPP scope.](c036e2540a94b31357ceb0002f0cacab_img.jpg) + +Figure 6.1.2.1-1: Bearer model on GTP based S2a. The diagram shows a UE connected to a Trusted Non-3GPP IP Access via Non-3GPP connectivity. The Trusted Non-3GPP IP Access is connected to a PGW via S2a. The connection between the Trusted Non-3GPP IP Access and the PGW is shown as three parallel GTP Tunnels. The Trusted Non-3GPP IP Access contains a UL TFT (Upstream Traffic Flow Template) and the PGW contains a DL TFT (Downstream Traffic Flow Template). A callout box indicates that the mapping between Non-3GPP connectivity and multiple GTP bearers (Default and dedicated bearers) is out of 3GPP scope. + +**Figure 6.1.2.1-1: Bearer model on GTP based S2a** + +NOTE: The mapping between Non-3GPP connectivity and multiple GTP bearers in the Trusted Non-3GPP IP Access is out of 3GPP scope. + +For Trusted non-3GPP access to the EPC, the PDN connectivity is made up of the concatenation of Non-3GPP connectivity (between the UE and the Trusted Non-3GPP access) and of GTP bearer(s) over S2a. + +The GTP based S2a interface is similar to GTP-S5/S8 and GTP-S2b. The Trusted Non 3GPP access handles the UL TFT received from the PGW over GTP with the same way as an ePDG terminating GTP based S2b handles the UL TFT received from the PGW. + +Whether GTP or PMIP is used in the network for S2a is transparent to the UE. + +### 6.1.3 Information flows + +#### 6.1.3.1 Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW + +NOTE 1: The exact list of parameters signalled in GTP S2a information flows will be defined during normative work. + +![Sequence diagram of the Initial Attach Procedure with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes the PDN GW, vPCRF, AAA Proxy, and hPCRF. The procedure includes steps: 1. Non-3GPP Specific Procedures, 2. EAP Authentication, 3. L3 Attach Trigger, 5. Create Session Request, 6. IP-CAN Session Establishment Procedure, 7. Update PDN GW Address, 8. Create Session Response, 9. GTP Tunnel, and 11. L3 Attach Completion.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TrustedNon3GPP as Trusted Non-3GPP IP Access + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note left of UE: 1. Non-3GPP Specific Procedures + UE->>TrustedNon3GPP: 2. EAP Authentication + TrustedNon3GPP->>HSS_AAA: 2. Authentication & Authorization + Note left of UE: 3. L3 Attach Trigger + TrustedNon3GPP->>PDN_GW: 5. Create Session Request + Note right of PDN_GW: 6. IP-CAN Session Establishment Procedure + PDN_GW->>HSS_AAA: 7. Update PDN GW Address + HSS_AAA->>PDN_GW: 8. Create Session Response + PDN_GW->>TrustedNon3GPP: 9. GTP Tunnel + Note left of UE: 11. L3 Attach Completion + +``` + +Sequence diagram of the Initial Attach Procedure with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes the PDN GW, vPCRF, AAA Proxy, and hPCRF. The procedure includes steps: 1. Non-3GPP Specific Procedures, 2. EAP Authentication, 3. L3 Attach Trigger, 5. Create Session Request, 6. IP-CAN Session Establishment Procedure, 7. Update PDN GW Address, 8. Create Session Response, 9. GTP Tunnel, and 11. L3 Attach Completion. + +**Figure 6.1.3.1-1: Initial attachment with Network-based MM mechanism over S2a for roaming, LBO and non-roaming scenarios** + +Principles are similar to those specified for the PMIPv6 S2a call flow in clause 6.2.1 of TS 23.402 [3], but with GTP signalling and following differences: + +The home routed roaming, LBO and non-roaming scenarios are depicted in the figure 6.1.3.1-1. + +- In the LBO case, the 3GPP AAA Proxy acts as an intermediary, forwarding messages from the 3GPP AAA Server in the HPLMN to the PDN GW in the VPLMN and vice versa. Messages between the PDN GW in the VPLMN and the hPCRF in the HPLMN are forwarded by the vPCRF in the VPLMN. + - In the home routed roaming and non-roaming cases, the vPCRF and the 3GPP AAA Proxy are not involved, except for the authentication and authorization in step 2. +- 1) as for step 1 of clause 6.2.1 of TS 23.402 [3]. + - 2) as for step 2 of clause 6.2.1 of TS 23.402 [3], with the following additions: + +- Upon successful authorization, the 3GPP AAA server downloads authorization (subscription) data to the Trusted non-3GPP Access. This information is used at step 5. +- The Trusted non 3GPP IP Access selects the S2a protocol variant (GTP vs PMIP). The Trusted non 3GPP IP Access may be configured with the S2a protocol variant(s) on a per HPLMN granularity, or may retrieve information regarding the S2a protocol variants supported by the PDN GW (PMIP or/and GTP) from the Domain Name Service function. +- The Trusted non-3GPP IP Access selects the PGW as per the existing PGW selection procedure; if the Trusted non-3GPP IP Access receives a PGW Identity under the form of a FQDN, it shall derive it to an IP address according to the selected mobility management protocol (here GTP). + +NOTE 2: As per existing principles, to support separate PDN GW addresses at a PDN GW for different mobility protocols (e.g. PMIP, MIPv4 or GTPv2), the PDN GW Selection function takes mobility protocol type into account when deriving PDN GW address by using the Domain Name Service function. + +3) as for step 3 of clause 6.2.1 of TS 23.402 [3]. + +NOTE 3: Only when IPv4, the L3 trigger may be relayed to the PDN GW after the GTP tunnel has been setup in step 9 using deferred IPv4 address mechanism. + +4) step 4 of clause 6.2.1 of TS 23.402 [3] is skipped. + +5) The Trusted non-3GPP IP Access sends a Create Session Request (IMSI, APN, RAT type, Trusted non-3GPP IP Access TEID of the control plane, PDN Type, PDN Address, EPS Bearer Identity, Default EPS Bearer QoS, Trusted non-3GPP IP Access Address for the user plane, Trusted non-3GPP IP Access TEID of the user plane, APN-AMBR, Selection Mode, Dual Address Bearer Flag, Trace Information, Charging Characteristics, Protocol Configuration Options) message to the PGW. The RAT type indicates the non-3GPP IP access technology type. The PDN Type shall be set based on the requested IP address types and subscription profile in the same way as the PDN type is selected during the E-UTRAN Initial Attach in TS 23.401 [6]. The Trusted non-3GPP IP Access Network shall set the Dual Address Bearer Flag when the PDN type is set to IPv4v6 and all SGSNs which the UE may be handed over to are Release 8 or above supporting dual addressing, which is determined based on node pre-configuration by the operator. The Trusted non-3GPP IP Access Network shall include Trace Information if PDN GW trace is activated. + +The PGW creates a new entry in its bearer context table and generates a Charging Id. The new entry allows the PGW to route user plane PDUs between the Trusted non-3GPP IP Access Network and the packet data network and to start charging. + +NOTE 4: The EPS Bearer Identity and Default EPS Bearer QoS parameters convey the S2a bearer identity and the default S2a bearer QoS. + +NOTE 5: As part of the access specific study it will be clarified whether step 5 (Create Session Request) is triggered by the completion of the authentication procedure (step 2) either/or by the reception of the L3 Attach trigger (step 3). + +6) as for step 6 of clause 6.2.1 of TS 23.402 [3] except that there is no associated Gateway Control Sessions. + +7) as for step 7 of clause 6.2.1 of TS 23.402 [3], with the following addition: + +- when informing the 3GPP AAA Server of the PDN GW identity, the selected PDN GW also indicates the selected S2a protocol variant (here GTP); this allows the option for the 3GPP AAA Server or 3GPP AAA Proxy not to return to the PDN GW PMIP specific parameters (e.g. static QoS Profile, Trace Information, APN-AMBR) if GTP is used over S2a; the PDN GW shall ignore those parameters if received from the 3GPP AAA Server or 3GPP AAA Proxy. + +8) The PDN GW returns a Create Session Response (PDN GW Address for the user plane, PDN GW TEID of the user plane, PDN GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, Protocol Configuration Options, Cause) message to the Trusted non-3GPP IP Access, including the IP address(es) allocated for the UE. + +NOTE 6: If the L3 attach trigger is relayed to the PDN GW, the IP address will not be returned in the Create Session Response. + +The PGW may initiate the creation of dedicated bearers on GTP based S2a (like it may do it on GTP based S5/S8 for an Attach on 3GPP access). + +9) The GTP tunnel is set up between the Trusted Non-3GPP IP Access and the PDN GW. + +NOTE 7: If the L3 Attach trigger is relayed to the PDN GW, the DHCP request is sent to the PDN GW in the established GTP tunnel. + +10) step 10 of clause 6.2.1 of TS 23.402 [3] is skipped. + +11) as for step 11 of clause 6.2.1 of TS 23.402 [3]. + +### 6.1.3.2 Detach and PDN Disconnection with GTP on S2a + +#### 6.1.3.2.1 UE/Trusted Non-3GPP IP Access Network Initiated Detach and UE/Trusted Non-3GPP IP Access requested PDN Disconnection Procedure with GTP on S2a + +![Sequence diagram showing the Detach and PDN Disconnection procedure with GTP on S2a. The entities involved are UE, Trusted Non-3GPP IP Access, PDN GW, AAA Proxy, hPCRF, and HSS/AAA. A shaded box labeled 'Roaming Scenarios' encompasses the AAA Proxy, hPCRF, and HSS/AAA. The steps are: 1. Access technology specific detach trigger (UE to Trusted Non-3GPP IP Access); 3. Delete Session Request (Trusted Non-3GPP IP Access to PDN GW); 4. Update PDN GW Address (PDN GW to AAA Proxy, then to HSS/AAA); 5. PCEF-Initiated IP-CAN Session Termination Procedure (interaction between AAA Proxy and hPCRF); 6. Delete Session Response (PDN GW to Trusted Non-3GPP IP Access); 7. Non-3GPP specific resource release procedure (between UE and Trusted Non-3GPP IP Access).](90ee16ccc0ad16aeca48087797d7b07f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TN3GPP as Trusted Non-3GPP IP Access + participant PGW as PDN GW + box Roaming Scenarios + participant AAA as AAA Proxy + participant hPCRF + participant HSS as HSS/AAA + end + + Note over UE, TN3GPP: 1. Access technology specific detach trigger + TN3GPP->>PGW: 3. Delete Session Request + PGW->>AAA: 4. Update PDN GW Address + AAA->>HSS: + Note over AAA, hPCRF: 5. PCEF-Initiated IP-CAN Session Termination Procedure + PGW->>TN3GPP: 6. Delete Session Response + Note over UE, TN3GPP: 7. Non-3GPP specific resource release procedure + +``` + +Sequence diagram showing the Detach and PDN Disconnection procedure with GTP on S2a. The entities involved are UE, Trusted Non-3GPP IP Access, PDN GW, AAA Proxy, hPCRF, and HSS/AAA. A shaded box labeled 'Roaming Scenarios' encompasses the AAA Proxy, hPCRF, and HSS/AAA. The steps are: 1. Access technology specific detach trigger (UE to Trusted Non-3GPP IP Access); 3. Delete Session Request (Trusted Non-3GPP IP Access to PDN GW); 4. Update PDN GW Address (PDN GW to AAA Proxy, then to HSS/AAA); 5. PCEF-Initiated IP-CAN Session Termination Procedure (interaction between AAA Proxy and hPCRF); 6. Delete Session Response (PDN GW to Trusted Non-3GPP IP Access); 7. Non-3GPP specific resource release procedure (between UE and Trusted Non-3GPP IP Access). + +**Figure 6.1.3.2.1-1: UE/Trusted Non-3GPP Access Network initiated detach procedure or PDN-disconnection with GTP on S2a** + +Principles are similar to those specified for the PMIP S2a call flow in clause 6.4.1.1 of TS 23.402 [3], but with GTP signalling: + +1) as for step 1 of clause 6.4.1.1 of TS 23.402 [3]. + +2) step 2 of clause 6.4.1.1 of TS 23.402 [3] is skipped. + +3) The active Bearer(s) Trusted non-3GPP IP Access regarding this particular UE and PDN connection are deactivated by the Trusted non-3GPP IP Access sending a Delete Session Request (Linked EPS Bearer ID) to the PGW for the related PDN connection. + +4 to 5) as for steps 4 to 5 of clause 6.4.1.1 of TS 23.402 [3]. + +6) The PDN GW acknowledges with Delete Session Response (Cause). + +7) as for step 7 of clause 6.4.1.1 of TS 23.402 [3]. + +#### 6.1.3.2.2 HSS/AAA Initiated Detach Procedure with GTP on S2a + +![Sequence diagram for HSS/AAA-initiated detach procedure with GTP on S2a. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access, PDN GW, AAA Proxv, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' covers the PDN GW, AAA Proxv, and hPCRF. Step 1: UE De-registration Request is sent from HSS/AAA to Trusted Non-3GPP IP Access. Step 2: A block labeled 'The procedures as figure 6.1.3.2.1-1, after Step 1' is shown. Step 3: UE De-Registration Ack is sent from AAA Proxv to HSS/AAA.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TNA as Trusted Non-3GPP IP Access + participant PDN_GW as PDN GW + participant AAA_Proxv as AAA Proxv + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW: Roaming Scenarios + Note right of PDN_GW: [ ] + Note right of hPCRF: [ ] + + HSS/AAA->>TNA: 1. UE De-registration Request + Note over TNA, PDN_GW, AAA_Proxv, hPCRF: 2. The procedures as figure 6.1.3.2.1-1, after Step 1 + AAA_Proxv->>HSS/AAA: 3. UE De-Registration Ack + +``` + +Sequence diagram for HSS/AAA-initiated detach procedure with GTP on S2a. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access, PDN GW, AAA Proxv, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' covers the PDN GW, AAA Proxv, and hPCRF. Step 1: UE De-registration Request is sent from HSS/AAA to Trusted Non-3GPP IP Access. Step 2: A block labeled 'The procedures as figure 6.1.3.2.1-1, after Step 1' is shown. Step 3: UE De-Registration Ack is sent from AAA Proxv to HSS/AAA. + +**Figure 6.1.3.2.2-1: HSS/AAA-initiated detach procedure with GTP on S2a** + +Principles are similar to those specified for the PMIP S2a call flow in clause 6.4.2.1 of TS 23.402 [3], but with GTP signalling: + +- 1) as for step 1 of clause 6.4.2.1 of TS 23.402 [3]. +- 2) This includes the procedures after step 1 as for Figure 6.1.3.2.1-1. + +For multiple PDN connectivity, this step shall be repeated for each PDN connected. + +- 3) as for step 3 of clause 6.4.2.1 of TS 23.402 [3]. + +**NOTE:** The HSS/AAA may also send a detach indication message to the PDN GW. The PDN GW does not remove the GTP tunnels on S2a, since the Trusted non-3GPP IP Access is responsible for removing those tunnels on S2a. The PDN GW acknowledges the receipt of the detach indication message to the HSS/AAA. + +#### 6.1.3.3 UE-initiated Connectivity to Additional PDN with GTP on S2a + +Establishment of connectivity to an additional PDN over Trusted Non-3GPP IP Access with S2a is supported only for the accesses that support such feature and the UEs that have such capability. + +During the establishment of a new PDN connection, the Trusted Non-3GPP IP Access allocates and sends a default EPS bearer ID to the PDN GW. The default EPS bearer ID is unique in the scope of the UE within an Trusted Non-3GPP IP Access, i.e. the IMSI and the default EPS bearer ID together identify a PDN connection within an Trusted Non-3GPP IP Access. In order to be able to identify a specific established PDN connection, both the Trusted Non-3GPP IP Access and the PDN GW shall store the default EPS bearer ID. + +For network supporting multiple mobility protocols, the AAA/HSS enforces the same IPMS decision for each additional PDN connection as for initial attach. + +![Sequence diagram illustrating Additional PDN connectivity with GTP on S2a for non-roaming and roaming scenarios. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access (MAG), PDN GW, PDN GW 2, vPCRF, AAA Proxv, hPCRF, and HSS/AAA. The process involves triggering new PDN connectivity, performing steps 5-9 of initial attach, replying with new PDN connectivity information, and establishing a new GTP tunnel.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The diagram is a sequence diagram with the following lifelines: UE, Trusted Non-3GPP IP Access (MAG), PDN GW, PDN GW 2, vPCRF, AAA Proxv, hPCRF, and HSS/AAA. A shaded box labeled 'Roaming Scenarios' covers the vPCRF, AAA Proxv, and hPCRF lifelines. The sequence of messages is as follows: + +- The UE sends a message '1. Trigger new PDN Connectivity' to the Trusted Non-3GPP IP Access (MAG). +- The Trusted Non-3GPP IP Access (MAG) initiates '2. Steps 5-9 of Initial Attach' with the PDN GW. +- The Trusted Non-3GPP IP Access (MAG) sends a message '3. Reply(new PDN connectivity information)' to the UE. +- A new GTP tunnel is established between the Trusted Non-3GPP IP Access (MAG) and the PDN GW 2, labeled '4. New GTP Tunnel'. + +Existing GTP tunnels are shown between the UE and the PDN GW. + +Sequence diagram illustrating Additional PDN connectivity with GTP on S2a for non-roaming and roaming scenarios. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access (MAG), PDN GW, PDN GW 2, vPCRF, AAA Proxv, hPCRF, and HSS/AAA. The process involves triggering new PDN connectivity, performing steps 5-9 of initial attach, replying with new PDN connectivity information, and establishing a new GTP tunnel. + +**Figure 6.1.3.3-1: Additional PDN connectivity with GTP on S2a for non-roaming and roaming** + +The steps in the procedure which are marked as optional occur only if dynamic policy provisioning has been deployed. + +The home routed roaming, LBO and non-roaming scenarios are depicted in the figure 6.1.3.3-1. + +- In the LBO case, the 3GPP AAA Proxy acts as an intermediary, forwarding messages from the 3GPP AAA Server in the HPLMN to the PDN GW in the VPLMN and vice versa. Messages between the PDN GW in the VPLMN and the hPCRF in the HPLMN are forwarded by the vPCRF in the VPLMN. + - In the home routed roaming and non-roaming cases, the vPCRF and the 3GPP AAA Proxy are not involved. +- 1) When the UE wishes to connect to an additional PDN, it sends a trigger indicating that connectivity with that specific PDN is desired. The UE provides information about the new PDN by using an APN. When multiple PDN connections to a single APN are supported then some additional access specific mechanism is needed between the UE and the Trusted Non-3GPP IP Access to differentiate the PDN connections towards the same APN. If supported by the non-3GPP access, the UE may send Protocol Configuration Options in this step using access specific mechanisms. The Protocol Configuration Options provided by the UE may include the user credentials for PDN access authorization. The UE triggers the re-establishment of existing PDN connectivity after the handover by providing a Request Type indicating "Handover" on accesses that support the indication. + +NOTE 1: The definition of the trigger that the UE provides to the access network is out of scope of 3GPP. + +- 2) At this step the Trusted non-3GPP IP Access performs PDN GW selection as described in Steps 5 to 9 of Initial Attach procedure, while PDN GW2 is selected. +- 3) The Trusted non-3GPP IP Access sends the reply message to the UE with the allocated IP address from the PDN that the UE indicated at step 1. If supported by the non-3GPP access, the Protocol Configuration Options provided by the PDN GW2 in step 2 are returned to the UE in this step using access specific mechanisms. Since UE requested for additional PDN connectivity, the UE configures the IP address received from the Trusted Non-3GPP IP Access without deleting its configuration for connectivity with any other previously established PDN. + +NOTE 2: The definition of the message used to carry the new connectivity information to the UE is out of scope of 3GPP. + +- 4) The GTP tunnel is thus set up between the Trusted Non-3GPP IP Access and the PDN GW corresponding to the requested additional PDN while maintaining tunnels previously established for other PDNs. + +#### 6.1.3.4 Dedicated bearer activation with GTP on S2a + +The dedicated bearer activation procedure for GTP based S2a is depicted in figure 6.1.3.4-1. + +![Sequence diagram of the Dedicated S2a Bearer Activation Procedure with GTP on S2a. The diagram shows interactions between UE, Trusted non-3GPP access, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxv, vPCRF, and hPCRF. The sequence is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Create Bearer Request (PDN GW to Trusted non-3GPP access), 3. Trusted non-3GPP access specific mechanism for resource allocation or modification (dashed box), 4. Create Bearer Response (Trusted non-3GPP access to PDN GW), 5. IP-CAN Session Modification (PDN GW to vPCRF).](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TNA as Trusted non-3GPP access + participant PDN_GW as PDN GW + participant AAA_Proxv as AAA Proxv + participant vPCRF + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of AAA_Proxv: Roaming Scenarios + PDN_GW->>vPCRF: 1. IP-CAN Session Modification + PDN_GW->>TNA: 2. Create Bearer Request + Note left of TNA: 3. Trusted non-3GPP access specific mechanism for resource allocation or modification + TNA->>PDN_GW: 4. Create Bearer Response + PDN_GW->>vPCRF: 5. IP-CAN Session Modification + +``` + +Sequence diagram of the Dedicated S2a Bearer Activation Procedure with GTP on S2a. The diagram shows interactions between UE, Trusted non-3GPP access, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxv, vPCRF, and hPCRF. The sequence is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Create Bearer Request (PDN GW to Trusted non-3GPP access), 3. Trusted non-3GPP access specific mechanism for resource allocation or modification (dashed box), 4. Create Bearer Response (Trusted non-3GPP access to PDN GW), 5. IP-CAN Session Modification (PDN GW to vPCRF). + +**Figure 6.1.3.4-1: Dedicated S2a Bearer Activation Procedure with GTP on S2a** + +1. If dynamic PCC is deployed, the PCRF sends a PCC decision provision (QoS policy) message to the PDN GW. This corresponds to the initial steps of the PCRF-Initiated IP CAN Session Modification procedure or to the PCRF response in the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203 [4], up to the point that the PDN GW requests IP CAN Bearer Signalling. If dynamic PCC is not deployed, the PDN GW may apply local QoS policy. +2. The PDN GW uses this QoS policy to assign the S2a bearer QoS, i.e., it assigns the values to the bearer level QoS parameters QCI, ARP, GBR and MBR. The PDN GW sends a Create Bearer Request message (IMSI, EPS bearer QoS, TFT, PDN GW Address for the user plane, PDN GW TEID of the user plane, Charging Id, LBI) to the trusted non-3GPP access. The Linked EPS bearer Identity (LBI) is the EPS bearer Identity of the default S2a bearer. +3. If supported by the trusted non-3GPP access, a trusted non-3GPP access specific resource allocation/modification procedure may be executed in this step. The details of this step are out of the scope of 3GPP. +4. The trusted non-3GPP access selects an EPS bearer Identity, which has not yet been assigned to the UE. The trusted non-3GPP access then stores the EPS bearer Identity and links the dedicated S2a bearer to the default S2a bearer indicated by the Linked Bearer Identity (LBI). The trusted non-3GPP access uses the uplink packet filter (UL TFT) to determine the mapping of uplink traffic flows to the S2a bearer. The trusted non-3GPP access then acknowledges the S2a bearer activation to the PDN GW by sending a Create Bearer Response (EPS bearer Identity, trusted non-3GPP access Address for the user plane, trusted non-3GPP access TEID of the user plane) message. + +- If the dedicated bearer activation procedure was triggered by a PCC Decision Provision message from the PCRF, the PDN GW indicates to the PCRF whether the requested PCC decision (QoS policy) could be enforced or not, allowing the completion of the PCRF-Initiated IP CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203 [4], after the completion of IP CAN bearer signalling. + +NOTE 1: The exact signalling of step 1 and 5 (e.g. for local break-out) is outside the scope of this TR. This signalling and its interaction with the dedicated bearer activation procedure are to be specified in TS 23.203 [4]. Steps 1 and 5 are included here only for completeness. + +### 6.1.3.5 Network-initiated S2a bearer modification with GTP on S2a + +#### 6.1.3.5.1 PDN GW Initiated Bearer Modification + +The PDN GW initiated bearer modification procedure for a GTP based S2a is depicted in figure 6.1.3.5.1-1. This procedure is used to update the TFT for an active default or dedicated S2a bearer, or in cases when one or several of the S2a bearer QoS parameters QCI, GBR, MBR or ARP are modified (including the QCI or the ARP of the default S2a bearer e.g. due to the HSS Initiated Subscribed QoS Modification procedure, as described in clause 6.1.3.5.2). + +![Sequence diagram of PDN GW-initiated S2a Bearer Modification Procedure with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP access, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxy, vPCRF, and hPCRF. The sequence is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Update Bearer Request (PDN GW to Trusted Non-3GPP IP access), 3. Access specific mechanism to enforce the policy (Trusted Non-3GPP IP access to UE), 4. Update Bearer Response (Trusted Non-3GPP IP access to PDN GW), 5. IP-CAN Session Modification (PDN GW to vPCRF).](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TrustedNon3GPP as Trusted Non-3GPP IP access + participant PDN_GW as PDN GW + participant AAA_Proxy as AAA Proxy + participant vPCRF + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of AAA_Proxy: Roaming Scenarios + PDN_GW->>vPCRF: 1. IP-CAN Session Modification + PDN_GW->>TrustedNon3GPP: 2. Update Bearer Request + Note left of TrustedNon3GPP: 3. Access specific mechanism to enforce the policy + TrustedNon3GPP->>PDN_GW: 4. Update Bearer Response + PDN_GW->>vPCRF: 5. IP-CAN Session Modification + +``` + +Sequence diagram of PDN GW-initiated S2a Bearer Modification Procedure with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP access, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains AAA Proxy, vPCRF, and hPCRF. The sequence is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Update Bearer Request (PDN GW to Trusted Non-3GPP IP access), 3. Access specific mechanism to enforce the policy (Trusted Non-3GPP IP access to UE), 4. Update Bearer Response (Trusted Non-3GPP IP access to PDN GW), 5. IP-CAN Session Modification (PDN GW to vPCRF). + +**Figure 6.1.3.5.1-1: PDN GW-initiated S2a Bearer Modification Procedure with GTP on S2a** + +- If dynamic PCC is deployed, the PCRF sends a PCC decision provision (QoS policy) message to the PDN GW. This corresponds to the initial steps of the PCRF-Initiated IP CAN Session Modification procedure or to the PCRF response in the PCEF initiated IP-CAN Session Modification procedure as defined in 3GPP TS 23.203 [4], up to the point that the PDN GW requests IP-CAN Bearer Signalling. If dynamic PCC is not deployed, the PDN GW may apply local QoS policy. +- The PDN GW uses this QoS policy to determine that a service data flow shall be aggregated to or removed from an active S2a bearer or that the authorized QoS of a service data flow has changed. The PDN GW generates the TFT and updates the S2a bearer QoS to match the traffic flow aggregate. The PDN GW then sends the Update Bearer Request (EPS bearer Identity, EPS bearer QoS, TFT) message to the trusted non-3GPP IP access. +- If supported by the trusted non-3GPP access, an IP-CAN specific resource allocation or resource release procedure may be triggered by the enforcement of the received policy rules. The details of this step are out of the scope of 3GPP. +- The trusted non-3GPP IP access uses the uplink packet filter (UL TFT) to determine the mapping of traffic flows to the S2a bearer and acknowledges the S2a bearer modification to the PGW by sending an Update Bearer Response (EPS bearer Identity) message. +- If the Bearer modification procedure was triggered by a PCC Decision Provision message from the PCRF, the PDN GW indicates to the PCRF whether the requested PCC decision (QoS policy) could be enforced or not by + +sending a Provision Ack message allowing the completion of the PCRF-Initiated IP CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203 [4], after the completion of IP CAN bearer signalling. + +NOTE: The exact signalling of step 1 and 5 (e.g. for local break-out) is outside the scope of this TR. This signalling and its interaction with the bearer activation procedure are to be specified in TS 23.203 [4]. Step 1 and 5 are included here only for completeness. + +#### 6.1.3.5.2 HSS Initiated Subscribed QoS Modification + +The HSS Initiated Subscribed QoS Modification for a GTP-based S2a is depicted in figure 6.1.3.5.2-1. + +![Sequence diagram for HSS Initiated Subscribed QoS Modification. The diagram shows the interaction between UE, Trusted non-3GPP IP access, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. The process starts with the HSS/AAA sending an '1. HSS-initiated User Profile Update procedure as in TS 23.402' to the PDN GW. The PDN GW then sends a '2. Modify Bearer Command' to the Trusted non-3GPP IP access. The Trusted non-3GPP IP access sends a '3. PCEF Initiated IP-CAN Session Modification' to the PDN GW. The PDN GW sends a '4. Update Bearer Request' to the Trusted non-3GPP IP access. The Trusted non-3GPP IP access uses an 'Access specific mechanism to enforce the policy' (indicated by a dashed box) and sends a '5. Update Bearer Response' to the PDN GW. The PDN GW sends a '6. Update Bearer Response' to the Trusted non-3GPP IP access. Finally, the PDN GW sends a '7. Provision Ack' to the HSS/AAA. A 'Roaming Scenarios' box covers the AAA Proxy, vPCRF, and hPCRF components.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +Sequence diagram for HSS Initiated Subscribed QoS Modification. The diagram shows the interaction between UE, Trusted non-3GPP IP access, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. The process starts with the HSS/AAA sending an '1. HSS-initiated User Profile Update procedure as in TS 23.402' to the PDN GW. The PDN GW then sends a '2. Modify Bearer Command' to the Trusted non-3GPP IP access. The Trusted non-3GPP IP access sends a '3. PCEF Initiated IP-CAN Session Modification' to the PDN GW. The PDN GW sends a '4. Update Bearer Request' to the Trusted non-3GPP IP access. The Trusted non-3GPP IP access uses an 'Access specific mechanism to enforce the policy' (indicated by a dashed box) and sends a '5. Update Bearer Response' to the PDN GW. The PDN GW sends a '6. Update Bearer Response' to the Trusted non-3GPP IP access. Finally, the PDN GW sends a '7. Provision Ack' to the HSS/AAA. A 'Roaming Scenarios' box covers the AAA Proxy, vPCRF, and hPCRF components. + +**Figure 6.1.3.5.2-1: HSS Initiated Subscribed QoS Modification** + +1. The HSS updates the User Profile as specified in clause 12.2.1 of TS 23.402[3]. +2. If the QCI and/or ARP and/or subscribed APN-AMBR has been modified and there is a related active PDN connection with the modified QoS Profile, the trusted non-3GPP IP access sends the Modify Bearer Command (EPS bearer Identity, EPS bearer QoS, APN AMBR) message to the PDN GW. The EPS bearer Identity identifies the default bearer of the affected PDN connection. The EPS bearer QoS contains the EPS subscribed QoS profile to be updated. +3. If PCC infrastructure is deployed, the PDN GW informs the PCRF about the updated EPS bearer QoS. The PCRF sends the new updated PCC decision to the PDN GW. This corresponds to the PCEF-initiated IP CAN Session Modification procedure as defined in TS 23.203 [4]. + +The PCRF may modify the APN-AMBR and the QoS parameters (QCI and ARP) associated with the default bearer in the response to the PDN GW as defined in TS 23.203 [4]. + +4. The PDN GW modifies the default bearer of each PDN connection corresponding to the APN for which subscribed QoS has been modified. If the subscribed ARP parameter has been changed, the PDN GW shall also modify all dedicated S2a bearers having the previously subscribed ARP value unless superseded by PCRF decision. The PDN GW then sends the Update Bearer Request (EPS bearer Identity, EPS bearer QoS, TFT, APN AMBR) message to the trusted non-3GPP IP access. +5. If supported by the trusted non-3GPP access, an IP-CAN specific procedure may be triggered by the enforcement of the received policy rules. The details of this step are out of the scope of 3GPP. + +6. The trusted non-3GPP IP access acknowledges the bearer modification to the PDN GW by sending an Update Bearer Response (EPS bearer Identity) message. If the bearer modification fails the PDN GW deletes the concerned S2a Bearer. +7. The PDN GW indicates to the PCRF whether the requested PCC decision was enforced or not by sending a Provision Ack message. + +### 6.1.3.6 PDN GW initiated Resource Allocation Deactivation with GTP on S2a + +This procedure depicted in figure 6.1.3.6-1 can be used to deactivate a dedicated bearer or deactivate all bearers belonging to a PDN address, for e.g., due to IP CAN session modification requests from the PCRF or due to handover from Non-3GPP to 3GPP access. If the default bearer belonging to a PDN connection is deactivated, the PDN GW deactivates all bearers belonging to the PDN connection. + +When it is performed for a handover, the connections associated with the PDN address are released, but the PDN address is kept in the PDN GW. + +![Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Delete Bearer Request (PDN GW to Trusted Non-3GPP IP Access), 3. Non-3GPP specific resource Release Procedure (dashed box between UE and Trusted Non-3GPP IP Access), 4. Delete Bearer Response (Trusted Non-3GPP IP Access to PDN GW), 5. Update PDN GW Address (PDN GW to AAA/HSS), 6. IP-CAN Session Modification (PDN GW to vPCRF).](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Delete Bearer Request (PDN GW to Trusted Non-3GPP IP Access), 3. Non-3GPP specific resource Release Procedure (dashed box between UE and Trusted Non-3GPP IP Access), 4. Delete Bearer Response (Trusted Non-3GPP IP Access to PDN GW), 5. Update PDN GW Address (PDN GW to AAA/HSS), 6. IP-CAN Session Modification (PDN GW to vPCRF). + +**Figure 6.1.3.6-1: PDN GW Initiated Bearer Deactivation with GTP on S2a** + +This procedure applies to the Non-Roaming, Roaming and Local Breakout cases. In the Local Breakout case, the vPCRF forwards messages between the PDN GW and the hPCRF. In the non-roaming and home routed roaming cases, the vPCRF is not involved at all. + +The optional interaction steps between the PDN GW and the PCRF in the procedures in figure 6.1.3.6-1 only occur if dynamic policy provisioning is deployed. Otherwise policy may be statically configured within the PDN GW. + +1. If dynamic PCC is deployed, the PDN GW initiated Bearer Deactivation procedure may for example be triggered due to 'IP CAN session Modification procedure', as defined in 3GPP TS 23.203 [4]. In this case, the resources associated with the PDN connection in the PDN GW are released. + +The PDN GW initiated Resource Allocation Deactivation can also be triggered during handovers from Non-3GPP to 3GPP. + +2. The PDN GW sends a Delete Bearer Request message (EPS Bearer Identity, Cause) to the trusted non-3GPP IP access. +3. If supported by the trusted non-3GPP access, the Non 3GPP specific resources may be released in the non-3GPP IP access. The details of this step are out of the scope of 3GPP. + +4. The trusted non-3GPP IP access deletes the bearer contexts related to the Delete Bearer Request, and acknowledges the bearer deactivation to the PDN GW by sending a Delete Bearer Response (EPS Bearer Identity) message. +5. In the case where the resources corresponding to the PDN connection are released in PDN GW, the PDN GW informs the 3GPP AAA Server/HSS of the PDN disconnection. If this is the last PDN connection for the given APN, the PDN GW identity information and APN corresponding to the UE's PDN Connection is removed from the AAA Server/HSS. This information is de-registered from the HSS as described in TS 23.402 [3]. +6. The PDN GW deletes the bearer context related to the deactivated EPS bearer. If the dedicated bearer deactivation procedure was triggered by receiving a PCC decision message from the PCRF, the PDN GW indicates to the PCRF whether the requested PCC decision was successfully enforced by completing the PCRF-initiated IP CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203 [4], proceeding after the completion of IP CAN bearer signalling. + +### 6.1.3.7 Handovers without Optimizations Between 3GPP Accesses and Non-3GPP IP Accesses with S2a GTP + +#### 6.1.3.7.1 Handover from a trusted non-3GPP IP access with S2a GTP to 3GPP Access + +The handover procedure from a trusted non-3GPP IP access using GTP S2a to E-UTRAN access using GTP S5/S8 connected to EPC is similar to the procedure specified in TS 23.402 [3], clause 8.2.1.1, except that: + +- at step 1, the tunnel between trusted non-3GPP access and the PGW is a GTP tunnel; +- at step 7, the PDN GW may create dedicated bearers during this procedure. +- at step 18, the PDN GW shall initiate resource allocation deactivation procedure in the trusted non-3GPP IP access as defined in clause 6.1.3.6 PDN GW initiated Resource Allocation Deactivation with GTP on S2a. + +![Sequence diagram for handover from Trusted Non-3GPP IP Access with GTP on S2a to E-UTRAN. The diagram shows network entities: UE, Trusted non-3GPP Access, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A green horizontal bar labeled '1. GTP Tunnel(s)' connects Trusted non-3GPP Access and PDN GW. A dashed box labeled '(C)' encloses MME, Serving GW, Old MME/SGSN, and PDN GW, containing the text 'Procedure per 8.2.1.1, steps 2 to 17'. At the bottom, arrows labeled '18. NON-3GPP EPS Bearer Release' point from the PDN GW back towards the Trusted non-3GPP Access and UE.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +| | | | | | | | | | | | +|----|-------------------------|---------|-----|------------|---------------|--------|-------------------|-------|-------|----------| +| UE | Trusted non-3GPP Access | E-UTRAN | MME | Serving GW | Old MME/ SGSN | PDN GW | Roaming Scenarios | | | HSS/ AAA | +| | | | | | | | AAA Proxy | vPCRF | hPCRF | | + +Sequence diagram for handover from Trusted Non-3GPP IP Access with GTP on S2a to E-UTRAN. The diagram shows network entities: UE, Trusted non-3GPP Access, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A green horizontal bar labeled '1. GTP Tunnel(s)' connects Trusted non-3GPP Access and PDN GW. A dashed box labeled '(C)' encloses MME, Serving GW, Old MME/SGSN, and PDN GW, containing the text 'Procedure per 8.2.1.1, steps 2 to 17'. At the bottom, arrows labeled '18. NON-3GPP EPS Bearer Release' point from the PDN GW back towards the Trusted non-3GPP Access and UE. + +**Figure 6.1.3.7.1-1: Handover from Trusted Non-3GPP IP Access with GTP on S2a to E-UTRAN** + +The handover procedure from a trusted non-3GPP IP access using GTP S2a to UTRAN/GERAN access using GTP S5/S8 connected to EPC is similar to the procedure specified in TS 23.402 [3], clause 8.2.1.3, except that: + +- at step 1, the tunnel between trusted non-3GPP access and the PGW is a GTP tunnel; +- at step 10, the PDN GW may create dedicated bearers during this procedure. +- at step 17, the PDN GW shall initiate resource allocation deactivation procedure in the trusted non-3GPP IP access as defined in clause 6.1.3.6 PDN GW initiated Resource Allocation Deactivation with GTP on S2a. + +![Sequence diagram for handover from Trusted Non-3GPP IP Access with GTP on S2a to UTRAN/GERAN. Lifelines: UE, Trusted Non-3GPP IP Access, 3GPP Access, SGSN, Serving GW, Old SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, HSS/AAA. The diagram shows step 1: GTP Tunnel(s) and step 17: Non-3GPP EPS Bearer Release. A dashed box labeled (D) encloses steps 2 to 16, labeled 'Procedure per 8.2.1.3 steps 2 to 16'. The 'Roaming Scenarios' group includes AAA Proxy, vPCRF, and hPCRF.](26d664119ad25250780f554633444e54_img.jpg) + +The diagram illustrates a sequence of messages for a handover procedure. The lifelines are: UE, Trusted Non-3GPP IP Access, 3GPP Access, SGSN, Serving GW, Old SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A dashed box labeled (D) encloses steps 2 to 16, labeled 'Procedure per 8.2.1.3 steps 2 to 16'. The 'Roaming Scenarios' group includes AAA Proxy, vPCRF, and hPCRF. Step 1 is 'GTP Tunnel(s)' and step 17 is 'Non-3GPP EPS Bearer Release'. + +Sequence diagram for handover from Trusted Non-3GPP IP Access with GTP on S2a to UTRAN/GERAN. Lifelines: UE, Trusted Non-3GPP IP Access, 3GPP Access, SGSN, Serving GW, Old SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, HSS/AAA. The diagram shows step 1: GTP Tunnel(s) and step 17: Non-3GPP EPS Bearer Release. A dashed box labeled (D) encloses steps 2 to 16, labeled 'Procedure per 8.2.1.3 steps 2 to 16'. The 'Roaming Scenarios' group includes AAA Proxy, vPCRF, and hPCRF. + +Figure 6.1.3.7.1-2: Handover from Trusted Non-3GPP IP Access with GTP on S2a to UTRAN/GERAN + +6.1.3.7.2 Handover from 3GPP Access to a trusted non-3GPP IP access with S2a GTP + +NOTE 1: This procedure is based on TS 23.402 [3], clause 8.2.2. Only the differences are described below. + +![Sequence diagram illustrating the handover from 3GPP Access to Trusted Non-3GPP IP Access with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, 3GPP Access, MME/SGSN, Serving GW, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. Key steps include: 1. GTP/PMIP tunnel establishment; 2. UE discovers Trusted Non-3GPP Access and initiates HO; 3. Access Authentication and Authorization (PDN GW); 4. L3 Attach Trigger; 5. Create Session Request (IMSI, PDN GW); 6A. PCEF-Initiated IP-CAN Session Modification Procedure; 6B. Update AAA Server/HSS; 7. Create Session Response (IP Addr); 8. L3 Attach Completion; 9. GTP tunnel establishment; 10. UE-initiated Connectivity to Additional PDN; 11. 3GPP EPS Bearer Release. A 'Roaming Scenarios' box covers the AAA Proxy, vPCRF, hPCRF, and HSS/AAA components.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Sequence diagram illustrating the handover from 3GPP Access to Trusted Non-3GPP IP Access with GTP on S2a. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, 3GPP Access, MME/SGSN, Serving GW, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. Key steps include: 1. GTP/PMIP tunnel establishment; 2. UE discovers Trusted Non-3GPP Access and initiates HO; 3. Access Authentication and Authorization (PDN GW); 4. L3 Attach Trigger; 5. Create Session Request (IMSI, PDN GW); 6A. PCEF-Initiated IP-CAN Session Modification Procedure; 6B. Update AAA Server/HSS; 7. Create Session Response (IP Addr); 8. L3 Attach Completion; 9. GTP tunnel establishment; 10. UE-initiated Connectivity to Additional PDN; 11. 3GPP EPS Bearer Release. A 'Roaming Scenarios' box covers the AAA Proxy, vPCRF, hPCRF, and HSS/AAA components. + +**Figure 6.1.3.7.2-1: Handover from 3GPP Access to Trusted Non-3GPP IP Access with GTP on S2a** + +1-4) Same as step 1-4 in TS 23.402 [3] clause 8.2.2 except that at step 1, the tunnel between Serving GW and the PGW may be both a GTP or a PMIP tunnel. + +5) The entity in the Trusted non-3GPP IP Access sends Create Session Request (IMSI, APN, Handover Indication, RAT type, Trusted non-3GPP IP Access TEID of the control plane, Trusted non-3GPP IP Access Address for the user plane, Trusted non-3GPP IP Access TEID of the user plane, EPS Bearer Identity) message to the PDN GW. The RAT type indicates the non-3GPP IP access technology type. If the UE supports IP address preservation and included the address in early steps, the Trusted non-3GPP IP Access sets the 'Handover Indication' in the Creation Session Request to allow the PDN GW to re-allocate the same IP address or prefix that was assigned to the UE while it was connected to the 3GPP IP access and to initiate a PCEF-Initiated IP CAN Session Modification Procedure with the PCRF. + +NOTE 2: With GTP on S2a, APN, IMSI and EPS Bearer ID identifies a PDN connection over GTP based S2a. + +NOTE 3: With GTP on S2a, there is no relation between the values of the EPS bearer identities used within 3GPP networks and non-3GPP networks. + +NOTE 4: In a non-3GPP to 3GPP access handover, the 'Handover Indication' leads the PDN GW to delay switching the DL user plane traffic from non-3GPP to 3GPP until a subsequent Modify Bearer Request is received. In a 3GPP to non-3GPP handover scenario with GTP based S2a, the 'Handover Indication' should not delay the switching of DL user plane traffic from 3GPP to non-3GPP access. + +6A-6B) Same as steps 7A and 7B in TS 23.402 [3] clause 8.2.2 with following additions: + +- at step 8, the PDN GW may create dedicated bearers during this procedure. + +7) The PDN GW responds with a Create Session Response (PDN GW Address for the user plane, PDN GW TEID of the user plane, PDN GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, Charging ID, Cause) message to the Trusted non-3GPP IP Access. The Create Session Response contains the IP address and/or the prefix that was assigned to the UE while it was connected to the 3GPP IP access. + +8-11) Same as step 9-12 in TS 23.402 [3] clause 8.2.2, except that at step 12, the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401 [6], clause 5.4.4.1. + +--- + +## 7 Additional considerations for WLAN access to EPC through S2a for Phase 1 + +### 7.1 Solutions without UE Impact + +#### 7.1.0 General + +1) Multiple PDN connections in the WLAN access + +Since the support of multiple PDN connections in the WLAN access would require the UE to signal the APN, a solution without UE impact only considers a single PDN connection in WLAN. This does not preclude multiple PDN connections through 3GPP and WLAN as long as there is only one PDN connection using WLAN access. + +2) Mobility aspects + +A solution without any impact to the UE only considers mobility without IP address preservation: the preservation on WLAN of the IP address the UE used on the 3GPP access would require changes in existing UEs as it is not specified in current 3GPP specifications. + +NOTE: The security considerations of the internal WLAN-based trusted non-3GPP access network architecture are outside the scope of this study item. + +#### 7.1.1 Solution 1 + +##### 7.1.1.1 Reference model + +When the WLAN is considered as trusted by the operator, the WLAN AN is interfaced as any trusted non-3GPP access i.e. via STa to the 3GPP AAA Server and via S2a to a PDN-GW. EPC access via Trusted WLAN is supported through S2a interface. A single SSID offering simultaneous access for a UE to EPC through S2a and non-seamless offload is not supported. Non-seamless offload may however be supported in some deployments (e.g. with separate SSIDs for non-seamless offload and access to EPC through S2a via Wireless LAN, see clause 7.1.1.4). + +The reference model is depicted in the following figure. + +![Figure 7.1.1.1-1: Non-roaming Trusted WLAN Inter-working reference model. This diagram shows a WLAN UE connected to a Trusted WLAN Access Network via an SWw interface. The Trusted WLAN Access Network is connected to an Intranet/Internet cloud and has two interfaces to the 3GPP Home Network: STa to a 3GPP AAA Server and S2a to a PDN GW. The 3GPP AAA Server is connected to an HSS via an SWx interface. The PDN GW is connected to an hPCRF via a Gx interface and has an external SGi/Gi interface.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +Figure 7.1.1.1-1: Non-roaming Trusted WLAN Inter-working reference model. This diagram shows a WLAN UE connected to a Trusted WLAN Access Network via an SWw interface. The Trusted WLAN Access Network is connected to an Intranet/Internet cloud and has two interfaces to the 3GPP Home Network: STa to a 3GPP AAA Server and S2a to a PDN GW. The 3GPP AAA Server is connected to an HSS via an SWx interface. The PDN GW is connected to an hPCRF via a Gx interface and has an external SGi/Gi interface. + +Figure 7.1.1.1-1: Non-roaming Trusted WLAN Inter-working reference model + +![Figure 7.1.1.1-2: Home Routed Roaming Trusted WLAN Inter-working reference model. This diagram is similar to the first but includes a 3GPP AAA Proxy. The Trusted WLAN Access Network connects to the 3GPP AAA Proxy via STa, which then connects to the 3GPP AAA Server via an SWd interface. The 3GPP AAA Server connects to the HSS via SWx. The PDN GW connects to the Trusted WLAN Access Network via S2a, to the hPCRF via Gx, and has an external SGi/Gi interface.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +Figure 7.1.1.1-2: Home Routed Roaming Trusted WLAN Inter-working reference model. This diagram is similar to the first but includes a 3GPP AAA Proxy. The Trusted WLAN Access Network connects to the 3GPP AAA Proxy via STa, which then connects to the 3GPP AAA Server via an SWd interface. The 3GPP AAA Server connects to the HSS via SWx. The PDN GW connects to the Trusted WLAN Access Network via S2a, to the hPCRF via Gx, and has an external SGi/Gi interface. + +Figure 7.1.1.1-2: Home Routed Roaming Trusted WLAN Inter-working reference model + +![Figure 7.1.1.1-3: Local Breakout Roaming Trusted WLAN Inter-working reference model. In this model, the Trusted WLAN Access Network connects to a 3GPP AAA Proxy via STa, which connects to a 3GPP AAA Server via SWd. The 3GPP AAA Server connects to an HSS via SWx. The PDN GW connects to the Trusted WLAN Access Network via S2a, to a vPCRF via Gx, and has an external SGi/Gi interface. The vPCRF connects to an hPCRF via an S9 interface.](805c475f0859e607af0530ba43194bf1_img.jpg) + +Figure 7.1.1.1-3: Local Breakout Roaming Trusted WLAN Inter-working reference model. In this model, the Trusted WLAN Access Network connects to a 3GPP AAA Proxy via STa, which connects to a 3GPP AAA Server via SWd. The 3GPP AAA Server connects to an HSS via SWx. The PDN GW connects to the Trusted WLAN Access Network via S2a, to a vPCRF via Gx, and has an external SGi/Gi interface. The vPCRF connects to an hPCRF via an S9 interface. + +Figure 7.1.1.1-3: Local Breakout Roaming Trusted WLAN Inter-working reference model + +Within the trusted non-3GPP IP access network (TNAN) we distinguish three functions: + +- A WLAN Access Network (WLAN AN). This function terminates the UE's WiFi air link defined in IEEE 802.11 [5]. +- A Trusted non-3GPP access's S2a peer (TNSP). This function terminates S2a. +- A Trusted non-3GPP access's STa peer (TNAP). This function terminates STa. + +NOTE 1: Policy and QoS aspects are studied as part of BBAI. + +NOTE 2: Whether multiple TNAN functions are mapped to a single non-3GPP access entity, or a single TNAN function is distributed among multiple non-3GPP access entities is out-of-scope of 3GPP. + +#### STa reference point + +The STa reference point is defined in TS 23.402 [3] and specified in TS 29.273 [7]. It connects the Trusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and transports access authentication, authorization, mobility parameters and charging-related information in a secure manner. + +STa might need to be enhanced to support: + +- A way for the Trusted WLAN Access Network to provide the AAA server with following information: + - An indication on whether the Trusted WLAN AN supports S2a, non-seamless offload or both; + +NOTE 3: Stage 3 discussions will determine whether existing "Mobility Capabilities" over STa may be reused for that purpose. + +- The SSID selected by the UE to access the Trusted WLAN AN. +- A way for the AAA server to provide the Trusted WLAN Access Network with following information: + - The APN the user is to be associated with for EPC access; this is required for the Trusted WLAN Access Network to establish the PDN connection with the PDN GW. Based on the HPLMN operator configuration the HSS may provide the 3GPP AAA server with a default APN for Trusted WLAN Access Network. + +NOTE 4: Stage 3 discussions will determine whether existing "Default APN" over STa may be reused for that purpose. + +- Whether access to EPC is allowed for the UE. + +NOTE 5: Stage 3 discussions will determine whether existing "Mobility Capabilities" over STa may be reused for that purpose. + +- The UE IMSI; this is required for the Trusted WLAN Access Network to build the S2a messages towards the PDN-GW. + +NOTE 6: Stage 3 discussions will determine whether existing "Permanent User Identity" over STa may be reused for that purpose. + +#### SWw reference point + +The SWw reference point connects the WLAN UE to the WLAN Access Network according to IEEE 802.11 [5]. This includes the support of: + +- the security that was defined as part of 802.11-2007 [5] and thus the transport of EAP signalling messages for authentication signalling between the 3GPP AAA Server and the WLAN UE; +- parameters for identification of the operator networks for roaming purposes (i.e. PLMN list). + +#### SWx reference point + +The SWx reference point is defined for EPC in TS 23.402 [3]. It is specified at stage 3 level respectively in TS 29.273 [7]. + +### 7.1.1.2 Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW + +![Sequence diagram of the Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes the PDN GW, vPCRF, AAA Proxy, and hPCRF. The process involves Non-3GPP Specific Procedures, EAP Authentication, L3 Attach Trigger, Create Session Request, IP-CAN Session Establishment Procedure, Update PDN GW Address, Create Session Response, GTP Tunnel, and L3 Attach Completion.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TNSP as Trusted Non-3GPP IP Access + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note left of TNSP: 1. Non-3GPP Specific Procedures + Note left of TNSP: 2. EAP Authentication + Note left of TNSP: 3. L3 Attach Trigger + Note right of PDN_GW: Roaming Scenarios + + TNSP->>HSS_AAA: 2. Authentication & Authorization + TNSP->>PDN_GW: 5. Create Session Request + Note right of PDN_GW: 6. IP-CAN Session Establishment Procedure + PDN_GW->>HSS_AAA: 7. Update PDN GW Address + PDN_GW->>TNSP: 8. Create Session Response + Note right of TNSP: 9. GTP Tunnel + Note left of TNSP: 11. L3 Attach Completion + +``` + +Sequence diagram of the Initial Attach Procedure with GTP on S2a and Anchoring in PDN GW. The diagram shows interactions between UE, Trusted Non-3GPP IP Access, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes the PDN GW, vPCRF, AAA Proxy, and hPCRF. The process involves Non-3GPP Specific Procedures, EAP Authentication, L3 Attach Trigger, Create Session Request, IP-CAN Session Establishment Procedure, Update PDN GW Address, Create Session Response, GTP Tunnel, and L3 Attach Completion. + +**Figure 7.1.1.2-1: Initial attachment with Network-based MM mechanism over S2a for roaming, LBO and non-roaming scenarios** + +A per-UE point-to-point link between UE and TNSP is assumed. In particular, it is assumed that the trusted non-3GPP access does not do any routing of UE traffic between WLAN AN and TNSP. It is assumed that the WLAN AN applies upstream and downstream forced-forwarding between the UE's WiFi air link and the WLAN AN -TNSP link. The aspects of point-to-point link described in IETF RFC 5213 [17] and IETF RFC 5844 [18] also applies to the point-to-point link between UE and TNSP. The implementation of the point-to-point link is out-of-scope for 3GPP. + +In this specific solution, it is assumed that TNSP is the first hop router and the DHCP server. + +NOTE 1: The link model is different from GTP based S5/S8 and GTP based S2b. + +No specific mechanisms are defined to support AP-to-AP handover. + +Refer to clause 6.1.3.1. Based on assumptions for solutions with no impact to UE, UE cannot provide APN and PCO to TNSP. So, there are following differences than clause 6.1.3.1: + +- At step 2, the following additions apply: + - The HSS provide APN information to the Trusted Non-3GPP IP Access in the subscription data. HSS provides a default APN for WLAN. PDN type is indicated from HSS in this step. Based on the HPLMN operator configuration the HSS may provide the 3GPP AAA server with a default APN for Trusted WLAN Access Network. + +NOTE 2: If the APN used in 3GPP side is the same as the default APN for Trusted WLAN the network may select the same or different PDN GWs for the PDN connections when PDN connections to this APN are activated via 3GPP access network and Trusted WLAN in the same time. If the same PDN GW is selected then the APN-AMBR is enforced for the PDN connections. If different PDN GWs are selected then the APN-AMBR is enforced separately in the PDN GWs for the PDN connections, i.e. the UE will receive double amount of bandwidth for the APN. Therefore it is recommended that the default APN for Trusted WLAN access be different from any APN that the UE may use on the 3GPP side. + +- The UE and the EPC are mutually authenticated through the WLAN Access as defined in TS 23.402 [3] clause 4.9.1. +- IEEE 802.1X as defined by IEEE 802.11 [5] is used over the WLAN air link to carry EAP. +- After EAP authentication, UE traffic over the WLAN air link may be confidentiality and integrity protected as defined by IEEE 802.11 [5]. +- The TNAN may indicate to the AAA server via STa whether it supports S2a, non-seamless offload or both. The HSS/AAA may indicate via STa whether access to EPC via S2a is or is not allowed for this subscriber. The HSS/AAA decision to allow EPC access or not could be based on information elements such as subscriber profile, access network, SSID selected. +- At step 3, For IPv4 address configuration, the use of DHCPv4 as in IETF RFC 5844 [18] is the L3 attach trigger. +- At step 3, For IPv6 address configuration, the use of RS as in IETF RFC 5213 [17] or LL-DAD NS is the L3 attach trigger. The TNSP does not send RAs until an L3 attach trigger is received. + +NOTE 3: It is assumed that, to identify the UE, the L3 triggers are transported in an L2 frame that contains the UE L2 address (MAC address). + +- The TNAN determines based on HSS/AAA indication or pre-configured information whether or not to establish S2a. +- If the TNAN determined that S2a shall not be used steps 5-9 are skipped. Instead, the TNAN assigns an IPv4 address and/or IPv6 prefix to the UE (depending on the trigger received in step 3) and offloads the traffic. +- At step 5, when TNSP receives L3 attach trigger message, the TNSP selects default APN according the subscription data received in step 2. If the L3 attach trigger is of an IP version not supported by the subscription PDN Type, the TNSP does not send Create Session Request. Otherwise, the TNSP sends a Create Session Request with the PDN Type of the subscription data: + - If the L3 attach trigger is IPv4 and step 2 indicates that PDN type IPv4v6 is supported for the default APN, then PDN type in the Create Session Request is set to IPv4v6. If the UE also performs an IPv6 L3 attach trigger, then the TNSP will correlate both requests to the same PDN connection. + - If the L3 attach trigger is IPv6, and step 2 indicates that PDN type IPv4v6 is supported for the default APN, then PDN type in the Create Session Request is set to IPv4v6. If the UE also performs an IPv4 L3 attach trigger, then the TNSP will correlate both requests to the same PDN connection. + - If the L3 attach trigger is IPv4, and step 2 indicates that PDN type is IPv4-only, then PDN type in the Create Session Request is set to IPv4. + - If the L3 attach trigger is IPv6, and step 2 indicates that PDN type is IPv6-only, then PDN type in the Create Session Request is set to IPv6. +- At step 8, PDN GW sends Create Session Response to the TNSP. +- At step 11, for IPv4, a DHCPv4 message with allocated IPv4 address is sent. For IPv6, the TNSP starts sending RAs with the allocated prefix and sets "autonomous address configuration" flag and "O" flag [RFC 4861]. + +NOTE 4: A UE might request to get some IP configuration parameters (e.g. DNS server) by means of DHCP. These parameters sent by TNSP(acting as a DHCP server) to the UE in a DHCP reply. These parameters are retrieved by the TNSP(acting as a DHCP client) from the PGW by means of DHCP. + +### 7.1.1.3 Without-UE-impact procedures except Initial Attach + +Based on the GTP-S2a procedures in Section 6, for the solution without UE impact the following procedures are considered: + +- Detach and PDN Disconnection with GTP on S2a: + - Trusted WLAN AN and HSS/AAA may disconnect the PDN Connection and detach the UE, and the PDN GW may initiate Resource Allocation Deactivation for the default bearer as the PDN disconnection. If there is no traffic received from the UE for a configurable duration and the WLAN AN detects the UE has left based on unanswered probes (e.g. ARP Request, Neighbour Solicitation message), it disconnects the PDN Connection. In these cases the UE IP address(es) are released in the network. When disconnecting the PDN Connection, the TNAN needs to locally remove the UE context and de-authenticate and disconnect the UE at Layer 2 according to IEEE Std. 802.11-2007 [5]. When UE connects to the network next time, the L2 disconnection serves as an indication to the UE that the previous IPv4 address/IPv6 prefix might no longer be valid. The UE can then proceed with re-validation or re-acquisition of its IPv4 address / IPv6 prefix. +- The UE can send an explicit DHCPv4 message to release the IPv4 address, then the PDN connection is disconnected when the PDN type is IPv4. +- PDN GW Initiated Bearer Modification and HSS Initiated Subscribed QoS Modification procedures may be used to modify the default and dedicated bearer but correspond to no signalling over Trusted WLAN's airlink. +- The dedicated bearer activation procedure may be used to activate the dedicate bearer in S2a but correspond to no signalling over Trusted WLAN's airlink. + +In addition, the following procedures in clause 6 are not supported: + +- UE-initiated Connectivity to Additional PDN connection. +- The handover between Trusted WLAN and 3GPP Access with IP address preservation. + +### 7.1.1.4 SaMOG deployment + +WLAN networks may be deployed such that separate SSIDs are used for EPC-routed and non-seamless WLAN offload, e.g. SSID\_EPC and SSID\_NSO. + +WLAN networks may also be deployed such that the same SSID in a WLAN Access Point provides different type of network access to different users attached to this Access Point. For example, SSIDX may provide EPC-routed access for subscriber A, but non-seamless WLAN offload for subscriber B. In such a deployment it would be up to the operator to provide network configuration that supports different user access preferences, subscriptions and UE configurations. + +It is recommended that the UE can be configured to apply different behavior when connected to different SSIDs, e.g. allow or prevent the usage of certain applications on specific SSIDs. For example, for the SSIDs used for SaMOG the UE can be configured to disable applications that require local connectivity (e.g. DLNA applications) and enable applications that require EPC connectivity to the default APN used for SaMOG. Such kind of special behavior for SSIDs used for SaMOG can improve the user experience and prolong the UE battery life. + +NOTE: An unmodified UE can be configured to apply different behaviour when connected to different SSIDs by means which are outside the scope of this document. For example, the UE can be configured over-the-air, by means of a downloadable application, or by means of manual configuration. + +### 7.1.1.5 PMIP based S2a considerations + +The solution described above can also work when PMIP is used over S2a with the following considerations: + +- To support PMIP, the TNSP shall implement the MAG function as it is specified in TS 23.402 [3], clause 6 for S2a. Instead of GTP messages the relevant PMIP messages are used as it is specified in TS 23.402 [3], clause 6 for S2a. +- The considerations described on APN and PDN type selection in clause 7.1.1.2 are also valid when PMIP based S2a is used. + +- The link model, IPv4 address and IPv6 prefix allocation considerations of the sections describing the solution with GTP S2a (e.g. TNSP is the first hop router and DHCPv4 server shall be located in the TNSP) are also valid when PMIP based S2a is used. + +## 7.1.2 Solution 2 + +### 7.1.2.0 General + +This solution is based on the S2a bearer creation and deletion between a Trusted Non-3GPP WLAN Access and the 3GPP Home Network be driven by the AAA signalling between these two. A key difference to the solution described in clause 7.1.1 is that this solution uses EAP and AAA signalling to trigger establishment of the S2a session, while the solution in clause 7.1.1 uses L3 messages to trigger the S2a session. The interfaces towards EPC (STa and S2a) do not differ between the solutions. + +NOTE: Although the solution is described for a GTP-based S2a, it would equally apply to a PMIP-based system were the GTP signalling be replaced by the corresponding PMIP signalling (i.e. Create Session Request replaced by Proxy Binding Update, and Create Session Reply replaced by Proxy Binding Acknowledgement, as well as the corresponding BBERF procedures between Trusted WLAN Access Gateway and PCRF). + +### 7.1.2.1 Reference Model + +NOTE: The shaded area in Figures 7.1.2.1-1, 7.1.2.1-2, and 7.1.2.1-3 refers to Trusted Non-3GPP WLAN Access functionality. + +![Figure 7.1.2.1-1: Non-roaming reference model diagram](94acd33fcad85bb6f207a308f9b63191_img.jpg) + +The diagram illustrates the non-roaming reference model. On the left, a 'UE' (User Equipment) is connected to a 'WLAN Access Network' via the 'Tw' interface. The 'WLAN Access Network' is part of a 'Trusted Non-3GPP WLAN' (indicated by a shaded oval). Inside the WLAN Access Network, there are two main components: 'TWAP' (Trusted WLAN Access Point) and 'TWA' (Trusted WLAN Access Gateway). The 'TWAP' is connected to the 'UE' via the 'Ta' interface and to the 'TWA' via the 'Tg' interface. The 'TWA' is connected to the 'UE' via the 'Tu' interface and to the 'PDN GW' (PDN Gateway) via the 'S2a' interface. The 'PDN GW' is connected to the '3GPP Home Network' via the 'SGi' interface. Inside the '3GPP Home Network', the 'PDN GW' is connected to '3GPP AAA' (Authentication, Authorization, Accounting) via the 'STa' interface. The '3GPP AAA' is connected to 'SWx' (SWx interface), which is in turn connected to the 'HSS' (Home Subscriber Server). + +Figure 7.1.2.1-1: Non-roaming reference model diagram + +Figure 7.1.2.1-1: Non-roaming reference model + +![Roaming reference model Trusted Non-3GPP WLAN Access - Home Routed](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +This diagram illustrates the 'Home Routed' roaming model for a Trusted Non-3GPP WLAN Access. On the left, a 'UE' (User Equipment) is connected to a 'WLAN Access Network' via a 'TW' (TWAP) interface. The 'WLAN Access Network' is part of a 'Trusted Non-3GPP WLAN Access' area. It connects to a 'TWAG' (TWAG) via 'Tn' and 'Tu' interfaces. The 'TWAG' is connected to a 'PDN GW' (PDN GW) via an 'S2a' interface. The 'PDN GW' is connected to the '3GPP Home Network' via an 'SGi' interface. The '3GPP Home Network' contains an 'HSS' (HSS) and a '3GPP AAA Server' (3GPP AAA Server) connected by an 'SWx' interface. The '3GPP Visited Network' (3GPP Visited Network) contains a '3GPP AAA Proxy' (3GPP AAA Proxy) connected to the '3GPP AAA Server' via an 'SWd' interface. The '3GPP Visited Network' is connected to the 'WLAN Access Network' via 'STa' and 'STg' interfaces. + +Roaming reference model Trusted Non-3GPP WLAN Access - Home Routed + +Figure 7.1.2.1-2: Roaming reference model Trusted Non-3GPP WLAN Access - Home Routed + +![Roaming reference model Trusted Non-3GPP WLAN Access - Local Break-Out](a4b963a07cc368283154762c4b156fe7_img.jpg) + +This diagram illustrates the 'Local Break-Out' roaming model for a Trusted Non-3GPP WLAN Access. On the left, a 'UE' (User Equipment) is connected to a 'WLAN Access Network' via a 'TW' (TWAP) interface. The 'WLAN Access Network' is part of a 'Trusted Non-3GPP WLAN Access' area. It connects to a 'TWAG' (TWAG) via 'Tn' and 'Tu' interfaces. The 'TWAG' is connected to a 'PDN GW' (PDN GW) via an 'S2a' interface. The 'PDN GW' is connected to the '3GPP Visited Network' via an 'SGi' interface. The '3GPP Visited Network' contains a '3GPP AAA Proxy' (3GPP AAA Proxy) connected to the '3GPP AAA Server' (3GPP AAA Server) via an 'SWd' interface. The '3GPP Visited Network' is connected to the 'WLAN Access Network' via 'STa' and 'STg' interfaces. The '3GPP Home Network' (3GPP Home Network) contains an 'HSS' (HSS) and a '3GPP AAA Server' (3GPP AAA Server) connected by an 'SWx' interface. The '3GPP Home Network' is connected to the '3GPP Visited Network' via an 'SWd' interface. + +Roaming reference model Trusted Non-3GPP WLAN Access - Local Break-Out + +Figure 7.1.2.1-3: Roaming reference model Trusted Non-3GPP WLAN Access - Local Break-Out + +## 7.1.2.2 Network elements + +### 7.1.2.2.1 UE + +For the purpose of accessing a Trusted Non-3GPP WLAN Access the UE is assumed to be unmodified and has the following standard functions: + +- WLAN Access Network authentication based on EAP methods. +- Configure an IP address on the WLAN using the relevant IETF standards, depending on the specific WLAN deployment: + - For IP version 4: DHCP as per IETF RFC 2131. Optionally, Detecting Network Attachment in IPv4 (DNAv4) according to IETF RFC 4436. + - For IP version 6: Stateless Address Autoconfiguration (SLAAC) as per IETF RFC 4861 [11], and optionally stateless DHCPv6 as per IETF RFC 3736 [19]. Optionally, Detecting Network Attachment in IPv6 (DNAv6) according to IETF RFC 6059 [14]. + +### 7.1.2.2.2 Trusted WLAN AAA Proxy + +The Trusted WLAN AAA Proxy (TWAP) function includes: + +- Relaying the AAA information between the WLAN Access Network and the 3GPP AAA Server or Proxy in case of roaming. +- Establishing Binding of UE IMSI with UE MAC address on the WLAN Access Network into (IMSI, MAC) tuple via snooping on the AAA protocol carrying EAP-AKA exchange. +- Detecting L2 Attach of UE to the WLAN Access Network via snooping on the AAA protocol for EAP-Success message. +- Detecting L2 Detach of UE from the WLAN Access Network via snooping on the AAA protocol for Accounting-Request STOP message. +- Informing the Trusted WLAN Access Gateway of WLAN Attach and Detach events for UE with (MAC, IMSI) tuple. +- Protocol conversion when the Ta and STa reference points do not use the same protocol (e.g. Ta based on RADIUS) +- Transfer necessary information for suitable per-UE L2 encapsulation (e.g. 802.1Q VLAN tag or MPLS label) between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway. + +The Trusted WLAN AAA Proxy functionality can reside in a separate physical network node, it may reside in the Trusted WLAN Access Gateway or any other physical network node. + +### 7.1.2.2.3 Trusted WLAN Access Gateway + +The Trusted WLAN Access Gateway function includes: + +- For IP version 4: + - Default IPv4 Router. + - DHCP server according to IETF RFC 2131 [9]. The TWAG allocates to the UE the IPv4 address that is allocated to the UE by the PDN GW. +- For IP version 6: + - Default IPv6 Router according to IETF RFC 4861 [11]. +- Enforces routing of packets between the UE MAC address and the GTP tunnel for that UE. +- Enforce per-UE L2 encapsulation of traffic to/from the UE. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between + +the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. + +NOTE 1: There is a per-UE subnet point-to-point link and subnet between the UE and the Trusted WLAN Access Gateway that acts as the default router. This link model is the same as the one used for PMIP-based S5/S8 and differs from that of GTP-based S5/S8. + +NOTE 2: Whether multiple TNAN functions are mapped to a single non-3GPP access entity, or a single TNAN function is distributed among multiple non-3GPP access entities is out-of-scope of 3GPP. + +### 7.1.2.3 Reference Points + +#### 7.1.2.3.1 Ta reference point + +The Ta reference point applies to Trusted Non-3GPP WLAN Access. + +The Ta reference point connects the WLAN Access Network to the Trusted WLAN AAA Proxy. The prime purpose of the protocols crossing this reference point is to transport authentication, authorization and accounting related information. The reference point has to accommodate also legacy WLAN Access Networks. + +EAP authentication shall be transported over the Ta reference point. + +The functionality of the reference point is to transport AAA frames: + +- Carrying data for authentication signalling between UE and 3GPP Network; As a side effect, allowing the Trusted WLAN AAA Proxy to detect L2 attach of the UE. +- Carrying data for authorization (including the authorization information update) signalling between WLAN Access Network and 3GPP Network. +- Carrying accounting signalling per WLAN user, e.g. for charging purposes; As a side effect, allowing the Trusted WLAN AAA Proxy to detect L2 detach of the UE. +- Carrying keying data for the purpose of radio interface integrity protection and encryption; +- Informs WLAN Access Network of per-UE L2 encapsulation information to be used with the Trusted WLAN Access Gateway. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. +- Purging a user from the WLAN Access Network for immediate service termination. + +#### 7.1.2.3.2 Tg reference point + +The Tg reference point applies to Trusted Non-3GPP WLAN Access. + +The Tg reference point connects the Trusted WLAN AAA Proxy to the Trusted WLAN Access Gateway. This is a AAA interface used to: + +- Trusted WLAN AAA Proxy notify Trusted WLAN Access Gateway of WLAN attach and detach events. +- Trusted WLAN Access Gateway Informs Trusted WLAN AAA Proxy of per-UE L2 encapsulation information to be used between the WLAN Access Network and the Trusted WLAN Access Gateway. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. + +#### 7.1.2.3.3 Tn reference point + +The Tn reference point applies to Trusted Non-3GPP WLAN Access. + +The Tn reference point connects the WLAN Access Network and the Trusted WLAN Access Gateway and provides the following functionality: + +- Per-UE encapsulation between the WLAN Access Network and the Trusted WLAN Access Gateway. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. + +#### 7.1.2.3.4 Tw reference point + +The Tw reference point applies to Trusted Non-3GPP WLAN Access. + +The Tw reference point connects the UE to the WLAN Access Network per IEEE 802.11 [5] specifications. The definition of IEEE Physical and Medium Access Control layers protocols (e.g. Layer 1 and Layer 2 defined by IEEE 802.11 [5] standards) is out of the scope of 3GPP. + +The functionality of the reference point is based on IEEE 802.11 [5] specifications and it is intended to transport signalling messages including: + +- Attach and Detach request from the UE to the WLAN Access Network. +- Detach signal from the WLAN Access Network to the UE. +- Parameters for authentication signalling between the 3GPP AAA Server and the UE; +- Per-UE encapsulation of data frames between the UE and the WLAN Access Network as per IEEE 802.11 [5] specifications. + +#### 7.1.2.3.5 Tu reference point + +The Tu reference point applies to Trusted Non-3GPP WLAN Access. + +The Tu reference point represents the point-to-point link and per-UE subnet between the UE and the Trusted WLAN Access Gateway. Transport for the Tu reference point is provided by a combination of: + +- The Tw reference point provides an IEEE 802.11 association between the UE and a BSSID/ESSID in the WLAN Access Network, as per IEEE 802.11 specifications. +- The WLAN Access Network internally provides per-UE encapsulation between the BSSID/ESSID and the Tn endpoint. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. +- The Tn reference point provides per-UE encapsulation between the WLAN Access Network and the Trusted WLAN Access Gateway. The specifics of the encapsulation method in use (e.g. L2 unicasting, IETF RFC 6085 [16], 802.11Q VLAN, MPLS, CAPWAP) and how it is negotiated between the Trusted WLAN Access Network and the Trusted WLAN Access Gateway via the Trusted WLAN AAA Proxy are dependent on the specifics of the WLAN Access Network Deployment and out-of-scope for 3GPP. + +#### 7.1.2.4 Procedures + +For the steps that already exist in the generic Trusted Non-3GPP Access procedure and are re-used in the Trusted Non-3GPP WLAN Access procedure, identical numbering is used, and the differences are outlined, if any. For the steps that are specific to the Trusted Non-3GPP WLAN Access procedure and do not exist in the generic Trusted Non-3GPP WLAN Access procedure, the steps are indexed with the number of the generic preceding step and a letter, and a description of the step is provided. + +#### 7.1.2.4.1 Initial Attach to Trusted Non-3GPP WLAN Access procedure + +![Sequence diagram of the Initial Attach to Trusted Non-3GPP WLAN Access procedure. The diagram shows interactions between UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, and hPCRF. The procedure includes steps: 1. WLAN Specific Procedures (UE to WLAN Access Network), 2. EAP Authentication (UE to WLAN Access Network), 2b. WLAN Attach Request (WLAN Access Network to TWAG), 5. Create Session Request (TWAG to PDN GW), 6. IP-CAN Session Establishment Procedure (PDN GW to vPCRF), 7. Update PDN GW Address (vPCRF to HSS/AAA), 8. Create Session Response (PDN GW to TWAG), 9. GTP Tunnel (TWAG to PDN GW), 9b. WLAN Attach Accept (TWAG to WLAN Access Network), 9c. EAP Success (WLAN Access Network to UE), and 11. L3 Attach Completion (WLAN Access Network to UE).](04cfca33e3fc26513abe649d7474f733_img.jpg) + +Sequence diagram of the Initial Attach to Trusted Non-3GPP WLAN Access procedure. The diagram shows interactions between UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, and hPCRF. The procedure includes steps: 1. WLAN Specific Procedures (UE to WLAN Access Network), 2. EAP Authentication (UE to WLAN Access Network), 2b. WLAN Attach Request (WLAN Access Network to TWAG), 5. Create Session Request (TWAG to PDN GW), 6. IP-CAN Session Establishment Procedure (PDN GW to vPCRF), 7. Update PDN GW Address (vPCRF to HSS/AAA), 8. Create Session Response (PDN GW to TWAG), 9. GTP Tunnel (TWAG to PDN GW), 9b. WLAN Attach Accept (TWAG to WLAN Access Network), 9c. EAP Success (WLAN Access Network to UE), and 11. L3 Attach Completion (WLAN Access Network to UE). + +**Figure 7.1.2.4.1-1: Initial attach to Trusted Non-3GPP WLAN Access** + +The procedure for Initial Attach to Trusted Non-3GPP WLAN Access is represented in Figure 7.1.2.4.1-1 and described below. It is based on the generic Initial Attach to Trusted Non-3GPP Access procedure described in clause 6.1.3.1. with the following differences: + +- At step 2, the following additions apply: + - The HSS/AAA provides to the Trusted Non-3GPP WLAN Access the APN to which the UE will be attached. in the subscription data. PDN type is indicated from HSS in this step. + - The mutual authentication between the UE and the EPC as defined in TS 23.402 [3], clause 4.9.1 is carried according to IEEE 802.11 [5] specifications through the Trusted Non-3GPP WLAN Access. + - At reception of the EAP Success, the Trusted WLAN AAA Proxy buffers it and notifies the Trusted WLAN Access Gateway of the layer 2 attach of the UE and provides MAC address and IMSI of the UE as depicted in step 2b. +- At step 5, after the Trusted WLAN AAA Proxy informs of layer 2 attach of the UE, the Trusted WLAN Access Gateway selects the APN as per the subscription data received in step 2 and send Create Session Request to the PDN GW with the PDN type. +- At step 8, After allocating an IPv6 prefix and/or an IPv4 address to the UE, the PDN GW sends Create Session Response to the Trusted WLAN Access Gateway. Deferred IPv4 address allocation may be used. +- At step 9b, the Trusted WLAN Access Gateway notifies the Trusted Non-3GPP Access AAA Proxy of successful GTP tunnel establishment, and provides the necessary parameters for establishment of a point-to-point link towards the UE through the WLAN Access Network. +- At step 9c, the Trusted WLAN AAA Proxy delivers the buffered EAP success to the WLAN Access Network together with the necessary parameters for establishment of a point-to-point link between the UE and the Trusted WLAN Access Gateway. On receiving this, the WLAN Access Network configures the point-to-point link adequately and informs the UE of EAP success. + +- At step 11, after the UE is associated and authenticated with the WLAN Access Network, the UE performs IP layer configuration with the Trusted WLAN Access Gateway acting as the default router according to standard IETF procedures [9] [12] [13] [14] [19]. + +NOTE: The WLAN Access Gateway can send unsolicited IP layer configuration signalling, e.g. DHCPv4 or RA, over the point-to-point link towards the UE. + +#### 7.1.2.4.2 UE/Trusted Non-3GPP WLAN Access Network Initiated Detach procedure + +![Sequence diagram for UE/Trusted Non-3GPP WLAN Access Network Initiated Detach procedure. The diagram shows interactions between UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded 'Roaming Scenarios' box contains vPCRF, AAA Proxy, and hPCRF. The procedure starts with a dashed box '1. UE or WLAN Access Network initiated detach'. Step 2b 'Session Termination' is a message from the WLAN Access Network to the HSS/AAA. Step 2c 'WLAN Detach Request' is from the AAA Proxy to the TWAG. Step 3 'Delete Session Request' is from the TWAG to the PDN GW. Step 4 'Update PDN GW Address' is from the PDN GW to the HSS/AAA. Step 5 is a dashed box 'PCEF-initiated IP-CAN Session Termination Procedure' between the PDN GW and the AAA Proxy. Step 6 'Delete Session Response' is from the PDN GW to the TWAG. Step 6b 'WLAN Detach Accept' is from the TWAG to the WLAN Access Network.](b6ad8b32179842fca5ad086cf22b03eb_img.jpg) + +Sequence diagram for UE/Trusted Non-3GPP WLAN Access Network Initiated Detach procedure. The diagram shows interactions between UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded 'Roaming Scenarios' box contains vPCRF, AAA Proxy, and hPCRF. The procedure starts with a dashed box '1. UE or WLAN Access Network initiated detach'. Step 2b 'Session Termination' is a message from the WLAN Access Network to the HSS/AAA. Step 2c 'WLAN Detach Request' is from the AAA Proxy to the TWAG. Step 3 'Delete Session Request' is from the TWAG to the PDN GW. Step 4 'Update PDN GW Address' is from the PDN GW to the HSS/AAA. Step 5 is a dashed box 'PCEF-initiated IP-CAN Session Termination Procedure' between the PDN GW and the AAA Proxy. Step 6 'Delete Session Response' is from the PDN GW to the TWAG. Step 6b 'WLAN Detach Accept' is from the TWAG to the WLAN Access Network. + +**Figure 7.1.2.4.2-1: UE/Trusted Non-3GPP WLAN Access Network Initiated Detach** + +The procedure for UE/Trusted Non-3GPP WLAN Access Network Initiated Detach is represented in Figure 7.1.2.4.2-1 and described below. It is based on the generic UE/Trusted Non-3GPP IP Access Network Initiated Detach procedure described in clause 6.1.3.2.1. with the following differences: + +- At step 2, the following additions apply: + - In step 2b, the UE/Trusted Non-3GPP WLAN Access Network Initiated Detach triggers AAA signalling between the WLAN Access Network and the home HSS/AAA server to terminate the session. + - Based on the AAA signalling for session termination, the Trusted WLAN AAA Proxy sends a WLAN Detach Request to the Trusted WLAN Access Gateway. +- Step 3 is initiated by the Trusted WLAN Access Gateway based on the WLAN Detach Request received from the Trusted WLAN AAA Proxy. +- At step 6, the following addition applies: + - In step 6b, the Trusted WLAN Access Gateway confirms session deletion by sending to the Trusted WLAN AAA Proxy a WLAN detach accept. + +### 7.1.2.4.3 HSS/AAA Initiated Detach procedure + +![Sequence diagram for HSS/AAA Initiated Detach procedure. Lifelines: UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. A 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF. Step 1: HSS/AAA sends a Session Termination Request to the PDN GW. Step 2: A block labeled 'The procedures as figure 7.1.2.4.2-1, Step 2c to 6b.' is shown. Step 3: The PDN GW sends a Session Termination Response to the HSS/AAA.](f5deee2f3301ee351c4008283ffafbb3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant WLAN as WLAN Access Network + participant TWAG + participant TWAP + participant PDN as PDN GW + participant vPCRF + participant AAA as AAA Proxy + participant hPCRF + participant HSS as HSS/AAA + + Note right of AAA: Roaming Scenarios + HSS->>PDN: 1. Session Termination Request + Note over WLAN, TWAG, TWAP, PDN, vPCRF, AAA, hPCRF: 2. The procedures as figure 7.1.2.4.2-1, Step 2c to 6b. + PDN->>HSS: 3. Session Termination Response + +``` + +Sequence diagram for HSS/AAA Initiated Detach procedure. Lifelines: UE, WLAN Access Network, TWAG, TWAP, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. A 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF. Step 1: HSS/AAA sends a Session Termination Request to the PDN GW. Step 2: A block labeled 'The procedures as figure 7.1.2.4.2-1, Step 2c to 6b.' is shown. Step 3: The PDN GW sends a Session Termination Response to the HSS/AAA. + +Figure 7.1.2.4.3-1: HSS/AAA Initiated Detach + +The procedure for HSS/AAA Initiated Detach from Trusted Non-3GPP WLAN Access Network is represented in Figure 7.1.2.4.3-1 and described below. As for the UE/Trusted Non-3GPP WLAN Access Network Initiated Detach, it is based on the generic HSS/AAA Initiated Detach procedure described in clause 6.1.3.2.2 with the following differences: + +- At step 2, the step 2c to 6b of the UE/Trusted Non-3GPP WLAN Access Network Initiated Detach procedure described in clause 7.1.2.4.2 are followed. + +### 7.1.2.4.4 Other procedures + +Other procedures defined for the generic Trusted Non-3GPP IP Access refer to clause 7.1.1.3 descriptions. + +## 7.1.3 Handovers with or without TNSP/TWAG relocation with unmodified UEs + +No specific mechanisms are defined to support AP-to-AP handover with and without TNSP/TWAG relocation. However, this does not preclude the support of IP address preservation in handovers without TNSP/TWAG relocation when supported by procedures out of 3GPP scope. + +# 8 Additional considerations for WLAN access to EPC through S2a for Phase 2 + +**Editor's Note:** Phase 2 of the study is aiming at studying enhancements to the Rel-11 solution to avoid those limitations (except emergency attach). In this phase it is expected that there will be some impacts to the UE. + +## 8.1 Requirements + +**Editor's Note:** This sub-clause will contain the requirement(s) related to SaMOG Phase 2 study. + +The solutions shall comply with the following Requirements: + +- The SaMOG phase 2 solution (e.g. possibly with impact to the UE) shall be able to co-exist with the SaMOG Release 11 solution. + +The solutions shall comply with one or more of the following requirements: + +- For a UE, multiple simultaneous PDN connections over Trusted WLAN are supported, including the support for establishment of concurrent PDN Connections via 3GPP access and over WLAN. +- For a UE, PDN Connectivity to EPC over Trusted WLAN concurrent with non-seamless WLAN offload is supported. +- The UE is capable of IP address preservation in case of mobility between a 3GPP access and a Trusted WLAN. The UE is capable to request IP address preservation per PDN connection in case of mobility between a 3GPP access and a Trusted WLAN. +- The UE is capable of signalling the requested APN over Trusted WLAN, and the UE is capable of receiving the selected APN over Trusted WLAN (e.g. in case the UE did not indicate an APN). +- The UE is capable of indicating whether it requests a PDN connection or a NSWO connectivity service over Trusted WLAN, and the UE is capable of receiving an indication of whether the granted service is a PDN connection or NSWO connectivity (e.g. in case the UE did not indicate the kind of service it was requesting). A solution may also enable NSWO connectivity establishment only as the first connection. It is not required to release the NSWO connection without releasing the other connections. +- The solution should minimize the UE functional changes. + +## 8.1A Key issues + +- Regarding the feature of handover with IP address preservation. S2a already supports the hand-over indication that can be used by the TWAG to tell the PGW that the IP address is to be preserved. A solution is needed to enable the UE to provide to the TWAN an indication of whether the access to the TWAN corresponds to a “handover” (with IP address preservation) or “initial attach”. +- Regarding the feature of connecting to a non-default APN. Also here, S2a already supports this. The TWAN will also get all relevant APN profile information for this UE from the 3GPP AAA/HSS as part of the STa authentication and authorization process. A solution is needed to enable the UE to explicitly indicate which APN to connect to, and for the UE to be informed about the APN that the TWAN connected the UE to. +- Regarding the feature of the UE choosing between access to EPC and NSWO. Also here, the TWAN will also get all relevant APN profile information for this UE from the 3GPP AAA/HSS as part of the STa authentication and authorization process. A solution is needed for enabling the UE to indicate to the network whether an IP session is requested for EPC access or for non-seamless WLAN offload, and the network to respond whether the access request has been granted. +- Regarding the feature of the UE requesting a connection to an additional PDN. Also here, a solution is needed for the UE to request an additional PDN connection. Besides this, additional logic may be needed to correlate an individual user plane IP packet to an individual PDN connection. The solution shall take into account all situations and in particular when: + - 1) Two or more PDN connections from one UE might have the same IP address. This is in particular possible if these PDN connections are towards different PDN(s) using IPv4 private addressing. + - 2) Downlink (link layer) broadcasts do not include a specific UE target IP address (associated with a PDN connection). + - 3) Downlink IP multicast does not include a specific UE target IP address, and the sources of multicast services would have also the same IPv4 private address. + +The UE, the TWAG and/or the link between them, may need to implement means to cope with these situations. + +- Regarding the support for the same UE of simultaneous access to EPC through S2a and of non-seamless offload, similar considerations than for the support of simultaneous PDN connections apply. + +## 8.2 Solutions + +*Editor’s Note: This clause will describe the solution(s) for SaMOG Phase 2 study.* + +### 8.2.1 Solution 1: Tunnelled approach with dedicated UE-TWAG control protocol + +#### 8.2.1.1 Functional Description + +*Editor's Note: It should be described whether and how the solution fulfils the requirements in subclause 8.1.* + +##### 8.2.1.1.1 Overview + +This solution uses a two-scenario approach to support handover, non-default APN and multiple PDN connections: + +1. Single-connection scenario: In this scenario, the network or the UE only supports a single IP connection over WLAN. An IP connection is either a PDN connection or a NSWO connection. EAP signaling between UE and network is enhanced to carry attach parameters (e.g. handover indicator or APN or a request for NSWO). +2. Multi-connection scenario: In this scenario, the network and the UE both support multiple connections over WLAN. In the multi-connection scenario, a signaling protocol to manage PDN connections is needed. Also, a user-plane separation mechanism is needed to separate user-plane traffic between the different active PDN connections. A NSWO IP address or prefix is obtained through standard IETF procedures (i.e. DHCP or IPv6 Stateless Address Auto-configuration). + +Negotiation of which scenario to choose is done once as part of the attachment EAP signaling between UE and network. + +##### 8.2.1.1.2 User plane + +In the single-connection scenario, the PDN connection over WLAN uses the per-UE point-to-point link as defined in TS 23.402 clause 16. Such point-to-point link carries MAC frames. The MAC frame would typically carry an IP packet. IP is indicated by means of the “EtherType” field in the MAC header as defined in IEEE 802.1 (e.g. IPv4 is indicated by the Ethertype 0x0800). + +![](1dbb1d90b2022a3a765c85929a515cc6_img.jpg) + +| | | | +|-----|----|---------| +| MAC | IP | payload | +|-----|----|---------| + +**Figure 8.2.1.1.2-1 Frame format for the single-connection scenario** + +For the multi-connection scenario, there is at most one NSWO connection. For all PDN connections over WLAN, an additional layer between MAC and IP is used when carrying IP packets belonging to these connections. The MAC “Ethertype” field would in this case instead indicate “XYZ”, where “XYZ” is an identifier for the protocol that is used to include: 1) A key to differentiate the PDN connections from each other; 2) A next header indicator, which will be typically IP. The key is unique within the scope of a single UE. The key combined with the MAC address of the UE provides a globally unique identification for a PDN connection. The TWAG and the UE can use this identification to correlate a packet to the correct PDN connection. In the following two subsections, two alternatives are proposed for “XYZ”. + +*Editor's Notes: One of these two alternatives needs to be chosen. Which one is still FFS.* + +![](265d5cb06b401cf460a20fd2c93fd6d5_img.jpg) + +| | | | | +|-----|-------|----|---------| +| MAC | “XYZ” | IP | Payload | +|-----|-------|----|---------| + +**Figure 8.2.1.1.2-2 Frame format for PDN connections in the multi-connection scenario** + +##### 8.2.1.1.2.1 Alternative 1: XYZ = GRE + +In this alternative, XYZ is the GRE header as defined in IETF RFC 2890. The GRE key is used to differentiate the PDN connections from each other. This requires that GRE is defined by IEEE as new EtherType. + +As the access point is functioning like a layer-2 bridge, it forwards frames between its WiFi interface and its wired interface without checking the EtherType value. If the access point implements a mapping between IEEE 802.11e priorities and DSCP, then the DSCP will be found on a different offset for frames with EtherType GRE compared to frames with EtherType IPv4 or IPv6. + +#### 8.2.1.1.1.2.2 Alternative 2: XYZ = VLAN + +In this alternative, XYZ is an extension of the MAC header, forming a VLAN-tagged MAC header. The VLAN ID is used as key to differentiate the PDN connections from each other. + +The AP performs translation between the IEEE Std 802.11 air link and the IEEE 802 AP-TWAG segment e.g. using IEEE 802.11 integration service per IEEE 802.11-2007 appendix M. The solution relies on the VLAN ID to be carried un-modified to the TWAG. + +The VLAN ID used to distinguish PDN connections is encapsulated over the air in LLC SNAP and thus cannot be used for any other (non-3GPP) service differentiation over the air. + +As described in TS 23.402 clause 16, the WLAN AN enforces upstream and downstream forced-forwarding between the UE's WLAN IEEE 802.11 association and the TWAG. The way this forced-forwarding is enforced ensures that the VLAN ID used to multiplex TWAN connectivity services is in a different protocol stack layer than VLAN ID potentially used on the transport interface between the UE and the TWAG. + +The VLAN ID used to multiplex TWAN connectivity services is not used to route traffic on the path between the AP and the TWAG. + +If the access point implements a mapping between IEEE 802.11e priorities and DSCP, then the DSCP will be found on a different offset for VLAN-tagged frames compared to frames without VLAN tagging. + +#### 8.2.1.1.3 Control plane + +A UE-TWAG protocol is needed to control (i.e. setup and teardown) the per-PDN point-to-point link. This protocol is denoted as TSM (TWAN Session Management). TSM is a new protocol defined by 3GPP. The functions that WLCP supports include: Establishment of a per-UE-and-PDN point-to-point link; Tear down of a per-UE-and-PDN point-to-point link. + +As described in clause 8.2.1.1.1, a User Plane Connection ID (GRE key or VLAN ID) value is needed to differentiate PDN connections. When establishing a new per-UE-and-PDN point-to-point link using TSM, the network decides upon this User Plane Connection ID value and returns it to the UE. + +In the following two subsections, two alternatives to support the control protocol are proposed. + +**Editor's Notes: One of these two alternatives needs to be chosen. Which one is still FFS.** + +##### 8.2.1.1.3.1 Alternative 1: L2.5-based control protocol + +In this alternative, the following frame format is used for control plane messages. + +![](142bb586c6d72f1be78c75cea40ff7de_img.jpg) + +| | | | +|-----|-------|---------| +| MAC | "XYZ" | Payload | +|-----|-------|---------| + +**Figure 8.2.1.1.3.1-1 Frame format for PDN** + +##### **for L2.5-based control protocol** + +Just as for the user plane frames, the EtherType in MAC is set to "XYZ" (i.e. GRE or VLAN). As described in section 8.2.1.1.2, "XYZ" contains both a next header field (i.e. EtherType) and a key field (i.e. GRE key or VLAN ID). The EtherType field in "XYZ" is set to a new value for control plane signalling. It is required that IEEE defines such new value. The key field is set to a dedicated value. The payload contains the control protocol message. + +Alternatively, the EtherType in MAC is not set to "XYZ" but to a new value for control plane signalling. The "XYZ" part of the frame can then be omitted for control signalling. In that case, the frame for the control protocol would be as follows. + +![](32ff77da4286b58c4778033acaa10836_img.jpg) + +| | | +|-----|---------| +| MAC | Payload | +|-----|---------| + +Figure 8.2.1.1.3.1-2 Alternative frame format for PDN for + +### L2.5-based control protocol + +Editor's Notes: One of these two alternatives needs to be chosen. Which one is still FFS. + +If the UE is unaware of the TWAG MAC address, the first TSM message is sent in MAC broadcast to the TWAG. From the TWAG reply, the UE learns the TWAG MAC address. Alternatively, the TWAG MAC address is sent to the UE as part of the EAP-AKA' signalling. + +Editor's Notes: One of these two alternatives needs to be chosen. Which one is still FFS. + +### 8.2.1.1.3.2 Alternative 2: L3-based control protocol + +In this alternative, the following frame format is used for control plane messages. + +![](c79b9212cfc136d4191e637cd9437ffb_img.jpg) + +| | | | | +|-----|----|------------|---------| +| MAC | IP | TCP or UDP | Payload | +|-----|----|------------|---------| + +Figure 8.2.1.1.3.2-1 + +### Frame format for PDN for L3-based control protocol + +The payload contains the control protocol message. The IP address used is either the NSWO address, or a link-local address in case NSWO is not possible. A dedicated TCP or UDP port is used for control plane signalling. + +Editor's Notes: It is FFS if TCP or UDP is to be used. + +If the UE is unaware of the TWAG MAC address, the first TSM message is sent in MAC broadcast to the TWAG. If the UE is unaware of the TWAG IP address, the first TSM message is sent in IPv4 broadcast / IPv6 multicast to the TWAG. From the TWAG reply, the UE learns the TWAG MAC and IP address. Alternatively, the TWAG MAC and IP address is sent to the UE as part of the EAP-AKA' signalling. + +Editor's Notes: One of these two alternatives needs to be chosen. Which one is still FFS. + +## 8.2.1.1.4 Protocol Stacks + +Editor's Notes: Impact on link model due to handover support is FFS. + +## 8.2.1.2 Procedures + +### 8.2.1.2.1 Initial Attach in WLAN on S2a + +![Sequence diagram for Initial Attach in WLAN on S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with '1. Non-3GPP Specific Procedures' between UE and TWAN, followed by '2. EAP Authentication' between UE and TWAN. A large arrow labeled '2. Authentication & Authorization' spans from the UE/TWAN pair to the HSS/AAA, passing through the PDN GW and a 'Roaming Scenarios' box containing vPCRF, AAA Proxy, and hPCRF.](1cd762800fb629a48ed907cf73d794f4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note left of UE: 1. Non-3GPP Specific Procedures + UE->>TWAN: 2. EAP Authentication + Note right of TWAN: 2. Authentication & Authorization + TWAN->>PDN_GW: + PDN_GW->>vPCRF: + vPCRF->>AAA_Proxy: + AAA_Proxy->>hPCRF: + hPCRF->>HSS_AAA: + HSS_AAA-->>PDN_GW: + PDN_GW-->>TWAN: + TWAN-->>UE: + +``` + +Sequence diagram for Initial Attach in WLAN on S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with '1. Non-3GPP Specific Procedures' between UE and TWAN, followed by '2. EAP Authentication' between UE and TWAN. A large arrow labeled '2. Authentication & Authorization' spans from the UE/TWAN pair to the HSS/AAA, passing through the PDN GW and a 'Roaming Scenarios' box containing vPCRF, AAA Proxy, and hPCRF. + +Figure 8.2.1.2.1.1-1: Initial attachment in WLAN on GTP S2a for roaming and non-roaming scenarios + +The procedure is as TS 23.402 clause 16.2.1 with the following additions: + +- Step 2. As part of this step, the UE shall send an indication to the network whether it supports single-connection or multi-connection or both. If the UE supports the single-connection scenario, the UE also indicates whether it requests EPC access or non-seamless WLAN offload. If the UE requests EPC access, it may indicate APN. + +These indicators are sent in EAP-AKA to the 3GPP AAA. The 3GPP AAA sends these indicators to the TWAN. Depending on the capabilities of the network and the request of the UE, the network informs the UE as part of step 2 whether the single-connection scenario or the multi-connection scenario is selected. If both network and UE support both single-connection and multi-connection, then the network selects the multi-connection scenario. + +In case the single-connection scenario is selected, the procedure continues as described in clause 8.2.1.2.2. In case the multi-connection scenario is selected, the procedure continues as described in clause 8.2.1.2.3. + +#### 8.2.1.2.2 Initial Attach in single-connection scenario in WLAN on S2a (continuation) + +##### 8.2.1.2.2.1 Initial Attach in single-connection scenario in WLAN on GTP S2a (continuation) + +![Sequence diagram for Initial attachment in single-connection scenario in WLAN on GTP S2a for roaming and non-roaming scenarios.](9edb407536d4d4d4a6ac391527af047c_img.jpg) + +The diagram shows a sequence of interactions between the following entities: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled "Roaming Scenarios" encompasses vPCRF and AAA Proxy. The sequence is as follows: + +Top bar: Step 1-2 as in clause 8.2.1.2.1 + +**Scenario (A):** + +3. Create Session Request (TWAN to PDN GW) +4. IP-CAN Session Establishment Procedure (PDN GW to vPCRF/AAA Proxy/hPCRF) +5. Update PDN GW Address (AAA Proxy to HSS/AAA) +6. Create Session Response (PDN GW to TWAN) +7. GTP Tunnel (Established between TWAN and PDN GW, highlighted in green) +8. EAP authentication Completion (TWAN to UE) +9. L3 Attach (UE to TWAN) + +**Scenario (B):** + +10. Create Session Request (TWAN to PDN GW) +11. IP-CAN Session Establishment Procedure (PDN GW to vPCRF/AAA Proxy/hPCRF) +12. Update PDN GW Address (AAA Proxy to HSS/AAA) +13. Create Session Response (PDN GW to TWAN) +14. GTP Tunnel (Established between TWAN and PDN GW, highlighted in green) +15. L3 Attach Completion (UE to TWAN) + +Sequence diagram for Initial attachment in single-connection scenario in WLAN on GTP S2a for roaming and non-roaming scenarios. + +**Figure 8.2.1.2.2.1-1: Initial attachment in single-connection scenario in WLAN on GTP S2a for roaming and non-roaming scenarios** + +The procedure continues from step 2 in clause 8.2.1.2.1: + +- Step 2. As part of this step, the UE is made aware of the network support of SAMOG phase 2 features and if the requested connectivity feature (attach to non-default APN, non-seamless WLAN offload, EPC-routed traffic) is accepted by the network. Also, if the UE requested EPC access without indicating APN, then the network indicates the selected (default) APN. If the UE requested EPC access and indicated an APN, then the network verifies that it is allowed by subscription. If the UE requested NSWO and it was accepted by the network, steps + +3-7 and 10-14 are skipped. If the requested connectivity feature is not possible, the request is rejected with a relevant authorization failure. + +- Step 3 and step 10. The TWAN selects the PDN GW for the APN, and includes the APN in the Create Session Request. The APN is determined by the TWAN based on the UE request and on the subscription data received from the AAA server. + +NOTE: In the single-connection scenario, if a UE using NSWO wants to establish a PDN Connection, or if the UE has a PDN Connection but wants to use NSWO, the UE needs to detach from TWAN and make a new Initial Attach. + +#### 8.2.1.2.2.2 Initial Attach in single-connection scenario in WLAN on PMIP S2a (continuation) + +**Editor's Notes: This procedure is still to be added.** + +In case the multi-connection scenario is selected, the following applies: + +- Steps 3-7 and steps 10-14 are not performed. +- As part of step 2, the UE is made aware if the network supports attachment to non-default APN, and if the network supports handover. +- Non-seamless WLAN offload is possible if the network supports this and the UE is entitled to use this. As part of step 2, the UE is made aware whether or not non-seamless WLAN offload is possible. If non-seamless WLAN offload is possible, then the UE receives the address or prefix of the non-seamless WLAN offload connection as part of steps 9 and 15. If non-seamless WLAN offload is not possible, then step 9 and 15 are not performed. +- After the attach procedure, the procedure “UE-Initiated Connectivity to PDN in WLAN on S2a” in clause 8.2.1.2.2 may be performed to establish a PDN connection. +- Step 3 and step 10. If the UE indicated an APN in step 2, the TWAN verifies that it is allowed by subscription, selects the PDN GW for the APN correspondingly, and includes the APN in the Create Session Request. + +NOTE: In the single-connection scenario, if a UE using NSWO wants to establish a PDN Connection, or if the UE has a PDN Connection but wants to use NSWO, the UE needs to detach from TWAN and make a new Initial Attach. 8.2.1.2.3 Initial Attach in multi-connection scenario in WLAN on S2a (continuation) + +![Sequence diagram for Initial attachment in multi-connection scenario in WLAN on GTP S2a for roaming, and non-roaming scenarios. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF. The sequence starts with 'Steps 1-2 as in clause 8.2.1.2.1', followed by '8. EAP authentication Completion', '9. L3 Attach', and '15. L3 Attach Completion' between UE and TWAN. A dashed box at the bottom indicates step 16: 'Procedure "UE-Initiated Connectivity to PDN in WLAN on S2a" in clause 8.2.x.2.41'.](762a17cd79880dbca172bcbbe9375223_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note over UE, TWAN: Steps 1-2 as in clause 8.2.1.2.1 + Note over UE, TWAN: 8. EAP authentication Completion + Note over UE, TWAN: 9. L3 Attach + Note over UE, TWAN: 15. L3 Attach Completion + Note over UE, TWAN: 16. Procedure "UE-Initiated Connectivity to PDN in WLAN on S2a" in clause 8.2.x.2.41 + +``` + +Sequence diagram for Initial attachment in multi-connection scenario in WLAN on GTP S2a for roaming, and non-roaming scenarios. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box covers vPCRF, AAA Proxy, and hPCRF. The sequence starts with 'Steps 1-2 as in clause 8.2.1.2.1', followed by '8. EAP authentication Completion', '9. L3 Attach', and '15. L3 Attach Completion' between UE and TWAN. A dashed box at the bottom indicates step 16: 'Procedure "UE-Initiated Connectivity to PDN in WLAN on S2a" in clause 8.2.x.2.41'. + +**Figure 8.2.1.2.3-1: Initial attachment in multi-connection scenario in WLAN on GTP S2a for roaming, and non-roaming scenarios** + +The procedure continues from step 2 in clause 8.2.1.2.1: + +- Step 2. As part of this step, the UE is made aware of the network support of SAMOG phase 2 features. Non-seamless WLAN offload is possible if the network supports this and the UE is entitled to use this. As part of step 2, the UE is made aware whether or not non-seamless WLAN offload is possible. If non-seamless WLAN + +offload is possible, then the UE receives the address or prefix of the non-seamless WLAN offload connection as part of steps 9 and 15. If non-seamless WLAN offload is not possible, and the control protocol is L2.5-based, then step 9 and 15 are not performed. If non-seamless WLAN offload is not possible, and the control protocol is L3-based, then step 9 is not performed and in step 15 only a link-local IP address is configured. + +- Step 16. The procedure “UE-Initiated Connectivity to PDN in WLAN on S2a” in clause 8.2.1.2.4 may be performed to establish a PDN connection. + +After the attach procedure, the UE has at least one IP connection (either a NSWO connection or a PDN connection). + +#### 8.2.1.2.4 UE-Initiated Connectivity to PDN in WLAN on S2a + +##### 8.2.1.2.4.1 UE-Initiated Connectivity to PDN in WLAN on GTP S2a + +This procedure can only be performed if the multi-connection scenario was selected during authentication. + +This procedure is used when the UE has previously attached to WLAN and the UE wishes to establish one or more PDN connections over WLAN. This procedure is also used when the UE already has one or more PDN connections over WLAN and wishes to establish one or more additional PDN connections over WLAN. This procedure is also used to request for connectivity to an additional PDN connection over WLAN when the UE is simultaneously connected to WLAN and a 3GPP access, and the UE already has active PDN connections over both the accesses. The UE establishes a separate point-to-point link to the TWAG for each PDN connection. + +There can be more than one PDN connection per APN when GTP is used between the TWAN and the PDN GW. During the establishment of a new PDN connection, the TWAN allocates and sends a default S2a bearer ID to the PDN GW. The default S2a bearer ID is unique in the scope of the UE within a TWAG, i.e. the IMSI and the default S2a bearer ID together identify a PDN connection within a TWAG. In order to be able to identify a specific established PDN connection, both the TWAG and the PDN GW shall store the default S2a bearer ID. + +NOTE: The establishment of a connection to a PDN connection does not impact the NSWO connection if that was previously setup. As a separate point-to-point link is used for each PDN connection, traffic separation can be achieved between all connections including the NWSO connection. + +![Sequence diagram for UE-Initiated Connectivity to PDN in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW 1, PDN GW 2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It details the steps for establishing a new PDN connection, including session requests, IP-CAN session establishment, and GTP tunnel creation.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +The diagram illustrates the sequence of messages for UE-Initiated Connectivity to PDN in WLAN on GTP S2a. The participants are UE, TWAN, PDN GW 1, PDN GW 2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with an 'Existing PDN connection' (dashed box) between UE and PDN GW 1. Step 1: UE sends '1. Establishment new per-UE-and-PDN point-to-point link Request' to TWAN. Step 2: TWAN sends '2. Create Session Request' to PDN GW 2. Step 3: PDN GW 2 initiates '3. IP-CAN Session Establishment Procedure' (dashed box) involving vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Step 4: AAA Proxy sends '4. Update PDN GW Address' to hPCRF. Step 5: PDN GW 2 sends '5. Create Session Response' to TWAN. Step 6: TWAN and PDN GW 2 establish a '6. GTP Tunnel' (highlighted in green). Step 7: TWAN sends '7. Establishment new per-UE-and-PDN point-to-point link Response' to UE. Step 8: UE sends '8. L3 Attach' (dashed box) to TWAN. Step 9: TWAN sends '9. L3 Attach Completion' to UE. The diagram ends with 'Existing PDN connection' (dashed box) between UE and PDN GW 1, and a 'New PDN connection' (solid box) between UE and PDN GW 2. + +Sequence diagram for UE-Initiated Connectivity to PDN in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW 1, PDN GW 2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It details the steps for establishing a new PDN connection, including session requests, IP-CAN session establishment, and GTP tunnel creation. + +**Figure 8.2.1.4.2.1-1: UE-Initiated Connectivity to PDN in WLAN on GTP S2a** + +- Step 1. The UE triggers the establishment of a new per-UE-and-PDN point-to-point link by means of TSM. This step establishes the setup of a new per-UE-and-PDN-connection point-to-point link to the TWAG. The UE may indicate the requested APN. The UE triggers the re-establishment of an existing PDN connectivity by providing a handover indicator. In that case, it shall provide an APN. +- Step 2-6. Same as step 3-7 in clause 8.2.1.2.2.1. As part of these steps, the TWAN verifies that the APN requested by the UE is allowed by subscription. Upon handover, the TWAN selects the PDN GW handling this PDN connection; otherwise, the TWAN performs PDN GW selection as described in TS 23.402. Steps 2-6 are executed with the selected PDN GW. +- Step 7. By means of TSM, the TWAN returns a response to the establishment of a new per-UE-and-PDN point-to-point link. This response contains a User Plane Connection ID. If the UE did not indicate the APN in the request, then the response indicates the selected default APN. If the UE does not receive an IPv4 address in this step, it may negotiate the IPv4 address with DHCPv4 in step 8, +- Step 8. As step 9 in clause 8.2.1.2.2.1. +- Step 9. As step 15 in clause 8.2.1.2.2.1. + +#### 8.2.1.2.4.2 UE-Initiated Connectivity to PDN in WLAN on PMIP S2a + +**Editor's Notes: This procedure is still to be added.** + +### 8.2.1.2.5 Handover procedure in single-connection scenario from 3GPP access to WLAN on S2a + +#### 8.2.1.2.5.1 Handover in single-connection scenario from 3GPP access to WLAN on GTP S2a + +This procedure is used in the single-connection scenario to hand over a single PDN Connection from 3GPP access to WLAN. The decision to use the single-connection scenarios is made during authentication as described in clause 8.2.1.2.1. + +![Sequence diagram for handover from 3GPP to WLAN on GTP S2a. Entities: UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. Steps include EAP authentication, session creation, IP-CAN modification, and bearer release.](4346261cc730a1eb683f35e4ce9deacf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant SGW as S-GW + participant PGW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note over SGW, PGW: 0. GTP/PMIPv6 tunnel + Note over UE, TWAN: 1. Non-3GPP Specific Procedures + UE->>TWAN: 2. EAP Authentication + TWAN->>HSS_AAA: 2. Authentication & Authorization + + rect rgb(240, 240, 240) + Note right of TWAN: (A) + TWAN-->>PGW: 3. Create Session Request + PGW-->>vPCRF: 4. PCEF-initiated IP-CAN Session Modification + vPCRF-->>HSS_AAA: 5. Update PDN GW Address + PGW-->>TWAN: 6. Create Session Response + Note over SGW, PGW: 7. GTP Tunnel + end + + TWAN->>UE: 8. EAP authentication Completion + TWAN-->>UE: 9. L3 Attach + + rect rgb(240, 240, 240) + Note right of TWAN: (B) + TWAN-->>PGW: 10. Create Session Request + PGW-->>vPCRF: 11. PCEF-initiated IP-CAN Session Modification + vPCRF-->>HSS_AAA: 12. Update PDN GW Address + PGW-->>TWAN: 13. Create Session Response + Note over SGW, PGW: 14. GTP Tunnel + end + + TWAN->>UE: 15. L3 Attach Completion + UE->>SGW: 16. 3GPP EPS bearer release + PGW->>SGW: 16. 3GPP EPS bearer release + +``` + +Sequence diagram for handover from 3GPP to WLAN on GTP S2a. Entities: UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. Steps include EAP authentication, session creation, IP-CAN modification, and bearer release. + +**Figure 8.2.1.2.5.1-1: Handover in single-connection scenario from 3GPP access to Trusted WLAN on GTP S2a for roaming and non-roaming scenarios** + +The home routed roaming, LBO and non-roaming scenarios are depicted in the figure 8.2.1.2.5.1-1: + +- In the LBO case, the 3GPP AAA Proxy acts as an intermediary, forwarding messages from the 3GPP AAA Server in the HPLMN to the PDN GW in the VPLMN and vice versa. Messages between the PDN GW in the VPLMN and the hPCRF in the HPLMN are forwarded by the vPCRF in the VPLMN. + +- In the home routed roaming and non-roaming cases, the vPCRF and the 3GPP AAA Proxy are not involved, except for the authentication and authorization in step 2. + +The steps in figure 8.2.1.2.5.1-1 are based on figure 8.2.1.2.2.1-1, with the following changes: + +- Step 0. The UE is connected in the 3GPP Access and has a PMIPv6 or GTP tunnel on the S5/S8 interface. +- Step 2. As step 2 in 8.2.1.2.1.1 with the following addition: If the UE supports single-connection, then the UE indicates handover via EAP-AKA to 3GPP AAA. +- Step 3 and 10. As step 3 and 10 in 8.2.1.2.2.1 with the following addition: The handover indication is set in the Create Session Request to allow the PDN GW to re-allocate the same IP address or prefix that was assigned to the UE while it was connected to the 3GPP access and to initiate a PCEF-Initiated IP CAN Session Modification Procedure with the PCRF. +- Step 4 and 11. The PDN GW executes a PCEF-Initiated IP-CAN Session Modification Procedure with the PCRF as specified in TS 23.203 [4]. The Event Report indicates the change in Access Type. + +If the PDN GW decides to allocate a new IP address/prefix instead of preserving the old IP address/prefix, as described in TS 23.402 clause 4.1.3.2.3, the PDN GW executes an IP-CAN session Establishment Procedure with the PCRF instead of a PCEF-Initiated IP-CAN Session Modification Procedure. + +- Step 6 and 13. The PDN GW responds with a Create Session Response (PDN GW Address for the user plane, PDN GW TEID of the user plane, PDN GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, Charging ID, Cause). The Create Session Response contains the IP address and/or the prefix that was assigned to the UE while it was connected to the 3GPP IP access. The Charging Id provided by the PGW is the Charging Id previously assigned to the default bearer of the PDN connection in the 3GPP access. + - Step 16. The PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure in 3GPP access as defined in TS 23.402 clause 5.6.2.2 or the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401 [xx], clause 5.4.4.1. For connectivity to multiple PDN connections, the UE establishes connectivity to each PDN that is being transferred from 3GPP access, by executing the UE-initiated Connectivity to PDN procedure specified in clause 8.2.1.2.2.1. +- + +#### 8.2.1.2.5.2 Handover in single-connection scenario from 3GPP access to WLAN on PMIP S2a + +**Editor's Notes: This procedure is still to be added.** + +#### 8.2.1.2.6 Handover procedure in multi-connection scenario from 3GPP access to WLAN on S2a + +##### 8.2.1.2.6.1 Handover in multi-connection scenario from 3GPP access to WLAN on GTP S2a + +This procedure is used in the multi-connection scenario to hand over a one or more PDN Connection from 3GPP access to WLAN. The decision to use the multi-connection scenario is made during authentication as described in clause 8.2.1.2.1. + +![Sequence diagram for handover from 3GPP access to Trusted WLAN on GTP S2a for roaming and non-roaming scenarios. The diagram shows interactions between UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, and hPCRF. Step 0 shows a GTP/PMIPv6 tunnel between S-GW and PDN GW. Steps 1-15 are grouped on the UE/TWAN side, with step 2 involving authentication with the AAA Proxy. Step 16 is a dashed arrow from UE to PDN GW. Step 17 shows bearer release messages from both UE and PDN GW.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +The diagram illustrates the sequence of messages for a handover from 3GPP access to a Trusted WLAN. The participants are UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded region labeled 'Roaming Scenarios' encompasses the vPCRF, AAA Proxy, and hPCRF. The sequence starts with step 0, where a GTP/PMIPv6 tunnel is established between the S-GW and PDN GW. Steps 1 through 15 are grouped on the UE/TWAN side, with step 2 involving EAP authentication and authorization with the AAA Proxy. Step 16 is a dashed arrow representing UE-initiated connectivity to the PDN. Step 17 shows the 3GPP EPS bearer release from both the UE and the PDN GW. + +Sequence diagram for handover from 3GPP access to Trusted WLAN on GTP S2a for roaming and non-roaming scenarios. The diagram shows interactions between UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, and hPCRF. Step 0 shows a GTP/PMIPv6 tunnel between S-GW and PDN GW. Steps 1-15 are grouped on the UE/TWAN side, with step 2 involving authentication with the AAA Proxy. Step 16 is a dashed arrow from UE to PDN GW. Step 17 shows bearer release messages from both UE and PDN GW. + +**Figure 8.2.1.2.6.1-1: Handover from 3GPP access to Trusted WLAN on GTP S2a for roaming and non-roaming scenarios** + +The home routed roaming, LBO and non-roaming scenarios are depicted in the figure 8.2.1.2.6.1-1: + +- In the LBO case, the 3GPP AAA Proxy acts as an intermediary, forwarding messages from the 3GPP AAA Server in the HPLMN to the PDN GW in the VPLMN and vice versa. Messages between the PDN GW in the VPLMN and the hPCRF in the HPLMN are forwarded by the vPCRF in the VPLMN. +- In the home routed roaming and non-roaming cases, the vPCRF and the 3GPP AAA Proxy are not involved, except for the authentication and authorization in step 2. + +If the UE is connected to both 3GPP access and non-3GPP access before the handover of PDN connections to non-3GPP access is triggered, steps 1 to 15 shall be skipped and the UE shall only perform step 16 for each PDN connection that is being transferred from 3GPP access. + +If the UE is connected only to 3GPP access before the handover of PDN connections to non-3GPP access is triggered, steps 2 to 15 shall be performed. As described in clause 8.2.1.2.3, these steps result in the UE receiving the address or prefix of the non-seamless WLAN offload connection, if supported by the network for this UE. The UE shall then perform step 16 for each PDN connection that is being transferred from 3GPP access. + +Step 17 shall be repeated for each PDN connection that is being transferred from 3GPP access. Step 16 can occur in parallel for each PDN. Other aspects related to the handover for multiple PDNs are described in TS 23.402 clause 8.1. + +The steps in figure 8.2.1.2.6.1-1 are based on figure 8.2.1.2.3-1, with the following changes: + +- Step 0. The UE is connected in the 3GPP Access and has a PMIPv6 or GTP tunnel on the S5/S8 interface. +- Step 2. As step 2 in 8.2.1.2.1 with the following addition: The UE indicates handover via EAP to 3GPP AAA. + +- Step 16. For connectivity to multiple PDN connections, the UE establishes connectivity to each PDN that is being transferred from 3GPP access, by executing the UE-initiated Connectivity to PDN procedure specified in clause 8.2.11.2.2.14. +- Step 17. The PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure in 3GPP access as defined in TS 23.402 clause 5.6.2.2 or the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401 [6], clause 5.4.4.1. + +#### 8.2.1.2.6.2 Handover from 3GPP access to WLAN on PMIP S2a + +**Editor's Notes: This procedure is still to be added.** + +## 8.2.1.2.7 + +## Handover procedure from WLAN on S2a to 3GPP access + +![Sequence diagram of the handover procedure from Trusted WLAN on S2a to 3GPP access. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access/ePDG, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. The process involves UE discovery, attach, authentication, location update, session creation, bearer establishment, and non-3GPP bearer release. Two scenarios are highlighted: (A) for roaming and (B) for non-roaming.](df1966d80c74bc127f159a48f38b13ee_img.jpg) + +The sequence diagram illustrates the handover procedure from a Trusted WLAN on S2a to 3GPP access. The participants are: UE, Trusted Non-3GPP IP Access/ePDG, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. The process is divided into two main scenarios: (A) Roaming and (B) Non-roaming. + +**Sequence of Messages:** + +- 1. PMIPv6 or GTP Tunnel:** A tunnel is established between the Trusted Non-3GPP IP Access/ePDG and the PDN GW. +- 2. UE discovers 3GPP access system and initiates HO:** The UE discovers the 3GPP access system and initiates the handover. +- 3. Attach:** The UE sends an Attach request to the E-UTRAN. +- 4. Access Authentication:** The E-UTRAN sends an Access Authentication request to the UE, which is then forwarded by the MME to the AAA Proxy. +- 5. Location Update and Subscriber Data Retrieval:** The MME sends a Location Update and Subscriber Data Retrieval request to the HSS/AAA. +- 6. Create Session Request (MN-NAI, PDN GW):** The MME sends a Create Session Request to the Serving GW. +- 7. Create Session Request:** The Serving GW sends a Create Session Request to the PDN GW. +- 8. PCEF-Initiated IP-CAN Session Modification Procedure:** The PDN GW initiates a PCEF-Initiated IP-CAN Session Modification Procedure with the vPCRF. +- 9. Create Session Response:** The PDN GW sends a Create Session Response to the Serving GW. +- 10. Create Session Response (IP Addr):** The Serving GW sends a Create Session Response to the MME. +- 11. Radio and Access Bearer Establishment:** The MME sends a Radio and Access Bearer Establishment request to the E-UTRAN. +- 12. Modify Bearer Request:** The MME sends a Modify Bearer Request to the Serving GW. +- 13. Modify Bearer Request:** The Serving GW sends a Modify Bearer Request to the PDN GW. +- 14. Modify Bearer Response:** The PDN GW sends a Modify Bearer Response to the Serving GW. +- 15. Modify Bearer Response:** The Serving GW sends a Modify Bearer Response to the MME. +- 16. Radio and Access Bearer / GTP Tunnel:** A new Radio and Access Bearer (for the UE) and a new GTP Tunnel (between the Serving GW and PDN GW) are established. +- 17. UE Requested PDN Connectivity:** The UE sends a UE Requested PDN Connectivity request to the E-UTRAN. +- 18. Non-3GPP EPS Bearer Release:** The PDN GW initiates a Non-3GPP EPS Bearer Release procedure in the Trusted Non-3GPP IP Access/ePDG. + +**Scenarios:** + +- (A) Roaming:** This scenario involves the interaction between the Serving GW, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. +- (B) Non-roaming:** This scenario involves the interaction between the Serving GW and PDN GW. + +Sequence diagram of the handover procedure from Trusted WLAN on S2a to 3GPP access. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access/ePDG, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. The process involves UE discovery, attach, authentication, location update, session creation, bearer establishment, and non-3GPP bearer release. Two scenarios are highlighted: (A) for roaming and (B) for non-roaming. + +**Figure 8.2.1.2.7-1: Handover from Trusted WLAN on GTP S2a to 3GPP access for roaming and non-roaming scenarios** + +This procedure is as in TS 23.402 clause 8.2.1.1/8.2.1.2 with the following differences: + +- Step 1. There is a GTP or PMIP tunnel between TWAN and PGW +- Step 18. The PDN GW shall initiate resource allocation deactivation procedure in the TWAN as defined in clause 8.2.1.2.9. + +## 8.2.1.2.8 Detach and PDN disconnection in WLAN on S2a + +## 8.2.1.2.8.1 Detach and PDN disconnection in WLAN on GTP S2a + +## 8.2.1.2.8.1.1 UE/TWAN Initiated Detach and UE/TWAN requested PDN Disconnection Procedure in WLAN on GTP S2a + +For UE/TWAN initiated detach, this procedure is the same as TS 23.402 clause 16.3.1.1. + +If the single-connection scenario was selected during authentication, then the UE/TWAN requested PDN disconnection procedure is the same as TS 23.402 clause 16.3.1.1. + +If the multi-connection scenario was selected during authentication, then this clause applies to UE/TWAN-requested PDN disconnection procedure. For multiple PDN connections, this disconnection procedure shall be repeated for each PDN connection that needs to be released. + +![Sequence diagram of UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN. The diagram shows interactions between UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes AAA Proxv, vPCRF, and hPCRF. The procedure involves a PDN Disconnect Request from UE to TWAN, a Delete Session Request from TWAN to PDN GW, an Update PDN GW Address from PDN GW to HSS/AAA via AAA Proxv, a PCEF-Initiated IP-CAN Session Termination Procedure between PDN GW and vPCRF, a Delete Session Response from PDN GW to TWAN, a PDN Disconnect Response from TWAN to UE, a PDN Disconnection Request from TWAN to UE, a PDN Disconnection Response from UE to TWAN, and finally a TWAN specific resource Release Procedure between UE and TWAN.](9e4f582a5d5f6742d1372956db0f8f0b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant AAA_Proxv as AAA Proxv + participant vPCRF + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW: Roaming Scenarios + UE->>TWAN: 1. PDN Disconnect Request + TWAN->>PDN_GW: 2. Delete Session Request + PDN_GW->>AAA_Proxv: 3. Update PDN GW Address + AAA_Proxv->>HSS_AAA: 3. Update PDN GW Address + PDN_GW-->>vPCRF: 4. PCEF-Initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Delete Session Response + TWAN->>UE: 6. PDN Disconnect Response + TWAN->>UE: 7. PDN Disconnection Request + UE->>TWAN: 8. PDN Disconnection Response + Note left of PDN_GW: 9. TWAN specific resource Release Procedure + UE-->>TWAN: 9. TWAN specific resource Release Procedure + +``` + +Sequence diagram of UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN. The diagram shows interactions between UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes AAA Proxv, vPCRF, and hPCRF. The procedure involves a PDN Disconnect Request from UE to TWAN, a Delete Session Request from TWAN to PDN GW, an Update PDN GW Address from PDN GW to HSS/AAA via AAA Proxv, a PCEF-Initiated IP-CAN Session Termination Procedure between PDN GW and vPCRF, a Delete Session Response from PDN GW to TWAN, a PDN Disconnect Response from TWAN to UE, a PDN Disconnection Request from TWAN to UE, a PDN Disconnection Response from UE to TWAN, and finally a TWAN specific resource Release Procedure between UE and TWAN. + +**Figure 8.2.1.2.8.1.1-1: UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN** + +This procedure applies to the Non-Roaming, Home Routed Roaming and Local Breakout cases. In the Local Breakout case, the vPCRF forwards messages between the PDN GW and the hPCRF. In the LBO cases, the 3GPP AAA Proxy serves as an intermediary between the Trusted Non-3GPP IP Access and the 3GPP AAA Server in the HPLMN. In the non-roaming and Home Routed Roaming case, the vPCRF is not involved at all. + +If dynamic policy provisioning is not deployed, the optional steps of interaction between the PDN GW and PCRF do not occur. Instead, the PDN GW may employ static configured policies. + +- Step 1. If the PDN disconnection connection is initiated by the UE, the UE sends a PDN Disconnection Request (User Plane Connection ID) to the TWAG by means of TSM. + +- Step 2. The TWAN releases the PDN connection and sends a Delete Session Request (Linked EPS Bearer ID) message for this PDN connection to the PDN GW. +- Step 3. The PDN GW informs the 3GPP AAA Server of the PDN disconnection. +- Step 4. The PDN GW deletes the IP CAN session associated with the UE and executes a PCEF-Initiated IP-CAN Session Termination Procedure with the PCRF as specified in TS 23.203 [4]. +- Step 5. The PDN GW acknowledges with a Delete Session Response (Cause) message. +- Step 6. If the PDN disconnection was initiated by the UE in step 1, then the UE is informed of the disconnection by means of a TSM PDN Disconnection Response. +- Step 7. If the PDN disconnection was initiated by the TWAG, then the UE is informed of the disconnection by means of a TSM PDN Disconnection Request (User Plane Connection ID). +- Step 8. The UE acknowledges the disconnection request received in step 7. + +NOTE: Either step 1 and 6, or step 7 and 8, are performed + +#### 8.2.1.2.8.1.2 HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a + +This procedure is the same as TS 23.402 clause 16.3.1.2. + +#### 8.2.1.2.8.2 Detach and PDN disconnection in WLAN on PMIP S2a + +Editor's Notes: This procedure is still to be added. + +#### 8.2.1.2.9 PDN GW initiated Resource Allocation Deactivation + +##### 8.2.1.2.9.1 PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a + +**If the single-connection scenario was selected during authentication, then this procedure is the same as TS 23.402 clause 16.4.1.** + +If the network selected the multi-connection scenario during authentication, then this procedure is as in TS 23.402 clause 16.4.1 with the following difference: If all TWAN resources related to a PDN connection are released, then in step 3 the UE is informed of the PDN connection release using WLCP. + +##### 8.2.1.2.9.2 PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a + +Editor's Notes: This procedure is still to be added. + +#### 8.2.1.3 Impacts on existing nodes or functionality + +Editor's Note: Impact on existing nodes or functionality is still to be added. + +#### 8.2.1.4 Evaluation + +Editor's Note: The fulfilment to the requirements in subclause 8.1 should be evaluated. + +## 8.2.2 Solution 2: Layer 2 solution based on Stateful Address Configuration of Per-PDN Connection/NSWO Point-to-Point Link Multiplexed at Layer 2 + +### 8.2.2.1 Functional Description + +#### 8.2.2.1.1 User Plane Multiplexing for Per-PDN Connection / NSWO Point-to-Point Link + +**8.2.2.1.1.0 General** + +The solution relies on the use of Stateful Address Configuration of Per-PDN Connection / NSWO Point-to-Point Link Multiplexed at Layer 2. + +In addition to the two mechanisms described as part of this solution in subclause 8.2.2.1.1.1 (Per PDN/NSWO VLAN Id), and subclause 8.2.2.1.1.2 (Per PDN/NSWO TWAG MAC Address), any type of per-PDN/NSWO packet marking mechanism layered directly over L2 but below IPv4/IPv6 could be used with this solution, including, but not limited to, keyed GRE over Ethernet as described as part of Solution 1 in subclause 8.2.1, or a new 3GPP specific LLC/SNAP header as described as part of Solution 8 in subclause 8.2.8. + +Multiple PDN Connections to the same APN are supported via allocation of multiple identifiers (e.g. VLAN Ids) for multiple point-to-point links. + +#### 8.2.2.1.1.1 Per-PDN Connection/NSWO Virtual Point-to-Point Link Model based on distinct VLAN ID + +![Figure 8.2.2.1.1.1-1: Point-to-point link model for PDN connection and NSWO access based on distinct VLAN ID](b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg) + +The diagram illustrates the network architecture for User Plane Multiplexing. At the top is the Application / Service Layer. Below it, traffic flows are split into UL Traffic Flow Aggregates and DL Traffic Flow Aggregates. The path for Uplink (UL) goes from the UE through an AP/WLC, then to a TWAG, and finally to the PDN GW. The Downlink (DL) path is the reverse. Key mapping points include: APN/NSWO mapping to VLAN ID at the UE/AP interface; DL-TFT mapping to S2a-TEID at the PDN GW; and a central mapping of VLAN-ID ↔ S2a-TEID at the TWAG. The TWAG also connects to an NSWO cloud. The connection between TWAG and PDN GW is labeled as an S2a Bearer. + +Figure 8.2.2.1.1.1-1: Point-to-point link model for PDN connection and NSWO access based on distinct VLAN ID + +**Figure 8.2.2.1.1.1-1: Point-to-point link model for PDN connection and NSWO access based on distinct VLAN ID** + +In this link model the virtual point-to-point link required to transport traffic for a given PDN connection, of for Non-Seamless WLAN Offload (NSWO) is realized via the TWAG reserving a distinct VLAN ID that uniquely (on a per-UE basis) corresponds to an APN or NSWO. These distinct VLAN ID are configured on the TWAG interface, i.e., the TWAG can receive and send layer 2 frames from and to each of these VLAN ID. + +As depicted in Figure 8.2.2.1.1.1-1, the virtual point-to-point link is realized via enforcing forwarding of uplink and downlink IP packets between distinct PDN connections and NSWO access into their corresponding VLANs via marking layer 2 frame contacting these IP packets with the appropriate VLAN ID. VLAN marking over the IEEE Std 802.11 air link is performed as per Annex P of IEEE Std 802.11 [5]. + +On the UE, each of the virtual point-to-point link is modelled as a virtual interface that is exposed to the IP layer with a fixed IPv4 and/or IPv6 address(es). Applications can bind sockets to a specific virtual interface thus in effect binding the socket to a specific PDN connection or to NSWO access. Packet transmission occurs as follow: + +- In the uplink direction, all IP packets transmitted via the virtual interface, including IP multicast packets, are encapsulated in layer 2 frames marked with the VLAN ID that corresponds to the PDN connection or NSWO access the socket/interface is bound to. On the receiving side, the TWAG is able to demultiplex incoming packets towards the appropriate PDN connection or NSWO access via looking up the VLAN ID of the layer 2 data frame. +- In the downlink direction, the TWAG transmits all IP packets, including IP multicast packets, encapsulated in layer 2 frames marked with the VLAN ID that corresponds to the PDN connection or NSWO access the packet originated from. On the receiving side, the UE is able to demultiplex incoming packets towards the appropriate PDN connection or NSWO access via looking up the VLAN ID of the layer 2 data frame, and passes the IP packets contained in these frames to the IP layer via the corresponding virtual interface. + +#### 8.2.2.1.1.2 Per-PDN Connection/NSWO Virtual Point-to-Point Link Model based on distinct layer 2 TWAG MAC addresses + +![Diagram of Point-to-point link model for PDN connection and NSWO access. It shows an Application/Service Layer at the top. Below are UL and DL Traffic Flow Aggregates. The UE (User Equipment) is on the left, connected to an AP/WLC. The AP/WLC connects to a TWAG. The TWAG connects to a PDN GW via an S2a Bearer and also to an NSWO cloud. Various mapping functions are shown: APN/NSWO to TWAG-MAC for uplink, and DL-TFT to S2a-TEID for downlink. The link between UE and TWAG is labeled '802 Flow UE-MAC ↔ TWAG-MAC'.](ef5f5c6665b6ae13660ede412333ba45_img.jpg) + +The diagram illustrates the network architecture for the Per-PDN Connection/NSWO Virtual Point-to-Point Link Model. At the top, the 'Application / Service Layer' is shown as an oval. Below it, 'UL Traffic Flow Aggregates' (uplink) and 'DL Traffic Flow Aggregates' (downlink) are depicted with arrows pointing down and up respectively. The UE (User Equipment) on the left contains a multiplexing/demultiplexing structure. The UE is connected to an AP/WLC (Access Point/Wireless LAN Controller) via bidirectional arrows representing 802 flows. The AP/WLC is connected to a TWAG (Trusted WLAN Access Gateway). The TWAG is connected to the PDN GW (PDN Gateway) via an S2a Bearer. The TWAG is also connected to an NSWO (Non-Seamless WLAN Offload) represented by a dashed semi-circle. Labels indicate various mapping and identification components: APN/NSWO, APN/NSWO → TWAG-MAC, DL-TFT, DL-TFT → S2a-TEID, TWAG-MAC ↔ S2a-TEID, 802 Flow UE-MAC ↔ TWAG-MAC, and S2a Bearer. + +Diagram of Point-to-point link model for PDN connection and NSWO access. It shows an Application/Service Layer at the top. Below are UL and DL Traffic Flow Aggregates. The UE (User Equipment) is on the left, connected to an AP/WLC. The AP/WLC connects to a TWAG. The TWAG connects to a PDN GW via an S2a Bearer and also to an NSWO cloud. Various mapping functions are shown: APN/NSWO to TWAG-MAC for uplink, and DL-TFT to S2a-TEID for downlink. The link between UE and TWAG is labeled '802 Flow UE-MAC ↔ TWAG-MAC'. + +Figure 8.2.2.1.1.2-1: Point-to-point link model for PDN connection and NSWO access based on distinct layer 2 TWAG MAC addresses + +In this link model the virtual point-to-point link required to transport traffic for a given PDN connection, or for Non-Seamless WLAN Offload (NSWO) is realized via the TWAG reserving a distinct MAC address that uniquely (on a per-UE basis) corresponds to an APN or NSWO. These distinct layer 2 MAC addresses are configured on the TWAG interface, i.e., the TWAG can receive and send layer 2 frames from each of these MAC addresses. + +As depicted in Figure 8.2.2.1.1.2-1, the virtual point-to-point link is realized via enforcing a forced forwarding of uplink and downlink IP packets respectively to and from the corresponding layer 2 TWAG MAC address located in the layer 2 header of the frame containing the IP packets. + +On the UE, each of the virtual point-to-point link is modelled as a virtual interface that is exposed to the IP layer with a fixed IPv4 and/or IPv6 address(es). Applications can bind sockets to a specific virtual interface thus in effect binding the socket to a specific PDN connection or to NSWO access. Packet transmission occurs as follow: + +- In the uplink direction, all IP packets transmitted via the virtual interface, including IP multicast packets, are encapsulated in layer 2 frames with destination layer 2 address set to the layer 2 unicast MAC + +address of the TWAG that corresponds to the PDN connection or NSWO access the socket/interface is bound to. On the receiving side, after identifying the associated UE using the source MAC address of the data frame, the TWAG is able to demultiplex incoming packets towards the appropriate PDN connection or NSWO access via looking up the layer 2 destination address TWAG-MAC of the data frame. + +- In the downlink direction, the TWAG transmits all IP packets, including IP multicast packets, encapsulated in layer 2 frames with source layer 2 address set to the layer 2 unicast MAC address of the TWAG that corresponds to the PDN connection or NSWO access the packet originated from. On the receiving side, the UE is able to demultiplex incoming packets towards the appropriate PDN connection or NSWO access via looking up the layer 2 source unicast MAC address of the data frame, and passes the IP packets contained in these frames to the IP layer via the corresponding virtual interface. + +#### 8.2.2.1.2 Initial Attach in WLAN + +![Sequence diagram titled 'Initial Attach in WLAN' showing the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The diagram is divided into two main phases: 1. Non-3GPP Specific Procedures and 2. EAP authentication. A shaded box labeled 'Roaming Scenarios' covers the vPCRF, AAA Proxy, and hPCRF components. The sequence starts with the UE sending a message to the TWAN, followed by the TWAN sending an 'Authentication & Authorization' request to the PDN GW, which then interacts with the vPCRF, AAA Proxy, hPCRF, and HSS/AAA.](237b76118be454462fc9b4e96adaa6c7_img.jpg) + +Sequence diagram titled 'Initial Attach in WLAN' showing the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The diagram is divided into two main phases: 1. Non-3GPP Specific Procedures and 2. EAP authentication. A shaded box labeled 'Roaming Scenarios' covers the vPCRF, AAA Proxy, and hPCRF components. The sequence starts with the UE sending a message to the TWAN, followed by the TWAN sending an 'Authentication & Authorization' request to the PDN GW, which then interacts with the vPCRF, AAA Proxy, hPCRF, and HSS/AAA. + +**Figure 8.2.2.1.2-1: Initial Attach in WLAN on GTP or PMIP S2a for roaming, LBO and non-roaming scenarios** + +As depicted in Figure 8.2.2.1.2-1, the initial attach procedure occurs with the following steps: + +The first step of the proposal is for both the UE, the Trusted WLAN Access, and the 3GPP AAA Server in the HPLMN to discover whether all of them do support fully fledged Trusted WLAN Access to the EPC (i.e., as per the requirements, concurrent multiple PDN connections, IP address preservation, and concurrent NSWO and EPC access). This is done in the following way: + +1. The UE discovers the TWAN and associates with it. +2. The TWAN begins the EAP exchange by sending an EAP Request message as part of the IEEE 802.1X authentication procedure [5]. As part of the EAP exchange, the UE, the Trusted WLAN Access, and the 3GPP AAA Server in the HPLMN to discover whether all of them do support fully fledged Trusted WLAN Access to the EPC (i.e., as per the requirements, concurrent multiple PDN connections, IP address preservation, and concurrent NSWO and EPC access): + - a) The UE indicates support to the 3GPP AAA server in the HPLMN via including an indication EAP-AKA attribute in the EAP-AKA Response messages it sends. + - b) The Trusted WLAN Access indicates support to the 3GPP AAA server in the HPLMN via including an indication AAA attribute in the Diameter EAP-Request message it sends. + - c) The 3GPP AAA server in the HPLMN indicates to the Trusted WLAN Access that both itself and the UE have support via inclusion of the same indication AAA attribute in the Diameter EAP-Answer message it sends. + - d) The 3GPP AAA server in the HPLMN indicates to UE that both itself and the Trusted WLAN Access have support via inclusion of a similar indication attribute within the EAP-AKA Request message. + - e) If either of the UE, the Trusted WLAN Access Network, or the 3GPP AAA Server in the HPLMN support fully fledged Trusted WLAN Access to the EPC, failback to single PDN connection to a default per-subscription APN ensues (phase 1 SaMOG) as per steps 3-15 of subclause 16.2.1 of 3GPP TS 23.402 [3] in case of GTP S2a or subclause 16.2.2 of 3GPP TS 23.402 [3] in case of PMIP S2a. If on the other hand all of the UE, the Trusted WLAN Access Network, and the HPMLN support fully fledged Trusted WLAN Access to the EPC, neither PDN connections nor Non-Seamless WLAN + +Offload (NSWO) is offered automatically by the Trusted WLAN Access without explicit request from the UE as described in subclause 8.2.2.1.3. + +### 8.2.2.1.3 UE Requested PDN or NSWO connectivity + +The UE explicitly requests establishment of PDN connections and/or NSWO in two steps: preparation and execution. + +In a first preparation step, the UE queries from the network the values of the VLAN or TWAG MAC address to use to reach a list of APNs it might want to establish a PDN connection to in the future, including the unspecified 'default' APN that will be selected by the network (similar to the default APN that exists in phase 1 of SaMOG), as well as NSWO. The UE also indicates to the network the PDN Type of the PDN connection it will desire to establish. The signalling to carry on with this query from the UE to the network based on the use of EAP-AKA [22] extensions attributes during the authentication phase. As a result of this query, the network indicates to the UE a list of VLAN identifiers (first variant of the virtual point-to-point link model), TWAG MAC addresses (second variant of the virtual point-to-point link model), or any other point-to-point link multiplexing identifier (e.g., for keyed GRE or new 3GPP SNAP protocol) that corresponds to each of the APN in which it has expressed interest in connecting to (as well as the value that was selected by the network as the 'default' APN) on one hand, and to NSWO on the other hand. Again, the signalling to carry on with this indication from the network to the UE is based on the use of EAP-AKA extension attributes that are populated by the 3GPP AAA Server based on information received from the Trusted WLAN Access. A list of L2 identifiers for multiplexing of the point-to-point links is chosen locally by the TWAN based on configuration, and sent to the AAA server over STa. The AAA server extracts from this list as many L2 identifiers as there are PDN connections requested by the UE in the EAP Response/Identity, and includes it together with the authorized PDN types for those APN as per the subscription in the EAP Request/AKA-Challenge or AKA-Reauthentication message sent back to the UE, while the list of APNs for the PDN connections requested by UE is sent to the TWAN over STa. + +**Editor's note:** It is FFS how a UE that requests a dual IP version PDN Type IPv4v6 is informed that the established PDN connection has a single IP version PDN Type (i.e., IPv4, or IPv6) in cases where the selected PDN GW only allows single IP version PDN Type for this APN. + +If a UE expects to need multiple PDN connections to a single APN, it needs to requests multiple point-to-point link multiplexing identifiers for that same APN. The network may decide to respond fully to the request, or with a lesser number of point-to-point link multiplexing identifiers. + +**NOTE:** Because the values of the point-to-point link identifiers for the various APNs the UE wishes to connect to are negotiated during the EAP-AKA exchange, APNs need to be known prior to authentication with the Trusted WLAN Access. In the unlikely event that the UE needs to connect to an unforeseen APN, the UE would be required to disconnect, then reconnect, to the Trusted WLAN Access. + +**NOTE:** Because the values of the point-to-point link identifiers for the various APNs the UE wishes to connect to are negotiated during the EAP-AKA exchange, all this information needs to fit in a single EAP-AKA message. This places a limit on the number of the point-to-point links and APNs that can be negotiated. However given that on a 3GPP access a UE is also limited to a maximum of 12 simultaneous bearers, and hence PDN connections, it is deemed reasonable that for Trusted WLAN Access a limitation also exists. + +**NOTE:** In case where the subscription profile list the wildcard APN, the TWAN would need to send all APNs supported by an HPLMN (with corresponding VLAN IDs or TWAG MAC addresses) to the UE via EAP-AKA' or ANQP. + +![Sequence diagram for UE requested PDN or NSWO connectivity for GTP-based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows two main paths: GTP S2a (steps 3-7) and NSWO (step 3b).](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +The sequence diagram illustrates the interaction for GTP-based S2a connectivity. It begins with '1. Virtual Point-to-Point Link Creation' between UE and TWAN, followed by '2. L3 Address Request' from UE to TWAN. The TWAN sends '3. Create Session Request' to the PDN GW. A dashed box labeled '4. IP-CAN Session Establishment Procedure' spans between the PDN GW and the HSS/AAA, with a '5. Update PDN GW Address' message from the AAA Proxy to the HSS/AAA. The PDN GW then sends '6. Create Session Response' back to the TWAN. A green bar labeled '7. GTP Tunnel' is shown between the TWAN and PDN GW. A separate dashed box for '3b. NSWO Activation' is also shown. The final step is '8. L3 Address Reply' from TWAN to UE. The 'Roaming Scenarios' box includes vPCRF, AAA Proxy, and hPCRF. Labels (GTP S2a) and (NSWO) are on the right. + +Sequence diagram for UE requested PDN or NSWO connectivity for GTP-based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows two main paths: GTP S2a (steps 3-7) and NSWO (step 3b). + +Figure 8.2.2.1.3-1: UE requested PDN or NSWO connectivity for GTP-based S2a + +![Sequence diagram for UE requested PDN or NSWO connectivity for PMIP-based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows two main paths: PMIP S2a (steps 3-7) and NSWO (step 3b).](848073118eebfdbfdb9a60e3923fe0b3_img.jpg) + +The sequence diagram illustrates the interaction for PMIP-based S2a connectivity. It begins with '1. Virtual Point-to-Point Link Creation' between UE and TWAN, followed by '2. L3 Address Request' from UE to TWAN. The TWAN sends '3. Proxy Binding Update' to the PDN GW. A dashed box labeled '4. IP-CAN Session Establishment Procedure' spans between the PDN GW and the HSS/AAA, with a '5. Update PDN GW Address' message from the AAA Proxy to the HSS/AAA. The PDN GW then sends '6. Proxy Binding Ack' back to the TWAN. A green bar labeled '7. PMIP Tunnel' is shown between the TWAN and PDN GW. A separate dashed box for '3b. NSWO Activation' is also shown. The final step is '8. L3 Address Reply' from TWAN to UE. The 'Roaming Scenarios' box includes vPCRF, AAA Proxy, and hPCRF. Labels (PMIP S2a) and (NSWO) are on the right. + +Sequence diagram for UE requested PDN or NSWO connectivity for PMIP-based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows two main paths: PMIP S2a (steps 3-7) and NSWO (step 3b). + +Figure 8.2.2.1.3-2: UE requested PDN or NSWO connectivity for PMIP-based S2a + +In a second execution step, the UE explicitly requests establishment of a PDN connection to a specific APN or activation and deactivation of NSWO as per the following steps depicted in Figure 8.2.2.1.3-1 for GTP-based S2a and Figure 8.2.2.1.3-2 for PMIP-based S2a: + +1. The UE creates a virtual IP interface corresponding to the APN towards which it desires to establish a PDN connection, or to NSWO. +2. The UE requests allocation of an IPv4 and/or IPv6 address for this virtual interface by sending a DHCP or DHCPv6 request message from this virtual interface. In the first variant of the virtual point-to-point link model, the layer 2 frame carrying the DHCP is marked with the corresponding VLAN Id. In the second variant of the virtual point-to-point link model, the layer 2 frame carrying the DHCP message will be unicasted to the corresponding TWAG MAC address. + +NOTE: The UE may requests allocation of an IPv4 address via DHCP but still perform IPv6 Stateless Address Auto-Configuration (SLAAC) for configuration of its IPv6 address. In this case, the UE or the network signal the will to tear down a PDN connection and/or NSWO access based solely on DHCP signaling for the IPv4 address. + +- 3-7. When the TWAG receives the DHCP IPv4 and/or IPv6 address allocation request over the virtual interface corresponding to a specific VLAN (first variant of the virtual point-to-point link model) or TWAG MAC address (second variant of the virtual point-to-point link model), that corresponds to an APN it requests to the PDN GW creation of a GTP or PMIP tunnel for the APN as per steps 3-7 of respectively subclause 16.2.1 or 16.2.2 of 3GPP TS 23.402 [5] in case of GTP-based S2a or PMIP-based S2a, otherwise it activates NSWO if the virtual interface corresponds to NSWO access (step 3b). +8. The TWAG then sends a DHCP reply to the UE with an IPv4 address and/or IPv6 address as allocated by the PDN GW or by the NSWO access. The UE can then use the PDN connection via the virtual interface. Within the Trusted WLAN Access, the different virtual point-to-point links ensure separation of user plane traffic belonging to separate APNs and NSWO. The TWAG enforces forwarding between specific virtual point-to-point links and the GTP or PMIP tunnels towards the specific APNs, or NSWO access. + +#### 8.2.2.1.4 UE Requested PDN or NSWO disconnection + +![Sequence diagram for UE requested PDN or NSWO disconnection for GTP-based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves L3 Address Release, Delete Session Request, Update PDN GW Address, PCEF-initiated IP-CAN Session Termination Procedure, Delete Session Response, L3 Address Release Confirmation, and Virtual Point-to-Point Link Deletion. Two scenarios are highlighted: (GTP S2a) and (NSWO).](077f85b82901283b4657fd2b45fc0294_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of HSS_AAA: Roaming Scenarios + + Note right of HSS_AAA: (GTP S2a) + Note right of HSS_AAA: (NSWO) + + UE->>TWAN: 1. L3 Address Release + TWAN->>PDN_GW: 2. Delete Session Request + PDN_GW->>HSS_AAA: 3. Update PDN GW Address + Note right of PDN_GW: 4. PCEF-initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Delete Session Response + TWAN->>UE: 6. L3 Address Release Confirmation + Note left of UE: 7. Virtual Point-to-Point Link Deletion + +``` + +Sequence diagram for UE requested PDN or NSWO disconnection for GTP-based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves L3 Address Release, Delete Session Request, Update PDN GW Address, PCEF-initiated IP-CAN Session Termination Procedure, Delete Session Response, L3 Address Release Confirmation, and Virtual Point-to-Point Link Deletion. Two scenarios are highlighted: (GTP S2a) and (NSWO). + +Figure 8.2.2.1.4-1: UE requested PDN or NSWO disconnection for GTP-based S2a + +![Sequence diagram for UE requested PDN or NSWO disconnection for PMIP-based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves L3 Address Release, Proxy Binding Update, Update PDN GW Address, PCEF-initiated IP-CAN Session Termination Procedure, Proxy Binding Ack, L3 Address Release Confirmation, and Virtual Point-to-Point Link Deletion. The diagram is divided into two main sections: GTP S2a and NSWO.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW: Roaming Scenarios + + UE->>TWAN: 1. L3 Address Release + TWAN->>PDN_GW: 2. Proxy Binding Update (lifetime=0) + PDN_GW->>HSS_AAA: 3. Update PDN GW Address + Note right of HSS_AAA: (GTP S2a) + PDN_GW-->>AAA_Proxy: 4. PCEF-initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Proxy Binding Ack + Note right of TWAN: 2b. NSWO Disconnect + Note right of HSS_AAA: (NSWO) + TWAN->>UE: 6. L3 Address Release Confirmation + UE->>TWAN: 7. Virtual Point-to-Point Link Deletion + +``` + +Sequence diagram for UE requested PDN or NSWO disconnection for PMIP-based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves L3 Address Release, Proxy Binding Update, Update PDN GW Address, PCEF-initiated IP-CAN Session Termination Procedure, Proxy Binding Ack, L3 Address Release Confirmation, and Virtual Point-to-Point Link Deletion. The diagram is divided into two main sections: GTP S2a and NSWO. + +**Figure 8.2.2.1.4-2: UE requested PDN or NSWO disconnection for PMIP-based S2a** + +The UE explicitly requests disconnection of a PDN disconnection to a specific APN or deactivation of NSWO and deactivation of NSWO as per the following steps: + +1. The UE releases the IPv4 and/or IPv6 address allocated for the virtual interface by sending a DHCP or DHCPv6 release from this virtual interface. In the first variant of the virtual point-to-point link model, the layer 2 frame carrying the DHCP message is marked with the corresponding VLAN Id. In the second variant of the virtual point-to-point link model, the layer 2 frame carrying the DHCP message will be unicasted to the corresponding TWAG MAC address. +2. When the TWAG receives the DHCP IPv4 and/or IPv6 address release message over the virtual interface corresponding that corresponds to an APN, it requests to the PDN GW deletion of the GTP tunnel, or the PMIP tunnel for this APN as per steps 2-5 of respectively subclause 16.3.1.1 of 3GPP TS 23.402 [5] in case of GTP-based S2a, or subclause 16.3.2.1 of 3GPP TS 23.402 [5] in case of PMIP-based S2a, or disconnects NSWO if the virtual interface corresponds to NSWO (step 2b). +6. The TWAG then sends a DHCP reply to the UE to confirm release of the IPv4 address and/or IPv6 address for the PDN connection or the NSWO access. +7. The UE then deletes the virtual IP interface for the virtual point-to-point link corresponding the PDN connection, or to NSWO. + +### 8.2.2.1.5 HSS/AAA Initiated PDN or NSWO Disconnection procedure in WLAN + +![Sequence diagram for HSS/AAA Initiated Detach on GTP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a session termination request from HSS/AAA to TWAN, followed by a block of steps 2-5 from another figure, then an L3 Address Force Renew/Reconfigure from TWAN to UE, and finally a Session Termination Response from AAA Proxy to HSS/AAA. A 'Roaming Scenarios' box covers the PDN GW, vPCRF, and AAA Proxy lifelines.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +Sequence diagram for HSS/AAA Initiated Detach on GTP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a session termination request from HSS/AAA to TWAN, followed by a block of steps 2-5 from another figure, then an L3 Address Force Renew/Reconfigure from TWAN to UE, and finally a Session Termination Response from AAA Proxy to HSS/AAA. A 'Roaming Scenarios' box covers the PDN GW, vPCRF, and AAA Proxy lifelines. + +Figure 8.2.2.1.5-1: HSS/AAA Initiated Detach on GTP S2a + +![Sequence diagram for HSS/AAA Initiated Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a session termination request from HSS/AAA to TWAN, followed by a block of steps 2-5 from another figure, then an L3 Address Force Renew/Reconfigure from TWAN to UE, and finally a Session Termination Response from AAA Proxy to HSS/AAA. A 'Roaming Scenarios' box covers the PDN GW, vPCRF, and AAA Proxy lifelines.](a4bfa2343d75076b79f7e33d93915e00_img.jpg) + +Sequence diagram for HSS/AAA Initiated Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a session termination request from HSS/AAA to TWAN, followed by a block of steps 2-5 from another figure, then an L3 Address Force Renew/Reconfigure from TWAN to UE, and finally a Session Termination Response from AAA Proxy to HSS/AAA. A 'Roaming Scenarios' box covers the PDN GW, vPCRF, and AAA Proxy lifelines. + +Figure 8.2.2.1.5-2: HSS/AAA Initiated Detach on PMIP S2a + +The procedure for HSS/AAA Initiated Detach from TWAN is represented in Figure 8.2.2.1.5-1 in case of GTP-based S2a and Figure 8.2.2.1.5-2 in case of PMIP-based S2a and described below: + +- 1) The HSS/AAA sends a Session Termination Request message to the TWAN to detach a specific UE. +- 2) The step 2 to 5 of the UE/TWAN Initiated PDN or NSWO Disconnection procedure described in clause 8.2.2.1.4 are followed. +- 3) The TWAG force the UE to renew its IPv4 and/or IPv6 address(es) by sending a DHCP FORCERENEW message as per IETF RFC 3203 [24] or DHCPv6 Reconfigure message as per IETF RFC 3315 [23]. The DHCP FORCERENEW message is secured via Forcerenew Nonce Authentication as per RFC 6704 [29]. When the UE proceeds with renewing the address lease for the APN or NSWO, the TWAG can in turn refuse to do so, notifying to the UE that the PDN or NSWO has been disconnected. +- 4) TWAN sends a Session Termination Response message to 3GPP AAA Server. If the detach procedure was initiated from the 3GPP AAA Server and if the UE no longer has any context in the 3GPP AAA Server, the 3GPP AAA Server communicates this to the HSS as described in clause 12.1.2 of 3GPP TS 23.402 [5]. If the detach procedure was initiated by HSS, the 3GPP AAA Server replies to the HSS as described in clause 12.1.3 of 3GPP TS 23.402 [5]. + +### 8.2.2.1.6 HSS/AAA Initiated Detach procedure in WLAN + +This procedure is similar as per subclause 16.3.2.2.2 of 3GPP TS 23.402 [5]. + +### 8.2.2.1.7 Handover from 3GPP Access to Trusted WLAN Access + +![Sequence diagram for Handover from 3GPP Access to Trusted WLAN Access. The diagram shows the interaction between UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It details the steps for creating a virtual point-to-point link, sending a handover request, establishing a session, and releasing the 3GPP EPS bearer.](1f1614411edea7edfc86c839a608e1fc_img.jpg) + +The diagram illustrates the sequence of messages for a handover from 3GPP Access to Trusted WLAN Access. The participants are UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, and hPCRF. A dashed box labeled '(A) repeated for each PDN connection to same APN' encloses steps 3 through 7. + +- 0.** Initial state: Radio Bearer & S1/S4 bearer (GTP/PMIP tunnel). +- 1.** Virtual Point-to-Point Link Creation (UE to TWAN). +- 2.** Handover Request (UE to TWAN). +- 3.** Create Session Request / Proxy Binding Update (TWAN to PDN GW). +- 4.** IP-CAN Session Establishment Procedure (PDN GW to AAA Proxy). +- 5.** Update PDN GW Address (AAA Proxy to HSS/AAA). +- 6.** Create Session Response / Proxy Binding Ack (PDN GW to TWAN). +- 7.** GTP/PMIP Tunnel (PDN GW to TWAN). +- 8.** Handover Reply (TWAN to UE). +- 9.** 3GPP EPS Bearer Release (TWAN to UE and PDN GW to S-GW). + +Sequence diagram for Handover from 3GPP Access to Trusted WLAN Access. The diagram shows the interaction between UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It details the steps for creating a virtual point-to-point link, sending a handover request, establishing a session, and releasing the 3GPP EPS bearer. + +**Figure 8.2.2.1.7-1: Handover from 3GPP Access to Trusted WLAN Access** + +In a second execution step, the UE explicitly requests handover of a PDN connection to a specific APN as per the following steps depicted in Figure 8.2.2.1.7-1 for GTP-based S2a and Figure 8.2.2.1.7-2 for PMIP-based S2a: + +- The UE is connected in the 3GPP Access and has a GTP or PMIP tunnel on the S5/S8 interface. +- The UE creates a WLAN virtual IP interface corresponding to the APN towards which it desires to handover a PDN connection. +- The UE requests handover of the PDN connection from the 3GPP access to this WLAN virtual interface by sending a DHCP and/or DHCPv6 request message from this WLAN virtual interface that contains a handover indication for the PDN connection. The handover indication consists of requesting allocation of the same IPv4 address than previously allocated for the PDN connection over the 3GPP access, or of an IPv6 address within the same IPv6 prefix than previously allocated for the PDN connection over the 3GPP access. The DHCP requests are transmitted over the virtual point-to-point link negotiated during authentication phase, i.e., the layer 2 frame carrying the DHCP is marked with the corresponding VLAN Id, or unicasted to the corresponding TWAG MAC address, or encapsulated with the corresponding GRE key. + +**NOTE:** The UE is not required to request re-allocation of all addresses it had previously been allocated over the 3GPP access; a single request for one of the addresses that were used over the 3GPP access is enough to signal a handover indication to the TWAG. The UE may however request allocation for as many addresses as it wishes. Hence for an IPv4v6 PDN connection the handover indication signalling may be based entirely on DHCPv4 with no use of DHCPv6. If that is the case the UE may configure with Stateless Address Autoconfiguration the same IPv6 address than previously allocated with Stateless Address Autoconfiguration for the PDN connection over the 3GPP access based on receiving from the TWAG the same IPv6 prefix in a router advertisement. + +- When the TWAG receives the first DHCP IPv4 and/or IPv6 address allocation request with a handover indication over the virtual point-to-point link corresponding to a specific APN, it request the PDN GW handover of the corresponding GTP or PMIP tunnel for the PDN connection to that APN. This is done by sending a Create Session Request or Proxy Binding Update with the handover indication for each of the PDN connections to the same APN. In case of multiple PDN connections to a same APN, the steps 3-5 in + +(A) shall be repeated for each PDN connection to the same APN that is being transferred from 3GPP access to Trusted WLAN access. The steps in (A) can occur in parallel for each PDN connection.. + +4. The PDN GW initiates the IP-CAN Session Modification Procedure with the PCRF, as specified in TS 23.203 [19]. +5. The selected PDN GW informs the 3GPP AAA Server of its PDN GW identity and the APN corresponding to the UE's PDN Connection. The message includes information that identifies the PLMN in which the PDN GW is located. This information is registered in the HSS as described in clause 12. +6. The PDN GW returns a Create Session Response or a Proxy Binding Update message to the TWAG, including the IPv4 and/or IPv6 address(es) allocated for the UE. +7. The GTP or PMIP tunnel is set up between the TWAN and the PDN GW. +8. The TWAG then sends a DHCP reply to the UE with the IPv4 address and/or IPv6 address as re-allocated by the PDN GW. The UE can then continue to use the PDN connection via the WLAN virtual interface. + +#### 8.2.2.1.8 Handover from Trusted WLAN Access to 3GPP Access + +This procedure is as described in subclause 8.2.1.3 of TS 23.402 for GTP-based S5/S8, with the difference that there is a GTP tunnel instead of a PMIP tunnel in step 1 in case of GTP-based S2a, and that the resource allocation deactivation procedure initiated by the PDN GW in step 17 is as defined in clause 16.4 of TS 23.402, followed by the additional step of the UE then deleting the virtual IP interface for the virtual point-to-point link corresponding the PDN connection. + +#### 8.2.2.2 Impacts on existing nodes or functionality + +The UE shall support: + +- Creation and deletion of per-PDN/NSWO WLAN virtual interfaces for the chosen user plane multiplexing scheme (VLAN, or unicast L2) +- For IPv4 PDN connections: stateful address configuration mechanisms DHCP, DHCP Forcerenew, DHCP Forcerenew Nonce Authentication. +- For IPv4v6 PDN connections: stateful address configuration mechanisms DHCP, DHCP Forcerenew, DHCP Forcerenew Nonce Authentication, and/or DHCPv6. +- For IPv6 PDN connections: stateful address configuration mechanism DHCPv6 +- Enhanced EAP-AKA' method for negotiation of SaMOG phase 2 capabilities with the UE, and discovery of per-PDN user plane multiplexing identifier (VLAN Id, or TWAG MAC address) + +The TWAN shall support: + +- Creation and deletion of per-PDN/NSWO WLAN virtual interfaces for the chosen user plane multiplexing scheme (VLAN Id, or TWAG MAC address) +- For IPv4 PDN connections: stateful address configuration mechanisms DHCP, DHCP Forcerenew, DHCP Forcerenew Nonce Authentication. +- For IPv4v6 PDN connections: stateful address configuration mechanisms DHCP, DHCP Forcerenew, DHCP Forcerenew Nonce Authentication, and/or DHCPv6. +- For IPv6 PDN connections: stateful address configuration mechanism DHCPv6 +- Additional AVP for negotiation of SaMOG phase 2 capabilities with the AAA server, and discovery of per-PDN user plane multiplexing identifier (VLAN Id, or TWAG MAC address) + +The AAA server shall support: + +- Additional AVP for negotiation of SaMOG phase 2 capabilities with the TWAN, and discovery of per-PDN user plane multiplexing identifier (VLAN Id, or TWAG MAC address) +- Enhanced EAP-AKA' method for negotiation of SaMOG phase 2 capabilities with the UE, and discovery of per-PDN user plane multiplexing identifier (VLAN Id, or TWAG MAC address) + +### 8.2.2.3 Evaluation + +The following aspects are considered and evaluated for the solution: + +- i) Impacts to existing network deployment: + - a) There is no requirement for WLAN APs compared to Rel-11. + - b) The TWAG shall support the point-to-point link multiplexing, the EAP-AKA enhancements, and the binding of an IPv4 and/or IPv6 session(s) for stateful address configuration with a PDN connection. +- ii) Impacts to UE: + - a) The UE shall support the point-to-point link multiplexing, the AAA enhancements, and the binding of an IPv4 and/or IPv6 session(s) for stateful address configuration with a PDN connection. +- iii) Impacts to 3GPP protocols/extensions (e.g. EAP AKA'): + +The following protocols are extended: + + - a) EAP-AKA is extended with UE network capability negotiation and PDN point-to-point link management (APN, PDN type, point-to-point link identifiers) + - b) STa protocol is extended with UE network capability negotiation and PDN point-to-point link management (APN, PDN type, point-to-point link identifiers). +- iv) Impacts to protocols defined by other SDOs (e.g. DHCP): + +No impact on other SDOs. +- v) Control plane + - a) The latency/load of first PDN connection is as for phase 1 SaMOG, i.e., EAP-AKA based authentication and IP layer address configuration. The latency/load of additional PDN connections is less as it only requires IP layer configuration. + - b) There is impact on the AAA server as it needs to be enhanced with the EAP-AKA extensions and the STa extensions. +- vi) Compliance to clause 8.1 SaMOG phase-2 system requirements: + - a) Co-existence with Rel-11 SaMOG + - b) Support for IP address preservation during handover + - c) Simultaneous support for S2a EPC-routed and NSWO; support of simultaneous multiple PDN connections +- vii) Other functional limitations: + - a) Limitation on the number of point-to-point links to specific APNs that can be negotiated – but no different from limit on number of bearers on 3GPP access. + - b) Limitation that APNs the UE will connect to have to be known prior to WLAN authentication phase. Were it not the case, connection to an unforeseen APN when the UE is already authenticated to WLAN would + +require UE to disconnect and reconnect to the WLAN such that the new APN can be negotiated in EAP-AKA authentication. The UE disconnecting and reconnecting from WLAN may cause the UE to release existing PDN connections anchored over the TWAN. + +## 8.2.3 Solution 3: Stateful DHCP-based Solution + +### 8.2.3.1 Functional Description + +Editor's Notes: It should be described whether and how the solution fulfils the requirements in Subclause 8.1. + +NOTE: The solution does not support stateless auto-configuration DHCPv6. + +#### 8.2.3.1.1 Functional Overview and Overall System Impacts + +##### 8.2.3.1.1.1 Overview + +The following table summarizes the proposed solution with respect to the Rel-12 SaMOG system requirements. + +| Table | Requirements | | Solution | +|-----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Co-exist with the SaMOG Release 11 solution | <ul style="list-style-type: none"> <li>• R12 UE interworks with Rel-11 TWAN and vice versa</li> <li>• R12 TWAN supports both R11 and R12 UEs attaching to the same TWAG</li> <li>• 3GPP AAA updates PDN GW identification to support HO operation for Rel-12 UE</li> </ul> | <p>Supports UE Rel-12 capability Indication obtained from EAP-AKA'</p> <p>Based on prior detection of the UE's release version during the capability negotiation, 3GPP AAA determines whether to update PDN GW identification to support HO operation for Rel-12 UE</p> | +| Multiple simultaneous PDN connections over Trusted WLAN including the simultaneous support Non-seamless WLAN offload (NSWO) | Control Plane | | Via DHCP request message to trigger additional PDN connection establishment. | +| | User Plane compatible with existing PDN connections | | <ul style="list-style-type: none"> <li>• User data for Multiple EPC-routed PDN connections can be separated by GRE tunnel.</li> <li>• Differentiate NSWO traffic from EPC-routed connection(s) without GRE tunnel</li> <li>- Supporting NSWO, IPv4, IPv6 and dual-stack as specified in DHCP request and permitted by the 3GPP UE's subscription policy</li> </ul> | +| IP address preservation | Signalling handover indication for IP address preservation to TWAN and the IP address | | TWAN determines UE requirement of IP address preservation by special indication in DHCP request message | +| Signalling the requested APN over Trusted WLAN | | | UE signals APN using DHCP request message | + +#### 8.2.3.1.1.1 : Solution overview + +##### 8.2.3.1.1.2 UE Impacts + +For the purpose of accessing a Trusted Non-3GPP WLAN Access, the UE will be modified with the following enhancements with respect to Rel-11 UE: + +- Control Plane: + - Incorporate the requested APN, uplink GRE key, and HO indication in DHCP request message to communicate with TWAN/EPC. + - Support SAMOG phase 2 capabilities exchange and negotiation with TWAN during the EAP Authentication and Authorization operation. + - Indicate the desired connectivity service (NSWO access/ PDN connection), and receive the indication via DHCP response message. + +- Support IPv4, IPv6 and dual-stack PDN connection corresponding to the UE's subscription policy with its operator + - Support hand-over and release specific PDN connection or multiple PDN connections. + - Set-up and release the NSWO access. + - Support multiple simultaneous (TWAN) connectivity services i.e. both EPC-routed and NSWO simultaneously. + - Decide on the unique downlink GRE key for the EPC-routed traffic across all the PDN connections and sent it to TWAN, and also track the uplink GRE key that is assigned by the TWAN +- User Plane: +- Encapsulate and decapsulate GRE-over-IP tunnel for its EPC-routed PDN connection + - Simultaneous support for EPC-routed and NSWO traffic + +#### 8.2.3.1.1.3 Trusted WLAN Access Gateway Impacts + +The Trusted WLAN Access Gateway is enhanced with respect to Rel-11 TWAG with the following functions: + +- Control Plane: +- Support the TWAN side of the operations corresponding to UE's operation as described in clause 8.2.3.1.1.2 above. + - Binding the PDN connection for S2a GTP/PMIP tunnel. +- User Plane: +- Enforces routing of packets between the PDN connection and the GTP/PMIP tunnel for that UE. + - Encapsulate and decapsulate GRE-over-IP tunnel for its EPC-routed PDN connection + - Simultaneous support for EPC-routed and NSWO traffic + +#### 8.2.3.1.1.4 Trusted WLAN Access Point Impacts + +None + +#### 8.2.3.1.1.5 Trusted WLAN Backhaul Impacts + +Same as SaMOG Rel-11 + +### 8.2.3.1.2 Control Plane Management + +#### 8.2.3.1.2.1 UE-Network Capability Negotiation + +The UE negotiates SaMOG phase 2 capabilities with its serving TWAN during its EAP Authentication and Authorization operation. The TWAN sends UE requested SaMOG phase 2 capabilities and local TWAN configuration policies (i.e. whether supporting NSWO and/or EPC-routed) to the 3GPP AAA server over STa interface. The 3GPP AAA server takes a decision on whether or not the capabilities may apply to the UE session on the TWAN based on UE's subscription policy and local TWAN policies. + +#### 8.2.3.1.2.2 Connection related control plan interface + +DHCP protocol is used as the connection related control plane interface between the UE and the TWAG. It is the control plane protocol for UE to trigger the setup/maintain and release of any PDN or NSWO access among multiple connections: + +- Allows the UE to set-up (or Handover) and release a specific PDN or multiple PDNs. +- Allows the UE to set-up and release the NSWO access. + +NOTE 1: For DHCPv4 Forcerenew message used for releasing an individual PDN, RFC6704 [27] “DHCP Forcerenew nonce authentication” shall be used to provide secure client/server signaling exchange . + +NOTE 2: For DHCPv6, RFC 3315 [23] specifies security mechanism to protect client/server signaling exchange . + +- Allows the UE to have multiple simultaneous (TWAN) connectivity services. +- Allows the UE to indicate the desired connectivity service (NSWO access/PDN), whether an initial attach or a handover is required, the PDN type, etc. + +NOTE 3: 3GPP Vendor-specific Information that has been assigned by IETF for 3GPP for DHCPv4 and DHCPv6 can be used to provide DHCP enhancement as required by this solution. Hence, there is no impact to IETF. + +### 8.2.3.1.3 User plane management + +Basic assumption of SaMOG is to have point-to-point underlying transport between the UE and TWAG within the TWAN. However, when emulating multiple S2a PDNs support over TWAN, it is possible that several UE's serving PDN GWs could allocate the same private IP(v4) address to an UE. Hence, a user plane connection identifier is required to support multiplexing multiple PDNs over the point-to-point link between the UE and the TWAG to support TWAN connectivity service i.e. EPC-routed traffic. + +In the following two subsections, two alternatives are proposed for the user plane connection identifier. + +**Editor's Notes: For which of these two alternatives needs to be chosen is FFS.** + +#### 8.2.3.1.3.1 Alternative 1: GRE over IP + +##### 8.2.3.1.3.1.1 Point-to-point link model and multiple PDN connections support + +In this alternative, a unique pair of per-UE based GRE Keys in the uplink and in downlink direction is required for differentiating individual PDN. + +As there is no need to manage bearers over the WLAN access, a GRE Key at the user plane interface between the UE and the TWAG, corresponds to an entire PDN. When different GTP-u bearers are used on S2a for a given PDN, it is the same mechanism used in Rel-11 SaMOG to determine the GTP-u bearer to be used to carry a given packet i.e. the usage of UL-TFT at the UE and DL-TFT at the PGW. + +NOTE 1: The figures in the following sections depict the case of a PDN using a single bearer over S2a. + +![Diagram of point-to-point link model for PDN and NSWO access based on distinct GRE Key. It shows traffic flow from Application/Service Layer through PDN to GRE Keys, then through UE, AP/WLC, TWAG, and NSWO to PDN GW. Labels include UL Traffic Flow Aggregates, DL Traffic Flow Aggregates, PDN --> GRE Key, GRE Key <-> S2a-TEID, 802 Flow UE-MAC <-> TWAG-MAC, NSWO, and S2a Bearer.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +The diagram illustrates a network architecture for PDN and NSWO access. At the top, an oval labeled 'Application / Service Layer' is connected to 'UL Traffic Flow Aggregates' and 'DL Traffic Flow Aggregates'. These aggregates point to 'PDN --> GRE Key' labels. Below this, a 'PDN' label is present. The main part of the diagram shows a 'UE' (User Equipment) on the left connected to an 'AP/WLC' (Access Point/Wireless LAN Controller), which is connected to a 'TWAG' (TWAN Access Gateway). The 'TWAG' is connected to an 'NSWO' (Non-3GPP Wireless Network) represented by a dashed oval. The 'NSWO' is connected to a 'PDN GW' (PDN Gateway) on the right. Arrows indicate traffic flow: uplink (UL) from UE to PDN GW, and downlink (DL) from PDN GW to UE. Labels include 'PDN --> GRE Key' near the UE and AP/WLC, 'GRE Key <-> S2a-TEID' near the TWAG, '802 Flow UE-MAC <-> TWAG-MAC' between the AP/WLC and TWAG, and 'S2a Bearer' between the TWAG and PDN GW. + +Diagram of point-to-point link model for PDN and NSWO access based on distinct GRE Key. It shows traffic flow from Application/Service Layer through PDN to GRE Keys, then through UE, AP/WLC, TWAG, and NSWO to PDN GW. Labels include UL Traffic Flow Aggregates, DL Traffic Flow Aggregates, PDN --> GRE Key, GRE Key <-> S2a-TEID, 802 Flow UE-MAC <-> TWAG-MAC, NSWO, and S2a Bearer. + +**Figure 8.2.3.1.3.1.1-1: Point-to-point link model for PDN and NSWO access based on distinct GRE Key** + +As depicted in the Figure 8.2.3.1.3.1.1-1 above, there are separate uplink and downlink GRE Keys. The virtual point-to-point link corresponding to a given connectivity service is realized as enforcing the packet forwarding of uplink and downlink traffic from different PDNs of which the IP packets are identified by specific GRE Key. + +The solution described above supports one or multiple PDN(s) corresponding with one or more APN(s). + +**8.2.3.1.3.1.2 GRE over IP tunneling establishment** + +It is assumed that a given 3GPP UE is always hosted by only one TWAG within the TWAN. Both the UE and the TWAG guarantees the uniqueness of GRE Key across all the 3GPP UE's PDNs. Each PDN is identified by both uplink GRE Key and downlink GRE Key. + +Figure 8.2.3.1.3.1.2 -1 shows the user data encapsulated in GRE tunnel. + +![Sequence diagram showing encapsulation of UE EPC-routed traffic in GRE tunnels. The diagram illustrates four traffic paths: Tunnel A (EPC-routed) for UE1, Tunnel C (EPC-routed) for UE2, NSWO for UE2, and a native local IP addressing path for UE2. Each path shows the flow of traffic from the UE through the TWAG to the PDN GW, with specific GRE keys assigned for each tunnel.](5e9af8986a5845504f251d3079da8078_img.jpg) + +The diagram illustrates the encapsulation of UE EPC-routed traffic in GRE tunnels across different network configurations. The components involved are UE1, UE2, TWAG1, TWAG2, PDN GW1 (APN1), and PDN GW2 (APN2). + +- Tunnel A (EPC-routed):** UE1 sends traffic with [UE local IP-A@UE1, Serving UE TWAG's IP-A@TWAG1]. This traffic is encapsulated in a GRE tunnel with key [i, j, k, l] and is routed through TWAG1 to PDN GW1 (APN1). +- Tunnel C (EPC-routed):** UE2 sends traffic with [UE local IP-C@UE2, Serving UE TWAG's IP-C@TWAG2]. This traffic is encapsulated in a GRE tunnel with key [k, l] and is routed through TWAG2 to PDN GW2 (APN2). +- NSWO:** UE2 sends traffic with [UE local IP-D@UE2, Serving UE TWAG's IP-D@TWAG2]. This traffic is routed through TWAG2 to PDN GW1 (APN1) using a GRE tunnel with key [l]. +- No GRE key, native local IP addressing:** UE2 sends traffic with [UE local IP-D@UE2, Serving UE TWAG's IP-D@TWAG2]. This traffic is routed through TWAG2 to PDN GW2 (APN2) without GRE encapsulation. + +Sequence diagram showing encapsulation of UE EPC-routed traffic in GRE tunnels. The diagram illustrates four traffic paths: Tunnel A (EPC-routed) for UE1, Tunnel C (EPC-routed) for UE2, NSWO for UE2, and a native local IP addressing path for UE2. Each path shows the flow of traffic from the UE through the TWAG to the PDN GW, with specific GRE keys assigned for each tunnel. + +**Figure 8.2.3.1.3.1.2-1: Encapsulation of UE EPC-routed Traffic in GRE Tunnel** + +#### 8.2.3.1.3.2 Alternative 2: TWAG virtual MAC Address + +In this alternative, a TWAG virtual MAC address in the uplink and in downlink direction is required for differentiating individual PDN. + +As there is no need to manage bearers over the WLAN access, a TWAG virtual MAC address at the user plane interface between the UE and the TWAG, corresponds to an entire PDN. When different GTP-u bearers are used on S2a for a given PDN, it is the same mechanism used in Rel-11 SaMOG to determine the GTP-u bearer to be used to carry a given packet i.e. the usage of UL-TFT at the UE and DL-TFT at the PGW. On the UL direction, the TWAG uses both the source MAC address and the TWAG virtual MAC address to identify the S2a bearer on which the packet is to be forwarded. Two different UEs served by the same TWAG can share the same TWAG virtual MAC address. + +![Figure 8.2.3.1.3.2-1: Point-to-point link model for PDN and NSWO access based on TWAG VMAC. The diagram shows traffic flow from the Application / Service Layer through UL and DL Traffic Flow Aggregates into a UE and PDN GW respectively. The UE connects to an AP/WLC, which is linked to a TWAG. The TWAG connects to the PDN GW via an S2a Bearer. Labels include APN/NSWO, APN/NSWO -> VMAC, Source_MAC, TWAG VMAC, DL-TFT, DL-TFT -> S2a -TEID, S2a-TEID, NSWO, and S2a Bearer.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +Figure 8.2.3.1.3.2-1: Point-to-point link model for PDN and NSWO access based on TWAG VMAC. The diagram shows traffic flow from the Application / Service Layer through UL and DL Traffic Flow Aggregates into a UE and PDN GW respectively. The UE connects to an AP/WLC, which is linked to a TWAG. The TWAG connects to the PDN GW via an S2a Bearer. Labels include APN/NSWO, APN/NSWO -> VMAC, Source\_MAC, TWAG VMAC, DL-TFT, DL-TFT -> S2a -TEID, S2a-TEID, NSWO, and S2a Bearer. + +Figure 8.2.3.1.3.2-1: Point-to-point link model for PDN and NSWO access based on TWAG VMAC + +### 8.2.3.1.4 Protocol stack + +The following mobility protocols are supported over S2a: + +- GTP. +- PMIPv6. + +The link model as well as IPv4 address and IPv6 prefix allocation considerations are equally valid for GTP and PMIPv6 S2a options. + +The figure below illustrates the control plane for Tunnel Management and the user plane for GTP option. + +![Figure illustrating the control plane and user plane for Tunnel Management. The diagram is split into two sections: Control Plane for Tunnel Management and User Plane for Tunnel Management. The Control Plane shows the stack for GTP-C, UDP, IP, and L2/L1 between the UE (via SWw) and the PDN GW (via S2a). The User Plane shows the stack for IPv4/IPV6, GRE, IP, MAC/L1 between the UE (via SWw) and the PDN GW (via S2a), with an additional SGi interface on the PDN GW side.](a6f9ef297168667527ab18da412f917d_img.jpg) + +Figure illustrating the control plane and user plane for Tunnel Management. The diagram is split into two sections: Control Plane for Tunnel Management and User Plane for Tunnel Management. The Control Plane shows the stack for GTP-C, UDP, IP, and L2/L1 between the UE (via SWw) and the PDN GW (via S2a). The User Plane shows the stack for IPv4/IPV6, GRE, IP, MAC/L1 between the UE (via SWw) and the PDN GW (via S2a), with an additional SGi interface on the PDN GW side. + +**Legend:** + +**802.11:** This refers to Layer 1 and Layer 2 defined by IEEE Std 802.11-2007 [5]. + +**L3 trigger:** This refers to DHCPv4/DHCPv6 which is used as mandatory attach trigger. + +**GRE:** The GPE tunnels user data between UE and the Trusted WLAN Access Gateway over the SWw interface, which identifies specific the data per PDN connection by different GRE key. + +**GTP-C:** The GPRS Tunnelling Protocol control plane consists of signalling messages between the Trusted WLAN Access Gateway and the PDN- GW over the S2a interface. It is defined in TS 29.274 [25]. + +**GTP-U:** The GPRS Tunnelling Protocol user plane tunnels user data between the Trusted WLAN Access Gateway and the PDN GW over the S2a interface. It is defined in TS 29.281 [26]. + +**UDP:** This is the transport layer protocol onto which both GTP-C and GTP-U are layered. + +#### Figure 8.2.3.1.4-1: Link Model for GTP-based S2a + +When PMIP based S2a is used with Trusted WLAN, the PMIPv6 protocol stacks described in TS 23.402 clause 6.1.1 apply. + +##### 8.2.3.1.5 IP addressing support for SaMOG phase-2 + +This clause describes the IP addressing support for SaMOG phase-2 based on the stateful DHCP-based solution. The main scenarios for IP address/prefix assignment to UE are: + +- The IP address allocated by TWAN which is used for NSWO access +- The IP address allocated by TWAN for GRE over IP tunnelling the EPC routed traffic, +- The IPv4 address/IPv6 prefix allocated by PGW which is used for EPC routed. + +###### 8.2.3.1.5.1 IP address assignment for NSWO + +If the requested connectivity is for NSWO and the NSWO connectivity is allowed by the user subscription, the TWAN shall assign a NSWO IP address or prefix via DHCPv4 or DHCPv6 procedures. + +###### 8.2.3.1.5.2 IP address assignment for GRE over IP tunnel + +In the case when additional PDN connection is requested, and the multiple PDN connectivity is allowed, the TWAN shall assign the tunnel IP address via DHCPv4 if TWAN support IPv4; otherwise, the TWAN supports IPv6, the UE may generate link local address to be used for GRE over IP tunnelling. + +###### 8.2.3.1.5.3 IP address assignment for EPC-routed + +The IPv4 address and/or IPv6 prefix is allocated to the UE by PDN GW or external PDN when a new PDN connection is established. In order to enable IPv4 or IPv6 connectivity, the TWAN shall support DHCPv4 and DHCPv6 server functionality for IP parameter configuration and IPv4 address and/or IPv6 prefix allocation as specified in IETF RFC 2131 [9] and IETF RFC 3315 [23]. + +The way that the UE sets the requested PDN type is as specified in sub-clause 5.3.1.1 of 3GPP TS 23.401 [6]. + +The following IP address allocation procedure applies to the following conditions accordingly: + +- If the requested PDN type is allowed by the user subscription, the TWAN requests the PDN connectivity towards EPC as requested. +- If the requested PDN type is IPv4v6, but the subscription data allows only PDN type IPv4 or only PDN type IPv6, the TWAN requests IPv4 address or IPv6 prefix in the Proxy Binding Update or GTP Create Session Request from the PDN GW according to the subscribed value. The TWAN shall return the assigned PDN type to the UE. In this case the UE shall not request another PDN connection to the same APN for the other IP version. The IPv4 address or IPv6 prefix is delivered to the TWAN during the PMIPv6 or GTP tunnel establishment. + - When the UE requests the IPv4 address via DHCPv4, and if the subscription data allows PDN type IPv4, the TWAN delivers the received IPv4 address to the UE within DHCPv4 signalling after the PMIPv6 or GTP tunnel is established between the TWAN and the PDN GW. Otherwise, the subscription data allows only PDN type IPv6, TWAN will reject the request with a cause value that PDN type IPv6 only. + +- b). When the UE requests the IPv6 prefix via DHCPv6, and if the subscription data allows PDN type IPv6, the TWAN delivers the received IPv6 address to the UE within DHCPv6 signalling after the PMIPv6 or GTP tunnel is established between the TWAN and the PDN GW. Otherwise, the subscription data allows only PDN type IPv4, TWAN will reject the request with a cause value that PDN type IPv4 only. +- If the requested PDN type is IPv4 or IPv6, and if either the requested PDN type or PDN type IPv4v6 are subscribed, the TWAN requested the PDN connectivity from the PDN GW as requested. Otherwise the requested PDN connection request is rejected with the appropriate cause value. + - If the requested PDN type is IPv4v6, and both IPv4 and IPv6 PDN types are allowed by subscription but not IPv4v6, the TWAN shall decide for which the PDN type that it will request and such decision is operator's implementation decision. + +### 8.2.3.2 Procedures + +*Editor's Note: The call flows are described in this subclause.* + +#### 8.2.3.2.1 Initial Attach in WLAN on S2a + +##### 8.2.3.2.1.1 Initial Attach in WLAN on GTP/PMIP S2a + +![Sequence diagram for Initial Attach in WLAN on GTP/PMIP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes the PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The sequence starts with '1. Non-3GPP Specific Procedures' between UE and TWAN. Step 2 is 'EAP Authentication' between UE and TWAN, with a corresponding '2. Authentication & Authorization' between TWAN and AAA Proxy. Step 3 is 'DHCP Discover/ Solicit' from UE to TWAN. Step 4 is 'Create Session Request/PBU' from TWAN to PDN GW. Step 5 is a dashed box labeled '5. IP-CAN Session Establishment Procedure' between PDN GW and AAA Proxy. Step 6 is 'Update PDN GW Address' from AAA Proxy to HSS/AAA. Step 7 is 'Create Session Response/PBA' from PDN GW to TWAN. Step 8 is a green bar labeled '8. GTP Tunnel' between TWAN and PDN GW. Steps 9a, 9b, 10a, and 10b are DHCP-related messages between UE and TWAN.](45578bd3ed11d45af63ce00e28bab2f8_img.jpg) + +Sequence diagram for Initial Attach in WLAN on GTP/PMIP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes the PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The sequence starts with '1. Non-3GPP Specific Procedures' between UE and TWAN. Step 2 is 'EAP Authentication' between UE and TWAN, with a corresponding '2. Authentication & Authorization' between TWAN and AAA Proxy. Step 3 is 'DHCP Discover/ Solicit' from UE to TWAN. Step 4 is 'Create Session Request/PBU' from TWAN to PDN GW. Step 5 is a dashed box labeled '5. IP-CAN Session Establishment Procedure' between PDN GW and AAA Proxy. Step 6 is 'Update PDN GW Address' from AAA Proxy to HSS/AAA. Step 7 is 'Create Session Response/PBA' from PDN GW to TWAN. Step 8 is a green bar labeled '8. GTP Tunnel' between TWAN and PDN GW. Steps 9a, 9b, 10a, and 10b are DHCP-related messages between UE and TWAN. + +**Figure 8.2.3.2.1.1-1: Initial attachment in WLAN on GTP/PMIP S2a for roaming, LBO and non-roaming scenarios** + +The scenario is defined as the TWAN using the layer 3 attach request, including a DHCPv4 or DHCPv6 message, sent by the UE as the attach trigger. + +1. The step is same as step 1 in TS 23.402 [3] clause 16.2.1. + +2. In this step, the UE indicates its capability (i.e. Rel-12 SaMOG capability) to the AAA server during the authentication procedure. Based on the UE capability provided by AAA server, the TWAN decides to use L3 trigger. +3. The UE shall send a DHCPv4 Discover as per IETF RFC 2131 [9], or DHCPv6 Solicit as per IETF RFC 3315[23] to TWAN, including the following information, + - The requested APN + - An indication on the requested access (EPC via S2a access or the use of NSWO access) + - And in the former case, an APN optionally. + - For alternative 1, downlink GRE key may be inserted in 3GPP Vendor Specific information for IPv4, IPv6 or IPv4v6 connection. + - Requested PDN type – one of IPv4, IPv6 or IPv4v6 + +Based on HSS/AAA authorization and the received UE EPC/NSWO access indication whether or not to establish S2a, TWAN can decide to allow EPC access or not. All the UE traffic through the TWAG is blocked unless the UE is granted NSWO/PDN access. The following steps 4-8 proceed according to the considerations below. + +If UE doesn't provide an APN to TWAN, then: + +- A. If the TWAN decides NSWO access, steps 4-8 below are skipped. Instead, the TWAN assigns an IPv4 address and/or IPv6 address from its local address pool to the UE (depending on the L3 attach request in step 3) and the NSWO traffic will be forwarded/received without traversing EPC. +- B. If the TWAN decides S2a access, the TWAN assigns an IPv4 address and/or IPv6 address from its local address pool to the UE (depending on the L3 attach request in step 3). The TWAN shall request to PDN GW for an IPv4 address and/or IPv6 address and PDN GW shall return an IPv4 address and/or IPv6 address to the TWAN during steps 4-8. + +If UE provides its requested APN to TWAN, and the TWAN determines that S2a shall be established, the TWAN assigns an IPv4 address and/or IPv6 address from its local address pool to the UE (depending on the L3 attach request in step 3). The TWAN proceeds according to steps 4-8 below. + +4. TWAN decides PDN type according to requested PDN type and subscribed PDN type from HSS, and sets the Dual Address Bearer Flag when the PDN type is set to IPv4v6. The TWAN sends a Create Session Request/PBU message to the PDN GW, including PDN type, Dual Address Bearer Flag. +5. The step is same as step 10 in TS 23.402[3] clause 16.2.1. +6. The 3GPP AAA Server decides whether or not to update PDN GW identification according to the UE capability, which has been provided at the authentication phase. If the UE supports IP address preservation, the 3GPP AAA Server shall update PDN GW identity towards the HSS. +- 7-8. These steps are the same as steps 6-7 in TS 23.402[3] clause 16.2.1. If Dual Address Bearer Flag is set, the PDN GW shall return IPv4 address and IPv6 address to TWAN. +- 9a. For DHCPv4, TWAN returns DHCP offer message to UE, TWAG virtual MAC address is included if alternative 2 is used. +- 9b. For DHCPv6, TWAN returns Advertise message to UE, TWAG virtual MAC address is included if alternative 2 is used. +- 10a. UE sends DHCP Request (for DHCPv4) to TWAN, and TWAN returns DHCP Ack message to the UE, including the indication on whether EPC access or NSWO access has been granted to the UE and UE IP allocated by PDN GW. + - (a) Alternative 1: For EPC access, GRE tunnelling information is included to UE, where GRE tunnel information includes uplink GRE key and UE's local IP address which are allocated by TWAN for tunnelling data for the given PDN. For NSWO, GRE tunnelling information isn't required. + +- (b) Alternative 2: Both UE and TWAN maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address. For NSWO, no dedicated virtual MAC address is needed. + +All NSWO traffic and control messages between UE and TWAG use TWAG's MAC address. 10b. UE sends Request (for DHCPv6) to TWAN, and TWAN returns Reply message to the UE, including the indication on whether EPC access or NSWO access has been granted to the UE and UE IP allocated by PDN GW. + +- (a) Alternative 1: For EPC access, GRE tunnelling information is included to UE where GRE tunnel information includes uplink GRE key and UE's local IP address which are allocated by TWAN for tunnelling data for the given PDN. For NSWO, GRE tunnelling information isn't required.. + +- (b) Alternative 2: Both UE and TWAN will maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address. For NSWO, no dedicated virtual MAC address is needed. + +All NSWO traffic and control messages between UE and TWAG are using TWAG's MAC address. When PDN type is IPv4, steps 9a and 10a apply. + +When PDN type is IPv6, steps 9b and 10b apply. + +When PDN type is IPv4v6, there are two subsequent cases: + +- Alternative 1: + - 1) If UE requests IPv4 address first, TWAN shall implement steps 9a and 10a and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send solicit message encapsulated by the GRE key which is allocated in step 10a to TWAN, TWAN and UE shall implement steps 9b and 10b which are encapsulated by the GRE key which is allocated in step 10a. + - 2) If UE requests IPv6 address first, TWAN shall implement steps 9b and 10b and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message encapsulated by the GRE key which is allocated in step 10b to TWAN, TWAN and UE shall implement steps 9a and 10a which are encapsulated by the GRE key which is allocated in step 10b. +- Alternative 2: + - 1) If UE requests IPv4 address first, TWAN shall implement steps 9a and 10a and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send solicit message with TWAG virtual MAC address which is allocated in step 9a to TWAN, TWAN and UE shall implement steps 9b and 10b. + - 2) If UE requests IPv6 address first, TWAN shall implement steps 9b and 10b and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message with TWAG virtual MAC address which is allocated in step 9b to TWAN, TWAN and UE shall implement steps 9a and 10a. + +## 8.2.3.2.2 UE-initiated Connectivity to Additional PDN + +### 8.2.3.2.2.1 UE-initiated Connectivity to Additional PDN on GTP S2a + +![Sequence diagram showing UE-initiated connectivity to additional PDN from Trusted WLAN Access with GTP. The diagram includes lifelines for UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains vPCRF, AAA Proxy, and hPCRF. The sequence of messages is: 1. DHCP Discover/ Solicit (APN) from UE to TWAN; 2. Create Session Request from TWAN to PDN GW; 3. IP-CAN Session Establishment Procedure (dashed box) between PDN GW and AAA Proxy; 4. Update PDN GW Address from AAA Proxy to HSS/AAA; 5. Create Session Response from PDN GW to TWAN; 6. GTP Tunnel (highlighted in green) between PDN GW and TWAN; 7a. DHCP Offer from TWAN to UE; 7b. Advertise from TWAN to UE; 8a. DHCP Request/DHCP Ack from UE to TWAN; 8b. Request/ Reply from TWAN to UE.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +Sequence diagram showing UE-initiated connectivity to additional PDN from Trusted WLAN Access with GTP. The diagram includes lifelines for UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains vPCRF, AAA Proxy, and hPCRF. The sequence of messages is: 1. DHCP Discover/ Solicit (APN) from UE to TWAN; 2. Create Session Request from TWAN to PDN GW; 3. IP-CAN Session Establishment Procedure (dashed box) between PDN GW and AAA Proxy; 4. Update PDN GW Address from AAA Proxy to HSS/AAA; 5. Create Session Response from PDN GW to TWAN; 6. GTP Tunnel (highlighted in green) between PDN GW and TWAN; 7a. DHCP Offer from TWAN to UE; 7b. Advertise from TWAN to UE; 8a. DHCP Request/DHCP Ack from UE to TWAN; 8b. Request/ Reply from TWAN to UE. + +**Figure 8.2.3.2.2.1-1: UE-initiated connectivity to additional PDN from Trusted WLAN Access with GTP** + +The scenario is defined as the TWAN using the layer 3 attach request, including DHCPv4 or DHCPv6 message, sent by the UE as the PDN trigger. NSWO is a special PDN. + +For DHCPv4 messaging and security handling, RFC 6704 shall be applied. + +1. The UE shall send layer 3 attach request to the TWAN, (e.g. a DHCPv4 discover as per IETF RFC 2131 [9], DHCPv6 Solicit as per IETF RFC3315 [23]), including requested APN, requested PDN type and an indication on the requested access (EPC via S2a access or the use of NSWO access), and for alternative 1, the downlink GRE key if EPC via S2a access. + +If UE doesn't send UE requested APN to TWAN, the TWAN determines whether or not to grant NSWO connectivity based on the authorization result during initial attach: + +- If TWAN determines NSWO and there isn't a existing NSWO access, TWAN forwards the traffic without traversing EPC. Otherwise, the NSWO access isn't allowed. + - If UE provides its requested APN to TWAN, and the TWAN determines that S2a shall be established, the TWAN proceeds according to steps 2-6 below. +2. TWAN decides PDN type according to requested PDN type and subscribed PDN type from HSS, and sets the Dual Address Bearer Flag when the PDN type is set to IPv4v6. The TWAN sends a Create Session Request message to the PDN GW, including PDN type, Dual Address Bearer Flag. + 3. The step is same as step 10 in TS 23.402[3] clause 16.2.1. + +4. The 3GPP AAA Server decides whether or not to update PDN GW identification according to the UE capability, which has been provided at the authentication phase. If the UE supports IP address preservation, the 3GPP AAA Server shall update PDN GW identity towards the HSS. +- 5-6. These steps are the same as steps 6-7 in TS 23.402[3] clause 16.2.1. If Dual Address Bearer Flag is set, the PDN GW shall return both IPv4 address and IPv6 address to TWAN. +- 7a. For DHCPv4, TWAN returns DHCP offer message to UE, TWAG virtual MAC address is included if alternative 2 is used. +- 7b. For DHCPv6, TWAG returns Advertise message to UE, TWAG virtual MAC address is included if alternative 2 is used. +- 8a. UE sends DHCP Request (for DHCPv4) to TWAN, and TWAN returns DHCP Ack message to the UE, including the indication on whether EPC access or NSWO access has been granted to the UE and UE's IP allocated by its serving PDN GW. + - 1) Alternative 1: For EPC access, GRE tunnelling information included to UE where GRE tunnel information includes uplink GRE key allocated by TWAN for tunnelling data for the given PDN. For NSWO, GRE tunnelling information isn't required. + - 2) Alternative 2: Both UE and TWAN maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address. For NSWO, no dedicated virtual MAC is needed. + +All NSWO traffic and control messages between UE and TWAG are using TWAG's MAC address. + +- 8b. UE sends Request (for DHCPv6) to TWAN, and TWAN returns Reply message to the UE, including the indication on whether EPC access or NSWO access has been granted to the UE and UE's IP address allocated by its serving PDN GW. + - 1) Alternative 1: For EPC access, GRE tunnelling information and UE's IP address allocated by its serving PDN GW are included to UE where GRE tunnel information includes uplink GRE key which is allocated by TWAN for tunnelling support in the case of multiple PDNs. For NSWO, GRE tunnelling information isn't required. + - 2) Alternative 2: Both UE and TWAN maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address etc.. For NSWO, no dedicated virtual MAC address is needed. + +All NSWO traffic and control messages between UE and TWAG are using TWAG's MAC address. + +When PDN type is IPv4, steps 7a and 8a apply. + +When PDN type is IPv6, steps 7b and 8b apply. + +When PDN type is IPv4v6, there are two following cases: + +- Alternative 1: + - 1) If UE requests IPv4 address first, TWAN shall implement steps 7a and 8a and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send solicit message encapsulated by the GRE key which is allocated in step 8a to TWAN, TWAN and UE shall implement steps 7b and 8b which are encapsulated by the GRE key which is allocated in step 8a. + - 2) If UE requests IPv6 address first, TWAN shall implement steps 7b and 8b and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message encapsulated by the GRE key which is allocated in step 8b to TWAN, TWAN and UE shall implement steps 7a and 8a which are encapsulated by the GRE key which is allocated in step 8b. +- Alternative 2: + - 1) If UE requests IPv4 address first, TWAN shall implement steps 9a and 10a and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send solicit message with TWAG virtual MAC address which is allocated in step 9a to TWAN, TWAN and UE shall implement steps 9b and 10b. + - 2) If UE requests IPv6 address first, TWAN shall implement steps 9b and 10b and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message with + +TWAG virtual MAC address which is allocated in step 9b to TWAN, TWAN and UE shall implement steps 9a and 10a. + +#### 8.2.3.2.2.2 UE-initiated Connectivity to Additional PDN on PMIP S2a + +![Sequence diagram for UE-initiated connectivity to additional PDN on PMIP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, and hPCRF. The process involves DHCP discovery, Proxy Binding Update, IP-CAN session establishment, and subsequent DHCP offer/advertisement and request/reply messages.](cf018d13814389b0bd7f94a2f9bb812a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW: Roaming Scenarios + + UE->>TWAN: 1. DHCP Discover/ Solicit (APN) + TWAN->>PDN_GW: 2. Proxy Binding Update + PDN_GW-->>AAA_Proxy: 3. IP-CAN Session Establishment Procedure + AAA_Proxy->>HSS_AAA: 4. Update PDN GW Address + HSS_AAA-->>PDN_GW: 5. Proxy Binding Acknowledgement + Note right of PDN_GW: 6. PMIP Tunnel + PDN_GW-->>UE: 7a. DHCP Offer + PDN_GW-->>TWAN: 7b. Advertise + UE->>PDN_GW: 8a. DHCP Request/DHCP Ack + TWAN-->>UE: 8b. Request/ Reply + +``` + +Sequence diagram for UE-initiated connectivity to additional PDN on PMIP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, and hPCRF. The process involves DHCP discovery, Proxy Binding Update, IP-CAN session establishment, and subsequent DHCP offer/advertisement and request/reply messages. + +**Figure 8.2.3.2.2.2-1: UE-initiated connectivity to additional PDN from Trusted WLAN Access with PMIP** + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.2.1 above, with the following differences: + +- Step 2 is a Proxy Binding Update. The parameters in the Proxy Binding Update message are same as step 5 in clause 8.2.3.2.2.1. +- Step 5 is a Proxy Binding Acknowledgement. The parameters in the Proxy Binding Acknowledgement message are same as step 6 in clause 8.2.3.2.2.1. + +### 8.2.3.2.3 Detach and PDN disconnection in WLAN on S2a + +#### 8.2.3.2.3.1 Detach and PDN disconnection in WLAN on GTP S2a + +##### 8.2.3.2.3.1.1 UE/TWAN requested single PDN Disconnection Procedure in WLAN on GTP S2a + +![Sequence diagram for UE/TWAN requested single PDN Disconnection Procedure in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with a DHCP release from UE to TWAN, followed by a Delete Session Request from TWAN to PDN GW. The PDN GW then sends an Update PDN GW Address to HSS/AAA. A PCEF-initiated IP-CAN Session Termination Procedure is initiated between PDN GW and AAA Proxy. The PDN GW sends a Delete Session Response to TWAN, which then sends a DHCP Reply to UE. Finally, a TWAN Specific resource release is performed between UE and TWAN.](efb282bed9f06eef1987a14fb27bc599_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW: Roaming Scenarios + UE->>TWAN: 1. DHCP release + TWAN->>PDN_GW: 2. Delete Session Request + PDN_GW->>HSS_AAA: 3. Update PDN GW Address + PDN_GW-->>AAA_Proxy: 4. PCEF-initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Delete Session Response + TWAN->>UE: 6. DHCP Reply + Note left of TWAN: 7. TWAN Specific resource release + +``` + +Sequence diagram for UE/TWAN requested single PDN Disconnection Procedure in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process starts with a DHCP release from UE to TWAN, followed by a Delete Session Request from TWAN to PDN GW. The PDN GW then sends an Update PDN GW Address to HSS/AAA. A PCEF-initiated IP-CAN Session Termination Procedure is initiated between PDN GW and AAA Proxy. The PDN GW sends a Delete Session Response to TWAN, which then sends a DHCP Reply to UE. Finally, a TWAN Specific resource release is performed between UE and TWAN. + +**Figure 8.2.3.2.3.1.1-1: UE/ TWAN requested single PDN Disconnection on GTP S2a** + +1. If the PDN Type is IPv4, UE releases the IPv4 address using DHCPv4 release message or IPv4 address lease time expires in TS23.402 [3] clause 16.3. And if the PDN Type is IPv6, UE releases the IPv6 address using DHCPv6 release message or IPv6 address lease time expires. If the PDN Type is IPv4v6, UE shall releases the IPv4 address and IPv6 address by the first DHCP release session, i.e. DHCPv4 release message or DHCPv6 release message, with PDN Type for IPv4v6 is included in the message. + - Alternative 1: +For DHCPv4 release message, a specific GRE key or a client id is used for identifying specific PDN. +For DHCPv6 release message, a specific GRE key or IAID is used for identifying specific PDN. + - Alternative 2: + +For DHCPv4 release message, TWAG virtual MAC address is used for identifying specific PDN. + +For DHCPv6 release message, TWAG virtual MAC address is used for identifying specific PDN. + +If there is no traffic received from the UE for a configurable duration and the TWAN detects the UE has left based on unanswered probes (e.g., ARP Request, Neighbour Solicitation message), the TWAN triggers PDN disconnection. + +2-5. After TWAN receives DHCP release message, it shall detect if the PDN supports IPv4v6 dual stack and PDN type for IPv4v6 is included in the message. If so, TWAN shall send delete session request message to PDN GW, in order to indicate PDN GW for deleting the PDN. Steps 3-5 are same as the steps 2-5 in TS23.402 [3] clause 16.3.1.1. + +6. TWAN shall remove the associated contexts corresponding to specific PDN, and send Reply message to inform UE of removing associated contexts in the case of DHCPv6. + +7. If TWAN requested Single PDN Disconnection, TWAN shall send a DHCPv4 FORCERENEW message as per IETF RFC 3203 [24] and RFC6704[27], and/or DHCPv6 Reconfigure message as per IETF RFC 3315 [23]. When the UE proceeds with renewing the address lease for single PDN, the TWAN shall in turn refuse the request and notify to the UE that the PDN has been disconnected. + +NOTE: For PDN type is IPv4v6, it is FFS. + +###### 8.2.3.2.3.1.2 UE/TWAN requested one IPv4 Address or one IPv6 address release for a dual stack PDN in WLAN on GTP S2a + +![Sequence diagram for UE/TWAN initiated release for one IPv4 Address or one IPv6 Address for dual stack PDN in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW1, PDN GW2, VPCRF, AAA Proxy, HPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains VPCRF, AAA Proxy, and HPCRF. The sequence of messages is: 1. DHCP release (UE to TWAN), 2. Modify Bearer Request (TWAN to PDN GW1), 3. PCEF-initiated IP-CAN Session Modification Procedure (PDN GW1 to VPCRF), 4. Modify Bearer Response (VPCRF to PDN GW1), 5. DHCP Reply (PDN GW1 to UE), and 6. TWAN Specific resource release (TWAN to UE).](68dad113f9a15ab01945110cb50cdcfb_img.jpg) + +Sequence diagram for UE/TWAN initiated release for one IPv4 Address or one IPv6 Address for dual stack PDN in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW1, PDN GW2, VPCRF, AAA Proxy, HPCRF, and HSS/AAA. A 'Roaming Scenarios' box contains VPCRF, AAA Proxy, and HPCRF. The sequence of messages is: 1. DHCP release (UE to TWAN), 2. Modify Bearer Request (TWAN to PDN GW1), 3. PCEF-initiated IP-CAN Session Modification Procedure (PDN GW1 to VPCRF), 4. Modify Bearer Response (VPCRF to PDN GW1), 5. DHCP Reply (PDN GW1 to UE), and 6. TWAN Specific resource release (TWAN to UE). + +**Figure 8.2.3.2.3.1.2-1: UE/ TWAN initiated release for one IPv4 Address or one IPv6 Address for dual stack PDN in WLAN on GTP S2a** + +When the PDN Type is IPv4v6, UE shall release the IPv4 address using DHCPv4 release message or IPv4 address lease time expires in TS23.402 [3] clause 16.3, and release the IPv6 address using DHCPv6 release message or IPv6 address lease time expires separately. + +The scenario applies that UE/TWAN deletes one IPv4 address or one IPv6 address for a Dual Stack PDN first, and subsequently, UE/TWAN deletes the PDN. + +1. UE sends DHCPv4 release message to TWAN if UE releases IPv4 address first, including PDN Type for IPv4. + +- Alternative 1: + +Specific GRE key or client id is used for identifying specific PDN to be deleted, and TWAN can detect that only IPv4 address shall be deleted according to PDN Type for IPv4 in DHCPv4 release message. + +UE sends DHCPv6 release message to TWAN, specific GRE key or IAID is used for identifying specific PDN to be deleted, if UE releases IPv6 address first. + +- Alternative 2: + +TWAG virtual MAC address is used for identifying specific PDN to be deleted, and TWAN can detect that only IPv4 address shall be deleted according to PDN Type for IPv4 in DHCPv4 release message. + +UE sends DHCPv6 release message to TWAN, TWAG virtual MAC address is used for identifying specific PDN to be deleted, if UE releases IPv6 address first. + +2. In case that TWAN receives DHCPv4 release message, then, IP type is IPv4 and TWAN indicates PDN GW for deleting IPv4 address from the PDN. In case that TWAN receives DHCPv6 release message, then, IP type is IPv6 and TWAN indicates PDN GW for deleting IPv6 address from the PDN. + +If TWAN requested IP release, TWAN decides the order of deleting IPv4 address and IPv6 address, If TWAN decides to delete IPv4 first, TWAN sets the IP type to be IPv4 and indicates PDN GW for deleting IPv4 address from the PDN. If TWAN decides to delete IPv6 address first, TWAN sets the IP type to be IPv6 and indicates PDN GW for deleting IPv6 address from the PDN. + +TWAN checks there are two associated IPv4 address and IPv6 address for the PDN, and sends modify Bearer Request to PDN GW, including the indication for IP type to be deleted, in order to indicate PDN GW for deleting this type of IP from the PDN. + +3. PDN GW initiates the IP-CAN Session Modification Procedure with the PCRF. + +4. PDN GW sends modify Bearer response to TWAN. + +If there are multiple bearers corresponding to the PDN, then steps 2-4 are repeated. + +5. TWAN shall remove the associated contexts corresponding to specific PDN, send Reply message in the case of DHCPv6, and inform UE of removing associated contexts. + +6. If TWAN requested IP release, TWAN shall send a DHCPv4 FORCERENEW message as per IETF RFC 3203 [24] and RFC6704 [27], or DHCPv6 Reconfigure message as per IETF RFC 3315 [23]. When the UE proceeds with renewing the IPv4 address or IPv6 address lease, the TWAN shall in turn refuse to do so, notifying to the UE that the IPv4 address or IPv6 address has been released. + +Subsequently, when UE sends DHCPv6 release (if DHCPv4 release is sent in step 1) or DHCPv4 release (if DHCPv6 release is sent in step 1) message, TWAN shall disconnect the PDN. If TWAN requested IP release, then TWAN shall send delete session request message to PDN GW, in order to disconnect the PDN. + +###### 8.2.3.2.3.1.3 UE/TWAN requested Detach Procedure in WLAN on GTP S2a + +![Sequence diagram for UE/ TWAN requested Detach on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Step 1: UE sends DHCP release to TWAN. Step 2: TWAN sends Delete Session Request to PDN GW1. Step 3: PDN GW1 sends Update PDN GW Address to HSS/AAA via AAA Proxy. Step 4: PCEF-Initiated IP-CAN Session Termination Procedure involving PDN GW1, vPCRF, and hPCRF. Step 5: PDN GW1 sends Delete Session Response to TWAN. Step 6: Steps 2-5 are repeated if additional PDN connections exist (involving PDN GW2). Step 7: TWAN sends DHCP Reply to UE. Step 8: TWAN Specific resource release.](69edc2887e907309499ac95b47ab6905_img.jpg) + +Sequence diagram for UE/ TWAN requested Detach on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Step 1: UE sends DHCP release to TWAN. Step 2: TWAN sends Delete Session Request to PDN GW1. Step 3: PDN GW1 sends Update PDN GW Address to HSS/AAA via AAA Proxy. Step 4: PCEF-Initiated IP-CAN Session Termination Procedure involving PDN GW1, vPCRF, and hPCRF. Step 5: PDN GW1 sends Delete Session Response to TWAN. Step 6: Steps 2-5 are repeated if additional PDN connections exist (involving PDN GW2). Step 7: TWAN sends DHCP Reply to UE. Step 8: TWAN Specific resource release. + +**Figure 8.2.3.2.3.1.3-1: UE/ TWAN requested Detach on GTP S2a** + +1. If the PDN Type is IPv4, UE releases the IPv4 address using DHCPv4 release message or IPv4 address lease time expires in TS23.402 [3] clause 16.3. And if the PDN Type is IPv6, UE releases the IPv6 address using DHCPv6 release message or IPv6 address lease time expires. If the PDN Type is IPv4v6, UE shall releases the IPv4 address and IPv6 address by the first DHCP release session, i.e. DHCPv4 release message or DHCPv6 release message. + +For DHCPv4 release message, the UE MAC address is included in the option of “chaddr”. By the option, UE indicates detach to TWAN. + +For DHCPv6 release message, the UE MAC address is included in the option of “client id”. By the option, UE indicates detach to TWAN. + +2-5. TWAN sends delete Session Request to PDN GW, in order to indicate PDN GW for deleting one PDN. The steps 2-5 are same as steps 2-5 in TS23.402 [3] clause 16.3.1.1. + +6. Repeat steps 2-5 above for remainder PDNs if multiple PDNs are established. + +7. TWAN shall de-authenticate and de-associate the UE at layer 2 according to IEEE STD 802.11-207 [5] , send Reply message to UE in the case of DHCPv6 and informing UE of removing associated contexts. + +8. If TWAN requested Detach, the TWAN locally removes the UE contexts and de-authenticates and disassociates the UE at Layer 2 according to IEEE Std. 802.11-2007 [5]. + +###### 8.2.3.2.3.1.4 HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a + +![Sequence diagram for HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a. Lifelines include UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Step 1: HSS/AAA sends Session Termination Request to AAA Proxy, which forwards it to TWAN. Step 2: The procedures as figure 8.2.3.2.3.1.3-1, step 2 to 5 are performed. Step 3: Step 2 is implemented if additional PDN connections exist. Step 4: TWAN Specific resource release. Step 5: TWAN sends Session Termination Response back to AAA Proxy, which forwards it to HSS/AAA.](b6e90f8ae3109449704b9b5c7951f631_img.jpg) + +Sequence diagram for HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a. Lifelines include UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Step 1: HSS/AAA sends Session Termination Request to AAA Proxy, which forwards it to TWAN. Step 2: The procedures as figure 8.2.3.2.3.1.3-1, step 2 to 5 are performed. Step 3: Step 2 is implemented if additional PDN connections exist. Step 4: TWAN Specific resource release. Step 5: TWAN sends Session Termination Response back to AAA Proxy, which forwards it to HSS/AAA. + +###### **Figure 8.2.3.2.3.1.4-1: HSS/AAA Initiated Detach on GTP S2a** + +The procedure for HSS/AAA Initiated Detach from TWAN is represented in Figure 8.2.3.2.3.1.4-1 and described below. + +This procedure applies to the Non-Roaming, Home Routed Roaming and Local Breakout cases. In the Local Breakout case, the vPCRF forwards messages between the PDN GW and the hPCRF. In the Home Routed Roaming and LBO cases, the 3GPP AAA Proxy serves as an intermediary between the Trusted Non-3GPP IP Access and the 3GPP AAA Server in the HPLMN. In the non-roaming and Home Routed Roaming case, the vPCRF is not involved at all. + +- 1) The HSS/AAA sends a Session Termination Request message to the TWAN to detach a specific UE. +- 2) The step 2 to 5 of the UE/TWAN Initiated Detach procedure described in clause 8.2.3.2.3.1.3 above are followed. +- 3) If additional PDNs exist, step 2 is implemented for each PDN. +- 4) During the step, TWAN shall de-authenticate and de-associate the UE at layer 2 according to IEEE STD 802.11-207 [5], and inform UE to remove the associated contexts. +- 5) TWAN sends a Session Termination Response message to 3GPP AAA Server, respectively. If the detach procedure was initiated from the 3GPP AAA Server and if the UE no longer has any context in the 3GPP AAA Server, the 3GPP AAA Server communicates the HSS as described in clause 12.1.2 TS23.402. If the detach procedure was initiated by HSS, the 3GPP AAA Server replies to the HSS as described in clause 12.1.3 TS23.402. + +NOTE: The HSS/AAA may also send a detach indication message to the PDN GW. The PDN GW does not remove the GTP tunnels on S2a, since the TWAN is responsible for removing the GTP tunnels on S2a. The PDN GW acknowledges the receipt of the detach indication message to the 3GPP AAA Server. + +##### 8.2.3.2.3.2 Detach and PDN disconnection in WLAN on PMIP S2a + +###### 8.2.3.2.3.2.1 UE/TWAN requested single PDN Disconnection Procedure in WLAN on PMIP S2a + +![Sequence diagram for single PDN disconnection in WLAN on PMIP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows the interaction between these entities to disconnect a single PDN session. The vPCRF, AAA Proxy, and hPCRF are grouped under 'Roaming Scenarios'. The sequence starts with a DHCP release from UE to TWAN, followed by a Proxy Binding Update from TWAN to PDN GW. The PDN GW then sends an Update PDN GW Address to the AAA Proxy, which in turn sends it to the HSS/AAA. A PCEF-initiated IP-CAN session termination procedure is initiated between the PDN GW and the AAA Proxy. The PDN GW then sends a Proxy Binding Ack to the TWAN, which sends a DHCP Reply to the UE. Finally, TWAN-specific resources are released.](f76f0f5dfff2511b51f6b875867c029f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note left of UE: fic +e + + UE->>TWAN: 1. DHCP release + TWAN->>PDN_GW: 2. Proxy Binding Update(lifetime=0) + PDN_GW->>AAA_Proxy: 3. Update PDN GW Address + AAA_Proxy->>HSS_AAA: 3. Update PDN GW Address + PDN_GW-->>AAA_Proxy: 4. PCEF-Initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Proxy Binding Ack + TWAN->>UE: 6. DHCP Reply + Note right of TWAN: 7. TWAN Specific resource release + +``` + +Sequence diagram for single PDN disconnection in WLAN on PMIP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows the interaction between these entities to disconnect a single PDN session. The vPCRF, AAA Proxy, and hPCRF are grouped under 'Roaming Scenarios'. The sequence starts with a DHCP release from UE to TWAN, followed by a Proxy Binding Update from TWAN to PDN GW. The PDN GW then sends an Update PDN GW Address to the AAA Proxy, which in turn sends it to the HSS/AAA. A PCEF-initiated IP-CAN session termination procedure is initiated between the PDN GW and the AAA Proxy. The PDN GW then sends a Proxy Binding Ack to the TWAN, which sends a DHCP Reply to the UE. Finally, TWAN-specific resources are released. + +Figure 8.2.3.2.3.2.1-1: UE/ TWAN requested single PDN Disconnection on PMIP S2a + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.3.1.1, with the following differences: + +- Step 2 is a Proxy Binding Update. The parameters in the Proxy Binding Update message are same as step 2 in clause 8.2.3.2.3.1.1. +- Step 5 is a Proxy Binding Acknowledgement. The parameters in the Proxy Binding Acknowledgement message are same as step 5 in clause 8.2.3.2.3.1.1. + +###### 8.2.3.2.3.2.2 UE/TWAN requested multiple PDN Disconnection Procedure in WLAN on PMIP S2a + +![Sequence diagram for multiple PDN disconnection in WLAN on PMIP S2a. Lifelines: UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows the interaction for disconnecting multiple PDN sessions. The vPCRF, AAA Proxy, and hPCRF are grouped under 'Roaming Scenarios'. The sequence starts with a DHCP release from UE to TWAN, followed by a Proxy Binding Update from TWAN to PDN GW1. PDN GW1 sends an Update PDN GW Address to the AAA Proxy, which sends it to the HSS/AAA. A PCEF-initiated IP-CAN session termination procedure is initiated between PDN GW1 and the AAA Proxy. PDN GW1 sends a Proxy Binding Ack to the TWAN. A loop indicates that steps 2-5 are repeated for additional PDN connections (e.g., PDN GW2). Finally, the TWAN sends a DHCP Reply to the UE and releases TWAN-specific resources.](01141eb99b707de5aead56f84afe3b1f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW1 as PDN GW1 + participant PDN_GW2 as PDN GW2 + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + UE->>TWAN: 1. DHCP release + TWAN->>PDN_GW1: 2. Proxy Binding Update(lifetime=0) + PDN_GW1->>AAA_Proxy: 3. Update PDN GW Address + AAA_Proxy->>HSS_AAA: 3. Update PDN GW Address + PDN_GW1-->>AAA_Proxy: 4. PCEF-Initiated IP-CAN Session Termination Procedure + PDN_GW1->>TWAN: 5. Proxy Binding Ack + Note right of TWAN: 6. steps 2-5 are implemented if additional PDN connections exist + TWAN->>UE: 7. DHCP Reply + Note right of TWAN: 8. TWAN Specific resource release + +``` + +Sequence diagram for multiple PDN disconnection in WLAN on PMIP S2a. Lifelines: UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows the interaction for disconnecting multiple PDN sessions. The vPCRF, AAA Proxy, and hPCRF are grouped under 'Roaming Scenarios'. The sequence starts with a DHCP release from UE to TWAN, followed by a Proxy Binding Update from TWAN to PDN GW1. PDN GW1 sends an Update PDN GW Address to the AAA Proxy, which sends it to the HSS/AAA. A PCEF-initiated IP-CAN session termination procedure is initiated between PDN GW1 and the AAA Proxy. PDN GW1 sends a Proxy Binding Ack to the TWAN. A loop indicates that steps 2-5 are repeated for additional PDN connections (e.g., PDN GW2). Finally, the TWAN sends a DHCP Reply to the UE and releases TWAN-specific resources. + +Figure 8.2.3.2.3.2.2-1: UE/ TWAN requested multiple PDN Disconnection on PMIP S2a + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.3.1.2, with the following differences: + +- Step 2 is a Proxy Binding Update. The parameters in the Proxy Binding Update message are same as step 2 in clause 8.2.3.2.3.1.2. + +- Step 5 is a Proxy Binding Acknowledgement. The parameters in the Proxy Binding Acknowledgement message are same as step 5 in clause 8.2.3.2.3.1.2. + +###### 8.2.3.2.3.2.3 UE/TWAN requested Detach Procedure in WLAN on PMIP S2a + +![Sequence diagram for UE/TWAN requested Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a sequence of messages starting with a DHCP release from UE to TWAN, followed by a Proxy Binding Update from TWAN to PDN GW1. A 'Roaming Scenarios' box contains steps 3 (Update PDN GW Address), 4 (PCEF-initiated IP-CAN Session Termination), and 5 (Proxy Binding Ack). A dashed box indicates steps 2-5 are repeated if additional PDN connections exist. Final steps are DHCP Reply and TWAN Specific resource release.](573c8f9e728e343b6864e1070c14b8cf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW1 as PDN GW1 + participant PDN_GW2 as PDN GW2 + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of AAA_Proxy: Roaming Scenarios + UE-->>TWAN: 1. DHCP release + TWAN->>PDN_GW1: 2. Proxy Binding Update(lifetime=0) + PDN_GW1->>AAA_Proxy: 3. Update PDN GW Address + Note right of AAA_Proxy: 4. PCEF-Initiated IP-CAN Session Termination Procedure + AAA_Proxy-->>PDN_GW1: 5. Proxy Binding Ack + Note right of PDN_GW1: 6.steps 2-5 are implemented if additional PDN connections exist + PDN_GW1-->>UE: 7. DHCP Reply + Note right of UE: 8. TWAN Specific resource release + +``` + +Sequence diagram for UE/TWAN requested Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW1, PDN GW2, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a sequence of messages starting with a DHCP release from UE to TWAN, followed by a Proxy Binding Update from TWAN to PDN GW1. A 'Roaming Scenarios' box contains steps 3 (Update PDN GW Address), 4 (PCEF-initiated IP-CAN Session Termination), and 5 (Proxy Binding Ack). A dashed box indicates steps 2-5 are repeated if additional PDN connections exist. Final steps are DHCP Reply and TWAN Specific resource release. + +Figure 8.2.3.2.3.2.3-1: UE/ TWAN requested Detach on PMIP S2a + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.3.1.3, with the following differences: + +- Step 2 is a Proxy Binding Update. The parameters in the Proxy Binding Update message are same as step 2 in clause 8.2.3.2.3.1.3. +- Step 5 is a Proxy Binding Acknowledgement. The parameters in the Proxy Binding Acknowledgement message are same as step 5 in clause 8.2.3.2.3.1.3. + +###### 8.2.3.2.3.2.4 HSS/AAA Initiated Detach Procedure in WLAN on PMIP S2a + +Same as the procedure for SaMOG R11, refer to TS23.402 [3] clause 16.3.1.2. + +![Sequence diagram for HSS/AAA Initiated Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a Session Termination Request from HSS/AAA to PDN GW. A 'Roaming Scenarios' box contains steps 2 (procedures from 8.2.3.2.3.2.1-1, step 2 to 5) and 3 (step 2 is implemented if additional PDN connections exist). Final steps are TWAN Specific resource release and Session Termination Response.](43fec6623ab9cb223a9ff74e2d2a4402_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note right of AAA_Proxy: Roaming Scenarios + HSS_AAA->>PDN_GW: 1. Session Termination Request + Note right of AAA_Proxy: 2. The procedures as figure 8.2.3.2.3.2.1-1, step 2 to 5 + Note right of AAA_Proxy: 3. step 2 is implemented if additional PDN connections exist + Note right of TWAN: 4. TWAN Specific resource release + PDN_GW-->>HSS_AAA: 5. Session Termination Response + +``` + +Sequence diagram for HSS/AAA Initiated Detach on PMIP S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows a Session Termination Request from HSS/AAA to PDN GW. A 'Roaming Scenarios' box contains steps 2 (procedures from 8.2.3.2.3.2.1-1, step 2 to 5) and 3 (step 2 is implemented if additional PDN connections exist). Final steps are TWAN Specific resource release and Session Termination Response. + +Figure 8.2.3.2.3.2.4-1: HSS/AAA Initiated Detach on PMIP S2a + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.3.1.4, the difference is that steps 2 and 3 refer to figure 8.2.3.2.3.2.3-1. + +##### 8.2.3.2.4 PDN GW initiated Resource Allocation Deactivation in WLAN on S2a + +Same as the procedure for SaMOG R11, refer to TS23.402 [3] clause 16.4. + +###### 8.2.3.2.4.1 PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a + +This procedure can be used to deactivate an S2a dedicated bearer or deactivate all S2a bearers belonging to a PDN address, e.g., due to IP-CAN session modification requests from the PCRF. If the default S2a bearer belonging to a PDN is deactivated, the PDN GW deactivates all S2a bearers belonging to the PDN. + +![Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Delete Bearer Request (PDN GW to TWAN), 3. TWAN specific resource Release Procedure (TWAN to UE), 4. Delete Bearer Response (TWAN to PDN GW), 5. Update PDN GW Address (PDN GW to 3GPP AAA proxy), and 6. IP-CAN Session Modification (PDN GW to vPCRF).](9791722d75115ddcc599b07d7bc35d73_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_proxy as 3GPP AAA proxy + participant hPCRF + end + participant AAA_HSS as AAA/HSS + + Note right of PDN_GW: 1. IP-CAN Session Modification + PDN_GW->>vPCRF: 1. IP-CAN Session Modification + PDN_GW->>TWAN: 2. Delete Bearer Request + Note left of TWAN: 3. TWAN specific resource Release Procedure + TWAN-->>UE: 3. TWAN specific resource Release Procedure + TWAN->>PDN_GW: 4. Delete Bearer Response + PDN_GW->>AAA_proxy: 5. Update PDN GW Address + Note right of PDN_GW: 6. IP-CAN Session Modification + PDN_GW->>vPCRF: 6. IP-CAN Session Modification + +``` + +Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Delete Bearer Request (PDN GW to TWAN), 3. TWAN specific resource Release Procedure (TWAN to UE), 4. Delete Bearer Response (TWAN to PDN GW), 5. Update PDN GW Address (PDN GW to 3GPP AAA proxy), and 6. IP-CAN Session Modification (PDN GW to vPCRF). + +**Figure 8.2.3.2.4.1-1: PDN GW Initiated Bearer Deactivation with GTP on S2a** + +This procedure applies to the Non-Roaming, Roaming and Local Breakout cases. In the Local Breakout case, the vPCRF forwards messages between the PDN GW and the hPCRF. In the non-roaming and home routed roaming cases, the vPCRF is not involved at all. + +The optional interaction steps between the PDN GW and the PCRF in the procedures in figure 16.4.1-1 occur only if dynamic policy provisioning is deployed. Otherwise policy may be statically configured within the PDN GW. + +1. If dynamic PCC is deployed, the PDN GW initiated Bearer Deactivation procedure may be triggered, for example, due to 'IP-CAN session Modification procedure', as defined in TS 23.203 [19]. In this case, the resources associated with the PDN in the PDN GW are released. +2. The PDN GW sends a Delete Bearer Request message (EPS Bearer Identity, Cause) to the TWAN. This message can include an indication that all bearers belonging to that PDN shall be released. +3. If supported by the TWAN, the TWAN shall remove the associated contexts corresponding to specific PDNs, and inform UE to remove the associated contexts. +4. The TWAN deletes the bearer contexts related to the Delete Bearer Request message, and acknowledges the bearer deactivation to the PDN GW by sending a Delete Bearer Response (EPS Bearer Identity) message. +5. In the case of the resources corresponding to the PDN are released in PDN GW, the PDN GW informs the 3GPP AAA Server/HSS of the PDN disconnection. +6. The PDN GW deletes the bearer context related to the deactivated S2a bearer. If the dedicated bearer deactivation procedure was triggered by receiving a PCC decision message from the PCRF, the PDN GW + +indicates to the PCRF whether the requested PCC decision was successfully enforced by completing the PCRF-initiated IP-CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203 [19], proceeding after the completion of IP-CAN bearer signalling. + +###### 8.2.3.2.4.2 PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a + +![Sequence diagram for PDN GW Initiated Bearer Deactivation with PMIP on S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Binding Revocation Indication (PDN GW to TWAN), 3. TWAN specific resource Release Procedure (TWAN internal), 4. Gateway Control Session Termination Procedure (TWAN to hPCRF), 5. Binding Revocation Ack (TWAN to PDN GW), 6. Update PDN GW Address (hPCRF to AAA/HSS), 7. IP-CAN Session Modification (hPCRF to vPCRF).](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant 3GPP_AAA_proxy as 3GPP AAA proxy + participant hPCRF + end + participant AAA_HSS as AAA/HSS + + PDN_GW->>vPCRF: 1. IP-CAN Session Modification + PDN_GW->>TWAN: 2. Binding Revocation Indication + Note left of TWAN: 3. TWAN specific resource Release Procedure + TWAN->>hPCRF: 4. Gateway Control Session Termination Procedure + TWAN->>PDN_GW: 5. Binding Revocation Ack + hPCRF->>AAA_HSS: 6. Update PDN GW Address + hPCRF->>vPCRF: 7. IP-CAN Session Modification + +``` + +Sequence diagram for PDN GW Initiated Bearer Deactivation with PMIP on S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. A 'Roaming Scenarios' box contains vPCRF, 3GPP AAA proxy, and hPCRF. The sequence of messages is: 1. IP-CAN Session Modification (PDN GW to vPCRF), 2. Binding Revocation Indication (PDN GW to TWAN), 3. TWAN specific resource Release Procedure (TWAN internal), 4. Gateway Control Session Termination Procedure (TWAN to hPCRF), 5. Binding Revocation Ack (TWAN to PDN GW), 6. Update PDN GW Address (hPCRF to AAA/HSS), 7. IP-CAN Session Modification (hPCRF to vPCRF). + +**Figure 8.2.3.2.4.2-1: PDN GW Initiated Bearer Deactivation with PMIP on S2a** + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.4.1, with the following differences: + +- Step 2 is a Binding Revocation Indication message. The parameters in the Binding Revocation Indication message are same as step 2 in clause 8.2.3.2.4.1. +- Step 4. If the resources are released in the TWAN, the TWAN initiates a Gateway Control Session Termination Procedure with the PCRF as specified in TS 23.203 [4]. +- Step 5 is a Binding Revocation Acknowledgement message. The parameters in the Binding Revocation Acknowledgement message are same as step 4 in clause 8.2.3.2.4.1. + +##### 8.2.3.2.5 Dedicated bearer activation in WLAN on GTP S2a + +Same as the procedure for SaMOG R11, refer to TS23.402 [3] clause 16.5. + +##### 8.2.3.2.6 Network-initiated bearer modification in WLAN on GTP S2a + +Same as the procedure for SaMOG R11, refer to TS23.402 [3] clause 16.6. + +##### 8.2.3.2.7 Handover from 3GPP Access to Trusted WLAN Access + +###### 8.2.3.2.7.1 Handover from 3GPP Access to Trusted WLAN Access on GTP S2a + +![Sequence diagram illustrating the handover from 3GPP Access to Trusted WLAN Access on GTP S2a. The diagram shows interactions between UE, TWAN, MME, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves radio bearer establishment, WLAN discovery, authentication, DHCP exchange, session creation, IP-CAN modification, and bearer release.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates the sequence of messages for a handover from 3GPP Access to Trusted WLAN Access on GTP S2a. The participants are UE, TWAN, MME, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes vPCRF, AAA Proxy, hPCRF, and HSS/AAA. + +- UE and TWAN establish a radio bearer and S1 bearer (highlighted in yellow). +- UE discovers WLAN Access and initiates HO. +- UE sends EAP Authentication to TWAN, which is relayed by AAA Proxy to HSS/AAA. +- UE sends DHCP Discover/Confirm to TWAN. +- TWAN sends Create Session Request to PDN GW. +- PDN GW initiates IP-CAN Session Modification Procedure with vPCRF (dashed box). +- PDN GW sends Update PDN GW Address to AAA Proxy. +- PDN GW sends Create Session Response to TWAN. +- TWAN and PDN GW establish a GTP Tunnel (highlighted in green). +- PDN GW sends DHCP Offer to UE. +- UE sends DHCP Request/DHCP Ack to PDN GW. +- UE sends Reply to PDN GW. +- UE initiates connectivity to Additional PDN. +- UE and TWAN send 3GPP EPS Bearer Release messages. + +Sequence diagram illustrating the handover from 3GPP Access to Trusted WLAN Access on GTP S2a. The diagram shows interactions between UE, TWAN, MME, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves radio bearer establishment, WLAN discovery, authentication, DHCP exchange, session creation, IP-CAN modification, and bearer release. + +**Figure 8.2.3.2.7.1-1: Handover from 3GPP Access to Trusted WLAN Access on GTP S2a** + +1-2) These steps are the same as steps 1-3 in TS 23.402 [3], clause 8.2.2. + +3. In this step, indication on whether the UE indicates its capability (i.e. Rel-12 SaMOG capability) to the AAA server during the authentication procedure. Based on the UE capability provided by AAA server, the TWAN decides to use L3 trigger. + +4. The UE shall send a DHCPv4 Discover as per IETF RFC 2131 [9], or DHCPv6 confirm as per IETF RFC3315[23] to TWAN with “requested IP address” included in DHCPv4 Discover message (option 50)/ DHCPv6 Confirm message (option IA\_NA) with all previously assigned UE IP addresses prior to its handover. TWAN determines IP address preservation by the presence of the “requested IP address” option. APN, PDN Type and downlink GRE key (for alternative 1) shall also be included. + +5. The TWAN sends a Create Session Request (APN PDN address, Handover Indication) message to the PDN GW. The PDN Address shall be set according to requested IP address for DHCP request message in step 4, and sent to the PDN GW. The TWAN sets the 'Handover Indication' to allow the PDN GW to re-allocate the same IPv4 address and/or IPv6 address that was assigned to the UE while it was connected to 3GPP IP access and to initiate an IP CAN Session Modification Procedure with the PCRF. Both the APN and PDN Address are used by the PDN GW to determine which PDN to establish connectivity for, in the case that the PDN GW supports multiple PDN connectivity. + +6) This steps is same as steps 7A-7B in TS 23.402 [3], clause 8.2.2. + +7) The PDN GW informs the 3GPP AAA Server of its PDN GW identity and the APN corresponding to the UE's PDN and obtains authorization information from the 3GPP AAA Server. The 3GPP AAA Server decides whether or not to update PDN GW identification according to the UE capability, which has been provided at the + +authentication phase. If the UE supports IP address preservation, the 3GPP AAA Server shall update PDN GW identity towards the HSS. + +8. The PDN GW responds with a Create Session Response to the TWAN. The Create Session Response contains the IPv4 address and/or the IPv6 address that were assigned to the UE while it was connected to the 3GPP IP access. +9. GTP tunnel is setup between TWAN and PDN GW. +10. For DHCPv4, TWAN returns DHCP offer message to UE, TWAG virtual MAC address is included if alternative 2 is used. +11. UE sends DHCP Request (for DHCPv4) to TWAN, and TWAN returns DHCP Ack message to the UE and UE IP allocated by PDN GW. + - a) Alternative 1: GRE tunnelling information is included to UE, where GRE tunnel information includes uplink GRE key and UE's local IP address which are allocated by TWAN for tunnelling support in the case of one or multiple PDNs. + - b) Alternative 2: Both UE and TWAN maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address. +12. TWAN returns Reply message to the UE, and UE IP allocated by PDN GW. + - a) Alternative 1: GRE tunnelling information is included to UE, where GRE tunnel information includes uplink GRE key and UE's local IP address which are allocated by TWAN for tunnelling support in the case of one or multiple PDNs. + - b) Alternative 2: Both UE and TWAN maintain the relations of TWAG virtual MAC address and associated UE information, including IMSI, APN, UE IP address. + +When PDN type is IPv4, steps 10-11 apply. + +When PDN type is IPv6, step 12 apply. + +When PDN type is IPv4v6, there are two following cases: + +- Alternative 1: + - (a) If UE requests IPv4 address first, TWAN shall implement steps 10-11 and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send confirm message encapsulated by the GRE key which is allocated in step 11 to TWAN, TWAN shall implement steps 12 which are encapsulated by the GRE key which is allocated in step 11. + - (b) If UE requests IPv6 address first, TWAN shall implement steps 12 and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message encapsulated by the GRE key which is allocated in step 12 to TWAN, TWAN and UE shall implement steps 10-11 which are encapsulated by the GRE key which is allocated in step 12. + - Alternative 2: + - (a) If UE requests IPv4 address first, TWAN shall implement steps 10-11 and return IPv4 address to UE. Subsequently, when UE requests IPv6 address, it shall send confirm message with TWAG virtual MAC address which is allocated in step 10 to TWAN, TWAN shall implement steps 12. +- (b) If UE requests IPv6 address first, TWAN shall implement steps 12 and return IPv6 address to UE. Subsequently, when UE requests IPv4 address, it shall send DHCP discovery message with TWAG virtual MAC address which is allocated in step 12 to TWAN, TWAN and UE shall implement steps 10-11. + +Both uplink and downlink GRE key corresponds to the specific PDN. And subsequently, user data for the PDN shall be encapsulated by corresponding GRE tunnel. + +13. For connectivity to multiple PDNs, the UE establishes connectivity to all the remain PDNs that are being transferred from 3GPP access besides the PDN, and steps 3 to 12 are repeated for per PDN, with the following exception: + +- Handover indication isn't included in step 5. + +14. The PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure in 3GPP access as defined in clause 5.6.2.2 in TS 23.402 [3] for PMIP S5/S8 or the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401 [6], clause 5.4.4.1 for GTP-S5/S8. + +##### 8.2.3.2.7.2 Handover from 3GPP Access to Trusted WLAN Access on PMIP S2a + +![Sequence diagram showing the handover procedure from 3GPP Access to Trusted WLAN Access on PMIP S2a. The diagram involves UE, TWAN, MME, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Steps include radio bearer setup, WLAN discovery, EAP authentication, DHCP exchange, Proxy Binding Update/Acknowledgement, IP-CAN session modification, and bearer release.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant MME + participant S-GW + participant PDN GW + participant vPCRF + participant AAA Proxy + participant hPCRF + participant HSS/AAA + + Note over UE, PDN GW: 1. Radio bearer and S1 bearer (GTP/PMIP) + Note over UE: 2. UE discovers WLAN Access and initiates HO + UE->>TWAN: 3. EAP Authentication + TWAN->>HSS/AAA: 3. Authentication & Authorization (via AAA Proxy) + UE->>TWAN: 4. DHCP Discover/ Confirm + TWAN->>PDN GW: 5. Proxy Binding Update + PDN GW->>hPCRF: 6. IP-CAN Session Modification Procedure (via vPCRF) + PDN GW->>HSS/AAA: 7. Update PDN GW Address + PDN GW->>TWAN: 8. Proxy Binding Acknowledgement + Note over TWAN, PDN GW: 9. GTP Tunnel + TWAN->>UE: 10. DHCP Offer + UE->>TWAN: 11. DHCP Request/DHCP Ack + TWAN->>UE: 12. Reply + UE->>HSS/AAA: 13. UE-initiated Connectivity to Additional PDN + Note over UE, S-GW: 14. 3GPP EPS Bearer Release + Note over PDN GW, HSS/AAA: 14. 3GPP EPS Bearer Release + +``` + +Sequence diagram showing the handover procedure from 3GPP Access to Trusted WLAN Access on PMIP S2a. The diagram involves UE, TWAN, MME, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Steps include radio bearer setup, WLAN discovery, EAP authentication, DHCP exchange, Proxy Binding Update/Acknowledgement, IP-CAN session modification, and bearer release. + +**Figure 8.2.3.2.7.2-1: Handover from 3GPP Access to Trusted WLAN Access on PMIP S2a** + +The procedure is similar to GTP S2a call flow in clause 8.2.3.2.7.1, with the following differences: + +- Step 5 is a Proxy Binding Update. The parameters in the Proxy Binding Update message are same as step 5 in clause 8.2.3.2.7.1. +- Step 8 is a Proxy Binding Acknowledgement. The parameters in the Proxy Binding Acknowledgement message are same as step 8 in clause 8.2.3.2.7.1. + +#### 8.2.3.3 Impacts on existing nodes or functionality + +#### 8.2.3.4 Evaluation + +*Editor's Notes: The fulfilment to the requirements in Subclause 8.1 as well as simplicity of implementation in the UE should be evaluated.* + +The following aspects are considered and evaluated for the solution: + +##### i) Impacts to existing network deployment: + +- a) There is no requirement for WLAN APs compared to Rel-11. +- b) For TWAG, it shall support DHCP enhancement, EAP enhancement, and the association of IPv4 session and IPv6 session for same PDN for dual stack scenario. + +##### ii) Impacts to UE: + +- a) For UE, it shall support DHCP enhancement, EAP enhancement, and the association of IPv4 session and IPv6 session for same PDN for dual stack scenario. + +NOTE 1: Required the support of Stateful DHCP as described in RFC 3315 with also the 3GPP vendor specific extensions + +NOTE 2: Required additional security support for DHCP Force renew as described in RFCs 3203 and 6704 + +NOTE 3: The IPv4 and IPv6 sessions association for dual-stack support is common to all SaMOG proposed solutions and is not specific to Solution 3. + +- b) UE is required to support GRE-over-IP encapsulation if alternative 1 is used. + +##### iii) Impacts to 3GPP protocols/extensions (e.g. EAP AKA'): + +The following protocols are extended: + +- a) UE network capability negotiation is enhanced for EAP protocol. +- b) Session Management (APN, PDN type, GRE tunnel information(for alternative 1), UE IP), is enhanced for DHCP protocol. +- c) 3GPP Vendor-specific Information can be used for enhanced information in DHCP protocol + +##### iv) Impacts to protocols defined by other SDOs (e.g. DHCP): + +No impact on other SDOs. + +##### v) Control plane + +- a) The latency/load can increase in the following procedures: + - 1) For first PDN and handover procedures, EAP (once for first PDN) and DHCP messages are implemented. + - 2) For additional PDN, DHCP messages are implemented. +- b) There is no impact on other network element, e.g. AAA signaling etc. + +#### vi) Compliance to clause 8.1 SaMOG phase-2 system requirements: + +- a) Co-existence with Rel-11 SaMOG +- b) Support for IP address preservation during handover +- c) Simultaneous support for S2a EPC-routed and NSWO; support of simultaneous multiple PDNs + +#### vii) Other functional limitations: + +There is no other functional limitation. + +### 8.2.4 Solution 4 + +#### 8.2.4.1 Functional Description + +##### 8.2.4.1.1 P2P link + +A per UE point-to-point link between the UE and the TWAG is assumed. + +The TWAG performs unicast layer 2 forwarding even when layer 3 is multicast address (e.g. Router Advertisement, RFC 6085). + +**Editor's Note:** Handling of unsolicited IPv6 Router Advertisement for PDN connections is FFS. + +**Editor's Note:** How to support multiple IPv4 PDN connections when same private IPv4 addresses are allocated from different PDN connections with per UE point-to-point link is FFS. + +In IPv4 case, the multiple PDN may use the same IP multicast address for different services, the source IP address in general could be used to disambiguate the multicast services. + +**Editor's Note:** If the source IP address is same, how to distinguish the services are FFS. + +## 8.2.5 Solution 5: Associating APN/PDN with Virtual IP Interface + +#### 8.2.5.1 Functional Description + +**Editor's Notes:** It should be described whether and how the solution fulfils the requirements in Subclause 8.1. + +##### 8.2.5.1.1 General + +This section describes in general the point-to-point link/IP forwarding and the control sequence for associating an APN/NSWO to a point-to-point link. The session control protocol carries the APN/PDN signalling attributes and uses distinct Gateway interface (gateway IP address, MAC address) for the connection to associate the APN in IP configuration signalling (DHCP for IPv4, stateless autoconfiguration for IPv6). + +##### Point-to-Point Link + +The point-to-point link in this solution uses the distinct MAC address per APN/NSWO at the gateway as described in subclause 8.2.2.1.1.2 for packet forwarding. In addition to a distinct MAC address, this solution has a distinct TWAG Gateway Interface per APN/NSWO connection. A TWAG Gateway Interface for a connection consists of an IP address and a MAC address – each of which is distinct for connections to a UE. + +![Diagram of a Point-to-Point Link between a UE and a PDN GW via a TWAG, showing traffic flow aggregates and control protocols.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates a Point-to-Point Link between a User Equipment (UE) and a PDN GW, connected via a TWAG (TWAN Gateway). At the top, an oval labeled 'Application / Service Layer' shows 'UL Traffic Flow Aggregates' entering the UE and 'DL Traffic Flow Aggregates' exiting the PDN GW. Inside the UE, traffic is associated with an 'APN/NSWO'. An arrow labeled 'APN/NSWO → TWAG-GW-If' points from the UE to the TWAG. Inside the PDN GW, traffic is associated with 'DL-TFT'. An arrow labeled 'DL-TFT → S2a-TEID' points from the PDN GW to the TWAG. The TWAG has two interfaces: 'TWAG-GW-If' facing the UE and 'S2a-TEID' facing the PDN GW. A dashed oval labeled 'NSWO' is shown below the TWAG. A label 'L2 Flow: UE-MAC ↔ TWAG-VMAC' points to the link between the UE and the TWAG. A label 'S2a Bearer' points to the link between the TWAG and the PDN GW. The TWAG is also connected to an 'AP/WLC' (Access Point/Wireless LAN Controller). + +Diagram of a Point-to-Point Link between a UE and a PDN GW via a TWAG, showing traffic flow aggregates and control protocols. + +**Figure 8.2.5.1.1-1: Point-to-Point Link** + +**PDN Control Protocol** The PDN control protocol is used to signal APN/PDN information between UE TWAN. This protocol also associates the APN/NSWO connection request to a distinct gateway IP address/MAC address prior to IP configuration using DHCP, RS/RA. The gateway IP address is derived from the MAC address and there is a 1:1 association between the distinct gateway MAC address and the gateway IP address. For IP configuration signalling using DHCP or RS/RA, the TWAG can uniquely associate a UE's PDN connection using UE MAC address (or IPv6 link layer address) and this gateway interface (IP address, virtual MAC address) that is distinct for each PDN connection of the UE. + +For IPv4 stateful address configuration, the UE provides a PDN connection request and the TWAG returns this distinct gateway IP address as input for server-identity in DHCP request. In the subsequent DHCP Request from UE, the server-identity is populated with this distinct gateway IP address as a means for the TWAG to identify the PDN connection. + +For IPv6 stateless address configuration, the UE provides an PDN connection request and the TWAG returns this distinct gateway IP address and also populates the same gateway IP address in a Router Advertisement that follows. For cases where the UE needs to send a Router Solicitation (optional), the TWAG also returns a transient multicast address corresponding to this PDN connection that the TWAG listens to. The UE may send a Router Solicitation with destination address set to this transient multicast address that is distinct for this PDN connection. + +If UE request handover from 3GPP to WLAN access, it indicates handover attach in the control protocol. + +If the UE needs to setup a second PDN connection, this can be signalled in a subsequent connection setup request. For disconnection of a PDN connection, either the UE or the TWAN may notify the other about an IP address/prefix that is released. The notified entity can then release the local connection resources. + +The PDN Control Protocol described above consists of requests / responses or notification messages and requires a transport for these messages. Two alternative transport protocols are considered here: + +###### - **Alternative A: ICMP Echo Payload** + +ICMP Echo [RFC 792] is typically used to verify if another host is active. However, it is possible to add an arbitrary data payload following the ICMP header as long as it is echoed back, and this solution uses the data payload to carry binary encoded connection control messages each of which is an ICMP Echo Request and Response. The PDN Control Protocol is identified by a unique sequence identifier (e.g. 0xFCFCFC) that follows the ICMP Echo message and precedes the PDN control protocol frame. The data payload of the ICMP Echo messages maybe authenticated (message authentication) using a hashed key each for UE and TWAG (established during EAP-AKA). Only one set of keys are established between UE – TWAG and either the link local address or the NSWO IP + +connection may be used for this signalling. + +Reliability of this control sequence is provided by virtue of receiving the echoed message. For re-transmission, this method re-uses the DHCP re-transmission timer value. No support for fragmentation is provided and is not necessary for the control protocol. + +The ICMP Echo payload mechanism uses existing ICMP protocol semantics and does not violate IETF RFC 792. Only the control messages need to be standardized (in 3GPP). The mechanism is basic and is efficient enough even if messages are echoed back since only a limited amount of control signalling required and is always across one IP hop. + +###### - **Alternative B: 802.11 GAS frame** + +802.11 GAS frames can be used to carry the PDN control protocol frames similar to the transport of ANQP/GAS between UE – WLAN Access Point. These control frames could then be carried to the TWAG over RADIUS or other similar protocol. The control protocol semantics are the same as in Alternative A above. + +Reliability of this control sequence is provided using 802.11 GAS and the backhaul protocol (e.g. RADIUS). Re-transmission timers re-use the DHCP re-transmission timer value. No fragmentation is expected as the signalling is expected to be well below the size of an Ethernet frame. + +The PDN Control protocol would be defined as a new GAS protocol in WFA as part of HS2.0 Rel-3 specifications. The protocol would use the WMM Notification Action frames as a L2 transport over the 802.11 air interface. In addition, RADIUS protocol messages Accept-Request/Response (for PDN Request/Response) and Change-of-Authorization (for Notification) should carry this protocol from AP – TWAN controllers. This underlying mechanism provides a reliable control protocol transport. As in the case above, DHCP re-transmission timer values may be used. + +**Editor's Note:** Selection of one of the control transport protocols is FFS. + +**Editor's Notes:** For uplink broadcasts signalling (e.g. IPv6 RS, IPv6 ND, ARP, and service discovery requests (e.g. DLNA) generally sent using a L2 (MAC) broadcast address: + +- when the destination MAC address used over WLAN is a broadcast address and not the TWAG MAC address associated with a TWAN connectivity service, a specific handling would be required at the TWAN to handle such traffic or +- the UE uses a unicast MAC addressing for such traffic as described in RFC 6085 “Address Mapping of IPv6 Multicast Packets on Ethernet “ for the IPv6 case. Using such technique for IPv4 is FFS. + +#### 8.2.5.2 Procedures + +**Editor's Notes:** The call flows are described in this subclause. + +##### 8.2.5.2.2 Connection Establishment Procedure + +The connection establishment procedures below support both PDN connection establishment and NSWO connections. In the case of PDN connections, the signalling from UE to TWAN explicitly provides the APN that the UE wishes to connect to. For NSWO connections, the UE indicates NSWO request or signal that it wants a local IP address. + +The figures below outline GTP S2a, PMIP S2a and NSWO connection setup. + +![Sequence diagram titled 'Attach Procedure for PDN and NSWO for GTP based S2a'. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It is divided into 'Roaming Scenarios' and 'Non-Roaming Scenarios'. The procedure includes: 1. Non-3GPP Specific Procedures; 2. EAP Authentication; 2b. Initialize Control Interface; 3. Request to associate APN/PDN to virtual IP interface; 4. Response to associate APN/PDN to virtual IP interface; 5a. Create Session Request; 6. IP-CAN Session Establishment Procedure; 7. Update PDN GW Address; 8. Create Session Response; 9. GTP Tunnel; 5b. Create NSWO connection context; 10. L3 Address Request; 11. L3 Address Ack. The GTP S2a and NSWO paths are highlighted with dashed boxes.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +Sequence diagram titled 'Attach Procedure for PDN and NSWO for GTP based S2a'. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It is divided into 'Roaming Scenarios' and 'Non-Roaming Scenarios'. The procedure includes: 1. Non-3GPP Specific Procedures; 2. EAP Authentication; 2b. Initialize Control Interface; 3. Request to associate APN/PDN to virtual IP interface; 4. Response to associate APN/PDN to virtual IP interface; 5a. Create Session Request; 6. IP-CAN Session Establishment Procedure; 7. Update PDN GW Address; 8. Create Session Response; 9. GTP Tunnel; 5b. Create NSWO connection context; 10. L3 Address Request; 11. L3 Address Ack. The GTP S2a and NSWO paths are highlighted with dashed boxes. + +**Figure 8.2.5.2.2-1: Attach Procedure for PDN and NSWO for GTP based S2a** + +The procedure to attach PDN or NSWO for a trusted WLAN access is represented in Figure 8.2.5.2.2-1 and described below: + +1. The initial TWAN specific L2 procedures are performed. These procedures are TWAN specific and outside the scope of 3GPP. +2. EAP authentication procedures are performed. During this sequence, support of Phase 2 by the UE and TWAG are conveyed using EAP-AKA [RFC 4187] extensions. If the UE, TWAG are Phase 2 compliant, the UE and TWAG setup and exchange keys to be used to provide integrity protection (e.g. checksum hash) for the subsequent signalling setup messages. +After successful authentication, in step 2b, for ICMP Payload transport of PDN signalling protocol, the UE sets up a link-local address for IPv4 (RFC 3927), or follows the procedure in RFC 4861 to setup an IPv6 link local address. The TWAG replies with a control-initialize message with source router IP, MAC address that UE can use in subsequent requests. +3. The UE sends a request with APN, other PDN signalling parameters (e.g. initial attach) to the TWAN to setup a PDN/NSWO connection. The signalling may be transported using ICMP Echo Payload (alternative 1) or 802.11 GAS (alternative 2). +4. The TWAN assigns a distinct IPv4 gateway address corresponding to the APN/NSWO and responds with this address in server-identity and router address for IPv4. For IPv6, the TWAN assigns a distinct IPv6 gateway address (source address in Router Advertisement) and transient multicast address for router solicitation if needed. + +**Editor's Note: The choice of a control protocol transport in steps 3-4 is FFS.** + +Steps 5 – 9 are performed as specified in TS 23.402, subclause 16.2.1, steps 3 – 7 for PDN connection establishment for GTP S2a. + +For NSWO connection, step 5b, the TWAG assigns local connection resources (gateway IP address, subnet, etc.) for the connection. + +- The UE sends a layer 3 attach request. + - For IPv4, the UE sends a DHCP Request with server-identity option set to the distinct gateway IP address obtained in step 4. + - For IPv6, the UE may optionally send a Router Solicitation with destination address set to the transient multicast address obtained in step 4. +- The TWAN responds to the layer 3 attach. + - For IPv4, the TWAG sends a DHCP Ack with server-identity, router option set to the distinct gateway IP address for the APN/NSWO. The IP address in the message is in yiaddr. + - For IPv6, the TWAG sends a Router Advertisement when a Create Session Response (step 8) is received for this PDN connection or it receives Router Solicitation in step 10. The Router Advertisement is sent with source address set to the distinct gateway IP address configured for this APN/NSWO in step 4. + - The UE can determine the L2 address of the router interface by sending an ARP Request (IPv4) or Neighbor Solicitation (IPv6) + +For subsequent PDN / NSWO connections, steps 3 – 11 are repeated. + +Establishing a second connection (IP address/interface) corresponding to an already signalled/established APN/NSWO session is straightforward using this method. In step 3 above, the explicit parameters that are conveyed between UE and TWAG can include the means to indicate if a second connection is being requested. + +![Sequence diagram showing the Attach Procedure for PDN and NSWO for PMIP based S2a. It details interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Key steps include EAP Authentication, APN/PDN association, Proxy Binding Update/Ack, PMIP Tunnel establishment, and L3 Address Request/Ack.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note over UE, TWAN: 1. Non-3GPP Specific Procedures + UE->>TWAN: 2. EAP Authentication + TWAN->>HSS_AAA: 2. Authentication & Authorization (via AAA Proxy) + TWAN->>UE: 2b. Initialize Control Interface + UE->>TWAN: 3. Request to associate APN/PDN to virtual IP interface + TWAN->>UE: 4. Response to associate APN/PDN to virtual IP interface + TWAN->>PDN_GW: 5a. Proxy Binding Update + rect rgb(240, 240, 240) + Note over PDN_GW, HSS_AAA: Roaming Scenarios + PDN_GW->>hPCRF: 6. IP-CAN Session Establishment Procedure (via vPCRF/AAA Proxy) + HSS_AAA->>PDN_GW: 7. Update PDN GW Address + end + PDN_GW->>TWAN: 8. Proxy Binding Ack + Note over TWAN, PDN_GW: 9.. PMIP Tunnel + TWAN->>UE: 5b. Create NSWO connection context + UE->>TWAN: 10. L3 Address Request + TWAN->>UE: 11. L3 Address Ack + +``` + +Sequence diagram showing the Attach Procedure for PDN and NSWO for PMIP based S2a. It details interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Key steps include EAP Authentication, APN/PDN association, Proxy Binding Update/Ack, PMIP Tunnel establishment, and L3 Address Request/Ack. + +**Figure 8.2.5.2.2-2: Attach Procedure for PDN and NSWO for PMIP based S2a** + +The procedure for attach using PMIP based S2a is similar to the sequence for GTP. However, steps 5a and 8 for PMIP consist of Proxy Binding Update (5a) and Proxy Binding Ack (8). + +##### 8.2.5.2.3 UE Initiated Disconnection Procedure + +The disconnection sequence in the figure below supports UE triggered disconnection of one connection (while the rest of the session remains unchanged). If the last connection (or all connections) is being released, all session resources are cleaned up also. + +![Sequence diagram showing the UE Initiated Disconnection Procedure for PDN and NSWO for GTP based S2a. The diagram involves UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It details steps 1 through 6, including conditional paths for GTP S2a and NSWO scenarios.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + rect rgb(240, 240, 240) + Note over vPCRF, AAA_Proxy: Roaming Scenarios + end + + UE->>TWAN: 1. Delete Connection (notification) + + rect dashed + Note right of TWAN: (GTP S2a) + TWAN->>PDN_GW: 2a. Delete Session Request + PDN_GW->>HSS_AAA: 3. Update PDN GW Address + Note over PDN_GW, hPCRF: 4. PCEF-initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Delete Session Response + end + + rect dashed + Note right of TWAN: (NSWO) + TWAN->>TWAN: 2b. NSWO release local resources + end + + TWAN->>UE: 6. TWAN specific resource release + +``` + +Sequence diagram showing the UE Initiated Disconnection Procedure for PDN and NSWO for GTP based S2a. The diagram involves UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It details steps 1 through 6, including conditional paths for GTP S2a and NSWO scenarios. + +**Figure 8.2.5.2.3-1: Disconnection Procedure for PDN and NSWO for GTP based S2a** + +The procedure to disconnect a PDN /NSWO session for GTP based S2a is shown in the figure above. + +1. The UE sends a delete connection notification with the IP address and gateway IP address for the connection to trigger disconnection. +2. If the IP address to be released is not an NSWO connection, the TWAG initiates a Delete Session Request with the IP address of the PDN connection. (2a). +For NSWO, the TWAN releases local connection resources (2b). + +Steps 3, 4 are as defined in TS 23.402 [3], subclause 16.3.1.1, steps 3, 4. + +5. The PDN GW acknowledges with Delete Session Response (cause). +6. Connection resources in TWAG and UE are released. + +![Sequence diagram for Disconnection Procedure for PDN and NSWO for PMIP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps for PMIP S2a (steps 2a, 3, 4, 5) and NSWO (steps 2b, 6).](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN GW + participant vPCRF + participant AAA Proxy + participant hPCRF + participant HSS/AAA + + Note over vPCRF, AAA Proxy: Roaming Scenarios + + UE->>TWAN: 1. Delete Connection (notification) + + rect rgb(255, 255, 255) + Note right of TWAN: (PMIP S2a) + TWAN->>PDN GW: 2a. Proxy Binding Update (lifetime = 0) + PDN GW->>HSS/AAA: 3. Update PDN GW Address + PDN GW->>vPCRF: 4. PCEF-initiated IP-CAN Session Termination Procedure + PDN GW->>TWAN: 5. Proxy Binding Ack + end + + rect rgb(255, 255, 255) + Note right of TWAN: (NSWO) + Note over TWAN: 2b. NSWO release local resources + end + + Note over UE, TWAN: 6. TWAN specific resource release + +``` + +Sequence diagram for Disconnection Procedure for PDN and NSWO for PMIP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps for PMIP S2a (steps 2a, 3, 4, 5) and NSWO (steps 2b, 6). + +**Figure 8.2.5.2.3-2: Disconnection Procedure for PDN and NSWO for PMIP based S2a** + +The procedure for disconnection using PMIP based S2a is similar to the sequence for GTP. However, steps 2a and 5 for PMIP consist of Proxy Binding Update with lifetime set to zero (2a) and Proxy Binding Ack (5). + +##### 8.2.5.2.4 HSS/AAA Initiated Disconnection Procedure + +The disconnection sequence in the figure below supports disconnection of one connection triggered by the HSS/AAA (while the rest of the session remains unchanged). If the last connection (or all connections) is being released, all session resources are cleaned up also. + +![Sequence diagram for Disconnection Procedure for GTP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps 1, 1b, 2, and 3.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN GW + participant vPCRF + participant AAA Proxy + participant hPCRF + participant HSS/AAA + + Note over vPCRF, AAA Proxy: Roaming Scenarios + + HSS/AAA->>AAA Proxy: 1. Session Termination Request + AAA Proxy->>UE: 1b. Delete Connection (notification) + + Note over UE, HSS/AAA: 2. The procedures as figure 8.2.x.2.3-1, step 2 to 6 + + AAA Proxy->>HSS/AAA: 3. Session Termination Response + +``` + +Sequence diagram for Disconnection Procedure for GTP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps 1, 1b, 2, and 3. + +**Figure 8.2.5.2.4-1: Disconnection Procedure for GTP based S2a** + +The procedure to disconnect a PDN /NSWO session for GTP based S2a when triggered by HSS/AAA is shown in the figure above. + +- 1. The HSS/AAA sends a Session Termination Request message to the TWAN to detach a specific UE. +In (1b), the TWAG sends a delete connection notification message with the IP address and gateway IP address of the connection to trigger release of connection resources at UE. +- 2. The procedures in 8.2.5.2.3, steps 2 – 6 are followed. +- 3. Step 3 defined in TS 23.402 [6], subclause 16.3.1.2 is followed. + +![Sequence diagram for Disconnection Procedure for PMIP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. A shaded area labeled 'Roaming Scenarios' covers vPCRF, AAA Proxy, and hPCRF. Step 1: HSS/AAA sends Session Termination Request to TWAN. Step 1b: TWAN sends Delete Connection (notification) to UE. Step 2: A block labeled 'The procedures as figure 8.2.x.2.3-2, step 2 to 6'. Step 3: TWAN sends Session Termination Response to HSS/AAA.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +Sequence diagram for Disconnection Procedure for PMIP based S2a. Lifelines: UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. A shaded area labeled 'Roaming Scenarios' covers vPCRF, AAA Proxy, and hPCRF. Step 1: HSS/AAA sends Session Termination Request to TWAN. Step 1b: TWAN sends Delete Connection (notification) to UE. Step 2: A block labeled 'The procedures as figure 8.2.x.2.3-2, step 2 to 6'. Step 3: TWAN sends Session Termination Response to HSS/AAA. + +**Figure 8.2.5.2.4-2: Disconnection Procedure for PMIP based S2a** + +The procedure for disconnection using PMIP based S2a is similar to the sequence for GTP. Step 2 in the figure is based on 8.2.5.2.3 for PMIP. + +##### 8.2.5.2.5 Handover procedure between 3GPP access and WLAN on GTP S2a + +![Sequence diagram of the handover procedure between 3GPP access and WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, Serving GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It is divided into 'Roaming Scenarios' and 'Non-Roaming Scenarios'. The process involves authentication, session establishment, and bearer release.](a3472689858b068ef469213682965325_img.jpg) + +The diagram illustrates the handover procedure from 3GPP access to a Trusted WLAN (TWAN) using GTP S2a. The participants are UE, TWAN, Serving GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process is as follows: + +- 0. GTP Tunnel:** An initial GTP tunnel exists between the UE and the PDN GW via the Serving GW. +- 1. Non-3GPP Specific Procedures:** Initial procedures specific to the non-3GPP access are performed. +- 2. EAP Authentication:** The UE performs EAP authentication with the TWAN, which then forwards it to the AAA Proxy/HSS/AAA. +- 3. Request to associate APN/PDN to virtual IP interface:** The UE sends a request to the TWAN to associate an APN/PDN with a virtual IP interface. +- 4. Response to associate APN/PDN to virtual IP interface:** The TWAN responds to the UE. +- 5a. Create Session Request:** The TWAN sends a Create Session Request to the Serving GW. +- 6. IP-CAN Session Establishment Procedure:** The Serving GW initiates the IP-CAN session establishment with the PDN GW and vPCRF. +- 7. Update PDN GW Address:** The PDN GW updates its address in the HSS/AAA. +- 8. Create Session Response:** The PDN GW sends a Create Session Response back to the Serving GW. +- 9. GTP Tunnel:** A new GTP tunnel is established between the UE and the PDN GW via the Serving GW. +- 5b. Create NSWO connection context:** The Serving GW creates an NSWO connection context for the UE. +- 10. L3 Address Request:** The UE sends an L3 Address Request to the TWAN. +- 11. L3 Address Ack:** The TWAN responds with an L3 Address Ack. +- 12. 3GPP EPS bearer release:** Both the UE and the Serving GW initiate the release of the 3GPP EPS bearer. + +The diagram is categorized into 'Roaming Scenarios' (involving vPCRF, AAA Proxy, and hPCRF) and 'Non-Roaming Scenarios' (involving NSWO). The GTP S2a interface is highlighted between the Serving GW and the PDN GW. + +Sequence diagram of the handover procedure between 3GPP access and WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, Serving GW, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It is divided into 'Roaming Scenarios' and 'Non-Roaming Scenarios'. The process involves authentication, session establishment, and bearer release. + +**Figure 8.2.5.2.6-1: Handover from 3GPP access to Trusted WLAN on GTP S2a** + +The handover procedure is based on the Connection Establishment Procedure in 8.2.5.2.2 with the following additions: + +0. The UE is connected in the 3GPP Access and has a PMIPv6 or GTP tunnel on the S5/S8 interface. +1. The initial TWAN specific L2 procedures are performed. These procedures are TWAN specific and outside the scope of 3GPP. +2. If the handover establishes the first PDN connection in WLAN of the UE, EAP procedure is performed in this step. +3. The UE sets up an IP interface to perform initial PDN signalling with the TWAN. During this sequence, if UE and TWAG are Phase 2 compliant, i.e. supporting EPC-routed, handover and multiple PDN connections, the UE sends a request with APN and handover indication, to setup a PDN connection. +4. The TWAN assigns a distinct IPv4 gateway address corresponding to the APN and responds with this address in server-identity and router address for IPv4. For IPv6, the TWAN assigns a distinct IPv6 gateway address (source address in Router Advertisement) and transient multicast address for router solicitation if needed. + +5. The TWAN sends a Create Session Request (APN, handover indication) message to the PDN GW. The APN and handover indication is set in the Create Session Request to allow the PDN GW to re-allocate the same IP address or prefix that was assigned to the UE while it was connected to the 3GPP IP access and to initiate a PCEF-Initiated IP CAN Session Modification Procedure with the PCRF. The APN is used by the PDN GW to determine which PDN connection(s) to handover, in the case that the UE has established multiple PDN connections to different APNs. + +Steps 6 – 11 are performed as Connection Establishment Procedure in 8.2.5.2.2. + +12. The PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure in 3GPP access as defined in TS 23.402 clause 5.6.2.2 or the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401 [6], clause 5.4.4.1. + +#### 8.2.5.3 Impacts on existing nodes or functionality + +**Editor's Notes:** Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause. + +This solution minimizes the impact to existing IP configuration procedures – both DHCP, stateless IPv6 auto-configuration by moving all PDN connection signalling to a new protocol that only handles PDN connection aspects. + +For transporting the new PDN connection signalling, ICMP Echo payload proposed here has low impact in terms of implementation on the UE and TWAG. The ICMP messages are echoed back to be compliant with RFC 792 and this adds a response (echo) by definition. Echoing the message takes additional network capacity for the echo message, but does not require significant processing in the TWAN/UE. Two such echoes are needed for each PDN connection setup. A full implementation of L3 control protocol would be more flexible and complete if the time and effort to develop it is acceptable – including its support on UE and TWAG. + +If GAS frames are the chosen method to transport PDN connection signalling, it requires UEs that support WFA/HS2.0 and standards extensions in WFA/HS2.0. This method also requires APs to map the PDN signalling over GAS to backhaul protocol (e.g. RADIUS). + +**Editor's Note:** The implications of using RADIUS to transport the control protocol between AP – TWAN is FFS. + +#### 8.2.5.4 Evaluation + +**Editor's Notes:** The fulfilment to the requirements in Subclause 8.1 as well as simplicity of implementation in the UE should be evaluated. + +### 8.2.6 Solution 6: X + +This solution has been merged with the solution in section 8.2.1 + +- + +### 8.2.7 Solution 7: PPP over Ethernet (PPPoE) + +#### 8.2.7.1 Functional Description + +**Editor's Notes:** It should be described whether and how the solution fulfils the requirements in Subclause 8.1. + +##### 8.2.7.1.1 Overview + +The solution described in this section does not require any new protocols. It is based on the well-known PPP and PPP over Ethernet (PPPoE) protocols, specified in RFC1661 and RFC2516, respectively. These protocols are used to implement both the control plane and the user plane. + +In summary, the solution is characterized by the following: + +1. A PDN Connection over a trusted WLAN (TWAN) is created by establishing a PPPoE/PPP session between the UE and TWAG (Trusted WLAN Access Gateway). +2. The PPPoE protocol is used to create a virtual point-to-point link between the UE and TWAG. +3. The UE encapsulates all traffic pertaining to a PDN connection into PPPoE frames (as shown below). These frames include a PPPoE session ID, which differentiates traffic between different PDN connections. + +![](844077b3034f0030b404207db0ad76b4_img.jpg) + +| | | | | +|-------------|---------------------------------------|-------------------------------|-------------| +| WLAN header | PPPoE header<br>(Session ID = 0x065d) | PPP header<br>(Protocol = IP) | IP Datagram | +| | 6 bytes | 2 bytes | | + +4. The TWAG binds a PPPoE session ID with a PDN connection. Traffic arrived from a certain PPPoE session ID is forwarded to the linked PDN connection and vice versa. +5. The TWAG behaves as an Access Concentrator that terminates both PPP and PPPoE protocols. It is very similar to a Broadband Remote Access Server (BRAS) function used in fixed broadband networks. +6. The UE needs to implement the PPP and PPPoE protocols. Both of them are already available in most smartphone platforms. Note that there are already applications available which enable the user to establish PPPoE connections on a smartphone. +7. A Non-Seamless WLAN Offload (NSWO) connection does not use PPP or PPPoE. So, NSWO traffic is transmitted directly over WLAN without any PPPoE encapsulation (as shown below). + +![](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +| | | +|-------------|-------------| +| WLAN header | IP Datagram | +|-------------|-------------| + +8. Since NSWO traffic does not use PPPoE, it does not necessarily need to be routed through TWAG. Instead, it can be optimally routed without going through TWAG. This allows TWAG to be offloaded from NSWO traffic. It also allows the WLAN network and the UE to support NSWO traffic with the currently deployed means (i.e. without any changes). However, the solution allows the AP to tunnel NSWO traffic to TWAG, if this is required. +9. There is no impact on the WLAN AP and on other legacy WLAN components. If the AP supports QoS on the WLAN air interface, it is assumed that the AP can still map between DSCP and WLAN QoS parameters. + +The solution requires the following protocol extensions: + +1. The EAP-AKA protocol is enhanced (as proposed by other solutions too) so that during initial connection to TWAN, the UE becomes aware of the supported capabilities, e.g. whether NSWO is supported, whether single or multiple concurrent PDN connections are supported, etc. This can be easily supported by defining new 3GPP-specific EAP-AKA attributes as already done for other attributes (see e.g. AT\_TRUST\_IND, AT\_IPMS\_IND, AT\_IPMS\_RES). +2. The PPP or PPPoE protocol should be enhanced in order to enable the UE and TWAG to negotiate PDN connectivity parameters (such as APN, attach type) when a new PPPoE/PPP session is created. Such enhancements can be supported by either of the following two options: + - a. Option 1: PDN connectivity parameters are negotiated during PPP session establishment. A new configuration option is specified for PPP, e.g. LCP (Link Control Protocol) or for IPCP and for IPV6CP (IP Configuration Protocol) protocols. This configuration option is used to negotiate specific PDN connectivity parameters (such as APN, attach type, etc.) between the UE and TWAG when a new PPP session is created. For this purpose the PPP Vendor Extensions as specified in RFC2153 could be used. + - b. Option 2: PDN connectivity parameters are negotiated during PPPoE session establishment. The Service-Name Tag within PPPoE could be used to transfer APN information and Vendor-Specific tag could be specified for other parameters. This way the UE can also indicate the requested PDN type (IPv4/IPv6/IPv4v6). + +The details for the above two options are further discussed in clause 8.2.7.2.1. The choice between these two options could be made during the normative work. + +The figure below illustrates the user-plane operation for a UE that concurrently has a NSWO connection and two PDN connections. Note that traffic for PDN connections is encapsulated in PPPoE frames while NSWO traffic does not require such encapsulation. Note also that each PPPoE frame carries a Session ID which is associated with a PDN connection. + +There is no requirement for NSWO traffic (i.e. traffic which does not traverse EPC) to be routed to TWAG. This enables TWAG offload and a single TWAG could support a larger number of UEs. + +![Figure 8.2.7.1.1-1: User plane operation when the UE has a NSWO connection and two PDN connections. The diagram shows three traffic paths from a UE: PDN-2, PDN-1, and NSWO. PDN-2 and PDN-1 traffic is encapsulated in PPPoE frames with Session IDs Y and X respectively, then in PPP and IP datagrams, with a WLAN header. NSWO traffic is just an IP datagram with a WLAN header. All frames are sent to an AP. The AP forwards based on DestMAC address. PDN traffic goes through Intermediate WLAN components to a TWAG, which has session bindings for PDN connection 1 and 2, and then to the EPC. NSWO traffic is offloaded directly from the AP.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +The diagram illustrates the user-plane operation for a UE with a NSWO connection and two PDN connections. The UE sends three types of traffic: PDN-2, PDN-1, and NSWO. PDN-2 and PDN-1 traffic is encapsulated in PPPoE frames with Session IDs Y and X respectively, then in PPP and IP datagrams, with a WLAN header. NSWO traffic is just an IP datagram with a WLAN header. All frames are sent to an AP. The AP forwards based on DestMAC address. PDN traffic goes through Intermediate WLAN components to a TWAG, which has session bindings for PDN connection 1 and 2, and then to the EPC. NSWO traffic is offloaded directly from the AP. + +Figure 8.2.7.1.1-1: User plane operation when the UE has a NSWO connection and two PDN connections. The diagram shows three traffic paths from a UE: PDN-2, PDN-1, and NSWO. PDN-2 and PDN-1 traffic is encapsulated in PPPoE frames with Session IDs Y and X respectively, then in PPP and IP datagrams, with a WLAN header. NSWO traffic is just an IP datagram with a WLAN header. All frames are sent to an AP. The AP forwards based on DestMAC address. PDN traffic goes through Intermediate WLAN components to a TWAG, which has session bindings for PDN connection 1 and 2, and then to the EPC. NSWO traffic is offloaded directly from the AP. + +**Figure 8.2.7.1.1-1: User plane operation when the UE has a NSWO connection and two PDN connections.** + +The figure below shows a simplified UE protocol architecture for a UE that concurrently has a NSWO connection and two PDN connections. Each PDN connection requires a PPPoE/PPP instance. NSWO traffic in the UE can be supported without the need for any new protocols. + +![Figure 8.2.7.1.1-2: Simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and two concurrent PDN connections. The diagram shows traffic from upper layers entering a Policy based routing block. From there, traffic is split into three paths: NSWO (direct to WLAN interface), APN-1 (through PPP and PPPoE to WLAN interface with Session ID=x), and APN-2 (through PPP and PPPoE to WLAN interface with Session ID=y).](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +The diagram illustrates a simplified UE protocol architecture. Traffic from upper layers enters a Policy based routing block. From there, traffic is split into three paths: NSWO (direct to WLAN interface), APN-1 (through PPP and PPPoE to WLAN interface with Session ID=x), and APN-2 (through PPP and PPPoE to WLAN interface with Session ID=y). + +Figure 8.2.7.1.1-2: Simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and two concurrent PDN connections. The diagram shows traffic from upper layers entering a Policy based routing block. From there, traffic is split into three paths: NSWO (direct to WLAN interface), APN-1 (through PPP and PPPoE to WLAN interface with Session ID=x), and APN-2 (through PPP and PPPoE to WLAN interface with Session ID=y). + +**Figure 8.2.7.1.1-2: Simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and two concurrent PDN connections.** + +#### 8.2.7.2 Procedures + +##### 8.2.7.2.1.1 PDN Connectivity Parameter Negotiation + +###### 8.2.7.2.1.1 Option 1: PDN connectivity parameters negotiated during PPP session establishment + +The figure below shows how a PDN connection can be established when the PDN connectivity parameters are negotiated with the PPP protocol. + +![Figure 8.2.7.2.1.1-1: PDN connection establishment with Option 1. The diagram shows two cases: Case A (IPv4) and Case B (IPv6). Both cases show a UE and a TWAN. The UE sends an EAP-AKA Authentication message to the TWAN, which responds with 'PDN Connectivity Supported'. The UE then decides to activate a PDN connection. In Case A (IPv4), the UE sends a PPPoE Session Data / PPP LCP Configuration Request to the TWAN, which responds with a PPPoE Session Data / PPP LCP Configuration Ack. The UE then sends a PPPoE Session Data / PPP IPCP Configuration Request, which includes 'Existing Options: IP Address, DNS Server, etc.' and 'New Configuration Option includes the requested APN, Attach Type, etc. (NOTE1)'. The TWAN responds with a PPPoE Session Data / PPP IPCP Configuration Ack, which includes 'Existing Options: IPv4 Address, DNS Server, etc.' and 'New Configuration Option includes the offered APN (NOTE1)'. In Case B (IPv6), the UE sends a PPPoE Session Data / PPP LCP Configuration Request to the TWAN, which responds with a PPPoE Session Data / PPP LCP Configuration Ack. The UE then sends a PPPoE Session Data / PPP IPV6CP Configuration Request, which includes 'Existing Options: Interface-Identifier' and 'New Configuration Option includes the requested APN, Attach Type, etc. (NOTE1)'. The TWAN responds with a PPPoE Session Data / PPP IPV6CP Configuration Ack, which includes 'Existing Options: Interface-Identifier' and 'New Configuration Option includes the offered APN (NOTE1)'. Finally, the UE performs 'Stateless or Stateful Autoconfiguration'.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +Figure 8.2.7.2.1.1-1: PDN connection establishment with Option 1. The diagram shows two cases: Case A (IPv4) and Case B (IPv6). Both cases show a UE and a TWAN. The UE sends an EAP-AKA Authentication message to the TWAN, which responds with 'PDN Connectivity Supported'. The UE then decides to activate a PDN connection. In Case A (IPv4), the UE sends a PPPoE Session Data / PPP LCP Configuration Request to the TWAN, which responds with a PPPoE Session Data / PPP LCP Configuration Ack. The UE then sends a PPPoE Session Data / PPP IPCP Configuration Request, which includes 'Existing Options: IP Address, DNS Server, etc.' and 'New Configuration Option includes the requested APN, Attach Type, etc. (NOTE1)'. The TWAN responds with a PPPoE Session Data / PPP IPCP Configuration Ack, which includes 'Existing Options: IPv4 Address, DNS Server, etc.' and 'New Configuration Option includes the offered APN (NOTE1)'. In Case B (IPv6), the UE sends a PPPoE Session Data / PPP LCP Configuration Request to the TWAN, which responds with a PPPoE Session Data / PPP LCP Configuration Ack. The UE then sends a PPPoE Session Data / PPP IPV6CP Configuration Request, which includes 'Existing Options: Interface-Identifier' and 'New Configuration Option includes the requested APN, Attach Type, etc. (NOTE1)'. The TWAN responds with a PPPoE Session Data / PPP IPV6CP Configuration Ack, which includes 'Existing Options: Interface-Identifier' and 'New Configuration Option includes the offered APN (NOTE1)'. Finally, the UE performs 'Stateless or Stateful Autoconfiguration'. + +**Figure 8.2.7.2.1.1-1: PDN connection establishment with Option 1.** + +NOTE 1: Although the figure above shows new configuration options for the IPCP and IPV6CP protocols, those new configuration options could be specified for the LCP protocol instead. + +For establishing a PDN connection with type IPv4, the UE uses the IP Control Protocol (IPCP), as specified in RFC 1332, “The PPP Internet Protocol Control Protocol”. With IPCP, the UE receives IPv4 configuration parameters, such as an IPv4 address, DNS servers, etc. + +For establishing a PDN connection with type IPv6, the UE uses the IPv6 Control Protocol (IPv6CP), as specified in RFC 5072, “IPv6 over PPP”. With IPv6CP, the UE negotiates an “Interface-Identifier” (a 64-bit interface identifier) to be used for address autoconfiguration. On the established PPP session the UE receives a Router Advertisement and, based on its content, the UE uses either stateless or stateful autoconfiguration. Since the Router Advertisement is sent to UE over a point-to-point link, it is possible to use stateless autoconfiguration in a similar manner as used over 3GPP RAN, i.e. the UE can receive the /64 IPv6 prefix in the RA message. Moreover it is also possible to use stateful autoconfiguration for some UEs (although this is not typically needed). + +To support PDN connections with type IPv4v6, the UE can establish two PPP connections over the same PPPoE session: one for IPv4 (using IPCP) and another for IPv6 (using IPv6CP). Traffic on both PPP connections is transported on the same PPPoE session and is thus mapped to the same PDN connection. + +Editor’s Note: It is FFS if the UE needs to explicitly indicate the requested PDN type within the new configuration options. + +##### 8.2.7.2.1.2 Option 2: PDN connectivity parameters negotiated during PPPoE session establishment + +The figure below shows how a PDN connection can be established when the PDN connectivity parameters are negotiated with the PPPoE protocol. + +![Sequence diagram showing PDN connection establishment with Option 2. The diagram illustrates the interaction between a UE and a TWAN. It starts with EAP-AKA Authentication and PDN Connectivity Supported messages. The UE then decides to activate a PDN connection with Type = IPv4. The process involves PPPoE Discovery (Initiation, Offer, Request, Session-Confirmation), PPPoE Session Data (PPP LCP Configuration, PPP IPCP Configuration), and finally PDN establishment with PDP Type = IPv4.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + Note left of UE: UE decides to activate a PDN Connection with Type = IPv4 + UE->>TWAN: PPPoE Discovery Initiation (Broadcast) + TWAN-->>UE: PPPoE Discovery Offer (from TWAG) + Note right of TWAN: AC-name: TWAG-1 + UE->>TWAN: PPPoE Discovery Request (to TWAG) + Note right of TWAN: AC-name: TWAG-1, Service-Name: APN + Note right of TWAN: Vendor-Specific: Attach-Type, PDN-Type = IPv4 + TWAN-->>UE: PPPoE Discovery Session-Confirmation (from TWAG) + Note right of TWAN: AC-name: TWAG-1, Session ID = 0x065d + UE->>TWAN: PPPoE Session Data / PPP LCP Configuration Request + TWAN-->>UE: PPPoE Session Data / PPP LCP Configuration Ack + UE->>TWAN: PPPoE Session Data / PPP IPCP Configuration Request + Note right of TWAN: Existing Options: IPv4 Address, DNS Server, etc. + TWAN-->>UE: PPPoE Session Data / PPP IPCP Configuration Ack + Note right of TWAN: Existing Options: IPv4 Address, DNS Server, etc. + +``` + +Case C: PDN establishment with +PDP Type = IPv4 + +Sequence diagram showing PDN connection establishment with Option 2. The diagram illustrates the interaction between a UE and a TWAN. It starts with EAP-AKA Authentication and PDN Connectivity Supported messages. The UE then decides to activate a PDN connection with Type = IPv4. The process involves PPPoE Discovery (Initiation, Offer, Request, Session-Confirmation), PPPoE Session Data (PPP LCP Configuration, PPP IPCP Configuration), and finally PDN establishment with PDP Type = IPv4. + +**Figure 8.2.7.2.1.2-1: PDN connection establishment with Option 2.** + +In the PPPoE Discovery Request message the UE includes in the existing *Service-Name* tag (see RFC2516) the requested APN. Also, in a *Vendor-Specific* tag (the details of which should be specified by 3GPP) the UE includes the Attach-Type and the requested PDN-Type. After the PPPoE session is established, the TWAG may start the GTP/PMIP tunnel over S2a establishment, which can result in faster PDN connection creation. + +After the PPPoE session is established the UE requests configuration data with the IPCP and/or IPV6CP (see RFC5072) protocol. If the negotiated PDN Type is IPv4v6, the UE establishes two PPP sessions, one with IPCP and another with IPV6CP. The allocation of IPv6 prefix and address can happen in the same way as in option 1. + +The main advantages of the Option 2 are the following: + +- No modifications to existing IPCP and IPV6CP are needed +- Avoids potential protocol ambiguities when providing both IPv4 and IPv6 on the same APN. IPV6CP for IPv6 is different to IPCP for IPv4. The PDN type is indicated within the PPPoE message. +- The network can learn sooner which APN the UE intend to use and thus the network can start creating the GTP/PMIP tunnel over S2a interface earlier (during PPPoE discovery), which can result in faster PDN connection creation. + +##### 8.2.7.2.2 Initial Attach and UE-initiated Connectivity to PDN + +The signaling flow below shows the steps carried out when a UE connects to a trusted WLAN (TWAN) and establishes a NSWO connection along with a PDN connection. The figure is generic and applies to both GTP S2a and PMIP S2a. + +![Sequence diagram illustrating the simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and a concurrent PDN connection. The diagram shows interactions between UE, TWAN, P-GW, PCRF, and HSS/AAA. It details the process from WLAN discovery and selection to PDN connection establishment and traffic handling.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +The diagram illustrates the following sequence of events: + +- WLAN discovery and selection:** The UE performs WLAN discovery and selection within the TWAN. +- EAP-AKA Authentication:** The UE sends an EAP-AKA Authentication request to the HSS/AAA via the TWAN. The message indicates that NSWO and Multi-PDN Connectivity are supported. +- DHCPv4 or SLAAC:** The UE receives an IP configuration for NSWO from the TWAN via DHCPv4 or SLAAC. +- NSWO traffic:** NSWO traffic is shown being handled by the TWAN. +- UE decides to activate a PDN Connection:** The UE decides to activate a PDN connection. It encapsulates an IP Datagram with a WLAN header and sends it to the TWAN. +- PPPoE Discovery:** The UE initiates PPPoE Discovery over the TWAN: + - PPPoE Discovery Initiation (Broadcast) + - PPPoE Discovery Offer (from TWAG) + - PPPoE Discovery Request (to TWAG) + - PPPoE Discovery Session-Confirmation (from TWAG) with **Session ID = 0x065d** +- TWAG discovery and PPPoE session establishment:** A note indicates that all subsequent frames include the allocated Session ID. +- PPP session establishment:** The UE and TWAG establish a PPP session: + - PPPoE Session Data / PPP LCP Configuration Request + - PPPoE Session Data / PPP LCP Configuration Ack + - PPPoE Session Data / PPP IPCP Configuration Request (Existing Options: IP Address, DNS Server, etc.; New Configuration Option includes the requested APN, Attach Type, etc.) + - PPPoE Session Data / PPP IPCP Configuration Ack (Existing Options: IP Address, DNS Server, etc.; New Configuration Option includes the offered APN) +- PDN Connection establishment:** The TWAG sends a PDN Connection establishment request to the P-GW. The P-GW interacts with the PCRF and HSS/AAA via an IP-CAN Session Establishment/Modification. +- PDN traffic:** PDN traffic is shown being handled by the P-GW. +- UE may decide to activate another PDN Connection:** The UE may decide to activate another PDN connection. It encapsulates an IP Datagram with a WLAN header, a PPPoE header (Session ID = 0x065d), and a PPP header (Protocol = IP) before sending it to the TWAN. + +Header sizes at the bottom of the diagram: + +- WLAN header +- PPPoE header (Session ID = 0x065d) - 6 bytes +- PPP header (Protocol = IP) - 2 bytes +- IP Datagram + +Sequence diagram illustrating the simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and a concurrent PDN connection. The diagram shows interactions between UE, TWAN, P-GW, PCRF, and HSS/AAA. It details the process from WLAN discovery and selection to PDN connection establishment and traffic handling. + +**Figure 8.2.7.2.2-2: Simplified UE architecture with a non-seamless WLAN offload (NSWO) connection and a concurrent PDN connection.** + +NOTE 1: The above figure assumes that Option 1 is used for PDN Connectivity parameter negotiation (see clause 8.2.7.2.1). However, Option 2 is equally applicable. + +During the EAP-AKA authentication the UE becomes aware of the services offered by the trusted WLAN network, e.g. whether NSWO is supported, whether a single and/or multiple concurrent PDN connections are supported, etc. This can be accomplished by defining 3GPP-specific EAP-AKA attributes. + +When the UE decides to activate a PDN connection (with type IPv4) over the TWAN, it uses the normal PPPoE procedures to discover the TWAG and to establish a new PPPoE session with the TWAG. A new session ID is allocated by TWAG to this PPPoE session (for example: Session ID=0x065d, as shown in the figure). + +Subsequently, the UE initiates the establishment of a PPP session according to the normal PPP procedures. Note that after the LCP negotiation: + +- The standard PPP authentication could be used if the requested PDN connection is needed for “Non-Transparent access to an Intranet or ISP” (see TS 29.061); or +- The standard PPP authentication could be skipped, if the requested PDN connection is needed for “Transparent access to the Internet” (see TS 29.061). In this case, even when the UE sends a PPP authentication request the TWAG may always accept it. + +In the figure above, it is assumed that during the IPCP configuration a new IPCP configuration option is used. This allows the UE to request a specific APN, attach type, etc. and allows the TWAG to respond with an offered APN and possibly other parameters. Although the figure above shows new configuration options for the IPCP protocol, those new configuration options could be specified for the LCP protocol instead. PPP Vendor Extensions should be specified by 3GPP to support these new configuration options. + +Note that the signaling flow shown in the figure above is based on known steps already used in practice. The only extension required is (a) the new EAP-AKA attribute(s) and (b) the new PPP configuration option(s) that allows the negotiation of PDN connectivity parameters between the UE and TWAG. + +##### 8.2.7.2.3 PDN Connection Release + +The figure below illustrates the control-plane signaling flow when the UE initiates a PDN connection release. The UE simply terminates the corresponding PPP session and subsequently terminates the associated PPPoE session too. + +![Sequence diagram illustrating the PDN connection release initiated by the UE. The diagram shows the interaction between UE, TWAN, P-GW, PCRF, and HSS/AAA. The UE sends a PPPoE Session Data / PPP LCP Terminate Request to the TWAN. The TWAN maps the PPPoE Session ID to an EPS Bearer Identity and sends a PDN Connection Release Request to the P-GW. The P-GW sends an Update PGW Address to the HSS/AAA and initiates an IP-CAN Session Termination with the PCRF. The P-GW sends a PDN Connection Release Response to the TWAN. The TWAN sends a PPPoE Session Data / PPP LCP Terminate Ack to the UE. The UE sends a PPPoE Discovery Terminate to the TWAN.](805c475f0859e607af0530ba43194bf1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant P-GW + participant PCRF + participant HSS/AAA + + Note left of UE: UE decides to deactivate a PDN Connection + UE->>TWAN: PPPoE Session Data / PPP LCP Terminate Request +Session ID = 0x065d + Note right of TWAN: TWAG maps PPPoE Session ID to an EPS Bearer Identity + TWAN->>P-GW: PDN Connection Release Request + P-GW->>HSS/AAA: Update PGW Address + Note right of P-GW: IP-CAN Session Termination + P-GW->>TWAN: PDN Connection Release Response + TWAN->>UE: PPPoE Session Data / PPP LCP Terminate Ack + UE->>TWAN: PPPoE Discovery Terminate +Session ID = 0x065d + +``` + +Sequence diagram illustrating the PDN connection release initiated by the UE. The diagram shows the interaction between UE, TWAN, P-GW, PCRF, and HSS/AAA. The UE sends a PPPoE Session Data / PPP LCP Terminate Request to the TWAN. The TWAN maps the PPPoE Session ID to an EPS Bearer Identity and sends a PDN Connection Release Request to the P-GW. The P-GW sends an Update PGW Address to the HSS/AAA and initiates an IP-CAN Session Termination with the PCRF. The P-GW sends a PDN Connection Release Response to the TWAN. The TWAN sends a PPPoE Session Data / PPP LCP Terminate Ack to the UE. The UE sends a PPPoE Discovery Terminate to the TWAN. + +**Figure 8.2.7.2.3-1: PDN connection release initiated by UE.** + +The figure below illustrates the control-plane signaling flow when the P-GW initiates a PDN connection release. Note that the TWAN could also initiate the PDN connection release. In this case, the TWAN terminates the PPP session with the UE and sends the Delete Session Request to P-GW. + +The TWAG may use the standard LCP Echo Request/Reply procedure (or other link management facilities provided by PPPoE) to determine when a UE becomes unreachable. In this case, the TWAG may detach the UE from EPC by releasing all its PDN connections. + +![Sequence diagram showing PDN connection release initiated by P-GW. The diagram involves five entities: UE, TWAN, P-GW, PCRF, and HSS/AAA. The sequence starts with a PDN Connection Release Request from P-GW to TWAN. TWAN then maps the EPS Bearer Identity to a PPPoE Session. TWAN sends a PPPoE Session Data / PPP LCP Terminate Request to UE with Session ID = 0x065d. UE responds with a PPPoE Session Data / PPP LCP Terminate Ack. TWAN sends a PDN Connection Release Response to P-GW. P-GW sends an Update PGW Address to PCRF. Finally, a dashed box labeled 'IP-CAN Session Termination' spans between P-GW and PCRF. UE also sends a PPPoE Discovery Terminate with Session ID = 0x065d to TWAN.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant P-GW + participant PCRF + participant HSS/AAA + + P-GW->>TWAN: PDN Connection Release Request + Note right of TWAN: TWAG maps the EPS Bearer Identity to a PPPoE Session + TWAN->>UE: PPPoE Session Data / PPP LCP Terminate Request +Session ID = 0x065d + UE-->>TWAN: PPPoE Session Data / PPP LCP Terminate Ack + TWAN->>P-GW: PDN Connection Release Response + P-GW->>PCRF: Update PGW Address + Note right of P-GW: IP-CAN Session Termination + UE->>TWAN: PPPoE Discovery Terminate +Session ID = 0x065d + +``` + +Sequence diagram showing PDN connection release initiated by P-GW. The diagram involves five entities: UE, TWAN, P-GW, PCRF, and HSS/AAA. The sequence starts with a PDN Connection Release Request from P-GW to TWAN. TWAN then maps the EPS Bearer Identity to a PPPoE Session. TWAN sends a PPPoE Session Data / PPP LCP Terminate Request to UE with Session ID = 0x065d. UE responds with a PPPoE Session Data / PPP LCP Terminate Ack. TWAN sends a PDN Connection Release Response to P-GW. P-GW sends an Update PGW Address to PCRF. Finally, a dashed box labeled 'IP-CAN Session Termination' spans between P-GW and PCRF. UE also sends a PPPoE Discovery Terminate with Session ID = 0x065d to TWAN. + +**Figure 8.2.7.2.3-2: PDN connection release initiated by P-GW.** + +##### 8.2.7.2.4 Handover from 3GPP access to WLAN + +The UE can handover a first PDN connection from 3GPP access to WLAN by re-using the “Initial Attach and UE-Initiated Connectivity to PDN” procedure described above. In the handover scenario, during the PPP session establishment the UE provides the associated APN and indicates “Attach Type = Handover”. Existing procedures can then be used (e.g. procedures specified in TS 23.402 for IP address preservation) to make sure that the PDN connection over the trusted WLAN uses the same PGW and the same IP address. + +If the UE wants to handover additional PDN connections from 3GPP access to WLAN, it should establish additional PPP connections over WLAN by providing the associated APNs and “Attach Type = Handover”. + +#### 8.2.7.3 Impacts on existing nodes or functionality + +**Editor's Notes: Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause.** + +#### 8.2.7.4 Evaluation + +The solution supports the following capabilities: + +1. Supports one or more concurrent PDN connections. Each PDN connection requires a PPP/PPPoE protocol instance in the UE and in the TWAG. +2. Supports NSWO traffic and concurrently EPC traffic (via one or more PDN connections). +3. Supports IPv4, IPv6 and IPv4v6 PDN connections. +4. Supports IPv6 stateless autoconfiguration. It does not mandate stateful DHCPv6, thus simplifies UE implementation. +5. Supports PDN connection handover from 3GPP to TWAN with IP address preservation. +6. Supports TWAG discovery by means of standard PPPoE procedures. +7. Supports PDN connections for “Non-Transparent access to an Intranet or ISP” and for “Transparent access to the Internet” (see TS 29.061). Standard PPP authentication can be used to authenticate PDN connections for “Non-Transparent access to an Intranet or ISP”. + +8. Supports SaMOG phase-2 capable UEs and “legacy” (pre-Rel-12) UEs on the same TWAN (and on the same SSID). + +The solution is also characterized by the following features: + +1. NSWO traffic does not need to go through TWAG. This enables TWAG offload and can lead to deployments with reduced cost. +2. NSWO traffic is transmitted without any encapsulation. This improves air-interface utilization and reduces complexity. +3. There is no need for special signaling to establish tunnels / point-to-point connections for NSWO traffic. This improves efficiency and reduces complexity. +4. It is based on the well-known PPP/PPPoE protocols. Thus avoids the effort to standardize and implement new protocols in the UE and in the network. In addition, it minimizes the need for new conformance specifications; only conformance testing against the new PPP configuration options and EAP-AKA attributes is required. +5. The PPP/PPPoE protocols are already supported by many smartphones (typically as build-in or loadable kernel modules). Thus, UE modifications are minimized. +6. Standard PPP/PPPoE procedures can be used to monitor the link between the UE and TWAG. For example, the TWAG may use the standard LCP Echo Request/Reply procedure to determine when a UE becomes unreachable and then trigger Detach procedures. +7. The standard PPP LCP protocol can be used to negotiate an MTU for each PDN connection. +8. The standard PPP Compression Control Protocol (CCP) can be used to enable data compression between the UE and TWAG. Although CCP is not considered necessary over WLAN, it is a readily available option for deployment. +9. The PDN connection establishment can be expedited when Option 2 (as per clause 8.2.7.2.1) is applied. +10. It is supported by existing WLAN APs. PPPoE frames can traverse existing WLAN APs without any modification. When the AP supports QoS on the WLAN air interface, it is expected that the AP can still map between DSCP and WLAN QoS parameters. + +The solution requires the following protocol extensions: + +1. The EAP-AKA protocol should be enhanced so that during initial connection to TWAN, the UE becomes aware of the supported capabilities, e.g. whether NSWO is supported, whether single or multiple concurrent PDN connections are supported, etc. This can be easily supported by defining new 3GPP-specific EAP-AKA attributes as already done for other attributes (see e.g. AT\_TRUST\_IND, AT\_IPMS\_IND, AT\_IPMS\_RES). +2. The PPP or PPPoE protocol should be enhanced in order to enable the UE and TWAG to negotiate PDN connectivity parameters (such as APN, attach type) when a new PPPoE or PPP session is created. Such enhancements can be supported by either of the following two options presented in clause 8.2.7.2.1. + +### 8.2.8 Solution 8: Solution using new 3GPP specific LLC/SNAP header settings + +#### 8.2.8.1 Functional Description + +##### 8.2.8.1.1 General + +This solution addresses the user plane problem of supporting multiple PDN connections between the UE and the TWAG. + +The solution has the following aspects: + +- a) Works both for the case where an AP only supports 802.11 $\leftrightarrow$ Ethernet II bridging or where it supports 802.3 $\leftrightarrow$ 802.11 bridging. +- b) The LLC Address field on the wireless link (and optionally on the 802.3 LAN, if 802.3 is used) is always set to indicate that a SNAP header is present. +- c) The OUI (Organisationally Unique Identifier) of the SNAP header on the wireless link (and optionally on the 802.3 LAN, if 802.3 is used) is set to the value used in RFC 1042 (00 00 00). +- d) 3GPP requests *x* (tbd) new EtherType values from the IEEE Registration Authority (note that: a request to IEEE RA for 12 EtherType values would be sufficient for supporting up to the maximum of 11 PDN connections per UE with one spare for support of a 3GPP control plane protocol if needed). These EtherTypes will be sufficient in number to provide differentiation between PDN connections as well as differentiation of any 3GPP control plane protocol that needs to be supported. +- e) These new EtherType values are directly mapped onto the SNAP Protocol Type field on the 802.11 network. On an Ethernet II network these new EtherType values are used to populate the EtherType field (and there is a one to one mapping between 802.11 Protocol Type and Ethernet II EtherType). On an 802.3 fixed network the EtherType values are used to populate the Protocol Type field (and there is a one to one mapping between SNAP Protocol Type on 802.11 and SNAP Protocol Type on 802.3 in the bridging function). +- f) In the uplink, the combination of source (device) MAC address and EtherType value can be used by the TWAG to bind the traffic to the appropriate GTP tunnel. In the downlink the TWAG binds the GTP tunnel to the appropriate Ethernet II 'link' by appropriate setting of the destination (device) MAC address and EtherType value. +- g) The allocation of a particular EtherType/Protocol Type value to a particular user plane PDN connection can be established dynamically via signalling. +- h) Since conventionally EtherType is used to indicate the higher layer protocol type that is associated with the payload, a method is needed by which the UE or TWAG can differentiate between IPv4 and IPv6 in the case of a dual stack PDN connection. This issue is solved at the IP layer since the UE or TWAG can inspect the first 4 bits of the payload to determine the IP type of the packet. In both IPv4 and IPv6 the first 4 bits of the payload convey 'version' of the IP packet. In IPv4 'version' takes the value '4' and in IPv6 it takes the value '6'. Note that an assumption here is that the only types of packet which need to be carried on the PDN connection are packets of type IPv4 and IPv6. + +##### 8.2.8.1.2 Protocol stack + +Error: Reference source not foundFigure 8.2.8.1.2-1 shows an example user plane protocol stack for this solution where the AP and TWAG are implemented separately and the AP provides a bridging function to an 802.3 LAN. + +![Figure 8.2.8.1.2-1: Example user plane protocol stack where 802.11 ↔ 802.3 bridging is used. The diagram shows five vertical protocol stacks. From left to right: Device (STA/UE) with layers App, TCP, IP, SNAP, LLC, 802.11 MAC, 802.11 PHY; AP with layers 802.11 MAC, 802.11 PHY on the left and 802.3 MAC, 802.3 PHY on the right; Router/AG with layers SNAP, LLC, 802.3 MAC, 802.3 PHY on the left and GTP-U, UDP, IP, L2, L1 on the right; P-GW with layers GTP-U, UDP, IP, L2, L1 on the left and IP, L2, L1 on the right; App server with layers App, TCP, IP, L2, L1. Horizontal lines connect corresponding layers across adjacent stacks.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Figure 8.2.8.1.2-1: Example user plane protocol stack where 802.11 ↔ 802.3 bridging is used. The diagram shows five vertical protocol stacks. From left to right: Device (STA/UE) with layers App, TCP, IP, SNAP, LLC, 802.11 MAC, 802.11 PHY; AP with layers 802.11 MAC, 802.11 PHY on the left and 802.3 MAC, 802.3 PHY on the right; Router/AG with layers SNAP, LLC, 802.3 MAC, 802.3 PHY on the left and GTP-U, UDP, IP, L2, L1 on the right; P-GW with layers GTP-U, UDP, IP, L2, L1 on the left and IP, L2, L1 on the right; App server with layers App, TCP, IP, L2, L1. Horizontal lines connect corresponding layers across adjacent stacks. + +**Figure 8.2.8.1.2-1: Example user plane protocol stack where 802.11 ↔ 802.3 bridging is used** + +Figure 8.2.8.1.2-2 shows an example user plane protocol stack where the AP and TWAG are implemented separately and the AP provides a bridging function to an Ethernet II LAN. + +![Figure 8.2.8.1.2-2: Example user plane protocol stack where 802.11 ↔ Ethernet II bridging is used. The diagram shows five vertical protocol stacks. From left to right: Device (STA/UE) with layers App, TCP, IP, SNAP, LLC, 802.11 MAC, 802.11 PHY; AP with layers SNAP, LLC, 802.11 MAC, 802.11 PHY on the left and Ethernet II MAC, 802.3 PHY on the right; Router/AG with layers Ethernet II MAC on the left and GTP-U, UDP, IP, L2, L1 on the right; P-GW with layers GTP-U, UDP, IP, L2, L1 on the left and IP, L2, L1 on the right; App server with layers App, TCP, IP, L2, L1. Horizontal lines connect corresponding layers across adjacent stacks.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +Figure 8.2.8.1.2-2: Example user plane protocol stack where 802.11 ↔ Ethernet II bridging is used. The diagram shows five vertical protocol stacks. From left to right: Device (STA/UE) with layers App, TCP, IP, SNAP, LLC, 802.11 MAC, 802.11 PHY; AP with layers SNAP, LLC, 802.11 MAC, 802.11 PHY on the left and Ethernet II MAC, 802.3 PHY on the right; Router/AG with layers Ethernet II MAC on the left and GTP-U, UDP, IP, L2, L1 on the right; P-GW with layers GTP-U, UDP, IP, L2, L1 on the left and IP, L2, L1 on the right; App server with layers App, TCP, IP, L2, L1. Horizontal lines connect corresponding layers across adjacent stacks. + +**Figure 8.2.8.1.2-2: Example user plane protocol stack where 802.11 ↔ Ethernet II bridging is used** + +##### **8.2.8.1.3 Protocol header** + +Figure 8.2.8.1.3-1 shows the population of LLC and SNAP fields on 802 (W)LAN's. + +| | | | | | | | +|------------|----------------------------------|-----------------------------|--------------------------------------|---------------------------|--------------------------|-----| +| MAC header | LLC<br>Destination<br>SAP = 0xAA | LLC<br>Source<br>SAP = 0xAA | SNAP OUI<br>= 00 00 00<br>(RFC 1042) | SNAP Protocol<br>Type = Y | IP header and<br>payload | FCS | +| MAC | LLC | | SNAP | | IP | | + +Y is an EtherType value that has been allocated to 3GPP by the IEEE Registration Authority and which may correspond to a specific PDN connection. The mapping between a given value Y and a given PDN connection is established via signalling. + +**Figure 8.2.8.1.3-1: User plane packet as seen on an 802 (W)LAN** + +Figure 8.2.8.1.3-2 shows the population of the MAC header on an Ethernet II packet. + +| | | | | | +|--------------------|---------------|-----------|------------|-----| +| Destination<br>MAC | Source<br>MAC | EtherType | Frame Body | FCS | +|--------------------|---------------|-----------|------------|-----| + +The EtherType value would be one that has been allocated to 3GPP by the IEEE Registration Authority and which may correspond to a specific PDN connection. The mapping between a given EtherType value and a given PDN connection is established via signalling. The EtherType value is the same as that which is used in the Protocol Type field across the wireless 802.11 interface + +**Figure 8.2.8.1.3-2: User plane packet as seen on an Ethernet II wired interface** + +#### 8.2.8.2 Procedures + +An LLC/SNAP user plane solution can be used in conjunction with a variety of the signaling solutions which are described as part of other solutions in this TR. These signaling possibilities are now discussed and any modifications to those proposals which are required in order to support the LLC/SNAP based user plane solution are described. + +It is worth noting that some of the signaling options presented within other solutions make use of new signaling protocols which would be defined by 3GPP. The LLC/SNAP solution can provide support for such protocols. This is achieved simply by reserving one of the 3GPP specific EtherType values for this purpose. For example an EtherType value *p* could correspond to a 3GPP specified control plane protocol that runs between the UE and the TWAG. If either the UE or the TWAG receives a frame with an EtherType value set to *p* then it would process the frame contents as a 3GPP control plane frame. Note that this reserved value *p* would be defined in a 3GPP specification and would not be dynamically changeable. + +Non Seamless Wireless Offload (NSWO) could be supported by the device in the way that the device would typically use today when directly accessing the internet over WLAN (eg SNAP OUI set to 00 00 00 (RFC 1042) and SNAP Protocol Type set to the EtherType value corresponding to the appropriate higher layer protocol (IP=0x0800, ARP=0x0806), and with IP address locally allocated by the TWAN). + +From a signaling point of view the UE needs to learn both the MAC address of the TWAG and the EtherType value that it should use for a given PDN connection. Regards the former issue, an approach which will be common to many if not all of the signaling solutions will be for the UE to determine the MAC address of the TWAG through DHCP/ARP messaging using a broadcast 802.11 MAC address. The TWAG also needs to learn the MAC address of the device and the EtherType values that should be bound with given GTP tunnels. + +Note: Because with this proposal EtherType is encapsulated in a Protocol Type field on an 802.3 LAN or on an 802.11 WLAN, and since EtherType is always used on Ethernet II, in the remainder of this section we will in general just use the term 'EtherType' as opposed to 'Protocol Type'. + +| <b>Solution</b> | <b>Signalling aspects of solution compatible with SNAP/LLC user plane solution?</b> | <b>Comment</b> | +|-----------------------------------------------------------------|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution 1: Two Scenario Approach | Yes | <p>The proposed UE-TWAG Wireless LAN Control Protocol (WLCP) can be supported by defining, in a 3GPP specification, one of the 3GPP specific EtherType values for use in carrying WLCP frames.</p> <p>As part of the 'UE initiated Connectivity to PDN in WLAN GTP S2a' procedure the TWAG allocates an EtherType value for each PDN connection which is being established and indicates this EtherType assignment and its association with a specific PDN connection to the UE using WLCP.</p> <p>Other procedures such as handover and PDN disconnection procedures make use of WLCP in the same way.</p> <ul style="list-style-type: none"> <li>• UE learns TWAG MAC address: DHCP/ARP on broadcast MAC addr</li> <li>• UE learns EtherType/PDN connection binding: WLCP</li> <li>• TWAG learns device MAC address: WLCP</li> <li>• TWAG learns GTP/EtherType binding: TWAG configures it</li> </ul> | +| Solution 2: Layer 2 solution based on per-APN/NSWO VLAN marking | Yes | <p>The first preparation step within the 'UE requested PDN or NSWO connectivity' (Section 8.2.2.1.3) procedure would be modified so that the UE can be informed, for each APN, of one EtherType value to be used for conveying user plane traffic and a second value to be used for conveying DHCP traffic that is associated with that APN. This request and response signaling takes place via extensions to EAP-AKA or ANQP.</p> <p>In the second execution step of this procedure the UE sends a DHCP request message using the EtherType value which has been allocated for carrying DHCP messages that is associated with the particular APN for which the IP address is being requested. When the TWAG receives this message it can determine, using the source (device) MAC address and the EtherType setting for which PDN the session is to be set up. The DHCP signaling from TWAG to the UE which carries the allocated IP address also makes use of this APN and DHCP specific EtherType header value when building the Layer 2 frame, so that the UE can associate the allocated IP address with the correct PDN connection.</p> <p>Similarly, PDN disconnection makes use of the same EtherType values at Layer 2 for conveying the DHCP signaling to release the IP address.</p> <p>If this signaling approach were to be adopted and if up to 11 APN's per device are to be supported then 3GPP would need to request 22 EtherType values from the IEEE RA.</p> | + +| | | | +|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | <ul style="list-style-type: none"> <li>UE learns TWAG MAC address: DHCP/ARP on broadcast MAC addr</li> <li>UE learns EtherType/PDN connection binding: EAP-AKA / ANQP</li> <li>TWAG learns device MAC address: During second DHCP execution step</li> <li>TWAG learns GTP/EtherType binding: TWAG configures it</li> </ul> | +| Solution 3: Stateful DHCP based solution | Yes | <p>The DHCP messaging is modified so that instead of the UE / TWAG indicating GRE keys the UE /TWAG indicates the EtherType value that will be used by certain PDN connections.</p> <ul style="list-style-type: none"> <li>UE learns TWAG MAC address: DHCP/ARP on broadcast MAC addr</li> <li>UE learns EtherType/PDN connection binding: modifications to DHCP</li> <li>TWAG learns device MAC address: DHCP procedure</li> <li>TWAG learns GTP/EtherType binding: TWAG configures it</li> </ul> | +| Solution 4 | N/A | No signalling solution provided. | +| Solution 5: Associating APN/PDN with virtual IP interface | Partially (some aspects of the solution may be used in conjunction with SNAP/LLC based approach) | <p>Solution 8 (SNAP/LLC based user plane) does support the use of a new 3GPP defined 'PDN Control protocol' as is defined as part of this solution. However, the methods described in Solution 5 for transporting the 'PDN Control Protocol', eg use of ICMP Echo payload or 802.11 GAS frame are competing methods to the approach proposed in Solution 8 (which instead would support such a 'PDN Control protocol' through the use of a specific EtherType value).</p> <p>(See for example comments under solution 1)</p> | +| Solution 6: X | Yes | <p>This approach proposes the use of a new 3GPP specified TSM (TWAN Session Management) control plane protocol to run between the UE and the TWAG. Solution 8 provides support for a new control plane protocol as discussed above.</p> <p>Instead of delineating PDN connections through VLAN ID or TWAG MAC address, if this signaling solution were to be combined with Solution 8 then Ethertype would be used to distinguish between PDN connections. These settings would be conveyed between UE and TWAG within the TSM protocol.</p> <ul style="list-style-type: none"> <li>UE learns TWAG MAC address: DHCP/ARP on broadcast MAC addr</li> <li>UE learns EtherType/PDN connection binding: TSM</li> <li>TWAG learns device MAC address: TSM</li> <li>TWAG learns GTP/EtherType binding: TWAG configures it</li> </ul> | +| Solution 7: PPP over Ethernet (PPPoE) | No | If a PPPoE approach is adopted for signaling then it would seem logical to use it in conjunction with the PPPoE user plane solution. | +| Solution 8 – Solution using new 3GPP specific LLC/SNAP header | N/A | | +| Solution 9 – EAP based signaling solution | Yes | EAP based signaling can be used for conveying the association between a specific PDN connection and an EtherType value. | + +| | | | +|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | <ul style="list-style-type: none"> <li>• UE learns TWAG MAC address: DHCP/ARP on broadcast MAC addr or EAP</li> <li>• UE learns EtherType/PDN connection binding: EAP modification.</li> <li>• TWAG learns device MAC address: May require TWAN internal signaling to communicate this setting to the TWAG from the entity terminating EAP.</li> <li>• TWAG learns GTP/EtherType binding: TWAN sets it. May require TWAN internal signaling to communicate this setting to the TWAG.</li> </ul> | +|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### 8.2.8.3 Impacts on existing nodes or functionality + +Editor's Notes: Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause. + +#### 8.2.8.4 Evaluation + +The evaluation of this user plane solution against relevant evaluation criteria is provided below: + +- i) Impacts to existing network deployment + - a. New requirements on WLAN APs compared to Rel-11 + - i. No new requirements + - b. Additional assumptions on AP-TWAG link + - i. No additional assumptions +- ii) Impacts to UE + - a. UE needs to populate EtherType value appropriately for the given PDN connection / control plane protocol. +- iii) Impacts to 3GPP protocols/extensions (e.g. EAP AKA') + - a. N/A (Solution 8 defines user plane solution between UE and TWAG) +- iv) Impacts to protocols defined by other SDOs (e.g. DHCP) + - a. No impact to protocols. + - i. 3GPP would need to ask the IEEE Registration Authority for multiple (eg 12) new EtherType values to be allocated for use by 3GPP. +- v) Control plane + - a. Latency/load of first/additional PDN connections setup and handover procedures + - i. N/A (Solution 8 is a user plane solution) + - b. Network element impacts (e.g. AAA signaling etc.) + - i. N/A (Solution 8 is a user plane solution) +- vi) Compliance to clause 8.1 SaMOG phase-2 system requirements + - a. Co-existence with Rel-11 SaMOG + +- i. This solution can coexist with Rel 11 SaMOG on the user plane. + - b. Support for IP address preservation during handover + - i. N/A (Solution 8 is a user plane solution) + - c. Simultaneous support for S2a EPC-routed and NSWO; support of simultaneous multiple PDN connections + - i. This is supported. +- vii) Others functional limitations + - i. None + +### 8.2.9 Solution 9: EAP based signaling solution + +#### 8.2.9.1 Functional Description + +**Editor's Notes: It should be described whether and how the solution fulfils the requirements in Subclause 8.1.** + +##### 8.2.9.1.1 General + +In this solution all 3GPP specification signaling between the UE and the network is carried within EAP signaling. This solution is based on defining a new attribute for EAP to transfer 3GPP specific information (e.g. APN, handover indication) between the UE and the network. This type of new attribute for EAP is also needed if EAP is used to create the first PDN connection at initial attach, but other mechanisms are used for creating additional PDN connections as it is described e.g. in solution 1 (section 8.2.1). The solution works in the following way. + +1) How the UE triggers the creation of the new PDN Connections: + +The assumption is that the UE has already been authenticated to the TWAN. When a new PDN Connection needs to be created the UE sends an IEEE 802.1X EAPoL Start message to the authenticator. The authenticator responds, as it must, with EAP-Request/Identity. The UE responds to this as expected for a re-authentication. The UE indicates the APN and other 3GPP specific parameters within the EAP-Response/AKA'-Reauthentication and EAP-Response/AKA'-Challenge messages in a new EAP attribute. + +2) How the EAP-Server indicates the support for the functionality described in this solution: + +The network can indicate the support for the functionality described in this solution within EAP-Request/AKA'-Reauthentication and EAP-Request/AKA'-Challenge messages in a new EAP attribute. + +3) How the network indicates to the UE that the creation of the new PDN Connection failed: + +A new AT\_NOTIFICATION notification code has to be defined. This code is sent by the EAP-server in EAP-Request/AKA'-Notification to the UE. The general rule is that both S and P bits must be set to 0, i.e. indicating an error after a successful authentication, because the APN & PDN specific authorization failed. + +4) How the network indicates to the UE that the creation of the PDN succeeded: + +A network specific information prior to or during the PDN Connection establishment is sent to the UE using a success-indicating EAP-Request/AKA'-Notification (such as VLAN tags, selected APN). + +5) How the UE or the network initiates a deletion of the PDN Connection. + +A UE can also trigger the release of a PDN connection using the (fast) re-authentication mechanism. The UE acts like in case 1) but sends different values within the messages to the network. The network initiated PDN Connection release is done by the network requesting a (fast) re-authentication. The indication that the PDN connection is released is included in the EAP-Response/AKA' Reauthentication or EAP-Response/AKA'-Challenge messages. + +The mechanism proposed does not depend on the selected user plane mechanism selected for SaMOG phase 2 as transporting EAP messages is possible in all anticipated solutions. + +As the capability indication from the network side is possible, the implementation of supporting additional PDN connection establishment in the network can also be optional. As there might be deployments where the additional PDN connection support is not needed, it is proposed to make this feature optional in the specification, however the proposed solution can also be specified in a way that the support of additional PDN creation in the network is mandatory. + +##### 8.2.9.1.2 Protocol stack + +The authentication procedure used in this solution follows the Authentication and key agreement procedures specified in section 6 of TS 33.402 [28]. Beyond the proposed additional parameters no other change is needed. + +Figure 8.2.9.1.2-1 shows the protocol stack that can be used together for authentication, capability negotiation and signaling for PDN connection management. + +![Figure 8.2.9.1.2-1: Protocol stack for authentication related signalling. The diagram shows the protocol layers across five entities: UE, SWw, TWAN (authenticator), STa, and 3GPP AAA Proxy/Server. The layers are: 3GPP ext., EAP-AKA', EAPoL (IEEE 802.1X), L1/L2. The TWAN (authenticator) contains a DIAMETER and Transport layer. The 3GPP AAA Proxy contains a DIAMETER and Transport layer. The 3GPP AAA Server contains a DIAMETER and Transport layer. The SWw and STa are represented by vertical dashed lines.](896e86ed12aff206d302c64f2e3091fa_img.jpg) + +| | | | | | | | +|----|---------------------|----------------------|---------------------|----------------|-----------------|---------------------| +| UE | 3GPP ext. | | | | | 3GPP ext. | +| | EAP-AKA' | | | | | EAP-AKA' | +| | EAPoL (IEEE 802.1X) | | EAPoL (IEEE 802.1X) | DIAMETER | DIAMETER | EAPoL (IEEE 802.1X) | +| | L1/L2 | | L1/L2 | Transport | Transport | L1/L2 | +| | SWw | TWAN (authenticator) | STa | 3GPP AAA Proxy | 3GPP AAA Server | | + +Figure 8.2.9.1.2-1: Protocol stack for authentication related signalling. The diagram shows the protocol layers across five entities: UE, SWw, TWAN (authenticator), STa, and 3GPP AAA Proxy/Server. The layers are: 3GPP ext., EAP-AKA', EAPoL (IEEE 802.1X), L1/L2. The TWAN (authenticator) contains a DIAMETER and Transport layer. The 3GPP AAA Proxy contains a DIAMETER and Transport layer. The 3GPP AAA Server contains a DIAMETER and Transport layer. The SWw and STa are represented by vertical dashed lines. + +**Figure 8.2.9.1.2-1: Protocol stack for authentication related signalling** + +3GPP access authentication based on EAP-AKA' as defined in IEEE RFC 5448 [27] (together with still necessary, 3GPP defined extensions) is performed end-to-end between UE and 3GPP AAA Server. Between UE and the TWAN/authenticator the information is transported over EAPoL (see IEEE 802.1X [5]). Between TWAN/authenticator and 3GPP AAA Server the EAP-AKA' payload is transported within Diameter messages. The following information is assumed to be exchanged newly, i.e. in addition to Rel. 11: + +- handover indication (from UE to NW); +- APN (requested one from UE to NW, selected one from NW to UE); +- success/failure of PDN connection request (from NW to UE); +- PDN connection identifier (from NW to UE at PDN connection establishment or teardown, from UE to NW at PDN connection teardown) +- User plane connection identifier (e.g. VLAN tag) + +However the solution is not limited in transferring the above listed parameters, other parameters could also be sent. + +Some examples how EAP procedures can be used for sending session management information between the UE and TWAN are presented. The principle is that the TWAN can read the parameters sent by the UE from EAP messages, but cannot modify them. This is possible as during EAP-AKA' the EAP messages are integrity protected, but not encrypted. When the TWAN needs to send a parameter to the UE, it inserts it in the Diameter message sent to the 3GPP AAA server and then the 3GPP AAA server moves the received parameter from the Diameter message to the consecutive EAP message. + +##### 8.2.9.1.3 Signaling information from UE to the network + +In Figure 8.2.9.1.3-1 an example is presented how the UE can send the requested APN to the TWAN during a fast re-authentication when a new PDN connection is established and how the network can send back the selected APN to the UE. Other session management parameters (e.g. handover indication, VLAN tags) can be sent in a similar manner + +![Sequence diagram showing the interaction between UE, TWAN, and 3GPP AAA server for sending the requested APN to the TWAN. The sequence starts with an Authentication Trigger from UE to TWAN. The TWAN sends an EAP REQ/Identity to the UE. The UE responds with an EAP RSP/Identity. The TWAN then sends a Diameter (EAP RSP/Identity) to the 3GPP AAA server. The 3GPP AAA server responds with a Diameter (EAP REQ/AKA'-ReAuth) to the TWAN. The TWAN sends an EAP REQ/AKA'-ReAuth to the UE. The UE responds with an EAP RSP/AKA'-ReAuth (R-APN) to the TWAN. The TWAN then reads the Requested APN from the EAP message and adds the Selected APN into the Diameter message. The TWAN sends a Diameter (EAP RSP/AKA'-ReAuth, S-APN) to the 3GPP AAA server. The 3GPP AAA server moves the S-APN into the EAP message and sends a Diameter (EAP REQ/AKA'-Notif, (S-APN)) to the TWAN. The TWAN sends an EAP REQ/AKA'-Notif (S-APN) to the UE. The UE responds with an EAP RSP/AKA'-Notif to the TWAN. The TWAN sends a Diameter (EAP RSP/AKA'-Notif) to the 3GPP AAA server. The 3GPP AAA server sends a Diameter (EAP Success) to the TWAN. The TWAN sends an EAP Success to the UE.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant AAA as 3GPP AAA server + + Note left of UE: 0. Authentication Trigger + UE->>TWAN: 1. EAP REQ/Identity + TWAN->>UE: 2a. EAP RSP/Identity + TWAN->>AAA: 2b. Diameter (EAP RSP/Identity) + AAA->>TWAN: 3a. Diameter (EAP REQ/AKA'-ReAuth) + TWAN->>UE: 3b. EAP REQ/AKA'-ReAuth + UE->>TWAN: 4a. EAP RSP/AKA'-ReAuth (R-APN) + Note right of TWAN: 4b. Reading Requested APN from EAP message + Note right of TWAN: 4c. Adding Selected APN into Diameter message + TWAN->>AAA: 4d. Diameter (EAP RSP/AKA'-ReAuth, S-APN) + Note right of AAA: 5a. Moving S-APN into EAP message + AAA->>TWAN: 5b. Diameter (EAP REQ/AKA'-Notif, (S-APN)) + TWAN->>UE: 5v. EAP REQ/AKA'-Notif (S-APN) + UE->>TWAN: 6a. EAP RSP/AKA'-Notif + TWAN->>AAA: 6b. Diameter (EAP RSP/AKA'-Notif) + AAA->>TWAN: 7a. Diameter (EAP Success) + TWAN->>UE: 7b. EAP Success + +``` + +Sequence diagram showing the interaction between UE, TWAN, and 3GPP AAA server for sending the requested APN to the TWAN. The sequence starts with an Authentication Trigger from UE to TWAN. The TWAN sends an EAP REQ/Identity to the UE. The UE responds with an EAP RSP/Identity. The TWAN then sends a Diameter (EAP RSP/Identity) to the 3GPP AAA server. The 3GPP AAA server responds with a Diameter (EAP REQ/AKA'-ReAuth) to the TWAN. The TWAN sends an EAP REQ/AKA'-ReAuth to the UE. The UE responds with an EAP RSP/AKA'-ReAuth (R-APN) to the TWAN. The TWAN then reads the Requested APN from the EAP message and adds the Selected APN into the Diameter message. The TWAN sends a Diameter (EAP RSP/AKA'-ReAuth, S-APN) to the 3GPP AAA server. The 3GPP AAA server moves the S-APN into the EAP message and sends a Diameter (EAP REQ/AKA'-Notif, (S-APN)) to the TWAN. The TWAN sends an EAP REQ/AKA'-Notif (S-APN) to the UE. The UE responds with an EAP RSP/AKA'-Notif to the TWAN. The TWAN sends a Diameter (EAP RSP/AKA'-Notif) to the 3GPP AAA server. The 3GPP AAA server sends a Diameter (EAP Success) to the TWAN. The TWAN sends an EAP Success to the UE. + +**Figure 8.2.9.1.3-1: Sending the requested APN to the TWAN** + +- Step 0. The UE triggers a new EAP authentication. + +*.Editor's Note: It is FFS how the UE can trigger a new authentication, especially if IEEE 802.1X EAPoL Start message can trigger a new EAP authentication.* + +- Step 1-3: These steps are performed as in 3GPP TS 33 402 [28]. +- Step 4: The UE adds the requested APN (and other session management parameters) into the EAP message into a new EAP information element. The TWAN reads the requested APN from the EAP message and adds the selected APN (and other session management parameters including the indication of success or failure of the PDN connection establishment) as a Diameter information element to the Diameter message sent to the 3GPP AAA server. Note that the requested APN is not removed from the EAP message as the TWAN cannot modify the EAP message. +- Step 5: The 3GPP AAA server extracts the selected APN from the Diameter message and inserts it into the EAP message in a new information element. Note that the 3GPP AAA server ignores the requested APN received in the EAP message and does not interpret the selected APN received in Diameter, it just copies the Selected APN value from the received Diameter message into the EAP message to be sent. The UE receives the selected APN (and other session management parameters) within the EAP message. +- Step 6-7: these steps are performed as in 3GPP TS 33 402 [28]. + +##### 8.2.9.1.4 Signaling information from the network to the UE + +In Figure 8.2.9.1.4-1 an example is presented how the network can send an indication to the UE that a PDN connection is released during a fast re-authentication. Other parameters (e.g. handover indication) can be sent in a similar manner. + +![Sequence diagram showing the PDN connection release procedure between UE, TWAN, and 3GPP AAA server. The diagram illustrates the exchange of EAP and Diameter messages, with a specific 'Release Indication' being added to the Diameter message and then moved into the EAP message by the 3GPP AAA server.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant AAA as 3GPP AAA server + + Note right of TWAN: 2b. Adding Release Indication into Diameter + Note right of AAA: 3a. Moving Rel-Ind into EAP message + + UE->>TWAN: 1. EAP REQ/Identity + TWAN-->>UE: 2a. EAP RSP/Identity + TWAN->>AAA: 2b. Diameter (EAP RSP/Identity, Rel-Ind) + AAA-->>TWAN: 3b. Diameter (EAP REQ/AKA'-ReAuth (Rel-Ind)) + Note right of AAA: 3a. Moving Rel-Ind into EAP message + AAA-->>UE: 3c. EAP REQ/AKA'-ReAuth (Rel-Ind) + UE-->>TWAN: 4a. EAP RSP/AKA'-ReAuth + TWAN->>AAA: 4b. Diameter (EAP RSP/AKA'-ReAuth) + AAA-->>TWAN: 5a. Diameter (EAP REQ/AKA'-Notif) + TWAN-->>UE: 5b. EAP REQ/AKA'-Notif + AAA-->>TWAN: 6b. Diameter (EAP RSP/AKA'-Notif) + TWAN-->>UE: 6a. EAP RSP/AKA'-Notif + AAA-->>TWAN: 7a. Diameter (EAP Success) + TWAN-->>UE: 7b. EAP Success + +``` + +Sequence diagram showing the PDN connection release procedure between UE, TWAN, and 3GPP AAA server. The diagram illustrates the exchange of EAP and Diameter messages, with a specific 'Release Indication' being added to the Diameter message and then moved into the EAP message by the 3GPP AAA server. + +**Figure 8.2.9.1.4-1: Sending the PDN connection release to the UE** + +- Step 1-2a: These steps are performed as in 3GPP TS 33 402 [28]. +- Step 2b-2c: The TWAN adds the indication of the PDN connection release into the Diameter message within a Diameter information element. This indication shall contain an identifier of the release PDN connection to be released. +- Step 3a: The 3GPP AAA server extracts the Release Indication from the Diameter message and inserts it into the EAP message in a new information element. Note that the 3GPP AAA server does not interpret the Release Indication, it just copies it from the received Diameter message into the EAP message. +- Step 3b-3c: The UE receives the Release Indication within the EAP message. +- Step 4-8: These steps are performed as in 3GPP TS 33 402 [28]. After the successful EAP procedure the UE shall consider the PDN connection released. + +In the procedures described below the principles presented in this section are used to carry session management information within EAP signaling, but for the sake of simplicity the details are not presented within the procedures. + +#### 8.2.9.2 Procedures + +**Editor's Notes: The call flows are described in this subclause.** + +##### 8.2.9.2.1 Initial Attach in WLAN on S2a + +The initial attach procedure is the same as (or similar to) the initial attach procedure described in section 8.2.1.2 with the following addition: + +In step 2 of Figure 8.2.1.2.1.1-1 during the EAP authentication within the capability indication the TWAN shall also indicate if it supports the creation of additional PDN connections or a simultaneous NSWO connection. This additional capability indication is only needed if the support of additional PDN connections or simultaneous NSWO connection creation is optional. + +##### 8.2.9.2.2 UE-Initiated Connectivity to Additional PDN in WLAN on S2a + +##### 8.2.9.2.2.1 UE-Initiated Connectivity to Additional PDN in WLAN on GTP S2a + +This procedure is used to create additional PDN connections or when the UE is authenticated to the network (via EAP-AKA') and has a NSWO session. + +![Sequence diagram titled 'Roaming Scenarios' showing UE-initiated connectivity to an additional PDN in WLAN on GTP S2a. The diagram is divided into two parts, (A) and (B). Part (A) shows the initial connection establishment, and Part (B) shows a subsequent connection establishment. The participants are UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS / 3GPP AAA Server. The sequence starts with '0. Existing authentication' between UE and TWAN. In part (A), the UE sends an 'Authentication trigger' (1) to the TWAN, which initiates 'EAP Authentication' (2). The TWAN sends a 'Create Session Request' (3) to the PDN GW, which triggers the 'IP-CAN Session Establishment Procedure' (4) involving the vPCRF and AAA Proxy. The PDN GW sends an 'Update PDN GW Address' (5) to the HSS / 3GPP AAA Server, which returns a 'Create Session Response' (6) to the PDN GW. The PDN GW then sends a 'Create Session Response' (6) to the TWAN, which establishes a 'GTP Tunnel' (7). The TWAN sends 'EAP authentication Completion' (8) to the UE, followed by 'L3 Attach' (9). In part (B), the UE sends another 'Create Session Request' (10) to the TWAN, which is forwarded to the PDN GW. The PDN GW triggers another 'IP-CAN Session Establishment Procedure' (11) and sends an 'Update PDN GW Address' (12) to the HSS / 3GPP AAA Server. The PDN GW returns a 'Create Session Response' (13) to the TWAN, which establishes another 'GTP Tunnel' (14). Finally, the TWAN sends 'L3 Attach Completion' (15) to the UE.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +Sequence diagram titled 'Roaming Scenarios' showing UE-initiated connectivity to an additional PDN in WLAN on GTP S2a. The diagram is divided into two parts, (A) and (B). Part (A) shows the initial connection establishment, and Part (B) shows a subsequent connection establishment. The participants are UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS / 3GPP AAA Server. The sequence starts with '0. Existing authentication' between UE and TWAN. In part (A), the UE sends an 'Authentication trigger' (1) to the TWAN, which initiates 'EAP Authentication' (2). The TWAN sends a 'Create Session Request' (3) to the PDN GW, which triggers the 'IP-CAN Session Establishment Procedure' (4) involving the vPCRF and AAA Proxy. The PDN GW sends an 'Update PDN GW Address' (5) to the HSS / 3GPP AAA Server, which returns a 'Create Session Response' (6) to the PDN GW. The PDN GW then sends a 'Create Session Response' (6) to the TWAN, which establishes a 'GTP Tunnel' (7). The TWAN sends 'EAP authentication Completion' (8) to the UE, followed by 'L3 Attach' (9). In part (B), the UE sends another 'Create Session Request' (10) to the TWAN, which is forwarded to the PDN GW. The PDN GW triggers another 'IP-CAN Session Establishment Procedure' (11) and sends an 'Update PDN GW Address' (12) to the HSS / 3GPP AAA Server. The PDN GW returns a 'Create Session Response' (13) to the TWAN, which establishes another 'GTP Tunnel' (14). Finally, the TWAN sends 'L3 Attach Completion' (15) to the UE. + +**Figure 8.2.9.2.2.1-1: UE-Initiated Connectivity to Additional PDN in WLAN on GTP S2a** + +The procedure is as in section 8.2.1.2.1.1 (Initial Attach in WLAN on GTP S2a for solution 1) with the following additions: + +- Step 0: The precondition of this procedure is that the UE has valid authentication with the TWAN. The UE might have an existing PDN connection or might use NSWO capability of the TWAN. +- Step 1: The UE triggers a new EAP authentication by sending an IEEE 802.1X EAPoL Start message to the authenticator. +- Step 2: An EAP authentication using Fast Reauthentication is performed if possible, otherwise a full authentication is performed. The UE indicates the APN and other 3GPP specific parameters within the EAP-Response/AKA'-Reauthentication and EAP-Response/AKA'-Challenge messages in a new EAP attribute in a similar way as it is indicated during initial attach. +- Step 8: After the successful PDN connection establishment the EAP procedure is completed. Within this step the TWAN sends back information about the established PDN connection (e.g. success indication, necessary user plane parameters, such as VLAN tag). +- During the procedure a new virtual point-to-point between the UE and the TWAG is created for the new PDN connection (on NSWO session). When and how this is performed depends on the mechanism used for point-to-point link creation. + +##### 8.2.9.2.2.2 UE-Initiated Connectivity to Additional PDN in WLAN on PMIP S2a + +The required additions to the procedure are the same as the ones described for GTP S2a (see previous section) as the proposed additions to the EAP procedures do not depend on the protocol used over S2a. + +##### 8.2.9.2.3 Handover procedure between 3GPP access and WLAN on S2a + +###### 8.2.9.2.3.1 Handover from 3GPP access to WLAN on GTP S2a + +This procedure is used to hand over a PDN connection from 3GPP access to WLAN on GTP S2a. If multiple PDN connections are handed over then this procedure is invoked for each PDN connections separately. + +![Sequence diagram for Handover from 3GPP access to WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/3GPP AAA Server. The process starts with an existing PDN connection over 3GPP. Step 1 involves authentication with the TWAN. Step 2 involves EAP Authentication between the UE and the AAA Proxy. Step 3 involves steps 3-15 from Figure 8.2.x.2.2.1-1. Step 4 involves resource release in the 3GPP RAN and CN. A 'Roaming Scenarios' box groups the vPCRF, AAA Proxy, and hPCRF.](50214d232017279410e9c9db8eb75119_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_3GPP_AAA_Server as HSS / 3GPP AAA Server + + Note over UE, PDN_GW: 0. Existing PDN connection over 3GPP + Note over UE, PDN_GW: 1. Step 2 of Figure 8.2.1.2.1.1-1 or Step 2 of Figure 8.2.9.2.2.1-1 + Note over UE, AAA_Proxy: 2. EAP Authentication + Note over AAA_Proxy, HSS_3GPP_AAA_Server: 2. Authentication & Authorization + Note over UE, PDN_GW: 3. Steps 3-15 in Figure 8.2.x.2.2.1-1 + Note over UE, PDN_GW: 4. Resource release in 3GPP RAN and CN + +``` + +Sequence diagram for Handover from 3GPP access to WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/3GPP AAA Server. The process starts with an existing PDN connection over 3GPP. Step 1 involves authentication with the TWAN. Step 2 involves EAP Authentication between the UE and the AAA Proxy. Step 3 involves steps 3-15 from Figure 8.2.x.2.2.1-1. Step 4 involves resource release in the 3GPP RAN and CN. A 'Roaming Scenarios' box groups the vPCRF, AAA Proxy, and hPCRF. + +**Figure 8.2.9.2.3.1-1: Handover from 3GPP access to WLAN on GTP S2a** + +During the steps of Figure 8.2.9.2.3.1-1 the following should be taken into account: + +- Step 0: The UE is connected in the 3GPP Access and has a PMIPv6 or GTP tunnel on the S5/S8 interface. +- Step 1: If the UE has no valid authentication with the TWAN, i.e. the UE has neither a PDN connection nor a NSWO connection then this step is the same as step 2 of 8.2.1.2.1.1-1. If the UE has a valid authentication with the TWAN either due to the UE having an existing PDN connection or using NSWO capability of the TWAN, then this step is the same as step 2 of 8.2.9.2.2.1-1. +- Step 2: As step 2 in 8.2.9.2.2.1-1 with the following addition: the UE indicates handover via EAP to the 3GPP AAA Server. +- Step 3: The same as step 3-15 in 8.2.9.2.2.1-1 with the addition that handover is performed: the handover indication is set in the Create Session Request to allow the PDN GW to re-allocate the same IP address or prefix that was assigned to the UE while it was connected to the 3GPP IP access and to initiate a PCEF-Initiated IP CAN Session Modification Procedure with the PCRF. +- Step 4: The PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure in 3GPP access as defined in TS 23.402 subclause 5.6.2.2 or the PDN GW Initiated Bearer Deactivation procedure as defined in TS 23.401, subclause 5.4.4.1. + +###### 8.2.9.2.3.2 Handover from 3GPP access to WLAN on PMIP S2a + +The required additions to the procedure are the same as the ones described for GTP S2a (see previous section) as the proposed additions to the EAP procedures do not depend on the protocol used over S2a. + +###### 8.2.9.2.3.3 Handover from TWAN to 3GPP access + +This procedure can be performed as specified in 3GPP TS 23.402 [3]. Solution specific changes are needed when after the handover the PGW initiates the removal of the resources in the TWAN. These changes can be found in section 8.2.9.2.4. + +##### 8.2.9.2.4 PDN GW initiated Resource Allocation Deactivation + +###### 8.2.9.2.4.1 PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a + +This procedure applies when the PDN GW would like to release a PDN connection. + +![Sequence diagram for PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, Roaming Scenarios (vPCRF, AAA Proxy, hPCRF), and HSS / 3GPP AAA Server. The sequence of messages is: 1. IP-CAN sessions Modification (PDN GW to vPCRF), 2. Delete Session Response (PDN GW to TWAN), 3. EAP Authentication (TWAN to UE) and 3. Authentication & Authorization (TWAN to HSS/AAA Server), 4. Delete Session Request (TWAN to PDN GW), 5. Update PDN GW Address (PDN GW to HSS/AAA Server), and 6. TWAN specific Resource Release Procedure (TWAN to UE).](030c758fd425016b03290c8f11bef69d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + vPCRF + AAA_Proxy as AAA Proxy + hPCRF + end + HSS as HSS / 3GPP AAA Server + + PDN_GW-->>vPCRF: 1. IP-CAN sessions Modification + PDN_GW-->>TWAN: 2. Delete Session Response + TWAN->>UE: 3. EAP Authentication + TWAN->>HSS: 3. Authentication & Authorization + TWAN->>PDN_GW: 4. Delete Session Request + PDN_GW->>HSS: 5. Update PDN GW Address + Note left of UE: 6. TWAN specific Resource Release Procedure + +``` + +Sequence diagram for PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, Roaming Scenarios (vPCRF, AAA Proxy, hPCRF), and HSS / 3GPP AAA Server. The sequence of messages is: 1. IP-CAN sessions Modification (PDN GW to vPCRF), 2. Delete Session Response (PDN GW to TWAN), 3. EAP Authentication (TWAN to UE) and 3. Authentication & Authorization (TWAN to HSS/AAA Server), 4. Delete Session Request (TWAN to PDN GW), 5. Update PDN GW Address (PDN GW to HSS/AAA Server), and 6. TWAN specific Resource Release Procedure (TWAN to UE). + +**Figure 8.2.9.2.4.1-1: PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a** + +During the steps of Figure 8.2.9.2.4.1-1 the following should be taken into account: + +- Step 3: An EAP authentication is triggered by the TWAN. Preferably a Fast Reauthentication is performed, but if it is not possible due to any reason then a full authentication is performed. The TWAN indicates that it requests a release of an existing PDN connection within the EAP-Request/AKA'-Reauthentication and EAP-Request/AKA'-Challenge messages in a new EAP attribute. + +NOTE: Step 3 and steps 4 and 5 can be performed simultaneously. + +##### 8.2.9.2.4.2 PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a + +The required additions to the procedure are the same as the ones described for GTP S2a (see previous section) as the proposed additions to the EAP procedures do not depend on the protocol used over S2a. + +##### 8.2.9.2.5 TWAN requested PDN Disconnection Procedures + +###### 8.2.9.2.5.1 TWAN requested PDN Disconnection Procedure in WLAN on GTP S2a + +This procedure applies when multiple PDN connections have been established or when the UE has at least one PDN connection and simultaneously uses NSWO. + +![Sequence diagram for TWAN initiated Resource Allocation Deactivation in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS / 3GPP AAA Server. A 'Roaming Scenarios' box covers the vPCRF, AAA Proxy, and hPCRF. The sequence of messages is: 1. PDN connection release trigger (TWAN to PDN GW); 2. EAP Authentication (TWAN to UE) and 2. Authentication & Authorization (TWAN to HSS/AAA Server); 3. Delete Session Request (TWAN to PDN GW); 4. IP-CAN Session Establishment Procedure (dashed box between PDN GW and vPCRF); 5. Update PDN GW Address (PDN GW to HSS/AAA Server); 6. Delete Session Response (PDN GW to TWAN); 7. TWAN specific Resource Release Procedure (TWAN to UE).](32ff77da4286b58c4778033acaa10836_img.jpg) + +Sequence diagram for TWAN initiated Resource Allocation Deactivation in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS / 3GPP AAA Server. A 'Roaming Scenarios' box covers the vPCRF, AAA Proxy, and hPCRF. The sequence of messages is: 1. PDN connection release trigger (TWAN to PDN GW); 2. EAP Authentication (TWAN to UE) and 2. Authentication & Authorization (TWAN to HSS/AAA Server); 3. Delete Session Request (TWAN to PDN GW); 4. IP-CAN Session Establishment Procedure (dashed box between PDN GW and vPCRF); 5. Update PDN GW Address (PDN GW to HSS/AAA Server); 6. Delete Session Response (PDN GW to TWAN); 7. TWAN specific Resource Release Procedure (TWAN to UE). + +**Figure 8.2.9.2.5.1-1: TWAN initiated Resource Allocation Deactivation in WLAN on GTP S2a** + +During the steps of Figure 8.2.9.2.3.1-1 the following should be taken into account: + +- Step 2. An EAP authentication is triggered by the TWAN. Preferably a Fast Reauthentication is performed, but if it is not possible due to any reason then a full authentication is performed. The TWAN indicates that it requests a release of an existing PDN connection within the EAP-Request/AKA'-Reauthentication and EAP-Request/AKA'-Challenge messages in a new EAP attribute. + +NOTE: An NSWO session that is simultaneously used with PDN connection(s) can also be terminated in this way. If the NSWO offload session is terminated then steps 3-6 are not performed. + +##### 8.2.9.2.5.2 TWAN Initiated Detach and requested PDN Disconnection Procedure in WLAN on PMIP S2a + +The required additions to the procedure are the same as the ones described for GTP S2a (see previous section) as the proposed additions to the EAP procedures do not depend on the protocol used over S2a. + +##### 8.2.9.2.6 UE requested PDN Disconnection Procedures + +##### 8.2.9.2.6.1 UE requested PDN Disconnection Procedure in WLAN on GTP S2a + +This procedure applies when multiple PDN connections have been established or when the UE has at least one PDN connection and simultaneously uses NSWO. + +![Sequence diagram of UE requested PDN Disconnection Procedure in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/3GPP AAA Server. A 'Roaming Scenarios' box covers the vPCRF, AAA Proxy, and hPCRF. The steps are: 1. Authentication trigger (UE to TWAN), 2. EAP Authentication (UE and TWAN), 2. Authentication & Authorization (TWAN to HSS/3GPP AAA Server), 3. Delete Session Request (TWAN to PDN GW), 4. IP-CAN Session Establishment Procedure (PDN GW to vPCRF), 5. Update PDN GW Address (vPCRF to HSS/3GPP AAA Server), 6. Delete Session Response (PDN GW to TWAN), 7. TWAN specific Resource Release Procedure (TWAN).](8e80de0cac529b2c3775d677c5203133_img.jpg) + +Sequence diagram of UE requested PDN Disconnection Procedure in WLAN on GTP S2a. The diagram shows interactions between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/3GPP AAA Server. A 'Roaming Scenarios' box covers the vPCRF, AAA Proxy, and hPCRF. The steps are: 1. Authentication trigger (UE to TWAN), 2. EAP Authentication (UE and TWAN), 2. Authentication & Authorization (TWAN to HSS/3GPP AAA Server), 3. Delete Session Request (TWAN to PDN GW), 4. IP-CAN Session Establishment Procedure (PDN GW to vPCRF), 5. Update PDN GW Address (vPCRF to HSS/3GPP AAA Server), 6. Delete Session Response (PDN GW to TWAN), 7. TWAN specific Resource Release Procedure (TWAN). + +**Figure 8.2.9.2.6.1-1: UE requested PDN Disconnection Procedure in WLAN on GTP S2a** + +During the steps of Figure 8.2.9.2.3.1-1 the following should be taken into account: + +- Step 1. The UE triggers a new EAP authentication. + +**.Editor's Note:** It is FFS how the UE can trigger a new authentication, especially if IEEE 802.1X EAPoL Start message can trigger a new EAP authentication. + +- Step 2. An EAP authentication is performed. Preferably a Fast Reauthentication is performed, but if it is not possible due to any reason then a full authentication is performed. The UE indicates that it requests a release of an existing PDN connection within the EAP-Response/AKA' Reauthentication and EAP-Response/AKA'-Challenge messages in a new EAP attribute. + +**NOTE:** An NSWO session that is simultaneously used with PDN connection(s) can also be terminated in this way. If the NSWO offload session is terminated then steps 3-6 are not performed. + +- Step 3-6: Step 3 is triggered by the PDN connection release request indication received in step 2. + +##### 8.2.9.2.6.2 UE requested PDN Disconnection Procedure in WLAN on GTP S2a on PMIP S2a + +The required additions to the procedure are the same as the ones described for GTP S2a (see previous section) as the proposed additions to the EAP procedures do not depend on the protocol used over S2a. + +##### 8.2.9.2.7 Detach Procedures + +There is nothing special in the detach procedures, they are in principle the same as specified in TS 23.402 [3] for Trusted Non-3GPP Access Networks. If the detach procedure requires to perform PDN connection release procedures then the procedures described above are applicable. + +#### 8.2.9.3 Impacts on existing nodes or functionality + +**Editor's Notes:** Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause. + +The UE shall support an enhanced EAP-AKA' scheme with new attributes in EAP messages. + +The 3GPP AAA server shall support: + +- an enhanced EAP-AKA' scheme with new attributes in EAP messages; +- additional Diameter AVP for parameters sent from TWAN to the UE. + +NOTE: The 3GPP AAA server does not process the new parameters, their values are simply ignored or copied between messages. + +#### 8.2.9.4 Evaluation + +**Editor's Notes:** The fulfilment to the requirements in Subclause 8.1 as well as simplicity of implementation in the UE should be evaluated. + +### 8.2.10 Solution 10 : WCS Solution + +#### 8.2.10.1 Functional Description + +**Editor's Notes:** It should be described whether and how the solution fulfils the requirements in Subclause 8.1. + +##### 8.2.10.1.1 Overview + +This solution proposes a control plane protocol between the UE and the TWAG for mobility management PDN connections. + +This solution supports simultaneous NSWO and PDN connections. + +For the user plane, a virtual MAC address or VLAN is used to differentiate multiple connections (including PDN connections and NSWO connection). + +UE and network capability is negotiated during EAP-AKA' procedure to decide whether the Rel-11 or the Rel-12 SaMOG procedure is performed. + +##### 8.2.10.1.2 User plane + +The point-to-point link required to transport traffic for a given PDN connection, or for Non-Seamless WLAN Offload (NSWO) is realized via the TWAN reserving a distinct VLAN ID or virtual MAC address that uniquely (on a per-UE basis) corresponds to an PDN connection or NSWO. + +The link model for VLAN based user plane is described in 8.2.2.1.1.1, and the link model for virtual MAC based user plane is described in 8.2.2.1.1.2. + +**Editor's Notes:** Whether VLAN or Virtual MAC address is chosen is FFS. + +##### 8.2.10.1.3 Control plane + +A UE-TWAG protocol is used to control (i.e. setup and teardown) the per-PDN point-to-point link. This protocol is denoted as WCS (WLAN Control Signaling) and should be defined by 3GPP. The functions that WCS supports include: Establishment of a per-UE-and-PDN point-to-point link; Tear down of a per-UE-and-PDN point-to-point link; IP address allocation for PDN connections connection. An NSWO connection is established using DHCP or IPv6 stateless autoconfiguration after authentication in the per UE p2p link. + +Reliability of the WCS protocol uses RFC 3315 reliability mechanisms and depends on the reception of a reply message in response to a request message. If no response is received, re-transmission of the request message can use the DHCP re-transmission timer value. No support for fragmentation is provided and is not necessary for the control protocol. + +Three alternatives for the transport of WCS are outlined below. + +**Editor's Notes:** One of these alternatives for protocol transport needs to be chosen. The selection would depend on the choice of user plane. + +###### 8.2.10.1.3.1 Alternative 1: Virtual MAC-based control protocol transport + +The frame format of the control plane is as shown in Figure 8.2.10.1.3-1. + +A new Ethertype is used to identify the WCS protocol. If the virtual MAC address is used by TWAG to differentiate the user plane PDN connections, a dedicated virtual MAC address may also be used to differentiate the control plane. + +The new Ethertype for WCS needs to be defined in IEEE. + +![](036ceaf207a7b289ca76e160892eb724_img.jpg) + +| | | | +|---------|---------------|--------------| +| MAC/LLC | WCS Ethertype | Payload(WCS) | +|---------|---------------|--------------| + +**Figure 8.2.10.1.3-1 Frame format for PDN for Virtual MAC-based control protocol** + +A dedicated p2p Link ID (i.e. (Virtual MAC address) allocated by TWAG is used for WCS signalling. The Virtual MAC address is unique per UE. + +This MAC address is sent to the UE during EAP-AKA' authentication as described in clause 8.2.10.1.3.4. In this case, the p2p link ID in clause 8.2.10.1.3.4 is a Virtual MAC address of the TWAG. + +###### 8.2.10.1.3.2 Alternative 2: VLAN-based control protocol transport + +The frame format of the control plane is as shown in Figure 8.2.10.1.3.2-1. + +![](d116934392360da963e91d840d1e45a8_img.jpg) + +| | | | | +|---------|------|---------------|---------------| +| MAC/LLC | VLAN | New Ethertype | Payload (WCS) | +|---------|------|---------------|---------------| + +**Figure 8.2.10.1.3.2-1 Frame format for PDN for L2.5-based control protocol** + +The VLAN ID is used to differentiate the tunnel between the control plane and the user plane protocol. In the corresponding user plane, the VLAN ID used to distinguish PDN connections. + +As in the case of Alternative 1 (clause 8.2.10.1.3.1), a new Ethertype is needed to indicate that payload is WCS. + +The dedicated p2p link ID (i.e. VLAN ID) used for control plane signalling on top of per UE p2p link is negotiated during the EAP-AKA' procedure. Details of provisioning the p2p link ID (i.e. VLAN ID) are described in clause 8.2.10.1.3.4. The TWAG MAC address is also sent to the UE during EAP-AKA' authentication sequence, along with the VLAN ID. + +###### 8.2.10.1.3.3 Alternative 3: L3-based control protocol transport + +In this alternative, the frame format of the control plane message is as shown in Figure 8.2.10.1.3.3-1. + +![](5cb74e3ca5034698d7eab12de06f8763_img.jpg) + +| | | | +|---------|--------|---------------| +| MAC/LLC | UDP/IP | Payload (WCS) | +|---------|--------|---------------| + +**Figure 8.2.10.1.3.3-1 Frame format for L3-based control protocol** + +The payload contains the WCS control protocol message. The UE gets a link-local address or NSWO address before using L3 based control protocol. The IP address of the TWAG is sent to the UE during the EAP-AKA' procedure in the same as how the TWAG MAC address is delivered in alternative2. + +###### 8.2.10.1.3.4 p2p link ID negotiation in EAP-AKA' procedure. + +This procedure describes the p2p link ID is negotiation during EAP-AKA'. The p2p link ID is used to establish tunnel to transport the control plane protocol (WCS). + +![Sequence diagram for p2p link ID negotiation between UE, Non-3GPP Access, Proxy AAA (optional), 3GPP AAA Server, and HSS. The diagram shows the flow of EAP and AAA messages, including optional AKA' identity negotiation and conditional notification messages.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Non-3GPP Access + participant Proxy AAA (optional) + participant 3GPP AAA Server + participant HSS + + Note left of UE: 1. Connection Established + UE->>Non-3GPP Access: 2. EAP-REQ / Identity + Non-3GPP Access->>UE: 3. EAP-RSP / Identity + Non-3GPP Access->>Proxy AAA: 4. AAA (EAP-RSP/Identity, P2P link ID) + Proxy AAA->>3GPP AAA Server: 5. AAA (EAP-RSP/Identity, P2P link ID) + + Note right of UE: Optional Messages + Non-3GPP Access->>Proxy AAA: 6b. AAA (EAP-REQ / AKA'-Identity) + Proxy AAA->>3GPP AAA Server: 6a. AAA (EAP-REQ / AKA'-Identity) + 3GPP AAA Server->>UE: 7. EAP-REQ / AKA'-Identity + UE->>Non-3GPP Access: 8. EAP-RSP / AKA'-Identity + Non-3GPP Access->>Proxy AAA: 9a. AAA (EAP-RSP / AKA'-Identity) + Proxy AAA->>3GPP AAA Server: 9b. AAA (EAP-RSP / AKA'-Identity) + + 3GPP AAA Server->>HSS: 10a. Request AKA vector + Note right of HSS: 10b. AKA Algorithm executed, outputs AK vector: AKA-RAND, AUTN, XRES + HSS->>3GPP AAA Server: 10c. Return AKA vector + 3GPP AAA Server->>HSS: 11a. Request Profile + HSS->>3GPP AAA Server: 11b. Return Profile + + Note right of 3GPP AAA Server: 12. Derive Keying Material + 3GPP AAA Server->>Proxy AAA: 13a. AAA (EAP-REQ / AKA'-Challenge, P2P link ID) + Proxy AAA->>Non-3GPP Access: 13b. AAA (EAP-REQ / AKA'-Challenge, P2P link ID) + Non-3GPP Access->>UE: 14. EAP-REQ / AKA'-Challenge, P2P link ID + + Note left of UE: 15. UE runs AKA algorithms, verifies AUTN, generates RES, and MSK + UE->>Non-3GPP Access: 16. EAP-RSP / AKA'-Challenge + Non-3GPP Access->>Proxy AAA: 17a. AAA (EAP-RSP / AKA'-Challenge) + Proxy AAA->>3GPP AAA Server: 17b. AAA (EAP-RSP / AKA'-Challenge) + + Note right of 3GPP AAA Server: 18. 3GPP AAA Verifies that AT-RES = XRES + + Note right of UE: Conditional Messages + 3GPP AAA Server->>Proxy AAA: 19a. AAA (EAP-REQ / AKA'-Notification) + Proxy AAA->>Non-3GPP Access: 19b. AAA (EAP-REQ / AKA'-Notification) + Non-3GPP Access->>UE: 20. EAP-REQ / AKA'-Notification + UE->>Non-3GPP Access: 21. EAP-RSP / AKA'-Notification + Non-3GPP Access->>Proxy AAA: 22a. AAA (EAP-RSP / AKA'-Notification) + Proxy AAA->>3GPP AAA Server: 22b. AAA (EAP-RSP / AKA'-Notification) + + 3GPP AAA Server->>Proxy AAA: 23a. AAA (EAP-Success) + Proxy AAA->>Non-3GPP Access: 23b. AAA (EAP-Success) + Non-3GPP Access->>UE: 24. EAP-Success + + Note right of 3GPP AAA Server: 25. Registration + +``` + +Sequence diagram for p2p link ID negotiation between UE, Non-3GPP Access, Proxy AAA (optional), 3GPP AAA Server, and HSS. The diagram shows the flow of EAP and AAA messages, including optional AKA' identity negotiation and conditional notification messages. + +Figure 8.2.10.1.3.4-1 p2p link ID negotiation + +Step4-Step5 TWAG sends the p2p link ID via TWAN to the 3GPP AAA. + +Step 13a,b-14, the p2p link ID is sent in EAP-REQ message to the UE. + +The p2p link ID could be the virtual MAC address or VLAN ID provisioned in the TWAN. + +##### 8.2.10.1.4 Protocol Stacks + +**Editor's Notes:** Impact on link model due to handover support is FFS. + +#### 8.2.10.2 Procedures + +**Editor's Notes:** The call flows are described in this subclause. + +##### 8.2.10.2.1 Initial Attach procedure + +###### 8.2.10.2.1.1 Initial Attach in WLAN on S2a – network capability negotiation + +![Sequence diagram for Initial Attach in WLAN on S2a for roaming and non-roaming scenarios. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The UE and TWAN perform '1. Non-3GPP Specific Procedures' and '2. EAP Authentication'. The PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA are grouped under 'Roaming Scenarios'. The PDN GW sends a message to the AAA Proxy labeled '2. Authentication & Authorization'.](0b452c5334567cbdc22ee9817e1246f5_img.jpg) + +``` +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + end + Note left of UE: 1. Non-3GPP Specific Procedures + Note left of UE: 2. EAP Authentication + UE->>TWAN: + TWAN->>PDN_GW: + PDN_GW->>AAA_Proxy: 2. Authentication & Authorization + AAA_Proxy->>HSS_AAA: + HSS_AAA->>AAA_Proxy: + AAA_Proxy->>PDN_GW: + PDN_GW->>TWAN: + TWAN->>UE: +``` + +Sequence diagram for Initial Attach in WLAN on S2a for roaming and non-roaming scenarios. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The UE and TWAN perform '1. Non-3GPP Specific Procedures' and '2. EAP Authentication'. The PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA are grouped under 'Roaming Scenarios'. The PDN GW sends a message to the AAA Proxy labeled '2. Authentication & Authorization'. + +**Figure 8.2.10.2.1-1: Initial attachment in WLAN on S2a for roaming and non-roaming scenarios** + +The procedure is as in TS 23.402 clause 16.2 with the following additions: + +- Step 2. As part of this step, the UE shall send an indication to the network as to whether it supports Rel-12 SaMOG. Depending on the capabilities of the network and the indication of the UE, the network informs the UE as part of step 2 whether the Rel-12 SaMOG procedures should be performed. + +###### 8.2.10.2.1.2 Initial Attach continuation for GTP based S2a + +![Sequence diagram for Initial Attach continuation for GTP based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It is divided into 'Roaming Scenarios' and 'Non-Roaming Scenarios'. The process starts with Step 1-2 as in clause 8.2.10.2.1. Step 3.1: UE obtains link local IP address. Step 3.2: UE sends attach request (WCS) to TWAN. Step 4: TWAN sends Create Session Request to PDN GW. Step 5: IP-CAN Session Establishment Procedure (dashed box) involving PDN GW, vPCRF, AAA Proxy, and hPCRF. Step 6: PDN GW sends Update PDN GW Address to HSS/AAA. Step 7: PDN GW sends Create Session Response to TWAN. Step 8: GTP Tunnel is established (highlighted in green). Step 9: TWAN sends attach accept (WCS) to UE.](7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + + Note over UE, HSS_AAA: Step 1-2 as in clause 8.2.10.2.1 + Note right of UE: 3.1 UE obtains link local IP address + UE->>TWAN: 3.2 attach request (WCS) + TWAN->>PDN_GW: 4. Create Session Request + Note right of PDN_GW: 5. IP-CAN Session Establishment Procedure + PDN_GW->>HSS_AAA: 6. Update PDN GW Address + PDN_GW->>TWAN: 7. Create Session Response + Note right of TWAN: 8. GTP Tunnel + TWAN->>UE: 9. attach accept (WCS) + +``` + +Sequence diagram for Initial Attach continuation for GTP based S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. It is divided into 'Roaming Scenarios' and 'Non-Roaming Scenarios'. The process starts with Step 1-2 as in clause 8.2.10.2.1. Step 3.1: UE obtains link local IP address. Step 3.2: UE sends attach request (WCS) to TWAN. Step 4: TWAN sends Create Session Request to PDN GW. Step 5: IP-CAN Session Establishment Procedure (dashed box) involving PDN GW, vPCRF, AAA Proxy, and hPCRF. Step 6: PDN GW sends Update PDN GW Address to HSS/AAA. Step 7: PDN GW sends Create Session Response to TWAN. Step 8: GTP Tunnel is established (highlighted in green). Step 9: TWAN sends attach accept (WCS) to UE. + +**Figure 8.2.10.2.1-2: Initial attachment in WLAN on S2a for roaming and non-roaming scenarios** + +The procedure continues from step 2 in clause 8.2.10.2.1: + +- Step 2, as part of the authentication procedure, the p2p link ID for WCS signalling is negotiated between the UE and the TWAG. There are following alternatives to establish the p2p link for WCS: + +- If Alternative 1 (clause 8.2.10.1.3.1) based mechanism is used for WCS, then a (virtual) MAC address of TWAG is sent to the UE. +- If Alternative 2 (clause 8.2.10.1.3.2) based mechanism is used for WCS, then the VLAN ID is negotiated between the UE and the TWAG. Also the MAC address of the TWAG should be sent to the UE. +- If Alternative 3 (clause 8.2.10.1.3.3) based mechanism is used for WCS, the TWAG IP address is sent to the UE. + +- Step 3.1, The UE will get a link local address or NSWO Address from TWAN using RFC 4861 for IPv6, or RFC 3927 for IPv4. The UE can use this IP address for the transport of the control plane protocol to TWAG. If the UE wants to setup an NSWO connection, the UE sends a DHCP Request (and optionally an IPv6 Router Solicitation Request) in this step. + +- Step 3.2: If the UE wants to set up a PDN connection, the UE sends a WCS Attach Request to the TWAN. This message includes AttachType, APN, , PDN type, PCO. The Attach Type field indicates initial attach and the APN field indicates the APN that the UE requests. The PDN type field indicates the IP address type the UE request. The PCO field + +may indicate that the UE wants deferred IP address allocation and if so, the UE will send DHCP/RS after the attach procedures. + +There are two options for user plane p2p link ID. 1) virtual MAC address 2) VLAN ID allocated by the UE + +-Step 4-8 refers to step-3 –step7 in clause 16.2.1 of TS 23.402. Additionally, if the PDN GW receives the PCO which indicates deferred IPv4 address allocation, then the PDN GW will not allocate IP address to the UE at this step. + +Step 9 the TWAN sends a WCS attach accept message to the UE. If the UE does not indicate an APN in the attach request, the TWAN should send the selected APN to the UE. The IP address(es) is also sent to the UE if the PDN GW has allocated the IP address to the UE (i.e., not deferred address for IPv4). . This response contains a User Plane p2p link ID to be used in further signalling associated with this PDN connection. + +If the user plane p2p link is VLAN based, the VLAN ID allocated by the TWAN is included in the p2p link field of the attach accept message. Alternatively, if the user plane p2p link is virtual MAC based, the virtual MAC allocated by the TWAN is included in the p2p link field. + +If the UE requests a deferred IPv4 address allocation, the UE may request for an IP address using DHCP after the attach procedure. DHCP signalling is performed over the established p2p link. In IPv6, prefix assignment takes place using RFC 4861 over the established p2p link. + +###### 8.2.10.2.1.2 Initial Attach in WLAN on PMIP S2a + +**Editor's Notes:** The procedure is FFS. + +##### 8.2.10.2.2 UE-initiated Connectivity to Additional PDN + +This procedure is used when the UE requests additional PDN connections. + +This procedure is also used when the UE requests more PDN connections in the same APN. + +The p2p link is established between UE and TWAG per each PDN connection. + +###### 8.2.10.2.2.1 UE-Initiated Connectivity to PDN in WLAN on GTP S2a + +![Sequence diagram for UE-initiated connectivity to PDN in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves a PDN Connectivity Request from UE to TWAN, followed by an S2a Create Session Request from TWAN to PDN GW. The PDN GW then initiates the IP-CAN Session Establishment Procedure (involving vPCRF, AAA Proxy, and hPCRF), which results in an Update PDN GW Address message to HSS/AAA. The PDN GW then sends an S2a Create Session Response back to TWAN, which establishes a GTP Tunnel. Finally, the TWAN sends a PDN connectivity accepted message to the UE.](4b82c57bac9f5800baee15745b212963_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + subgraph Roaming Scenarios + participant vPCRF + participant AAA_Proxy as AAA Proxy + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + Note right of PDN_GW: Roaming Scenarios + + UE->>TWAN: 1. PDN Connectivity Request + TWAN->>PDN_GW: 2. S2a Create Session Request + PDN_GW-->>vPCRF: 3. IP-CAN Session Establishment Procedure + PDN_GW->>HSS_AAA: 4. Update PDN GW Address + PDN_GW-->>TWAN: 5. S2a Create Session Response + Note right of TWAN: 6. GTP Tunnel + TWAN->>UE: 7. PDN connectivity accepted + +``` + +Sequence diagram for UE-initiated connectivity to PDN in WLAN on GTP S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, AAA Proxy, hPCRF, and HSS/AAA. The process involves a PDN Connectivity Request from UE to TWAN, followed by an S2a Create Session Request from TWAN to PDN GW. The PDN GW then initiates the IP-CAN Session Establishment Procedure (involving vPCRF, AAA Proxy, and hPCRF), which results in an Update PDN GW Address message to HSS/AAA. The PDN GW then sends an S2a Create Session Response back to TWAN, which establishes a GTP Tunnel. Finally, the TWAN sends a PDN connectivity accepted message to the UE. + +**Figure 8.2.10.2.2.1-1: UE initiated connectivity to PDN/NSWO** + +- Step 1. The UE triggers the establishment of a new per-UE and per-PDN point-to-point link. The UE sends WCS PDN Connectivity Request (APN, PDN Type, Protocol Configuration Options, Request Type). The Request Type indicates "initial request" if the UE requests new additional PDN connectivity over the 3GPP access network for multiple PDN connections, the Request Type indicates "handover" when the UE is performing a handover from 3GPP access and the UE has already established connectivity with the PDN over the 3GPP access. +- Step 2-6. Same as step 3-7 in clause 8.2.10.2.2.1. As part of these steps, the TWAN verifies that the APN requested by the UE is allowed by subscription. Upon handover, the TWAN selects the PDN GW handling this PDN connection; otherwise, the TWAN performs PDN GW selection as described in TS 23.402. Steps 2-6 are executed with the selected PDN GW. +- Step 7. The TWAN replies with WCS PDN connectivity accept to the UE. This response contains a p2p link id to be used in further signalling associated with this PDN connection. +- If the UE requests deferred IPV4 address allocation, it may negotiate the IPv4 address with DHCPv4 after step7. + +###### 8.2.10.2.2.2 UE-Initiated Connectivity to PDN in WLAN on PMIP S2a + +Editor's Notes: The procedure is FFS. + +##### 8.2.10.2.3 Handover procedure in multi-connection scenario from 3GPP access to WLAN on S2a + +###### 8.2.10.2.3.1 Handover in multi-connection scenario from 3GPP access to WLAN on GTP S2a + +![Sequence diagram for handover from 3GPP access to WLAN on GTP S2a. Lifelines: UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps 0 through 10, with a 'Roaming Scenarios' box covering vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Step 0 is a GTP/PMIPv6 tunnel between S-GW and PDN GW. Step 1 is 'Non-3GPP Specific Procedures' between UE and TWAN. Step 2 is 'EAP Authentication' between UE and TWAN, and 'Authentication & Authorization' between TWAN and AAA Proxy. Step 3 is 'Handover attach' from UE to TWAN. A dashed box contains 'Step4-step8 in Figure 8.2.10.2.1.2'. Step 9 is 'attach accept' from TWAN to UE. Step 10 is '3GPP EPS bearer release' from PDN GW to S-GW and from TWAN to S-GW.](58bbc570572758132ea39938e4f03b5b_img.jpg) + +Sequence diagram for handover from 3GPP access to WLAN on GTP S2a. Lifelines: UE, TWAN, S-GW, PDN GW, vPCRF, AAA Proxy, hPCRF, HSS/AAA. The diagram shows steps 0 through 10, with a 'Roaming Scenarios' box covering vPCRF, AAA Proxy, hPCRF, and HSS/AAA. Step 0 is a GTP/PMIPv6 tunnel between S-GW and PDN GW. Step 1 is 'Non-3GPP Specific Procedures' between UE and TWAN. Step 2 is 'EAP Authentication' between UE and TWAN, and 'Authentication & Authorization' between TWAN and AAA Proxy. Step 3 is 'Handover attach' from UE to TWAN. A dashed box contains 'Step4-step8 in Figure 8.2.10.2.1.2'. Step 9 is 'attach accept' from TWAN to UE. Step 10 is '3GPP EPS bearer release' from PDN GW to S-GW and from TWAN to S-GW. + +Figure 8.2.10.3.1-1: Handover from 3GPP access to WLAN + +Step1- Step2, same as in clause 8.2.10.2.1-1 + +Step3- Refer to Step3.2 of attach procedure in clause 8.2.10.2.1.2. Attach type indicates handover attach. + +If L3 based WCS is used, then the UE should get a link local IP address or NSWO address before step3 as described in step3.1 of attach procedure in clause 8.2.10.2.1.2. + +Step4-step8: Since these steps represent handover attach, IP address preservation is handled by the PDN GW. + +Step9: same as Step9 of attach procedure in clause 8.2.10.2.1.2. + +8.2.10.2.3.2 Handover in multi-connection scenario from 3GPP access to WLAN on PMIP S2a + +**Editor's Notes: The procedure is FFS.** + +8.2.10.2.4 Handover procedure in multi-connection scenario from WLAN on S2a to 3GPP access + +**Editor's Notes: The procedure is FFS.** + +##### 8.2.10.2.5 Handover procedure from WLAN on S2a to 3GPP access + +![Sequence diagram of the handover procedure from Trusted WLAN on S2a to 3GPP access. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access/ePDG, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. The process involves UE discovery, attachment, authentication, location update, session creation, bearer establishment, and non-3GPP bearer release. Key steps include: 1. PMIPv6 or GTP Tunnel (existing); 2. UE discovers 3GPP access system and initiates HO; 3. Attach; 4. Access Authentication; 5. Location Update and Subscriber Data Retrieval; 6. Create Session Request (MN-NAI, PDN GW); 7. Create Session Request; 8. PCEF-Initiated IP-CAN Session Modification Procedure; 9. Create Session Response; 10. Create Session Response (IP Addr); 11. Radio and Access Bearer Establishment; 12. Modify Bearer Request; 13. Modify Bearer Request; 14. Modify Bearer Response; 15. Modify Bearer Response; 16. Radio and Access Bearer; 16. GTP Tunnel; 17. UE Requested PDN Connectivity; 18. Non-3GPP EPS Bearer Release. The diagram is divided into two main sections: (A) for the session creation and modification, and (B) for the bearer modification. A 'Roaming Scenarios' box groups the AAA Proxy, vPCRF, hPCRF, and HSS/AAA components.](195611c20b2dc7ed0fa3033392e22908_img.jpg) + +The sequence diagram illustrates the handover procedure from a Trusted WLAN on S2a to 3GPP access. The participants involved are: UE, Trusted Non-3GPP IP Access/ePDG, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. The process is as follows: + +1. PMIPv6 or GTP Tunnel (existing between Trusted Non-3GPP IP Access/ePDG and PDN GW) +2. UE discovers 3GPP access system and initiates HO +3. Attach (UE to E-UTRAN) +4. Access Authentication (E-UTRAN to UE, E-UTRAN to AAA Proxy) +5. Location Update and Subscriber Data Retrieval (MME to AAA Proxy) +6. Create Session Request (MN-NAI, PDN GW) (MME to PDN GW) +7. Create Session Request (PDN GW to Old MME/SGSN) - part of (A) +8. PCEF-Initiated IP-CAN Session Modification Procedure (Old MME/SGSN to PDN GW) - part of (A) +9. Create Session Response (Old MME/SGSN to PDN GW) - part of (A) +10. Create Session Response (IP Addr) (PDN GW to MME) +11. Radio and Access Bearer Establishment (MME to E-UTRAN) +12. Modify Bearer Request (MME to PDN GW) +13. Modify Bearer Request (PDN GW to Old MME/SGSN) - part of (B) +14. Modify Bearer Response (Old MME/SGSN to PDN GW) - part of (B) +15. Modify Bearer Response (PDN GW to MME) +16. Radio and Access Bearer (E-UTRAN to UE), 16. GTP Tunnel (PDN GW to Trusted Non-3GPP IP Access/ePDG) +17. UE Requested PDN Connectivity (UE to E-UTRAN) +18. Non-3GPP EPS Bearer Release (PDN GW to Trusted Non-3GPP IP Access/ePDG) + +Sequence diagram of the handover procedure from Trusted WLAN on S2a to 3GPP access. The diagram shows the interaction between UE, Trusted Non-3GPP IP Access/ePDG, E-UTRAN, MME, Serving GW, Old MME/SGSN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. The process involves UE discovery, attachment, authentication, location update, session creation, bearer establishment, and non-3GPP bearer release. Key steps include: 1. PMIPv6 or GTP Tunnel (existing); 2. UE discovers 3GPP access system and initiates HO; 3. Attach; 4. Access Authentication; 5. Location Update and Subscriber Data Retrieval; 6. Create Session Request (MN-NAI, PDN GW); 7. Create Session Request; 8. PCEF-Initiated IP-CAN Session Modification Procedure; 9. Create Session Response; 10. Create Session Response (IP Addr); 11. Radio and Access Bearer Establishment; 12. Modify Bearer Request; 13. Modify Bearer Request; 14. Modify Bearer Response; 15. Modify Bearer Response; 16. Radio and Access Bearer; 16. GTP Tunnel; 17. UE Requested PDN Connectivity; 18. Non-3GPP EPS Bearer Release. The diagram is divided into two main sections: (A) for the session creation and modification, and (B) for the bearer modification. A 'Roaming Scenarios' box groups the AAA Proxy, vPCRF, hPCRF, and HSS/AAA components. + +Figure 8.2.10.2.5-1: Handover from Trusted WLAN on S2a to 3GPP access for roaming, LBO and non-roaming scenarios + +This procedure is as in TS 23.402 clause 8.2.1.1/8.2.1.2 with the following differences: + +- Step 1. There is a GTP or PMIP tunnel between TWAN and PGW. +- Step 18. The PDN GW shall initiate resource allocation deactivation procedure in the TWAN as defined in clause 8.2.10.2.9. + +##### 8.2.10.2.6 UE/TWAN Requested PDN disconnection in WLAN on S2a + +###### 8.2.10.2.6.1 UE/TWAN requested PDN disconnection in WLAN on GTP S2a + +For multiple PDN connections, this disconnection procedure shall be repeated for each PDN connection that needs to be released. + +![Sequence diagram showing the UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN. The participants are UE, TWAN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. Steps include: 1. PDN Disconnect Request (UE to TWAN), 2. Delete Session Request (TWAN to PDN GW), 3. Update PDN GW Address (PDN GW to HSS/AAA via AAA Proxy), 4. PCEF-Initiated IP-CAN Session Termination Procedure (PDN GW with vPCRF/hPCRF), 5. Delete Session Response (PDN GW to TWAN), 6. PDN Disconnect Response (TWAN to UE), 7. PDN Disconnection Request (TWAN to UE), 8. PDN Disconnection Response (UE to TWAN), and 9. TWAN specific resource Release Procedure.](21327313f7b18a481da0c87a6472a80d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + rect rgb(240, 240, 240) + Note over AAA_Proxy, hPCRF: Roaming Scenarios + participant AAA_Proxy as AAA Proxy + participant vPCRF + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + UE-->>TWAN: 1. PDN Disconnect Request + TWAN->>PDN_GW: 2. Delete Session Request + PDN_GW->>HSS_AAA: 3. Update PDN GW Address (via AAA Proxy) + PDN_GW->>vPCRF: 4. PCEF-Initiated IP-CAN Session Termination Procedure + PDN_GW->>TWAN: 5. Delete Session Response + TWAN-->>UE: 6. PDN Disconnect Response + TWAN->>UE: 7. PDN Disconnection Request + UE-->>TWAN: 8. PDN Disconnection Response + Note over UE, TWAN: 9. TWAN specific resource Release Procedure + +``` + +Sequence diagram showing the UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN. The participants are UE, TWAN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. Steps include: 1. PDN Disconnect Request (UE to TWAN), 2. Delete Session Request (TWAN to PDN GW), 3. Update PDN GW Address (PDN GW to HSS/AAA via AAA Proxy), 4. PCEF-Initiated IP-CAN Session Termination Procedure (PDN GW with vPCRF/hPCRF), 5. Delete Session Response (PDN GW to TWAN), 6. PDN Disconnect Response (TWAN to UE), 7. PDN Disconnection Request (TWAN to UE), 8. PDN Disconnection Response (UE to TWAN), and 9. TWAN specific resource Release Procedure. + +**Figure 8.2.10.2.6.1-1: UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN** + +This procedure applies to the Non-Roaming, Home Routed Roaming and Local Breakout cases. In the Local Breakout case, the vPCRF forwards messages between the PDN GW and the hPCRF. In the LBO cases, the 3GPP AAA Proxy serves as an intermediary between the Trusted Non-3GPP IP Access and the 3GPP AAA Server in the HPLMN. In the non-roaming and Home Routed Roaming case, the vPCRF is not involved at all. + +If dynamic policy provisioning is not deployed, the optional steps of interaction between the PDN GW and PCRF do not occur. Instead, the PDN GW may employ static configured policies. + +- **Step 1.** If the PDN disconnection is initiated by the UE, the UE sends a WCS PDN Disconnection Request (p2p link ID) to the TWAG. The p2p link ID identifies a PDN connection uniquely. **Step 2.** The TWAN releases the PDN connection and sends a Delete Session Request (Linked EPS Bearer ID) message for this PDN connection to the PDN GW. +- **Step 3.** The PDN GW informs the 3GPP AAA Server of the PDN disconnection. +- **Step 4.** The PDN GW deletes the IP CAN session associated with the UE and executes a PCEF-Initiated IP-CAN Session Termination Procedure with the PCRF as specified in TS 23.203 [4]. +- **Step 5.** The PDN GW acknowledges with a Delete Session Response (Cause) message. +- **Step 6.** TWAN sends WCS PDN disconnection response to the UE. + +- Step 7. If the PDN disconnection was initiated by the TWAG, then the UE is informed of the disconnection by means of a WCS PDN Disconnection Request (User Plane Connection ID). +- Step 8. The UE acknowledges the disconnection request received in step 7. + +NOTE: Either step 1 and 6, or step 7 and 8, are performed. Step 1 and 6 is used for UE initiated disconnection procedure, step 7 and 8 is for TWAN initiated disconnection procedure. + +NOTE: If NSWO disconnection is performed steps from 2 to 5 are skipped. + +###### 8.2.10.2.6.2 UE TWAN requested PDN disconnection in WLAN on PMIP S2a + +Editor's Notes: The procedure is FFS. + +##### 8.2.10.2.7 UE initiated Detach in WLAN on S2a + +###### 8.2.10.2.7.1 UE initiated Detach in WLAN on GTP S2a + +![Sequence diagram for UE-initiated Detach procedure with GTP S2a in WLAN. The diagram shows interactions between UE, TWAN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box covers the AAA Proxy, vPCRF, and hPCRF. Step 1: UE sends Detach Request to TWAN. Step 2: TWAN sends Delete Session Request to PDN GW. Step 3: PDN GW sends Update PDN GW Address to HSS/AAA. Step 4: A dashed box labeled 'PCEF-Initiated IP-CAN Session Termination Procedure' is shown between PDN GW and vPCRF. Step 5: PDN GW sends Delete Session Response to TWAN. Step 6: TWAN sends Detach Response to UE. Step 7: A dashed box labeled 'TWAN specific resource Release Procedure' is shown between UE and TWAN.](7156cf400ef0e19f9d06a5d0549834a3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + box gray Roaming Scenarios + participant AAA_Proxy as AAA Proxv + participant vPCRF + participant hPCRF + end + participant HSS_AAA as HSS/AAA + + UE->>TWAN: 1. Detach Request + TWAN->>PDN_GW: 2. Delete Session Request + PDN_GW->>HSS_AAA: 3. Update PDN GW Address + rect rgb(255, 255, 255) + Note over PDN_GW, vPCRF: 4. PCEF-Initiated IP-CAN Session Termination Procedure + end + PDN_GW->>TWAN: 5. Delete Session Response + TWAN->>UE: 6. Detach Response + rect rgb(255, 255, 255) + Note over UE, TWAN: 7. TWAN specific resource Release Procedure + end + +``` + +Sequence diagram for UE-initiated Detach procedure with GTP S2a in WLAN. The diagram shows interactions between UE, TWAN, PDN GW, AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A 'Roaming Scenarios' box covers the AAA Proxy, vPCRF, and hPCRF. Step 1: UE sends Detach Request to TWAN. Step 2: TWAN sends Delete Session Request to PDN GW. Step 3: PDN GW sends Update PDN GW Address to HSS/AAA. Step 4: A dashed box labeled 'PCEF-Initiated IP-CAN Session Termination Procedure' is shown between PDN GW and vPCRF. Step 5: PDN GW sends Delete Session Response to TWAN. Step 6: TWAN sends Detach Response to UE. Step 7: A dashed box labeled 'TWAN specific resource Release Procedure' is shown between UE and TWAN. + +**Figure 8.2.10.2.7.1-1: UE -initiated Detach procedure with GTP S2a in WLAN** + +- Step 1 The UE sends a WCS Detach Request to the TWAN. +- Step 2 - Step 5. Same as step 2-5 in clause 8.2.10.2.6.1 The TWAN deleted all the S2a bearers. - Step 6. TWAN send Detach Response to the UE. + +For NSWO connection, the release procedure is the same as TS 23.402 clause 16.3.1.1. + +###### 8.2.10.2.7.2 UE initiated Detach in WLAN on PMIP S2a + +Editor's Notes: This procedure is FFS. + +##### 8.2.10.2.8 HSS/AAA Initiated Detach Procedure in WLAN + +###### 8.2.10.2.8.1 HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a + +![Sequence diagram for HSS/AAA Initiated Detach Procedure with GTP S2a. Lifelines: UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, HSS/AAA. A 'Roaming Scenarios' box covers AAA Proxv, vPCRF, and hPCRF. The sequence includes: 1. Detach Request (HSS/AAA to TWAN), 2. Delete Session Request (TWAN to PDN GW), 3. Update PDN GW Address (PDN GW to HSS/AAA), 4. PCEF-Initiated IP-CAN Session Termination Procedure (dashed box between PDN GW and vPCRF), 5. Delete Session Response (PDN GW to TWAN), 6. Detach Request (TWAN to UE), 7. TWAN specific resource Release Procedure (dashed box between UE and TWAN).](367378559e35017a5e1a6f5c30798c5a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN GW + participant AAA Proxv + participant vPCRF + participant hPCRF + participant HSS/AAA + + Note right of AAA Proxv: Roaming Scenarios + + HSS/AAA->>TWAN: 1. Detach Request + TWAN->>PDN GW: 2. Delete Session Request + PDN GW->>HSS/AAA: 3. Update PDN GW Address + Note right of PDN GW: 4. PCEF-Initiated IP-CAN Session Termination Procedure + PDN GW->>TWAN: 5. Delete Session Response + TWAN->>UE: 6. Detach Request + Note left of UE: 7. TWAN specific resource Release Procedure + +``` + +Sequence diagram for HSS/AAA Initiated Detach Procedure with GTP S2a. Lifelines: UE, TWAN, PDN GW, AAA Proxv, vPCRF, hPCRF, HSS/AAA. A 'Roaming Scenarios' box covers AAA Proxv, vPCRF, and hPCRF. The sequence includes: 1. Detach Request (HSS/AAA to TWAN), 2. Delete Session Request (TWAN to PDN GW), 3. Update PDN GW Address (PDN GW to HSS/AAA), 4. PCEF-Initiated IP-CAN Session Termination Procedure (dashed box between PDN GW and vPCRF), 5. Delete Session Response (PDN GW to TWAN), 6. Detach Request (TWAN to UE), 7. TWAN specific resource Release Procedure (dashed box between UE and TWAN). + +Figure 8.2.10.2.8.1-1: HSS/AAA Initiated Detach Procedure with GTP S2a + +-Step-1 HSS/AAA send Detach Request to the TWAN + +-Step-2-step5 is same as procedure in 8.2.10.2.6.1. + +For NSWO connection, the release procedure is the same as TS 23.402 clause 16.3.1.1. + +###### 8.2.10.2.8.2 HSS/AAA Initiated Detach Procedure in WLAN on PMIP S2a + +Editor's Notes: This procedure is still to be added. + +##### 8.2.10.2.9 PDN GW initiated Resource Allocation Deactivation + +###### 8.2.10.2.9.1 PDN GW initiated Resource Allocation Deactivation in WLAN on GTP S2a + +![Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. The process involves IP-CAN Session Modification, Delete Bearer Request, TWAN specific resource Release Procedure, Delete Bearer Response, and Update PDN GW Address. A 'Roaming Scenarios' box groups the vPCRF, 3GPP AAA proxy, and hPCRF. Steps 7-8 are referenced as being in clause 8.2.10.2.6.1.](1033dc9fde75540d224c907681b1b7aa_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant PDN_GW as PDN GW + participant vPCRF + participant 3GPP_AAA_proxy as 3GPP AAA proxy + participant hPCRF + participant AAA_HSS as AAA/HSS + + Note right of vPCRF: Roaming Scenarios + PDN_GW->>vPCRF: 1. IP-CAN Session Modification + PDN_GW->>TWAN: 2. Delete Bearer Request + Note left of TWAN: Steps 7-8 as in clause 8.2.10.2.6.1 + Note left of TWAN: 3. TWAN specific resource Release Procedure + TWAN->>PDN_GW: 4. Delete Bearer Response + PDN_GW->>AAA_HSS: 5. Update PDN GW Address + PDN_GW->>vPCRF: 6. IP-CAN Session Modification + +``` + +Sequence diagram for PDN GW Initiated Bearer Deactivation with GTP on S2a. The diagram shows the interaction between UE, TWAN, PDN GW, vPCRF, 3GPP AAA proxy, hPCRF, and AAA/HSS. The process involves IP-CAN Session Modification, Delete Bearer Request, TWAN specific resource Release Procedure, Delete Bearer Response, and Update PDN GW Address. A 'Roaming Scenarios' box groups the vPCRF, 3GPP AAA proxy, and hPCRF. Steps 7-8 are referenced as being in clause 8.2.10.2.6.1. + +Figure 8.2.10.2.9.1-1: PDN GW Initiated Bearer Deactivation with GTP on S2a + +The step 1,-6 is same as step 1,2,4,5,6 in Clause 16.4.1 in TS23.402 + +If all TWAN resources related to a PDN connection are released, then step 7 and 8 of Figure 8.2.10.2.6.1-1: (UE/TWAN-initiated PDN disconnection procedure with GTP S2a in WLAN) are carried out to inform the UE of the PDN connection release. + +###### 8.2.10.2.9.2 PDN GW initiated Resource Allocation Deactivation in WLAN on PMIP S2a + +Editor's Notes: This procedure is FFS. + +#### 8.2.10.3 Impacts on existing nodes or functionality + +Editor's Notes: Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause. + +#### 8.2.10.4 Evaluation + +Editor's Notes: The fulfilment to the requirements in Subclause 8.1 as well as simplicity of implementation in the UE should be evaluated. + +## 8.3 Evaluation + +Editor's Note: This clause will include solution(s) assessment. + +The following aspects are considered and evaluated for the solution: + +- i) Impacts to existing network deployment: + - a) There is no additional requirement for WLAN APs compared to Rel-11. + - b) For TWAG, it shall support EAP enhancement for UE and network capability negotiation, and support the new control plane protocol, support p2p link for each PDN connections. +- ii) Impacts to UE: + +The UE should be capable of supporting enhanced EAP procedures. + +It should support the new control plane protocol and user plane p2p link using virtual MAC or VLAN. +- iii) Impacts to 3GPP protocols/extensions (e.g. EAP AKA'): + +The following protocols are extended: + + - a) UE network capability negotiation is enhanced for EAP protocol. + - b) Defining a new control plane protocol for mobility management (e.g. APN, PDN type, user plane p2p link delivery etc). +- iv) Impacts to protocols defined by other SDOs (e.g. DHCP): + +For VLAN based/Virtual MAC based control plane protocol, we need to define a new Ethertype in IEEE. +- v) Control plane + - a) The latency/load can be affected by the messages in the following procedures: + - b) A new control plane protocol is used for all the PDN connections/ NSWO connection. + - c) For L3 based control plane protocol, the NSWO connection may also established by DHCP/RS/RA after authentication procedure. +- vi) Compliance to clause 8.1 SaMOG phase-2 system requirements: + - a) Co-existence with Rel-11 SaMOG + - b) Support for IP address preservation during handover + - c) Simultaneous support for S2a EPC-routed and NSWO; support of simultaneous multiple PDN connections +- vii) Other functional limitations: + +There is no other functional limitation. + +### 8.2.x Solution x + +#### 8.2.x.1 Functional Description + +**Editor's Notes:** It should be described whether and how the solution fulfils the requirements in Subclause 8.1. + +#### 8.2.x.2 Procedures + +**Editor's Notes:** The call flows are described in this subclause. + +#### 8.2.x.3 Impacts on existing nodes or functionality + +**Editor's Notes:** Impacts to UE and network elements within TWAN as well as EPC to support backward compatibility and co-existence with Rel-11 in this subclause. + +#### 8.2.x.4 Evaluation + +**Editor's Notes:** The fulfilment to the requirements in Subclause 8.1 as well as simplicity of implementation in the UE should be evaluated. + +## 8.3 Evaluation + +**Editor's Note:** This clause will include solution(s) assessment. + +# --- 9 Conclusion + +**Editor's note:** This clause will provide conclusions with respect to what further specification work is required in order to provide the feature of S2a mobility based on GTP and WLAN access to EPC. + +## 9.1 Conclusion on SaMOG Phase 1 + +For the support of SaMOG without UE impact, it has been concluded that Solution 2 (described in clause 7.1.2) is selected as the basis for normative specifications: + +- The style of the reference model and call flows of Solution 1 (described in clause 7.1.1.1, 7.1.1.2 and 7.1.1.3) will be used for documentation of the normative specification, i.e., the internal structure of the WLAN Access Network will not be exposed. +- The L2 attach/detach triggers for solution 2 (described in clause 7.1.2.4) will be used in the work of normative specifications. Only L2 attach triggers are used for PDN type IPv6 and IPv4v6; L2 or L3 attach triggers may be used for PDN type IPv4 as described in clause 9.1.1. +- Enhancements on STa reference point in clause 7.1.1.1 will be used in the work of normative specifications. +- Simultaneous access for a UE to EPC through S2a and non-seamless offload using a single SSID is not supported. For a network deployment, behaviour described in clause 7.1.1.4 will be used in the work of normative specifications. +- Whether multiple TNAN functions are mapped to a single non-3GPP access entity, or a single TNAN function is distributed among multiple non-3GPP access entities is out-of-scope of 3GPP. + +### 9.1.1 Conclusion on attach trigger solution + +Two solutions are proposed in chapter 7.1. The main difference between the two solutions is how the TNSP/TWAG is triggered to setup the S2a tunnel towards the PGW. For the support of SaMOG without UE impact, it has been concluded that: + +After the successful authentication, the AAA in the TNAN (TNAP/TWAP) knows from the UE profile the PDN type for the default APN. There are two possibilities: + +1. PDN type = IPv6 or IPv4v6. In that case, TNAP/TWAP shall send a trigger signal to the TNSP/TWAG. TNSP/TWAG establishes the S2a tunnel. +2. PDN type = IPv4. In that case, S2a tunnel setup by the TNSP/TWAG is triggered either by a signal from the TNAP/TWAP, or by a L3 trigger from the UE. A trigger from the TNAP/TWAP is the recommended way. + +In all cases, there shall be no difference on STa and S2a signaling. + +NOTE: That this conclusion applies even though the call flows in clause 7.1 have not been updated to reflect this conclusion. + +## 9.2 Conclusion on SaMOG Phase 2 + +# Annex A: Example of WLAN integrated with Femto + +For the Femto, the network will perform authentication and integrity checking through AAA before the femto can be connect to the EPC. In addition, the IPSec function in Femto can be used to build a secure transmission tunnel through the backhaul to the EPC. Therefore, the WLAN module integrated with the Femto box can leverage the authentication, integrity checking and the IPSec function to build a trusted WLAN access for connectivity to the EPC. + +![Diagram showing the network architecture for a Femto integrated with WLAN accessing the EPC through S2a.](3c04b14104f95eb8f7100f6d497d956e_img.jpg) + +``` +graph LR; A[Femto integrated with WLAN] -- IPSec --> B[IPSec termination function]; B -- S2a --> C[PGW]; +``` + +The diagram illustrates a network architecture. On the left, a blue rectangular block is labeled 'Femto integrated with WLAN'. A green horizontal bar, representing an IPSec tunnel, connects this block to a central blue rectangular block labeled 'IPSec termination function'. Above this green bar is the label 'IPSec'. From the 'IPSec termination function' block, a black line labeled 'S2a' extends to a blue rectangular block on the right labeled 'PGW'. + +Diagram showing the network architecture for a Femto integrated with WLAN accessing the EPC through S2a. + +**Figure A-1: WLAN integrated with Femto accessing EPC through S2a** + +Editor's note: Figure A-1 is illustrative and does not imply the location of the non-3GPP GTP peer. + +# Annex B: Change History + +| Change history | | | | | | | | +|----------------|--------|-----------|----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2011-04 | SA2#84 | | | | Initial draft | | 0.0.0 | +| 2011-04 | SA2#84 | | | | Inclusion of P-CRs approved during SA2#84: S2-111940, S2-111941, S2-112138, S2-111943 | 0.0.0 | 0.1.0 | +| 2011-05 | | | | | Add the TR number (Rapporteur) | 0.1.0 | 0.1.1 | +| 2011-05 | SA2#85 | | | | Inclusion of P-CRs approved during SA2#85: S2-112731, S2-112733, S2-112836, S2-112837, S2-112905, S2-112906, S2-112907, S2-112908 | 0.1.1 | 0.2.0 | +| 2011-07 | SA2#86 | | | | Inclusion of P-CRs approved during SA2#86: S2-113828, S2-113829, S2-113779 | 0.2.0 | 0.3.0 | +| 2011-10 | SA2#87 | | | | Inclusion of P-CRs approved during SA2#87: S2-114542, S2-114543, S2-114697, S2-114648, S2-114681, S2-114682, S2-114683, S2-114626 | 0.3.0 | 0.4.0 | +| 2011-11 | SA2#88 | | | | Inclusion of P-CRs approved during SA2#88: S2-114800, S2-114857, S2-114987, S2-115319, S2-115332, S2-115361, S2-115364, S2-115433, S2-115434, S2-115456 | 0.4.0 | 0.5.0 | +| 2011-12 | SP#54 | SP-110758 | - | - | MCC Update to version 1.0.0 for presentation to TSG SA for information | 0.5.0 | 1.0.0 | +| 2012-05 | SA2#91 | | | | Inclusion of P-CRs approved during SA2#91: S2-122490, S2-122491 | 1.0.0 | 1.1.0 | +| 2012-07 | SA2#92 | | | | Inclusion of P-CRs approved during SA2#92: S2-123190, S2-123191, S2-123193, S2-123194, S2-123195, S2-123196, S2-123365, | 1.1.0 | 1.2.0 | +| 2012-12 | SA2#94 | | | | Inclusion of P-CRs approved during SA2#94: S2-124845, S2-124768, S2-124846, S2-124770, S2-124771, S2-124772, S2-124847 | 1.2.0 | 1.3.0 | +| 2013-02 | SA2#95 | | | | Inclusion of P-CRs approved during SA2#95: S2-130562, S2-130675, S2-130565, S2-130677, S2-130566, S2-130625, S2-130624 | 1.3.0 | 1.4.0 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23854/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/23_series/23854/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92bcea91776b3afa580cda3bbbefd8a9e61d2eab --- /dev/null +++ b/marked/Rel-11/23_series/23854/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11c127c3bb20ff2bd9de9f04ad946aa0f18c895a65f17bdc8e09b67611a92f56 +size 89515 diff --git a/marked/Rel-11/23_series/23854/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/23_series/23854/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3124bb7007ffb66bb29ce13e63c57a6b345d0871 --- /dev/null +++ b/marked/Rel-11/23_series/23854/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9558c47b9e6638e99b528ebdcda207baeb112ac4dc0d9fc83d3c859b3f5a64d1 +size 60325 diff --git a/marked/Rel-11/23_series/23854/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/Rel-11/23_series/23854/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8b0baac2675c5e9affa11a139faad8d425b310c --- /dev/null +++ b/marked/Rel-11/23_series/23854/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:804db2da29d293fd9f2d890870145a7da6f7e2eca532d1aaea75159e48cead75 +size 20154 diff --git a/marked/Rel-11/23_series/23854/29f586959675cafdf81cf934954908eb_img.jpg b/marked/Rel-11/23_series/23854/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8b7365743c885ffa107c31be7744c0e0de106a8 --- /dev/null +++ b/marked/Rel-11/23_series/23854/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4069920ca4a52815745af719bc87805b5486735e5d0fb4d14bdc1e295fb0601f +size 62943 diff --git a/marked/Rel-11/23_series/23854/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-11/23_series/23854/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5486cecad1a8a78f9937546813aed709b42b5ee --- /dev/null +++ b/marked/Rel-11/23_series/23854/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d7faeb725e88c9986072b8ccbc3ad8d3058b673ec45b9c384634eaaa8932b02 +size 23303 diff --git a/marked/Rel-11/23_series/23854/356eb99ab9489bbd647223390a913903_img.jpg b/marked/Rel-11/23_series/23854/356eb99ab9489bbd647223390a913903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6b2878e6dda44172e8c77f46df345a4d62e680a --- /dev/null +++ b/marked/Rel-11/23_series/23854/356eb99ab9489bbd647223390a913903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:774543ee3ab41b3cf2b07a279b566a63163d66161956a8247d5ae1c0e65018fc +size 69500 diff --git a/marked/Rel-11/23_series/23854/5a95b187de0044da69b7322e04761b86_img.jpg b/marked/Rel-11/23_series/23854/5a95b187de0044da69b7322e04761b86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6efa0b7c3f5a08ba1b0ff1f021ebb7a84f95276d --- /dev/null +++ b/marked/Rel-11/23_series/23854/5a95b187de0044da69b7322e04761b86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f48880d193992e99dc91ccc8c47ff03dc590300eab040b28008662a790f5b8d6 +size 83046 diff --git a/marked/Rel-11/23_series/23854/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-11/23_series/23854/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b56c24c93694f0f2951687481db3399fd750f74 --- /dev/null +++ b/marked/Rel-11/23_series/23854/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3034be926b1c9ba5a6adcaf0698b5c626258516c816743e213e3f57e085836a0 +size 52383 diff --git a/marked/Rel-11/23_series/23854/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Rel-11/23_series/23854/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2aab1184e95c5c7b356bdd2fc7038ba41e3b4ccb --- /dev/null +++ b/marked/Rel-11/23_series/23854/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77c60d836b2bd2bbd04e5f2e9303aa592d2087a2b98204fd6018c74c227e4360 +size 68777 diff --git a/marked/Rel-11/23_series/23854/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/23_series/23854/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a3f3200d7a8f764939597e07242762972c47d71 --- /dev/null +++ b/marked/Rel-11/23_series/23854/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea0777b12583bf2c2312cb756fa37c7c6f646d6435edb5d3b30c12ada77e17af +size 25847 diff --git a/marked/Rel-11/23_series/23854/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/23_series/23854/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..064cdcd619b368dd11b0e3021238dd9a169b0d84 --- /dev/null +++ b/marked/Rel-11/23_series/23854/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ef1172a9e608db2dfb41c8f48927c67eb756f47521ebd95d12233fa4d235bcd +size 122007 diff --git a/marked/Rel-11/23_series/23854/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg b/marked/Rel-11/23_series/23854/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0ffb6fe992277d7e9c5faf6a53a8cb96886cc1d --- /dev/null +++ b/marked/Rel-11/23_series/23854/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17f23f4e1e224b3070a1ef3ceac8395fd9c4cf8c88f6089b33b464eba94bc826 +size 62576 diff --git a/marked/Rel-11/23_series/23854/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-11/23_series/23854/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca20056d5beba6bb0affb502f314d06f55d34ea6 --- /dev/null +++ b/marked/Rel-11/23_series/23854/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b275c8da84fd19dd2ebab9498f61b6508babe87bf62f42780d266d664c76e89 +size 156483 diff --git a/marked/Rel-11/23_series/23854/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23854/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..797be602ccb7d34fe1c6ca28b34b8893c8471606 --- /dev/null +++ b/marked/Rel-11/23_series/23854/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63cef84ceb20f11b9ee82ea7ecda5fb682e1a63b95fd1b5a7d582ad39f8433cd +size 43264 diff --git a/marked/Rel-11/23_series/23854/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/23_series/23854/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54d2c6db3ed4cc924d6600e0016c732855d95a4e --- /dev/null +++ b/marked/Rel-11/23_series/23854/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6d195dae6da25e5090303a7f62e72437c4b66530e0fab98a9c9f92473265bb4 +size 117126 diff --git a/marked/Rel-11/23_series/23854/875c6f4f441fdd3ca7e1908fd1582983_img.jpg b/marked/Rel-11/23_series/23854/875c6f4f441fdd3ca7e1908fd1582983_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..420a032c3a5b4f36bf883dbcae527039a08cc0d1 --- /dev/null +++ b/marked/Rel-11/23_series/23854/875c6f4f441fdd3ca7e1908fd1582983_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f852655e7833a8f753442aea65ceb032717108d964f0fede087b3133abaa95df +size 159190 diff --git a/marked/Rel-11/23_series/23854/88a6d9692a52989caa6b208a1ba70dc0_img.jpg b/marked/Rel-11/23_series/23854/88a6d9692a52989caa6b208a1ba70dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f080ce7d6095a0c6d50663ec9a9ae6825eac43ac --- /dev/null +++ b/marked/Rel-11/23_series/23854/88a6d9692a52989caa6b208a1ba70dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71e3d93c994ca14cf5e00959f655eb7c3aa20f378295568c6dd770396dcb5844 +size 36153 diff --git a/marked/Rel-11/23_series/23854/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/23_series/23854/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e5dd7ad26cdf8f140ec3125d95601470beeab94 --- /dev/null +++ b/marked/Rel-11/23_series/23854/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:605e8e235259b5d101da60dfed4fad8d9151ca0cca9fc7e13d5b9b76059a09fd +size 71695 diff --git a/marked/Rel-11/23_series/23854/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/23_series/23854/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfc69eb6054ddb369ca7c8d4d6f6b402675acc80 --- /dev/null +++ b/marked/Rel-11/23_series/23854/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08b9f48a7913b496b876c5bed1052a263cb9ef68174430e85bd247b8ee5901b6 +size 72395 diff --git a/marked/Rel-11/23_series/23854/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/23_series/23854/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1156aa165f89194d24f95253e9152013fd2f22d6 --- /dev/null +++ b/marked/Rel-11/23_series/23854/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97d82fa123a825f3315b49ab9dcc5611960d759ea4b0a4fcddf1e805bc7a46fa +size 98837 diff --git a/marked/Rel-11/23_series/23854/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/Rel-11/23_series/23854/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68578a213c48e1625226910085a5d9f5b2d652df --- /dev/null +++ b/marked/Rel-11/23_series/23854/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5a3e232324c9bfe049b9f1f072e9cac9d04fb976559d0622bc7afce02597766 +size 99747 diff --git a/marked/Rel-11/23_series/23854/cad89c017c9e7c1785bcd104fde4e737_img.jpg b/marked/Rel-11/23_series/23854/cad89c017c9e7c1785bcd104fde4e737_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ba8431f457aaed053babd5ea92f81d749fec62b --- /dev/null +++ b/marked/Rel-11/23_series/23854/cad89c017c9e7c1785bcd104fde4e737_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:546c07fce5b9d954180063d76d8d8a02b1287f889a70e5a7d952c5101538c7eb +size 24759 diff --git a/marked/Rel-11/23_series/23854/raw.md b/marked/Rel-11/23_series/23854/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7c5e4fa80173351861f787386702684cdddf3d95 --- /dev/null +++ b/marked/Rel-11/23_series/23854/raw.md @@ -0,0 +1,1389 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 Priority service scenarios ..... | 8 | +| 4.1 IMS Multimedia Priority Service..... | 8 | +| 4.2 Priority EPS Bearer Service ..... | 8 | +| 4.3 CS Fallback ..... | 9 | +| 4.3.1 CS Fallback to GERAN/UTRAN..... | 9 | +| 4.3.2 CS Fallback to 1xRTT..... | 9 | +| 5 Architectural requirements..... | 9 | +| 5.1 General Architecture principles for Multimedia Priority Services ..... | 9 | +| 5.1.1 MPS High Level Principles ..... | 9 | +| 5.1.2 MPS Bearer Management Principles..... | 10 | +| 5.2 IMS Multimedia Priority Services ..... | 10 | +| 5.2.1 General ..... | 10 | +| 5.3 Priority EPS Bearer Service ..... | 10 | +| 5.4 CS Fallback ..... | 11 | +| 5.4.1 CS Fallback to GERAN/UTRAN..... | 11 | +| 5.4.1.1 Mobile-terminated GERAN/UTRAN CS Fallback call for a user in E-UTRAN..... | 11 | +| 5.4.1.2 Mobile-originated GERAN/UTRAN CS Fallback call by a Service User..... | 11 | +| 5.4.2 CS Fallback to 1xRTT..... | 11 | +| 5.4.2.1 Mobile-terminated 1xCSFB call originated by service-user in 1xRTT..... | 11 | +| 5.4.2.2 Mobile-originated 1xCSFB call by a service-user..... | 11 | +| 5.5 SRVCC..... | 12 | +| 6 Key Issues for MPS..... | 12 | +| 6.1 IMS Multimedia Priority Services ..... | 12 | +| 6.1.1 Key Issue 1 - Mobile Originated MPS Voice Session ..... | 12 | +| 6.1.1.1 Description..... | 12 | +| 6.1.1.2 Solution ..... | 12 | +| 6.1.1.3 Impacted entities in the System ..... | 14 | +| 6.1.2 Key issue 2 - QoS handling for IMS multimedia priority Service ..... | 14 | +| 6.1.2.1 Description..... | 14 | +| 6.1.2.2 Solution ..... | 14 | +| 6.1.2.3 Impacted entities in the System ..... | 15 | +| 6.1.3 Key issue 3 - Mobile-terminating IMS multimedia service to a user in E-UTRAN..... | 15 | +| 6.1.3.1 Description..... | 15 | +| 6.1.3.2 Solution..... | 15 | +| 6.1.3.2.1 Terminating MPS session to users when the existing ARP of the default bearer and IMS signalling bearer is not consistent with MPS use..... | 15 | +| 6.1.3.2.2 Terminating MPS session to users when the existing ARP of the default bearer and IMS signalling bearer is already consistent with MPS use ..... | 17 | +| 6.1.4 Key Issue 4 - Priority information download procedure ..... | 19 | +| 6.1.4.1 Description..... | 19 | +| 6.1.4.2 Solution ..... | 19 | +| 6.1.5 Key Issue 5 – Priority resource handling in SRVCC ..... | 21 | +| 6.1.5.1 Description..... | 21 | +| 6.1.5.2 Solution ..... | 22 | +| 6.2 Priority EPS Bearer Service ..... | 23 | +| 6.2.1 Key issue1 - QoS of Default Bearer Assignment for an Always-On MPS Subscription..... | 23 | +| 6.2.1.1 Description..... | 23 | +| 6.2.1.2 Solution ..... | 23 | +| 6.2.2 Key issue2 - Priority Invocation/Revocation ..... | 25 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------|----| +| 6.2.2.1 | Description..... | 25 | +| 6.2.2.2 | Solution..... | 25 | +| 6.2.2.2.1 | Solution 1: Upgrading/Downgrading priority (MPS) for Invoke/Revoke of On demand MPS ..... | 25 | +| 6.2.2.2.2 | Solution-2: Always On MPS Activation..... | 25 | +| 6.2.2.3 | Impacted entities in the System ..... | 26 | +| 6.2.2.3.1 | Solution-1: Upgrading/Downgrading priority (MPS) for Invoke/Revoke of On demand MPS ..... | 26 | +| 6.2.2.3.2 | Solution-2: Always On MPS Activation..... | 26 | +| 6.3 | CS Fallback ..... | 27 | +| 6.3.1 | CS Fallback to GERAN/UTRAN..... | 27 | +| 6.3.1.1 | Key Issue1 - Priority handling of mobile terminating call ..... | 27 | +| 6.3.1.1.1 | Description ..... | 27 | +| 6.3.1.1.2 | Solution ..... | 27 | +| 6.3.1.1.3 | Impacted functions in the System ..... | 30 | +| 6.3.1.2 | Key Issue2 - Priority radio resource handling in CS fallback ..... | 31 | +| 6.3.1.2.1 | Description ..... | 31 | +| 6.3.1.2.2 | Solution ..... | 31 | +| 6.3.1.2.3 | Impacted functions in the System ..... | 33 | +| 6.3.1.3 | Key Issue 3 - Priority handling of mobile originating call ..... | 33 | +| 6.3.1.3.1 | Description ..... | 33 | +| 6.3.1.3.2 | Solution ..... | 33 | +| 6.3.1.3.3 | Impacted functions in the System ..... | 35 | +| 6.3.2 | CS Fallback to 1xRTT ..... | 35 | +| 6.3.2.1 | Key Issue1 - Procedure Flow for Priority handling of mobile terminating call ..... | 35 | +| 6.3.2.1.1 | Description ..... | 35 | +| 6.3.2.1.2 | Solution ..... | 36 | +| 6.3.2.1.3 | Impacted functions in the System ..... | 37 | +| 6.3.2.2 | Key Issue 2 – Procedure flow for Priority handling of mobile originated call..... | 37 | +| 6.3.2.2.1 | Description ..... | 37 | +| 6.3.2.2.2 | Solution ..... | 37 | +| 6.3.2.3 | Impacted functions in the System..... | 39 | +| 7 | Overall Solution ..... | 39 | +| 7.1 | IMS Multimedia Priority Services ..... | 39 | +| 7.2 | Priority EPS Bearer Service ..... | 39 | +| 7.3 | CS Fallback ..... | 39 | +| 8 | Conclusions..... | 39 | +| Annex A: | Change history..... | 41 | + +# --- Foreword + +This Technical Report has been produced by the 3<sup>rd</sup> 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 + +MPS will enable National Security/Emergency Preparedness (NS/EP) users (herein called Service Users) to make priority calls/sessions using the public networks. This service needs to be ensured also under special conditions such as network congestion. Service Users are the government-authorized personnel, emergency management officials and/or other authorized users. Effective disaster response and management rely on the Service User's ability to communicate during congestion conditions. Service Users are expected to receive priority treatment, in support of mission critical multimedia communications. + +The enhancements for MPS evaluated in this document are priority aspects of EPS packet bearer services and priority related interworking between IMS and EPS packet bearer services. These enhancements enable the network to support end-to-end priority treatment for MPS call/session origination/termination, including the Non Access Stratum (NAS) and Access Stratum (AS) signalling establishment procedures at originating/terminating network side as well as resource allocation in the core and radio networks for bearers. Priority treatment will be applicable to IMS based multimedia services, priority EPS bearer services and CS Fallback. + +This document clarifies the architectural requirements for MPS, considers the priority service scenarios, and evaluates solution alternatives. Solutions will be proposed and evaluated based on the following three service categories: IMS based multimedia service (voice, video etc), priority EPS bearer services (PS data without IMS interaction) and CS Fallback. Common issues for multiple service categories should be resolved by single solution to limit the amount of overall functionality and to avoid complexity. + +The basic eMPS, i.e. priority handling of IMS based multimedia service, EPS bearer services and CS Fallback have completed in Rel-10. In Rel-11, Single Radio Voice Call Continuity (SRVCC) from LTE to UTRAN/GERAN/1xCS will be investigated based on Rel-10 SRVCC specification. + +The result of the analysis should be suitable as a basis for normative MPS specification work. + +The scope of the MPS part is to further investigate: + +- The signalling and procedures for identifying priority and authorizing the usage of priority service. +- The required priority attributes used in enabling end-to-end priority marking and priority treatment during establishment, modification and release of an IMS based priority voice/video/data session. +- The scenarios and capabilities for supporting priority EPS bearer data services. +- The potential impacts on existing and relevant standard procedures in order to provide preferential treatment for MPS requests in the event of congestion. +- Inter-working with other IMS and CS networks to provide an end-to-end priority service. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.153: "Multimedia priority service". +- [3] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". + +- [4] 3GPP TS 23.002: "Network architecture". +- [5] 3GPP TS 25.413 [5]: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". +- [6] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2". +- [7] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [8] 3GPP TS 22.011: "Service accessibility". +- [9] 3GPP2 A.S0008-C: "Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network". +- [10] 3GPP2 A.S0009-C: "Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Packet Control Function". +- [11] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [12] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [13] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [14] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents". +- [15] 3GPP TS 23.203: "Policy and charging control architecture". +- [16] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC)". +- [17] 3GPP TS 23.009: "Handover procedures". +- [18] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System(MSC-BSS) interface; Layer 3 specification". +- [19] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2". +- [20] 3GPP TS 23.221: "Architectural requirements". + +# --- 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]. + +**MPS:** Based on TS 22.153 [2]. Multimedia Priority Service allows authorized users to obtain and maintain radio and network resources with priority, also during situations when PLMN congestion is blocking session establishment attempts. + +**MPS session:** A session (e.g., voice, video, data session) for which priority treatment is applied for allocating and maintaining radio and network resources. + +**MPS subscription:** A subscription by which priority services are provided, if the network supports MPS. MPS subscription entitles a USIM with special Access Class(es). MPS subscription profile is stored in the operator's network. + +**MPS-subscribed UE:** A UE having a USIM with MPS subscription. + +**Service User:** As per TS 22.153 [2]. + +**On-demand MPS:** Priority treatment is explicitly requested by a Service User. Priority treatment is granted by the network and can be revoked by the Service User or network. An example of the On-demand mechanism is the use of specific access code provided by the Service User when activating a session to request priority treatment. + +**Always-on MPS subscription:** A type of MPS subscription where priority treatment is provided for all PS sessions for the Service User. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply. + +# --- 4 Priority service scenarios + +**Editor's Note:** This clause will list the service scenarios for which priority handling is applied. + +## 4.1 IMS Multimedia Priority Service + +An example of an IMS-based MPS session is a voice call established using IMS procedures. The MPS voice session described by the following use cases shall be handled in a prioritized way. + +- Mobile origination from an MPS-subscribed UE by including an MPS code/identifier: A Service User originates an IMS-based MPS session by including an MPS code/identifier followed by a destination address (e.g., SIP URI, Tel URI) from an MPS-subscribed UE attached to E-UTRAN. In this scenario, based on the EPS subscription information and operator's policy, priority treatment for the default bearer and the EPS bearer carrying SIP/IMS signalling may be given in the EPS prior to and during IMS-based MPS invocation. Priority treatment in the EPS for signalling and media bearers may be modified/established via PCC based on the session authorization information received from the AF. +- Mobile origination from any UE by including an MPS input string: A Service User invokes an IMS-based MPS session by including an MPS input string from any UE (MPS subscribed or not) attached to E-UTRAN. Following an IMS-based MPS identification and authorization, priority indication and priority treatment are provided to the session in the EPS via PCC. In this scenario, the UE may also receive priority for signalling and media for collection of additional credentials from the Service User. +- Mobile termination: A Service User initiates an MPS session to a terminating user (either a Service User or a normal user) in E-UTRAN. The terminating network identifies the priority of the session and applies priority treatment to ensure that the call is delivered with priority. +- SRVCC of IMS based priority call: When the UE has on-going IMS based priority call and the eNB initiates SRVCC procedure, network resources for voice bearer in the PS, CS and IMS networks of the target system should be reserved in prioritized manner. + +NOTE 1: For Mobile Origination from any UE, the UE should be able to originate a session (e.g., for prepaid UEs, there is available credit). + +NOTE 2: For a Mobile Terminating IMS session from a normal user to a Service User, no priority treatment for the media is required. However, based on operator's policy and subscription information, EPS signalling may still be treated with priority on the terminating side. + +NOTE 3: No analysis has been done for IMS-based MPS session for video and voice/video. + +## 4.2 Priority EPS Bearer Service + +**Editor's Note:** This clause will describe the MPS scenarios for setting up priority EPS bearers when IMS is not used. + +On-demand MPS is activated/deactivated via an AF (e.g., HTTPS server) interaction: The connected Service User interacts with an AF to activate/authorize invocation of priority bearer service. The AF communicates the priority authorization to the PCC infrastructure. Priority is deactivated when the Service User explicitly revokes the priority bearer service via the AF, the AF revokes the priority bearer service or when the PDN connection is released. + +For a third-party AF, the invocation/revocation of the On-demand EPS priority treatment may be performed, but outside of the scope of this work. + +Always-on MPS receives priority bearer service (e.g. ARP and QCI) for all bearers. + +## 4.3 CS Fallback + +### 4.3.1 CS Fallback to GERAN/UTRAN + +In the following CS Fallback use case, the CS Fallback related procedures shall be handled in the following way. + +- **Mobile-terminating call to a user in E-UTRAN:** A Service User initiates a voice call to the terminating user (either a Service User or normal user) in E-UTRAN access and terminating MSC forwards the paging request to the MME. The MME initiates the CS Fallback procedure with priority so that the terminating user can receive the mobile terminating call in the GERAN/UTRAN CS domain. +- **Mobile-originating call by a MPS-subscribed UE in E-UTRAN:** A Service User initiates a voice call in E-UTRAN using procedure for CS fallback to GERAN/UTRAN with priority indication. + +NOTE 1: A mobile-originating call made by non-MPS-subscribed UE dialling MPS input string (dialling number) is treated as normal CSFB call. + +NOTE 2: For a Mobile Terminating Call from a normal user to a service user, no special handling is required. + +### 4.3.2 CS Fallback to 1xRTT + +The following two MPS scenarios are supported: + +- **Mobile-terminating call to a user in E-UTRAN:** A Service User initiates an 1xCS voice call to the terminating user (either a Service User or normal user) in E-UTRAN access and the IWS forwards the paging request to the MME with a priority indication. The MME initiates the CS Fallback procedure with a priority indication in order to transfer the terminating user to the 1x RTT network. +- **Mobile-originating call by a Service User in E-UTRAN:** A Service User initiates a voice call in E-UTRAN using procedure for CS fallback to 1xRTT with a priority indication. + +NOTE: For a Mobile Terminating Call from a normal user to a service user, no special handling is required. + +# --- 5 Architectural requirements + +*Editor's Note: This clause will identify the architectural requirement for scenarios described in clause 4.* + +## 5.1 General Architecture principles for Multimedia Priority Services + +### 5.1.1 MPS High Level Principles + +The MPS Solution(s) shall be based on the following principles: + +- MPS shall be based on existing 3GPP architecture TS 23.002 [4]. +- MPS shall be based on the existing QoS mechanisms as specified in E-UTRAN and EPC specifications, e.g. TS 23.401 [3]. +- MPS supports priority sessions on an "end-to-end" priority basis. Note that if a session terminates on a server in the Internet (e.g. web-based service), then the remote end and the Internet transport are out of scope. +- MPS is based on the ability to invoke, modify, maintain and release sessions with priority and deliver the priority media packets under network congestion conditions. +- A user shall be subscribed and authorized for MPS. Such user is referred to as a Service User as per TS 22.153 [2]. +- The solution(s) shall support an on-demand MPS session that is based on Service User invocation. + +- MPS is applicable to IMS session based services (voice, video and data) as well as EPS bearer data services. Pre-emption of non-Service Users is subject to national/regional regulations. +- MPS shall be supported in a roaming environment when roaming agreements are in place and where regulatory requirements apply. +- An MPS-subscribed UE shall belong to one of the 5 special access-classes (Access Classes 11 to 15) as defined in TS 22.011 [8] +- Network uses existing Access Class Barring mechanism per TS 36.331 [7] and TS 22.011 [8] to provide preferential access to MPS subscribers compared to ordinary users, and to avoid overload situations. + +### 5.1.2 MPS Bearer Management Principles + +When an MPS session is requested by a Service User, the following bearer management principles shall apply: + +- EPS bearers employed in an MPS session shall be assigned ARP value settings corresponding to the priority level of the Service User. +- ARP pre-emption capability and vulnerability settings for eMPS bearers are subject to operator policies and depending on national/regional regulatory requirements. + +## 5.2 IMS Multimedia Priority Services + +### 5.2.1 General + +- For IMS-based Multimedia Services, MPS shall support mechanisms to establish AS and NAS connections with priority. +- An MPS subscribed UE shall be assigned special Access Class(es), within the range 11-15, to gain prioritized access to the E-UTRAN during congestion. +- Based on regional regulatory requirements, an MPS subscribed UE may optionally establish an EPS default bearer and a dedicated bearer that is used to transport IMS/SIP signalling with priority. During the time of initial attach/PDN connection, based on the priority indication received from the SPR for the user, the PCRF determines whether to establish the default EPS bearer and a dedicated bearer that handles IMS/SIP signalling with priority. +- PCC shall be deployed in a network supporting MPS IMS priority services. Subscription information in SPR for Service User shall reflect the user's priority level as defined in TS 22.153 [2] and enable the PCRF to determine the appropriate ARP setting for PCC rules when IMS priority service is invoked. + +## 5.3 Priority EPS Bearer Service + +**Editor's Note: This clause will describes the architecture requirement for priority handling of EPS bearer when IMS is not used as service layer.** + +The Priority EPS bearer services solution(s) shall be based on the following principles: + +- On-demand priority EPS Bearer Service invocation is performed via network initiated resource allocation procedure and does not use UE initiated bearer resource allocation procedure. +- PCC shall be deployed in a network supporting MPS Priority Bearer service. Subscription information in SPR for Service User shall reflect the user's priority level as defined in TS 22.153 [2] and enable the PCRF to determine the appropriate ARP setting for PCC rules when MPS bearer service is invoked. + +## 5.4 CS Fallback + +### 5.4.1 CS Fallback to GERAN/UTRAN + +For CS Fallback to GERAN/UTRAN, MPS shall support a mechanism to properly handle the priority voice call and enable the terminating user and/or call originating Service User to establish the AS and NAS connection to fallback to the GERAN/UTRAN + +Followings are the architectural requirements to achieve priority handling of GERAN/UTRAN CS Fallback MPS scenarios. + +#### 5.4.1.1 Mobile-terminated GERAN/UTRAN CS Fallback call for a user in E-UTRAN + +- If MME receives paging request with priority from MSC, the MME shall preferentially handle paging request to initiate CS Fallback procedure compared to other normal transactions. +- If MME receives paging request with priority from MSC, MME and eNodeB shall be able to page the normal terminating UE in prioritized way to establish the radio and S1 connection for subsequent CS Fallback procedures. + +#### 5.4.1.2 Mobile-originated GERAN/UTRAN CS Fallback call by a Service User + +- MME and eNodeB shall be able to provide prioritized treatment for mobile originated GERAN/UTRAN CS Fallback originated by an authorized Service User. + +### 5.4.2 CS Fallback to 1xRTT + +For CS Fallback to 1x CS, MPS shall support a mechanism to properly handle priority voice calls and enable the terminating user and/or the call-originating Service User to establish the AS and NAS connection to fallback to 1x CS. + +Priority MO or MT 1xCSFB with enhanced 1xRTT CS fallback procedure shall be executed without the concurrent PS handover procedure. + +The architectural requirements to achieve priority handling for 1x CS Fallback MPS scenarios are the following: + +#### 5.4.2.1 Mobile-terminated 1xCSFB call originated by service-user in 1xRTT + +- If the MME receives a message from 1xCS IWS which includes a prioritized 1x CS Paging request, handling of the message should be in accordance with the priority level indicated in the request (i.e. independent of the fact that request originated in the 1xRTT network). +- If the MME receives a message from 1xCS IWS which includes a prioritized 1x CS Paging request, the MME and eNodeB shall be able to page the terminating UE in prioritized way to establish the radio and S1 connection for subsequent CS Fallback procedures. + +#### 5.4.2.2 Mobile-originated 1xCSFB call by a service-user + +- The MME and eNodeB shall be able to provide prioritized treatment for a 1xCSFB request originated in E-UTRAN by a service-user. + +## 5.5 SRVCC + +When SRVCC is being applied and the call is a priority call, the network entities shall assign priority level to voice that can be mapped to priority level used in CS domain. In order to provide priority for SRVCC: + +- For SRVCC to GERAN/UTRAN: + - The MME shall be able to detect that the session requires priority handling in the target system, and notify the priority information to the MSC/MGW in order for the target system to allocate CS and IMS network resources with priority. + - The MSC shall notify the priority indication to the IMS for priority handling in IMS level, e.g. session transfer. + - The source system notifies the priority information to the target system in order for the RNC/BSS to allocate network resources with priority in case of congestion situation. + - The MSC Server shall be able to derive the IMS priority to be used for the access transfer from the information priority information provided from MME. The transfer request to IMS from MSC should have the same priority as the original session over IMS. + +# 6 Key Issues for MPS + +Editor's Note: This clause will describe the proposed solutions to meet the architecture requirements in clause 5. + +## 6.1 IMS Multimedia Priority Services + +Editor's Note: This clause will describe the key issues for IMS based multimedia priority service including the aspect of interworking between IMS and EPS bearer. + +### 6.1.1 Key Issue 1 - Mobile Originated MPS Voice Session + +#### 6.1.1.1 Description + +Call-flow is required to capture mobile originated MPS Voice Session. + +#### 6.1.1.2 Solution + +Figure 6.1.1.2-1 shows the call flow for a mobile originating MPS session. + +![Sequence diagram of Mobile Originated MPS Voice Session call flow between UE, eNodeB, MME, S-GW, PDN-GW, PCRF, and P-CSCF.](5a95b187de0044da69b7322e04761b86_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNodeB + participant MME + participant S-GW + participant PDN-GW + participant PCRF + participant P-CSCF + + Note over UE, PCRF: 1. RRC Establishment and Service Request + UE->>P-CSCF: 2. INVITE + P-CSCF->>PCRF: 3. PCC + P-CSCF->>UE: 4. INVITE + Note over UE, PCRF: 5. Default and IMS Signaling Bearer Modification (Conditional) + P-CSCF->>UE: 6. 183 Progress + P-CSCF->>PCRF: 7. PCC + P-CSCF->>UE: 8. 183 Progress + UE->>P-CSCF: 9. PRACK + P-CSCF->>UE: 9. PRACK + Note over UE, PCRF: 10. Media Bearer(s) Establishment + Note over UE, P-CSCF: 11. IMS Call Establishment continues + +``` + +Sequence diagram of Mobile Originated MPS Voice Session call flow between UE, eNodeB, MME, S-GW, PDN-GW, PCRF, and P-CSCF. + +Figure 6.1.1.2-1: Mobile Originated MPS Voice Session + +1. RRC Establishment and Service Request: If the UE is in EMM-CONNECTED state, this step is not required. Else the UE establishes RRC connection as per TS 23.401 [3] clause 5.3.2.1. Since the Service User has an access class in the range of 11-15, the Establishment Cause in RRC connection request is set to highPriorityAccess. When the MME receives mobile initiated signalling with establishment cause set to highPriorityAccess, the MME and eNodeB prioritize RRC connection requests and establish the S1 bearer and radio resources with priority. +2. INVITE: The UE sends a SIP INVITE message to the P-CSCF on a pre-established default or dedicated EPS bearer used to transport IMS/SIP signalling. The MPS code/identifier and destination address or the MPS input string supplied by the Service User is the SIP message. The P-CSCF detects voice session origination invoked by MPS code identifier or MPS input string and derives the session information. +3. PCC Interaction: The P-CSCF invokes dynamic policy and forwards the derived session information by communicating with the PCRF. The P-CSCF provides information that the originating session is from a Service User. The PCRF recognizes that this request is associated with an MPS session and should be given priority treatment. The PCRF stores the received session information and identifies the affected IP-CAN session. + +4. INVITE: The P-CSCF forwards the SIP INVITE message to the Serving CSCF (S-CSCF). +5. Modification of Default and dedicated EPS Bearer used to transport IMS/SIP Signalling: The PCRF checks if the ARP of the EPS bearer (default or dedicated) that is used to transport IMS/SIP signalling has a value appropriate for the MPS session. If the ARP of the EPS bearer that is used to transport IMS/SIP signalling is not appropriate for the MPS session, the PCRF modifies the ARP of the EPS bearer that is used to transport IMS/SIP signalling to a value appropriate for the MPS session. If the IMS/SIP signalling traffic is transported over a dedicated EPS bearer, then the PCRF modifies the ARP of the default EPS bearer of the same PDN connection to ensure the IMS signalling transported over a dedicated EPS bearer and default EPS bearer have an ARP value appropriate for MPS service, in order to avoid being released due to congestion. This may also be done, based on the operator's policy, to give priority for setting up signalling for early media to collect additional credentials from a Service User in case of priority call origination from any UE. +6. 183 Progress: The IMS core receives a "183 Progress" message in response to the SIP INVITE. The P-CSCF identifies that the session belongs to MPS and the Service User's priority level. The P-CSCF maps the AF-Application Identifier and the Reservation-Priority AVPs with appropriate settings for the MPS session. +7. PCC Interaction: The P-CSCF authorises the QoS resources and invokes dynamic policy. The PCRF stores the received session information and identifies the affected IP-CAN session. +8. 183 Progress: The P-CSCF forwards the 183 Progress message to the UE. +9. PRACK: After receiving 183 Progress message, the UE sends a SIP PRACK message to the P-CSCF as a response to the 183 Progress message. +10. Media Bearer(s) Establishment: The PCRF initiates the establishment of dedicated EPS bearer(s) to transport the media traffic for the MPS session. The dedicated EPS bearer media is handled with priority in EPS. In case the MPS session is not authorized and is required to collect additional credentials from the Service User, based on the operator's policy, priority may be provided to the EPS bearers that are used for the authorisation of the Service User. + +NOTE 1: The mechanisms and protocols used to collect additional credentials from the Service User for authorization of the MPS session are outside the scope of the TR. + +11. IMS call establishment procedure continues. + +NOTE 2: If the call fails or is rejected during the call establishment process or when the call is released and if no other MPS calls are in progress the PCRF downgrades the ARP of the Default and EPS bearer that were used to transport IMS/SIP signalling back to its original value. + +#### 6.1.1.3 Impacted entities in the System + +P-CSCF needs to detect MPS code/identifier or the MPS input string in the SIP INVITE message and provide service information to the PCRF. When the PCRF receives service information from the IMS network, it needs to check if the existing default bearer and dedicated EPS bearer that is used to transport IMS/SIP signalling are appropriate for MPS and if they are not, the PCRF initiates modifying these bearers. When the PCRF receives information that the IMS session is authorized, and receives the authorized priority of the session, the PCRF initiates the media bearer establishment with priority in the EPS. When the PCRF receives an indication from the IMS network that the session is MPS, but the authorization is not completed, if necessary as determined by the operator's policy, the PCRF may provide priority to collect additional credentials from the Service User. When the MME receives a request to modify or establish a bearer with an ARP appropriate for an MPS session, the MME and eNodeB establish the S1 bearer and radio resources with priority. When the MME receives mobile initiated signalling with an establishment cause set to highPriorityAccess, the MME and eNodeB prioritize the RRC connection requests and establish the S1 bearer and radio resources with priority. + +### 6.1.2 Key issue 2 - QoS handling for IMS multimedia priority Service + +#### 6.1.2.1 Description + +If the IMS Multimedia Priority service is invoked the related EPS bearer used for IMS Multimedia Priority service media and IMS/SIP signalling will receive priority treatment. + +The QCI parameter is used to control bearer level packet forwarding treatment. It is not needed to upgrade the QCI of MPS service related EPS bearer or add some indicator to differentiate the MPS service related EPS bearer against the non MPS service related EPS bearer with the same QCI. + +To assure the MPS service related EPS bearers receive priority treatment comparing to the non MPS service related EPS bearers when network need release EPS bearer due to congestion. The ARP setting of the EPS bearers need to be upgraded if these EPS bearers are changed from non MPS service related EPS bearer to MPS service related EPS bearers. + +#### 6.1.2.2 Solution + +As the IMS media bearer will be established after the IMS session of the MPS service has been established, it can be assigned with correct ARP value when it is established. However IMS/SIP signalling related EPS bearer needs to be upgraded if it has not been assigned with the appropriate ARP setting for the MPS service when the IMS session of the MPS service has been initiated. + +Also to avoid default bearer can not be allocated resource due to the low ARP priority value in the handover case, for the MPS service related PDN connection it is necessary to assure the ARP value of the default bearer receives the appropriate ARP setting for MPS service. + +#### 6.1.2.3 Impacted entities in the System + +PCRF needs to assure that the ARP setting of the EPS bearer that is used to transport the IMS/SIP signalling and the default bearer of that PDN connection are assigned with the appropriate ARP setting for MPS service when it received the MPS service activation indication from P-CSCF. + +When IMS media bearer of MPS service is established, the PCRF needs to assure that the ARP value of that bearer is assigned with the appropriate ARP setting for MPS service. + +### 6.1.3 Key issue 3 - Mobile-terminating IMS multimedia service to a user in E-UTRAN + +#### 6.1.3.1 Description + +In Rel-9 for Mobile-terminating IMS multimedia service originated by the Service User, following issues needs to be resolved. + +1. There is no mechanism for P-GW and S-GW to identify the priority indication and further prioritize the handling internally. +2. When the MME receives the downlink data notification, it may reject the downlink data notification under congestion situation as MME cannot distinguish whether it is the request for priority service. +3. There is no mechanism for the system to page the terminating UE and allow it to establish the AS and NAS signalling connection for subsequent resource allocation/maintaining in prioritized way. + +Due to lack of above capabilities, there is a case where the MT IMS multimedia service triggered by the Service User cannot be completed successfully under network congestion situation, e.g. MME and eNodeB congestions. + +![Figure 6.1.3.1-1: Capability required for mobile terminating IMS multimedia service originated by a Service User. The diagram shows a sequence of messages and priority treatments across network elements: S/P-CSCF, P-GW, S-GW, MME, and eNB. An 'Invite (Priority indication)' is sent from an external source to the S/P-CSCF, which then forwards it to the P-GW. The P-GW performs 'Priority treatment' and sends an 'IP-CAN bearer' message to the S-GW. The S-GW performs 'Priority treatment' and sends a 'Downlink data notification' to the MME. The MME performs 'Priority treatment' and sends a 'Paging' message to the eNB. The eNB performs 'Priority treatment'.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Figure 6.1.3.1-1: Capability required for mobile terminating IMS multimedia service originated by a Service User. The diagram shows a sequence of messages and priority treatments across network elements: S/P-CSCF, P-GW, S-GW, MME, and eNB. An 'Invite (Priority indication)' is sent from an external source to the S/P-CSCF, which then forwards it to the P-GW. The P-GW performs 'Priority treatment' and sends an 'IP-CAN bearer' message to the S-GW. The S-GW performs 'Priority treatment' and sends a 'Downlink data notification' to the MME. The MME performs 'Priority treatment' and sends a 'Paging' message to the eNB. The eNB performs 'Priority treatment'. + +**Figure 6.1.3.1-1: Capability required for mobile terminating IMS multimedia service originated by a Service User** + +#### 6.1.3.2 Solution + +##### 6.1.3.2.1 Terminating MPS session to users when the existing ARP of the default bearer and IMS signalling bearer is not consistent with MPS use + +The following procedure shows the terminating MPS session procedure to UE when the existing ARP of the default bearer and IMS signalling bearer is not consistent with MPS use. + +![Figure 6.1.3.2.1: PCRF initiated Bearer Modification Procedure with priority handling. This sequence diagram shows interactions between UE, eNodeB, MME, S-GW, PDN-GW, PCRF, and P-CSCF. The procedure starts with the P-CSCF sending an INVITE (step 1) and Service Information Provision (step 2) to the PCRF. The PCRF then sends an Indication of IP-CAN Session Modification (step 3) to the PDN-GW. The PDN-GW sends an Update Bearer Request (step 4) to the S-GW, which in turn sends an Update Bearer Request (step 5) to the MME. The MME initiates a Network Triggered Service Request (clause 5.3.4.1 of TS 23.401) (step 7) to the eNodeB, which sends a Paging (step 8) to the UE. The UE responds with a UE triggered Service Request (clause 5.3.4.1 of TS 23.401) (step 10). The MME then sends a Bearer Modify Request (step 11) to the eNodeB, which performs RRC/NAS Signaling (step 12) with the UE. The eNodeB sends a Bearer Modify Response (step 13) to the MME, which then sends an Update Bearer Response (step 14) to the S-GW, which sends an Update Bearer Response (step 15) to the PDN-GW. The PDN-GW sends an Acknowledge IP-CAN Session Modification (step 16) to the PCRF. Finally, the IMS based session termination continues (step 17).](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +Figure 6.1.3.2.1: PCRF initiated Bearer Modification Procedure with priority handling. This sequence diagram shows interactions between UE, eNodeB, MME, S-GW, PDN-GW, PCRF, and P-CSCF. The procedure starts with the P-CSCF sending an INVITE (step 1) and Service Information Provision (step 2) to the PCRF. The PCRF then sends an Indication of IP-CAN Session Modification (step 3) to the PDN-GW. The PDN-GW sends an Update Bearer Request (step 4) to the S-GW, which in turn sends an Update Bearer Request (step 5) to the MME. The MME initiates a Network Triggered Service Request (clause 5.3.4.1 of TS 23.401) (step 7) to the eNodeB, which sends a Paging (step 8) to the UE. The UE responds with a UE triggered Service Request (clause 5.3.4.1 of TS 23.401) (step 10). The MME then sends a Bearer Modify Request (step 11) to the eNodeB, which performs RRC/NAS Signaling (step 12) with the UE. The eNodeB sends a Bearer Modify Response (step 13) to the MME, which then sends an Update Bearer Response (step 14) to the S-GW, which sends an Update Bearer Response (step 15) to the PDN-GW. The PDN-GW sends an Acknowledge IP-CAN Session Modification (step 16) to the PCRF. Finally, the IMS based session termination continues (step 17). + +**Figure 6.1.3.2.1: PCRF initiated Bearer Modification Procedure with priority handling** + +1. The P-CSCF receives the SIP INVITE which includes MPS session indication and the originating Service User's priority level and performs service information provision in step 2. The bearer modification procedure (step 2) and SIP INVITE message forwarding (step 6) are performed in parallel. + +2. P-CSCF provides service information to the PCRF including the MPS session information and Service User priority level. The PCRF stores the service information and sends the Ack back to the P-CSCF. +3. The PCRF makes the policy decision. If the existing ARP of the default bearer and IMS signalling bearer is not consistent with the desired ARP for MPS session, the PCRF initiates Bearer Modification Procedure with Bearer QoS Update as defined in clause 5.4.2.1 of TS 23.401 [3]. + +The PCRF sends the Policy and Charging Rules Provision to the PDN GW with appropriate QoS parameters (including the desired ARP) for the PCC rules pertaining to the default and IMS signalling bearers. + +NOTE 1: In case of PMIP based S5, the PCRF sends the Gateway Control and QoS Rules Provision to the Serving GW with the desired ARP. + +4. For GTP-based S5/S8, the PDN GW enforces the decision and sends the Update Bearer Request message to the Serving GW to modify the ARP of the existing default bearer and IMS signalling bearer. +5. The Serving GW sends the Update Bearer Request message to the MME to modify the ARP of the existing default bearer and IMS signalling bearer. The MME updates the contexts to reflect the appropriate ARP for the default and IMS signalling bearers. If ISR is activated, instead of sending Update Bearer Request message to the MME, S-GW buffers the Update Bearer Request message and sends a Downlink Data Notification message to the MME. The message includes the priority indication, i.e. ARP, contained within the Update Bearer Request that is intended to be applied to the default bearer and IMS signaling bearer. If the Serving GW already sent the Downlink Data Notification without priority to MME and is waiting for the user plane to be established, the SGW shall immediately send the Downlink Data Notification message again with priority. The MME sends a response to the S-GW. + +NOTE 2: Priority indication format in Downlink Data Notification is to be confirmed in Stage3. + +6. The P-CSCF sends the SIP INVITE message (i.e. as Downlink Application Layer Data to the PDN GW and the PDN GW forwards it to the Serving GW). +7. If the UE is in ECM-CONNECTED state, this step 7 and the following steps 8, 9, and 10 are not performed. If the Serving GW determines that there is no downlink user plane established for the UE over the S1-U, the Serving GW sends a Downlink Data Notification message to the MME. +8. The MME sends Paging together with priority indication appropriate for an MPS session to the eNodeB according to the indicated ARP. + +If the MME already sent the paging message without priority and is waiting for the paging response, the MME shall immediately send Paging together with priority indication appropriate for an MPS session to the eNodeB again, e.g. MME receives Downlink Data Notification without priority in step 7 and afterwards receives Update Bearer Request with priority in step 5. Otherwise, if the MME already sent the paging message with priority and is waiting for the paging response, the MME shall not send Paging with priority again, i.e. MME receives Update Bearer Request in step 5 and afterwards receives Downlink Data Notification with priority in step 7. + +9. The eNodeB processes the Paging from MME according to the indicated priority and sends RRC Paging message to the UE. The priority handling mechanism at eNB is based on operator policy. +10. The UE initiates the UE triggered Service Request procedure as specified in clause 5.3.4.1 of TS 23.401 [3]. After the downlink S1-U bearer has been established, S-GW forwards to the UE all IMS signalling bearer downlink data (which includes the SIP INVITE message) that was buffered if the UE was in ECM-IDLE state in step 6. + +NOTE 3: In order to avoid a congestion situation at eNodeB, eNodeB may initiate the access control which prevents normal users from making access attempts in specified areas of a PLMN. + +11. The MME sends a Bearer Modify Request to the eNodeB. + +12. If ISR is activated, the MME builds a Session Management Request as described in step 4 of the Bearer Modification Procedure in clause 5.4.2.1 of TS 23.401 [3] and performs the corresponding Session Management procedure. If ISR is not activated and only the QoS parameter ARP is modified, this step 12 is skipped. + +NOTE 4: If the UE is in ECM-IDLE state, steps 11, 12 and 13 can be combined with the Service Request procedure in step 10 or be performed standalone (see clause 5.4.2.1 of TS 23.401 [3]). + +13. The eNodeB responds to the MME with a Bearer Modify Response to the request received in step 11. +14. The MME sends the Update Bearer Response to the S-GW. +15. The S-GW sends the Update Bearer Response to the PDN-GW. + +NOTE 5: In case of PMIP based S5, the Serving GW sends the Gateway Control and QoS Rules Ack to the PCRF. + +16. If the PCRF requested an acknowledgement for Indication of IP-CAN Session modification, then the PDN-GW sends the Acknowledge IP CAN Session Modification Message to the PCRF. +17. The IMS-based session termination procedure continues over the IMS signalling bearer, and priority treatment applies in the event of congestion when establishing the corresponding bearer(s) for the session. + +NOTE 6: If the call fails or is rejected during the call establishment process or when the call is released and if no other MPS calls are in progress, the PCRF downgrades the ARP of the Default and EPS bearer that were used to transport IMS/SIP signalling back to its original value. + +##### 6.1.3.2.2 Terminating MPS session to users when the existing ARP of the default bearer and IMS signalling bearer is already consistent with MPS use + +The following procedure shows the terminating MPS session procedure to UE when the existing ARP of the default bearer and IMS signalling bearer is already consistent with MPS use. + +![Sequence diagram illustrating the Network initiated Paging Procedure with priority handling. The diagram shows interactions between UE, eNodeB, MME, S-GW, PDN-GW, PCRF, and P-CSCF. The process starts with an INVITE from P-CSCF, followed by Service Information Provision to PCRF. A shaded region labeled 'Network Triggered Service Request (clause 5.3.4.1 of TS 23.401)' contains steps 3 through 7. Step 3 is Downlink Data (INVITE) from P-CSCF to PDN-GW. Step 4 is Downlink Data Notification/ACK from PDN-GW to S-GW. Step 5 is Paging from S-GW to MME. Step 6 is Paging from MME to eNodeB. Step 7 is UE triggered Service Request (clause 5.3.4.1 of TS 23.401) from UE to eNodeB. Step 8 indicates that the IMS based session termination continues.](29f586959675cafdf81cf934954908eb_img.jpg) + +``` + +sequenceDiagram + participant P-CSCF + participant PCRF + participant PDN-GW + participant S-GW + participant MME + participant eNodeB + participant UE + + Note right of P-CSCF: 1. INVITE + P-CSCF->>PCRF: 2. Service Information Provision + Note right of P-CSCF: 3. Downlink Data (INVITE) + P-CSCF->>PDN-GW: 3. Downlink Data (INVITE) + PDN-GW->>S-GW: 4. Downlink Data Notification/ACK + S-GW->>MME: 5. Paging + MME->>eNodeB: 6. Paging + Note left of UE: 7. UE triggered Service Request (clause 5.3.4.1 of TS 23.401) + UE->>eNodeB: 7. UE triggered Service Request (clause 5.3.4.1 of TS 23.401) + Note right of eNodeB: 8. IMS based session termination continues + +``` + +Sequence diagram illustrating the Network initiated Paging Procedure with priority handling. The diagram shows interactions between UE, eNodeB, MME, S-GW, PDN-GW, PCRF, and P-CSCF. The process starts with an INVITE from P-CSCF, followed by Service Information Provision to PCRF. A shaded region labeled 'Network Triggered Service Request (clause 5.3.4.1 of TS 23.401)' contains steps 3 through 7. Step 3 is Downlink Data (INVITE) from P-CSCF to PDN-GW. Step 4 is Downlink Data Notification/ACK from PDN-GW to S-GW. Step 5 is Paging from S-GW to MME. Step 6 is Paging from MME to eNodeB. Step 7 is UE triggered Service Request (clause 5.3.4.1 of TS 23.401) from UE to eNodeB. Step 8 indicates that the IMS based session termination continues. + +**Figure 6.1.3.2.2: Network initiated Paging Procedure with priority handling** + +1. The P-CSCF receives the SIP INVITE which includes MPS session indication and the originating Service User's priority level. +2. P-CSCF provides service information to the PCRF including the MPS session information and Service User priority level. The PCRF stores the service information and sends the Ack back to the P-CSCF. The PCRF makes the policy decision. If the existing ARP of the default bearer and IMS signalling bearer is consistent with the desired ARP for MPS session, then Bearer Modification Procedure with Bearer QoS Update is not performed. +3. The P-CSCF sends the SIP INVITE message (i.e. as Downlink Application Layer Data to the PDN GW). The PDN GW forwards the downlink data to the Serving GW over the established EPS bearer for IMS signalling. +4. If the Serving GW determines that there is no downlink user plane established for the UE over the S1-U, the Serving GW sends a Downlink Data Notification message to the MME with "priority-indication". The message includes the ARP of the EPS bearer over which Downlink Data Packet (for SIP INVITE) arrived that represents the priority applied to the IMS signaling bearer. If the Serving GW already sent the Downlink Data Notification + +without priority to MME and is waiting for the user plane to be established, the SGW shall immediately send the Downlink Data Notification message again with priority. The MME sends a response to the S-GW. + +5. The MME sends Paging together with priority indication appropriate for an MPS session to the eNodeB according to the indicated ARP. + +If the MME already sent the paging message without priority and is waiting for the paging response, the MME shall immediately send Paging together with priority indication appropriate for an MPS session to the eNodeB again, e.g. MME receives Downlink Data Notification without priority for non MPS related service and afterwards receives Downlink Data Notification with priority in step 4. + +The eNodeB processes the Paging from MME according to the indicated priority and sends RRC Paging message to the UE. The priority handling mechanism at eNB is based on operator policy. + +6. The UE initiates the UE triggered Service Request procedure as specified in clause 5.3.4.1 of TS 23.401 [3]. + +NOTE: In order to avoid congestion situation at eNodeB, eNodeB may initiate the access control which prevents normal users from making access attempts in specified areas of a PLMN. + +7. The IMS-based session termination procedure continues over the IMS signalling bearer, and priority treatment applies in the event of congestion when establishing the corresponding bearer(s) for the session. + +### 6.1.4 Key Issue 4 - Priority information download procedure + +#### 6.1.4.1 Description + +To recognize the MPS service on IMS application level, the P-CSCF needs subscriber's profile of service priority level. + +#### 6.1.4.2 Solution + +The figure 6.1.4.2-1 shows the priority information download procedure. + +![Sequence diagram of IMS Registration Flow between UE, P-CSCF, I-CSCF, HSS, and S-CSCF.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` +sequenceDiagram + participant UE + participant P-CSCF + participant I-CSCF + participant HSS + participant S-CSCF + + Note left of UE: 1. Register + UE->>P-CSCF: 1. Register + P-CSCF->>I-CSCF: 2. Register + I-CSCF->>HSS: 3. Cx-Query/ Cx-Select-pull + HSS-->>I-CSCF: 4. Cx-Query Resp/ Cx-Select-pull Resp + I-CSCF->>S-CSCF: 5. Register + S-CSCF->>HSS: 6. Cx-put/ Cx-pull + HSS-->>S-CSCF: 7. Cx-put Resp/ Cx-pull Resp + S-CSCF-->>I-CSCF: 8. 200 OK + I-CSCF-->>P-CSCF: 9. 200 OK + P-CSCF-->>UE: 10. 200 OK + Note right of I-CSCF: 11. Subscribe + I-CSCF->>S-CSCF: 11. Subscribe + S-CSCF-->>I-CSCF: 12. 200 OK + I-CSCF->>P-CSCF: 13. Notify + P-CSCF-->>I-CSCF: 14. 200 OK +``` + +Sequence diagram of IMS Registration Flow between UE, P-CSCF, I-CSCF, HSS, and S-CSCF. + +**Figure 6.1.4.2-1: IMS Registration Flow** + +1-6. These steps do not change from the corresponding IMS Registration procedures specified in TS 23.228 [12]. + +7. The S-CSCF receives the priority information, i.e. Service Priority Level, for the MPS-subscribed UE from HSS, and maintains it as a part of user profile. (See TS 24.229 [13] and TS 29.228 [14] for details). + +8-14. The priority information is sent to P-CSCF. The P-CSCF stores this information for the MPS-subscribed UE. + +NOTE: CT WG1 is discussing various mechanisms on how to transfer the priority status between S-CSCF and P-CSCF. + +The figure 6.1.4.2-2 shows the SIP message handling for IMS MO call initiated by the MPS-subscribed UE. + +![Sequence diagram of IMS MO call procedure initiated by the MPS-subscribed UE. The diagram shows interactions between UE, P-CSCF, S-CSCF, and the Terminating Network. The procedure includes INVITE, Service Control, QoS Authorization, and media flow enabling steps.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCSCF as P-CSCF + participant SCSCF as S-CSCF + participant TN as Terminating Network + + Note over UE, SCSCF: Originating Home Network + UE->>PCSCF: 1. Invite (Initial SDP Offer) + PCSCF->>SCSCF: 2. Invite (Initial SDP Offer) + Note right of SCSCF: 3. Service Control + SCSCF->>TN: 4. Invite (Initial SDP Offer) + TN->>SCSCF: 5. Offer Response + SCSCF->>PCSCF: 6. Offer Response + Note right of PCSCF: 7. Authorize QoS Resources + PCSCF->>UE: 8. Offer Response + UE->>PCSCF: 9. Response Conf (Opt SDP) + Note left of UE: 10. Resource Reservation + PCSCF->>SCSCF: 11. Response Conf (Opt SDP) + SCSCF->>TN: 12. Response Conf (Opt SDP) + TN->>SCSCF: 13. Conf Ack (Opt SDP) + SCSCF->>PCSCF: 14. Conf Ack (Opt SDP) + PCSCF->>UE: 15. Conf Ack (Opt SDP) + UE->>PCSCF: 16. Reservation Conf + PCSCF->>SCSCF: 17. Reservation Conf + SCSCF->>TN: 18. Reservation Conf + TN->>SCSCF: 19. Reservation Conf + SCSCF->>PCSCF: 20. Reservation Conf + PCSCF->>UE: 21. Reservation Conf + TN-->>SCSCF: 22. Ringing + SCSCF-->>PCSCF: 23. Ringing + PCSCF-->>UE: 24. Ringing + Note left of UE: 25. Alert User + TN->>SCSCF: 26. 200 OK + SCSCF->>PCSCF: 27. 200 OK + Note right of PCSCF: 28. Enabling of Media Flows + PCSCF->>UE: 29. 200 OK + Note left of UE: 30. Start Media + UE->>PCSCF: 31. ACK + PCSCF->>SCSCF: 32. ACK + SCSCF->>TN: 33. ACK + +``` + +Sequence diagram of IMS MO call procedure initiated by the MPS-subscribed UE. The diagram shows interactions between UE, P-CSCF, S-CSCF, and the Terminating Network. The procedure includes INVITE, Service Control, QoS Authorization, and media flow enabling steps. + +**Figure 6.1.4.2-2: IMS MO call procedure initiated by the MPS-subscribed UE** + +Step1 does not change from the corresponding IMS MO call procedures specified in TS 23.228 [12] and TS 24.229 [13]. + +2. P-CSCF judges whether the INVITE message requires the priority handling based on user profile stored during the registration procedure and/or the priority requested by the user and/or MPS code/identifier provided by INVITE message. .If the session is determined to have priority handling, then P-CSCF inserts/replaces the priority indication and forwards it to the S-CSCF. + +Step 3 does not change from the corresponding IMS MO call procedures specified in TS 23.228 [12] and TS 24.229 [13]. + +4. S-CSCF will treat the INVITE request based on the priority indication received from the P-CSCF. S-CSCF then forwards the INVITE to the next node with this priority indication. + +Following Steps do not change from the corresponding IMS MO call procedures specified in TS 23.228 [12] and TS 24.229 [13]. + +### 6.1.5 Key Issue 5 – Priority resource handling in SRVCC + +#### 6.1.5.1 Description + +As described in the following bullets, there is no capability for MME, MGW/MSC server and MSC to inform priority indication to neighbour nodes e.g. MSC Server or RNC/BSS during handover preparation. + +There is no capability for MME to inform priority indication to MSC Server/MGW and MSC server in the core network. + +![Sequence diagram illustrating the SRVCC handover process and the lack of priority resource allocation capability.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +``` +sequenceDiagram + participant eNodeB + participant MME + participant IMS/SCC AS + participant MSC Server/MGW + participant MSC + participant Target RAN/BSS + + Note right of Target RAN/BSS: Priority resource allocation!! + + eNodeB->>MME: 1. HO Required (SRVCC) + MME->>MSC Server/MGW: 2. PS to CS Request (Priority level, Pre-emption Cap/vulner) + MSC Server/MGW->>IMS/SCC AS: INVITE (STN-SR, priority indication, level) + MSC Server/MGW->>MSC: 3. Pre HO Req (mapped Priority level, Pre-emption Cap/vulner) + MSC->>Target RAN/BSS: 4. Rel/Ho req (priority level, pre-emption cap/vulner) +``` + +The diagram illustrates the SRVCC handover process. It shows the flow of messages between the eNodeB, MME, IMS/SCC AS, MSC Server/MGW, MSC, and Target RAN/BSS. The messages are: 1. HO Required (SRVCC) from eNodeB to MME; 2. PS to CS Request (Priority level, Pre-emption Cap/vulner) from MME to MSC Server/MGW; 3. Pre HO Req (mapped Priority level, Pre-emption Cap/vulner) from MSC Server/MGW to MSC; 4. Rel/Ho req (priority level, pre-emption cap/vulner) from MSC to Target RAN/BSS. A callout bubble from the Target RAN/BSS points to the message from MSC with the text "Priority resource allocation!!", indicating a lack of capability in this step. + +Sequence diagram illustrating the SRVCC handover process and the lack of priority resource allocation capability. + +**Figure 6.1.5.1-1 Capability required for PS to CS handover in SRVCC** + +Due to lack of above capabilities, there is a case where the SRVCC procedure is triggered for the IMS based priority call may fail if target network, i.e. UTRAN/GERAN and/or CS core network, is in congested situation. Therefore, it shall be possible for MME, MGW/ MSC server and MSC to notify the target RAT of the priority indication and target RAT and CS core network allocate its radio and core network resources for the IMS based priority call. + +#### 6.1.5.2 Solution + +The solution for priority handling of radio resource in SRVCC procedure is illustrated in Figure 6.1.5.2-1. + +![Sequence diagram illustrating the priority handling of SRVCC from E-UTRAN to UTRAN/GERAN. The diagram shows the interaction between UE, eNodeB, Target RNC, MME, MSC server/MGW, Target MSC, Target SGSN, and IMS (SCC-AS). The process starts with an LTE IMS Voice session. The sequence of messages is: 1. Measurement report (UE to eNodeB), 2. Decision for HO (eNodeB internal), 3. S1-AP: Handover Required (eNodeB to MME), 4. Bearer Splitting (MME internal), 5. PS to CS Handover (MME to MSC server/MGW), 6. Prepare HO Request (MSC server/MGW to Target MSC), 7. Relocation Request (Target MSC to Target RNC), 8. PS HO procedure (Target RNC internal), 9. Relocation Request Acknowledge (Target RNC to MME), 10. Prepare HO Response (Target MSC to MSC server/MGW), 11. Establish circuit (MSC server/MGW internal), 12. Initiation of Session Transfer (MSC server/MGW to IMS (SCC-AS)), 13. PS to CS Response (MSC server/MGW to MME), 14a. Handover from EUTRAN Command (MME to eNodeB), 14b. Handover from EUTRAN Command (eNodeB to UE), 15. Handover to UTRAN Complete (UE to Target RNC), 16a. Relocation Complete (Target RNC to MME), 16b. SES ( HO complete ) (Target MSC to MSC server/MGW), 16c. ANSWER (MSC server/MGW to IMS (SCC-AS)), 16d. PS to CS Complete (MME to MSC server/MGW), 17. CS bear setup procedure (Target RNC internal), 18. PS bear setup procedure (Target RNC internal).](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +Sequence diagram illustrating the priority handling of SRVCC from E-UTRAN to UTRAN/GERAN. The diagram shows the interaction between UE, eNodeB, Target RNC, MME, MSC server/MGW, Target MSC, Target SGSN, and IMS (SCC-AS). The process starts with an LTE IMS Voice session. The sequence of messages is: 1. Measurement report (UE to eNodeB), 2. Decision for HO (eNodeB internal), 3. S1-AP: Handover Required (eNodeB to MME), 4. Bearer Splitting (MME internal), 5. PS to CS Handover (MME to MSC server/MGW), 6. Prepare HO Request (MSC server/MGW to Target MSC), 7. Relocation Request (Target MSC to Target RNC), 8. PS HO procedure (Target RNC internal), 9. Relocation Request Acknowledge (Target RNC to MME), 10. Prepare HO Response (Target MSC to MSC server/MGW), 11. Establish circuit (MSC server/MGW internal), 12. Initiation of Session Transfer (MSC server/MGW to IMS (SCC-AS)), 13. PS to CS Response (MSC server/MGW to MME), 14a. Handover from EUTRAN Command (MME to eNodeB), 14b. Handover from EUTRAN Command (eNodeB to UE), 15. Handover to UTRAN Complete (UE to Target RNC), 16a. Relocation Complete (Target RNC to MME), 16b. SES ( HO complete ) (Target MSC to MSC server/MGW), 16c. ANSWER (MSC server/MGW to IMS (SCC-AS)), 16d. PS to CS Complete (MME to MSC server/MGW), 17. CS bear setup procedure (Target RNC internal), 18. PS bear setup procedure (Target RNC internal). + +**Figure 6.1.5.2-1: Priority handling of SRVCC from E-UTRAN to UTRAN/GERAN.** + +The key modifications to the basic flow for providing MPS service are as follows: + +0. Based on IMS based priority call handling mechanism, eNodeB and MME recognizes that the ongoing session is an IMS based MPS session. The SCC AS is also aware the IMS MPS session(s) during the IMS based MPS session establishment procedures as defined in TS 23.228 [12], i.e. during the session establishment procedure. + +From Step 1 to Step 2, the procedure does not change from the corresponding SRVCC procedures specified in TS 23.216 [16]. + +3. The eNodeB sends "Handover required message" to the MME. + +Step 4 does not change from the corresponding SRVCC procedure specified in TS 23.216 [16]. + +5. MME detects the session requires priority handling based on the priority indication (i.e. ARP) associated with IMS CN signalling (i.e. QCI-5) received during the IMS based MPS session establishment and sends the SRVCC PS to CS Request message to the MSC Server/MGW by sending a priority indication (i.e. ARP) for the ongoing IMS call in the PS to CS Handover message to MSC Server. The priority indication is used by the target RNC/BSS to determine whether the call needs priority during congestion for its resource allocation. +6. Based on the priority indication (i.e. ARP) in the SRVCC PS to CS Request, the MSC server/MGW sends Prepare Handover Request message to the Target MSC with priority indication mapped from the ARP. The MSC Server maps the ARP to the priority level, pre-emption capability/vulnerability for CS services based on local regulation or operator settings. The priority indication indicates the CS call priority during handover as specified in TS 25.413 [5] for UMTS and TS 48.008 [18] for GSM/EDGE. +7. The target MSC sends "Relocation Request/Handover Request" to the RNC/BSS. The RNC/BSS allocates the radio resource based on the existing procedures with priority indication, as specified in TS 25.413 [5] for UMTS and TS 48.008 [18] for GSM/EDGE. + +Both Step 8 and step 9 do not change the corresponding SRVCC procedure specified in TS 23.216 [16]. + +10. The target MSC sends a Prepare Handover Response message to the MSC server with priority indication. +11. When the MGW receives a Handover Response in step 10, the CS bearer is established in prioritized way between the target MSC and the MGW associated with the MSC Server. +12. MSC Server sends the SIP Session Transfer message with the priority indication to the IMS and the IMS entity handles the session transfer procedure with priority. The priority indication in the SIP Session Transfer message is mapped by the MSC Server from the priority indication (i.e. ARP) in the SRVCC PS to CS Request received in step 5. The mapping of the priority level is based on operator policy and/or local configuration, and the IMS priority indicator should be the same as for the original IMS created over PS. + +From Step 13 to Step 18, the procedure does not change from the corresponding SRVCC procedures specified in TS 23.216 [16]. + +NOTE: The priority handling procedures for CS handover is defined in TS 23.009 [17], TS 48.008 [18], and TS 25.413 [5]. It is not expected to change due to SRVCC HO. + +## 6.2 Priority EPS Bearer Service + +*Editor's Note: This clause will describes the key issues for EPS bearer priority when IMS is not used as service layer.* + +### 6.2.1 Key issue1 - QoS of Default Bearer Assignment for an Always-On MPS Subscription + +#### 6.2.1.1 Description + +When attaching to the network, UE is given a default bearer, which it may use for signalling any requests for services to the network. This clause discusses QoS parameters assignment given to the default bearer when a Service User having an Always-On MPS subscription attaches to the network to ensure UE's PDN connection is admitted and not pre-empted during the congestion. + +#### 6.2.1.2 Solution + +This clause describes the signalling flow for IP-CAN Session establishment for a UE with an Always-On MPS subscription. The profile downloaded from the SPR includes a priority indication. In this case the rules installed into the PDN GW will include the appropriate QoS attributes (e.g. ARP, QCI). These attributes will be assigned by the PDN GW to the EPS Bearer. + +![Sequence diagram for IP-CAN Session Establishment showing interactions between GW (BBERF), GW (PCEF), V-PCRF, H-PCRF, SPR, and OCS. The diagram is titled 'Roaming Scenarios' and includes five numbered steps.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +The diagram illustrates the IP-CAN Session Establishment procedure across six lifelines: GW (BBERF), GW (PCEF), V-PCRF, H-PCRF, SPR, and OCS. A shaded area labeled 'Roaming Scenarios' covers the V-PCRF lifeline. The sequence of events is as follows: + +1. Steps 1-3 in Figure 7.2-1 in 23.203 (A large box spanning the first three lifelines) +2. Profile Request (A dashed arrow from H-PCRF to SPR) +3. Profile Response (A dashed arrow from SPR to H-PCRF) +4. Policy Decision (A box on the H-PCRF lifeline) +5. Steps 5-12 in Figure 7.2-1 in 23.203 (A large box spanning all six lifelines) + +Sequence diagram for IP-CAN Session Establishment showing interactions between GW (BBERF), GW (PCEF), V-PCRF, H-PCRF, SPR, and OCS. The diagram is titled 'Roaming Scenarios' and includes five numbered steps. + +**Figure 6.2.1.2.1: IP-CAN Session Establishment** + +1. Steps 1-3 for an IP-CAN Session Establishment procedure with PCC as in TS 23.203 [15], Figure 7.2-1. +2. If the PCRF does not have the subscriber's subscription related information, it sends a request to the SPR in order to receive the information related to the IP-CAN session. The PCRF provides the subscriber ID and, if applicable, the PDN identifier to the SPR. The PCRF may request notifications from the SPR on changes in the subscription information. +3. The user profile downloaded from the SPR includes a priority indication for establishing an PS session with priority. The PCRF stores the subscription related information containing the information about the allowed service(s) and PCC Rules information. +4. The PCRF makes the authorization and policy decision. The priority indication is used to apply operator specific policy and configuration to derive necessary QoS parameters (e.g. ARP, QCI) for establishing an MPS session. +5. Steps 5-12 for an IP-CAN Session Establishment procedure with PCC as in TS 23.203 [15], Figure 7.2-1. + +### 6.2.2 Key issue2 - Priority Invocation/Revocation + +#### 6.2.2.1 Description + +Depending on the system design or operator choice, priority for EPS bearer services can be given permanently to a Service User, or can be provided only if specifically requested by the Service User (on-demand). If configured for permanent priority, initial attach constitutes an invocation of priority for EPS Bearer services. If however, on-demand priority is required, a mechanism for invocation should be elaborated upon. Details for each case of priority invocation should be investigated. + +If priority is invoked at a time that user is already engaged in EPS bearer services, the interaction with the existing bearers will be done having the PCRF instruct the PDN-GW accordingly. + +The indication of on-demand "Priority Status" can be communicated to the PCRF by Application Function (AF) for a session which is requesting priority. This can be done via the Rx interface. During the Priority invocation process, the applicable bearer shall be upgraded with proper priority level according to operator policy and configuration. After successful Priority Invocation, priority level for that bearer shall be derived according to operator policy and configuration. + +During the Priority Revocation process, the existing bearers shall be modified to a proper priority level according to operator policy and configuration. + +#### 6.2.2.2 Solution + +##### 6.2.2.2.1 Solution 1: Upgrading/Downgrading priority (MPS) for Invoke/Revoke of On demand MPS + +The solution relies on existing Rx procedures between the AF and the PCRF whereby the AF requests modification of existing AF session, to upgrade/downgrade priority of the UE's existing AF session(s). + +The procedure used is the PCRF initiated IP-CAN session modification procedure in clause 7.4.2 of TS 23.203 [15]. The AF identifies the sessions to be affected and using existing Rx procedure requests the PCRF to upgrade or downgrade the priority of the existing AF sessions. + +##### 6.2.2.2.2 Solution-2: Always On MPS Activation + +The solution relies on existing procedures between the SPR and the PCRF whereby the SPR notifies the PCRF when the subscriber's profile changes. Once the PCRF receives a notification of a change in the subscriber's profile (Priority EPS Bearer Service Invoked/Revoked) it triggers the PCRF initiated IP CAN Session Modification per TS 23.203 [15], clause 7.5, to upgrade or downgrade the QCI and/or ARP of existing GBR and non-GBR bearers (except for the signalling bearer) when EPS Priority Bearer service is invoked/revoked, respectively. + +![Sequence diagram illustrating the SPR Triggered IP CAN Session Modification procedure. The diagram shows three lifelines: GW (PCEF), PCRF, and SPR. The sequence of messages is: 1. SPR detects the related profile changed; 2. SPR sends a Profile update to PCRF; 3. PCRF sends a response to SPR; 4. PCRF stores the updated profile and makes a PCC decision; 5. PCRF sends a PCC decision provision to GW (PCEF).](88a6d9692a52989caa6b208a1ba70dc0_img.jpg) + +``` + +sequenceDiagram + participant SPR + participant PCRF + participant GW as GW (PCEF) + Note right of SPR: 1.Detects the related profile changed + SPR->>PCRF: 2.Profile update + PCRF-->>SPR: 3.response + Note left of PCRF: 4.stores the updated profile and make PCC decision + PCRF-->>GW: 5.PCC decision provision + +``` + +Sequence diagram illustrating the SPR Triggered IP CAN Session Modification procedure. The diagram shows three lifelines: GW (PCEF), PCRF, and SPR. The sequence of messages is: 1. SPR detects the related profile changed; 2. SPR sends a Profile update to PCRF; 3. PCRF sends a response to SPR; 4. PCRF stores the updated profile and makes a PCC decision; 5. PCRF sends a PCC decision provision to GW (PCEF). + +Figure 6.2.2.2-1: SPR Triggered IP CAN Session Modification procedure + +1. The SPR detects that the related subscription profile of an IP-CAN session has been changed. For instance, the Priority EPS Bearer Service of a Service User has been invoked/revoked. +2. If requested by the PCRF, the SPR notifies the PCRF on the changed profile. +3. The PCRF responds to the SPR. +4. The PCRF stores the updated profile and makes resulting PCC decisions to upgrade/downgrade the ARP of the appropriate service data flows. +5. The PCRF provides all new PCC decisions to the PCEF, using the PCRF initiated IP-CAN session modification procedure in clause 7.4.2 of TS 23.203 [15]. The PCEF upgrades/downgrades the ARP of bearers. + +#### 6.2.2.3 Impacted entities in the System + +##### 6.2.2.3.1 Solution-1: Upgrading/Downgrading priority (MPS) for Invoke/Revoke of On demand MPS + +##### 6.2.2.3.2 Solution-2: Always On MPS Activation + +The impacted entities are: SPR, PCRF + +###### **SPR:** + +New information elements/indicators are added to the user's profile to reflect the Always-on MPS subscription status. The new IEs/indicators shall be supported by the Sp interface. + +###### **PCRF:** + +PCRF updates all affected IP-CAN bearers. + +## 6.3 CS Fallback + +### 6.3.1 CS Fallback to GERAN/UTRAN + +#### 6.3.1.1 Key Issue1 - Priority handling of mobile terminating call + +##### 6.3.1.1.1 Description + +In Rel-9 GERAN/UTRAN CS Fallback procedure for mobile terminating call originated by the Service User, following issues needs to be resolved. + +1. There is no mechanism for MME to prioritize the handling of Paging Request with priority indication arrived from MSC. +2. There is no mechanism for eNodeB to page the terminating UE and allow it to establish the AS and NAS signalling connection for subsequent CS Fallback procedure in prioritized way. + +Due to lack of above capabilities, there is a case where the CS Fallback procedure triggered by the call arrival from a Service User cannot be completed successfully under network congestion situation, e.g. MME and eNodeB congestions. Therefore, when MME detects the CS Fallback requires the priority handling, it shall be possible for the MME and eNodeB to handle the CS Fallback related procedure preferentially compared to other normal transactions as well as to page the UE and enable the terminating UE to establish the AS and NAS signalling connections. + +![Figure 6.3.1.1.1: Capability required for mobile terminating call originated by a Service User. This sequence diagram shows three entities: MSC/VLR, MME, and eNodeB. 1. An external 'IAM' message is received by the MSC/VLR. 2. The MSC/VLR sends a 'Paging request (Priority indication)' to the MME. 3. The MME sends a 'Paging (Priority indication)' to the eNodeB. Callouts labeled 'Priority treatment' point to the MME and eNodeB, indicating preferential processing of these messages.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Figure 6.3.1.1.1: Capability required for mobile terminating call originated by a Service User. This sequence diagram shows three entities: MSC/VLR, MME, and eNodeB. 1. An external 'IAM' message is received by the MSC/VLR. 2. The MSC/VLR sends a 'Paging request (Priority indication)' to the MME. 3. The MME sends a 'Paging (Priority indication)' to the eNodeB. Callouts labeled 'Priority treatment' point to the MME and eNodeB, indicating preferential processing of these messages. + +**Figure 6.3.1.1.1: Capability required for mobile terminating call originated by a Service User** + +##### 6.3.1.1.2 Solution + +###### 6.3.1.1.2.1 Priority handling of CS Fallback for Mobile Terminating Call in idle mode + +The solution for priority handling of terminating call is illustrated in Figure 6.3.1.2.1. + +![Figure 6.3.1.1.2.1: Priority handling of CS Fallback for Mobile Terminating Call in idle mode. This sequence diagram involves five entities: UE, eNodeB, RNC, MME, and MSC/VLR. 1. The MSC/VLR receives an 'IAM' message. 2. It sends a 'Paging Request' to the MME. 3. The MME sends a 'Paging' message to the eNodeB. 4. The eNodeB sends a 'Paging' message to the UE. 5. The UE sends an 'RR Connection Setup' message to the eNodeB. 6a. The eNodeB sends an 'Extended Service Request' to the MME. 6b. The MME sends a 'Service Request' to the MSC/VLR. 7. The MSC/VLR sends an 'S1AP: Initial Context Setup' message to the MME. 8. The MME sends a 'Radio Bearer Establishment' message to the eNodeB. 9. The eNodeB sends an 'S1AP: Response message' to the MME. 10. A 'PSHO' (Packet Switched Handover) phase occurs between the UE and the eNodeB. 11a. The UE sends a 'Paging Response' to the eNodeB. 11b. The eNodeB sends a 'Paging Response' to the RNC. 12. The RNC initiates the 'Existing CS terminating call procedure (see TS23.018)'.](356eb99ab9489bbd647223390a913903_img.jpg) + +Figure 6.3.1.1.2.1: Priority handling of CS Fallback for Mobile Terminating Call in idle mode. This sequence diagram involves five entities: UE, eNodeB, RNC, MME, and MSC/VLR. 1. The MSC/VLR receives an 'IAM' message. 2. It sends a 'Paging Request' to the MME. 3. The MME sends a 'Paging' message to the eNodeB. 4. The eNodeB sends a 'Paging' message to the UE. 5. The UE sends an 'RR Connection Setup' message to the eNodeB. 6a. The eNodeB sends an 'Extended Service Request' to the MME. 6b. The MME sends a 'Service Request' to the MSC/VLR. 7. The MSC/VLR sends an 'S1AP: Initial Context Setup' message to the MME. 8. The MME sends a 'Radio Bearer Establishment' message to the eNodeB. 9. The eNodeB sends an 'S1AP: Response message' to the MME. 10. A 'PSHO' (Packet Switched Handover) phase occurs between the UE and the eNodeB. 11a. The UE sends a 'Paging Response' to the eNodeB. 11b. The eNodeB sends a 'Paging Response' to the RNC. 12. The RNC initiates the 'Existing CS terminating call procedure (see TS23.018)'. + +**Figure 6.3.1.1.2.1: Priority handling of CS Fallback for Mobile Terminating Call in idle mode** + +NOTE: In order to avoid congestion situation at eNodeB, it may initiate the access control which prevents normal UE users from making access attempts in specified areas of a PLMN. + +1. The MSC receives an IAM message with priority marking, e.g. eMLPP priority. In order to handle the CS call establishment procedure after step 11b, the MSC/VLR memorises that the UE is paged with priority. +2. The MME receives paging request message with priority indication, e.g. eMLPP priority, from the MSC, then the MME processes this message and also the subsequent CS fallback procedure preferentially compared to other normal transactions. For this purpose, the MME memorises that the UE is paged with priority. +3. The MME sends Paging with priority marking to the eNodeB. +4. With the priority indication in the received Paging, eNodeB sends Paging to the UE preferentially compared to other normal Pagings. +5. The UE and eNodeB establishes the RRC connection. + +- When MME receives Extended Service Request in Step 6a, it detects this message is the response to the priority CS Fallback procedure initiated in step 3, and the MME processes this message with priority. + +From Step 7 to 10, procedure described in clause 6.3.1.2.2 of this TR is applied. + +Step 11a does not change from the corresponding CS Fallback procedures specified in TS 23.272 [6]. + +- The MSC receives the paging response or Location Area Update Request and detects this message as the response to the priority CS Fallback procedure initiated in Step2 as currently specified. Then, the MSC continues with subsequent priority CS setup procedure. + +- Existing priority CS voice call establishment procedure for mobile terminating call is preformed, e.g. eMLPP. + +###### 6.3.1.1.2.2 Priority handling of CS Fallback for Mobile Terminating Call in Active mode + +The solution for priority handling of terminating call is illustrated in Figure 6.3.1.1.2.2. + +![Sequence diagram illustrating the priority handling of CS Fallback for Mobile Terminating Call in Active mode. The diagram shows interactions between UE, eNodeB, RNC, MME, and MSC/VLR. The sequence starts with an IAM message from an external source to the MSC/VLR. The MSC/VLR sends a Paging Request to the MME. The MME sends a CS Paging Notification to the UE. The UE sends an Extended Service Request to the MME. The MME sends an S1AP: UE Context Modification Request with CSFB indicator to the RNC. The RNC performs a PS-HO (Packet Switched Handover) to the eNodeB. The eNodeB sends a Paging Response to the RNC. The RNC sends a Paging Response to the MSC/VLR. Finally, the MSC/VLR performs the existing CS terminating call procedure.](7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg) + +``` + +sequenceDiagram + participant External + participant MSC_VLR as MSC/VLR + participant MME + participant RNC + participant eNodeB + participant UE + + External->>MSC_VLR: 1. IAM + MSC_VLR->>MME: 2. Paging Request + MME->>UE: 3. CS Paging Notification + UE->>MME: 5. Extended Service Request + MME->>RNC: 6. S1AP: UE Context Modification Request with CSFB indicator + Note over RNC, eNodeB: 7. PS -HO + eNodeB->>RNC: 8. Paging Response + RNC->>MSC_VLR: 9. Paging Response + Note over MSC_VLR: 10. Existing CS terminating call procedure (see TS23.018) + +``` + +Sequence diagram illustrating the priority handling of CS Fallback for Mobile Terminating Call in Active mode. The diagram shows interactions between UE, eNodeB, RNC, MME, and MSC/VLR. The sequence starts with an IAM message from an external source to the MSC/VLR. The MSC/VLR sends a Paging Request to the MME. The MME sends a CS Paging Notification to the UE. The UE sends an Extended Service Request to the MME. The MME sends an S1AP: UE Context Modification Request with CSFB indicator to the RNC. The RNC performs a PS-HO (Packet Switched Handover) to the eNodeB. The eNodeB sends a Paging Response to the RNC. The RNC sends a Paging Response to the MSC/VLR. Finally, the MSC/VLR performs the existing CS terminating call procedure. + +**Figure 6.3.1.1.2.2: Priority handling of CS Fallback for Mobile Terminating Call in Active mode** + +- The MSC receives an IAM message with priority marking, e.g. eMLPP priority. In order to handle the CS call establishment procedure after step 9, the MSC/VLR memorises that the UE is paged with priority. +- The MME receives paging request message with priority indication, e.g. eMLPP priority, from the MSC, then the MME processes this message and also the subsequent CS fallback procedure preferentially compared to other normal transactions. For this purpose, the MME memorises that the UE is paged with priority. + +From Step 3 to 5, does not change from the corresponding CS Fallback procedures specified in TS 23.272 [6]. + +From Step 6 to 7, procedure described in clause 6.3.1.2.2 of this TR is applied. + +From Step 8 to 9, does not change from the corresponding CS Fallback procedures specified in TS 23.272 [6]. + +- Existing priority CS voice call establishment procedure for mobile terminating call is preformed, e.g. eMLPP. + +###### 6.3.1.1.2.3 Priority handling of mobile terminating call when ISR active and SGs is active between MSC/VLR and MME + +The solution for priority handling of terminating call when ISR active and SGs is active between MSC/VLR and MME is illustrated in Figure 6.3.1.1.2.3. + +![Sequence diagram illustrating the priority handling of a mobile terminating call when ISR is active and SGs is active between MSC/VLR and MME. The diagram shows the interaction between UE, eNodeB, MME, RNC, SGSN, MSC/VLR, HSS, and GMSC. The process starts with an IAM message from GMSC to MSC/VLR, followed by an SRI procedure. The MSC/VLR then sends an IAM to HSS and a CS paging message to the MME. The MME sends CS paging messages to the SGSN, which in turn sends them to the RNC and eNodeB. The UE receives the paging message and responds. The RNC and eNodeB also send CS paging responses to the MME, which then forwards them to the MSC/VLR.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNodeB + participant MME + participant RNC + participant SGSN + participant MSC/VLR + participant HSS + participant GMSC + + Note right of GMSC: 1 IAM + GMSC->>MSC/VLR: 1 IAM + Note right of MSC/VLR: 2. SRI procedure in TS23.018 + MSC/VLR->>HSS: 3 IAM + MSC/VLR->>MME: 4 CS paging + Note right of MME: 5a CS paging (CS domain Indicator) + MME->>eNodeB: 5a CS paging (CS domain Indicator) + Note right of eNodeB: 5b CS paging (CS domain Indicator) + eNodeB->>UE: 5b CS paging (CS domain Indicator) + Note right of MME: 6a CS paging + MME->>SGSN: 6a CS paging + Note right of SGSN: 6b CS paging (CS domain Indicator) + SGSN->>RNC: 6b CS paging (CS domain Indicator) + Note right of RNC: 6c CS paging (CS domain Indicator) + RNC->>UE: 6c CS paging (CS domain Indicator) + Note right of UE: 7. CS fallback or Cell Reselection, UE Access from UTMS/GSN CS domain + UE->>eNodeB: 8 CS paging response + eNodeB->>MME: 8 CS paging response + Note right of MME: 9 CS paging response + MME->>MSC/VLR: 9 CS paging response + +``` + +Sequence diagram illustrating the priority handling of a mobile terminating call when ISR is active and SGs is active between MSC/VLR and MME. The diagram shows the interaction between UE, eNodeB, MME, RNC, SGSN, MSC/VLR, HSS, and GMSC. The process starts with an IAM message from GMSC to MSC/VLR, followed by an SRI procedure. The MSC/VLR then sends an IAM to HSS and a CS paging message to the MME. The MME sends CS paging messages to the SGSN, which in turn sends them to the RNC and eNodeB. The UE receives the paging message and responds. The RNC and eNodeB also send CS paging responses to the MME, which then forwards them to the MSC/VLR. + +**Figure 6.3.1.1.2.3: Priority handling of mobile Terminating Call when ISR active and SGs is active between MSC/VLR and MME** + +From Step 1 to Step 3 the procedure does not change from the corresponding CS Fallback procedures specified in TS 23.272 [6]. + +- The MSC/VLR sends a Paging message to the MME via SGs with priority marking, e.g. eMLPP priority. + +Steps 5a and 5b does not change from the corresponding CS Fallback procedures for Mobile Terminating Call in figure 6.3.1.1.2.1. + +- The MME sends CS Paging message to the SGSN with priority marking, e.g. eMLPP priority. Then the SGSN treats this paging message preferentially compared to other normal transactions. +- The SGSN receives the CS paging message from the MME, then the SGSN sends paging messages to RNC/nodeB. SGSN may consider RNC overload conditions as specified in TS 25.413 [5]. + +NOTE: If ISR is not active or the UE is in ECM-CONNECTED state, the MME does not send the CS paging message to the SGSN. + +From Step 6c to Step 9 the procedure does not change from the corresponding CS Fallback procedures specified in TS 23.272 [6]. + +##### 6.3.1.1.3 Impacted functions in the System + +MSC maps priority indication of the IAM message to a priority indication of the paging message sent on the SGs interface. + +In a congestion situation the MME should use this priority indication to process this message and also the subsequent CS fallback procedure preferentially compared to other normal transactions. For this purpose and for each paging attempt the MME memorizes that the UE is paged with priority. The MME forwards the paging message with priority indication to the eNodeB. + +In a congestion situation the eNodeB should handle received paging messages with priority indication with preference over normal paging messages. + +#### 6.3.1.2 Key Issue2 - Priority radio resource handling in CS fallback + +##### 6.3.1.2.1 Description + +If the CS Fallback is triggered when UE is in the Idle mode, MME requests the eNodeB to allocate the E-RAB resource. If the call is originated in scenarios described in clause 4.3.1, the following issue needs to be resolved. + +1. There is no capability for MME to inform priority indication to eNodeB. + +![Diagram illustrating the capability required for MME and eNodeB for priority radio resource handling. The diagram shows three entities: UE, eNodeB, and MME. The MME sends a '1. Request message with CS Fallback indicator (Priority indication)' to the eNodeB. The eNodeB then sends a '2. Radio bearer Establishment' message to the UE, which is associated with an 'E-RAB'. A callout bubble from the eNodeB indicates 'Priority resource allocation'.](24c9e038a791677ed33100667b64f7e6_img.jpg) + +``` + +graph LR + MME[ MME ] -- "1. Request message with CS Fallback indicator (Priority indication)" --> eNodeB[ eNodeB ] + eNodeB -- "2. Radio bearer Establishment" --> UE[ UE ] + UE -- "E-RAB" --> eNodeB + eNodeB -- "Priority resource allocation" --> Callout(( )) + +``` + +Diagram illustrating the capability required for MME and eNodeB for priority radio resource handling. The diagram shows three entities: UE, eNodeB, and MME. The MME sends a '1. Request message with CS Fallback indicator (Priority indication)' to the eNodeB. The eNodeB then sends a '2. Radio bearer Establishment' message to the UE, which is associated with an 'E-RAB'. A callout bubble from the eNodeB indicates 'Priority resource allocation'. + +**Figure 6.3.1.2.1-1: Capability required for MME and eNode for priority radio resource handling** + +Due to lack of above capability, there is a case where the CS Fallback procedure triggered in scenarios described in clause 4.3.1 will fail if E-UTRAN radio network is in congestion situation. Therefore, it shall be possible that the MME notifies the priority indication to the eNodeB in E-RAB resource request and the eNodeB allocates E-UTRAN radio bearer resources preferentially compared to other normal MT calls and PS services. + +Another case is that if the CS Fallback with PS handover support is triggered, MME will initiate handover procedure to request the RNC to allocate the RAB resource in GERAN/UTRAN. If the resource allocation at RNC fails, it is considered that the PS handover fails and result in the failure of the CS Fallback. Therefore, it shall be possible that eNodeB allocates the priority indication to the RNC and the RNC allocates GERAN/UTRAN radio bearer resources preferentially compared to other normal MT calls and PS services. With this analysis, the following issue needs to be resolved. + +2. There is no capability for eNodeB to inform priority indication to RNC in handover trigger. + +![Diagram illustrating the capability required for PS handover in CS fallback. The diagram shows four entities: eNodeB, MME, SGSN, and RNC. The eNodeB sends a '1. Handover required (Priority indication)' to the MME. The MME sends a '2. Forward relocation request (Priority indication)' to the SGSN. The SGSN sends a '3. Relocation request (Priority indication)' to the RNC. A callout bubble from the RNC indicates 'Priority resource allocation!!'.](cad89c017c9e7c1785bcd104fde4e737_img.jpg) + +``` + +graph TD + eNodeB[ eNodeB ] -- "1. Handover required (Priority indication)" --> MME[ MME ] + MME -- "2. Forward relocation request (Priority indication)" --> SGSN[ SGSN ] + SGSN -- "3. Relocation request (Priority indication)" --> RNC[ RNC ] + RNC -- "Priority resource allocation!!" --> Callout(( )) + +``` + +Diagram illustrating the capability required for PS handover in CS fallback. The diagram shows four entities: eNodeB, MME, SGSN, and RNC. The eNodeB sends a '1. Handover required (Priority indication)' to the MME. The MME sends a '2. Forward relocation request (Priority indication)' to the SGSN. The SGSN sends a '3. Relocation request (Priority indication)' to the RNC. A callout bubble from the RNC indicates 'Priority resource allocation!!'. + +**Figure 6.3.1.2.1-2: Capability required for PS handover in CS fallback** + +Due to lack of above capability, there is a case where the CS Fallback procedure triggered in scenarios described in clause 4.3.1 will fail if UTRAN radio network congestion situation. Therefore, it shall be possible for eNodeB to notify the RNC of priority indication and RNC to allocate UTRAN radio resources for the priority MT call. + +##### 6.3.1.2.2 Solution + +The solution for priority handling of radio resource in CS fallback procedure is illustrated in Figure 6.3.1.2.2. + +![Sequence diagram illustrating the priority handling of PS HO in CS fallback procedure. The diagram shows interactions between UE, eNodeB, RNC, MME, and SGSN. The process starts with MO or MT procedures (idle or active) before step 2 or 6b/5. Step 1: S1-AP: Request message with CS Fallback indicator from MME to eNodeB. Step 2: Radio Bearer Establishment between UE and eNodeB. Step 3: S1-AP: Response message from eNodeB to MME. Step 4: S1-AP: Handover Required from eNodeB to MME. Step 5: Forward Relocation Request from MME to SGSN. Step 6: Relocation Request from SGSN to RNC. Step 7: Relocation Request Acknowledge from RNC to SGSN. Step 8: Forward Relocation Response from SGSN to MME. Step 9a: S1-AP: Handover Command from MME to eNodeB. Step 9b: Handover from E-UTRAN Command from eNodeB to UE. Step 9c: Handover to UTRAN Complete from UE to RNC. Step 10: Relocation Complete from RNC to SGSN. Step 11: Forward Relocation Complete from SGSN to MME. Step 12: Forward Relocation Complete Acknowledge from MME to SGSN. The process ends with MO or MT procedures (idle or active) after step 7 or 11a/8.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNodeB + participant RNC + participant MME + participant SGSN + + Note over UE, MME: MO procedure Fig. 6.3.1.3-1, before step 2 or MT procedure (idle) Fig. 6.3.1.1.2.1 before step 6b or MT procedure (active) Fig.6.3.1.1.2.1a before step 5 + MME->>eNodeB: 1. S1-AP: Request message with CS Fallback indicator + Note over UE, eNodeB: 2. Radio Bearer Establishment + eNodeB->>MME: 3. S1-AP: Response message + eNodeB->>MME: 4. S1-AP: Handover Required + MME->>SGSN: 5. Forward Relocation Request + SGSN->>RNC: 6. Relocation Request + RNC->>SGSN: 7. Relocation Request Acknowledge + SGSN->>MME: 8. Forward Relocation Response + MME->>eNodeB: 9a. S1-AP: Handover Command + eNodeB->>UE: 9b. Handover from E-UTRAN Command + UE->>RNC: 9c. Handover to UTRAN Complete + RNC->>SGSN: 10. Relocation Complete + SGSN->>MME: 11. Forward Relocation Complete + MME->>SGSN: 12. Forward Relocation Complete Acknowledge + Note over UE, MME: MO procedure Fig. 6.3.1.3-1, after step 7 or MT procedure (idle) Fig. 6.3.1.1.2.1 after step 11a or MT procedure (active) Fig.6.3.1.1.2.1a after step 8 + +``` + +Sequence diagram illustrating the priority handling of PS HO in CS fallback procedure. The diagram shows interactions between UE, eNodeB, RNC, MME, and SGSN. The process starts with MO or MT procedures (idle or active) before step 2 or 6b/5. Step 1: S1-AP: Request message with CS Fallback indicator from MME to eNodeB. Step 2: Radio Bearer Establishment between UE and eNodeB. Step 3: S1-AP: Response message from eNodeB to MME. Step 4: S1-AP: Handover Required from eNodeB to MME. Step 5: Forward Relocation Request from MME to SGSN. Step 6: Relocation Request from SGSN to RNC. Step 7: Relocation Request Acknowledge from RNC to SGSN. Step 8: Forward Relocation Response from SGSN to MME. Step 9a: S1-AP: Handover Command from MME to eNodeB. Step 9b: Handover from E-UTRAN Command from eNodeB to UE. Step 9c: Handover to UTRAN Complete from UE to RNC. Step 10: Relocation Complete from RNC to SGSN. Step 11: Forward Relocation Complete from SGSN to MME. Step 12: Forward Relocation Complete Acknowledge from MME to SGSN. The process ends with MO or MT procedures (idle or active) after step 7 or 11a/8. + +**Figure 6.3.1.2.2: Priority handling of PS HO in CS fallback procedure** + +NOTE 1: In case of no PS handover support, only the priority radio resource allocation in E-UTRAN, i.e. from step 1 to step 3, applies. + +- 1) The MME sends S1-AP request message to the eNodeB with priority indication. This message also includes the CS fallback indicator. + +NOTE 2: The priority indication shall be able to set a different priority level from the one for the emergency call triggered CS fallback. + +- 2) The eNodeB allocates radio bearer resources to the UE preferentially compared to other normal calls when the UE is in idle mode. + +Step 3 does not change from the corresponding CS Fallback procedures specified in TS 23.272 [6]. + +NOTE 3: Based on operator policy, this indicator may be used by eNodeB to decide whether to continue CS Fallback procedures with PS HO, i.e. step 4, or to initiate radio release procedure to redirect the UE to 2G/3G Circuit Switch as specified in TS 23.272 [6]. + +- 4) The eNodeB may send "Hand over required message" to the MME with priority indication contained in Source to Target Transparent Container as specified in TS 25.413 [5]. In this case, the priority indication is forwarded to the target RNC transparently through the MME and SGSN. The indicator is used to show whether the call needs consideration on the priority level. + +NOTE 4: As UTRAN/GERAN does not have "high-priority" indicator for handover in GPRS, normally, the priority indication in step 4 is considered as "normal call" which have lower priority handling at target RAT. + +- 5) The MME sends "Forward relocation request message" to the SGSN + +- 6) The SGSN sends "Relocation request" to the RNC. When RNC receives relocation request in Step 6 and if priority indication is sent in step 4, it detects this message is the priority CS Fallback procedure initiated in step 4, and the RNC may use this information to handle allocates the radio resource preferentially compared to other normal radio bearers, e.g. allocates the radio resource in prioritized way, as specified in TS 25.413 [5]. + +From Step 7 to Step 12, the procedure does not change from the corresponding CS Fallback handover procedures specified in TS 23.272 [6]. + +##### 6.3.1.2.3 Impacted functions in the System + +The MME provides priority indication to the eNodeB in S1 AP Initial Context Setup and UE Context Modification Request messages. + +In a congestion situation the eNodeB should use priority indication to allocate E-UTRAN radio bearer resources preferentially compared to normal resource requests with no priority indication. + +When CSFB based on PS handover is employed, the eNodeB provides priority indication to the target GERAN/UTRAN which in congestion situation, should allocate radio bearer resources with preference over normal resource requests with no priority indication. + +#### 6.3.1.3 Key Issue 3 - Priority handling of mobile originating call + +##### 6.3.1.3.1 Description + +In Rel-9 GERAN/UTRAN CS Fallback procedure for mobile originating call, it is not clear how the MME determines whether an originating call needs priority handling. This is a necessary function for the MME as it needs to send the request message to the eNodeB to request the radio resource allocation in E-UTRAN if UE is in Idle mode and/or for the eNodeB to forward the priority indication to the RNC for radio resource allocation if PS handover is supported (see clause 6.3.1.2: Key Issue2 - Priority radio resource handling in CS fallback). + +In case of emergency call, TS 23.272 [6] specifies as follows, so that MME can determine the call requires priority and informs E-UTRAN to allocate the radio resource in prioritized way, + +*In TS 23.272 [6], clause 4.6:* + +*When UE is performing CS fallback procedure for Mobile Originating Call for the purpose of emergency call, it shall indicate to the MME that this CS fallback request is for emergency purpose. MME also indicates to the E-UTRAN via the appropriate SI-AP message that this CS fallback procedure is for emergency purpose.* + +In addition, PS handover priority handling for emergency call is also specified in TS 25.413 [5] where priority indication is forwarded from source RAT to the target RAT. + +For MPS-subscribed UEs, the similar mechanisms for emergency call need to be specified for priority call handling. + +##### 6.3.1.3.2 Solution + +###### 6.3.1.3.2.1 Mobile Originating call - PS HO supported + +The solution for priority handling of originating call is illustrated in Figure 6.3.1.3-1. The priority handling in this call flow applies to both cases of UE in Idle mode and Active mode. + +![Sequence diagram illustrating the priority handling of CS Fallback for Mobile Originating Call in idle mode. The diagram shows interactions between UE, eNodeB, RNC/ NodeB, MME, MSC, SGSN, and Serving GW. The process starts with UE E-UTRAN and CS Attach, followed by RRC Connection Setup, NAS: Extended Service Request, S1-AP: Request message with CS Fallback indicator, Radio Bearer Establishment, S1-AP: Response message, PS HO (Priority handling for PS-HO during CS fallback), NAS: CM Service Request, ALU- cs CS message (with CM Service Request), CM Service Reject, Location Area Update or Combined RA/LA Update, CS call establishment procedure, and PS HO as specified in 23.401 [2] (continuation of execution phase).](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNodeB + participant RNC/NodeB + participant MME + participant MSC + participant SGSN + participant ServingGW as Serving GW + + Note over UE, MSC: 0. UE is E-UTRAN and CS Attach + Note over UE, eNodeB: 1. RRC Connection Setup + Note over UE, MME: 2. NAS: Extended Service Request + Note over MME, eNodeB: 3. S1-AP: Request message with CS Fallback indicator + Note over UE, eNodeB: 4. Radio Bearer Establishment + Note over eNodeB, MME: 5. S1-AP: Response message + Note over UE, MSC: 6. PS HO (see 3.1.x Priority handling for PS-HO during CS fallback) + Note over UE, RNC/NodeB: 7. NAS: CM Service Request + Note over RNC/NodeB, MSC: 7. ALU- cs CS message (with CM Service Request) + Note over UE, RNC/NodeB: 8. CM Service Reject + Note over RNC/NodeB, MSC: 8. CM Service Reject + Note over UE, MSC: Location Area Update or Combined RA/LA Update + Note over UE, MSC: 9. CS call establishment procedure + Note over UE, MSC: 10. PS HO as specified in 23.401 [2] (continuation of execution phase) + +``` + +Sequence diagram illustrating the priority handling of CS Fallback for Mobile Originating Call in idle mode. The diagram shows interactions between UE, eNodeB, RNC/ NodeB, MME, MSC, SGSN, and Serving GW. The process starts with UE E-UTRAN and CS Attach, followed by RRC Connection Setup, NAS: Extended Service Request, S1-AP: Request message with CS Fallback indicator, Radio Bearer Establishment, S1-AP: Response message, PS HO (Priority handling for PS-HO during CS fallback), NAS: CM Service Request, ALU- cs CS message (with CM Service Request), CM Service Reject, Location Area Update or Combined RA/LA Update, CS call establishment procedure, and PS HO as specified in 23.401 [2] (continuation of execution phase). + +**Figure 6.3.1.3-1: Priority handling of CS Fallback for Mobile Originating Call in idle mode** + +- 0) During the E-UTRAN attach procedure the subscription information downloaded from the HSS contains CS priority indication if the user has subscribed the eMLPP priority service in the CS domain. +- 1) This step is performed if UE is in Idle mode, and UE sets the establishment cause to HighPriorityAccess based on Access Class information, i.e. UE is subscribed to one of 11 to 15 in order to ensure that the RRC connection is treated with adequate priority (see TS 36.331 [7]). +- 2) UE sends the Extended Service Request to MME. This message is transported by S1-AP message which has establishment cause "HighPriorityAccess" from eNodeB if Step 1 is performed. + +In this step, UE may get the lower layer failure due to radio congestion and in this case, UE reselects the 2G/3G radio and establish the CS call as specified in TS 24.301 [11]. Otherwise, if UE receives Extended Service Reject from MME in response to step 2 due to, for instance, network congestion, UE reselects the 2G/3G radio and establishes the CS call as well as specified in TS 24.301 [11]. + +NOTE 1: Based on operator policy, MME may decide whether to initiate CS Fallback taking other ongoing service(s), e.g. LCS over LTE, into account. + +MME determines the CS Fallback procedure needs priority handling and sends S1-AP Request message to the eNodeB with CS Fallback indicator and priority indication. In case Step 1 was performed, the MME determines that the Extended Service Request required priority handling based on either the "HighPriorityAccess" establishment cause sent by eNB to the MME in the SIAP message, i.e. in case Step 1 was performed or the CS priority Indication if "HighPriorityAccess" establishment cause has not been received, i.e. in case step 1 was not performed. + +According to operator policy the MME may use CS priority Indication to verify the priority handling of the CS Fallback procedure, in the case "HighPriorityAccess" is received in the S1-AP message. + +NOTE 2: The priority indication shall be able to set a different priority level from the one for the emergency call triggered CS fallback. + +From Step 3 to 6, procedure described in clause 6.3.1.2.2 of this TR is applied. + +From Step 7 to step 10, there is no change from the corresponding CS Fallback procedures specified in TS 23.272 [6]. + +Related procedure for Attach is described in Figure 6.3.1.3-2. + +![Sequence diagram of the Attach procedure for priority handling of CS Fallback. The diagram shows interactions between UE, MME, MSC/VLR, and HSS. Step 1: UE sends Attach Request to MME. Step 2: MME performs steps 3 to 16 of the Attach procedure specified in TS 23.401. Step 3: MME derives VLR number. Step 4: MME sends Location Update Request to MSC/VLR. Step 5: MSC/VLR creates SGs association. Step 6: MSC/VLR performs location update in CS domain. Step 7: MSC/VLR sends Location Update Accept to MME. Step 8: MME performs steps 17 to 26 of the Attach procedure specified in TS 23.401.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME + participant MSC/VLR + participant HSS + Note right of MME: 2. Step 3 to step 16 of the Attach procedure specified in TS 23.401 + UE->>MME: 1. Attach Request + MME->>MSC/VLR: 4. Location Update Request + MSC/VLR->>HSS: 5. Create SGs association + Note right of MSC/VLR: 6. Location update in CS domain + MSC/VLR->>MME: 7. Location Update Accept + Note right of MME: 8. Step 17 to step 26 of the Attach procedure specified in TS 23.401 + +``` + +Sequence diagram of the Attach procedure for priority handling of CS Fallback. The diagram shows interactions between UE, MME, MSC/VLR, and HSS. Step 1: UE sends Attach Request to MME. Step 2: MME performs steps 3 to 16 of the Attach procedure specified in TS 23.401. Step 3: MME derives VLR number. Step 4: MME sends Location Update Request to MSC/VLR. Step 5: MSC/VLR creates SGs association. Step 6: MSC/VLR performs location update in CS domain. Step 7: MSC/VLR sends Location Update Accept to MME. Step 8: MME performs steps 17 to 26 of the Attach procedure specified in TS 23.401. + +**Figure 6.3.1.3-2: Attach procedure for priority handling of CS Fallback** + +- 1)-6) Step 1-6 are performed as defined in TS 23.272 [6]. If the UE has subscribed the eMLPP service in the CS domain, MME get the CS priority indication in the subscription data from the HSS via the Update Location Ack (IMSI, Subscription data) message. The CS priority indication is derived from the eMLPP Service Subscription. +- 7) The VLR responds with Location Update Accept (VLR TMSI) to the MME. + +##### 6.3.1.3.3 Impacted functions in the System + +The HSS provides the CS priority indication to the MME during the subscription data update procedure if the user subscribes the eMLPP service in the CS domain. MME determines whether the CSFB MO procedure needs to be handled preferentially based on that indication. + +The MME provides priority indication in S1 AP Initial Context Setup and UE Context Modification Request messages to the eNodeB. + +In a congestion situation, the eNodeB should use priority indication to allocate E-UTRAN radio bearer resources with preference over normal resource requests with no priority indication. + +### 6.3.2 CS Fallback to 1xRTT + +#### 6.3.2.1 Key Issue1 - Procedure Flow for Priority handling of mobile terminating call + +##### 6.3.2.1.1 Description + +In Rel-9 1x CS Fallback procedure for mobile terminating call originated by the Service User, following issues need to be resolved. + +1. There is no mechanism for MME to prioritize the handling of Paging Request with priority indication arrived from MSC. +2. There is no mechanism for eNodeB to page the terminating UE and allow it to establish the AS and NAS signalling connection for subsequent CS Fallback procedure in prioritized way. + +Due to lack of above capabilities, there is a case where the CS Fallback procedure triggered by the call arrival from a Service User cannot be completed successfully under network congestion situation, e.g. MME and eNodeB congestions. Therefore, when MME detects the CS Fallback requires the priority handling, it shall be possible for the MME and eNodeB to handle the CS Fallback related procedure preferentially compared to other normal transactions as well as to page the UE and enable the terminating UE to establish the AS and NAS signalling connections. + +![Sequence diagram showing priority handling for a mobile terminating call. It involves three entities: 1xCS IWS, MME, and eNodeB. 1. A 'Paging request (Priority indication)' is sent from an external source to the 1xCS IWS. 2. The 1xCS IWS sends a 'Paging request (Priority indication)' to the MME. 3. The MME sends a 'Paging (Priority indication)' to the eNodeB. Callouts labeled 'Priority treatment' are shown next to the MME and eNodeB.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +Sequence diagram showing priority handling for a mobile terminating call. It involves three entities: 1xCS IWS, MME, and eNodeB. 1. A 'Paging request (Priority indication)' is sent from an external source to the 1xCS IWS. 2. The 1xCS IWS sends a 'Paging request (Priority indication)' to the MME. 3. The MME sends a 'Paging (Priority indication)' to the eNodeB. Callouts labeled 'Priority treatment' are shown next to the MME and eNodeB. + +Figure 6.3.2.1.1: Capability required for mobile terminating call originated by a Service User + +##### 6.3.2.1.2 Solution + +The solution for priority handling of terminating call is illustrated in Figure 6.3.2.1.2-1. + +![Detailed sequence diagram for an MT call to a 1x CS user in E-UTRAN. Lifelines: 1xCS CSFB UE, E-UTRAN, MME, 1xCS IWS, 1xRTT MSC, S-GW. The sequence starts with the UE being attached and registered. The call process involves: 2a. Paging Request from 1xRTT MSC; 2b. 1xRTT CS Paging from 1xRTT MSC to 1xCS IWS; 3a. Page from 1xCS IWS to E-UTRAN; 3b. Paging from E-UTRAN to UE; 4a. RRC Setup; 4b. Service Request from UE to MME; 4c. Bearer Setup from MME to S-GW; 5. 1xRTT CS Paging from MME to 1xRTT MSC; 5a. UL/DL S1 cdma2000 Tunneling; 6. Extended Service Request from UE to MME; 7. S1 UE Context Modification from MME to E-UTRAN; 8. Optional measurement report solicitation; 9a. RRC Release with Redirection from E-UTRAN to UE; 9b. Enhanced 1xCSFB Signalling between E-UTRAN and 1xRTT MSC; 10. S1 UE Context Release Request from E-UTRAN to MME; 11. Suspend Request from 1xRTT MSC to S-GW; 12. Suspend Request Ack from S-GW to 1xRTT MSC; 13. S1 UE Context Release from MME to E-UTRAN; 14. 1xRTT CS Page Response Message from 1xRTT MSC to 1xCS IWS; 15. 1x MT call establishment per 3GPP2 specifications.](875c6f4f441fdd3ca7e1908fd1582983_img.jpg) + +Detailed sequence diagram for an MT call to a 1x CS user in E-UTRAN. Lifelines: 1xCS CSFB UE, E-UTRAN, MME, 1xCS IWS, 1xRTT MSC, S-GW. The sequence starts with the UE being attached and registered. The call process involves: 2a. Paging Request from 1xRTT MSC; 2b. 1xRTT CS Paging from 1xRTT MSC to 1xCS IWS; 3a. Page from 1xCS IWS to E-UTRAN; 3b. Paging from E-UTRAN to UE; 4a. RRC Setup; 4b. Service Request from UE to MME; 4c. Bearer Setup from MME to S-GW; 5. 1xRTT CS Paging from MME to 1xRTT MSC; 5a. UL/DL S1 cdma2000 Tunneling; 6. Extended Service Request from UE to MME; 7. S1 UE Context Modification from MME to E-UTRAN; 8. Optional measurement report solicitation; 9a. RRC Release with Redirection from E-UTRAN to UE; 9b. Enhanced 1xCSFB Signalling between E-UTRAN and 1xRTT MSC; 10. S1 UE Context Release Request from E-UTRAN to MME; 11. Suspend Request from 1xRTT MSC to S-GW; 12. Suspend Request Ack from S-GW to 1xRTT MSC; 13. S1 UE Context Release from MME to E-UTRAN; 14. 1xRTT CS Page Response Message from 1xRTT MSC to 1xCS IWS; 15. 1x MT call establishment per 3GPP2 specifications. + +Figure 6.3.2.1.2-1: MT call to a 1x CS user in E-UTRAN + +The key modifications to the basic flow for providing MPS service are: + +1. Same as in 1xCSFB. + - 2a. The paging request message from the 1xRTT MSC to the IWS will contain a priority value or an emergency indicator as specified in 3GPP2 specification A.S0008-C v3.0 [9] / A.S0009-C v3.0 [10]. + - 2b. The S102 message containing the paging request message sent from the 1xCS IWS to the MME contains a priority value. + - 3a. Based on the priority field or an emergency indicator in S102 message, if the UE is idle, the MME indicates priority handling to the eNB for the page message. + - 3b. The eNB handles the page message in a priority manner. + - 4a. The UE and the eNB setup RRC connection. +- Steps 4b through 6 occur as specified in TS 23.272 [6]. +6. When MME receives Extended Service Request in Step 6, it detects this message is the response to the priority CS Fallback procedure initiated in step 3, and the MME processes this message with priority. + 7. The MME sends S1AP UE Context Modification with CSFB indication and a priority indication. + +Steps 8 through 15 occur as specified in TS 23.272 [6]. Either Step 9a occurs in case basic 1xCSFB and Step 9b occur for enhanced 1xCSFB. + +Steps 8 and 9 are handled with priority by the eNB. + +##### 6.3.2.1.3 Impacted functions in the System + +The MME receives a S102 message which includes 1xRTT CS Paging with priority indication. + +In a congestion situation the MME should use this priority indication to process this message and also the subsequent CS fallback procedure preferentially compared to other normal transactions. For this purpose and for each paging attempt memorizes that the UE is paged with priority. The MME forwards the paging message with priority indication to the eNodeB. + +In a congestion situation the eNodeB should handle received paging messages with priority indication with preference over normal paging messages. + +#### 6.3.2.2 Key Issue 2 – Procedure flow for Priority handling of mobile originated call + +##### 6.3.2.2.1 Description + +Flows for priority handling of mobile originated call. + +##### 6.3.2.2.2 Solution + +The solution for priority handling of originating call is illustrated in Figure 6.3.2.2.2-1. + +![Sequence diagram for CS MO call using fallback to CDMA 1x RTT network by a Service user. The diagram shows interactions between 1xCS CSFB MPS UE, E-UTRAN, MME, 1xCS IWS, 1xRTT MSC, and S-GW. The process starts with the UE being attached and registered. Upon a decision to make a MO call, the UE sends an RRC Connection Setup (if idle) or an Extended Service Request. The MME performs context setup/modification and optional measurement report solicitation. The UE then receives an RRC Release with Redirection (6a) or Enhanced 1xCSFB Signalling (6b). The MME sends a S1 UE Context Release Request to the E-UTRAN, a Suspend Request to the S-GW, and receives a Suspend Request Ack. Finally, the MME performs a S1 UE Context Release and the 1x MO call establishment per 3GPP2 specifications.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant UE as 1xCS CSFB MPS UE + participant E-UTRAN + participant MME + participant IWS as 1xCS IWS + participant MSC as 1xRTT MSC + participant S-GW + + Note over UE, S-GW: 1. UE is E-UTRAN attached and registered with 1xRTT CS + Note over UE: 2. UE decision to perform MO call in 1xCS + rect rgb(255, 255, 255) + Note over UE, E-UTRAN: 2a. RRC Connection Setup if UE in idle-mode (Priority Indication) + end + UE->>MME: 3. Extended Service Request (Priority Indication) + MME->>E-UTRAN: 4. S1 UE Context Setup/ Modification + rect rgb(255, 255, 255) + Note over UE, E-UTRAN: 5. Optional measurement report solicitation + end + rect rgb(255, 255, 255) + E-UTRAN->>UE: 6a. RRC Release with Redirection + E-UTRAN->>IWS: 6b. Enhanced 1xCSFB Signalling + end + E-UTRAN->>MME: 7. S1 UE Context Release Request + MME->>S-GW: 8. Suspend Request + S-GW->>MME: 9. Suspend Request Ack + rect rgb(255, 255, 255) + MME->>E-UTRAN: 10. S1 UE Context Release + end + Note over UE, MSC: 11. 1x MO call establishment per 3GPP2 specifications + +``` + +Sequence diagram for CS MO call using fallback to CDMA 1x RTT network by a Service user. The diagram shows interactions between 1xCS CSFB MPS UE, E-UTRAN, MME, 1xCS IWS, 1xRTT MSC, and S-GW. The process starts with the UE being attached and registered. Upon a decision to make a MO call, the UE sends an RRC Connection Setup (if idle) or an Extended Service Request. The MME performs context setup/modification and optional measurement report solicitation. The UE then receives an RRC Release with Redirection (6a) or Enhanced 1xCSFB Signalling (6b). The MME sends a S1 UE Context Release Request to the E-UTRAN, a Suspend Request to the S-GW, and receives a Suspend Request Ack. Finally, the MME performs a S1 UE Context Release and the 1x MO call establishment per 3GPP2 specifications. + +**Figure 6.3.2.2.2-1: CS MO call using fallback to CDMA 1x RTT network by a Service user** + +The key modifications to the basic flow for providing MPS service are: + +1. During the E-UTRAN attach procedure the subscription information downloaded from the HSS contains the CS priority indication if the user is a service user. +- 2a. If the UE is in idle-mode, in order to ensure that the RRC connection is treated with adequate priority the UE sets the establishment cause to HighPriorityAccess. +3. The UE sends extended service request which does not contain any priority indication. +4. The MME determines that the Extended Service Request requires priority handling based on either (a) the "HighPriorityAccess" establishment cause sent by eNB to the MME in the S1AP message if the MO 1xCSFB call occurred when the UE is in idle-mode, or (b) the CS priority indication in subscription information sent by the HSS during the attach procedure if MO 1xCSFB call occurred when the UE is in connected state. The MME sends an S1 UE Context modification (for an active UE) or, UE Context setup (for an idle UE). This message also includes a priority indication. + +According to operator policy the MME may use the CS priority indication to verify the priority handling of the CS Fallback procedure, in the case "HighPriorityAccess" is received in the S1-AP message. + +Steps 5 through 11 occur as specified in TS 23.272 [6]. Either Step 6a occurs in case basic 1xCSFB and Step 6b occur for enhanced 1xCSFB. + +Steps 5 and 6 are handled with priority by the eNB and does not execute concurrent PS handover to CDMA eHRPD access. + +#### 6.3.2.3 Impacted functions in the System + +The HSS provides the CS priority indication to the MME during the subscription data update procedure if the user subscribes the 1xCS priority service in the CS domain. MME determines whether the CSFB MO procedure needs to be handled preferentially based on that indication. + +The MME provides priority indication in S1 AP Initial Context Setup and UE Context Modification Request messages to the eNodeB. + +In a congestion situation, the eNodeB uses priority indications to allocate E-UTRAN radio bearer resources with preference over to normal resource requests with no priority indication. + +# --- 7 Overall Solution + +*Editor's Note: This clause will capture the overall solution (e.g. information storage, call flows, impacts to NE, etc.).* + +## 7.1 IMS Multimedia Priority Services + +## 7.2 Priority EPS Bearer Service + +## 7.3 CS Fallback + +# --- 8 Conclusions + +This Technical Report has served its purpose in providing analysis and solutions in order to support Multimedia Priority Services for E-UTRAN access within Rel-10. + +Based on the analysis provided in the main body of this TR, SA2 can undertake the normative work towards the specifications under its responsibility. + +The potential impacted stage 2 specifications under SA2 responsibility are as follows (list is not exhaustive): + +- TS 23.401 [3] +- TS 23.203 [15] +- TS 23.228 [12] +- TS 23.272 [6] +- TS 23.002 [4]/TS 23.221 [20] (if needed) + +And based on the analysis provided in clause 6.1.5 Priority resource handling in SRVCC, SA WG2 can undertake the normative work towards the Rel-11 specifications under its responsibility. + +The potential impacted stage 2 specifications under SA WG2 responsibility are as follows (list is not exhaustive): + +- TS 23.216 [16] +- TS 23.237 [19] + +No special mechanisms and hence no standards impacts are required to support priority resource handling for SRVCC to 1xCS. + +# --- Annex A: Change history + +| :Change history | | | | | | | | +|-----------------|-------|-----------|----|-----|-----------------------------------------------------------------------|-------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2010-09 | SP-49 | SP-100559 | - | - | <a href="#">MCC Update for presentation to TSG SA for information</a> | 0.5.0 | 1.0.0 | +| 2011-06 | SP-52 | SP-110354 | - | - | <a href="#">MCC update for presentation to TSG SA for approval</a> | 1.4.0 | 2.0.0 | +| 2011-06 | SP-52 | - | - | - | MCC update to version 11.0.0 for publication after TSG SA approval | 2.0.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23855/raw.md b/marked/Rel-11/23_series/23855/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..390a96181ee9b89730fc3cb3d823a84f831db054 --- /dev/null +++ b/marked/Rel-11/23_series/23855/raw.md @@ -0,0 +1,284 @@ + + + + + + +# --- Contents + +| | | +|------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 Justification, Scenarios and Architectural Requirements ..... | 5 | +| 4.1 Justification ..... | 5 | +| 4.2 Architectural requirements..... | 6 | +| 4.3 Scenarios ..... | 6 | +| 4.3.1 Identification of traffic based on throughput..... | 6 | +| 4.3.2 Identification of traffic based on application..... | 6 | +| 4.3.3 Identification of traffic based on content type..... | 7 | +| 4.3.4 Identification of traffic based on destination domain..... | 7 | +| 4.3.5 Identification of traffic based on content size ..... | 7 | +| 5 Solutions..... | 7 | +| 5.1 Alternative 1: Extensions to ISRPs for DIDA ..... | 7 | +| 5.1.1 General ..... | 7 | +| 5.1.2 ISRPs based on destination domain ..... | 8 | +| 5.1.3 ISRPs based on application ..... | 8 | +| 5.1.4 ISRPs based on content type ..... | 8 | +| 5.1.5 ISRP based on content size..... | 8 | +| 6 Conclusions..... | 9 | +| 6.1 Analysis of Scenarios..... | 9 | +| 6.2 Recommendations ..... | 10 | +| Annex A: Change history ..... | 11 | + +# --- Foreword + +This Technical Report has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +This Technical Report describes proposed extensions to ANDSF Inter-System Routing Policies (ISRP) to provide to operators a better control of the network resources used for each application or IP flow. Specifically the Technical Report focuses on additional mechanism to identify classes of traffic an ISRP applies to. + +Any extension to the ANDSF framework which is not related to identification of traffic is outside the scope of this Technical Report. + +# --- 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.402: "Architecture enhancements for non-3GPP accesses". +- [3] 3GPP TS 23.261: "IP flow mobility and seamless WLAN offload". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply. + +# --- 4 Justification, Scenarios and Architectural Requirements + +## 4.1 Justification + +**Editor's note: This clause describes the shortcomings of current ISRP design and the justifications of DIDA work.** + +In Release 10 simultaneous network connections to multiple radio access technologies have been enabled by MAPCON, IFOM and non seamless WLAN offload. To take this into account, the ANDSF framework has been enhanced with the introduction of Inter System Routing Policies (ISRP), allowing the operator to provide policies based on the traffic exchanged by the UE. + +Based on the current Release 10 specification the operator can indicate different preferred or forbidden radio access technologies as a function of the type of traffic the UE sends. As an example an ISRP can be based on: + +- the APN the UE uses for a given connection; +- the destination IP address the UE sends traffic to; + +- the destination port number the UE connects to; +- a combination of the three elements above. + +The current specification has limitations on how the traffic is identified in the UE, e.g. due to the growing aggregation of Internet traffic onto few transport port numbers. This trend negatively impacts the ability of an ANDSF policy to specify how traffic should be routed by the UE. For example the operator with the current framework is not able to provide policies to the UE that allow to discriminate between video streaming (e.g. [www.videostreaming.example.com](http://www.videostreaming.example.com)) and web browsing (e.g. [www.news.example.com](http://www.news.example.com)) based on the port number because both are carried over HTTP. + +## 4.2 Architectural requirements + +The following architectural requirements apply for the DIDA solution(s): + +- Support for DIDA should enable IP flows to be identified in the UE even though encryption is enabled e.g. using SSL/TLS. + +## 4.3 Scenarios + +**Editor's note:** This clause describes the scenarios to be taken into account for the definition of solutions. + +**Editor's note:** Combinations of the following scenarios will also be analyzed. + +### 4.3.1 Identification of traffic based on throughput + +The operator may be interested in providing policies in order to influence the radio technology used by the UE for high-throughput traffic. As an example, the operator may indicate via ANDSF policies that IP flows which require a data rate above a certain threshold are to be sent over a given access. + +**Editor's note:** More detailed scenarios need to be provided. + +**Editor's note:** It is desirable to avoid the UE measuring the data rate of all IP flows to enable this scenario. + +**Criteria of the identification:** IP flows are identified based on the required data rate + +### 4.3.2 Identification of traffic based on application + +The operator may want to set the preferred or restricted access technology for specific applications (e.g., a specific video streaming application). For example this would be useful in the following scenarios: + +- The operator may want some applications to use non-seamless WLAN (NS-WLAN) offload, and other applications to be routed through the 3GPP core network. Given the high number of IP addresses used by some application servers, it is difficult to support this scenario using Rel-10 policies. +- Some applications will not work with NS-WLAN offload because service requests (i.e. control traffic) need to go through the 3GPP core network, although media traffic may be performed with NS-WLAN offload. As an example, an RTSP session may need to go through the 3GPP core (e.g. to identify and bill the subscriber) but RTP/RTCP traffic may be routed over NS-WLAN and offload the 3GPP system. To accommodate such scenarios, it is required to support ISRP policies for NS-WLAN offload of the form: "Traffic of application X and of protocol Y shall be restricted on the WLAN radio access". + +**Editor's note:** FFS how separation of RTP and RTSP would work with NAT, Firewalls and security. + +- Some applications will work with NS-WLAN offload but should preferably be routed over 3GPP access for example to enjoy improved performance from guaranteed QoS. Traffic from such applications should be identified in the UE and routed to the 3GPP radio access. For this purpose, it is required to support ISRP policies for NS-WLAN offload of the form: "Traffic of application X shall be restricted on the WLAN radio access". + +This is a way for the operator to provide control over the usage of resources even for different applications which use the same port number and for services which are hosted in the same servers. + +**Criteria of the identification:** IP flows are identified based on an application identifier or the name of the application which generated them. + +### 4.3.3 Identification of traffic based on content type + +The operator may want to set the preferred or restricted access technology for IP flows which carry a specific content type (e.g. all IP flows associated with a given MIME media type such as video, image, text). This may be needed for those applications which cannot be easily identified. This would be useful in the following scenarios: + +- The operator prefers that all IP flows associated with video streaming content are routed through WLAN when available. In this case the group of applications is all applications which provide a video streaming service. + +**Criteria of the identification:** IP flows are identified based on the content type. + +### 4.3.4 Identification of traffic based on destination domain + +With the advent of virtual hosts and Content Delivery Networks, a single IP address can actually host different services. Moreover the same service can be provided via different IP addresses depending on the location of the UE. This implies that the destination IP address and destination port that currently can be used in ISRP policies are not enough to describe a specific IP flow. To overcome this limitation, the FQDN of the application peer could be used instead. This would be useful in the following scenarios: + +- The operator prefers that all traffic destined to [www.example.com](http://www.example.com) is routed through WLAN when available. + +**Criteria of the identification:** IP flows are identified based on the application peer's FQDN. + +### 4.3.5 Identification of traffic based on content size + +The operator may need to restrict large content from being transferred over 3GPP access in order to protect users with limited data plans and/or to offload the 3GPP network from excess data traffic. To fulfil this need, it would be beneficial to extend data identification in the ANDSF in order to support policies, as an example, of the form: + +- "Content larger than X bytes should not use 3GPP access between 10am and 5pm". + +**Editor's Note:** It is FFS how to ensure a consistent user experience with such an operator policy. + +It is expected that the content size determination will be carried out in the UE with implementation specific means. The ANDSF policies that identify traffic based on content size should be considered as operator preferences applied by the UE only when the UE can determine the size of the content. + +# --- 5 Solutions + +## 5.1 Alternative 1: Extensions to ISRPs for DIDA + +### 5.1.1 General + +Enhancements to current ISRPs can be defined to accommodate the scenarios described in section 4. The overall format of an ISRP is not expected to be affected. + +The ANDSF can provide a list of ISRP to the UE based on Release 10 procedures described in TS 23.402 [2]. In order to enable enhanced IP flow identification based on the scenarios in section 4, the ISRP provided to the UE will include the following information: + +- Validity conditions as per current 23.402 (Release 10). +- For IFOM: one or more Filter Rules, each one identifying a prioritised list of access technologies / access networks which should be used by the UE when available to route traffic that matches specific IP filters on a specific APN or on any APN. This is the same as in Release 10 procedure. +- For non-seamless WLAN offload: one or more Filter Rules, each one identifying which flows corresponding to specific IP filters shall or shall not be non-seamlessly offloaded to a WLAN when available. This is the same as in Release 10 procedure. +- The Filter Rules can include: + +- Previous Release 10 parameters (protocol type, source IP address, destination IP address, source port number, destination port number, address type, DSCP value); +- Additional information as listed in the following subsections. + +### 5.1.2 ISRs based on destination domain + +To enable ANDSF policies based on destination domain, the Filter Rules include: + +- Fully Qualified Domain Name (e.g. [www.example.com](http://www.example.com)) that was resolved into the destination IP address. + +For example, when the UE receives an ISR with [www.example.com](http://www.example.com) in IP filter and WLAN as preferred access technology, it should route all traffic with destination IP addresses resolved from [www.example.com](http://www.example.com) through WLAN. + +A combination of different IP filters parameters is possible. For example, the operator can indicate that all traffic with destination IP addresses resolved from [www.example.com](http://www.example.com) and with a specific destination port number should be routed through a preferred access. + +### 5.1.3 ISRs based on application + +To enable ANDSF policies based on application, the Filter Rules include: + +- A globally unique identifier of the application. + +NOTE 1: Detailed definition of these IDs and respective namespace is left to stage 3. + +NOTE 2: This solution assumes that the UE can bind the connection request with the application which generated that request. + +For example, when the UE receives an ISR with an application identifier in the filter and WLAN as preferred access technology, it should route all traffic generated by that application(s) through WLAN. + +### 5.1.4 ISRs based on content type + +To enable ANDSF policies based on content type, the Filter Rules include: + +- Content Type (e.g. video, image, text). + +For example, when the UE receives an ISR with content type in the filter and WLAN as preferred access technology, it should route all traffic carrying contents of which type is matched with the received content type through WLAN. The content type may be one of Internet media types included in the MIME Content-Type header. + +### 5.1.5 ISR based on content size + +To enable ANDSF policies based on content size, the Filter Rules include: + +- Range of content size. + +For example, when the UE receives an ISR with a range of content size in the filter and WLAN as preferred access technology, it should route all traffic of which size is within the received range through the WLAN. The range of content size in ISR can be a pair of minimum and maximum of content size in bytes and the UE applies this rule if it can determine content size. + +**Editor's note:** It is FFS how the UE determines its content size before retrieving a content. + +**Editor's note:** Evaluation for the feasibility of this solution is also FFS. + +# --- 6 Conclusions + +## 6.1 Analysis of Scenarios + +This clause provides some analysis and concluding remarks for the scenarios documented in clause 4.3. + +NOTE: All references to UE refer to a UE that is capable of routing IP traffic simultaneously over multiple radio access interfaces, e.g. an IFOM capable UE or a UE capable of non-seamless WLAN offload. + +### Identification of traffic based on throughput + +- This scenario requires the UE to identify IP flows with specific throughput requirements and route these flows based on the provisioned ANDSF policies. It is assumed that the throughput requirement of a specific IP flow is explicitly provided by the application that generates this IP flow or it is derived by the UE's operating system by other means, e.g. by pre-configuring the throughput requirements of specific IP flows. This assumption makes it unnecessary for the UE to measure the traffic rate of all IP flows in real-time and can thus avoid excessive complexity and power consumption in the UE. +- It is envisioned that in several situations the UE may not be able to determine the required throughput of an IP flow. For example, a streaming application may request a video content but does not know if the content will be provided by the server in high-definition format or not, so it cannot pre-determine how much throughput will be required to support the streaming session. In another case, the application may be able to pre-determine the required throughput of an IP flow but there is no API to provide this information to the operating system (most mobile operating systems today do not support such API). Even when the operating system is upgraded to support a new API that will enable applications to provide the required throughput of an IP flow, there is no guarantee that application developers will make use of this API. +- Based on the above considerations, it is concluded that the UE will not be able to identify the throughput requirements of IP flows in many cases. Therefore the ANDSF policies that rely on traffic identification based on throughput can only be applied on a "best-effort basis", meaning that the UE will not be able to guarantee the enforcement of these policies and the behaviour will vary a lot based on UE implementations. + +### Identification of traffic based on destination domain + +- This scenario requires the UE to identify IP flows based on the destination FQDN, i.e. identify all flows to [www.example.com](http://www.example.com). +- The UE could easily identify traffic based on the destination FQDN. For example, the UE could store all IP addresses associated with a specific FQDN (these addresses are discovered with DNS queries) and then detect which IP flows have a destination address that matches one of these IP addresses. +- It is expected that the UE could support ANDSF policies that identify traffic based on the destination FQDN and would be able to contact specific domain names over the desired radio access. + +### Identification of traffic based on application + +- This scenario requires the UE to identify IP flows based on the application that generated them. It means to provide operators with a tool for steering the traffic of some applications to a specific radio access, for example, "traffic of application X should use 3GPP access". +- In practice, it is expected that operators will require the UE to identify the traffic of a limited number of applications; notably, of applications that the operator prefers not to use 3GPP access in the presence of a more preferred access or that are preferred to use exclusively 3GPP access. Therefore, it is not expected that operators will need to determine the identities of hundreds of applications and it is not expected that the UE will need to be provisioned with hundreds of policies for traffic identification based on application ids. +- The traffic identification in the UE based on the application identity does not intent to address all possible scenarios. For example, it may not be possible to identify malicious applications that change their identities or applications downloaded in the UE from various application repositories. +- There is no need to create a 3GPP-specific "application registry" which assigns unique identities to all possible mobile applications. Each application contains its own identity which is known to the UE and can be included in the applicable routing policies. +- Current major mobile platforms today provide some means for assigning application identities or names that are unique in the default application repository. For example, Java applications use identities/names of the form [com.organization.app-name](http://com.organization.app-name). Unique application identifiers are also used in platforms with non-Java applications. In addition, current major mobile platforms provide means to identify the traffic created by specific applications. Thus, traffic identification based on application id is expected to be feasible for UEs based on such platforms. + +- Based on the above considerations, it is concluded that (i) it is possible to identify an application in most mobile platforms today (ii) the ANDSF has the means to know the UE's platform so it can provide platform specific policies to UE and (iii) traffic identification based on application id is expected to be feasible for the UE. + +NOTE: Whether platform-specific ANDSF policies are distributed to the UE is left for stage 3 to decide. + +### **Identification of traffic based on content type** + +- This scenario requires the UE to identify IP flows which are used to retrieve content of a specific type (e.g. audio, video, text, etc). An example use case is when the operator wants to restrict video retrieval over a specific radio access only. +- When the content is retrieved with the HTTP protocol, the UE can determine the content type before retrieving the content, e.g. by using the HEAD method. Similarly, when RTSP is used, the UE can determine the content type before retrieving the content, e.g. by sending a DESCRIBE request. +- However, to enforce IP flow routing based on content type, it is expected that the mobile platform should be capable to intercept content requests from applications and determine the content type before retrieving the requested content on the desired radio access. The use of HTTPS may also impose additional restrictions. + +### **Identification of traffic based on content size** + +- This scenario requires the UE to identify IP flows which are used to retrieve content with specific size attributes. A typical example is when the operator wants to restrict very large content (e.g. more than 10Mbytes) from being transferred over 3GPP access. +- Most content retrieval on mobile devices is based on the HTTP, FTP and RTSP protocols. All of these protocols provide means for determining the content size before retrieving the content. For example, with the FTP protocol the SIZE command could be used, with the HTTP protocol the HEAD method could be used and with the RTSP protocol the DESCRIBE command could be used. +- However, to enforce IP flow routing based on the content size, it is expected that the mobile platform should be capable to intercept content requests from applications and determine the content size before retrieving the requested content on the desired radio access. The use of HTTPS may also impose additional restrictions. + +## **6.2 Recommendations** + +This Technical Report has proposed and analyzed several scenarios that extend the data identification capabilities of ANDSF policies. As a result of the analysis, the following scenarios are recommended for normative specification: + +- Identification of traffic based on domain name. +- Identification of traffic based on application ID. + +**Editor's note: Is it FFS whether other scenarios should be recommended for normative specification.** + +In addition, a solution based on the extension of ISRP as the one documented in clause 5.1 is recommended for inclusion in the normative specifications. + +# --- Annex A: Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +|---------|-------|-----------|----|-----|-----|-------------------------------------------------------------------------------------|-------|--------| +| 2011-12 | SP-54 | SP-110757 | - | - | - | MCC Update to version 1.0.0 for presentation to TSG SA for information and approval | 0.4.0 | 1.0.0 | +| 2011-12 | SP-54 | - | - | - | - | MCC Update to version 11.0.0 after TSG SA approval | 1.0.0 | 11.0.0 | +| | | | | | | | | | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23888/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-11/23_series/23888/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c3a8f5cbadbbbe2ebc26223f217a252ec28fbca --- /dev/null +++ b/marked/Rel-11/23_series/23888/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b6c2f896e0be40bb0fe0c4e70b74200a80b56d5f486905f0d92f3f85606be56 +size 106249 diff --git a/marked/Rel-11/23_series/23888/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-11/23_series/23888/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f2e0bc4400e4bc1e328caa6802df5470efb91a5 --- /dev/null +++ b/marked/Rel-11/23_series/23888/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d197a0dc54a798d7d737c41794d9a5bf296c519be36f706aaa72e4b37ee01f8 +size 71642 diff --git a/marked/Rel-11/23_series/23888/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/23_series/23888/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07ea43de6d87c3725465d5c042290069d674f1e3 --- /dev/null +++ b/marked/Rel-11/23_series/23888/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e256bda02b2464280857707bbfe1eea3d8bd05963855d0f1265f41de207ae6fc +size 34211 diff --git a/marked/Rel-11/23_series/23888/1b2ce053624064d94a4143854da46702_img.jpg b/marked/Rel-11/23_series/23888/1b2ce053624064d94a4143854da46702_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecb199cb2ed58ba1a1c36ed46bd0d3138a9ac7e0 --- /dev/null +++ b/marked/Rel-11/23_series/23888/1b2ce053624064d94a4143854da46702_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1dbe9c63caba7b5295ad36fb788eda54f2a36f1037167cd0d677a592352e873 +size 28383 diff --git a/marked/Rel-11/23_series/23888/1b3c088f23921d4eeb45ffc05586e59b_img.jpg b/marked/Rel-11/23_series/23888/1b3c088f23921d4eeb45ffc05586e59b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad9421ab8d5132fae2351fcdc566e0e2943d0a42 --- /dev/null +++ b/marked/Rel-11/23_series/23888/1b3c088f23921d4eeb45ffc05586e59b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:583135c9d9de14dbd35f3e48368e989c0623d10336e410fc100734b70c7d9e9e +size 72301 diff --git a/marked/Rel-11/23_series/23888/1d723f5111a010a80347ee4ead0da1a9_img.jpg b/marked/Rel-11/23_series/23888/1d723f5111a010a80347ee4ead0da1a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68823486312137841c9b9dae9469ef2b97af3c49 --- /dev/null +++ b/marked/Rel-11/23_series/23888/1d723f5111a010a80347ee4ead0da1a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6075f135b53c65748ddcdb7ffd1d9b893b260401244349b6491febadcdc2a12c +size 68699 diff --git a/marked/Rel-11/23_series/23888/1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg b/marked/Rel-11/23_series/23888/1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00a22b5010cfcc9ed0c68826d9c05f3dfde19d7b --- /dev/null +++ b/marked/Rel-11/23_series/23888/1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be861cb479f83c676d583c1a80858a33035aca99f0fade9964cceeac32b29d77 +size 89368 diff --git a/marked/Rel-11/23_series/23888/1ff58ab75ff926ead7067453006a75fe_img.jpg b/marked/Rel-11/23_series/23888/1ff58ab75ff926ead7067453006a75fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2bb0b8c23343c4e31695e06626182014208e40a --- /dev/null +++ b/marked/Rel-11/23_series/23888/1ff58ab75ff926ead7067453006a75fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fa07c3b41568792db1817c02fd5faafb6a7ab7c6595524086097eb8c97da501 +size 61587 diff --git a/marked/Rel-11/23_series/23888/2119293733c74fc64de88aefd597f4bb_img.jpg b/marked/Rel-11/23_series/23888/2119293733c74fc64de88aefd597f4bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7408448031105dbf77afc9acfcb415f112ced63b --- /dev/null +++ b/marked/Rel-11/23_series/23888/2119293733c74fc64de88aefd597f4bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8f1dfe458dbec65f42b801e6fb572e21ab9d895921cf5ceb7eb377fa9eaaf1d +size 30379 diff --git a/marked/Rel-11/23_series/23888/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-11/23_series/23888/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33d3ff62c04b9cf7b99260b7dd555706d18e51a5 --- /dev/null +++ b/marked/Rel-11/23_series/23888/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a4802fc594cecee19fe1a13ed3096e1d187222f7ba0aa544e46f249a46776f4 +size 69173 diff --git a/marked/Rel-11/23_series/23888/2bea721b89ee5816651ed9cdc328bc9f_img.jpg b/marked/Rel-11/23_series/23888/2bea721b89ee5816651ed9cdc328bc9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c08a2e763e06f4480a739106c416c4db55cd7a3a --- /dev/null +++ b/marked/Rel-11/23_series/23888/2bea721b89ee5816651ed9cdc328bc9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dece226a7c5db93dbe7d4da3af31585fba0d02bcb8fdccb4bde0d3d634c714e +size 49908 diff --git a/marked/Rel-11/23_series/23888/34cbe6293693bd7fa95f2755c16b66bd_img.jpg b/marked/Rel-11/23_series/23888/34cbe6293693bd7fa95f2755c16b66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43220a65279d158379a04b49aec32f53da89e4a7 --- /dev/null +++ b/marked/Rel-11/23_series/23888/34cbe6293693bd7fa95f2755c16b66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6372d13d561f93b94bca97b887f286c020122170b796a8d24b115bf13cf263fb +size 48901 diff --git a/marked/Rel-11/23_series/23888/351432d1a55458897fdc5e81ffc832fe_img.jpg b/marked/Rel-11/23_series/23888/351432d1a55458897fdc5e81ffc832fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77be9b0250878e9d9efdef1383f74025e0f3ad00 --- /dev/null +++ b/marked/Rel-11/23_series/23888/351432d1a55458897fdc5e81ffc832fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd207b38aa0c63683c36e648e61ce9ef91249de2ba29d7d918406ac7cf105efb +size 70218 diff --git a/marked/Rel-11/23_series/23888/3558a64b4f3d03eb8da8e584c606af39_img.jpg b/marked/Rel-11/23_series/23888/3558a64b4f3d03eb8da8e584c606af39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0924673faf9ebc00e8a77828a036883f6174c98e --- /dev/null +++ b/marked/Rel-11/23_series/23888/3558a64b4f3d03eb8da8e584c606af39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65f71dba73d81caf80dc67562eebb406411c68e7af1b281ecc2b2e618611a3c0 +size 914 diff --git a/marked/Rel-11/23_series/23888/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/Rel-11/23_series/23888/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44a4cf14e87cb9664be0a1e9a6e75062049019ad --- /dev/null +++ b/marked/Rel-11/23_series/23888/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b526c0b601bd6e7a80e00a9fb87dae859810a026fec3caf9d6abb5fdd5d6dee5 +size 37915 diff --git a/marked/Rel-11/23_series/23888/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-11/23_series/23888/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f71705f55080f6d1802ec07655212038dbfee121 --- /dev/null +++ b/marked/Rel-11/23_series/23888/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f3a8995e91318426213f285742167a1074cd758f29eb3dec98cab99f9b8452a +size 84083 diff --git a/marked/Rel-11/23_series/23888/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Rel-11/23_series/23888/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..757d53b3a5e9b449e340cfb4f80687c5358aa655 --- /dev/null +++ b/marked/Rel-11/23_series/23888/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:103cd49a34ad4f76422cf689ef3cccc9da0a6da8fbac40439ac9aff8e2137398 +size 15744 diff --git a/marked/Rel-11/23_series/23888/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/23_series/23888/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43636db9997945a4ebb4ea42366945747f5bdbce --- /dev/null +++ b/marked/Rel-11/23_series/23888/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a96f3316c9e256c63da7e0ffaeaa1f41c9610646dc2f22a4739e47d690dc870f +size 83470 diff --git a/marked/Rel-11/23_series/23888/6e9fbc3d95eb2b3f67cbbbd5de0c3999_img.jpg b/marked/Rel-11/23_series/23888/6e9fbc3d95eb2b3f67cbbbd5de0c3999_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0b3a39087176abd44c3b2e84a7cf555b7cc3ba7 --- /dev/null +++ b/marked/Rel-11/23_series/23888/6e9fbc3d95eb2b3f67cbbbd5de0c3999_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6c528628b622708fbbf80f79eaf48cb43f612ff0380139c135ec1407bceb6fd +size 51313 diff --git a/marked/Rel-11/23_series/23888/6ee202d340236de98def8045f273fa38_img.jpg b/marked/Rel-11/23_series/23888/6ee202d340236de98def8045f273fa38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad96aef41db6e1f5059ca7324841812399e22b01 --- /dev/null +++ b/marked/Rel-11/23_series/23888/6ee202d340236de98def8045f273fa38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3aa2bfb96a2be82d7059b93f400f3e210a86531a6452aaf22cb19de088ff8030 +size 80475 diff --git a/marked/Rel-11/23_series/23888/7528e790beec9b44a780eed57fb933f1_img.jpg b/marked/Rel-11/23_series/23888/7528e790beec9b44a780eed57fb933f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb0fbdf91d7713a63df69383c83950ce45183061 --- /dev/null +++ b/marked/Rel-11/23_series/23888/7528e790beec9b44a780eed57fb933f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbe7456bd90342e3c97a46720ae558d3fa1c9485d364ee200222ccac4305ec8f +size 24193 diff --git a/marked/Rel-11/23_series/23888/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-11/23_series/23888/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6eab52a23c1073d1b3503234017273b71eaf77bb --- /dev/null +++ b/marked/Rel-11/23_series/23888/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58e0044207108dd5bad618a7b0a99f0528c676791ab6757467acd9bd2701b5dd +size 60339 diff --git a/marked/Rel-11/23_series/23888/78a8921806daa748fe4258601b530f39_img.jpg b/marked/Rel-11/23_series/23888/78a8921806daa748fe4258601b530f39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4958ee4288bb73c330aced79266202c5097af41 --- /dev/null +++ b/marked/Rel-11/23_series/23888/78a8921806daa748fe4258601b530f39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b979d9194fd2f6f8a2f70691cd40c3612b5a52ab65ace892ca23218b0fc075a9 +size 26454 diff --git a/marked/Rel-11/23_series/23888/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/23_series/23888/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d65c30f3182de236961180445b06c6c87bbc5fc5 --- /dev/null +++ b/marked/Rel-11/23_series/23888/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82180e5616728ad3e294fb3641f3f36122a18c5eaf09bfa7b7233dd348871066 +size 68571 diff --git a/marked/Rel-11/23_series/23888/868ee7df1ec851f132ccf8c390de76a8_img.jpg b/marked/Rel-11/23_series/23888/868ee7df1ec851f132ccf8c390de76a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e62aecc7493a75e497a70a16b1af7af07e59935c --- /dev/null +++ b/marked/Rel-11/23_series/23888/868ee7df1ec851f132ccf8c390de76a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d63ee81b6fec46d1d6b4d7582ff98312221f6c516a83faef884c1ab85c984898 +size 74542 diff --git a/marked/Rel-11/23_series/23888/88066268366ca160709e20f13ed8f356_img.jpg b/marked/Rel-11/23_series/23888/88066268366ca160709e20f13ed8f356_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e3bc3bccfc470573f05a9007f71168ed1f640fa --- /dev/null +++ b/marked/Rel-11/23_series/23888/88066268366ca160709e20f13ed8f356_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:649a912a94ee17f7a5552522f8fe8b078b81e963f706a3398f1c58779f857489 +size 48120 diff --git a/marked/Rel-11/23_series/23888/8def7bf8f6f13fd54fb7c2386dc4b635_img.jpg b/marked/Rel-11/23_series/23888/8def7bf8f6f13fd54fb7c2386dc4b635_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d7035d9b6891e79ebc5f9a0fde97a4d3bc09b18 --- /dev/null +++ b/marked/Rel-11/23_series/23888/8def7bf8f6f13fd54fb7c2386dc4b635_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e8c6d5c273a25cb40410d292ca4b6965705eea3fb4dfcefdfdd3db84e9e306a +size 30404 diff --git a/marked/Rel-11/23_series/23888/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg b/marked/Rel-11/23_series/23888/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6e91c694bfc6706bdf5909ea89533cc1b5f62ea --- /dev/null +++ b/marked/Rel-11/23_series/23888/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c4737164efa1b4523d6698318f93dcbb48f5fdb838542e2a530eb6c193f6b11 +size 35249 diff --git a/marked/Rel-11/23_series/23888/901343511e3efc3f994eaffe6fc393ca_img.jpg b/marked/Rel-11/23_series/23888/901343511e3efc3f994eaffe6fc393ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8887775250b93633ce6c5a4b16c631b61fe8a9e5 --- /dev/null +++ b/marked/Rel-11/23_series/23888/901343511e3efc3f994eaffe6fc393ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d4e09b21bd4cde522472c45e9f9145991a0acae64e91401e1740016f60c41b7 +size 24356 diff --git a/marked/Rel-11/23_series/23888/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/Rel-11/23_series/23888/977811d1c73b74f801be9f4c376694ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ee06e9cbe4e6928673fb68dbf07829c98a4f0d1 --- /dev/null +++ b/marked/Rel-11/23_series/23888/977811d1c73b74f801be9f4c376694ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a97d90881d4be853d7283e21f377d5437ed38dede2ea7f0def05a856bcf1df22 +size 56871 diff --git a/marked/Rel-11/23_series/23888/9aa0b1bed68fb431319e7a58045a3146_img.jpg b/marked/Rel-11/23_series/23888/9aa0b1bed68fb431319e7a58045a3146_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60f8b3ec61417fcb95b6399a3accb31666719294 --- /dev/null +++ b/marked/Rel-11/23_series/23888/9aa0b1bed68fb431319e7a58045a3146_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dde88da8b1f7014ceeca13c7e2aa8ee675a16d7b5cd27fc3234b450d6ddffdea +size 55097 diff --git a/marked/Rel-11/23_series/23888/9ba75f891de20483c291538e38701d96_img.jpg b/marked/Rel-11/23_series/23888/9ba75f891de20483c291538e38701d96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f653cc61c4716f92f509d6d5234b4d9aae56f7a --- /dev/null +++ b/marked/Rel-11/23_series/23888/9ba75f891de20483c291538e38701d96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c031e107eb44d0f57d4e38a66d7824ee0b4162c301ba011ba731518b9a9d687 +size 26939 diff --git a/marked/Rel-11/23_series/23888/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-11/23_series/23888/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61e844e698086c4333aad92ccc297982cdeef0ed --- /dev/null +++ b/marked/Rel-11/23_series/23888/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21a880f667c473e110c28804c7ba78992ae4d18b2d7da5ef634ff6fe4f1b4ecb +size 76853 diff --git a/marked/Rel-11/23_series/23888/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/23_series/23888/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7f81d3e052940f4b09a8473a0c4b77cd5958d41 --- /dev/null +++ b/marked/Rel-11/23_series/23888/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e562b15f946e0bc923e18f162650fcd24b63264e364ab37a7773c4008864371 +size 18582 diff --git a/marked/Rel-11/23_series/23888/a9241101d638c568cd5a84ab7ad39f15_img.jpg b/marked/Rel-11/23_series/23888/a9241101d638c568cd5a84ab7ad39f15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bf0ae5263c9d08d2f9365f9b25c54b009e08872 --- /dev/null +++ b/marked/Rel-11/23_series/23888/a9241101d638c568cd5a84ab7ad39f15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3598ae7daad58163d4410981b427379608984e85bd7fb8978af84c1a6303af43 +size 65277 diff --git a/marked/Rel-11/23_series/23888/aec32fe54f8d88d7a631e4cb8d76e70d_img.jpg b/marked/Rel-11/23_series/23888/aec32fe54f8d88d7a631e4cb8d76e70d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4c7f7407e5d1d51ad201b306b2442ba8bad5c39 --- /dev/null +++ b/marked/Rel-11/23_series/23888/aec32fe54f8d88d7a631e4cb8d76e70d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7857c319a6ebb59b2f307356d1adab79ea0f299ff18710e4f8286f07da39d7a4 +size 34385 diff --git a/marked/Rel-11/23_series/23888/b361fd4d68b14568a6c5acbcd9bfe8ee_img.jpg b/marked/Rel-11/23_series/23888/b361fd4d68b14568a6c5acbcd9bfe8ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..889c55a0c8a6a0090d32e93ffefece64deb9e6e6 --- /dev/null +++ b/marked/Rel-11/23_series/23888/b361fd4d68b14568a6c5acbcd9bfe8ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdf3fd9a8dbe336fab5f4389da01e5acea233e606ace65d744a9a9e216a1a598 +size 34577 diff --git a/marked/Rel-11/23_series/23888/b4e9fc9d087037ebe92a54050272e7d6_img.jpg b/marked/Rel-11/23_series/23888/b4e9fc9d087037ebe92a54050272e7d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04ee171c2e5b892eb428aa659085d16593d5c23d --- /dev/null +++ b/marked/Rel-11/23_series/23888/b4e9fc9d087037ebe92a54050272e7d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:613ee33e2d0f1a0560234f77081fe38421e815f94bb99200e74cb6ac573c2910 +size 30657 diff --git a/marked/Rel-11/23_series/23888/b50f38be091844d58b11e3d47bc71e73_img.jpg b/marked/Rel-11/23_series/23888/b50f38be091844d58b11e3d47bc71e73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9775ae6c654ac2f4135220a249b036ef53209c21 --- /dev/null +++ b/marked/Rel-11/23_series/23888/b50f38be091844d58b11e3d47bc71e73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51442b2d8ff9ecec09d642f3f91cbdeb655e3f0723939776d42572a1daf160ad +size 53855 diff --git a/marked/Rel-11/23_series/23888/bedcefe3d0fc5b6a061f16121cd2f291_img.jpg b/marked/Rel-11/23_series/23888/bedcefe3d0fc5b6a061f16121cd2f291_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96ca22c668b6f59620e319b3db28de19b6d26c8c --- /dev/null +++ b/marked/Rel-11/23_series/23888/bedcefe3d0fc5b6a061f16121cd2f291_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbba0f0300bcaab28d3406680b0ba55a76fd6ce5e944ecf6514aa0bbd0dd5d0d +size 43011 diff --git a/marked/Rel-11/23_series/23888/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg b/marked/Rel-11/23_series/23888/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1780889cd0fb4294ed249517ba9168969da874e5 --- /dev/null +++ b/marked/Rel-11/23_series/23888/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e9785dd051854b4f97964c3e18066bfd58f8f49b9b62172aea38180fc2a7c55 +size 37213 diff --git a/marked/Rel-11/23_series/23888/ced309874aec0546651b0976d5030a42_img.jpg b/marked/Rel-11/23_series/23888/ced309874aec0546651b0976d5030a42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..478d767500685d6ca8dec75c780aa96a0b4a980b --- /dev/null +++ b/marked/Rel-11/23_series/23888/ced309874aec0546651b0976d5030a42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7986bd3d78269183081797d1336c58c016343e51bd64a7997ef35f5860776bea +size 27447 diff --git a/marked/Rel-11/23_series/23888/d4e22bbe01024f0a4981d41da11252a9_img.jpg b/marked/Rel-11/23_series/23888/d4e22bbe01024f0a4981d41da11252a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbfee5a78b0f99e6ebf0a47aa170bc6d4f6d0144 --- /dev/null +++ b/marked/Rel-11/23_series/23888/d4e22bbe01024f0a4981d41da11252a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a163b177eeaa44fc255fb144cc7a326c14918e2d04e547273b1a1e6bc749921 +size 24166 diff --git a/marked/Rel-11/23_series/23888/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-11/23_series/23888/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e06835b93c45f2013774c65f530648178305b480 --- /dev/null +++ b/marked/Rel-11/23_series/23888/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c1000f4ad4f47b8213ed82e58067266db53b5f9c37a836c76149c335745621f +size 51220 diff --git a/marked/Rel-11/23_series/23888/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-11/23_series/23888/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e076bb7904150b1a1f674ca244abb27214d41f47 --- /dev/null +++ b/marked/Rel-11/23_series/23888/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:312b5a0d9bd918af8915e7ae72799b67540e4a25ff51db7b359e77cc6469eabd +size 113083 diff --git a/marked/Rel-11/23_series/23888/e38206fcefa2045af01d494b2956775a_img.jpg b/marked/Rel-11/23_series/23888/e38206fcefa2045af01d494b2956775a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9905e7079192bd07431f5b01dc3fa9bf8371a24 --- /dev/null +++ b/marked/Rel-11/23_series/23888/e38206fcefa2045af01d494b2956775a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1f255edc2d240d976f5ec4837429166a2e500756ec96e80fcf584d8210bef0a +size 18101 diff --git a/marked/Rel-11/23_series/23888/e6cd61d926d5742b7c149a8377b3f55b_img.jpg b/marked/Rel-11/23_series/23888/e6cd61d926d5742b7c149a8377b3f55b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c3fc823a500609d78ffc2cb39af9494dc8b6e0b --- /dev/null +++ b/marked/Rel-11/23_series/23888/e6cd61d926d5742b7c149a8377b3f55b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f786fca2a20cabb10a39a4d454e513fb40f5f34c7a4a4761d5c7de3ae15b0c2a +size 38572 diff --git a/marked/Rel-11/23_series/23888/e9c070631848606db3524757b0121c06_img.jpg b/marked/Rel-11/23_series/23888/e9c070631848606db3524757b0121c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86c4cffcdd92c485ebd44d765d21d62c2eb7402e --- /dev/null +++ b/marked/Rel-11/23_series/23888/e9c070631848606db3524757b0121c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32904374c8825dfc86a86162df79107f092097850269078c25e28226aade8188 +size 28137 diff --git a/marked/Rel-11/23_series/23888/f502d41e990d86acbbd785962f2af138_img.jpg b/marked/Rel-11/23_series/23888/f502d41e990d86acbbd785962f2af138_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..718a24364a54321f7585213d37eaefe68f1115e9 --- /dev/null +++ b/marked/Rel-11/23_series/23888/f502d41e990d86acbbd785962f2af138_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb2402a0e22bb3e854804dab4d66d2b82500d80b5c1788e530b4b1b394f098d8 +size 95098 diff --git a/marked/Rel-11/23_series/23888/f796c4b6ef101faa39b887a86820c3d1_img.jpg b/marked/Rel-11/23_series/23888/f796c4b6ef101faa39b887a86820c3d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72ce2c1c9bfdf64fd84d452ab0381e6e416b1565 --- /dev/null +++ b/marked/Rel-11/23_series/23888/f796c4b6ef101faa39b887a86820c3d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3c72a8d3bfa913b9cec61696d44c717fc8d98e5fd2ad5cb8b5e395705ddea77 +size 49089 diff --git a/marked/Rel-11/23_series/23888/raw.md b/marked/Rel-11/23_series/23888/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9dd5907d09d19de39edb13e6d63df97a335f32c1 --- /dev/null +++ b/marked/Rel-11/23_series/23888/raw.md @@ -0,0 +1,6251 @@ + + + + +**Error:** + +**2** + +**Error: Reference source not** + +# Contents + +| | | +|------------------------------------------------------------------------------------------------|----| +| Foreword..... | 11 | +| 1 Scope..... | 12 | +| 2 References..... | 12 | +| 3 Definitions and abbreviations..... | 13 | +| 3.1 Definitions..... | 13 | +| 3.2 Abbreviations..... | 13 | +| 4 Architectural Considerations..... | 14 | +| 4.1 Architectural requirements..... | 14 | +| 4.1A. Architecture Principles..... | 14 | +| 4.2 Architecture Model..... | 14 | +| 4.3 Architectural Reference Model for MTC..... | 16 | +| 4.4 Network Elements..... | 19 | +| 4.4.1 General..... | 19 | +| 4.4.2 MTC-IWF..... | 19 | +| 4.4.3 HLR/HSS..... | 20 | +| 4.4.4 GGSN/PGW..... | 20 | +| 4.4.5 SGSN/MME..... | 20 | +| 4.5 Reference Points..... | 20 | +| 4.5.1 General..... | 20 | +| 4.5.2 List of Reference Points..... | 21 | +| 4.5.3 Reference Point Requirements..... | 21 | +| 4.5.3.1 MTCsp Reference Point Requirements..... | 21 | +| 4.5.3.2 T4 Reference Point Requirements..... | 21 | +| 4.5.3.3 T5a/T5b Reference Point Requirements..... | 22 | +| 4.5.3.4 S6m Reference Point Requirements..... | 22 | +| 4.6 High Level Functions..... | 22 | +| 4.6.1 General..... | 22 | +| 4.7 Authorization and Security..... | 22 | +| 4.8 Protocol Stacks..... | 23 | +| 4.8.1 User plane..... | 23 | +| 4.8.2 Control plane..... | 23 | +| 4.8.2.1 MTC Server-MTC-IWF MTCsp reference point..... | 23 | +| 4.8.2.2 MTC Server-SMS SC MTCsms reference point..... | 24 | +| 5 Description of envisioned System Improvements for Machine Type Communication, use cases..... | 24 | +| 5.1 Key Issue - Group Based Optimization..... | 24 | +| 5.1.1 Use case description..... | 24 | +| 5.1.2 Required Functionality..... | 24 | +| 5.1.3 Evaluation..... | 24 | +| 5.2 Key Issue - MTC Devices communicating with one or more MTC Servers..... | 24 | +| 5.2.1 Use case description..... | 24 | +| 5.2.2 Required Functionality..... | 25 | +| 5.3 Key Issue - IP Addressing..... | 25 | +| 5.3.1 Use case description..... | 25 | +| 5.3.2 Required Functionality..... | 26 | +| 5.3.3 Evaluation..... | 26 | +| 5.4 Key Issue - Small Data Transmission..... | 29 | +| 5.4.1 Use case description..... | 29 | +| 5.4.2 Required Functionality..... | 29 | +| 5.4.3 Evaluation..... | 30 | +| 5.5 Void..... | 30 | +| 5.6 Key Issue - Low Mobility..... | 30 | +| 5.6.1 Use case description..... | 30 | +| 5.6.2 Required Functionality..... | 30 | +| 5.6.3 Evaluation..... | 30 | +| 5.7 Key Issue - MTC Subscriptions..... | 30 | + +| | | | +|------------|---------------------------------------------------------------------------|----| +| 5.7.1 | Use case description..... | 30 | +| 5.7.2 | Required Functionality..... | 30 | +| 5.8 | Key Issue - MTC Device Trigger..... | 31 | +| 5.8.1 | Use case description..... | 31 | +| 5.8.2 | Required Functionality..... | 32 | +| 5.8.3 | Evaluation..... | 34 | +| 5.8.3.1 | Comparison of the MTC Device Trigger solutions..... | 34 | +| 5.8.3.2 | Delivery of device trigger information from 3GPP system to UE..... | 35 | +| 5.8.3.3 | Submission of device trigger requests from MTC server to 3GPP system..... | 35 | +| 5.8.3.4 | 3GPP system internal handling of device triggers..... | 35 | +| 5.9 | Key Issue –Time Controlled..... | 36 | +| 5.9.1 | Use case description..... | 36 | +| 5.9.2 | Required Functionality..... | 37 | +| 5.9.3 | Evaluation..... | 37 | +| 5.10 | Key Issue - MTC Monitoring..... | 37 | +| 5.10.1 | Use case description..... | 37 | +| 5.10.2 | Required Functionality..... | 37 | +| 5.11 | Key Issue - Decoupling MTC Server from 3GPP Architecture..... | 38 | +| 5.11.1 | Use Case Description..... | 38 | +| 5.11.2 | Required Functionality..... | 38 | +| 5.12 | Key Issue - Signalling Congestion Control..... | 38 | +| 5.12.1 | Use Case Description..... | 38 | +| 5.12.2 | Required Functionality..... | 39 | +| 5.12.3 | Evaluation..... | 40 | +| 5.12.3.1 | General..... | 40 | +| 5.12.3.2 | Evaluation for Congestion Control..... | 40 | +| 5.12.3.3 | Evaluation for Overload Control..... | 40 | +| 5.12.3.4 | Comparison of Each Solution..... | 41 | +| 5.13 | Key Issue - MTC Identifiers..... | 43 | +| 5.13.1 | Use Case Description..... | 43 | +| 5.13.2 | Required Functionality..... | 43 | +| 5.13.3 | Evaluation..... | 44 | +| 5.14 | Key Issue - Potential overload issues caused by Roaming MTC devices..... | 44 | +| 5.14.1 | Use Case Description..... | 44 | +| 5.14.1.1 | What is the likelihood of M2M devices being roamers?..... | 44 | +| 5.14.1.2 | What are the consequences if most M2M devices are roaming?..... | 44 | +| 5.14.1.2.1 | Commercial arrangements..... | 44 | +| 5.14.1.2.2 | Devices that only power-up/attach when they need to do something..... | 45 | +| 5.14.1.2.3 | Failure of "M2M partner" network..... | 45 | +| 5.14.2 | Required Functionality..... | 45 | +| 5.14.3 | Evaluation..... | 46 | +| 5.14.3.1 | Evaluation for M2M "access class barring" functionality..... | 46 | +| 5.15 | Key Issue - Low Power Consumption..... | 46 | +| 5.15.1 | Use case description..... | 46 | +| 5.15.2 | Required Functionality..... | 46 | +| 5.15.3 | Evaluation..... | 46 | +| 6 | Solutions..... | 46 | +| 6.1 | Solution - FQDN Identifier Solution..... | 47 | +| 6.1.1 | Problem Solved / Gains Provided..... | 47 | +| 6.1.2 | General..... | 47 | +| 6.1.3 | Impacts on existing nodes or functionality..... | 48 | +| 6.1.4 | Evaluation..... | 48 | +| 6.2 | Solution - Transfer of device trigger or data via SMS..... | 49 | +| 6.2.1 | Problem Solved / Gains Provided..... | 49 | +| 6.2.2 | General..... | 49 | +| 6.2.3 | Impacts on existing nodes or functionality..... | 49 | +| 6.2.4 | Evaluation..... | 49 | +| 6.3 | Solution - Paging within configured area..... | 49 | +| 6.3.1 | Problem Solved / Gains Provided..... | 49 | +| 6.3.2 | General..... | 49 | +| 6.3.3 | Impacts on existing nodes or functionality..... | 50 | + +| | | | +|--------|-----------------------------------------------------------------------------------------------------------|----| +| 6.3.4 | Evaluation..... | 50 | +| 6.4 | Solution - Paging stepwise..... | 50 | +| 6.4.1 | Problem Solved / Gains Provided..... | 50 | +| 6.4.2 | General..... | 50 | +| 6.4.3 | Impacts on existing nodes or functionality..... | 50 | +| 6.4.4 | Evaluation..... | 50 | +| 6.5 | Solution - Paging within reported area..... | 50 | +| 6.5.1 | Problem Solved / Gains Provided..... | 50 | +| 6.5.2 | General..... | 50 | +| 6.5.3 | Impacts on existing nodes or functionality..... | 50 | +| 6.5.4 | Evaluation..... | 50 | +| 6.6 | Solution - Triggering of non-attached MTC Devices based on location information provided by MTC User..... | 51 | +| 6.6.1 | Problem Solved / Gains Provided..... | 51 | +| 6.6.2 | General..... | 51 | +| 6.6.3 | Impacts on existing nodes or functionality..... | 51 | +| 6.6.4 | Evaluation..... | 51 | +| 6.7 | Solution – Network access control by the PLMN..... | 51 | +| 6.7.1 | Problem Solved / Gains Provided..... | 51 | +| 6.7.2 | General..... | 51 | +| 6.7.3 | Impacts on existing nodes or functionality..... | 52 | +| 6.7.4 | Evaluation..... | 53 | +| 6.8 | Solution - Introduction of a 3GPP MTC Service Abstraction Layer..... | 53 | +| 6.8.1 | Problem Solved / Gains Provided..... | 53 | +| 6.8.2 | General..... | 53 | +| 6.8.3 | Impacts on existing nodes or functionality..... | 54 | +| 6.8.4 | Evaluation..... | 54 | +| 6.9 | Solution - MTC Monitoring - General..... | 55 | +| 6.9.1 | Problem Solved / Gains Provided..... | 55 | +| 6.9.2 | General..... | 55 | +| 6.10 | Solution – SGSN/MME based detection..... | 56 | +| 6.10.1 | Problem Solved / Gains Provided..... | 56 | +| 6.10.2 | General..... | 56 | +| 6.10.3 | Impacts on existing nodes or functionality..... | 56 | +| 6.10.4 | Evaluation..... | 56 | +| 6.11 | Solution - HLR/HSS based detection..... | 56 | +| 6.11.1 | Problem Solved / Gains Provided..... | 56 | +| 6.11.2 | General..... | 57 | +| 6.11.3 | Impacts on existing nodes or functionality..... | 57 | +| 6.11.4 | Evaluation..... | 57 | +| 6.12 | Solution - GGSN/P-GW based detection..... | 58 | +| 6.12.1 | Problem Solved / Gains Provided..... | 58 | +| 6.12.2 | General..... | 58 | +| 6.12.3 | Impacts on existing nodes or functionality..... | 58 | +| 6.12.4 | Evaluation..... | 58 | +| 6.13 | Solution - Reporting by SGSN/MME..... | 59 | +| 6.13.1 | Problem Solved / Gains Provided..... | 59 | +| 6.13.2 | General..... | 59 | +| 6.13.3 | Impacts on existing nodes or functionality..... | 59 | +| 6.13.4 | Evaluation..... | 59 | +| 6.14 | Solution - Reporting by HLR/HSS..... | 59 | +| 6.14.1 | Problem Solved / Gains Provided..... | 59 | +| 6.14.2 | General..... | 59 | +| 6.14.3 | Impacts on existing nodes or functionality..... | 60 | +| 6.14.4 | Evaluation..... | 60 | +| 6.15 | Solution - Reporting by GGSN/P-GW..... | 60 | +| 6.15.1 | Problem Solved / Gains Provided..... | 60 | +| 6.15.2 | General..... | 60 | +| 6.15.3 | Impacts on existing nodes or functionality..... | 60 | +| 6.15.4 | Evaluation..... | 61 | +| 6.16 | Solution - Reporting by PCRF..... | 61 | + +| | | | +|--------|-------------------------------------------------------------------------------------|----| +| 6.16.1 | Problem Solved / Gains Provided..... | 61 | +| 6.16.2 | General..... | 61 | +| 6.16.3 | Impacts on existing nodes or functionality..... | 61 | +| 6.16.4 | Evaluation..... | 61 | +| 6.17 | Solution – Allowed Time Period after TAU/RAU..... | 61 | +| 6.17.1 | Problem Solved / Gains Provided..... | 61 | +| 6.17.2 | General..... | 62 | +| 6.17.3 | Impacts on existing nodes or functionality..... | 62 | +| 6.17.4 | Evaluation..... | 62 | +| 6.18 | Solution - MT Communication with NATTT..... | 62 | +| 6.18.1 | Problem Solved / Gains Provided..... | 62 | +| 6.18.2 | General..... | 62 | +| 6.18.3 | Impacts on existing nodes or functionality..... | 64 | +| 6.18.4 | Evaluation..... | 64 | +| 6.19 | Solution - MT Communication with Micro Port Forwarding..... | 65 | +| 6.19.1 | Problem Solved / Gains Provided..... | 65 | +| 6.19.2 | General..... | 65 | +| 6.19.3 | Impacts on existing nodes or functionality..... | 68 | +| 6.19.4 | Evaluation..... | 68 | +| 6.20 | Solution - Optimizing periodic LAU/RAU/TAU Signalling..... | 69 | +| 6.20.1 | Problem Solved / Gains Provided..... | 69 | +| 6.20.2 | General..... | 69 | +| 6.20.3 | Impacts on existing nodes or functionality..... | 70 | +| 6.20.4 | Evaluation..... | 70 | +| 6.21 | Solution - Randomized triggering of time-controlled MTC operations..... | 71 | +| 6.21.1 | Problem Solved / Gains Provided..... | 71 | +| 6.21.2 | General..... | 71 | +| 6.21.3 | Impacts on existing nodes or functionality..... | 72 | +| 6.21.4 | Evaluation..... | 72 | +| 6.22 | Solution – Rejecting connection requests by the SGSN/MME..... | 72 | +| 6.22.1 | Problem Solved / Gains Provided..... | 72 | +| 6.22.2 | General..... | 72 | +| | Providing a back-off time and a reject indication to the MTC Device..... | 73 | +| 6.22.3 | Impacts on existing nodes or functionality..... | 73 | +| 6.22.4 | Evaluation..... | 75 | +| 6.23 | Solution – Low Priority Access Indication..... | 75 | +| 6.23.1 | Problem Solved / Gains Provided..... | 75 | +| 6.23.2 | General..... | 75 | +| 6.23.3 | Impacts on existing nodes or functionality..... | 76 | +| 6.23.4 | Evaluation..... | 77 | +| 6.24 | Solution - Directly Reporting to MTC Server from CN entity..... | 78 | +| 6.24.1 | Problem Solved / Gains Provided..... | 78 | +| 6.24.2 | General..... | 78 | +| 6.24.3 | Impacts on existing nodes or functionality..... | 79 | +| 6.24.4 | Evaluation..... | 79 | +| 6.25 | Solution - Reporting to MTC Server through the intermediate node..... | 79 | +| 6.25.1 | Problem Solved / Gains Provided..... | 79 | +| 6.25.2 | General..... | 79 | +| 6.25.3 | Impacts on existing nodes or functionality..... | 80 | +| 6.25.4 | Evaluation..... | 80 | +| 6.26 | Solution – Rejecting RRC Connection and Channel Requests by the eNodeB/RNC/BSS..... | 80 | +| 6.26.1 | Problem Solved / Gains Provided..... | 80 | +| 6.26.2 | General..... | 80 | +| 6.26.3 | Impacts on existing nodes or functionality..... | 81 | +| 6.26.4 | Evaluation..... | 81 | +| 6.27 | Time Control Solution Summary..... | 83 | +| 6.28 | Solution - Access Control by RAN..... | 85 | +| 6.28.1 | Problem Solved / Gains Provided..... | 85 | +| 6.28.2 | General..... | 85 | +| 6.28.3 | Impacts on existing nodes or functionality..... | 86 | +| 6.28.4 | Evaluation..... | 88 | + +| | | | +|----------|---------------------------------------------------------------------------------------|-----| +| 6.29 | Solution – IP address assignment mechanisms..... | 90 | +| 6.29.1 | Problem Solved / Gains Provided..... | 90 | +| 6.29.2 | General approach based on existing standards..... | 90 | +| 6.29.3 | IP address assignment by the PDN of the MTC server..... | 91 | +| 6.29.4 | IP address assignment by the GGSN/P-GW..... | 91 | +| 6.29.5 | MTC Server located on Internet and public IP addresses for MTC devices..... | 92 | +| 6.29.6 | Impacts on existing nodes or functionality..... | 93 | +| 6.29.7 | Evaluation..... | 93 | +| 6.30 | Solution - MME/SGSN overload control by DL MTC traffic throttling..... | 93 | +| 6.30.1 | Problem Solved / Gains Provided..... | 93 | +| 6.30.2 | General..... | 94 | +| 6.30.3 | Impacts on existing nodes or functionality..... | 95 | +| 6.30.4 | Evaluation..... | 95 | +| 6.31 | Solution – Rejecting connection requests at partial signalling links..... | 95 | +| 6.31.1 | Problem Solved / Gains Provided..... | 95 | +| 6.31.2 | General..... | 95 | +| 6.31.3 | Impacts on existing nodes or functionality..... | 95 | +| 6.31.4 | Evaluation..... | 96 | +| 6.32 | Solution – Rejecting connection requests based on request types..... | 96 | +| 6.32.1 | Problem Solved / Gains Provided..... | 96 | +| 6.32.2 | General..... | 96 | +| 6.32.3 | Impacts on existing nodes or functionality..... | 97 | +| 6.32.4 | Evaluation..... | 97 | +| 6.33 | Solution – UE behaviour changes..... | 97 | +| 6.33.1 | Problem Solved / Gains Provided..... | 97 | +| 6.33.2 | General..... | 97 | +| 6.33.3 | Impacts on existing nodes or functionality..... | 98 | +| 6.33.4 | Evaluation..... | 98 | +| 6.34 | Solution – M2M device indication to network..... | 98 | +| 6.34.1 | Problem Solved / Gains Provided..... | 98 | +| 6.34.2 | General..... | 98 | +| 6.34.3 | Impacts on existing nodes or functionality..... | 98 | +| 6.34.4 | Evaluation..... | 98 | +| 6.35 | Solution - Overload control within an MTC access grant time interval..... | 98 | +| 6.35.1 | Problems solved / Gains provided..... | 98 | +| 6.35.2 | General..... | 98 | +| 6.35.3 | Impacts on existing nodes or functionality..... | 99 | +| 6.35.4 | Evaluation..... | 100 | +| 6.36 | Solution - Time controlled feature via Operator and MTC User Business Agreements..... | 100 | +| 6.36.1 | Problem Solved / Gains Provided..... | 100 | +| 6.36.2 | General..... | 100 | +| 6.36.3 | Impacts on existing nodes or functionality..... | 100 | +| 6.36.4 | Evaluation..... | 100 | +| 6.37 | Solution - Simple Subscription Control..... | 101 | +| 6.37.1 | Problem Solved / Gains Provided..... | 101 | +| 6.37.2 | General..... | 101 | +| 6.37.3 | Impacts on existing nodes or functionality..... | 101 | +| 6.37.4 | Evaluation..... | 101 | +| 6.38 | Solution – Device identifier used over MTC <sub>SP</sub> ..... | 102 | +| 6.38.1 | Problems solved / Gains provided..... | 102 | +| 6.38.2 | General..... | 102 | +| 6.38.3 | Impacts on existing nodes or functionality..... | 104 | +| 6.38.4 | Evaluation..... | 104 | +| 6.39 | Solution - Triggering MTC devices via HSS and NAS signalling..... | 104 | +| 6.39.1 | Problem Solved / Gains Provided..... | 104 | +| 6.39.2 | General..... | 104 | +| 6.39.2.1 | Overview..... | 104 | +| 6.39.2.2 | Detailed solution..... | 104 | +| 6.39.3 | Impacts on existing nodes or functionality..... | 107 | +| 6.39.4 | Evaluation..... | 107 | +| 6.40 | Solution - Information sent to trigger a UE used for MTC..... | 107 | + +| | | | +|----------|------------------------------------------------------------------------------------------------------------------|-----| +| 6.40.1 | Problem solved..... | 107 | +| 6.40.2 | Required Functionality..... | 107 | +| 6.41 | Solution - Triggering of attached MTC Devices by reusing Network Requested PDP Context Activation procedure..... | 107 | +| 6.41.1 | Problem Solved / Gains Provided..... | 107 | +| 6.41.2 | General..... | 108 | +| 6.41.3 | Impacts on existing nodes or functionality..... | 109 | +| 6.41.4 | Evaluation..... | 110 | +| 6.42 | Solution - Triggering of attached MTC Device via Pre rel-11 SMS..... | 110 | +| 6.42.1 | Problem Solved / Gains Provided..... | 110 | +| 6.42.2 | General..... | 110 | +| 6.42.3 | Impacts on existing nodes or functionality..... | 110 | +| 6.42.4 | Evaluation..... | 110 | +| 6.43 | Solution - Triggering of attached MTC Device via intermediate node..... | 110 | +| 6.43.1 | Problem Solved / Gains Provided..... | 110 | +| 6.43.2 | General..... | 110 | +| 6.43.3 | Impacts on existing nodes or functionality..... | 111 | +| 6.43.4 | Evaluation..... | 111 | +| 6.44 | Solution – Device Triggering reuse of MT SMS..... | 111 | +| 6.44.1 | Problems solved / Gains provided..... | 111 | +| 6.44.2 | General..... | 111 | +| 6.44.3 | Impacts on existing nodes or functionality..... | 114 | +| 6.44.3.1 | Impacts for MT-SMS device trigger - MSISDN based..... | 114 | +| 6.44.3.2 | Impacts for MT-SMS and MSISDN-less based..... | 114 | +| 6.44.3.3 | Properties of the solution..... | 116 | +| 6.44.4 | Evaluation..... | 116 | +| 6.45 | Solution – Device trigger gateway solution..... | 117 | +| 6.45.1 | Problem Solved / Gains Provided..... | 117 | +| 6.45.2 | General..... | 117 | +| 6.45.3 | Submission of device trigger request from MTC Server to HPLMN..... | 117 | +| 6.45.4 | HPLMN internal handling of device triggers..... | 118 | +| 6.45.5 | Delivery of device trigger from HPLMN to UE..... | 119 | +| 6.45.6 | DT functionality..... | 119 | +| 6.45.7 | Information flows..... | 120 | +| 6.45.8 | Impacts on existing nodes or functionality..... | 121 | +| 6.45.9 | Evaluation..... | 121 | +| 6.46 | Solution - Address resolution via MTC-IWF..... | 121 | +| 6.46.1 | Problem Solved / Gains Provided..... | 121 | +| 6.46.2 | General..... | 121 | +| 6.46.3 | UP MT communications UE current IP address resolution..... | 122 | +| 6.46.4 | CP device triggering assigned MTC-IWF address resolution..... | 123 | +| 6.46.5 | Impacts on existing nodes or functionality..... | 123 | +| 6.46.4 | Evaluation..... | 123 | +| 6.47 | Solution – UE without unique MSISDN using ICCID..... | 124 | +| 6.47.1 | Problem Solved / Gains Provided..... | 124 | +| 6.47.2 | General..... | 124 | +| 6.47.3 | Impacts on existing nodes or functionality..... | 124 | +| 6.47.4 | Evaluation..... | 124 | +| 6.48 | Solution - Transfer data via SMS for MTC Devices sharing one MSISDN..... | 125 | +| 6.48.1 | Problem Solved / Gains Provided..... | 125 | +| 6.48.2 | General..... | 125 | +| 6.48.3 | Impacts on existing nodes or functionality..... | 126 | +| 6.48.4 | Evaluation..... | 126 | +| 6.49 | Solution - UE configured to build its IPv6 address with the provided interface identifier..... | 126 | +| 6.49.1 | Problem Solved / Gains Provided..... | 126 | +| 6.49.2 | General..... | 126 | +| 6.50 | Solution - Use of FQDN Identifier with Dynamic DNS Update..... | 127 | +| 6.50.1 | Problem Solved / Gains Provided..... | 127 | +| 6.50.2 | General..... | 127 | +| 6.51 | Solution- MT Communication with MTCsp/MTCsms signalling..... | 128 | +| 6.51.1 | Problem Solved/ Gains Provided..... | 128 | + +| | | | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 6.51.2 | General..... | 128 | +| 6.51.3 | Impacts on existing nodes or functionality..... | 129 | +| 6.51.4 | Evaluation..... | 129 | +| 6.52 | Solution - Transfer of device trigger or data via optimised SMS..... | 129 | +| 6.52.1 | Problem Solved / Gains Provided..... | 129 | +| 6.52.2 | General..... | 129 | +| 6.52.2.1 | Overview..... | 129 | +| 6.52.2.2 | Removal of CP protocol layer..... | 130 | +| 6.52.2.3 | Flexible deployment of MSC functionality for SMS over SGs..... | 130 | +| 6.52.2.4 | Stateless SMS IWF..... | 132 | +| 6.52.2.5 | Evolution of the signalling interfaces between MME and HSS/SMSC..... | 133 | +| 6.52.2.6 | Use of pre-established NAS security context to transfer the SMS PDUs as NAS signalling without establishing RRC security..... | 133 | +| 6.52.2.7 | Transfer of Device Trigger as MT SMS or NAS payload without U-plane bearer establishment in E-UTRAN..... | 134 | +| 6.52.3 | Impacts on existing nodes or functionality..... | 135 | +| 6.52.4 | Evaluation..... | 135 | +| 6.53 | Solution - Small Data Transfer (E-UTRAN): Use of pre-established NAS security context to transfer the IP packet as NAS signalling without establishing RRC security..... | 135 | +| 6.53.1 | Problem Solved / Gains Provided..... | 135 | +| 6.53.2 | General..... | 135 | +| 6.53.3 | Impacts on existing nodes or functionality..... | 138 | +| 6.53.4 | Evaluation..... | 138 | +| 6.54 | Solution - NAT Traversal using controlled NAT..... | 138 | +| 6.54.1 | Problem Solved / Gains Provided..... | 138 | +| 6.54.2 | General..... | 138 | +| 6.54.3 | Impacts on existing nodes or functionality..... | 139 | +| 6.54.4 | Evaluation..... | 139 | +| 6.55 | Solution - NAT Traversal using Non-Managed-NAT..... | 140 | +| 6.55.1 | Problem Solved/ Gains Provided..... | 140 | +| 6.55.2 | General..... | 140 | +| 6.55.3 | Non-Managed-NAT for MTC..... | 140 | +| 6.55.3 | Impacts on existing nodes or functionality..... | 141 | +| 6.55.4 | Evaluation..... | 141 | +| 6.56 | Solution – SMS Transfer by SGSN for PS-only..... | 141 | +| 6.56.1 | Problem Solved / Gains Provided..... | 141 | +| 6.56.2 | General..... | 141 | +| 6.56.3 | Impacts on existing nodes or functionality..... | 142 | +| 6.56.4 | Evaluation..... | 142 | +| 6.57 | Solution - Optimised SMS over SGs architecture..... | 142 | +| 6.57.1 | Problem Solved / Gains Provided..... | 142 | +| 6.57.2 | General..... | 143 | +| 6.57.3 | Impacts on existing nodes or functionality..... | 143 | +| 6.57.4 | Evaluation..... | 143 | +| 6.58 | Solution – Triggering using Cell Broadcast..... | 144 | +| 6.58.1 | Problem Solved / Gains Provided..... | 144 | +| 6.58.2 | General..... | 144 | +| 6.58.3 | Impacts on existing nodes or functionality..... | 145 | +| 6.58.4 | Evaluation..... | 145 | +| 6.59 | Solution – Load/Overload Control via MTC-IWF..... | 146 | +| 6.59.1 | Problem Solved / Gains Provided..... | 146 | +| 6.59.2 | General..... | 146 | +| 6.59.3 | MTC-IWF Load Control to MTC servers..... | 146 | +| 6.59.4 | MME/SGSN Overload Control of Trigger Requests to MTC-IWF(s)..... | 147 | +| 6.59.5 | Impacts on existing nodes or functionality..... | 148 | +| 6.59.6 | Evaluation..... | 148 | +| 6.60 | Solution - Device trigger using MT-SMS & direct SGSN/MME delivery..... | 149 | +| 6.60.1 | Problem Solved / Gains Provided..... | 149 | +| 6.60.2 | General..... | 149 | +| 6.60.3 | Impacts on existing nodes or functionality..... | 149 | +| 6.60.4 | Evaluation..... | 150 | + +| | | | +|-----------------|-------------------------------------------------------------------------|------------| +| 6.61 | Solution – Native SMS over NAS for PS-only..... | 150 | +| 6.61.1 | Problem Solved / Gains Provided..... | 150 | +| 6.61.2 | General..... | 150 | +| 6.61.3 | Impacts on existing nodes or functionality..... | 150 | +| 6.61.4 | Evaluation..... | 151 | +| 6.62 | Solution - User plane based device Triggering..... | 151 | +| 6.62.1 | Problem Solved / Gains Provided..... | 151 | +| 6.62.2 | High level information flow for Device Triggering using user plane..... | 151 | +| 6.62.3 | Proposals for MTC-IWF to determine IP address of MTC device..... | 152 | +| 6.62.3.1 | Alternate 1 - Explicit Registration based..... | 152 | +| 6.62.3.2 | Alternate 2 - Mapping Table based..... | 152 | +| 6.62.3.2.1 | MME/HSS based mapping table update..... | 152 | +| 6.62.3.2.2 | PGW/GGSN based mapping table update..... | 153 | +| 6.62.4 | IMS-based trigger delivery over user plane..... | 153 | +| 7 | Conclusions..... | 154 | +| 7.1 | Interim conclusions for release 10 specification work..... | 154 | +| 7.2 | Interim conclusions for release 11 specification work..... | 154 | +| 7.2.1 | IP Addressing - Key Issue 5.3..... | 154 | +| 7.2.2 | MTC Device Triggering - Key Issue 5.8..... | 155 | +| 7.2.3 | MTC Identifiers - Key Issue 5.13..... | 157 | +| 7.2.4 | MTC Feature Control - Key Issue 5.7..... | 157 | +| 7.2.5 | MTC Feature - Packet Switched only..... | 157 | +| 8 | Impacts to normative specifications..... | 158 | +| 8.1 | Related to Interim conclusions for release 10 specification work..... | 158 | +| 8.2 | Related to Interim conclusions for release 11 specification work..... | 158 | +| 8.2.1 | IP addressing..... | 158 | +| 8.2.1.1 | Guiding Principles..... | 158 | +| 8.2.1.2 | Documentation approach..... | 158 | +| 8.2.2 | MTC Identifiers..... | 159 | +| 8.2.2.1 | Guiding Principles..... | 159 | +| 8.2.2.2 | Documentation approach..... | 159 | +| <b>Annex A:</b> | <b>Stage 2 PS Dependencies on MSISDN-based Subscriptions.....</b> | <b>160</b> | +| A.1 | General Considerations..... | 160 | +| A.2 | PS stage 2 MSISDN dependencies..... | 160 | +| A.2.1 | General network architecture..... | 160 | +| A.2.2 | GPRS..... | 160 | +| A.2.3 | EPS..... | 160 | +| A.2.4 | WLAN..... | 161 | +| A.2.5 | SMS..... | 161 | +| A.2.6 | IMS..... | 162 | +| A.2.7 | PCC..... | 162 | +| A.2.8 | LCS..... | 162 | +| A.2.9 | SIPTO..... | 162 | +| A.2.10 | CAMEL..... | 163 | +| A.2.11 | Other services..... | 163 | +| A.3 | Impact of MSISDN-less subscriptions for PS only MS/UEs..... | 164 | +| Annex B: | Change history..... | 165 | + +--- + +## Foreword + +This Technical Report has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +This Technical Report studies and evaluates architectural aspects of the System Improvements for Machine Type Communications requirements specified in TS 22.368 [2]. + +Specifically, the following system improvements are considered: + +- Architectural enhancements to support a large number of Machine-Type Communication (MTC) devices in the network; +- Architectural enhancements to fulfil MTC service requirements; +- Support combinations of architectural enhancements for MTC, though not all combinations may be possible. + +The end-to-end aspects of communication between MTC devices and MTC servers (which can be located outside or inside the network operator's domain) are out of the scope of this study. However, the transport services for MTC as provided by the 3GPP system and the related optimizations are considered in this study. In addition, the aspects needed to ensure that MTC devices and/or MTC servers and/or MTC applications do not cause peak loads of short duration (e.g. a "busy minute" rather than a "busy hour") are within the scope of this TR. + +Even though some provided solutions may be beneficial for communications from a MTC Device towards another MTC Device, this particular type communication has not been explicitly considered in this Technical Report. + +This Technical Report analyzes architectural aspects to achieve these objectives and to gather technical content until it can be included in the relevant technical specifications. + +NOTE: Some aspects in this feasibility study have led into normative specification in TS 23.682 [20], TS 23.060 [21], TS 23.401 [5], TS 23.221 [22] and TS 23.272 [23]. The text of the present document was not updated to align with normative specifications. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.368: "Service Requirements for Machine-Type Communications". +- [3] NAT Traversal through Tunnelling (NATTT) available at: +<http://www.cs.arizona.edu/~bzhang/nat/nattt.htm> +- [4] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based services and Packet Data Networks (PDN)". +- [5] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [6] 3GPP TS 23.040: "Technical Realization of the Short Message Service (SMS)". +- [7] ITU-T Recommendation E.118: "Operation, numbering, routing and mobile service – International operation – General provisions concerning Administrations". +- [8] ETSI TS 102 221: "UICC-Terminal interface; Physical and logical characteristics". + +- [9] 3GPP TS 23.142: "Value-added Services for SMS (VAS4SMS)". +- [10] Void. +- [11] 3GPP TS 23.251: "Network sharing; Architecture and functional description". +- [12] 3GPP TS 23.003: "Numbering, Addressing and Identification". +- [13] 3GPP TS 29.303: "Domain Name System Procedures; Stage 3". +- [14] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [15] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2". +- [16] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [17] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [18] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [19] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [20] 3GPP TS 23.682: "Architecture Enhancements to facilitate communications with Packet Data Networks and Applications". +- [21] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [22] 3GPP TS 23.221: "Architectural requirements". +- [23] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2". + +--- + +## 3 Definitions and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 22.368 [2], and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**External Identifier:** Identifier used from outside the 3GPP system (e.g. at the MTCsp interface), to refer to a UE using a subscription (or the subscription itself e.g. when UE is not registered). + +**Internal Identifier:** Identifier used within the 3GPP system to uniquely identify a UE using a subscription (or the subscription itself e.g. when the UE is not registered). In Rel-11, IMSI is the internal identifier in the 3GPP network for mapping to/from an external identifier. + +### 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]. + +| | | +|-----|-----------------------------| +| MTC | Machine Type Communications | +| M2M | Machine-to-Machine | + +## 4 Architectural Considerations + +### 4.1 Architectural requirements + +**Editor's note:** Contributions to this clause should follow after agreements are achieved in the Required Functionality clauses of individual Key Issues. + +- 1) The 3GPP Core Network can communicate with the MTC Server. An intermediary entity may be used for the control plane communication for topology hiding or protocol translation purposes. Any intermediary entity for the user plane communication is out of scope of 3GPP standardization. +- 2) Both mobile terminated and mobile originated communication shall be supported. To initiate mobile terminated communication, an MTC Server shall be able to uniquely identify an MTC Device. + +**Editor's note:** Unique identification of an MTC Device when the UE comprises multiple TEs may imply further requirements. + +- 3) The mobile network shall provide security mechanisms that can be used to: + +- ensure that an MTC Server can only communicate with certain UEs used for MTC; + +**NOTE:** This requirement does not imply that it applies to all MTC Server communication to UEs used for MTC. Some scenarios allowing for less restricted communication have been considered. + +**Editor's note:** The association of an MTC Server to certain UEs used for MTC for means of restricting communication (e.g. between an MTC User and the MTC Subscriber) is FFS. + +- ensure that only authorized PDN entities can communicate with the UEs used for MTC; +- ensure that a UE used for MTC can only communicate with the MTC Server(s) of its subscriber, and that communication with any other entity is not possible. + +The existing 3GPP security functions e.g. authentication and encryption shall be unaffected by the above security measures. + +- 4) It shall be possible to provide secure and encrypted communication between PLMN and MTC Server. +- 5) The reference points between the MTC Server and the PLMN shall enable message exchange to support the following services: + - a. Device Triggering + - b. ... +- 6) Architectural enhancements for MTC shall be designed to work in network sharing environments for all sharing configurations described in TS 23.251 [11]. + +### 4.1A. Architecture Principles + +**Editor's note:** This clause captures principles that can be agreed in discussion of architecture. Once agreed, these principles will guide further work in the TR. + +- 1) Communication at the application level between the MTC Device and the MTC Application is out of scope of 3GPP standardization. + +## 4.2 Architecture Model + +Different models are foreseen for machine type of traffic in what relates to the communication between the MTC Application and the 3GPP network. In a so called Direct Model, the MTC Application communicates with the UE for MTC directly as an over-the-top application on 3GPP network. This is shown as Figure 4.2-1(A). + +In a complementary way, several sub models are foreseen for an Indirect model, in which the MTC Application communicates with the UE for MTC by making use of additional services provided by the 3GPP network: + +1. The MTC Application would make use of an MTC Server, for additional value added services, provided by a third party Service Provider, that is, outside the 3GPP responsibility. The interface between the MTC server and the MTC application is totally out of the scope of 3GPP. The MTC server communicates with the 3GPP network by means of an interface or set of interfaces. This is shown as Figure 4.2-1(B). + +2. The MTC Application makes use of an MTC Server, again for additional value added services, provided by the 3GPP operator (which becomes a Service Provider). The interface between the MTC Server and the MTC application remains still out of the scope of 3GPP, whilst the communication between the MTC server and the 3GPP network becomes internal to the PLMN. This is shown as Figure 4.2-1(C), + +![Figure 4.2-1: MTC Application to UE for MTC Communication Models. The diagram illustrates three models: A) Direct Model, B) Indirect Model (Service Provider controlled), and C) Indirect Model (3GPP operator controlled).](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +The diagram shows three architectural models for MTC communication: + +- Model A (Direct Model):** Shows an 'MTC Application' above a '3GPP Boundary' line. Below the boundary is the '3GPP Network' and 'UE'. A dashed line connects the MTC Application directly to the 3GPP Network, and another dashed line connects the 3GPP Network to the UE. +- Model B (Indirect Model - Service Provider controlled):** Shows an 'MTC Application' connected via a double-headed arrow to an 'MTC Server'. Both are above the '3GPP Boundary'. The MTC Server is connected by a solid line to the '3GPP Network' below the boundary, which is then connected to the 'UE'. +- Model C (Indirect Model - 3GPP operator controlled):** Shows an 'MTC Application' above the '3GPP Boundary' connected via a double-headed arrow to an 'MTC Server' which is located *below* the boundary (internal to the network). The MTC Server is part of the '3GPP Network' oval, which connects to the 'UE'. + +Figure 4.2-1: MTC Application to UE for MTC Communication Models. The diagram illustrates three models: A) Direct Model, B) Indirect Model (Service Provider controlled), and C) Indirect Model (3GPP operator controlled). + +**Figure 4.2-1: MTC Application to UE for MTC Communication Models** + +- 3 Since the sub models in the indirect scenario are not mutually exclusive but just complementary, it is possible for a 3GPP operator to combine them for different applications. Next figure provides a high level model in which the 3GPP operator provides value added services to an MTC Application and in addition, offers telecom services to a third party Service provider. This is shown as Figure 4.2-2. + +The communication between the MTC server and 3GPP network is, as in bullet #1, within the scope of 3GPP, including when that communication becomes internal to the network, as in bullet #2. The communication between the MTC Application and the MTC Server is out of the scope of 3GPP. + +![Diagram illustrating Multiple MTC Applications using Diverse Communication Models. The diagram shows two MTC Applications at the top. The left application connects via a large double-headed arrow to an internal MTC Server within a 3GPP Network. The right application connects via a double-headed arrow to an external MTC Server. A vertical line labeled '3GPP Boundary' separates the external MTC Server from the internal one. The internal MTC Server is connected to a stack of User Equipment (UE) at the bottom. The label 'Indirect Model' is placed near the internal MTC Server and the UE.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Diagram illustrating Multiple MTC Applications using Diverse Communication Models. The diagram shows two MTC Applications at the top. The left application connects via a large double-headed arrow to an internal MTC Server within a 3GPP Network. The right application connects via a double-headed arrow to an external MTC Server. A vertical line labeled '3GPP Boundary' separates the external MTC Server from the internal one. The internal MTC Server is connected to a stack of User Equipment (UE) at the bottom. The label 'Indirect Model' is placed near the internal MTC Server and the UE. + +**Figure 4.2-2: Multiple MTC Applications using Diverse Communication Models** + +NOTE: The services provided by the MTC server within the 3GPP network maybe either: + +- different from those offered by the external MTC Server; +- the same as those in the external MTC Server; +- a subset/superset of those offered by the external MTC Server; + - The functionality provided by either MTC Server is out of the scope of this document. +- a subset/superset of those offered by the external MTC Server. + - The functionality provided by either MTC Server is out of the scope of this document. + +## 4.3 Architectural Reference Model for MTC + +The end-to-end application, between the UE used for Machine Type Communication (MTC) and the MTC Application, uses services provided by the 3GPP system, and optionally services provided by an MTC Server. The 3GPP system provides transport and communication services (including 3GPP bearer services, IMS and SMS) including various optimizations that can facilitate MTC. + +Figure 4.3-1 shows a UE used for MTC connecting to the 3GPP network (UTRAN, E-UTRAN, GERAN, I-WLAN, etc) via the Um/Uu/LTE-Uu interface. The architecture covers the various architectural models described in Clause 4.2. + +- Direct Model - Direct Communication provided by the 3GPP Operator: The MTC Application connects directly to the operator network without the use of any MTC Server; +- Indirect Model - MTC Service Provider controlled communication: The MTC Server is an entity outside of the operator domain. The MTCsp and MTCsms are external interfaces (i.e. to a third party M2M service provider); +- Indirect Model - 3GPP Operator controlled communication: The MTC Server is an entity inside the operator domain. The MTCsp and MTCsms are internal to the PLMN; +- Hybrid Model: The direct and indirect models are used simultaneously in the hybrid model e.g. connecting the user plane using the direct model and doing control plane signalling using the indirect model. + +**Editor's note:** Considerations for hybrid scenarios and for security and scalability for the direct model is FFS. + +![Figure 4.3-1: Non-Roaming Architecture for 3GPP Architecture for Machine-Type Communication. The diagram shows the network architecture for Machine-Type Communication (MTC) within a 3GPP network. On the left, a UE (User Equipment) containing an MTC Application is connected to a RAN (Radio Access Network). The RAN is connected to an SGSN/MME via the Um/Uu/LTE-Uu interface. The SGSN/MME is connected to an HLR/HSS via the Gr/S6a/S6d interface and to an MTC-IWF via the T5a/T5b interface. The MTC-IWF is connected to an SMS-SC/IP-SM-GW via the T4 interface and to an MTC Server via the MTCsp interface. The SMS-SC/IP-SM-GW is connected to Legacy SMS and IP SMS. The MTC Server is connected to a GGSN/S-GW/P-GW via the Gi/SGi interface. The GGSN/S-GW/P-GW is connected to the RAN via the Gn/Gp/S1-U interface and to the MTC Server via the Gi/SGi interface. The MTC Server is also connected to an MTC Application (MTC User) via an API. The diagram is divided into three models: Indirect Model (1), Direct Model (2), and Hybrid Model (1 + 2). The Indirect Model (1) shows the MTC Server connected to the GGSN/S-GW/P-GW. The Direct Model (2) shows the MTC Server connected to the RAN. The Hybrid Model (1 + 2) shows both connections. The diagram also indicates 'service provider controlled' and 'operator controlled' areas. A legend at the bottom left defines the control plane (dashed line) and user plane (solid line).](8307f6b04df072c9332f9987e034272c_img.jpg) + +Figure 4.3-1: Non-Roaming Architecture for 3GPP Architecture for Machine-Type Communication. The diagram shows the network architecture for Machine-Type Communication (MTC) within a 3GPP network. On the left, a UE (User Equipment) containing an MTC Application is connected to a RAN (Radio Access Network). The RAN is connected to an SGSN/MME via the Um/Uu/LTE-Uu interface. The SGSN/MME is connected to an HLR/HSS via the Gr/S6a/S6d interface and to an MTC-IWF via the T5a/T5b interface. The MTC-IWF is connected to an SMS-SC/IP-SM-GW via the T4 interface and to an MTC Server via the MTCsp interface. The SMS-SC/IP-SM-GW is connected to Legacy SMS and IP SMS. The MTC Server is connected to a GGSN/S-GW/P-GW via the Gi/SGi interface. The GGSN/S-GW/P-GW is connected to the RAN via the Gn/Gp/S1-U interface and to the MTC Server via the Gi/SGi interface. The MTC Server is also connected to an MTC Application (MTC User) via an API. The diagram is divided into three models: Indirect Model (1), Direct Model (2), and Hybrid Model (1 + 2). The Indirect Model (1) shows the MTC Server connected to the GGSN/S-GW/P-GW. The Direct Model (2) shows the MTC Server connected to the RAN. The Hybrid Model (1 + 2) shows both connections. The diagram also indicates 'service provider controlled' and 'operator controlled' areas. A legend at the bottom left defines the control plane (dashed line) and user plane (solid line). + +**Figure 4.3-1: Non-Roaming Architecture for 3GPP Architecture for Machine-Type Communication** + +The 'MTC Application' entities and the reference point API in the figure are outside of 3GPP scope. They are solely used as abstracts to show the end-to-end view for MTC and simplify mapping to MTC specifications of other standardization organizations. The MTC Application can be collocated with the MTC Server. + +The MTC Server is an entity which connects to the 3GPP network to communicate with UEs used for MTC and nodes in the PLMN. + +The 3GPP Architecture supports roaming scenarios in which the UE used for MTC obtains service by means of Um/Uu/LTE-Uu in a VPLMN. + +For the roaming UE in the visited network, the MTC-IWF shall have the connection with HSS/HLR and SMS-SC within the home network only and with serving SGSN/MME in the visited network. + +![Roaming Architecture for 3GPP Architecture for Machine-Type Communication for Home Routed scenario. This diagram shows the network architecture for Home Routed scenarios. On the left, a UE with an MTC Application connects to a RAN, which is part of a VPLMN. The RAN connects to an SGSN/MME. The SGSN/MME connects to a GGSN/P-GW in the HPLMN via an S8 interface. The GGSN/P-GW connects to an MTC Server via a Gi/SGi interface. The MTC Server connects to an MTC Application, which is accessed by an MTC User. The MTC Server is controlled by the service provider (Indirect Model 1) and the operator (Direct Model 2). The SGSN/MME also connects to an HLR/HSS via a Gr/S6a/S6d interface. The HLR/HSS connects to a CDF/CGF via an S6m interface. The CDF/CGF connects to an SMS-SC/IP-SM-GW via an Rf/Ga interface. The SMS-SC/IP-SM-GW receives Legacy SMS and IP SMS and connects to the MTC Server via an MTCsms interface. The MTC Server also connects to the MTC Application via an API. The diagram is divided into HPLMN and VPLMN by a dashed orange line. A vertical dashed line marks the 3GPP Boundary. Control plane is shown as dashed lines, and user plane as solid lines. A legend indicates: Indirect Model (1), Direct Model (2), and Hybrid Model (1 + 2).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Roaming Architecture for 3GPP Architecture for Machine-Type Communication for Home Routed scenario. This diagram shows the network architecture for Home Routed scenarios. On the left, a UE with an MTC Application connects to a RAN, which is part of a VPLMN. The RAN connects to an SGSN/MME. The SGSN/MME connects to a GGSN/P-GW in the HPLMN via an S8 interface. The GGSN/P-GW connects to an MTC Server via a Gi/SGi interface. The MTC Server connects to an MTC Application, which is accessed by an MTC User. The MTC Server is controlled by the service provider (Indirect Model 1) and the operator (Direct Model 2). The SGSN/MME also connects to an HLR/HSS via a Gr/S6a/S6d interface. The HLR/HSS connects to a CDF/CGF via an S6m interface. The CDF/CGF connects to an SMS-SC/IP-SM-GW via an Rf/Ga interface. The SMS-SC/IP-SM-GW receives Legacy SMS and IP SMS and connects to the MTC Server via an MTCsms interface. The MTC Server also connects to the MTC Application via an API. The diagram is divided into HPLMN and VPLMN by a dashed orange line. A vertical dashed line marks the 3GPP Boundary. Control plane is shown as dashed lines, and user plane as solid lines. A legend indicates: Indirect Model (1), Direct Model (2), and Hybrid Model (1 + 2). + +Figure 4.3-2: Roaming Architecture for 3GPP Architecture for Machine-Type Communication for Home Routed scenario + +![Roaming Architecture for 3GPP Architecture for Machine-Type Communication for Local Breakout scenario. This diagram shows the network architecture for Local Breakout scenarios. On the left, a UE with an MTC Application connects to a RAN, which is part of a VPLMN. The RAN connects to a GGSN/S-GW+P-GW in the VPLMN via a Gn/Gp/S1-U interface. The GGSN/S-GW+P-GW connects to an MTC Server via a Gi/SGi interface. The MTC Server connects to an MTC Application, which is accessed by an MTC User. The MTC Server is controlled by the service provider (Indirect Model 1) and the operator (Direct Model 2). The RAN also connects to an SGSN/MME, which connects to an HLR/HSS via a Gr/S6a/S6d interface. The HLR/HSS connects to a CDF/CGF via an S6m interface. The CDF/CGF connects to an SMS-SC/IP-SM-GW via an Rf/Ga interface. The SMS-SC/IP-SM-GW receives Legacy SMS and IP SMS and connects to the MTC Server via an MTCsms interface. The MTC Server also connects to the MTC Application via an API. The diagram is divided into HPLMN and VPLMN by a dashed orange line. A vertical dashed line marks the 3GPP Boundary. Control plane is shown as dashed lines, and user plane as solid lines. A legend indicates: Indirect Model (1), Direct Model (2), and Hybrid Model (1 + 2).](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +Roaming Architecture for 3GPP Architecture for Machine-Type Communication for Local Breakout scenario. This diagram shows the network architecture for Local Breakout scenarios. On the left, a UE with an MTC Application connects to a RAN, which is part of a VPLMN. The RAN connects to a GGSN/S-GW+P-GW in the VPLMN via a Gn/Gp/S1-U interface. The GGSN/S-GW+P-GW connects to an MTC Server via a Gi/SGi interface. The MTC Server connects to an MTC Application, which is accessed by an MTC User. The MTC Server is controlled by the service provider (Indirect Model 1) and the operator (Direct Model 2). The RAN also connects to an SGSN/MME, which connects to an HLR/HSS via a Gr/S6a/S6d interface. The HLR/HSS connects to a CDF/CGF via an S6m interface. The CDF/CGF connects to an SMS-SC/IP-SM-GW via an Rf/Ga interface. The SMS-SC/IP-SM-GW receives Legacy SMS and IP SMS and connects to the MTC Server via an MTCsms interface. The MTC Server also connects to the MTC Application via an API. The diagram is divided into HPLMN and VPLMN by a dashed orange line. A vertical dashed line marks the 3GPP Boundary. Control plane is shown as dashed lines, and user plane as solid lines. A legend indicates: Indirect Model (1), Direct Model (2), and Hybrid Model (1 + 2). + +Figure 4.3-3: Roaming Architecture for 3GPP Architecture for Machine-Type Communication for Local Breakout scenario + +Editor's note: Constraints on any MTC specific functionality for Local Breakout scenario is FFS and dependent on the solutions selected as part of the conclusions reached for SIMTC. + +**Editor's note:** Any additional entities or interfaces to be added to the MTC architecture figures are FFS and are dependent on the solutions selected as part of the conclusions reached for SIMTC. + +## 4.4 Network Elements + +### 4.4.1 General + +The following 3GPP network elements provide functionality to support the Indirect and Hybrid models of MTC. Additionally, IMS network elements may provide functionality to support the Indirect and Hybrid models of MTC. + +**NOTE:** As further development of the MTC architecture takes place as well as when additional MTC common functionality and features are addressed, further network elements may be defined. + +**Editor's note:** The final naming of any new entities added as part of the SIMTC work is FFS and dependent on the solutions selected as part of the conclusions reached for SIMTC. + +### 4.4.2 MTC-IWF + +To support the Indirect and Hybrid models of MTC, one or more instances of an MTC InterWorking Function (MTC-IWF) reside in the HPLMN. An MTC-IWF could be a standalone entity or a functional entity of another network element. The MTC-IWF hides the internal PLMN topology and relays or translates signaling protocols used over MTCsp to invoke specific functionality in the PLMN. + +The functionality of the MTC-IWF includes the following: + +- terminates the MTCsp, S6m, T5a, T5b, T4 and Rf/Ga reference points; +- may authenticate the MTC Server before communication establishment with the 3GPP network; +- may authorize control plane requests from an MTC Server; +- support the following control plane messaging from an MTC Server: + - receive device trigger request. +- support the following control plane messaging to an MTC Server: + - may report device trigger request acknowledgement; + - device trigger success/failure delivery report; + +**Editor's note:** Additional request messages between the MTC Server and the MTC-IWF are FFS and are dependent on the solutions selected as part of the conclusions reached for SIMTC. + +- an HSS resolution mechanism for use when multiple and separately addressable HSSs have been deployed by the network operator (see e.g. the SLF / Diameter Proxy agent specified in clause 5.8 TS 23.228 [14]); +- interrogation of the appropriate HLR/HSS, when needed, to map E.164 MSISDN or external identifier to the IMSI of the associated UE subscription and gather UE reachability information; + +**Editor's note:** The set of UE reachability information utilized for MTC-IWF for device triggering is FFS and is dependent on the solutions selected as part of the conclusions reached for SIMTC. + +- selection of the most efficient and effective device trigger delivery mechanism and shielding this detail from MTC Server based on; + - current reachability information of the UE; + - the possible device trigger delivery services supported by the HPLMN and, when roaming, VPLMN; + - the device trigger delivery mechanisms supported by the UE; + - any MNO device trigger delivery policies; and/or + - any information received from the MTC Server. + +- perform protocol translation, if necessary, and forwarding towards the relevant network entity (i.e. serving SGSN/MME or SMS-SC inside HPLMN domain) of a device trigger request to match the selected trigger delivery mechanism; +- generation of device trigger CDRs and forwarding to CDF/CGF over new instance of Rf/Ga; +- may support secure communications between the 3GPP network and the MTC server. + +**Editor's note:** Solutions for the security related functionality described in the three bullets above are in the scope of SA WG3. + +The characteristics of the MTC-IWF includes the following: + +- multiple MTC-IWFs can be used with a HPLMN; +- system shall be robust to single MTC-IWF failure. + +**Editor's note:** Additional MTC functionality in the MTC-IWF is FFS and dependent on the solutions selected as part of the conclusions reached for SIMTC. + +#### 4.4.3 HLR/HSS + +HLR and HSS specific functionality to support the Indirect and Hybrid models of MTC. + +Functionality for triggering includes the following: + +- termination of the S6m reference point where MTC-IWFs connect to the HLR/HSS; +- stores and provides the mapping/lookup of E.164 MSISDN or external identifier(s) to IMSI, routing information (i.e. serving MME/SGSN/MSC address), configuration information and UE reachability information to the MTC-IWF. + +**Editor's note:** The specific configuration information used by MTC-IWF for device triggering is FFS and dependent on the final conclusions reached for SIMTC. + +**Editor's note:** Specific MTC functionality in the HLR/HSS is FFS and dependent on the solutions selected as part of the conclusions reached for SIMTC. + +#### 4.4.4 GGSN/PGW + +GGSN and PGW specific functionality to support the Indirect and Hybrid models of MTC: + +**Editor's note:** Specific MTC functionality for the GGSN/PGW is FFS and dependent on the solutions selected as part of the conclusions reached for SIMTC. + +#### 4.4.5 SGSN/MME + +SGSN and MME specific functionality to support the Indirect and Hybrid models of MTC includes the following: + +- SGSN terminates the T5a reference point; +- MME terminates the T5b reference point; +- receives device trigger from MTC-IWF and optionally stores it; +- encapsulates device trigger delivery information in NAS message sent to the UE used for MTC. + +**Editor's note:** Additional MTC functionality for the SGSN/MME is FFS and dependent on the solutions selected as part of the conclusions reached for SIMTC. + +### 4.5 Reference Points + +#### 4.5.1 General + +The following 3GPP reference points support the Indirect and Hybrid models of MTC. + +NOTE: As further development of the MTC architecture takes place as well as when additional MTC common functionality and features are addressed, further reference points may be added. + +## 4.5.2 List of Reference Points + +The description of the MTC related reference points: + +| | | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| <b>MTCsms:</b> | It is the reference point an entity outside the 3GPP system uses to communicate with UEs used for MTC via SMS. | +| <b>MTCsp:</b> | It is the reference point an entity outside the 3GPP system uses to communicate with the MTC-IWF related control plane signalling. | +| <b>T4:</b> | Reference point used by MTC-IWF to route device trigger to the SMS-SC in the HPLMN. | +| <b>T5a:</b> | Reference point used between MTC-IWF and serving SGSN. | +| <b>T5b:</b> | Reference point used between MTC-IWF and serving MME. | +| <b>S6m:</b> | Reference point used by MTC-IWF to interrogate HSS/HLR for E.164 MSISDN or external identifier mapping to IMSI and gather UE reachability and configuration information. | + +Protocol assumption: + +- User plane communication with MTC Server, for Indirect and Hybrid models, and MTC Application, for Direct and Hybrid models, is achieved using existing protocols over Gi and SGi reference points. Existing control plane protocols over those reference points such as RADIUS/Diameter as specified in TS 29.061 [4] can also be supported towards the MTC Server. +- S6m may be based on pre-existing protocols e.g. RADIUS/Diameter/MAP. + +## 4.5.3 Reference Point Requirements + +### 4.5.3.1 MTCsp Reference Point Requirements + +The MTCsp reference point shall fulfil the following requirements: + +- connect a MTC-IWF to one or more MTC Servers; +- supports following services: + - reception of a device trigger request from MTC Server; + - may report to the MTC Server the acknowledgement of the device trigger request; and + - report to the MTC Server the success or failure of a device trigger request. + +**Editor's note:** Additional message exchange support is FFS and dependent on the solutions selected as part of the conclusions reached for SIMTC. + +- optional security and privacy protection for communication between the MTC-IWF and MTC Server. + +**Editor's note:** Solutions for the security related functionality described in the above bullet are in the scope of SA WG3. + +- Domain Name System procedures similar to what is specified in TS 29.303 [13] may be used by the MTC Server for lookup and selection of which specific MTC-IWF to be used. +- the protocol used on the MTCsp should support repetitions and switching MTC-IWF to ensure operation if one MTC-IWF fails; +- the protocol used on the MTCsp should allow the MTC-IWF and the MTC Server to detect duplicated trigger request and response messages. + +**Editor's note:** Additional MTC reference point requirements are FFS and dependent on the solutions selected as part of the conclusions reached for SIMTC. + +### 4.5.3.2 T4 Reference Point Requirements + +The T4 reference point shall fulfil the following requirements: + +- connect the MTC-IWF to SMS-SC inside HPLMN domain; +- transfer of device trigger, addressed by either an MSISDN or IMSI from MTC-IWF to SMS-SC inside HPLMN domain; +- report back to MTC-IWF the success or failure of delivering a device trigger to UE. + +**Editor's note:** Additional message exchange support is FFS and dependent on the solutions selected as part of the conclusions reached for SIMTC. + +#### 4.5.3.3 T5a/T5b Reference Point Requirements + +The T5a/T5b reference point shall fulfil the following requirements: + +- T5a connects the MTC-IWF to the serving SGSN; +- T5b connects the MTC-IWF to the serving MME. + +**Editor's note:** The specific requirements of these reference points are FFS and dependent on the solutions selected as part of the conclusions reached for SIMTC. + +#### 4.5.3.4 S6m Reference Point Requirements + +The S6m reference point shall fulfil the following requirements: + +- connect the MTC-IWF to HSS/HLR containing UE subscription information; +- support interrogation of HSS/HLR to map external identifier to IMSI and gather UE reachability and configuration information. + +**Editor's note:** Additional message exchange support is FFS and dependent on the solutions selected as part of the conclusions reached for SIMTC. + +### 4.6 High Level Functions + +#### 4.6.1 General + +The following functions describe the MTC functions performed within this system. + +**Editor's note:** The set of functions for MTC specific logic are FFS and are dependent on the solutions selected as part of the conclusions reached for SIMTC. + +**NOTE:** As further development of the MTC architecture takes place as well as when additional MTC common functionality and features are addressed, further functions may be defined. + +### 4.7 Authorization and Security + +Authorization and security measures may be applied to MTC reference points when communication extends beyond the boundary of the 3GPP system. + +**Editor's note:** The authorization and security measures needed are to be studied and specified in SA WG3. + +## 4.8 Protocol Stacks + +### 4.8.1 User plane + +![Figure 4.8.1-1: User plane stack for Machine Type Communication architecture. The diagram shows the protocol stack across five entities: UE, 3GPP PLMN (RAN+CN nodes), P-GW/GGSN, MTC Server, and Application Domain. The UE stack consists of MTC Application, IP, MT/L3, MT/L2, and MT/L1. The 3GPP PLMN stack consists of L3, L2, and L1. The P-GW/GGSN stack consists of IP, L3, L2, and L1. The MTC Server stack consists of MTC UP Function (optional, dashed box) and IP. The Application Domain stack consists of MTC Application and IP. Interfaces are labeled: Um/Uu/LTE-Uu between UE and 3GPP PLMN; S5/S8 Gn/Gp between 3GPP PLMN and P-GW/GGSN; MTCi between P-GW/GGSN and MTC Server; and API between MTC Server and Application Domain.](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +Figure 4.8.1-1: User plane stack for Machine Type Communication architecture. The diagram shows the protocol stack across five entities: UE, 3GPP PLMN (RAN+CN nodes), P-GW/GGSN, MTC Server, and Application Domain. The UE stack consists of MTC Application, IP, MT/L3, MT/L2, and MT/L1. The 3GPP PLMN stack consists of L3, L2, and L1. The P-GW/GGSN stack consists of IP, L3, L2, and L1. The MTC Server stack consists of MTC UP Function (optional, dashed box) and IP. The Application Domain stack consists of MTC Application and IP. Interfaces are labeled: Um/Uu/LTE-Uu between UE and 3GPP PLMN; S5/S8 Gn/Gp between 3GPP PLMN and P-GW/GGSN; MTCi between P-GW/GGSN and MTC Server; and API between MTC Server and Application Domain. + +**Figure 4.8.1-1: User plane stack for Machine Type Communication architecture** + +NOTE 1: Both transparent and non-transparent models as defined in TS 29.061 [4] can be used in the connectivity with the PDN where the MTC Server is. + +NOTE 2: The internal user plane architecture of the MTC Server is out of scope of 3GPP, the MTC UP Function is optional and is shown for illustration purposes in order to indicate that if such entity exists it resides in the domain of MTC Server. + +**Editor's note:** Impacts on the protocol stack in the internal nodes, when 3GPP UE is acting as a capillary network are FFS. + +### 4.8.2 Control plane + +#### 4.8.2.1 MTC Server-MTC-IWF MTCsp reference point + +![Figure 4.8.2.1-1: MTCsp protocol stack for Machine Type Communication architecture. The diagram shows the protocol stack across three entities: 3GPP PLMN Network elements, MTC-IWF, and MTC Server. The 3GPP PLMN stack consists of CP Protocol(s) and IP. The MTC-IWF stack consists of CP Protocol(s), MTCsp protocol(s), and IP. The MTC Server stack consists of MTCsp protocol(s) and IP. Interfaces are labeled: TBD between 3GPP PLMN and MTC-IWF; and MTCsp between MTC-IWF and MTC Server.](2119293733c74fc64de88aefd597f4bb_img.jpg) + +Figure 4.8.2.1-1: MTCsp protocol stack for Machine Type Communication architecture. The diagram shows the protocol stack across three entities: 3GPP PLMN Network elements, MTC-IWF, and MTC Server. The 3GPP PLMN stack consists of CP Protocol(s) and IP. The MTC-IWF stack consists of CP Protocol(s), MTCsp protocol(s), and IP. The MTC Server stack consists of MTCsp protocol(s) and IP. Interfaces are labeled: TBD between 3GPP PLMN and MTC-IWF; and MTCsp between MTC-IWF and MTC Server. + +**Figure 4.8.2.1-1: MTCsp protocol stack for Machine Type Communication architecture** + +NOTE 1: The MTCsp reference point can map to a protocol or number of protocols. + +**Editor's note:** Whether the interface between the MTC-IWF and the various 3GPP PLMN Network Elements can map to a number of protocols that may be same or different from the ones used in MTCsp is FFS. In this respect it is also FFS whether the MTC-IWF simply proxies requests from MTC Server or performs protocol translation. + +**Editor's note:** It is FFS whether the protocol stack of MTC-IWF remains the same in case of direct and indirect model as described in section 4.2. + +#### 4.8.2.2 MTC Server-SMS SC MTCsms reference point + +![Diagram of MTCsms protocol stack for Machine Type Communication architecture. It shows two stacked boxes representing the protocol stack for SMS-SC and MTC Server. Each box has 'MTCsms protocol' on top and 'IP' on the bottom. A dashed vertical line labeled 'MTCsms' separates the two stacks, indicating the reference point between the SMS-SC and the MTC Server.](4b87467ad9642943235f48f7d4b59449_img.jpg) + +Diagram of MTCsms protocol stack for Machine Type Communication architecture. It shows two stacked boxes representing the protocol stack for SMS-SC and MTC Server. Each box has 'MTCsms protocol' on top and 'IP' on the bottom. A dashed vertical line labeled 'MTCsms' separates the two stacks, indicating the reference point between the SMS-SC and the MTC Server. + +**Figure 4.8.2.2-1: MTCsms protocol stack for Machine Type Communication architecture** + +*Editor's note: It is FFS whether MTCsms is within the scope of 3GPP to specify.* + +## 5 Description of envisioned System Improvements for Machine Type Communication, use cases + +*Editor's note: This clause is intended to provide an overview of the alternative architecture fulfilling the requirements. Architecture solutions may apply to all or only some scenarios.* + +### 5.1 Key Issue - Group Based Optimization + +#### 5.1.1 Use case description + +*Editor's note: Expand upon the Service Description use case, including technical constraints and interpretations.* + +MTC Devices can be grouped together for the control, management or charging facilities etc. to meet the need of operators. This optimization may provide easier mode to control/update/charge the MTC devices, in a granularity of group, which may decrease the redundant signalling to avoid congestion. Also the network resource could be saved by using group based optimization when the number of MTC devices is large. The MTC devices within the same group can be in the same area and/or have the same MTC features attributed and/or belong to the same MTC user, which provides the flexibility to allocate a group. Moreover, each of the MTC devices is visible from the network perspective. + +*Editor's note: Group based optimization may include many optimizations. E.g. group based charging, group based signalling saving etc. It is not clear whether the solutions for these optimizations will be independent to each other or not. Whether this key issue will be split for evaluation is FFS.* + +#### 5.1.2 Required Functionality + +*Editor's note: Capture agreements on requirements for solving the key issue. This clause may be omitted if deemed unnecessary.* + +#### 5.1.3 Evaluation + +### 5.2 Key Issue - MTC Devices communicating with one or more MTC Servers + +#### 5.2.1 Use case description + +A MTC subscriber may have one or more MTC servers that communicate with the subscriber's MTC devices through the PLMN, which is optimized for machine-type communications. This key issue focuses on the common service requirements as specified in TS 22.368 [2] (e.g. addressing, identifiers, charging, security, etc.) for communication between MTC devices and MTC servers. + +## 5.2.2 Required Functionality + +To enable communication between MTC devices and MTC servers the following requirements shall be met: + +- It shall be possible to use one or more MTC servers for communicating with the MTC devices of a MTC subscriber. +- The PLMN shall allow transactions between an MTC device and an MTC server, either initiated by the MTC device or the MTC server. +- The PLMN shall be able to authenticate and authorize an MTC device before the device can communicate with an MTC server. +- It shall be possible to uniquely identify an MTC device. +- It shall be possible to uniquely identify an MTC Group i.e. a collection of MTC devices belonging to the same MTC subscriber. + +## 5.3 Key Issue - IP Addressing + +### 5.3.1 Use case description + +This key issue focuses on the common service requirements regarding IP addressing as specified in TS 22.368 [2] for communication between UEs used for MTC and MTC servers. The key issue relates to communication in the user plane i.e. the SGi/Gi reference point. + +For some MTC Applications, there is a need for the MTC Server to be the initiator of communications between the MTC Server and the UE used for MTC (e.g. due to the need for centralized control). + +It is expected in Rel-11 timeframe that the UE used for MTC and the MTC Server are assigned IPv6 addresses, and are thus in the same routable address space (see figure 5.3.1-1). For IPv6 addressing, the number of available IPv6 prefixes is abundant and thus there is no limitation for the IPv6 address space. + +When IPv4 addressing is used, the UE used for MTC is normally assigned a private IPv4 address due to the limitation of the public IPv4 address space. The MTC Server may reside in the same private IPv4 address space as the UE, or the MTC Server may reside in public IPv4 address space (see figure 5.3.1-2). In the former case, the UE used for MTC and the MTC Server are in the same routable address space. In the latter case, the UE used for MTC and the MTC Server are located in different non-routable address spaces. + +For both IPv4 and IPv6 addressing, the network may employ network topology security techniques that are intended to thwart unauthorized mobile terminated communications over a pre-existing globally routable IP connection. These security techniques are employed by the network operator to address various security goals. These security goals may include, but are not limited to, the desire for end-system privacy (e.g. to prevent device profiling), topology hiding (e.g. to mitigate scanning attacks) and to prevent unauthorized or unwanted communications with the UE used for MTC. + +**Editor's note:** The security solutions that may be needed for MTC are specified by SA WG3. + +The following scenarios must be specifically targeted for MTC addressing (the large ovals in the figures depict routable address spaces): + +- A. The MTC Server and the UE used for MTC are both located in the IPv6 address space. The UE used for MTC is assigned an IP address by the MNO. + +![Diagram illustrating the MTC Server and the UE used for MTC in the IPv6 address space. A large light blue oval labeled 'IPv6 Address Space' contains three smaller ovals: 'UE used for MTC' (purple), 'MNO' (blue), and 'MTC Server' (purple). Arrows indicate bidirectional communication flow between the UE and the MNO, and between the MNO and the MTC Server.](ced309874aec0546651b0976d5030a42_img.jpg) + +``` +graph LR; subgraph IPv6_Address_Space [IPv6 Address Space]; direction LR; UE[UE used for MTC] <--> MNO((MNO)); MNO <--> MTC[MTC Server]; end; +``` + +Diagram illustrating the MTC Server and the UE used for MTC in the IPv6 address space. A large light blue oval labeled 'IPv6 Address Space' contains three smaller ovals: 'UE used for MTC' (purple), 'MNO' (blue), and 'MTC Server' (purple). Arrows indicate bidirectional communication flow between the UE and the MNO, and between the MNO and the MTC Server. + +**Figure 5.3.1-1: MTC Server and the UE used for MTC in the IPv6 address space** + +NOTE 1: IPv6 based addressing for both UEs used for MTC and MTC Servers is considered the primary addressing solution and is preferred to ensure future proof and scalable deployments. + +NOTE 2: Middleboxes (e.g. firewalls) may be deployed by the MNO in an IPv6 address space to thwart unauthorized mobile terminated communication. + +- B. The MTC Server is located in a public IPv4 address space. The UE used for MTC is assigned a private IPv4 address from an address pool that is owned and managed by the MNO. +- C. The MTC Server is located in a private IPv4 address space. The UE used for MTC is assigned by the MNO a private IPv4 address corresponding to the same IPv4 address space the MTC Server belongs to. + +![Diagram illustrating two network scenarios for MTC. The left scenario shows a 'Private IPv4 Address Space' (blue oval) containing a 'UE used for MTC' (purple oval) and an 'MNO' (blue oval). The right scenario shows an 'IPv4 Address Space' (light blue oval) containing an 'MTC Server' (purple oval). Arrows indicate communication flow from the UE to the MNO and from the MTC Server to the MNO.](392a79ccd95e682ccd08f35ab2e64144_img.jpg) + +The diagram consists of two large ovals. The left oval is blue and labeled 'Private IPv4 Address Space'. Inside it, there are two smaller ovals: a purple one on the left labeled 'UE used for MTC' and a blue one on the right labeled 'MNO'. An arrow points from the purple oval to the blue oval. The right oval is light blue and labeled 'IPv4 Address Space'. Inside it, there is a purple oval labeled 'MTC Server'. An arrow points from this purple oval to the boundary of the light blue oval, which is adjacent to the blue oval's boundary. + +Diagram illustrating two network scenarios for MTC. The left scenario shows a 'Private IPv4 Address Space' (blue oval) containing a 'UE used for MTC' (purple oval) and an 'MNO' (blue oval). The right scenario shows an 'IPv4 Address Space' (light blue oval) containing an 'MTC Server' (purple oval). Arrows indicate communication flow from the UE to the MNO and from the MTC Server to the MNO. + +**Figure 5.3.1-2: MTC Server in a public or private IPv4 address space, UE used for MTC in a private IPv4 address space** + +NOTE 3: IPv4 based addressing solutions are considered transition solutions and are deprecated but not precluded. + +## 5.3.2 Required Functionality + +The system shall provide communication between the MTC Server and the UE used for MTC in the scenarios described in clause 5.3.1. For any used addressing mechanism: + +- The mechanism shall be scalable; +- The mechanism shall minimize the required configuration by the MNO and the MTC User; +- The mechanism shall minimize the required messaging transactions by the MTC Server to initiate MT communications; +- The mechanism shall minimize the messaging sent over the air to the UE used for MTC; +- The mechanism shall minimize any additional user plane latency; +- The mechanism shall minimize any additional security threats to the UE used for MTC. + +## 5.3.3 Evaluation + +IPv6 based addressing for both UEs used for MTC and MTC Servers is considered the primary addressing solution and is preferred to ensure future proof and scalable deployments. IPv4 based addressing solutions are considered transition solutions and are deprecated. + +Solutions for the Key issue IP addressing have been selected by: + +- 1) focusing on the most important and realistic deployment scenarios as per clause 5.3.1; +- 2) maximizing the reuse of existing 3GPP standards and minimizing the impact on the 3GPP System; +- 3) using IPv6 as the primary solution for IP addressing of UEs used for MTC. IPv4 based addressing is deprecated. + +NOTE: The scenario where the MTC Server and/or the end-to-end connection between the MTC Server and the mobile operator's domain are pure and only IPv4 is becoming unlikely, especially in Rel-11 timeframe. However an IPv6 capable MTC Server (i.e. dual-stack) in an IPv4 public address space can still be a valid scenario for some years. For such scenarios when there is no end-to-end IPv6 connectivity, well known transition mechanisms can be used. This is considered normal network design and should be transparent to 3GPP specifications. Therefore an MTC Server using IPv6 addressing connected to IPv6 MTC Devices over a public IPv4 address space is considered an IPv6 scenario (i.e. scenario A in clause 5.3.1). + +The use of dedicated APNs (clause 6.29.2) with tunnelling towards the MTC Server can be used in all the IP Addressing scenarios and satisfies the above required selection criteria, required functionality and other criteria as outlined in Table x APN Tunnel Evaluation below. It is especially suited when the Indirect model is used. There may be scalability and configuration concerns when the Direct or Hybrid models are used. The solution should be documented as an IPv4 addressing solution, and can also be used as an IPv6 solution to fulfil other requirements such as security. + +This approach eliminates any IPv4 Address limitations, allows full use of private IPv4 addressing space and allows overlapping IPv4 address pools. IP address assignment can be handled by the MNO or controlled by the M2M enterprise providing for either static or dynamic addressing assignment. + +MT Communication can be initiated by the MTC Server without the need for issuing a request to the 3GPP system to trigger attached MTC devices using the always on model. This is solved by the relaying of RADIUS/Diameter accounting start/stop messages (clause 6.29.3) to provide an indication of the presence and IP address of MTC Device towards MTC Server. For other connection models, like PDP/PDN connections on demand, device trigger requests may be used in together with RADIUS/Diameter updates of MTC Device presence and IP address. + +Solution can be achieved with no or minimal standards impacts using existing 3GPP capabilities and VPN techniques (e.g. MPLS VPN, IPSec Tunnel, and other Layer 2 and Layer 3 tunnelling techniques) over Gi/SGi. + +**Table 5.3.3-1: APN Tunnel Evaluation** + +| <b>Criteria</b> | <b>Solution: Dedicated APN tunnels (i.e. 6.29.2, 6.29.3, 6.29.4)</b> | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| The mechanism shall be scalable | <p>A GGSN/P-GW can typically support a large number of APNs. Operators may have different policies for usage of dedicated APNs.</p> <p>No IPv4 Addressing limitations. Allows for overlapping and full use of private IPv4 address space. This eliminates scalability constraints also for always-connected scenarios.</p> <p>Some considerations about scalability issues may be needed for events that affect large amounts of the always-on PDN/PDP connections like a need for (re-)balancing due to O&M measures for network nodes or when there is a recovery/restoration.</p> <p>No scalability issues are expected during normal operation when the Indirect model – Operator Controlled (i.e. single dedicated APN/IPSec tunnel per MTC Server and GGSN/PDN-GW combination) is used.</p> <p>When the Direct, Indirect model – Service Provider Controlled and Hybrid models are used, scalability will be an issue when there are multiple MTC Applications communicating with UEs directly (requiring dedicated APN/VPN tunnel per MTC Application and GGSN/PGW combinations) or indirectly via the MTC Server (i.e. problem of public IP address resolution for addressing by MTC Application pushed from mobile network onto MTC Server).</p> <p>When the Indirect model – Service Provider Controlled are used, it is FFS if scalability will be an issue when a MTC Server is communicating with a set of UEs whose subscriptions are spread across multiple MNOs</p> | +| The mechanism shall minimize the required configuration by the MNO and the MTC User; | <p>IPSec tunnel with IKE (Internet key Exchange) can be used for dynamic setting of IPSec Security associations minimizing configuration by operator. UE needs APN configuration. Dedicated APN configuration required per APN and MTC Server or MTC Application.</p> <p>When a high numbers of VPN tunnels are required per MTC Server this will cause significant configuration burden for MTC Server.</p> <p>For Hybrid model, when a high number of VPN tunnels are required per MTC Application, this will cause significant configuration burden for MTC Applications.</p> | +| The mechanism shall minimize the required messaging transactions by the MTC Server to initiate MT communications; | <p>With always on support no additional message transactions required for MT terminated communication, besides perhaps for some specific situations where triggering may be used e.g. to recover the (always-on) PDP/PDN connection from error cases or to set triggers for devices that are out of coverage.</p> <p>MTC Server can be aware of presence of MTC device and assigned Private IP address as described using techniques as described in 6.29.3 and 6.29.4</p> <p>For PDP/PDN connections not using always on, triggering should be used similar to any non-always-on solution. Triggering may also be used e.g. to recover the PDP/PDN connection from error cases or to set triggers for devices that are out of coverage.</p> | +| The mechanism shall minimize the messaging sent over the air to the MTC Device; | <p>For the always-on model there is no new signalling induced or alternate communication channels (e.g. SMS) for delivery of a "push" stimulus to an attached MTC device with an established PDN connection is required.</p> <p>For PDP/PDN connections not using always on, triggering should be used similar to any non-always-on solution.</p> | +| The mechanism shall minimize any additional user plane latency; | For the always-on model there is no change to user plane latency in core network and radio interface. | +| The mechanism shall minimize any additional security threats to the MTC Device | Traffic Separation achieved with IPSec tunnel. Additional security provided with dedicated APNs. Only MT communication originating from the MTC server or emanating from the MTC enterprise network can be initiated towards MTC device. Similar level of security provided as per existing 3GPP deployments providing corporate access to corporate APNs | +| Direct Model - Direct Communication provided by the 3GPP Operator: The M2M Application connects directly to the operator network without the use of any MTC Server; | <p>Supported</p> <p>Instead of terminating in the MTC Server, the tunnel could terminate into another node (IPSec GW) with Public IP interface in the MTC enterprise network. Otherwise, there will be scalability issue (see scalability criteria above).</p> | +| Indirect Model – MTC Service Provider controlled communication: The MTC Server is an entity outside of the operator domain. | Supported with traffic separation over public Internet e.g. using IPSec tunnel. Tunnel terminated at the MTC Server. When MTC Server communicates with multiple HPLMNs, there will be scalability issues (see scalability criteria above). | +| Indirect Model – 3GPP Operator controlled communication: The MTC | Tunnelling within operators domain towards MTC Server can be achieved with other existing VPN techniques such as MPLS VPN | + +| Criteria | Solution: Dedicated APN tunnels (i.e. 6.29.2, 6.29.3, 6.29.4) | +|------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Server is an entity inside the operator domain | | +| Hybrid model | Supported with traffic separation over public Internet e.g. using IPSec tunnel. Tunnel terminated at the MTC Application. There may be a scalability issue (see scalability criteria above). | +| MTC Server Complexity | MTC Server could serve as tunnel endpoint as IPSec/IKE supported by common OS (e.g. Linux /FreeBSD).<br>Alternately the MTC enterprise network tunnel endpoint could be served by readily available infrastructure (IPSec GW) instead of MTC Server.<br>Dedicated APN configuration requirements and public IP address resolution burden (see scalability criteria above). | +| Impacts to Standards | For the always-on model there is none.<br>Reuse of existing 3GPP features (e.g. dedicated APNs, Private IPv4 addressing, Traffic Separation over Gi/SGi using well known VPN techniques (e.g. IPSec Tunnel, MPLS VPN), Radius/Diameter accounting to relay presence of and IP address of MTC Device towards MTC Server | +| Support for roaming | Roaming is supported via HPLMN. Not suitable for local breakout scenarios. | +| Deployment solutions | Various solutions based on dedicated APN and tunnelling exists today for the enterprise domain. | +| Terminal complexity | If the MTC Device needs to have simultaneous access to MTC Servers associated with different APNs, the solution requires that the MTC device support multiple PDN connections (i.e. multiple IP addresses) | +| Added complexity to the 3GPP network elements | Uses existing function in the existing 3GPP system. | +| Dependency on other SDOs before the solution is deployable | None. | + +## 5.4 Key Issue - Small Data Transmission + +### 5.4.1 Use case description + +**Editor's note:** Expand upon the Service Description use case, including technical constraints and interpretations. + +MTC Devices with Small Data Transmission send or receive only small amounts of data. The exact amount that is considered to be small may differ per individual system improvement proposal. It is the amount of data where a specific system improvement proposal still provides its benefits. + +For online small data transmission it is assumed that data transfer can happen any time when needed by the application. Before the transmission of the small data, the MTC device may be attached to or detached from the network. + +### 5.4.2 Required Functionality + +**Editor's note:** Capture agreements on requirements for solving the key issue. This clause may be omitted if deemed unnecessary. + +The following functionalities are required for Small Data Transmission: + +- It shall be possible to transmit small amounts of data with very efficient resource. +- Before transmission of small amount of data, the MTC Device may be attached or detached to/from the network. +- The definition of a small amount of data shall be configurable per subscription or by network operator policy. + +**Editor's note:** Considerations for solutions should include the small data upper limit that the solution is suitable for. + +**Editor's note:** Considerations for solutions should include the frequency of small data transmissions that the solution is suitable for. + +**Editor's note:** Considerations for solutions should include support for mobility management or retransmission of lost data. + +Editor's note: Need to determine charging requirements. + +Editor's note: Need to determine subscription aspects related to small amount data transmission. + +### 5.4.3 Evaluation + +## 5.5 Void + +## 5.6 Key Issue - Low Mobility + +### 5.6.1 Use case description + +Editor's note: Expand upon the Service Description use case, including technical constraints and interpretations. + +For MTC Device with low mobility, several use cases should be captured in this TR as follows: + +- not move frequently and may move only within small area: e.g. health monitoring at home. +- not move frequently but may move within wide area: e.g. mobile sales terminals. +- not move normally, i.e. with fixed location: e.g. water metering. + +For this kind of MTC Device, it is studied how to reduce the frequency of mobility management procedures and how to optimize the paging. + +### 5.6.2 Required Functionality + +The required functionality for low mobility should result in: + +- reduction in resource usage for low mobility MTC Devices (e.g. paging, location management signalling, mobility context in MME/SGSN/MSC) + +### 5.6.3 Evaluation + +## 5.7 Key Issue - MTC Subscriptions + +### 5.7.1 Use case description + +Based on stage1 requirements, MTC Features are subscribed and controlled by subscription. + +Any usage of the subscribed MTC features is activated by default at the time of the subscribing the feature. + +It should be possible to allow the MTC Subscribers to activate the unsubscribed MTC Features or deactivate the subscribed MTC Features based on the operator policy. The mechanisms used for activation/deactivation are outside the scope of 3GPP. The MTC solution shall make it possible to provision the home PLMN with MTC subscriptions and allow one or more MTC Devices to share this subscription. This key issue aims at specifying the architectural requirements related to MTC subscriptions as well as the relationship between MTC subscriptions, MTC Devices and MTC architecture enhancements. + +### 5.7.2 Required Functionality + +MTC Features are controlled by subscription in HSS. + +NOTE: MTC Features should be subscribed by already existing methods; It is normally out of scope of 3GPP standardisation e.g. via the provisioning interface or via a web interface. + +The capability to subscribe/unsubscribe MTC Features is provided to the MTC Subscriber. The subscription information (i.e. MTC Feature is subscribed) of the MTC Feature shall be stored in the relevant 3GPP CN entities. + +It is also possible for a network operator to restrict incompatible MTC Feature subscription (according to network operator policy.) During the activation/deactivation, if the MTC Subscriber request results in a set of incompatible MTC Features (according to network operator policy), it shall be possible for the operator to reject the request. + +Upon attachment or subscription update, it shall be possible for the SGSN/MME to support only a subset of the subscribed MTC features based on network capability and/or MTC device capability. + +**Editor's note:** It is FFS how the device capability can be known to the network. + +**Editor's note:** It is FFS, if MTC feature(s) may be designated as "essential". In which case, the MME/SGSN informs the MTC device and detaches the device when the MTC Features cannot be supported. + +A feature is considered as essential if a MTC device cannot operate normally when the feature is not enabled. + +A feature is considered as mandatory when the home operator forbids attachment to the network when this feature is not/cannot be enabled. + +**Editor's note:** Upon attachment or subscription update when the MTC device is in roaming, it may be possible for the visited network operator to inform the home operator of the features are not supported. + +It may be possible for the network operator to inform the MTC Device enabled/disabled status of the MTC features. + +**Editor's note:** It is FFS which MTC features' enabled status may be notified to the MTC device. + +The following requirements are relevant to MTC subscriptions: + +- It shall be possible to provision the home PLMN with MTC Subscriptions, each one shared by one or more MTC Devices. +- Each MTC Device shall be associated to one MTC subscription and shall have a device subscription including the security credentials used to authenticate the device. +- An MTC subscription shall indicate MTC Features that are subscribed by the MTC Devices sharing this subscription. +- It shall be possible for all MTC Devices sharing the same MTC subscription to use all subscribed MTC Features belonging to this subscription. + +**Editor's note:** As it is assumed that subscribed MTC Features are activated whenever supported by the network, the above requirement may be redundant. + +## 5.8 Key Issue - MTC Device Trigger + +### 5.8.1 Use case description + +For many M2M applications there may be an interest to have poll model for communications between MTC devices and the MTC Server. This may be because the MTC User wants to be in control of communication from MTC Devices, and does not allow MTC Devices to randomly access the MTC Server. Also for applications where normally the MTC Devices initiate communications, there may occasionally be a need for the MTC Server to poll data from MTC devices. + +If an MTC Server has an IP address available for the device it needs to poll data from, it tries to communicate with the device using the IP address. If the communications fails, or if no IP address is available for the device, the MTC Server can use the MTC Device Trigger to try to establish the communication. This may cause a PDP/PDN connection to be established if it didn't exist or re-established if it wasn't working e.g. after an error condition in the network. It is important that it can be guaranteed to the MTC User that MTC Devices can only be triggered by authorized MTC Servers. If the network is not able to trigger the MTC Device, e.g. due to network congestion, the network may report the trigger failure to the MTC Server. The MTC Device Trigger is a service provided by the 3GPP system for the MTC server over control plane signalling. + +Triggering of MTC Devices is based on the use of an identifier identifying the MTC Device that needs to be triggered. The identifier used by the MTC User in the triggering request to the MTC Server can be different from the identifier used by the MTC Server in the triggering request to the PLMN network. + +## 5.8.2 Required Functionality + +The following functionality is required to trigger MTC Devices: + +- The PLMN shall be able to trigger MTC Devices to initiate communication with the MTC Server based on a trigger indication from the MTC server. +- The network shall provide a mechanism such that the MTC Device can only receive trigger indications from authorized MTC Servers. +- Upon receiving a trigger indication from a source that is not an authorised MTC Server, the network shall be able to provide the details of the source (e.g. address) to the MTC User. +- The network shall provide a mechanism to the MTC User to provide a set of authorized MTC Server(s). +- The trigger mechanism shall be able to provide a scalable transmission of trigger request and trigger response messages for multiple MTC Devices in the PLMN and on the interfaces to the MTC Server. +- The main characteristic of the device trigger feature is the *control plane* interaction between the MTC Server and the 3GPP system that initiates all necessary functions or procedures within the 3GPP system and towards the MTC Server to enable the MTC Server to send user plane data towards the MTC Device. Any triggering activity on MTC application level, which results in traffic being transferred by the 3GPP system transparently as user plane data, is not considered as device trigger (feature). +- A MTC Device shall be able to receive trigger indications from the network and establish communication with the MTC server when receiving the trigger indication. Possible options are: + - Receiving trigger indication in detached state and establish communication. + - Receiving trigger indication in attached state and the MTC device has no PDP/PDN connection. + - Receiving trigger indication in attached state and the MTC device has a PDP/PDN connection. + +NOTE 1: There are currently available solutions to trigger MTC Devices (e.g. unanswered CS call attempts, sending an SMS). However, these have disadvantage when used at a large scale (e.g. they are based on MSISDNs), and work only for attached MTC Devices. This key issue will investigate possible improvements over the currently available means for triggering. + +NOTE 2: In reference to the three sub-bullets above (beginning with "*Receiving trigger indication in...*"), the trigger indication denotes a control plane indication specific to the MTC Device Trigger feature, including the case of the MTC device having a PDP/PDN connection. Reasons for recurring to device triggering in the latter case are e.g. when the MTC Server does not know the IP address assigned to the MTC Device, or when the MTC device does not respond after using MT IP communication e.g. due to network problems or that the IP address has become obsolete, or when the MTC device is not user plane reachable by a MTC Server over the currently established PDP/PDN connections, or because of other reasons where user plane communication needs to be initiated from the MTC device side. + +- A HPLMN supporting the MTC device trigger feature shall provide an interface for reception of a trigger indication into the PLMN in order to be delivered by the network to the addressed MTC device. This MTCsp interface: + - shall be globally consistent (i.e. the same) across PLMNs supporting the MTC device trigger feature. + - shall not require the MTC server to have prior knowledge of the current reachability state (e.g. attachment and PDP context/PDN connection states) of the targeted MTC device. + - shall allow for providing a validity or life time that indicates how long the network should store the trigger request when it cannot be delivered to the UE, e.g. when the UE is not reachable or when load control prevents immediate delivery + - PLMNs supporting the MTC device trigger feature shall be able to collect appropriate CDRs for each trigger delivered to a UE. + +NOTE 3: This interface does not preclude an MTC server from interrogating/monitoring the network for the current reachability state of a MTC device. + +NOTE 4: For backwards compatibility reasons, this interface does not preclude a MTC server from using a pre-existing interface (e.g. submitting an SMS-based trigger indication directly to an SMS-SC). However, the intention would be for MTC service providers to migrate towards utilizing this new interface for device triggering. + +- The network shall be able to report the success or failure of the trigger (e.g. due to network congestion) to the MTC server, if so requested by the MTC Server. +- It shall be possible to provide a load control mechanism for the trigger requests, e.g. controlling the ingress rate of triggers from a specific MTC server at the MTC-IWF or the aggregate ingress rate from all MTC servers at the MTC-IWF or by some other means to reduce the load on the network. +- NAS level congestion control assumes that the network will not trigger the UE as long as the particular congestion situation remains. Trigger load control mechanisms shall ensure that the network congestion is not exacerbated by UEs that respond to triggers. + +**Editor's note:** It is FFS how existing or new congestion control mechanism works with the selected triggering solution to control trigger requests. + +- In the triggering request to the PLMN the MTC Server shall use an external identifier to indicate the UE used for MTC that is required to be triggered. + +NOTE 5: The identifier used by the MTC User in the triggering request to the MTC Server can be a different identifier than the one used by the MTC Server in the triggering request to the PLMN. The identifier used by the MTC User is out of scope of 3GPP standardisation and may e.g. be an application specific identifier. + +### 5.8.3 Evaluation + +#### 5.8.3.1 Comparison of the MTC Device Trigger solutions + +| Evaluation characteristic<br>Solution <img alt="phone icon" data-bbox="263 246 295 280" src="3558a64b4f3d03eb8da8e584c606af39_img.jpg"/> | Impact on existing system and UE | Possibility to trigger device without MSISDN | Possibility to trigger device without CS subscription | Possibility to trigger device behind a middle box (NAT/firewall) | Load on CS nodes | Complexity (incl. issues like need for new entities) | Efficiency | Migration (incl. issues like roaming or interoperation with legacy, MSISDN-less, PS only, triggering when device becomes reachable) | Comment (specific issues not covered by other columns) | +|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------|------------------|------------------------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| 6.6 Solution - Triggering of non-attached MTC Devices based on location information provided by MTC User | | | | | | | | | | +| 6.39 Solution – Triggering MTC devices via HSS and NAS signalling | | | | | | | | | | +| 6.41 Solution – Triggering of attached MTC Devices by reusing Network Requested PDP Context Activation procedure | | | | | | | | | | +| 6.42 Solution - Triggering of attached MTC Device via Pre rel-11 SMS | | | | | | | | | | +| 6.43 Solution - Triggering of attached MTC Device via intermediate node | | | | | | | | | | +| 6.44 Solution – Device Triggering reuse of MT SMS WAP Push | | | | | | | | | | +| 6.45 Solution – Device trigger gateway solution | | | | | | | | | | + +### 5.8.3.2 Delivery of device trigger information from 3GPP system to UE + +When it is possible for an MTC device to receive MT-SMS (e.g., currently over E-UTRAN requires a CS or IMS subscription) and to be associated with an individual MSISDN, for reasons of minimizing impact on the existing system, keeping complexity low and facilitating migration from triggering solutions used today, an MT-SMS based solution shall be supported for delivering trigger information from 3GPP system to the device. This would also allow roaming in other PLMNs without any upgrade in the visited network. + +A 3GPP network may support more than one trigger delivery methods, e.g. a pre-Rel-11 SMS delivery without any system enhancements and another trigger delivery method to cope with different capability and deployment conditions, e.g. for triggering an MTC device to which no E.164-MSISDN is assigned. + +**Editor's note:** Whether any additional trigger delivery mechanisms are to be supported in Rel-11 is FFS. + +### 5.8.3.3 Submission of device trigger requests from MTC server to 3GPP system + +The 3GPP network shall support standardized control signalling between the MTC Server and the 3GPP system via the MTCsp reference point for submission of the device trigger requests. The MTCsp is provided by an MTC-IWF. + +In order to provide an automated, reliable and scalable mechanism for an MTC Server to determine the address/route of the assigned MTC-IWF(s) for a UE used for MTC to be triggered, e.g. DNS resolution of the address of assigned MTC-IWF for each UE used for MTC that can be triggered over MTCsp shall be supported. + +The MTC-IWF performs PLMN related control functionality such as MTC Server authentication, trigger request authorization and charging, and shields the MTC Server from the actual trigger delivery mechanism used within the PLMN. + +The protocol used from the MTC Server for submitting device trigger requests to the 3GPP system (and subsequent protocols within the PLMN) should support an option where the UE can be identified without the use of an E.164-MSISDN. + +MTCsp shall always be provided by the HPLMN and the MTC-IWF will only accept a device trigger for a UE subscribed with the HPLMN. This removes the need for the MTC-IWF in the VPLMN to map the external identifier and forward the trigger request to the HPLMN of a roaming device. + +Additionally, the 3GPP network shall support control signalling between the MTC Server and the 3GPP system via the MTCsms reference point for submission of the device trigger requests as part of user data of a MT-SMS. The MTCsms is provided by an SMS-SC. + +### 5.8.3.4 3GPP system internal handling of device triggers + +The protocols within the PLMN should support an option where the UE can be identified without the use of an E.164-MSISDN. A PLMN may support delivery of MT-SMS with an IMSI as destination address instead of an E.164-MSISDN. However, in order to avoid exposure of IMSI outside the MNO domain, this shall only be allowed for SMEs located in the MNO domain. + +The MTC-IWF interrogates HLR/HSS, when needed, to map external identifier to IMSI and gather UE reachability and configuration information, selects the trigger delivery mechanism and performs protocol translation if necessary, e.g. to reformat the triggered request to match the selected trigger delivery method, and routes the request towards the relevant network entity. Validity time is used for the delivery of device trigger requests to the UE. + +Synergies might be possible with MTC Small data transmission where MT-SMS or other trigger delivery services are also a candidate for small data transmission. + +**Editor's note:** The MT-SMS should be further detailed, including how E.164-MSISDN-less operation is done. This detailing may include both the existing MT-SMS and possible future evolutions. + +## 5.9 Key Issue –Time Controlled + +### 5.9.1 Use case description + +MTC Devices with Time Controlled MTC Feature send / receive data only at certain pre-defined time periods. Network operators can pre-define / alter the time period based on criteria (e.g. daily traffic load) and only allow MTC Devices to access the network (attach to the network or send / receive data) during the pre-defined time period. The key issue aims + +at describing how to restrict MTC Device's access to the network and avoid unnecessary network load outside these pre-defined time periods. The home network operator may restrict altering the time period by the visited network operator e.g. to avoid traffic when the MTC server is in maintenance by means of a 'forbidden time interval.' During this forbidden interval, the network shall reject access requests per MTC Device. This allows for maintenance, e.g. of the MTC Server. + +**Editor's note:** The interaction of PAM and Time Control are FFS. + +Typically, an MTC User agrees with an operator on a predefined time period for a group of MTC Devices. The time in which access is permitted is termed a 'grant time interval.' The network shall communicate the (altered) grant time interval to the MTC Device and may also do so to the MTC Server and MTC User. A 'grant time interval' does not overlap with a 'forbidden time interval.' + +In roaming scenarios, the local network operator may alter the access grant time interval based on local criteria, e.g. (daily traffic load, time zones) but the forbidden time interval may not be altered. + +It is desirable that access of MTC Devices with the same access grant interval is distributed across this interval in a manner to reduce peaks in the signalling and data traffic. + +For many applications, individual MTC Devices do not need the total duration of this predefined time period to communicate with the MTC Server. Typically a 5-10 minutes communication window is sufficient for an individual MTC Device. The network operator may limit the duration of these communication windows. To avoid network overload, signalling and data traffic the communication windows of the devices shall be distributed over the pre-defined time period e.g. through randomization of the start time of the individual communication windows. For a network operator, it can be beneficial that the MTC Devices are not attached outside their communication window. Therefore, the network operator should be able to enforce detach of an MTC Device from the network at the end of the communication window of a device. + +The network operator may allow MTC Devices to exchange signalling and send and receive data outside of defined time intervals but charge differently for such traffic. + +Time Control terminology is illustrated in Figure 5.9.1-1. + +![Figure 5.9.1-1: Time Control Terminology. A horizontal timeline labeled 'Time' with arrows at both ends. Below the timeline, there are two adjacent intervals marked by vertical tick marks: 'Grant Time Interval' on the left and 'Forbidden Time Interval' on the right. Below the 'Grant Time Interval', there is a shorter interval marked by vertical tick marks, labeled 'Communication Window'.](e38206fcefa2045af01d494b2956775a_img.jpg) + +Figure 5.9.1-1: Time Control Terminology. A horizontal timeline labeled 'Time' with arrows at both ends. Below the timeline, there are two adjacent intervals marked by vertical tick marks: 'Grant Time Interval' on the left and 'Forbidden Time Interval' on the right. Below the 'Grant Time Interval', there is a shorter interval marked by vertical tick marks, labeled 'Communication Window'. + +**Figure 5.9.1-1: Time Control Terminology** + +**NOTE:** The Communication Window can be expressed as a start and stop time, a start time and duration, an offset from the beginning of the Grant Time Interval and a duration, etc dependent on the solution. + +The MTC Device may defer access of the network until it will originate communication, provided that the MTC Device's upper layers do not require reception of mobile terminated communication during the period of time the MTC Device remains Detached. + +## 5.9.2 Required Functionality + +The following requirements can be derived from the Time Controlled MTC feature requirements specified in TS 22.368 [2]: + +- the network operator shall be able to allocate for a group of MTC devices time periods during which signalling or user plane traffic to/from the network is allowed. This is termed 'grant time interval'; +- the network operator shall be able to further restrict the time during which signalling or user plane traffic to/from the network is allowed for individual MTC devices in the group to a time window with a defined duration; + +- the network shall be able to inform the MTC Device of the (altered) time periods during which signalling or user plane traffic to/from the network is allowed. The network may communicate the (altered) time periods to the MTC Server or MTC User; +- enforcement of a detach of an MTC Device from the network at the end of the of the Device's communication window shall be supported; +- roaming shall be supported for MTC devices with Time Controlled Feature. The local network operator (in roaming scenarios) may alter the grant time interval based on local criteria; +- the network shall be able to alter above time periods; +- the network operator shall be able to allocate for a group of MTC devices a time period during which signalling or user plane traffic to/from the network is disallowed. This is termed 'forbidden time interval.' A forbidden time interval and a grant time interval shall not overlap. The forbidden interval shall not be altered. The home network operator or MTC User use the 'forbidden interval' to restrict the extent to which change of the time periods is allowed by the (visited) network operator (e.g. to avoid traffic when the MTC server is in maintenance); +- peaks in traffic (including signalling traffic) shall be avoided (e.g. by randomization of the time during which the MTC Devices communicate.). + +NOTE: It is possible for the network operator to allow or reject the MTC device's access to the network according to the operator policy, when it is out of time period. + +## 5.9.3 Evaluation + +# 5.10 Key Issue - MTC Monitoring + +## 5.10.1 Use case description + +MTC Devices may be deployed in locations with high risk, e.g. possibility of vandalism or theft of the communication module. For those MTC Devices, it is desirable that the network detects and reports events (including location) caused by those devices that may result, for example, from vandalism or theft of the communication module. If such an event is detected, the network might be configured to perform special actions, e.g. limit the access or reduce the allocated resource. + +## 5.10.2 Required Functionality + +The following functionalities are required for MTC monitoring: + +- It shall be possible for the MTC User to configure the monitoring events, e.g. monitoring the association of the MTC Device and UICC, misalignment of the MTC feature, change in the point of attachment, loss of connectivity. +- The MTC User shall configure the action to be executed by the network. +- It shall be possible for the network to detect monitoring events. +- It shall be possible for the network to report the detected events to the MTC User or the appropriate MTC Server and optionally to perform action to reduce services provided to the MTC Device. +- It shall be possible to configure the maximum time between the actual loss of connectivity and its detection in the MTC subscription. The maximum detection time can be in the order of 1 minute to 1 hour. + +## 5.11 Key Issue - Decoupling MTC Server from 3GPP Architecture + +### 5.11.1 Use Case Description + +Machine to machine communications exist today, over a variety of access systems. These essentially make use of particular features exposed by individual access systems, devices and aggregation services to build a unique 'vertical system' to support an application for an end customer. Examples include logistics, point of sale and power metering. + +The current direction of the industry is to eventually provide general service interfaces to enable a new class of 'layered' applications that can work with diverse MTC devices, network operators, accesses and diverse business logic components without requiring a unique 'from scratch' system integration effort. + +The current abstraction shown in the SA1 service aspects specification TS 22.368 [2] represents the MTC server as an entity with which the 3GPP PLMN and the MTC Device directly communicate. This depicts a service delivery representation well, but has very misleading implications if accepted as a basis for the MTC architecture, + +Two potential deployment scenarios exist for MTC Services – either under the control of a mobile network operator or by a third party. + +To support MTC services deployed by third parties, it is assumed that additional interaction between MTC service logic components and the 3GPP PLMN are required, beyond data communications (SMS and packet domain communication.), These interactions include at least the ability for service logic components to securely interact with the 3GPP PLMN and the ability for the service logic components to obtain certain information regarding MTC Subscriptions and modifying this information (if allowed by the network operator). + +Some service logic components only interact with MTC Devices by means of established user plane communication (e.g. SMS or TCP/IP based applications). These service logic components may have no direct means to interact with or become aware of MTC Features. For example, there are existing M2M applications that employ GPRS and/or SMS to communicate with MTC Devices. For such service logic components, no additional mediating interfaces as proposed in this key issue shall be required. + +A 3GPP MNO can restrict or deliberately allow access to information, resources and services in the core network by means of the Service Abstraction Layer. + +### 5.11.2 Required Functionality + +MTC Service Logic components may be deployed within a mobile network operator's control or externally. + +The Baseline Architecture in clause 4.3 shall be updated with additional interfaces for secure communications between MTC Service Logic Components and the 3GPP PLMN as well as for MTC Service Logic Components to query or possibly update MTC subscription information. + +It is desirable to minimize the requirements for MTC Service Logic components to support 3GPP interfaces and 3GPP-specific configuration. This facilitates the design of MTC services that function over multiple access systems. + +## 5.12 Key Issue - Signalling Congestion Control + +### 5.12.1 Use Case Description + +MTC related signalling congestion and overload is an urgent issue that network operators are currently facing. Not only network operators that are providing MTC services, but also network operators in which MTC Devices are roaming can be affected by MTC related signalling congestion and overload. + +MTC related signalling congestion and overload can be caused by: + +- a malfunctioning in the MTC application and/or MTC Server. + +This cause leads to a congestion situation for which the operator wants to protect its network without affecting other MTC users. + +- an external event triggering massive numbers of MTC Devices to attach/connect all at once. + +This cause leads to an overload situation for which the operator wants to prevent its network from a complete collapse. As the overload situation relates to abnormal usage from a multitude of applications and customers, a protection mechanism will affect all or a significant number of MTC applications. + +- recurring applications that are synchronised to the exact (half/quarter) hour. + +This cause leads to a peak load situation for which the operator wants to spread the required capacity over time with the goal of reducing the investment needed to fulfil the required capacity demand. + +Though some of the signalling congestion issues could be avoided if MTC applications behave more mobile network operator friendly, there is little a network operator can do to influence the application developers. It is important that the mobile network operator has the capability to control signalling network congestion independent of the application providers. + +Signalling network nodes that may suffer from MTC related signalling congestion include all PS domain control plane nodes and gateways. With large scale attach requests, mainly the SGSN/MME is vulnerable. With connection requests, also the SGSN/MME is vulnerable as this node has a relative large load per connection request. GGSNs/PGWs are especially vulnerable as often M2M applications use a dedicated APN which may be terminated at one GGSN/PGW unless DNS and load balancing mechanisms are used. All connection requests for that particular application will then have to be handled by a single GGSN/PGW. MTC devices may concurrently attempt signalling interaction only in a limited area. That means the signalling congestion could occur just at one or several particular signalling links and no overall congestion appears on network nodes. + +In order to combat signalling congestion, network nodes shall be able to reject or prevent attach or connection requests. The challenge is to block the traffic of the particular MTC application(s) that is causing the congestion, without restricting non-MTC traffic or traffic from other MTC applications that are not causing a problem. A dedicated APN or a MTC Group Identifier are possible identifiers to indicate particular large scale MTC applications. How to identify applications that are causing recurring signalling congestion (e.g. mail applications, buddy finders, etc) that are often downloaded applications on a smart phone is still a challenge. + +Care shall be taken that rejecting connection requests or attach requests does not result in a MTC Device immediately re-initiating the same request. The network should be able to instruct MTC Devices not to initiate a similar request until after a back off time. This back off time may also be used to instruct MTC Devices with recurring applications to change their timing of attach/connection requests. + +Care shall be taken that preventing attachment or connection requests by a targeted group of MTC Devices does not immediately or sometime thereafter result in the same group of MTC Devices almost simultaneously attempting signalling or data interactions with the same or different PLMN. Randomization should be applied to spread any resultant network access attempts by the group. + +## 5.12.2 Required Functionality + +The required functionality depends on the identified congestion and overload situation. + +Congestion control provides means to manage the network load from a particular MTC group and/or related to a specific APN. Congestion control requires the following functionalities: + +**Editor's note: Further architecture work is required on the MTC Group concept before it is possible to progress solutions depending on MTC Group Identifiers.** + +- It shall be possible to reduce signalling load (Attach, PDP/PDN Activation, Service Request, ...) from MTC devices related to a specific APN or from MTC Devices belonging to a particular MTC Group. +- Congestion control per APN or MTC group shall be possible with a granularity of a single SGSN, MME, GGSN or PGW. +- In order to reduce network load due to congestion situation, it shall be possible for the network to detach MTC devices belonging to a particular MTC Group and/or related to a specific APN and/or deactivate the bearers belonging to a specific APN or to a particular MTC device group. +- In order to avoid network congestion, it shall be possible for the network to prevent MTC devices related to a specific APN and/or belonging to a particular MTC group from too frequent initiation of attach and/or connection requests. + +Congestion control shall also be taken with a granularity of a single signalling link between BSC/RNC and SGSN or eNodeB and MME, or a signalling link set which contain all links connecting to a single BSC, RNC, eNodeB, RA or TA(List). + +Overload control provides means to manage the network load from all MTC devices independently from other devices. Overload control requires the following functionalities: + +- It shall be possible to reduce signalling load caused by MTC Devices independently from signalling load caused by non-MTC devices. +- Overload control shall be possible with a granularity of a single SGSN, MME, GGSN and/or PGW. +- In order to reduce network load due to overload situation, it shall be possible for the network to detach MTC devices selectively and/or deactivate the bearers selectively among APNs or MTC device groups. +- In order to avoid network overload, it shall be possible for the network to prevent MTC Devices from too frequent initiation of attach and/or connection requests. + +NOTE 1: [It is for further study](#) how it can be prevented that large numbers of devices re-initiate their deferred attach and/or connection requests at (almost) the same time to avoid excessive network congestion. + +Peak shaving requires the following functionalities: + +- It shall be possible to reduce (quarter/half) hourly signalling peaks from recurring MTC applications +- It shall be possible to spread over time signalling load of requests from all MTC Devices. + +NOTE 2: The relation of this key issue with the key issue Time controlled is for further study especially regarding the treatment of MTC devices that are sending/signalling during their assigned time period [is for further study](#). + +## 5.12.3 Evaluation + +### 5.12.3.1 General + +**Editor's note:** The evaluations for this clause were approved distinctly and are complimentary. They are provided without any attempt to merge them. + +### 5.12.3.2 Evaluation for Congestion Control + +For congestion control, a combined solution from "Solution - Rejecting connection requests by the SGSN/MME", see clause 6.22, and "Solution - Broadcasting MTC Access Control by RAN", see clause 6.28, provides the most complete, fast and efficient means to manage the network load from a particular MTC group and/or related to a specific APN. + +At the immediate onset of a congestion scenario, the first few MTC Devices from the congesting MTC Group/APN requesting RRC and/or NAS access can be rejected assuming there are enough signalling resources available to receive and reject the RRC and/or NAS access requests. To prevent the remaining MTC Device from the congesting MTC Group/APN from sending any access requests during the remainder of the congestion scenario, MTC access barring can be broadcast by the RAN to efficiently bar the specific congesting MTC Group/APN from attempting access. The RRC and/or NAS rejection back-off times and MTC access barring randomization can successful prevent the rejected/barred MTC Devices from almost simultaneously initiating access attempts after the congestion scenario has subsided. + +Given this solution is dependent on the implementation of MTC Groups, it does not provide for a low impact on existing 3GPP standards and products and thus is not feasible in Rel-10. + +### 5.12.3.3 Evaluation for Overload Control + +For overload control, a combined solution from "Solution – Rejecting connection requests by the SGSN/MME", see clause 6.22, "Solution - Rejecting RRC Connection and Channel Requests by the eNodeB/RNC/BSS", see clause 6.26, and "Solution - Broadcasting MTC Access Control by RAN", see clause 6.28, provides the most complete, fast and efficient means to manage the network load from all MTC Devices independently from other devices. + +At the immediate onset of an overload scenario, the first few MTC Devices requesting RRC and/or NAS access can be rejected assuming there are enough signalling resources available to receive and reject the RRC and/or NAS access requests. To prevent the remaining MTC Device from sending any access requests during the remainder of the overload + +scenario, MTC access barring can be broadcast by the RAN to efficiently bar all MTC Devices, low-priority MTC Devices, and/or MTC Devices of a PLMN type from attempting access. The RRC and/or NAS rejection back-off times and MTC access barring randomization can successful prevent the rejected/barred MTC Devices from almost simultaneously initiating access attempts after the overload scenario has subsided. + +Given this solution is not dependent on the implementation of MTC Groups, it provides for a low impact on existing 3GPP standards and products that may be feasible in Rel-10. + +### 5.12.3.4 Comparison of Each Solution + +The pros and cons of each solution are as follows. + +#### 1. Access Control by the RAN (eNB/RNC/BSS) as per 6.28. + +##### a. Pros : + +There is no wasted signalling with the MTC devices + +It can be used for controlling the overload of the RAN node and also for the CN node with the extension of the S1AP: Overload Start and Stop message. + +##### b. Cons: + +For applying the barring with the finer granularity such as per group, the more information should be broadcasted in the system information. + +NOTE 1: The randomized barring computed as $T303 = (0.7 + 0.6 * \text{rand}) * \text{ac-BarringTime}$ may decrease the possibility that a large number of MTC devices simultaneously access the network. But the possibility still exists. Due to this possibility, we may need to enhance the current RACH mechanism that limits the number of the UE identifying the opportunities at the same time. For the other two solutions, it is also required to enhance the current RACH mechanism. + +#### 2. Rejecting RRC connection and channel requests by the eNB/RNC/BSS as per 6.26. + +##### a. Pros: + +This solution wastes the smaller number of signals than rejecting the request by the SGSN/MME. + +##### b. Cons: + +It is possible to use the solution for finer granularity control, such as per group. But, per group, the group ID should be included and then the RRC message; that is, including the group ID in the RRC connection setup complete rather than the RRC connection request. This is needed because the RRC connection request message is sent using CCCH before the dedicated control channel to the UE. Hence, for the finer granularity control, more signals (Precisely, RRC connection request, RRC connection setup, RRC Connection Setup complete) are wasted. + +NOTE 2: When a low priority cause value in the RRC connection request is used as the low priority MTC device indicator, the network may experience confusion in deciding the policy for the low priority normal UE and the low priority MTC device. The details of the argument is in S2-103122. + +#### 3. Rejecting connection requests by the SGSN/MME as per 6.22 (and S2-103120 for Mobile Terminated communication.) + +##### a. Pros: + +The mechanism can be implemented without any change on the RAN node. + +The SGSN/MME can consider various conditions (such as roaming restriction, group, APN etc.) in order to determine whether to accept or reject the request from the MTC device. + +##### b. Cons: + +Before the SGSN/MME receives the NAS message from the MTC device, the network and the MTC device exchange the many signals (RRC signals for connection establishment, S1AP/RNANP message from the RAN to the SGSN/MME.) All these exchanged signals may be wasted just for rejecting the request from the MTC device. + +Congestion/overload control solutions proposed so far describe mechanisms that start to block signalling traffic or transactions when the system load reaches certain thresholds. There are three basic solutions: + +- Broadcast based solutions that prevent any access from MTC (or low priority) devices, and +- reject based solutions that imply some MTC device individual signalling. The reject based solution may be further categorised into: + - Reject by RAN, and + - Reject by CN nodes. + +Table 5.12.3.4-1 collects pros and cons for the three solution alternatives: broadcast based, reject by RAN and reject by SGSN/MME. The reject by GGSN/PGW can be considered as covered by the reject by SGSN as the functionality is similar and the rejection to the MTC device is finally the SGSN/MME may need to send. + +**Table 5.12.3.4-1: Pros and Cons for the three solution alternatives** + +| | <b>Broadcast control</b> | <b>Reject by RAN</b> | <b>Reject by SGSN/MME</b> | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| <b>pros</b> | Reduces load without any signalling with the device. It is the only solution that allows for preventing any signalling from MTC devices. Also suitable for cell/RAN node overload control. | Reduces load by rejecting already the first RRC message of the device (assuming proper criteria are available with first RRC message, like the proposed "low priority" indication). Also suitable for cell/RAN node overload control. RAN node can quickly start to reduce load by rejection. Suited for SGSN/MME MTC load control on higher granularity as RAN based reject can be started by SGSN/MME, e.g. as specified for MME overload. Load control granularity per SGSN/MME, per shared PLMN and also per low/high priority is possible. | Reduces load by rejecting NAS requests (MM or SM) of the device (ideally rejecting already the first message when proper criteria are available) SGSN/MME can have group/APN information, and therefore suited for controlling load with group/APN granularity. Load control granularity per certain PLMN or roaming conditions and also per low/high priority are also possible, specifically when it can be derived from already existing signalling. | +| <b>cons</b> | Reacts slower on load than reject solutions as it depends on frequency of sending and reading the control information. (How slow in absolute figures?) Less suited for reducing load per group/APN or per CN node as extensive broadcast information seems needed to indicate a group/APN. | Less suited for reducing load per group/APN. Requires device individual RRC signalling. Some interference with NAS timers and repetitions might occur when the proposed long wait timers are longer than the NAS timers. | Requires certain amount of device individual signalling: first RRC setup needs to be performed and at least some initial NAS signalling before the SGSN/MME can reject. Without further enhancements the SGSN/MME needs more signalling before it can reject an attach, e.g. get subscriber data from HSS, to know the group/APN of the device. | +| <b>others</b> | Additional mechanism may be needed to avoid that all devices start immediately when the broadcast indication changes to allow access. | Some new identity handling is proposed (e.g. indicate IMSI when re-selecting PLMN) to provide specific criteria for deciding on reject. RNC could also reject based on establishment cause, e.g. "background traffic". | NAS/MM (e.g. attach) may need extensions to allow for rejecting already first NAS message Some delay/wait mechanism is needed in addition (e.g. the proposed back-off timer) to prevent frequent retry from device If SGSN/MME stores all MM contexts from MTC devices after detach then the SGSN/MME may have sufficient information to reject group/APN based already with initial NAS message. | + +The only safe method to block MTC signalling load without impacting other traffic is the broadcast mechanism. As it is hard to predict whether reject mechanisms alone would be able to manage all potential situations it seems useful to adopt a broadcast solution. The granularity would be rather high so that some reject solution may be needed in addition to perform a more fine granular control. + +Broadcast control granularity could be all MTC or with some high granularity it could prevent access from devices that change PLMN. Allowing access again may cause many devices to access at the same time. Some load distribution mechanism may be needed in addition. + +The adoption of a reject mechanism in addition to a broadcast mechanism seems useful for more fine granular load control. As the RAN reject seems not suited to control based on group/APN the SGSN/MME based rejection may be used in addition to it. Also here some wait time is needed before the UE is allowed to retry. + +However, as the eNodeB reject mechanism exists already it may be enhanced with reasonable effort to reduce an MME's MTC load. The MME could request the eNodeB to reject MTC devices before it request to reject all UEs besides emergency services. Applying this mechanism for GERAN/UTRAN may need further study. + +## 5.13 Key Issue - MTC Identifiers + +### 5.13.1 Use Case Description + +The amount of MTC Devices is expected to become 2 orders of magnitude higher than the amount of devices for human to human communication scenarios. This has to be taken into account for IMSI, IMEI and MSISDN. Regulatory bodies indicate shortages of IMSIs and MSISDNs. + +The MTC Feature PS Only in TS 22.368 [2] includes a requirement that PS Only subscriptions shall be possible without an MSISDN. In principle an MSISDN is not used in any of the PS based signalling procedures. However, it will have to be assured that all PS procedures indeed work and subscriptions can be uniquely identified without providing an MSISDN. Furthermore, TS 22.368 [2] specifies that remote MTC Device configuration shall be supported for PS only subscriptions without an MSISDN assigned. Current remote MTC Device configuration solutions (i.e. Device Management and Over-the-Air configuration) are based on SMS, which assumes the use of MSISDNs. So a solution to support remote MTC Device configuration that does not require the use of MSISDNs is needed. + +The identifiers can be categorised into: + +- Internal Identifiers: used within the 3GPP system to identify a UE using a subscription (or the subscription itself e.g. when the UE is not registered). +- External Identifiers: used from outside the 3GPP system (e.g. at the MTCsp interface), to refer to a UE using a subscription (or the subscription itself e.g. when the UE is not registered). + +### 5.13.2 Required Functionality + +- It shall be possible to uniquely identify the ME. + +NOTE 1: This requirement relates to the ME which is generally identified by the IMEI. + +- It shall be possible to uniquely identify the UE using a subscription or the subscription itself. + +NOTE 2: The two requirements above also apply to human-to-human communications. However, for Machine-Type Communication identifiers will have to be able to cater for a number of identifiers up to two orders of magnitude higher than for human-to-human communications. + +- It shall be possible to use the following identifiers: + 1. IMSI, for internal usage within the 3GPP operator domain, and either + 2. E.164 MSISDN, for usage outside the 3GPP operator domain, or + 3. Unique identifier (e.g. FQDN), other than E.164 MSISDN, for usage outside the 3GPP operator domain. + +NOTE 3: Use of IMSI outside the 3GPP operator domain is an operator option (i.e. not subject to standardization) + +- If no (unique or common) MSISDN is assigned to a PS only subscription, the Internal Identifier (IMSI) shall be used as charging identifier. +- It shall be possible to associate one or more External Identifiers to the same Internal Identifier (e.g. several MSISDNs associated with the same IMSI). + +- Globally unique External Identifiers shall be supported for identifying UEs used for MTC that must be globally reachable (i.e. irrespective of which mobile operator owns the subscription) +- Operator specific External Identifiers (e.g. based on a private numbering plan) may be supported for identifying UEs used for MTC that have to be reachable only from the operator domain to which they are subscribed. +- The Internal Identifier shall be globally unique. +- Remote MTC Device configuration shall still be supported for subscriptions without an MSISDN. + +NOTE 4: Current remote MTC Device configuration solutions (i.e. Device Management and Over-the-Air configuration) are based on SMS, which assumes the use of MSISDNs. + +### 5.13.3 Evaluation + +## 5.14 Key Issue - Potential overload issues caused by Roaming MTC devices + +### 5.14.1 Use Case Description + +#### 5.14.1.1 What is the likelihood of M2M devices being roamers? + +In many cases (possibly the vast majority of cases) M2M devices will be used as part of a contract between one network operator (or network operator group with operations in multiple countries) and a large (possibly multi-national) company. + +##### *Coverage:* + +One of the key aspects that the operator will "sell" to the corporate customer is coverage. The use of "national roaming" obviously improves geographic coverage, but, its utilisation poses several challenges. An obvious solution to some of these national roaming challenges is for the operator to use "international roaming", either with a SIM from a different company within the same operator group, or, by using a SIM with "non-geographic" Mobile Country Code (e.g. MCC 901). + +Both of these options appear to already be in use, and are likely to be used widely in the future. + +##### *Multi-national customer:* + +Typically a multi-national customer will want to be delivered devices and choose in which country they are used. This inevitably leads to 'roaming' for their M2M devices. + +This situation is exacerbated by the use of factory "pre-fitted" SIMs. + +##### *Chance of Roaming Summary:* + +Overall, for devices sending low data volumes, there seem to be some strong reasons to expect most devices to be camped on a PLMN that is different to their IMSI's PLMN-ID, i.e. it may be that MOST M2M devices ARE ROAMING. + +#### 5.14.1.2 What are the consequences if most M2M devices are roaming? + +##### 5.14.1.2.1 Commercial arrangements + +Currently, most roaming agreements seem to implicitly assume some degree of balance/mutual benefit between the two operators. + +However, the subscribers of a network with a non-geographic Mobile Country Code are "all outbound roamers". And, the outbound roaming M2M devices are likely to generate very little traffic per device but still generate 'normal' levels of signalling and occupy 'normal' levels of VLR space. This "imbalance" might lead to the VPLMN operator being "unhappy". + +At the moment the only 3GPP-standards consequence of this would seem to be, that, we should ensure that the VPLMN has sufficient counters and capabilities to measure the level of "imbalance". + +#### 5.14.1.2.2 Devices that only power-up/attach when they need to do something + +If the M2M devices with foreign SIMs are normally not-attached to the network, then the VPLMN may only discover that these devices are in its territory when an event happens that causes the device to report back to the "MTC server". + +If a large set of such devices get activated by the same event (e.g. burglar alarms with foreign SIMs responding to a power cut or earthquake) then the VPLMN may suddenly get loaded by huge numbers of M2M devices: yet, potentially, the VPLMN would have been totally unaware of the existence of (millions of) these devices. + +Without prior knowledge of the number of inactive devices in the geographic area, network capacity planning is close to impossible. + +Such scenarios lead to the need for a VPLMN to be able to "survive" a potentially massive increase in unplanned/unpredicted signalling load. + +Some "tools" in the 3GPP standards may be needed to help manage this scenario. + +#### 5.14.1.2.3 Failure of "M2M partner" network + +It is likely that many M2M "roaming" devices will be using the network of a PLMN within the same operator group, but not necessarily the same operator within a certain country. + +For example, "OperatorX UK" might have a contract to supply 5 million electricity meters in the South of England. To 'enhance' their coverage area, they could equip them with SIM cards from their partner network "OperatorX in country A". + +But what then happens if the "OperatorX UK" network fails? These devices will NOT have "OperatorY UK" as a forbidden PLMN and so, when their periodic update fails, they are likely to change network, and, over a potentially fairly short time period, up to 5 million new devices appear on the "OperatorY UK" network. + +Again, we need "tools" in the 3GPP standards to permit networks to "survive" these situations. + +### 5.14.2 Required Functionality + +Tools are required to protect a VPLMN from any overload caused by the failure of one (or more) other networks in that country. However, it should be noted that a degree of co-operation from the HPLMN is still likely to be required. + +The following tools needed to be *investigated* further: + +- a) counters/alarms (on e.g. a per MCC and MNC basis) to detect unusual increases in the number of roaming devices in a VPLMN; +- b) the ability to remotely configure M2M devices to indicate that they are "low value" M2M devices; +- c) signalling from the UE to the RAN to permit the IDNNS function in the RAN to steer "low value" M2M devices towards Core Network nodes with large VLR/storage capacity and/or large processing capacity, especially in the CS domain; +- d) "access class barring" functionality that can be used to bar e.g.: + - low value" M2M devices that are not on their HPLMN or a PLMN in the (U)SIM's preferred PLMNs list; + - low value" M2M devices that are not on their HPLMN or an Equivalent HPLMN; + - low value" M2M devices that are not on their HPLMN; + - low value" M2M devices; +- e) control of the "more preferred PLMN background search timer" so that M2M devices do not return too rapidly to a failed PLMN, and/or do not scroll through multiple different PLMNs in that country; +- f) minimising M2M device to network signalling at inter-PLMN change, e.g. by using Attach rather than RAU/TAU and using IMSI rather than a temporary ID; + +- g) slowing down the rate at which "low value" M2M devices detect network failure, e.g. by having mechanisms to give "low value" M2M devices relatively long CS and PS domain periodic update timers; +- h) modifications to the existing specification of how the M2M device reacts to some MM/GMM/EMM reject cause values such as "IMSI unknown in HLR"; "illegal ME"; and "PLMN not allowed"; +- i) inclusion of a "low value" M2M device indicator in the M2M device to RAN signalling to permit the RAN to provide special handling to such devices in times of congestion (e.g. by rejecting them with a back off time); +- j) inclusion of a "low value" M2M device indicator in the M2M device to Core Network signalling to permit the CN to provide special handling to subsets of such devices in times of congestion (e.g. by checking the IMSI and/or APN and/or MTC group ID and rejecting certain groups with a back off time); +- k) specification of new MM/GMM/EMM functionality (e.g. reject cause values or "abuse" of the Accept message) that causes new UE behaviour (e.g. a cause value that says "LA not allowed, but stay in this LA for X deci-hours before searching for another PLMN", or, sending RAU accept with a 20 minute PRU timer value and locally loading a "no services permitted" subscription into the SGSN's database); +- l) modification of signalling to/from the EIR to permit the EIR e.g. to allow rejection/parking of an M2M device without overloading the inter-operator signalling links; +- m) the specification of a new Network Mode of Operation that permits the VPLMN to offer NMO=II to their existing devices while minimising signalling from "low value" M2M devices by getting those M2M devices to use NMO=I. + +### 5.14.3 Evaluation + +#### 5.14.3.1 Evaluation for M2M "access class barring" functionality + +The "PLMN type" option from "Solution - Broadcasting MTC Access Control by RAN", see clause 6.28, defines the required mechanisms for barring MTC Devices based on their current PLMN type (e.g. not in HPLMN, PLMN in the (U)SIM's preferred PLMNs list, Equivalent HPLMN, etc). Given this solution is not dependent on the implementation of MTC Groups and can use a very efficient encoding of the PLMN type to take advantage of spare bits in pre-existing system information messages, it provides for a low impact on existing 3GPP standards and products that may be feasible in Rel-10. + +NOTE: The detailed "PLMN type" indication parameters should be specified in stage 3. + +Editor's note: Text to be added for remaining functionality requirements + +## 5.15 Key Issue - Low Power Consumption + +### 5.15.1 Use case description + +For some types of MTC Devices, operation with very low power consumption is a critical requirement. For some devices, such as those used for gas metering and animal, cargo, prisoner, elderly and children tracking, low power consumption is critical because it is not easy to re-charge or replace the battery. This creates the need for system enhancements that would minimize the power consumption of MTC Devices. + +### 5.15.2 Required Functionality + +It shall be possible to save battery energy consumption for UEs. + +### 5.15.3 Evaluation + +--- + +## 6 Solutions + +Editor's note: Solutions to all Key Issues are listed here. Under Problem Solved / Gains Provided, please list the Key Issue(s) that are addressed by the solution. + +## 6.1 Solution - FQDN Identifier Solution + +### 6.1.1 Problem Solved / Gains Provided + +See Key Issue 5.2 "MTC Devices communicating with one or more MTC Servers". + +### 6.1.2 General + +MTC devices relying on IP communications that need to be reachable for mobile terminated communications are assigned a static unique "host name" (i.e. an FQDN identifier specific to the MTC device). The "host name" is assigned in addition to any EPS-level identity (such as IMSI or MSISDN) of the MTC device. + +NOTE 1: The "host name" may be defined via the EPS-level identity. For instance, assuming that the MTC device has an IMSI as the EPS-level identity, the "host name" can be defined as "mtc.IMSI.pub.3gppnetworks.org". The exact definition of the "host name" is a Stage 3 matter. + +The "host name" is used as the primary addressing identifier for mobile terminating communications. + +Upon attachment to the PLMN the MTC device that relies on IP communications is assigned dynamic IP address. In roaming scenarios the dynamic IP address may be assigned in the Visited PLMN. + +The association between the "host name" and the dynamically assigned IP address is stored in the authoritative DNS server in the Home PLMN. + +When the MTC device is assigned a dynamic IP address, the authoritative DNS server is kept up-to-date using DNS Update mechanisms. + +The entity performing DNS updates is preferably located in the Home PLMN in order to reduce the number of trusted interfaces to the DNS server. + +The call flow depicted in Figure 6.1.2-1 describes how MT communication with MTC devices inside public IP address space works in step by step fashion: + +![Sequence diagram showing the call flow for MT communication with an MTC device inside public IP address space. The diagram involves six entities: MTC device, MME, SGW/PGW, HSS/AAA, DNS, and MTC server. The sequence starts with the MTC device performing an EPS Attach procedure (Step 1). The SGW/PGW then sends a Notify Req/Rsp to the MME (Step 2). The MME sends a DNS Update (FQDN, 'D') to the HSS/AAA (Step 3). The HSS/AAA sends a DNS Update (FQDN, 'D') to the DNS server (Step 4). The MTC server sends a DNS Query (FQDN) to the DNS server (Step 5). The DNS server sends a DNS Response ('D') to the MTC server (Step 6). The MTC server then sends a packet to the IP address '@=](1b3c088f23921d4eeb45ffc05586e59b_img.jpg) + +``` + +sequenceDiagram + participant MTC device + participant MME + participant SGW/PGW + participant HSS/AAA + participant DNS + participant MTC server + + Note right of MTC device: 1. EPS Attach procedure (3GPP TS 23.401); assignment of public address "D" + MTC device->>MME: + MME->>SGW/PGW: 2. Notify Req/Rsp ("D") + SGW/PGW->>HSS/AAA: + HSS/AAA->>DNS: 3. DNS Update (FQDN, "D") + Note right of MTC server: 4. MTC server wishes to send MT message + MTC server->>DNS: 5. DNS Query (FQDN) + DNS->>MTC server: 6. DNS Response ("D") + Note right of MTC server: 7. Send packet to IP@="D" + MTC server-->>MTC device: 8. Packet delivered in EPS bearer + +``` + +Sequence diagram showing the call flow for MT communication with an MTC device inside public IP address space. The diagram involves six entities: MTC device, MME, SGW/PGW, HSS/AAA, DNS, and MTC server. The sequence starts with the MTC device performing an EPS Attach procedure (Step 1). The SGW/PGW then sends a Notify Req/Rsp to the MME (Step 2). The MME sends a DNS Update (FQDN, 'D') to the HSS/AAA (Step 3). The HSS/AAA sends a DNS Update (FQDN, 'D') to the DNS server (Step 4). The MTC server sends a DNS Query (FQDN) to the DNS server (Step 5). The DNS server sends a DNS Response ('D') to the MTC server (Step 6). The MTC server then sends a packet to the IP address '@= + +**Figure 6.1.2-1: Call flow for MT communication with MTC device inside public IP address space** + +1. MTC device performs the EPS Attach procedure as described in TS 23.401 [5]. As part of the EPS Attach procedure the MTC device is assigned a public IP address, referred to here shortly as "D". The S5/S8/S11 Create Session Response message (not shown) is used to convey "D" from the PGW to the MME. + +NOTE 2: For IPv6 it is assumed that the MTC device relies on DHCPv6 for stateful address allocation, or uses the solution described in clause 6.49. + +2. As part of the previous step, or at the end of the EPS Attach procedure, the MME notifies the HSS/AAA with "D". Currently there is no direct interface between the PGW and the HSS/AAA, which is why the Notification is sent from the MME. + +NOTE 3: If an interface between the PGW and the HSS/AAA is defined in the future, the MTC device's IP address "D" can be notified directly without passing through the MME. + +3. The association between the "host name" of the MTC device and the dynamically assigned IP address "D" is stored in the authoritative DNS server in the Home PLMN. The HSS/AAA sends a DNS Update to the authoritative DNS server. +4. At some point the MTC server wishes to send a Mobile terminated (MT) message to the MTC device whose unique identifier is FQDN. +5. MTC server sends a DNS query that eventually reaches the authoritative DNS server. +6. The DNS response of the authoritative DNS server includes "D". +7. MTC server sets the Destination IP address in the packet it wishes to send to the MTC device to "D". +8. The PGW hosting the MTC device's public IP address delivers the packet to the MTC device via an appropriate EPS bearer. + +The proposed solution also applies to GERAN and UTRAN devices, in which case MME and PGW are replaced with SGSN and GGSN. + +It also applies to MTC device-to-device communications, where both MTC devices are located inside public IP address space. In this case it is the source MTC device itself that performs the DNS query to resolve the FQDN of the target MTC device. + +**Editor's note:** If the MTC device has multiple PDN connections, it is FFS which IP address the MTC Server selects for sending packets to the MTC device. + +NOTE 4: Further details on mobile terminated communications to MTC devices inside a private IPv4 address space are described as a separate key issue, see clause 5.3 "IPv4 Addressing." + +### 6.1.3 Impacts on existing nodes or functionality + +For IP address assignment via DHCPv4, the PGW needs to notify the SGSN/MME of the assigned IPv4 address outside of the Attach procedure (e.g. via the Bearer Modification procedure). + +SGSN/MME needs to notify the HSS of the device's IP address "D" (e.g. new parameter in the Notify Request message). + +HSS need to perform DNS updates of the authoritative DNS server that stores the association between the "host name" of the MTC device and the dynamically assigned IP address "D". + +### 6.1.4 Evaluation + +Benefits: + +- Low impact on existing Core Network nodes; +- Generic IP-level solution that does not rely on application-level identifiers (e.g. SIP URI); +- Works in all scenarios (non-roaming, roaming with home routed traffic, roaming with local breakout); +- The solution does not rely on alternative communication channels (e.g. SMS) for delivery of a "push" stimulus; +- Works also for device-to-device communication; +- Compatible with the solution for Mobile Terminated communication into private IPv4 address space (refer to clause 6.18). + +Drawbacks: + +- For IPv6 the solution requires stateful address configuration via DHCPv6. + +## 6.2 Solution - Transfer of device trigger or data via SMS + +### 6.2.1 Problem Solved / Gains Provided + +See clause 5.4 "Key Issue – Online Small Data Transfer" and clause 5.8 "Key Issue - MTC Device Trigger". + +### 6.2.2 General + +MTC Devices with low data usage send or receive data utilizing SMS via SGSN/MSC or SMS over SGs. The MTC Server connects with the SM-SC or behaves as a SM-SC (e.g. has an integrated SM-SC) to send or receive MTC service data or send device trigger message encapsulated in short message. SMS transfer is suited for MTC users that infrequently transfer amounts of data that can be carried by SMS(s) and where SMS transfer generates less system load compared to the usage of packet data bearers. + +**Editor's note:** The impact of storing and forwarding nature of SMS delivery on MTC service is FFS. + +The SGSN/MME is aware that the MTC Device has the low data usage feature (e.g. the usage of that feature is known from the HLR/HSS subscription data). The MME and MTC Device will not create any EPS bearer for MTC service. + +**NOTE 1:** In the current pre Rel-11 E-UTRAN it is not possible to establish NAS signalling connection without establishing at least the default EPS bearer. Clause 6.52 describes some potential optimisations to SMS transmission without establishing the EPS bearer. + +**NOTE 2:** According to stage 1 requirements the small data upper limit can be around 1000 octets. + +**Editor's note:** Need to address how this solution can support subscription and operator policy on data size. + +**Editor's note:** The frequency of small data transmissions that can be supported with this solution needs to be described. + +### 6.2.3 Impacts on existing nodes or functionality + +- a) Extensive use of SMS for transmission of small data puts additional load on control plane nodes (e.g., MME, SGSN, MSC Server, SMS-GMSC, SMS-IWMSC, SMS-SC) in order to transport user data. + +### 6.2.4 Evaluation + +## 6.3 Solution - Paging within configured area + +### 6.3.1 Problem Solved / Gains Provided + +See clause 5.6 "Key Issue – Low Mobility". + +### 6.3.2 General + +For MTC devices that do not move frequently or move only within a small area, the paging area (e.g. TAI, CGI, ECGI) is configured in the HLR/HSS as a part of the subscription of the MTC subscriber. The SGSN/MME stores the paging area as part of the subscriber data as received from HLR/HSS. + +During the mobile terminated service, the SGSN/MME pages the MTC Device within the specific area. The configured paging area is assumed to be smaller than typical paging areas for other UEs. Thereby paging traffic can be reduced. + +An issue might be needed for reconfiguring subscription data when the network reconfigures some cells or the MTC Device is roaming. + +### 6.3.3 Impacts on existing nodes or functionality + +### 6.3.4 Evaluation + +## 6.4 Solution - Paging stepwise + +### 6.4.1 Problem Solved / Gains Provided + +See clause 5.6 "Key Issue – Low Mobility". + +### 6.4.2 General + +For the MTC Device with low mobility, the SGSN/MME stores the RAI/TAI(s) like for any other UE and in addition the last known cell (i.e. CGI/ECGI) or last known service area (i.e. SAI) as provided by RAN in S1/Iu/Gb signalling. For low mobility MTC devices the MME preferentially includes only one TAI for TAI List in the accept message. + +During the mobile terminated service, the SGSN/MME may page stepwise, e.g. first in the last known cell (i.e. CGI/ECGI) or last known service area (i.e. SAI) and if there is no response the SGSN/MME pages the MTC Device in a wider area, i.e. within the RAI or TAI List allocated to the MTC Device. + +### 6.4.3 Impacts on existing nodes or functionality + +### 6.4.4 Evaluation + +## 6.5 Solution - Paging within reported area + +### 6.5.1 Problem Solved / Gains Provided + +See clause 5.6 "Key Issue – Low Mobility". + +### 6.5.2 General + +For the MTC Device with fixed location (i.e. not move normally), which can be deduced by the SGSN/MME when receiving the same area identifier (e.g. CGI, ECGI, SAI, RAI or TAI) via S1/Iu/Gb signalling during a predefined period or receiving a explicit report from the MTC Device. The SGSN/MME stores the area identifier and pages the MTC Device within the specific area. + +When the MTC Device moves (e.g. for maintain purpose), the SGSN/MME detects the moving and pages within the new area which is reported by RAN or by the MTC Device explicitly. + +### 6.5.3 Impacts on existing nodes or functionality + +### 6.5.4 Evaluation + +## 6.6 Solution - Triggering of non-attached MTC Devices based on location information provided by MTC User + +### 6.6.1 Problem Solved / Gains Provided + +See clause 5.8 "Key Issue - MTC Device Trigger". + +### 6.6.2 General + +With non-attached MTC Devices, the network has no knowledge of the location of the MTC Device. However, in many cases the MTC User does have knowledge about the location of the MTC Device. In these cases the MTC User can provide the PLMN with information on the location of the MTC Device. Based on that information the PLMN can then broadcast a trigger message in a relevant cell or group of cells. The MTC Device, while not attached, will still listen to the broadcast channel of the PLMN. + +A possible solution to broadcast the triggers may be by using the Cell Broadcast Service (CBS) as specified in TS 23.041. A Cell Broadcast Center (CBC) is under control of a mobile network operator and connected to the radio network i.e. to the BSCs in case of GSM and to the RNCs in case of UMTS. Connected to a CBC are one or more Cell Broadcast Entities (CBEs) which may originate CBS messages. A mobile network operator may make available the interface on the CBC to trusted 3rd parties to interconnect their CBE to the CBC of the mobile network operator. The MTC Devices are programmed to monitor a preset CB channel(s), even when they are not attached to the network, and have assigned a Unique Paging Identity (UPID). This way the MTC Server of the 3rd party is able to send CBS messages, including one or more UPIDs, to its MTC Devices in certain areas based on location information available in the MTC Server. But also other broadcast solutions (such as using the BCCH) can be considered to trigger the MTC Devices that are not attached to the network to attach and establish PDP/PDN connectivity. Solutions to reduce the amount of trigger request and trigger response messages to be transmitted through these broadcast solutions shall also be considered together. + +### 6.6.3 Impacts on existing nodes or functionality + +### 6.6.4 Evaluation + +## 6.7 Solution – Network access control by the PLMN + +### 6.7.1 Problem Solved / Gains Provided + +See clause 5.9 "Key Issue - Time Controlled"; clause 5.12, "Key Issue - Signalling Congestion Control". + +### 6.7.2 General + +The 3GPP network supports policing of the MTC Device's access to the network to prevent or allow (e.g. with specific charging) traffic to/from the network during unauthorized time periods. This may be accomplished as follows: + +- i) the operator provisions the access duration, grant time interval and forbidden time interval within the MTC subscription in the HLR/HSS; +- ii) the SGSN/MME receives the access duration, grant time interval and forbidden time interval periods from the HLR/HSS during the Attachment, Routing Area Update or Tracking Area Update procedure; +- iii) the SGSN/MME alters the grant time interval periods for MTC devices base on the value received from HLR/HSS or local operator policies, e.g. due to locally determined congestion overload conditions; + - a. SGSN/MME randomly determines a communication window within the grant time interval to improve uniform utilization of the network and reduce the chance of overload at the beginning or end of the grant time interval + +- b. The length of the communication window shall not be less than the Access Duration agreed between the MTC Subscriber and network operator, though it could be longer. +- iv) The SGSN/MME provides the communication window to the GGSN/P-GW, e.g. for the purpose of specific charging rate, or stopping data transmission when outside of the authorized time period. +- v) the SGSN/MME police the MTC Device's access to the network to prevent or allow (e.g. with specific charging) traffic to/from the network outside of the communication window. In the former case, the SGSN/MME reject the access request message (e.g. Attach Request or Tracking Area Update Request) or Service Requests initiated by the MTC device outside of the communication window. In all cases, the SGSN/MME indicates the communication window to the MTC device in the accept or reject message. + +**Editor's note:** It is FFS whether the network detaches MTC devices which remain attached to the network when the communication window expires. + +**Editors note:** It is FFS whether the network should let MTC Devices attach to the network outside of the communication window, but reject session management requests (e.g. Activate PDP Context Request in GPRS). + +The network may inform the MTC Devices of the communication window as follows: + +- i) the network provides the communication window to the MTC Server; the MTC Server distributes them to the MTC Devices via application level data; this approach has however the following drawbacks: + - a modification of the communication window may generate important signalling/traffic between the MTC Server and a possibly significant number of MTC Devices; + - MTC Devices' accesses to the network may be rejected or unduly charged until the MTC Server communicates them the communication window in-use in the Mobile Network. + +Or + +- ii) the SGSN/MME provides the communication window directly to the MTC Devices via NAS signalling, e.g. the first time the MTC Device registers to the network, and upon subsequent NAS signalling from the MTC Device if the communication window has changed. Following an operator's update of the communication window, the MTC Device might initiate NAS signalling outside of the new communication window. In that case, the network may either: + - reject the MTC Device request and return the new communication window in the response; or accept the first access outside of the new communication window and provide at that time the new communication window for subsequent accesses. E.g. the MME/SGSN could store both the 'Time-Intervals In-Use' (i.e. the last time intervals communicated to the MTC Device) and the 'Subscribed Time-Intervals' received from the HLR/HSS, and accept the first access of the MTC Device during the 'Time-Intervals In-Use'. + +In all cases where a communication window is supplied to the MTC Device, a timestamp is also provided to aid in synchronization. + +### 6.7.3 Impacts on existing nodes or functionality + +The HLR/HSS need to support provisioning of authorized time periods (i.e. access duration, grant time interval and forbidden time interval) in MTC subscriptions. + +The SGSN/MME needs to determine the communication window and grant time interval for MTC devices based on the value received from the HLR/HSS randomization or the local operator policies, e.g. due to locally determined congestion or overload conditions. + +The SGSN/MME needs to police the MTC Device's access to the network according to the authorized time periods. + +The SGSN/MME needs to provide the MTC Devices with the communication window and timestamp information in NAS signalling (if NAS signalling is used to inform MTC Devices of the communication window). + +The SGSN/MME needs to store both the new and last communication window. The SGSN/MME uses both the last and new communication windows to authorize the MTC device access to the network (e.g. reject or accept access request of the MTC Device) until the MTC device is updated with the new communication window. + +MTC Devices need to store the communication window and check the stored communication window before accessing the network. + +NOTE: This implies some time management and possibly buffering in the MTC Device to defer\* the sending of application traffic until the next authorized time period. + +Editor's note: PGW impact is still FFS. If some information needs to be transferred to PGW from MME/SGW, the information is expected to be sent using GTP if S5/S8-GTP is used, or using PCC infrastructure if S5/S8-PMIP is used. + +## 6.7.4 Evaluation + +Network Access control by the PLMN satisfies all requirements listed in clause 5.9.2. The access duration, grant time interval and forbidden interval are taken into consideration. Randomization occurs for access to prevent non-uniform utilization of the network and peaks in traffic. The VPLMN policy can be accommodated by means of applying local policy at the serving SGSN or MME. Use of the network can be enforced as required, either by detaching the MTC Device, refusing to allow it to attach or surcharging it, outside of the authorized time period. + +This solution introduces some complexity in that the MTC Device and the network must agree to time periods allowed for communication. This synchronization should not be needed in the ordinary case, as the communication window is retained by both the MTC Device and the network and can be reused. + +# 6.8 Solution - Introduction of a 3GPP MTC Service Abstraction Layer + +## 6.8.1 Problem Solved / Gains Provided + +See clause 5.11 "Key Issue – Decoupling the MTC Server from 3GPP Architecture". + +## 6.8.2 General + +### A) Add additional terminology to clause 3.1: + +**MTC Service Logic Components:** Business logic, configuration, data and other elements that implement an MTC Application and provide service to the MTC User. MTC Service Logic Components communicate with MTC Devices and may be deployed under or external to mobile network operator control. + +**3GPP MTC Service Abstraction Layer:** A functional entity that shares reference points with network elements in the 3GPP PLMN that are specified by 3GPP. The Service Abstraction Layer also exposes interfaces to PDNs to allow Service Logic Components to communicate with MTC Devices and services offered by mobile network operators to support interaction with MTC Devices. + +### B) Modify clause 4.3 Architecture Baseline, as follows: + +The end to end application, between the MTC device and the MTC server, uses services provided by the 3GPP system. The 3GPP system provides transport and communication services (including 3GPP bearer services, IMS and SMS) optimized for the Machine-Type Communication. For the purposes of 3GPP standardization, the MTC Server - including its internal state, operations and interfaces remain out of scope. + +As shown in Figure 4.3.1, MTC Device connects to the 3GPP network (UTRAN, E-UTRAN, GERAN, etc) via MTCu interface. MTC Device communicates with MTC Service Logic Components by means of an MTC Service Abstraction Layer or other MTC Devices using MTC Functions, 3GPP bearer services, SMS and IMS Application Servers provided by the PLMN. The MTC Server is an entity which connects to the 3GPP network via a Generic Service Layer API which remains out of scope of 3GPP standardisation. The MTC Service Abstraction Layer separates the MTC Service Logic Components from access specific interfaces. The MTC Service Abstraction Layer presents generic capabilities that map to concrete ones offered by the specific access. For example, communication capabilities in the 3GPP access are supplied using the MTCi/MTCsms interfaces and thus communicates with MTC Devices. MTC Server Logic Components may be outside of the operator domain or inside an operator domain. + +![Diagram of MTC Service Abstraction architecture. At the top is a large black rectangle with a white rectangle inside it. Below this, a light blue oval contains three small blue squares, each connected to the black rectangle by a vertical line. Below the oval is a single blue rectangle, which is connected to a stack of three blue rectangles at the bottom by a vertical line.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +Diagram of MTC Service Abstraction architecture. At the top is a large black rectangle with a white rectangle inside it. Below this, a light blue oval contains three small blue squares, each connected to the black rectangle by a vertical line. Below the oval is a single blue rectangle, which is connected to a stack of three blue rectangles at the bottom by a vertical line. + +**Figure 4.3-1: MTC Service Abstraction architecture** + +The reference points are listed as below: + +- MTCu:** It provides MTC Devices access to 3GPP network for the transport of user plane and control plane traffic. MTCu interface could be based on Uu, Um, Ww and LTE-Uu interface. +- MTCi:** It is the reference point that MTC Server uses to connect the 3GPP network and thus communicates with MTC Device via 3GPP bearer services/IMS. MTCi could be based on Gi, Sgi, and Wi interface. +- MTCsms:** It is the reference point MTC Server uses to connect the 3GPP network and thus communicates with MTC Device via 3GPP SMS. +- NOTE:** Both MTCi and MTCsms may be defined in such a way as to traverse the Service Abstraction Layer transparently. +- MTCsh:** It provides transport of service-related data (opaque to the 3GPP system) as well as user / subscriber related data. This reference point may be based upon Sh. + +Additional reference points between the 3GPP PLMN and the 3GPP MTC Service Abstraction Layer (e.g. for IMS) are FFS. + +It is FFS whether the 3GPP MTC service abstraction layer applies to pre-release 8 3GPP core networks and I-WLAN. + +### 6.8.3 Impacts on existing nodes or functionality + +### 6.8.4 Evaluation + +## 6.9 Solution - MTC Monitoring - General + +### 6.9.1 Problem Solved / Gains Provided + +See clause 5.10 "Key Issue – MTC Monitoring". + +### 6.9.2 General + +The MTC Monitoring events are configured in the HLR/HSS as part of the MTC subscription. The related criteria (e.g. the mapped IMSI/IMEI or the allowed location area) for reporting purpose are configured together with the event as well unless the event type is self explanatory, e.g., loss of connectivity. For those configured MTC Monitoring events, default action can be predefined as well, e.g. detaching the MTC Device when the IMEI and IMSI are not mapped. + +According to the requirement, the following MTC Monitoring events shall be configured in the HLR/HSS: + +1. Monitoring the association of the MTC Device and UICC. + +In this case, the HLR/HSS shall also configure the mapped IMSI and IMEI as the criteria together with this event. + +2. Monitoring the alignment of the MTC feature. + +In this case, the activated MTC features and the expected behavior for the special MTC Device, which is configured in the HLR/HSS as part of the MTC subscription, apply for this monitoring event. + +3. Monitoring change in the point of attachment. + +In this case, the allowed location information may also need to be configured as the criteria in the HLR/HSS (e.g. the Low Mobility feature is also activated for the MTC Device). + +4. Monitoring loss of connectivity. + +The network shall be able to detect such configured MTC monitoring events. The following alternatives (i.e. solution 1 to solution 3) can be used for the detecting purpose. The alternatives (solution 6.24 to solution 6.25) can be used for the MTC Event Reporting entity to get the MTC Server identity. + +**Editor's note:** It is FFS whether other alternatives can be used for the event detecting purpose. + +**Editor's note:** It is FFS whether MTC Device can be used for assisting in MTC monitoring. + +When such event is detected, the network shall be able to report to the MTC Server and/or MTC User. The following alternatives (solution 4 to solution 7) can be used for the reporting purpose. + +**Editor's note:** It is FFS for whether other alternatives can be used for the reporting purpose. + +When any event is detected, the network may also trigger MTC Monitoring actions accordingly, i.e. reduce services provided to the MTC Device or restrict access of the MTC Device or detach the MTC Device completely. When default action is predefined in the MTC subscription, the network triggers the default action (s). Dynamic action indication from the MTC server/user is not supported. + +When the MTC monitoring action "reduce services provided to the MTC device" is triggered, the SGSN initiates the PDP Context Modification procedure or the MME initiates the Modify Bearer Command to the Serving GW with included modified QoS parameters for the reduced service. + +When the MTC monitoring action "restrict access of the MTC Device" is triggered, in order to restrict the access of an MTC Device in idle mode, the SGSN rejects based on access restriction the Routing Area Update procedure or the MME rejects based on access restriction the Tracking Area Update procedure initiated by the MTC device. In order to restrict the access of an MTC Device in active mode, the SGSN or MME informs the RAN about the access restriction during the attach procedure or TAU/RAU procedure (the allowed location). The RAN restricts the handover only to allowed locations. + +When the MTC monitoring action "detach the MTC Device" is triggered, the SGSN or MME initiates the Detach procedure. + +**Editor's note:** How to handle the roaming scenario for this monitoring key issue is FFS. + +Editor's note: How to guarantee a MTC Monitoring action will not restrict network access to the MTC Device in a way that prevents the network or MTC Server to update the MTC Device to resolve the issue that triggered the MTC Monitoring action is FFS. + +## 6.10 Solution – SGSN/MME based detection + +### 6.10.1 Problem Solved / Gains Provided + +See clause 5.10 "Key Issue - MTC Monitoring" and 6.9 "Solution - MTC Monitoring - General". + +### 6.10.2 General + +For this solution, the SGSN/MME is responsible for detecting monitoring event, so the configured MTC monitoring events along with the related criteria and default action are downloaded from the HLR/HSS to the SGSN/MME during the Insert Subscription procedure along with the MTC subscription e.g. during Attach procedure. + +Basically, the SGSN/MME monitors the MTC Device behavior according to the MTC monitoring event trigger and performs corresponding action. The following table shows the procedures of the SGSN/MME. + +**Table 6.10.2-1: SGSN/MME based detection** + +| Monitoring Event | Procedures | +|-------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Monitoring the association of the MTC Device and UICC | The SGSN/MME asks for the MTC Device IMEI (e.g. Identity procedure).<br>2> The SGSN/MME checks whether the IMEI provided by the device is the same as the configured IMEI.<br>3> If not, the SGSN/MME shall trigger the reporting. | +| Monitoring the alignment of the MTC feature | The SGSN/MME checks whether the MTC Device behavior is aligned with the activated MTC features for the device.<br>2> If not (e.g. the MTC Device with low mobility feature performs RAU/TAU or handover procedure frequently), the SGSN/MME shall trigger the reporting. | +| Monitoring change in the point of attachment | The SGSN/MME checks whether there is change in point of attachment by comparing the location area information from RAN against the configured location area information from the HLR/HSS (e.g. the allowed location area information).<br>2> If yes, the SGSN/MME shall trigger the reporting. | +| Monitoring loss of connectivity | The SGSN/MME checks whether the MTC Device is offline.<br>2> If yes, the SGSN/MME shall trigger the reporting. | + +### 6.10.3 Impacts on existing nodes or functionality + +Impacts on HLR/HSS: + +- Support configuring and provisioning of monitoring related information (e.g. monitoring event, criteria, default action and etc) in MTC subscription. + +Impacts on SGSN/MME: + +- Support storing the monitoring related information (e.g. monitoring event, criteria, default action and etc) for a particular MTC Device. +- Support monitoring detecting behaviour. +- Support executing monitoring action, e.g. according to the pre-defined action. + +### 6.10.4 Evaluation + +All events can be detected and the signals to obtain the information for detecting the events can be optimized. + +However the load of the SGSN/MME may increase depending on the number of events and actions. + +## 6.11 Solution - HLR/HSS based detection + +### 6.11.1 Problem Solved / Gains Provided + +See clause 5.10 "Key Issue - MTC Monitoring" and 6.9 "Solution - MTC Monitoring - General". + +### 6.11.2 General + +For this solution, the HLR/HSS is responsible for detecting monitoring event with the assistance of other nodes. The MTC monitoring events along with the related criteria and default action are configured in the HLR/HSS. The HLR/HSS monitors the MTC Device behaviour according to the MTC monitoring event trigger and performs corresponding action. + +The following table shows the procedures of the HLR/HSS. + +**Table 6.11.2-1: HLR/HSS based detection** + +| Monitoring Event | Procedures | +|--------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| <b>Monitoring the association of the MTC Device and UICC</b> | 1.> The SGSN/MME provides the MTC Device IMEI together with the IMSI to the HLR/HSS.<br>2> The HLR/HSS checks whether the IMEI provided by the SGSN/MME is the same as the configured IMEI for the MTC Device.<br>3> If not, the HLR/HSS shall trigger the reporting. | +| <b>Monitoring the alignment of the MTC feature</b> | 1.> The HLR/HSS checks whether the MTC Device behaviour is aligned with the activated MTC features for the device.<br>2> If not (e.g. the HLR/HSS is aware that the MTC Device with low mobility feature changes the serving SGSN/MME), the HLR/HSS shall trigger the reporting. | +| <b>Monitoring change in the point of attachment</b> | 1.> The SGSN/MME reports the UE location (e.g. RAI, TAI, CGI, E-CGI and etc) to the HLR/HSS during MM procedure.<br>2> The HLR/HSS checks whether the UE location is allowed comparing to the configured location.<br>3> If not, the HLR/HSS shall trigger the reporting. | +| <b>Monitoring loss of connectivity</b> | 1.> The HLR/HSS checks whether the MTC Device is offline, e.g. the GGSN/P-GW information for the M2M APN is deleted, or receives Purge message.<br>2> If yes, the HLR/HSS shall trigger the reporting. | + +### 6.11.3 Impacts on existing nodes or functionality + +Impacts on HLR/HSS: + +- Support configuring monitoring related information (e.g. monitoring event, criteria, default action and etc) in MTC subscription. +- Support monitoring detecting behaviour. + +Impacts on SGSN/MME: + +- Support reporting location information to the HLR/HSS so that the HLR/HSS can detect a change by comparing with a subscribed location, or by comparing with the earlier stored location. +- Support registering GGSN/P-GW information to the HLR/HSS. To detect loss of connectivity quicker the SGSN/MME may need to configure very short periodic update timers, which increases MM signalling considerably. +- Support reporting MTC Device IMEI to the HLR/HSS. + +### 6.11.4 Evaluation + +Without any impacts on other nodes or signalling the HLR/HSS is able to detect when another device (IMEI) uses the UICC (IMSI). Also an action (e.g. cancel location or invalidate UICC) can be added and affects only the HLR/HSS. + +Monitoring of feature activation clearly requires additional functions in other nodes and related signalling. Also monitoring of the point of attachment by the HLR/HSS requires additional functions in other nodes and related signalling. + +Monitoring of the connectivity is not necessarily suited for the HLR/HSS as other HLR/HSS signalling is much less frequent. Detection of lost connectivity may require frequent indications to the HLR/HSS that connectivity exists. + +## 6.12 Solution - GGSN/P-GW based detection + +### 6.12.1 Problem Solved / Gains Provided + +See clause 5.10 "Key Issue - MTC Monitoring" and 6.9 "Solution - MTC Monitoring - General". + +### 6.12.2 General + +For this solution, the GGSN/P-GW is responsible for detecting monitoring event with the assistance of other nodes. The GGSN/P-GW obtains such information from the HLR/HSS, and monitors the MTC Device behavior according to the MTC monitoring event trigger and performs corresponding action. + +The following table shows the procedures of the GGSN/P-GW. + +**Table 6.12.2-1: GGSN/P-GW based detection** + +| Monitoring Event | Procedures | +|--------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| <b>Monitoring the association of the MTC Device and UICC</b> | 1.>2% The SGSN/MME provides the MTC Device IMEI together with the IMSI to the GGSN/P-GW during the bearer establishment procedure.<br>2> The GGSN/P-GW obtains the mapped IMEI and IMSI pair from e.g. the HLR/HSS.<br>3> The GGSN/P-GW checks whether the IMEI and IMSI provided by the SGSN/MME matches with the configured IMEI and IMSI pair.<br>4> If not, the GGSN/P-GW shall trigger the reporting. | +| <b>Monitoring the alignment of the MTC feature</b> | 1.>2% The GGSN/P-GW checks whether the MTC Device behaviour is aligned with the activated MTC features for the device.<br>2> If not (e.g. the GGSN/P-GW is aware that the MTC Device with low mobility feature changes location), the GGSN/P-GW shall trigger the reporting. | +| <b>Monitoring change in the point of attachment</b> | 1.>2% The GGSN/P-GW activates the MS Info Change Reporting Action when PDN connection is created.<br>2> The SGSN/MME reports the UE location (e.g. RAI, TAI, CGI, E-CGI and etc) to the GGSN/P-GW during bearer management procedure.<br>3> The GGSN/P-GW checks whether the UE location is allowed comparing to the configured location.<br>4> If not, the GGSN/P-GW shall trigger the reporting. | +| <b>Monitoring loss of connectivity</b> | 1.>2% The GGSN/P-GW checks whether the MTC Device is offline, e.g. the PDN connection for the M2M APN is deactivated.<br>2> If yes, the GGSN/P-GW shall trigger the reporting. | + +### 6.12.3 Impacts on existing nodes or functionality + +Impacts on HLR/HSS: + +- Support configuring monitoring related information (e.g. monitoring event, criteria, default action and etc) in MTC subscription. + +Impacts on SGSN/MME: + +- Support provisioning of monitoring related information (e.g. monitoring event, criteria, default action and etc) to the GGSN/P-GW. + +Impacts on GGSN/P-GW: + +- Support monitoring detecting behaviour. + +Impacts on PCRF/BBERF/PCEF: + +- Support provisioning of monitoring related information (e.g. monitoring event, criteria, default action and etc) to the P-GW, if PMIP is used over S5/S8. + +## 6.12.4 Evaluation + +With a proper subscription it can be prevented that a UICC can be used for anything else than the PDP/PDN connection provided for MTC. PDP/PDN connections are then only possible with the subscribed APN/P-GW/GGSN. The GGSN/P-GW can refuse PDP/PDN activation when the IMEI does not match. Compared to the HLR/HSS with the existing signalling the GGSN/P-GW cannot detach the device and also not invalidate the UICC. + +The GGSN/P-GW gets location information by setting "the MS Info Change Reporting Action" to start in the create session response to the MME and then the GGSN/P-GW can monitor change of the point of attachment using the existing procedure of the MS info change reporting procedure. + +If the MTC device has only one PDN connection, the P-GW may detect the monitoring of the connectivity by detecting the PDN disconnection, but when the multiple PDN connections is used, a PDN disconnection does not imply that the UE is detached and the connectivity with the UE is lost. Hence, the GGSN/P-GW is not necessarily suited for detecting lost connectivity. + +**Editor's note: Evaluation for PMIP based S5/S8 is FFS.** + +## 6.13 Solution - Reporting by SGSN/MME + +### 6.13.1 Problem Solved / Gains Provided + +See clause 5.10 "Key Issue – MTC Monitoring" and 6.9 "Solution – MTC Monitoring – General". + +### 6.13.2 General + +For this solution, the SGSN/MME is responsible for reporting the event. + +This solution can only be used for solution 1, i.e. the SGSN/MME is responsible for detecting (clause 6.10.) + +When the event is detected, the SGSN/MME reports towards the MTC Server + +### 6.13.3 Impacts on existing nodes or functionality + +The SGSN/MME needs to provide a new reference point for event reporting. + +### 6.13.4 Evaluation + +## 6.14 Solution - Reporting by HLR/HSS + +### 6.14.1 Problem Solved / Gains Provided + +See clause 5.10 "Key Issue - MTC Monitoring" and 6.9 "Solution - MTC Monitoring – General". + +### 6.14.2 General + +For this solution, the HLR/HSS is responsible for reporting the event. When the event is detected, the HLR/HSS reports towards the MTC Server. + +This solution can be used with solution 1 and 2, i.e. the SGSN/MME or the HLR/HSS is responsible for detecting. The following table shows the procedures for different detecting solution. + +**Table 6.14.2-1: HLR/HSS based Reporting** + +| <b>Detecting solution</b> | <b>Procedures</b> | +|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution 1: SGSN/MME based detection (clause 6.10) | <p>The SGSN/MME reports the event related information (e.g. event type, MTC Device identifier) to the HLR/HSS.</p> <p>The HLR/HSS forwards the warning notification request message to the MTC Server.</p> <p>3> The HLR/HSS receives the warning notification acknowledgement message from the MTC Server and forwards it to the SGSN/MME.</p> | +| Solution 2: HLR/HSS based detection (clause 6.11) | <p>The HLR/HSS sends the warning notification request message to the MTC Server, which includes the event related information (e.g. event type, MTC Device identifier).</p> <p>2> The HLR/HSS receives the warning notification acknowledgement message from the MTC Server.</p> | + +### 6.14.3 Impacts on existing nodes or functionality + +The path between the HLR/HSS and the MTC Server needs to be updated in order to exchange the warning notification. + +For solution 1, the message between SGSN/MME and the HLR/HSS e.g. Notify Request message, also needs to be updated. + +### 6.14.4 Evaluation + +## 6.15 Solution - Reporting by GGSN/P-GW + +### 6.15.1 Problem Solved / Gains Provided + +See clause 5.10 "Key Issue – MTC Monitoring" and 6.9 "Solution – MTC Monitoring – General". + +### 6.15.2 General + +For this solution, the GGSN/P-GW is responsible for reporting the event. The GGSN/P-GW reports towards the MTC Server. + +This solution can be used with solution 1 and 3, i.e. the SGSN/MME or the GGSN/P-GW is responsible for detecting. The following table shows the procedures for different detecting solution. + +**Table 6.15.2-1: GGSN/P-GW based Reporting** + +| <b>Detecting solution</b> | <b>Procedures</b> | +|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution 1: SGSN/MME based detection (clause 6.10) | <p>The SGSN/MME reports the event related information (e.g. event type, MTC Device identifier) to the GGSN/P-GW through S-GW via GTP-C message (e.g. reusing the Change Notification Request message) for GTP based S5/S8. Those information are transferred to PGW via PCC for PMIP based S5/S8.</p> <p>The GGSN/P-GW encapsulates and sends the warning notification request message to the MTC Server.</p> <p>3> The SGSN/MME receives the warning notification acknowledgement message from the MTC Server and forwards it to the SGSN/MME via the GTP-C path.</p> | +| Solution 2: GGSN/P-GW based detection (clause 6.12) | <p>The GGSN/P-GW sends the warning notification request message to the MTC Server, which includes the event related information (e.g. event type, MTC Device identifier).</p> <p>2> The GGSN/P-GW receives the warning notification acknowledgement message from the MTC Server.</p> | + +### 6.15.3 Impacts on existing nodes or functionality + +The GGSN/P-GW needs to be updated to communicate with the MTC Server. + +For solution 1, the GTP-C message also needs to be updated to transfer the warning notification. For PMIP based S5/S8, PCRF/BBERF/PCEF: shall support provisioning of monitoring related information (e.g. monitoring event, criteria, default action and etc) to the P-GW, if PMIP is used over S8. + +## 6.15.4 Evaluation + +# 6.16 Solution - Reporting by PCRF + +## 6.16.1 Problem Solved / Gains Provided + +See clause 5.10 "Key Issue – MTC Monitoring" and 6.9 "Solution – MTC Monitoring – General". + +## 6.16.2 General + +For this solution, the GGSN/P-GW or S-GW (PMIP based) is responsible for reporting the event via PCRF. The GGSN/P-GW/S-GW exchanges warning notification message with the PCRF, and the PCRF reports towards the MTC Server. + +This solution can be used with solution 1 and 3, i.e. the SGSN/MME or the GGSN/P-GW is responsible for detecting. The following table shows the procedures for different detecting solution + +**Table 6.16.2-1: PCRF based Reporting** + +| Detecting solution | Procedures | +|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution 1: SGSN/MME based detection (clause 6.10) | <p>The SGSN/MME reports the event related information (e.g. event type, MTC Device identifier) to the GGSN/P-GW through S-GW via GTP-C message (e.g. reusing the Change Notification Request message) for GTP based S5/S8. For PMIP based S5/S8, the SGSN/MME reports the event to the S-GW.</p> <p>For GTP based S5/S8 case, the GGSN/P-GW encapsulates and sends the warning notification request message to the PCRF by reusing the IP-CAN session modification request message.</p> <p>For the PMIP based S5/S8 case, the S-GW directly informs the PCRF by reusing Gateway Control session modification message.</p> <p>The PCRF reports the event to the MTC Server and obtains acknowledge from the MTC Server.</p> <p>The PCRF forwards the acknowledgement message to the GGSN/P-GW or S-GW (i.e. PMIP based S5/S8).</p> <p>5> The GGSN/P-GW or S-GW forwards the warning notification acknowledgement message to the SGSN/MME.</p> | +| Solution 2: GGSN/P-GW based detection (clause 6.12) | <p>The GGSN/P-GW sends the warning notification request message to the PCRF by reusing the IP-CAN session modification request message.</p> <p>The PCRF forwards the warning notification request message to the MTC Server, which includes the event related information (e.g. event type, MTC Device identifier).</p> <p>3> The PCRF receives the warning notification acknowledgement message from the MTC Server and forwards it to the GGSN/P-GW.</p> | + +## 6.16.3 Impacts on existing nodes or functionality + +The PCC related messages needs to be updated to transfer warning notification. + +For solution 1, the GTP-C message also needs to be updated to transfer the warning notification. + +For solution 2, PCC/BBERF/PCEF need to be updated to transfer the warning notification if PMIP is used over S8. + +NOTE: PCRF impacts are expected to be the same as GTP based S5/S8. + +## 6.16.4 Evaluation + +## 6.17 Solution – Allowed Time Period after TAU/RAU + +### 6.17.1 Problem Solved / Gains Provided + +See clause 5.9 "Key Issue –Time Controlled" and clause [TBD] "Key Issue – Extra Low Power". + +### 6.17.2 General + +The solution specified in this clause can be used for Extra-low power consumption, possibly together with Time-controlled MTC communications. + +The basic idea behind the solution is that downlink data transfer is only possible during an allowed time period after the MTC Device performed a TAU/RAU procedure. During that allowed time period the MTC server can communicate with the MTC device. After the allowed time period the MTC device may switch off the receiver and communication is not possible. + +**Editor's note:** It is FFS how this solution can cope with MTC Devices with low mobility, which may perform the TAU/RAU procedure very rarely. + +**Editor's note:** It is FFS how this solution can cope with MTC Devices performing TAU/RAU often during network-determined forbidden time interval (i.e., assuming that TAU/RAU is allowed during the forbidden time). + +After the MTC Device performs a TAU/RAU procedure the MTC Device may stay in power-up mode and inform the MTC Server that is available for communication so that the MTC Server(s) can forward all buffered traffic to the device. The MTC Device may be configured not to inform the MTC Server after every TAU/RAU procedure and thus reduce the frequency of allowed time periods based on the applicable time-controlled requirements. How often an allowed time period occurs is thus configurable. For example, the MTC Device may be configured to stay in power-up mode after a TAU/RAU and inform the MTC Server about its availability only between 1am – 5am every day. + +The MTC Server buffers downlink traffic for the MTC Device until the MTC Device informs the server that is ready for MTC communications. + +NOTE 1: Since this solution requires downlink traffic buffering, it is appropriate for time-tolerant MTC applications. + +The EPS network configures the MTC Device as to initiate allowed-time periods (after a RAU/TAU) according to the operator requirements and the MTC subscription options. Normally, downlink traffic does not occur outside of an allowed time period because the MTC Server(s) expect the device to send first a message to announce its availability for MTC communications. However, if downlink traffic for the MTC Device occurs outside an allowed time period, then the EPS network rejects/drops this traffic (i.e. the EPS network does not page the MTC Device outside the allowed time period). + +### 6.17.3 Impacts on existing nodes or functionality + +### 6.17.4 Evaluation + +## 6.18 Solution - MT Communication with NATTT + +### 6.18.1 Problem Solved / Gains Provided + +See clause 5.3 "Key Issue – Ipv4 Addressing". + +### 6.18.2 General + +What follows below are some additional considerations, beyond the FQDN Identifier Solution described in clause 6.1, when the assigned Ipv4 address belongs to the range of private Ipv4 addresses. Depicted in Figure 6.18.2-1 is a general MTC scenario with MTC device roaming in a VPLMN. The MTC device is assigned a private IP address (referred to as + +"D") that is hosted on the PGW node residing in the VPLMN (i.e. Local breakout). All the relevant EPS nodes are located in the VPLMN, except for the HSS/AAA node that resides in the HPLMN. + +The MTC server wishing to establish a Mobile Terminated (MT) communication may be owned by the HPLMN, by the VPLMN or by a third party. It is located somewhere on the Internet, which is why a Network Address Translation (NAT) device is needed at the public/private boundary. + +![Diagram of NATTT applied to the MTC context showing network nodes and interfaces across HPLMN and VPLMN domains.](977811d1c73b74f801be9f4c376694ca_img.jpg) + +``` + + graph TD + subgraph HPLMN + HSS[HSS/AAA] + DNS1[DNS NATTT enhanced] + end + subgraph VPLMN + subgraph EPC + MME + SGW_PGW[SGW/PGW] + end + HeNB + NATTT + subgraph Private_IP_Network [private IP network] + MTC_device[MTC device] + end + end + subgraph Public_IP_Network [public IP network] + DNS2[DNS NATTT enhanced] + MTC_server[MTC server] + end + + DNS2 --> DNS1 + DNS1 --> HSS + HSS -- S6a --> MME + MME -- S11 --> SGW_PGW + MME -- S1-mme --> HeNB + SGW_PGW -- S1-u --> HeNB + HeNB --> MTC_device + MTC_server -- UDP tunnel --> NATTT + NATTT --> SGW_PGW + NATTT --> DNS2 + +``` + +The diagram illustrates the network architecture for Mobile Terminated (MT) communications. It is divided into HPLMN (Home PLMN) and VPLMN (Visited PLMN) by a dashed red line. The HPLMN contains the HSS/AAA node and a DNS (NATTT enhanced) node. The VPLMN contains the EPC (MME and SGW/PGW), HeNB, and a NATTT device. The MTC server is located in the public IP network, connected to the NATTT device via a UDP tunnel. The NATTT device is connected to the SGW/PGW and a public DNS (NATTT enhanced) node. Interfaces shown include S6a (HSS to MME), S11 (MME to SGW/PGW), S1-u (SGW/PGW to HeNB), and S1-mme (MME to HeNB). The MTC device is located in a private IP network behind the HeNB. + +Diagram of NATTT applied to the MTC context showing network nodes and interfaces across HPLMN and VPLMN domains. + +**Figure 6.18.2-1: NATTT applied to the MTC context** + +In order to support MT communications to MTC devices inside private IP address space, the NAT device on the public/private boundary is replaced by a NATTT-capable device ([3]) i.e. a NAT device capable of UDP encapsulation for packets exchanged on the "public" side (i.e. to/from the MTC server), in addition to its traditional role as a NAT device. The reason for using UDP encapsulation (instead of simple IP-in-IP encapsulation) is because the NATTT device relies on a well-known UDP port number to identify the encapsulated packets. + +The call flow depicted in Figure 6.18.2-2 describes how MT communication with MTC devices inside private IP address space works in step by step fashion: + +![Sequence diagram showing the call flow for MT communication with an MTC device inside a private IP address space. The diagram involves seven participants: MTC device, MME, SGW/PGW, HSS/AAA, DNS, NATTT, and MTC server. The sequence of messages is: 1. EPS Attach procedure (TS 23.401) resulting in private IP 'D' and public IP 'N'; 2. MME notifies HSS/AAA of 'D' and 'N'; 3. HSS/AAA sends a DNS Update to the DNS server; 4. MTC server wants to send an MT message; 5. MTC server sends a DNS Query to the DNS server; 6. DNS server responds with 'D' and 'N'; 7. MTC server encapsulates a UDP packet with outer IP 'N' and inner IP 'D'; 8. NATTT decapsulates the packet, leaving inner IP 'D'; 9. The packet is delivered to the MTC device via an EPS bearer.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` + +sequenceDiagram + participant MTC device + participant MME + participant SGW/PGW + participant HSS/AAA + participant DNS + participant NATTT + participant MTC server + + Note right of MTC device: 1. EPS Attach procedure as in TS 23.401; assignment of "D" and "N" + MME->>HSS/AAA: 2. Notify Req/Rsp ("D", "N") + HSS/AAA->>DNS: 3. DNS Update (FQDN, "D", "N") + Note right of MTC server: 4. MTC server wishes to send MT message + MTC server->>DNS: 5. DNS Query (FQDN) + DNS->>MTC server: 6. DNS Response ("D", "N") + MTC server->>NATTT: 7. UDP encapsulated packet (outer@="N", inner@="D") + NATTT-->>SGW/PGW: 8. Decapsulated packet (IP@="D") + SGW/PGW-->>MTC device: 9. Packet delivered in EPS bearer + +``` + +Sequence diagram showing the call flow for MT communication with an MTC device inside a private IP address space. The diagram involves seven participants: MTC device, MME, SGW/PGW, HSS/AAA, DNS, NATTT, and MTC server. The sequence of messages is: 1. EPS Attach procedure (TS 23.401) resulting in private IP 'D' and public IP 'N'; 2. MME notifies HSS/AAA of 'D' and 'N'; 3. HSS/AAA sends a DNS Update to the DNS server; 4. MTC server wants to send an MT message; 5. MTC server sends a DNS Query to the DNS server; 6. DNS server responds with 'D' and 'N'; 7. MTC server encapsulates a UDP packet with outer IP 'N' and inner IP 'D'; 8. NATTT decapsulates the packet, leaving inner IP 'D'; 9. The packet is delivered to the MTC device via an EPS bearer. + +**Figure 9.18.2-2: Call flow for MT communication with MTC device inside private IP address space** + +1. MTC device performs the EPS Attach procedure as described in TS 23.401 [5]. As part of the EPS Attach procedure the MTC device is assigned a private IP address, referred to here shortly as "D". Also as part of this procedure, the PGW node returns the public IP address of the NATTT device ("N") through which the private address "D" is reachable. If there are several NATTT devices on the border of the private IP network, the PGW selects any that provides access to the private address "D". The S5/S8/S11 Create Session Response message (not shown) is used to convey both "D" and "N" from the PGW to the MME. +2. As part of the previous step, or at the end of the EPS Attach procedure, the MME notifies the HSS/AAA with "D" and "N". Currently there is no direct interface between the PGW and the HSS/AAA, which is why the Notification is sent from the MME. +3. The HSS/AAA sends a DNS Update to the authoritative DNS server in order to associate "D" and "N" with the DNS record for the MTC device (the latter being referenced via its unique FQDN). This requires a new type of DNS record. +4. At some point in time the MTC server wishes to send a Mobile terminated (MT) message to the MTC device whose unique identifier is FQDN. +5. MTC server sends a DNS query that eventually reaches the authoritative DNS server. +6. The DNS response of the authoritative DNS server includes "D" and "N". +7. MTC server performs UDP encapsulation of the IP packet it wishes to send to the MTC device. The destination IP address in the outer IP header is set to "N". The destination IP address in the inner IP header is set to "D". The UDP port in the UDP encapsulation header is set to a well known value, as described in [3]. The source IP address in both the inner and outer IP headers is set to the public IP address of the MTC server. +8. The NATTT device identifies the packet as a NAT tunnelled packet because it arrives on a well-known UDP port. It strips off the outer IP/UDP header and forwards the inner IP packet on the private IP network. +9. The inner IP packet reaches the PGW hosting the MTC device's private IP address. The PGW delivers the packet to the MTC device via an appropriate EPS bearer. + +The proposed solution also applies to GERAN and UTRAN devices, in which case MME and PGW are replaced with SGSN and GGSN. + +It also applies to MTC device-to-device communications, where either or both MTC devices are located inside private IP address space. In this case it is the source MTC device itself that performs the DNS query to resolve the FQDN of + +the target MTC device (i.e. to obtain the private IP address of the target MTC device, as well as the public address of the NATTT device in the target network). It is also the source MTC device that performs the packet encapsulation. + +NOTE: It is FFS how to prevent unwanted traffic from being sent to the MTC device. + +### 6.18.3 Impacts on existing nodes or functionality + +The PGW needs to notify the SGSN/MME of the NAT device's public address "N" (e.g. new parameter in the Create Session Response message). + +For IP address assignment via DHCPv4, the PGW needs to notify the SGSN/MME of the assigned IPv4 address outside of the Attach procedure (e.g. via the Bearer Modification procedure). + +SGSN/MME needs to notify the HSS of the MTC device's private address "D" and the NAT device's public address "N" (e.g. new parameters in the Notify Request message). + +HSS needs to perform DNS updates of the authoritative DNS server that stores the association between the "host name" of the MTC device on one hand, and the dynamically assigned private IP address "D" plus the NAT device's public address "N" on the other. + +Requires definition of a new DNS record, capable of storing the NAT device's IP address "N". + +### 6.18.4 Evaluation + +Benefits: + +- Low impact on existing Core Network nodes; +- Generic IP-level solution that does not rely on application-level identifiers (e.g. SIP URI); +- Works in all scenarios (non-roaming, roaming with home routed traffic, roaming with local breakout) to an attached MTC device with an established PDN connection; +- The solution does not rely on alternative communication channels (e.g. SMS) for delivery of a "push" stimulus; +- Works also for device-to-device communication; +- The solution is based on the generic FQDN Identifier solution described in clause 6.1, but the public DNS functionality needs to be extended. + +Drawbacks: + +- Requires support of a new DNS record (supporting D and N addresses) in the public DNS infrastructure, this DNS record needs to be standardised by the IETF and globally deployed as part of the public DNS infrastructure. Such a deployment may take a relatively long period of time. + +**Editor's note:** A solution may exist not requiring support of the new DNS record by the public DNS infrastructure, whereby the private IP address "D" would be transferred in the DNS infrastructure via transparent strings. This is FFS. + +- If the failure of a NATTT box requires to modify the public IP address "N" through which the private address "D" is reachable, then all the DNS entries of all MTC devices served by this NATTT must be updated (via the MME in this case). In addition the DNS cache entries at the MTC Server need to be cleared, generally after a timeout of few minutes (depending on the implementation). +- additional complexity in the MTC Server to support new DNS records and UDP/IP encapsulation (according to [3] this may require the support of a NAT Daemon in the MTC Server which intercepts DNS queries and user plane traffic to hide the DNS extension and UDP/IP encapsulation to the application). + +## 6.19 Solution - MT Communication with Micro Port Forwarding + +### 6.19.1 Problem Solved / Gains Provided + +See clause 5.3 "Key Issue – IP Addressing". + +## 6.19.2 General + +The general concept of this solution is that during initial PDP context / PDN connection establishment, the network will setup special very narrow port forward rule(s) (i.e. a Micro Port Forward rule) with the NAT to allow MT messages only from a defined MTC Server(s). Not only is the port forward narrowed based on the MTC Server IP address, it is further narrowed by only allowing specific source and destination port numbers. This effectively creates the same size pinhole in the NAT that UE used for MTC creates with a normal outbound packet. The difference being that this pinhole is now more specifically managed. + +When NAPT (Network Address and Port Translation) port forwarding only uses a mandated SRC IP address (i.e. public MTC Server IP address) and DST port number (i.e. public UE port number), this yields only 65,536 ( $2^{16}$ ) unique port forwarding rules per public UE IP address per public MTC Server IP address. However, when the port forward rule is extended to a MPF rule (additionally mandate of the SRC port number (i.e. public MTC Server port number), this yields $\sim 4$ billion ( $2^{32}$ ) unique port forwarding rules per public UE IP address per public MTC Server IP address. + +More than one MPF rule may be established for a particular UE used for MTC. The UE needs a MPF rule for each MTC Server it requires MT messaging support for. + +The set of MPF rule configuration parameters that can be specified as input into the NAT entity establishing a new MPF rule could include the following: + +- Per UE subscription: + - default MPF enablement flag; + - default set of authorized MTC Server public IP address(es) that can use an established PDP context / PDN connection for IP communications; + - default private UE DST port # range (optional)(Eases the requirement on the UE to only have to listen to pre-configured static ports); + - public MTC Server port # range (optional); + - protocol constraints (optional); + - lease time (time for the NAT to maintain the MPR rule) (optional). +- Per authorized MTC Server public IP address (optional configuration parameters that overrides the default above): + - reference to the authorized MTC Server public IP address; + - private UE DST port # range constraints (optional); + - public MTC Server port # range constraints (optional); + - protocol constraints (optional); + - lease time (time for the NAT to maintain the MPR rule) (optional). +- Per APN configuration / PDN subscription context (optional configuration parameter that overrides the default above): + - reference to APN configuration / PDN subscription context; + - MPF enablement flag; + - references to the subset of authorized MTC Server public IP address(es) that can use an established PDP context / PDN connection for IP communications. + +These MPF rule configuration parameters could be configured in the UE used for MTC (e.g. by the MTC Server through Device Management procedures) and/or in the subscription data for the UE in the HSS/HLR. If there is a conflicting parameter value between a parameter stored both in the UE and the HSS/HLR, the subscription data value in the HSS/HLR will have priority over the value stored in the UE. Furthermore, if there is still a conflicting parameter + +value between the default value and a MTC Server or APN configuration / PDN subscription context specific value, the latter will have priority over the default value. + +An established MPF rule contains the following parameters: + +- reference to the established PDP context / PDN connection; +- set of authorized MTC Server public IP address(es) that can use the established PDP context / PDN connection for IP communications; +- public UE IP address; +- public MTC Server port number; +- public UE port number. +- private UE IP address; +- private UE port number; +- lease time (optional); +- protocol constraints (optional). + +Once a MPF rule is established, the methods to communicate the public portion of the MPF rule to the MTC Server so that it can be used for MT communications includes: + +- 1) UE used for MTC sends MPF rule to MTC Server - The UE used for MTC receives the public portion of the MPF rule from the network during the PDN connection establishment procedure. Then the UE used for MTC sends a message(s) to the MTC Server(s) containing the information regarding the public portion of the MPF rule that was created. The UE used for MTC can do this by simply sending a transport layer (e.g. UDP or TCP) message using the appropriate IP address and port numbers. Alternatively, the UE used for MTC can send this information via an application layer message; +- 2) MTC Server request MPF rule from DNS server - This option uses the FQDN Identifier Solution described in clause 6.1. When the MTC Server wants to send a MT message it will do a DNS query of the FQDN of the UE used for MTC. The DNS response will contain the information defining the public portion of the MPF rule; +- 3) MTC Server obtains MPF rule from DT-GW - This option uses the MT communications address resolution via DT-GW solution described in clause 6.46. When the MTC Server wants to send a MT message to a UE used for MTC and the address of the assigned DT-GW is not known, the MTC Server will first perform a DNS query of the hostname of the UE. The DNS response will contain the IP addresses of the assigned DT-GW for the UE. Once the address of the assigned DT-GW for the UE is known, the MTC Server communicates with the DT-GW to ascertain the public portion of the MPF rule. + +Figure 6.19.2-1 illustrates how the IP address(es) and port numbers of a MPF rule are then used to route a MT IP packet from the MTC Server to the UE used for MTC in both the public and private address space. + +![Diagram illustrating Micro Port Forwarding for MT messages between an MTC Device and an MTC Server via a NAT Function.](f796c4b6ef101faa39b887a86820c3d1_img.jpg) + +The diagram shows the flow of an MT IP packet through a NAT Function. On the left, the **MTC Device** is in the **Private Address Space**. On the right, the **MTC Server** is in the **Public Address Space**. The **NAT Function** is in the center. Arrows indicate the packet flow from the MTC Server to the MTC Device. + +| Private Address Space (MTC Device) | NAT Function | Public Address Space (MTC Server) | +|------------------------------------|--------------|-----------------------------------| +| MT IP Packet | | MT IP Packet | +| SRC IP = Public MTC Server IP | | SRC IP = Public MTC Server IP | +| DST IP = Private MTC Device IP | | DST IP = Public MTC Device IP | +| SRC Port = Public MTC Server Port | | SRC Port = Public MTC Server Port | +| DST Port = Private MTC Device Port | | DST Port = Public MTC Device Port | + +Diagram illustrating Micro Port Forwarding for MT messages between an MTC Device and an MTC Server via a NAT Function. + +**Figure 6.19.2-1: MT message sent into a private IPv4 address space using Micro Port Forwarding** + +Figure 6.19.2-2 illustrates how a MPF rule is established for a new PDN connection, communicated to the MTC Server and utilized for MT communications. + +![Sequence diagram showing the call flow for MPF rule establishment for a PDN connection. The diagram involves seven entities: MTC device, MME, S-GW/P-GW, NAT (may be co-located w/P-GW), HSS, DT-GW, and MTC server. The process starts with an Attach Request from the MTC device to the MME, followed by an Update Location Request from the MME to the HSS. The HSS responds with an Update Location ACK. The MME then sends a Create Session Request to the S-GW/P-GW, which in turn sends an MPF Request to the NAT. The NAT establishes the MPF rule and sends an MPF Response. The S-GW/P-GW sends a PDN establishment status update to the DT-GW. The S-GW/P-GW then sends a Create Session Response to the MME, which includes the entire MPF rule. The MME sends an Attach Accept to the MTC device, which responds with an Attach Complete. The MTC device then sends an IP payload to the MTC server. The MTC server obtains the public portion of the MPF rule from the DT-GW. Finally, MT/MO communications occur over the private portion of the MPF rule between the MTC device and the MTC server, and over the public portion of the MPF rule between the MTC server and the DT-GW.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant MTC device + participant MME + participant S-GW/P-GW + participant NAT as NAT (may be co-located w/P-GW) + participant HSS + participant DT-GW + participant MTC server + + Note right of MTC device: Error: + Note right of MTC server: Error: Reference source not + + MTC device->>MME: 1. Attach Request(any MPF configuration parameters) + MME->>HSS: 2. Update Location Request + HSS-->>MME: 3. Update Location ACK(any MPF configuration parameters,assigned NAT, assigned DT-GW) + MME->>S-GW/P-GW: 4. Create Session Request(any MPF configuration parameters) + S-GW/P-GW->>NAT: 5. MPF Request(MPF configuration options) + NAT-->>NAT: 6. MPF rule established + NAT-->>S-GW/P-GW: 7. MPF Response(MPF rule) + S-GW/P-GW-->>DT-GW: 8. PDN establishment status update(public/private portions of MPF rule) + S-GW/P-GW->>MME: 9. Create Session Response(entire MPF rule) + MME->>MTC device: 10. Attach Accept(entire MPF rule) + MTC device->>MME: 11. Attach Complete + MTC device-->>MTC server: 12. IP payload (public portion of MPF rule) + Note right of DT-GW: 12'. MTC server obtains public portion of MPF rule from DT-GW + Note bottom: 13b. MT/MO communications over private portion of MPF Rule + Note bottom: 13a. MT/MO communications over public portion of MPF Rule + +``` + +Sequence diagram showing the call flow for MPF rule establishment for a PDN connection. The diagram involves seven entities: MTC device, MME, S-GW/P-GW, NAT (may be co-located w/P-GW), HSS, DT-GW, and MTC server. The process starts with an Attach Request from the MTC device to the MME, followed by an Update Location Request from the MME to the HSS. The HSS responds with an Update Location ACK. The MME then sends a Create Session Request to the S-GW/P-GW, which in turn sends an MPF Request to the NAT. The NAT establishes the MPF rule and sends an MPF Response. The S-GW/P-GW sends a PDN establishment status update to the DT-GW. The S-GW/P-GW then sends a Create Session Response to the MME, which includes the entire MPF rule. The MME sends an Attach Accept to the MTC device, which responds with an Attach Complete. The MTC device then sends an IP payload to the MTC server. The MTC server obtains the public portion of the MPF rule from the DT-GW. Finally, MT/MO communications occur over the private portion of the MPF rule between the MTC device and the MTC server, and over the public portion of the MPF rule between the MTC server and the DT-GW. + +**Figure 6.19.2-2: Call flow for MPF rule establishment for a PDN connection** + +1. UE used for MTC sends initial attach request specifying any MPF configuration preferences for the default PDN connection e.g. that may have been configured using Device Management procedures by the MTC service provider. +2. If the MME does not have the subscription data for the UE, the Update Location request is sent to the HSS. +3. The HSS sends the Update Location ACK to the MME containing subscription data for any MPF configuration parameters and, if a DT-GW is employed for the UE, the assigned NAT entity for the new PDN connection, if not co-locate with the P-GW and the assigned DT-GW. The MME resolves any duplicate and conflicting MPF configuration parameter values by applying the appropriate priority. +4. The MME and S-GW include any MPF configuration parameters in their respective Create Session requests. +5. If the MPF enablement flag is set for the new PDN connection and the NAT entity and P-GW are not co-located, the P-GW sends a MPF request to the NAT entity responsible for the establishing the MPF rule for the new PDN connection. +6. NAT entity establishes the MPF rule for the new PDN connection using any specified MPF configuration parameters. +7. If a MPF rule was established and the NAT entity and P-GW are not co-located, the NAT entity includes the entire MPF rule (both public and private portions) in the MPF response to the P-GW. +8. If a DT-GW is assigned for the UE, the P-GW sends a PDN establishment status update to the assigned DT-GW containing the complete MPF rule. +9. If a MPF rule was established, the P-GW and S-GW includes the entire MPF rule in their respective Create Session responses. +10. If a MPF rule was established, the MME includes the entire MPF rule in the Attach Accept message. +11. UE responds with the Attach Complete message. +12. The UE used for MTC sends a transport layer (e.g. UDP or TCP) message using the appropriate IP address and port numbers. Alternatively, the MTC device can send this information via an application layer message. + +12'. In an alternative to step 12, the MTC server obtains the public portion of the MPF rule from the DT-GW. + +13a. When the NAT entity receives an incoming packet from the MTC server that matches the MPF rule (i.e. public MTC Server SRC IP and port #, public UE DST IP and port #), it performs the normal NAT on the public UE device IP address and DST port #. + +13b. The NAT entity then forwards the packet to the UE. + +### 6.19.3 Impacts on existing nodes or functionality + +Impacts on CN nodes: + +- NAT functionality is extended to employ MPF (addition of the SRC port number to the port forwarding rule); +- If NAT entity is not co-located with the GGSN/P-GW, a new interface and messaging between the GGSN/P-GW and NAT entity is required to establish MPF rules; +- HSS/HLR additional storage of MPF configuration parameters as part of subscription data; +- PDP context / PDN establishment procedure messaging to be extended to include MPF configuration parameters and MPF rule; +- if DT-GW is used for MTC Server to obtain public portion of MPF rule, the "MT communications address resolution via DT-GW" solution described in clause 6.46 shall be supported. + +### 6.19.4 Evaluation + +Benefits: + +- Increases the number of possible unique port forwarding rules per public UE IP address per public MTC server IP address from 65,536 ( $2^{16}$ ) to ~4 billion ( $2^{32}$ ); +- For security, reduces scanning attack success rate from malicious network entities. +- Works in all scenarios (non-roaming, roaming with home routed traffic, roaming with local breakout); +- The solution does not rely on alternative communication channels (e.g. SMS) for delivery of a "push" stimulus to an attached MTC device with an established PDN connection, but this requires the network to periodically re-new the MPF rule in the NAT entity; + +Drawbacks: + +- MPF rule adds additional port forwarding requirements on NAT in network; +- MPF rule adds additional subscription data and/or UE configuration. +- If the application payload need to transport IP addresses then there is a need for ALG (Application Level Gateway), which may not be possible if the payload is encrypted end to end; If no encryption is used then the NAT needs to parse the application level payload. +- NAT single point of failure (the MPF rules are lost if the NAT box fails) but this is similar to traditional port forwarding; +- MTC Device needs an explicit protocol to discover the NAT and also set the MPC filter in the NAT. + +## 6.20 Solution - Optimizing periodic LAU/RAU/TAU Signalling + +### 6.20.1 Problem Solved / Gains Provided + +See clause 5.6 "Key Issue – Low Mobility," clause 5.12 "Key issue – Signalling Congestion Control", clause 5.14 "Key Issue – Potential overload issues caused by Roaming MTC devices" and clause [TBD] "Key Issue – Extra Low Power". + +## 6.20.2 General + +This solution can be used for low mobility and/or extra low power MTC devices (CS and PS domain specific systems), MTC devices that indicate "Low-Priority-Access" (PS domain specific system) (see clause 6.23), and for signalling congestion control and potential overload issues caused by roaming MTC devices. + +For CS domain specific systems, MTC devices can be pre-provisioned with MTC\_T3212\_Multiplier. If provisioned, the MTC device shall calculate the periodic LAU timer by multiplying T3212 (received from BCCH) with MTC\_T3212\_Multiplier. MTC\_T3212\_Multiplier is also configured at MSC/VLR in order to derives new implicit detach timer. Alternatively, MTC\_T3212\_Multiplier may be part of an MTC subscription data stored in HLR/HSS and downloaded to MSC/VLR during attach procedure. + +NOTE: The MTC device may need to be configured to apply the specific timer, e.g. whether to adopt the special timer value from broadcast information. + +**Editor's note:** It is FFS if dynamic synchronization of MTC\_T3212\_Multiplier is needed between MSC/VLR and MTC device. + +Alternatively, a separate setting for the T3212 timer can be added into the LAU procedure. Details for such solution including whether to add specific MS capability sent from the MTC device can be decided in stage 3. + +For PS domain specific systems, in order to reduce periodic RAU/TAU signalling the granularity of T3312/T3412 and Mobile reachable timer can be increased. New binary coding can be added for example to indicate GPRS timer value is incremented in multiple of 10 or 100 decihours. + +**Editor's note:** Exact changes to coding of the GPRS timer value is FFS and will be specified as part of stage-3 specification. + +A long periodic RAU/TAU timer (T3312/T3412) or specific coding to deactivate the timers may be part of an MTC subscription data stored in HLR/HSS and downloaded to the SGSN/MME during the Attach procedure. During Attach and periodic RAU/TAU procedures the SGSN/MME sets the device's periodic RAU/TAU timer and the mobile reachable timer to long values or deactivate the timers according to the parameter received from the MTC subscription data. Alternatively, if periodic RAU/TAU timer is not stored as part of MTC subscription data, or if SGSN/MME is experiencing overload situation, or if MTC device indicates "Low priority Access", SGSN/MME may decide to set them to higher values or decide to deactivate them. + +If the subscribed periodic timer changes the SGSN/MME provides the MTC device with the new timer value during the next RAU/TAU procedure. Alternatively the SGSN/MME can initiate an SGSN/MME-Initiated Detach procedure with a re-attach indication to enforce an Attach procedure and provide the MTC device with the new timer value. + +For M2M devices that support both the PS and CS domains, an alternative implementation is that these devices are commanded to use Network Mode of Operation (NMO) I and use a long PRU timer in the PS domain. With NMO=I, the MSC deactivates its implicit detach functionality and the device only performs periodic updates to the PS domain. By using a new broadcast indication, the network operator can maintain the use of NMO=II for existing devices and only use NMO=I for M2M devices. + +## 6.20.3 Impacts on existing nodes or functionality + +Impacts to HLR/HSS: + +- Support configuring and provisioning of periodic LAU/RAU/TAU information (e.g. MTC\_T3212\_Multiplier, T3312/T3412 timer value or special encoding to disable them) as part of MTC subscription. + +Impacts on SGSN/MME: + +- Support configuring and storing the periodic RAU/TAU information (e.g. T3312/T3412 timer value or special encoding to disable them) and mobile reachable timer for a particular MTC Device, according to the parameter received from the HSS/HLR. +- Support modification of periodic RAU/TAU and mobile reachable timer values, if the subscribed periodic timer value changes, and provide the MTC device with the new timer value during the next RAU/TAU procedure or by initiating detach with "re-attach indication". + +- Support configuring longer timer values for RAU/TAU or disable them based on local configuration, if periodic timer is not present in subscription information, or if SGSN/MME is experiencing overload situation, or if the device indicates "low priority access". +- Support for an extended coding of the timers (e.g. T3312/T3412) + +#### Impacts on MSC/VLR: + +- Support configuring and storing the periodic LAU information (e.g. MTC\_T3212\_Multiplier). +- Using MTC\_T3213\_Multiplier to derive new implicit detach timer. +- Downloading MTC\_T3213\_Multiplier during the attach procedure, if it is stored as part of subscription data. + +#### Impact on the MTC Device / UE + +- Support pre-configuring MTC\_T3213\_Multiplier and calculating the periodic LAU timer. +- Configuration flag on whether to use MTC\_T3213\_Multiplier or special periodic timer value from broadcast information. +- MTC devices need to be able to read the NMO I indication in the broadcast information + +#### Impacts on the RAN/GERAN: + +- New broadcast indication telling specifically MTC devices to use NMO I (In UTRAN this can be an existing spare bit in one of the 'transparent containers' of NAS information that the UTRAN broadcasts), +- For CS domain system, generation of special periodic timer value in the broadcast information + +## 6.20.4 Evaluation + +Following conclusion can be drawn: + +- For the protection of other networks in the case of one network's failure, long periodic timers seem to be useful in slowing down the rate at which low activity mobiles detect the network failure. Hence mechanisms with the minimal impact on VPLMN equipment are desirable. +- Extending the periodic timer in one domain (e.g. PS) and not the other (e.g. CS) will not slow down the rate at which mobiles detect network failure unless NMO=1 is used. +- Proposed solution does not avoid overload or provide a congestion control mechanism, but it provides a simple way to limit the signalling load in the network. +- Extending the existing periodic LAU/RAU/TAU timers and defining configuration of new parameter (MTC\_T3212\_Multiplier) is fairly simple. +- MTC device indication of "Low Priority Access" to SGSN/MME can be added by using new IE on existing NAS messages. +- HLR/HSS control of the periodic timer ranges is useful longer term functionality. Operator can control the frequency of the periodic update performed by MTC devices by configuring the periodic timer related parameters in the MTC subscription database. +- Adding the new timer values or indication to broadcast information may have an impact on RAN and GERAN. In general Broadcast channels are a scarce resource. + +Based on the above conclusion following items are proposed for normative work: + +- Add normative stage 2 requirements for enabling the long periodic LAU/RAU/TAU update timer for MTC devices. +- Add encoding of the extended periodic LAU/RAU/TAU timers and MTC\_T3212\_Multiplier. +- Standardization and encoding for new subscription parameters in HLR/HSS for extended periodic LAU/RAU/TAU timers and MTC\_T3212\_Multiplier. + +- Standardization of mechanism for MTC device to indicate "Low priority Access" to SGSN/MME/MSC. +- GERAN broadcast information and the existing NAS information broadcast by UTRAN is modified so that M2M devices can be commanded to use NMO=I (Gs interface) while existing devices use NMO=II. + +## 6.21 Solution - Randomized triggering of time-controlled MTC operations + +### 6.21.1 Problem Solved / Gains Provided + +See clause 5.9, "Key Issue – Time Controlled"; clause 5.12, "Key Issue – Signalling Congestion Control." + +### 6.21.2 General + +Simultaneous operations by too many MTC devices especially at the beginning of the time period may cause serious network or MTC server overload. Therefore, the triggering of time-controlled MTC operations needs to be randomized. + +The time-controlled operation can be triggered by MTC device or the network including MTC server. When triggered by the network, the operation of MTC device can be started after receiving paging from the network elements (e.g. SGSN/MME) or application-level data from the MTC server directly if the MTC device is online. + +Therefore, two alternatives to randomize triggering point of time-controlled operation can be considered: + +- 1) Randomization of triggering at the MTC device – The MTC device randomizes triggering of the operation over the authorized time-controlled period informed by the network or MTC server. + +NOTE: The MTC devices shall not trigger operations due to signalling congestion/overload situations, e.g. based on access control by RAN via broadcast system information. + +- 2) Randomized triggering from the MTC server – Based on the poll model for communications between MTC devices and the MTC server, the MTC server randomizes the initiation of communication for the MTC devices during the time-controlled period provided by the network. + +NOTE: The MTC server shall quit triggering operations if indicated from the network due to signalling congestion/overload situations. + +Editor's note: It is FFS how the MTC server can communicate with VPLMN when the MTC device is roaming. + +Editor's note: It is FFS if applying the two above-mentioned approaches concurrently would be more beneficial. In other words, it is FFS if the operation of the MTC device should start immediately after the MTC device is paged or if it would be beneficial that the operation starts only after a randomly selected time. + +### 6.21.3 Impacts on existing nodes or functionality + +### 6.21.4 Evaluation + +## 6.22 Solution – Rejecting connection requests by the SGSN/MME + +### 6.22.1 Problem Solved / Gains Provided + +See clause 5.12, "Key Issue – Signalling Congestion and Overload Control", more specifically congestion control. + +### 6.22.2 General + +The solution is applied for both GTP and PMIP based EPC. A number of variants of rejecting connection requests by the SGSN/MME can be distinguished: + +### **Rejecting connection requests per APN** + +The SGSN/MME and/or GGSN/PGW can reject connection requests targeted at a particular APN. When the MTC application uses a dedicated APN, the specific MTC application can be targeted that causes the congestion. + +### **Rejecting connection requests and attach requests per MTC Group** + +The SGSN/MME can reject connection requests targeted at a particular MTC Group. With the attach procedure the MTC Group Identifier can be downloaded as part of the service profile from the HSS into the SGSN/MME. When a connection request is received by the SGSN/MME, the SGSN/MME can find in the service profile if the particular MTC Device is part of a MTC Group that causes congestion. In case only the GGSN/PGW is congested, the SGSN/MME need to be informed about which MTC Group is causing that congestion. + +The SGSN/MME can reject attach requests on the basis of MTC Group is the only option. One option is that the MTC Group is downloaded from the HSS during the attach procedure. However this implies the service profile is only downloaded when most of the attach procedure is already done. + +Another option would be to add the MTC Group ID to the connection requests and attach requests from the MTC Device. That way the SGSN/MME can easily identify that a particular request comes from a MTC Application that is causing congestion. + +### **Rejecting service request and attach attempts based on MTC Device provided low priority access indication** + +With availability of an access priority indication from the MTC Device the SGSN/MME can take an early decision to reject the request. Depending on internal SGSN/MME congestion mechanisms the SGSN/MME can appropriately treat the "low priority access" (e.g. used by Time Tolerant MTC device) in comparison to other accesses. + +The treatment can be performed without inducing or consuming further load in the SGSN/MME and the network as it could be performed prior to the download of the service profile from the HSS. The treatment could include returning an extended back-off time to the MTC Device requesting the "low priority access". + +When using SGSN/MME level rejection of devices, care is needed to guard against the possibility that the devices use the result as a soft (or hard) trigger for network reselection. This is because triggering network reselection can lead to the device repeatedly, cyclically attempting access on all the local competing networks and adding load to all of them. + +### **Providing a back-off time and a reject indication to the MTC Device** + +To avoid a MTC Device from re-initiating a connection request or attach request immediately after a reject to an earlier request, the SGSN/MME can provide a back off time to the MTC Device in the reject message. If it is the GGSN/PGW that sent the reject originally, the SGSN/MME may append a back off time to the reject message. + +In case of large number of MTC Devices, to avoid them from re-initiating access requests simultaneously, the back off time should be randomized. SGSN/MME may randomize the back off time with certain range and assign it to each individual MTC Device directly. + +Alternatively, SGSN/MME may just send "back-off time" to MTC device and the MTC device can randomize its local back-off time. + +The reject message from the SGSN/MME may contain a reject indication informing the MTC Device about the reject cause. For example a reject indication could inform that there is a signalling congestion at the SGSN/MME, or overload at the GGSN/PGW, or restricted access per requested APN, or the QoS requirements of the requested PDN connection cannot be fulfilled etc. + +The reject indication may inform the MTC Devices capable of dealing with multiple connections how to proceed when establishing additional connections. In one example the MTC Devices could be informed that no additional connection to a particular APN shall be established. In another example when the resources at the GGSN/PGW are limited per MTC Device, if the MTC Device has an existing connection and initiates an additional connection establishment, the reject indication can inform the MTC Device about the limited available resources. Additionally the MTC Device may be allowed to keep the already existing PDN connection(s) at time, and/or the MTC Device is allowed to establish multiple connections within the limited resources and/or number of possible PDN connections. In this case, if the MTC Device has an existing connection and has higher priority data to send over new connection, the MTC Device may decide to share the resources among the existing and additional connections or to release the existing connection and establish the new one. When the reject message contains reject indication together with a back off time, the reject indication is valid only during the back off time. + +The MTC Device shall not re-initiate a similar request during the back off time depending on the reject indication. + +The SGSN/MME may store the back off time for a particular MTC Device and immediately reject any subsequent requests from that MTC Device before the back off time is expired. A new (longer) back off time may be provided to further deter the MTC Device from repeated attempts before its back off time is expired. + +Providing a back off time could also be a solution to the issue of recurring (quarter/half) hourly applications. If the MTC Device could identify the recurring applications, it could delay attach request or connection requests for these applications with the back off time. How to identify such recurring applications is unclear. + +### 6.22.3 Impacts on existing nodes or functionality + +Impact on the SGSN/MME: + +Additional functionality for SGSN/MME with this solution includes: + +- Rejection of a connection request targeted at a particular APN. +- Rejection of attach and connection requests by MTC Devices belonging to a particular MTC Group. +- Detection if an MTC Device is part of a particular MTC Group (e.g. based on subscription information requested from the HSS/HLR). +- Determining the MTC Group or APN that causes congestion, within SGSN/MME, or upon reception of indication from GGSN/PGW. +- Providing a reject cause including a back off time in the reject messages. +- Providing a reject indication in the reject message. +- Randomization of the back off time that is applicable for a particular MTC Device. +- Determination of the reject indication that is applicable for a particular MTC Device and connection. +- (For SGSN) Indicating MTC Group ID to GGSN. +- (For MME) Indicating MTC Group ID to SGW. +- In the case that the MTC device supports the Time Controlled feature and the subscriber data is available, based on implementation the SGSN/MME may take this into consideration when calculating a wait time. +- In the case of the SGSN/MME rejecting a service request the Mobile Reachable Timer may be compensated by the extended wait time to take into consideration that a periodic TAU/RAU may be suppressed during this period. + +Impact on the MTC Device / UE: + +Additional functionality for the communication module in MTC Device / UE with this solution includes: + +- Not re-initiating further attach or connection requests before the back off time is expired, if timer value is provided by the network. +- Possibly needing to randomize the local back off time according to the back off time received in reject signalling, if such information is provided by the network. +- Determining how the MTC Device deals with additional connections depending on the reject indication. +- Handling of reject causes such that network reselection is not triggered. +- Capability to configure the device with a low priority indication. + +Impact on the SGW: + +Additional functionality for SGW with this solution includes: + +- Forwarding MTC Group ID received from MME to PGW. + +- Forwarding low priority device indication to PGW. +- Forwarding the overload/congestion situation indication received from PGW to MME for a particular APN or MTC Group. +- Forwarding a reject cause in the reject messages received from PGW to MME. +- Forwarding a reject indication in the reject messages received from PGW to MME. + +Impact on the GGSN / PGW: + +Additional functionality for the GGSN and PGW with this solution includes: + +- Detecting the overload/congestion. +- Determining the MTC Group or APN that causes overload/congestion. +- Rejection of a connection request targeted at a particular APN. +- Rejection of connection requests by MTC Devices belonging to a particular MTC Group, possibly taking the low priority device indication into account. +- Indicating the overload/congestion situation to SGSN/MME for a particular APN or MTC Group. +- Suggesting value of back off time to SGSN/MME. +- Providing a reject cause in the reject messages. + +Impact on the HSS/HLR: + +Additional functionality for HSS/HLR with this solution includes: + +- Storing the MTC Group Identifier as part of the subscription profile of an MTC Device. + +Impact on the PCC: + +- Forwarding MTC Group ID received from MME to PGW (via BBERF, PCRF, PCEF). + +**Editor's note:** It is FFS how PGW exactly indicates the congestion situation back to MME and how SGW(BBERF) correlates such information. + +**Editor's note:** It is FFS if PCC needs to be used. PMIP mobility related information may be used instead. + +## 6.22.4 Evaluation + +In the case that the MTC device also supports the Time Controlled feature and the subscriber data is unavailable, the calculated wait time may coincide with a Time Controlled "Forbidden Time Interval". This is not considered significant as the MTC device as per Time Control implementation would access the network at the next available Grant Time Interval. + +Benefits: + +- Low impact on existing 3GPP RAN standards and products. +- Allows for CN node specific load control in flex or sharing scenarios (in UTRAN and E-UTRAN, but not GSM) +- For roaming scenarios, the SGSN/MME rejects or accepts the connection requests of roaming MTC device based on the load situation and operator's policy. +- Within the network, only requires changes to core network nodes +- By using back-off time, devices are prohibited from generating any more signalling traffic, both in the core network and in the radio network, from requests that would be denied anyway. +- Back-off times allow for peak shaving; making more efficient use of existing capacity. + +Drawbacks: + +- This solution consumes the RAN and CN resource even at the congestion and overload situation. +- Requires updates to mobiles (their behaviour while a MM/GMM/EMM and/or CM/SM/ESM back off timer is running needs to be defined, specified and tested). + +## 6.23 Solution – Low Priority Access Indication + +### 6.23.1 Problem Solved / Gains Provided + +See clause 5.12, "Key Issue – Signalling Congestion Control", more specifically overload control; and 5.14 "Key Issue - Potential overload issues caused by Roaming MTC devices". + +### 6.23.2 General + +This solution introduces the concept that access attempts from certain MTC devices or applications (e.g. "time tolerant" utility meters) can be treated as a low priority requests. + +In the abnormal case of congestion due to many simultaneous connection requests it is of benefit that the connection requests are rejected as early on in the access procedures such that resources are not consumed or induced further into the network. + +NOTE: It is assumed that the network is appropriately dimensioned i.e. congestion or close to maximum resource usage is an abnormal situation. + +This solution addresses (unexpected) unacceptable high load resulting from MTC devices in the Low-Priority-Access category. High load resulting from MTC devices out of this category is not covered. + +This is a solution that avoids problems in the network that affects both MTC devices that do and MTC devices (in the Low-Priority-Access category) that do not generate an unacceptable high load. + +At a high level the following stages occur for UE access from RRC Idle state: + +1. Read broadcasted System Information +2. Identifying a RACH opportunity +3. RRC Connection Establishment (E-UTRAN/UTRAN), Channel Request/EGPRS Packet Channel Request (GERAN) +4. Service Request, EPC ATTACH Procedure or GPRS ATTACH/PDP Context Activation) + +At step 1 the access class barring mechanism can protect the network. + +At step 2 contention based random access procedure exists for identifying an access opportunity on acquiring the Random Access Channel. + +At step 3 reception of a priority indication at the access attempt can be used to manage access attempts in RAN (GERAN, UTRAN, E-UTRAN) prior to knowing (decoding and authentication) of the specific identity of the accessing MTC device. + +At step 4, reception of a priority indication at the access attempt can be used to manage the requests received in the MME/SGSN early on in the process, i.e. prior to decoding any NAS messages of the accessing "time tolerant" MTC device is attempted. If the request is admitted the indication can also possibly be used to verify the behaviour towards subscription data for the MTC user. An extended use case of the indication can also be to propagate the information for charging purposes. + +A priority indication allowing for "Low-Priority-Access" can be used to determine whether to reject the service request or attach attempt depending on the current load. + +This indication can be used by MTC devices (e.g. "time tolerant" utility meters) during their normal operating access or access attempts following a power failure (i.e. mass simultaneous registration scenario) as means to request a "Low-Priority-Access". Note that in other scenarios these same devices when accessing the network could use other priorities + +as required. For example this may be the case of a MTC device supporting multiple MTC applications requiring different priorities (i.e. the MTC application will determine the priority to be indicated during an access attempt). + +In the case of overload condition in the RAN, where RACH overload isn't a factor, the RAN may take the decision to reject these requests without further propagating signalling into the core network. In addition, the RAN can use the "low-Priority-Access" indicator to signal a longer back off time to a "low priority access" device compared to any back-off time sent to a normal UE (e.g. one attempting a voice call). + +The MME/SGSN can initiate gradual overload procedures by first reducing low priority traffic. The MME/SGSN can notify the RAN to allow all traffic except low priority, using a similar overload mechanism as defined currently for requesting the RAN to reject all non-emergency traffic by sending the OVERLOAD START message. + +In the absence of overload condition in the RAN or notification to RAN, the request is eventually transported to the SGSN/MME. Depending on internal MME/SGSN congestion mechanisms the MME/SGSN can appropriately treat the "Low-Priority-Access" request in comparison to other priorities. The treatment can be performed without inducing or consuming further load in the SGSN/MME and for example could be performed prior subscriber profile retrieval. + +Also, the "Low-Priority-Access" should be passed to the GGSN/S-GW/P-GW. For Mobile Originating communication, in the absence of overload condition in the RAN and the SGSN/MME and the signal screening at the SGSN/MME for GGSN/S-GW/P-GW, the GGSN/S-GW/P-GW can appropriate treat the request related with the existing session marked as "Low-Priority-Access". For Mobile Terminating call, the S-GW can decide whether to send downlink data notification or not for the existing session marked as "Low-Priority-Access" + +This indication conveyed by MTC Devices at the access attempt implies the MTC application is less critical. It can be used as a criterion by the network to determine which MTC Devices/bearers should be detached / deactivated prior to others in case of congestion. When the network status is normal without congestion, the "low priority" MTC Devices will be accepted by the network and bearers will be established. When the network starts to get congested, the already attached "low priority" MTC Devices or established "low priority" MTC bearers can be detached / deactivated first. + +This Low Priority Access Indication can be used in combination with Group ID or APN, e.g. when the network decided to detach devices/deactivate bearers belonging to a certain group, the "low priority" MTC Devices within the group can be detached/bearers deactivated first, followed by the remaining devices in the group. + +### 6.23.3 Impacts on existing nodes or functionality + +In E-UTRAN a new RRC Establishment cause could be introduced. The purpose of the *RRC Establishment Cause* IE is to indicate to the eNB the reason for RRC Connection Establishment (ref TS 36.331 clause 6.2.1 - "RRConnectionRequest" message). Existing values can indicate emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data. Following this model of "normal", emergency and high priority causes it is proposed that some MTC device accesses could be viewed as "Low-Priority-Access" as compared to the existing establishment causes. The *RRC establishment cause* IE is as currently specified (ref TS 36.413 clause 9.1.7.1) forwarded to the MME in the "Initial UE message" over the S1-AP protocol. + +In the UTRAN case a new *establishment cause* could be used by MTC "time tolerant" devices in the RRC Connection Request. Signalling would be impacted to include the establishment cause such that SGSN can be made aware of a low priority access (e.g. by a MTC "time tolerant" device). + +NOTE 1: the existing UTRAN establishment cause "Originating Low Priority Signalling" is used for mobile originating SMS and is unsuitable for re-use as this code-point. + +For the GERAN case a priority indication may be introduced in the access message (e.g. EGPRS Packet Channel Request or by partial re-coding of the existing Channel Request message) to indicate when an access is attempted by an MTC device and the priority of the corresponding MTC message requiring transmission. The priority indication should allow for the equivalent of a "Low-Priority-Access". MM/GMM Signalling would be impacted to include a priority indication such that MSC/SGSN can be made aware of a low priority access (e.g. by a MTC "time tolerant" device). + +NOTE 2: The above mechanisms are provided as examples. If the solution is supported, it is the responsibility of the RAN/GERAN to specify the messages and parameters in which the low priority indicator would be passed. + +For E-UTRAN/UTRAN/GERAN, the OVERLOAD START message would need to support the ability to request RAN to reject low priority access requests. + +For E-UTRAN, UTRAN and GERAN it is likely that the "low priority access" codepoint should be used for EMM, GMM and MM signalling as well as for initiating data transfer/responding to paging. However, some further study on this aspect may be needed. + +The SGSN/MME should include the "Low Priority Access" indicator in the session create message in order to notify it to GGSN/S-GW/P-GW. A GGSN/S-GW/P-GW that experience overload, may decide to reject any additional "Low Priority" session creation requests in order not to increase its number of sessions and any potential traffic related to these sessions. If a GGSN/S-GW/P-GW reject a session create request due to an overload condition, a specific reject cause shall be indicated back to the SGSN/MME so that the SGSN/MME can take appropriate action (e.g. try another GGSN/S-GW/P-GW instead or reject with a wait time). + +A low priority access indication usage control parameter may be pre-configured (e.g. at manufacturing) or set via OMA device management in the MTC Device SIM/USIM to allow for: + +- MTC Device that uses the low priority access indication for all its access attempts +- MTC Device that uses the low priority access indication for all its delay tolerant accesses attempts, but which may use other priorities for services that require immediate response + +The MTC Device low priority indication usage could be according to the Service Level Agreement (SLA) established between the mobile operator and the MTC service provider. + +SGSN/MME/GGSN/P-GW are required to store the "Low-Priority-Access" indication for each attached MTC Device. SGSN/MME need to forward this indication to GGSN/P-GW. + +## 6.23.4 Evaluation + +Benefits: + +- Should be possible to easily add parameters/mechanisms to the UTRAN and E-UTRAN RRC protocol and to GERAN although the network's support/non-support for these new parameters may probably need to be broadcast. + +NOTE: Whether necessity to broadcast network's support/non-support for these new parameters should be decided at the stage 3. + +- Works in a roaming environment. A network upgraded with "low priority" functionality can take advantage of this as soon as there are terminals also supporting this regardless if terminals are roaming or not. +- Low impact on existing 3GPP standards and products and may be feasible in Rel-10. +- allows for CN node specific load control in flex or sharing scenarios +- Initially provides, from the time RAN decides to start rejecting low-priority-access requests until the first low-priority-access barring is broadcast in system information, a faster way to protect from overload compared to mechanisms relying on broadcasted system information (e.g. ACB) +- Allows GGSN/S-GW/P-GW to handle signalling overload appropriately +- Allows the UE flexible access to the network by indicating the priority that is suitable for use (e.g., low priority MTC service vs normal priority when not in MTC low priority mode). +- Provides a criterion for the network to determine the MTC Devices to be detached / bearers to be deactivated for congestion control. + +Drawbacks: + +- Doesn't allow to switch off specific groups or applications (vs. broadcasting in system information which can prevent low-priority-access requests from devices that have not received access rejections). +- the node specific load control or network sharing specific control might not work if the device signals the IMSI instead of temporary IDs e.g. during PLMN changes +- As it bases on UE individual signalling it might not be possible to completely avoid Radio Resource congestion. There are also related work in RAN e.g. usage of concentrators. + +- In the case that the MTC device also supports the Time Controlled feature, the calculated wait time may coincide with a Time Controlled "Forbidden Time Interval". This is not considered significant as the MTC device as per Time Control implementation would access the network at the next available Grant Time Interval. + +## 6.24 Solution - Directly Reporting to MTC Server from CN entity + +### 6.24.1 Problem Solved / Gains Provided + +In the MTC Monitoring solution, clause 5.10 "Key Issue – MTC Monitoring" and 6.9 "Solution – MTC Monitoring – General", the MTC Event Reporting entity (e.g. SGSN/MME or GGSN/PGW or PCRF) is not aware of the MTC Server identity, thus it cannot send the MTC Event Report to the MTC Server. + +### 6.24.2 General + +In this solution, the MTC Server identity (e.g. FQDN or IP address) is stored in the HLR/HSS as part of MTC subscription per MTC device or per MTC group, and is downloaded to the SGSN/MME through Insert Subscription Data procedure. The SGSN/MME then stores this MTC Server identity. + +If the CN entity for MTC Event Reporting is the GGSN/PGW, the SGSN/MME transfers the MTC Server identity to the GGSN/PGW through Create PDP Context Request / Create Session Request, or carries the MTC Server identity within the MTC Event Report when it sends MTC Event Report to the GGSN/PGW, and PCEF may send the Event Report to PCC if GTP is used over S5/S8. If PMIP is used, these information are transferred via PCC i.e. BBERF sends MTC Event Report to PCRF. + +If the CN entity for MTC Event Reporting is the PCRF, after receiving the MTC Server identity, the GGSN/PGW then transfers the MTC Server identity to the PCRF through PCC procedure, or carries the MTC Server identity within the MTC Event Report when it sends MTC Event Report to the PCRF. The PCRF uses the MTC Server identity to send MTC Event Report. + +If the MTC server is out of the operator control, a security connection between the CN entity and the MTC server may be needed. + +**Editor's note:** It is FFS how to setup a security connection to the MTC Server, and where the security connection information is stored and how to establish the secure connection. + +**Editor note:** It is FFS how to report MTC events to multiple MTC servers. + +### 6.24.3 Impacts on existing nodes or functionality + +HLR/HSS: + +- The HLR/HSS stores the MTC Server identity as part of MTC subscription. + +SGSN/MME: + +- SGSN/MME stores the MTC Server identity +- The SGSN/MME includes the MTC Server identity in the Create PDP Context Request / Create Session Request. + +GGSN/PGW: + +- The GGSN/PGW includes the MTC Server identity during the Gx session procedure to the PCRF. + +SGW(BBERF) + +- The BBERF forwards the MTC Server identity during the Gxx session procedure to the PCRF, if PMIP is used over S5/S8. + +PCRF + +- The PCRF receives MTC Server Identity from PCEF (if GTP is used over S5/S8) and from BBERF (if PMIP is used over S5/S8) +- The PCRF uses the MTC Server identity to send MTC Event Report. + +## 6.24.4 Evaluation + +# 6.25 Solution - Reporting to MTC Server through the intermediate node + +## 6.25.1 Problem Solved / Gains Provided + +See clause 6.24.1. + +## 6.25.2 General + +In this solution, there is an operator controlled intermediate node (e.g. MTC Monitoring GW or IWKF) deployed to collect MTC event reports. The CN entity for MTC event reporting (e.g. the SGSN/MME or GGSN/PGW or the PCRF) sends MTC Event Report to this intermediate node, and the intermediate node then gets the corresponding MTC server identity and forwards the MTC Event Report to that MTC server. + +The CN entity for MTC event reporting can get the identity of this intermediate node through the following methods: + +- A) Static configuration based on the local configuration for the home PLMN or the roaming agreement for the visited PLMN. +- B) The MTC subscription from HLR/HSS. + +The CN entity for MTC event reporting needs not know where the MTC server is, the intermediate node will find MTC server through the following methods: + +The intermediate node locally configures the MTC Server identity. + +Or, the MTC Server(s) contact the Intermediate Node (e.g. the3GPP PLMN-MTC Server IWK Function) and register. The Intermediate node then requires no configuration or information from the CN to locate the MTC Server(s). + +If the MTC server is out of the operator control, the security connection between the intermediate node and the MTC Server may be needed. + +**Editor's note:** It is FFS how to setup a security connection to the MTC Server, and where the security connection information is stored. + +**Editor's note:** Whether there are changes to the roaming architecture and message flow are FFS. + +**Editor's note:** It is FFS whether new interface between the CN entity and the intermediate node is introduced. + +**Editor's note:** It is FFS how to report MTC events to multiple MTC servers. + +## 6.25.3 Impacts on existing nodes or functionality + +HLR/HSS: + +- The HLR/HSS stores the intermediate node identity as part of MTC subscription if the CN entity for MTC event reporting gets the intermediate node identity from HLR/HSS. + +CN nodes for MTC event reporting (SGSN/MME, GGSN/PGW, PCRF): + +- The CN entity for MTC event reporting shall send MTC Event report to the intermediate node (e.g. MTC Monitoring GW or IWKF) located in the HPLMN. +- A new network entity (e.g. MTC Monitoring GW) may be introduced and new interfaces are introduced. + +**Editor's note:** Whether there are additional impacts in roaming scenario is FFS. + +## 6.25.4 Evaluation + +## 6.26 Solution – Rejecting RRC Connection and Channel Requests by the eNodeB/RNC/BSS + +### 6.26.1 Problem Solved / Gains Provided + +See clause 5.12, "Key Issue – Signalling Congestion Control", more specifically overload control, and 5.14 "Key Issue – Potential overload issues caused by Roaming MTC devices". + +### 6.26.2 General + +This solution introduces the concept that accesses from certain MTC devices (e.g. "time tolerant" Utility meters) can be treated as a low priority access and could be rejected with an extended wait time. + +In the abnormal case of massive simultaneous connection requests it is of benefit that the connection requests be rejected as early on as possible in the access procedure such that resources are not consumed or induced further into the network. + +NOTE: It is assumed that the network is appropriately dimensioned i.e. congestion or close to maximum resource usage is an abnormal situation. + +This solution addresses (unexpected) unacceptable high load resulting from MTC devices in the Low-Priority-Access category. High load resulting from MTC devices out of this category is not covered. + +This is a solution that avoids problems in the network that affects both MTC devices that do and MTC devices (in the Low-Priority-Access category) that do not generate an unacceptable high load. + +In the case of priority indication being received from the MTC Device the RAN (E-UTRAN, UTRAN, GERAN) has the opportunity to reject the connection request with a wait time that is appropriate for the access priority indicated by the MTC Device. + +It is proposed that the existing wait time range in the rejection messages be extended to allow better control of such MTC "Time Tolerant" devices. + +It is proposed that a new "extended wait time" could potentially range in the order of minutes or even hours. + +With this potentially wide timer range the RAN could have for example the logic to assign a wait time ranging from 5 to 60 minute or even from 1- 24 hours to better control the MTC devices and ensure an even distribution of future incoming requests of low priority accesses into the system. + +Some care is needed to ensure that these rejections do not lead to network reselection attempts that repeatedly load the local competing networks. + +To ensure an even distribution of the re-initiated access attempts by a large group of "low priority access" MTC Devices, it is proposed that, when allocating the extended wait time for a MTC Device, eNB/RNC/BSS could apply randomization of the extended wait time within the overall maximum allowed wait time, and optionally allocate longer wait times to "low priority access" MTC Devices compared to that for normal MTC Devices. + +The randomized wait times allocated to MTC Devices should be different from one another as much as possible. On the other hand, for each MTC Device, the start time of re-initiation is the current time of rejection + randomized wait time. When the wait time is being randomized, the current time of rejection should also be taken into account to ensure that the start time of re-initiation of different MTC Devices is sufficiently different from one another. + +Alternatively, eNB/RNC/BSS could send one "reference wait time" to the MTC Devices, and each MTC Device calculates its own randomized offset time independently. Then for each MTC Device, the start time of re-initiation could be calculated as current time of rejection + reference wait time (from the network) + randomized offset (calculated by individual MTC Device). + +### 6.26.3 Impacts on existing nodes or functionality + +The E-UTRAN, UTRAN and GERAN would be impacted by the introduction of an extended and randomized wait time whose range would extend beyond the following documented values: + +- For E-UTRAN the RRC Protocol Spec (36.331 v.9.1.0) shows a *waitTime* of between 1-16 seconds for the *RRConnectionReject*. +- For UTRAN the RNC (25.331 RRC UTRAN) can return an *RRC Connection Reject* which includes a *waitTime* of between 0-15 seconds. +- For GERAN the BSS (TS 44.018 RRC) can return an *IMMEDIATE ASSIGNMENT REJECT* which includes *wait* indication octet (i.e. 0-255 seconds). + +E-UTRAN, UTRAN and GERAN devices and networks extended and randomized wait time support would benefit from support of the Low priority access value (see solution "Low Priority Access Indication") that is indicated by the MTC Device when the MTC Device attempts to connect to the network and evaluated by the RAN when allowing/rejecting the request. + +MME/SGSN in the case of MTC devices shall set the mobile reachable timer to be longer than the periodic update timer used by an MS and may take into consideration (i.e. through configuration) the value of the extended wait time that the RAN may use when rejecting channel requests in overload conditions. + +MTC Devices receiving an extended wait time shall start any necessary the periodic update procedure following expiration of the extended wait time. + +Impact on the MTC Device/UE + +Additional functionality for the communication module in MTC Device/UE for this solution includes: + +- Possibly randomizing the local offset time according to the reference wait time received in *RRConnectionReject/ IMMEDIATE ASSIGNMENT REJECT*, if such information is provided by the network. +- Not re-initiating further attach/connection requests before the extended wait time is expired. + +### 6.26.4 Evaluation + +Benefits: + +- Based on an existing concept of a wait time parameter in the E-UTRAN, UTRAN and GERAN protocols. +- Works in a roaming environment as solution is not dependent on coordinating any specific MTC application level identifiers between operators. Instead broad control is possible in the serving network based on devices making access attempts as a low-priority-access. If a rejection is required an extended wait time can be returned for those accesses. +- Low impact on existing 3GPP standards and products and may be feasible in Rel-10. +- allows for CN node specific load control in flex or sharing scenarios (in UTRAN and E-UTRAN, but not GSM) +- Provides a faster way to react to varying levels of overload/unused capacity compared to mechanisms relying on broadcasted system information (e.g. ACB). + +Drawbacks: + +- Doesn't allow to target specific MTC groups or applications +- Allows each unique low-priority-access device to send a connect request followed by a corresponding reject sent by the RAN, thus adding to the current congestion load in the RAN (vs, broadcasting which can prevent the remaining low-priority-access devices from sending any access requests). +- In the case that the MTC device also supports the Time Controlled feature, the calculated wait time may coincide with a Time Controlled "Forbidden Time Interval". This is not considered significant as the MTC device as per Time Control implementation would access the network at the next available Grant Time Interval. + +- Doesn't protect the core/centralized network elements in the case that, say, two M2M mobiles per cell access every cell in the network at the same time. + +## 6.27 Time Control Solution Summary + +This solution considers the Time Control MTC Feature Solutions thus far included in the TR and several that have not yet been included. The goal is to make progress towards understanding the solution space better and facilitating a comparison of alternatives. This solution neither replaces other existing solutions in the TR nor do the summarized solutions necessarily suffice as a 'key issue solutions.' + +**Table 6.27-1** + +| <b>Solution</b> | <b>Status</b> | <b>Randomization of Communication Window in the Grant Time Interval</b> | <b>Informs MTC Device of altered Grant Time Interval</b> | <b>Informs MTC Server or User of altered Grant Time Interval</b> | <b>Enforcement of Grant Time Interval and Forbidden Interval</b> | <b>Information Storage of Grant Time Interval and Forbidden Interval</b> | +|-------------------------------------------------------|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| +| 1) Network Access Control by the PLMN | 6.7 | Not considered in solution 6.7 yet. | (1) The MTC Server via application level data<br>(2) MME/SGSN via NAS initially or when the time period changes (accepting the first access outside the interval or informing when to use the network.) | "The network provides the information." | GGSN/P-GW (for charging and stopping data transmission.)<br>MME/SGSN may prevent access outside of the Grant Time Interval. | HLR/HSS, SGSN/MME may alter the Grant Time Interval to conform with local policies. | +| 2) "Randomized Time Control" [S2-102404] | t doc | Either in the HSS or in the MME or SGSN (if local policy is applied.) A time window is selected within the Grant Time Interval to uniformly distribute access | (1) O&M procedure<br>(2) NAS procedures as per 6.7 or during Grant Time Interval initiated by the MME/SGSN (notifying the MTC Device). Also synchronizes the device with respect to the MME/SGSN. | Not discussed | As 6.7 | In HSS/HLR (the time window is stored along with the grant time interval and forbidden interval). | +| 3) "Time control for MTC Time Controlled" [S2-102588] | t doc | The MME or SGSN selects a random start time and duration. Local policy may reset the start time and duration to a new value. | NAS procedure communicate the time window during attach or connection request. A time stamp may be added by the network to synchronize the MTC Device to the network | Not discussed | As 6.7 | In HSS/HLR (the grant time interval and forbidden interval) | +| 4) "Allowed Time Period after TAU/RAU" [S2-102572] | 6.17 | The TAU or RAU will occur randomly within the Grant Time Interval. | "The EPS network configures the MTC Device ... according to operator requirements and MTC subscription options." NAS will be used | Not discussed | Not discussed | Presumably in the HSS/HLR for subscription options. | + +| Solution | Status | Randomization of Communication Window in the Grant Time Interval | Informs MTC Device of altered Grant Time Interval | Informs MTC Server or User of altered Grant Time Interval | Enforcement of Grant Time Interval and Forbidden Interval | Information Storage of Grant Time Interval and Forbidden Interval | +|---------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| | | | to inform the length of the communication window. | | | | +| 5) "Randomized triggering of time-controlled MTC operations" | 6.21 | 1) the MTC Device<br>2) the MTC server | interval from the network or the MTC Server | by the network | Not discussed | Not discussed | +| 6) PCRF based network access control [S2-102475] | t doc | not discussed | The PCRF informs the MTC Device during IP CAN session establishment | The PCRF receives the grant time interval from the SPR | The PCRF rejects IP CAN sessions outside of the grant time interval or terminates IP CAN sessions that exceed the time limit. | SPR | +| 7) Time control according to MTC Device Identifiers [S2-102330] | t doc | Use of MTC Identifier to randomly distribute at a fixed point (based on a known start time and a randomized offset) | not discussed | not discussed | not discussed | not discussed | +| 8) Time controlled feature via Operator and MTC Business Agreements [S2-102436] | t doc | not discussed (It is asserted that the application will be 'well behaved' and randomize communication through the grant time interval.) | not discussed | off-line (the MTC User informs the MTC Server) | not discussed | not discussed | +| 9) MTC Request to Release Resources [S2-102519] | t doc | not discussed | the network sends this using NAS as part of detach or S1 release. The MTC Device may propose a time. | "The network then ... forwards the ... notification to the MTC User" | not discussed | not discussed | +| 10) Proactive congestion control [S2-102225] | t doc | Randomization algorithm in the device | Periodically through broadcast | not discussed (the network or the UE may notify the MTC Server/User when communication is granted) | not discussed (as 6.7) | Not necessary when this method is used. | + +## 6.28 Solution - Access Control by RAN + +### 6.28.1 Problem Solved / Gains Provided + +See clause 5.12, "Key Issue – Signalling Congestion Control", more specifically congestion control and overload control and clause 5.14, "Key Issue – Potential overload issues caused by Roaming MTC devices." + +### 6.28.2 General + +To avoid and handle the overload situations caused by MTC Devices, the MME/SGSN can send OVERLOAD START message to the RAN node, O+M action can be directed to the RAN node, and/or internal congestion alarm in RAN node can trigger the broadcasting of access control for MTC Devices to avoid further access to the network. The OVERLOAD START message, O+M action and internal congestion alarm in the RAN can include specific MTC Access Class Barring (ACB) overload actions as follows: + +- Coarse-grained access control for MTC Devices with "Low-Priority-Access". MME/SGSN, O+M action and/or internal RAN congestion alarm will request MTC access control with indication of "Low-Priority-Access". Based on that, RAN will broadcast "access barring for MTC Devices with Low-Priority-Access" in system information. +- Fine-grained access control for MTC Devices with specific group. MME/SGSN O+M action and/or internal RAN congestion alarm will provide group related access control information, (e.g. an MTC Group or specific APN,) to RAN node. Based on that, RAN node will broadcast "access barring for MTC Devices with specific group" in the system information; or +- Coarse-grained access control for MTC Devices with specific "PLMN type". MME/SGSN, O+M action and/or internal RAN congestion alarm will provide PLMN type related control information, i.e. "MTC Devices that are not on their HPLMN or a PLMN in the (U)SIM's preferred PLMNs list", "MTC Devices that are not on their HPLMN or an Equivalent HPLMN", "MTC Devices that are not on their HPLMN" and "all MTC Devices", to RAN node and/or RAN will determine from internal. Based on that, RAN node will broadcast "access barring for MTC Devices with specific PLMN type" in the system information. + +MTC access control with different granularities could be triggered by signalling thresholds in the RAN, SGSN/MME and/or GGSN/PGW. In the case of the GGSN/PGW, the GGSN/PGW informs the SGSN/MME when a congestion threshold is exceeded. P-GW/GGSN can reject the connection request for a particular MTC group, e.g. a specific APN, when the congestion control policy is triggered, and indicates a delay value to the MME/SGSN in the reject message. The delay value is set by P-GW/GGSN for the requested MTC group. By receiving the reject message, MME/SGSN can reject the connection request described under "6.22 Solution – Rejecting connection requests by the SGSN/MME" for the corresponding MTC group until the delay value expires, and the MME/SGSN can also be triggered to provide the congestion indication to RAN nodes. + +NOTE 1: This functionality is supported for both PMIP and GTP based S5/S8. + +**Editor's note:** It is FFS if and how access control for MTC Devices with specific groups can be triggered by signalling thresholds in the RAN. + +**Editor's note:** This functionality is supported for both PMIP and GTP based S5/S8. It is FFS how PGW informs its congested status to the SGSN/MME. + +When a SGSN/MME needs to trigger a MTC access control due to the MME/SGSN's load situation or the congestion indication received from P-GW/GGSN,, the SGSN/MME sends the specific OVERLOAD START message to the RANs (eNodeBs/RNCs/BSCs) specifically for MTC Devices, i.e. OVERLOAD START message with an indication of the type (i.e. "Low-Priority-Access" or one of the "PLMN type" options) or group (e.g. MTC Group Identifier) of MTC access to be barred and any load status information. + +Similar to general MME overload control procedures in TS 23.401 [5], the set of eNodeBs/RNCs/BSCs to send an OVERLOAD START message should be randomly selected (so that if two SGSNs/MMEs within a pool area are overloaded, they do not both send OVERLOAD START messages to exactly the same set of eNodeBs/RNCs/BSCs) and, in total, be proportional to reflect the amount of load that the SGSN/MME wishes to reduce. In addition, the set of eNodeBs/RNCs/BSCs to consider sending an OVERLOAD START message may be limited to a particular location area or subset of eNodeBs/RNCs/BSCs (e.g. where MTC Devices of the targeted type are registered). + +The RAN uses the information from the SGSN/MME in the OVERLOAD START message, from the O+M action or from the internal RAN congestion alarm to determine if and when to broadcast the corresponding MTC ACB information in the system information to the UEs. Any barring factor and/or barring time or functional equivalent included in the barring information will be derived internally by RAN (similar to general ACB) but should take into consideration any load status information provided by the SGSN/MME or input from the O+M action. The RAN uses the information from the SGSN/MME in the OVERLOAD STOP message, from the O+M action, or from internal RAN congestion alarms to determine if and when to stop broadcasting the corresponding MTC ACB information in the system information to the UEs. The RAN should not have to wait for indication from or be prevented by SGSN/MME from starting or stopping the broadcast of a particular MTC ACB action. + +NOTE 2: OVERLOAD START/STOP messages from SGSNs/MMEs to RAN are considered amongst other inputs that can influence the decisions RAN ultimately makes in management of MTC access barring. + +When using pooling of CN nodes, the RAN shall only broadcast a SGSN/MME-triggered MTC overload action when all connected MMEs/SGSNs from the same pool area have enabled the MTC overload action. When only a subset have triggered the MTC overload action, the RAN shall instead reject RRC connection requests, as described in clause 6.26, for specific access to a barring SGSN/MME from a MTC Device type or group that the SGSN/MME is barring. An O+M or internally RAN-triggered MTC overload action can be broadcasted regardless of the set of SGSNs/MMEs that have enabled the same MTC overload action. + +The MTC Device which is going to access the network will receive the broadcasted system information for MTC access barring and uses this information to determine whether this access is barred or not. If so the corresponding MTC Devices will delay the access to the network. Subsequent initial access attempts to the network will be randomized by each MTC Device using the last barring time or equivalent value(s) provided by the RAN. + +**Editor's note:** Broadcasting access control barring information in a large area, e.g. whole PLMN, caused by GGSN/PGW congestion should be avoided. + +A MTC Device priority (i.e. "low" or "normal") shall be configured in a MTC Device in order to determine when "Low-Priority-Access" is barred by the network, + +**Editor's note:** It is FFS how to configure the MTC access priority in the MTC Device, e.g. SIM OTA or OMA DM. + +**Editor's note:** It is FFS how MTC Device priority will be applied to all applications on the device for Rel-10. + +The operator may configure in a MTC Device (using OMA DM) a penalty level to be applied (i.e. weighted) to the received barring factor and/or barring time or equivalent when MTC Low-Priority-Access is barred by all MTC Devices. + +NOTE: When using a penalty level, computed barring values should not be less than originally ordered by RAN in order to prevent an MTC Device from gaining an advantage in access. + +## 6.28.3 Impacts on existing nodes or functionality + +Impact on the RAN: + +Additional RAN functionality for RAN-triggered solution includes: + +- For coarse-grained MTC access barring: + - Determining when overall congestion situation within the RAN warrants starting/stopping a particular MTC ACB action + - Broadcasting MTC access barring with the indication of the type (i.e. "Low-Priority-Access or one of the "PLMN type" options) +- For fine-grained MTC access barring: + - Determining the MTC Group or APN that is causing congestion within RAN. + - Determine the barring time and/or barring factor or equivalent for a new MTC access barring start operation. + - Broadcasting MTC access barring with the indication of the type or group of MTC access to be barred, barring time and/or barring factor or equivalent in the system information to the UEs. + +- Control via O+M input to the RAN node is less 'automatic' but impacts fewer network entities and may attract the human/management attention needed to handle cases of very high overload. + +Additional RAN functionality for CN-triggered solution includes: + +- Receive the OVERLOAD START/STOP messages from the SGSN/MME with the indication of the type (i.e. "Low-Priority-Access" or one of the "PLMN type" options) or group of MTC access to be barred. +- Determine if CN provided OVERLOAD START/STOP request influences MTC ACB and/or RRC rejection operations for the requesting CN node and other CN nodes sharing a pool area with the requesting CN node. +- Determine the barring time and/or barring factor or equivalent for a new MTC access barring start operation. +- Broadcasting MTC access barring with the indication of the type (i.e. "Low-Priority-Access" or one of the "PLMN type" options) or group of MTC access to be barred, barring time and/or barring factor or equivalent in the system information to the UEs. + +Impact on the SGSN/MME + +Additional SGSN/MME functionality for CN-triggered solution includes: + +- For coarse-grained MTC access barring: + - Determining when overall congestion situation, within SGSN/MME or upon reception of congestion indication from GGSN/PGW, warrants starting/stopping a particular MTC ACB action. +- For fine-grained MTC access barring: + - Determining the MTC Group or APN that is causing congestion, within SGSN/MME, or upon reception of indication from GGSN/PGW. + - (For GGSN/PGW-triggered) Indicating MTC Group ID to GGSN/SGW +- Determining the proportion and specific set of RANs to send a new MTC ACB action. +- Sending the OVERLOAD START/STOP messages to the targeted RANs specifically for MTC Devices with the indication of the type (i.e. "Low-Priority-Access" or one of the "PLMN type" options) or group of MTC access to be barred. +- For penalty level configuration: + - A mechanism is required to configure a penalty level in the MTC Device to be used for processing MTC access barring information for Low-Priority-Access attempts by the MTC Device. + +NOTE: The detailed message name and indication parameters should be specified in stage 3. + +Impact on the HSS/HLR + +Additional HSS/HLR functionality for CN-triggered solution includes: + +- For fine-grained MTC access control: + - Storing the MTC Group Identifier as part of the subscription profile of an MTC Device. + +Impact on the SGW + +**Editor's note:** It is FFS whether such information may be transferred via PCC, if PMIP is used on S5/S8. + +Additional SGW functionality for PGW-triggered solution includes: + +- For coarse-grained MTC access barring: + - Forwarding the overall PGW congestion situation indication received from PGW to MME +- For fine-grained MTC access barring: + - Forwarding MTC Group IDs received from MME to PGW + +- Forwarding the congestion situation indication received from PGW to MME for a particular MTC Group or APN + +Impact on the GGSN/PGW + +Additional GGSN and PGW functionality for GGSN/PGW-triggered solution includes: + +- The GGSN/PGW needs to provide the different overload actions for MTC Devices to the SGSN/MME node. +- For coarse-grained MTC access control: + - Detecting the overall GGSN/PGW congestion condition. + - Indicating the overall GGSN/PGW congestion situation to SGSN/MME. +- For fine-grained MTC access control: + - Receiving MTC Group ID from SGSN/SGW. + - Determining the MTC Group or APN that is causing congestion within GGSN/PGW. + - Indicating the congestion situation within GGSN/PGW to the SGSN/SGW for a particular MTC Group or APN. + +Impact on the MTC Device / UE + +Additional functionality for the communication module in MTC Device / UE with this solution includes: + +- The MTC Device needs to recognize the different MTC specific access control types and groups that are applicable to it. +- The MTC Device uses the latest received MTC access barring information to determine if, and for how long, not to initiate any access requests. +- For penalty level configuration: +- A mechanism is required to configure a penalty level in the MTC Device to be used for processing MTC access barring information for Low-Priority-Access attempts by the MTC Device. + +## 6.28.4 Evaluation + +Benefits: + +- RAN and core network resource consumption can be avoided during congestion situation and there will be no further AS and NAS signalling initiated from the targeted, access barred MTC Devices. +- Can be used for both congestion control as well as overload control as described in clause 5.12. +- Can reuse existing UE functionality (e.g. GSM Immediate Assignment Reject already specifies Wait Times out to 255 seconds). +- With broadcasting MTC access barring it may be possible to completely stop congestion even if RRC and/or NAS signalling are almost instantaneously overwhelmed with access attempts. +- Different combinations of MTC ACB actions provides for a low impact on existing 3GPP standards and products that may be feasible in Rel-10 (e.g. coarse-grained via RAN and/or SGSN/MME triggering) while allowing reuse for expanded functionality in Rel-11 (e.g. fine- and coarse-grained via RAN, SGSN/MME and/or GGSN/PGW). +- Complements RRC and NAS access request rejection mechanisms i.e. initial few requests rejected and remaining subsequent requests prevented through MTC access barring. +- Barring time randomization or equivalent prevents simultaneous subsequent initial access attempts by a previously blocked group. +- Provides solution for "unhappy" VPLMN operator to handle signalling and VLR space congestion from roaming MTC Devices. + +- For RAN triggered options: + - Does not impact CN entities (coarse-grained options). + - Permits the VPLMN to activate barring because of a situation reported by another PLMN operator and/or due to severe abnormalities in the levels of core network signalling to particular HSS(s). +- For CN triggered options: + - Allows aggregated MTC specific congestion at the SGSN/MME and/or GGSN/PGW to be stopped and/or prevented without guaranteed signalling bandwidth for worse-case individualized access request rejections. +- For O+M triggered options: + - An effective yet relatively simple solution for catastrophic overload is probably the use of O+M controlled "access class barring" functionality that can be used to bar e.g.: + - "low value" M2M devices that are not on their HPLMN or a PLMN in the (U)SIM's preferred PLMNs list; + - "low value" M2M devices that are not on their HPLMN or an Equivalent HPLMN; + - "low value" M2M devices that are not on their HPLMN; + - "low value" M2M devices; + - This may be achievable with just 2 broadcast bits. Reducing the core network load by X% can be achieved by the O+M barring of X% of the base stations/Node Bs/eNodeBs. +- For coarse-grained options: + - Not dependent on implementation of MTC Group Identifier support. + - Allows for efficient encoding of MTC access barring information that should fit in the spare bits of pre-existing System Information messages used for Access Class Barring. +- For fine-grained options: + - Does not impact/block MTC applications that are not causing a problem. + - When a MTC application uses a dedicated APN, the specific MTC application that causes the congestion can be targeted. +- For penalty level configuration: + - When broadcast MTC barring information includes uniform barring info toward all MTC Devices, a penalty level can be used to discriminate some MTC Devices (i.e. this selectively assigns MTC Devices an advantage or disadvantage). + +#### Drawbacks: + +- The broadcast information for access barring needs to be enhanced to restrict the further MTC device access with different granularity triggered by RAN, SGSN/MME or GGSN/PGW. +- Initially, from the time determined to start rejecting and barring connect requests from MTC Devices from a particular group until the barring is broadcast, not as fast as RRC and NAS signalling access request rejections. +- For CN-triggered options: + - When using pooling of core network nodes, care is needed in the use of ACB functionality as it can limit load on all MMEs/SGSNs/MSCs in the pool. + - Added complexity during MME/SGSN overload to determine cause of overload type (e.g. Group/APN, PLMN type and/or "Low-Priority-Access") in order to request specific MTC overload action when not combined with rejecting connection requests by the SGSN/MME in clause 6.22 (can uses same mechanisms within CN to make this determination). + +- Added complexity in RAN to evaluate CN MTC overload action request amongst status of other CNs, O+M request and internal RAN MTC overload process. +- For coarse-grained options: + - Impacts MTC applications that are not causing a problem. +- For fine-grained options: + - Requires enhancements for broadcasting one or more unique MTC Group Identifiers. + - Requires enhancements to HLR/HSS to store the MTC Group Identifier as part of the subscription profile of an MTC Device + - Requires new mechanisms for detecting and indicating between nodes the MTC Group or APN that is causing congestion + +## 6.29 Solution – IP address assignment mechanisms + +### 6.29.1 Problem Solved / Gains Provided + +See clause 5.3. "Key Issue – Ipv4 addressing". + +NOTE: The stage 1 requirement that an MTC Server in a public address space can successfully send a mobile terminated message to the MTC Device inside a private Ipv4 address space is not addressed by this solution. + +### 6.29.2 General approach based on existing standards + +This solution shows how the key issue Ipv4 addressing can be addressed based on the mechanisms in the existing standards. Minor further optimization might be required. The alternatives outlined should be seen as examples and additional alternatives or variants may exist. An operator can choose to deploy one of the configurations for all its customers or deploy different configurations for different customers. + +The MTC server is either deployed by the PLMN operator or by an application provider who owns an MTC Server and uses a specific APN assigned by the PLMN. In both cases a tunnelling mechanism is used between the GGSN/P-GW and the PDN of the MTC server to allow carrying the IP packets enabling assignment of private IP addresses to the MTC Devices. The tunnelling allows for connecting the PLMN with the MTC server(s) using public IP networks. Furthermore that tunnelling allows for setting up private network with multiple GGSNs/P-GWs and multiple MTC servers where every GGSN, P-GW or MTC server can be deployed at a different location. By using a separate APN per application (provider) the MTC servers from different applications can use the same overlapping private IP addresses as needed without the need for the network to implement a NAT function as the MTC devices and MTC servers belonging to one application share the same private IP address space. + +Such a segregation of the traffic also reduces the motivation for subscribers to try to use this subscription for other purposes (e.g. free Internet service) since they cannot reach the public Internet. It also helps to simplify other operational issues, such as monitoring that all the MTC devices obey potential access restrictions like being active only during the network's low traffic periods. Traffic within this private intranet at other times would indicate the devices or applications are not working properly. + +A PGW/GGSN can serve one or multiple APNs. A GGSN/PGW can be configured to use an AAA server for address allocation and protocol configuration options notification. When serving multiple APNs the PGW/GGSN may be configured with an AAA server per APN. The use of the AAA server and the communication and security feature needed to dialogue with this / those AAA server(s) e.g. tunnel, IPSec security association are specified in TS 29.061 [4]. + +The following figure shows just one MTC server per PDN/APN. There may be however multiple MTC Servers in the same PDN/APN. + +![Diagram illustrating IP address assignment when the MTC Server is owned by the MNO or by a M2M Application Provider using a specific dedicated APN. On the left, multiple MTC Devices (Device 1, Device i, Device j, Device k) are connected to GGSN/PGW units (A, B, C). These units are connected via tunnels to three separate PDNs (PDN A, PDN B, PDN C). Each PDN contains an MTC server (MTC server 1, 2, 3). All three servers are connected to a single 'Overlapping private IP address pool e.g. (10.0.0.0)'.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +The diagram shows a central column of GGSN/PGW units labeled A, B, and C. To the left, MTC Devices (Device 1, Device i, Device j, Device k) are connected to these units. Device 1 connects to GGSN/PGW A, Device i to GGSN/PGW A, Device j to GGSN/PGW B, and Device k to GGSN/PGW C. Each GGSN/PGW unit is connected via a tunnel to a specific PDN: GGSN/PGW A to PDN A, GGSN/PGW B to PDN B, and GGSN/PGW C to PDN C. Each PDN contains an MTC server: PDN A has MTC server 1, PDN B has MTC server 2, and PDN C has MTC server 3. All three MTC servers are connected to a common 'Overlapping private IP address pool e.g. (10.0.0.0)'. + +Diagram illustrating IP address assignment when the MTC Server is owned by the MNO or by a M2M Application Provider using a specific dedicated APN. On the left, multiple MTC Devices (Device 1, Device i, Device j, Device k) are connected to GGSN/PGW units (A, B, C). These units are connected via tunnels to three separate PDNs (PDN A, PDN B, PDN C). Each PDN contains an MTC server (MTC server 1, 2, 3). All three servers are connected to a single 'Overlapping private IP address pool e.g. (10.0.0.0)'. + +**Figure 6.29.2-1: IP address assignment when the MTC Server is owned by the MNO or by a M2M Application Provider using a specific dedicated APN** + +In clause 6.29.5, the MTC Server is located on Internet (i.e. using an APN providing Internet connectivity) and hence no tunnelling is required between the GGSN/PGW and the MTC Server. This solution in clause 6.29.5 also assumes no NAT is used and is hence optimized for usage of Ipv6 addresses or public Ipv4 addresses. + +### 6.29.3 IP address assignment by the PDN of the MTC server + +A RADIUS or Diameter client at the GGSN/P-GW can obtain an IP address from the MTC server (providing an AAA server) upon receiving a PDP context/PDN connection request with the APN corresponding to the MTC server and assign that address to the MTC Device. The GGSN/P-GW indicates an MTC device provided PDN specific ID, an MSISDN or an IMSI to the MTC server when obtaining an IP address. Thereby the MTC server knows the IP address for an MTC device. + +The application in the MTC Device may provide a PDN specific id potentially together with a related password in e.g., the PCO IE at PDP Context /PDN Connection establishment. Alternatively a PDN specific ID may be provided by the SGSN/MME at PDP Context /PDN Connection establishment. The PDN specific ID or the MSISDN or the IMSI are used to identify the MTC device. The ID is conveyed to the MTC Server when an IP address is requested via a RADIUS or Diameter interface from the MTC Server. The IP address assigned can be a private or public IP address. Overlapping IP address ranges can be handled by using different APNs. + +A separate AAA server can be used to enable multiple MTC servers to forward MT data to an MTC device. The GGSN/P-GW obtains IP addresses from the AAA server and the AAA server updates the DNS entries of the DNS server functionality administered by the PDN with the assigned IP address. The MTC servers or other entities of the MTC User query the DNS server for the IP addresses of the MTC devices. + +NAT functionality (along with related ALG) can be implemented by the MTC Server or on a separate entity if needed by the MTC business logic. + +### 6.29.4 IP address assignment by the GGSN/P-GW + +This is an alternative for the address allocation described in 6.29.3. In difference to the IP address allocation by an AAA server from the MTC specific PDN here the IP address is assigned by the GGSN/P-GW from a specific private or public address pool that is used for this particular APN. In the case when the address is a private, traffic will be tunnelled to the MTC Server(s). + +The rest of the approach is the same as for 6.29.3. The application in the MTC Device may provide its PDN specific device id in e.g., the PCO IE at PDP Context /PDN Connection establishment. Alternatively a PDN specific ID may be provided by the SGSN/MME at PDP Context /PDN Connection establishment. The PDN specific ID, or IMSI or MSISDN are used as identity for the MTC device. Although the IP address is assigned locally, there can be RADIUS or Diameter signalling providing the AAA server with the IP address and the identity, which triggers the AAA server to update the DNS entry of the DNS server functionality administered by the PDN with a domain name including the + +identity and the IP address. The same mechanism needs to be used to update the MTC Device DNS entry once the IP address is released by the GGSN/P-GW. + +An alternate to the use of DNS is that the MTC Server receives AAA accounting messages from the GGSN/P-GW. The AAA accounting messages provide the MTC Server with the IP address assigned to the UE. From that the MTC server can also deduce the presence of the device (at accounting start) as well as when it is no longer available (e.g. accounting stop). This may for example be used by the MTC Server to decide when device triggering is required or not. + +## 6.29.5 MTC Server located on Internet and public IP addresses for MTC devices + +For this scenario a dedicated APN with public IP addresses is used for the MTC Server. A general APN for Internet access might not be used as the AAA server needs to provide a special interface towards MTC servers and also because updating an AAA server by a GGSN/P-GW is not necessarily required for every Internet APN. The IP address allocation is done by either the GGSN/P-GW or by an AAA server within the PLMN domain. When the MTC device application registers its ID (PDN specific ID, IMSI, MSISDN) at the MTC server the MTC server can use an $S_{MTC}$ interface to verify with the AAA server whether the MTC device with the specific ID got the IP address allocated. + +The basic idea of the proposal is that it is left for the application layer in the MTC Device and the MTC Server to do the necessary registration of the MTC device and make an MTC device ID and its IP address known in the MTC Server. The 3GPP system provides the communication connection and a means to verify that the IP address is assigned to a specific ID (IMSI, MSISDN, PDN specific ID). A notification of bearer releases can optionally be provided to the MTC Server, e.g. for cases when the MTC Device cannot deregister because of lost coverage. Existing protocols and nodes are used in the 3GPP system and enhanced for this scenario here. This scenario assumes public IPv4 addresses or IPv6 addresses. + +**Editor's note:** In case MTC Monitoring is part of Rel-10, the optional notification of bearer releases mentioned above may be replaced by corresponding MTC Monitoring features. + +![Diagram illustrating the registration and authentication process between an MTC Device and an MTC Server. The diagram shows the flow of messages: 1. PDP Context / PDN Connection establishment from the Communication Layer to the GGSN/P-GW. 2. SGI/Gi RADIUS from the GGSN/P-GW to the AAA server. 3. Registration from the Application Layer to the MTC Server. 4. SMTc interface from the MTC Server to the AAA server. 5. Response from the AAA server to the MTC Server.](88066268366ca160709e20f13ed8f356_img.jpg) + +``` + +graph LR + subgraph MTC_Device [MTC Device] + AL[Application Layer] + CL[Communication Layer] + end + subgraph Network [3GPP scope] + PGW[GGSN/P-GW] + AAA[AAA] + end + subgraph MTC_Server [MTC Server] + MS[MTC Server] + end + + CL -- "1 PDP Context / PDN Connection establishment" --> PGW + PGW -- "2 SGI/Gi RADIUS" --> AAA + AAA -- "4 SMTc" --> MS + MS -- "5" --> AAA + AL -- "3 Registration" --> MS + +``` + +Diagram illustrating the registration and authentication process between an MTC Device and an MTC Server. The diagram shows the flow of messages: 1. PDP Context / PDN Connection establishment from the Communication Layer to the GGSN/P-GW. 2. SGI/Gi RADIUS from the GGSN/P-GW to the AAA server. 3. Registration from the Application Layer to the MTC Server. 4. SMTc interface from the MTC Server to the AAA server. 5. Response from the AAA server to the MTC Server. + +**Figure 6.29.5-1: MTC Device doing registration at the MTC Server, authenticating the IP address, and subscribing to bearer releases from the network** + +The flow of events in the figure above: + +1. The device establishes its communication connection by attaching to the network and creating a PDP Context or PDN Connection. +2. The Sgi/Gi/RADIUS protocol as specified in TS 29.061 [4] clause 16 is used to provide the IP address of the device to a AAA server. The AAA server stores the IP address as long as the bearer is active together with an ID (IMSI, MSISDN, PDN specific ID provided by MTC device in PCO). Optionally the PGW/GGSN may let the AAA do the IP address allocation. If a PDN specific ID is used the AAA server needs to be configured with a PDN specific ID for each MSISDN or IMSI. If a PDN specific ID is used the AAA server needs to verify that the UE provided ID matches the GGSN/P-GW provided IMSI or MSISDN. However the effort of configuring the UE might be avoided and the configuration of the AAA server, which is needed for verifying a UE provided ID, can directly be used to map the PLMN internal IMSI to an ID that can be used by the MTC application. + +The AAA Server is deployed in the PLMN. + +3. The application in the MTC Device registers at the MTC Server. At a minimum the PDN specific ID or the IMSI or the MSISDN and the IP address of the device is provided. + +**Editor's note:** It is FFS how to handle communication scenarios with multiple MTC Servers belonging to the same application/APN/PDN. + +4. The MTC Server checks at the AAA Server the relationship between the IP address and the MTC Device provided ID thus checking the validity of the MTC Device provided id. This checking is the same mechanism as the GIBA mechanism that is already specified in TS 33.203. Only the PDN specific ID allocation needs to be managed in a different way. + +NOTE: Similar restrictions and limitations apply as with GIBA, e.g. the IP address spoofing needs to be prevented. + +5. A notification may optionally be sent to the MTC Server at a later stage when the PDP Context/PDN Connection is released and the IP address of the Device becomes invalid. + +## 6.29.6 Impacts on existing nodes or functionality + +This solution has a low impact on the existing mobile system as: + +- RADIUS client is already part of the GGSN/P-GW as per TS 29.061 [4]; +- Need to add a mechanism to dynamically update the DNS function in the MTC Server or on a separate DNS server. The existing RADIUS client in the GGSN (accounting message) may be used; in that case, the AAA server may need new functionality if not located on the MTC server. + +An MTC device that needs to support simultaneous access to different MTC Servers associated with different APNs establishes multiple PDN connections and support multiple IP addresses. + +## 6.29.7 Evaluation + +Benefits: + +- Avoids the need for NAT in the operator network as overlapping private IP addresses can be used among different MTC Servers on different APNs; +- Minimum or no impact on the existing standard/ existing Core Network nodes; +- the solutions described in 6.29.3 and 6.29.4 are generic IP-level solution that does not rely on application-level identifiers (e.g. SIP URI); +- The solution does not rely on alternative communication channels (e.g. SMS) for delivery of a "push" stimulus to an attached MTC device with an established PDN connection; + +Drawbacks: + +- requires tunnelling mechanism to be used between the GGSN/P-GW and the PDN of the MTC Server to enable assignment of private IP addresses to the MTC Devices; +- if the MTC device needs to have simultaneous access to MTC Servers associated with different APNs, the solutions described in 6.29.3 and 6.29.4 require that the MTC device support multiple PDN connections (i.e. multiple IP addresses); +- the solutions described in 6.29.3 and 6.29.4 may not be suitable for local breakout scenarios; +- the solution in 6.29.5 works with Ipv6 and public Ipv4 addresses only. + +## 6.30 Solution - MME/SGSN overload control by DL MTC traffic throttling + +### 6.30.1 Problem Solved / Gains Provided + +See clause 5.12, "Key Issue – Signalling Congestion Control". + +## 6.30.2 General + +An MME or SGSN starting to experience overload should be able to trigger partial or complete throttling of the signalling traffic generated by low priority MTC devices/applications while still allowing normal operations for other traffic (e.g. voice, data, signalling). + +This solution specifically addresses throttling of DL traffic received on low priority PDN connections for MTC devices in ECM-Idle state or PMM-Idle mode, i.e. traffic for which the SGW would normally send a Downlink Data Notification message to the MME/S4-SGSN to trigger a network-initiated service request procedure. + +An S4-SGSN or MME starting to experience overload (i.e. whose load exceeds a threshold to start MTC low priority traffic throttling) may reduce its load by requesting the SGW to throttle DL low priority MTC traffic for MTC devices in idle mode according to a throttling factor (%) and for a throttling delay specified in the request, e.g. within the Downlink Data Notification Ack message. + +During that throttling delay, the SGW drops DL packets received on all its PDN connections marked as low priority served by that MME/S4-SGSN and without an S1/12 bearer in proportion to the throttling factor, and sends a Downlink Data Notification message to the MME/S4-SGSN only for the non throttled PDN connections. + +The SGW resumes normal operations at the expiry of the throttling delay. The last received value of the MTC throttling factor and throttling delay supersedes any previous values received from that MME/S4-SGSN. The reception of an "MTC throttling delay" restarts the SGW timer associated with that MME/S4-SGSN. + +When dropping a DL IP packet the SGW may send an ICMP packet (e.g. ICMP "destination un-reachable") that should tell the source that there is no use in repeating the packet. + +When setting up the PDN connection, the MME/S4-SGSN signal to the SGW whether the PDN connection is for low priority MTC traffic or not. + +![Sequence diagram illustrating the MTC throttling mechanism. The diagram shows interactions between eNB, MME, S-GW, and P-GW. It starts with 'start of MME overload'. The P-GW sends a 'DL user plane packet' to the S-GW. The S-GW sends a 'Downlink Data Notification' to the MME. The MME responds with 'Downlink Data NotificationAck' specifying 'throttle 50% of low prio DL MTC traffic, for duration T'. The S-GW then receives another 'DL user plane packet' and, during period T, either throttles traffic or sends a DDN message according to a reduction factor. If no throttling, the S-GW sends a 'Downlink Data Notification' to the MME, which triggers 'Paging' in the eNB and a 'service request procedure'. If throttling, the S-GW sends an 'ICMP unreachable destination' message to the P-GW.](f502d41e990d86acbbd785962f2af138_img.jpg) + +``` + +sequenceDiagram + participant eNB + participant MME + participant S-GW + participant P-GW + + Note left of MME: start of MME overload + P-GW->>S-GW: DL user plane packet + S-GW->>MME: Downlink Data Notification + MME-->>S-GW: Downlink Data NotificationAck +("throttle 50% of low prio DL MTC traffic, for duration T") + P-GW->>S-GW: DL user plane packet + Note right of S-GW: During period T, if low prio,traffic +throttle or send DDN msg according +to reduction factor + alt If no throttling + S-GW->>MME: Downlink Data Notification + MME-->>S-GW: Downlink Data NotificationAck + MME-->>eNB: Paging + Note left of eNB: service request procedure + else If throttling + S-GW-->>P-GW: ICMP unreachable destination + end + +``` + +Sequence diagram illustrating the MTC throttling mechanism. The diagram shows interactions between eNB, MME, S-GW, and P-GW. It starts with 'start of MME overload'. The P-GW sends a 'DL user plane packet' to the S-GW. The S-GW sends a 'Downlink Data Notification' to the MME. The MME responds with 'Downlink Data NotificationAck' specifying 'throttle 50% of low prio DL MTC traffic, for duration T'. The S-GW then receives another 'DL user plane packet' and, during period T, either throttles traffic or sends a DDN message according to a reduction factor. If no throttling, the S-GW sends a 'Downlink Data Notification' to the MME, which triggers 'Paging' in the eNB and a 'service request procedure'. If throttling, the S-GW sends an 'ICMP unreachable destination' message to the P-GW. + +Figure 6.30.2-1 + +Editor's note: Any relation to ARP for the throttling mechanism in SGW is FFS. + +Editor's note: Throttling in GPRS core is FFS. + +This solution allows selective throttling of low priority DL MTC traffic in case of overload in the EPS Network, at the closest point of the source of the DL traffic. This allows to reduce immediately the load in MME/SGSN induced by low priority DL MTC traffic. It also allows to stop the sending of further DL packets by the application. + +### 6.30.3 Impacts on existing nodes or functionality + +MME/S4-SGSN signals MTC throttling parameters to the SGW. + +The SGW throttles DL low priority MTC traffic according to the MME/S4-SGSN request. + +### 6.30.4 Evaluation + +This approach enables an MME/SGSN to reduce its load by reducing the signalling traffic resulting from DL user traffic received for PDN connections marked as low priority for MTC devices in ECM-Idle state or PMM-Idle mode (Downlink Data Notification / Downlink Data Notification Ack messages on S11/S4, paging and service request procedures). + +It provides mainly benefits by protecting MME/S4-SGSN from massive simultaneous push or poll transactions from ("badly implemented") MTC server for devices with established low priority PDN connections. + +It is complementary to an UL MTC signalling traffic throttling approach. + +## 6.31 Solution – Rejecting connection requests at partial signalling links + +### 6.31.1 Problem Solved / Gains Provided + +See clause 5.12, "Key Issue – Signalling Congestion and Overload Control", more specifically congestion control. + +### 6.31.2 General + +MTC devices maybe concurrently attempt signalling interaction only in a limited area. That means the signalling congestion could occur just in one or several particular signalling links and no overall congestion appears on network elements. For example, in 2G network, the link congestion would be met frequently for Gb interface over Frame Relay because of limited capacity of the interface protocol. It is not appropriate to reject all the MTC related signalling requests receiving from every signalling link for the control of the congestion existed only at partial signalling links. + +**Editor's note:** It is FFS whether this problem can be addressed purely as a network element implementation issue or by means of an effect application of mechanisms available through SCTP, to be further studied in stage 3. + +#### Rejecting signalling requests at separate signalling links + +The signalling link could be the connection between BSC/RNC and SGSN or eNodeB and MME. SGSN/MME or other network functions (e.g. OAM) shall detect whether the congestion caused by MTC devices just occurs at the partial signalling links or the overall network node. Upon the congestion of the partial links, SGSN/MME can reject MTC related signalling requests received from other network nodes at one or several signalling links. + +#### Rejecting signalling requests at a single signalling link set + +A signalling link set contains all links connecting to a single BSC, RNC, eNodeB, RA or TA (List). The SGSN/MME or other network functions (e.g. OAM) shall detect whether the signalling congestion caused by MTC devices just occurs within one kind of link set or not. If yes, SGSN or MME can reject all MTC related signalling requests belonging to a BSC, RNC, eNodeB, RA or TA(List). + +The mechanism of back-off time to the MTC Device as described in the clause 6.22 is also applicable for this solution. + +### 6.31.3 Impacts on existing nodes or functionality + +Possible impacts on SGSN/MME + +- Rejection of a connection request targeted at a particular signalling link + +- Rejection of a connection request targeted at signalling links connecting to a BSC, RNC, eNodeB, RA or TA(List). +- Detection if the congestion only occurs on one or several signalling links. +- Detection if the congestion only occurs on signalling links belonging to one BSC, RNC, eNodeB, RA or TA(List). +- Providing a reject cause including a back off time in the reject messages (same as the solution specified in 6.22), +- Determination of the back off time that is applicable for a particular MTC Device (same as the solution specified in 6.22). + +Possible impact on the MTC Device / UE + +- Same as the solution specified in 6.22. + +## 6.31.4 Evaluation + +Benefits + +Avoids that most innocent MTC signalling requests are rejected when congestion only occurs on partial signalling links. + +Drawbacks + +MME/SGSN will make more complex detections for the congestion. + +# 6.32 Solution – Rejecting connection requests based on request types + +## 6.32.1 Problem Solved / Gains Provided + +See clause 5.12, "Key Issue – Signalling Congestion and Overload Control", more specifically congestion control. + +## 6.32.2 General + +Sometimes the congestion is triggered only by part of MTC devices controlled by one APN or one MTC group. For example, parts of MTC devices belonging to an APN concurrently attach to the network and cause the congestion for the network node. At the same time the other MTC devices with the same APN that already have PDP context and are in IDLE state attempt Service Request to the network, and their requests will be rejected. + +Additionally, the different signalling request indicates the different application's appeal. For example, Attach request with Follow-on indicator may mean a MTC device wants to initiate data transfer immediately, which is more important than the one without Follow-on indicator. If undistinguished signalling rejection by the network node is executed on the congestion time, any MTC device requests can not survive. In fact the congestion may be also released while keeping some important requests unaffected. + +Two alternatives to accomplish the solution of rejecting connection requests based on signalling types can be considered. + +- 1) The network node count numbers of different kinds of signalling requests around the congestion time. The O&M periodic counting data created in the nearest time to the congestion occurrence can be used. The network nodes reject one or more signalling requests with the largest amount and extend the scope of rejection until the congestion disappears. + +**Editor's note: It is out of the specification scope how to get the O&M statistic data for the signalling requests.** + +- 2) The operator or MTC users provide the configuration for the priority of different kinds of signalling requests. The network nodes reject one or more signalling requests with the lowest importance firstly and extend the scope of rejection until the congestion disappears. + +The both alternatives could be used together for congestion control. How many kinds of signalling requests shall be selected once time to the rejection list can be decided by the operator's configuration. + +The mechanism of back-off time to the MTC Device as described in the clause 6.22 is also applicable for this solution. This solution could be used together with other basic solutions for congestion control, e.g. solution .6.22 Rejecting connection request per APN or MTC group. + +### 6.32.3 Impacts on existing nodes or functionality + +Additional impacts on CN nodes (SGSN, GGSN, MME, S-GW, P-GW) + +- Rejecting a connection request with a particular type +- Counting numbers of different kinds of signalling requests in the statistics period nearest to the time of congestion occurrence. + +### 6.32.4 Evaluation + +Benefits + +On the congestion time part kinds of signalling request can still be handled normally. + +Drawbacks + +Rejecting part kinds of signalling request at the beginning and extending the signalling scope of rejection gradually may not resolve the congestion in a short time. + +## 6.33 Solution – UE behaviour changes + +### 6.33.1 Problem Solved / Gains Provided + +5.14 "Key Issue – Potential overload issues caused by Roaming MTC devices". + +### 6.33.2 General + +The scenarios outlined in clause 5.14 highlight some areas where the UE internal behaviour would benefit from small but important changes: + +- the ability to remotely configure a device as, a "low value M2M" device. Typically this could be done via OMA DM. +- modification (increase) of the minimum value of the timer for the background PLMN search, e.g. to greater than one hour, for a "low value M2M" device. This UE internal value would over-rule any smaller value contained on the (U)SIM. + +It is FFS whether this modification applies to just the background search for a more preferred VPLMN, or, to the background search for both VPLMN and HPLMN. + +- for ALL M2M devices, modification of the behaviour following receipt of 'fatal' MM/GMM/EMM cause values such as "IMSI unknown in HLR", "illegal ME" and "persistent" cause values such as "PLMN not allowed". These cause values could be wrongly sent "in panic" by an overloaded (V)PLMN, or, in a denial of service attack by a (mobile) false base station. Following receipt of these cause values, a site visit to all M2M devices is untenable, however, so is immediate re-accessing by the device. Some new middle ground is needed (e.g. retry at a randomly selected time between 24 and 48 hours later). + +It is FFS whether the behaviour following receipt of "PLMN not allowed" needs modification or not. + +- For a "low value M2M" device, always use IMSI when Attaching to a new network, or, performing an RA update into a different PLMN that is not an ePLMN. This decreases UE-network signalling in a potentially heavily loaded network. + +It is FFS whether this solution is applicable to EUTRAN. + +- In the CS domain, at power on in a new location area, perform a location update with LU type=Attach rather than "normal". + +- f) Modification of "low value M2M" device behaviour following repeatedly unsuccessful MM/GMM/EMM procedures so that the device does NOT move to competing network(s) and inflict them with similar levels of signalling (over)load. + +### 6.33.3 Impacts on existing nodes or functionality + +The above features are internal to the M2M device (and/or application on the M2M device). + +### 6.33.4 Evaluation + +These features seem useful to be developed in more detail (e.g. by CT 1) and specified as part of 3GPP release 10. + +## 6.34 Solution – M2M device indication to network + +### 6.34.1 Problem Solved / Gains Provided + +5.14 "Key Issue – Potential overload issues caused by Roaming MTC devices". + +### 6.34.2 General + +By providing the network with indications that the UE is a "low priority" M2M device, the network is able to more easily protect itself against overload, and/or to detect that an increase in load is being caused by M2M devices. + +Clause 5.14 highlighted the utility of M2M device indicators in the following signalling: + +- a) in the GSM Channel Request message, and UTRAN and E-UTRAN RRC Connection Establishment messages; +- b) in the IDNNS signalling at Attach and RA update from a non-equivalent PLMN; + +NOTE: From the stage 2 design point of view, there is no harm in always sending this M2M indicator in the IDNNS. It is left to stage 3 to decide whether to do this simplification. + +- c) in the NAS signalling to the MME/SGSN/MSC. + +### 6.34.3 Impacts on existing nodes or functionality + +For the Channel Request message (and its equivalents), the RAN will probably need to broadcast its support/non-support for the new code points. + +For b, c the signalling should be able to be added in a backwards compatible manner. + +### 6.34.4 Evaluation + +These indicators appear useful to specify in 3GPP Release 10. + +## 6.35 Solution - Overload control within an MTC access grant time interval + +### 6.35.1 Problems solved / Gains provided + +See Clause 5.9 "Key Issue –Time Controlled" and Clause 5.12 "Key Issue – Signalling Congestion Control". + +### 6.35.2 General + +The network may suffer from a dramatic increase in its load at the beginning of the MTC access grant time interval due to the simultaneous signalling actions (e.g., simultaneous attachment operations) of many MTC devices. The main idea of the solution presented here is to let SGSN/MME restrict the number of its attached MTC devices in such a manner that the total number of attached UEs (including both MTC and non-MTC devices) is always under, or, at most, fluctuates slightly around, a pre-defined upper bound during the MTC access grant time interval. + +Developed to restrict MTC device accesses only, this solution recommends that each MTC device carry an MTC indication with which the network can distinguish MTC devices from normal human-to-human (H2H) devices. Also, + +we suggest that the MTC devices remain detached if they are not expected to have any mobile terminated communications. + +To implement this method, the network operator needs to set an upper bound of the number of attached UEs. This upper bound is supposed to be the maximum number of attached UEs while keeping the network in a normal working condition. It can be determined according to the network equipment capability and the operating experience. + +As the load increases or decreases, the allowed number of UE sessions may have to be adjusted, as a number that is too high will ensure congestion, while a number that is too low will ensure underutilization. + +A series of discrete time points (e.g., with a spacing of 1 second) are selected within the MTC access grant time interval as the time instants at which the MTC devices are allowed to request attachment. At other times, the network shall reject the MTC attachment requests and tell each of those MTC devices to resend the request at an aforementioned time point. + +At each of the time points described above, the SGSN/MME checks the number of attached non-MTC UEs, the margin between this number and the aforementioned upper bound is regarded as the maximum number of MTC devices allowed to attach at this moment. If the number of currently attached MTC devices is less than that maximum number, the SGSN/MME accepts the attach requests from MTC devices until the number of attached MTC devices reaches the maximum number, otherwise the attach requests are rejected. While rejecting an attach request, the SGSN/MME selects a subsequent MTC attachment time point and tells the MTC device to resend the attach request at that specific time point. + +The algorithm is first-come-first-serve. Any device that requests access after the maximum number have been allowed access, will be given a deferral. It is therefore anticipated that devices will attempt to access the network as soon as possible (at the beginning of the Grant Time Interval). Further, it is possible that devices may get deferrals repeatedly, and there is no bound to the number of deferrals that may occur. + +The SGSN/MME must select a subsequent MTC attach time such that the MTC Device can complete its minimum Access Duration. + +After completing the communication tasks in the MTC access grant time interval, the MTC devices shall get detached (either by themselves or by the network) from the SGSN/MME so that other MTC devices can have chances to successfully attach to the network. + +**Editor's note:** It is FFS how surcharging instead of detaching can be supported by this solution. + +### 6.35.3 Impacts on existing nodes or functionality + +Impacts on the SGSN/MME: + +- With the MTC indication carried by each MTC device, the SGSN/MME needs to be able to distinguish MTC devices from normal H2H devices. +- The SGSN/MME needs to store the discrete time points at which the MTC devices are allowed to request attachment, and reject MTC attach requests except at those time points. While rejecting an attach request, the SGSN/MME needs to select a subsequent MTC attachment time point and inform the MTC device. +- The SGSN/MME needs to count the numbers of both MTC and non-MTC devices separately. At the time points when MTC devices are allowed to request attachment, the SGSN/MME needs to calculate the maximum number of MTC devices allowed to attach at this moment, and decide how many more MTC attach requests it can accept. +- The SGSN/MME must take into account the Grant Time Interval, Forbidden Time Interval and Access Duration policy that applies to the subscription corresponding to the MTC Device when it calculates the deferred access time point. The MTC Device must be able to fulfil its Access Duration within a Grant Time Interval. + +Impacts on the MTC device: + +- Each MTC device needs to carry an MTC indication. +- MTC devices need to remain detached if they are not expected to have any mobile terminated communications. +- When its attach request is rejected, the MTC device needs to resend the request at the time point provided by the SGSN/MME in the rejection message. + +- After completing the communication tasks, the MTC device needs to get detached (either by themselves or by the network) from the SGSN/MME. + +## 6.35.4 Evaluation + +# 6.36 Solution - Time controlled feature via Operator and MTC User Business Agreements + +## 6.36.1 Problem Solved / Gains Provided + +See clause 5.9 "Key Issue – Time Controlled". + +## 6.36.2 General + +The outline of the solution is as follows: + +- The operator informs the MTC user about preferred time-window for MTC devices to communicate with the network. This is performed as part of business agreement between the operator and the MTC User. +- The MTC device informs the MTC Server about its current location and PLMN via application layer. + +NOTE: Finer granularity than PLMN may be needed if the time-window is based on geographical location within the PLMN, e.g. for a PLMN covering a large geographical area + +- The MTC user via the MTC Server informs the MTC device about the appropriate time window to communicate with the network via application layer. +- The charging for MTC communication may be set such that the communication has higher charges if these occur outside of the preferred time-window. +- The Operator keeps track, via regular OAM, about the time when the communication with MTC device occurs. The operator provides this information, e.g. as part of bill, to the MTC User. The MTC user takes appropriate action if certain MTC devices are communicating outside of the desired time-window. The operator may also take appropriate action, based on analyzing the call-records, e.g. cancel MTC devices subscription. +- Based on traffic pattern, the operator may modify the preferred time-window for MTC device communication and provide this information to the MTC User. The MTC user updates the new time-window of communication to MTC device via application layer. + +## 6.36.3 Impacts on existing nodes or functionality + +None + +## 6.36.4 Evaluation + +The over-the-top solution exists independent to 3GPP standardization. + +This solution cannot enforce time control policy as defined by TS 22.368 [2], clause 7.2.2. It would be possible to configure a surcharging policy using PCC. + +Dynamic local criteria, e.g. current load on network beyond perhaps 'time zone information', especially from the VPLMN, cannot be taken into account by in a real-time manner, as it is based upon subscription and roaming agreements. + +This solution is based on application control. If the same MTC Device uses more than one application, all applications will need to be controlled in a coordinated manner. + +## 6.37 Solution - Simple Subscription Control + +### 6.37.1 Problem Solved / Gains Provided + +This solution answers the requirements of 5.7 "Key Issue - MTC Subscriptions." + +### 6.37.2 General + +#### Solution 1) "Do Nothing" + +It is possible that there will be no MTC Features in release 10. If this is the case, it would suffice that the lack of any MTC subscription elements indicates that no MTC Features are subscribed. + +#### Solution 2) "Simple Solution" + +The MTC Subscription identifies subscribed MTC Features (as an IE or as IEs) in the HSS. + +It is assumed for this release of this specification that all subscribed MTC Features may be considered by the network to be 'essential' and mandatory. If an MTC Device or visited network does not support one or more subscribed MTC Features, the MME/SGSN may inform the MTC Device and the MTC Device detaches. + +To determine whether a subscribed MTC Feature is activated: + +- The Network may determine if a given MTC Device supports a given MTC Feature through implementation dependent evaluation of the IMEI. For example, the operator may maintain a database of MTC Devices types based upon the IMEI. +- Further, it may be assumed that a subscribed MTC Feature is supported by the MTC Device. If this is not the case, the MTC Device will fail to operate +- If either the network or the MTC Device (e.g. based on IMEI or due to missing but expected parameters during the attach request) does not support a subscribed MTC Feature, the MME/SGSN may reject the MTC Device when it attempts to attach. The MME/SGSN includes information regarding the unsupported MTC Feature in the rejection cause. + +An indication of capabilities from the MTC Device is unnecessary to define in a general way. For each MTC Feature, such interaction between the MTC Device and the network may be defined (as has been done for other features, e.g. SR VCC capability, etc.). + +If the MME/SGSN is pre-Rel-10 and accepts the MTC devices without any notification about the MTC features, and the device expects such an indication for the feature, the MTC device performs detach procedure. + +### 6.37.3 Impacts on existing nodes or functionality + +#### Solution 1) + +None + +#### Solution 2) + +The HSS must support an IE (or IEs) representing MTC Features included in the MTC subscription. + +The MME/SGSN determine whether an MTC Device supports the subscribed set of MTC Features on the basis of the IMEI the device capabilities (e.g. by means of a database) or by checking whether expected IEs are present. + +The MME/SGSN knows (due to local policy) whether a given MTC Feature is supported by the network. + +The MME/SGSN may reject MTC Devices attempting to attach using a new rejection code. + +### 6.37.4 Evaluation + +Solution 1 is preferable if no MTC Feature is standardized in release 10. This solution has no impact on the standard and will not complicate future MTC Feature control mechanisms. + +Solution 2 is preferable if MTC Features are standardized in release 10. A simple approach is taken in which the minimum semantics are assumed in order to support the architecture requirements expressed by the Key Issue. + +## 6.38 Solution – Device identifier used over MTCS<sub>P</sub> + +### 6.38.1 Problems solved / Gains provided + +See + +clause 5.8 "Key Issue –MTC Device Trigger", + +clause 5.13 "Key Issue - MTC Identifiers", + +clause 5.10 "Key Issue - MTC Monitoring", + +clause 5.11 "Key Issue - Decoupling MTC Server from 3GPP Architecture". + +### 6.38.2 General + +![Figure 6.38.2-1: 3GPP Architecture for Machine-Type Communication. The diagram shows an MTC Device connected to a central oval labeled '3GPP bearer services / SMS / IMS' via the MTCu interface. The oval is connected to an 'MTC Server' via three interfaces: MTCsms, MTCsp, and MTCi. The 'MTC Server' is connected to an 'MTC User' via an API interface.](b4e9fc9d087037ebe92a54050272e7d6_img.jpg) + +``` + +graph LR + MTC_Device[MTC Device] -- MTCu --> 3GPP_Bearer[3GPP bearer services / SMS / IMS] + 3GPP_Bearer -- MTCsms --> MTC_Server[MTC Server] + 3GPP_Bearer -- MTCsp --> MTC_Server + 3GPP_Bearer -- MTCi --> MTC_Server + MTC_Server -- API --> MTC_User[MTC User] + +``` + +Figure 6.38.2-1: 3GPP Architecture for Machine-Type Communication. The diagram shows an MTC Device connected to a central oval labeled '3GPP bearer services / SMS / IMS' via the MTCu interface. The oval is connected to an 'MTC Server' via three interfaces: MTCsms, MTCsp, and MTCi. The 'MTC Server' is connected to an 'MTC User' via an API interface. + +**Figure 6.38.2-1: 3GPP Architecture for Machine-Type Communication** + +The reference points are listed as below: + +- MTCu:** It provides MTC Devices access to 3GPP network for the transport of user plane and control plane traffic. MTCu interface could be based on Uu, Um, Ww and LTE-Uu interface. +- MTCi:** It is the reference point that MTC Server uses to connect the 3GPP network and thus communicates with MTC Device via 3GPP bearer services/IMS. MTCi could be based on Gi, Sgi, and Wi interface. +- MTCsp:** It is the reference point the MTC Server uses for signalling with the 3GPP network. +- MTCsms:** It is the reference point MTC Server uses to connect the 3GPP network and thus communicates with MTC Device via 3GPP SMS. + +**Editor's note:** It is ffs if MTCsms exists as a separate reference point or whether MTCsp is used for 3GPP SMS as well. + +In the general case the MTC Server is located outside the operator domain. In the special case when the MTC Server is located in the operator domain, the MTC<sub>sp</sub> and the MTC<sub>i</sub> becomes internal in the operator network. In a deployment there may simultaneously be MTC Server located inside the operator domain and MTC Servers located outside the operator domain. There might be one or several functional entities in the mobile operator network that terminate the MTC<sub>sp</sub> reference point. In the text below these entities(s) are simply referred to as "Service Centre configured for MTC". The MTC Server and the MTC User may either be separate entities or co-located. + +Guiding requirements for a device identifier to be used instead of MSISDN at signalling between the MTC Server and the mobile operator network are: + +- The identifier must be globally unique since some MTC service providers operate worldwide. +- The allocation of the new identifier should be efficient. +- The identifier shall also be usable towards other access networks such as 3GPP2, etc. +- The new identifier shall support certain functions in the operator domain: + - Enable routing of signalling, that is, discovering which MTC Server or service provider the MTC device belongs to and its signalling shall be routed to + +- Enable charging and billing. One device (and the charging data produced from its activities) shall easily be traced back to the service provider it belongs to. Optionally also which user at the service provider it belongs to. +- Selective congestion control or enabling/disabling e.g. per MTC User and per Service Provider. +- Migration aspects when changing from MSISDN to the new identifier should be considered. +- Other. + +The details for a device identifier used in MTCSP protocols should be specified in stage 3 (already established protocols such as HTTP RESTful may be candidates for a MTCSP protocol). However in the SA2 requirements of a device identifier, there may also be requirements such as what information it contains (see example below). + +In this example below the "Service Provider ID" is a domain name that belongs to the MTC service provider. The "topdomain" would ensure that the "Service Provider ID" becomes internationally unique. The "topdomain" would be a FQDN in itself such as ".com", ".se", ".co.uk", ".operator.com", etc. The "User ID" should identify a subscriber within the service provider domain, for example an enterprise or even a person using MTC services. There would be a unique "Device ID" part for each MTC device a user has (at least unique within the user domain). The "Device ID" may for example be a serial number of the hardware running the "application part" of the MTC device (i.e. not the IMEI) or any other number used by the MTC user to distinguish the MTC device. All these different parts together constitute the full device identifier, as used over a MTCSP interface. In the remainder of this document, the term "International Service provider Subscription Identifier" (abbreviated to ISSI) is used for a device identifier used over the MTCSP interface and meeting the requirements listed above. + +**Editor's note:** The name for the device identifier "International Service provider Subscription Identifier" (ISSI) is tentative and may change. + +- | | | +|-------------------------------|---------------------------------------------------| +| a) <b>FQDN:</b> | deviceid.userid.serviceproviderid.topdomain. | +| b) <b>Dedicated 3GPP URN:</b> | urn:issi:deviceid.userid.serviceproviderid.topdom | + +**Figure 6.38.2-2: Examples of different URI style formats of a device identifier (ISSI)** + +An advantage with an URI style format of a device identifier is that this can be considered mainstream internet technology and that the administration and allocation of the different identifier parts, e.g. the Service Provider ID part, does already exist as part of the normal domain name administration. A slight disadvantage could be that if the different identifiers parts are domain names, such as the "serviceproviderid.topdomain", care needs to be taken so that clashes with other usages of the same domain name is avoided. + +Another advantage of a URI style format for the device identifier is that it allows much more flexibility in the subdivision of the addressing space than an identifier based on a number. However, this advantage would disappear if a constraint to only use URI derived from numbers (such as sip+33612345678@domain.topdomain) would be introduced. + +Alternative a) above using a FQDN for identifying a device should work but there is an implicit assumption of the content/structure of the domain name that needs to be specified. + +Alternative b) using a Uniform Resource Name (URN) is probably more correct way to use a URI when the intention is to specify an identity. By using a new specific Namespace ID in the URN such as "ISSI" in the example, the syntactic interpretation of the Namespace Specific String would be defined. There may be other already registered Namespace ID's that can be used more or less according to 3GPP requirements. + +Alternative c) using a SIP URI is also a possibility. The syntax associated with SIP URI's should be possible to use for what 3GPP requires of a device identifier, but when following it strictly the SIP protocol is also expected for a SIP URI which may not be the case for the MTCSP interface. + +**NOTE:** Depending on what type of URI is selected as device identifier, there might be assumptions on what protocol is used over the MTCsp. + +### 6.38.3 Impacts on existing nodes or functionality + +Impact on GPRS/EPS architecture: + +- A new termination point for the MTCSP reference point in the operator network. + +Impacts on the HSS/HLR: + +- Storage of a new parameter (ISSI) in the subscription information. Making ISSI searchable to be able to find a specific subscriber profile based on an ISSI. +- A new or modified existing protocol is specified for the reference point between the HSS/HLR and a Service Centre configured for MTC. **It is FFS** how the Service Centre configured for MTC can find the HLR/HSS when there are multiple HLR/HSS. + +**Editor's note:** The place where to store the ISSI is still subject for discussion. Hence the HSS/HLR impacts may change. + +### 6.38.4 Evaluation + +## 6.39 Solution - Triggering MTC devices via HSS and NAS signalling + +### 6.39.1 Problem Solved / Gains Provided + +See clause 5.8, "Key Issue – MTC Device Trigger" and clause 5.13 "Key issue - MTC Identifiers". + +### 6.39.2 General + +#### 6.39.2.1 Overview + +A network application server (e.g. Device Management Server) that needs to trigger a connection request from a UE informs the HSS/HLR about this need by providing "UE application trigger request" information defined in clause 6.40.2 + +Each of the UE targeted by the network application server request is then notified about that request via signalling exchange through the serving MME/SGSN, during the next NAS signalling exchange with the UE if there is no on-going signalling connection between the UE and MME/SGSN, or immediately if there is an on-going signalling connection with the UE or if this is an urgent request. + +Upon reception of this "UE application trigger request" information, the UE application is triggered and contacts the network application server. + +#### 6.39.2.2 Detailed solution + +The procedure is illustrated in figure 6.39.2-1 and works as follows: + +![Sequence diagram illustrating the process of triggering MTC devices via HSS and NAS signalling. The diagram shows four main entities: UE, MME/SGSN, HLR/HSS, and Application Server. The process involves five steps: 1. UE application trigger request from Application Server to HLR/HSS; 2. Insert Subscriber Data request from HLR/HSS to MME/SGSN; 3. NAS signaling (RAU Request, RAU Accept, RAU Complete) between MME/SGSN and UE; 4. UE contacts the application; 5. Notify request and Notify answer between MME/SGSN and HLR/HSS. Annotations include 'when there is an MME/SGSN associated to the UE', 'controls & stores the request', 'stores the request', and 'deletes the request'.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME/SGSN + participant HLR/HSS + participant Application Server + + Note right of HLR/HSS: controls & stores the request + Application Server->>HLR/HSS: 1. UE application trigger request + Note right of HLR/HSS: stores the request + HLR/HSS->>MME/SGSN: 2. Insert Subscriber Data request (UE application trigger request) + Note right of MME/SGSN: stores the request + MME/SGSN->>HLR/HSS: Insert Subscriber Data answer + Note left of MME/SGSN: when there is an MME/SGSN associated to the UE + Note left of MME/SGSN: NAS signaling e.g. periodic RAU + MME/SGSN->>UE: 3. RAU Request + UE-->>MME/SGSN: RAU Accept (UE application trigger request) + MME/SGSN->>UE: RAU Complete + Note left of UE: 4. UE contacts the application + Note right of MME/SGSN: deletes the request + MME/SGSN->>HLR/HSS: 5. Notify request (Ack of UE application trigger request) + HLR/HSS-->>MME/SGSN: Notify answer + Note right of HLR/HSS: deletes the request + +``` + +Sequence diagram illustrating the process of triggering MTC devices via HSS and NAS signalling. The diagram shows four main entities: UE, MME/SGSN, HLR/HSS, and Application Server. The process involves five steps: 1. UE application trigger request from Application Server to HLR/HSS; 2. Insert Subscriber Data request from HLR/HSS to MME/SGSN; 3. NAS signaling (RAU Request, RAU Accept, RAU Complete) between MME/SGSN and UE; 4. UE contacts the application; 5. Notify request and Notify answer between MME/SGSN and HLR/HSS. Annotations include 'when there is an MME/SGSN associated to the UE', 'controls & stores the request', 'stores the request', and 'deletes the request'. + +**Figure 6.39.2-1: Triggering MTC devices via HSS and NAS signalling** + +- 1) Each time a network application server wants to contact a UE, it informs the HSS/HLR about this need by providing "UE application trigger request" information. + +The interface between an external application and the HSS/HLR needs to be secured. Limitation may be enforced to avoid simultaneous storage of too many "UE application trigger request" in the network. + +The HSS/HLR (or a gateway between the application and the network): + +- a) validates the request from the application (e.g. checking the application rights to issue such requests, enforcing application throttling, etc.); + - b) translates the identity of the target UE received from the application into a network identity of the UE (e.g. corresponding to the IMSI of the target UE); + - c) stores this request in its database record associated with the target UE; + - d) determines the MME/SGSN that currently serves the target UE or waits for such a MME/SGSN to be allocated to the UE (i.e. waits for a subsequent Update Location from an MME/SGSN for that user). +- 2) The HSS/HLR notifies/updates the serving MME/SGSN with this "UE application trigger request" information, immediately if the UE is already served by a SGSN/MME, or when the SGSN/MME changes, otherwise when the UE registers to the network. + +The "UE application trigger request" may be sent within the MAP (Gr) or Diameter (S6a/S6d) Insert Subscriber Data operation. The MME/SGSN stores this request in its database record associated with the UE and returns an Insert Subscriber Data answer. + +If more than one serving nodes are registered with the HSS (e.g., both the MME and the SGSN are registered with the HSS), the HSS sends "UE application trigger request" to each registered serving node. + +- 3) The serving MME/SGSN transfers the "UE application trigger request" information to the UE upon the next NAS signalling exchange with the UE: + +- a) RAU / TAU procedure: + - the RAU/TAU Accept message may carry the "UE application trigger request" notification; + - the TAU/RAU Complete message acknowledges the correct UE reception of the "UE application trigger request" notification. The UE has to send a TAU/RAU Complete message as if a new GUTI or a new P-TMSI had been assigned. +- b) Attach procedure: + - the Attach Accept message may carry the "UE application trigger request" notification; + - the Attach Complete message acknowledges the correct UE reception of the "UE application trigger request" notification. The UE has to send an Attach Complete message as if a new GUTI or a new P-TMSI had been assigned. +- c) a dedicated Notification procedure (with a UE acknowledgment) which takes place immediately if there is an on-going signalling connection with the UE when the MME/SGSN receives the request from the HSS/HLR. + +This may be implemented as follows: + +- for LTE access: the Network and UE initiated Generic transport of NAS messages procedures (see TS 24.301 [17] clauses 5.6.4.3 and 5.6.4.2) may be used to carry the "UE application trigger request" notification to the UE and its acknowledgment by the UE. I.e. using the DOWNLINK GENERIC NAS TRANSPORT message and the UPLINK GENERIC NAS TRANSPORT message with a Generic message container type IE set to a specific value for the transfer of "UE application trigger request" and with the Generic message container IE containing the "UE application trigger request" information. + - For 2G/3G access, a similar mechanism may be defined or an existing GMM message may be extended to carry the UE application trigger request, e.g. GMM Information message (see TS 24.008 [16] clause 9.4.19). +- 4) Upon reception of this "UE application trigger request" information, the UE + - a) acknowledges the reception of this information via NAS signalling to the MME/SGSN; + - b) checks that this is not a duplicate request (using the request counter). If this is a duplicate step 4) stops here. Otherwise, the UE application is triggered; + - c) establish the relevant PDN connection / PDP context using the existing EPC/GPRS procedures, if it is not already established; + - d) triggers the UE application which then contacts the network application server in the network. The addressing information to contact the application server in the network may be known in advance on the UE or may have been communicated in the "UE application trigger request" notification. +- 5) Upon receipt of the acknowledgement from the UE: + - a) the MME/SGSN removes the UE application trigger request information from its database record associated with the UE and notifies the HLR/HSS that the UE has received the "UE application trigger request" by sending a Diameter Notification message or a MAP Update GPRS Location message. + - b) When the HSS/HLR receives the acknowledgement from either the MME or the SGSN about a UE, the HSS/HLR removes this request in its database record associated with this UE. + +The HSS/HLR does not need to wait for the acknowledgement from both MME and SGSN to remove the request. This means that an UE may receive twice (once via MME, once via SGSN) such a notification. If so, the UE can detect a duplicated request via the request counter, discards the repeated request and returns a positive acknowledgement to the sending node. Another alternative would be for the HSS/HLR to remove an obsolete UE application trigger request from a MME/SGSN. + +An application may cancel an UE application trigger request using its application Id and the request counter. + +If an MME/SGSN fails and loses the information about not yet transferred "UE application trigger request" notifications, this is not an issue as the HSS/HLR sends to an MME/SGSN that starts serving an UE all "UE application trigger request" notification information it has in its database record associated with this UE. + +An urgency request parameter may also be associated with the "UE application trigger request" notification. If the request is urgent, the UE is notified as soon as possible i.e. the serving MME/SGSN pages the UE as soon as it receives the "UE application trigger request" information from the HSS/HLR. Otherwise the UE is notified only the next time it exchanges signalling with the MME/SGSN. + +If an "UE application trigger request" indicates an expiration time and the timer is about to expire, and there is no ongoing NAS signalling exchange with the UE, the SGSN/MME pages the UE to deliver the "UE application trigger request" a configurable times before the expiry of the expiration time. + +### 6.39.3 Impacts on existing nodes or functionality + +HLR/HSS provides interface to application server for receiving trigger requests and to report trigger results. HLR/HSS stores UE application trigger requests, transfers them to the each serving MME/SGSN and erase them upon getting the acknowledgement from either of the serving MME or SGSN entities that they have been successfully delivered to the UEs. The signaling cost of this procedure on HSS/HLR should be equivalent to the cost of a triggering based on terminating SMS. + +MME/S4-SGSN stores UE application trigger requests, transfers them via NAS signalling to the UE and erase them upon getting the acknowledgement that they have been successfully delivered to the UEs. + +UEs receive and acknowledge UE application trigger requests via NAS signalling and trigger the corresponding application. + +### 6.39.4 Evaluation + +## 6.40 Solution - Information sent to trigger a UE used for MTC + +### 6.40.1 Problem solved + +This solution describes the information to be provided by a network application server (e.g. Device Management Server) that needs to trigger a connection request from a UE. See clause 5.8, "Key Issue - MTC Device Trigger". + +### 6.40.2 Required Functionality + +A network application server (e.g. Device Management Server) that needs to trigger a connection request from a UE provides "UE application trigger request" information containing e.g.: + +- the identity of the target UE; +- the identity of the application; +- a request counter associated to this request allowing to detect duplicated requests, to correlate requests with their acknowledgement and to allow the application to cancel a request; +- optionally the IP@ (or FQDN) and/or TCP (or UDP) port of the server/application that the UE has to contact; +- optionally an urgency request indication; +- optionally a validity timer (allowing to remove storage of the UE application is triggered when it is no more needed); +- optionally application specific information (of limited size). + +**Editor's note:** It is FFS whether other parameters such as provided within a SMS based trigger are needed. + +## 6.41 Solution - Triggering of attached MTC Devices by reusing Network Requested PDP Context Activation procedure + +### 6.41.1 Problem Solved / Gains Provided + +See clause 5.8 "Key Issue - MTC Device Trigger". + +### 6.41.2 General + +This solution proposes to trigger the attached MTC Devices by reusing Network-Requested PDP Context Activation procedures. This solution supports the scenario where an MTC Device has a subscribed static IP address and the scenario where only dynamic IP address assignment for MTC Devices is supported. The MTC Device can obtain IP address dynamically during the subsequent PDP context activation procedure in case there is no subscribed static IP address. + +The MTC Server initiates DNS query to retrieve the IP address for the MTC Device if it is not available in the MTC Server. The DNS Server can be standalone or the front-end of the AAA Server. The DNS Server lookup the entry based on the query input (i.e. a FQDN, which includes the device identifier) provided by the MTC Server. If there is a valid record in the DNS Server, the DNS Server returns IP address to the MTC Server (e.g. a PDP context or PDN connection has been established) directly, otherwise, it requires the AAA Server to trigger the MTC Device to establish PDP context or PDN connection firstly. + +**Editor's note:** The device identifier format, e.g. FQDN is FFS. + +NOTE 1: For E-UTRAN access, a default PDN connection is established during Attach procedure, so the DNS Server can return the IP address directly. + +NOTE 2: The AAA Server and DNS Server can be deployed as standalone physical entities or as functional entities collocated in a Device Trigger Gateway (DT-GW; refer to Figure 6.45.2-1). + +There are two alternatives for the AAA Server to trigger the MTC Device. + +#### Alternative 1: + +![Figure 6.41.2-1: Illustration of alternative 1. This sequence diagram shows the interaction between an MTC Device, SGSN, GGSN, AAA Server, HSS, and MTC Server. The process starts with the MTC Server sending a 'Request Device's IP' (1) to the AAA Server. The AAA Server sends a 'Request Device's info' (2) to the HSS. The AAA Server sends a 'Connectivity Request' (3) to the GGSN. The GGSN sends a 'Registration' (7) to the AAA Server. The AAA Server sends a 'Network initiates PDP activation' (4) to the SGSN. The SGSN sends a 'Device initiates PDP activation' (5) to the MTC Device. The MTC Device sends a response (6) to the SGSN. The AAA Server also sends a 'Request Device's IP' (8) to the MTC Server.](2bea721b89ee5816651ed9cdc328bc9f_img.jpg) + +``` + +sequenceDiagram + participant MTC Device + participant SGSN + participant GGSN + participant AAA Server + participant HSS + participant MTC Server + + Note right of MTC Server: Network initiates PDP activation + Note left of GGSN: Device initiates PDP activation + + MTC Server->>AAA Server: 1 Request Device's IP + AAA Server->>HSS: 2 Request Device's info + AAA Server->>GGSN: 3 Connectivity Request + GGSN->>AAA Server: 7 Registration + AAA Server->>SGSN: 4 + SGSN->>MTC Device: 5 Device initiates PDP activation + MTC Device->>SGSN: 6 + AAA Server->>MTC Server: 8 + +``` + +Figure 6.41.2-1: Illustration of alternative 1. This sequence diagram shows the interaction between an MTC Device, SGSN, GGSN, AAA Server, HSS, and MTC Server. The process starts with the MTC Server sending a 'Request Device's IP' (1) to the AAA Server. The AAA Server sends a 'Request Device's info' (2) to the HSS. The AAA Server sends a 'Connectivity Request' (3) to the GGSN. The GGSN sends a 'Registration' (7) to the AAA Server. The AAA Server sends a 'Network initiates PDP activation' (4) to the SGSN. The SGSN sends a 'Device initiates PDP activation' (5) to the MTC Device. The MTC Device sends a response (6) to the SGSN. The AAA Server also sends a 'Request Device's IP' (8) to the MTC Server. + +**Figure 6.41.2-1: Illustration of alternative 1** + +The AAA Server selects the HLR/HSS based on the IMSI, which is derived from the device identifier (i.e. the IMSI is included in the device identifier) or mapped from the device identifier based on local configuration, and sends an information request (IMSI) message to the HLR/HSS. The HLR/HSS returns the serving SGSN address for the MTC Device. + +The APN can be provided by the MTC Server (e.g. included in the FQDN for DNS query), or derived from, e.g. the FQDN according to local configuration. + +The AAA Server selects a GGSN based on e.g. APN, and initiates Network-Requested PDP Context Activation procedure as specified in TS 23.060 [21], with the exception as follows: + +- 1) In step 3 of above figure, the AAA Server sends a Connectivity Request message (IMSI, APN, SGSN address) to the selected GGSN. + +- 2) In step 4 of above figure, the GGSN sends PDU Notification Request (IMSI, APN, PDP address) message to the SGSN. The PDP address is set to zero or the static IP address configured in the GGSN. +- 3) In step 7 of above figure, the GGSN registers the MTC Device to the DNS Server via AAA Server as specified in TS 29.061 [4], with providing the device identifier, APN and the IP address (i.e. the subscribed static IP address or the dynamically allocated IP address during the PDP context activation procedure in step 6), which are provided by the MTC Device in PCO IE. + +NOTE 3: For IPv6 it is assumed that the MTC Device relies on DHCPv6 for stateful address allocation, or uses the solution described in clause 6.49. + +NOTE 4: Alternative 1 can be combined with the solution described in 6.50 to avoid the use of stateful address allocation. + +#### Alternative 2: + +![Diagram illustrating Alternative 2 for PDP activation. The diagram shows the interaction between an MTC Device, SGSN, GGSN, HSS, AAA Server, and MTC Server. The process starts with the MTC Server sending a 'Request Device's IP' (1) to the AAA Server. The AAA Server sends a 'Connectivity Request' (2) to the GGSN. The GGSN sends a 'Request Device's info' (3) to the HSS. The HSS returns the serving SGSN address. The GGSN sends a 'PDU Notification Request' (4) to the SGSN. The SGSN sends a 'Request PDP Context Activation' (5) to the MTC Device. The MTC Device responds with 'Device initiates PDP activation' (6). The GGSN sends a 'Registration' (7) to the AAA Server. Finally, the AAA Server sends a response (8) to the MTC Server. The diagram also shows 'Network initiates PDP activation' and 'Device initiates PDP activation' labels.](34cbe6293693bd7fa95f2755c16b66bd_img.jpg) + +Diagram illustrating Alternative 2 for PDP activation. The diagram shows the interaction between an MTC Device, SGSN, GGSN, HSS, AAA Server, and MTC Server. The process starts with the MTC Server sending a 'Request Device's IP' (1) to the AAA Server. The AAA Server sends a 'Connectivity Request' (2) to the GGSN. The GGSN sends a 'Request Device's info' (3) to the HSS. The HSS returns the serving SGSN address. The GGSN sends a 'PDU Notification Request' (4) to the SGSN. The SGSN sends a 'Request PDP Context Activation' (5) to the MTC Device. The MTC Device responds with 'Device initiates PDP activation' (6). The GGSN sends a 'Registration' (7) to the AAA Server. Finally, the AAA Server sends a response (8) to the MTC Server. The diagram also shows 'Network initiates PDP activation' and 'Device initiates PDP activation' labels. + +Figure 6.41.2-2: Illustration of alternative 2 + +The AAA Server selects a GGSN based on e.g. APN which is provided by the MTC Server (e.g. included in the FQDN for DNS query), or derived from, e.g. the FQDN according to local configuration, and then initiates Network-Requested PDP Context Activation procedure as specified in TS 23.060 [21], with the exception as follows: + +- 1) In step 2 of above figure, the AAA Server sends a Connectivity Request message (IMSI, APN) to the selected GGSN. The IMSI is derived from the device identifier (i.e. the IMSI is included in the device identifier) or mapped from the device identifier based on local configuration. +- 2) In step 3 of above figure, the GGSN sends MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS Service (IMSI) message to the HLR/HSS. The HLR/HSS address is derived from the IMSI. The HLR/HSS returns the serving SGSN address. +- 3) In step 4 of above figure, the GGSN sends PDU Notification Request (IMSI, APN, PDP address) message to the SGSN. The PDP address is set to zero or the static IP address configured in the GGSN. +- 4) In step 5 of above figure, the SGSN sends a Request PDP Context Activation (APN, PDP address) message to the MTC Device. +- 5) In step 7 of above figure, the GGSN registers the MTC Device to the DNS Server via AAA Server as specified in TS 29.061 [4], with providing the device identifier, APN and the IP address (i.e. the subscribed static IP address or the dynamically allocated IP address during the PDP context activation procedure in step 6), which are provided by the MTC Device in PCO IE. + +NOTE 5: For IPv6 it is assumed that the MTC Device relies on DHCPv6 for stateful address allocation, or uses the solution described in clause 6.49. + +NOTE 6: Alternative 2 can be combined with the solution described in 6.50 to avoid the use of stateful address allocation. + +Afterwards, the DNS Server returns the IP address of the MTC Device to the MTC Server, so that the MTC Server can transmit packet data to the MTC Device. + +**Editor's note:** The alternative with using dynamic address allocation needs to solve issues addressed in TR 23.976. The solution with using static IP address allocation needs to detail how static address allocation is performed as it has been removed from TS 23.060 [21] and TS 23.401 [5]. + +### 6.41.3 Impacts on existing nodes or functionality + +Impacts on the Network-Requested PDP Context Activation procedure: + +- It is triggered by a signalling over Gi interface instead of a PDU; +- It needs to support dynamical IP address allocation; +- In alternative 1, the GGSN does not communicate with HLR/HSS via Gc interface. + +### 6.41.4 Evaluation + +## 6.42 Solution - Triggering of attached MTC Device via Pre rel-11 SMS + +### 6.42.1 Problem Solved / Gains Provided + +See clause 5.8 "Key Issue - MTC Device Trigger". The solution focuses on the scenario that MTC devices receive trigger indication in attached state w/o PDP/PDN connection. + +### 6.42.2 General + +The MTC server sends indication to MTC Devices via SMS and make MTC Devices initially establish data communication with the MTC server. The short message should contain MTC Server address and required triggering information. + +### 6.42.3 Impacts on existing nodes or functionality + +None. + +### 6.42.4 Evaluation + +#### Benefits: + +- No impact for existing network. + +#### Drawbacks: + +- The subscription of MTC Device must associate with a MSISDN. +- CS network is involved in case the short message is only supported by the CS domain and/or LTE access is deployed. + +## 6.43 Solution - Triggering of attached MTC Device via intermediate node + +### 6.43.1 Problem Solved / Gains Provided + +See clause 5.8 "Key Issue - MTC Device Trigger". The solution focuses on the scenario that MTC devices receive trigger indication in attached state. + +### 6.43.2 General + +This solution re-uses the intermediate node introduced by MTC Monitoring solution specified in clause 6.25. MTC Server may first register its desired events with IMSI or device ID. Towards the triggering purpose, the monitoring event should include CN node-level location change (e.g. SGSN/MME change) of the MTC device and it might be configured in SGSN/MME by operators or inserted into SGSN/MME along with the subscription. SGSN/MME shall + +report location changes to the intermediate node once the new MTC device enters into or the already camping MTC device changes location. Upon the location report, the intermediate node shall store the SGSN/MME address associated with the IMSI or device ID and then push registered location information to the related MTC server. Above procedures shall follow monitoring mechanism covered in clause 6.25. + +When the MTC user wants to trigger an attached MTC Device which can be located, the MTC Server sends notification message with the IMSI or device ID and the MTC Server address to the intermediate node, which thus forwards the message to the SGSN/MME that sends location update message last time. SGSN/MME might use the existing or new NAS message to initiate data communication between the MTC device and MTC server. + +In case of no PDP context, the MTC device activates a PDP context after receiving trigger indication. Or SGSN may initiate PDP context activation directly. + +**Editor's note:** How SGSN initiates a PDP based on the notification from the intermediate node is FFS. The MTC server can also trigger the MTC device without register location monitoring service if all related MTC device are monitored with location by default. Since the MTC Server does not know whether the MTC device is attached before triggering, the triggering might not success. + +The intermediate node shall keep the SGSN/MME address per IMSI or device ID in this solution. + +**Editor's note:** Whether there are changes to the roaming architecture and message flow are FFS. + +### 6.43.3 Impacts on existing nodes or functionality + +#### CN nodes: + +- Event reporting function through the intermediate node specified in clause 6.25 shall be supported by SGSN/MME, HLR/HSS. +- A new network entity may be introduced and new interfaces are introduced. + +**Editor's note:** Whether there are additional impacts in roaming scenario is FFS. + +### 6.43.4 Evaluation + +#### Benefits: + +- MSISDN is not mandatory for this solution. +- It is applicable for PS only network. + +#### Drawbacks: + +- The new network entity and new interfaces add complexity of the system. +- SGSN/MME need report location changes to the intermediate node. + +## 6.44 Solution – Device Triggering reuse of MT SMS + +### 6.44.1 Problems solved / Gains provided + +See clause 5.7 "Key Issue -MTC Device Trigger". + +### 6.44.2 General + +The solution described and evaluated below addresses the Key issue "MTC Device Triggering" and allows an MTC server to trigger registered devices (i.e. IMSI attached or GPRS attached) without a PDP connection to establish a connection making communication with the MTC server possible. + +The MTC-IWF (e.g. potentially collocated with SMS-SC) would use a standardized protocol over the MTCsp interface point. The Service Centre resides at the edge of the operators' network (see figure 6.44.2-1). The MTC Server could request the Service Centre to deliver a device trigger over the MTCsp. + +The role of the MTC-IWF (clause 6.45 Solution- Device trigger gateway solution) is to hide the details of the triggering mechanism in the operator' domain and provide the MTC Server a generalized interface for it to make a device triggering request. + +The functionality includes: + +- Support for a function for MTC device triggering and acknowledgement over the MTCsp reference point between the MTC server and the MTC-IWF. +- May be collocated with the SMS-SC +- May operate in PS domain only or it may operate in both PS and CS domain. In the latter case it may do the triggering through the MSC +- Reuse of a existing SMS infrastructure and protocols +- Reuse of existing functionality in the terminal to trigger the application (i.e. no terminal impact). +- Mapping the validity time in MTCsp to the Validity Period for SMS delivery. + +A first solution can allow the MTC Server to request a Device Trigger using the new external identifier (see clause 6.38 Solution - Device identifier used over MTCsp). This new external identifier could be mapped by the MTC-IWF to the MSISDN and allow for delivery of device trigger using the existing MT SMS functionality. This approach allows reuse of the SMS nodes with no system impact. + +A later evolution could be a MSISDN-less mode of operation allowing SMS-GMSC to interrogate the HLR using the new identifier for retrieval of the corresponding IMSI and routing information. In conjunction with updates allowing for a MSISDN-less mode (e.g. SMS interfaces and nodes would be impacted) the MT SMS would be delivered using the IMSI. + +![Figure 6.44.2-1: MTC-IWF at edge of Mobile Operator Domain. This diagram shows the architecture where an MTC Device connects to a 3GPP bearer services / SMS / IMS cloud. Inside this cloud, the MTC-IWF is connected to the SMS-SC / IP-SM-GW. The MTC-IWF connects to the MTC Server via the MTCsp interface. The MTC Server connects to an MTC Application via an API. The SMS-SC / IP-SM-GW connects to the MTC Server via the MTCsms interface. The 3GPP bearer services / SMS / IMS cloud is connected to the MTC Server via the Gi/SGi interface.](1b2ce053624064d94a4143854da46702_img.jpg) + +Figure 6.44.2-1: MTC-IWF at edge of Mobile Operator Domain. This diagram shows the architecture where an MTC Device connects to a 3GPP bearer services / SMS / IMS cloud. Inside this cloud, the MTC-IWF is connected to the SMS-SC / IP-SM-GW. The MTC-IWF connects to the MTC Server via the MTCsp interface. The MTC Server connects to an MTC Application via an API. The SMS-SC / IP-SM-GW connects to the MTC Server via the MTCsms interface. The 3GPP bearer services / SMS / IMS cloud is connected to the MTC Server via the Gi/SGi interface. + +**Figure 6.44.2-1: MTC-IWF at edge of Mobile Operator Domain** + +NOTE: If MTC server uses MTCsms to send an SMS for triggering, then similar principles applies as if MTC-IWF forwards the trigger towards SMS entities. Whether MTCsms is enhanced e.g. to support non-E.164 MSISDNs is out of scope. + +From TS 23.040 [6] clause 4.1 the follow entities are in the provision of SMS. + +![Figure 6.44.2-2: Entities involved in the provision of short message. This diagram shows the flow of SMS entities. On the left, outside the scope of the 3GPP/GSM specification set, are the SME and SMS-SC. On the right, inside the scope, are the SMS-GMSC / SMS-IWMSC *, SMS Router *** (with a note that *** applies if SMS Router is used), MSC/VLR or SGSN ** (with a note that ** applies if SMS is sent over CS), and the MS. A dashed vertical line separates the SME and SMS-SC from the other entities.](aec32fe54f8d88d7a631e4cb8d76e70d_img.jpg) + +Figure 6.44.2-2: Entities involved in the provision of short message. This diagram shows the flow of SMS entities. On the left, outside the scope of the 3GPP/GSM specification set, are the SME and SMS-SC. On the right, inside the scope, are the SMS-GMSC / SMS-IWMSC \*, SMS Router \*\*\* (with a note that \*\*\* applies if SMS Router is used), MSC/VLR or SGSN \*\* (with a note that \*\* applies if SMS is sent over CS), and the MS. A dashed vertical line separates the SME and SMS-SC from the other entities. + +**Figure 6.44.2-2 Entities involved in the provision of short message** + +The MTC-IWF takes the role of the SME (Short Message Entity). The MTC-IWF may be co-located with the SMS-SC. As per TS 23.040 [6] the Service Centre may be integrated with the SMS GMSC/SMS IWMSC. + +Steps for the MTC Server to request a device trigger include: + +- The MTC-IWF would receive the Device Trigger Request over the MTCsp interface point. The Device Trigger request may use the new external identifier as per Solution - Device Identifier used over MTCsp (clause 6.38) or using private numbering plans as detailed below. +- When the MTC-IWF decides to trigger via the SMS SC, the SMS Service Centre receives the device identifier and initiates a message transfer that eventually results in a MT SMS that triggers the MS to establish a PDP connection. +- The SM TP SUBMIT DELIVERY message needs to carry an indication when the MT-SMS carries device triggering information. +- The SM TP User Data may contain further details for the MTC device on what PDP connection to establish if this is not implicit for the MTC application. The format of this information can be application specific. An example would be to use SMS application port addressing with an URL embedded in the payload similar as once defined for WAP Push and nowadays used for MMS triggering). +- Mechanisms similar to Authentication and security headers as for USIM download could be contained in the TP-User\_Data to ensure that an authorized MTC servers has triggered the MTC device. +- The existing flow as per clause 10 of TS 23.040 [6] would be triggered by the Service Centre without impacts (i.e. for the MSISDN case) to the SMS interfaces and involved nodes. The Service Centre sends the short message to the SMS GMSC. The SMS GMSC interrogates the HLR to retrieve routing information necessary to forward the short message, and then sends the message to the relevant MSC or SGSN, transiting other networks if necessary. The MSC or SGSN then sends the short message to the MS. +- The MTC Server receives Device Trigger Report from the Service Centre. + +![Sequence diagram showing a successful short message transfer attempt via the MSC or the SGSN. The diagram involves six lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, and MS. The sequence of messages is: 1a. Message transfer (SC to SMS-GMSC), 2. SendRoutingInfo - ForShortMsg (SMS-GMSC to HLR), 4a. ForwardShortMessage (SMS-GMSC to MSC or SGSN), 5. sendInfoFor- MT-SMS (MSC or SGSN to VLR), 6. Message transfer (MSC or SGSN to MS), 4b. Delivery report (MSC or SGSN to SMS-GMSC), 3. SM-Delivery ReportStatus (SMS-GMSC to HLR), and 1b. Delivery report (SMS-GMSC to SC). A legend indicates that single arrows represent operation invocation or message transfer, and double arrows represent successful operation invocation or message transfer including report.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant MSC or SGSN + participant VLR + participant MS + + Note right of SC: Error: + Note right of HLR: 116 + Note right of VLR: Error: Reference source not + + SC->>SMS-GMSC: 1a. Message transfer + SMS-GMSC->>HLR: 2. SendRoutingInfo - ForShortMsg + SMS-GMSC->>MSC or SGSN: 4a. ForwardShortMessage + MSC or SGSN->>VLR: 5. sendInfoFor- MT-SMS + MSC or SGSN->>MS: 6. Message transfer + MSC or SGSN->>SMS-GMSC: 4b. Delivery report + SMS-GMSC->>HLR: 3. SM-Delivery ReportStatus + SMS-GMSC->>SC: 1b. Delivery report + +``` + +→ Operation invocation or message transfer. + ↔ Successful operation invocation or message transfer including report. + +Sequence diagram showing a successful short message transfer attempt via the MSC or the SGSN. The diagram involves six lifelines: SC, SMS-GMSC, HLR, MSC or SGSN, VLR, and MS. The sequence of messages is: 1a. Message transfer (SC to SMS-GMSC), 2. SendRoutingInfo - ForShortMsg (SMS-GMSC to HLR), 4a. ForwardShortMessage (SMS-GMSC to MSC or SGSN), 5. sendInfoFor- MT-SMS (MSC or SGSN to VLR), 6. Message transfer (MSC or SGSN to MS), 4b. Delivery report (MSC or SGSN to SMS-GMSC), 3. SM-Delivery ReportStatus (SMS-GMSC to HLR), and 1b. Delivery report (SMS-GMSC to SC). A legend indicates that single arrows represent operation invocation or message transfer, and double arrows represent successful operation invocation or message transfer including report. + +NOTE 1: This operation is not used by the SGSN. + +**Figure 6.44.2-3: Successful short message transfer attempt via the MSC or the SGSN** + +A further evolution of the MT SMS device trigger mechanism could be considered for a MSISDN-less mode of operation on the SMS provisioned interfaces. + +The MAP message the SMS-GMSC uses to interrogate the HLR to retrieve routing information necessary to forward the short message currently carries the MSISDN. The HLR uses the MSISDN to retrieve the IMSI as well as other necessary information (e.g. Network Node Number/GPRS Node indicator) to which to forward the short message. + +The MSISDN usage for MT SMS would have to be replaced by a new device identifier. Two possibilities include: + +- The MTC-IWF could maintain a mapping of the Device Identifier to the IMSI by interrogating the HLR. The intent would be to use the IMSI instead of the MSISDN in the MAP message possibly introducing a new IMSI IE. The HLR would subsequently be interrogated by the SMS-GMSC use the received IMSI as the index to retrieve the subscriber record containing the routing information. This approach requires 2 interrogations and is not efficient (unless the MTC-IWF also receives the routing information to be forwarded to the SC and used by the SMS-GMSC). +- Alternately, and more efficiently, the device identifier used on the MTCsp interface could be stored in the subscription information and would be propagated to the SC and used by the SMS-GMSC to interrogate the HLR which would return the IMSI and routing information based on the new device identifier. +- Either option requires introduction of new Device Identifier IE to replace the MSISDN in the existing MAP message (i.e. SendRoutingInfoForShortMsg). + +NOTE 2: Typically the MSISDN (e.g. using MNC, MCC) and/or IMSI number series is used to determine which HLR to interrogate. If a solution is pursued such that the Service Centre does not map the new device identifier to an existing 3GPP Identifier (i.e. MSISDN, IMSI) an alternate means to determine which HLR to interrogate would be required and be FFS. + +MAP services that may be influenced by a new identifier to replace the MSISDN include: MAP-SEND-ROUTING-INFO-FOR-SM , MAP-REPORT-SM-DELIVERY-STATUS , MAP-ALERT-SERVICE-CENTRE and MAP-INFORM-SERVICE-CENTRE. Correspondingly the following nodes that use these services would be influenced: HLR, SMS-GMSC, SMS-IWMSC, SMS-Router and IP-SM-GW. + +Originator and destination address as defined in TS 23.040 [6] are qualified with "Type of number" (TON) and "Numbering plan identification" (NPI). These fields allow to define a private numbering plan other than E.164 MSISDN type number. Such a private numbering plan could be used as External Identifier for identifying UEs used for MTC that have to be reachable only from the operator domain to which they are subscribed. An advantage of such an Operator Specific External Identifier would be that existing SME SMS-SC protocols can be used on the MTCsp interface as established protocols typically expose the TON and NPI fields. + +**Editor's note:** Whether the structure of the private numbering plan and the exact use of TON and NPI has to be specified by 3GPP or whether this is Operator specific is FFS. + +### 6.44.3 Impacts on existing nodes or functionality + +#### 6.44.3.1 Impacts for MT-SMS device trigger - MSISDN based + +In the case of a solution using MT SMS and the existing MSISDN based SMS interfaces it is expected that the entities and interfaces (i.e. interfaces 1 thru 5 of figure ZA below) are not impacted. + +Impact on GPRS/EPS architecture: + +- None, a SMS Service Center receiving triggers for MTC is identical to a SMS-SC as currently defined in the GPRS/EPS architecture. + +Impact on the SMS-SC: + +- May be impacted for solution that co-locates the MTC-IWF with the SMS-SC. + +Introduction of a new protocol over the MTCsp interface point between MTC Server and the MTC-IWF. Depending on the external identifier format selected it will even be possible to use established protocols defined between SME and SMS-SC. + +The Device Trigger Request could contain new device identifier (e.g. URI based or SMS-SC private address scheme) that the Service Centre will map to an existing 3GPP identifier (i.e. MSISDN) thereby eliminating impacts to interfaces 2-5 in figure 6.44.3-1 below. + +#### 6.44.3.2 Impacts for MT-SMS and MSISDN-less based + +Impacts include the above along with SMS entities and related interface to allow MT-SMS based on IMSI + +The main network structure from TS 23.040 [6] illustrated in figure 6.44.3-1 below highlights potential scope of impacts. + +![Figure 6.44.3-1: Main network structure and reference pts. The diagram shows the network architecture for MT-SMS. On the left, the SMS-SC is connected to the SMS-IWMSC and SMS-GMSC via interface 1. The SMS-IWMSC and SMS-GMSC are connected to the HLR via interface 2. The SMS-IWMSC and SMS-GMSC are connected to the SMS Router via interface 3. The SMS Router is connected to the HLR via interface 2 and to the MSC/SGSN via interface 3. The MSC/SGSN is connected to the MS via interface 5 and to the VLR via interface 4. The HLR is connected to the SMS Router via interface 2.](8def7bf8f6f13fd54fb7c2386dc4b635_img.jpg) + +``` + +graph LR + SMS-SC[SMS-SC] -- 1 --> SMS-IWMSC[SMS-IWMSC] + SMS-SC -- 1 --> SMS-GMSC[SMS-GMSC] + SMS-IWMSC -- 2 --> HLR[HLR] + SMS-IWMSC -- 3 --> MSC_SGSN[MSC/SGSN] + SMS-GMSC -- 2 --> HLR + SMS-GMSC -- 3 --> SMS_Router[SMS Router] + SMS_Router -- 2 --> HLR + SMS_Router -- 3 --> MSC_SGSN + MSC_SGSN -- 4 --> VLR[VLR] + MSC_SGSN -- 5 --> MS[MS] + +``` + +Figure 6.44.3-1: Main network structure and reference pts. The diagram shows the network architecture for MT-SMS. On the left, the SMS-SC is connected to the SMS-IWMSC and SMS-GMSC via interface 1. The SMS-IWMSC and SMS-GMSC are connected to the HLR via interface 2. The SMS-IWMSC and SMS-GMSC are connected to the SMS Router via interface 3. The SMS Router is connected to the HLR via interface 2 and to the MSC/SGSN via interface 3. The MSC/SGSN is connected to the MS via interface 5 and to the VLR via interface 4. The HLR is connected to the SMS Router via interface 2. + +NOTE 1: Reference point 4 is not used for SMS transfer via the SGSN. + +NOTE 2: The SMS Router is an optional entity that may be present in the MT case only. If it is not present, reference point 3 extends from the SMS-GMSC directly to the MSC/SGSN. + +**Figure 6.44.3-1: Main network structure and reference pts** + +MSISDN usage in existing messages on interfaces 1-5 would have to allow for an equivalent MSISDN-less mode. MSISDN usage primarily appears in operation in interface pts 1, 2, 3(SMS Router) and 4. On interface 5 IMSI appears to be used and may not be impacted by an MSISDN-less mode of operation. + +#### HLR: + +- The interrogation to the HLR to retrieve routing information, interface 2, would be based on new device identifier. HLR would store and access information based on this new device identifier. +- Handle updated MAP messages: + - MAP-SEND-ROUTING-INFO-FOR-SM + - MAP-REPORT-SM-DELIVERY-STATUS + - MAP-INFORM-SERVICE-CENTRE + - MAP-ALERT-SERVICE-CENTRE + +NOTE 3: The HLR is already capable of retrieving routing information based on IMSI for applications other than SMS. + +#### SMS-GMSC + +- Interrogation of the HLR to retrieve routing information will be based on the new device identifier +- Handle updated MAP messages: + - MAP-SEND-ROUTING-INFO-FOR-SM + - MAP-REPORT-SM-DELIVERY-STATUS + - MAP-INFORM-SERVICE-CENTRE + +#### SMS-IWMSC + +- Handle updated MAP message: MAP-ALERT-SERVICE-CENTRE + +#### SMS-Router + +- Handle updated MAP messages: + - MAP-SEND-ROUTING-INFO-FOR-SM + - MAP-INFORM-SERVICE-CENTRE + +#### IP-SM-GW + +- Handle updated MAP messages: + - MAP-SEND-ROUTING-INFO-FOR-SM + - MAP-REPORT-SM-DELIVERY-STATUS + +Other non SMS functionality may be affected by the absence MSISDN in the subscriber record. For example charging records generated by the SGSN may be populated with the MSISDN. See Annex A for further MSISDN dependencies and impacts for supporting MSISDN-less subscriptions which is a prerequisite for MSISDN-less/MT-SMS functionality. + +Further MAP messages are impacted in case SMS is enhanced for MSISDN-less subscriptions for the general case i.e. not only for MT-SMS used for online triggering. + +### 6.44.3.3 Properties of the solution + +This solution for MSISDN-less MT-SMS device triggering implies that: + +- a) The MTC-IWF shall behave as a Short Message Entity towards the SMS Service Centre; + +- b) The MTCsms interface pt shall maximize reuse of existing SME (MTC-IWF) SMS Service Centre protocols. SMPP is a main target for support.; +- c) A decision needs to be taken whether the MTCsms interface shall be brought into 3GPP or whether to continue having it outside the 3GPP specification (as per existing TS 23.040 [6] support) and be referenced using existing TS 23.039, to identify updated de-facto standards(s); +- d) For MTCsms: usage of other numbering plan than "ISDN/telephone numbering plan (E.164/E.163)" between the SME and SMS service centre may be considered if that minimize system impacts; +- e) Necessary MAP (TS 29.002 [18]) updates for MSISDN-less MT-SMS may require techniques (e.g. use of dummy MSISDN, MSISDN Alert values) to populate mandatory fields allowing introduction of new identifier information elements in a manner that minimizes system impacts; + +NOTE: Similar way to extend MAP will be required to introduce MSISDN-less support for PS only subscriptions in general; + +- f) Consideration to exclude CAMEL support for MSISDN-less MT-SMS if not deemed essential for Rel-11 device triggering; and +- g) Deployment of MSISDN-less MT-SMS is dependent on and requires general MSISDN-less subscription system support, or shared/dummy MSISDNs used by multiple subscriptions. + +## 6.44.4 Evaluation + +This solution minimizes system impacts by building on and extending the existing SMS functionality. + +Benefits for both solutions include: + +- Allows for use of new Device identifier within the MTC Server Provider domain +- Provides over a standardized interface the means for the MTC Server to trigger a device to establish a connection and to start to communicate with the MTC Server. +- The MTCsp interface can be a stable interface to the MTC Server, while allowing device triggering methods internal in the PLMN to evolve (e.g. MT SMS - MSISDN-less, or even new non-SMS triggering techniques). +- Can be used as a first phase in a migration towards a more optimized triggering solution. The interface towards the MTC Server is stable regardless what triggering method is used internally in the PLMN. +- Well established protocols for SME SMS-SC can be re-used on the on the MTCsms interface. +- Also addresses "Key issues" for small data transmission. + +Drawbacks for both solutions include: + +- SMS infrastructure and interface impacts. + +### MT-SMS - MSISDN based + +Benefits + +- MTC-IWF that performs MTCsp device id mapping to MSISDN allows for complete re-use of MT-SMS and associated infrastructure with no impacts to the SMS nodes and interfaces. +- Address part of the "Key Issue - MTC Identifiers" by using non E164 numbering plans. + +### MT-SMS– MSISDN-less + +Benefits + +- Re-uses existing SMS infrastructure (though with impacts). +- Address part of the "Key Issue - MTC Identifiers" whereby PS-Only MT SMS can be delivered without MSISDN. + +## 6.45 Solution – Device trigger gateway solution + +### 6.45.1 Problem Solved / Gains Provided + +- See clause 5.8 "Key Issue - MTC Device Trigger", +- clause 5.3 "Key Issue - IP Addressing", +- clause 5.11 "Key Issue - Decoupling MTC Server from 3GPP Architecture" and +- clause 5.13 "Key Issue - MTC Identifiers". + +### 6.45.2 General + +This solution shows how the key issue MTC Device Trigger can be solved with a control plane Device Trigger Gateway (DT-GW) function in the HPLMN that is flexible enough to transparently, from MTC Server/Application perspective, utilize different 3GPP services available within a particular PLMN for delivery of device trigger information from the 3GPP system to the UE while providing a single protocol for submission of the device trigger request from the MTC Server to the 3GPP system. The set of device trigger delivery services described in this solution are only for example purposes in order to show how the DT-GW solution can support any device trigger delivery service supported by the HPLMN. + +A DT-GW function could be implemented as a standalone physical entity or a functional entity. At least one DT-GW function is deployed in a HPLMN that supports the MTC device trigger feature. The DT-GW function is deployed on the boundary between the HPLMN and the public Internet, Intranet or ISP. + +To align this solution with the architectural reference model for MTC, described in clause 4.3, the DT-GW function is implemented as a functional entity within the MTC-IWF, thus simply further referred to as the Device Trigger (DT) function. The device trigger request is submitted by the MTC Server to the HPLMN of the subscribed device over the MTCsp reference point. + +### 6.45.3 Submission of device trigger request from MTC Server to HPLMN + +At any given point of time, there is at least one reachable MTC-IWF with DT function capability assigned for each subscribed MS/UE. The MTC-IWF terminates the MTCsp reference point which is used for submission of a device trigger request from an authorized MTC Server. + +The authorized MTC Server determines the IP address/ports for submitting device trigger request to a particular UE used for MTC over MTCsp through either local configuration in the MTC Server or DNS resolution as described in clause 6.46.4. Once the IP address/ports of the assigned MTC-IWF are known, the MTC Server submits a device trigger request to the assigned MTC-IWF encapsulated in an IP packet. + +When a trigger indication is received from a submitting node, the DT function first authorizes the received request, making sure it originated from a trusted MTC Server and is targeted for a device for which the MTC Server is authorized to trigger. The set of authorized MTC Servers for device triggering of a particular UE used for MTC could be configured in the assigned MTC-IWF or in the subscription data for the UE in the HSS/HLR. + +### 6.45.4 HPLMN internal handling of device triggers + +The next step is for the DT function to determine the device trigger delivery service and route to utilize for delivery of the device trigger to the UE used for MTC. This decision can be based on the one or more of the following criteria: + +- current reachability information of the UE; and/or; +- the possible device trigger delivery services supported by the HPLMN and, when roaming, VPLMN; and/or +- the UE's device trigger delivery service capabilities; and/or +- any MNO device trigger delivery policies; and/or +- information received from the MTC Server. + +The HLR/HSS is interrogated to gather UE reachability information. The relational identity (e.g. MCC, MNC) of the HLR/HSS to interrogate can be abstracted or derived from the external identifier included in the device trigger request + +(e.g. as is done today based on MSISDN). The external identifier could be a hostname device identity or a 3GPP/EPS-level subscription identity (e.g. MSISDN or ICCID). After which, the DT function then interrogates the determined HLR/HSS using the C and/or Sh interface. + +![Figure 6.45.4-1: MTC device trigger function architecture with examples of possible DT delivery services. The diagram shows the flow of device triggers from an MTC Server through various network elements to a UE. The MTC Server is connected to an MTC Application (operator controlled) and an MTC User (service provider controlled). The MTC Server sends a 'device trigger' to the MTC-IWF. The MTC-IWF is connected to the GGSN/P-GW via a G/SGi interface. The GGSN/P-GW reports 'PDP/PDN connection Gn Status(RadiusDiameter)' to the MTC-IWF. The MTC-IWF also receives 'NetworkRequested PDP Context request' from the SGSN/MME. The SGSN/MME is connected to the UE used for MTC. The MTC-IWF has a 'DNS' block and is connected to the HLR/HSS via a C/SH interface. The HLR/HSS is connected to the CDF via an Rf interface. The CDF is connected to the CTF. The CTF is connected to the AS via an ISC interface. The AS is connected to the SME via an SMS interface. The SME is connected to the CBC via a CBS interface. The CBC is connected to the GGSN/P-GW via a G/SGi interface. The GGSN/P-GW is connected to the UE used for MTC via a pre-established or new PDP/PDN connection. The diagram is divided into 'Control plane' (dashed lines) and 'User plane' (solid lines). A '3GPP Boundary' is indicated between the MTC-IWF and the GGSN/P-GW.](1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg) + +Figure 6.45.4-1: MTC device trigger function architecture with examples of possible DT delivery services. The diagram shows the flow of device triggers from an MTC Server through various network elements to a UE. The MTC Server is connected to an MTC Application (operator controlled) and an MTC User (service provider controlled). The MTC Server sends a 'device trigger' to the MTC-IWF. The MTC-IWF is connected to the GGSN/P-GW via a G/SGi interface. The GGSN/P-GW reports 'PDP/PDN connection Gn Status(RadiusDiameter)' to the MTC-IWF. The MTC-IWF also receives 'NetworkRequested PDP Context request' from the SGSN/MME. The SGSN/MME is connected to the UE used for MTC. The MTC-IWF has a 'DNS' block and is connected to the HLR/HSS via a C/SH interface. The HLR/HSS is connected to the CDF via an Rf interface. The CDF is connected to the CTF. The CTF is connected to the AS via an ISC interface. The AS is connected to the SME via an SMS interface. The SME is connected to the CBC via a CBS interface. The CBC is connected to the GGSN/P-GW via a G/SGi interface. The GGSN/P-GW is connected to the UE used for MTC via a pre-established or new PDP/PDN connection. The diagram is divided into 'Control plane' (dashed lines) and 'User plane' (solid lines). A '3GPP Boundary' is indicated between the MTC-IWF and the GGSN/P-GW. + +**Figure 6.45.4-1: MTC device trigger function architecture with examples of possible DT delivery services** + +The interrogated HLR/HSS returns the latest reachability information available in the HLR/HSS for the specified UE. Additionally, the HLR/HSS could return the device trigger delivery service capabilities of the UE. + +Separately, for each UE with an assigned MTC-IWF, GGSN/P-GW reports the status of PDP/PDN connections (i.e. PDP/PDN connection establishment/disconnection and IP address changes) to the assigned MTC-IWF using the Radius/Diameter interface (as described in clause 16 of TS 29.061 [4]). + +MNO device trigger delivery policy information could be configured as part of the subscription data in the HLR/HSS, the MTC-IWF. + +The DT function uses the gathered reachability, capabilities and MNO policy information to determine the most efficient and effective service and route to use for forwarding delivery of the device trigger indication to be delivered to the UE used for MTC. + +To support the charging of device triggering, the DT function includes a CTF (Charging Trigger Function) in order to generate charging events based on the triggering indications sent by the MTC Server. To support this, an Rf reference point is defined between the MTC-IWF and the CDF entity. + +To support the SMS based trigger, the DT function includes a SME (Short Message Entity) function in order to generate SMS trigger requests based on the triggering indications sent by the MTC Server. The SME uses validity time in MTCsp for mapping to the Validity Period in SMS delivery. + +## 6.45.5 Delivery of device trigger from HPLMN to UE + +The device trigger delivery services described in this clause are for example purposes only in order to show how the DT-GW solution can support any device trigger delivery service supported by the HPLMN. Some possible examples of device trigger delivery services that could be supported are shown in Figure 6.45.4-1, for which the DT function reformats, as needed, and forwards the trigger indication to the appropriate: + +- a) GGSN/P-GW for delivery over an already established PDP context / PDN connection; +- b) GGSN for delivery over a newly established PDP context (via a Network-Requested PDP Context Activation Procedure initiated by the DT function e.g. as described in clause 6.41); +- c) S-CSCF for delivery over SIP/IMS service; +- d) SMS-SC for delivery over SMS; or +- e) CBC for broadcast delivery over CBS (assumes location information available in trigger indication request or from other source in order to limit the broadcast area). + +When a routable PDP context / PDN connection is pre-established in the UE used for MTC (as described in bullet a) or is newly established (as described in bullet b), the DT function utilizes this connection to deliver the device trigger to the UE using IP-based communications. + +The deployment of these trigger delivery services could be done in a phased approach without impacting the MTC Server implementation which will be largely transparent to the delivery service mechanism selected by the DT function. + +## 6.45.6 DT functionality + +The DT functionality includes the following: + +- submission over MTCsp of a device trigger indication messages into the PLMN request from an MTC Server to the assigned MTC-IWF of a targeted UE used for MTC; + +NOTE: It should be possible for an MTC Server to resolve by DNS the MTC-IWF for a specific UE used for MTC. + +- authorization that the device trigger request is from a trusted MTC Server; +- authorization that the UE used for MTC addressed in a device trigger request is from a MTC Server that is authorized to trigger the addressed UE used for MTC; +- determination of HLR/HSS to interrogate for the availability of the UE used for MTC based on the external identifier included in the device trigger request; +- selection of the device trigger delivery service and route to use for delivery of the device trigger to the UE used for MTC (e.g. based on collected reachability information , UE's device trigger delivery service capabilities and network operator policy); +- reformatting, as needed, of the device trigger information to match the format required for the selected delivery service; +- forwarding of trigger information from the DT function to the selected delivery service entity for delivery to the UE used for MTC; +- generation of accounting messages at the CTF; and +- Appropriate e.g. error handling, error logging and/or error notification when trigger indication is determined to be invalid or unauthorized. + +The UE used for MTC must be capable of receiving, interpreting and providing a trigger indication to the appropriate MTC application on the UE, if the trigger content is application specific. + +## 6.45.7 Information flows + +MTC-IWF receives a Device Trigger request from the MTC server, interrogates the HSS to obtain UE IMSI and serving SGSN/MME information etc., if not available locally and delivers trigger information to the next serving node involved in the delivery of the trigger request. + +![Figure 6.45.7-1: Device Trigger Flow diagram showing the sequence of messages between MTC Device, SGSN/MME, PGW/GGSN, MTC-IWF, HSS, and MTC Server.](b50f38be091844d58b11e3d47bc71e73_img.jpg) + +``` + +sequenceDiagram + participant MTC Server + participant HSS + participant MTC-IWF + participant SGSN/MME + participant PGW/GGSN + participant MTC Device + Note right of MTC Server: other nodes + + MTC Server->>MTC-IWF: 1. Device Trigger Request + MTC-IWF->>HSS: 2. Inquiry + MTC-IWF->>MTC Server: 3. Delivery Ack + MTC-IWF->>SGSN/MME: 4. Delivery Request + SGSN/MME->>MTC Device: 5. Delivery Req + MTC Device->>SGSN/MME: 6a. Delivery Resp + SGSN/MME->>MTC-IWF: 6b. Delivery Resp + MTC-IWF->>MTC Server: 6c. Delivery Response + MTC Device->>PGW/GGSN: 7. PDP/PDN activation + MTC Device->>MTC Server: 8. Application signalling + +``` + +Figure 6.45.7-1: Device Trigger Flow diagram showing the sequence of messages between MTC Device, SGSN/MME, PGW/GGSN, MTC-IWF, HSS, and MTC Server. + +Figure 6.45.7-1: Device Trigger Flow + +1. The MTC Server wants to communicate with the MTC device, but has no sufficient information for being able to send data packets to the MTC device or identified a need to recover or test IP connectivity, e.g. as the device is not responding anymore. The MTC server submits a Device Trigger Request providing the external device identifier and optionally a validity period or need for recovery of the IP connectivity. +2. The MTC-IWF authorises the trigger request. The IWF interrogates the HSS with the external device identifier to derive the IMSI and any additional information needed for trigger delivery. +3. The MTC-IWF may return trigger Deliver Ack to the MTC server confirming the submission of trigger request. In case of failure, a failure cause may be included to indicate the reason of failure e.g., network congested or overloaded, MTC-IWF can not find UE routing information from HSS, UE is unreachable, etc. +4. The MTC-IWF selects the trigger delivery method and forwards the delivery request to the next node involved in the delivery. + +For the trigger delivered over T5a/T5b, if any APN is provided and known and no bearer exists for that APN the SGSN/MME may perform APN related load control, i.e. decides whether to deliver the request to the device. + +5. The SGSN/MME delivers the device trigger to the MTC device using Delivery Request message. For the trigger delivered over T5a/T5b, the delivery of Delivery Request may be upon the next NAS signalling exchange with the UE as indicated in clause 6.39 step 3. +6. The success or failure of delivery of trigger Delivery Request is acknowledged to the MTC server via Delivery Response message with appropriate cause value. + +For successful delivery of the device trigger, the MTC device acknowledges the Delivery Request using Delivery Response message with a success cause value to the MTC server via SGSN/MME and MTC-IWF (steps 6a, 6b and 6c). For the trigger delivered over T5, the Delivery Response message may be different NAS messages. + +7. The MTC device activates the PDP/PDN connection if necessary. +8. The application on the MTC device communicates with the MTC server, e.g. it registers with the application server. + +Editor's note: The handling of the validity period needs to be described. + +## 6.45.8 Impacts on existing nodes or functionality + +Impact to the Core Network: + +- Deployment of the DT function; +- New instances of pre-defined reference points (e.g. C, Sh, ISC, Gn, Gi/SGi) to connect the DT function in the MTC-IWF to HLR/HSS, the GGSN/P-GWs and the actual trigger delivery services (e.g. SMSC, CBS, S-CSCF, GGSN/PGW, etc.). + +- Storage of the assigned MTC-IWF of a particular UE used MTC and possibly the UE's device trigger delivery service capabilities; +- HLR/HSS, MTC-IWF or UE to store addresses of authorized MTC servers for device triggering of a particular MTC device; +- HLR/HSS or MTC-IWF to store network operator policy information used for device trigger delivery service and route. + +## 6.45.9 Evaluation + +Benefits: + +- Remove the burden of determining the type of trigger delivery service to invoke and support from MTC Server implementation; +- Allow for many different sets of trigger delivery services to be utilized across MNOs without impacting MTC Server on the device trigger request submission functionality (i.e. delivery to UE transparent from submission to HPLMN); +- Allows for secure authorization and delivery of device triggers from authorized MTC Servers; +- Supports both MSISDN-based and MSISDN-less subscriptions (with phased rollout approach and/or simultaneously support). + +Drawbacks: + +- Requires new device trigger information to be stored in HLR/HSS; +- Requires new DT function in the HPLMN; +- Requires new instances of pre-defined reference points for reachability determination; + +## 6.46 Solution - Address resolution via MTC-IWF + +### 6.46.1 Problem Solved / Gains Provided + +See clause 5.3 "Key Issue - IP Addressing" , clause 5.8 "Key Issue - MTC Device Trigger" and clause 5.13 "Key Issue - MTC Identifiers". + +### 6.46.2 General + +This solution solves two similar requirements: + +- How to determine the routable IP address(es) of a UE used for MTC for initiating UP MT communications (as required in clause 5.3.2); and; +- How to determine the MTCsp reference point terminating in the assigned MTC-IWF of a UE used for MTC to initiate CP device triggering (required in clause 5.8.2). + +Similar to the solution in clauses 6.1 and 6.38, UEs used for MTC that need to be reachable for data plane mobile terminated communications are assigned an external identifier that can be structured as a static unique hostname (e.g. a FQDN, NAI, dedicated 3GPP URN or URI). + +Distinct from the solutions in clause 6.1 and 6.38, the hostname of the device is used to perform a DNS query for the address of the MTCsp reference point terminating in the assigned MTC-IWF. This address is then used either to request the assigned MTC-IWF for the routable IP address(es) to use for initiating data plane mobile terminated communications, as described further in clause 6.43.3, or to request the assigned MTC-IWF to e.g. perform control plane device triggering, as described further in clause 6.43.4. + +When a message related to a particular UE used for MTC is sent over MTCsp, the device external identifier included in the message could be a hostname or just the standalone 3GPP/EPS-level external subscription identity of the UE (e.g. MSISDN, ICCID). In either case, this solution can simultaneously support both MSISDN-based and MSISDN-less + +subscriptions. However, to allow for a phased rollout of MTC features, initially this solution may only support subscriptions with an assigned MSISDN. + +As the assigned MTC-IWF for a particular UE used for MTC will rarely change, if at all, the MTC Server will infrequently need to perform the DNS query to resolve the assigned MTC-IWF address. This approach significantly reduces the number of DNS query procedures to be performed relative to if a DNS query were to be performed each time a MTC Server needed to determine the current reachable IP addresses of a particular UE used for MTC. Additionally, this approach significantly reduces the number of DNS updates that must be performed relative to if a DNS update were to be performed each time a PDN connection was established or disconnected for a UE used for MTC (aka dynamic DNS). + +### 6.46.3 UP MT communications UE current IP address resolution + +When the routable UP IP address of the target UE is unknown, the sample call flow scenario depicted in Figure 6.46.3-1 illustrates how UP MT communication can be achieved through the use of the hostname device identity lookup of the IP address of the assigned MTC-IWF. + +![Figure 6.46.3-1: Call flow scenario for UP MT communications UE current IP address resolution. The diagram shows a sequence of interactions between MS/UE, GGSN/P-GW, HLR/HSS, DNS, MTC-IWF, and MTC Server. The sequence starts with a DNS update from MTC-IWF to DNS (1. DNS update of address of assigned MTC-IWF). An alternative path shows HLR/HSS sending a DNS update to DNS (1'. DNS update of address of assigned MTC-IWF). Next, MTC Server sends a DNS lookup to DNS (2. DNS lookup(URI device identity of UE used for MTC)). Then, a PDP context/default EPS bearer activation procedure occurs (3. PDP context/ default EPS bearer activation procedure). MTC Server sends an IP address determination request to MTC-IWF (4.&5. IP address determination reqrsp). MTC Server initiates initial MT communications over the data plane (6. initial MT communications over data plane). Finally, IP communications over a globally routable PDP context/PDN connection are established (7. IP communications over globally routable PDP context/PDN connection).](a9241101d638c568cd5a84ab7ad39f15_img.jpg) + +Figure 6.46.3-1: Call flow scenario for UP MT communications UE current IP address resolution. The diagram shows a sequence of interactions between MS/UE, GGSN/P-GW, HLR/HSS, DNS, MTC-IWF, and MTC Server. The sequence starts with a DNS update from MTC-IWF to DNS (1. DNS update of address of assigned MTC-IWF). An alternative path shows HLR/HSS sending a DNS update to DNS (1'. DNS update of address of assigned MTC-IWF). Next, MTC Server sends a DNS lookup to DNS (2. DNS lookup(URI device identity of UE used for MTC)). Then, a PDP context/default EPS bearer activation procedure occurs (3. PDP context/ default EPS bearer activation procedure). MTC Server sends an IP address determination request to MTC-IWF (4.&5. IP address determination reqrsp). MTC Server initiates initial MT communications over the data plane (6. initial MT communications over data plane). Finally, IP communications over a globally routable PDP context/PDN connection are established (7. IP communications over globally routable PDP context/PDN connection). + +**Figure 6.46.3-1: Call flow scenario for UP MT communications UE current IP address resolution** + +1. Initially, e.g. when the UE used for MTC subscription is provisioned or changed, a MTC-IWF of the HPLMN is assigned as part of the subscription data stored in the HSS/HLR. Afterwards, the MTC-IWF performs a DNS update to the DNS authoritative server that stores the association between the hostname of the UE and the assigned MTC-IWF address. +- 1'. Alternatively, the HSS/HLR could perform the DNS update to the DNS server. +2. At some point thereafter, the MTC Server performs a DNS query for the hostname of the UE in order to determine the address of the assigned MTC-IWF. The MTC Server may then store the assigned MTC-IWF address for later use while assuming the assigned MTC-IWF will largely not be changed for the UE. +3. At some point thereafter, a PDP/PDN connection is initiated and established for the UE that is reachable by the MTC Server. +4. At some point thereafter, the MTC Server needs to initiate MT communicate with the UE but does not know the routable IP address(es); thus will send an IP address determination query to the assigned MTC-IWF over MTCsp. +5. The assigned MTC-IWF returns an IP address determination response with the routable IP address(es) and, possibly, the SRC/DST ports to use for MT communications with the UE. +6. The MTC Server initiates the MT communications. + +## 6.46.4 CP device triggering assigned MTC-IWF address resolution + +When the MTCsp reference point for submitting a CP device trigger to a target UE is unknown, the sample call flow scenario depicted in Figure 6.46.4-1 illustrates how CP device triggering can be achieved through the use of the hostname device identity lookup of the IP address of the assigned MTC-IWF. + +![Sequence diagram illustrating the call flow scenario for CP device triggering assigned MTC-IWF address resolution. The diagram shows interactions between MS/UE, GGSN/P-GW, HLR/HSS, DNS, MTC-IWF, and MTC Server. The sequence starts with a DNS update from MTC-IWF to DNS, followed by a DNS update from HLR/HSS to DNS. Then, a DNS lookup is performed by MTC-IWF on DNS for the UE's device identity. The MTC Server sends a trigger indication request to the MTC-IWF, which ACKs. The MTC-IWF then delivers the trigger indication to the MS/UE via the GGSN/P-GW. The MS/UE initiates a PDP context/default EPS bearer activation procedure. Finally, the UE initiates IP communications over the data plane with the MTC Server, and IP communications continue over a globally routable PDP context/RDN connection.](868ee7df1ec851f132ccf8c390de76a8_img.jpg) + +``` + +sequenceDiagram + participant MS/UE + participant GGSN/P-GW + participant HLR/HSS + participant DNS + participant MTC-IWF + participant MTC Server + + Note right of MTC-IWF: 1. DNS update of address of assigned MTC-IWF + MTC-IWF->>DNS: 1. DNS update of address of assigned MTC-IWF + Note right of HLR/HSS: 1'. DNS update of address of assigned MTC-IWF + HLR/HSS->>DNS: 1'. DNS update of address of assigned MTC-IWF + Note right of MTC-IWF: 2. DNS lookup(URI device identity of UE used for MTC) + MTC-IWF->>DNS: 2. DNS lookup(URI device identity of UE used for MTC) + Note right of MTC Server: 3. trigger indication request + MTC Server->>MTC-IWF: 3. trigger indication request + MTC-IWF->>MTC Server: ACK + Note right of GGSN/P-GW: 4. trigger indication delivery + MTC-IWF->>GGSN/P-GW: 4. trigger indication delivery + Note right of MS/UE: 5. PDP context/ default EPS bearer activation procedure + MS/UE->>GGSN/P-GW: 5. PDP context/ default EPS bearer activation procedure + Note right of MS/UE: 6. UE initiates IP communications over data plane + MS/UE->>MTC Server: 6. UE initiates IP communications over data plane + Note right of MS/UE: 7. IP communications over globally routable PDP context/RDN connection + MS/UE->>MTC Server: 7. IP communications over globally routable PDP context/RDN connection + +``` + +Sequence diagram illustrating the call flow scenario for CP device triggering assigned MTC-IWF address resolution. The diagram shows interactions between MS/UE, GGSN/P-GW, HLR/HSS, DNS, MTC-IWF, and MTC Server. The sequence starts with a DNS update from MTC-IWF to DNS, followed by a DNS update from HLR/HSS to DNS. Then, a DNS lookup is performed by MTC-IWF on DNS for the UE's device identity. The MTC Server sends a trigger indication request to the MTC-IWF, which ACKs. The MTC-IWF then delivers the trigger indication to the MS/UE via the GGSN/P-GW. The MS/UE initiates a PDP context/default EPS bearer activation procedure. Finally, the UE initiates IP communications over the data plane with the MTC Server, and IP communications continue over a globally routable PDP context/RDN connection. + +**Figure 6.46.4-1: Call flow scenario for CP device triggering assigned MTC-IWF address resolution** + +1-2. Same as steps 1-2 illustrated in figure 6.46.3-1. + +3. At some point thereafter, the MTC Server needs to send a device trigger indication to the UE used for MTC; thus sending it to the assigned MTC-IWF over MTCsp. + +4. The network delivers the device trigger indication to the UE. + +5. A PDP/PDN connection is initiated and established for the UE that is reachable by the MTC Server. + +6. The UE initiates data plane communications with the requesting entity (e.g. MTC Server). + +7. IP communications continues. + +## 6.46.5 Impacts on existing nodes or functionality + +Impacts on CN nodes: + +- DT function solution specified in clause 6.45 shall be supported by the Core Network; +- a network interface between authoritative DNS server and DT-GW is required to perform DNS updates when the assigned DT-GW for a UE used for MTC is initially assigned or changed. + +## 6.46.4 Evaluation + +Benefits: + +- DNS update and DNS query frequency drastically less vs. requiring a DNS update/query each time a PDN connection is established/disconnected or the IP address of the device changes; +- As assigned MTC-IWF will rarely change, if at all, there is little risk of "middlemen" ISPs ignoring the TTL for a DNS record containing the association of the hostname of the UE used for MTC and the assigned MTC-IWF address; +- For security, DNS updates of the authoritative DNS server can be limited to only originating from within the HPLMN; + +- Supports both MSISDN-based and MSISDN-less subscriptions (with phased rollout approach and/or simultaneously). + +Drawbacks: + +- Dependency on MTC-IWF deployment in HPLMN. + +## 6.47 Solution – UE without unique MSISDN using ICCID + +### 6.47.1 Problem Solved / Gains Provided + +See clause 5.8 "Key Issue – MTC Device Trigger", see clause 5.13 "Key Issue – MTC Identifiers". + +### 6.47.2 General + +A unique Integrated Circuit Card ID (ICCID), defined by ITU-T Recommendation E.118 [7], is stored today in every UICC. The ICCID may be used by a mobile network, MTC Server, MTC Application and/or MTC user as a unique external identifier for PS only devices that do not specifically require an MSISDN (i.e. no Circuit-Switched support). + +The ICCID is a 20-digit number comprised of a variable length (maximum 7-digits) Issue Identification Number (IIN), a variable length (11 to 14 digits) Individual account identification number and a check digit. It is stored in the UICC Elementary File, EF<sub>ICCID</sub> and efficiently encoded in BCD format (1-nibble per digit) as described in ETSI TS 102.221 [8]. + +An ICCID with the minimum sized Individual account identification number (11-digits) provides $\sim 10^{11}$ or 100B unique identifiers per IIN. This amount per issuer (e.g. per MNO) would appear to be more than adequate to provide a new unique subscription identifier for the expected onslaught of new M2M devices. + +Similar to the MSISDN, the composition of the ICCID contains enough routeing information that can be used to identify the HSS/HLR of the MS/UE. The IIN is composed of a Country code field (analogous to the CC in the MSISDN or MCC in the IMSI) and an Issue identifier number field (analogous to the NDC in the MSISDN or the MNC in the IMSI). If further routeing information is required, it could be contained in the first few digits of the Individual account identification number field. + +When a hostname based external identifier (e.g. FQDN, NAI, URI or 3GPP specific URN) is defined for a UE, the ICCID can be included as part of the hostname (e.g. FQDN: mtc.ICCID.pub.3gppnetworks.org or ICCID.userid.serviceproviderid.topdomain) in order to associate the hostname with a particular UE used for MTC. + +If flexibility for 1-to-1 mapping between the external subscription identifier and IMSI are required (i.e. multiple unique external subscription identifiers per IMSI) then the ICCID could be used as a base for a set of multiple unique IDs associated with a particular IMSI. + +The impacted network entities (e.g. MTC-IWF, HLR/HSS) and interface protocols are enhanced to support the above functionality so that a UE subscription can be identified by its ICCID and mapped to the internal identifier of the UE. + +### 6.47.3 Impacts on existing nodes or functionality + +### 6.47.4 Evaluation + +Benefits: + +- provides a pre-existing unique ID that is generated and available today at the device; +- could be a base for unique IDs when multiple subscription identifiers per IMSI are required; +- plethora ( $\sim 100B$ ) of unique IDs per Issue Identification Number; +- efficiently encoded. + +Drawbacks: + +- if (U)SIM needs to be swapped to change network operator subscription, ICCID will not be portable to new network operator; + +- if (U)SIM is permanently coupled to ME, when subscription needs to be swapped to a different UE/MS, ICCID will not be portable to new device and MNO cannot use ICCID as a permanent identifier for the subscription; + +**Editor's note:** It is FFS if subscription identifier portability is required for PS only subscriptions without MSISDN. + +- the granularity for the ICCID is per MT and there could be multiple TEs per MT; +- similar to MSISDN, ICCID identifier of a UE/MS is easily ascertainable (e.g. sometimes printed on inside device). + +## 6.48 Solution - Transfer data via SMS for MTC Devices sharing one MSISDN + +### 6.48.1 Problem Solved / Gains Provided + +See clause 5.2 "Key Issue - MTC Devices communicating with one or more MTC Servers." and 5.13 "Key Issue - MTC Identifiers" + +### 6.48.2 General + +For the lack of MSISDN, MTC Devices belonging to the same MTC Subscriber could share one MSISDN for the purpose of transferring data via SMS. For these MTC Devices, a static unique "MTC Device ID" (e.g. an FQDN identifier or a private number specific to the MTC device or subscription such as IMSI) needs to be assigned and the association between the "MTC Device ID" and the IMSI is stored in HLR/HSS, in case the "MTC Device ID" is not the IMSI, and optionally in the VAS AS. The static "MTC Device ID" can be configured into the MTC Device via OMA DM or SIM OTA or be statically configured as part of the subscription info. Privacy of "MTC Device ID" has to be protected if the "MTC Device ID" is configured in the MTC Device. + +NOTE 1: Using the IMSI as "MTC Device ID" (i.e. as an External identifier) implies that the MTC Server may have to be under operator control or have trust relationship with the operator. + +**Editor's note:** How the coupling between the common MSISDN and a static unique "MTC Device ID" can support number portability requirements, if needed, is FFS. + +For MO communication of MTC devices sharing one MSISDN via SMS (i.e. the SMS is sent from the MTC Device to the MTC Server), the MTC Device shall insert the "MTC Device ID" into the SMS. The MTC Server identifies the MTC Device by the "MTC Device ID" contained in the SMS. + +Alternatively, the "MTC Device ID" is inserted by the MSC/SGSN in the MAP-MO-FORWARD-SHORT-MESSAGE similar to how it works with the MSISDN in current specifications. + +For MT communication of MTC devices sharing one MSISDN via SMS (i.e. the SMS is sent from the MTC Server to the MTC Device), the following procedures are performed: + +- The MTC Server sends a SMS with the "MTC Device ID" in the header or the body of the SMS and the DA (destination address) of the SMS is set to the common MSISDN of the target MTC Device. And the SMS is routed to the VAS AS serving the MTC Devices identified by the common MSISDN. +- The VAS AS acts as an SMS GMSC to interrogate the HLR/HSS with the "MTC Device ID" which is obtained from the SMS directly. Or, if the VAS AS has stored the mapping information between the IMSI and the "MTC Device ID" of the MTC Device, the VAS AS interrogates the HLR/HSS with the IMSI of the MTC Device if the "MTC Device ID" is not the IMSI, based on the "MTC Device ID" in the SMS. +- The VAS AS delivers the SMS to the MTC Device according to the routing info returned from the HLR/HSS. +- The MTC Device verifies the "MTC Device ID" in the message upon receiving the SMS. + +Alternatively, in case having stored the internal association between "MTC Device ID" and the IMSI, if the "MTC Device ID" is not the IMSI, VAS AS can submit to the SMS Center a new SMS as specified in TS 23.142 [9] with the DA of the SMS set to the IMSI of the MTC Device. After receiving the SMS submitted by the VAS AS, SMS GMSC interrogates the HLR/HSS with the IMSI. With the returned routing information from HLR/HSS, SMS GMSC delivers the SMS to the MTC Devices according to the IMSI and the routing info as specified in TS 23.040 [6]. + +Another alternative method is that the SMS GMSC interrogates the HLR/HSS with the "MTC Device ID" which is obtained from the SMS and delivers the SMS according to the IMSI and the routing info returned from HLR/HSS as specified in TS 23.040 [6] when receiving the SMS from the MTC Server. No VAS AS is involved in this alternative. + +**Editor's note:** The use of the shared MSISDN in the delivery of SMSs needs to be further developed. + +### 6.48.3 Impacts on existing nodes or functionality + +This solution is dependent on 6.2 Solution - Transfer data via SMS. See also clause 6.2.3. + +### 6.48.4 Evaluation + +Drawbacks: + +- Including the "MTC Device ID" inside the SMS would decrease the effective payload size and increase overhead. Some "MTC device ID" proposed in this TR may exceed the size of SMS, e.g. an URI. Concatenated SMSs can be used in order to transfer the data and contain the "MTC device ID". The "MTC Device ID" when provided by the UE will need to be linked to the subscription so that it can be trusted. +- Modifications to the MSC/SGSN are required if the "MTC Device ID" is asserted by the MSC/SGSN. Modifications to the protocol are also required if the "MTC Device ID" cannot be carried in the TS 23.040 [6] TP-OA field. +- For MT communication of MTC devices sharing one MSISDN modifications will be required to SMS-GMSC and HSS if the "MTC Device ID" cannot be carried in the TP-DA field. +- The MSC/SGSN may have problems with large numbers of devices sharing the same MSISDN. +- Impacts on the OCS if a large number of devices are sharing the same MSISDN. + +## 6.49 Solution - UE configured to build its IPv6 address with the provided interface identifier + +### 6.49.1 Problem Solved / Gains Provided + +See clause 5.3 "Key Issue - IP addressing". + +### 6.49.2 General + +According to TS 23.401 [5] and TS 23.060 [21], the GGSN/P-GW shall provide an interface identifier to the UE to use it as a link-local address in order to avoid any collision with the link-local address of the GGSN/P-GW. This interface identifier may also be used by the UE to build its global IPv6 address. + +For functions requiring the full IP address knowledge in the network, it is proposed in this solution that the UE uses the interface identifier assigned by the GGSN/P-GW to construct its global IPv6 address. Thus, the MTC device will append its interface identifier (64 bits) to the prefix (64 bits) received in the Router Advertisement. For security reasons, it is assumed that the GGSN/P-GW is in charge of providing a well randomized interface identifier. + +Consequently, the GGSN/P-GW knows the full IPv6 address used by the MTC device and solutions listed in clauses 6.1 and 6.41 can be realised without any need for a stateful address configuration. + +To support this solution, a "UE configured to build its IPv6 address with the provided interface identifier" is introduced. Such UE shall indicate to the GGSN/P-GW that it will use the interface identifier to construct its global IPv6 address. In addition, MTC device should keep the global address configured and avoid changing its interface ID. + +## 6.50 Solution - Use of FQDN Identifier with Dynamic DNS Update + +### 6.50.1 Problem Solved / Gains Provided + +See clause 5.3 "Key Issue - IP addressing" and clause 5.2 "Key Issue - MTC Devices communicating with one or more MTC Servers". + +## 6.50.2 General + +This solution addresses some aspects of IP addressing related to MT communications initiated by the MTC server. It is based on the FQDN Identifier solution described in clause 6.1 and proposes to use dynamic DNS updates initiated by the UE instead of a network entity. In case of stateless IPv6 addressing, this overcomes the problem of the network ignoring the global IPv6 address used by the MTC device. In this case, DNS updates are performed after the UE configures its IPv6 address via stateless IPv6 address autoconfiguration and when the UE changes its IPv6 address. Hosts with a IPv6 stack that frequently change their address for privacy reasons can use Dynamic DNS Updates (RFC 2136) to allow the authoritative DNS to keep the association between FQDN and the current IP address up to date. This solution is also applicable to IPv4 addressing. + +**Editor's note:** Huge numbers of UEs that frequently signal a change of IP address may create an untenable load on the network. Therefore, the use of IPv6 privacy extensions, and if used the frequency at which the UE may be allowed to change its IP address, is FFS. + +Consequently, the call flow depicted in clause 6.1 becomes: + +![Sequence diagram showing the call flow for MT communication with MTC device using Dynamic DNS Updates. The diagram involves six lifelines: MTC device, MME, SGW/PGW, HSS/AAA, DNS, and MTC server. The sequence starts with the MTC device performing an EPS Attach procedure. It then sends a DNS Update (FQDN, 'D') to the DNS server. Later, a DNS Update (FQDN, 'D') for a UE Address change is sent. The MTC server wishes to send an MT message, sends a DNS Query (FQDN) to the DNS server, receives a DNS Response ('D'), sets the destination IP address to 'D', and sends a packet to the IP address. Finally, the packet is delivered in an EPS bearer to the MTC device.](6ee202d340236de98def8045f273fa38_img.jpg) + +``` + +sequenceDiagram + participant MTC device + participant MME + participant SGW/PGW + participant HSS/AAA + participant DNS + participant MTC server + + Note over MTC device, HSS/AAA: 1. EPS Attach procedure (3GPP TS 23.401); Assignment or stateless autoconfiguration of a public address "D" + MTC device->>DNS: 2. DNS Update (FQDN, "D") + Note over MTC device, DNS: 3. DNS Update (FQDN, "D") UE Address change + MTC server->>MTC server: 4. MTC server wishes to send MT message + MTC server->>DNS: 5. DNS Query (FQDN) + DNS->>MTC server: 6. DNS Response ("D") + Note over MTC server, DNS: 7. Send packet to IP@="D" + MTC server-->>MTC device: 8. Packet delivered in EPS bearer + +``` + +Sequence diagram showing the call flow for MT communication with MTC device using Dynamic DNS Updates. The diagram involves six lifelines: MTC device, MME, SGW/PGW, HSS/AAA, DNS, and MTC server. The sequence starts with the MTC device performing an EPS Attach procedure. It then sends a DNS Update (FQDN, 'D') to the DNS server. Later, a DNS Update (FQDN, 'D') for a UE Address change is sent. The MTC server wishes to send an MT message, sends a DNS Query (FQDN) to the DNS server, receives a DNS Response ('D'), sets the destination IP address to 'D', and sends a packet to the IP address. Finally, the packet is delivered in an EPS bearer to the MTC device. + +**Figure 6.50.2-1: Call flow for MT communication with MTC device using Dynamic DNS Updates** + +1. MTC device performs the EPS Attach procedure as described in TS 23.401 [5]. As part of the EPS Attach procedure, a public IP address is assigned or Stateless IPv6 address autoconfiguration is accomplished, resulting in the MTC device being configured with a public IP address, referred to here shortly as "D", and information about the authoritative DNS is sent in PCO. +- 2, 3. MTC device stores the association between the FQDN and "D" in the authoritative DNS server. The MTC device performs DNS Updates whenever it changes its interface ID. + +**Editor's note:** Huge numbers of UE that frequently signal a change of IP address may create an untenable load on the network. Therefore, the use of IPv6 privacy extensions, and if used the frequency at which the UE may be allowed to change its IP address, is FFS. + +4. At some point the MTC server wishes to send a Mobile terminated (MT) message to the MTC device whose unique identifier is FQDN. +5. MTC server sends a DNS query to the authoritative DNS server. +6. The authoritative DNS sends "D" to the MTC server. +7. MTC server sets the Destination IP address in the packet it wishes to send to the MTC device to "D". +8. The PGW serving the MTC device delivers the packet to the MTC device using an appropriate EPS bearer. + +NOTE 1: Security measures shall be taken in order to avoid attacks on the DNS from a rogue/misbehaving MTC device. + +Editor's note: If the MTC device has multiple PDN connections, it is FFS which IP address the MTC Server selects for sending packets to the MTC device. + +Editor's note: Scalability of this solution is FFS. + +## 6.51 Solution- MT Communication with MTCsp/MTCsms signalling + +### 6.51.1 Problem Solved/ Gains Provided + +See clause 5.3 "Key Issue - IP Addressing". + +### 6.51.2 General + +This solution is based on using MTC Device Trigger from MTC Server in order to have the MTC device initiate an IP communication with the MTC server. The first outbound IP packet from the UE creates a mapping in the NAT device between the private IP address of the UE and a (public IP address, port number) couple. When the MTC server receives this IP packet, it knows the public IP address and port number allocated by the NAT to the UE. + +This procedure is depicted in the figure below: + +![Sequence diagram illustrating MT communication with MTCsp signalling. The diagram shows four entities: UE used for MTC, NAT, DT-GW, and MTC server. The sequence of events is: 1. MTC server wishes to send MT message; 2. Trigger; 3. MO communication.](6e9fbc3d95eb2b3f67cbbbd5de0c3999_img.jpg) + +``` +sequenceDiagram + participant UE as UE used for MTC + participant NAT as NAT + participant DT-GW as DT-GW + participant MTC_server as MTC server + Note right of MTC_server: 1. MTC server wishes to send MT message + MTC_server->>DT-GW: 2. Trigger + DT-GW->>UE: + UE->>MTC_server: 3. MO communication +``` + +Sequence diagram illustrating MT communication with MTCsp signalling. The diagram shows four entities: UE used for MTC, NAT, DT-GW, and MTC server. The sequence of events is: 1. MTC server wishes to send MT message; 2. Trigger; 3. MO communication. + +Figure 6.51.2-1: MT communication with MTCsp signalling + +1. The MTC server wishes to send a Mobile Terminated packet to the UE used for MTC and the MTC server doesn't know the IP address of the UE used for MTC. +2. The MTC server sends a trigger indication over the MTCsp reference point to DT-GW (also called MTC IWF) or using MTCsms. Which trigger solution to use is agnostic for this solution, but the trigger needs to include the IP address (or FQDN) and port of the application that the UE has to contact. + +NOTE 1: The trigger delivery service selected by the DT-GW is outside of the scope of this solution. The trigger delivery service is mainly described in clause 6.45, but can be also a part of other solutions. + +3. Once the UE used for MTC is notified by the network, it initiates a communication to the MTC server by sending a trigger response; the first outbound packet creates a mapping from a port number on the NAT, which forwards the IP packet with a mapped public IP address and a port number that distinguishes the UE used for MTC within the private addressing space. The MTC server sends the MT packet to the targeted UE used for MTC within this communication. + +NOTE 2: In order to recognize which UE used for MTC sent the IP packet containing the trigger response, the UE used for MTC should include its Device Identifier, which may be different from the one used over MTCsp/MTCsms. Alternatively, another mechanism could be specified to solve this need. + +NOTE 3: If there are several applications running on the UE used for MTC, then the trigger needs to support multiple applications (e.g. see clauses 6.40 and 6.45) + +### 6.51.3 Impacts on existing nodes or functionality + +This solution reuses the Device Trigger Gateway solution described in clause 6.45. The only additional impact is on the MTC Server, to behave as described above. + +### 6.51.4 Evaluation + +Benefits for this solution include: + +- No configuration of NAT is required. +- An external port on NAT is open only when there is a need for communication; this avoids the UE used for MTC to receive IP packets from non legitimate sources. +- Keep-alive messages are avoided when there is no traffic exchanged between the UE used for MTC and the MTC Server. + +Drawbacks of this solution include: + +- the solution relies on a trigger response message between the UE used for MTC and the MTC Server for delivery of the device ID; +- the solution relies on a separate channel to deliver a 'Push' stimulus. + +## 6.52 Solution - Transfer of device trigger or data via optimised SMS + +### 6.52.1 Problem Solved / Gains Provided + +See clauses 5.4 "Key Issue - Online Small Data Transfer" and 5.8 "MTC Device Trigger". + +### 6.52.2 General + +#### 6.52.2.1 Overview + +Various mechanisms for addressing the MTC 'small data transmission' topic have been proposed in contributions to SA WG2. Typically they proposed message flows with some similarities to SMS, but, propose new interfaces and slightly different functionality. The use of such new functionality poses some challenges for rolling out the feature in roaming situations. + +In order to allow a proper evaluation and identification of the best solution, this solution takes an alternative approach by looking at what optimisations can be made to the existing SMS mechanisms. + +There are 6 components to the optimisations: + +- i) For UMTS-PS; UMTS-CS; GSM-CS; 2G-GPRS; and SMS over SGs in LTE; removal of the CP protocol layer. +- ii) For LTE, SMS over SGs enhancements that give greater flexibility in the deployment of the MSC functionality. +- iii) Extension of ii) to support stateless SMS-IWF. +- iv) Evolution of the signalling interfaces between MME and HSS/SMSC. +- v) For LTE, use of the pre-established NAS security context to transfer the SMS PDUs as NAS signalling without establishment of all the radio bearers or RRC security context. + +vi) For delivery of Device Trigger information to UE over E-UTRAN using NAS signalling, an additional optimisation related to bullet point v) above is described. + +Each component can be deployed independently. The capability to deploy these sub-features independently is anticipated to ease rollout and deployment issues, especially for roaming situations, and, where the MTC-subscriber needs coverage from more than one RAT. + +Editor's note: Need to address how this solution can support subscription and operator policy on data size. + +Editor's note: The small data upper limit needs to be specified for this solution. + +Editor's note: The frequency of small data transmissions that can be supported with this solution needs to be described. + +Editor's note: Whether or not mobility management needs to be supported during small data transmission needs to be specified (or the solution needs to provide retransmissions). + +## 6.52.2.2 Removal of CP protocol layer + +The 'real SMS' is sent in an RP-DATA message. Successful delivery of the SM to the SMSC (for Mobile Originated SMS) and to the mobile (for Mobile Terminated SMS) leads to the transmission of an RP-ACK message. + +On all of the radio and network interfaces (LTE, 3G, 2G-PS, 2G-CS), a relatively reliable concatenation of layer 2 data links are used to transport the RP messages. Following successful radio transfer at layer 2, message loss is rare and can be covered by application layer retransmission at SMSC or mobile. + +However, the RP messages are always encapsulated in CP-DATA messages and each CP-DATA message generates a CP-ACK message. The CP layer messages appear unnecessary, and, e.g. if a CP-ACK is lost, the CP layer can cause added delay. The CP layer also causes radio interface inefficiency. + +Given the local nature of the CP protocols (they run between 'edge CN node' and the mobile) they could be removed independently on any RAT/domain. + +The use/no-use of the CP protocol layer can be negotiated between the mobile and the 'edge CN node' at Attach/TAU/RAU/LAU and is then applicable within that TA, RA or LA. + +NOTE 1: The "removal" of the CP protocol layer does not necessarily imply removal from the protocol stack. Instead, the "removal" can be effectively achieved by enhancing the state machines in the UE and in the network (refer to the normative Annex B: "SDL description of the CM layer" in TS 24.011), so that the CP-ACK is rarely sent. Moreover, for MO SMS the CP retransmission timer in the UE (TC1M) needs to be properly configured to account for the round-trip delay of the RP-PDU (from the network edge to the SMS-SC and backwards). + +Removal of the CP layer would save one or two messages on the radio interface for MO SMS and MT SMS. + +NOTE 2: For MO SMS the UE may need to indicate to the network that it has no more messages for sending, so that the network's signalling connection release procedure does not overtake the 'low priority' RP-ACK. In current specifications the network releases the signalling connection upon receipt of CP-ACK. + +## 6.52.2.3 Flexible deployment of MSC functionality for SMS over SGs + +In LTE, SMS is currently supported by both "SMS using IMS" and "SMS over SGs". In some deployment scenarios, the use of "SMS over IMS" can be regarded as rather heavyweight for low end M2M applications. + +![Figure 6.52.2.3-1: CS Fallback architecture diagram. A UE is connected to UTRAN (via Uu), GERAN (via Um), and E-UTRAN (via LTE-Uu). UTRAN is connected to SGSN (via Iu-ps) and MSC Server (via Iu-cs). GERAN is connected to SGSN (via Gb) and MSC Server (via A). E-UTRAN is connected to MME (via S1-MME). MME is connected to SGSN (via S3) and MSC Server (via SGs).](8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg) + +Figure 6.52.2.3-1: CS Fallback architecture diagram. A UE is connected to UTRAN (via Uu), GERAN (via Um), and E-UTRAN (via LTE-Uu). UTRAN is connected to SGSN (via Iu-ps) and MSC Server (via Iu-cs). GERAN is connected to SGSN (via Gb) and MSC Server (via A). E-UTRAN is connected to MME (via S1-MME). MME is connected to SGSN (via S3) and MSC Server (via SGs). + +**Figure 6.52.2.3-1: CS Fallback architecture (from TS 23.272 [23])** + +Figure 6.52.2.3-1 shows the current CS-Fallback architecture, the MSC/VLR function can become a standalone SMSoSGs function. The resulting architecture is shown below in Figure 6.52.2.3-2. + +![Figure 6.52.2.3-2: New architecture of MME and SMSoSGs Function diagram. Three UEs (UE 1, UE 2, UE 3) are connected to eNodeBs, which are connected to MMEs (MME A, MME B, MME C) via S1-MME. Each MME is connected to a central SMSoSGs Function via SGs. The SMSoSGs Function is connected to an HSS via S6a and D interfaces, and to an SMS service layer (containing SMS-GMSC, SMS-IWMSC, SM-SC, or SMS Router) via E and C interfaces.](e6cd61d926d5742b7c149a8377b3f55b_img.jpg) + +Figure 6.52.2.3-2: New architecture of MME and SMSoSGs Function diagram. Three UEs (UE 1, UE 2, UE 3) are connected to eNodeBs, which are connected to MMEs (MME A, MME B, MME C) via S1-MME. Each MME is connected to a central SMSoSGs Function via SGs. The SMSoSGs Function is connected to an HSS via S6a and D interfaces, and to an SMS service layer (containing SMS-GMSC, SMS-IWMSC, SM-SC, or SMS Router) via E and C interfaces. + +**Figure 6.52.2.3-2: New architecture of MME and SMSoSGs Function, showing that multiple MMEs can be connected to one SMSoSGs Function** + +![Figure 6.52.2.3-3: MME and integrated SGs SMSoSGs Function diagram. A single UE is connected to an eNodeB, which is connected to an MME via S1-MME. The MME has an integrated SMSoSGs Function. This function is connected to an HSS via S6a and D interfaces, and to an SMS service layer (containing SMS-GMSC, SMS-IWMSC, SM-SC, or SMS Router) via E and C interfaces.](901343511e3efc3f994eaffe6fc393ca_img.jpg) + +Figure 6.52.2.3-3: MME and integrated SGs SMSoSGs Function diagram. A single UE is connected to an eNodeB, which is connected to an MME via S1-MME. The MME has an integrated SMSoSGs Function. This function is connected to an HSS via S6a and D interfaces, and to an SMS service layer (containing SMS-GMSC, SMS-IWMSC, SM-SC, or SMS Router) via E and C interfaces. + +**Figure 6.52.2.3-3: MME and integrated SGs SMSoSGs Function** + +NOTE: The architectures shown in Figures 6.52.2.3-2 and 6.52.2.3-3 could also be used by CSFB devices, but, Fall Back will entail an MSC change. + +These architectures permit an LTE operator to use SMS over SGs without substantial investments in CS domain infrastructure. Upgrades to the HSS or SMSC are not required. + +### 6.52.2.4 Stateless SMS IWF + +The handling of SMS in CS Fall Back today requires the MSC/VLR to have 'CS domain' Mobility Management functionality and to maintain long term storage of the MSISDN that corresponds to the mobile's IMSI. + +SA WG2 document, S2-095320 described how, by the addition of the MSISDN to certain SGs interface messages, the MSC/VLR function can become a simple interworking function that does not require long term storage of the IMSI-MSISDN relationship. The resulting architecture is shown below in Figure 6.52.2.4-1. + +![Figure 6.52.2.4-1: New architecture of MME and SMS IWF, showing that multiple MMEs can be connected to one SMS IWF. The diagram shows three UEs (UE 1, UE 2, UE 3) connected to eNodeBs, which are connected to MMEs (MME A, MME B, MME C) via S1-MME interfaces. Each MME is connected to a central SMS IWF via SGs interfaces. The SMS IWF is connected to an HSS via a D interface and to an SMS service layer (SMS-GMSC, SMS-IWMSC, SM-SC or SMS Router) via an E interface. The HSS is also connected to the SMS service layer via a C interface. The HSS is connected to the eNodeBs via an S6a interface.](ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg) + +Figure 6.52.2.4-1: New architecture of MME and SMS IWF, showing that multiple MMEs can be connected to one SMS IWF. The diagram shows three UEs (UE 1, UE 2, UE 3) connected to eNodeBs, which are connected to MMEs (MME A, MME B, MME C) via S1-MME interfaces. Each MME is connected to a central SMS IWF via SGs interfaces. The SMS IWF is connected to an HSS via a D interface and to an SMS service layer (SMS-GMSC, SMS-IWMSC, SM-SC or SMS Router) via an E interface. The HSS is also connected to the SMS service layer via a C interface. The HSS is connected to the eNodeBs via an S6a interface. + +**Figure 6.52.2.4-1: New architecture of MME and SMS IWF, showing that multiple MMEs can be connected to one SMS IWF** + +When using the architecture in Figure 6.52.2.4-1, the 'source address' of the SMS IWF (used in Registration messages to the HSS) depends upon the MME in which the UE is registered, e.g. as shown in Table 6.52.2.4-1 below. The HSS stores these different SS7 Global Title addresses as if they were the "real MSC/VLR address" and gives them to the SMSC in the SendRoutingInformation for Short Message Response. The SMSC then uses that SS7 GT to send the Short Message to the SMS IWF. The SMS IWF uses the addressed SS7 GT to identify the correct MME. + +**Table 6.52.2.4-1: Mapping table of MME name to SS7 GT stored in SMS IWF** + +| MME | MME name/IP address | Assigned SS7 GT | +|-----|-----------------------------|-----------------| +| A | 192.168.1.4 | 447700900111 | +| B | aaa-1.internal.operator.com | 447700900112 | +| C | 10.34.78.67 | 447700900113 | + +A further reduction in the number of nodes can be achieved if the SMS IWF is co-located with the MME (see Figure 6.52.2.4-2 below). This would mean that the MME would have to support the MAP D and E interfaces, however, as many vendors offer combined MME/SGSN platforms, this is not necessarily a huge problem. + +![Figure 6.52.2.4-2: MME and integrated SGs SMS IWF. The diagram shows a single UE connected to an eNodeB, which is connected to an MME via an S1-MME interface. The MME is connected to an HSS via an S6a interface and has an integrated SGs IWF. The SGs IWF is connected to the HSS via a D interface and to an SMS service layer (SMS-GMSC, SMS-IWMSC, SM-SC or SMS Router) via an E interface. The HSS is also connected to the SMS service layer via a C interface.](7528e790beec9b44a780eed57fb933f1_img.jpg) + +Figure 6.52.2.4-2: MME and integrated SGs SMS IWF. The diagram shows a single UE connected to an eNodeB, which is connected to an MME via an S1-MME interface. The MME is connected to an HSS via an S6a interface and has an integrated SGs IWF. The SGs IWF is connected to the HSS via a D interface and to an SMS service layer (SMS-GMSC, SMS-IWMSC, SM-SC or SMS Router) via an E interface. The HSS is also connected to the SMS service layer via a C interface. + +**Figure 6.52.2.4-2: MME and integrated SGs SMS IWF** + +NOTE: The architectures shown in Figures 6.52.2.4-1 and 6.52.2.4-2 can be used by CSFB devices, but, Fall Back will entail an MSC change. + +These architectures permit an LTE operator to use SMS over SGs without substantial investments in CS domain infrastructure. Upgrades to the HSS or SMSC are not required. + +### 6.52.2.5 Evolution of the signalling interfaces between MME and HSS/SMSC + +In the architectures shown in clauses 6.52.2.3 and 6.52.2.4, movement of the mobile inter a new MME area results in the HSS receiving mobility related signalling on both S6a and D interfaces. In the case of successful uptake of LTE M2M using SMS for small data transmission, this 'double update' may represent a significant load/inefficiency. + +For the case of an "SMS over SGs Function/IWF" being integrated in the MME, to prepare for such a situation, it would be logical to consider extending the S6a functionality to incorporate the CS domain update (for SMS only). This can be done on a "per MME-HSS pair" basis. + +Similarly, if load or cost reasons were to warrant it, the "MME/SMS over SGs Function/IWF" to SMSC interface could be upgraded from its current MAP protocol form to an appropriate IETF based interface. Again this can be done on a "per MME-SMSC pair" basis. + +### 6.52.2.6 Use of pre-established NAS security context to transfer the SMS PDUs as NAS signalling without establishing RRC security + +In LTE, the current SMS over SGs procedures require the use of the Service Request procedure. This entails the download of the RRC security context to the eNB and the establishment of the radio bearers. If all that is intended is the transfer of one SMS-like data packet, these procedures lead to a substantial increase in radio resource utilisation. + +In 2G GPRS, these procedures are avoided as 2G-PS is relatively connectionless, and, the user plane and signalling messages are encrypted at the SGSN, not in the RAN. + +The MME has encryption functionality for the NAS signalling and thus the transfer of the RRC security context to the eNB does not seem strictly necessary. Note that when performing a TAU from Idle mode, the RRC security context and radio bearers are not established. + +The following bullets describe more optimised radio interface message sequences for SMS over SGs. They are most suited for (and are described here for) the case when the CP layer has been removed, but, they can still function if the CP layer is retained. + +#### MO LTE procedure for SMS over SGs: + +- a) The mobile performs a combined Attach/TAU, typically, for "SMS-only" and returns to RRC-idle. + +During the Attach and TAU procedures, the UE and MME exchange information on their (and in the case of a real, separate, MSC, the MSC's) ability to support optimised SMS procedures. + +- b) The UE's NAS requests the UE's AS to establish an RRC connection "for a Tracking Area Update" (sending the S-TMSI in the RRC Connection Request). However, the NAS PDU is a new form of initial layer 3 message that includes the RP-DATA in an encrypted IE. This NAS PDU is sent in the NAS container in the RRC Connection Setup Complete message. The unencrypted part of this new initial layer 3 message in the NAS PDU carries the "KSI and sequence number" IE and the MME uses this, and the S-TMSI, to identify the security context to decrypt the RP-DATA. + +NOTE 1: During the Attach procedure, the RRC Connection Setup Complete message typically carries a NAS PDU of around 80 bytes (for an SRVCC mobile), so, the radio's Layer 1 and 2 mechanisms are probably not harmed by an RP-DATA payload of up to 160 bytes. + +The size of this NAS PDU means that it is worth setting the RRC establishment cause to "mo-Signalling" rather than "mo-Data". + +NOTE 2: the "mo-Signalling" cause value, potentially coupled with the receipt of the S-TMSI in the RRC Connection Request, can be used by the eNB to detect that a short lived signalling procedure is in progress. Hence it is unlikely that the MME will download the security context to the eNB. Without the security context, handover cannot be performed. Thus radio resources can be saved if the eNB does not configure the UE to perform measurement reporting. + +If the UE's application knows that it needs to send multiple or concatenated SMSs, then the UE sets a (new) flag in the NAS PDU to inform the MME of this fact. The UE's application could also indicate the number of SMSs that need to be sent. + +- c) The eNB forwards the encrypted RP DATA to the MME in the S1AP Initial UE message. +- d) The MME decrypts the RP-DATA, and the MME (or SGs SMS IWF) adds the UE's identity information (e.g. MSISDN received from the HSS in step a) and forwards the Short Message to the SMSC. +- e) The SMSC stores the SM and returns an RP-ACK to the MME. +- f) The MME forwards the RP-ACK in an encrypted NAS PDU to the eNB in an S1 Downlink NAS Transport message. + +An additional, optional, IE is added to the S1 Downlink NAS Transport message that allows the MME to request the eNB to release the RRC connection. (The MME does not use this indication if the UE indicated that multiple SMSs needed to be transferred in step b). + +NOTE 3: this situation is similar to the completion of a (periodic) TAU. i.e. the MME has not sent the Initial UE Context message to the eNB and so the eNB cannot perform any commands on the UE that require RRC level security (in particular clause 5.3.1.1 of TS 36.331 specifies that Handover cannot be performed in this state). + +- g) The eNB sends the RP-ACK to the UE and releases the RRC Connection. The small size of the RP-ACK means that it is possible for the eNB to include it as a NAS PDU within the RRC Connection Release message itself. + +Facets of the above procedure: + +- This MO SMS transfer only uses 4 RRC messages (plus the Hybrid ARQ frames and the 2 messages that precede the RRC Connection Request). +- The CP Layer messages are not used. + +## MT SMS + +This uses similar concepts to MO SMS, but it requires 2 more RRC messages. + +- a) The MME and UE have negotiated (at Attach/TAU) that the CP layer need not be used. +- b) Paging leads to the establishment of the RRC Connection. The addition of a "SMS flag" to the radio interface (and S1 interface) paging messages allows the UE to change the RRC establishment cause from "mt-access" to "mo-signalling" (or to a new cause value of "mt-signalling"). In turn, this RRC establishment cause allows the eNB to optimise its resource allocation and to not configure the UE for measurement reporting). + +The Service Request sent as the paging response by the UE carries the "KSI and sequence number" IE. The MME uses this, and the S-TMSI, to encrypt the RP-DATA sent in step c below. + +- c) The MME then sends the RP-DATA in an encrypted IE in a NAS PDU in an S1 Downlink NAS Transport message and the eNB sends the NAS PDU onto the UE. +- d) The UE sends the RP-ACK in an encrypted IE in a NAS PDU in an UL Information Transfer message and the eNB forwards the NAS PDU to the MME. + +The UE adds a new optional IE to the UL Information Transfer to request the eNB to release the RRC connection. + +- e) The eNB releases the RRC Connection. + +### 6.52.2.7 Transfer of Device Trigger as MT SMS or NAS payload without U-plane bearer establishment in E-UTRAN + +For the transmission of the Device Trigger contained in the MT SMS the establishment of U-plane bearers is not necessarily needed. Depending on the triggered MTC application, the UE used for MTC may either not require the establishment of U-plane bearers, or not the immediate establishment of U-plane bearers. + +NOTE 1: In the following exemplary cases the establishment of the U-plane bearers is not needed: 1) the UE used for MTC may reply to the MTC server using MO SMS; 2) the UE used for MTC may first need some time to gather information and then the IP-based communication to the MTC server is initiated (e.g. 1 minute later). + +The solution proposed in this clause is an alternative to the one proposed in clause 6.52.2.6 above. The main difference results from the UE behaviour after receiving the Device Trigger message. Namely, the eNB/MME may not immediately initiate the NAS/RRC connection release after the delivery of the Device Trigger (e.g. MT SMS) to the UE. During the Device Trigger processing in the UE, the UE determines if uplink data shall be immediately sent to the MTC server. Further, the uplink data may result in either: + +- 1) establishment/activation of EPS bearers for IP/based MO communication or +- 2) the transmission of MO SMS to the MTC Server. + +If the UE needs to transmit an MO SMS, the UE reuses the existing NAS MM connection to the MME. If the UE needs to set up the U-plane bearers, the UE sends a corresponding EPS Bearer Activation message to the MME. + +If the UE determines that the uplink data will be transmitted later (i.e. MO communication will be established later), the UE indicates to the MME that the NAS signalling connection is not anymore needed. The latter helps the network to shorten the radio resource occupation. + +As an alternative to solution from clause 6.52.2.6, the MME may establish the Access Stratum (AS) security for the Signalling Radio Bearers. For this reason, the MME establishes only the UE AS-security context at the eNB for the RRC connection (i.e. the MME doesn't include the E-RAB context in the S1-AP Initial Context Setup request message to the eNB). The main reasons for the establishment of the AS-security are: + +- 1) The support of mobility; and +- 2) The ability of the UE to reliably activate the U-plane bearers if needed. + +NOTE 2: Some further alternative signalling and/or indications during the Paging and Service Request procedure are possible compared to the MT SMS solution from clause 6.52.2.6. If the UE has no data to send via the U-plane when responding to the Paging message with "SMS flag", then the UE can send a new or an existing initial NAS message, e.g. TAU request without an active flag, to the MME. This message only triggers the establishment of the NAS signalling connection. After the reception of the Device Trigger, in the reply from the UE to the MME (e.g. SMS Relay protocol PDUs, RPDUs), the UE indicates further actions to the MME such as keeping or releasing the NAS signalling connection. This helps the network to shorten the radio resource occupation. + +**Editor's note:** The evaluation of the benefits and drawbacks has to be done when the evaluation for the whole clause 6.52 will be provided. + +## 6.52.3 Impacts on existing nodes or functionality + +- a) Extensive use of SMS for transmission of small data puts additional load on control plane nodes (e.g., MME, SGSN, MSC Server, SMS-GMSC, SMS-IWMSC, SMS-SC) in order to transport user data. + +## 6.52.4 Evaluation + +# 6.53 Solution - Small Data Transfer (E-UTRAN): Use of pre-established NAS security context to transfer the IP packet as NAS signalling without establishing RRC security + +## 6.53.1 Problem Solved / Gains Provided + +See clauses 5.4 "Key Issue – Small Data Transfer". + +## 6.53.2 General + +NOTE: This is a development of the concept in clause 6.52.2.6 "Use of pre-established NAS security context to transfer the SMS PDUs as NAS signalling without establishing RRC security". + +In LTE, the current data transfer procedures require the use of the Service Request procedure. This entails the download of the RRC security context to the eNB and the establishment of the radio bearers. If all that is intended is the transfer + +of one, possibly small, IP data packet, and perhaps its response, these procedures lead to a substantial increase in radio resource utilisation. + +In 2G GPRS, these procedures are avoided as 2G-PS is relatively connectionless, and, the user plane and signalling messages are encrypted at the SGSN, not in the RAN. + +If the MME is using encryption functionality for the NAS signalling the transfer of the RRC security context to the eNB does not seem strictly necessary. Note that when performing a TAU from Idle mode, the RRC security context and radio bearers are not established. + +Figure 6.53-1, below, illustrates the architecture for this 'small data' feature. + +![Figure 6.53-1: E2E data paths for small data transmission. The diagram shows a sequence of components: UE/MTC Device, MME, S-GW, PDN-GW, and PDN (containing MTC Server). Arrows indicate data flow: S1-MME(NAS(encrypted Small data)) from UE to MME; S11 (Small data) from MME to S-GW; S5/S8 (Small data) from S-GW to PDN-GW; and IP traffic(Small data) from PDN-GW to MTC Server. The PDN is highlighted with a yellow oval.](78a8921806daa748fe4258601b530f39_img.jpg) + +``` + +graph LR + UE[UE/MTC Device] -- "S1-MME(NAS(encrypted Small data))" --> MME + MME -- "S11 (Small data)" --> SGW[S-GW] + SGW -- "S5/S8 (Small data)" --> PGW[PDN-GW] + PGW -- "IP traffic(Small data)" --> MTC[PDN: MTC Server] + style PDN fill:#ffff00,stroke:none + +``` + +Figure 6.53-1: E2E data paths for small data transmission. The diagram shows a sequence of components: UE/MTC Device, MME, S-GW, PDN-GW, and PDN (containing MTC Server). Arrows indicate data flow: S1-MME(NAS(encrypted Small data)) from UE to MME; S11 (Small data) from MME to S-GW; S5/S8 (Small data) from S-GW to PDN-GW; and IP traffic(Small data) from PDN-GW to MTC Server. The PDN is highlighted with a yellow oval. + +**Figure 6.53-1: E2E data paths for small data transmission** + +The following bullets describe more optimised radio interface message sequences for the transfer of one IP packet (and its response). + +#### **LTE procedure for single MO IP packet (and response):** + +- The mobile performs Attach activating a PDN connection or TAU (with an already active PDN a connection). + +During the Attach and TAU procedures, the UE and MME exchange information on their ability to support the "small data" procedures. The MME also obtains information (e.g. from the HSS) about the likelihood that this UE will predominately use (or not use) the small data transfer feature. + +As a result, the MME might perform UTRAN-MOCN style MME redirection procedures to cause the UE to register on an MME optimised for MTC Small Data Transfers. + +The finally selected MME instructs the UE to use encryption of NAS signalling messages. + +The finally selected MME performs S-GW and P-GW selection taking into account the UE's likelihood to perform small data transfers. + +The UE returns to RRC Idle mode. + +- When the UE's application knows that it needs to send just one IP packet (and that this uplink IP packet should not trigger multiple downlink IP packets), the UE's application requests NAS to request the UE's AS to establish an RRC connection "for a Tracking Area Update" (sending the S-TMSI in the RRC Connection Request). However, the NAS PDU is a new form of initial layer 3 message that includes the IP packet and its EPS Bearer ID in an encrypted IE. This NAS PDU is sent in the NAS container in the RRC Connection Setup Complete message. The unencrypted part of this new initial layer 3 message in the NAS PDU carries the "KSI and sequence number" IE and the MME uses this, and the S-TMSI, to identify the security context to decrypt the IP packet and EPS Bearer ID. + +NOTE 1: RRC has not placed any significant size constraint on the NAS PDU payload. Hence RRC is believed to be able to support a 1500 byte IP packet within the NAS PDU. Any loss of radio efficiency needs to be determined, but, it is believed that power control features would work correctly, and, that low end devices would not deploy advanced/multi antenna features that need the download of the UE Radio Capabilities IE from the MME to the eNB. + +The size of this NAS PDU means that it is worth setting the RRC establishment cause to "mo-Signalling" rather than "mo-Data". + +NOTE 2: The "mo-Signalling" cause value, potentially coupled with the receipt of the S-TMSI in the RRC Connection Request, can be used by the eNB to detect that a short lived signalling procedure is in progress. Hence it is unlikely that the MME will download the security context to the eNB. Without the security context, handover cannot be performed. Thus radio resources can be saved if the eNB does not configure the UE to perform measurement reporting. + +If the UE's application knows that it needs to transfer more than one uplink and one downlink IP packet, then it should (shall) use the normal service request procedure. + +NOTE 3: It could be considered to use this procedure to transfer more than one (pair) of IP packets. This may be possible (e.g. it is not dissimilar to TAU procedures where several NAS messages can be exchanged without downloading the UE Radio Capabilities to the eNB), however this would have a larger RAN performance impact. + +NOTE 4: How to ensure that the application correctly uses the Service Request procedure and does not abuse this 'Small Data' NAS procedure is an open issue. However the MME's ability to release the connection provides a control point. An additional possibility is for the NAS signalling in the Attach/TAU procedure to carry a TFT, or some other 'rule', to the UE which the UE uses to restrict the traffic that can use the 'Small Data' procedure. + +- c) The eNB forwards the encrypted IP packet to the MME in the S1AP Initial UE message. +- d) The MME decrypts the IP packet. + +Using the EPS Bearer ID, the MME retrieves the IP address and TEID of that bearer, forms the GTP-U packet and sends it to the S-GW. + +- e) The S-GW sends the packet to the P-GW and the P-GW forwards the IP packet on to the SGi interface. +- f) The MME uses knowledge of the subscriber to determine whether to proceed with the full UE triggered Service Request procedure, or, to immediately release the RRC connection, or to wait for some time (e.g. to see if a downlink IP packet causes the S-GW to send a Downlink Data notification to the MME). +- g) (If the MME has not proceeded with the full UE triggered Service Request procedure,) when a (response) IP packet arrives in the S-GW, the S-GW appends the IP packet to the Downlink Data Notification and sends it to the MME. The S-GW also buffers the IP packet. +- h) If the MME has retained the RRC connection, then the MME can append the EPS Bearer ID to the downlink IP packet, encrypt them and send them in a downlink NAS PDU to the UE. Knowledge of the subscriber type would permit the MME to request the eNB to release the RRC connection in conjunction with the eNB's delivery of the NAS PDU/IP response packet. +- i) The Downlink Data Notification Ack sent by the MME to the SGW is extended to inform the SGW that the packet has been delivered (or, that the normal Network Initiated Service Request procedure has been triggered). +- j) If the S-GW has not received a Downlink Data Notification Ack indicating that the normal Network Initiated Service Request procedure has been triggered, when a second downlink IP packet arrives in the S-GW, the S-GW sends a new Downlink Data Notification with that IP packet appended to the S-GW. If the S-GW receives multiple IP packets, the S-GW can use the Downlink Data Notification to request the MME to perform the normal Network Initiated Service Request procedure. + +Facets of the above procedure: + +- This IP packet pair transfer only uses 4 RRC messages (plus the Hybrid ARQ frames and the 2 messages that precede the RRC Connection Request). + +#### LTE procedure for single MT IP packet delivery + +This uses similar concepts to the MO case described above. + +- a) The MME and UE have (at Attach/TAU) performed similar negotiations to those for the MO case, NAS encryption is activated and a PDN connection has been activated. +- b) when an IP packet arrives in the S-GW, the S-GW buffers the IP packet, appends it to the Downlink Data Notification and sends it to the MME. The S-GW monitors whether subsequent packets have arrived for the delivery to the UE and whether the total size of these packets is greater than the value configured by the operator's policy or subscription. If this is the case the S-GW sends the Downlink Data Notification to request the establishment of the S1 bearer(s). +- c) The MME pages. The addition of a "Small data flag" to the radio interface (and S1 interface) paging messages allows the UE to change the RRC establishment cause from "mt-access" to "mo-signalling" (or to a new cause + +value of "mt-signalling"). In turn, this RRC establishment cause allows the eNB to optimise its resource allocation and to not configure the UE for measurement reporting). + +The MME uses knowledge of the subscriber to decide whether to include the "Small Data Flag", and, whether to not fully proceed with the subsequent Service Request procedure. + +The Service Request sent as the paging response by the UE carries the "KSI and sequence number" IE. The MME uses this, and the S-TMSI, to encrypt the IP packet sent in step d below. + +- d) The MME then sends the IP packet and EPS Bearer ID in an encrypted IE in a NAS PDU in an S1 Downlink NAS Transport message and the eNB sends the NAS PDU onto the UE. +- e) Typically the UE sends an IP packet as an acknowledgement. This IP packet, along with the EPS Bearer ID, is sent in an encrypted IE in a NAS PDU in an UL Information Transfer message. The eNB forwards the NAS PDU to the MME. The MME decrypts the IE, adds the GTP header and forwards it to the S-GW. + +The UE adds a new optional IE to the UL Information Transfer to request the eNB to release the RRC connection. + +- f) The eNB releases the RRC Connection. + +### 6.53.3 Impacts on existing nodes or functionality + +### 6.53.4 Evaluation + +Typical IP flow scenarios (e.g. when TCP transport is used) require multiple round trips. + +## 6.54 Solution - NAT Traversal using controlled NAT + +### 6.54.1 Problem Solved / Gains Provided + +See clause 5.3 "Key Issue - IPv4 Addressing" and clause 5.8 "Key Issue - MTC Device Trigger". + +### 6.54.2 General + +This alternative is intended to give a NAT traversal option that could be implemented without requiring normative impacts on existing 3GPP entities. This is one option of how this could be implemented, and other variants exist today on the market. + +This alternative is similar in nature to clause 6.18 "Solution - MT Communication with NATTT", but with the difference that there is no need to setup a tunnel between the NAT and MTC Server (or MTC application). This solution addresses the scenario where the MTC Server/Application impact needs to be minimized, but where similar principles for DNS based lookup is considered beneficial. In general, it is assumed that the UE applications are using a few ports and that these ports are either known or possible to learn from application layer signalling. When the UE has received the (private) IP address from the PGW, the PLMN NAT at Gi is configured to map the configured port values to public IP ports. The values of the ports at the public side of the NAT are automatically configured in the DNS. + +![Figure 6.54-1: Overall outline of NAT solution. The diagram shows a UE connected to a P-GW / S-GW. The P-GW / S-GW is connected to a NAT node. The NAT node is connected to an MTC Server / Application. Above the NAT node is an AAA / NAT control node, which is connected to a DNS node. Dashed lines indicate control plane connections: UE to P-GW / S-GW, P-GW / S-GW to AAA / NAT control, AAA / NAT control to DNS, and a dashed line from the DNS node to the MTC Server / Application. Solid lines indicate data plane connections: UE to P-GW / S-GW, P-GW / S-GW to NAT, and NAT to MTC Server / Application.](9ba75f891de20483c291538e38701d96_img.jpg) + +``` + +graph LR + UE[UE] --- P[PGW / SGW] + P --- NAT[NAT] + NAT --- MTC[MTC Server / Application] + P -.-> AAA[AAA / NAT control] + AAA -.-> DNS[DNS] + DNS -.-> MTC + +``` + +Figure 6.54-1: Overall outline of NAT solution. The diagram shows a UE connected to a P-GW / S-GW. The P-GW / S-GW is connected to a NAT node. The NAT node is connected to an MTC Server / Application. Above the NAT node is an AAA / NAT control node, which is connected to a DNS node. Dashed lines indicate control plane connections: UE to P-GW / S-GW, P-GW / S-GW to AAA / NAT control, AAA / NAT control to DNS, and a dashed line from the DNS node to the MTC Server / Application. Solid lines indicate data plane connections: UE to P-GW / S-GW, P-GW / S-GW to NAT, and NAT to MTC Server / Application. + +**Figure 6.54-1: Overall outline of NAT solution** + +NOTE: The AAA/NAT control function is considered out of 3GPP standardization scope. + +In this alternative, the following will take place: + +- The UE is attached to the network, and the AAA/NAT Control function is updated with the user context, including IP address. +- Based on configuration or user profile data, the NAT is setup with a number of bindings for the communication between the UE and MTC Server. This could be done in similar fashion as for the Micro port forwarding in clause 6.19. The AAA/NAT Control function will be the responsible to perform this. It is expected, that only a limited set of ports may be required to be kept in the NAT, for a specific standard set of services. +- The AAA / NAT Control function updates the DNS with IP address for the UE, including the ports to which it can be reached for the specific advertised services. +- The MTC Server will be able at anytime perform a DNS query according to normal DNS lookup procedures, and retrieve correct IP address (and port) for the device (and service on the device) it wish to contact. + +### 6.54.3 Impacts on existing nodes or functionality + +Under the assumption that M2M dedicated APNs are used with Radius forwarding performed by PGW, existing functions would not be impacted. + +### 6.54.4 Evaluation + +Benefits: + +- No impact on existing Core Network nodes and UE; +- The solution does not rely on alternative communication channels (e.g. SMS) for delivery of a "push" stimulus; +- Works also for device-to-device communication; +- No impact on MTC Server/MTC-IWF. + +Disadvantages: + +- Using DDNS for exposing the IP address may cause problem due to the applications and SP ignoring the TTL of the DNS bindings. +- Not efficient for short lived PDN connections, unless same IP address re-used for the UE. +- For local breakout, a large number of trusted interfaces would be required to update the DNS. +- The solution is limited to one (or pre-defined number) of port number(s). +- The solution is limited to the number of port bindings per IP address. + +## 6.55 Solution - NAT Traversal using Non-Managed-NAT + +### 6.55.1 Problem Solved/ Gains Provided + +See clause 5.3 "Key Issue - IP Addressing". + +### 6.55.2 General + +In order to support communications between the MTC Server and the UE used for MTC that are located in different IPv4 address spaces, Network Address Translator (NAT) is deployed at the address space boundary. Such NAT could be a managed-NAT or a non-managed-NAT. + +The solution described in clause 6.19: 'MT Communications with Micro Port Forwarding' is an example of the managed-NAT solution shown. The proposal in this clause provides the architectural framework for a non-managed-NAT solution for MTC. + +NOTE 1: NAT Traversal proposal illustrated here applies to the Indirect and Hybrid communication models in clause 4.2. The solution assumes that UE used for MTC initiates communications for Direct communication model. NAT traversal is not an issue if the UE used for MTC initiates communications. + +NOTE 2: Market requirements and Use Case for non-Managed NATs is FFS. + +### 6.55.3 Non-Managed-NAT for MTC + +Architectural overview of non-managed-NAT traversal solution for 3GPP MTC is illustrated in Figure 6.55.3-1. Bindings in non-managed-NATs are not controlled by the network. Bindings in the non-managed-NAT are created when the MTC Server wants to initiate communications with the UE used for MTC. + +![Figure 6.55.3-1: Non-Managed NAT with Address Determination Server. The diagram shows the architectural components and data flows for non-managed NAT traversal. On the left, a UE is connected to a GGSN/P-GW. The GGSN/P-GW is connected to a NAT User Plane Communications block via an MTCyy interface. The NAT block is connected to an Address Determination Server via an MTCsp interface. The NAT block is also connected to an MTC-IWF block via a Gi/SGi interface. The MTC-IWF block is connected to an MTC Server via an MTCsp interface. The UE is connected to the GGSN/P-GW via a dashed line. The GGSN/P-GW is connected to the NAT block via a dashed line. The NAT block is connected to the Address Determination Server via a dashed line. The NAT block is connected to the MTC-IWF block via a dashed line. The MTC-IWF block is connected to the MTC Server via a dashed line.](e9c070631848606db3524757b0121c06_img.jpg) + +``` + +graph LR + UE[UE] --- GGSN["GGSN / P-GW"] + GGSN -.-> NAT["NAT User Plane Communications"] + NAT -.-> ADS["Address Determination Server"] + NAT -.-> MTC_IWF["MTC-IWF"] + MTC_IWF -.-> MTC_Server["MTC Server"] + GGSN -.-> MTC_IWF + MTC_IWF -.-> MTC_Server + +``` + +Figure 6.55.3-1: Non-Managed NAT with Address Determination Server. The diagram shows the architectural components and data flows for non-managed NAT traversal. On the left, a UE is connected to a GGSN/P-GW. The GGSN/P-GW is connected to a NAT User Plane Communications block via an MTCyy interface. The NAT block is connected to an Address Determination Server via an MTCsp interface. The NAT block is also connected to an MTC-IWF block via a Gi/SGi interface. The MTC-IWF block is connected to an MTC Server via an MTCsp interface. The UE is connected to the GGSN/P-GW via a dashed line. The GGSN/P-GW is connected to the NAT block via a dashed line. The NAT block is connected to the Address Determination Server via a dashed line. The NAT block is connected to the MTC-IWF block via a dashed line. The MTC-IWF block is connected to the MTC Server via a dashed line. + +**Figure 6.55.3-1: Non-Managed NAT with Address Determination Server** + +1. Once PDP/PDN connection is established for a UE used for MTC, the IP address is made available to the MTC-IWF. +2. When the MTC Server queries the MTC-IWF for UE's public IP address and port information (transport address), the MTC-IWF initiates Address Translation Request/Reply procedure with the GGSN/P-GW by passing the assigned IPv4 Address and Port information (based on the Application ID/Port information received in the trigger request from the MTC Server) to the GGSN/P-GW. The GGSN/P-GW emulates the UE by sending address determination packets through the NAT to an Address Determination Server over the MTCyy interface. The Address Determination Server is used to discover the public side of the transport address assigned to the UE. +3. The UE emulation IP packets include the address assigned to the UE and the expected port to be used. Such IP packets create bindings for the UE at the NAT. The UE emulation IP packets conform to the protocol defined in RFC 5389 (STUN) or RFC 5766 (TURN), depending on the type of the non-managed-NAT. +4. The STUN/TURN packets are intercepted by the Address Determination Server (STUN Server/Turn Relay) on the public side of the NAT. The Address Determination Server returns the public side of the IP Address and port information (transport address) for the UE to the GGSN/P-GW. The GGSN/P-GW intercepts the public AP Address/Port information, which is passed to the MTC Server via the MTC-IWF. +5. With such information about the public transport address for the UE, the MTC Server initiates user plane communications with the UE used from MTC. + +Depending on the nature of the non-managed-NATs (EIM or non-EIM type), the UP traffic flows directly from the public side of the NAT or via the Address Determination Server. + +- For EIM type NAT, UP traffic flows from the public side of the NAT over Gi/SGi interface. +- For non-EIM type NAT, UP traffic flows through the Address Determination Server (TURN Relay) over Gi/SGi interface. + +NAT bindings are kept alive by virtue of the flow of UP traffic. Additionally, some traffic monitoring capability at the GGSN/P-GW or the MTC-IWF can keep the bindings alive via appropriate keep alive STUN/TURN signalling. + +### 6.55.3 Impacts on existing nodes or functionality + +Impact on MTC-IWF: + +- Perform address translate procedure with the GGSN/P-GW. + +Impact on GGSN/P-GW: + +- STUN/TURN user agent function at the GGSN/P-GW. + +### 6.55.4 Evaluation + +Benefits: + +- Low impact on existing Core Network nodes. +- The solution is based on known IETF protocols. +- No complex configuration of 'forwarding-rules' at the MTC device and/or in the Core Network entities. +- No impact on subscription data. + +Drawbacks: + +- New Address Determination Server entity (STUN/TURN server) in the Core Network. +- STUN/TURN user agent function at the GGSN/P-GW. +- Public IP Address/Port pairs per public IP address limited to 65,536 ( $2^{16}$ ). +- Control plane communications needed between the GGSN/P-GW and the MTC-IWF. +- The solution assumes that UE used for MTC initiates communications for Direct communication model. + +## 6.56 Solution – SMS Transfer by SGSN for PS-only + +### 6.56.1 Problem Solved / Gains Provided + +"PS-Only Support". + +### 6.56.2 General + +For 2G/3G the SGSN already supports SMS transfer in PS domain, which doesn't rely on a CS registration of the UE. For GERAN/UTRAN, the PS only MTC Device only registers in PS domain. SMS transfer is via the SGSN without involving MSC/VLR. MM protocols and state machines may need to be updated to reject any potential CS registration attempt without affecting PS services or SMS provision via E-UTRAN. + +The MME registers a device that initiates combined Attach/TAU procedure with an SGSN instead of an MSC/VLR. Comparable to 6.52.2.3/4 or other solutions that deploy a reduced SGs-MSC-function just for SMS the approach of SGs with an SGSN provides only SMS services. CSFB devices may also be registered via SGs with the SGSN so that the MME is not modified and a CS fallback will fail. Or, the MME is enhanced to select an SGSN instead of an MSC/VLR based on the "SMS only" indication. In the latter case SMS for PS-only device is provided by the SGSN without any CS registration in the network. And CSFB devices are registered with an MSC for receiving CS services. + +For E-UTRAN-only devices and/or subscriptions this approach requires only PS subscription data. For multi-RAT capable devices and PS only subscriptions the MM protocols and state machines may need to be updated to reject any potential CS registration attempt without affecting 2G/3G PS services or SMS provision via E-UTRAN. If a CS subscription is required, e.g. to handle LTE capable multi-RAT UEs that cannot be prevented from registering with the MSC via 2G/3G, or if the PLMN doesn't configure SMS transfer via 2G/3G SGSNs, there will be no HSS update signalling caused by RAT-reselection in contrast to solutions that deploy an SGs-MSC-function. When CS registrations are prevented there is only the SGSN registered at HSS for MT SMS. Regardless of the RAT the UE camps on MT-SMS can always be delivered via SGSN. As there is no need for trying the MSC path for MT-SMS there are no unsuccessful delivery attempts, which may occur with an SGs-MSC-function when configuring PS-only for 2G/3G. + +As an alternative to cope with devices that require a 2G/3G CS registration the MSC may accept registration requests from the UE without creating an MM context or providing any services to the UE. This assumes that any required SMS services are provided by the SGSN or fail like other MSC provided services when initiated by the UE. + +![Diagram illustrating the use of SMS transfer function of SGSN for PS only Device. The diagram shows a UE connected to an eNodeB via LTE-Uu. The eNodeB is connected to an MME via S1-MME. The MME is connected to an SGSN via SGs. The SGSN is connected to an HSS via S6a and S6d. The HSS is connected to an SMS service layer (SMS-GMSC, SMS-IWMSC, SM-SC or SMS Router) via C. The SGSN is also connected to the SMS service layer via Gd.](d4e22bbe01024f0a4981d41da11252a9_img.jpg) + +``` + +graph LR + UE[UE] -- LTE-Uu --> eNodeB[eNodeB] + eNodeB -- S1-MME --> MME[MME] + MME -- SGs --> SGSN[SGSN] + MME -- S6a --> HSS((HSS)) + SGSN -- S6d --> HSS + HSS -- C --> SMS[SMS service layer +(SMS-GMSC, SMS-IWMSC, +SM-SC or SMS Router)] + SGSN -- Gd --> SMS + +``` + +Diagram illustrating the use of SMS transfer function of SGSN for PS only Device. The diagram shows a UE connected to an eNodeB via LTE-Uu. The eNodeB is connected to an MME via S1-MME. The MME is connected to an SGSN via SGs. The SGSN is connected to an HSS via S6a and S6d. The HSS is connected to an SMS service layer (SMS-GMSC, SMS-IWMSC, SM-SC or SMS Router) via C. The SGSN is also connected to the SMS service layer via Gd. + +Figure 6.56.2-1: Use of SMS transfer function of SGSN for PS only Device + +### 6.56.3 Impacts on existing nodes or functionality + +The SGSN provides SGs functionality for SMS towards MME, like an MSC. Optionally the MME can be enhanced to differentiate "SGs" to an SGSN (for SMS only) and SGs to an MSC (for CSFB). For rejecting CS registrations attempts without affecting any registrations for SMS over SGs the MM NAS signalling may need to be enhanced. + +Alternatively the MSC provides functionality to accept CS registrations without providing MSC services for UEs that receive SMS services from the SGSN. + +### 6.56.4 Evaluation + +In contrast to solutions with an SGs-MSC-function this approach does not require a CS subscription. With a CS/PS subscription, e.g. when the PLMN prefers transferring SMS by MSC for 2G/3G the multi-RAT UEs will not cause updates for the HSS registered MSC (function), which will happen during every RAT re-selection for alternatives that deploy a dedicated SGs-MSC-function. For PS-only only deployments (SMS transfer by the 2G/3G SGSN) there is only an SGSN registered at HSS for MT-SMS routing. + +## 6.57 Solution - Optimised SMS over SGs architecture + +### 6.57.1 Problem Solved / Gains Provided + +See TS 22.368 [2] clause 7.2.24 "Packet Switched (PS) only" and clause 5.8 "Key Issue - MTC Device Trigger". + +## 6.57.2 General + +![Figure 6.57.2-1: Optimised 'SMS over SGs' architecture diagram. The diagram shows the following components and connections: MS (Mobile Station) connected to MME (Mobility Management Entity) which contains an 'MSC' (Mobile Switching Center) function. MME is connected to HSS/HLR (Home Subscriber Server/Home Location Register) via the S6a interface. A dashed blue arrow labeled 'PS + "CS" loc update' points from MME to HSS/HLR. HSS/HLR is connected to SMS-GMSC/SMS-IWMSC via the MAP interface. SMS-GMSC/SMS-IWMSC is connected to SMS-SC (SMS Center) via the MAP interface. SMS-GMSC/SMS-IWMSC is also connected to IWF (TS29.305) via the MAP interface. A dashed red arrow labeled 'SMS forwarding' points from IWF to the 'MSC' function in the MME. A solid black arrow labeled 'Diameter' points from IWF to the MME.](b361fd4d68b14568a6c5acbcd9bfe8ee_img.jpg) + +Figure 6.57.2-1: Optimised 'SMS over SGs' architecture diagram. The diagram shows the following components and connections: MS (Mobile Station) connected to MME (Mobility Management Entity) which contains an 'MSC' (Mobile Switching Center) function. MME is connected to HSS/HLR (Home Subscriber Server/Home Location Register) via the S6a interface. A dashed blue arrow labeled 'PS + "CS" loc update' points from MME to HSS/HLR. HSS/HLR is connected to SMS-GMSC/SMS-IWMSC via the MAP interface. SMS-GMSC/SMS-IWMSC is connected to SMS-SC (SMS Center) via the MAP interface. SMS-GMSC/SMS-IWMSC is also connected to IWF (TS29.305) via the MAP interface. A dashed red arrow labeled 'SMS forwarding' points from IWF to the 'MSC' function in the MME. A solid black arrow labeled 'Diameter' points from IWF to the MME. + +**Figure 6.57.2-1: Optimised "SMS over SGs" architecture** + +Depicted in Figure 6.57.2-1 is an optimised SMS over SGs architecture obtained by merging the MSC Server functionality with the MME. There are no changes to the NAS or AS protocols. + +Given that MM signalling in the optimised architecture is performed over the same interface (S6a), the CS and PS location updates are merged into a single procedure. + +A MAP-Diameter interworking function (IMF) may be used on the SMS forwarding path in order to avoid the need for MAP interface support on the MME node. + +While the architecture still appears to be CS+PS from UE perspective, the "CS domain" in this architecture is completely virtual. The Location Area Identifiers (LAIs) signalled over the radio have no meaning other than identifying the combined MME/MSC node as the destination for mobile terminated SMS. + +**Editor's note:** It is FFS how the HSS/HLR can respond successfully to the piggybacked CS domain MM signalling without having any CS subscription data. + +**NOTE:** An MSISDN parameter is still required on the MAP interface between the SMS-GMSC and the HLR/HSS, but this is addressed by solutions targeting the "MSISDN-less" requirement. + +## 6.57.3 Impacts on existing nodes or functionality + +Piggybacking of CS domain mobility management messages over S6a. + +Collocation of MSC Server functionality in the MME for handling of SMS-related MAP procedures (possibly interworked via Diameter). + +Addition of MAP-Diameter interworking procedures in the TS 29.305 interworking function (IWF) in relation to MAP procedures for SMS. + +**Editor's note:** It is FFS if the MSC Server functionality residing in the MME should register with the HSS as an SGSN, instead of registering as an MSC. This is regardless of the fact that the UE performs combined EPS/IMSI Attach and combined TA/LA Update procedures over the radio. + +**Editor's note:** The impact on the HSS/HLR is FFS. + +## 6.57.4 Evaluation + +Benefits: + +- Reduces the amount of MM signalling in the Core Network for E-UTRAN devices; +- Allows for PS-only subscription for devices connecting via E-UTRAN; +- There are no changes to the AS or NAS protocols, which is why this architecture can also be used for existing UEs that attach over E-UTRAN as "SMS-only". + +Drawbacks: + +- The solution as described works only for single-mode E-UTRAN devices. + +## 6.58 Solution – Triggering using Cell Broadcast + +### 6.58.1 Problem Solved / Gains Provided + +See clause 5.8 "Key Issue - MTC Device Trigger", "Key Issue – Low Mobility", "Key Issue - Group Based Optimization" + +### 6.58.2 General + +With MTC devices that are attached, if the network has knowledge of the location of the device, a broadcast trigger may be useful to limit the amount of signalling between the CN and the devices, or to trigger communications by means other than via a PDP/PDN connection or SMS. + +Clause 6.6.2 describes the use of Cell Broadcast for triggering non-attached devices. This solution can also be used for triggering MTC devices that are attached, whereby triggers may be broadcast by using the Cell Broadcast Service (CBS) as specified in TS 23.041. This solution could be extended for E-UTRAN access, using warning message delivery as specified in TS 23.401 [5]. The existing CBS architecture for GERAN and UTRAN accesses, as well as the warning message approach in E-UTRAN (if extended to support triggering) should be evolved to handle multi-operator shared networks, for example, to allow the independent operation of CBC nodes by the sharing partners. + +A mobile network operator may provide an interface to the CBC to third parties, or alternately, the MTC Server may send a trigger containing, for instance, geographic information and trigger information to the MTC-IWF over MTCsp. The MTC-IWF could then act as a CBE to deliver the message to the CBC. The information provided by the MTC Server to the MTC-IWF would include the geographic information on where the broadcast should be done, and the MTC-IWF converts this to cell information for the CBC (or the MTC-IWF could get the serving SGSN/MME from the HLR/HSS and then get the cell information from SGSN/MME.) + +In order to limit the number of UEs responding, the message itself could identify the devices to be triggered. In order to allow it, the MTC-IWF would transparently pass the trigger information received from the MTC Server over MTCsp to the CBC. + +#### Device Identification + +The Cell Broadcast or Warning Message solution can be used to address MTC devices. For instance, the device's MSISDN, or some other unique paging identifier (UPID) can be used. + +Several different options might be considered for directing the cell broadcast messages. One option might be to assign PLMN specific CBS message identifiers to MTC devices that run certain applications. Broadcasting messages in a specific geographic area will trigger devices listening for these message identifiers. The devices to be triggered could be further constrained by using implementation dependent structures within the message itself. + +In order to direct the broadcast message in smaller deployments where assignment of separate message identifiers is not practical, a message structure could possibly be used whereby both the type of identifier and the identifier itself are broadcast. + +#### Protocol Aspects + +The current message definitions for Cell Broadcast and Warning Message delivery include a Message ID IE (see TS 23.041), which is defined for each different type of service. This IE is sent from the CBC to the UE, and is not acted upon in any of the intervening nodes. As part of the existing protocol, a device that is not interested in a particular Message ID value will simply ignore the message. Hence, already allocated PLMN specific message identifiers can be used, or possibly a new value or values can be allocated for use with MTC device triggering. Only those devices that use this type of triggering, and are programmed to process the specific message identifiers, would have to process messages beyond the message identifier. + +#### Scalability + +Indiscriminate use of cell broadcast for triggering could potentially cause a flood of signalling, which could cause problems for both the mobile network operator and the MTC application owner. This should be manageable, but would require limits set by the operator. For instance, the mobile network operator could limit the geography in which the + +messages are sent. Also, presuming that this mechanism could be expanded to cover multiple devices with a single broadcast message, agreements between the mobile network operator and the MTC operator could be set such that only a limited number of devices are triggered at a given time. Such agreements in isolation may not be enough and it may also be necessary to consider the context of current and historical network load which can be enforced by the mobile network operator in specific network entities such as the SGSN/MME. The scalability needs to be considered in the context for multi-operator shared networks so that operation of MTC services by the sharing partners are as independent as possible. + +Cell broadcast is suitable for triggering individual MTC Devices when triggering is infrequent. When many trigger messages are to be sent, cell broadcast is not likely to be an optimal solution. Hence, this solution should be seen as complementary to other mechanisms for sending triggers where the volume of triggers (product of number and frequency of triggers) exceeds a certain threshold. + +### Scalability in a Multi-Operator Sharing Scenario + +There may be one shared CBC in a multi-operator scenario. For emergency broadcast services, this situation is fine due to the low frequency and limited size of broadcast messages. In commercial services, sharing a CBC brings in the potential for competitive issues related to capacity, fair share of costs, and similar issues. + +These concerns can be addressed by recognizing the commercial factors in various ways. One approach is to use the number of instances of sending a broadcast trigger as a basis for sharing costs among the operators sharing the resource. Considering issue 2, with multiple operators using this capability, the likelihood increases that capacity limits might be reached. This can be addressed through providing additional CBCs which can still be shared when deployed geographically (i.e. each CBC covers a reduced geographic area but is still shared by the operators serving that area) or by moving from shared CBCs to individually owned CBCs. It is envisaged that a transition from one shared CBC to multiple non-shared CBCs could include a hybrid arrangement of shared/non-shared CBCs and geographic coverage. + +## 6.58.3 Impacts on existing nodes or functionality + +The CBC must be modified to: + +- assign the Message ID IE to the value(s) allocated for MTC Device triggering; +- allow independent operation of CBCs by the partners (a maximum of 6) in a multi-operator network, where GERAN, UTRAN, or E-UTRAN radio access networks are shared. + +### MTC-IWF + +- provide conversion of MTC Server provided location (e.g., civic addresses or geographic area) to network location information (e.g., TA/RA/LA); +- Interface to CBC needed. + +### MME/SGSN + +- Possibly add ability to support MTC-IWF location request: MTC-IWF could get the serving SGSN/MME from the HLR/HSS and then get the cell information from SGSN/MME. + +MTC devices will need to: + +- listen on the appropriate broadcast channel(s) for triggering messages; +- understand the message ID(s) that are to be used by the application; +- understand the device identification mechanisms that might be used to identify the device for triggering; +- perform the appropriate action after being triggered; +- MTC Devices need to have controlled access to avoid network overload. + +## 6.58.4 Evaluation + +### Benefits + +- Provides a base capability for group-based triggering. + +Cons: + +- For triggering a single device, extra overhead on the device to listen to paging as well as broadcast channel(s). +- The network may need to control access to avoid overload. +- Possible impacts on radio access nodes due to the independent CBC operation by sharing partners in GERAN, UTRAN, and E-UTRAN need further consideration. +- The solution needs to be extended to apply to E-UTRAN. +- Possible complexities due to roaming need to be investigated. +- Charging considerations would have to be investigated (e.g. if application information included), based on size of broadcast. + +## 6.59 Solution – Load/Overload Control via MTC-IWF + +### 6.59.1 Problem Solved / Gains Provided + +See clause 5.8 "Key Issue - MTC Device Trigger". + +### 6.59.2 General + +For MTC device triggering, the MTC server can send trigger requests with trigger indication information to the MTC-IWF for further processing to trigger target MTC devices. However due to network congestion the MME/SGSN may not be able to process the trigger requests from the MTC-IWFs or the responses to the trigger requests from the target MTC devices. + +The MTC-IWF contains load/overload mechanisms for handling and avoiding overload situations. In addition, under unusual circumstances (e.g. when the load of MME/SGSN exceeds an operator configured threshold or the MME/SGSN performs NAS level congestion control), the MME/SGSN restricts the load of trigger requests that are generating on it by its MTC-IWFs if it is configured to enable the overload restriction. With above considerations, there are two phases that the MTC-IWF performs to restrict the load of trigger requests from the MTC servers as well as to restrict the generated load of trigger requests on the MMEs/SGSNs. The first phase is to conduct load control on MTC servers and the second phase is to conduct overload/congestion control based on the guidance from the MME/SGSNs. + +**Editor's note:** One of the architecture options considered for MTC is that the MTC-IWF delivers triggers through an SMS-SC. The trigger load towards the network in this scenario may rely on existing load control mechanism of an SMS-SC. The interaction between SMS-SC and MTC-IWF load control is FFS. + +### 6.59.3 MTC-IWF Load Control to MTC servers + +The use of the load control on MTC-IWF is for handling of signalling load and avoiding signalling overload from the MTC servers sending triggering requests to target UEs which may be for a specific application. + +The MTC-IWF should detect the trigger signalling load associated with a particular MTC server, a specific application identifier, etc. The MTC-IWF performs the load control based on criteria such as: + +- The ingress/service rate of triggers from a specific MTC server; or +- The aggregate ingress/service rates from all MTC servers; or +- The maximum number of queuing trigger requests from a specific MTC server or all MTC servers for further processing; or +- One or multiple MME/SGSNs indicate congestion to the MTC-IWF; or +- Setting in network management. + +The MTC-IWF and MTC servers support the functions to provide load control over the MTCsp interface in the following manners: + +- The MTC-IWF provides the rules/instructions to the MTC server to reduce trigger load by sending an appropriate message over MTCsp interface with optional IEs indicating suppression factor, suppression delay or + +the suppression subcategories, e.g. an application identifier, a priority type, a specific MTC server, a specific TCP/UDP port, etc., to suppress the triggers sending from one or more MTC servers. + +- The MTC-IWF reports the success or failure of the trigger (e.g. due to network congestion) to the MTC server. +- The MTC server follows received rules/instructions received from the MTC-IWF and/or follow the policies of the MTC subscription to control traffic load of the trigger requests. + +With load control mechanism at MTC-IWF, it is anticipated that the trigger load generated by each MTC server to the MTC-IWF is handled well. However under certain circumstances, e.g. network congestion on the MME/SGSNs, The MTC-IWF may be overloaded due to slow forwarding rate of the trigger requests to the congested MME/SGSNs (trigger delivery via control plane). In this case, the MTC-IWF needs to conduct overload control which is detailed in the following clause 6.59.4 to adjust load control rules/instructions to the MTC servers, as indicated in clause 6.59.3. + +## 6.59.4 MME/SGSN Overload Control of Trigger Requests to MTC-IWF(s) + +To control trigger requests from MTC-IWF that generates trigger loads on the MME/SGSN, the overload control can be achieved by the MME/SGSN invoking the overload control procedure to MTC-IWF over T5b/T5a interface. The MTC-IWF performs the overload control by suppressing trigger requests, e.g. to stop forwarding the stored trigger requests to the next network node, to reject/drop the new arrival trigger requests and send notification message to the MTC server, or to delete the stored trigger request with reporting the trigger failure to the MTC server. + +To reflect the amount of trigger load that the MME/SGSN wishes to reduce, the MME/SGSN can send an appropriate message over T5b/T5a interface with optional IEs indicating the suppression factor, suppression duration, and/or suppressing subcategories, e.g. a specific application identifier, a specific priority type, etc., to reduce the trigger load from the MTC-IWF. + +Further, to prevent the network congestion from being exacerbated by UEs that respond to triggers, the network needs to ensure that no UEs is triggered as long as the particular congestion situation remains in the following manners: + +- If the MME/SGSN performs General NAS level Mobility Management Congestion Control or APN based Congestion Control, the MME/SGSN shall activate MTC-IWF overload control on trigger loads by sending an appropriate message to the MTC-IWF over T5b/T5a interface with optional IEs indicating suppression factor, suppression delay or the suppression subcategories, e.g. a particular congested APN, an application identifier, a priority type, a specific MTC server, a specific TCP/UDP port, etc. For example, if congested APN information is provided, the MTC-IWF reduces the trigger load of trigger requests for the UE that is targeting at the congested APN (see TS 23.401 [5], clause 4.3.7.4.2) by suppressing the trigger requests. + +**Editor's note:** It is FFS how the network node obtains APN information for the trigger requests. The overload control via MTC-IWF for APN based congestion control may not apply for the case when the trigger is sent transparently. + +- If the MME/SGSN stores the trigger request for a target UE, the MME/SGSN stops forwarding the trigger request to the UE and restart forwarding the trigger request when the network congestion is resolved and the validity time of the trigger is not expired. +- During an overload situation the MME/SGSN and MTC-IWF should attempt to maintain support for triggering UEs for emergency bearer services or high priority services. + +When receiving an appropriate message from the MME/SGSNs, the MTC-IWF can suppress the trigger requests from the MTC servers to reduce trigger load by sending an appropriate message over MTCsp interface as indicated in clause 6.59.3. + +The MME/SGSN and MTC-IWF should not suppress trigger requests for emergency services or high priority services due to network congestion. + +When the MME/SGSN is recovering, the MME/SGSN can: + +- send an appropriate message with optional IEs for suppression triggers, or +- send an appropriate message with new optional IEs that permits more trigger traffic to be carried, or +- resume handling triggers when the suppression delay is expired, to the MTC-IWF. + +## 6.59.5 Impacts on existing nodes or functionality + +- MTCsp interface needs to support protocols and messages for signalling suppressing trigger requests between the network node and the MTC server. +- The interface between MTC-IWF and MME/SGSN needs to support protocols and messages for triggers suppression. +- MTC server needs to follow the load control rules sending from the MTC-IWF or configured in the MTC subscription. +- MTC-IWF needs to detect trigger load and support load/overload control mechanisms to the MTC servers, and MME/SGSN. +- MME/SGSN needs to initiate overload control on triggers sending from the MTC-IWF when conducting NAS level congestion control. + +## 6.59.6 Evaluation + +### Benefits: + +- Enable the MTC-IWF to regulate trigger loads by load/overload control to reduce the trigger signalling from the trigger requests received from MTC servers. +- Protect network nodes (e.g. MME/SGSN, MTC-IWF) effectively from network congestions due to massive simultaneous trigger requests from MTC servers. +- Avoid massive individual reject messages responding from a congested network node to the MTC-IWF. + +### Drawbacks: + +- Existing network node (e.g. MME/SGSN) needs to support the load/overload control function for suppressing trigger load from MTC-IWF due to network overload/congestion. + +### Others: + +#### 1) Delivery of device trigger information from 3GPP system to UE: + +- Some information, e.g. validity time, priority type, contained in trigger request message may have impact on the handling of trigger suppression. + +#### 2) Submission of device trigger requests from MTC server to 3GPP system: + +- The MTCsp interface supports the protocol for the load control related messages. +- The MTC server follows the rules/instructions indicated in load/overload control message sending from the MTC-IWF. +- The MTC-IWF supports load/overload control mechanism based on the detection of criteria or received message sending from the MME/SGSN. +- The overload control via MTC-IWF for APN based congestion control may not apply for the case when the trigger is sent transparently. + +#### 3) 3GPP system internal handling of device triggers: + +- The network node (e.g. MME/SGSN) supports the overload control mechanism based on delivery of device trigger requests in the control plane (e.g. NAS level congestion control). +- The protocol and the messages of the interface between MME/SGSN and MTC-IWF supports overload control. + +## 6.60 Solution - Device trigger using MT-SMS & direct SGSN/MME delivery + +### 6.60.1 Problem Solved / Gains Provided + +Clause 5.8 "Key Issue - MTC Device Trigger", + +Clause 5.11 "Key Issue - Decoupling MTC Server from 3GPP Architecture"; and + +Clause 5.13 "Key Issue - MTC Identifiers". + +### 6.60.2 General + +This solution uses two trigger delivery methods, delivery using MT-SMS, and delivery from the MTC-IWF to the SGSN/MME for delivery to the UE. (It is a scaled down version of clause 6.45). + +![Figure 6.60.2-1: MTC device trigger architecture using MT-SMS delivery or direct MTC-IWF to SGSN/MME delivery. The diagram shows the flow of trigger information from an MTC Application through various network elements to a UE. Control plane messages (dashed lines) include 'Lookup' from CTF to HSS, 'SMS with trigger information' from CTF to SMS-SC, and 'Trigger Information' from MTC-IWF to SGSN/MME. User plane messages (solid lines) show data flow between the UE, SGSN/MME, and GGSN/P-GW. The MTC-IWF is connected to an MTC Server, which is in turn connected to an MTC Application via an API. The MTC-IWF also has a direct connection to the SGSN/MME. The diagram is divided into 'service provider controlled' and 'operator controlled' regions by a vertical dashed line labeled '3GPP Boundary'.](1d723f5111a010a80347ee4ead0da1a9_img.jpg) + +Figure 6.60.2-1: MTC device trigger architecture using MT-SMS delivery or direct MTC-IWF to SGSN/MME delivery. The diagram shows the flow of trigger information from an MTC Application through various network elements to a UE. Control plane messages (dashed lines) include 'Lookup' from CTF to HSS, 'SMS with trigger information' from CTF to SMS-SC, and 'Trigger Information' from MTC-IWF to SGSN/MME. User plane messages (solid lines) show data flow between the UE, SGSN/MME, and GGSN/P-GW. The MTC-IWF is connected to an MTC Server, which is in turn connected to an MTC Application via an API. The MTC-IWF also has a direct connection to the SGSN/MME. The diagram is divided into 'service provider controlled' and 'operator controlled' regions by a vertical dashed line labeled '3GPP Boundary'. + +**Figure 6.60.2-1: MTC device trigger architecture using MT-SMS delivery or direct MTC-IWF to SGSN/MME delivery** + +The interrogated HSS returns information related to delivery of the device trigger, such as IMSI and serving SGSN/MME. The trigger information is delivered to the UE using MT-SMS, or delivered from the MTC-IWF to the SGSN/MME for delivery to the UE. + +The MTC-IWF is a pure control plane function which delivers the trigger information towards the UE regardless of PDP/PDN connection state. The network confirms the success or failure of delivering the trigger to the UE back to the MTC Server. The trigger information is delivered to the MTC Application in the UE, which may for example start communicating with the MTC Server or MTC Application. For this the user plane connection is established as needed. + +**Editor's note:** The details of the solution are FFS. + +### 6.60.3 Impacts on existing nodes or functionality + +Impact to the Core Network: + +- Deployment of the MTC IWF; + +- New reference points (T4, T5a and T5b) to connect the MTC-IWF to SMSC, to SGSN/MME and to HSS. The T5a and T5b reference points need to be specified as roaming interfaces; +- New instance of pre-defined reference point (Rf) to connect the CDF. + +## 6.60.4 Evaluation + +# 6.61 Solution – Native SMS over NAS for PS-only + +## 6.61.1 Problem Solved / Gains Provided + +"PS-Only Support". + +## 6.61.2 General + +A PS-only device is a device that avoids using any CS service from a MSC in GERAN/UTRAN and would only use SMS from a MSC in GERAN/UTRAN if the SGSN does not provide support SMS transfer in the serving network. The UE subscribes only to PS domain and SMS services and may not be assigned an MSISDN. As such, if SMS over IP is not used, it can only receive SMS on the PS domain of GERAN/UTRAN or on the EPS over NAS Signalling. The former is not supported in all networks, the latter has not been defined without a combined registration as in TS 23.272 [23] to achieve SMS delivery over SGs. + +In rel-8 the delivery of SMS over NAS in EUTRAN is allowed for UE's that perform a combined registration. The assumption is that these devices can also camp on the CS domain of GERAN/UTRAN when they are out for EUTRAN coverage, to be able to receive SMS in networks not delivering SMS over GPRS. If a UE is only EPS registered, however, it is assumed that the mechanism used for SMS delivery would be SMS over IP. As per statement in clause 6.52.2.3 "Flexible deployment of MSC functionality for SMS over SGs", there is awareness that "In some deployment scenarios, the use of "SMS over IMS" can be regarded as rather heavyweight for low end M2M applications". It may be argued that in an inexpensive MTC device using EUTRA, and maybe also UTRA and GERA, may not need an IMS client for other purposes than SMS, hence it could be something it could be stripped of if SMS could be delivered over NAS. + +In order to deliver SMS over NAS without impacting MSC's the UE needs to indicate to the network that it supports Native SMS Capability on E-UTRAN and that it intends to register for that in both EPS Attach and TAU procedures, as in fact from rel-8 an EPS-only registration would not allow for SMS delivery over E-UTRAN (we need a combined registration as in TS 23.272 [23] to achieve that over SGs). The MME also needs to be able to accept or reject the SMS registration at EPS attach time, and indicate whether it support as an alternative SMSoverSGs. + +An interface needs to be defined between the MME and the SMS-GMSC/SMS-IWMC for SMS delivery (either using existing MAP procedures or equivalent IP based protocols to be defined at stage 3). + +The HSS needs to be able to perform SMS routing and SMS waiting list management and interact with the SMS-GMSC/SMS-IWMC (either using existing MAP procedures or a DIAMETER-based equivalent to be defined at stage 3). The adoption of DIAMETER - based interface may be preferred if we do not want to support legacy protocols in MME and HSS. This is in line with the conclusions b) in clause 7.2.2. However the interface to SGSN may still need to be using the legacy option. + +Due to the fact the UE is dual registered on an SGSN and an MME with the HSS, a mechanism is needed to deliver the SMS to the correct serving node in MT-SMS case. One possibility is to update the location of the UE's requiring support of native SMS over EUTRAN and also subscribing to SMS services, when they change RAT, which would have no impact on the delivery interfaces or the SMS-GMSC/IWMC. This precise "current serving node" information then also may be beneficial for other Mobile terminated services for MTC type devices. + +When the PS only UE is in GERAN/UTRAN it may first attempt to register for PS services only. If the UE detects it is not possible to receive SMS from the serving SGSN, then if it is capable of obtaining SMS services from the CS domain it would register on the CS domain also. The CS subscription profile of a PS-only UE would have to be configured only for SMS services and no other CS services. + +### 6.61.3 Impacts on existing nodes or functionality + +MME needs to be augmented with Native SMS capability, i.e. an SMS delivery interface with the SMS-GSMS and an updates S6a with SMS delivery capability notification in attach and TAU. The NAS must be capable to transfer SMS and also to receive indication of support of SMS transfer over NAS in EUTRAN from the UE and whether accept it or reject it. This indication may also need to be provided in TAU's so that when the UE moves from 2G/3G to the EPS the capability is known. + +The UE needs to be capable of explicitly registering for native SMS over NAS at EPS attach and to send indication of registration and support to this capability at TAU time (in addition of supporting NAS procedures for SM transfer). + +The MME and S4 SGSN shall be capable to detect whether the UE requires SMS delivery on EPS natively, and if so would update the HSS when the UE is changing between EUTRAN and GERAN/UTRAN. + +### 6.61.4 Evaluation + +This solution may be superior to SMS over IP in inexpensive devices (see 6.52.2.3 on Flexible deployment of MSC functionality for SMS over SGs). + +## 6.62 Solution - User plane based device Triggering + +### 6.62.1 Problem Solved / Gains Provided + +Clause 5.8 "Key Issue - MTC Device Trigger". + +### 6.62.2 High level information flow for Device Triggering using user plane + +These solutions assume there is an application on the MTC device listening on a particular TCP/IP port to receive the application triggers. + +![Figure 6.62.2-1: High level information flow for Device Triggering using user plane. The diagram shows the interaction between an MTC Device, PGW/GGSN, Other Entities, MTC IWF, Mapping Table, and MTC Server. The flow is as follows: 1. MTC Server sends a Device Trigger Request to MTC IWF. 2. MTC IWF sends an Inquiry to the Mapping Table. 3. MTC IWF sends a Delivery Request to the PGW/GGSN. 4. PGW/GGSN sends a Delivery Ack to the MTC Device. 5. MTC IWF sends a Delivery Ack to the MTC Server. 6. Application signalling occurs between the MTC Device and the MTC Server via the PGW/GGSN.](bedcefe3d0fc5b6a061f16121cd2f291_img.jpg) + +``` + +sequenceDiagram + participant MTC Server + participant MTC IWF + participant Mapping Table + participant Other Entities + participant PGW/GGSN + participant MTC Device + + Note right of MTC Server: 1. Device Trigger Request + MTC Server->>MTC IWF: Device Trigger Request + Note left of MTC IWF: 2. Inquiry + MTC IWF-->>Mapping Table: Inquiry + Note right of MTC IWF: 3. Delivery Request + MTC IWF->>PGW/GGSN: Delivery Request + Note left of PGW/GGSN: 4. Delivery Ack + PGW/GGSN->>MTC Device: Delivery Ack + Note right of MTC IWF: 5. Delivery Ack + MTC IWF->>MTC Server: Delivery Ack + Note right of PGW/GGSN: 6. application signalling + MTC Device->>MTC Server: application signalling + +``` + +Figure 6.62.2-1: High level information flow for Device Triggering using user plane. The diagram shows the interaction between an MTC Device, PGW/GGSN, Other Entities, MTC IWF, Mapping Table, and MTC Server. The flow is as follows: 1. MTC Server sends a Device Trigger Request to MTC IWF. 2. MTC IWF sends an Inquiry to the Mapping Table. 3. MTC IWF sends a Delivery Request to the PGW/GGSN. 4. PGW/GGSN sends a Delivery Ack to the MTC Device. 5. MTC IWF sends a Delivery Ack to the MTC Server. 6. Application signalling occurs between the MTC Device and the MTC Server via the PGW/GGSN. + +Figure 6.62.2-1:High level information flow for Device Triggering using user plane + +1. The MTC server submits a Device Trigger Request providing the external device identifier and optionally a validity period. +2. The MTC-IWF authorises the trigger request. The IWF interrogates the HSS with the external device identifier to derive the IMSI and any additional information needed for trigger delivery. + +The MTC-IWF optionally queries other entities (such as mapping table etc) to obtain the IP address of the MTC Device. If the MTC Device had previously registered its IP address with the MTC-IWF through application layer signalling, the MTC-IWF does not have to query the mapping Table. + +Optionally, the MTC-IWF may also send the trigger to the MTC device over the user plane through other network entities such as IMS. + +3. The IWF delivers the trigger request to the MTC device over the user plane. This message is seen as a data packet by the EPC. + +4. The MTC UE sends a delivery ack. +5. The delivery or non-delivery is acknowledged to the MTC server. +6. The application on the device communicates with the MTC server. + +### 6.62.3 Proposals for MTC-IWF to determine IP address of MTC device + +This clause discusses various alternatives for the MTC-IWF to obtain the IP address of the MTC device. + +#### 6.62.3.1 Alternate 1 - Explicit Registration based + +In this alternative, the MTC device explicitly registers with the MTC-IWF through application layer signalling. + +![Sequence diagram for Alternate 1 - Explicit Registration based. The diagram shows three main entities: MTC device, PGW/GGSN, and MTC-IWF. The sequence of events is: 1. PDN/PDP connectivity procedure between MTC device and PGW/GGSN. 2. Application layer registration between MTC device and MTC-IWF. 3. MTC-IWF receives trigger from MTC Server. 4. MTC-IWF consults local DB to get IP address of MTC device. 5. MTC-IWF sends packet to PGW/GGSN. 6. Packet delivered over user plane from PGW/GGSN to MTC device.](9aa0b1bed68fb431319e7a58045a3146_img.jpg) + +``` + +sequenceDiagram + participant MTC device + participant PGW/GGSN + participant MTC-IWF + Note left of MTC device: 1. PDN/PDP connectivity procedure + MTC device->>MTC-IWF: 2. Application layer registration + Note right of MTC-IWF: 3. MTC-IWF receives trigger from MTC Server + Note right of MTC-IWF: 4. MTC-IWF consults local DB to get IP address of MTC device + MTC-IWF-->>PGW/GGSN: 5. MTC-IWF sends packet to PGW/GGSN + PGW/GGSN-->>MTC device: 6. Packet delivered over user plane + +``` + +Sequence diagram for Alternate 1 - Explicit Registration based. The diagram shows three main entities: MTC device, PGW/GGSN, and MTC-IWF. The sequence of events is: 1. PDN/PDP connectivity procedure between MTC device and PGW/GGSN. 2. Application layer registration between MTC device and MTC-IWF. 3. MTC-IWF receives trigger from MTC Server. 4. MTC-IWF consults local DB to get IP address of MTC device. 5. MTC-IWF sends packet to PGW/GGSN. 6. Packet delivered over user plane from PGW/GGSN to MTC device. + +**Figure 6.62.3.1-1: Alternate 1 - Explicit Registration based** + +1. The UE initiates PDN/PDP connectivity procedure as in TS 23.401 [5]/TS 23.060 [21]. +2. The application on the MTC device registers its IPv4/IPv6 address with the MTC-IWF. +3. The MTC-IWF receives a trigger over MTCsp from the MTC server. +4. The MTC-IWF queries its local database to obtain the IPv4/IPv6 address of the UE. +5. The MTC-IWF sends the trigger to the MTC device using the IPv4/IPv6 address. +6. The PGW/GGSN delivers the packet to the UE over the user plane bearer. + +Evaluation: + +- This solution needs to define an application layer signalling message between MTC device and MTC-IWF to transport/register the IP address assigned to the MTC device. +- The MTC device needs to listen on specific port to receive & process the MTC trigger. + +#### 6.62.3.2 Alternate 2 - Mapping Table based + +This clause discusses possible alternate solutions for the mapping table to be populated by different network entities with the MTC device's IP address. + +##### 6.62.3.2.1 MME/HSS based mapping table update + +The flow/procedures for this option is specified in clause 6.1. + +## 6.62.3.2.2 PGW/GGSN based mapping table update + +![Sequence diagram for PGW/GGSN based mapping table update. Lifelines: MTC device, PGW/GGSN, Mapping Table, MTC-IWF. The sequence starts with the MTC device initiating a PDN/PDP connectivity procedure with the PGW/GGSN. The PGW/GGSN then updates the mapping table. Later, the MTC-IWF receives a trigger from an MTC Server, queries the mapping table, receives an IP address response, and sends a trigger to the IP address over the user plane. Finally, the PGW/GGSN delivers the packet to the MTC device over the user plane.](1ff58ab75ff926ead7067453006a75fe_img.jpg) + +``` + +sequenceDiagram + participant MTC device + participant PGW/GGSN + participant Mapping Table + participant MTC-IWF + Note right of MTC device: 1. PDN/PDP connectivity procedure + MTC device->>PGW/GGSN: 1. PDN/PDP connectivity procedure + PGW/GGSN->>Mapping Table: 2. Update the mapping table + Note right of MTC-IWF: 3. MTC-IWF receives trigger from MTC Server + MTC-IWF->>Mapping Table: 4. Query + Mapping Table->>MTC-IWF: 5. Response (IP Address) + Note right of MTC-IWF: 6. Send trigger to IP address over UP + MTC-IWF->>PGW/GGSN: 6. Send trigger to IP address over UP + Note right of PGW/GGSN: 7. Packet delivered over user plane + PGW/GGSN-->>MTC device: 7. Packet delivered over user plane + +``` + +Sequence diagram for PGW/GGSN based mapping table update. Lifelines: MTC device, PGW/GGSN, Mapping Table, MTC-IWF. The sequence starts with the MTC device initiating a PDN/PDP connectivity procedure with the PGW/GGSN. The PGW/GGSN then updates the mapping table. Later, the MTC-IWF receives a trigger from an MTC Server, queries the mapping table, receives an IP address response, and sends a trigger to the IP address over the user plane. Finally, the PGW/GGSN delivers the packet to the MTC device over the user plane. + +Figure 6.62.3.2.2-1: PGW/GGSN based mapping table update + +1. The UE initiates PDN/PDP connectivity procedure as in TS 23.401 [5]/TS 23.060 [21]. +2. The PGW/GGSN updates the mapping table with the IP address assigned to the UE. + +NOTE 1: In case of the IPv6, the UE is configured to form its global IPv6 address as the concatenation of the IPv6 Prefix and the Interface Identifier provided by PGW/GGSN. + +Editor's note: The mechanism/procedures/interfaces for updating the mapping table by the PGW/GGSN is FFS. + +Editor's note: The use of DNS server as mapping table is FFS. + +3. The MTC-IWF receives a trigger over MTCsp from the MTC server. +4. The MTC-IWF queries the mapping table for the IPv4 and/or IPv6 address that corresponds to the UE's FQDN. +5. The mapping table replies with the IPv4 and/or IPv6 address for the UE. +6. The MTC-IWF sends the trigger to the MTC device using the IPv4/IPv6 address. +7. The PGW/GGSN delivers the packet to the UE over the user plane bearer. + +NOTE 2: When the UE detaches, the PGW/GGSN updates the mapping table. + +## Evaluation: + +- This solution requires the PGW/GGSN to update/maintain the mapping table entry related to the MTC device. +- In case of IPv6, the global IPv6 address is constructed using the concatenation of the IPv6 prefix and the Interface ID provided by the PGW/GGSN. + +## 6.62.4 IMS-based trigger delivery over user plane + +Trigger can be delivered to UE over IMS using procedures defined in TS 23.204 [15]. There are no further impacts to any specification. + +## 7 Conclusions + +**Editor's note:** This clause is intended to list conclusions that have been agreed during the course of the work item activities. + +### 7.1 Interim conclusions for release 10 specification work + +This clause contains the agreed conclusions corresponding to Key Issue 5.12 and 5.14. 3GPP Release 10 specifications should be developed in the following areas: + +- a) the UE behaviour changes outlined in bullets a, b, c, d and e in clause 6.33; +- b) the M2M device indicators outlined in bullets a, b and c in clause 6.34 (some of which are also mentioned in clauses 6.20, 6.23 and 6.26; +- c) the non HPLMN (PLMN type) and Low-Priority-device style access class barring functionality outlined in clauses 5.12, 5.14 and 6.28.4; + +NOTE: Updates to SA1 specifications such as TS 22.011 may be needed. + +'Course grained' (i.e. "Low-Priority-Access" and "PLMN type") MTC access barring triggered via O+M into the RAN, internal RAN functionality, and by signalling from the Core Network is expected to be included in Rel-10. Other options for broadcasting of MTC access barring by RAN (e.g. based on the APN or MTC Group) may be considered for Rel-11. + +- d) the use of RR(C) connection reject messages with extended Wait Times outlined in clauses 6.23 and 6.26; +- e) the use of M2M device specific (long) periodic update timers in MM, GMM and EMM signalling, including signalling from HSS to MSC/SGSN/MME (see clause 6.20); +- f) in combination with the use of long, MTC specific PTU/PRU/PLU timers, the specification of signalling that permits the operator to command M2M devices to use Network Mode Of Operation I while keeping existing mobiles in Network Mode of Operation II (see clauses 5.14 and 6.20); +- g) the specification of MM/GMM/EMM functionality that can limit load on CN entities of all local PLMNs (e.g. by the transmission of an RA Update ACCEPT message with PRU timer of 20 minutes rather than an RA Update Reject message); +- h) the use of NAS-level back-off timer per APN to reject Attach and connectivity establishment requests as outlined in clause 6.22; +- i) The use of connectivity establishment request rejection at MME/SGSN and PGW/GGSN as outlined in clause 6.22. +- j) The use of the MME/SGSN overload control by DL MTC traffic throttling such as described in clause 6.30; +- k) [///list to be completed. ///](#) + +### 7.2 Interim conclusions for release 11 specification work + +#### 7.2.1 IP Addressing - Key Issue 5.3 + +This clause contains the agreed conclusions corresponding to Key Issues 5.3. + +3GPP Release 11 specifications should be developed in the following areas: + +- a) IPv6 as the primary solution for IP addressing of UEs used for MTC. +- b) IPv4 based solutions are considered transition solutions and are deprecated. The following IPv4 capable addressing solutions are documented in appropriate informative annexes as described in clause 8.2. + - For all models, when the UE and the network support online device triggering, use the online device triggering to handle NAT traversal. + +NOTE 1: The above solution resolves the issue when the UE and the MTC server do not share IPv4 addresses from a common IPv4 address space. + +- For indirect and direct model, use of separate APNs (as described in clause 6.29.2), and IPv4 address allocation is performed following procedures already described in 3GPP specifications. + +NOTE 2: The scenario where the MTC Server and/or its end-to-end connection to the mobile operator's domain is dependent on IPv4 addressing will be reduced as the migration to IPv6 proceeds. However an IPv6 capable MTC Server (i.e. dual-stack) in an IPv4 public address space can still be a valid scenario for some years. For such scenarios where there is no end-to-end IPv6 connectivity, well known transition mechanisms can be used. This is considered normal network design and should be transparent to 3GPP specifications. Therefore an MTC Server using IPv6 addressing connected to IPv6 UE used for MTC over a public IPv4 address space can be considered as an IPv6 scenario (i.e. scenario A in clause 5.3.1). + +## 7.2.2 MTC Device Triggering - Key Issue 5.8 + +**Editor's note:** The conclusions do not imply a decision whether there will be one or multiple triggering methods standardised. + +This clause contains the agreed conclusions corresponding to Key Issues 5.8. 3GPP Release 11 specifications should be developed in the following areas: + +### 1) Delivery of device trigger information from 3GPP system to UE: + +All device triggering should provide mechanism to ensure authenticity. + +The following device trigger delivery mechanisms shall be developed/supported: + +#### A. MT-SMS for the following cases: + +- For UE subscriptions with an E.164-MSISDN assigned, submitted to SMS-SC of 3GPP system over MTCsms. + - This solution is especially applicable for providing triggers via legacy networks, i.e. networks that don't deploy any specific trigger delivery mechanism that might be introduced with Rel-11. +- For UE subscriptions with or without an E.164-MSISDN assigned, submitted to MTC-IWF of 3GPP system over MTCsp. + - When UE subscription does not have an E.164-MSISDN assigned, the MTC-IWF shall allow the IMSI as the destination address for submission of the MT-SMS to the SMS-SC. + +**Editor's note:** Considerations for alternative to IMSI as the destination address for MTC-IWF submission of the MT-SMS to the SMS-SC is FFS. + +For devices that may camp on E-UTRAN cells, this trigger delivery solution is applicable only when the UE also has a CS domain subscription and the UE and network support SMS using SMSOverSGs, as defined in TS 23.272 [23], or the UE and HPLMN are using SMS over IMS. + +UEs should be able to discriminate an MT-SMS carrying device triggering information from any other type of SMS. + +**Editor's note:** It is FFS if MT-SMS procedures will be enhanced in Rel-11 to support MT-SMS to overcome the above limitations. + +**Editor's note:** In order to avoid upgrades to legacy networks a protocol within the SMS body to carry the triggering information identified in clause 6.40 is FFS. + +#### B. Improvements to MT-SMS that: + +- ensure the SMS can be delivered to a PS-only device with only one HPLMN-VPLMN interaction, as SMS over SGs without improvement would entail an 'MSC' delivery attempt followed by an SGSN delivery attempt; + +- b. permit the replacement of MAP interfaces with more IETF friendly interfaces (e.g. Diameter); and + - c. ensure that the MTC device can verify the authenticity of the trigger. +- C. Trigger delivery over T5a/T5b/T5c +- a. When serving SGSN/MME/MSC is available, the trigger is sent directly from the MTC-IWF to serving SGSN/MME/MSC over T5a/T5b/T5c. + - b. SGSN/MME/MSC delivers the trigger to UE over the NAS. + +**Editor's note:** How trigger is delivered to UE (e.g. using SMS transport or NAS generic container) will be taken during the normative phase of the work. + +D. The following solutions related to User plane based trigger delivery: + +- a. Solutions (e.g., explicit registration, see 6.62.3.1) which do not require enhancements to 3GPP specifications. + +**NOTE:** User plane trigger can be delivered to UE over IMS using procedures defined in TS 23.204 [15]. There are no further impacts to any specifications. + +- b. The possibility to support other user plane solutions depend on whether mapping between IP address and external id is available as a result of technical specification of the control plane solution. + +## 2) Submission of device trigger requests from MTC server to 3GPP system: + +- a) The standardised protocol used from the MTC Server to the 3GPP system via reference point MTCsp should support both triggering with unique E.164-MSISDN (for backward compatibility) and without such an MSISDN. The MTCsp is provided by an MTC-IWF. It is transparent for the MTC server how the triggering information is delivered by the 3GPP system to the UE. +- b) It shall be possible for an MTC server to resolve the MTC-IWF(s) address(es) for a particular UE, e.g. by DNS +- c) The MTC-IWF performs PLMN related control functionality such as MTC server authentication, trigger request authorization and charging, and shields the MTC server from the actual trigger delivery mechanism used in the PLMN. +- d) MTCsp shall always be provided by the HPLMN. The MTC-IWF will only accept a device trigger request for a UE whose HPLMN is the operator of the MTC-IWF. +- e) The MTC Server uses validity time over MTCsp. +- f) The MTC-IWF shall support load control functionality to indicate MTC server over MTCsp interface to limit the load generated on it. + +**Editor's note:** The load control function needs to consider the possible causes to complicate the trigger handling of the MTC server. + +## 3) 3GPP system internal handling of device triggers: + +- a) The protocols within the PLMN should support an option where the UE can be identified without the use of an E.164-MSISDN. A PLMN may support delivery of MT-SMS submitted with an IMSI as destination address instead of an E.164-MSISDN. However, in order to avoid exposure of IMSI outside of MNO domain, this shall only be allowed for SMEs located in the MNO domain. +- b) The 3GPP system shall support MTC-IWF interrogation, when needed, of HLR/HSS to map an external identifier to IMSI and gather information stored in HLR/HSS required for device triggering. +- c) The MTC-IWF shall support selection of the trigger delivery mechanism and performs protocol translation if necessary, e.g. to reformat the triggered request to match the selected trigger delivery method, and routes the request towards the relevant network entity. +- d) When SMS service is selected as the trigger delivery mechanism, validity time over MTCsp is mapped to Validity Period in SMS delivery. + +- e) The MME/SGSN/MSC and MTC-IWF shall support overload control functionality to allow the MME/SGSN/MSC to indicate in the rejection or acknowledgement to the MTC-IWF over T5a/T5b/T5c interface to limit the load generated on it. + +### 7.2.3 MTC Identifiers - Key Issue 5.13 + +This clause contains the agreed conclusions corresponding to Key Issues 5.13. 3GPP Release 11 specifications should be developed in the following areas: + +- a) IMSI is the internal identifier. +- b) The existing 3GPP identifiers are not modified, i.e. there will be neither changes to IMSI/IMEI structure nor other changes to existing 3GPP identifiers. +- c) When the MSISDN is not available for CDR generation in the PS domain, the IMSI shall be used for CDR generation purposes. Typically, the external identifier is used for customer billing. +- d) Alternative identifier(s) to MSISDN shall be supported on the MTCsp as the external identifier(s). +- e) External identifier shall have following components that makes it globally unique: + - a. Domain-Identifier that identifies a domain that is under the control of a Mobile Network Operator (MNO). This is used to find MTC-IWF (i.e. IP address on MTCsp) to be used. Domain-Identifier may have further identification for example to identify MTC-IWF specific for application. + - b. Local-Identifier that is assigned by the mobile network operator. This identifier is used to derive or obtain internal identifier by the network operator. The local identifier shall be unique within this domain. The structure of the Local Identifier is flexible. For Example it may be structured into one or more different parts: + - i. A part optimized to find an entry in MNO database (e.g. subscription context in HLR/HSS to derive Internal Identifier). Few examples are the Subscriber Number part of an E.164 MSISDN (see TS 23.003 [12]) or other scheme specified by the MNO. + - ii. Another part relevant to customer application (e.g. to enable corporate customer to find information in their database). Few examples are serial number, chassis number for car, etc. +- f) Multiple external identifiers can map to single internal identifier (i.e. IMSI). + +### 7.2.4 MTC Feature Control - Key Issue 5.7 + +This clause contains the agreed conclusions corresponding to Key Issues 5.7 + +- a) No solution for MTC Feature Control is standardized for Rel-11. + +### 7.2.5 MTC Feature - Packet Switched only + +This clause contains the agreed conclusions for the MTC feature "Packet Switched (PS) only". 3GPP Release 11 specifications should be developed in the following areas: + +- a) It shall be possible to provide PS services and SMS for a UE via GERAN and UTRAN without involving an MSC. This includes the case where an HSS does not provide subscription data to a GERAN or UTRAN MSC for that UE when both UE and serving PLMN support the feature. +- b) Not receiving services from a GERAN or UTRAN MSC due to PS only shall not affect services provided to that UE, which may include that an unsuccessful/rejected registration attempt towards a GERAN/UTRAN MSC shall not result in loosing SMS services provided via another RAT or domain used by the UE. +- c) It shall be possible to provide PS services and SMS via E-UTRAN/MME with efficient HSS signalling, which may include an HSS registration procedure that provides subscription data for PS services and SMS together. It should not have adverse effects like increased HSS signalling, e.g. when the UEs reselect between RATs. +- d) The PS only feature shall not prevent receiving SMS services when the UE or the visited/serving PLMN don't provide the capabilities required for PS only. + +- e) There need to be mechanisms to allow the UE to select the appropriate SMS delivery mechanism(s). Whether to adopt existing E-UTRAN access procedures for SMS via NAS signalling (i.e. Combined EPS/IMSI Attach and Combined TA/LA Update) or to use different procedures (e.g. EPS Attach and TA Update with addition of new information elements) is TBD. For 2G/3G access the SGSN and/or MSC registration procedures may be enhanced to inform the UE that it should use only the PS domain for receiving PS and specifically SMS services. +- f) The PS only feature shall not affect PS or SMS services and shall work whether the UE has an MSISDN assigned or not. + +--- + +## 8 Impacts to normative specifications + +**Editor's note:** This clause is intended to capture the impacts to normative specifications within the responsibility of SA2. It can be used as a placeholder to document agreements until a set of normative CRs can be generated for the selected solutions(s) + +### 8.1 Related to Interim conclusions for release 10 specification work + +The changes outlined in bullets a through g in clause 7.1 have minimal impact on SA2's specifications. Probably, some general clause s could be added to TS 23.060 [21] and TS 23.401 [5] to describe the overall problem and solutions. + +With the exception of TS 23.122, and a new OMA DM Managed Object, stage 3 work is probably also relatively limited: e.g. a few new code points or information elements are needed in the NAS signalling (TS 24.008 [16] and TS 24.301 [17]); the HSS-MSC/SGSN/MME signalling (TS 29.002 [18] and TS 29.272 [19]); the UE-RAN signalling (TS 36.331, TS 25.331 and TS 44.018); and possibly in the S1/Iu/Gb/A interface Overload messages. + +Modified TS 23.122 procedures and the associated UE interactions with multiple local PLMNs probably represents the major complex task ahead in Release 10. + +**Editor's note:** The impact of bullets h, i and j in clause 7.1 still has to be checked. + +### 8.2 Related to Interim conclusions for release 11 specification work + +#### 8.2.1 IP addressing + +##### 8.2.1.1 Guiding Principles + +This clause provides a proposed way forward and guiding principles on how to document IP addressing related aspects in normative Stage 2 specifications. + +The guiding principles when to documenting IP addressing solutions are: + +- A. Focus on most important deployment scenarios as in clause 5.3.1. +- B. Maximize the reuse of existing 3GPP standards and minimize the impact on the 3GPP System. +- C. Use of IPv6 addressing as the primary solution for IP addressing of UEs used for MTC. IPv4 based addressing is deprecated but not precluded. + +##### 8.2.1.2 Documentation approach + +It is proposed that IP addressing aspects are documented using the following approach: + +- A normative part giving an overview of IPv6 addressing mechanisms. +- An informative annex documenting how existing mechanisms can be used to support IPv4 addressing mechanisms to serve as implementation guideline for transition solutions. + +#### 8.2.2 MTC Identifiers + +##### 8.2.2.1 Guiding Principles + +The guiding principles when documenting identifiers for MTC are: + +- A. Continued usage of IMSI, i.e. no need to define an Internal Identifier in normative specifications. +- B. The External Identifier is required for protocols used across the 3GPP boundary, where MSISDN and IMSI cannot be used (e.g. when MSISDN-less operation is used and security reasons prevent IMSI to be used). These protocols include: + - Protocols used on the Tsp reference point. + - The RADIUS/Diameter protocols used on Gi/SGi reference point. + +**Editor's note:** It is FFS whether and where in CN the External Identifier(s) need to be present to support e.g. Lawful Interception or charging. + +#### 8.2.2.2 Documentation approach + +MTC Identifiers aspects are documented in SA WG2 specifications using the following approach: + +- A normative part giving an overview of External Identifier usage on MTC-IWF based interfaces in TS 23.682 [20]. +- Normative parts in TS 23.003 [12], TS 23.060 [21], TS 23.401 [5] and TS 23.682 [20] updating the information storage of relevant key nodes. + +--- + +## Annex A: Stage 2 PS Dependencies on MSISDN-based Subscriptions + +### A.1 General Considerations + +In order to facilitate the enhancement of the stage 2 architecture to support MSISDN-less subscriptions for PS only devices, this annex attempts to: + +- summarize all the stage 2 PS dependencies on the MSISDN; and +- analyse the stage 2 impact of supporting MSISDN-less subscriptions for PS only MS/UEs. + +--- + +### A.2 PS stage 2 MSISDN dependencies + +#### A.2.1 General network architecture + +- TS 23.002-a11 (3GPP PLMN network architecture overview): + - clause 4.1.1.1.3 - HSS user identification handling includes providing relationship between MSISDN and other appropriate user identities in the PS domain. +- TS 23.008-920 (organization of subscriber data): + - clause 2.1 - specifies MSISDN, basic MSISDN and MSISDN-Alert indicator as permanent UE/MS subscriber data stored in Gn/Gp-SGSN as conditionally appropriate; + - clause 3B.1.2 - specifies MSISDN is used for WLAN-IW subscription; + - clause 5 - possible to retrieve or store subscriber data for a particular MS/UE from the HSS, 3GPP AAA Server , 3GPP AAA Proxy, WAG, PDG through reference to the MSISDN and IMSI. +- TS 23.228-a31 (IMS): + - clause 4.2.4a - Sh interface supports mechanisms for transfer of user related data stored in the HSS, including the MSISDN. + +Editor's note: Additional dependencies are FFS. + +#### A.2.2 GPRS + +- TS 23.060-a20 (GPRS): + - MSISDN is stored as part of HLR/HSS GPRS/EPS subscription data (clause 13.1), SGSN MM and PDP/EPS bearer contexts (clause 13.2.3) and GGSN PDP Context (clause 13.3); + - clause 9.2.2.1 - SGSN sends MSISDN to GGSN in PDP Context Activation procedure; + - clause 9.2.2.1A - SGSN sends MSISDN to S-GW in Create Session Request procedure. + +#### A.2.3 EPS + +- TS 23.401-a21 (EPS): + - clause 5.7.1 - The basic MSISDN is optionally stored in the subscription data stored in the HSS; + - clauses 5.7.2, 5.7.3 and 5.7.4 - The presence of the basic MSISDN in the MM context and EPS bearer context information stored in the MME, S-GW and P-GW is dictated by its storage in the HSS. + +Editor's note: Additional dependencies are FFS. + +## A.2.4 WLAN + +1) TS 23.234-900 (WLAN interworking): + +- clause F.3.1 - TTG retrieves the IMSI and MSISDN from the AAA server during (Interworking procedure over Gn') Tunnel establishment procedure. + +**Editor's note:** Additional dependencies are FFS. + +## A.2.5 SMS + +Figure A.2.5-1 aims at illustrating the use of MSISDN for SMS communication today. Depicted is a scenario where both the SMS Originator (UE-O) and SMS Recipient (UE-R) are roaming in VPLMN-O and VPLMN-R, respectively, and there is no Home Routeing of SMS. + +![Diagram illustrating the use of MSISDN for SMS communication (no Home Routeing). The diagram shows four network entities: HPLMN-O (Home PLMN-O), HPLMN-R (Home PLMN-R), VPLMN-O (Visited PLMN-O), and VPLMN-R (Visited PLMN-R). HPLMN-O contains a Service Centre and HPLMN-R contains an HLR. VPLMN-O contains an MSC-O and VPLMN-R contains an MSC-R. UE-O is connected to MSC-O, and UE-R is connected to MSC-R. The sequence of messages is: 1. UE-O to MSC-O: SUBMIT (MSISDN-R, 0) / RP (SC@, 0); 2. MSC-O to Service Centre: MO_Fwd_SM (SC@, MSISDN-O) / TCAP (GMSC-O@, MSC-O@); 3. Service Centre to MSC-O: MO_Fwd_SM_ack; 4. MSC-O to UE-O: SUBMIT Report; 5. Service Centre to HLR: SRI_For_SM (MSISDN-R, SC@); 6. HLR to Service Centre: SRI_For_SM_ack (IMSI-R + MSC-R@); 7. Service Centre to MSC-R: MT_Fwd_SM (IMSI-R, SC@) / TCAP (MSC-R@, GMSC-O@); 8. MSC-R to UE-R: DELIVER (0, MSISDN-O) / RP (SC@, 0); 9. UE-R to MSC-R: DELIVER Report; 10. MSC-R to Service Centre: MT_Fwd_SM_ack.](351432d1a55458897fdc5e81ffc832fe_img.jpg) + +Diagram illustrating the use of MSISDN for SMS communication (no Home Routeing). The diagram shows four network entities: HPLMN-O (Home PLMN-O), HPLMN-R (Home PLMN-R), VPLMN-O (Visited PLMN-O), and VPLMN-R (Visited PLMN-R). HPLMN-O contains a Service Centre and HPLMN-R contains an HLR. VPLMN-O contains an MSC-O and VPLMN-R contains an MSC-R. UE-O is connected to MSC-O, and UE-R is connected to MSC-R. The sequence of messages is: 1. UE-O to MSC-O: SUBMIT (MSISDN-R, 0) / RP (SC@, 0); 2. MSC-O to Service Centre: MO\_Fwd\_SM (SC@, MSISDN-O) / TCAP (GMSC-O@, MSC-O@); 3. Service Centre to MSC-O: MO\_Fwd\_SM\_ack; 4. MSC-O to UE-O: SUBMIT Report; 5. Service Centre to HLR: SRI\_For\_SM (MSISDN-R, SC@); 6. HLR to Service Centre: SRI\_For\_SM\_ack (IMSI-R + MSC-R@); 7. Service Centre to MSC-R: MT\_Fwd\_SM (IMSI-R, SC@) / TCAP (MSC-R@, GMSC-O@); 8. MSC-R to UE-R: DELIVER (0, MSISDN-O) / RP (SC@, 0); 9. UE-R to MSC-R: DELIVER Report; 10. MSC-R to Service Centre: MT\_Fwd\_SM\_ack. + +**Figure A.2.5-1: Use of MSISDN for SMS communication (no Home Routeing)** + +1) TS 23.040-920 (SMS) + +- SM-RL (Short Message Relay Layer) protocol messages can include MSISDN / MSIsdn-Alert in the following messages: + - clause 3.2.6 - SMS-GMSC/IP-SM-GW includes MSISDN and conditionally MSIsdn-Alert to set the Message Waiting Data into the HLR or to inform the HLR of successful SM transfer after polling via MAP-REPORT-SM-DELIVERY-STATUS (see TS 29.002 [18] clause 12.3); + - clause 9.3.2.4 - conditionally includes the MSIsdn-Alert in RP ERROR => MAP-REPORT-SM-DELIVERY-STATUS (see TS 29.002 [18], clause 12.3) when transfer attempt failed because the MS is not reachable or because the MS memory capacity was exceeded; + - clause 9.3.2.1 - RP MO DATA => MAP-MO-FORWARD-SHORT-MESSAGE (see TS 29.002 [18], clause 12.2); + - clause 9.3.2.2 - RP-MT-DATA => MAP-MT-FORWARD-SHORT-MESSAGE (see TS 29.002 [18], clause 12.9). +- clause 8.1.4 - SMS Router may store the MSISDN against the MT Correlation ID as part of the a routing information retrieval operation; +- clause 8.2.1 - MSC/SGSN retrieves MSISDN from VLR/HLR after receiving a short message TPDU from the MS/UE; + +- d) clauses 9.2.2 and 9.1.2.5 - the Short Message Transfer Layer (SM-TL) protocol allows for MSISDN (E.164) or other types of number-plan-identification. However the address size is limited to 12 octets, which may not be sufficient for some very long identifiers. The MSISDN is used as the address in the following messages: + - 1) SMS DELIVER (clause 9.2.2.1); + - 2) SMS SUBMIT (clause 9.2.2.2); + - 3) SMS STATUS REPORT (clause 9.2.2.3); + - 4) SMS COMMAND (clause 9.2.2.4). + - e) There is no impact on the SS7 TCAP, the addresses used on these layers being node addresses (MSC, GMSC) rather than device addresses. +- 2) TS 23.204-a20 (SMS over generic 3GPP IP access): +- a) clause 5.3.1 - IP-SM-GW acquires and maintains knowledge of the association between the MSISDN, IMSI and the address of the S-CSCF serving of the user; + - b) clause 5.3.1 - For SM MT, IP-SM-GW maps the recipient's address from an MSISDN/IMSI to TEL URI format when receiving an SMS for an IP-based UE. + +Editor's note: Additional dependencies are FFS. + +## A.2.6 IMS + +- 1) TS 23.167-b01 (IMS emergency sessions): +- a) clause 7.5.1 - PSAP uses the MSISDN (E.164) of the user for call back. + +Editor's note: Additional dependencies are FFS. + +## A.2.7 PCC + +- 1) TS 23.203-b01 (PCC architecture): +- a) clauses 6.2.1.1, A.1.3.2.1.1 and A.1.3.2.2.1 - subscriber identity (e.g. IMSI, MSISDN) provided to PCRF as input for PCC decisions; + - b) clause A.1.3.2.2.1 - For each PDP context, the PCEF shall accept the MSISDN during bearer establishment and modification and shall use this information in the OCS request/reporting or request for PCC rules. + +Editor's note: Additional dependencies are FFS. + +## A.2.8 LCS + +- 1) TS 23.271-a11 (LCS). + +Editor's note: Dependencies are FFS. + +## A.2.9 SIPTO + +- 1) TS 23.060-a20 (GPRS): +- a) Clause 5.3.12.2 and Annex B.1-2 - to support activation of "SIPTO at Iu-ps" function, the SGSN sends MSISDN to target RNC during the: + - 1) SRNS Relocation procedures (clauses 6.9.2.2.1, 6.9.2.2.2 and 6.9.2.2.3); + - 2) Service Request Procedures (clauses 6.12.1 and 6.12.2); + - 3) the intersystem change procedures from A/Gb mode to Iu mode (clauses 6.13.1.2.1 and 6.13.2.2.1); + - 4) RAB Assignment procedure (clause 12.7.4.1). + +Editor's note: Additional dependencies are FFS. + +## A.2.10 CAMEL + +1) TS 23.078-910 (CAMEL Phase 3): + +- a) clause 6.6.1.5 - for GPRS interworking for CAMEL, basic MSISDN included in the gprsSSF to gsmSCF Initial DP GPRS IF when a trigger is detected at a DP in the GPRS state model, to request instructions from the gsmSCF; +- b) clause 7.6.1.2 - for MO/MT SMS interworking for CAMEL, MSISDN included as the Called/Calling Party Number in the gprsSSF to gsmSCF Initial DP SMS IF when a trigger is detected at a DP in the SMS state model, to request instructions from the gsmSCF; +- c) clause 7.6.2.1 - for MO/MT SMS interworking for CAMEL, MSISDN may be included as the Calling Party Number in the gsmSCF/gsmSSF or gprsSSF Connect SMS IF to request the gsmSSF/gprsSSF to perform the actions to route the Short Message to a specific destination (for MO SMS) or to deliver the Short Message to the MS (for MT SMS); +- d) clause 9.4.1.1 - for GPRS Mobility Management in CAMEL, basic MSISDN included as GPRS mobile subscriber identity in SGSN to gsmSCF Mobility Management event IF; +- e) clause 10.3.1.1 -for control and interrogation of subscription data by CAMEL, MSISDN or IMSI used as subscription identity in gsmSCF to HLR Any Time Modification Request IF; +- f) clause 10.3.1.2 - for control and interrogation of subscription data by CAMEL, MSISDN and/or IMSI used as subscription identity in gsmSCF to HLR Any Time Subscription Interrogation Request IF; +- g) clause 10.3.2.2 - for control and interrogation of subscription data by CAMEL, MSISDNs used as subscription identity in HLR to gsmSCF Any Time Subscription Interrogation ack IF; +- h) clause 10.3.2.3 - for control and interrogation of subscription data by CAMEL, MSISDN used as subscription identity in HLR to gsmSCF Notify Subscriber Data Change IF; +- i) clause 10.3.3.1 - for control and interrogation of subscription data by CAMEL, MSISDN or IMSI used as subscription identity in IP-SM-GW to HLR Any Time Modification Request IF used to register the IP-SM-GW for a subscriber in the HLR; +- j) clause 11.3.1.1 - for subscriber location and subscriber state information retrieval by CAMEL, MSISDN or IMSI used as subscription identity in gsmSCF to GMLC Any Time Interrogation Request IF used to request information (Mobile Station location) from the GMLC; +- k) clause 11.3.3.1 - for subscriber location and subscriber state information retrieval by CAMEL, MSISDN or IMSI used as subscription identity in gsmSCF to HLR Any Time Interrogation Request IF used to request information (any one or more of subscriber state, subscriber location, IMEI (with software version) and MS classmark information for the requested domain) from the HLR; + +Editor's note: Additional dependencies are FFS. + +## A.2.11 Other services + +1) TS 23.066-900 (MNP): + +- a) Various - describes several alternatives for the realisation of Mobile Number Portability to retain ones MSISDN. + +2) TS 23.141-900 (Presence Service): + +- a) clause 6.1.1 - MSISDN can be the contact address attribute of the subscriber. + +3) TS 23.246-950 (MBMS): + +- a) clauses 8.2 and 10.3 - MSISDN is passed from SGSN to GGSN and GGSN to MB-SC during MBMS Multicast Service Activation to provide the operator with the ability to associate GPRS location information (i.e. serving network identity) with a user. + +4) TS 23.240-900 (3GPP GUP): + +- a) Annex B - GUP access for the "PLMN specific user information" by the S-CSCF and AS includes the MSISDN; +- b) Annex B - GUP access for the "Authorized and subscribed service information for CS & PS" by the MSC/VLR, GMSC, SGSN, GGSN and MMS server includes the MSISDN. + +Editor's note: Additional dependencies are FFS. + +--- + +## A.3 Impact of MSISDN-less subscriptions for PS only MS/UEs + +Editor's note: Analysis is FFS. + +--- + +## Annex B: Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|----|-----|------------------------------------------------------------------------|-------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2010-09 | SP-49e | SP-100562 | - | - | MCC Update to version 1.0.0 for presentation to TSG SA for information | 0.5.1 | 1.0.0 | +| 2012-08 | SP-57 | SP-120489 | - | - | MCC Update to version 2.0.0 for presentation to TSG SA for approval | 1.7.0 | 2.0.0 | +| 2012-09 | - | - | - | - | MCC Update to version 11.0.0 after TSG SA approval (Rel-11) | 2.0.0 | 11.0.0 | \ No newline at end of file